Related
Hello, I followed the quoted instructions but when I flashed CM7 (including RC2, nightly #19, #22,#24...) I would get stuck in the CM7 splash screen, then it would boot loop back to the HTC splash screen.
I also flashed the Killer_Llama.v2 CM7 ROM and it booted just fine...but this ROM is extremely buggy for me.
Anyone have an idea why this is happening? Did I miss a step? Is there information I can retrieve to help you answer my question?
Thank you.
habanosrus said:
I am going to assume a couple of things.
* You are on Windows
* You have S-Off and you have root (confirm otherwise this will not work)
* You have the Hack Kit installed. IF YOU DO NOT, download it here...
- Make sure you turn off your antivirus software
- Make sure on your phone Fastboot unchecked, USB Debugging checked, Charge Only
- Connect your phone to computer via USB cable
- Open a CMD window (as administrator) Start button, type CMD in search box, right-click on CMD and click on Run As Administrator
- go to the directory where you unzipped the Hack Kit
- in the CMD window type "hackerize-ace install-downgrade", you will see a message that ROM is being pushed to SD card, it'll take a little while. (do not close CMD window)
- After pushing ROM your phone should reboot automatically and you may see your computer installing driver files (don’t worry if it does not successfully install all drivers).
- At the FASTBOOT USB menu press power. Your phone will search for the downgrade rom and start loading PD98IMG.zip file (blue progress bar on right, be patient).
- Confirm Start Update
- Then reboot
- Go through the Setup on your phone, check to make sure Fastboot unchecked, USB Debugging on and Charge Only
- Go back to the CMD window and type "hackerize-ace rage" (do not close CMD window)
- Start Visionary program on the phone
- Click Temp Root Now, then try Perm Root (it’ll say rooting device), allow superuser.
- Your phone should reboot
- Start ROM manager and Flash Clockwork Recover (3.0.0.6 is fine)
- Back to the CMD window and type “tools\win\adb reboot recovery”
- It should reboot your phone into Recovery Mode. For the time being reboot your phone and just check the fastboot unchecked, usb debugging checked and charge only settings.
- Go back to the CMD window and type "hackerize-ace setup-radio", "hackerize-ace flash-radio" which will reboot the phone into Fastboot mode. Press power to start the process.
- Reboot phone
- Go to the CMD window and type "hackerize-ace clean" (removes zip file from sd card).
- You won’t have any sound until you install a ROM. I would suggest you start with CM7.
- Download and copy the file to the root of your SD Card.
- Turn off your phone to boot into ClockworkMod Recovery. Hold Vol-Down and press power, hold Vol-Down until Fastboot menu, press power to enter HBOOT mode (let it do its check), Vol-Down to select Recovery and press power, phone will boot into ClockworkMod Recovery.
-
- First wipe your data/factory reset, then wipe cache partition.
- Now you can install the CM7 Rom. Use Volume keys to select "Install zip from sdcard", press Power, Vol keys to select "choose zip from sdcard", press power, Vol keys to select cm_ace....zip(or any other ROM you download).
- After you install CM7 you may also want to install Google Apps. Download the following file and repeat the process above.
Good Luck!
Click to expand...
Click to collapse
malignance said:
Hello, I followed the quoted instructions but when I flashed CM7 (including RC2, nightly #19, #22,#24...) I would get stuck in the CM7 splash screen, then it would boot loop back to the HTC splash screen.
I also flashed the Killer_Llama.v2 CM7 ROM and it booted just fine...but this ROM is extremely buggy for me.
Anyone have an idea why this is happening? Did I miss a step? Is there information I can retrieve to help you answer my question?
Thank you.
Click to expand...
Click to collapse
It is because you don't read and follow directions.....jk. Those instructions that you just posted are for people to get their clockmod recovery working.
1) Did you make a nandroid before you tried CM7?
malignance said:
Hello, I followed the quoted instructions but when I flashed CM7 (including RC2, nightly #19, #22,#24...) I would get stuck in the CM7 splash screen, then it would boot loop back to the HTC splash screen.
Click to expand...
Click to collapse
You need to have wiped your data/cache (some even suggest wiping Dalvik in advanced menu) when changing Roms, no wipe necessary when upgrading within the same ROM unless directed to by the dev. Just pull your battery and reboot back into Recovery (vol-den + pwr).
Sent from my HTC Inspire 1G
Please post in the proper section.
Yes, I did a nandroid backup.
Yes, I did a wipe of data/cache/dalvick
I followed the quoted instructions word for word. I have successfully flashed CM7 on a mytouch 4G...also I have successfully flashed Killer Llama.v2 CM7 on the Inspire 4g.
Please feel free to move this thread to the proper section, I was unsure where to post considering it was a question about Android Development...but it wasn't a "general" question so I did not post it in the General Discussion Board.
Thank you for your replies.
http://forum.xda-developers.com/showthread.php?t=997056
Hi all.
I have an Spanish wifi-only Xoom (MZ604) and I'm tired of waiting for motorola's updates (still in Honeycomb 3.2!!!).
I want to test either EOS3 (Android 4.1.1) or EOS2 (Android 4.0.4) custom roms. I've read almost all tutoriales but I still have some doubts about the procedures... could anybody check this message and warn me if I'm going to do something wrong?
DOUBT 1.- Key shortcuts in Xoom
Can anybody tell me the existing key combinations in Xoom? I only know about POWER+VOL_UP key to enter bootloader mode.
DOUBT 2.- How to install CWM.
If I understand it correctly, both EOS2 and EOS3 should be installed from CWM recovery...
Is the following procedure OK?
- Some tutorials say that you have to be root first to install CWM ... is it really needed? Can't be done directly with ADB?
- Install Android SDK in the PC.
- Download eos-recovery-r6.img or eos-recovery-r6-softkeys.img
- Connect XOOM to PC with the original USB cable.
- Reboot XOOM in bootloader mode (Power + VolUp)
- Exec adb and then:
fastboot oem unlock <---- is this a requirement?
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
DOUBT 3.- How to install or upgrade EOS 2 or 3 ROM?
Is the following procedure OK?
- Download ROM and gapps zip files.
- Start XOOM in recovery mode (CWM) -> How to do this?
- Do a nandroid backup.
- Wipe everything (data, cache, dalvik, etc)
- Install ROM zip.
- Install gapps zip.
- No need to do anything to root it, the rom is already rooted <-- is that right?
- Reboot
Is everything OK? Did I miss anything? Do I need to root my 3.2 install before any other step? Do I have to do the "oen unlock"?
Thanks.
All you need to do is unlock your boot loader and get into flashing eos3. Will give you details how to soon
Sent from my MZ601 using Tapatalk 2
wesamothman said:
All you need to do is unlock your boot loader and get into flashing eos3. Will give you details how to soon
Click to expand...
Click to collapse
Thanks for answering. If I'm understanding you correctly, you say that I don't need CWM and I can just flash the EOS ROM directly to my xoom without "applying" it as a zip in CWM...
I would really like to install CWM, I appreciate a lot the possibility to do "nandroid" backups to be able to go back before installing kernels, updates or so ...
NoP_Compiler said:
Thanks for answering. If I'm understanding you correctly, you say that I don't need CWM and I can just flash the EOS ROM directly to my xoom without "applying" it as a zip in CWM...
I would really like to install CWM, I appreciate a lot the possibility to do "nandroid" backups to be able to go back before installing kernels, updates or so ...
Click to expand...
Click to collapse
Since you are going to install EOS Jellybean, I don't advise you with CWM. A different recovery made by EOS team is better through which you can do nandroid backup and other stuff...
Here is what you need to do step by step...
Note: please read this procedure carefully more than once until you are fully aware of it. If you have any doubts or concerns, just ask to avoid confusion before you apply. This should be followed step by step.
To summarize:
First, download the above ROM and GAPPs and put them onto your xoom internal and external SD card. Put them under /mnt/sdcard for internal sd or somewhere accessible, and under the root of your external sd card.
To download:
• Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
• Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html
• Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
• GAPPS: http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120726-eos-signed.zip
• ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ ; get the latest one...
Steps:
1. Power off your XOOM device.
2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
3. Connect Xoom to your computer via USB.
4. Open a ‘Command Prompt’ or ‘Terminal’ window on your computer in your sdk/tools folder. This is the sdk you downloaded above.
5. unlock your xoom and flash the recovery image. The recovery image should be in your current working directory where you have command line navigated to: Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
adb reboot recovery
Now, you have your device unlocked and recovery installed.
Reboot your xoom by selecting the option "reboot system now" from recovery. you can navigate up and down using the volume buttons. Once an option is highlighted, press the power button to select, you will still have your old ROM.
To flash the other ROM downloaded above,
1. Boot into recovery by:
i. As soon as you hit the reboot command above, you should see a Motorola logo appear. Wait 3 seconds and tap the Volume down button and the words Android Recovery should appear on the screen. When you see that, tap the Volume up button and you’ll boot into recovery.
2. From within Recovery, perform wipe data, wipe cache, and go to advanced, wipe dalvik cache and battery stats. Don't worry, if the ROM and GAPPs are deleted, which should not be the case, you will have them on your external sd card
Note: wipe data will delete your stuff on the xoom. It would be great if you backup your files that you need to your external sd card before you start any of this procedure.
3. In recovery, navigate to install zip from sdcard > choose zip from sd card and select the EOS ROM you copied to the root of the SD card. Once the files are flashed, DO NOT reboot afterwards. Hold on.
4. Again, from Recovery, choose install zip from sdcard > choose zip from sd card and select the GAPPs you copied to the root of the SD card.
Then hit reboot system now. It will take 2 - 3 minutes for the first reboot. Setup your google account. and you are good to go.
Later reboots will be much faster (around 30 - 45 seconds). The more apps you install, the slower it boots...
That is pretty much it. Enjoy, I hope this helps you
Of course it helps! In fact, a lot.
When I was talking about CRW I really meant EOS recovery (which is based in CRW itself IIRC).
The only that I can't understand is why some tutorials ask me to root the tablet before doing all this process...
Anyway, I think I'm finally going with EOS3 + EOS recovery if nobody here advices me to flash EOS 2 instead...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.
So, before flashing:
- Do you think EOS3 (JB in Xoom) is mature enough to use it, or I should go with EOS2 final (ICS)?
- Do you know of anything not working in a wifi xoom with EOS3 rel.127?
- I've downloaded eos6-recovery.img ... do you think I should flash the "soft-keys" or the rogue-recovery instead?
- I don't have Microsoft Windows in my laptop: I work under Linux, so I haven't downloaded Motorola's USB drivers... I imagine that they are not needed under Linux, and It will work just with SDK's "adb" and "fastboot", right?
- Can the device be bricked with this procedure, or there is always a "Power+VolKey" way to flash a stock image? (like galaxys2 that its almost unbrickable).
PS: Thanks for informing me in the other thread that the EOS rom comes already rooted
I will be away for couple of hours, will answer your questions all as soon as I get back...
Sent from my MZ601 using Tapatalk 2
NoP_Compiler said:
So, before flashing:
- Do you think EOS3 (JB in Xoom) is mature enough to use it, or I should go with EOS2 final (ICS)?
- Do you know of anything not working in a wifi xoom with EOS3 rel.127?
- I've downloaded eos6-recovery.img ... do you think I should flash the "soft-keys" or the rogue-recovery instead?
- I don't have Microsoft Windows in my laptop: I work under Linux, so I haven't downloaded Motorola's USB drivers... I imagine that they are not needed under Linux, and It will work just with SDK's "adb" and "fastboot", right?
- Can the device be bricked with this procedure, or there is always a "Power+VolKey" way to flash a stock image? (like galaxys2 that its almost unbrickable).
PS: Thanks for informing me in the other thread that the EOS rom comes already rooted
Click to expand...
Click to collapse
Alright, eos jelly bean is fully stable, ,such faster and smoother than ICS. You want feel the difference until you try it... however, eos ICS is stable too and has more features and addons by eos because it has been there under dev for longer time, jellybean is new, one month old only... I recommend you to go for jellybean, and try and see for yourself. At anytime you can flash ICS since your Xoom booloader is already unlooked and recovery installed, you can do that by just wiping data and flash ICS zip. That is as simple as that...
For Motorola drivers on Linux, I think it is not needed, adb is built in with Linux, but I am not sure as I haven't tried that yet.
For eos recovery, don't use the soft key version, use the normal one...
with this recovery, you will be safe, because at all times, your external SD is accessible in emergencies...
Hope that helps...
Sent from my MZ601 using Tapatalk 2
You have it down perfectly. Just to recap.
1. Set up android sdk. Download recovery image and store in sdk folder. Download rom/gapps and store on tablet.
2. Boot into fastboot (power + volume up).
3. fastboot oem unlock (required). This will wipe all data.
4. fastboot flash recovery recovery.img (whatever recovery you decide to go with, I recommend eos soft key).
5. boot into recovery, make nandroid backup, flash rom of your choice + gapps if necessary.
People tie rooting to flashing custom roms because many people have become so reliant on apps like rom manager that flash the recovery for you, an app that requires root access. I never rooted my galaxy nexus or xoom. I simply flashed recoveries in fastboot and proceeded to flash roms in recovery.
It actually bothers me how some have become so reliant on root access to flash roms. It has gotten to a point where many people genuinely don't know the difference and that, to me, says they don't really understand what it is they're doing, which will lead to issues should they ever need to troubleshoot.
You seem to have it down well though. Good luck.
Thanks a lot to both.
I'm still waiting for JDK to download for Android SDK to work (I'm on hollydays in a small house in the middle of the forest and Im connecting with GPRS via tethering...).
I'll inform about the results...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.
Good luck...
Sent from my MZ601 using Tapatalk 2
Ok. EOS6-RECOVERY installed correctly. There are a couple of mistakes and some missing info in the "tutorial", so I'm going to change it to help future users:
I finally did it under Windows because almost all tutorials in Internet explain all the possible problems that you can find in Windows, and it's a "too risky" task for me to "experiment" by myself.
PART 1 .- HOW TO INSTALL EOS6 RECOVERY:
Originally quoted from wesamothman:
First, download the above ROM and GAPPs and put them onto your xoom external SD card. Put them in a folder called /sources/ of your external sd card.
- Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
- Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html
- GAPPS: http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120726-eos-signed.zip
- ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ ; get the latest one...
And the most important:
- Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
Check that the md5sum of this file is correct and matches with the one provided in the download page. This is the most important file because it will allow to install the CWM recovery system and it's CRITICAL that the file is not corrupted.
Steps:
a.- Install in your PC the lastest JavaSE JDK from Oracle's website.
b.- Install in yout PC Android SDK, open Windows' cmd, enter the android-sdk folder and run:
Code:
tools\android.bat update sdk
Now select "Android SDK Tools", "Android SDK platform-tools", and Extras/"Google USB Driver". Click on "Install packages".
c.- Enable USB debugging in the XOOM (in settings, development).
d.- Install the Motorola USB drivers for your laptop (32 or 64 bits, check it in the Windows system properties).
e.- Plug the Xoom to your laptop.
f.- Execute cmd and enter the android-sdk/platform-tools folder.
Run "adb devices", if you get an empty "List of devices attached", then you must enter the control-panel -> devices and "Fix problem with device" over the MZ60x device. After a While, Windows will fix it and "adb devices" will show a message like:
Code:
List of devices attached
037887sda897xz device
(the digits string will vary according to your device)
NO NEED TO DO THIS:
NO -> 1. Power off your XOOM device.
NO -> 2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
Because the first command show after this lines: (adb reboot bootloader) won't work while in fastboot. Only "fastboot" commands work in fastboot mode. If you try that command in fastboot mode, it will say "Error: device not found".
So just, with your xoom working under the Android OS, do:
Code:
adb reboot bootloader
With the above, you'll enter fastboot mode without needing to press any key in the startup.
Now your Xoom will show the Motorola logo and the words "Fastboot protocol...". If you need to stop now for any reason, you can abandon this mode safely and reboot the tablet with "Power+VolUP+VolDown" for a few seconds.
But let's continue.... If you now do:
Code:
fastboot devices
You should get a string like
Code:
List of devices attached
037887sda897xz fastboot
If you don't see that string (and you see and error about device not found), you have to "fix/repair" the usb drivers again in the Windows ControlPanel / Devices. Now you'll see a "FASTBOOT" device instead of the MZ60x you repaired before (that's why we have to repair/fix again the device, because WIndows see it as a different device while in fastboot mode).
After repairing it, unplug and plug the USB cable (still in fastboot mode) and repeat the command:
Code:
fastboot devices
Now it will work and you'll see the device recognized by "fastboot"
Issue the following command to unlock the Xoom (you'll void the warranty):
Code:
fastboot oem unlock
Follow the Xoom's onscreen instructions to unlock the bootloader. You have to use VolDown to move through options and VolUP to accept an option.
The xoom will reboot and your old android OS will show, but now with a factory reset. Select language, time, etc and enable again USB debugging and execute in the PC:
Code:
adb reboot bootloader
(to start again the tablet in fastboot mode)
Now copy the file eos-recovery-r6.img to the android-sdk/platform-tools/ folder and execute:
Code:
fastboot flash recovery eos-recovery-r6.img
You will see something like:
Code:
C:\Users\sromero\Desktop\android-sdk-windows\platform-tools>
fastboot flash recovery eos-recovery-r6.img
sending 'recovery' (4114 KB)...
OKAY [ 0.499s]
writing 'recovery'...
OKAY [ 1.014s]
finished. total time: 1.529s
Check in the xoom's screen that the file was correctly written and execute:
Code:
fastboot reboot
You xoom will start again in Android OS mode. Execute:
Code:
adb reboot recovery
And you'll start the nice EOS Recovery (based on Clockworld Mod) recovery system.
You can also do it manually by powering on the Xoom and when the motorola logo appears, wait 3 seconds and press VolUp.
Now, you have your device unlocked and recovery installed. Now, you are SAFE because you can do nandroid backups and restores and can put any ROM in your system and go back with a backup or flash another different rom.
PART 2 .- HOW TO USE CWM / EOS RECOVERY
Code:
Up -> VolumeUp button
Down -> VolumeDown button
Select -> POWER button
PART 3 .- HOW TO INSTALL EOS3 ROM:
Under recovery mode (abd reboot recovery), do:
- Backup/restore -> backup to external SD.
- Wipe data/factory reset
- Wipe cache
- Advanced -> Wipe Dalvik Cache
- Advanced -> Wipe Battery Stats
- Install ZIP from SDCARD -> /sources/ -> the eos3 rom .zip file.
- Install ZIP from SDCARD -> /sources/ -> the gapps .zip file.
- Reboot
- Enjoy your new rom!
Very well detailed... great...thx.
Sent from my MZ601 using Tapatalk 2
wesamothman said:
Very well detailed... great...thx.
Click to expand...
Click to collapse
No... thank you for the initial info
After restarting, I have a notification about a ROM update (128). The ROM-management app allows me to download it or apply a incremental update...
Do you know if that second option (incremental update) is safe?
Anyway, I can just always do a Nandroid and test it ... having CWM I can't loose never anything, right?
Of course it is safe, I use it a lot. Just boot into recovery now by long press on power menu, select reboot, recovery,
First download build128. It will be under /storage/sdcard0/goo manager.
From recovery, wipe cache, dalvik, flash build 128, and reboot,
FYI, this latest build has theme engine now
Sent from my MZ601 using Tapatalk 2
wesamothman said:
First download build128. It will be under /storage/sdcard0/goo manager.
From recovery, wipe cache, dalvik, flash build 128, and reboot,
FYI, this latest build has theme engine now
Click to expand...
Click to collapse
So, the incremental update has to be flashed from recovery too?
I'll try it after a few days, when people confirms that it has not any major bug...
Thanks.
NoP_Compiler said:
Thanks a lot to both.
I'm still waiting for JDK to download for Android SDK to work (I'm on hollydays in a small house in the middle of the forest and Im connecting with GPRS via tethering...).
I'll inform about the results...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.
Click to expand...
Click to collapse
Worth noting that to use fastboot and stuff, you only really need to install the Android SDK Platform-tools, maybe the regular SDK tools as well, I can't remember.
You don't need to install all the other stuff.
---------- Post added at 08:02 AM ---------- Previous post was at 08:01 AM ----------
NoP_Compiler said:
So, the incremental update has to be flashed from recovery too?
I'll try it after a few days, when people confirms that it has not any major bug...
Thanks.
Click to expand...
Click to collapse
Yes, any updates/mods/gapps updates need to be flashed in recovery.
Unless specified that its necessary by devs though, you don't need to wipe anything. I've been on JB nightlies from day 1 and I haven't wiped cache or anything since the initial wipe.
Is it possible to...
a.- change the system font (too 'light' in my xoom).
b.- disable jellybean UI animations...
?
I don't know about question a, though I'm sure its possible.
As for question b, try a different launcher. Apex launcher and nova launcher are both popular Android 4.0+ launchers (check play store for them).
Eos ROM,m settings, developer options, disable animations and transitions
Sent from my MZ601 using Tapatalk 2
. I don't even want a custom ROM. I just want to be rooted and run stock with rooted google play store apps. Am I there?
I just want to run rooted apps with no ROM flashing...oh god why...where is the guide to root and only root?
You'd think this http://forum.xda-developers.com/show....php?t=1652398 would be where to go to do that, but evidently it's sending me down the road to custom ROM flashing. AGHGHGhjkdashbdas. Do not want.
Ok, so here's where I am, I have finished step 8:
1. Download Odin 1.85 .
2. Download(USE FIREFOX!) ClockworkMod TOUCH 5.5.0.4 OR TWRP 2.2.2.0, they are both named "recovery.tar.md5" and will be downloaded as "recovery.tar.md5", DO NOT CHANGE the filename or else it wont install.
3. Extract the contents of odin-185.zip to a folder.
4. Run Odin 1.85.exe from the folder you extracted it to.
5. Prepare Odin: Check "auto-reboot" and UNCHECK ALL OTHER OPTIONS. SEE COMPUTER SREEN PICS BELOW.
6. Only Click "PDA" and select the recovery.tar.md5 file you downloaded. SEE COMPUTER SREEN PICS BELOW.
7. How To Put your device into Download Mode: DO NOT TOUCH THE POWER BUTTON FOR THIS PROCEDURE. - download mode is NOT the same as recovery mode
a. Connect the USB cable to your PC, but NOT to your phone.
b. Remove the battery.
c. Reinsert the battery.
d. ATT PHONES - Press and keep down both Volume Up and Volume Down keys simultaneously.
ROGERS PHONES - Press and keep down only the Volume Down key.
DO NOT RELEASE THE VOLUME KEY(S) UNTIL INSTRUCTED TO DO SO IN STEP (f)
e. Insert the USB cable into your device. The phone will turn itself on when usb cable is inserted - DO NOT TOUCH THE POWER BUTTON.
f. You will now see a screen w/a yellow triangle warning you about installing a rom . Now release the volume key(s) - SEE PHONE PICS BELOW
g. Press and release the "Volume Up" key to enter into download mode - SEE PHONE PICS BELOW
h. You should now be at the Download Mode screen w/odin recognizing your phone. SEE COMPUTER SREEN PICS BELOW.
8. Click Start in Odin. It will flash the new recovery and will reboot the phone when completed. Your device will autoreboot into android. You are done using ODIN.
9. UPDATING CWM OR TWRP:
Now you need to udate CWM, download and copy cwm6027touch_v14.4.6_skyrocket.zip file to your sdcard, boot into recovery and choose "INSTALL FROM SDCARD" from recovery, install the file and reboot back into recovery to see if it installed correctly.
sk8erwitskil's CWM thread is here HERE , check to see if above file is the latest or dl the "Flashable zip" CWM file from there.
If upgrading TWRP go here HERE and follow the dev's instructions on using goo app, or you can use the flashable TWRP 2.4.1.0 file HERE and copy that file to your sdcard, boot into recovery and pick "INSTALL" from recovery, install the file and reboot back into recovery to see if it installed correctly.
How to enter recovery read section #2 below.
How to use cwm read THIS, also read Q&A on recoveries
You can upgrade to either CWM OR TWRP from which ever recovery TAR file you used in ODIN in step #2 from above.
10. You're done newbie and soon to be a power user, read and educate yourself as much as you can before flashing, happy flashing.
Click to expand...
Click to collapse
I don't know how to do step 9. Do I even need it? I have no desire to run a custom ROM.
yargdpirate said:
OK so here's the list of instructions I'm using to root my Skyrocket:
I have completed everything through step 4. I completely do not understand what to do after that. So, like I'm a 40 year old soccer mom, can you explain what I'm supposed to do to fulfill step 5? Is it through the odin app on my pc? Is this completed on my phone? The link provided that ostensibly explains to noobs how to do this (http://forum.xda-developers.com/showthread.php?t=1777970) doesn't adequately explain to me what I'm doing and where.
Help, please!
Click to expand...
Click to collapse
Assuming that you have successfully installed your custom recovery you then need to know which recovery you installed before you update it. If you used CWM you can get the updated version from the Skyrocket development thread. Put the updated CWM file on your SD card and flash that zip while in recovery. If you used TWRP you can update it through the app that it installed if it did install one. GooManager (someone correct me if I am wrong on the name) I think GooManager needs suoeruser privileges. So which recovery did you flash?
CodeNameRedNeck said:
Assuming that you have successfully installed your custom recovery you then need to know which recovery you installed before you update it. If you used CWM you can get the updated version from the Skyrocket development thread. Put the updated CWM file on your SD card and flash that zip while in recovery. If you used TWRP you can update it through the app that it installed if it did install one. GooManager (someone correct me if I am wrong on the name) I think GooManager needs suoeruser privileges. So which recovery did you flash?
Click to expand...
Click to collapse
Put the updated CWM file on your SD card and flash that zip while in recovery?
Click to expand...
Click to collapse
It's CWM. How do I
A. Put the updated CWM file on my SD card and
B. Flash that zip while in recovery? Is that through Odin, or what?
Thanks
yargdpirate said:
It's CWM. How do I
A. Put the updated CWM file on my SD card and
B. Flash that zip while in recovery? Is that through Odin, or what?
Thanks
Click to expand...
Click to collapse
i think you should stay on stock, read more b4 you brick your phone, no sense in rooting/installing custom roms when you dont know how to install a file on your scard, im not putting you down but trying to give you friendly advice
Vincom has a point. I taught myself through these forums and Google how to do it back in October of 2011. I flashed many a ROM and many files since then until I bricked mine Thursday. Now I have to pay 60 dollars to get it fixed. But on the upside I now have a Note II to play with.
Edit: She is asking for help though and she did ask in the right thread. Some people need more help than others.
vincom said:
i think you should stay on stock, read more b4 you brick your phone, no sense in rooting/installing custom roms when you dont know how to install a file on your scard, im not putting you down but trying to give you friendly advice
Click to expand...
Click to collapse
Oh. ****. I don't even want a custom ROM. I just want to be rooted and run stock with rooted google play store apps. Am I there?
I just want to run rooted apps with no ROM flashing...oh god why...where is the guide to root and only root?
You'd think this http://forum.xda-developers.com/showthread.php?t=1652398 would be where to go to do that, but evidently it's sending me down the road to custom ROM flashing. AGHGHGhjkdashbdas. Do not want.
Ok, so here's where I am, I have finished step 8:
1. Download Odin 1.85 .
2. Download(USE FIREFOX!) ClockworkMod TOUCH 5.5.0.4 OR TWRP 2.2.2.0, they are both named "recovery.tar.md5" and will be downloaded as "recovery.tar.md5", DO NOT CHANGE the filename or else it wont install.
3. Extract the contents of odin-185.zip to a folder.
4. Run Odin 1.85.exe from the folder you extracted it to.
5. Prepare Odin: Check "auto-reboot" and UNCHECK ALL OTHER OPTIONS. SEE COMPUTER SREEN PICS BELOW.
6. Only Click "PDA" and select the recovery.tar.md5 file you downloaded. SEE COMPUTER SREEN PICS BELOW.
7. How To Put your device into Download Mode: DO NOT TOUCH THE POWER BUTTON FOR THIS PROCEDURE. - download mode is NOT the same as recovery mode
a. Connect the USB cable to your PC, but NOT to your phone.
b. Remove the battery.
c. Reinsert the battery.
d. ATT PHONES - Press and keep down both Volume Up and Volume Down keys simultaneously.
ROGERS PHONES - Press and keep down only the Volume Down key.
DO NOT RELEASE THE VOLUME KEY(S) UNTIL INSTRUCTED TO DO SO IN STEP (f)
e. Insert the USB cable into your device. The phone will turn itself on when usb cable is inserted - DO NOT TOUCH THE POWER BUTTON.
f. You will now see a screen w/a yellow triangle warning you about installing a rom . Now release the volume key(s) - SEE PHONE PICS BELOW
g. Press and release the "Volume Up" key to enter into download mode - SEE PHONE PICS BELOW
h. You should now be at the Download Mode screen w/odin recognizing your phone. SEE COMPUTER SREEN PICS BELOW.
8. Click Start in Odin. It will flash the new recovery and will reboot the phone when completed. Your device will autoreboot into android. You are done using ODIN.
9. UPDATING CWM OR TWRP:
Now you need to udate CWM, download and copy cwm6027touch_v14.4.6_skyrocket.zip file to your sdcard, boot into recovery and choose "INSTALL FROM SDCARD" from recovery, install the file and reboot back into recovery to see if it installed correctly.
sk8erwitskil's CWM thread is here HERE , check to see if above file is the latest or dl the "Flashable zip" CWM file from there.
If upgrading TWRP go here HERE and follow the dev's instructions on using goo app, or you can use the flashable TWRP 2.4.1.0 file HERE and copy that file to your sdcard, boot into recovery and pick "INSTALL" from recovery, install the file and reboot back into recovery to see if it installed correctly.
How to enter recovery read section #2 below.
How to use cwm read THIS, also read Q&A on recoveries
You can upgrade to either CWM OR TWRP from which ever recovery TAR file you used in ODIN in step #2 from above.
10. You're done newbie and soon to be a power user, read and educate yourself as much as you can before flashing, happy flashing.
Click to expand...
Click to collapse
I don't know how to do step 9. Do I even need it? I have no desire to run a custom ROM.
For just rooting u have to run the superuser zip through your recovery
Oh and if you are not understanding what the stickies are saying to do then look it up on youtube because there are a lot of step by step instructions there.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
a. put updated file in your micro sd card.... plug ur micro sd card to pc... drag file and drop it in your micro sd card. put the micro sd card back in phone.
b. to go to recovery press power button + vol+ + vol- all at once and hold.
why do u need to unlock play store app? playstore is accessible completely even without root. you can also sideload Amazon appstore and other apps without root. no need to get all bricked up just to run playstore. i'm confused what are you trying to do again?
droidbabyxda said:
a. put updated file in your micro sd card.... plug ur micro sd card to pc... drag file and drop it in your micro sd card. put the micro sd card back in phone.
b. to go to recovery press power button + vol+ + vol- all at once and hold.
why do u need to unlock play store app? playstore is accessible completely even without root. you can also sideload Amazon appstore and other apps without root. no need to get all bricked up just to run playstore. i'm confused what are you trying to do again?
Click to expand...
Click to collapse
im guessing he wants to run apps from play that require root, eg titanuim backup, but he doesnt know how to put a file on his sdcard, but then he has to learn how to install zips from recovery which someones got to teach him since he doesnt want to read/learn/search for the answers. he seems to be impatient and wants it done "now", its a brick waiting to happen, my advice to him was to slowdown and learn
vincom said:
im guessing he wants to run apps from play that require root, eg titanuim backup, but he doesnt know how to put a file on his sdcard, but then he has to learn how to install zips from recovery which someones got to teach him since he doesnt want to read/learn/search for the answers. he seems to be impatient and wants it done "now", its a brick waiting to happen, my advice to him was to slowdown and learn
Click to expand...
Click to collapse
agree and such bad attituted too. i wouldn't want to help anybody who cusses in every conversation geez little respect goes a long way
It you just want to root and not want to flash any custom ROMs or anything related to it,I will tell you how to from total beginning
ALL DATA WILL BE LOST , BACKUP EVERYTHING
In order to root Android 4.2 the following three requirements must be satisfied beforehand:
The Android SDK, which you can download from Google Developers
A custom recovery like ClockworkMod (CWM) or Team Win Recovery Project (TWRP)
SuperSU, which you can download from CF-Root
There are no major differences between the two, but TWRP is more touch-oriented thanks to larger buttons. CWM is also available in a touch-compatible variant, but it has much smaller buttons. It's a matter of personal preference between the two though, but you have to choose one.
Before starting the process I urge you to perform a backup, as all data might be lost afterwards. You can copy the contents of the SD card to a safe external location such as cloud storage service or computer hard drive.
The first step that needs to be performed after all the files are downloaded is to install the Android SDK. Afterwards open the Android SDK Manager and select the following two items:
Android SDK Platform-tools -- it contains the required programs to install Android 4.2 Jelly Bean
Google USB Driver -- it contains the necessary drivers for the Nexus device
Then you should create a folder in an easily accessible location within the command line. In this example I will use a folder named "Root" in my C:\ drive in Windows. The path name will therefore be: "C:\Root".
From the folder where Android SDK Platform-tools is installed (in my case it is "C:\Program Files x86)\Android\android-sdk\platform-tools" copy the following files to the previously created "Root" folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
The following files must also be copied to the "Root" folder:
CWM-SuperSU-v0.97.zip -- SuperSU file
The custom recovery that you previously downloaded for your specific device (please see below)
For my 8 GB nexus 7 wifi(codename "grouper" I will use TWRP with the name "openrecovery-twrp-2.3.1.0-grouper.img".
You can easily find the codename for your devoice by looking into Google
The custom recovery file differs for each device, please make sure you download the correct file
In order to make the process smoother for instance the SuperSU file can be renamed to "root.zip" and the custom recovery to "customrecovery.zip". It's a matter of convenience, but for accuracy I will stick to the original naming for this guide.
If the previous steps are completed you must have the following six files in your "Root" folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
CWM-SuperSU-v0.97.zip -- SuperSU file
The custom recovery. In my case it is "openrecovery-twrp-2.3.1.0-grouper.img"
From there, you can proceed to install the drivers for "fastboot mode". To install them, follow these steps:
Power off your Nexus device.
Press and hold Volume Up and Volume Down then press and hold the Power button; the device will now enter "fastboot mode".
Go to Device Manager (Computer -> Properties -> Device Manager in Windows 7/8) and identify the device; for me it shows up as Android 1.0.
Right click Android 1.0 and select "Update Driver Software," then select "Browse my computer for driver software".
Select "Let me pick from a list of device drivers on my computer," then click "Next".
From "Have Disk..." option go to the folder where you have Google USB Driver installed (for me it's "C:\Program Files .(x86)\Android\android-sdk\extras\google\usb_driver" and select "android_winusb.inf".
Out of the three options select "Android ADB Interface" and validate any future warning window to install the driver.
Final preparations
Everything is prepared in order to start the installation process, but in order to do so a command window must be opened. Windows Key + R opens "Run"; type in "cmd" and the command window appears. Typing "cd C:\Root" and pressing Enter sets the "Root" folder as the working directory. Pressing the Shift key and right clicking inside the "Root" folder will also deliver the same result.
The device must be turned on in "fastboot mode" which I have explained at step no.2 during the driver installation process, and obviously plugged-in to the computer. You then have to type in the following commands while in "fastboot mode":
fastboot devices -- this is just for verification purposes; if there is no listed device then the drivers have been improperly installed and steps 1 through 7 must be redone.
fastboot oem unlock -> you have to accept the prompt in order to continue -- this command will unlock the bootloader, but it will also erase the data on the device which is why a backup is necessary.
fastboot reboot-bootloader -- this will reboot the bootloader.
fastboot flash recovery openrecovery-twrp-2.3.1.0-grouper.img -- this will flash the custom recovery --please use the specific file and name for your particular Nexus device!
fastboot erase cache -- this will erase the cache -- might not be necessary but it's just as a precaution.
fastboot reboot -- this will reboot the device.
After Android 4.2 is loaded and running the SuperSU file must be copied from the "Root" folder to the internal storage (shows up in Windows Explorer as a Nexus device). A simple copy and paste will do the trick here.
Then you have to power off the Nexus device and enter "fastboot mode" again. Use the Volume Up and Volume Down keys to navigate until you can select "Recovery Mode". After the power button is pressed the device will reboot in the new custom recovery.
Rooting your Nexus device
If you have ClockworkMod installed, you have to perform the following steps:
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select "0" (zero) folder
Select "CWM-SuperSU-v0.97.zip"
Select "Yes - Install CWM-SuperSU-v0.97.zip"
Select "Go Back"
Select "reboot system now"
If you have Team Win Recovery Project installed, you have to perform the following steps:
Press "Install".\
Select "CWM-SuperSU-v0.97.zip" -- for me it's in the "0" (zero) folder
Swipe to confirm flash
Press "Wipe cache/dalvik" (just as a precaution)
Swipe to wipe
Press "Reboot System"
After Android 4.2 loads your device can run apps with elevated privileges (meaning it's rooted). A SuperSU app is installed in order to allow root requests, so please use your judgement on which apps you grant access.
If you experiences any problem, please reply and I will look into it.
Sent from my Nexus 7 using xda app-developers app
Sent from my Nexus 7 using xda app-developers app
^^you want him todo that, lmao, he doesnt even know how to put a file on his sdcard to flash it in recovery, theres no way a computer newb is going to be able to follow what you posted
That's why I have not used the word flash anywhere, I know that he does not know how to flash , I have posted the right thing for a total noob,( at least if he knows how to use command in windows or install drivers)
I helped him in the way I could and what he requested
Sent from my Nexus 7 using xda app-developers app
You think that helped. LOL. Your telling him to do things that aren't even required to gain root with this device. Not everything is a nexus bro. Next time you wanna help study up on the phone your giving advice about. lol
Well , thanks for telling me that every android isn't rooted in same manner, I was thinking that all devices are rooted in same ways like for my nexus
Sent from my Nexus 7 using xda app-developers app
naman14, im not putting you down, your step by step howto is admirable, good work, but the problem is that the op is clueless on tech stuff, its not the word "flash" he has a problem with, i could of said "install" and it would lead to same conclusion, he doesnt know how to copy a file to his sdcard, if he cant do that he has no business in modding his phone until he learns more. anyhow the op is long gone by now
I upgraded my samsung skyrocket s2 version 2.3.6 to 4.0.4 through the Kies. Then I tried to install TWRP 2.2.0 and Odin 1.85. I saw COM 14 ; COM 17 when I hit start button .It said
FAILED. Now it showed a yellow triangle in the middle of phone & monitor pictures. ( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again). Please help . Thank you very much.
I just tried other laptop . I saw COM 3 but it said it couldn't open the serial (COM )port . All thread completed (success 0/ failed 1)
So I changed from CM11 to Omni. With omni twrp got installed automatically... Then I didn't like omni and flashed CM11 again. But then my Xperia Z didn't get any cellular signal, so I couldn't do phone calls, receive phone calls etc... Then I thought about flashing CWM again. It worked, flashed CM and everything was working perfectly! But then after reboot into CWM, it booted into twrp.
No matter what I do, twrp gets it way through somehow. I wiped everything, even formatted data (twice)...
The problem with twrp is, that after updating the CM the cellular thingy doesn't work (sorry don't know what it's called in englisch)
TWRP doesn't work with CM11 on my xperia z, CM 10.2 was just fine... but I want CM 11
I installed CM11 on my nexus aswell, there I haven't got any problems at all. The updates work just fine, and no twrp is being installed.
Ohh
I am a real noob... formulate your help as easy as possible
EDit:
I am using philz version of cwm. But that's not the problem, is it?
success (hopefully)
I think I figured out myself...
Will update this post if so
So everything works fine again.
This is what I did:
1. Flash stock rom by using flashtool
2.
Installing CyanogenMod on Sony Devices
Note:
Some devices do not have removable SD cards. Regardless, there should still be a partition on the device named "/sdcard" that can be used for flashing purposes, even though the contents of /sdcard may actually be in internal storage.
Download the prebuilt release of CyanogenMod you wish to install. (Or if you've built CM yourself, look in the $OUT directory for the .zip.)
Optional: Download any supplemental 3rd-party applications packages for the device you wish to use. (You have to install a 3rd-party app to get the Google apps, like Gmail, Play Store, and Youtube.)
Extract the boot.img from the zip to your computer, you will need this file for fastboot.
Place the CyanogenMod rom .zip file on the root of the SD card.
Optional: Place any supplemental packages' .zip file on the root of the SD card.
Put the phone into fastboot mode:
With the device powered down, hold Volume Up and connect the USB cable. The notification light should turn blue to indicate you are in fastboot mode.
Open a terminal on the PC and enter the following:
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
While the device reboots, press the Volume rockers a few times to load recovery.
Once the device boots into the ClockworkMod Recovery, use the physical volume buttons to move up and down. On most devices, the power button is used to confirm your selection, although for some devices the power button is used as a "back" button to go up one level, in which case the home button is used to confirm the selection.
Optional/Recommended: Select backup and restore to create a backup of the current installation on the Xperia Z.
Select the option to wipe data/factory reset.
Select Install zip from sdcard.
Select Choose zip from sdcard.
Select the CyanogenMod file you placed on the sdcard. You will then need to then confirm that you do wish to flash this file.
Optional: Install any additional packages you wish using the same method.
Once the installation has finished, return back to the main menu, and select the reboot system now option. The Xperia Z should now boot into CyanogenMod.
Click to expand...
Click to collapse
http://wiki.cyanogenmod.org/w/Install_CM_for_yuga
Click to expand...
Click to collapse
3. update via Cyandelta updater (Takes less time)
4. Checked if twrp hasn't been installed
5. got happy
6. checked if cellular thingy is working
7. happy^2
It's been a rough morning over here.
I've had a lot of issues with the latest update (12.1) so I decided to download the .zip for CM12s and install it from recover - the exact same way I updated it initially (before I got the 12.1 OTA update).
I used the same .zip file from before, builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-signed
After installing from internal storage from the menu, it seems to install fine, and then it takes me back to the menu and I select Restart System.
After 20 minutes looking at the Cyanogen boot logo, I'm assuming it's stuck.
When I plug the phone into the computer, it says it's charging but neither Windows or my Chromebook recognize the device to allow file transfer.
If I press down+power, I can still get to the Cyanogen menu, but without a new .zip file I'm not sure what else to try.
Any advice? I'm pretty worried!
nagem145 said:
It's been a rough morning over here.
I've had a lot of issues with the latest update (12.1) so I decided to download the .zip for CM12s and install it from recover - the exact same way I updated it initially (before I got the 12.1 OTA update).
I used the same .zip file from before, builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-signed
After installing from internal storage from the menu, it seems to install fine, and then it takes me back to the menu and I select Restart System.
After 20 minutes looking at the Cyanogen boot logo, I'm assuming it's stuck.
When I plug the phone into the computer, it says it's charging but neither Windows or my Chromebook recognize the device to allow file transfer.
If I press down+power, I can still get to the Cyanogen menu, but without a new .zip file I'm not sure what else to try.
Any advice? I'm pretty worried!
Click to expand...
Click to collapse
Have you tried using fastboot to flash the stock images?
Are you using twrp?
1.I suggest installing twrp vor any recovery you like.
2. Than redownload rom and gapps (just to be sure)
3. Mount your device as mtp storage in twrp and put Rom and gapps in it
4. Than wipe /system /data /cache
(data wipe will delete all apps, your internal storage will be untouched)
5. flash rom and gapps
6. reboot your phone
If that does not help try Heisenbergs solution.