Donut + Sense? Possible? - myTouch 3G, Magic Android Development

guys, is there any possibility thats any of yo'all devs baking donuts with a lil sense?

check the donut 1.6 tattoo port by eugene373

wokie boss

Anything for the 32A?
I felt kind of offended at "NO 32A questions!" in the thread. Anyone know of a 32A rom with donut and the HTC goodies?

nope. no 32a version of it. would need a dev to port it to 32a.

Might get by using Redglasses Kernel. Can't say for sure it will Boot though.

yea... currently no 32a port.. too bad..

eugene373 said:
Might get by using Redglasses Kernel. Can't say for sure it will Boot though.
Click to expand...
Click to collapse
So the userspace part is always the same for 32A and 32B?

I've created 32A porting package for eugene's Tattoo ROM some time ago and was about to mention it, but as I see now, in the chaos of the past few weeks, I somehow forgot to upload and share it...I'll check it up against the latest ROM and upload it later today.

Case_ said:
I've created 32A porting package for eugene's Tattoo ROM some time ago and was about to mention it, but as I see now, in the chaos of the past few weeks, I somehow forgot to upload and share it...I'll check it up against the latest ROM and upload it later today.
Click to expand...
Click to collapse
thanks case..
is this the post?
http://forum.xda-developers.com/showthread.php?t=564949

perbu said:
I felt kind of offended at "NO 32A questions!" in the thread. Anyone know of a 32A rom with donut and the HTC goodies?
Click to expand...
Click to collapse
\move this to q&a and start asking your questions in the right place
read posts more thourougly because the patch is there
if your too impatient to look through the posts use the search bar
if that doesnt work the only thing thta makes it 32a vs 32b wich is the kernel
wich is in boot.img
sooooo
take ANY 32a sense rom
take the boot.img
and /system/lib/modules/wlan.ko
and run
adb push boot.img /data/local
adb shell flash_image boot /data/local/boot.img
adb push wlan.ko /system/lib/modules/
adb shell reboot

Zarboz said:
\move this to q&a and start asking your questions in the right place
read posts more thourougly because the patch is there
if your too impatient to look through the posts use the search bar
if that doesnt work the only thing thta makes it 32a vs 32b wich is the kernel
wich is in boot.img
sooooo
take ANY 32a sense rom
take the boot.img
and /system/lib/modules/wlan.ko
and run
adb push boot.img /data/local
adb shell flash_image boot /data/local/boot.img
adb push wlan.ko /system/lib/modules/
adb shell reboot
Click to expand...
Click to collapse
wo wo wo... dude, dun be mad k? thats what make the forum running right? i know i'm impatient. i'm sorry..

limkoksoon said:
wo wo wo... dude, dun be mad k? thats what make the forum running right? i know i'm impatient. i'm sorry..
Click to expand...
Click to collapse
use your search function and google is your best friend
im not mad this is developement and the more cluttered this forum becomes the less developement is ACTUALLY happening because were busy looking at n00b questions asked in the wrong forum
no offense meant
for future reference ask in the right place

sure bro... no offence at all...
but i need to ask u one question.
i need to push a file into the system so i have to use adb. this is what i get:
adb remount
remount failed: invalid argument
adb push libsqlite.so /system/lib/libsqlite.so
1179 KB/s <282528 bytes in 0.234s>
adb shell reboot
so is this mean i successfully push the file? so something wrong? but things seem to be the same and my problem still doesn't solve. could u help please?

limkoksoon said:
adb remount
remount failed: invalid argument
adb push libsqlite.so /system/lib/libsqlite.so
1179 KB/s <282528 bytes in 0.234s>
adb shell reboot
Click to expand...
Click to collapse
"remount failed" indicates that adb didn't manage to mount your filesystem read-write. Since its still read-only "adb push" fails (silently).
if you can execute commands "mount -o remount,rw /dev/$DEVICE" where $DEVICE is the device you want to remount read-write should do it - or at least give you a more sensible error message. "dmesg|tail" might also indicate whats wrong.

perbu said:
"remount failed" indicates that adb didn't manage to mount your filesystem read-write. Since its still read-only "adb push" fails (silently).
if you can execute commands "mount -o remount,rw /dev/$DEVICE" where $DEVICE is the device you want to remount read-write should do it - or at least give you a more sensible error message. "dmesg|tail" might also indicate whats wrong.
Click to expand...
Click to collapse
mount -o remount,rw -t yaffs2 /dev/block/mmcblock0
I THINK
idk ive gotten lazy and just used lucidrems script

Case_ said:
I've created 32A porting package for eugene's Tattoo ROM some time ago and was about to mention it, but as I see now, in the chaos of the past few weeks, I somehow forgot to upload and share it...I'll check it up against the latest ROM and upload it later today.
Click to expand...
Click to collapse
Sweet Man, You truly are turning into my 32a Hero Dev.
Thanks for porting a Boot.img.
And thanks for all youor great Work as well.

ok guys... i'll try right away...

eugene373 said:
Sweet Man, You truly are turning into my 32a Hero Dev.
Thanks for porting a Boot.img.
And thanks for all youor great Work as well.
Click to expand...
Click to collapse
please post link somewhere so we can stop the N00B questions about this stuff
thank you for your time in making a 32a porter for eugenes stuff

Sorry, I just don't seem to have enough time to do all the things I'd like to do lately...(and to do the things I promised I'll do).
I've added the 32A porting package for eugene373's Tattoo ROM into my thread now:
http://forum.xda-developers.com/showthread.php?t=564949

Related

[ROM] Haykuro Hero *Tutorial link Post2*

As of 10:07 PM EST 05/31/09 Haykuro posted to Twitter:
haykuro - One last release is coming out in a bit.. i feel that i should at least have the honor of presenting hero before some lifeless loser. 3 minutes ago from web.
Click to expand...
Click to collapse
You need to obtain the new SPL and Radio first PRIOR to installing this ROM. Follow this post. ​
Visit the Unwatermarked, Official, Hero ROM thread: http://forum.xda-developers.com/showthread.php?t=521059
Now, let's show him some respect and support. Please remember to donate if you are able to and to at least send a thanks when Hero drops.
Follow his twitter: Haykuro
Also, please remember ethics when interacting with Haykuro or any developer. To get a good idea of what I'm talking about visit this thread: http://forum.xda-developers.com/showthread.php?t=520835
[TUTORIAL] How To Get Your Phone Running Hero (Rosie UI)(Noob Friendly) per: law_ren_ce
Optimize by creating ODEX files for all apps. per: buttkicker
Bug Reports
Fixed - hero optimized but won't install apps by twistedumbrella
Optimized Hero.. Simpler, Better.. by blackgin
Steps to install Hero by teknomanelvis
ONLY - Haykuro Hero Rom
[Tutorial] "Squished Hero" with A2SD + More
Okay, I had several problems installing Haykuro's ROM but JustAnotherCrowds seemed to do the trick. In this tutorial we will install the "Squished" Hero and send Applications, Data, Dalvik-Cache, and last, App_s to the SD card!
Here goes!
Partition you SD card, various tutorials and links can be found throughout XDA, try the search button!
Install the “Squished” Version of Hero – http://www.wise-projects.com/android/hero.zip
(If this link needs to be removed, please let me know, and please do not delete the topic, If it's helpful, it's necessary right?)
Mount your SD card and create a folder named tmp on the root directory.
Save the following text file into the sdcard/tmp directory
http://98.131.185.198/jf/system/bin/lucid.txt
Now unmount your device
Open the terminal emulator on your phone(If you don’t have it, get it from the market)
Once in the Terminal Emulator
#mount -o rw,remount /dev/block/mtdblock3 /system
#cd /sdcard/tmp
#busybox cp lucid.txt /system/bin/lucid
#chmod 755 /system/bin/lucid
#busybox chown 0:0 /system/bin/lucid
#lucid (Should Clarify whether or not the Script installed)
#lucid -d -sd
#lucid -dc -sd
#lucid -m –sd
#lucid -a –sd (DO THIS LAST, IT WILL CLOSE THE TERMINAL EMULATOR)
#exit
Now ADB Commands;
adb remount
adb Shell
cp –a /data/app_s /system/sd/app_s
rm –r /data/app_s
rm –r /system/app
ln –s /system/sd/app_s /data/app_s
ln -s /system/sd/app_s /system/app
reboot
Hopefully this helps some people! If you have any quetsions I'd be glad to help.
All credit is to Haykuro for the amazing ROM and JustAnotherCrowd for "Squishing" it up for us!
holy toledo
yes i love haykuro
Between this thread, twitter, I'm going to break my F5 key tonight. Just sayin.
I peeped that. I can't wait from what I can glean from various posts his inner circle just got their hero roms
And now we play the waiting game..
Yesssssssssssssss
It's great that Haykuro wants to release a Hero Rosei UI rom. Can't wait.
He truly is an asset to the community and with his help i have the phone that all friends and co-workers envy.
the other hero thread was closed. What gives?
Paging Dr B said:
the other hero thread was closed. What gives?
Click to expand...
Click to collapse
yeah, seriously.. no explanation.. where's the consideration
Does anyone know why it keeps saying its a read file system only blah blah blah..
adb remount is needed
parmenti said:
yeah, seriously.. no explanation.. where's the consideration
Click to expand...
Click to collapse
these mother lovers close everything that has to do wit haykuro
I wish we had a general Hero discussion thread now that Haykuro is no longer going to be working on it. Some of us still want to read and discuss it but there really isn't any other thread to do so; just a bunch of scattered ones.
As for H; I hope he reconsiders his resignation to the community, don't let 1 bad apple spoil the bunch for you. Either way, I promised some Nesquick when his Hero release dropped and Nesquick he shall get.
wooo, rosie is amazing, as is Haykuro.
The other thread was mysteriously closed. Guess I will follow this one.
I for one am not going to install Hero for awhile. I'm sure that now that it's out, it will get modded and tweaked until it's working better.
Hero has myfaves? Do i need Haykuro SPL?
Jefpier said:
Hero has myfaves? Do i need Haykuro SPL?
Click to expand...
Click to collapse
yep
http://android-roms.googlecode.com/files/haykuro_new_spl-signed.zip

Us sprint 2.1 rom leaked.its exe file . For non rooted

http://www.4shared.com/file/WU7XiKt-/RUU_Hero_C_Sprint_2206511_sign.html
to all dev. its said the leak for sprint 2.1 .is exe file.non rooted phone can upgrade it. heard everyyhing work fine. im gsm version. im not respondsible for any damage or bricked of your phone.
the source from facebook htc hero page.
Sent from my Hero using Tapatalk
IS FOR SPRINT. NOT GSM. BE ALERT
Sent from my Hero using Tapatalk
orangeclanz said:
http://www.4shared.com/file/WU7XiKt-/RUU_Hero_C_Sprint_2206511_sign.html
to all dev. its said the leak for sprint 2.1 .is exe file.non rooted phone can upgrade it. heard everyyhing work fine. im gsm version. im not respondsible for any damage or bricked of your phone.
the source from facebook htc hero page.
Sent from my Hero using Tapatalk
Click to expand...
Click to collapse
Nice to see the CDMA Hero has it's official 2.1 fame .. but come on lazy HTC, where is 2.1 for the GSM cousin? Let's hope tomorrow is THE day..
Looks like it's working
EDIT: However, this is exactly the same as Villain 5.2 (the same leak that is).
Pretty stable
It does work well.. What an improvement from the previous version
HomerSp said:
Looks like it's working
Click to expand...
Click to collapse
But not on GSM Hero's - grrrrrrrrrrrrrrrr
Didn't the GSM hero come out before the CDMA one? How come the CDMA one came out first?
hkr said:
But not on GSM Hero's - grrrrrrrrrrrrrrrr
Click to expand...
Click to collapse
It does if you port it (I only have gsm) ;-)
HOW LEGIT IS THIS RUU THOUGH? who can co-sign it? my buddy wants to use it but doesn't want to take any chances..
someonenewhere said:
Who can co-sign it?.
Click to expand...
Click to collapse
What?
I need a Mercedes? Can someone co-sign it?
Just playing
Old news >> http://forum.xda-developers.com/showthread.php?t=661057
All of our dev's 2.1 builds are already based on this build.
FYI, when the final (non-test) build .exe comes out, flashing your phone with it may render your phone unrootable.
someonenewhere said:
HOW LEGIT IS THIS RUU THOUGH? who can co-sign it? my buddy wants to use it but doesn't want to take any chances..
Click to expand...
Click to collapse
I put it on my Hero with no problems. My guess is its very close to the RC. Or he could just wait!!
Once you have used this leaked RUU from Sprint, how do you go and flash one of the ROMs here? When I attempt to do it, I get a pic of a generic HTC phone with a red triangle and a red exclamation point. I have to do a battery pull to get it to go away.
Don't flash a ruu that doesn't have root. The exploits used to gain root are probably patched. Also this will over write your custom recovery. Leaving you with no way to flash custom roms. Wait until someone puts out a build with root.
tedya said:
Once you have used this leaked RUU from Sprint, how do you go and flash one of the ROMs here? When I attempt to do it, I get a pic of a generic HTC phone with a red triangle and a red exclamation point. I have to do a battery pull to get it to go away.
Click to expand...
Click to collapse
Sounds like you already installed the ruu I'm guessing?..lol.
You need flash a custom recovery to the phone now to be able to flash custom ROMs.
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid backup your phone first thing >> Next you choose flash .zip and choose any custom ROM signed .zip on your sdcard to flash. >> After it flashes, reboot.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb remount
adb push flash_image.zip /system/bin/flash_image
danknee said:
Sounds like you already installed the ruu I'm guessing?..lol.
You need flash a custom recovery to the phone now to be able to flash custom ROMs.
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid backup your phone first thing >> Next you choose flash .zip and choose any custom ROM signed .zip on your sdcard to flash. >> After it flashes, reboot.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image
Click to expand...
Click to collapse
Hi Dankee. I am having difficulties pushing flash_image. This is what I type/get:
C:\android-sdk-windows\tools>adb push flash_image /system/bin/flash_image
failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system
Any ideas? Thanks so much.
tedya said:
Hi Dankee. I am having difficulties pushing flash_image. This is what I type/get:
C:\android-sdk-windows\tools>adb push flash_image /system/bin/flash_image
failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system
Any ideas? Thanks so much.
Click to expand...
Click to collapse
you cant gain root in any other way now theres no known exploit for 2.1 yet so your basically screwed till someone finds a exploit next time gather information before you run some random program that hasnt even really been verified
Yeah, I have learned my lesson I think. I think I am going to wait around until there is an exploit for 2.1 before I end up bricking this thing. I ended up getting the flash_image pushed but now I can't reboot and use the recovery image. It goes straight to a HTC with red triangle and red exclamation point. Luckily I was able to do a battery pull and it rebooted straight to the RUU 2.1 ROM. I thought I had bricked the thing. Whew! I'll see what some of the masterminds come up with here.
I think all I am missing is being able to go into bootloader and do the v1.6.2 recovery image and then flash a custom ROM.
http://forum.androidcentral.com/htc-hero-roms-hacks/9542-how-repair-your-bootloader-a
http://forum.androidcentral.com/htc-hero-roms-hacks/9542-how-repair-your-bootloader-after-using-2-1-ruu.html
This worked for me thanks to GBhil!
Thanks SooooneR! This worked for me. I am flashing one of DamageControl's ROMs right now. Very cool.

[Q] Can someone PLEASE help me adb remount?? details inside...

im using the stock .7 official, rooted. i deleted a bunch of crap, running clockwork mod recovery.
i cant adb remount or push to /system/framework. says its read only or some junk...will someone please help me fix this?? ive tried 'cooking' a rom, im not great at it and get frustrated. is there any way to get it while using the rom im currently running? i just want to edit the ev icon and the bars but cant push the file to my device. please help!!
thank you thank you
try the Q & A forum.....
http://forum.xda-developers.com/forumdisplay.php?f=650
someonenewhere said:
try the Q & A forum.....
http://forum.xda-developers.com/forumdisplay.php?f=650
Click to expand...
Click to collapse
but that would be to easy!
I'd recommend just remounting the /system partition while in Clockwork Mod... there is no real point to pushing a file while out of recovery since 1. You won't see the change, and 2. You'll start getting FC's. Note that you shouldn't have to use adb remount either in recovery... go to Partitions, and then mount /system.
mrinehart93 said:
I'd recommend just remounting the /system partition while in Clockwork Mod... there is no real point to pushing a file while out of recovery since 1. You won't see the change, and 2. You'll start getting FC's. Note that you shouldn't have to use adb remount either in recovery... go to Partitions, and then mount /system.
Click to expand...
Click to collapse
ill try that, thank you for the INFORMATIVE response...
mrinehart93 said:
I'd recommend just remounting the /system partition while in Clockwork Mod... there is no real point to pushing a file while out of recovery since 1. You won't see the change, and 2. You'll start getting FC's. Note that you shouldn't have to use adb remount either in recovery... go to Partitions, and then mount /system.
Click to expand...
Click to collapse
thanks a lot man. i did that and now ive rid my display of that ugly ass Ev icon. thanks!
tailsthecat3 said:
thanks a lot man. i did that and now ive rid my display of that ugly ass Ev icon. thanks!
Click to expand...
Click to collapse
No problem. Just next time remember to post in the Questions and Answers forums, as this forum we are in right now is for HTC Hero projects, such as new ROM's, etc.
mrinehart93 said:
I'd recommend just remounting the /system partition while in Clockwork Mod... there is no real point to pushing a file while out of recovery since 1. You won't see the change, and 2. You'll start getting FC's. Note that you shouldn't have to use adb remount either in recovery... go to Partitions, and then mount /system.
Click to expand...
Click to collapse
You can do it while your phone is running.
Code:
adb remount
adb shell stop
adb push framework-res.apk /system/framework/framework-res.apk
adb shell start
Phone reboots and you have your new framework mods up and running.

Getting update.zip with test key working on froyo

Hi guys, it just came to my mind that test-key signed update.zip files were working back in the eclair days, so i guess the problem is the new recovery in the froyo builds needing Samsung signed files. Same problem was present on the sgs when it moved to froyo, but the devs there managed to change back to old recovery to make them work again, would be nice if someone could find a similar solution for the sg3 also... for more info search for recovery 2e 3e howto in sgs dev section... i am very busy at the moment and go for vacation on Sunday so wont find time to look into this before beginning of March, but eventually someone else could do it and just needed the hint....
Ok, to give this a bump, i need someone with a eclair rom installed and a rooted system. What i need is two files: /sbin/recovery and /sbin/recovery.sh
I think if we swap those files in jpf or whatever Froyo version we could use update.zip files again...
FadeFx
I have JK1 but in sbin directory I have only recovery file, no signs of recovery.sh
sorry, my bad, recovery.sh is part of the modified clockwork mod recovery on sgs custom kernel. also i am in conversation with hardcore about this, and eventually wed have to change the file in initramfs of the kernel... but we will see. to bad i go on vacation tomorrow and will be away for 3 weeks (going to thailand, cant wait to be there...) so i wont have time to complete this, but i will gather info and eventually gsam101 could compile a zimage with old recovery...
Ok, here is my pm conversation with hardcore, seems it can be done easily with loosing new recovery, or the complicated way keeping new recovery for system calls (CSC changes and stuff) and loading old recovery when using 3 button combo. All this is done by recovery.sh
hardcore said:
No u replace /system/bin/recovery in the rom, not kernel.
For kernel if u want to reroute to another recovery u have to use some shell script logic. Check out the initramfs source of my kernel for recovery.sh.
ok, thanx... so we would have to change the file /system/bin/recovery in the zimage´s initramfs to exchange recovery, right?
can we also put the replacement recovery into /sbin to replace the original? and if how is it then called when actually entering recovery mode so we dont enter the old recovery?
thanx Gerd
The recovery executable that comes with the ROM is actually in /system/bin/recovery
Modified kernels like mine have another CWM recovery in the kernel which is in /sbin/recovery which is compiled into the kernel's read-only initramfs.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Content of recovery.sh:
(lagfix stuff is about sztupys lagfix for the sgs and can be ignored for g3 at the moment.
This replaces stock froyo recovery (3e) with clockwork recovery, but same procedure applies to old 2e recovery.
Code:
#!/sbin/busybox sh
/sbin/busybox cp /sbin/fat.format /system/bin/fat.format
# use default recovery from rom if we have an update to process, so things like CSC updates work
# Use CWM if we simply entered recovery mode by hand, to be able to use it's features
if /sbin/busybox [ -f "/cache/recovery/command" ];
then
# if we use the original recovery it might modify the filesystem, so we erase our config, in order to avoid regeneration
# of the filesystems. The drawback is that the lagfix has to be re-applied by hand
/sbin/busybox rm /system/etc/lagfix.conf
/sbin/busybox rm /system/etc/lagfix.conf.old
rm /sdcard
mkdir /sdcard
#/sbin/rec2e &
/system/bin/recovery &
else
# TODO: CWM is a bit more intelligent, but it might fail to
/sbin/recovery &
fi;
Hope someone can make use of this to get update.zip working again...
Nobody looked into this yet? This would make much things easier for us...
Bump
....
realy hope we get some good progress and development on this thread....
sry but im just a noob and flashing is all i do right now
but if i can give any help feel free to ask
Gonna check this out. If I get OCD about this, v1.2 will be delayed.
This could be really useful. For everyone.
Sent from my Lestatious v1.2 Galaxy 3 FROYO
Lestat, i think this is info enough, if not pm me with the questions and ill do my best to find out.
FadeFx said:
Lestat, i think this is info enough, if not pm me with the questions and ill do my best to find out.
Click to expand...
Click to collapse
Alright. Will do chief. Gonna bookmark this thread so I remember tomorrow.
Sent from my Lestatious v1.2 Galaxy 3 FROYO
I have the 2.1 recovery file. . If anyone interested i think i can post if xda allows. ..
Sent from my GT-I5800 using XDA App
I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.
Gsam101 said:
I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.
Click to expand...
Click to collapse
How buggy is it?
And i noticed that's where recovery was also. I was like, Hmm. Strange.
The Dark Lestat said:
How buggy is it?
And i noticed that's where recovery was also. I was like, Hmm. Strange.
Click to expand...
Click to collapse
Like i had to flash my phone back to make it work ^^
Did u use the sgs version of cwm or did u do an own port for the g3? I guess the sgs version wont run due to different bml layout
Gsam101 said:
I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.
Click to expand...
Click to collapse
Hi Gsam101
I interested in compile custom recovery too.
Can You please share build configs for apollo projects?
just wanted to bump this thread, since i think we should now have devs that should be capable of doing such stuff, update.zip support is normally a must have for any android device
is this helpful in any way? -> http://forum.xda-developers.com/showpost.php?p=12244509&postcount=159
No, not yet. Clockwork needs to be ported to our device to run, which i am not able to do. If u can port it i can eventually give some hints...
i have wrote to the developer of ROM Manager APP (Clockwork Recovery) asking him to support our phone. I wrote just because i saw
Don't see your phone? Email me if you want to help me get it working!
Click to expand...
Click to collapse
on his page (http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html)
i'm not good at programming so i think if the developer replies and the answer will be yes then someone like FadeFx or anyone else who can help should contact [email protected] or [email protected]

Root and downgrade for Android 2.3.4 {Script included - ShiftySonofA script dl added)

Well, I'm writing this thread because I happily have a root method that doesn't require HTC unlock and you can downgrade to 2.2. Let's get into the information about it:
Required:
ADB
PG06IMG.zip {Downgraded version}
misc.img * {md5sum = c88dd947eb3b36eec90503a3525ae0de}
tacoroot *
*included in zip file
Instructions:
Alright, for this you will need to run the following commands:
Code:
adb push tacoroot.sh /data/local/tmp/taco
adb shell chmod 755 /data/local/tmp/taco
adb shell sh /data/local/tmp/taco --setup
[COLOR="Red"]YOU NEED TO Hit Vol up + Vol Down + Power all at once after it goes into recovery![/COLOR]
After it reboots type:
Code:
adb shell sh /data/local/tmp/taco --root
and then you use
Code:
adb shell dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Pull your battery after you check the md5sum of the img by using adb shell md5sum /dev/block/mmcblk0p17
and then reboot into hboot to downgrade
Download here
Script Download, features, changelog is in this post
credits:
Misc.img file: OTAKing (Ohai buddeh)
tacoroot: jcase
Well looks like someone has been at work.
I never doubted you buddy! Good work! Thanks!
Sent from my PG06100
Nice work as always.
Sent from my HTC Evo Shift using Tapatalk
You never cease to amaze young Padawan!!
Just imagine If they could of waited a little longer! Lmao!
Indirect for the win!!!
Script information:
This one is called ShiftySonOfA
It is basically Fre3atlast rewritten for this with about 3/4ths of it changed. Enjoy.
Download link:
here
Features:
Code:
MD5 Check
Easy to use
Includes all information needed
Offers download for EXE or Zip for RUU back to froyo.
Version Changelog:
Code:
1.0: Initial Release
Anyone think we can get this stickied? It's pretty important. :|
You got it...
Sent from my PG06100
Indirect said:
Anyone think we can get this stickied? It's pretty important. :|
Click to expand...
Click to collapse
Done.
EDIT: I've created a single sticky which links to all other stickies. We had about 6 so it needed to be tidied up.
Thanks once again Indirect
TEAM MiK
MikROMs Since 3/13/11
Glad to help out where I started developing.
Sent from my Nexus S 4G using xda premium
Indirect said:
Glad to help out where I started developing.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I'm just glad your still helping out
TEAM MiK
MikROMs Since 3/13/11
He told me he is too scared to ask anyone for a donation for a shift, he will work on roms if he can get his hands on one, any takers?
gigermunit said:
He told me he is too scared to ask anyone for a donation for a shift, he will work on roms if he can get his hands on one, any takers?
Click to expand...
Click to collapse
Because I knew everyone would say no.
If I had an extra one, you'd be welcome to it. Your work kicks ass.
Sent from my Supremely Shifted Speedy.
I honestly have a extra shift but have been trying to sell it times are tough at the moment, thing is less then 6 months old and doesn't even get used back in the box mint...
Just don't think I'm comin off as a ****, if I could donate bro I define would just can't afford to...
Sent from my PG06100 using Tapatalk
Indirect said:
Because I knew everyone would say no.
Click to expand...
Click to collapse
Im considering reporting my current shift lost and sending it to you.
but after I get money to pay for a replacement lol
guys, look on the bright side: If I have a donated shift, I can also try to develop a root for the rom instead of having to downgrade. I already have some ideas but I need to test on latest version. :|
Indirect said:
... I happily have a root method that doesn't require HTC unlock and you can downgrade to 2.2.
Click to expand...
Click to collapse
Thanks for this! I was able to use the temp root to "adb pull" the entirety of the (kernel visible) flash, as well as the /boot, /system, WiMax, and /data partitions (after remounting r/o). Because of that, after I'd downgraded (which seems really unnecessary JUST to get to a flashable HBoot, but that's another topic), I was able to flash back the new radios and touchscreen firmware (as seen in another thread), then flash the CWM recovery, which let me reflash /system and /data from my previously-unlocked Shift (and Nandroid that for future use, as well). After modifying the stock 2.3.4 /boot to set ro.secure to "0" then flashing that with fastboot, then pushing Superuser.apk and the "su" binary, I was exactly back to where I was before (which was VERY important to me, I didn't want to have to start over from a clean wipe), except now I have root- so I was able to use TiBu to move stuff that was ordinarily marked "Phone Only" to the SD-Card, freeing up some space (which along with how slow this phone is and how little memory it's got are my major gripes with the Shift).
(TL;DR: I now have root and didn't lose anything I had before I started).
It's nice to have the TiBu and Nandroids, too- despite the glowing reviews I read here, I seriously dislike this handset, but I hear there's ROMs out there that make this thing usable. So, now I get to try 'em, and always go back if they're no better after all.

Categories

Resources