Related
My Xoom is completely stock and I just received and installed the 3.2 update. I am pretty disappointed in the SD card support and lack of other features. I held off on rooting and installing Tiamat before as I wanted to see what Google would give us, and well I think I have waited long enough to see that it pales in comparison to what you devs can do.
So now I would like to give the Tiamat kernel a try. So I read through several of the threads and on the Tiamat 2.0.0 Kernel thread it assumes you are on 3.1, where I am already on 3.2. As it took me several months to convince the wifey that I needed my Xoom I do not want to risk bricking it, so I am looking for some help.
-First, is it currently possible to go straight from complete stock 3.2 to Katana?
-Second, and much more difficult, can someone provide me step by step instructions? I've seen several of the threads out there, some of them are very helpfull, some get me part way, but none of them cover this exact upgrade scenario. This just makes me very concerned with doing something wrong or if something changed in 3.2.
I know this is a lot to ask, but I think there are a lot of people who would benefit from this information.
Thanks
HuckFinn said:
My Xoom is completely stock and I just received and installed the 3.2 update. I am pretty disappointed in the SD card support and lack of other features. I held off on rooting and installing Tiamat before as I wanted to see what Google would give us, and well I think I have waited long enough to see that it pales in comparison to what you devs can do.
So now I would like to give the Tiamat kernel a try. So I read through several of the threads and on the Tiamat 2.0.0 Kernel thread it assumes you are on 3.1, where I am already on 3.2. As it took me several months to convince the wifey that I needed my Xoom I do not want to risk bricking it, so I am looking for some help.
-First, is it currently possible to go straight from complete stock 3.2 to Katana?
-Second, and much more difficult, can someone provide me step by step instructions? I've seen several of the threads out there, some of them are very helpfull, some get me part way, but none of them cover this exact upgrade scenario. This just makes me very concerned with doing something wrong or if something changed in 3.2.
I know this is a lot to ask, but I think there are a lot of people who would benefit from this information.
Thanks
Click to expand...
Click to collapse
The quick answer to your question is Yes, you can go from stock 2.3 to Tiamat Katana 2.0 kernel, but you must be rooted.
Are you rooted? If so, and if you have already installed Clockwork Mod Recovery 3.2.0.0 (from solarnz' thread in Development) you can just flash the Katana kernel and you should be fine.
If you are not unlocked and rooted--you can follow the directions here:
http://forum.xda-developers.com/showthread.php?t=1170760
There are actually some more user-friendly (for noobs) instructions http://forum.xda-developers.com/showthread.php?t=1130996 in this thread, but for STEP 5 (ROOTING) you have to substitute the method from jase's post (above) for the instructions for Step 5 in the "idiot's guide" I can't find any 3.2 root files yet. It's the same procedure but a bit more hands on. No matter what you do, you will have to use adb to unlock your bootloader and root, so gather all the necessary files, drivers and print out your instructions.
One thing to know is never try to install a .zip file through adb...that will cause massive headaches. However, it seems pretty hard to actually brick one of these Xooms through updating and flashing. (Don't drop it into water, though!)
Thank you for the information. All the posts asking for help because something did not go right still have me pretty apprehensive. I am not at all interested in over clocking, so it is really the what I assume is proper SD card support and USB tethering that interest me the most.
HuckFinn said:
Thank you for the information. All the posts asking for help because something did not go right still have me pretty apprehensive. I am not at all interested in over clocking, so it is really the what I assume is proper SD card support and USB tethering that interest me the most.
Click to expand...
Click to collapse
It's only by rooting that you are able to get the full functionality of the Xoom. It's great as it is...HC 3.2 is very good and improved, but this device is made to driven like a sports car, not just sat in like a minivan.
okantomi,
Well I have gone back and forth on wether to root or not and you have been very helpful with pointing me to good information. I am hoping you do not mind answering a couple more questions.
-In the "Idiot's guide to flashing" you pointed me to it installed CWM before rooting. Is this the proper order or would you root first? I know I should just follow the guide and give it a shot, but that just seems odd.
-Can you explain to be the difference between the Tiamat kernels and the ROMs? My assumption is that the ROM would include the kernel, but I have a strong feeling that is incorrect. I have read posts of installing the ROM first and then the kernel and I am just more confused.
Thanks, one day I will get there.
HuckFinn said:
okantomi,
Well I have gone back and forth on wether to root or not and you have been very helpful with pointing me to good information. I am hoping you do not mind answering a couple more questions.
-In the "Idiot's guide to flashing" you pointed me to it installed CWM before rooting. Is this the proper order or would you root first? I know I should just follow the guide and give it a shot, but that just seems odd.
-Can you explain to be the difference between the Tiamat kernels and the ROMs? My assumption is that the ROM would include the kernel, but I have a strong feeling that is incorrect. I have read posts of installing the ROM first and then the kernel and I am just more confused.
Thanks, one day I will get there.
Click to expand...
Click to collapse
I've got to be quick...I have to do some work today, lol, but here goes:
Actually, follow the Idiots Guide regarding the adb, moto drivers setup.
Then follow this http://forum.xda-developers.com/showthread.php?t=1170760
It's got all the right files and steps, and though it's pretty much to the point, it's user friendly enough. It will get you rooted, I'm sure.
While the difference between ROMs and kernels is somewhat over my head, the ROM does contain the kernel (it's sort of an all inclusive package to tell the device how to behave, whereas the kernel manages particular functions, but not others. It's more limited.) Because the Honeycomb source code hasn't been released, the developers are somewhat limited in the ROM-development department, but they have been able to work wonders with kernels. However, the Tiamat 1.1 Rom for HC3.1 was great and the new ROM in development for HC3.2 will be great too, if the Katana kernal for HC3.2 is any indicator.
Sorry to be a pest but just want to make sure I understand.
A) Follow the idiot's guide steps 1-2, which covers Xoom driver installation and ADB installation.
B) Then follow the other link (How to root your Xoom from stock 3.2) for unlocking and rooting.
C) Then go back to the idiot's guide, skip step 3 (unlocking-already done above) and do step 4 (CWM Installation), skip step 5 (rooting-already done above), then follow step 6 (installing the new kernel).
Again I really appreciate all the advice.
-HuckFinn
HuckFinn said:
Sorry to be a pest but just want to make sure I understand.
A) Follow the idiot's guide steps 1-2, which covers Xoom driver installation and ADB installation.
B) Then follow the other link (How to root your Xoom from stock 3.2) for unlocking and rooting.
C) Then go back to the idiot's guide, skip step 3 (unlocking-already done above) and do step 4 (CWM Installation), skip step 5 (rooting-already done above), then follow step 6 (installing the new kernel).
Again I really appreciate all the advice.
-HuckFinn
Click to expand...
Click to collapse
I guess that my original idea of using the idiot's guide for everything but step 5 still might work, as long as you substitute any older HC 3.1 specific files with the new ones from jase33's post.Meaning new boot image for old boot image, etc...At some point, someone willcreate a "rootboot"zip for HC3.2 but til then, jase33's way is it.
The Tiamat recovery listed in the Idiot's Guide is still valid and jase33 didn't include a custom recovery in his guide (at least I didn't see it). So I think you can install it earlier or later. I'm not sure it makes a difference, as long as you have it installed so you can flash the new kernel!
I just upgraded from a rooted Viewsonic G tablet to the Xoom WiFi. I have not had a chance to work with it yet. A list of reasons to root would be helpful. Thanks in advance.
.
okantomi said:
I've got to be quick...I have to do some work today, lol, but here goes:
Actually, follow the Idiots Guide regarding the adb, moto drivers setup.
Then follow this http://forum.xda-developers.com/showthread.php?t=1170760
It's got all the right files and steps, and though it's pretty much to the point, it's user friendly enough. It will get you rooted, I'm sure.
While the difference between ROMs and kernels is somewhat over my head, the ROM does contain the kernel (it's sort of an all inclusive package to tell the device how to behave, whereas the kernel manages particular functions, but not others. It's more limited.) Because the Honeycomb source code hasn't been released, the developers are somewhat limited in the ROM-development department, but they have been able to work wonders with kernels. However, the Tiamat 1.1 Rom for HC3.1 was great and the new ROM in development for HC3.2 will be great too, if the Katana kernal for HC3.2 is any indicator.
Click to expand...
Click to collapse
I believe the kernel is the Linux derivative operating system that the Java based android layer runs on top of. Technically ROM means Read Only Memory which is not being used correctly. A ROM really is a factory produced Masked ROM (burned in, fixed) or an EPROM (Erasable Programmable Read Only Memory) as in a chip or integrated circuit.
davidsos said:
I believe the kernel is the Linux derivative operating system that the Java based android layer runs on top of. Technically ROM means Read Only Memory which is not being used correctly. A ROM really is a factory produced Masked ROM (burned in, fixed) or an EPROM (Erasable Programmable Read Only Memory) as in a chip or integrated circuit.
Click to expand...
Click to collapse
Your answer is more technically correct. Thanks.
Random reboots, coming from 3.2 stock OTA
Does anybody else get random reboots in Tiamat Katana coming from 3.2 stock OTA? So far it's been exclusively a sleep-related problem; I haven't seen it reboot during active use. I'm not (over|under)(clocking|volting).
I've tried clearing cache and Dalvik cache. If it matters, I've been using the Overclocked GPU version. I'll try the Standard GPU version of Katana, but that's not a likely fix, since all the problems seem to be sleep-related.
(PS: I've read all the FAQs I could find, but I couldn't find the answer to this one: I'm coming from a Viewsonic G, and I'm used to the ability to nvflash completely back to a working state no matter what. Is there an equivalent method of restoring a Xoom to absolute stock? Thanks!)
Nevermind...I did one more "clear user data" and now it's stable. Tiamat devs, you are gods among men and heroes to all the little children. Thanks!
redhairedscot said:
Nevermind...I did one more "clear user data" and now it's stable. Tiamat devs, you are gods among men and heroes to all the little children. Thanks!
Click to expand...
Click to collapse
And if you set WiFi sleep to NEVER (hardly uses any additional battery) you will not have any more random sleep-related reboots.
CWM after rooting?
I followed the instructions in Post #2 of this thread to root my Xoom (HC 3.2). All seemed to go well. However, I have noticed that when following pingvinen's instructions (linked from Post #2), in http://forum.xda-developers.com/showthread.php?t=1130996, to install Tiamat 2.0.0, the steps include installing CWM before rooting. I can't see that it matters that I install CWM after rooting and before Tiamat installation, but I thought that I had better check. Could somebody please confirm that it doesn't matter whether CWM is installed before or after rooting?
Thank you
Gordon
cwm before root, because you need to flash a new recovery to root and flash a new ROM. I'm a noob, too, and just figuring this out myself, but think I am explaining this right.
one of the many guides I reviewed was by steady Hawkins (now part of team tiamat) over on xoomforums... partly pasted below... I actually rooted using the older files and images he references, then upgraded cwm to 3.2 then flashed tiamat 2.0... probably more steps than necessary, but these were the clearest directions and by going through several rounds of flashing I learned a good bit about the process.
Prerequisites:
1) Copy whatever you want to retain, your device will wipe when it unlocks 2) You must have SDK/ADB set up, for instructions please see- Setting up ADB on Windows 7 64 bit (and other Windows platforms) 3) Open SDK and copy all of the files inside of tools folder and paste them inside of platform-tools folder. Vice versa will work as well. If it asks you if you want to replace files select no. The folder you paste these files into will be the folder you will run ADB commands from. 4) Download the files from the link below. Place recovery.img in the file you will run commands from in ADB. ***Wifi-Only Users***- manually put the System and bootloader zips files onto a sdcard card and insert card into xoom. ***3G/4G Users***- manually put the System, bootloader, and 3G fix zips onto a sdcard and insert card into xoom.
Downloads:
Recovery- http://db.tt/GXNxZkF System- 3.1 System - Downloads - Android Forum Bootloader- Bootloader Patch - Downloads - Android Forum 3G Fix- 3G Fix for 3.1 - Downloads - Android Forum
Notes:
In the following two sections you will see red text. This text represents the command that needs to be entered in ADB/Command Prompt. After each command press enter and wait for your computer to push the info to your Xoom. When you see the next command line come up you are ok to enter the next command. You can copy and paste the commands if you would like.
1) To start the process place your Xoom into USB debugging mode. This is done by going to settings, applications, development, and checking the box next to USB Debugging. 2) Plug your Xoom into your computer, open your command prompt (with the path set to the correct folder) and type adb devices 3) If you get a string of numbers your good to proceed, if not refer back to Setting up ADB on Windows 7 64 bit (and other Windows platforms) to see where you went wrong.
Unlocking:
adb reboot bootloader Xoom will reboot into a screen with text on the upper left corner. While you are on this screen enter the following fastboot oem unlock A bunch of text will appear and you will need to use the down volume rocker to select yes, followed by volume up to confirm Xoom will then wipe, reboot, and your back up and running. At this point you will need to go back and re-enable USB debugging
Flash Recovery Img:
Make sure Xoom is connected to computer. Test connection by running adb devices if you get the string of numbers proceed.
Rename the Recovery img you downloaded ~~~> recovery.img
adb reboot bootloader Xoom will reboot into a screen with text on the upper left corner. While you are on this screen enter the following fastboot flash recovery recovery.img Wait for it to finish, then read the below note before you enter the next command!!!!!!!!! fastboot reboot ***As soon as you enter the "fastboot reboot" command in the previous step, your device will reboot. You have to boot into recovery right away or your Xoom will reflash the stock recovery over the custom recovery you just flashed. Follow these next steps very carefully-
a. When you see the Motorola logo appear, wait approximately 3 seconds. b. Tap the Volume Down button. You should see the words "Android Recovery" appear at the top of the screen. Now tap the Volume Up button to boot into recovery. c. If when attempting to boot into recovery it says 'Starting Fastboot protocol support' then you hit Volume Down too soon. Hold Vol UP + Power to reboot and try again.
Root Time:
***For the following use the volume rocker to move the selector up and down, use the power button to select***
1)Select wipe data/factory reset and confirm 2)Select install zip from SD and confirm 3)Select the system file and confirm After it loads select install zip from SD again and confirm 4)Select the bootloader file and confirm
***3G USERS ONLY- Select 3G fix and confirm***
5)Select Reboot and confirm
At this point Xoom will reboot. Please note the first boot will take a while. After it boots up you will be rooted and you should have SDsupport!
Root info:
To ensure that you are rooted download Terminal Emulator from the market (its free). Open it and type su followed by pressing enter. On the next line you should see #. If you do your dialed in.
To view your SDcard use a file manager program such as Root Explorer. Your sdcard will be located in /sdcard/external.
Big thanks to Bigrushdog for the imgs!!!!!
kosenn said:
I just upgraded from a rooted Viewsonic G tablet to the Xoom WiFi. I have not had a chance to work with it yet. A list of reasons to root would be helpful. Thanks in advance.
.
Click to expand...
Click to collapse
Had my 3g zoom for 4+ months before deciding to root. The advantages I've seen in a few short days rooted:
better performance, faster booting, smoother webpages
full SD card use (write access to go along with read in stock 3.2)
ability to fully and truly back up the device
a very resposive developer community
a very knowledgeable and helpful user community (though they'll help you even stock)
a growing understanding of how this great device works
what I'm not sure of is how much effort and attention it will take to keep up with updates from the dev community, and whether tinkering with this thing will become addictive and end up consuming as much time as my original reasons/uses for buying it in the first place
Thank you for the reply. I thought the thread had died
You say:
cwm before root, because you need to flash a new recovery to root and flash a new ROM. I'm a noob, too, and just figuring this out myself, but think I am explaining this right.
I tried to install CWM (flash with fastboot) on a rooted stock US 3.2 WiFi Xoom. I am not clear why starting with a rooted device would make any difference for flashing a new recovery, before flashing a new ROM. Can you explain further? Nevertheless, I haven't managed to flash a fully functioning CWM. It works but with error messages, as indicated in my post at http://forum.xda-developers.com/showthread.php?t=1130996&page=4.
Maybe I need to go back and unroot.
Thank you
Gordon
1st, a disclaimer that I'm not much more experienced than you (if at all). Take what I offer knowing that.
I actually experienced an identical problem. Like you, I was working from several "guides" at once and I think the issue resultedbfrom mixing instructions for one cwm version with an earlier (or later) version. I THINK the version you have is the same as the one referenced in the guide I pasted. If you'll note his directions, he suggested renaming the recovery document to "recovery.img" before flashing it. When I went back and did that, it worked for me... then I was able to flash the updated cwm 3.2.0.0 with no errors.... then tiamat 2.0
I have no idea, though, whether there are ramifications to being rooted without a error-free recovery.
Thanks again for this ... at least someone has been through the same problems as me!
The version of CWM that I am trying to flash is "recovery-Tiamat-R4c-100611-1150-cwm.img", which is what is shown in the fastboot line in http://forum.xda-developers.com/showthread.php?t=1130996. However, I am not seeing any reference to renaming to recovery.img. Are we looking at different threads?
If necessary, I will go back to stock 3.0.1 and un-root, but I would like to avoid the stress, if possible
Thank you
Gordon
Having been a member on this forum for years I must admit it has been incredible the wealth of information I've gained from it. I've had all sorts of phones/pdas and I'ved used this site to help me get the most out of it and to help m "tame" the device and stop rubbish from the vendors being installed on there when I don't want it.
A couple of years ago I got an HTC Desire. Great phone although limited memory. I was happy with it. Didn't bother to root it or anything. I then got a Motorola Xoom. Didn't bother rooting that either. I got myself an HTC Sensation now. I decided one day that I was going to unlock/root the thing to see if I could do it.
Somehow, I think I managed it. I haven't really noticed a difference but then I haven't put a custom rom on it. On all my old Windows mobiles I always had a custom rom.
Now, going back to the Xoom. It's an original Xoom. I bought it in May 2011. It is running Android 3.2 after Motorola sent out an update. All is good.
However, I would like to have ICS on it. This is where my problems begin. I've tried following so many different how-to's on how to do this unyet none so far have worked. So, either I'm completely stupid or, the guides are not easy to follow or the process (that is always touted as easy) is not very easy.
So I am asking for help. Here is what I understand are the steps that I need to acheive.
1. I need to unlock the device
2. I need to install a recovery image
3. I need to install ICS
Questions: I *think* I have done 1. How do I check? After what I believe is a convoluted process, I have installed the Android SDK. I have the drivers for the device on the [Windows 7 64bit] PC and I can see it listed when I type adb devices.
Why do I need to unlock the device? What does the act of unlocking it do? When I followed this:
http://forum.xda-developers.com/showthread.php?t=1242241
I got to step 3. I typed in the first command:
adb reboot bootloader
After much faffing around I found out from another site I needed USB Debugging enabled. Nobody told me this. No, it isn't obvious that I need this.
The boot screen appeared and gave a message at the top and then I typed in:
fastboot oem unlock
I followed the instructions on the screen. I unlocked the device. It took a while. When it rebooted I found I had to set the device back up again as if it was the first time I'd used it. "Great!" I am thinking, I've lost everything. Thankfully I backed up what I wanted so I am not bothered. Slowly the apps appeared to come back after it synched with Google. I'm assuming stuff gets backed up somewhere.
I typed:
fastboot reboot
It rebooted.I typed:
adb reboot bootloader
It rebooted into the bootloader. Now here is where things started to go off track. I typed the next command:
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
I get this:
unknown partition 'recovery-Tiamat-R4c-100611-1150-cwm.img'
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img'
So what now?
I cannot believe the process to unlock and flash a rom is so unbelievably convoluted. I've read dozens of walkthroughs, how-to's and forums and each one seems to be very similar unyet there is always something different on there to what I get on my screen or something doesn't happen quite the same way.
Here is what I am trying to acheive:
I have Android 3.2 on my Xoom and I would like it to be ICS.
We'll assume that I am completely stupid and need serious handholding to get to ICS. Is there anyone that can help with these seemingly simple steps?
One thing I keep reading is about the recovery image file. Is this related to Cyanogenmod? I am assuming as it is called a recovery image file it helps you get back when things go wrong.
Thanks and much love to the person that takes up the reigns and helps me out here.
Hi!
If you are rooted already that's pretty easy. But if not, try using LordAIOTool to root (yea it's mine and I think it's worth a try). After you are rooted flash a new recovery - download from development section - after, rename the recovery to recovery.img and then use the following commands on adb, fastboot and this recovery folder (simultaneously)
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
Then after keep clicking the vol- after 2s of your tablet appears on Motorola logo. Then keep cycling until appears Android Recovery then press vol+
You are on recovery now, just select install zip from sdcard...
Good luck
Sent from my MZ601 using XDA Premium HD app
If you wanted your xoom rom'd, then you could try wesamothman's guide: http://forum.xda-developers.com/showthread.php?t=1717402 It is great for beginners and the experienced alike.
This is for the wifi only xoom MZ604. There is another guide by him i believe for the MZ602
Do I need to flash a new rom to get root on my MZ604? What is the easiest way to just root the stock 4.0.4 firmware? I have no desire for a different rom. I just want to root it.
Hey there.
If you don't want to flash a custom ROM and only want to root it, try this:
1) unlock your bootloader.
2) thru ADB, flash a recovery image.
3) thru Recovery, flash superuser flashable zip: http://www.4shared.com/zip/g3yzbrIa/...?cau2=403tNull
I ran the first couple of steps to unlocking. That is as far as I have got. As I said, I have tried so many of these walkthroughs and not one of them has all the steps. They all make an assumption somewhere along the line.
For example: xxlordxx replied with:
"If you are rooted already that's pretty easy".
I'm not, that is the problem.
Again:
1. adb reboot bootloader
2. fastboot flash recovery recovery.img <---- This didn't work and gave me the error I pointed out earlier and that is where it all stopped. Noone explains what to do when it goes wrong.
Anything passed this stage is irrelevant until I can sort out the problem above.
yosterwp, you mentioned wesamothmans guide. I will try that one as it looks a bit more "dummies guide-like" and it is for my exact device which is the MZ604 wifi only. I hadn't seen this one as it was only posted a couple of days ago
Just so I know, can someone anser these questions? I'm sure they're very simple but I don't know.
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
2. Is unlocking the same as setting s-off?
3. If not, what is the difference?
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
5. What is Cyanogenmod and do I need it or is this another custom rom?
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Thanks for everything so far. I will let you know how I get on with wesamothmans guide.
Hi Snert.
Answering your queries:
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
yes.
2. Is unlocking the same as setting s-off?
I don't really understand what you mean by s-off... but unlocking is this: you unlock the bootloader that is considered as a security checkpoint of your device. It is locked by default. when it is unlocked, you can then install recovery image passing thru this checkpoint (allowed). without bootloader being unlocked, no rooting can be done. this is the very first step.
3. If not, what is the difference?
same as above
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
Recovery explanation details is here: http://www.androidcentral.com/what-recovery-android-z
5. What is Cyanogenmod and do I need it or is this another custom rom?
It is a different ROM based Firmware...
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Go for the best custom ROM for your MZ604. It is from Team EOS.
Hope I answered your questions
wesamothman said:
Hi Snert.
Answering your queries:
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
yes.
2. Is unlocking the same as setting s-off?
I don't really understand what you mean by s-off... but unlocking is this: you unlock the bootloader that is considered as a security checkpoint of your device. It is locked by default. when it is unlocked, you can then install recovery image passing thru this checkpoint (allowed). without bootloader being unlocked, no rooting can be done. this is the very first step.
3. If not, what is the difference?
same as above
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
Recovery explanation details is here: http://www.androidcentral.com/what-recovery-android-z
5. What is Cyanogenmod and do I need it or is this another custom rom?
It is a different ROM based Firmware...
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Go for the best custom ROM for your MZ604. It is from Team EOS.
Hope I answered your questions
Click to expand...
Click to collapse
You did
Much love!
I am new here so please bear with me.
I have a "rooted" Nexus S i9020. When I bought it it had Android 4.0.4 installed. Recently I have been receiving a message telling me that a system update to Android 4.1 is ready to be installed. I have tried accepting the update, but halfway through it stalls and all I see is a triangle with an exclamation mark in it. The phone will then not respond and requires removal and refitting of the battery to restart it. Luckily, it has returned to working order with 4.0.4 still installed.
Is the phone not accepting the update because it is rooted?
Can I get the OTA update without erasing all data and settings?
I have an app. called Superuser v.3.1.3 on the phone. It has a box to tick marked "temp unroot" and another "OTA survival".
Would either of these tools be any use?
I have tried to understand all the information given on the forum posts but there is just too much to take in.
Can someone explain what I have to do to get the phone updated without "bricking" it?
When I enter Bootloader mode it says:
FIRST BOOT MODE
PRODUCTNAME HERRING
HW VERSION REV 11
BOOTLOADER VERSION I9020 XXKL1
BASEBAND VERSION I9020 XXKI1
SER.NO etc.
LOCK STATE LOCKED
Is this information helpful? I have read about "clockwork mods" and "Roms", but I don't know what you mean.
Thank you in advance.
Clockworkmod replaces your stock recovery and then giving you options to flash ROMs etc. If you want to learn more... start with the sticky threads in development.
Your phone is rooted so if you want to get the update you need to temp. Unroot using the superuser app like you mentioned. Try to get the update. Please report back if it helped
Sent from my Nexus S using xda app-developers app
so far no brick...
kwibis said:
Clockworkmod replaces your stock recovery and then giving you options to flash ROMs etc. If you want to learn more... start with the sticky threads in development.
Your phone is rooted so if you want to get the update you need to temp. Unroot using the superuser app like you mentioned. Try to get the update. Please report back if it helped
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
I ticked the "temp unroot" box and tried installing the update again. Same result. Install stops with exclamation mark triangle and grinning android. Restart by taking out the battery. Ok, I still have a phone. Running Android 4.0.4, but now there is no upgrade available and I will have to wait until they get around to offering it again before I can experiment further. If I check for updates, it tells me that I am up to date.
I wish that there was more information. I mean, what's the point of a triangle with an exclamation mark? Why can't it tell me what the problem is? Then I might be able to fix it.
Thank you for taking the trouble to reply.
PS. This device cost me £150, I really don't want to break it, and I would like to be in control of it. If I brick it, then I suppose I will sigh, then go down to Carphone Warehouse and sign a contract for a locked, dumbed down, boring, toe-the-line Samsung SIII. But I would much rather be the master of a rogue, rooted, rough and ready-for-anything Nexus S.
monkey shoulder said:
I ticked the "temp unroot" box and tried installing the update again. Same result. Install stops with exclamation mark triangle and grinning android. Restart by taking out the battery. Ok, I still have a phone. Running Android 4.0.4, but now there is no upgrade available and I will have to wait until they get around to offering it again before I can experiment further. If I check for updates, it tells me that I am up to date.
I wish that there was more information. I mean, what's the point of a triangle with an exclamation mark? Why can't it tell me what the problem is? Then I might be able to fix it.
Thank you for taking the trouble to reply.
PS. This device cost me £150, I really don't want to break it, and I would like to be in control of it. If I brick it, then I suppose I will sigh, then go down to Carphone Warehouse and sign a contract for a locked, dumbed down, boring, toe-the-line Samsung SIII. But I would much rather be the master of a rogue, rooted, rough and ready-for-anything Nexus S.
Click to expand...
Click to collapse
The triangle with an exclamation mark is most likely your stock recovery, that somehow got restored. Re-flash CWM or TWRP, then try to apply the OTA again.
Can't you be rooted and not have cwm?
Sent from my Nexus S using xda app-developers app
Install rom manager... the cwm 6.0.1.0 applies the ota.
Make sure you tick ota survival in superuser and after the ota cwm will ask you is you want to keep the stock recovery for next boot or keep the cwm.
Then it asks you to fix root rightz..select fix . And now you got the 4.1.1 rooted by ota
Sent from my Nexus S using xda app-developers app
monkey shoulder said:
I am new here so please bear with me.
I have a "rooted" Nexus S i9020. When I bought it it had Android 4.0.4 installed. Recently I have been receiving a message telling me that a system update to Android 4.1 is ready to be installed. I have tried accepting the update, but halfway through it stalls and all I see is a triangle with an exclamation mark in it. The phone will then not respond and requires removal and refitting of the battery to restart it. Luckily, it has returned to working order with 4.0.4 still installed.
Is the phone not accepting the update because it is rooted?
Can I get the OTA update without erasing all data and settings?
I have an app. called Superuser v.3.1.3 on the phone. It has a box to tick marked "temp unroot" and another "OTA survival".
Would either of these tools be any use?
I have tried to understand all the information given on the forum posts but there is just too much to take in.
Can someone explain what I have to do to get the phone updated without "bricking" it?
When I enter Bootloader mode it says:
FIRST BOOT MODE
PRODUCTNAME HERRING
HW VERSION REV 11
BOOTLOADER VERSION I9020 XXKL1
BASEBAND VERSION I9020 XXKI1
SER.NO etc.
LOCK STATE LOCKED
Is this information helpful? I have read about "clockwork mods" and "Roms", but I don't know what you mean.
Thank you in advance.
Click to expand...
Click to collapse
Unlock your bootloader first (will erase SD card) How to is in these.
http://forum.xda-developers.com/showthread.php?t=1007782
http://forum.xda-developers.com/showthread.php?t=1623481
after that do this
http://forum.xda-developers.com/showthread.php?t=1785672
this is hard...
thank you all, i am working on it, but i still don't understand.
Jayjay: I downloaded the SDK and followed the instructions in the guide you suggested, but my PC does not recognize the Android device.
When I try to browse for the driver software I get a Hardware Update Wizard, and then I'm up to my ass in alligators. "Choose Hardware Type" it says but none of them are accepted. There is no choice called "Android Bootloader Interface". There are 2 folders, one for i386 and one for amd64, my PC is athlon64X2 so I look in there, and there are 3 "dll"s but nothing with that name.
Anyway I thought my phone was already rooted, why do I have to root it again? Must it be done in a certain way so that you can be sure that it was done properly?
I will keep trying, but this is bloody hard work.
are you sure?
raducux said:
Install rom manager... the cwm 6.0.1.0 applies the ota.
Make sure you tick ota survival in superuser and after the ota cwm will ask you is you want to keep the stock recovery for next boot or keep the cwm.
Then it asks you to fix root rightz..select fix . And now you got the 4.1.1 rooted by ota
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
I have read this on another forum:
Please note that you cannot flash clockwork on Samsung Phones using ADB, or ROM Manager (you'll hard brick the device). If there is a version of clockwork (specific to that particular Samsung device) it must be flashed using Odin.
So what do I believe?
monkey shoulder said:
Jayjay: I downloaded the SDK and followed the instructions in the guide you suggested, but my PC does not recognize the Android device.
When I try to browse for the driver software I get a Hardware Update Wizard, and then I'm up to my ass in alligators. "Choose Hardware Type" it says but none of them are accepted. There is no choice called "Android Bootloader Interface". There are 2 folders, one for i386 and one for amd64, my PC is athlon64X2 so I look in there, and there are 3 "dll"s but nothing with that name.
Anyway I thought my phone was already rooted, why do I have to root it again? Must it be done in a certain way so that you can be sure that it was done properly?
I will keep trying, but this is bloody hard work.
Click to expand...
Click to collapse
So you didn't get through part 1 in this? http://forum.xda-developers.com/showthread.php?t=895545
This can help you with the drivers. Install and run.
http://junefabrics.com/android/download.php
I heard people using this, I've never tried it http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/ or http://forum.xda-developers.com/showthread.php?p=23573589
You are rooted but your bootloader is locked so you have to unlock it to reflash a rom, including 4.1.1. You can't do the OTA in the current state of your phone. http://forum.xda-developers.com/showpost.php?p=29519097&postcount=11
More info http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Hope this helps.
monkey shoulder said:
I have read this on another forum:
Please note that you cannot flash clockwork on Samsung Phones using ADB, or ROM Manager (you'll hard brick the device). If there is a version of clockwork (specific to that particular Samsung device) it must be flashed using Odin.
So what do I believe?
Click to expand...
Click to collapse
clockworkmod website. Pick nexus s http://www.clockworkmod.com/rommanager/
Getting tired...
jayjay3333 said:
So you didn't get through part 1 in this? http://forum.xda-developers.com/showthread.php?t=895545
This can help you with the drivers. Install and run.
http://junefabrics.com/android/download.php
I heard people using this, I've never tried it http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/ or http://forum.xda-developers.com/showthread.php?p=23573589
You are rooted but your bootloader is locked so you have to unlock it to reflash a rom, including 4.1.1. You can't do the OTA in the current state of your phone. http://forum.xda-developers.com/showpost.php?p=29519097&postcount=11
More info http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Hope this helps.
clockworkmod website. Pick nexus s http://www.clockworkmod.com/rommanager/
Click to expand...
Click to collapse
When I plug the phone into the PC a "New Hardware Wizard" starts. I guided it to the "\\android-sdk\extras\google\usbdriver" folder and it "cannot install this hardware because it cannot find any software". The folder "USB driver" has a file called "android_winusb.inf", which appears to contain information specifically relating to the Nexus S, but the sub folders contain .dlls which are not recognized by the wizard, and there is no file called "Android Bootloader Interface" anywhere.
So I tried again. This time I let the wizard search for software, and it found an Acer USB driver which it installed. But when I connect the phone it is still not recognised, and the wizard wants to run again.
Ok this time I try the PDA net software that JayJay recommends. I'm not sure what it's supposed to do, but when I try to connect my phone the PC says "Error 2DAnet driver is either not installed or must be reset, try to reboot you computer", which I do, with no improvement. Oh and a pop up from the systray sez "Broadband error 13"
I am assuming that when the phone is "recognized", I will have full access to the file system. At the moment, when I connect, it calls the phone " usb mass storage device, drive J " and is treating it as if it is a memory stick. I have successfully backed up photos, music and downloaded files to the PC. One of the things I have been trying to do is get at the wallpaper photo which I have read is in "data\data\com.android.settings\files\wallpaper.jpg" but I cannot find such a folder on my phone, so I assume it must be one of those things you get to see when you've got this "android debug bridge " thing.
I am getting tired now I have been at this for hours.
Tomorrow I will try the "ROM Manager"
Goodnight.
Progress
So I download the ROM Manager. On the first Run the screen goes black and stays black. A great start. I reboot and get Rom manager. It is trying to sell me google chrome. No thank you I want Android 4.1.
Rom manager tells me that my ROM "is not set up to receive over the air updates - please contact ROM developer." Who might that be? Is it called Herring? I have no idea who supplied the 4.0.4 ROM for this device. I try to backup the current ROM and Rom manager wants to reflash the ClockworkMod recovery.
Now I have discovered that I have CWM installed already. (It must have been there for the previous owner to have installed ICS.) I have CWM 5.0.2.0.
Still, best to have the latest version...and so I flash the CWM.
This fails 3 times and I have to reboot each time. I then try updating Superuser to the latest version. This also fails and hangs the phone, just a screen saying "downloading manifest". No sign of progress, no status bar, no rotating thingy. Eventually I reboot and try again. ( I am getting confident about this reboot game, I've had to do it lot's of times and so far it hasn't let me down, and brings me back to a working phone.)
When Superuser has finally settled down to v3.1.3, su binary v3.1.1 I have another shot at flashing CWM from ROM manager. Yeah! This time it sticks!
I now have CWM 6.0.1.0
So I back up my ROM...this seems ok apart from a message "no sd-ext found"... but I don't know what that means so I ignore it.
Now I try applying the 4.1.1 update. All looks good for a while with a little android with a dodecahedran or something in its belly. Then..clunk!
The little android is on it's back with it's legs in the air. There is a report that I send to rommanager. It is long, (would you like me to Post it?)
basically it says:
" can't open /dev/tty0: no such file or directory"
"unable to get recovery.fstab info for datadata fstab generation"
"failed to verify whole file signature"
"failed to open /sys/class/android-usb/android0/state: no such file or directory" - this over and over again...
Now I think I have a BIG problem.
I get the feeling that something is corrupted and there are bits missng from my file structure. This would explain why I could not find a "data/data" directory and a whole lot else.
Actually beginning to enjoy this, I may end up with £150 paperweight, but I am learning a lot about code. Like when I got the SDK ADB installed and typed help then found that I couldn't send the output on the Command Line to the printer so I had to look it up on Wikipedia...
I am still learning. I think I need to know where to get the true Google Android 4.1.1 from if I cant get it over the air.
I have read about a thing called Nexus Root Toolkit by a chap called Wug fresh or something, I am not unfamiliar with DOS but my command line skills are a bit rusty.
I started with Algol 60 you know.
Goodnight
Close but no cigar...
OK. I have backed up my rom, using Titanium Backup.
I have "unlocked" my bootloader using the downloaded Android SDK ADB fastboot.exe ( It's in "platform tools" now, not "tools")
I have CWM 6.0.1.0 , Superuser 3.1.3 with OTA survival ticked.
Now all I have to do is wait until the OTA upgrade is offered again. ( It seems to come round randomly, every few days.)
Ssh! wait.. Yes! After leaving the phone overnight, the upgrade was waiting for me in the morning. I tap install..
...and fail again.!
This time its:
E: failed to verify whole file signature
E: error in /cache/9ZGgDXDi.zip (status 7)
installation aborted.
Why do you guys make it sound so easy?
I clear my cache ( if there is an error in it, it makes sense to clear it.)
I'll try again tomorrow.
monkey shoulder said:
OK. I have backed up my rom, using Titanium Backup.
I have "unlocked" my bootloader using the downloaded Android SDK ADB fastboot.exe ( It's in "platform tools" now, not "tools")
I have CWM 6.0.1.0 , Superuser 3.1.3 with OTA survival ticked.
Now all I have to do is wait until the OTA upgrade is offered again. ( It seems to come round randomly, every few days.)
Ssh! wait.. Yes! After leaving the phone overnight, the upgrade was waiting for me in the morning. I tap install..
...and fail again.!
This time its:
E: failed to verify whole file signature
E: error in /cache/9ZGgDXDi.zip (status 7)
installation aborted.
Why do you guys make it sound so easy?
I clear my cache ( if there is an error in it, it makes sense to clear it.)
I'll try again tomorrow.
Click to expand...
Click to collapse
Ok now just get the proper factory image. You are a Nexus S i9020 just check if you are a T or an A (look under the battery). Flash Android 4.1.1 (JRO03E). Follow part 1 of this guide http://forum.xda-developers.com/showthread.php?t=1785672
Then flash clockwork and super su
Stock, rooted, profit!
stick with it...
monkey shoulder said:
OK. I have backed up my rom, using Titanium Backup.
I have "unlocked" my bootloader using the downloaded Android SDK ADB fastboot.exe ( It's in "platform tools" now, not "tools")
I have CWM 6.0.1.0 , Superuser 3.1.3 with OTA survival ticked.
Now all I have to do is wait until the OTA upgrade is offered again. ( It seems to come round randomly, every few days.)
Ssh! wait.. Yes! After leaving the phone overnight, the upgrade was waiting for me in the morning. I tap install..
...and fail again.!
This time its:
E: failed to verify whole file signature
E: error in /cache/9ZGgDXDi.zip (status 7)
installation aborted.
Why do you guys make it sound so easy?
I clear my cache ( if there is an error in it, it makes sense to clear it.)
I'll try again tomorrow.
Click to expand...
Click to collapse
Its a bit confusing to begin with mate, but read and re-read the many tutorials and guides on here, take it slowly and step by step and youll get there in the end.
Youll be flashing custom ROMs before you know it! (take your time and always backup)
Is worth it. :good:
S
It is good that in the process you learnt lot of things. Now you have fastboot working and you know how use fastboot.
Now that the OTA is giving errors, the best way is to flash the Jelly Bean factory image which is available from Google. As per suggestions from
jayjay3333 said:
Ok now just get the proper factory image. You are a Nexus S i9020 just check if you are a T or an A (look under the battery). Flash Android 4.1.1 (JRO03E). Follow part 1 of this guide http://forum.xda-developers.com/showthread.php?t=1785672
Then flash clockwork and super su
Stock, rooted, profit!
Click to expand...
Click to collapse
Go to the link to download the image files first, then flash the 3 files using the fastboot commands provided. The overall process of flashing the factory images does not take more than 5 mins.
Best of luck.
nearly there...
jayjay3333 said:
Ok now just get the proper factory image. You are a Nexus S i9020 just check if you are a T or an A (look under the battery). Flash Android 4.1.1 (JRO03E). Follow part 1 of this guide http://forum.xda-developers.com/showthread.php?t=1785672
Then flash clockwork and super su
Stock, rooted, profit!
Click to expand...
Click to collapse
Ok I downloaded the jro03e file it is 191Mb
The download is a .tar file not a tar.gz It is called soju_jro03e_factory_c9f5a67d.tar. It is196,458 kb
The instructions say I should 'extract' it, using 7zip, which gives me a file with the same name but no extension! Windows identifies it as a ".file". It is now 207,410 kb.
The instructions say there is a folder inside which I should extract. No such thing is visible.
The next part of the instructions says I should modify the file names before running. Does that mean:
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju_jro03e_factory_c9f5a67d.tar
Is that right? Shouldn't all those hyphens be underscores?
Is that xxkl1 or xxki1 the same or different? ( looks like a typo).
Does only the last bit change?
Ready when you are!
oops silly me...
Well it looks like I don't understand 7Zip very clearly.
After a bit of fiddling about I "extracted" the .tar file, then "extracted" the resulting file to get a folder with a bootloader image, a radio image and an image-soju-jro03e.zip
I tried to follow the XDA instructions given here http://forum.xda-developers.com/showthread.php?t=1785672
but it seems I don't understand how to use ADB fastboot either, because when I entered the commands all I got was a list of options, a sort of helpfile for the fastboot command.
I am just not comfortable with the command line, you make one mistake and you've got to enter it all again.
Anyway I decided to try the "Nexus Root Toolkit" http://www.wugfresh.com/dev/nexus-root-toolkit/
After ensuring that my drivers were OK, I pointed the toolkit at the files and executed them individually. ( There is a "flash-all.sh" , but I don't understand how to use that. )
first of all I flashed the bootloader... Success! I now have bootloader crespo i9020xxlc2.
I didn't bother with the radio, I already have radio-crespo-i9020xxki1.
So I try to flash the jro03e.zip... Damn! The toolkit cannot find my device! Funny, it was perfectly happy before the bootloader flash...maybe that has changed something. I start again, reboot everything, check drivers... yes all ok. This time the toolkit is happy and offers to install the .zip, I include a full nandroid backup and drag and drop the image-soju-jro03e.zip to the install/flash.zip box.
TWRP v2.2.0 does it's thing and after a lot of stuff happens on the phone screen I get a menu, from which I access a report that basically says: "Error flashing zip". My heart sinks...
Other attempts with different settings result in the same:
"signature verification failed"
"no MD5 file found"... etc... etc...
So I reboot again and am relieved to find that I still have a phone.But it is still 4.0.4.
Ah! but now it has the image.zip on the SD! Progress! My heart soars with new hope!
This time I use ROM Manager to install the .zip from SD... But no such luck, "installation aborted", the little green android is flat on its back again.
Rom Manager generated a recovery log. (would you like me to post it?) Basically it says:
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/mtdblock4 on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
Installing update...
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/!ReadyToFlash/image-soju-jro03e.zip")
Have you any idea what that all means?
Will I ever get JB 4.1 on this phone?
Its beginning to look like there is something fundemental missing.
Please help!
S.
its gone quiet...
This thread doesnt seem to be getting attention anymore so I shall start a new one.
Is that ok? Its a new question "what does this recovery log tell me?", but it is still the same problem. The trouble is there are too many questions and it is very difficult to know what to ask.
I am still trying to get Android 4.1 on my phone. I have read the various instructions and tried to follow them but they did not work in the way I expected. Part of the problem is that I do not understand what I am doing. I don't understand the tools I am using.
I think it would help a great deal to see the file structure on my phone.
Is there a program that can look at that like windows explorer? Then I might be able to see what I am doing. At the moment I have no idea what is on my "SD card". The Nexus S doesnt actually have one of course, but I understand that it has 16Gb of storage that work like an SD card.
Now In the course of this project, I have "Backed up" with Rom Manager, but I don't know where that backup is, or what it is called. I did a "Nandroid backup" with the Nexus Root Toolkit but I have no idea where that is (is it on PC, or on the phone somewhere?) or what it is called. I assume it will be found automatically by the software when it needs to restore it. I have not backed up with "Titanium Backup" beause I am not sure how to do it. When I select "Backup/Restore" it displays a long list of files, some in red some in green, which say they are not backed up yet. Which ones do I select? All of them? I have no idea.There are so many options in the menus that I am terrified of Titanium, and don't know where to start, and it is going to take days to read the helpfiles. Is Titanium saying they are not backed up because it didn't back them up, or because it can't recognise the backups that were made with Rom Manager? If I backup everything with Titanium, is it going to make backups of the backups that another program made?
I'd like to be sure that I have just one good copy of the backup, that I havent filled my memory with useless junk.
S
Okay so, I love my Infuse but getting really tired of not being able to download anything off the play store. Just tired of it's rather less than great performance right now as well. It's is running 2.3.6 GB and want to get this thing up to ICS if possible. Just something running 4.0 so I can use my phone for what I need too. It is not rooted, no cyanogenMod, NOTHING. As the title says, I'm a full on noob here and I apologize if all this is covered in other threads, however I have just gotten to the point where I have found myself even more lost than where I started on what I needed to do/get. If someone can, I will literally need this spelled out to me (no pun intended), in order of the steps I need to take with everything. I'm getting tired of confusing myself even more from all the different stuff I have seen all over the place and I know without some serious guidance, I will just brick my phone. Thanks for any help! :laugh:
I understand this community can be a bit unorganized and confusing so I'll give you my process for rooting and installing custom firmware (there are other ways, but this works for my AT&T Infuse 4G SGH-i997).
First of all, no one uses ICS on the Infuse. There is a ROM, but it's underdeveloped because JB came out so quick. You will need to flash it to get to higher operating systems, but it is by no means a daily driver. Even JB is a little buggy compared to KitKat on the Infuse these days.
The first thing you want to do is root your phone and get a custom recovery.
There are more than a few options for rooting, but I prefer using ODIN (as I understand it, this is the tool Samsung uses to restore soft bricked phones). So this is a good thing to know how to do, in case you ever do soft brick your phone, you'll know exactly what to do.
Read the ODIN instructions in full as I will only briefly explain.
You're going to have to install Samsung drivers.
You'll be using UCLB3_Unbrick_root_1.1.zip. If you used UCLB3_Unbrick_1.1.zip it would just get you back to stock GB with no root added.
To put your phone into download mode, first turn off your phone. Plug a usb cable into your computer. Then with the phone off, hold down both volume buttons and plug the usb cable into your phone. A warning will come up and you push volume up to accept, realizing that you can easily soft brick your phone if you loose power or unplug during a download.
Once downloading is done, the phone will reboot and you'll be disappointed to see that nothing has changed. Except one small thing, you are now rooted and you should have an application called SuperUser that will allow you to do nifty and also dangerous things.
Now follow this step in the ODIN instructions to add the custom recovery (CWM = Clock Work Mod):
The version with root works exactly like the above version, but adds root. To add CWM recovery to the rooted version, download a custom Gingerbread kernel from HERE or HERE and flash the zImage using SGS Kernel Flasher (found in the Play Store) on the phone. If you go this route for root and CWM, your Custom Binary Download counter will not show any custom binary activity.
Click to expand...
Click to collapse
If you follow the link in the second "HERE," you'll get the kernel I prefer since it was most recently updated. Scroll down the downloads section and grab "2013.04.30-CWM-Synthesis-1.2Ghz.zip." (1.2Ghz is stock for our processor, anything higher will be overclocked which I don't recommend).
Extract that and grab the zImage file in the update folder. You're going to copy this to your phone in a second.
But first you need SGS Kernal Flasher, you can get it off the playstore, but I despise having to log in to an OS I'm going to write over in less than a minute so I download the APK from here. Hopefully you know how to install APKs from your SD card and that you'll have to check install from unknown sources.
Now flash the zImage using SGS Kernel Flasher. Your phone will reboot and hang on the Samsung logo and a creepy voice is going to tell you about how she's partitioning your phone and installing Voodoo lag fix. This is normal. Eventually your phone will reboot back into GB and you'll be ready to flash any ROM of your choice by rebooting into recovery.
You reboot into recovery by holding the volume up and volume down button while powering on the phone. This is different than download mode and will take you do a new screen that you control with the volume keys.
You'll be using this to put new software on your phone.
Now you can bassically follow the instructions for getting to CyanogenMod 11 (Kit Kat) from GB.
The first bullet is what I just explained in detail.
Note that I didn't include the links in these instructions, just follow the link above to get to the original post.
Obtain CWM, this can be done using Jscotts Odin back to stock (Follow instructions and use SGS kernal flasher to obtain CWM)
Run Qksters IMEI backup script here
Make certain you are on ICS, this can be done by flashing Entropy's CM9
It is recommended now that you remove your SD Card
CWM: Wipe Cache / Factory Reset
Install ROM: Scroll down for downloads sectoion
... The package will start to install..
... Phone will reboot into the install screen again...
... Continue to install [Automatically] If not manually flash again
... Phone will reboot again and be at the recovery screen...
Install Gapps: Here - Working swipe!
CWM: Wipe Cache Partition
CWM: Advanced/Wipe Dalvik Cache
Reboot
Click to expand...
Click to collapse
To be clear, when you flash a ROM, it won't be like flashing the zImage (that was just to get custom recovery). To flash the CM9 ROM or Qksters IMEI backup script for example, you leave the rom in the .zip file and simply put it on your SD card. Once in the recovery screen, you select "Install Update from ZIP" and navigate to the particular ROM you wish to install.
Also after updating to a higher version of Android, your phone will sometimes hang on the install screen for a long time. If it does for more than five minutes, it's safe to pull the battery and try flashing again (and sometimes necessary).
After flashing Entropy's CM9, you will be on ICS, you can use if you want but I don't advise it. You should continue with the instructions and update to KitKat after getting to ICS. I recommend Scott's CM11 (what I linked you to) or Scott's BeanStalk (find it in the Android Development Section).
Lately I've been using CyanFox and I have to say, it's the most stable ROM I've used in a while.
If you have any questions about this, feel free to ask.
Best of luck and happy flashing,
~bokonon9
Thank you muchness!
Thank you very much for helping me in this mess! I greatly appreciate it. I love my Infuse and do not want to get rid of it quite yet so hopefully this will help! Once I get a new usb cord I will get on this. My toddler decided to get a hold of it and it has to set a certain way now and can't be moved. This, is no bueno! Anyways, THANKS AGAIN!!! :laugh:
Goodluck! :laugh: :good:
I'm new in the android world and I'm using a nexus 7 and an infuse to make experiments just to learn.
bokonon9, thank you! You're guide has been precious to me.
Unfortunately I only succeeded installing ICS, infact I get till here:
After flashing Entropy's CM9, you will be on ICS, you can use if you want but I don't advise it. You should continue with the instructions and update to KitKat after getting to ICS. I recommend Scott's CM11 (what I linked you to) or Scott's BeanStalk (find it in the Android Development Section).
Click to expand...
Click to collapse
I tried to install CM11 and even CM10 at least half a dozen times each, following step by step the instructions that I've found on the thread but all the times I have the same issue:
after the zip rom update and the reboot, the bootloader keeps launching the CWM recovery. I see the logo, the progress bar and then I land in recovery
I don't get any kind of error (and I don't know where to look for to get more information than what's shown on the screen) and I'm just stuck in the recovery and I have to start from scratch every time using Odin all the way down.
I'm not interested in Gapps so, at the beginning I tried without installing them but then I tried also using the appropriate gapps as indicated in the procedure. Either way I didn't get any solution to my problem.
Do you have an idea? Is there a way for me to provide more information or debug?
Thank you!
wwr said:
I'm new in the android world and I'm using a nexus 7 and an infuse to make experiments just to learn.
bokonon9, thank you! You're guide has been precious to me.
Unfortunately I only succeeded installing ICS, infact I get till here:
I tried to install CM11 and even CM10 at least half a dozen times each, following step by step the instructions that I've found on the thread but all the times I have the same issue:
after the zip rom update and the reboot, the bootloader keeps launching the CWM recovery. I see the logo, the progress bar and then I land in recovery
I don't get any kind of error (and I don't know where to look for to get more information than what's shown on the screen) and I'm just stuck in the recovery and I have to start from scratch every time using Odin all the way down.
I'm not interested in Gapps so, at the beginning I tried without installing them but then I tried also using the appropriate gapps as indicated in the procedure. Either way I didn't get any solution to my problem.
Do you have an idea? Is there a way for me to provide more information or debug?
Thank you!
Click to expand...
Click to collapse
i would say go back to stock gb with odin and basically start over but with ics i always let it reboot to get a "feel" for it then i reboot to recovery and wipe basically everything then flash the next level of android which should be cm 10 then i let that boot then repeat that to get to kitkat 4.4.3 CarbonRom....sometimes you have to flash the same rom twice to get it to flash tho
I already tried all that and I can't figure out a way out ... I'm really banging my head against the wall
wwr said:
I already tried all that and I can't figure out a way out ... I'm really banging my head against the wall
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2091900&page=370
read the last post on that page by scmfxt
Hi, folks,
After many, many attempts, I finally was able to root my Verizon LG Enact/VS890/FX3, using NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243.apk, which I got from this forum about a week ago... for which I heartily thank Zero Sparks. Finally able to uninstall a lot of the crapware I didn't want, and to install several root-only apps which I did want.
The thing I'm having trouble with now, is finding custom ROMs for the phone. It's running KitKat, so it's not ancient, and if I can't use anything but the stock ROM, so be it. But I'm dying to try flashing Lollipop or even Marshmallow. It has to be a very specific ROM for that phone, because of the slide-out QWERTY keyboard... the wrong firmware wouldn't function properly. And there are a lot of bogus sites out there which want you to "complete a survey" or "sign up for one of these offers", but they never give you the download, it's just an endless circle of phishing sites... with lots of malware for my system, I'm sure. I'd much rather trust you folks on here, if you have anything.
I'm in the same boat, would love to upgrade off of 4.1.2 but can't find anything to use.
Additionally, a previous owner (bought off ebay) apparently unlocked the bootloader and replaced the stock recovery with something I don't recognize. When holding down power and vol down I see this:
Rooted
*********************************************
FACTORY HARD RESET
*********************************************
Permanently Erase User Data & Reset Settings?
Press Power key to confirm, and Volume Down or Up key to cancel
So not only can't I find a ROM to use, I can't even upgrade the stock ROM due to it not passing the root check. And I can't use stock recovery since it was replaced by the above. Anyone see this before?
I wish there was better support for the VS890 around, but I can't even find the original recovery / ROM image to flash.
UsualNoise said:
I'm in the same boat, would love to upgrade off of 4.1.2 but can't find anything to use.
Additionally, a previous owner (bought off ebay) apparently unlocked the bootloader and replaced the stock recovery with something I don't recognize. When holding down power and vol down I see this:
Rooted
*********************************************
FACTORY HARD RESET
*********************************************
Permanently Erase User Data & Reset Settings?
Press Power key to confirm, and Volume Down or Up key to cancel
So not only can't I find a ROM to use, I can't even upgrade the stock ROM due to it not passing the root check. And I can't use stock recovery since it was replaced by the above. Anyone see this before?
I wish there was better support for the VS890 around, but I can't even find the original recovery / ROM image to flash.
Click to expand...
Click to collapse
In my research, I could have sworn I came across a site that had the original "stock" LG software for download, but I can't find it now. The closest I come is this LG link that will give you the firmware -- and the VS890 is on their list: http://www.mylgphones.com/latest-lg-phones-firmware-update-model-version-date
I don't know if that might restore your stock recovery, at least. But have you tried doing the "factory reset" they offer, in this recovery app? Typically, this often restores the phone to whatever it was shipped with... which in your case, is just what you want. And there might be a method out there to un-root, I've seen that option in some of the better apps, like the "LG One-Click Root" found here. Then (if you're on Verizon, anyway), you could snag the OTA upgrade to 4.4.2, like I have... and root it again with the method I found.
ADDED LATER: Look in SuperSU, you should find an option for Permanent UnRoot.
Mr2nSmith said:
But have you tried doing the "factory reset" they offer, in this recovery app? Typically, this often restores the phone to whatever it was shipped with... which in your case, is just what you want. And there might be a method out there to un-root, I've seen that option in some of the better apps, like the "LG One-Click Root" found here. Then (if you're on Verizon, anyway), you could snag the OTA upgrade to 4.4.2, like I have... and root it again with the method I found.
ADDED LATER: Look in SuperSU, you should find an option for Permanent UnRoot.
Click to expand...
Click to collapse
Thanks for responding. Unfortunately my issue isn't the rooting of the OS (which I can undo, and have), it's the fact that the bootloader was unlocked and original recovery was replaced with that custom one I listed above. And yes, I did the 'factory reset', which reset everything to the original state of 4.1.2 ... but it didn't remove the custom recovery. Because of that, I can't ever upgrade via normal means (get the 0x13 error when I try).
Same deal with SuperSU, unrooting simply removes root access in the 4.1.2 OS, doesn't affect recovery. And, since there is no CMW / TWRP custom recovery option for VS890 I can't even attempt replacing the existing recovery. I'm stuck at this point unless someone figures out 1) where the stock recovery and firmware are located, and 2) a method to safely flash it to the phone. It sucks, I like this phone but it has some severe limitations. It also won't work with my Pebble watch, which is what prompted this whole endeavor in the first place (trying to upgrade to KitKat).
UsualNoise said:
Thanks for responding. Unfortunately my issue isn't the rooting of the OS (which I can undo, and have), it's the fact that the bootloader was unlocked and original recovery was replaced with that custom one I listed above. And yes, I did the 'factory reset', which reset everything to the original state of 4.1.2 ... but it didn't remove the custom recovery. Because of that, I can't ever upgrade via normal means (get the 0x13 error when I try).
Same deal with SuperSU, unrooting simply removes root access in the 4.1.2 OS, doesn't affect recovery. And, since there is no CMW / TWRP custom recovery option for VS890 I can't even attempt replacing the existing recovery. I'm stuck at this point unless someone figures out 1) where the stock recovery and firmware are located, and 2) a method to safely flash it to the phone. It sucks, I like this phone but it has some severe limitations. It also won't work with my Pebble watch, which is what prompted this whole endeavor in the first place (trying to upgrade to KitKat).
Click to expand...
Click to collapse
Have you tried simply finding and uninstalling the custom recovery? I know you said it was unfamiliar to you, but it has to be in there somewhere, under some name. And once it's removed, the phone would revert to its stock recovery. This is a great little phone, even if you can only get it to KitKat, don't give up.
Mr2nSmith said:
Have you tried simply finding and uninstalling the custom recovery? I know you said it was unfamiliar to you, but it has to be in there somewhere, under some name. And once it's removed, the phone would revert to its stock recovery. This is a great little phone, even if you can only get it to KitKat, don't give up.
Click to expand...
Click to collapse
The bad news: I would have no idea how to 'find' the custom recovery unfortunately.
The good news: I solved my problem! Although I couldn't update the OS via normal means (network) or via PC connection, I was able to manually flash KitKat (4.4.2) myself successfully. Here's what I did:
1) I downloaded the drivers for the phone from LG's site and installed them.
2) Connected the phone, it went into 'install' mode first where a drive appeared in my computer that contained the Verizon Upgrade Assistant.
3) Ran the upgrade assistant, it found the phone and downloaded the new firmware (.cab file). The upgrade assistant would not apply the update, unfortunately. I don't know if it was because of my bootloader issue or not, but I was at a dead end. Temporarily.
4) Tried following the procedure here but it didn't work with the current LG tools available. However it did point me in the right direction for
5) I found the LGFlashTool. I followed the instructions on that site. First went into download mode (powered off, removed battery, inserted battery, held vol up and down while plugging in the USB cable - *make sure it's a good cable!!*), then in the flash tool dialog itself I entered the .cab file name, selected [ CDMA, Diag, 33000 ], left what was auto-filled in version (but deleted the .cab extension) and hit the CSE Flash button. Next dialog I tried reading phone info, but it crashed (didn't fill me with confidence). Restarted, got back to that dialog, hit START. Next dialog, selected my country and language, hit OK. Then it popped up a new LG update window that actually did the update / flash.
Shockingly, it successfully worked. I was preparing myself for a bricked phone, but it worked ... AND fixed my bluetooth connection issue with my Pebble watch.
I have no idea if this procedure would work for custom ROMs or not (and I'm not going to press my luck and try), so I can't recommend it for non-stock stuff, but at least it's a way to flash a known working ROM for the LG Enact. Hopefully this helps someone else down the road. This was the first firmware flashing endeavor I've undertaken where I didn't already know someone else did it successfully first. Thus, my trepidation.
UsualNoise said:
The bad news: I would have no idea how to 'find' the custom recovery unfortunately.
The good news: I solved my problem! Although I couldn't update the OS via normal means (network) or via PC connection, I was able to manually flash KitKat (4.4.2) myself successfully. Here's what I did:
1) I downloaded the drivers for the phone from LG's site and installed them.
2) Connected the phone, it went into 'install' mode first where a drive appeared in my computer that contained the Verizon Upgrade Assistant.
3) Ran the upgrade assistant, it found the phone and downloaded the new firmware (.cab file). The upgrade assistant would not apply the update, unfortunately. I don't know if it was because of my bootloader issue or not, but I was at a dead end. Temporarily.
4) Tried following the procedure here but it didn't work with the current LG tools available. However it did point me in the right direction for
5) I found the LGFlashTool. I followed the instructions on that site. First went into download mode (powered off, removed battery, inserted battery, held vol up and down while plugging in the USB cable - *make sure it's a good cable!!*), then in the flash tool dialog itself I entered the .cab file name, selected [ CDMA, Diag, 33000 ], left what was auto-filled in version (but deleted the .cab extension) and hit the CSE Flash button. Next dialog I tried reading phone info, but it crashed (didn't fill me with confidence). Restarted, got back to that dialog, hit START. Next dialog, selected my country and language, hit OK. Then it popped up a new LG update window that actually did the update / flash.
Shockingly, it successfully worked. I was preparing myself for a bricked phone, but it worked ... AND fixed my bluetooth connection issue with my Pebble watch.
I have no idea if this procedure would work for custom ROMs or not (and I'm not going to press my luck and try), so I can't recommend it for non-stock stuff, but at least it's a way to flash a known working ROM for the LG Enact. Hopefully this helps someone else down the road. This was the first firmware flashing endeavor I've undertaken where I didn't already know someone else did it successfully first. Thus, my trepidation.
Click to expand...
Click to collapse
Good for you! See, you don't give up, and you get a happy ending.
It's a shame no roms for ours enact, its a cute qwerty android phone...please Can someone tell me how to enter recovery mode ? I bought this phone 2 day's ago but i haven't signal i want to do a wipe cache.. .sorry for my English.. .
Androide3 said:
It's a shame no roms for ours enact, its a cute qwerty android phone...please Can someone tell me how to enter recovery mode ? I bought this phone 2 day's ago but i haven't signal i want to do a wipe cache.. .sorry for my English.. .
Click to expand...
Click to collapse
Wish I could help you, but I never could do that on mine... had to use a sideload tool to do it from my PC. BUT -- I have two suggestions for you. First, download and install the KingRoot tool, to root the phone... it's called NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243.apk, and I think there is a link earlier in this thread which you can use to find and download it. You'll have to install it manually, then run it. (Don't bother with the "Purify" portion, you don't need that for now.) Your phone will now be rooted, by the only method that ever worked for me. Next, go to the Play Store, and download an app called "Quick Reboot", from Phong IT. This is a root-only app (hence the need to root, first) which includes a "Recovery" option. Try that out, and see what happens.
UsualNoise said:
The bad news: I would have no idea how to 'find' the custom recovery unfortunately.
The good news: I solved my problem! Although I couldn't update the OS via normal means (network) or via PC connection, I was able to manually flash KitKat (4.4.2) myself successfully. Here's what I did:
1) I downloaded the drivers for the phone from LG's site and installed them.
2) Connected the phone, it went into 'install' mode first where a drive appeared in my computer that contained the Verizon Upgrade Assistant.
3) Ran the upgrade assistant, it found the phone and downloaded the new firmware (.cab file). The upgrade assistant would not apply the update, unfortunately. I don't know if it was because of my bootloader issue or not, but I was at a dead end. Temporarily.
4) Tried following the procedure here but it didn't work with the current LG tools available. However it did point me in the right direction for
5) I found the LGFlashTool. I followed the instructions on that site. First went into download mode (powered off, removed battery, inserted battery, held vol up and down while plugging in the USB cable - *make sure it's a good cable!!*), then in the flash tool dialog itself I entered the .cab file name, selected [ CDMA, Diag, 33000 ], left what was auto-filled in version (but deleted the .cab extension) and hit the CSE Flash button. Next dialog I tried reading phone info, but it crashed (didn't fill me with confidence). Restarted, got back to that dialog, hit START. Next dialog, selected my country and language, hit OK. Then it popped up a new LG update window that actually did the update / flash.
Shockingly, it successfully worked. I was preparing myself for a bricked phone, but it worked ... AND fixed my bluetooth connection issue with my Pebble watch.
I have no idea if this procedure would work for custom ROMs or not (and I'm not going to press my luck and try), so I can't recommend it for non-stock stuff, but at least it's a way to flash a known working ROM for the LG Enact. Hopefully this helps someone else down the road. This was the first firmware flashing endeavor I've undertaken where I didn't already know someone else did it successfully first. Thus, my trepidation.
Click to expand...
Click to collapse
I did as you said, but I'm still on 4.1.2:crying: