Related
I bought this Xperia ARC LT15a on Friday and have been having LOTS of trouble figuring out what to do with it. I came on here and I can say the tutorials aren't very noob-friendly because you have your own "lingo" that I dont understand whatsoever.
Now, for you guys to understand my frustration, I am coming from IOS, and was told "rooting" an Android phone is a much simpler process then jailbreaking an iPone. Well, that sure as hell has proven to be wrong since I can't even figure out how to UPDATE my phone >_>
First off, what I'm trying to do is update it to ICS. Sony says you can do it using the PC Companion, but it says I'm up to date. Same thing with the SEUS or whatever you call it...says I'm up to date. I am running Android Ver. 2.3.4 so I'm pretty sure I am NOT up to date...my IM number (or whatever) is listed as compatible with ICS so it should just update via seus or pc companion...but no...
So someone linked me to tutorials on how to FLASH ics to it... but all of the tutorials have dead links and are completely useless to me now...
Can someone PLEASE tell me what to do... I just want to update to ICS and root it, but I can't even f***ing update.........!!!! very frustrating
i felt exactly the same mate haha
but this was my first smartphone full stop lol
is it the tutorial links in general that are dead?
but do some searching, i found pretty much everything i needed on here
and now i can change ROMS, kernels, baseband etc in minutes
im sure someone more helpful will be along soon lol
Right - I haven't posted much but having been pretty much under the same level of noob frustration before I'll try to help....
First - Often, during updates you can be driven mad with reboots and reboot cycles..... hopefully, what is outlined below can be a guide to sorting out any problems you might have.
1. Backup everything.
- go to play store and search for "backup" and you'll find what you need. I use Astro File Manager for application backup and sms backup for messages. I'm not bothered about backing up anything else.
2. Unlock the Bootloader.
- download sdk starter package
Code:
://developer.android.com/sdk/index.html
- so far as I can figure this will facilitate communications between your pc and phone. CyanogenMod Wiki guides you through this process:
Code:
://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
- download latest version of fastboot. Now, you'll never double click on this program to run it. Instead you'll run commands from your command tool which will use the program to do the work.
- record your IMEI - in dialer type in *#06# for your IMEI & write it down.
- get your phone attached in fastboot mode. to do this you turn off your phone and hold the menu button while you attach it via USB to your computer.
- see if you're connected properly. Look for command prompt (Windows Key - All Programs - Accessories). Right click on this and run as administrator. Type in the following: fastboot -i 0x0fce getvar version . It will give an obviously positive message if you are correctly connected - if not, ensure you've attached in properly.
- get code to unlock bootloader - go here:
Code:
://unlockbootloader.sonymobile.com/
and go through the process to get an unlock key. Once you have this, go back to your command prompt and type fastboot -i 0x0fce oem unlock 0xUNLOCKKEY (where UNLOCKKEY is the number you have gotten from Sony website. You should get a confirming message.
Now that you've unlocked the bootloader you need to decide what kind of kernel and ROM you want. You can regard the ROM as software whereas the kernel links the software to the hardware. This is my limited understanding anyway.
3. Now, sometimes people make standalone kernels and sometimes they are kept with the ROM.
This leaves a couple of options
- you can flash a stand-alone kernel using flashtool (
Code:
://androxyde.github.com/
). The process is pretty simple.
- Now, if you download a ROM which advises that you need to extract and flash a file called "boot.img" there is a different method. In this case your ROM zip file can be extracted to find the boot.img file.
When you get the boot.img file you can place it in C:\. Now, all advice will be to place it in the platform-tools folder which is created in step 1. It doesn't matter really so long as you point at the right place when flashing.
(I also think that you can use flashtool in flashmode to do this job....)
4. Now you have a kernel on your Xperia and seeing as you've got the bootloader unlocked you can now unplug the phone and turn it on. While the phone is booting up, keep toggling the volume button and it should go into bootloader. This is a text-based interface that allows you several functions.
Somewhere in there is an option to mount the SD card (for which you need to plug into your comp again)
5. You'll see the phone's SD card in Windows explorer and will be able to put your ROM onto it (NOT the extracted stuff from earlier but the original zip file).
6. You can now install this ROM but first clear all data and the dalvik cache. I also always to the battery stats here too. It might take a little bit of exploring to find these.
7. Now you can go to "install zip from SD Card". Step through and you will find where you put the ROM zip file. Select it and install the ROM.
At this point, you may get a bit frustrated - because it's here that you find things like:
The ROM sucks
Bits don't work or
You can't get it to work
For any of the above try again....
Currently I'm on Paranoid Android ICS ROM which I like but if I can't get the Wi-Fi working there's no way I'll be sticking to it. Another that I really liked and will return to is Boost HD RC4
I hope it works out for you.....
Tony
Canned30 said:
Right - I haven't posted much but having been pretty much under the same level of noob frustration before I'll try to help....
First - Often, during updates you can be driven mad with reboots and reboot cycles..... hopefully, what is outlined below can be a guide to sorting out any problems you might have.
1. Backup everything.
- go to play store and search for "backup" and you'll find what you need. I use Astro File Manager for application backup and sms backup for messages. I'm not bothered about backing up anything else.
2. Unlock the Bootloader.
- download sdk starter package
Code:
://developer.android.com/sdk/index.html
- so far as I can figure this will facilitate communications between your pc and phone. CyanogenMod Wiki guides you through this process:
Code:
://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
- download latest version of fastboot. Now, you'll never double click on this program to run it. Instead you'll run commands from your command tool which will use the program to do the work.
- record your IMEI - in dialer type in *#06# for your IMEI & write it down.
- get your phone attached in fastboot mode. to do this you turn off your phone and hold the menu button while you attach it via USB to your computer.
- see if you're connected properly. Look for command prompt (Windows Key - All Programs - Accessories). Right click on this and run as administrator. Type in the following: fastboot -i 0x0fce getvar version . It will give an obviously positive message if you are correctly connected - if not, ensure you've attached in properly.
- get code to unlock bootloader - go here:
Code:
://unlockbootloader.sonymobile.com/
and go through the process to get an unlock key. Once you have this, go back to your command prompt and type fastboot -i 0x0fce oem unlock 0xUNLOCKKEY (where UNLOCKKEY is the number you have gotten from Sony website. You should get a confirming message.
Now that you've unlocked the bootloader you need to decide what kind of kernel and ROM you want. You can regard the ROM as software whereas the kernel links the software to the hardware. This is my limited understanding anyway.
3. Now, sometimes people make standalone kernels and sometimes they are kept with the ROM.
This leaves a couple of options
- you can flash a stand-alone kernel using flashtool (
Code:
://androxyde.github.com/
). The process is pretty simple.
- Now, if you download a ROM which advises that you need to extract and flash a file called "boot.img" there is a different method. In this case your ROM zip file can be extracted to find the boot.img file.
When you get the boot.img file you can place it in C:\. Now, all advice will be to place it in the platform-tools folder which is created in step 1. It doesn't matter really so long as you point at the right place when flashing.
(I also think that you can use flashtool in flashmode to do this job....)
4. Now you have a kernel on your Xperia and seeing as you've got the bootloader unlocked you can now unplug the phone and turn it on. While the phone is booting up, keep toggling the volume button and it should go into bootloader. This is a text-based interface that allows you several functions.
Somewhere in there is an option to mount the SD card (for which you need to plug into your comp again)
5. You'll see the phone's SD card in Windows explorer and will be able to put your ROM onto it (NOT the extracted stuff from earlier but the original zip file).
6. You can now install this ROM but first clear all data and the dalvik cache. I also always to the battery stats here too. It might take a little bit of exploring to find these.
7. Now you can go to "install zip from SD Card". Step through and you will find where you put the ROM zip file. Select it and install the ROM.
At this point, you may get a bit frustrated - because it's here that you find things like:
The ROM sucks
Bits don't work or
You can't get it to work
For any of the above try again....
Currently I'm on Paranoid Android ICS ROM which I like but if I can't get the Wi-Fi working there's no way I'll be sticking to it. Another that I really liked and will return to is Boost HD RC4
I hope it works out for you.....
Tony
Click to expand...
Click to collapse
I should have mentioned that the only thing I was successful doing was unlocking the bootloader...but then I was told to re-lock it so I could update using the PC companion.......... very annoying
thanks for the detailed reply..
I'm thinking now I wont bother with ICS and ill just root my current version 2.3.4 but yet again ive run into problems with dead links since most have not been updated since this time last year..
*EDIT*
I've tried DooMLords app thing to root, and all I get is a bunch of errors
trying to post a pic with all the errors but im not allowed...............................frustration after frustration after frustration
Try downloading some custom kernels n Roms from this site to see which version of ICS suits not best
There are threads with very explicit details on how to do so, you just need to look
I used to be a noob, on longer the case now.
Currently running acronium 2.4 with doomkernel v04 with WiFi modules, learned how to do all this from here
I'll figure out a site to upload all that I've downloaded so you have access to them with instructions cause some links don't work in other threads
Sent from my LT15i using xda app-developers app
Wanting to root my new Telstra T-Hub 2, made by Technicolor.
There appears to be no USB drivers available (nothing via Google)
There also appears to be no way to get into the Download Mode for connection to Odin. (again nothing on Google)
So these two points have left me a bit lost.
It is running Android (GB) 2.3.7
Any one have any ideas????
Rabs_1976 said:
Wanting to root my new Telstra T-Hub 2, made by Technicolor.
There appears to be no USB drivers available (nothing via Google)
There also appears to be no way to get into the Download Mode for connection to Odin. (again nothing on Google)
So these two points have left me a bit lost.
It is running Android (GB) 2.3.7
Any one have any ideas????
Click to expand...
Click to collapse
I got ADB working on my T-Hub 2 by using the generic Google drivers, and edited the adb_usb.ini to just say 0x069B
So far I have problems rooting it.
wocko1 said:
I got ADB working on my T-Hub 2 by using the generic Google drivers, and edited the adb_usb.ini to just say 0x069B
So far I have problems rooting it.
Click to expand...
Click to collapse
BUMP
I have this Tablet as-well and having the same problem.
any ideas on the best way to root this thing?
wocko1 do you have any more details on how to got that far?
Thanks guys.
Rabs_1976 said:
Wanting to root my new Telstra T-Hub 2, made by Technicolor.
There appears to be no USB drivers available (nothing via Google)
There also appears to be no way to get into the Download Mode for connection to Odin. (again nothing on Google)
So these two points have left me a bit lost.
It is running Android (GB) 2.3.7
Any one have any ideas????
Click to expand...
Click to collapse
was it released in any other countries as another device?
even if we got root on it what can we do for a custom ROM if noone can dev for it
Madaz2 said:
was it released in any other countries as another device?
even if we got root on it what can we do for a custom ROM if noone can dev for it
Click to expand...
Click to collapse
We as owners/users of T-Hub 2 devices require sensible answers to important questions.
We need usb drivers for the T-Hub 2, either from Telstra or from Technicolor the manufacturer of the device so that we can attain " ROOT ACCESS" via a usb cable connection to a computer.
Unless we can get "ROOT ACCESS" we cannot move applications to an external SD card (32 GB in my case) or use Titanium Backup or certain Antivirus programs that require "ROOT ACCESS".
Please accept the undeniable fact that 1 Gigabyte of storage on the internal SD card is totally insufficient and pathetic, almost as pathetic as the fact that we are still stuck with "Gingerbread" which puts us three versions behind on Android which is now up to "JellyBean" v2.
The fact is, I believe the Android operating system running on the T-Hub 2 is, like all other versions of Android, based on the Linux kernel which is software using the GNU General Public License, which allows people to see, copy, use, and modify for their own needs.
If indeed I am correct in my assumption then Telstra/Technicolor could be in breach of a world standard which would mean that the proprietary blocks and gates that they have built to prevent access to the kernel on the T-Hub 2 are illegal.
Download Mode discovered...and more...
I thought this:
Hold "Volume-" and "Volume+" and "Power Button" boots into download mode. This is incorrect.
This gets you to recovery mode (which shows the Android robot fallen over).
Help!
wocko1 said:
I got ADB working on my T-Hub 2 by using the generic Google drivers, and edited the adb_usb.ini to just say 0x069B
So far I have problems rooting it.
Click to expand...
Click to collapse
Have been looking for the drivers everywhere, and so far none of them have worked. Even tried wireless adb to no avail. Also tried gingerbreak but still nothing. Sick of looking at the bloatware. Someone please help!
anyone had more success now that it has ICS 4.0.4
Yes, it can be rooted, but...
Hi,
Yes, much more progress. I've gained ADB root access using the restore method (i.e., restoring a backup which has been modified to install a file to a strange path, e.g,: ../../../system/bin/su), I recommend creating your own restore file rather than using one of the many out there and using it to install the necessary SU software to the appropriate locations.
If your device isn't detected by ADB, check that the device ID has been added to the ADB config file. The Thub2 ID is not recognised automatically. Also, when using fastboot remember to specify this ID or it won't find your THub.
The biggest issue with the THub2 is that Telstra have (in an oddly intelligent move) adopted SquashFS for the root file system; this is the FS used on things like linux liveCD's, and it's 100% RO (well, 99% RO . I have gotten around this in a number of ways. 1: I copied the SquashFS partition using DD to an Ext4 partition, then forced a dirty unmount of the SquashFS partiition chained to a mount of the new Ext4 partition to /system. RW access no problems, SU installs OK, but no persistence without forcing the dirty unmount each boot. 2: I copied the SquashFS partition to my ~ using DD, mounted and edited the partition, then re-flashed to the thub. worked much better, persistence across reboots, but dangerous and dodgy method that could risk many NANDs. 3: I cross-compiled a busybox containing UnionFS to Android.
Option 3 is by far the best option. UnionFS provides a transperent RW layer for SquashFS filesystems, writing the updates that couldn't be written to a RO system like squash to another partition (e.g., Ext4 on SD card). Mount a UnionFS system over /system to enable write access to the system. Maybe a better idea to mount it at /, but that raises other problems I couldn't be bothered dealing with.
I mentioned above that SquashFS is on 99% RO (in all my other experiences, it has been well and truly 100% RO, so this indicates something else a-going on that we should be able to use; I haven't looked into it yet.). For some reason, files installed to the Thub2 using the Restore method are persistent. Very useful, and should lead to a cleaner method.
So rooting so far:
Root with Restore method to install (1 & 2., SU bins, or 3., UnionFS Busybox)
Remount / as RW
-->Path 1 & 2
Dirty unmount /system && dirty unmount /system2 && mount /dev/block/etc.. NOTE: Once you dirty unmount /system, you will need to reference the location of the Ext4 partiition using the absolute (real) name of the device. You will also need to invoke busybox from a fully qualified path, eg. /data/local/tmp/busybox, as the internal /bin applications are no longer available (eg., mount).
-->Path 3
No need to umount /system, just mount the UnionFS system over the top.
Finally, for Paths 1 & 3...
Install Superuser application and be free!
So to sum up; I have easily rooted the Thub2 to root over ADB using a number of methods, however the Restore method works 100% of the time. I have mounted an Ext4 system to /system in order to have RW, but this isn't persistent. I have re-flashed the SquashFS with modified content, and this works a treat, but is RO and dangerous to NAND. I have mounted a UnionFS system over the SquashFS system, and this seems to provide the best all round performance.
I also wrote a short and nasty .apk to mount the UFS system without terminal, so that's a go as well.
Have fun pulling it all apart; I don't read these message boards, so I probably won't se any questions. More than enough to get rooted though.
THub Drivers and ADB Access
THUB 2 DRIVER INSTALLATION AND ADB ACCESS
This method sets out how to install drivers for the THub 2 and access ADB (Android Debug Bridge).
Access to ADB is the usual way that you use to Root an Android device.
Please note that not all ADB versions work. If you download and try a root method, you may have to copy the ADB.exe and support files across so that the root method can at least have a chance of working.
INSTALLING GOOGLE UNIVERSAL ANDROID DRIVERS
1. Ensure that Debugging has been enabled – Settings Developer options USB debugging and make sure the box is checked
2. The following is for Windows 7, other versions will be similar
3. Unzip the file and copy contents to a folder on the C: drive. I copied it to a folder I named THub
4. Plug the THub into your PC and it will try to find suitable drivers – some drivers may load and install but at least one will come up with “No driver found”
5. Open “Computer”
6. Click on “System properties”
7. Click on “Device Manager”
8. Under “Other devices” you will see T-Hub2 with an icon with a yellow exclamation mark.
9. Right-click the device and select "Update Driver"
10. Select "Browse my computer for driver software"
11. Select "Let me pick from a list of device drivers"
12. Click “Show All Devices”
13. Click “Have disk …”
14. Browse to where you put the extracted files
15. Select and open “Android_winusb.inf”
16. Select “Android Composite ADB Interface”
17. Click “Next” and then Click “Yes” (Ignore warning)
18. Wait until the software installs
19. You should now have Android Composite Interface” under the “Android Phone” listing
If you have problems, ensure Debugging is selected and try unplugging the THub and reconnecting it
ACCESSING ADB
1. Ensure that Debugging has been enabled – Settings Developer options USB debugging and make sure the box is checked
2. The following is for Windows 7, other versions will be similar, It also assumes that the file has been down loaded, unzipped and installed in a folder called THub on you C: drive
3. Connect the THub to your PC
4. Click in the “Start” icon, lower left icon on your PC Desktop
5. In the entry box type in “CMD” and push “Enter”
6. You will be at the “Command Prompt”
7. You need to navigate to the “THub” folder, the following are my entries, and yours should be similar.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Terry>cd .. and “Enter”
C:\Users>cd .. and “Enter”
C:\>
C:\>cd THub and “Enter”
C:\THub>
8. At the THub folder type in “ADB devices” and “Enter”
9. You should get an output similar to this:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
01545CAB0B015004 device
C:\THub>
10. You now have ADB access
11. Try “adb shell” and “Enter” to enter ADB and then “ls” and “Enter” to get the THub Root folder listing
What next, I don’t know but at least we have ADB access?
I have been trying to copy system files to my SD card to have a look at them but have no success.
Does anyone know how?
Here is the site I uploaded the files to:
"You can fill in the missing bits"
xxx.mediafire.com/download/voku3wnuff5s2ef/THub.zip
NOTE: There is also a file called “UniversalAdbDriverSetup6.msi”.
I don’t know what it is for, but I installed it anyway. It MAY be necessary for the above method.
Firstly, I understand this is an old thread but quite a lot of us Australians have this THub 2 now because Telstra seem to basically be handing them out like shots at a party.
As far as I know this thing still has no root access. You can get into ADB with it without too much trouble.
But what I really want to know is how I can get root access with SuperSU so I can install something like AdAway to remove the seemingly ridiculous amount of advertisements that apps and etc. come with.
In addition to that, after installing just TWO small apps. It seems the device's internal memory is already full and it cannot install any more apps.. I need root access in order to run Apps2SD so I can move some apps to the SD card that I have purchased for it.
Does anyone, and I mean anyone have any ideas about how to root this thing? There has to be some Australian who has a rooted version with SuperSU running.
I tried 'towelroot' but the device just rebooted (meaning it failed) and then when I ran the .apk again it said that the device was unsupported.
It's one thing to be able to get access to the root partition (which is possible over ADB) but it's another to be able to run apps with root privileges.
For any information.
The specs are:
Manufacturer - Technicolor
Operating System - Ice Cream Sandwich 4.0.4
Processor - 1 GHz dual core
Screen - 7″ (1024 x 600 pixels)
Camera - 1.9 MP rear camera, 1.2 MP HD front camera
RAM - 1GB
Storage - 2 GB Internal with an expandable Micro SD card slot (1GB internal usable)
Battery - 6000 mAh (non-removable)
I know it's nothing amazing, but if I could root the device and change the DPI, remove advertisements and install a few hacks. I'd get so much more out of the device.
I picked it up in almost perfect condition second-hand off eBay for only $15. They're worth $360 AU brand-new.
If anyone has any information at all, please do post something. My apologies again for bumping a super old thread but otherwise I was going to just start my own.
Possible to restore system partition
Hi Guys,
I done goofed.
I killed my T-Hub by flashing a corrupted system partition and now the device wont boot and only displays the Telstra logo at the boot loader. I do have a backup of my system partition however I cant work out how I would perform the restore. The boot loader will not allow an ADB connection so no luck there.
Im thinking JTAG may be my only option. I have experience with this on other devices but i cant find the JTAG terminals on this thing? I must have tapped about 60 different combinations of testpoints now and have only been able to get console out of the radio module which is obviously no good for talking to the kernel.
Any help would be greatly appreciated.
Cheers,
Swamp
SwampCrack1210 said:
Hi Guys,
I done goofed.
I killed my T-Hub by flashing a corrupted system partition and now the device wont boot and only displays the Telstra logo at the boot loader. I do have a backup of my system partition however I cant work out how I would perform the restore. The boot loader will not allow an ADB connection so no luck there.
Im thinking JTAG may be my only option. I have experience with this on other devices but i cant find the JTAG terminals on this thing? I must have tapped about 60 different combinations of testpoints now and have only been able to get console out of the radio module which is obviously no good for talking to the kernel.
Any help would be greatly appreciated.
Cheers,
Swamp
Click to expand...
Click to collapse
I'm completely new to this. What ROM would i look for to install on the THUB if any? And if i could install it?
clearburn said:
I'm completely new to this. What ROM would i look for to install on the THUB if any? And if i could install it?
Click to expand...
Click to collapse
sorry but no one has developed a ROM for this device, there is no demand
Madaz2 said:
sorry but no one has developed a ROM for this device, there is no demand
Click to expand...
Click to collapse
Thanks. I thought there might have been a rom from the basic device that didn't have all of the Telstra stuff on it.
It is currently a brick
if you can root it then you could install Titanium backup and uninstall the bloatware off of it
Some moderate success
I have had some moderate advancements of late.
I can get temporary ADB root using the directory traversal exploit
.
While the above method gets you a root terminal session, as it screws with some settings the device is nearly unusable due to screen flicker and general lag. I guess the exploit breaks some settings. Does anyone know how to leave the exploit in place and restore the settings file to eliminate the flickering and lag?
I have been able to export the system partition, edit it (add su.bin and SuperUser.apk) then swap the system mount so the device uses my edited system partition as described by malleus. When I try to flash my partition the device reboots and is in a semi brick state (reboot loop, stuck on boot loader Telstra logo).
I was able to obtain the OTA update files by getting an old 2.3.7 device, rooting it then grabbing the OTA files using ADB once it had downloaded them. These OTA's can be flashed from an SD card (ext4 format) in 3e recovery. This was a good bit of progress as it means I can restore from a bricked state. If anyone needs them, the files I have are:
Product_4.0.4_3.38-FOTA
Product_4.0.4_3.48-FOTA
This is all new territory for me but i think I am getting close to achieving full, persistent root in 4.0.4.
Any help would be appreciated.
I would be very interested in your progress as I have one of these but in default state it is only usable as a phone on the DECT base.....
Having some useful apps running off an SD card would help no end (like multimedia remote for my home theatre system)
Cheers,
Alex B
SwampCrack1210 said:
I have had some moderate advancements of late.
I can get temporary ADB root using the directory traversal exploit
.
While the above method gets you a root terminal session, as it screws with some settings the device is nearly unusable due to screen flicker and general lag. I guess the exploit breaks some settings. Does anyone know how to leave the exploit in place and restore the settings file to eliminate the flickering and lag?
I have been able to export the system partition, edit it (add su.bin and SuperUser.apk) then swap the system mount so the device uses my edited system partition as described by malleus. When I try to flash my partition the device reboots and is in a semi brick state (reboot loop, stuck on boot loader Telstra logo).
I was able to obtain the OTA update files by getting an old 2.3.7 device, rooting it then grabbing the OTA files using ADB once it had downloaded them. These OTA's can be flashed from an SD card (ext4 format) in 3e recovery. This was a good bit of progress as it means I can restore from a bricked state. If anyone needs them, the files I have are:
Product_4.0.4_3.38-FOTA
Product_4.0.4_3.48-FOTA
This is all new territory for me but i think I am getting close to achieving full, persistent root in 4.0.4.
Any help would be appreciated.
Click to expand...
Click to collapse
Has anyone made any progress on this?
I have two of these tablets that have sat unused since I got them from Telstra. I really just want to update it to at least 4.1, but there's no official release from Telstra for the T-Hub, and I don't think there will be. Are ports entirely unfeasible?
Do you think I could contact Technicolor? What should I say?
P.S. there is a recovery mode, because I've booted into it.
hxxp://imgur.com/O0uq4Uk
This is another howto on upgrading your A100 from Android 4.0 (ICS) to the latest and greatest Android 4.1 (JB). I am posting this because I had a heck of a time getting it on my tablet because the /system/ refused to mount as RW and I received a dead droid logo. Also I did not find an all in one for n00b's.
Hopefully this helps some people out!
######################################
Acer Iconia A100 - Custom ROM Walkthrough
######################################
Root Method One: http://forum.xda-developers.com/showthread.php?t=1531646
Root Method Two: http://forum.xda-developers.com/showthread.php?t=1886460
Unlock The Bootloader: http://forum.xda-developers.com/showthread.php?t=1557445
Install CWM 5.5.0.4: http://forum.xda-developers.com/showthread.php?t=1601663&highlight=cwm
CyanogenMod 10 Jelybean: http://forum.xda-developers.com/showthread.php?p=29276033&highlight=gapps#post29276033
Jelybean Overclocked Kernel: http://forum.xda-developers.com/showthread.php?t=1818924
IMPORTANT!
----------
Before you can do anything below you need to be running ICS and have a rooted device! I received ICS in an over the air update and used THIS root method.
Preliminary:
-----------------
- Your running ICS and root right?
- Download the zip at the end of this post for all the files you will need (Windows Only)
- If you do not have the a100 drivers installed yet open "Acer_ADB_Drivers" and run "setup.exe"
- Open the command prompt with admin rights and goto your unzipped folder
Bootloader:
----------------
- Run "install-eng.bat" and wait a while. If it looks stuck WAIT, fight the urge to push any buttons!
- A screen will appear with a lock and a door. Press the volume down (Left) key then volume up (Right) to select it
- At the command propmpt type "fastboot reboot-bootloader"
- The Tab will reboot at you will see in the top left "Bootloader v0.03.06-ICS(UnlockMode)"
NOTE: The Acer logo on boot gets a bit funky but its nothing to worry about.
ClockWork Recovery:
-------------------------------
- Enter "adb devices" to make sure ADB still can communicate. If not restart the Tab and make sure the USB is still plugged in.
- Enter "adb reboot bootloader" The tab will stay on the "Bootloader v0.03.06-ICS(UnlockMode)" screen
- Once bootloader is in fastboot type "fastboot erase recovery"
- Enter "fastboot flash recovery recovery.img" and it will write in a few seconds
- Enter "fastboot reboot"
- After the tab is back in ICS open the SDCARD drive in windows and drop the "cm-10-20120902-UNOFFICIAL-a100.zip" and "ICS A100 gapps.zip" files to the root of the SDCARD, not the internal
- Now you can shut off the Tab
Boot Into CWM:
-----------------------
Hold the "Power" button and the "Volume Down (Left)" buttons for a few seconds and the Tab will start into CWM. If you get the dead droid logo then goto the section at the bottom!
Install A ROM:
---------------------
- Select "Backup and restore" and do a backup! if you skip this you will have nothing to go back to if it fails...
- Next do a factory reset and wipe the cache
- Select "Install ZIP from SDCARD" and choose "Select ZIP from Internal SDCARD"
- Choose "cm-10-20120902-UNOFFICIAL-a100.zip"
- Choose "Go Back" and then "Install" again
- Select "ICS A100 gapps.zip" this time
Congrats! You now have Jellybean with all the google apps!
Overclocked Kernel:
-----------------------------
Goto the link provided at the top and read all about this kernel as it has A LOT of features and options. Below is my quick setup.
- Off the forum thread choose a Zram if you want to use it.
- Plug your tab into the USB port and transfer the "gm-a100-v2.0-signed.zip" and whatever Zram zip you downloaded into the SDCARD drive.
- Reboot into CWM
- Do a factory reset and wipe the cache
- Choose "Install" and select "gm-a100-v2.0-signed.zip" to install the new kernel
- Go back and choose install again and select the Zram zip file if your using it
- Thats all you need to do. Just restart and Jellybean will be running the new kernel.
NOTE: After installing the new kernel I got a Quadrent score of 2563 which is better then the A500 and Galaxy Tab 10" so I am now quite happy with this device. One thing to mention is if you have used JB on something like the NExus 7 the UI is not the same on the a100. Other then the intro and the settings page the UI feels just like ICS but don't be discouraged as theirs a TON of new features in the settings tab I not can't live without!
Dead Droid Logo:
-------------------------
This happened to me as my previous root worked at everything except my tab REFUSES to mount /system/ as RW! If the normal steps above would have worked this would all be avoidable...
- Start your tab and transfer "A100_Recovery.zip" to your "Internal Storage" drive
- In your file manager make sure "A100_Recovery.zip" is in "/mnt/sdcard/" and NOT "/mnt/external_sd/" and then unzip the contents to the current directory
- Download a terminal emulator from the Play store or open yours if you have one
- Run "su" to gain root permissions and accept any pop ups
- Run "sh /mnt/sdcard/rec.sh" and this will hammer CWM into your flash location
- Exit out of the terminal and shutdown your tab and go back to the Boot Into CWM section
########################
DOWNLOAD ------ (Dropbox)
DOWNLOAD---- (Sendspace)
########################
Nice, only noticed a few things that need addressing.
Few typos here and there, it happens lol
Edit: no longer relevant.
Tapatalked from my Galaxy S II.
Also, I prefer and I'd even go as far as to prefer TWRP, much faster and its touch!
Sent from my A100 using xda premium
Nice write up. I would like to add a few tidbits.
I agree with twrp, it is way more noob friendly, interface wise and installation. With the self installing scripts.
Step 5 and step 8 are having the user reboot into the boot loader, the second time for no reason, as you would already be there.
Step 12, use the JB gapps 713 from the general cm10 thread.
You can install the gapps right after installing the ROM and kernel, all in one boot into the recovery. Also linuxsociety's goddroid ROMs have his kernel already installed with cm10.
Installing the kernel separately. Always wipe cache and davlik cache, as a last step before rebooting.
Oh also I may have missed it but renaming install-recovery.sh.
Tapatalked from my Galaxy S II.
@pio_masaki:
- Hopefully I got all the spelling mistakes, I posted just before bed and it shows lol.
- I did have a statement that you needed root in the important tab and I made it more colorfull and noticable now. I also included links to the two rooting methods I know work.
- About renaming "install-recovery.sh" as I could not get my /system/ to mount RW I had no way to try and see if that worked. If someone gets to that stage though the section at the bottom under "Dead Droid Logo" gives a method that definatly works
@das_webos_transformer:
- I have never used TWRP and I have CWM on my other devices so I just used it automatically. I don't think speed or needing touch is very important as your only using the recovery mode a few times a year. (Unless your a DEV and then you wont need a N00b tutorial) I will check it out though.
@Romman0:
- Selecting the unlocked icon restarted my tablet to the UI so I can only assume if someone uses my zip they will get the same sequence as me. I wrote the guide as I did the steps myself.
- I looked through the CM10 thread and they said the ICS gapps worked just fine. I got them right off the thread's title post.
- I combined the CM10/gapps install and added a wipe cache to the kernel step. Thanks for the pointer
Consernimg twrp, its much simpler and way faster. You can auto install ROMs! Clockwork mod is fine for devices that are old or have a small screen but, honestly, with a 7in best like ours touch is the way to go. Promise you will like it better.
Sent from my A100 using xda premium
Hello.need help. im on the installing rom section and when i choose "select zip from internal sdcard" i get a "E:cant mount /emmc/" message
nene150 said:
Hello.need help. im on the installing rom section and when i choose "select zip from internal sdcard" i get a "E:cant mount /emmc/" message
Click to expand...
Click to collapse
Not to go against this guide but install from external SD. Installing from internal seems to cause problems at times, and is also a bad place to keep stuff you wish to keep, like ROMs and backups.
Tapatalked from my Galaxy S II.
pio_masaki said:
Not to go against this guide but install from external SD. Installing from internal seems to cause problems at times, and is also a bad place to keep stuff you wish to keep, like ROMs and backups.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
thanks for the advice but i think the tablet has the internal and external mixed cause when i go to the "choose zip from sdcard" option all my files from my internal is in there. So me think that i was smart i put the 2 zips (gapps&cm zips) in the internal so i could install it to the tab cause of the problem i had and now i get stuck on the cm boot screen
nene150 said:
thanks for the advice but i think the tablet has the internal and external mixed cause when i go to the "choose zip from sdcard" option all my files from my internal is in there. So me think that i was smart i put the 2 zips (gapps&cm zips) in the internal so i could install it to the tab cause of the problem i had and now i get stuck on the cm boot screen
Click to expand...
Click to collapse
That error only exists in CWM. If you use TWRP, you wouldn't experience switched mount points.
Go to advanced and mounts and mount sdcard you can switch between them.
Tapatalked from my Galaxy S II.
I am having problems when unlocking the bootloader. I get the following message:
It does not reboot or do anything. It is rooted and there are several applications that use the root. Anyone know what is going on?
Code:
Wait for connecting device
'adb' is not recognized as an internal or external command,
operable program or batch file.
-
-
Prepare...
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
-
-
Execute scripts
'adb' is not recognized as an internal or external command,
operable program or batch file.
-
-
Rebooting
-
-
Wait for connecting device
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
-
-
Press key volume down, then key volume up and reboot device!
Good luck!
It isn't being run where adb and fastboot are. Run the script from wherever adb and fastboot are located.
Tapatalked from my Galaxy S II.
OK, so I should be keeping that library of files on my computer? I tried that and it just says "Wait for connecting device" and it never moves. So I thought I had to move the files to my tablet. I am running Win 7 x64 and it doesn't seem to think my device is connected and it certainly is.
edit: nm, I closed out some running tasks and it seems like something was still running in the background.
now I get the message:
Wait for connecting device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
The device doesn't reboot or anything.
[email protected] said:
OK, so I should be keeping that library of files on my computer? I tried that and it just says "Wait for connecting device" and it never moves. So I thought I had to move the files to my tablet. I am running Win 7 x64 and it doesn't seem to think my device is connected and it certainly is.
edit: nm, I closed out some running tasks and it seems like something was still running in the background.
now I get the message:
Wait for connecting device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
The device doesn't reboot or anything.
Click to expand...
Click to collapse
May want to uninstall then reinstall the drivers, reboot then try again.
Tapatalked from my Galaxy S II.
problems with cwm
Ok, I followed this guide and have trouble at the point of booting into cwm. I get no options for loading .zip. The updating status bar almost comes to the end then the tab reboots. It says updating "ebt" or something then reboots back into ics. Any help on this?
solved
Ok, after some serious thread reading all over here I found this by pio_masaki, and it solved my problem. Thanks to pio_masaki
It's because I said what the scripts you guys are running are doing. Trust me, I know the process, I know what it's doing, I know how to do it by hand without running scripts. The process I outlined above is correct.
Root the device (this must be done FIRST)
Flash the A200 bootloader (this is required for fastboot oem unlock to work)
Reboot back into android
Delete /system/etc/install-recovery.sh (if you don't you overwrite your custom recovery with stock) (this is the part I missed)
Install your custom recovery
From this point on you can backup, flash new ROMs, do whatever you want.
The reason I mentioned deleting (or renaming for that matter) the /system/etc/install-recovery.sh file is BECAUSE it isn't mentioned where it should be in the directions, resulting in people flashing their new recovery, and then losing it again. You can go back and forth flashing recoveries all you want, removing this file is required to keep it past a reboot. The file is also used for the crossix mount swap mod, in which case you will leave it alone, it won't touch the recovery.
The first time I went through this entire thing, no one had mentioned the file being renamed or moved, and it overwrote my recovery, so I had to rename it, then flash again. I say to do it when I do to save that extra time and flashing. I'm helping you, trust me. Also as the file sits in /system/etc you need root and system R/W to mess with it, so again, Root, Unlock, Recovery. In that order.
Oh another edit lol you can do the file rename any time after root, it doesn't have to be after the boot loader step, I put it there because you generally reboot after rooting and the next script also reboots you, so I chose that time because of that.
Click to expand...
Click to collapse
How to
marcusjbid said:
Ok, after some serious thread reading all over here I found this by pio_masaki, and it solved my problem. Thanks to pio_masaki
Click to expand...
Click to collapse
I had to search around a bit to find out how to rename the file. I used Root Browser Light from the Android market and renamed it on the tab. Other file browsers didn't work. Now no more dead droid! =D
Help! Followed instructions and now I'm bricked
Hi, thanks for the guide but I have an issue.
At the point where you reboot to CMW using power on and left volume it did not boot to CMW. Instead I got a "configuring tablet" message that looked like and oem message.
When it rebooted I'm left with the Acer logo and "Bootloader Version 0.03.06-ICS (unlock mode) screen and nothing else.
It does not complete boot.
Is that it for my tablet?
Hope you can help.
Hey guys,
I was using Sandvolds ICS for some weeks, but since yesterday my phone won't work anymore. I was starting a bike tour, but GPS on Endomondo didn't really work. So I restarted my phone. When I boot it'll show the white screen with green HTC logo, then it'll show the Evervolv animation and this animation will be displayed until I remove the battery, one time I had it running for half an hour.
I tried to boot the phone without sd card and could boot, but after "optimising" apps it kept on crashing because, as it appears, the system data is partly on the sd card.
Now I don't know what to do, what would you recommend? I'd probably just wipe everything and reinstall a backup, but - I don't have a backup
wipe everythin and reflash another rom/same rom...............
2012katas said:
wipe everythin and reflash another rom/same rom...............
Click to expand...
Click to collapse
i guess that'll work, but could anyone recommend another, more time-saving possibility?
greets to india!
Tourist06 said:
Hey guys,
I was using Sandvolds ICS for some weeks, but since yesterday my phone won't work anymore. I was starting a bike tour, but GPS on Endomondo didn't really work. So I restarted my phone. When I boot it'll show the white screen with green HTC logo, then it'll show the Evervolv animation and this animation will be displayed until I remove the battery, one time I had it running for half an hour.
I tried to boot the phone without sd card and could boot, but after "optimising" apps it kept on crashing because, as it appears, the system data is partly on the sd card.
Now I don't know what to do, what would you recommend? I'd probably just wipe everything and reinstall a backup, but - I don't have a backup
Click to expand...
Click to collapse
I got the same situation with you dude!!
I'm now using beta 0.17.1, but after this afternoon everything was wrong.
Then I did a full wipe and installed the latest version of Sandvolds ICS,
It's good and normal before I activate a2sd, but after that
everything went wrong again.
And finally I tried HTC DESIRE-AOKP-milestone6 v2,
It is working normally with INT2EXT, but not very smooth and stable.
actually i don't know what's going on right now :crying:
UserMatty said:
I got the same situation with you dude!!
I'm now using beta 0.17.1, but after this afternoon everything was wrong.
Then I did a full wipe and installed the latest version of Sandvolds ICS,
It's good and normal before I activate a2sd, but after that
everything went wrong again.
And finally I tried HTC DESIRE-AOKP-milestone6 v2,
It is working normally with INT2EXT, but not very smooth and stable.
actually i don't know what's going on right now :crying:
Click to expand...
Click to collapse
hi everybody..i've got the same problem..everything was ok until yesterday with the latest release of the sandvold ics rom..when my phone shutted down for low battery,i put it on charge..after that,i booted it up,and it still remain on the evervolv logo...so i tried to wipe cache,wipe partition,factory reset and format and repartition the sd card..reinstall the rom..and eveything was ok the first time..after that,i enabled the a2sd,and it strucked another time..so i did everything again from the beginning,but this time i enabled the a2sd without any problem..so i started to download from the market all the stuff that i needed,and everything was fine..so i rebooted the phone..and here we go again..strucked!but the worst thing is that without the sd,the phone boot without any problem!now..i bought the sd a week ago..it's a new one..i don't think that it's an sd problem..or also the first times it won't be able to boot up and everything..also i would't be able to install the rom!..so..any suggestion?
Cesk87 said:
hi everybody..i've got the same problem..everything was ok until yesterday with the latest release of the sandvold ics rom..when my phone shutted down for low battery,i put it on charge..after that,i booted it up,and it still remain on the evervolv logo...so i tried to wipe cache,wipe partition,factory reset and format and repartition the sd card..reinstall the rom..and eveything was ok the first time..after that,i enabled the a2sd,and it strucked another time..so i did everything again from the beginning,but this time i enabled the a2sd without any problem..so i started to download from the market all the stuff that i needed,and everything was fine..so i rebooted the phone..and here we go again..strucked!but the worst thing is that without the sd,the phone boot without any problem!now..i bought the sd a week ago..it's a new one..i don't think that it's an sd problem..or also the first times it won't be able to boot up and everything..also i would't be able to install the rom!..so..any suggestion?
Click to expand...
Click to collapse
maybe you can temporarily try DESIRE-AOKP-milestone6 v2
it's also a good choice! and a good rom also.
Hey,
I have the same problem! I also have Sandvolds ICS rom and it gets stuck on the Evervolv loading screen.
It loads up flawlessly without my SD card but then all my stuff is gone.
Any way to backup my data? (EDIT: Nevermind that question, I used backup from recovery)
BTW, SD card works, I can mount it from recovery mode.
Guys, what you say doesn't make me happy!
Maybe it's worth mentioning that I was NOT using the latest version of ICS, but I had no problems for weeks. I'm already waiting for the new Nexus phones, one of them will save me a lot of time and trouble updating to the newest OS and software
Good luck everyone, and please tell us if you manage making your phone working again
tried updating to latest ics via 4ext - fail! i could watch the evervolv animation for hours
Possible Solution
Looking in the Sandvold's thread a lot of people have been claiming that the bootloops is caused by the most recent version of Google Play 3.9.16. Apparently just deleting that will let you boot fine.
AceShinobi said:
Looking in the Sandvold's thread a lot of people have been claiming that the bootloops is caused by the most recent version of Google Play 3.9.16. Apparently just deleting that will let you boot fine.
Click to expand...
Click to collapse
The solution is here: http://forum.xda-developers.com/showthread.php?t=1944766
For me didn't work, but I want to try again and apply the solution directly on the first boot.
AceShinobi said:
Looking in the Sandvold's thread a lot of people have been claiming that the bootloops is caused by the most recent version of Google Play 3.9.16. Apparently just deleting that will let you boot fine.
Click to expand...
Click to collapse
Thanks for your hint, but after a few steps, I was stuck. After downloading the SDK (not mentioned in the tutorial) I experienced problems in the following steps, here is where I had problems
- cd Program Files(x86)/Android/android-sdk/platform-tools/ - I had to enter cd AppData\Local\Android/android-sdk/platform-tools/
- adb shell - command didn't work - I entered adb resulting in lots of text on my screen
- cd /data/data/ - the shell didn't accept this
Tourist06 said:
- cd /data/data/ - the shell didn't accept this
Click to expand...
Click to collapse
Probably because there is no folder /data/data? Have you followed the instructions in this thread? That should work.
Tourist06 said:
Thanks for your hint, but after a few steps, I was stuck. After downloading the SDK (not mentioned in the tutorial) I experienced problems in the following steps, here is where I had problems
- cd Program Files(x86)/Android/android-sdk/platform-tools/ - I had to enter cd AppData\Local\Android/android-sdk/platform-tools/
- adb shell - command didn't work - I entered adb resulting in lots of text on my screen
- cd /data/data/ - the shell didn't accept this
Click to expand...
Click to collapse
Seems like an adb fault.
If you type: adb get-state and adb get-serialno you have in output the infos of your Desire?
freakymonkey said:
Seems like an adb fault.
If you type: adb get-state and adb get-serialno you have in output the infos of your Desire?
Click to expand...
Click to collapse
adb shell will return device not found, adb get-serialno and adb-get-state return unknown
Using 4ext, I mounted system and sd-card
I also tried dietwice's tip (http://forum.xda-developers.com/showpost.php?p=33073702&postcount=8), but at step 3, cd /system/app , it says path not found. I'm no guru, so I don't really know what to do now.
Sorry about the fonts, it's a mess^^
Tourist06 said:
[...] I mounted system and sd-card [...]
Click to expand...
Click to collapse
You need to mount "system" and "USB storage". You have to be connected to your computer.
gartenriese said:
You need to mount "system" and "USB storage". You have to be connected to your computer.
Click to expand...
Click to collapse
Exactly, you have to mount more or less everything, depends on what kind of a2sd you have.
In my case, I had to mount everything because of "standard app2sd"; my "vending" are in /system, /data and /sdext.
Just to be sure, you have to undestand if the phone is connected to the computer. To check this try to write:
...../platform-tools/adb kill-server (press enter)
...../platform-tools/adb start-server (press enter)
NOW plugin your HTC Desire (in Recovery mode) to the computer and digit:
...../platform-tools/adb devices
Should appear at least your Deside (on the right side of the phone code will appear the word"recovery")
If this appear, you can prooced with "adb shell" or all other commands required for the procedure.
I had the same bootloop problem, it was easy to remove all the Play Store files.
Hope helping you.
Mat
Tourist06 said:
adb shell will return device not found, adb get-serialno and adb-get-state return unknown
Using 4ext, I mounted system and sd-card
I also tried dietwice's tip (http://forum.xda-developers.com/showpost.php?p=33073702&postcount=8), but at step 3, cd /system/app , it says path not found. I'm no guru, so I don't really know what to do now.
Sorry about the fonts, it's a mess^^
Click to expand...
Click to collapse
gartenriese said:
You need to mount "system" and "USB storage". You have to be connected to your computer.
Click to expand...
Click to collapse
I think that Tourist06 can't resolve with mounting /system or something else, because he has a problem with adb (adb don't talks with his device).
Have you followed this guide for installing adb?
@freakymonkey: I followed the guide, seemed to work! If I enter the shell I no more need to enter the whole path, entering "adb" will produce text. Please have a look at the following screenshot, hope you can confirm this.
@matteo.rex, no success, here's a screenshot
A pop-up appeared saying there were unidentified devices.
Thanks for your help, guys! My phone isn't working for the sixth day now
Tourist06 said:
A pop-up appeared saying there were unidentified devices.
Click to expand...
Click to collapse
Uhm, this is the problem maybe.
First question: is the phone charging when you plugin it to the pc? (I had a problem with the cable...solved changing it)
Second: could be not an ADB installation problem, but a Driver Installation problem. Check this thread to download it: http://forum.xda-developers.com/showthread.php?t=654047
If typing "ADB" a list of command appear, this mean that it work.
Windows, after the driver installation, have to recognize you Desire also during Recovery, not only during common use.
I hope it could help you!
Let us know!
p.s. I use ADB over Ubuntu, but the work is the same.
I wanted to install LineageOS.
I followed the tutorial here: https://wiki.lineageos.org/devices/bullhead/install
I completed the folowing steps
Code:
6.) Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
7.) Go back to return to main menu, then select Install.
8.) Navigate to /sdcard, and select the LineageOS .zip package.
But couln't complete the 8th step becaus I think I don't have the LinageOS zip on my phone, How can I move it there?
How can I send LineageOS install package to my phone so I can install it with TWRP ?
I am using Nexus 5x with Windows 10.
Not to worry
Easy. Just boot up your current ROM and USB, SD Card, Bluetooth, WHATEVER means you have available to move the file to your downloads folder or someplace like that. As long as you can navigate to it, TWRP will let you do that when the time comes. Recommend you put your GApps zip file (I prefer nano) and the appropriate L.O.S. su-addon zip in there as well. After all, what's the use of the ROM if it isn't rooted
Now, fire it up in TWRP and do at least one complete, everything you can include backup of the whole thing before you do ANYTHING else. TWO backups are better if you can move one of them completely off device, as in to a USB stick, etc... The more good backups you have, the less the evil Gods of screwing up installs will try to seek you out. Yes, that has been scientifically proven, even if it sounds like superstitious mumbo-jumbo.
Still good? Wipe dalvik, cache, whatver your build recommends, and flash L.O.S., the su-addon, and GApps all at once. Reboot, be just a little bit patient the first time around, and enjoy. Good Luck.
nezlek said:
Easy. Just boot up your current ROM and USB, SD Card, Bluetooth, WHATEVER means you have available to move the file to your downloads folder or someplace like that. As long as you can navigate to it, TWRP will let you do that when the time comes. Recommend you put your GApps zip file (I prefer nano) and the appropriate L.O.S. su-addon zip in there as well. After all, what's the use of the ROM if it isn't rooted
Now, fire it up in TWRP and do at least one complete, everything you can include backup of the whole thing before you do ANYTHING else. TWO backups are better if you can move one of them completely off device, as in to a USB stick, etc... The more good backups you have, the less the evil Gods of screwing up installs will try to seek you out. Yes, that has been scientifically proven, even if it sounds like superstitious mumbo-jumbo.
Still good? Wipe dalvik, cache, whatver your build recommends, and flash L.O.S., the su-addon, and GApps all at once. Reboot, be just a little bit patient the first time around, and enjoy. Good Luck.
Click to expand...
Click to collapse
Sorry I don't know what you mean exactly. Can you exlain a bit more?
My situation looks like this:
1) I don't need to backup anythig.
2) My problem is that I don't have the lineageOS zip on my phone so I can't install it with TWRP
3) because of step 5,6 on the tutorial I believe I don't have any current ROMS!
step 5,6:
Code:
5) Select Wipe and then Advanced Wipe.
6) Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
My assumption is that no ROM will load as the current ROM got deleted during step 5&6.
All I get when I start the phone is GOOGLE sign and the lock sign at the bottom.
4) When I go to Reboot inside TWRP and click System I get "No OS Installed! Are you sure you wish to reboot?"
Can you help?
flex567 said:
Sorry I don't know what you mean exactly. Can you exlain a bit more?
My situation looks like this:
1) I don't need to backup anythig.
2) My problem is that I don't have the lineageOS zip on my phone so I can't install it with TWRP
3) because of step 5,6 on the tutorial I believe I don't have any current ROMS!
step 5,6:
Code:
5) Select Wipe and then Advanced Wipe.
6) Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
My assumption is that no ROM will load as the current ROM got deleted during step 5&6.
All I get when I start the phone is GOOGLE sign and the lock sign at the bottom.
4) When I go to Reboot inside TWRP and click System I get "No OS Installed! Are you sure you wish to reboot?"
Can you help?
Click to expand...
Click to collapse
H'mmm.......... It does appear that you wiped the whole thing, and THAT may make it a bit more of a challenge, but let us try our best. HOPEFULLY your device will recognize the necessary files on a USB stick. You can tell TWRP to MOUNT the USB drive in order to do that if you must, and many devices have no problem and will recognize the device with no added effort, and you just have to navigate to it within TWRP. THAT will be the EASY way, and given what you've described, there isn't anything left on the device to be concerned about with respect to backups, etc... so cross your fingers, and if TWRP can mount and find a USB storage device you just have to flash the three zip files from USB storage as previously described. Otherwise, there is not much I could do personally without the device in hand, although the easiest path forward might be to re-flash a stock ROM and start over again. And please note you would not be the first person reading (or writing) this message to need to do that. Once you get the hang of this, it is not a brutal process, but the first time or two it can be a bit intimidating. Hang in there, the good news is that it is somewhat difficult to totally brick most of these things, so persistence should win out. As long as you can still boot it into TWRP you're fine. Now, one other very important thing. If somehow the bootloader was not unlocked, none of this is going to work at all. SO if that is the case, your only recourse is going to be to get that taken care of first, which requires one of: some finesse with ADB / fastboot, a ROM of some sort (i.e. re-install stock) installed on the device that lets you unlock it by flipping the switch in developer settings , or some other more geeky process that is best supervised by a person who genuinely knows what they are doing and with physical access to the device. There will be no shortage of content out here concerning how-to, but some of the folks writing it are not necessarily technical writers targeting a less experienced audience, even if they are in many cases quite brilliant programmers.
nezlek said:
H'mmm.......... It does appear that you wiped the whole thing, and THAT may make it a bit more of a challenge, but let us try our best. HOPEFULLY your device will recognize the necessary files on a USB stick. You can tell TWRP to MOUNT the USB drive in order to do that if you must, and many devices have no problem and will recognize the device with no added effort, and you just have to navigate to it within TWRP. THAT will be the EASY way, and given what you've described, there isn't anything left on the device to be concerned about with respect to backups, etc... so cross your fingers, and if TWRP can mount and find a USB storage device you just have to flash the three zip files from USB storage as previously described. Otherwise, there is not much I could do personally without the device in hand, although the easiest path forward might be to re-flash a stock ROM and start over again. And please note you would not be the first person reading (or writing) this message to need to do that. Once you get the hang of this, it is not a brutal process, but the first time or two it can be a bit intimidating. Hang in there, the good news is that it is somewhat difficult to totally brick most of these things, so persistence should win out. As long as you can still boot it into TWRP you're fine. Now, one other very important thing. If somehow the bootloader was not unlocked, none of this is going to work at all. SO if that is the case, your only recourse is going to be to get that taken care of first, which requires one of: some finesse with ADB / fastboot, a ROM of some sort (i.e. re-install stock) installed on the device that lets you unlock it by flipping the switch in developer settings , or some other more geeky process that is best supervised by a person who genuinely knows what they are doing and with physical access to the device. There will be no shortage of content out here concerning how-to, but some of the folks writing it are not necessarily technical writers targeting a less experienced audience, even if they are in many cases quite brilliant programmers.
Click to expand...
Click to collapse
The bootloader is unlocked becaues I unlocked it and I see the red sign:
Code:
DEVICE STATE - unlocked
When I click Mount I get the following options, System, Vendor Data, Cache, USB OTG, which one should I select ?
I was able to fix it and I installed it now the Lineage OS works
I had to go to
Code:
Mount > enable MTP
and after that I was able to use
Code:
ADB SHELL
and after that I was able to push the zip to the device. Once it was on the phone I was able to use TWARP to install it.
Code:
$ adb push lineage-15.1-20180430-nightly-bullhead-signed.zip sdcard
The only question I have is why I get this message every time I turn on the phone, how can I remove it? :
Code:
A vendor image mismatch has been detected. Typically this means your vendor images us out of date. Please enousre your vendor image matches OPM2. 171019.029
Since I decided not to install Play Store, how can I now install some programs without the playstore ?
flex567 said:
I was able to fix it and I installed it now the Lineage OS works
I had to go to
Code:
Mount > enable MTP
and after that I was able to use
Code:
ADB SHELL
and after that I was able to push the zip to the device. Once it was on the phone I was able to use TWARP to install it.
Code:
$ adb push lineage-15.1-20180430-nightly-bullhead-signed.zip sdcard
The only question I have is why I get this message every time I turn on the phone, how can I remove it? :
Code:
A vendor image mismatch has been detected. Typically this means your vendor images us out of date. Please enousre your vendor image matches OPM2. 171019.029
Click to expand...
Click to collapse
Wow, you took what I would have thought of as the long way, but so far, so good it would seem. I was thinking you could have simply mounted the USB as an OTG device and flashed directly from that via TWRP. I have ZERO clue about the "vendor image mismatch" message. But now that you have it more or less working, you COULD try putting the zip files into the regular downloads folder, do a dalvik and cache (factory reset) wipe, and re-flash them. You haven't loaded up a bunch of stuff to worry about replacing. Worst case you repeat initial setup. What have you got to lose?
---------- Post added at 08:36 PM ---------- Previous post was at 08:27 PM ----------
flex567 said:
I was able to fix it and I installed it now the Lineage OS works
I had to go to
Code:
Mount > enable MTP
and after that I was able to use
Code:
ADB SHELL
and after that I was able to push the zip to the device. Once it was on the phone I was able to use TWARP to install it.
Code:
$ adb push lineage-15.1-20180430-nightly-bullhead-signed.zip sdcard
The only question I have is why I get this message every time I turn on the phone, how can I remove it? :
Code:
A vendor image mismatch has been detected. Typically this means your vendor images us out of date. Please enousre your vendor image matches OPM2. 171019.029
Since I decided not to install Play Store, how can I now install some programs without the playstore ?
Click to expand...
Click to collapse
Missed that one, sorry. If you did not flash the GApps zip when you installed Lineage, you can hunt down the .APK files for apps you want on the web. That'd be the only way I can think of and a good reason to re-do it before it is too long into the process !!! If you pick the nano or even pico options you won't be dragging much if any Google bloat onto the phone. Personally, while I often find the Play Store to be a pain in the .... I can ignore it until I need something. On some devices it can certainly be most intrusive.
I don't think I will play around with it now for some time.
I was thinking you could have simply mounted the USB as an OTG device and flashed directly from that via TWRP
Click to expand...
Click to collapse
I tried to select the OTG thing but was unable to put the checkmark in.
I also found the fix for Vendor Image mismatch, didn't try if it works though:
https://gist.github.com/MacKentoch/48ad6b91613213ee9774c138267e2ed4#file-fix-lineageos-vendor-mismatch-error-nexus5x-md
I also think this needs to be updated:
https://wiki.lineageos.org/adb_fastboot_guide.html
https://wiki.lineageos.org/devices/bullhead/install
you COULD try putting the zip files into the regular downloads folder
Click to expand...
Click to collapse
I had problems pushing the LineageOS.zip file anywhere else, I coulnt create new folder.
flex567 said:
I was able to fix it and I installed it now the Lineage OS works
I had to go to
and after that I was able to use
and after that I was able to push the zip to the device. Once it was on the phone I was able to use TWARP to install it.
The only question I have is why I get this message every time I turn on the phone, how can I remove it? :
Since I decided not to install Play Store, how can I now install some programs without the playstore ?
Click to expand...
Click to collapse
Congratulations for not installing play store. I think you not installed play services as well. You simply did not install any GApps. That's the first step to get your setup slim and privacy friendly. Next steps are installing f-droid app. From f-droid you can install free software. If you really need apps from play store you can get them with yalp. If they don't run without Google play services you can try microG.
I found a page from which I can download apk files from play store so I will just use that for now.