Thanks to Flipz at Geek For Me for the link (surprised this hadnt been posted yet)
http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1
I'm using the carebear blue version
HeroMeng said:
I'm using the carebear blue version
Click to expand...
Click to collapse
So am I!!!!!
Vrekk said:
So am I!!!!!
Click to expand...
Click to collapse
me three...
green here.....
Cool themes huh! Seems every part of Android can be "brightened up"
hey guys im a little bit of a noob so can you help me on installing this?? like how to use adb shell?
Had a few quick questions on this...
Can I just use FlashRec to update the Recovery?
Do I have to use the newest version off of ZenThought like I read? (Just wondering cause the site is not coming up)
Will I have to re-install a rom or restore a nandroid or will it just update the recovery and I'm good?
If you already have root, its pretty easy to do, just copy the file to your sdcard then
Code:
adb shell
su
cd /sdcard/
flash_image recovery recovery-RA-heroc-v1.6.2.img
If for some reason "flash_image" is not found, change it to
Code:
/system/bin/flash_image recovery recovery-RA-heroc-v1.6.2.img
If you are using one of the colored ones change the recovery-RA-heroc-v1.6.2.img to the name of whatever one it is.
If you don't have root already :
http://forum.xda-developers.com/showthread.php?t=583291
Just replace v.1.5.2 with v.1.6.2
You don't have to re flash any roms after this and your backups should still work
but what is that code or what?? where does it go?
juicyj11 said:
but what is that code or what?? where does it go?
Click to expand...
Click to collapse
it is command line input on your pc
juicyj11 said:
but what is that code or what?? where does it go?
Click to expand...
Click to collapse
You run them in the command line. Cmd.exe for windows, terminal for linux and mac
If you are on windows, install htc sync, it helps with driver issuse.
Then download and extract http://developer.android.com/sdk/index.html for your OS. On windows extract to C:\android-sdk\
Then you will run
Code:
cd C:\android-sdk\tools\
then the code I posted above, if you have root that is
If you are using linux or Mac, just skip the htc sync part, they have the needed drivers already
okayy thank you
carebear green for me!
The easiest way of ALL to flash a new recovery image is to download Flipz's kitchen, go into the "root" folder of it, find the recovery images, and rename the 1.5.2 (something like that) to something else, like dog. Then rename the recovery image you want to flash to whatever the 1.5.2 image was named. Then run the auto-rooter, and walah! New recovery flashed. That's how I flashed mine
stupid question, mostly because I don't see much difference...but what's the major differences between this and 1.5.2 (besides the annoying ass carebears)?
I didn't know it was going to be a Care Bear!
ok i did the adb command and flashed the new image, but now i am no longer to get into the recovery mode and it's taking a very long time to boot
i need help. The code you gave me doesnt work. It says no such file or directory found? I have already tried changing the file names but it still doesnt work.
tatonka_hero said:
stupid question, mostly because I don't see much difference...but what's the major differences between this and 1.5.2 (besides the annoying ass carebears)?
Click to expand...
Click to collapse
There's a change log on the original thread, but the one biggy I saw is that a Nandroid backup will not backup/restore the recovery console version. Also some bug fixes. Ah hell... here's the changelog:
Code:
- Added power off menu item
- New unyaffs binary patched by Koushik Dutta and Packetlss to fix the "losing root"-issue and incorrect file-time after a Nandroid restore
- New dump_image binary (by Brainaid) patched by Packetlss to fix the "bad blocks"- Nandroid restore issue.
(This will not fix old corrupted Nandroid backups! Please make new backups!!)
- New mkyaffs2image binary
- New flash_image binary
- Updated busybox to v1.5.3
- Nandroid menu options will NOT backup or restore recovery, cache, misc, splash1+2 (to avoid issues)
- Fixed wipe option not wiping when ext was not present
- Created carebear versions after the idea of packetlss
- Switched the Nexus logo to a Green Carebear with Nexus One logo (Thanks Montalbert!)
Related
ok so im confused. I was reading the "how to flash cupcake" thread and came across this post by ridli. i tried following the instructions below but they failed, it seems like it works for him. if this truly works then there is no need for fastboot to reflash a nandroid back up. please help. thnx. BTW dudes .8 G build is awesome. (posted from my G1-modded w/root and gloss suite theme)
I tried the below on my G1 using recovery mode from JF-RC33 and i get:
error opening /sdcard/bu/system.img: no such file or directory.
I have checked the sdcard and its there, please help.
ridli said:
You can do the same without linux or any other SO.
1) Download cupcake
2) copy IMG files to a DIR in your SDCARD
3) reboot the phone in recovery mode
4) press ALT+X for go to console
5) #mount -a (for mount all partitions, without this you dont have flash_image becouse it is in /system/bin/)
6) use flash_image for flash the partitions
Code:
#flash_image system /sdcard/<dir>/system.img
#flash_image boot /sdcard/<dir>/boot.img
#flash_image userdata /sdcard/<dir>/data.img
7) #reboot
Optional: Do a backup of the phone with nandroid from the recovery mode, this do a img of system, data and boot partitions of your phone and copy to your sdcard. If you have any problem you can reflash your phone with you img.
Click to expand...
Click to collapse
It didn't work for me either, but it said I could not remount system as r/w because it was busy.
Anyway, I find instructions on how to do it via PC a lot easier. And if your phone would not boot, and you are stuck without backup, you can always pull it with adb.
Karolis:
System shouldn't be busy in recovery mode... also, it shouldn't be mounted if you're trying to write a fs image
And... no, if your phone can't boot, it can't boot. That includes starting adbd.
If you can enter recovery/spl, it's booting just fine.
flak0:
Have you checked the sdcard from the shell in android, or from your computer?
If it's the latter, you should make sure you can access the file from android.
I would recommend that you copy the flash_image binary out of /system (and /data), because you're rewriting that partition
Okay, don't use the forums when on a bad connection... my browser thought it lost connection, and decided to refresh, and send my post again... *Looks for a delete button*
this does not work
just so everyone is clear
DOES NOT WORK!
Note To Self, do not follow tutorials from junior members
arteshiftedscreen said:
this does not work
just so everyone is clear
DOES NOT WORK!
Note To Self, do not follow tutorials from junior members
Click to expand...
Click to collapse
Ummmm actually this does work if you do itcorrectly. Note to self no bashing people that are just trying to help.
so how is it done?
korndub said:
Ummmm actually this does work if you do itcorrectly. Note to self no bashing people that are just trying to help.
Click to expand...
Click to collapse
And could a Gscript or similar be written to do something like this? I'd be psyched to have the option to restore my phone on the fly. And of course, if you could do that, what would stop you from having a Nandroid restore point saved for a number of different builds? I would love that.
Out of curiosity, and I've never tried this method myself, are you just entering the following exactly?
#flash_image system /sdcard/<dir>/system.img
#flash_image boot /sdcard/<dir>/boot.img
#flash_image userdata /sdcard/<dir>/data.img
Click to expand...
Click to collapse
Or are you changing <dir> to the directory of your nandroid backup? Because if you aren't it certainly won't work.
ei8htohms said:
And could a Gscript or similar be written to do something like this? I'd be psyched to have the option to restore my phone on the fly. And of course, if you could do that, what would stop you from having a Nandroid restore point saved for a number of different builds? I would love that.
Click to expand...
Click to collapse
But it would be very unsafe to flash a fs image when the partition is actually mounted and your gscript is probably in it.
the only way is to do it in recovery mode.
one little problem though: i copied flash_image to /cache and chmod, but the shell kept telling me no such file. why is that?
billc.cn said:
But it would be very unsafe to flash a fs image when the partition is actually mounted and your gscript is probably in it.
the only way is to do it in recovery mode.
one little problem though: i copied flash_image to /cache and chmod, but the shell kept telling me no such file. why is that?
Click to expand...
Click to collapse
flash_image is a binary, should not be moved. why did you move it to cache? of course it wont work...
Unfortunately, flash_image does not support writing yaffs2 images. Look in the code, there's no support for writing the OOB data to the NAND. If it was possible I would've integrated backup AND restore in nandroid 2.0, and JesusFrekes recovery image would then also have a restore option. But alas, it's not to be.
Perhaps in a future release I can find a C coder who can add the code to the flash_image source, so that this becomes possible. But I'm not even sure if that can be done (because you need kernel driver support as well).
infernix said:
Unfortunately, flash_image does not support writing yaffs2 images. Look in the code, there's no support for writing the OOB data to the NAND. If it was possible I would've integrated backup AND restore in nandroid 2.0, and JesusFrekes recovery image would then also have a restore option. But alas, it's not to be.
Perhaps in a future release I can find a C coder who can add the code to the flash_image source, so that this becomes possible. But I'm not even sure if that can be done (because you need kernel driver support as well).
Click to expand...
Click to collapse
Can't we just use nandwrite from mtd-utils to do this? I haven't tried it yet (I'll build it for ARM when I get home from work), but it appears to be the right tool for the job. I'm really interested in getting a menu-driven restore in my recovery image.
cyanogen said:
Can't we just use nandwrite from mtd-utils to do this? I haven't tried it yet (I'll build it for ARM when I get home from work), but it appears to be the right tool for the job. I'm really interested in getting a menu-driven restore in my recovery image.
Click to expand...
Click to collapse
Oh that would be sooooooooo sweet!
Having seen this thread http://forum.xda-developers.com/showthread.php?t=512319
I thought that also linux users could need a script like that, so I wrote this simple script in python that automates the fastboot restore process.
Requirements:
File attached that contains fastboot for linux and the script
Fastboot working (you must have drivers for fastboot working)
Python installed
Procedure:
Create a folder
put script, fastboot and img files you want to restore in the folder
open a terminal
run: "cd /folderYouCreated
run "python nandrest_linux.py"
Follow on-screen instructions
For any problem use this thread
Good idea.
Could your script be tweaked so that it could be put into the 'restore' image by JF or the Dude? It would be great to be able to do a restore from the restore mode, just as one can now do the Nandroid backup.
I don't know, because it is written in python.. Maybe if someone translate it in bash script language..
well the bigger problem is, blackgin's script is doing exactly what the windows batch file is doing - calling fastboot. I just wonder why we can't use flash_image in recovery?
billc.cn said:
well the bigger problem is, blackgin's script is doing exactly what the windows batch file is doing - calling fastboot. I just wonder why we can't use flash_image in recovery?
Click to expand...
Click to collapse
Not sure why you keep saying you can't use flash_image in recovery as I stated on the other thread you CAN use flash_image. I have done it several times
korndub said:
Not sure why you keep saying you can't use flash_image in recovery as I stated on the other thread you CAN use flash_image. I have done it several times
Click to expand...
Click to collapse
I have been able to get it to work also in Recovery Mode
Well ok, but then im wondering, why JF didn't add that function, if it is so simple..
Markazeh said:
Well ok, but then im wondering, why JF didn't add that function, if it is so simple..
Click to expand...
Click to collapse
he added the console to his recovery image thus providing that ability to do this....
Blackgin, your script is so easy for noobs like me to use!
Now that I've corrected my foolish folly, its now on to installing Cyanogen's 4.1.999 ROM!
Hello.
I cooked a rom with some changes and my question is... How can I try it? I know there's a metod to emulate roms, but I want to check if the update.zip is signed correctly, so what I want is to emulate recovery or fastboot, but I can't.
Somebody knows how to do it?
Thanks.
realjumy said:
Hello.
I cooked a rom with some changes and my question is... How can I try it? I know there's a metod to emulate roms, but I want to check if the update.zip is signed correctly, so what I want is to emulate recovery or fastboot, but I can't.
Somebody knows how to do it?
Thanks.
Click to expand...
Click to collapse
should be moved to Q&A
but i have the same questions i went through everything emulator related on the android site and through the command line help functions and i got as for as creating a sysdir image and i got stuck where you do the kernel image .....
I only found this:
http://android.modaco.com/content/g...p-and-running-a-full-rom-with-the-market-etc/
But I can't enter in bootloader or fastboot with [Home Key], [Back Key], o [Menu Key] While it's loading.
what SDK are you using (HUGE DEAL)
if your using the latest SDK have you precompiled your AVD profile (android virtual device) see http://developer.android.com/guide/developing/tools/avd.html#creating
if you have compiled your AVD and pointed your emulator at the correct AVD profile
http://developer.android.com/guide/developing/tools/emulator.html
if your booting an actual update.zip youll have to flash do a NAND dump of the phone and copy your NAND files to your pc and boot those through your emulator to ensure it runs correctly
(i only say this because i dont know if its possible to enter recovery mode straight from the emulator)
you place your system.img and your AVD stuff in the same folder
9. Copy the above file (referring to system.img{which would be the dump of your /system folder in a img format} to the location of the enhanced.avd directory ('C:\Documents and Settings\<user>\.android\enhanced.avd' on Windows XP, and 'C:\Users\<user>\.android\enhanced.avd' on Windows Vista).
10. You're ready! Type 'emulator -avd enhanced' to run! Note: inital boot may take a few minutes!
Click to expand...
Click to collapse
::::EDIT:::::
if you did have success making an AVD or know where i can find some premade profiles for the HTC Magic/Dream lmk
:::EDIT2::::
i just gotta finish downloading my JDK and i can get it to boot
does anyone know how to compile a system.img from just my /system folder or in essence can the /system folder just be booted without having to compile it into system.img format?
Zarboz said:
does anyone know how to compile a system.img from just my /system folder or in essence can the /system folder just be booted without having to compile it into system.img format?
Click to expand...
Click to collapse
I may be dead wrong, but you can extract a .img file to the system folder contents by unyaffs-ing it, so I assume you could do the reverse...maybe.
bcrook said:
I may be dead wrong, but you can extract a .img file to the system folder contents by unyaffs-ing it, so I assume you could do the reverse...maybe.
Click to expand...
Click to collapse
im not super linux familiar... im learning as i go and reading everything i can about it
thanks for the info :thumbsup:
so you mean
su
mkyaffs /system
or
su
mkyaffs /block/devblock/mmc0blk (i think thats system idk for sure right now tho)
just checked the unyaffs google code page... says it only supports unyaffs right now not making system.img's.....
but theres links for a mkyaffs so maybe thatll do it
---checking google site sdk site for info on compiling system.imgs maybe theres a tool included---
NOPE NOTHING!
umm
i have an idea for you man
boot into your environment and then adb shell in and just try it because the whole image that you booted to should be read write
once you boot into your emulator load a sd card file with the mksdcard commands
http://developer.android.com/guide/developing/tools/othertools.html#mksdcard
then your gunna get your adb and
adb push cyanogen1.4recovery.img /sdcard
adb shell
$ su
# flash_image recovery /sdcard/cyanogen1.4recovery.img
#reboot recovery
and see if itll do it that way if it boots into recovery with the custom recovery.img sweet action your good to go grab your ADB window and
adb push (your custom rom).zip /sdcard
adb shell
#reboot recovery
then select choose update.zip to flash and choose your custom rom and in theory it should flash it to your Readwrite system.img........
someone anyone correct me if im wrong cuz im gunna have to try this when i get home
THIS IS ALL IN THEORY I HAVE NOT TESTED NOR DO I KNOW IF THIS WILL WORK JUST AN IDEA FOR YA
Zarboz said:
im not super linux familiar... im learning as i go and reading everything i can about it
thanks for the info :thumbsup:
so you mean
su
mkyaffs /system
or
su
mkyaffs /block/devblock/mmc0blk (i think thats system idk for sure right now tho)
just checked the unyaffs google code page... says it only supports unyaffs right now not making system.img's.....
but theres links for a mkyaffs so maybe thatll do it
---checking google site sdk site for info on compiling system.imgs maybe theres a tool included---
NOPE NOTHING!
umm
i have an idea for you man
boot into your environment and then adb shell in and just try it because the whole image that you booted to should be read write
once you boot into your emulator load a sd card file with the mksdcard commands
http://developer.android.com/guide/developing/tools/othertools.html#mksdcard
then your gunna get your adb and
adb push cyanogen1.4recovery.img /sdcard
adb shell
$ su
# flash_image recovery /sdcard/cyanogen1.4recovery.img
#reboot recovery
and see if itll do it that way if it boots into recovery with the custom recovery.img sweet action your good to go grab your ADB window and
adb push (your custom rom).zip /sdcard
adb shell
#reboot recovery
then select choose update.zip to flash and choose your custom rom and in theory it should flash it to your Readwrite system.img........
someone anyone correct me if im wrong cuz im gunna have to try this when i get home
THIS IS ALL IN THEORY I HAVE NOT TESTED NOR DO I KNOW IF THIS WILL WORK JUST AN IDEA FOR YA
Click to expand...
Click to collapse
I tried before, but emulator freezes when I try to reboot it. I think can install Cyanogenmod and the CMUpdater and use my own update.zip to do the update, but I think it will not work.
realjumy said:
I tried before, but emulator freezes when I try to reboot it. I think can install Cyanogenmod and the CMUpdater and use my own update.zip to do the update, but I think it will not work.
Click to expand...
Click to collapse
it doesnt work you have to nandroid the update.zip
i was up till like 4 am last night trying to compile a tattoo build and i kept getting stuck on flash at my update script where it CHMOD CHOWN system:xbin
toooo tired to care to mess with it anymore...
tried everything to get the emulator to boot my custom rom but no go
tried doing it like
emulator -sysdir c:\c\herosysimage\ -avd hero
and like
emulator -system C:\c\herosysimage\system.img -avd hero
no boot
also tried putting system.img in the avd folder
All credit for this goes to Razor950
Coby Kyros MID-7015
Download recovery.img from Sendspace.com - send big files the easy way
use flash_image and flash recovery to tablet. (ex flash_image recovery /sdcard/recovery.img)
Navigating:
Home is down
Menu is select
Back is back
Everything works and I'll post stock nandroid dumps on here soon.
Update some are reporting that they are unable to Flash to the recent firmware update that was posted
on the coby website do to the clockworkmod being installed.
Thanks to Kasten for coding this then thanks to adamdietrick for creating a new zip
That can be flashed with the clockworkmod installed.
Clockworkmod Coby Firmware update
Donate if you like Razor950's work!
thanks for posting
any issues that anyone gets with this recovery, please pm me.
enjoy
havic said:
Everything works and I'll post stock nandroid dumps on here soon.
Donate if you like Razor950's work!
Click to expand...
Click to collapse
Here's my backup
http://www.megaupload.com/?d=5ALHYN80
You must be rooted (I assume z4root or universal android root works)
then either using terminal (grab terminal app from market) or using adb.
Grab the recovery.img and drop it into sdcard via usb or adb push.
Open terminal and type su and then flash_image recovery /sdcard/recovery.img
or if using adb, its adb shell and then su and then flash_image recovery /sdcard/recovery.img
Note: I am not the best at writing noobie guides but hopefully it helps
Thanks for this. I do not have mine yet( lol, just ordered it) but I donated for your work!
Thanks!
Anyone have a idea on how to get back into recovery? I have it installed but have tried holding every button to get me back and nothing kinda sucks since I have been testing new mods for this and cant get to my backup because the first shot at the mod was a fail.
I was able to get clockwork installed thanks to you. Do you know of any images that are out for the 7015?
Lawful123 said:
I was able to get clockwork installed thanks to you. Do you know of any images that are out for the 7015?
Click to expand...
Click to collapse
Aside from stock(rooted) dump, there is nothing, I'll work with havic to get a rooted dump with google apps(market mostly) working correctly.
Besides that there is nothing else from my end for now. I personally don't like telechip tablets, bad experience from a gentouch :X
Also telechip company are retards and don't release kernel source, it'd help developers optimize a 2.1 rom and also be able to port kernel to a newer one for 2.2
I can see that this model gained popularity this black Friday. We are just now starting to see android tablets hit " Joe User ". I think that the telechip tabs will become popular so long as the price is on point. Thanks for all you do.
what exactly is this recovery for?
does installing this offer me additional features, or is it merely what we would restore to in case of disaster?
Deenybird said:
what exactly is this recovery for?
does installing this offer me additional features, or is it merely what we would restore to in case of disaster?
Click to expand...
Click to collapse
For now it is a good way to backup your unit so that if you screw it up you can go back. In the future people will make images for it. Hopefully someday android 2.2
Which version of flash_image tool is needed to flash this recovery or is the tool stock on the tablet?
EDIT: figured it out. stock. Looking through the dump now =)
adamdietrick said:
Here's my backup
http://www.megaupload.com/?d=5ALHYN80
Click to expand...
Click to collapse
If you try and recover from the backup that is in the link you may or may not get a error.The error is md5 mismatch. So the recovery fails to install.
What needs to be done is need to have busybox installed then shell in and run the following commands.
This has to be ran from the dir. that contains the backup files.
Which will more than likely be similar to this
/sdcard/clockworkmod/backup/2010-12-01.20.41.18
#busybox md5sum -c nandroid.md5
boot.img: OK
cache.img: OK
data.img: OK
recovery.img: OK
system.img: OK
# reboot recovery
reboot recovery
Once in clockwork then run a recovery.
If you have a Issue let me know I will try my best to get you some answers.
razor950 said:
You must be rooted (I assume z4root or universal android root works)
then either using terminal (grab terminal app from market) or using adb.
Grab the recovery.img and drop it into sdcard via usb or adb push.
Open terminal and type su and then flash_image recovery /sdcard/recovery.img
or if using adb, its adb shell and then su and then flash_image recovery /sdcard/recovery.img
Note: I am not the best at writing noobie guides but hopefully it helps
Click to expand...
Click to collapse
When I type this it it says its file not found.
I double checked and in astro I see
sdcard/recovery.img
any ideas?
beccaannabell said:
When I type this it it says its file not found.
I double checked and in astro I see
sdcard/recovery.img
any ideas?
Click to expand...
Click to collapse
where are you when you type that? does it not find the flash_image binary or the .img?
Worked for me
I got it working by doing the following.
1. Download and installed "Android Terminal Emulator" on to the device.
2. Download and installed Z4Root 1.3.0.apk from here http://forum.xda-developers.com/showthread.php?t=833953
3. Run it and pressed the "Permanent Root" button. It took a bit and it auto rebooted.
4. Place the recovery.img on the root of my sd card. (Razor950's recovery.img is from post#1 on this thread.)
5. Opened "Android Terminal Emulator".
6. Entered the following.
su
flash_image recovery /sdcard/recovery.img
7. Locked everything up for about 5 min and it went back to # prompt when it was done.
8. I powered off the device.
9. After it turned off I pressed and held the back button then pressed the power button. Kept holding it until you see clockworkMod v2.5.1.3. (If it says Android it's too late.)
I have a question myself what is sd-ext on clockwork? Also is there a way to do a selective backup? Just system with no data?
Thanks.
Thanks for your procedure, will try it when I receive my tablet.
Regarding your question about sd-ext, it's a partition of your sdcard. One will be in fat32 and the other in ext2 or ext3. Usually ext2 is used when you have app2sd or 12sd+. The purpose of this is to have more apps in install by installing them on your ext partition instead of internal memory. I use it for my HTC desire (smartphone)
Regarding your second question, I don't know anyway of doing a backup without data but pretty sure it's possible, for example, if you go in your Android do a factory reset. reboot in recovery then do your backup. Not sure if there's another way to do it
Yezir!
Kasten said:
I got it working by downing the following.
1. Download and installed "Android Terminal Emulator" on to the device.
2. Download and installed Z4Root 1.3.0.apk from here http://forum.xda-developers.com/showthread.php?t=833953
3. Ran it and pressed the "permit root" button. It look a bit and it auto rebooted.
4. Place the recovery.img on the root of my sd card.
5. Opened "Android Terminal Emulator.
6. Entered the following.
su
flash_image recovery /sdcard/recovery.img
7. Locked everything up for about 5 min and went back to # prompt when done.
8. Powered off device.
9. Press and held the back button then pressed the power button. Kept holding it until I saw clockworkMod v2.5.1.3. (If it says Android its too late)
I have a question myself what is sd-ext on clockwork? Also is there a way to do a selective backup? Just system with no data?
Thanks.
Click to expand...
Click to collapse
this is perfect!!!!! thanks for thinking of us dummies
Daali said:
where are you when you type that? does it not find the flash_image binary or the .img?
Click to expand...
Click to collapse
same thing for me
"error opening /sdcard/recovery.img:No such file or directory"
Help
noonerealy said:
same thing for me
"error opening /sdcard/recovery.img:No such file or directory"
Help
Click to expand...
Click to collapse
Can you see the recovery.img on your sd card from a file manger app like Astro? If so when your in the terminal can you cd to /sdcard? If so can you enter ls -l recovery.img? Check the size to make sure it is all there.
I have anther question myself.
At cobyusa.com/?p=prod&prod_num_id=10498&pcat_id=1013 there is a firmware update. in the update.zip in system in the build.prop file i see a line that says "ro.build.version.incremental=eng.enzo.20101125.200217". I notice that the build number on the device says "MID7015 1.6a_20101105-2". Looks like they may have changed somethings but not sure what. What would be bet best way to figure out what they changed?
I tried to run it from clockwork and i get
assert failed: getprop("ro.product.device") == "tcc8900" || getprop("ro.build.product") == "tcc8900"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
To install this update would I just have to unroot my device? Not sure how to look what the current ro.build.product is now.
Thanks.
So, I
got myself an i9023 (yay!),
unlocked the bootloader,
updated it to 2.3.4 (GRJ22),
booted (not flashed) recovery-clockwork-3.0.2.4-crespo.img and applied su-2.3.6.1-ef-signed.zip from there and rebooted --> root.
Then I installed Superuser from Market and verifed that it works and
celebrated ...
... - as it turns out, rather prematurely. Apparently this doesn't give adb root because for that "ro.secure" in default.prop needs to be 0, and that file sits in the ro rootfs, which in turn is a part of the boot image ... ...
I guess my question is, how can I get root access for adb?
Is there an easy way to extract the boot image, change that detail and repack it?
EDIT: Solved, see http://forum.xda-developers.com/showthread.php?p=14219782.
fallenguru said:
So, I
got myself an i9023 (yay!),
unlocked the bootloader,
updated it to 2.3.4 (GRJ22),
booted (not flashed) recovery-clockwork-3.0.2.4-crespo.img and applied su-2.3.6.1-ef-signed.zip from there and rebooted --> root.
Then I installed Superuser from Market and verifed that it works and
celebrated ...
... - as it turns out, rather prematurely. Apparently this doesn't give adb root because for that "ro.secure" in default.prop needs to be 0, and that file sits in the ro rootfs, which in turn is a part of the boot image ... ...
I guess my question is, how can I get root access for adb?
Is there an easy way to extract the boot image, change that detail and repack it?
Click to expand...
Click to collapse
flash a custom rom through the recovery. they all pretty much have root.
I'm sure there's a way to get what you want exactly. I don't know it exactly though.
If it was my phone and i wanted to keep it stock. I would flash ~This Rom~. It's a stock deodexed zipaligned rom with a few minor tweaks.
I'm not 100 percent here but i believe if you just wanted the boot.img you could extract it from that rom then flash it using "fastboot flash boot boot.img" If you're running a stock build the boot image from a stock rom should work for you. but like i said i'm not 100% sure. I'm only a moderately well informed nub.
fallenguru said:
So, I
got myself an i9023 (yay!),
unlocked the bootloader,
updated it to 2.3.4 (GRJ22),
booted (not flashed) recovery-clockwork-3.0.2.4-crespo.img and applied su-2.3.6.1-ef-signed.zip from there and rebooted --> root.
Then I installed Superuser from Market and verifed that it works and
celebrated ...
... - as it turns out, rather prematurely. Apparently this doesn't give adb root because for that "ro.secure" in default.prop needs to be 0, and that file sits in the ro rootfs, which in turn is a part of the boot image ... ...
I guess my question is, how can I get root access for adb?
Is there an easy way to extract the boot image, change that detail and repack it?
Click to expand...
Click to collapse
If you type “su” in a terminal emulator, do you get a “$” or “#”? # means that you have root, otherwise you only have su app installed, nothing more. Same thing goes for “adb shell” "su" in your command prompt (in windows). If this is your situation then you could try this procedure:
-Flash or boot into clockwork recovery
-mount system partition (this part does the trick, I don’t see this steep in you post)
-install su-2.3.6.1-ef-signed.zip
-reboot
-enable USB debugging
simms22 said:
flash a custom rom through the recovery. they all pretty have root.
Click to expand...
Click to collapse
I'd rather stay with the stock ROM (+Voodoo module) for now, I'm not bored yet.
NVMENOR said:
If you type “su” in a terminal emulator, do you get a ...
Click to expand...
Click to collapse
#. Root on the phone and within adb shell is working fine, it's just adb itself that doesn't have root access. I'm used to modifying system files using adb pull - modify - adb push and uninstalling system apps via adb ... ...
Solved, see http://forum.xda-developers.com/showthread.php?p=14219782.
Excellent!
Thank you! Thank you! I've been trying for weeks to figure out why my rooted nexus s 4g was getting permission denied when trying to use push/pull (among other adb commands). Now I can backup my app's sqlite database using pull!
For my own education, what might the downside of flashing this boot image be? I know there is an obvious security vulnerability since adb runs as root by default now on the device. I'm willing to tolerate that for the time being. Are there any other possible issues or gotchas to be aware of?
peterwbeck said:
Thank you!
Click to expand...
Click to collapse
You're welcome.
peterwbeck said:
For my own education, what might the downside of flashing this boot image be?
Click to expand...
Click to collapse
As opposed to just booting it? I don't think there are any but I'm far from sure - maybe some incremental OTA updates won't work, for example.
Since the change only affects adb and you need to connect the phone to a computer for that anyway you might as well just boot the image whenever you need full adb access.