Related
i chose to start this thread as an educational and informative way of answering simple question so new questions arent repeatedly asked.
first off try to use the search window as much as possible before you post a question, chances aer your question has been asked before, so you will find the answer somewhere.when you do have to post a question be patient, the answer will come either in the form of an informative response or with a link to an informative response.
in every thread or be it for a rom ,a mod a theme etc. there are instructions. follow them to the letter and you shouldnt have any problem.
most importantly, be grateful to the devs or members which might assist you , at least say thank you and hit the thanks button, and donate if you can. these individuals work very hard at what they do here to provide you with the information and freedom you need to do what you want to do with your HEROC.
say thanks,,,its not that difficult.
Root your HTC HERO200 CDMA...
there are many different methods of rooting your device, it depends on your particular device.
they all work you simply have to find the one that works for you. for instance myself i use the regawmod one click method. (thanks regaw) when
i tried to use it on an associates device it didnt work...you have to find the method that works for your device.
youll find the files and programs you need to perform whatever procedure you choose to try on the developers page.
make sure you read the instruction completly before you begin. when you do begin follow the instruction to the letter and you shouldnt have any problem.once again, dont get piussed at the dev because it didnt work, its not that the procedure doesnt work, it just didnt work for you...simply search for another method and try again.and you will succeed.
i was going to post some of the methods but dont have permission from the devs to do so, so for now youll have to search for the precedures yourself. if or when i do get permission ill edit this thread or post the link in order to help yo on your way,,,ehhh for now itll be good practice for using the search window.
method 1.
hhttp://www.gadgetsdna.com/how-to-root-htc-hero-cdma-stock-android-2-1/3628/
The HTC Hero 2.1 exploit is based on the EVO rooting method. Rooting HTC Hero Android phone provides full access to its system files allowing you to modify the phone’s firmware and install third party apps, themes and custom ROMs. You can then spruce up your HTC Hero handset with number of third party applications.
How to Root Sprint’s 2.27.651.5 Release for CDMA Hero (Stock Android 2.1)
Note: If you already have the Android SDK and HTC Sync set up on your computer, skip to Step 4 now
Step 1: Download the Android SDK.
Step 2: Extract the Android SDK zip. Move the contents of the extracted zip to C:\
Your Android tools folder path should now be C:\android-sdk-windows\tools
Step 3: Download HTC Sync 2.0.33 here. Run the installer, and reboot your computer when it is finished. Skip to step 4 once rebooted.
Step 4: Download the hero-root.zip. This zip contains everything you need to root your Hero.
(md5: c6e5058ed14f71c68fb099e10be142fb)
Step 5: Extract the 3 files inside hero-root.zip to the C:\android-sdk-windows\tools folder on your computer.
Step 6: Make sure USB Debugging is ON (checked) on your Hero. Navigate to Settings > Applications > Development > and make sure it is checked
Step 7: Plug your phone into the computer via USB, Make sure that the connection type in the Notification Pull-Down Bar is “Charge Only”, not “Disk Drive” or else this won’t work. You may restart your comuter when prompted to do so.
Step 8: Open a Command Prompt window by clicking the Start button and typing cmd into the search box and pressing enter. Alternatively, navigate to Start Menu > All Programs > Accessories > Command Prompt
Step 9: You enter the commands followed by pressing ENTER, one code at a time.
1 cd C:\android-sdk-windows\tools
You should now see C:\android-sdk-windows\tools>
Now type
adb devices
You will now notice your HTC Hero phone’s serial number. If you get “device not found” error, you either need to make sure you the drivers were properly installed or make sure you enable USB debugging on your phone. Continue on once you get the proper phone serial output.
You will now push the files needed to gain root to your sdcard in your phone with these following commands one by one:
adb push unrevoked /sdcard
adb push recovery.img /sdcard
adb push boot-patched.zip /sdcard
Now we run the exploit. Be patient, this may take up to 40 seconds.
adb shell
sh /sdcard/unrevoked
You should now see output that says this:
UNREVOKED
============================================================ unrEVOked: root for HTC evo and hero (http://unrevoked.com)
Now, on your phone, go to your app tray, and you will see that the Superuser Permissions app is in it, which is only possible on rooted devices.
Open the Superuser Permissions app. You will see a blank screen.
In the Command Prompt on your computer, type:
A prompt will appear on your Hero asking you to give /system/bin/sh privileges. Click Allow.
Go back to your command prompt, and you should see
$ su su #
Now Type
flash_image recovery /sdcard/recovery.img
Flashing the recovery may take many seconds to complete. Wait until the # symbol returns to proceed.
You should now see
# flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
#
This means it was a successful flash.
Now type
reboot recovery
Your phone will now boot to the custom recovery image you just flashed. In the Recovery Menu on your phone, choose the option:
Flash zip from sdcard
Then Select
boot-patched.zip
and press the Home button to apply. Once Recovery says “Install from sdcard complete” select “Reboot system now” from the menu.
Voila!! You now have full root access on HTC Hero 2.1!
Thanks to the guys at xda-developers and gadgetsdna
or, you can try regaw's one click root method. you can find it here on Xda, just use the search window,,,it's easy
both of these methods have worked well for me in the past, im sure one of them WILL work for you
-----------------------------------------------------------------------------
Flashing a ROM (from clockworkMod)
this is the method i use and i "never" have any problems
download the ROM of your choosing and move to the root of your sdcard
follow the devs instruction for installation which should be something like this;
1. do a nandroid backup
2. reboot into recovery
3. wipe data
4. wipe cashe
5. choose advanced, wipe dalvik
***OPTIONAL***
6. choose mounts and storage
7. format system
8. format data
9. formatcashe
10. go back. and choose install zip from sd card
11. choose, choose zip from sd card
12. find the rom you want to flash and choose yes
13. when its through flashing choose install zip from sd card
14. find the gapps you want to flash and choose yes
when its through with the flash the screen will return to the main menu and choose reboot system
the first boot will take a little longer than usual this is normal. setup your google s#@ts as usual and enjoy your new ROM.
follow these instructions and you shouldnt have any problems, if you do, go back to the thread you downloaded from post a reply to report it to the dev so they know theres a problem and they can determine if its a problem with the rom, a problem with the way you flashed or a problem with your system.
15. "ONCE AGAIN" most importantly, be grateful to the devs, at least say thank you and hit the thanks button, and donate if you can.
these individuals work very hard at what they do here to provide you with the information you need to do what you want to do with your HEROC.
say thanks,,,its not that difficult.
-----------------------------------------------------------------------------
themeing your new ROM
1. make sure the theme you choose is compatable with the rom you have flashed
2. since alot of the themes have a different procedure for installation,"READ AND FOLLOW THE DEVS INSTRUCTIONS"(sorry for the caps)
they are there for a reason.
-----------------------------------------------------------------------------
boot animations
1. Put the zip file in your tools folder from the android-sdk-windows
2. Load up Command Prompt (cmd) and go to your tools directory inside the android-sdk-windows folder
3. Load up your phone into recovery and mount /system
4. Type in command prompt
adb remount
adb push bootanimation.zip /system/media
adb reboot
or (compliments of user7618)
Boot animations are easier to change by sliding the .zip into /system/media or /data/local. That way, there is no need for adb commands, just a file explorer like root explorer. Make sure that it is named bootanimation.zip.
-----------------------------------------------------------------------------
Flashing a different recovery image
cd C:\android-sdk-windows\tools...got
cd C:\android-sdk-windows\tools>adb devices...got
(recognized phone)>>>>>
cd C:\android-sdk-windows\tools>adb shell
#flash_recovery image /sdcard/recovery-clockwork-4.0.0.2-heroc-20110611.img (enter)
mtd: successfully bla bla bla
#reboot....
or,,,
[edit] Method I
Flash recovery using: ADB
NOTE: This method will work while you are booting into the current recovery on the phone.
1.Download the ClockworkMod Recovery: HeroC Download Optimus V Download.
2.Copy the recovery.img to root of the SD card.
3.Boot the phone into recovery.
4.Open command prompt, cd to the Android SDK directory & type the following commands:
adb shell
mount /sdcard
flash_image recovery /sdcard/"name of recovery".img
reboot recovery
5.Your phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
[edit] Method II
Flash recovery using: RomManager
1.Download the ClockworkMod Recovery: HeroC Download Optimus V Download.
2.On the SD card, go to /clockworkmod/download/koush.tandtgaming.com/recoveries.
3.Rename the old image there named recovery-clockwork-2.5.0.1-heroc.img to recovery-clockwork-2.5.0.1-xxx.img.
4.Move, then rename, the recovery.img you downloaded to recovery-clockwork-2.5.0.1-heroc.img.
5.Open RomManager and press Flash ClockworkMod Recovery and reboot the phone to recovery, you should see the orange text.
[edit] Method III
Flash recovery using: Terminal Emulator Note: Requires s-off, otherwise you'll recieve "out of memory" errors.
1.Download the ClockworkMod Recovery: HeroC Download Optimus V Download.
2.Move recovery.img to root of the SD card.
3.Open the Terminal Emulator on the phone & type the following commands:
4.:
su
flash_image recovery /sdcard/"name of recovery".img
reboot recovery
5.The phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
[edit] Method IV
Flash recovery using: H-Boot/S-Off Only HeroC Only
See S-Off for CDMA Hero if you are unsure what S-OFF is.
1.Download HERCIMG.zip
Newest Download: (version 3.0.5) HERCIMG.zip <--Updated 01212011
md5: 6dcd265a51cc7090824d7f9f889b370b
Alternate Download: (version 2.5.0.7) HERCIMG_clockwork-2.5.0.7 <--Updated 02-07-2011
md5: 0a367eb1d4445c72f8022769f7edc9dd
2.Move HERCIMG.zip to root of the SD card. Make sure the file is named HERCIMG.zip or H-Boot will not recognize it.
3.Power off the phone.
4.Hold the Volume Down & Power' button until the phone boots into the bootloader.
5.Wait for bootloader to scan and find HERCIMG.zip.
6.Press action to install.
7.The phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
Retrieved from "http://romrepo.info/wiki/index.php?title=Flash_the_ClockworkMod_Recovery"
-----------------------------------------------------------------------------
Change sprint insignia (ON AOSP) to whatever you want
1. Download eri.zip
2. Unzip the file to wherever you please.
3. Right click on eri.xml and choose "Open with Notepad"
4. Once you open the file you will see "Sprint" in the 5th line.
5. Delete Sprint and place whatever you would like in it's place. I believe you have up to 16 spaces to work with if need be.
6. Save the file with an .xml extension. Important: Make sure it is eri.xml and not eri.xml.txt. This will cause issues.
7. Place the eri.xml in your /androidsdk/tools directory.
8. Pull up your Command Promt/Terminal/Etc
9. CD to your /androidsdk/tools directory and:
adb remount
adb push eri.xml /data/eri.xml
adb reboot
or, (thanks to user 7618 )
I threw together a simple app to change the Carrier Name in the status bar/lockscreen to whatever you want since my alot of people seem to ask how to change it. Feel free to use it. Tested on Incredible and Eris. Dev's feel free to thow it your roms if you want. No ads and free just a simple tool to change the text. Thanks to the great Eris community.
Currently only works for AOSP roms such as cyanogenmod.
V1.3
While trouble shooting some radio issues on a rom I realized there's no need to reboot the phone to apply the new carrier name. I only needed to cycle the radio so I changed the app to toggle airplane mode on and then back off after you input your text so the change should take place immediately. This should make it a little easier to test and try different things or just change it more often.
I also added some shortcut buttons at the bottom to quickly add the text for the ", < and > signs so you don't have to type it all out. Only tested this with cm7 but should still work with any rom's it worked with before. Again thanks to Psiphon for pointing these symbol fixes out.
http://www.multiupload.com/RO6RZUUL16
V1.2
Fix for phones that don't already have an eri.xml file there
Added version number to bottom of screen so people can be sure what version they are running.
http://www.androidphiles.com/files/g.../ccname1.2.apk
V1.1
Fixed force closes when using symbols.
You can now use symbols except for double quotes. Apostrophe (single quote) seems to work fine.
Some usefull info if you want to use quotes....
Originally Posted by Psiphon
You can use special characters like the quotation marks and greater/less than signs by using entity references (either using an entity name or number):
" (quotation mark) use "
< (less than sign) use either < or <
> (greater than sign) use either > or >
I hope this helps!
Added Toast popup to let you know the name has been set.
If reboot button does not reboot phone just reboot the phone manually
http://www.androidphiles.com/files/g.../ccname1.1.apk
This app does one thing. It takes the input text you type and creates and eri.xml file and puts it in data/ folder on your phone. Then you can reboot for change to take effect. You can uninstall the app after you change it if you want or you can leave it on there(it's pretty small) in case you like to switch it every now and then. If you flash a new rom you will have to rerun the app.
-----------------------------------------------------------------------------
hopefully there will be more info in the future to add to this thread that will make things easier for everyone all around.
-----------------------------------------------------------------------------
***TO ALL DEVS AND OTHER MEMBERS*** i myself cant thank you enough for the help and advice ive recieved in the past, if you might hace any information you feel would be helpful to this thread please feel free to PM it to me and ill see that i edit this post with your procedures. and ofcourse your names will be added to a list of thanks at the bottom of the post,,,Thanks again,
THANX FOR THEIR HELP TO ME IN THE PAST;
flipz
coffeehandle
MattCrystal
laie1472
user7618
PMGRANDS
kushdeck
bierce22
conap
psiphon
kifno(aspentree)
-----------------------------------------------------------------------------
all of the information i have provided here has been compiled from Devs and other membes in order to assist new memberslike myself , and to help the devs and senior members so they dont have to keep answering the same questions again and again.
*** i f you want to thank someone, thank them for passing on their knowlege to me as im passing it on to you***
enjoy,,,
please dont double post
Nice beginners guide.
-----
3vo. That is all that needs be said.
Nice beginners guide.
Also, an easier way to change the carrier banner:
http://forum.xda-developers.com/showthread.php?t=960099
Instead of all that goofy crap with files and whatnot.
Boot animations are easier to change by sliding the .zip into /system/media or /data/local. That way, there is no need for adb commands, just a file explorer like root explorer. Make sure that it is named bootanimation.zip.
-----
3vo. That is all that needs be said.
Thanks man ill keerp adding, i really hope this helps some folks
Kudos. Good guide.
#Root/Hack-Mod_Always*
Also we dont talk about "he who must not be named" around here so you might want to take that out of the credits.
lai and user know who im talking about lol.
Uhhhhh,,,Ooops. My bad....sorry bout that guys.
ha lol i was just kidding but seriously that guy went bannanas and had a severe case of schizophrenia lmao.
lol, i hear ya man, i feel credits given where credits due, but on the other hand,,,,aw well you know what i was gonna say
Yeah, dude was crackers, but if he helped you, then he helped you. I'd leave him in there, personally.
-----
3vo. That is all that needs be said.
Yup agreed. A if he helped he helped that's just how it is. Like the guy or not.
#Root/Hack-Mod_Always*
cool guys i do feel the same way, but dont wanna stir any bees nests either, ill put it back in but we'll just overlook it. thanx for understanding
If you are new to rooting your phone, there are simple ways to go about getting clockwork mod onto your LG thrill
You can root it easily with the 1 click root tool (I dont have the link on hand) after installing the LG Drivers from the LG Website.
Then, Download Rootexplorer, Rom manager (which i think is installed with 1 click root along with superuser)
First thing, download the recovery.img here after installing ADB guide is located here
After downloading recovery image, go to your pc's user folder C:\users\yourname and move it to there, that way there is no mistaking its location for adb
Now, on your phone you first need to go into root explorer, go to the /data folder, long click and go to permissions and select all available boxes and also make sure your device is in R/W mode not R/O mode.
Run CMD as administrator and do the following:
adb push recovery.img /data
then type:
SU
(this makes superuser active)
then:
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
then after clockwork is flashed to finalize the settings type:
rm /data/recovery.img
reboot
Presto, Clockwork Mod is installed, remember you can access the clockwork menu via rom manager menu, or 3D+Volume Down +Power releasing the power button when the LG screen appears.
I will soon post onto this, how to update to gingerbread just making sure it works well on my own first. also, working on ICS as well.
Hope this helps anyone who has had trouble with it!
kobos311 said:
If you are new to rooting your phone, there are simple ways to go about getting clockwork mod onto your LG thrill
You can root it easily with the 1 click root tool (I dont have the link on hand) after installing the LG Drivers from the LG Website.
Then, Download Rootexplorer, Rom manager (which i think is installed with 1 click root along with superuser)
First thing, download the recovery.img here after installing ADB guide is located here
After downloading recovery image, go to your pc's user folder C:\users\yourname and move it to there, that way there is no mistaking its location for adb
Now, on your phone you first need to go into root explorer, go to the /data folder, long click and go to permissions and select all available boxes and also make sure your device is in R/W mode not R/O mode.
Run CMD as administrator and do the following:
adb push recovery.img /data
then type:
SU
(this makes superuser active)
then:
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
then after clockwork is flashed to finalize the settings type:
rm /data/recovery.img
reboot
Presto, Clockwork Mod is installed, remember you can access the clockwork menu via rom manager menu, or 3D+Volume Down +Power releasing the power button when the LG screen appears.
I will soon post onto this, how to update to gingerbread just making sure it works well on my own first. also, working on ICS as well.
Hope this helps anyone who has had trouble with it!
Click to expand...
Click to collapse
All of this is already posted as is the instructions on how to update to gingerbread.
i have install CWM by as your guide. but when i use Rom Manager to Back up , message pop up that install CWM first to complete this action. i am new to these things.
Thanks
This is the account of my foolishness and I advice everyone not to follow it.:::
1.installed Linux installer std and complete Linux installer from play store.
2.when the 2nd app failed to unmount and GUI crashed showing some errors with busybox, followed 3rd step.
3. found the embedded busybox from 1st app n directly placed it in /system /xbin
4. the original busybox is gone n everything is fine but got too many errors in reading root directory of phone. None of the file manager is showing me root.
5. I'm suspecting that it has done something wrong with my cwm recovery as well for which I can't take a chance of bricking my phone.
6. NOW I need kind advice of u ppl on how to confirm the presence of recovery.img or whatever it should be to recover my cwm backed up data.
boot into recovery, if recovery do not boot then pull battery and start the mobile it will start normally, download busybox installer from play store (the one from stephen)
install busybox through the app(busybox problem will be solved)
download tass recovery cwm.tar file and flash with odin you will get cwm recovery back
did it
I've already tried busybox installers. non of them worked cause the whole root directory is unreadable to any of my apps except diskusage n similar things those show memory occupied.
then you should flash firmware and root again
Superuser
maybe update superuser binary?
solved
chmod 777 path name n got busybox 1.12
You lost root access because there is no busybox. Reflash the ROM. Easy way out.
nothing lost at all just replaced.
as I've stated the command above u, it was just a busybox w/0 permissions. I was getting permission denied.
thanks to Gael péron for his Help.
**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..
jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.
mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options
You have .bat file in the package.
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions
I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?
I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app
mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app
can I install image-nakasi-jop40c.zip directly without upgrading bootloader?
Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.
Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!
Update 11-26-2012
The issue that this procedure was designed to overcome has been resolved in the latest version of CWM (6.0.1.9 or newer). Please view http://forum.xda-developers.com/showthread.php?t=1781899 for details and download links. If you do not want to upgrade to the latest CWM the directions below will still work but you should really just update.
Background
Due to the multi-user support capabilities of Android 4.2(+) the clockworkmod directory created by ClockworkMod and used to store downloads and backups is being created in /data/media. Unfortunately this directory is not accessible to individual users and therefore backups created in recovery can not be viewed or modified by ROM Manager and vice versa. ROM Manager will look for the directory /data/media/<user number> (e.g. /data/media/0) to which /sdcard is mounted when you are logged in as the user whose number is <user number> (e.g. 0).
Requirements
ClockworkMod Recovery installed and functioning
ROM Manager
ADB installed on your computer and functioning
Willingness to accept that you are on your own and I am not responsible if you mess something up!
Solution
1. Boot into CWM recovery
2. Attach your Nexus 7 to your computers USB port
3. Open an ADB shell using a console from your computer
Code:
adb shell
4. Confirm that you have a clockworkmod directory at /sdcard/clockworkmod (I am using user number 0 for the rest of this procedure, if you wish to use a different user substitute 0 with your user number)
Code:
cd /data/media/0
ls
4a. If you do not see a clockworkmod directory create one with the command below, otherwise proceed to step 5
Code:
mkdir /data/media/0/clockworkmod
5. See if you have a clockworkmod directory at /data/media
Code:
cd /data/media
ls
5a. If you see a clockworkmod directory type the command below, otherwise proceed to step 6
Code:
mv clockworkmod clockworkmod_bak
6. Create the symbolic link
Code:
ln -s /data/media/0/clockworkmod/ clockworkmod
7. If you already had backups in clockworkmod (now clockworkmod_bak) you can move them to the new folder by executing the following command
Code:
mv clockworkmod_bak/backup/ clockworkmod/
mv clockworkmod_bak/blobs/ clockworkmod/
mv clockworkmod_bak/download/ clockworkmod/
WARNING: I tested a backup from recovery and verified the backup was in ROM Manager, renamed the backup in ROM Manager, and confirmed the backup was renamed in recovery. Due to time constraints I did not restore the backup though I can't imagine why it would fail. As mentioned above do this at your own risk. If you do not have a unix/linux experience I would suggest that you wait for someone with experience to follow these steps (I wrote them after I did the procedure so they haven't been vetted) before you attempt it yourself.
Very helpful, i was wondering what they did to mess up clockwork mod
been trying to undo 4.2 for hours as i dont quite like it
truehybridx said:
Very helpful, i was wondering what they did to mess up clockwork mod
been trying to undo 4.2 for hours as i dont quite like it
Click to expand...
Click to collapse
I am on the fence about 4.2 myself and when I couldn't see my 4.1.2 backup I had a panic moment. I have to admit that either 4.2 is growing on me or I am already forgetting how good 4.1.2 was .
sandnap said:
I am on the fence about 4.2 myself and when I couldn't see my 4.1.2 backup I had a panic moment..
Click to expand...
Click to collapse
+1! Panic indeed! LOL
Great tutorial. Thanks and have a happy thanksgiving
Is there a way to do this without using adb? I don't know how to get it working.
It looks like you are just moving all the files from one location to another, right? If thats the case can I just move them with a file explorer? Also where are the back-ups from pre 4.2 stored, I thought it was sdcard/clockworkmod/ Can I move the back-ups from there to a data/media/clockworkmod folder?
StarOrc said:
Is there a way to do this without using adb? I don't know how to get it working.
It looks like you are just moving all the files from one location to another, right? If thats the case can I just move them with a file explorer? Also where are the back-ups from pre 4.2 stored, I thought it was sdcard/clockworkmod/ Can I move the back-ups from there to a data/media/clockworkmod folder?
Click to expand...
Click to collapse
Please see my update to the original post. Once you update to the latest CWM you can copy any existing backups to the new backup and blobs folders under /data/media/clocworkmod. This is discussed in more detail in the thread I linked to.
Code:
mv clockworkmod_bak/backup/ clockworkmod/
mv clockworkmod_bak/blobs/ clockworkmod/
mv clockworkmod_bak/download/ clockworkmod/
This is me just being nit picky, but this looks better:
Code:
mv clockworkmod_bak/* clockworkmod/
I guess for people not confident in their linux abilities that '*' misplaced could be deadly though...anyway thanks for the simple and great workaround/explanation.
Wiping/ Factory resets (in CWM or TWRP) don't erase this data folder? Are we confident in this?
255|[email protected]:/data/media/clockworkmod # mv backup/ /sdcard/clockworkmod/
failed on 'backup/' - Cross-device link
How are you able to move the directories?
This seriously annoys me. Despite the recent surge of newer android devices not containing any sd card slots for secure file storage away from ROM flashing, everything is now embedded. I have had several accidental internal storage deletions containing backups and roms and no the clockworkmod is even harder to locate and backup conveniently through usb/ftp. Thanks for the tut.
TheAtheistReverend said:
Wiping/ Factory resets (in CWM or TWRP) don't erase this data folder? Are we confident in this?
Click to expand...
Click to collapse
Yeah i am wondering that too.it doesnt feel safe for me that the backups are in the system but not in sdcard.
nexus file locations
On the nexus devices (certainly the 7, which has no external sdcard), the only real mounted portions are cache, system and data. Locations like /sdcard/ /storage/emulated/0 etc. are all fuse mounted from /data/media
Supposedly most of the data portion will survive flashing new ROMs and recoveries, everything except unlocking the boot loader, which wipes data f to meet the android security model.
Doesn't feel very safe, though.
amp said:
This seriously annoys me. Despite the recent surge of newer android devices not containing any sd card slots for secure file storage away from ROM flashing, everything is now embedded. I have had several accidental internal storage deletions containing backups and roms and no the clockworkmod is even harder to locate and backup conveniently through usb/ftp. Thanks for the tut.
Click to expand...
Click to collapse
I would use TWRP. I have switched and never looked back. It has quite a few more advanced options that I didn't see with clockworkmod, and overall has be MUCH more reliable.
The clockworkmod recovery issue stated in this thread does not affect TWRP at all.
Thanx for this, it seems to work even for the latest CWM.
Sent with desire from My One
angusc said:
Thanx for this, it seems to work even for the latest CWM.
Sent with desire from My One
Click to expand...
Click to collapse
Iget an error: Read-only File system :crying:
fokus said:
Iget an error: Read-only File system :crying:
Click to expand...
Click to collapse
If doing commands with adb did you remember to use
adb shell
And check that your command line starts with #......
Sent with desire from My One
angusc said:
If doing commands with adb did you remember to use
adb shell
And check that your command line starts with #......
Sent with desire from My One
Click to expand...
Click to collapse
Yes, that is exactly what i did.
I am on ARHD 11.0
S-off
ElementalX 2.2
I'm on ARHD 11.0 as well.
Strange, I followed the OP from step 1 to 6. I couldn't get step 7 to work so I just used my root explorer to copy the directory contents across in to the newly created clockworkmod folder, then deleted the clockworkmod.bak directory and all was good.
Tip: copy and paste each cmd from the OP in to your adb commands window......
Sent with desire from My One
angusc said:
I'm on ARHD 11.0 as well.
Strange, I followed the OP from step 1 to 6. I couldn't get step 7 to work so I just used my root explorer to copy the directory contents across in to the newly created clockworkmod folder, then deleted the clockworkmod.bak directory and all was good.
Tip: copy and paste each cmd from the OP in to your adb commands window......
Sent with desire from My One
Click to expand...
Click to collapse
THX. That is what i did. I also tried it via Terminal on the device - same error: System read only... hmmm
EDIT: Works fine now after e vew reboots. THX