[GUIDE] Port firefox OS to Nexus 4 + Galaxy 2 Dual Boot - Firefox OS General

How To Install Firefox OS on a nexus 4 and dual boot. ​
XDA-Developers member pureexe has created an Image that will help you to port Firefox OS to your Google Nexus 4. Here is the list of what works and what doesn’t works:
What Works:
– Wi-Fi
– Data
– Phone Calls
– Contact Import
– GPS
– SMS/MMS
-Some Sensors (Light+Gyroscope+Acceleration)
-ADB
Does NOT Work:
– Camera
-MTP/PTP
– A lot of other things
How To Flash
Step 1: First connect your device to PC (desktop/laptop) via USB and make sure that USB debugging enabled on your device.
Step 2: Now to be on safe side create a Nandroid backup from recovery its because if something goes wrong then you can easily backup all your data.
Step 3: After creating backup, now download the ROM (FFOS_mako_********.zip) file and place these files on the SD card of the phone.
Step 4: Now switch off the phone and boot the phone into Recovery mode.
Step 5: Assuming you are in the Recovery mode and now you have to wipe the full data on your device. To do this, you have to click on “Wipe Data/Factory Reset” option. As soon as you click on “Wipe Data/Factory Reset” option a new screen pop-up where you have to click on “Yes” option.
Step 6: After wiping out all the data on your device you have to wipe the cache & the dalvik cache also.
Step 7: Now go to “install zip from SD card” option and click on “select zip from SD card”. After selecting the option “select zip from SD card” you have to choose the ROM file.
Step 8: After performing all the correctly in step 7 you have to clear the cache and & dalvik cache again.
Step 9: Now, go to “Install zip from SD card” option and click on “Select zip from SD card”. After selecting the option “Select zip from SD card”, you have to choose the optional file like home app or server module
Step 10 : Assuming you have performed all the steps correctly, now simply reboot your device and it will boot into Firefox OS.
Click to expand...
Click to collapse
How to dual boot: ONLY FOR GALAXY S2
Warning: This procedure doesn't really work anymore. It only works with Android 4 (Ice Cream Sandwich) and Siyah Kernel v 5.0.1. Later versions of either won't work. Consider this guide archived, and use it at your own risk.
If you want to test B2G from time to time but continue using Android as your main OS and you have a Samsung Galaxy S2, you can choose to install B2G in a separate partition (which is already present on the phone) and choose where to boot into when your device starts.
Prerequisites
In order to dual boot Android and B2G, you have to meet these prerequisites:
You have to have built B2G for the Galaxy S2
You have to download the Siyah kernel v. 5.0.1 for the Galaxy S2
You need the tool simg2img, that you get automatically if you build B2G following the guide on MDN
You need the heimdall tool, best if version 1.3.1 as you may encounter problems with version 1.3.2
One-time operations
There are several operations to do in order to get a working dual boot. The following ones need to be done the first time only.
In order to use heimdall without requiring root access, you should create a file called android.rules (the portion of the name before the .rules extension is arbitrary) and place it in /etc/udev/rules.d. The file should contain a line line the following:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
In order to activate this rule, you should restart udev:
Code:
sudo service udev restart
and then unplug and replug in the phone. The above rule will also allow adb to access the SGS2 without requiring root privlidges.
Flashing the Siyah kernel
The Siyah kernel is mandatory for the dual boot, because it is this kernel that manages it. Once you have downloaded and decompressed the tar file, you'll be left with a file named zImage. In order to flash it on your phone you have to follow these steps:
Switch off your phone
Reboot in download mode (press together volume down + home + power buttons and then, when asked, volume up button)
Use heimdall to flash the kernel with the following command (your phone needs to be connected to your PC):
heimdall flash --kernel /path/to/zImage
Once the kernel is flashed the phone will reboot.
Preparing the B2G rom environment
Once you've installed the Siyah kernel, it's time to use its functions to prepare the environment to install your B2G image in the secondary partition. Follow these steps:
Switch off your phone
Reboot in recovery mode (press together volume up + home + power buttons)
In the CWMR Touch interface, go to dual-boot options -> Wipe 2ndROM data/cache -> Yes - Wipe. This operation will take some time
Once the operation is finished, select Go Back and then reboot system now to reboot your phone. If you check, inside the internal SD card of your phone you'll now have a .secondrom directory with inside two files named cache.img and data.img.
B2G update operations
The following operations need to be done every time you build a new version of B2G.
In order to simplify command line instructions, it's advised to copy all needed files in a same folder of your choice. These are the files that need to be copied inside the folder:
Code:
simg2img, found in B2G/out/target/product/galaxys2/system/bin/
system.img, found in B2G/out/target/product/galaxys2/
userdata.img, found in B2G/out/target/product/galaxys2/
Once you have all the files in one place, do the following:
Create a data.img file out of the sparse file userdata.img. You can do it with the following command:
Code:
simg2img userdata.img data.img
Put the data.img file on your phone's .secondrom folder. You can do this either by enabling file storage mode on your phone and connecting it to your PC or, if you have USB Debug active, you can use adb:
adb push /path/to/data.img /sdcard/.secondrom/data.img
Switch off your phone
Reboot in download mode (press together volume down + home + power buttons and then, when asked, volume up button)
Use heimdall to flash B2G firmware inside the second partition:
heimdall flash --hidden system.img
Once the flash is finished, your phone will reboot and at boot time you can boot into your second rom (the B2G one) by pressing the home button during the bootloader countdown. If everything has gone right, once you've finished booting B2G you'll have a black screen on your phone. You now have to install Gaia.
Note: Depending on how you want to test B2G, you may not want to put a new data.img file on the phone every time you update B2G, as it will wipe all of your preferences, installed applications and in general pretty much everything you've done while using B2G.
Boot operations
The following operations need to be done every time you boot inside B2G.
Unfortunately, there's no simple way to put Gaia inside the system.img B2G image, and it get lost when you switch off your phone, so you'll need to install Gaia again every time you boot inside B2G. To install Gaia, type the following on a console after you've booted your phone inside B2G (so you have a black screen) and have connected your phone to your PC:
cd B2G/gaia
GAIA_DOMAIN=foo.org make install-gaia
After the upload of Gaia is completed, on your phone's screen the B2G interface will appear.
Click to expand...
Click to collapse
Dual Boot With Nexus 4 :
Original Link Here
Text Steps :
-Download FFOS.zip file
-Go to TWRP recovery
-Go to advanced, MultiROM, add ROM
-Select android, and don't share kernel
-Select next, then select zip file
-Select the FFOS.zip file
-After that go to list ROMs, pick FFOS, select flash zip, and flash the addons you want
-Reboot to multiboot
-Select FFOS and boot it
-Wait about 2 minutes
-You're now booted to FFOS
BTW FFOS stands for firefox OS
Downloads :
FFOS image Here
Contributors + Complier
pureexefor image and steps
Mozilla (for Dual Boot 1)
Riro Zizo for dual boot 2
Me, for putting all this stuff together!

@Apph3x
I have two version of porting
- Base Jellybean 4.3
- Base Kitkat
i know Base Kitkat is bad but working fine on base Jellybean 4.3
on jellybean everything working except MTP
Please read this post http://forum.xda-developers.com/showpost.php?p=44451567&postcount=2

Thanks
@pureexe I know but I'm sparse on time will update soon. The image is your latest 1 tho ;D thanks for original guide

Updated
Removed by owner
vvvvvvvvvvvvvvvv

Updated
UPDATE BASE LAYER 4.3
What Works:
- Wi-Fi
- Data
- Phone Calls
- Bluetooth
- Camera (Rear Camera & Front Camera)
- Video Record
- GPS
- SMS/MMS
- MUSIC (Mp3 & ogg decoder working)
- USB tethering
- WIFI tethering
- Video HQ decoder
- Sensor (Light+Gyroscope+Acceleration)
- ADB
- A lot of thing
Does NOT Work:
-MTP/PTP
Download
http://forum.xda-developers.com/devd...ct/dl/?id=3793

Related

Complete Mod guide for Mytouch 3g 32b w/o data

How to root and mod a Mytouch 32b without a data plan
This is the exact same phone that I had 32b HBOOT-1.33.0006 (SAPP30000)
I tried to root it and install several different root methods and several different roms. I never bricked the phone, but I did at one point have a phone that would go to the cyanogen bootsplash screen, then continually reboot.
The issue that I had was that I didn't have a data plan, and the mytouch is set up where the phone must register with google before it can be used. To get to the wifi screen, you first had to register with google, so without a data plan, the phone was worthless. To bypass the data plan, I put an old tmobile sim in the phone, went to the corporate store, told my tale of woe, and begged then to let me use a sim with a data plan so I could register with google. I actually had to do this twice because the first tome I rooted and modded the phone, I was stuck in a boot loop and I got scared, and reset the phone to factory. The phone would boot up, but when it got to the modded rom, it would always just reboot and reboot. I googled all over the place about all of these issuse, and decided to compile everything so that someone else could benefit, and if I forgot how I did it, years later I would have a reference. I also never formatted my sd card to fat32 because I did it before. It is a good idea to remove old files from the root of the SD card once you have finished flashing your phone.
This is the first step I did, and it worked perfectly.
[MT3G 32b] Root / Break perfect SPL / Way less steps from http://forum.xda-developers.com/showthread.php?t=570659
I'm creating this thread in hopes no one who owns a MyTouch, in America, on T-Mobile with a perfected SPL doesn't have to go through the brain numbing process I've just adventured through over the past week.
Special thanks to Amon_RA and Radix999 who have compiled an impressive set of information on this topic. I would have been totally lost without their contributions to this forum.
Setup:
You'll need a brand-spanking-new MyTouch 3G, 1.6 updated, un-modded, perfected SPL [Mine was: HBOOT-1.33.0006 (SAPP30000)]. To find out if your SPL is perfected power your phone off: press the vol button down > hit the power button > compare the info listed in fastboot (white screen with three skateboarding Androids) to Amon_RA's list of SPL's. If you have done anything to your phone before attempting this process go consult someone who knows wtf they are doing. I don't, but I rather tell people how this went down for me.
How I Rooted my MT3G:
1. Get your phone back to 1.5 cupcake by whatever means necessary. I used these directions: http://theunlockr.com/2009/08/22/how...ur-mytouch-3g/ (see below they are copied for your convienience)
How To: UnRoot Your MyTouch 3G/MyTouch 1.2 MyTouch and Get Back to Cupcake (Updated 04.19.10)
Written by: David Cogen
Posted on 08.22.09
Android How To's (Advanced), Featured, How To's, HTC MyTouch 1.2/Fender myTouch How To's (Advanced), HTC MyTouch 3G How To's (Advanced), Video
562 Comments
UPDATE: THIS NOW WORKS ON THE MYTOUCH 1.2 (THE MYTOUCH WITH THE 3.5MM HEADPHONE JACK AT THE TOP) AND THE OLD MYTOUCH AS WELL.
1. Download the correct .nbh file for your device and rename it to sappimg.nbh if necessary (make sure it is sappimg.nbh and NOT sappimg.nbh.nbh or anything else)
NBH File (Works for the Old MyTouch)
Zip File (Works for the new MyTouch w/ 3.5mm headphone jack) RENAME IT TO sappimg.zip (not sappimg.zip.zip, just sappimg and its a .zip file!) Thanks Caesar for sending this in!
2. Save the sappimg.nbh/sappimg.zip file to your SD card. As always, do not place it in any folder on the SD card, just on the SD card.
3. Put the SD card into the phone and turn the phone on by holding down Volume Down and Power.
4. Push the trackball down on that screen and wait for it to pick up the Sappimg.nbh.
5. Push the trackball to begin, it should automatically update from there.
6. Once the flashing is fully complete, reboot the phone. DONE!
Reported Issues
Issue: Phone says that the wrong Main Version is Older or Wrong Model ID…
Solution: Use our Goldcard Method instead.
2.Follow these steps to root your device: http://theunlockr.com/2009/08/29/how...-in-one-click/. When you are done with this process you should have Amon_RA's recovery and boot loader all setup. This will allow you to format your SD card to whatever file system you want, flash roms, do nandroid backups, the works.
Once your phone is reflashed with sappimg.nbh if you do not have a data plan, you will have to head to your nearest tmobile corporate store and beg to use a data sim. They are pretty nice, and will usually allow you to do it. Register your phone with google, then quickly go to market and install Astro File Manager, or Linda File Manager. If you do it right away with a tmobile data sim, that is the best. If you want to do it later on wifi, it is difficult. You might be able to do it right away as soon as you register with wifi because I managed to install one program that way. Shortly after you register with wifi, tmobile does something in your phone that prevents market from working. You get a download unsuccessful error over and over. I finally figured out you could take out the tmobile sim and replace it with a different sim, and the market would start working again, but it is a hassle, and you might not have a non tmobile sim handy.
I then proceeeded to the following proceedure
How To: Root the HTC Magic in One Click! http://theunlockr.com/2009/08/29/how-to-root-the-htc-magic-in-one-click/
Written by: David Cogen
Posted on 08.29.09
Android How To's (Advanced), Featured, How To's, HTC Magic How To's (Advanced), Video
422 Comments
I. Read Before You Begin
1. You must downgrade back to cupcake first:
Get Back to Cupcake for Magic
After you have done the above procedure and are back on cupcake (Android 1.5), you can come back to this procedure and continue.
II. How to Check Your Motherboard Version
1. Turn off your phone
2. Turn the phone on by either holding down the volume down button and power button at the same time OR by holding down the back button and power button at the same time.
3. When the screen comes up, it should say somewhere on the first line either 32A or 32B. THAT is your motherboard version. Remember it…
4. Turn off and on the phone.
5. Goto Settings > Applications *> and make sure Unknown sources is checked ON.
III. Root the Magic
1.Â*Download this APK and the appropriate recovery image for your motherboard (32A or 32B) and save it to your computer:
FlashRec.apk (Updated: 09/26/09)
Amon Ra’s Recovery Image (32B)(Updated 11.18.09)
Amon Ra’s Recovery Image (32A)(Updated 11.18.09)
2. Once they are saved to your computer, copy them both to your SD card (do NOT put them inside any folders on the SD card, just put them on the SD card itself).
3. Unplug the phone from the computer once they are downloaded to the SD card.
4. Goto the Market and download Linda File Manager or any file manager program if you do not already have one.
5. Open the file manager and goto SDCard and then find the FlashRec apk file and click it. If asked tell it to use Package Installer to open it.Â*It should automatically install the apk.
6. Open the FlashRec program and click on Backup Recovery Image and wait for it to finish.
7 (FOR 32A ONLY) Once done, click on the empty text box in the FlashRec program and type:
/sdcard/recovery-RAv1.6.2H.img
7 (FOR 32B ONLY) Once done, click on the empty text box in the FlashRec program and type:
/sdcard/recovery-RA-sapphire-v1.6.2G.img
8. Then click on the Flash Custom RecoveryImage button and wait for it to finish.
9. Turn off the phone and turn it on into Recovery mode by holding down Home and Power to turn it on (keep holding until the recovery screen comes up has a bunch of text on a black background). So long as that screen comes up, you have done it correctly and can now go on to the*How to Load a ROM video for your appropriate device!
10. To get Root access you MUST go to the next video mentioned above and load a custom ROM.
Reported Issues
Issue: I get Invalid Recovery Image when using the FlashRec program.
Solution: Make sure that the spell correction and auto completion are OFF in the Text Settings (Settings > Locale and Text > Touch Input > Text Input then turn off Prediction, spell correction, and word completion) of your phone. If not then it may put in spaces where they do not belong. (I had it put a space after .img and couldn’t see it so couldn’t figure out why it kept saying invalid recovery image, like you guys).
Other than that, just make sure it is on the root of the SD card (not in any folder) and that you are typing in the recovery name and filepath correctly.
Then and it should show Flash Recovery Image.
Issue: When I download the FlashRec.apk it shows up as a .zip not an apk.
Solution: No problem. Do NOT extract it, just simply replace the .zip with .apk and then proceed with the procedure.
Issue: I get backup failed or flash failed when I try to use the FlashRec progam.
Solution: This is most likely because you already have a custom recovery image, please use one of the unrooting procedures to get back to the original recovery image and THEN you can use this procedure.
Also, instead of doing that, if you have root access, you can just put the recovery image on your SD card then go into Terminal (download it from the Market if you don’t already have it) and type:
flash_image recovery /sdcard/recovery-RA-dream-v1.2.3.img
3.
3. Go to Amon_RA's thread about SPL's: http://forum.xda-developers.com/showthread.php?t=529019
and download a Engineering SPL for your phone. (Engineering SPL 1.33.2004 by Crios worked for me)
4. Edit the SPL file name to "update.zip"
5. Load the SPL to the root of your SD card.
6. Load up RA's boot loader. (Power + Home)
7. Wipe / Clear from the boot loader menu.
8. Apply update.zip from the boot loader menu.
9. Wait for the phone to reboot, all kinds of whacky **** will happen, don't mess with the device, etc. Eventually you should reboot into recovery mode. Whatever you do - figure out how to get to recovery mode.
10. Wipe / Clear from the boot loader menu.
11. Format the SD VIA boot loader.
12. Load a new / favorite ROM onto the SD. (I use Blueberry Hero)
13. Install the Rom VIA boot loader.
14. Crack open a beer.
No gold card, fastbook, no crazy 40 step process. There may be some security issues or something involved with this process. Whatever the case, whatever the politics are between XDA/unlockr - this WORKED for me from a STOCK 1.6 device.
With a little bit of reading you should either have turned your phone into a 400$ brick or a happy little Hero pumping Android phone.
Cheers.
I backed up whatever was on my SD card, and then did this proceedure without the SuperWipe.conf step.
[WIPE][COMPLETE][FLASHABLE] SuperWipe v2 (30 Jan 2011) - So Fresh and So Clean Clean! http://forum.xda-developers.com/showthread.php?t=834812
One thing we have run into with BiffMod ROM is that there is no single "COMPLETELY erase the phone" solution.
So this is my attempt at it.... No console/terminal, no adb shell, no USB, no anything required. Just flash the file in recovery and you are done.
But OHSAKA! There are tons of threads about this, there are even existing "wipe-update" files to erase the phone. What makes your flashable update file so special???
Well I'm glad you asked that. This update contains the 'erase_image' executable with all the needed libraries statically linked. (thanks ezterry) 'erase_image' performs a low-level format of the partition which can fix unforeseen problems. Most other wipe-updates just perform "rm -rf *" at the file system level and don't touch the boot partition.
v2
---
Kudos to RichieDaze! He stepped up and added some often requested functionality to this popular wipe script. Now SuperWipe will check the root of the /sdcard/ directory for a file named "SuperWipe.conf". This file will control which partitions get erased and also control if the script triggers an auto-reboot. If the file is not present, then the script will default to wiping all partitions.
SuperWipe.conf
Code:
## SuperWipe Custom Configuration
## So Fresh and So Clean Clean Menu
## Cannot be blank (yes or No)
#
Wipe_Cache=yes
Wipe_Userdata=yes
Wipe_System=yes
Wipe_Boot=yes
Wipe_Sd_Secure=yes
Wipe_Sd_Ext=yes
#
##
## Extras
#
Reboot_when_done=no
Reboot_Delay=5
#
##
SuperWipe v2 (MD5: a3c358c1e027c8ec039ada8e667cab1a)
SuperWipe.conf (MD5: 1e7eb3a97270142aa6bf7c4fca9c2490)
You will need to reboot back into recovery after running this. If you forget and try to boot normally, you will have to pull battery to power off.
v1
---
This update will:
1) Call erase_image on CACHE, SYSTEM, USERDATA, and BOOT partitions
2) Mount /sd-ext (if it exists) and delete all files from it
3) Delete all files in the /sdcard/.android_secure directory which is where all the froyo apps2sd files live
4) Run e2fsck (file system repair) on the your ext partition
5) Log all output to the /tmp/wipe.log file (if you care)
I think this is the most complete way to wipe a phone. It supersedes 'fastboot erase system -w', VOL_DOWN+HOME+BACK, Amon_RA wipes, or various other flashable update-wipe zips.
I have tested this file the best I can on my phone. I verified all partitions are completely empty after running it. Any suggestions or bug reports are welcome!
SuperWipe (MD5: 945218bbbeab63d2c41e20c3243176ce)
You will need to power off and reboot back into recovery after running this. If you forget and try to boot normally, you will have to pull battery to power off.
I then went with this modded rom. It works pretty well.
http://android.modaco.com/content/h...tom-rom-for-gsm-hero-now-with-online-kitchen/
I'm pleased to present my MoDaCo Custom Hero ROM! No 'wipe' is required for anyone coming from MCR 1.2 onwards, or the stock 2.73.x updates.
You can now create a customised ROM containing only the parts you required - click here to read more about the MoDaCo Custom Custom ROM online kitchen!
MCR now includes a MoDaCo Custom Kernel modified by Teknologist, TCK, for additional features.
MCR now optionally includes Wavesecure in ROM, allowing you to lock / locate / wipe your device remotely in the event of loss and be notified if the SIM is changed. The application cannot be uninstalled by a thief and we we have actively worked with Wavesecure to ensure that your settings will survive a hard reset!
This ROM is based on the 2.73.x release series (currently 2.73.771.73 together with my own optimisations) for the best possible performance! The ROM is now available in 2 core versions, with and without Chinese input, with optional add on packs that can be applied to either ROM.
Included in the 'core' version
- Built with my new MCR build process which reduces size and boost speed of the ROM
- Includes Teknologist's Custom Kernel 1.91 featuring additional filesystem support (EXT4, NFS, CramFS, SquashFS 4.0), CompCache modules and config, DroidWall support and much more! See here for details.
- Rooted with 'adb remount' permission and superuser APK
- A2SD included (fully automatic - thanks cyanogen!) - create a EXT2, EXT3 or EXT4 partition as your second partition to use. dalvik-cache remains on device.
- Added Jbed Java
- Added Google Voice Search and required speech library
- Added Dropbear SSH server running by default, check 'About' screen for password (port 2222). You can now remove this by running /system/bin/removedropbear.sh
- Added Notes app from Dragon ROM
- Added Spare Parts (run it and switch the 2 animation types to 'fast' for an even better experience!)
- Added android-wifi-tether 1.60 pre3 (props to the developer, this is a great app!)
- Added WiFi Status indicator, with kind permission of Andrew Schwimmer
- Added busybox 1.15.3 with Droid Explorer support
- Added Titanium Backup
- Added all 4 available HTC widgets
- Added nano 2.09 - text editor for use in shell mode
- Added parted and sqlite tools
- Added terminfo and settings to boot.img to allow nano etc. use
- Added files required for Debian linux including loxley's updated bootdeb script
- Added huge APN list
- Moved Quickoffice to data partition to allow easy uninstall
- Deleted 'Learn More' application
- ROM now includes touch focus in Camera app
- ROM now supports shortcuts using BetterCut (and therefore I assume anycut!) in Rosie
- Silenced boot sound (it's still there and can be reactivated with a file edit)
- You can now check your MoDaCo Custom ROM (MCR) version from the about menu
Included in main 'enhanced' add on pack
- Added Business Card Scanner
- Added 'Plurk' client (currently unavailable)
- Added WAP browser
Other optional add on packs (apply as normal update zips)
- 'WaveSecure' add on pack (puts Wavesecure in ROM - it is no longer in core)
- 'Boot Sounds' add on pack (restores boot sounds)
- 'Hebrew Fonts' add on pack (installs hebrew fonts)
Recommended applications (available from the market)
- More Locale for setting non english Locales
Downloads
This ROM is also available customised to your exact requirements in the MoDaCo Custom Custom ROM online kitchen in the second post of this topic - check it out!
'Core': DOWNLOAD (Mediafire Pro) - MD5: d767e7335a4bb6ef022e7d3082f28bb7
'Enhanced' add on pack: DOWNLOAD (Mediafire Pro)
'Wavesecure' add on pack: http://www.wavesecure.com/installations/update.zip
'Boot Sounds' add on pack: DOWNLOAD (Mediafire Pro)
'Hebrew Fonts' add on pack: DOWNLOAD (Mediafire Pro)
ENSURE YOU DO A NANDROID BACKUP SO YOU CAN 'ROLL BACK' IF REQUIRED!
A 'wipe' is MANDATORY when installing this ROM if you are coming from pre MCR 1.2 or a stock 1.x ROM, and you MUST do this BEFORE applying the update zip (as the update zip puts files on the data partition)! I also recommend you install the latest radio from my 'update zips' topic if you have not done so.
Please note that first boot may take a little while, especially if you have a lot of apps on your A2SD partition. Be patient! If you want a real clean start or you have issues with your existing A2SD installed apps when you boot, you need to wipe your EXT3 partition on SD too by executing 'adb shell rm -r /system/sd/app', 'adb shell rm -r /system/sd/app-private' and 'adb shell reboot'
The ROM is in an update.zip format for installation via the custom recovery image, I also strongly recommend installing the latest radio (63.18.55.06JU_6.35.08.29 at time of writing). As always, do a Nandroid backup before you do anything... just in case!
For the complete newbies, these are the steps you need to take with a 'virgin' Hero:
- Download the patched recovery image linked above and install as detailed in that post
- Download this custom ROM, and copy it to your SD card
- Enter the recovery image (if you're not in it already) by powering on while pressing 'home'
- Select 'nandroid backup' from the menu to do a backup
- If you copied the custom rom as update.zip, select 'apply sdcard:update.zip', else select the option below.
- all done
If you would like to remove parts of the ROM that you do not use, see this post.
Feedback / feature requests welcome!
Finally, if you would like to show your appreciation for the ROM, please consider supporting MoDaCo by signing up for a MoDaCo Ad Free or MoDaCo Plus account, both of which also give you early access to Beta ROM releases and access to the the online kitchens.
flashrec.apk
here is the flashrec.apk file I used. I had a hard time finding it on the net, the website was down
Honestly, this method is much easier... http://forum.xda-developers.com/showthread.php?t=1121776
That method might be easier, but I was having trouble getting the SDK installed on my machine. I wanted to do everything from the phone, and I needed detailed step by step instructions.
Thanks for the help.

Full OpenAOS Boot Menu Instructions

Full OpenAOS Boot Menu Instructions
Index:
Thanks/Index
Install the SDE
Install Boot Menu
Install Cyanogen
Install Urukdroid on the openAOS Boot Menu
Editing the menu.lst
Videos
Links
Any one could say to me how to link posts inside a Thread? without opening a new tab?
Thanks:
Thanks goes to:
msticninja for give me Instructions how to install Urukdroid on the Menu.
Bubu for creating the openAOS Boot Menu and Cyanogen.
$aur0n for creating Urukdroid.
vantoman for telling me the right init.rc mounting line for urukdroid.
AlaskaPardus for telling me how to install gapps on cyan.
Install the SDE
Install the SDE
The SDE is a "Special Developer Edition"(=SDE) - Firmware, from Archos, usually only for Developers.
It cames with the Angstrôm Linux-Distribution.
You can use the normal Archos Android, if you have the SDE installed.
Warning, you will loose your Warranty by installing this firmware!
Your device will be watermarked after installation, so Archos can detect that you have installed the SDE!
Installing the SDE:
1) Shut down your Archos.
2) Boot your Archos by holding down the Volume Up ( + ) Button.
3) You will get to the Recovery Menu. You can navigate with the Volume Buttons and the Power Button.
4) Choose "Update Firmware" and connect your Archos with your PC (USB).
5) Download the SDE Firmware here: http://www.archos.com/support/support_tech/_ppp.html?country=de&lang=de&p=gen8
6) Copy the firmware_archos_android_gen8.aos file to your Archos and press the Power Button once.
7) Your Archos now install the SDE Firmware.
8) When you Boot up, your Archos will normally Boot the normal Archos Android, but if you hold down the Volume Down ( - ) Button during Boot Up, you will see the "Boot Menu". (This isnt the openAOS Boot Menu!)
Install Boot Menu
The openAOS Boot Menu, developed from Bubu, allows you to Boot multible OS (f.e. Archos Android,Linux,Cyanogen,Urukdroid,etc...)
Install the Boot Menu:
1) Shut down your Archos.
2) Boot into the SDE Boot Menu by holding down the Volume Down ( - ) Button.
3) Choose "Recovery System" >> "Developer Edition Menu" >> "Flashing zImage and Initramfs".
4) Connect your Archos with your PC (USB).
5) Download the lastest openAOS Boot Menu files (zImage & initramfs.cgio.gz) from here: http://download.openaos.org/bubu/gen8/
6) Copy these two files to your Archos and press the Power Button once.
7) Your Archos now flashes the Boot Menu`s zImage and initramfs.
8) From now on, when you Boot Up your Archos, the openAOS Boot Menu, will showed you can navigate trough the Menu with the Volume Buttons and the Power Button.
9) From standart you will be able to choose between "Archos" (Normal Archos Android) and "Angstrom" (SDE Linux Distribution)
Please often look into the download archive of Bubu ( http://download.openaos.org/bubu/gen8/ ) for a new version of the Boot Menu!
Install Cyanogen
Install Cyanogen
"CyanogenMod is an aftermarket firmware for a number of cell phones
based on the open-source Android operating system.
It offers features not found in the official Android based firmwares of vendors of these cell phones."
(from cyanogenmod.com)​
You can use the lastest Cyanogen version (based on Android 2.3.4 Gingerbread) with the openAOS Boot Menu. (Both systems are from Bubu)
Install Cyanogen
1) Boot into normal Archos Android and connect it with your PC.
2) Download the lastest Cyanogen *.img file from here: http://download.openaos.org/bubu/gen8/android/
3) Once your downloaded the lastest *.img file from there, you have to rename it to "openaos-gingerbread.img.
4) Now copy that file into the root of your Archos.
5) Now download this menu.lst file (from gbohm) http://www.filesonic.com/file/1302552154/menu.lst.
6) Copy that file to the root of your Archos. (maybe copy&overwrite)
7) Reboot your Archos.
8) I you should see a new entry in the Boot Menu, named "Ginger-bread", choose this.
9) Your Archos now boots Cyanogen!
Please often look into the download archive of Bubu ( http://download.openaos.org/bubu/gen8/android/ ) for a new version of Cyanogen!
Install Urukdroid on the openAOS Boot Menu
Install Urukdroid on the openAOS Boot Menu
UrukDroid is an Android distribution for Archos GEN8 devices.
It's mix of Android 2.2.1, original Archos OS with different Linux/GNU utilities, kernel patches and all kind of modification.
Goal of this system is to allow users to do most of the operations
they are allowed to do on normal Linux distributions.
It's aimed for more advanced users, but tries to be useful on basic level of all people if they don't need special features.​(from http://code.google.com/p/urukdroid/)
Urukdroid is created by $aur0n and many other developers.
Some Users may have problems with this, because you need a bit of Linux Knowledge!
Install Urukdroid on the openAOS Boot Menu
If you dont have Urukdroid already, please also follow the Orange Instructions.
Otherwise start with the Black Instructions below.
1) Shut down your Archos.
2) Boot into the SDE Boot Menu. and choose "Recovery System" >> "Developers Edition Menu" >> "Flash Kernel and Initramfs"
3) Connect your Archos with your PC (USB).
4) Download the Urukdroid 1.1 Installation file from here: http://sauron.pourix.com/UrukDroid/UrukDroid-1.0/UrukDroid_1.0-Install.rar
5) Extract the 3 files inside.
6) Copy the zImage and initramfs.cpio.gz files to your Archos.
7) Press the Power Button once.
8) Your Archos now flash the Urukdroid Kernel.
9) Restart your Archos into the SDE (Holding down Volume Down ( - ) Button)
10) Choose your options at the EasyInstall of Urukdroid.
11) Follow the Installation Process of Urukdroid.
12) You now have Urukdroid.
1) If you dont have Linux on your PC already, please download a Ubuntu Live CD from here: http://www.ubuntu.com/download/ubuntu/download
2) Boot your PC with that CD/USB Stick.
3) Shutdown your Archos.
4) Boot into the SDE Boot Menu. (Hold down Volume Down ( - ) Button)
5) Choose "Recovery System" >> "Repair System" >> "Start USB MSC" and connect your Archos to your PC with booted Ubuntu. (USB)
5.5) You should now see 3 "Devices" connected to your Archos.
These are the 3 Partitions of your Archos.
6) Download this file: http://www.mediafire.com/?oi9g4kujjsytd9x
7) Extract the files out of the archive (one folder & one file)
8) Go to Terminal. (Applications >> Accessories >> Terminal)
9) Type "sudo nautilus"
10) A window, like the Windows Explorer, should open.
11) Go to the directory, where you extracted the archos.inc out of the downloaded file.
12) Copy that file to the root of your Urukdroid Partition.
The Urukdroid Partition is normally 0.5 GB or 1.0 GB big.
13) Now go to the Directory where you have extracted the 2.6.29-omap1 folder out of the downloaded file.
14) Copy that folder into [YOUR URUKDROID PARTITION]/lib/modules.
(You first have to delete the, on your Urukdroid Partition excisting,2.6.29-omap1 folder)
15) Download this file and extract the 2 files out of it http://www.mediafire.com/?xaabbc9in9q4l2u
15) Overwrite the init.rc file on the root of your Urukdroid Partition with the downloaded and extracted one.
[COLOR="Red[COLOR="Red"][/COLOR]"]Warning! This init.rc only work if you have urukdroid installed on internet flash!
You, who have urukdroid installed on sd, please do this steps:[/COLOR]
1) Search for the (commented) Topic "Mount Partitions"
2) The third line under this Topic is commented. (with a #)
3) Uncomment it by erase the #.
4) Now change the line from "mount |____| /data noatime nosuid" (i forgot the middle-part) to "mount ext4 /dev/block/mmcblk1p3 /data noatime nosuid"
(if you use Urukdroid from sd card you have to change the line to "mount /dev/mmcblk2p3 /data")
5) Now search a Topic called "First Boot Logo" (or so) with only one line under it.
Warning: You just have to do this 2 following steps, if you dont have the A70 S or H
6) You have to add the line "exec /system/bin/flip.sh", but you have to add this below the excisting command under the Topic!
7) Save the init.rc file and exit the text editor.
23) Copy the downloaded and extracted file flip.sh to /system/bin
Warning: The following steps should done by all(also the A70 S or H users!)
24) "Exit" the Urukdroid Partition safely and press the Power Button. (on your Archos)
25) Boot your Archos into the normal Archos Android and connect it with your PC. (You can choose if you use Ubuntu or Windows for this, i used windows)
26) Open the file, named menu.lst.
--> If you do it on Windows, be sure you open it with Notepad ++ (can downloaded here: http://notepad-plus-plus.org/release/5.9.2) and that you have enabled the UNIX line endings! (Edit>>EOL Conversation>>UNIX)
27) Add the line:
Code:
UrukDroid|/dev/mmcblk1p2|/rootfs.img|/init|0
If you use Urukdroid from SD Card you have to change "/dev/mmcblk1p2" to "/dev/mmcblk2p2".
28) Save the file and "exit" your Archos safely and reboot your Archos.
29) Boot Up your Archos, now you should see a new Option, to choose, named "Urukdroid".
30) You now have Urukdroid running on the openAOS Boot Menu!
Editing the menu.lst
Editing the menu.lst
This Tutorial is for the more powerful users!
The menu.lst say to the openAOS Boot Menu, which OS are installed on the Device.
The Standart menu.lst, automatically created by the menu on first boot up, looks like:
Code:
Archos|ARCHOS|ARCHOS|/init|0
Angstrom||/rootfs.img|/sbin/init|1
Lets investigate a normal line:
Code:
Angstrom||/rootfs.img|/sbin/init|1
----1---|2|-----3----|-----4----|5
1) The first Part is the name, that is showed on the Boot Menu.
2) The second Part (empty here) is the Developer/producer of the Rom/OS/Image
3) The third Part is the name and directory of the Image File to Boot.
4) The fourth Part is the directory of the root of the Imaeg/Os.
5) The fifth Part is the SGX Overlay Version, you have to set :
"1" for a Linux/Debian OS/Image
"0" for a Android Os/Image
Editing the menu.lst on Windows
If you want to edit the menu.lst on Windows you have to use Notepad++ for this. (can downloaded here: http://notepad-plus-plus.org/download)
You have to be sure, that you have enabled the UNIX Line Endings!
(Edit >> EOL Conversation >> UNIX)
If its "grayed-out" its okey, if not just click on it.
The most maked fault
The most maked fault is this:
Code:
Archos|ARCHOS|ARCHOS|/init|0 [BREAK]
Angstrom||/rootfs.img|/sbin/init|1 [BREAK]
Ginger-bread||/openaos-gingerbread.img|/init|0 [BREAK]
This menu.lst dont work!
It has to be:
Code:
Archos|ARCHOS|ARCHOS|/init|0 [BREAK]
Angstrom||/rootfs.img|/sbin/init|1 [BREAK]
Ginger-bread||/openaos-gingerbread.img|/init|0 [BREAK]
[BREAK]
You have to add a empty line! (Not just press "Enter" once when you are on the end of the last (gingerbread here) line, you have do it twice!)
After that you have to be 2 lines below the last OS line!
Install Google-Apps on Cyanogen
These Instructions are about getting the Google-Applications on Cyanogen.
(Like: Market,Sync,Talk,Backup,..)​1) First install a Root File Explorer (I recommend this free one: https://market.android.com/details?id=gpc.myweb.hinet.net.TaskManager )
2) Download this file: http://www.mediafire.com/?5iu9zvrq0ns6w15
3) Extract all apks out of the zip.
4) Copy all extracted apks to /system/app and reboot your device.
5) When your device boots up you should get to the "Start Up Wizard".
6) Here you have to create or sign in to your Google-Account.
7) Now you have all Google-Apps on Cyanogen!
Videos
Here Are Videos all around the openAOS Boot Menu/Urukdroid/Cyanogen.
Installation Process of the SDE
Installation Process of the Boot Menu and Cyanogen
Hands on with Cyanogen
Warning: This Video is old! Its from the very first version of Cyan! The lastest version is much more stable!
Links
Here are helpfull links to Websites about the openAOS Boot Menu:
openAOS - The "Home" of Bubu, the developer of the menu, with updates and news about archos stuff and cyanogen (also Bubu`s work)
Arctablet - An Archos news portal. They make many of the videos (2 of the 3 videos above). Here you can read about the Boot Menu and other Archos stuff and news.
Bubus file server - The file archive of Bubu. Here you can find the lastest version of the Boot Menu and Cyanogen.
Great summary, thanks a bunch
after doing ur how to for Urukdroid it didn't work ; but i'm root now on the original firmware i dont know how or why super user is working... god damn it
with full read and write
Just as a note.
If you have a A70s/h you don't need step 24 in Uruk configuration as our Display is mounted correct.
I can't startup my urukdroid in A101. I have tried below two lines in my config.
I can see it will start to boot Urukdroid, but after that it will switch to ARCHOS animation screen and wait for a long time.
UrukDroid|/dev/mmcblk2p2||/init|0
For this one, it will also start to boot Urukdroid at the first time, then it switch to ARCHOS animation screen and boot up android stock firmware.
UrukDroid|/dev/mmcblk2p2|/rootfs.img|/init|0
vantoman said:
after doing ur how to for Urukdroid it didn't work ; but i'm root now on the original firmware i dont know how or why super user is working... god damn it
with full read and write
Click to expand...
Click to collapse
and
I can't startup my urukdroid in A101. I have tried below two lines in my config.
Click to expand...
Click to collapse
I know, I know
This is Urukdroid! I didnt believe it too, but i tested Urukconfig and it works normally
It dont install the normal Urukdroid apps... i dont know why...
fzelle said:
Just as a note.
If you have a A70s/h you don't need step 24 in Uruk configuration as our Display is mounted correct.
Click to expand...
Click to collapse
Thanks for the tip
I added this at first post
jan_tsui said:
I can't startup my urukdroid in A101. I have tried below two lines in my config.
I can see it will start to boot Urukdroid, but after that it will switch to ARCHOS animation screen and wait for a long time.
UrukDroid|/dev/mmcblk2p2||/init|0
For this one, it will also start to boot Urukdroid at the first time, then it switch to ARCHOS animation screen and boot up android stock firmware.
UrukDroid|/dev/mmcblk2p2|/rootfs.img|/init|0
Click to expand...
Click to collapse
Try the latest initramfs from BuBu, the one from 4 July. The devices for the external SD card were added again.
Sent from my HTC Desire using Tapatalk
Lenn said:
and
I know, I know
This is Urukdroid! I didnt believe it too, but i tested Urukconfig and it works normally
It dont install the normal Urukdroid apps... i dont know why...
Click to expand...
Click to collapse
Lenn ; no i mean it start archos firmware from the boot menu and u'll get root i've tested it with the latest firmware and i'm root
vantoman said:
Lenn ; no i mean it start archos firmware from the boot menu and u'll get root i've tested it with the latest firmware and i'm root
Click to expand...
Click to collapse
Yeah i know you mean,i have this too
But this is urukdroid^^ urukconfig works normally
Your howto works fine, thank you very much.
But I have a problem - maybee simple.
On my Archos 101, after booting gingerbread (last bubu image) all stands upside down (bootmenu, afterwards the ADW screen). I just have checked all in the CM settings, so ADW become right, but some apps (like camera) won't follow and stay upside down .
What have I misdone?
zingel said:
Your howto works fine, thank you very much.
But I have a problem - maybee simple.
On my Archos 101, after booting gingerbread (last bubu image) all stands upside down (bootmenu, afterwards the ADW screen). I just have checked all in the CM settings, so ADW become right, but some apps (like camera) won't follow and stay upside down .
What have I misdone?
Click to expand...
Click to collapse
Actually this bug have been solved...
Do you have the lastest versions? Please check
Lenn said:
Actually this bug have been solved...
Do you have the lastest versions? Please check
Click to expand...
Click to collapse
The 101 will still have problems with the camera, etc. Display output is reversed, and the accelerometer has been reversed as well to cope with it. Eventually we'll get the display reversed instead of the accelerometer. Speaking of the camera, can you use it? I can't as the sdcard isn't mounted properly.

[Q] Feedback to [GUIDE] Root (Updated for ICS) #213 on page 22

Am 10 postings away from being allowed to join the original discussion.
Have ICS 4.0.4 OTA upgrade to ...-P6800XXLQ1-...
Used the procedures and data from Attached Files of posting #213 by kable in #213 in
http://forum.xda-developers.com/showthread.php?t=1454112&page=22
CWM installed well from recovery.
But CWM did not install root.zip!
Error message:
CWM Recovery v5.8.1.5
E: Can't mount /sdcard/
What could have gone wrong? What further details are needed to find a remedy? What else is needed to root successfully?
Updates:
I have found solutions after reading all posts related.
If you have just PC Odin an unrooted SGT 6800 into ICS, your SGT now cannot be rooted. What I have done thereafter is as follows:
1. PC Odin CWM 5.5.0.4 into my 6800;
2. set-up your 6800 into recovery mode ( press power & vol-up same times, release power button once your see active screen, then release vol-up button as well, you will be in CWM recovery mode;
3. goto zip from sdcard; toggle signature verification & script asserts to disable;
4. then choose zip from internal sdcard; from there you should choose root.zip ( this root.zip was saved into your external sdcard in advance.)
5. Once done, choose reboot.
Now you new ICS is rooted.
Which zip and which sdcard, that is the question.
Hi ronnieho,
thanks for your quick response and help. I am sure you will get me running. Please give me some more details which due to my lack of experience I feel to be missing.
Please let me explain this, then you will know which details still trouble me:
Last week I managed to root my ICS SGS2 following these instructions:
http://www.pocketpc.ch/samsung-gala...-stock-ics-firmware-ohne-flashen-kernels.html
It is in german, but based on the original thread
http://forum.xda-developers.com/showthread.php?t=1501719
The german instruction was very specific about which zip to put into which (internal or external) sdcard.
The english XDA instructions are not that specific about these obviously very important details.
Would you please add these details to your instructions:
1. PC Odin CWM 5.5.0.4 into my 6800;
Does this mean, place CWM.zip into the external sdcard (i.e. /sdcard/extStorages/SdCard) of the 6800?
From the threads refered to in my first post I have CWM 5.8.1.5. May this work too? Or must it be CWM 5.5.0.4? Where can I get CWM 5.5.0.4?
2. set-up your 6800 into recovery mode ( press power & vol-up same times, release power button once your see active screen, then release vol-up button as well, you will be in CWM recovery mode;
Yes, this is how I get into recovery mode.
3. goto zip from sdcard; toggle signature verification & script asserts to disable;
goto _which_ zip from _which_ sdcard.
Rooting my SGS2 I used
- install zip from sdcard
Here _sdcard_ meant the external sdcard
And _zip_ meant CWM.zip.
Is this also true for your instruction step 3?
toggle signature verification & script asserts to disable;
Where/to what item should I apply these instructions?
4. then choose zip from internal sdcard; from there you should choose root.zip ( this root.zip was saved into your external sdcard in advance.)
So far I did not save any zip to the internal sdcard?
Should I have saved root.zip into the internal sdcard in step 1?
Which root.zip? Remember, I have CWM.zip and root.zip from the Attached Files of posting #213 by kable in http://forum.xda-developers.com/showthread.php?t=1454112&page=22
Can I use these files or should I download different zip-files? From where?
Sure, I could simply try out my questions, but I am afraid to brick my Tab.
Another important detail may be that I did not use Odin to copy the zip files to the tap. In my successful rooting of the SGS2 I simply used the USB MTP connection and copied the zip-files like I copy video and audio files, and it worked. I would prefer to keep this copy practice also regarding the Tab7.7. Or must I copy with Odin? Why? Do I miss something if I copy in MTP mode? Does Odin do a different copy? Does Odin copy to different/specific sdcard locations?
I am confident that using your instruction will make the difference. Please give me the details which I feel to be missing.
Thanks!
Took the risk - Success, at last!
Since I did not get any more helpful answers, I had to reconsider the situation. Finally I decided to take the risk by using a best of
a) the xda-developers [GUIDE] Root (Updated for ICS)
http://forum.xda-developers.com/showthread.php?t=1454112
, e.g. postings #1 by Jade Eyed Wolf, #213 by kable, #227 by ronnieho, #230 by mashkuov, etc.
b) aljee77 guide for the SGS2
http://www.pocketpc.ch/samsung-gala...-stock-ics-firmware-ohne-flashen-kernels.html
Trusting that the xda-developers zip-files, CWM.zip and root.zip, will be ok for the Tab7.7
and hoping that the aljee77 procedure will also work as well for my Tab7.7 as it has worked for my SGS2,
I took the risk and finally succeeded to root my Tab7.7.
My successful procedure (Thanks to aljee77 and mashkuov):
1. Data preparation (zip-files)
1.1 Downloaded CWM.zip and root.zip to my computer from mashkuov, post #230 in http://forum.xda-developers.com/showthread.php?t=1454112&page=23
1.2 Copy these zip files from my computer to respective sdcard in my tab.
I have the Samsung Kies drivers installed on my computer. But I do not use Odin. I connect the tab and the computer with the USB data cable and simply use the USB MTP connection. I simply copy the zip-files like I would copy video and audio files by simple Windows Explorer file-drag/drop between the the source/target location icons.
1.3 I copy CWM.zip into my _external_ SDCARD
(on the computer: GT-P6800/Card
on the tab: /sdcard/extStorages/SdCard)
1.4 I copy root.zip into my _internal_ SDCARD ( /sdcard/ ) <--- aljee77 procedure <--- :good:
(on the computer: GT-P6800/Tablet
on the tab: /sdcard/)
2. Temporary installation of CWM Recovery:
- Reboot to recovery:
2.1 Download and install LATEST SAMSUNG KIES (or stand-alone USB drivers if you can find them)
2.2 Transfer CWM.zip to the EXTERNAL CARD on Galaxy Tab 7.7 (already done in step 1.3)
2.3 Turn off the Galaxy Tab 7.7
2.4 Enter Recovery
- Hold Volume UP button + Power Button
- When TAB turns ON, RELEASE POWER BUTTON (Keep Holding Volume UP Button)
* Will Enter Recovery
2.5 In the following basic menu use Volume Up/Down to navigate and Power OFF to select/accept options!
- Choose apply update from external storage.
- Choose CWM.zip and wait until CWM recovery appears.
* Now a temporary CWM is installed and activated.
* This CWM recovery is only a _temporary_ CWM and will be gone after reboot!
* see #217 by vegaman: http://forum.xda-developers.com/showpost.php?p=28300775&postcount=217
3. Install root
* Once the CWM recovery appears:
* _Touch-screen_ to navigate and to choose an option!
- install zip from sdcard (1st CWM menu)
- choose zip from internal sdcard (2nd CWM menu) <--- aljee77 procedure <--- :good:
- toggle signature verification & script asserts to disable <--- ronnieho #227 http://forum.xda-developers.com/showthread.php?t=1454112&page=22
- +++ GO BACK ++++ (from 2nd to 1st CWM menu)
- reboot system now (1st CWM menu)
* After reboot your tab will be rooted and temporary CWM will be gone.
4. Enjoy!
Now the tab is rooted! Temporary CWM is gone.
Now you can download Superuser App and Superuser Elite App (both by ChainsDD) from the market.
5. If you want a permanent CWM see #220 by Handymeister: http://forum.xda-developers.com/showpost.php?p=28319010&postcount=220
- after installing temporary CWM I flashed the root.zip with it.
- then reboot
- with root I flashed the CWM with Mobile Odin and that works fine and is now resistant again
Click to expand...
Click to collapse
6. If you need to unroot, see #5 by kazuni: http://forum.xda-developers.com/showpost.php?p=21600037&postcount=5
Re-flashing manufacturer rom through Odin is the only method as far as i know
Click to expand...
Click to collapse
Many thanks to aljee77 from pocketpc.ch and to the xda-developers posting experts in [GUIDE] Root (Updated for ICS)!
http://forum.xda-developers.com/showthread.php?t=1454112
Problem solved!

Adoptable Storage and Root SM-G935T -- Having issues

I dont know if the T-Mobile version of the s7 Edge just doesn't work with this root or I have some isolated issue. Anyways when I flashed the boot file it doesn't boot and stuck on the t-mobile screen.
Then I format the OS and it loads then I enabled adoptable storage stuff crashes and again it wont boot.
Try starting from scratch. There are plenty of posts detailing how to do this.
Here is what I did:
1) Back everything up
2) Boot into recovery (Power+Home+VolUp)
3) Factory reset
4) Boot to Download mode (Power+Home+VolDown)
5) Connect to computer and flash stock PD8 firmware via Odin (links are all over)
6) Wait until phone loads set up screen
7) Boot into recovery (Power+Home+VolUp)
8) Factory reset
9) Wait until phone loads set up screen, then minimally set up phone - i only added Google account, i did not add Samsung account
9.1) Now is a good time to install certain apps that don't like root - like SnapChat​10) Boot to Download mode (Power+Home+VolDown)
11) Connect to computer and flash custom bootloader via Odin (links are all over)
12) Wait for phone to load, then connect to computer
13) Browse to where you put the root package, hold SHIFT and right click, then select "Open command window here"
14) Run root.bat (part of the root package) and phone will restart
15) After phone loads, there are a few tweaks that can be done (you can search for these)
15.1) If running slow, download kernel modifier and change to interactive/ondemand governor​15.2) Disable samsung/knox packages (lists can be found in root threads)​16) NOW YOU ARE ROOTED!
17) For adoptable storage, connect to computer and run adb (how to do this is everywhere)
18) In adb, type:
Code:
adb shell
Then run the following, which will output a name of a disk, such as "disk:188,3"
Code:
sm list-disks
Then run the following, but put in your disk name for DISKNAME and for METHOD, put the way you want your storage set up (private makes the whole microSD adopted, mixed ##[/] splits the microSD by a percentage so if ## is 50, then it is split 50/50 adopted and external, or public which makes it all external (WARNING, THIS WILL DELETE ANYTHING ON THE CARD, SO BACK IT UP FIRST):
Code:
sm partition DISKNAME METHOD
For example, i did mine full adopted, so i ran the following:
Code:
sm partition disk:188,3 private
snpalavan said:
Try starting from scratch. There are plenty of posts detailing how to do this.
Here is what I did:
1) Back everything up
3) Boot into recovery (Power+Home+VolUp)
4) Factory reset
5) Boot to Download mode (Power+Home+VolDown)
6) Connect to computer and flash stock PD8 firmware via Odin (links are all over)
7) Wait until phone loads set up screen
8) Boot into recovery (Power+Home+VolUp)
9) Factory reset
10) Wait until phone loads set up screen, then minimally set up phone - i only added Google account, i did not add Samsung account
10.1) Now is a good time to install certain apps that don't like root - like SnapChat
11) Boot to Download mode (Power+Home+VolDown)
12) Connect to computer and flash custom bootloader via Odin (links are all over)
13) Wait for phone to load, then connect to computer
14) Browse to where you put the root package, hold SHIFT and right click, then select "Open command window here"
15) Run root.bat (part of the root package) and phone will restart
16) After phone loads, there are a few tweaks that can be done (you can search for these)
16.1) If running slow, download kernel modifier and change to interactive/ondemand governor
16.2) Disable samsung/knox packages (lists can be found in root threads)
17) NOW YOU ARE ROOTED!
18) For adoptable storage, connect to computer and run adb (how to do this is everywhere)
19) In adb, type:
Then run the following, which will output a name of a disk, such as "disk:188,3"
Then run the following, but put in your disk name for DISKNAME and for METHOD, put the way you want your storage set up (private makes the whole microSD adopted, mixed ##[/] splits the microSD by a percentage so if ## is 50, then it is split 50/50 adopted and external, or public which makes it all external (WARNING, THIS WILL DELETE ANYTHING ON THE CARD, SO BACK IT UP FIRST):
For example, i did mine full adopted, so i ran the following:
Click to expand...
Click to collapse
Can this be done from the phone with a terminal app?
noobiedev83 said:
Can this be done from the phone with a terminal app?
Click to expand...
Click to collapse
You can try running the sm commands from terminal. When i tried it, it wouldn't work - it just gave an error. But theoretically, it should :fingers-crossed:
snpalavan said:
Try starting from scratch. There are plenty of posts detailing how to do this.
Here is what I did:
1) Back everything up
3) Boot into recovery (Power+Home+VolUp)
4) Factory reset
5) Boot to Download mode (Power+Home+VolDown)
6) Connect to computer and flash stock PD8 firmware via Odin (links are all over)
7) Wait until phone loads set up screen
8) Boot into recovery (Power+Home+VolUp)
9) Factory reset
10) Wait until phone loads set up screen, then minimally set up phone - i only added Google account, i did not add Samsung account
10.1) Now is a good time to install certain apps that don't like root - like SnapChat​11) Boot to Download mode (Power+Home+VolDown)
12) Connect to computer and flash custom bootloader via Odin (links are all over)
13) Wait for phone to load, then connect to computer
14) Browse to where you put the root package, hold SHIFT and right click, then select "Open command window here"
15) Run root.bat (part of the root package) and phone will restart
16) After phone loads, there are a few tweaks that can be done (you can search for these)
16.1) If running slow, download kernel modifier and change to interactive/ondemand governor​16.2) Disable samsung/knox packages (lists can be found in root threads)​17) NOW YOU ARE ROOTED!
18) For adoptable storage, connect to computer and run adb (how to do this is everywhere)
19) In adb, type:
Code:
adb shell
Then run the following, which will output a name of a disk, such as "disk:188,3"
Code:
sm list-disks
Then run the following, but put in your disk name for DISKNAME and for METHOD, put the way you want your storage set up (private makes the whole microSD adopted, mixed ##[/] splits the microSD by a percentage so if ## is 50, then it is split 50/50 adopted and external, or public which makes it all external (WARNING, THIS WILL DELETE ANYTHING ON THE CARD, SO BACK IT UP FIRST):
Code:
sm partition DISKNAME METHOD
For example, i did mine full adopted, so i ran the following:
Code:
sm partition disk:188,3 private
Click to expand...
Click to collapse
Lol where is step two.
Frostkitty97 said:
Lol where is step two.
Click to expand...
Click to collapse
whooooops, fixed
snpalavan said:
whooooops, fixed
Click to expand...
Click to collapse
Lol

trying to bring my brothers A500 to life in 2019

Hey together,
I really hope someone out there is still using a A500 Tablet and may be able to help me fix a weird issue i encounter on every ROM i tried so far.
I installed the ROMs mentioned in this Thread: https://forum.xda-developers.com/iconia-a500/general/2018-a500-upgrade-threaddownloads-to-t3832293
And all of them come with the Same Problem for me.
If i try to open the Google PlayStore or something else that wants me to login into a Google Account it just says: "There was a problem communicating with Google Servers" "Try again later"
anyone knows of this issue ? All the fixes several Google searches gave me did not help to fix that issue for me on any of the ROMs.
help would be highly appreciated
kind regards
Finn
Hi,
have you read the tips? It says:
"- Google play will not work right if you do not format your data partition to f2fs. (You can do this in recovery)"
Have you tried it?
Matra-PB said:
Hi,
have you read the tips? It says:
"- Google play will not work right if you do not format your data partition to f2fs. (You can do this in recovery)"
Have you tried it?
Click to expand...
Click to collapse
That may not be the problem I've hear a lot of people are having this problem. But it's a good place to start if he hasn't tried it yet.
Success story upgrading A500 in 2019 July
finneus_ said:
Hey together,
I really hope someone out there is still using a A500 Tablet and may be able to help me fix a weird issue i encounter on every ROM i tried so far.
I installed the ROMs mentioned in this Thread: https://forum.xda-developers.com/iconia-a500/general/2018-a500-upgrade-threaddownloads-to-t3832293
And all of them come with the Same Problem for me.
If i try to open the Google PlayStore or something else that wants me to login into a Google Account it just says: "There was a problem communicating with Google Servers" "Try again later"
anyone knows of this issue ? All the fixes several Google searches gave me did not help to fix that issue for me on any of the ROMs.
help would be highly appreciated
kind regards
Finn
Click to expand...
Click to collapse
First my thanks to the forum key members for providing answers to queries and to all the key contributors of SW/ROMS in this forum. I followed the procedures from this forum to Flash / upgrade my Acer Iconia A500 on 4.0.3 ICS that was sitting in a trunk for the last few years. Summary of steps I tried out.
STEP 1: Install the Acer device drivers listed in the links in this forum on your Laptop/Computer even if by default your Windows 10 OS (assuming you are on Win10 like me) is able to recognize the A500 connected to the USB port.
USB_Acer_1.00.0524_A30HA31HA32H_A.ZIP
STEP 2: ROOTING the Acer A500.
1. The tablet should be already upgraded to stock ICS for A50x (or stock ICS A10x/A510 for other tablets).
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch ON. If you do not see this menu, then click 7 times of the Android Build No. listed under settings and come back to the menu above to enable USB Debugging.
3. Connect the tablet to the computer (Before connection it is recommended to update the driver for a tablet from here: A10x, A50x, A510).
4. Since most of the discussions regarding flashing A500 were from 2011, the earlier Gingerbreak method for rooting did not work.
I downloaded the following file from this forum to root my tablet.
ICS_rooting_A10x_A5xx.zip
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
Note: The McAfee Antivirus software started tagging a file 'mempodroid' within this ZIP file Tools folder as a virus or malicious file. This rooting method uses the 'mempodroid' exploit which is detected as a VIRUS by McAfee and Qurantined. So restore from Qurantine and check list of files are still present in the folder. If not verify 8+8 files in folders again.
As per inputs in this forum, I restored the files quarantined and then suppressed McAfee SW for the duration of my upgrade activities on my laptop and was able to successfully extract all the files in the ZIP file to a local folder on the laptop. This ZIP file has adb and fastboot - two key programs useful for rooting your A500 apart from SU or superuser base file used in step 2. The file to run is the BAT file runit-win.bat if you are on windows. At the end of this step your tablet should be rooted. You may check by installing the RootCheck app from Google Playstore.
Step1a: Install a File Manager app from the Google playstore. This will help you extract the CPU ID and convert it with the SBK tool to get the SBK number/string. important steps SBK tool was available in file - SBCalc_v1.1.ZIP available in this forum.
STEP 2b: SUPERUSER and SUPERSU installation
1. Install SuperUser.apk first.. (IMP - Its available in this forum. Its like a base version for superSU to install over. If you do not install SuperUser.apk, then each time you try installing SuperSU, you would get an error message about a SU file being incompatible.)
2. Then install an older version of SuperSU downloaded from the website - filename -> eu.chainfire.supersu_v2.65-265.ZIP . Newer versions will not work. U got to install an older version as new version seems to be a paid SW.
3. Next Open SuperSU app on your tablet and let it update itself a couple of times each time opening and closing the app after the upgrade.
4. Remove SuperUser.apk file as now its no longer needed.
5. Now that you have ROOT access and SuperUSer access
6. Install Titanium Backup. File name in this forum- update-recovery-TWRP-rev2.0-beta4.ZIP . This will help you to flash/upgrade ROM software on your tablet.
Twrp 2.8:
http://www.mediafire.com/file/e7wpny5f39vw3pc/update-recovery-TWRP-rev2.0-beta4.zip/file
Compressed Archive (.ZIP)
File size: 4.91MB
Uploaded: 2018-08-14 21:40:26
https://www.mediafire.com/download/e7wpny5f39vw3pc
STEP 3: Install an Unlocked Bootloader i.e. unlocked bootloader Skrillax v9 - file name in this forum BabSector.rar or A500-Bootloader-Nvflash.ZIP
Once you have reached this step, you now have the basic tools needed for the final ROM upgrade of the tablet.
I did get error message after the reboots that happened after Unlocking the Bootloader. Someting about a LNX partition not being okay or some such msg. Each time I just WIPED the Cache and selected similar options to wipe System, Data, User, Dhelvic cache (spelling incorrect) etc. Since you have not installed the final OS or ROM for your tablet yet, no harm in deleting these partition data. Actually its recommended to wipe, format in f2f formats etc. all of which is possible using the TWRP Recovery software you installed in step 2. Choose Recovery menu option each time the tablet boots or gives errors.... using the volume rocket and power buttons. More info -> Go through this thread and install unlocked bootloader.
https://forum.xda-developers.com/showthread.php?t=1622425
Flashing Bootloader Steps
-------------------------
1. generate your SBK from cpuid
2. put tab in APX by holding reset (small pinhole bottom right side)
and pushing power for 3-4 sec. - then release reset approx 1 sec. later
the screen should be blank and power button should be lit - plug in USB to PC.
2. Run A501 A.bat - when finished reboot tab to recovery (win 7 and under
right click on A501 A.bat and select Run as Administrator)
3. run Recovery(power and volume-) ->WIPE -> "Advanced wipe ->System (only)and swipe to wipe.
4. unplug USB and reboot tab to APX
5. plug in USB afer it is in APX mode -> Run A501 B.bat (win 7 and under
right click on A501 B.bat and select Run as Administrator)
Bootloader unlock tutorial
--------------------------
Step 1: Get your cpuid - https://forum.xda-developers.com/showthread.php?t=1624645
Step 2: Convert it into an SBK - https://forum.xda-developers.com/showthread.php?t=1810618
Step 3: Download the A500 drivers
- http://www.mediafire.com/file/pde8rojv1t8gnif/USB_Acer_1.00.0524_A30H_A31H_A32H_A500_A501.zip/file
Step 4: Download the files to install the bootloader
- http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file
Step 5: Follow the instructions in "how to.txt"
Step 6: Download a rom and flash in twrp
This tutorial is based of
https://forum.xda-developers.com/showthread.php?t=2450119 thread so big thanks to KaijiKun .
Bootloader unlock files:
http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file
STEP 4. Downloaded file omni-4.4.4-20150210-a500-IconiaHD.ZIP as I was not sure version omni 5.1.1 was as stable as Omni4.4.4 reading all the threads in this forum.
First rename the downloaded OMNIROM file as update.zip .
OmniRom 4.4.4
http://www.mediafire.com/file/ghd72j3g618kk9g/OMNIROM-5.1.1-Tegraowners_ROM_v13t2.zip/file
File size: 244.66MB
Uploaded: 2015-04-05 17:40:14
STEP 5: Install another tool adb_fast.ZIP. This tool is also available in this forum.
Note:You need to copy the update.zip file to your computers folder where this tool adb_fast is installed. In mine it was C:\Program files (x86)\Minimal ADB and Fastboot folder. This adb_fast file creates an application shortcut on your computer desktop. Clicking on the short cut launches adb and fast boot programs I mentioned at the beginning.
STEP 6: Copy the file to the SD card (16GB) of your tablet.
Run the adb_fast tool from your desktop shortcut. This will open a Command Prompt type black screen window where you can enter the code as given below. Note you may need to see how your SD card is listed in a file manager in your computer
Code:
adb push update.zip /mnt/sdcard/update.zip --- NOTE: this creates mnt folder on internal storage and I had to then move the file using TWRP recovery tool installed in step 2, to the SD card.
adb push < ------- is the push command.
rom.zip < ------- is the name of the Rom zip file.
/sdcard < ------- is the location your pushing the Rom to.
E.) Reboot tablet with Power+Down Arrow i.e. This will start the Upgrade process for the tablet to OMNIROM 4.4.4
-- Power Button + UP VOLUME pressed... then release Power button after LED lights.
-- System will boot to commmand prompt
STEP 7: Install GAPPS using pico gapps short version and Wipe Data/Factory reset ----------------?>and wipe cache partition?
Reboot after 1st reboot
G.) https://opengapps.org/ to install a minimal version of Google Apps on the tablet.
File name -> pa_gapps-modular-mini-4.4.4-20150410-signed.ZIP
Root tablet again and install SuperSU if you need it
other info.
You can use TWRP to flash the OmniROM on the tablet or you can use the following in worst case senario to do the same.
Code:
fastboot devices
fastboot flash update.zip -- check if syntax is ok from threads in this forum
fastboot reboot-bootloader
copied below from other threads ---->
I find that a large amount of complaints in developer threads are due to people not properly wiping before a flash.
Of course there is times when a 'dirty' flash is fine, but if you're ever not sure, wipe as cleanly as possible.
fastboot allows for about the cleanest of wipes by the way. And each partition can be done separately too.
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
can all be done individually, but to do these all in one command
Code:
fastboot erase system -w
If possible I recommend to do these steps before flashing a ROM, and now that you know you can do this all within fastboot mode i suggest to try it out, its quick and painless!
Don't forget to wipe your kernel too! (fastboot erase boot)
~Important~ If your device uses an emulated SD card (as in no removable micro SD but an SD partition on phone)
Then be careful wiping data/userdata as this will erase all contents of internal SD - you are forewarned!
ADB= Android Debugging Bridge (ADB)
[TOOL]Minimal ADB and Fastboot [2-9-18]
https://forum.xda-developers.com/showthread.php?t=2317790&page=12
First a short explanation:
Fastboot, like ADB, is a tool to communicate from PC to Android phone. There are times when it is a must to use, and times when it is just helpful.
ADB is used within your recovery or within your OS, but when you are in bootloader mode and need to communicate with your phone then you need fastboot.
And you may ask why would i ever need this?
Well many reasons. Main one is knowledge, learning the ins and outs of fastboot, like learning ADB, can get you out of many jams.
And if you want to unlock your bootloader this is done through fastboot. Granted HTC's unlock is... well crap, but for a Nexus this is how its done.
One other reason I have to stress is learning for safety reasons, This is about the safest way possible to flash firmware to your phone (ie Radio, Hboot, Recovery)
Lastly you may want to know the limitations,
There are many of course, this isnt JTAG, it will not resurrect a hard brick, but it often save peoples phones from 'soft bricks' and lots of time when know how and when to use it.
Think of fastboot as the program that takes over when ADB cant be used, it works with firmware more than software.
https://forum.xda-developers.com/showthread.php?t=1624645&page=3
GUIDES
---------------
Civs Guide to flashing the bootloader http://forum.xda-developers.com/showthread.php?t=1622425
Walkthrough using APXFLASH tool at Step 6 http://forum.xda-developers.com/showthread.php?t=1624645&page=2
From Civato's OP of The Guide: nvFlashToolPackages
Skrilax_CZ bootloader thread http://forum.xda-developers.com/showthread.php?t=1619913 and should be "required reading" for anyone mucking about in their tabs internals!!!!
Rollback to HC
jazzyjames guide http://forum.xda-developers.com/showthread.php?t=1516012
Iconia Root http://forum.xda-developers.com/showthread.php?t=1138228 /gingerbreak: For returning to Honeycomb
----------------
To get my CPUID, I have followed the steps below:
Open yr file explorer, esfile explorer is a great one....navigate to:
/sys/firmware/fuse/acer_cpuid - add a zero to the front!
To get CPUID get a Root browser of some sort and go to sys/firmware/fuse/acer_cpu_id
convert my CPUID into SBK?
--------------------------
https://forum.xda-developers.com/showthread.php?t=1055354&page=6
What Does Root Give Me?
1. Full control over your system
2. Ability to alter system files. You can replace many parts of the "Android Core" with this including:
o Themes
o Core apps (maps, calendar, clock etc)
o Recovery image
o Bootloader
o Toolbox (linux binary that lets you execute simple linux commands like "ls") can be replaced with Busybox (slightly better option)
o Boot images
o Add linux binaries
3. Run special apps that need more control over the system
o SuperUser (lets you approve or deny the use of root access to any program)
o Task Manager For Root (Lets you kill apps that you otherwise could not kill)
Tether apps (like the one found at [android-wifi-tether.googlecode.com])
4. Backup your system
o You can make a folder on your SDCARD and backup all of your .APK files to your SDCARD (helps if an author decides to "upgrade" you to a version that requires you to pay to use the version you just had)
5. Relocate your (browser/maps/market) cache to your /sdcard
6. Relocate your installed applications to your /sdcard
7. Reboot your phone from the terminal app easily (su <enter> reboot <enter>)
Turn the rotation lock off.
-------------------------------------------------------
SUMMARY - Regardless of version, rooting is the same... next
** Unlock the bootloader.
** Fastboot flash a Custom Recovery (TWRP).
** Download to the Tablet, Chainfire's SuperSU root updater .zip
** Boot into the previously fastboot flashed Custom Recovery, and flash the SuperSU updater .zip.
** Reboot - you're rooted.
-------------------------------------------------------
PS. I tried to maintain a log in Notepad during my upgrade. Unfortunately did not write detailed instructions and link to required files. Above is a summary of what worked for me.
Can not root
sukasis said:
First my thanks to the forum key members for providing answers to queries and to all the key contributors of SW/ROMS in this forum. I followed the procedures from this forum to Flash / upgrade my Acer Iconia A500 on 4.0.3 ICS that was sitting in a trunk for the last few years. Summary of steps I tried out.
STEP 1: Install the Acer device drivers listed in the links in this forum on your Laptop/Computer even if by default your Windows 10 OS (assuming you are on Win10 like me) is able to recognize the A500 connected to the USB port.
USB_Acer_1.00.0524_A30HA31HA32H_A.ZIP
STEP 2: ROOTING the Acer A500.
1. The tablet should be already upgraded to stock ICS for A50x (or stock ICS A10x/A510 for other tablets).
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch ON. If you do not see this menu, then click 7 times of the Android Build No. listed under settings and come back to the menu above to enable USB Debugging.
3. Connect the tablet to the computer (Before connection it is recommended to update the driver for a tablet from here: A10x, A50x, A510).
4. Since most of the discussions regarding flashing A500 were from 2011, the earlier Gingerbreak method for rooting did not work.
I downloaded the following file from this forum to root my tablet.
ICS_rooting_A10x_A5xx.zip
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
Note: The McAfee Antivirus software started tagging a file 'mempodroid' within this ZIP file Tools folder as a virus or malicious file. This rooting method uses the 'mempodroid' exploit which is detected as a VIRUS by McAfee and Qurantined. So restore from Qurantine and check list of files are still present in the folder. If not verify 8+8 files in folders again.
As per inputs in this forum, I restored the files quarantined and then suppressed McAfee SW for the duration of my upgrade activities on my laptop and was able to successfully extract all the files in the ZIP file to a local folder on the laptop. This ZIP file has adb and fastboot - two key programs useful for rooting your A500 apart from SU or superuser base file used in step 2. The file to run is the BAT file runit-win.bat if you are on windows. At the end of this step your tablet should be rooted. You may check by installing the RootCheck app from Google Playstore.
......
Click to expand...
Click to collapse
Hi sukasis, i was unable to root the tablet. I download all and run the runit.win.bat (trying normal, as admin, and open a cmd as admin and then navigate to the bat to execute).
- It say device connected
- Then push 7 files correctly
- Executing of the main script. (it freeze here a lot of time)
Then error: protocol fault (no status)
The file "su" isn't created
Not getting root!
I try in USB 3.0 and 2.0 same error.
I have windows 10.
I uncheck the Debugging mode and it's bring another error, so i believe the connection is good because in debug mode can push files.
I don't know whate else i can do.

Categories

Resources