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
OUT OF DATE USE THE ONE CLICK 1.85 ROOT TOOL IN THE FORUMS
As the ROM chefs go to work, we want to be sure that we are ready to flash the ROMs when they come to be available! This guide will help you set up your phone so that you can flash custom ROMs.
After this process you will have a phone on the latest firmware (1.85 at the moment) with bootloader unlock, rooted, and busybox installed.
This guide assumes you are on a root friendly firmware (as of now, it is firmwares 1.82.502.3 and below).
This is really going to be done in a four step process. First we need to root the device in order to access the place where the CID is stored so that we can change it and get unlocked. After changing the CID, we can unlock via htcdev.com. Then we can go on to installing a custom recovery and finally rooting!
From there I will give you some tips on installing ROMs.
NOTE: THIS PROCESS IS EXTREMELY DANGEROUS. IT MAY BE A BIT CONFUSING. READ OVER THE STEPS BEFORE STARTING. IF YOU DO NOT THINK YOU WANT TO RISK YOUR DEVICE BECOMING A BRICK THEN DO NOT ATTEMPT THIS. THIS VERY EASILY COULD RUIN YOUR DEVICE.
BACKUP EVERYTHING BEFORE STARTING AS EVERYTHING ON YOUR DEVICE WILL PROBABLY BE WIPED.
I, XDA, AND THE ORIGINAL TOOL CREATORS DO NOT TAKE RESPONSIBILITY FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. IT IS SOLELY YOUR RESPONSIBILITY FOR WHAT YOU DO TO YOUR DEVICE.
Click to expand...
Click to collapse
Your warranty will be void if you unlock the bootloader. If you just root though then you can return to 100% stock by running the RUU.
This guide is for Windows only at the moment though I will try to post Mac and Linux guides at some point.
ORIGINAL TOOL THREADS:
One Click Root for 1.82 and below: http://forum.xda-developers.com/showthread.php?t=1644167
Spoof CID Script: http://forum.xda-developers.com/showthread.php?t=1672284
I will try to keep this as up to date as possible! Taking a visit to the index of the development forums (http://forum.xda-developers.com/showthread.php?t=1671237) is also a good idea!
Last Updated: 5/28/12
0. Getting the prerequisites:
Download the package at the bottom of the first post to get started.
Extract the package somewhere you will remember (like on your desktop).
Connect your device via USB and make sure you have USB Debugging enabled under settings.
Click to expand...
Click to collapse
1. Root your device
1. Open the folder you downloaded and navigate to the "root" directory.
2. Double click on the root-windows.bat file
3. Let the root run and do not touch your device. It will reboot several times- do not touch it or you may brick your device. Just let it do its thing and eventually after around 3 minutes you will have a rooted device in your hand.
Click to expand...
Click to collapse
2. Get the unlock token
In order to unlock the bootloader we will need to change a value called the CID. This will allow the htcdev.com site to unlock our phones.
1. Go to the downloaded folder and go to the "change_cid" folder.
2. Click on the "Spoof-CID.bat" file. Follow the instructions. Your CID will change from CWS__001 (stock AT&T CID) to 11111111 (called "SuperCID," will allow you to flash anything)
3. Log in to htcdev and go here: http://www.htcdev.com/bootloader/unlock-instructions (NOTE: This skips the agreements you need to click through as some of the buttons on their website are wonky. Doing this assumes you agree to their policies that are listed there)
4. Follow the instructions very carefully (they are written very well) untill the point where you get the file "Unlock_code.bin" via email. Stop there.
5. You should now have the file for bootloader unlock. MAKE SURE TO SAVE THAT FILE "Unlock_code.bin" TO THE "generic" FOLDER IN THE PACKAGE YOU DOWNLOADED! YOU WILL NEED IT LATER.
Click to expand...
Click to collapse
3. Run the RUU to update to latest firmware
1. Download the latest RUU from the xda forums (should be an .exe file)
Currently it is version 1.85.502.3 and you can download it here:
http://briefmobile.com/download-htc-one-x-att-1-85-update
2. Follow its instructions very carefully. It will take approximately 20 minutes to complete. BE PATIENT. IF YOU UNPLUG YOUR PHONE HERE YOU WILL GET A BRICK.
3. Let your phone reboot and go through initial setup again
Click to expand...
Click to collapse
4. Unlock your bootloader using Unlock Token
1. Navigate to the "generic" folder in cmd (you should have added the Unlock_code.bin file to this folder already) and plug your phone in in fastboot mode. To do this, first shut off your phone. Wait for it to turn off. Then hold the volume down button. Press the power button for 3 seconds while still holding the volume down key. Let go of the power button but keep holding the volume down button untill you see a white screen with a bunch of small text on it. Use the volume up and down keys and the power button to select the FASTBOOT option. Plug your phone into your computer. Then wait for the FASTBOOT text to turn into FASTBOOT USB.
2. Type the following into cmd on your computer:
fastboot flash unlocktoken Unlock_code.bin
NOTE: This step might take quite a few tries. For some it works on the first time. For others, it may take around 20 times. Just keep typing in the command until you get a sucessful flash. We aren't sure why it does this at the moment but just keep trying and don't give up.
3. Use the volume keys to say that you do want to unlock your bootloader and wait for reboot
4. Bootloader should be unlocked! Congrats, most of the grunt work is done! Go to Settings - Developer Options - Enable USB Debugging. This will allow us to continue
5. Re-set up phone and enable USB debugging again
Click to expand...
Click to collapse
5. Install a custom recovery so that we can gain root access
1. Currently there are two recovery options: ClockWorkMod Touch and TWRP (TeamWinRecoveryProject). Both are pretty much the same as they both use touch input but TWRP does have some other nice features like a built in file browser and more. It is also more touch optimized. ClockWorkMod is more "old school" and I personally feel more comfortable using it, but using TWRP is fine as well. It doesn't really matter which recovery your choose, both are good choices. Download whichever one you want below:
CWM Touch: http://forum.xda-developers.com/showthread.php?t=1677304
TWRP: http://forum.xda-developers.com/showthread.php?t=1677447
2. Drag the .img recovery file you just downloaded into the "generic" folder
3. Connect your phone via fastboot
4. Type the following:
fastboot flash recovery <insert name of recovery .img file here>
Replace the stuff between the <> with the name of the file you just downloaded
5. Wait for your device to reboot. Then type into cmd which is cd'ed to the "generic" folder:
adb reboot recovery
6. Make sure your recovery works as soon as it is done loading and then press "reboot system"
7. Follow its instructions
Click to expand...
Click to collapse
6. Root your system
1. Connect your phone as a "Disk Drive" and drag the "root.zip" file in the "root" folder to your phone's memory
2. Reboot into recovery with the adb command (adb reboot recovery)
3. Go to install zip from sdcard and navigate to the zip file you downloaded. Say "yes" and watch it flash
4. Reboot system now
5. Go to the play store and download any app that has "Busybox installer" in its name (the one by JRummy16 works good I believe)
Click to expand...
Click to collapse
If all goes well, you should be sitting at an AT&T HTC One X which is on the latest RUU leaked firmware (1.85.502.3 at this moment), rooted, busyboxed, and unlocked.
Congrats!
If you want to flash any ROMs, download the .zip file of the ROM, place it on your phones memory, and then install the zip like you did to the root.zip file.
Enjoy your AT&T HTC One X!
CREDITS:
kennethpenn: For initial root, getting all the RUUs from the "source" and for giving the HTC One X's situation prime press appearance on his website, BriefMobile.com
grankin01: For finding out how to edit the CID originally
designgears: For creating the One Click Super CID tool for bootloader unlock
paulobrien: For porting CWM Touch to our device
sk08: For leading the way in terms of MODs and organizing an S-OFF thread to get this thing fully ours
JSLEnterprises: For initially being there to help organize a bootloader unlock
Team Nocturnal: For their awesome ROM
Click to expand...
Click to collapse
If you want to thank or donate to someone, please do not do so to me. The people above are the ones that deserve the thanks and the donations to encourage them to keep doing the fantastic work they have been doing! I'm just a high school student
Some common terminology:
Deoxdexed: OEMs package their apps with .odex files because they are more optimized for your device. However, this makes the file uneditable by developers and things like mods cannot be used with odexed ROMs. A ROM with "deodexed" as a feature means it is easier to use mods with that ROM
Busybox: A collection of linux tools that are helpful for flashing ROMs and doing other basic Android tasks
RUU: ROM Update Utility, made by HTC, completely reflashes device firmware, useful if you get bricks. Only for Windows.
Root: Allows you to edit system level files
S-OFF: (currently unattainable) Security-OFF, it is a "feature" in HTC phones that allows us to modify almost any part of your system.
Unlocked Bootloader: Allows us to flash custom images to the device.
Click to expand...
Click to collapse
As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.
HydroSkillet said:
As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.
Click to expand...
Click to collapse
Wasnt sure, there are still a few people asking how to do it since it is a bit complicated with the 1.85 update breaking root so I just compiled everything into a master one.
And yeah, I use a lot of the scripts in the package I put for download.
Anyway, mods do what you think with this thread! And this might be in the wrong section, wasnt sure if it goes in general or development.
Please keep this up. As it is the most aggregated list of instructions, I'm sure it will help many who have just gotten their phone. Great work by the way.
HydroSkillet said:
As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.
Click to expand...
Click to collapse
As I agree with you, a "one stop shop" that can be pointed out to for the noobs who got their mommy's to buy them their cool phone should at least keep the redundant questions to a minimum.
you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG
squishy5 said:
you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG
Click to expand...
Click to collapse
Locked boot loader yes.
Root for cwm no.
Sent from my HTC One X using xda premium
squishy5 said:
you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG
Click to expand...
Click to collapse
Why don't you read before you comment on things like this?
I never "Unlock the bootloader"
I simply get the Unlock token from HTC.
So stop acting like you know everything, because you dont
Don't ever use caps with me and expect me to come back with a nice response. I put this out for the community, not for some kid who thinks he knows it all to come back and say that I did it wrong when he didn't even read the post properly.
And you don't need root to install CWM, just an unlocked bootloader.
Stop calling my stuff wrong if you yourself don't even know what is right
rohan32 said:
Why don't you read before you comment on things like this?
I never "Unlock the bootloader"
I simply get the Unlock token from HTC.
So stop acting like you know everything, because you dont
Don't ever use caps with me and expect me to come back with a nice response. I put this out for the community, not for some kid who thinks he knows it all to come back and say that I did it wrong when he didn't even read the post properly.
And you don't need root to install CWM, just an unlocked bootloader.
Stop calling my stuff wrong if you yourself don't even know what is right
Click to expand...
Click to collapse
He put his foot in his mouth, apology should be coming oh and Good job man, Good job. Thanks for the work, this should be a sticky.
This is a great write up and would have been extremely helpful last night. I will admit I have done a lot of reading before I unlocked the bootloader and updated to 1.85, but it was still very confusing at some points. The htcdev site actually gave me the most trouble because I didn't realize most of the steps were completed and I could skip all the way to entering the token and the site was simply used for entering the token and getting the unlock file.
And yes, I almost said the same thing about the relock step. I had to read it twice to realize you didn't unlock yet. That's another thing that confused me last night was unlocking/relocking immediately.
I think this should be a sticky and all the other tutorials and such should be deleted. This is a perfect summary IMO and will use it when I unlock my friends one x
Sent from my HTC One X
My problem with this is that you packaged it all up while the individual threads for each thing are updating and you are severing up potentially outdated scripts.
designgears said:
My problem with this is that you packaged it all up while the individual threads for each thing are updating and you are severing up potentially outdated scripts.
Click to expand...
Click to collapse
I agree. While it is nice to have a all-in-one, you should be linking to the threads since they are updating them on a daily basis instead of linking to their scripts. Ive already had to change JeepFreaks script this morning as he updated it. It would make your world a lot easier if you did it that way, and also not risk giving some new user outdated scripts.
I think this should go in the General section as the first few pages should redirect to the original threads anyway.
Red5 said:
I agree. While it is nice to have a all-in-one, you should be linking to the threads since they are updating them on a daily basis instead of linking to their scripts. Ive already had to change JeepFreaks script this morning as he updated it. It would make your world a lot easier if you did it that way, and also not risk giving some new user outdated scripts.
I think this should go in the General section as the first few pages should redirect to the original threads anyway.
Click to expand...
Click to collapse
Sure thing, I will add to the original post for the links.
Also I will try to keep this updated, but yeah I might not catch all the updates
Thank you so much Rohan! Really appreciate it! Took me about 4 hours to get this done but it was worth it. Now to install cleanrom. Thanks again. This is my first time doing something like this.
Duse ijuat saw this and I'm going to do this and flash clean from when I get home and I read through this I honestly love you for doing this it helps more than you think thanks a lot
Deffinitlet should be stickied
Sent from my HTC One X using XDA
These are the best instructions! Wish i had them when all this shenanigans started. Thx
ethantarheels123 said:
Please keep this up. As it is the most aggregated list of instructions, I'm sure it will help many who have just gotten their phone. Great work by the way.
Click to expand...
Click to collapse
I agree. This guide is very helpful for me. I consider myself to be fairly computer literate and have flashed ROMs on previous phones, but I am a complete n00b to android and linux. Looking around some of the other threads -- it appears to me that there are many people who could have much confusion resolved by reading this. Thanks for the thread.
-- Jon
Not quite sure what's going on with my update...
I'm using the exe that updates the RUU and it gets stuck on the "sending to phone" step. Reboots the bootloader once, gets stuck again (as far as I can tell , nothing is ever sent) and then gives me an error telling me "The ROM Update Utility cannot update your Android Phone. Please get the correct ROM Update Utility and try again"
i've got the correct drivers installed (was having some trouble related to that a couple days ago but have since figured it all out ) would it be better to just do the update manually? (On my evo you just change the update file to Update.zip and it automatically installs it for you when you boot into bootloader)
maybe I'll have to look into it further, but just curious if anyone's run into this issue or figured out how to get past it as of yet...
Edit: Just an update- I'm betting its because I forgot to relock my bootloader before updating. So anyone who's already completed SOME of the steps in the second post here, make sure you relock your bootloader if you haven't already done so.
Edit1.5: This assumption was correct and the bootloader is now unlocked.
Edit 2- Almost done here... Busybox wont install. Tried two different apps, neither one worked. No indication as to why (got very vague error messages to the effect of "busybox was not installed")
Edit 3- FIXED- Ok, figured it out. As far as I can tell, the process should be Root first, THEN install busybox. It doesn't work without root privelages (at least that was my experience here)
I've searched & found 'How to....' threads on here but TBH I'm not a techy and most of it doesn't make sense to me.
I did try to upgrade from 4.0.4 to 4.1 this week and almost succeeded until some 'signature not recognised' message appeared. So I'm going to attempt another way (if possible/allowed) and ask if there's anybody out there who'd be willing to root (whatever that means), flash (ditto) and upgrade to 4.1 for me in return for payment.
I really hope this isn't against forum rules - it's a genuine, last-ditch attempt.
I live in the West Mids but travel a big chunk of the country each week so could possibly deliver the thing.
Here's hoping for an avalanche of replies.....
Can anyone tell me why I get the 'signature not verified' message please?
I've downloaded the upgrade from an October thread on this forum.
Which xoom do you have (wifi, 3g/4g, international, family)? Are you rooted yet?
dfib1 said:
Which xoom do you have (wifi, 3g/4g, international, family)? Are you rooted yet?
Click to expand...
Click to collapse
Thanks for replying!!
It's the wi-fi model. As for 'is it rooted?' - I would say not. One, because it's hardly been used and two, because I have no idea what 'rooted' means.
junctiontwo said:
Thanks for replying!!
It's the wi-fi model. As for 'is it rooted?' - I would say not. One, because it's hardly been used and two, because I have no idea what 'rooted' means.
Click to expand...
Click to collapse
Sorry I took so long to answer.
As for being rooted if you are the only one to have own the xoom and don't know what it means then you are most likely not rooted. Root is like getting administrator rights in windows. It gives you the ability to customize your device, install custom roms and also completely screw up your device .
You should be able to go to settings-about tablet--update (or system update) and it will check for your update and ask you to start the download and install. If this does not happen then you can flash back to Honeycomb (which I can walk you through this will also wipe all your data or maybe for a fresh start) and let your device automatically update to ICS (4.04) and the JB (4.1).
I can also walk you through rooting and installing a custom JB rom like you asked for free.
dfib1 said:
Sorry I took so long to answer.
As for being rooted if you are the only one to have own the xoom and don't know what it means then you are most likely not rooted. Root is like getting administrator rights in windows. It gives you the ability to customize your device, install custom roms and also completely screw up your device .
You should be able to go to settings-about tablet--update (or system update) and it will check for your update and ask you to start the download and install. If this does not happen then you can flash back to Honeycomb (which I can walk you through this will also wipe all your data or maybe for a fresh start) and let your device automatically update to ICS (4.04) and the JB (4.1).
I can also walk you through rooting and installing a custom JB rom like you asked for free.
Click to expand...
Click to collapse
Please don't apologise - you're the only one to answer!
I've tried the system update and have been told that there are none. (In my ignorance I actually thought it would update to 4.1.2 automatically!).
Your offer to walk me through the rooting & upgrade is extremely generous and I accept without hesitation.
If it's flashed back to HC, will it default back to ICS or move to JB?
A huge 'Thanks'.
James
PS. Having tried numerous times very recently to upgrade there's no data to erase so that's not an issue....
I am going to give you the steps to unlock your xoom, install a recovery, root, install CWM Rogue Touch recovery (better than the one you used to root) and then install stock JB.
Now that we are talking root I am going to ask a moderator to moved this thread to the root section.
Here is how I rooted my xoom.
follow the directions here but instead of doing step 1 follow this for adb install http://www.support-4-you.com/main/i...ged-adb-installation&catid=40:how-tos&Itemid= it is a 1 click adb install then follow from step 2 on.
When you are done there you can install CWM Rogue Touch screen recovery
Download CWM Rogue Touch zip and put on the root of your external sd card. ( if you don't have a sd card we will do it another way just let me know)
Boot into recovery by turning your xoom off.
1. press power
2. when the moto dual core logo comes on wait 3 seconds and press volume down
3. recovery should be displayed across the top press volume up.
You can skip steps 1- 3 now that you are rooted if you download Quick Boot open it, select recovery and the grant Super user permission
4. go to install zip from sd card (just like when you rooted) and find the CWM Rogue Touch Zip and install
5. reboot your xoom
6. you now have CWM Rogue Touch installed.
To install JB on your xoom you do need an sd card for this part
DownloadJB stock for wifi xoom and copy to your sd-card
Here is the thread discussing this [JB]Stock Android 4.1.1 JRO03H, Root, via CWM Recovery (US Wi-Fi MZ604) and also there steps for installing it but I will post them for you here.
boot into recovery
select backup and let it backup your current system (a Parachute)
then select wipe factory/data ( I Can't remember excactly what it says because I use a different one)
then select install zip from sd card
locate the JB rom you copy to your sd-card and install.
reboot system (it will take some time the first time)
sign in to android with your gmail account.
You are on JB
Good luck and don't worry if something goes wrong we can get you out of 99.99% of any issues that arise.
dfib1 = I cannot thank you enough.....
The frustrating thing is I'm about to leave the house and am working away until the weekend so can't try it until then! I'll let you know the outcome.
Have a great day :good:
If you need help with his excellent guide just post here or hit with a pm
Sent from my Xoom using xda app-developers app
Ok, a quick mid-procedure question....
(I'm doing something fundamentally wrong because I can't quite finish the upgrade).
Do I install the folders onto the Xoom from the SD in a zipped or un-zipped state? I've tried both but no luck so far in completing the task.
I've rooted successfully as my PC recognizes the device. I believe I've installed CWM ok - is there a way to confirm this?
On the final 4.1 install I get the 'installation aborted' message as 'signature not verified'. One thing I may be doing wrong is installing the wrong files? On selecting the JRO03H folder I'm then given file choices and I'm clicking on what I think are the most obvious. I can post a list of the choices if it helps?
Sorry to be such a newbie pain - I realize that these questions are irritating to those 'in the know'!
did you reboot after fastbooting the recovery? the recovery says clockwork at the top. It should also be touch screen controlled
When you move the zip over leave it as a zip on you xoom and when you flash the recovery will unzip it for you.
what step are you up to?
Sorry for the late update. I've tried the whole procedure several times from the very beginning, even removing previously installed Rogue & JB software, but STILL get the same error messages as previously described. I've re-booted at the right time according to the instructions but this still makes no difference, and have checked the 'USB de-bugging' option.
I did make a couple of basic errors in the Command function to begin with but realised these & corrected them. My device serial no. appeared so I assume I rooted successfully? I'm able to change Developer settings which I couldn't before. I even installed the USB drivers independently via the Motorola website.
I have a free day today so am going to make a bucket of coffee, make myself comfortable and start again.
One quick point - I'm in the UK and assume you two helpful guys are in the US? Looking at numerous sites it seems our respective Xoom models have different procedures which is maybe why this isn't working?
Thank you again for your seemingly endless patience.......
i believe you are getting these issues because you might still be running the stock recovery.
lets just backup and start fresh.
You followed the instructions mentioned before and I assume you have adb and fastboot installed.
Connect your xoom and make sure usb debugging is on.
open up a command line and type adb reboot bootloader
I'm going to assume because of the previous steps you unlocked the bootloader if not type in the command line fastboot oem unlock
You can download the recovery from here http://bit.ly/iLRAIV
If unlocked at the bootloader type fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img Note:make sure the img file is in the same folder where your fasboot.exe is in the sdk
after it has been flashed reboot device by hold volume up and power.
Move the JB stock rom into your sd card. you can download the rom from here http://www.mediafire.com/?qhbhlbvu859bv0f
after the device restarts type adb reboot recovery
in recovery Wipe everything except the sd card. Then flash the above jb rom. In theory everything should work. If you keep getting the error get back to us because Im going to give up and guide you through the install of the Team EOS Jellybean 4.1 rom that I know works without issues. PM if you want to have my direct contact info for gtalk so we can discuss further for any issues.
OK I've just tried another 8 times to root the thing, c-a-r-e-f-u-l-l-y following the instructions step-by-step.
1. I don't have the 'from SD card' option, instead have 'from USB drive'. I have a 16Gb flash drive connected via an adaptor for the Xoom which doesn't appear to prevent anything as it reads the contents of the card just fine, unless you can tell me otherwise?
2. In Recovery I get these options:
* reboot system now
* apply update from USB drive
* wipe data/factory reset
* wipe cache partition
3. Even when trying the very first install (Rogue), I get:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E: signature verification failed
Installation aborted
I love a challenge and always get a buzz when I manage to do something that is foreign to me i.e computers. On this occasion however I'm fast getting to the stage where I think it'd be easier to leave things at 4.0.4.
My reason for wanting the upgrade in the first place is because I'm comparing this tablet to my work-supplied Galaxy Tab 2 running 4.1.1. Realistically I don't think the two will ever be comparable and I'm probably foolish to think this could be the case. It only remains to say that I am so very grateful to both of you for taking so much time & effort in talking me though the procedures.
I consider myself pretty 'switched on' but this has me foxed!
Cheers guys - have a great weekend. Hope the snow doesn't cause you problems!
here are the outline of the steps
1. unlock your xoom
2. fastboot a recovery to install custom recovery on your xoom
3. reboot into new recovery
4. flash universal root zip to root your phone
5. reboot phone that is now rooted.
6. reboot phone into custom recovery again
7. flash jb update
I think you have missed step 1 or 2.
When you type fastboot oem unlock what does it say?
Hmmm, I MAY be one step closer?
After typing' fastboot oem unlock' the tablet has gone into 'Starting Fastboot protocol support' but appears to be stuck. Do I wait until it's done it's thing?
OR would it be a whole lot easier for all concerned if we tried your other suggestion dfib and flashed back to HC and then to JB?
What if you type adb devices? Does a bunch of numbers show up or does it say waiting for device?
Hold the front page!!!!!!!
I just watched a video on how to unlock and it's worked. You were quite correct - I had missed your point 1 above and probably point 2. I'm moving onto the next bit now....
Great let us know what happens. I will be around for a while.
Make sure phone is on 4.1.1 or 4.1.2, if not, put phone in usb debugging mode and open the RUU file and run it.
RUU downloads
make sure it matches your baseband though
download Hasoon2000 all in one/AIO for HTC One X
put phone in usb debugging and plugged in to android home screen
use chopper, step 2 on the list of options to the left, and make sure you get cid 1111111
use AIO to get into bootloader
select unlock bootloader in AIO
phone will reboot to factory android, skip ahead to android home page
hit finish or ok on AIO message
after success, get into usb debug and android homescreen and use AIO to flash TWRP, then boot into recovery and flash install to wipe TWRP
after CMD screens finish, reboot to phone, then use AIO to reboot into recovery
in TWRP select reboot into phone and itll prompt to flash SU and finish install to root
one booted to android file supersu app in app section, finish download thru playstore
open supersu app again and finish updates thru twrp, it will reboot into recovery, install zip, and reboot again to android
device is still cid111111
put soffbin file in adb location of of sdk, the platform tools folder usually
use AIO to flash one x zip file and follow prompts
after closing final cmd screen after failed 92, use AIO to boot up device in step 5
complete s-off with phone screen unlocked, close the cmd's as prompted
boot into bootloader, check for s-off
if s-off, boot into recovery
while in recovery;
enable usb mode
transfer CM and gapps files to device (or whatever rom and gapps)
wipe cache and dalvik and system
factory wipe
installCM and gapps
reboot
I'm hoping someone has links to the soffbin and one x zip files because they didnt work in AIO if I remember, a friend sent them to me.
enjoy
While you meant well, there might be a couple of problems with this.
1) This method will only work on certain firmware versions. You didn't properly note those firmware versions, you only noted Android versions which is irrelevant. A phone can be on 4.1.x without having the correct firmware version to use this method.
2) Using an RUU is a great way to update your device to the latest firmware, but there are instances where this will brick phones. For example, SuperCID + s-on + RUU = brick. That hasn't been noted in your post at all.
3) There are already explicit guides to unlocking/rooting for each firmware version here in our device forum. Creating another "guide" without all of the correct information is dangerous. It can also cause confusion due to the fact that there are different methods for different firmware versions.
My advice to anyone reading this who wants to root their device is this: work out which firmware/hboot you have and find the method already listed on this forum. There is a link in my signature to a resource thread, you'll find everything you'll ever need there.
To the OP: I'm not trying to cut you down, I hope you understand my reasons for this post after reading the information above.
Sent from my Evita
timmaaa said:
To the OP: I'm not trying to cut you down, I hope you understand my reasons for this post after reading the information above.
Click to expand...
Click to collapse
It all looks like constructive criticism to me, so hopefully it will be taken as such the the OP.
I agree, this isn't any more helpful than what is already out there, and not nearly comprehensive enough. It also needs a lot of cleanup, such as numbered steps and proper capitalization and punctuation. Some people might think this is nitpicky. But if you care enought to write it up, than do it in a way that is easy to read.
In his defense, this forum is crazy-messy.
I was a longtime ThunderBolt user, and on that forum there were clear paths to do what you needed to do. I will note that the ThunderBolt had only one version, and was only on Verizon.
My wife has an AT&T HOX. Not XL. She's on JB and her phone is slow and the battery lasts about 6 hours with moderate use. Nothing has been done to her phone to unlock, root, or S-off. But her phone is in such bad shape I'm thinking about stepping in.
Not trying to sound like a jerk, but all I care about is how I would go about taking a stock AT&T HOX through the rooting and romming process. I don't have Linux. I don't have a HTC OneXL. I'm not Canadian (Not that there's anything wrong with that, eh?).
Is there a CONSOLIDATED guide that will take me from stock to flashaholic? This thread attempts to answer this, and I applaud the OP. Hopefully we can work on perfecting this gem...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I don't think our forum is messy at all. There are different guides for a reason. Different firmware versions have different methods and therefore have separate threads. All you need to do is find out the firmware version the phone is on, and find the appropriate method. The concerns I raised are all valid and I stated them for a reason.
Sent from my Evita
Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.
blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.
I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.
@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!