Related
hey guys right now im using darchstar's godspeed recovery.. but whats the most recommended recovery mode that everyone uses?
My personal favorite is Clockwork Mod Recovery. You can find the latest for our phone in the Andorid Development section, on the first page of the aospGBmod thread. Should be easy to find as it is right on top 99% of the time due to popularity.
DARCH All the way if your running GB then clockwork because I've read people have had problems with Darch's recovery with GB but if your running CM6 then stick with Darch
Root-Hack-Mod-Always™
laie1472 said:
DARCH All the way if your running GB then clockwork because I've read people have had problems with Darch's recovery with GB but if your running CM6 then stick with Darch
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
Anyone Have The Apk. Or Zip File For Darch's Recovery?
Sent from my HERO200 using XDA App
PMGRANDS said:
Anyone Have The Apk. Or Zip File For Darch's Recovery?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I got it off of darch's website but it's been down as far as I know for a little while now.. Luckily I backed it up on my dropbox when I first downloaded it
I attached it so it'll be on XDA for everyone
Download the Darchstar_ra.zip and extract it onto the root of your sdcard.
Boot up into your rom
Open up terminal emulator and enter the following:
Code:
su
flash_image recovery /sdcard/darchdroid_ra.img
reboot
2 questions will this restore previous RA nandroids and also can this do the complete wipe like clockwork?
kyouko said:
I got it off of darch's website but it's been down as far as I know for a little while now.. Luckily I backed it up on my dropbox when I first downloaded it
I attached it so it'll be on XDA for everyone
Download the Darchstar_ra.zip and extract it onto the root of your sdcard.
Boot up into your rom
Open up terminal emulator and enter the following:
Code:
su
flash_image recovery /sdcard/RA-Darchstar.img
reboot
Click to expand...
Click to collapse
sent from my twopointtwo themed hero
thoughtlesskyle said:
2 questions will this restore previous RA nandroids and also can this do the complete wipe like clockwork?
sent from my twopointtwo themed hero
Click to expand...
Click to collapse
I don't see why it would have problems restoring older nandroids, I've never had problems after updating.
And yes, you can wipe data/cache, cache, davlik-cache, battery stats, and rotation settings in the wipe menu.
I currently use ClockworkMod Recovery 2.5.0.1 for recovery mode.
Specs of my Sprint HTC Hero/APA6277 are...
Android version: AOSP
Baseband version 2.42.02.10.29,
Kernel version 2.6.29.6-aospMD [email protected] #1
Mode version: aospMOD-0.9.9.2
Build number: FRG83
I plan on flashing the AOSP GB Mod to my device as soon as a stable version of it becomes available.
kyouko said:
I don't see why it would have problems restoring older nandroids, I've never had problems after updating.
And yes, you can wipe data/cache, cache, davlik-cache, battery stats, and rotation settings in the wipe menu.
Click to expand...
Click to collapse
have you had any issues with wiping and flashing gingerbread because i didnt at first but lately it seems like its not a full wipe, then again im using a really old version of RA
kyouko said:
I got it off of darch's website but it's been down as far as I know for a little while now.. Luckily I backed it up on my dropbox when I first downloaded it
I attached it so it'll be on XDA for everyone
Download the Darchstar_ra.zip and extract it onto the root of your sdcard.
Boot up into your rom
Open up terminal emulator and enter the following:
Code:
su
flash_image recovery /sdcard/RA-Darchstar.img
reboot
Click to expand...
Click to collapse
Thanx A lot Kyouko!!
I Downloaded It....
But I Wanted To Pick Your Brain A Bit, Before I Flashed It.... Lol!
As I'm Sure You Know,
*Rom Manager* Has The Option "Flash Alternate Recovery" Which Switches The Users Recovery From Clockwork, To Amon_Ra, Right?
So I Guess My Question To You Is, What's The Difference Between This Recovery & The Other Two?
Is There More Features??
Oh, One More Thing.... Sorry!!
I Have A **** Load Of Backups From *Rom Manager* Will The Still Be Compatible, Since I Made'em With Clockwork?
Sent from my HERO200 using XDA App
thoughtlesskyle said:
have you had any issues with wiping and flashing gingerbread because i didnt at first but lately it seems like its not a full wipe, then again im using a really old version of RA
Click to expand...
Click to collapse
That issue was fixed in the newer RA versions (which includes this one and godspeed)
There was a problem wiping with the older RA after the cache location got moved in newer rom versions or something along those lines
PMGRANDS said:
As I'm Sure You Know,
*Rom Manager* Has The Option "Flash Alternate Recovery" Which Switches The Users Recovery From Clockwork, To Amon_Ra, Right?
So I Guess My Question To You Is, What's The Difference Between This Recovery & The Other Two?
Is There More Features??
Oh, One More Thing.... Sorry!!
I Have A **** Load Of Backups From *Rom Manager* Will The Still Be Compatible, Since I Made'em With Clockwork?
Click to expand...
Click to collapse
I'm not sure what the "flash alternate recovery" does because I only tried clockwork once and flashed over the recovery using terminal
As for features I took screens of each menu on the recovery
And I don't know what kind of backups rom manager does. If they're structured like nandroids it might work You may have to create a folder named "nandroid" and inside that folder create another and throw the backups in there. It'd be structured something like this:
/sdcard/nandroid/oldbackups/*folders go here*
And worst case scenario if they don't work but you really want all of them back you can just flash clockwork back to restore them.
kyouko said:
That issue was fixed in the newer RA versions (which includes this one and godspeed)
There was a problem wiping with the older RA after the cache location got moved in newer rom versions or something along those lines
I'm not sure what the "flash alternate recovery" does because I only tried clockwork once and flashed over the recovery using terminal
As for features I took screens of each menu on the recovery
And I don't know what kind of backups rom manager does. If they're structured like nandroids it might work You may have to create a folder named "nandroid" and inside that folder create another and throw the backups in there. It'd be structured something like this:
/sdcard/nandroid/oldbackups/*folders go here*
And worst case scenario if they don't work but you really want all of them back you can just flash clockwork back to restore them.
Click to expand...
Click to collapse
Darch's Recovery is an overclocked version of AmonRa with EXT4 Support. See here for more info
kyouko said:
That issue was fixed in the newer RA versions (which includes this one and godspeed)
There was a problem wiping with the older RA after the cache location got moved in newer rom versions or something along those lines
I'm not sure what the "flash alternate recovery" does because I only tried clockwork once and flashed over the recovery using terminal
As for features I took screens of each menu on the recovery
And I don't know what kind of backups rom manager does. If they're structured like nandroids it might work You may have to create a folder named "nandroid" and inside that folder create another and throw the backups in there. It'd be structured something like this:
/sdcard/nandroid/oldbackups/*folders go here*
And worst case scenario if they don't work but you really want all of them back you can just flash clockwork back to restore them.
Click to expand...
Click to collapse
Thanx For The Screenshots,
Now I'm Curious! And I Already Like The Way It Looks Better Than Clockwork! But To Be Honest Im A Little Nervous About Using ADB. Or Terminal Emulator!
Is It Easy/Hard?
I Heard You Can Brick Your Phone If You Enter A Command Wrong, Is That True?
Sent from my HERO200 using XDA App
PMGRANDS said:
Thanx For The Screenshots,
Now I'm Curious! And I Already Like The Way It Looks Better Than Clockwork! But To Be Honest Im A Little Nervous About Using ADB. Or Terminal Emulator!
Is It Easy/Hard?
I Heard You Can Brick Your Phone If You Enter A Command Wrong, Is That True?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
As long as you don't put "flash_image (BOOT or any other partition here)" you should be fine.
If you input it incorrectly it won't flash,
example: flashimage recovery /sdcard/darchdroid_ra.img
How to flash it via ADB:
Code:
adb shell
su
flash_image recovery /sdcard/darchdroid_ra.img
reboot
kyouko said:
As long as you don't put "flash_image (BOOT or any other partition here)" you should be fine.
If you input it incorrectly it won't flash,
example: flashimage recovery /sdcard/darchdroid_ra.img
How to flash it via ADB:
Code:
adb shell
su
flash_image recovery /sdcard/darchdroid_ra.img
reboot
Click to expand...
Click to collapse
followed the code lines for terminal emu and adb both times got Flash_img: not found even tried entering Darchstar_ra.img same error
thoughtlesskyle said:
followed the code lines for terminal emu and adb both times got Flash_img: not found even tried entering Darchstar_ra.img same error
Click to expand...
Click to collapse
Weird.. Do this for me, open up terminal emulator and type:
Code:
su
flash_image
you should get a return line saying:
Code:
usage: flash_image partition file.img
*see attached picture for example*
Make sure you're inputing it exactly the way I had it in the previous post - underscores and all. If the recovery.img name is different make sure whatever you type is exactly what the img is called.
If it's not in the /sdcard/ directory enter the correct one.
Example) /sdcard/downloads/oldrecovery.img
On my second attached picture you can see that the command worked, but since I already have that recovery flashed it aborts.
thoughtlesskyle said:
have you had any issues with wiping and flashing gingerbread because i didnt at first but lately it seems like its not a full wipe, then again im using a really old version of RA
Click to expand...
Click to collapse
I'd just use CW for Gingerbread, RA doesn't wipe boot or system I believe.
Does anyone know if you are able to Wipe Data/cache/dalvik from adb shell?
just making a script to automate the process.
anyone know the commands?
thanks
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
I initially looked for a complete update guide on here and eventually found all the information I needed, but it was in multiple places and sometimes hard to find. After getting everything installed on my N1 I thought I would write a guide for other noobs like me that want to try out ICS or JB but would like a step-by-step guide. I hope that it is helpful. SpazeDog ROMs (both ICS and JB) are working wonderfully on my N1 - its a very nice update from CM7 with only minor issues so far.
Note: this was initially written specifically for SpazeDog roms, but as they have not been updated in a while I have provided links to other popular roms as well. If you would like to try a different ICS or JB rom this guide should work, just substitute with the appropriate rom and depending on the one you choose, you may also need to install Google apps.
If you looking at this guide and don't know the basics yet, check out the Newbie Friendly thread first.
Links to popular roms that will work using this guide:
Evervolv JB 4.2
Evervolv JB 4.1
CM 10, JB 4.1.2 by vijendrahs
CM 10, JB 4.2.1 by vijendrahs
Spazedog ICS/JB
Disclaimer: This guide involves making changes to your phone that potentially could brick your phone leaving it unusable. I am not liable for any changes you make or problems you may have with your phone. You should at least be familiar with entering commands using command prompt. This procedure will erase ALL the data on your phone. Make sure you have a backup of everything. A nandroid backup is highly recommended. Proceed at your own risk.
Before we get started make sure you have the following: a rooted Nexus One, a USB cable to attach your phone to a computer, and the Android SDK. If you are just now installing the Android SDK, open the SDK manager and make sure to install the "Tools" and in "Extras" the "Google USB Driver" are checked off and download them. Alternatively, you just download ADB and Fastboot (search this forum or google). If you have a Mac see this thread to get started with ADB and Fastboot.
If you Nexus One is NOT already rooted, then follow this guide from Cyanogenmod to root your phone. If you plan to use the adb commands below (they are optional) make sure you have usb debugging enabled: go to "Settings" → "Applications" → "Development" → enable "USB debugging."
Step 1 - Download everything you will need:
4EXTRecovery Updater - the first link will download the .apk to your computer or phone.
BlackRose - go down to bottom of the first post to "Attached Files" and download the latest BlackRose zip file. If you don't want to do it yourself, check out this thread to flash a pre-made partition scheme. Often the developers (Evervolv) will also have a partition schemes that you can flash via Fastboot from your PC as well.
Your rom of choice - go to the downloads section and choose which rom you would like to try. Download the zip installation file.
Since you will be decreasing the size of your partition that apps can be stored on consider something like Mounts2SD or AD2SDX to move apps to your SD card.
Step 2 - Install and use 4EXTRecovery Updater on your phone:
The easiest thing to do is go to the 4ext link above, download and install it, directly from your nexus one. You can also install it by copying the APK file to your SD card, then using a file manager to find it and install it or you can use command prompt by opening command prompt, cd to the location of the Android SDK tools, and then type in the following command (replacing "path" with the path to where the APK is located on your computer):
Code:
adb install /path/4EXTRecoveryUpdater.apk
After you have installed 4ext open the 4EXT Recovery Updater. Tap "Settings" → "Allow" superuser request → "Yes" to connect to 4ext to get new data. Now select "Online install/upgrade" → "Yes" assuming it detects your nexus one correctly → select and install the latest 4ext recovery (at the top of the list).
After 4ext has installed, it will have placed a recovery image on your SD card - find it (its called recover.img) and it should be located in SD/Download/4EXT_Recovery_Touch/ folder. Copy this to your computer in case something goes wrong later and you need to re-flash the recovery image!
After installation of the 4ext recovery turn off your phone and boot into recovery by turning off your phone, turning it on again while holding the trackball down. This will boot into the bootloader, then press the power button once, use Volume Down to select "recovery" and press the trackball to select. Alternatively you can use the command prompt:
Code:
adb reboot recovery
Your phone should now boot into the 4ext recovery menu. Before moving on make sure you have any important stuff backed up because you are about to erase your entire SD card! Select "tools" →“partition sd card” → “remove all partitions and start from scratch.” Then for the 1st partition select “1024″ for a 1GB partition (this will be where ICS will be able to put your applications & data). Select "skip" for the 2nd partition and for the swap partition. Finally select the system “ext4″.
Step 3 - Copy the Evervolv, SpazeDog, or whatever zip installation file you have chosen to your phone's SD card
Download the ICS or JB zip file above and copy it to the root of your newly formatted SD card.
Step 4 - Installing and using BlackRose to resize the system partition:
Download the BlackRose application and install it on your computer. (Alternatively people have made flash-able partition schemes that you can just flash from your PC - usually links and instructions are provided in the installation rom's thread, Evervolv's here. If you do have access to a computer you can check out this thread).
Make sure your nexus one is attached via USB to your computer.
Open the BlackRose application - it will install and reboot your phone. Then follow along as shown in this video to resize your partitions for a JB ROM.
If you plan to install the ICS rom then use the video above as a guide but use the numbers (sizes) for the different partitions as indicated below.
After BlackRose has installed you will need to restart the application. After it has started up and recognized your device select "apply stock/custom blackrose" by typing in 1 and enter.
Then select "custom blackrose" by typing in 2.
Then type "resize" when prompted.
Now you will need to change the sizes of the system partition to 220 for ICS or 260 for JB.
Change the cache size to 8.
Finally name the new system partition, either "ICS" or "JB" depending on what you plan to install.
Note: some people have reported having problems getting into recovery at this point (if not move on to step 5). If that happens, luckily for you, 4ext put a recovery image in the downloads folder of your SD card and if you did what I said in step 2 you saved it. Try reflashing that recovery image using fastboot (remember the one that was in SD/Download/4EXT_Recovery_Touch/ and was named "recovery.img"). Put your phone into the bootloader by turning off your phone, turning it on again while holding the trackball down. To reflash the recovery open command prompt and cd to the location of the Android SDK tools. Then type in the following command (replacing "path" with the path to where the recovery image is located on your computer):
Code:
fastboot flash recovery /path/recovery.img
If that does not solve your problems (inability to get into recovery) then I would recommend going back to the cyanogenmod wiki and installing Amon_Ra's recovery. Then you can use it to flash your installation zip.
Step 5 - Install JB or ICS:
Now turn your phone off and boot into recovery as you did in step 2.
4ext will load. Select "wipe/format" → "format all partitions (except sdcard)" and then also "wipe data/factory reset."
Now go back and select "install from sdcard" → "choose zip from sdcard" → and then select the ICS or JB zip you copied to the SD card in step 3.
Now either the ICS/JB installer will load or it will just install in one step. Just follow the prompts to install and enjoy.
Depending on the ROM you chose you may need to install Google apps (see the specific ROM thread for details) and will also likely want to flash an apps-to-SD script as mentioned above so you do not run out of space.
This method worked perfectly for me, hopefully it will work well for you as well. Enjoy.
Great work, your guide is amazing!!! I followeed it and ended with an infinite bootanimation , I'm trying to discover what I did wrong :fingers-crossed:, but the guide was superb!
diegolm said:
Great work, your guide is amazing!!! I followeed it and ended with an infinite bootanimation , I'm trying to discover what I did wrong :fingers-crossed:, but the guide was superb!
Click to expand...
Click to collapse
I am sorry to hear that. Can you boot into recovery or is that broken as well? If you can boot into ext recovery try selecting "wipe/restore" → "wipe data/factory reset" and then try to install BCM again. I probably should have added that above, I will do that now.
If your recovery is broken but you can get into the bootloader (holding down trackball while starting up), you should be ok. You will probably need to flash Amon_Ra's Recovery using Hboot as was described in the guide from cyanogenmod link above. If there is a way to directly hboot flash 4ext recovery I don't know how to do it. Then you can try installing BCM again from the Amon_Ra's recovery and re-install 4ext after you get everything working.
I tried the Texasice ROM and it worked, but I didn't like it! Later I tried again BCM and It worked! I dont know, maybe I did something wrong... Anyway thanks again for the guide!!
Does work the same if using fastboot method? Thx
Sent from my Nexus One using Tapatalk 2
intel415 said:
Does work the same if using fastboot method? Thx
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
I am not sure which part you are referring to, but, yes, a few of the above instructions could be replaced with fastboot commands.
The adb commands, instead using adb I can use fastboot commands right. That's what I used to root my n1 kinda familiar with fastboot. Thx
Sent from my Nexus One using Tapatalk 2
intel415 said:
The adb commands, instead using adb I can use fastboot commands right. That's what I used to root my n1 kinda familiar with fastboot. Thx
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
I used the adb commands above because you can use adb to reboot directly into recovery (fastboot you can only reboot normally or into the bootloader) and you can also use adb to directly install apk files - fastboot cannot do those two things - it is more for flashing images (recovery, roms, etc). In order for adb to work make sure you have usb debugging enabled: go to "Settings" → "Applications" → "Development" → enable "USB debugging."
Note that adb commands are not required - you can reboot into recovery and install the 4ext manually.
It won't let me post a link right now, but just google "adb commands" to find a list of all the commands you can use.
Hope that helps.
Thx. All I need it was to install black rose and partition it. Put zip on SD card wipe and flash. Installation was easier than I thought it would be lol
Also on ur guide you forgot to put 200 for the data part. You only had 220 and 16
Thx again got ics installed on my n1 smoother than cm 7.2
Sent from my Nexus One using Tapatalk 2
intel415 said:
Thx. All I need it was to install black rose and partition it. Put zip on SD card wipe and flash. Installation was easier than I thought it would be lol
Also on ur guide you forgot to put 200 for the data part. You only had 220 and 16
Thx again got ics installed on my n1 smoother than cm 7.2
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
Yeah, its not bad - glad you got it working! ICS has been smoother than cm 7.2 for me as well.
Blackrose didn't ask me about userdata - it just assumed that automatically after putting in 220 system and 16 cache... I'll make note of that in the guide so its clearer. Thanks.
Got the issue with not being able to get into recovery after step 4, but I don't have the recovery image to flash. Once the SD card was formatted in step 2 I don't have a download folder. I attached what is in my SD card right now. Help please.
Look for "recovery.img"
bobbyphoenix said:
Got the issue with not being able to get into recovery after step 4, but I don't have the recovery image to flash. Once the SD card was formatted in step 2 I don't have a download folder. I attached what is in my SD card right now. Help please.
Click to expand...
Click to collapse
Try to find if there is a "recovery.img" anywhere on your SD card, perhaps in the 4ext folder?
If you can't find it, do not worry, you can just go to the first page of this thread, click on the link labeled "follow this guide from Cyanogenmod" and then go to the section on how to download and install Amon_Ra's Recovery. Once you get Amon_Ra's recovery flashed you will be able to install any ROM of your choice.
You can reinstall the 4ext recovery later if you want.
c2med said:
Try to find if there is a "recovery.img" anywhere on your SD card, perhaps in the 4ext folder?
If you can't find it, do not worry, you can just go to the first page of this thread, click on the link labeled "follow this guide from Cyanogenmod" and then go to the section on how to download and install Amon_Ra's Recovery. Once you get Amon_Ra's recovery flashed you will be able to install any ROM of your choice.
You can reinstall the 4ext recovery later if you want.
Click to expand...
Click to collapse
OK I'm stuck on what the path name is suppose to be. I tried it every way I can think of. Can you take a look at my screen shot, and tell me where I'm going wrong? The recovery image is on my desktop, so I'm not sure what exactly I should be replacing "path" with. I tried it from the link, and how you have it in your note. You don't have the "/to/" after path as in the CM link.
Well I tried a couple more times, and I can get it to seemingly do it, but it just hangs on this: (see screen shot) I get no error, and if I try to enter recovery on the phone I still get the reboot to the android and triangle with the ! in it.
place the recovery under the folder which contains fastboot.exe and rename it to recovery.img
now use the command
fastboot flash recovery recovery.img from platform-tools directory
Sent from my Nexus One using Tapatalk
And right-click this folder while pressing the SHIFT key on your keyboard. Then choose "Open command window here".
n1newbie said:
place the recovery under the folder which contains fastboot.exe and rename it to recovery.img
now use the command
fastboot flash recovery recovery.img from platform-tools directory
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
tommert38 said:
And right-click this folder while pressing the SHIFT key on your keyboard. Then choose "Open command window here".
Click to expand...
Click to collapse
WOW Thank you both. I spent literally hours yesterday trying to get it to work. Tried your suggestions, and in five minutes it was up and running!
---------- Post added at 12:31 PM ---------- Previous post was at 11:33 AM ----------
I may have spoke too soon. I followed the instructions to the end. Installed the ROM, and rebooted, but now after the X I get the Spazdog splash screen with the big Z in the middle and green dots moving, but it stays there forever. I waited 20 minutes one time. Tried reflashing, but I get the same thing.
---------- Post added at 01:17 PM ---------- Previous post was at 12:31 PM ----------
Just giving an update on progress (in case someone else is in my boat too) Flashed back to stock GB. Reinstalled recovery, and reflashed Spaz. Got past the X, and the splash screen, but now it's stuck on the Android logo that looks like the night rider beam that goes across the word. Been there now for about 10 minutes.
You do have Blackrose, right?
Yep. Installed everything according to OP. I think it may be the partition sizes as I think flashing back to GB messed with them. It says 220 and 10, but after checking some threads, it looks like there is one missing (userdata). I tried flashing a custom GB from here http://forum.xda-developers.com/showthread.php?t=1214543&page=98 and I was able to install everything. Got it up and running, so I'm going to start over for ICS, or do you think I can flash one of these for ICS http://forum.xda-developers.com/showthread.php?t=1637166 , and then just flash the ROM after?
220/10 means that you have 220MB for system and 10MB for cache, everything that's left will be userdata, so it doesn't ask (total is ~436MB, so userdata will be ~206MB in that case).
In HBOOT you can check how large your partitions are, or you could use the FreeSpace app for example. Always make sure your system partition is large enough before flashing a ROM.
My current situation is as follows:
ROM on it is bad and bootloops
Storage was wiped for a pure clean install
TWRP 2.5.0 doesn't seem to have any method to mount while in Recovery
As a result, I cannot boot it up to add the good files and I cannot mount it in Recovery to add the good files
I am at work and as such cannot use ADB.
If I can get it to mount, I can copy over the known good backups or just a known good ROM I can flash. There just doesn't seem to be any way to get it to mount in Windows 7 or 8. Does anyone have any suggestions?
rougegoat said:
My current situation is as follows:
ROM on it is bad and bootloops
Storage was wiped for a pure clean install
TWRP 2.5.0 doesn't seem to have any method to mount while in Recovery
As a result, I cannot boot it up to add the good files and I cannot mount it in Recovery to add the good files
I am at work and as such cannot use ADB.
If I can get it to mount, I can copy over the known good backups or just a known good ROM I can flash. There just doesn't seem to be any way to get it to mount in Windows 7 or 8. Does anyone have any suggestions?
Click to expand...
Click to collapse
Your only option now is to run the Stock ruu and return to stock. Theres plenty of threads on this forum that describe the procedure. You should never wipe the storage just for this reason. its much easier and less time consuming to flash a nandroid backup than having to revert back to stock via the ruu. Good luck and I hope everything works out
wranglerray said:
Your only option now is to run the Stock ruu and return to stock. Theres plenty of threads on this forum that describe the procedure. You should never wipe the storage just for this reason. its much easier and less time consuming to flash a nandroid backup than having to revert back to stock via the ruu. Good luck and I hope everything works out
Click to expand...
Click to collapse
I managed to find a machine I have sufficient privileges on for ADB. I can now push files to it. Do you know off hand what the path needed for TWRP backups is?
rougegoat said:
I managed to find a machine I have sufficient privileges on for ADB. I can now push files to it. Do you know off hand what the path needed for TWRP backups is?
Click to expand...
Click to collapse
should be /mnt/sdcard0/twrp/backups
but you wiped storage. Can you boot into fastboot? if so you can run the fastboot command
fastboot flash nameofrom.zip
you'll have to place the rom zip in the same directory as fastboot but fastboot should interrogate the zip file and flash the correct partitions
wranglerray said:
should be /mnt/sdcard0/twrp/backups
but you wiped storage. Can you boot into fastboot? if so you can run the fastboot command
fastboot flash nameofrom.zip
you'll have to place the rom zip in the same directory as fastboot but fastboot should interrogate the zip file and flash the correct partitions
Click to expand...
Click to collapse
I can get there. The issue is the one zip I have on hand doesn't seem to like being pushed that way. Rather than sit through a gig download I was just going to push a backup of stock I have on hand into the proper folder. At the very least I'd attempt it while downloading a stock+root rom.
rougegoat said:
I can get there. The issue is the one zip I have on hand doesn't seem to like being pushed that way. Rather than sit through a gig download I was just going to push a backup of stock I have on hand into the proper folder. At the very least I'd attempt it while downloading a stock+root rom.
Click to expand...
Click to collapse
ok the correct path according to my phone's file system is /sdcard/TWRP/BACKUPS
if those files don't exsist you can create them from adb shell
mk dir sdcard
cd sdcard
mk dir TWRP
cd TWRP
mk dir BACKUPS
exit out of adb shell by issuing the command exit
the
adb push nameofbackup.win /sdcard/TWRP/BACKUPS
wranglerray said:
ok the correct path according to my phone's file system is /sdcard/TWRP/BACKUPS
if those files don't exsist you can create them from adb shell
mk dir sdcard
cd sdcard
mk dir TWRP
cd TWRP
mk dir BACKUPS
exit out of adb shell by issuing the command exit
the
adb push nameofbackup.win /sdcard/TWRP/BACKUPS
Click to expand...
Click to collapse
Giving it a shot now.
Sorry my syntax was off it's mkdir without a space
Sent from my HTCONE using Xparent BlueTapatalk 2
wranglerray said:
Sorry my syntax was off it's mkdir without a space
Sent from my HTCONE using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
No worries, I'm versed enough commandline wise to know what you were getting at. Unfortunately it seems that random number path for the device chunk has changed since I did my backup(probably because of my wiping and being an overall idiot). The stock+root zip of a rom finished downloading though, so I'm flashing that now. Hopefully that ends this ordeal.
(Edit) Success getting it to be usable again. Now to start from scratch. (/edit)
rougegoat said:
No worries, I'm versed enough commandline wise to know what you were getting at. Unfortunately it seems that random number path for the device chunk has changed since I did my backup(probably because of my wiping and being an overall idiot). The stock+root zip of a rom finished downloading though, so I'm flashing that now. Hopefully that ends this ordeal.
Click to expand...
Click to collapse
good luck! post your results i'd be interested in knowing how it ends up.
Hey rogue.... went through this same problem about four days ago, almost blew my brains out because I thought I would have to smash my phone and return it through the best buy protection plan. Anyways... the ONLY way to fix your problem is to use the Sprint HTC One RUU. Boot your phone into fastboot usb mode and run the RUU. Takes about 10-15 minutes, and will have you COMPLETELY back to stock. From there, you need to start from scratch unlocking and installing the recovery. ViperRom is the only rom that won't bug out your sprint phone atm. Also be sure you relocked your phone before you run the RUU. I'm super busy atm and can't go find the RUU links, but google it and i'm sure you can find it. If not, i'll get you the links later if you pm me. Peace bro and good luck.
---------- Post added at 09:57 PM ---------- Previous post was at 09:51 PM ----------
cburch85 said:
Hey rogue.... went through this same problem about four days ago, almost blew my brains out because I thought I would have to smash my phone and return it through the best buy protection plan. Anyways... the ONLY way to fix your problem is to use the Sprint HTC One RUU. Boot your phone into fastboot usb mode and run the RUU. Takes about 10-15 minutes, and will have you COMPLETELY back to stock. From there, you need to start from scratch unlocking and installing the recovery. ViperRom is the only rom that won't bug out your sprint phone atm. Also be sure you relocked your phone before you run the RUU. I'm super busy atm and can't go find the RUU links, but google it and i'm sure you can find it. If not, i'll get you the links later if you pm me. Peace bro and good luck.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2250904
I know another person suggested this earlier, but failed to mention that sideloading once you're caught in this loop won't work. Run the RUU, unlock, and flash ViperRom.
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.
Rooted HTC one, no os, don't know how to push rom
I accidently wiped my os while putting a new rom on. I am INCREDIBLY inexperienced with this and really had no business fooling around with it. Regardless, I have the HTC One rooted with TWRP but cant get the new rom on to the phone. I'm on a mac and android file transfer is not recognizing my phone. Any help anyone could give would be great.
Try putting the rom on a usb stick and using an otg cable then mount it under twrp and flash from there?
Sent from my HTC One using xda app-developers app
Good Info
EazyVG said:
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.
Click to expand...
Click to collapse
Thanks for the Info
Disclaimer: If you are not comfortable with using Fastboot and ADB and editing system files than this guide might not be for you. At this point this is what I have to offer.
Click here for the unofficial twrp image - Latest version as of 12/27/14
So getting right into it.
1. Turn on ADB mode on the watch by going to about and tapping the build info 7 times.
2. Download ADB and Fastboot utilties
3. Plug the watch into the computer and your phone should vibrate and ask you to accept the computers fingerprint, tick the check box to always allow and hit ok
4. Open up a command prompt or terminal inside of where the ADB utilities are located and enter
Code:
adb reboot bootloader
This next step will wipe your data!
5. Now you should be in fastboot, go ahead and on the terminal use the next code and follow prompts to unlock
Code:
fastboot oem unlock
6. Now after you re-set up your watch again you will need to do step 1 and 3 again.
Please do not skip step 6!
7. Go ahead and issue
Code:
adb reboot bootloader
8. Flash unofficial twrp, make sure the recovery image file is in the same location as fastboot than issue
Code:
fastboot flash recovery YOURIMGNAMEHERE.img
9. Upon successfully doing that you should have twrp installed
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB use the proper name of what you downloaded. Issue
Code:
adb push SUPERSUNAMEHERE.zip /sdcard/
11. Issue
Code:
adb reboot recovery
12. than using the very tiny TWRP and somewhat messed up go ahead and use it to install the supersu.zip under the folder /sdcard
13. Enjoy root and twrp.
I will make this guide into a much easier Java program in the very near future to make it easier to use.
This was typed up pretty fast and it is kinda hacky, I will work on a bat script and a shell script if we have enough osx users here. I'm sure someone will come along and make this better if I don't get around to it.
Credits:
Dees-Troy for his TWRP support for dory our fish brother device which worked on our device
Chainfire for all his hard work these many years
Q: ADB complains there is no device listed.
A: Install universal ADB drivers and then go to device manager and under the device with a yellow warning icon go to update driver, Browse my computer, let me pick from list of device drivers, than Google ADB interface. If it still complains turn off debugging, than turn it back on, revoke authorization, then disable and re-enable again.
One more just in case.
Great work!!
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?
hatefuel19 said:
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?
Click to expand...
Click to collapse
The latest supersu is version 2.36 dated 11.27.2014. 1.94 is well over a year old, you need to update for sure that is why you are force closing.
I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!
hatefuel19 said:
I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!
Click to expand...
Click to collapse
I'm here to help! I'm working on adding other mods to my other thread right now I'm working on getting busybox working.
Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
---------- Post added at 09:31 PM ---------- Previous post was at 09:28 PM ----------
jimmydigital00 said:
Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
Click to expand...
Click to collapse
Disregard I did it again and for some reason it worked. Maybe I need to reboot first.
Recovery
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?
adamrobles said:
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?
Click to expand...
Click to collapse
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app
reflashed
tonu42 said:
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.
adamrobles said:
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.
Click to expand...
Click to collapse
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
Thank you for that information, I stopped the download of the dump.
Downloading the stock recovery now.
---------- Post added at 02:24 PM ---------- Previous post was at 02:10 PM ----------
tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
I must have skipped a step...
installed stock recovery
booted into the watch system
enabled adb debugging
reboot to bootloader
install your recovery image
rebooted
pushed supersu
rebooted to twrp
installed supersu
rebooted to system
adb shell - verified root!
You are awesome! Thank you for taking the time to help me!
HYPE for 5.0.1
'm Hype! can't wait to flash the first 5.0.1 system dump on this as stated by +Darek Ross we MAY be receiving update as early as today!
I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...
zvieratko said:
I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...
Click to expand...
Click to collapse
My guide is setup like the one you put there. In order to get adb working again you need to re setup the watch step 6. Read the instructions carefully. I'll post a batch script later to simplify this.
Sent from my A0001 using XDA Free mobile app
Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there
zvieratko said:
Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there
Click to expand...
Click to collapse
By default debugging is disabled, I'm not sure how you were able to issue an ADB command on step 7 with out first performing step 6.
Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)
zvieratko said:
Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)
Click to expand...
Click to collapse
Ah I see, yea the guide is written as the absolute minimum to work right now. Like I said later today I'll try to post a script that automates all of this, its much easier.