[Q] A2SD+ on rooted stock sense froyo? - Desire Q&A, Help & Troubleshooting

Hi all,
is it poosible to get a2sd+ on stock htc sense froyo?. I`m desperately running out of space, but i want to retain the stock froyo because of app updates, those on customs had issue not been able to update for example map, yt, etc. I may be wrong. In that case is there a rom with stock sense and latest froyo update?
Any info about rooting the handset with latest froyo update (stock) would also be helpful.
Thanks.

Hi There
I found this link the other day about forcing apps to the SD card without rooting on Froyo
http://myhtcdesire.com/category/tipstweaks
I have tried it a few times but just can't get it to work for me, perhaps I am missing something
Hope thios helps

JaykaySLO said:
Hi all,
is it poosible to get a2sd+ on stock htc sense froyo?. I`m desperately running out of space, but i want to retain the stock froyo because of app updates, those on customs had issue not been able to update for example map, yt, etc. I may be wrong. In that case is there a rom with stock sense and latest froyo update?
Any info about rooting the handset with latest froyo update (stock) would also be helpful.
Thanks.
Click to expand...
Click to collapse
DISCLAIMER: be very, very careful especially if you don't have S-OFF yet and plan to use this method. Mind your exact Desire variant and read all the info on listed stuff before attempting
I use a rooted stock rom with Darktremors Apps2SD method. You just have to install the scripts and modify the init.rc script as described in this thread
You will need to prepare an update.zip with the boot.img or have S-OFF hboot (like AlphaRev) to flash the boot partition on which the init.rc script resides.
It might be also possible to use flash_image, but I'm not sure it will be possible without S-OFF.
I used AmonRA 1.7.0.1 Recovery R5 to repartition the SD, as it seemed to me that using Clockwork which was embedded in Unrevoked 3.21, caused my last USB brick.
This will enable you to move not only the apps but also the dalvik cache to the SD's ext partition. The data from /data/data still remains in the internal storage, but moving the apps and dalvik cache is a huge space saver.
IIRC moving some apps data from the /data/data (I think it was systems apps mostly but honestly I don't recall) to the ext partition may result in errors.
Right now the situation looks like this on my phone:
Code:
# df -h /data
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock5 147.6M 102.8M 44.9M 70% /data
# du -sh /system/sd/*
200.3M /system/sd/app
8.0M /system/sd/app-private
54.9M /system/sd/dalvik-cache
# ls -1 /system/sd/app /system/sd/app-private | wc -l
129
Additional bonus:
Because the ext partition is not being unmounted when connecting the phone as external storage to a computer, you don't end up with screwed up app links, and disappearing widgets when you do.
good luck

thanks for the info.
2 things: what is S-OFF and is there a windows based procedure as I dont have a *.nix system

JaykaySLO said:
thanks for the info.
2 things: what is S-OFF and is there a windows based procedure as I dont have a *.nix system
Click to expand...
Click to collapse
This particular *.nix system in my example is the Android OS as seen from the adb shell.
Please search the forum for what S-OFF is, there are tons of tutorials and howtos on this subject, it's basicly an unlocked variant of the HBOOT bootloader. The standard HBOOT won't allow you to flash partitions using fastboot mode like in earlier HTC models, Dream for example.
My advice is not to touch the HBOOT if you're not familiar with it as screwing something up when trying to change it is the quickest way to a bricked phone.
best of luck

"To begin, you'll need a Linux or a Mac system and basic knowledge on how to navigate through your Linux or Mac via a terminal program. The tools presented in this guide will only work with those systems."
As u said, its best I dont mess with hboot.

First things first - I think it should be possible to flash boot.img from an update.zip (just a regular update from the recovery mode). So no S-OFF modification needed this way.
Or just ask around the forum. It could be possible to flash the boot partition on the device using flash_image. Since my phone is already s-off I can't verify that.
JaykaySLO said:
"To begin, you'll need a Linux or a Mac system
and basic knowledge on how to navigate through your Linux or Mac via a terminal program. The tools presented in this guide will only work with those systems."
As u said, its best I dont mess with hboot.
Click to expand...
Click to collapse
Ah, that My bad, I thought you meant the code in my post.
Well you need a *.nix-ish environment for that particular solution, but that doesn't necessarily has to be an actual Linux / MacOS box.
There are a couple of ways to work around not having a Linux / MacOSX box:
First: If you have at least some knowledge of operating a unix shell, you can just download a live boot linux distro in the form of ISO image. Download and install VirtualBox, run the iso from there.
Second choice would be Cygwin, which is basically your *.nix environment for Windows.
Third is to install just a Windows perl interpreter needed for some of the scripts, and download a windows version of the mkbootimg binary, and just do the whole procedure manually. You pretty much just have to be able to run:
1. perl
2. cpio
3. mkbootimg
You can google all the needed exe's, and then you google "how to unpack boot.img" and take your pick - OR just take a peak inside the scripts from the semi-automatic solution (the thread you just quoted). The scripts are simplicity itself, pretty much don't differ much from a simple windows / dos batch file.
Fourth is to ask someone you trust to prepare the image for you
Either way, you have to modify the init.rc to be able to run the a2sd scipt on android boot.
OFC you can just start the process manually from a Terminal Emulator directly on the phone, and repeat it every time after you power on the phone, but that's hardly a comfortable way to go
Tell you what. If you feel really courageous I can fashion up a web form for you (and anyone else interested) which could allow you to submit a boot.img and have it modifed automatically, allow you to download a modified version. But: no warranties and also I might end up being an evil sneaky, sneaky bastard Your call

Thanks for the comprehensive info, but I`m not willing to experiment too much for the sake of not bricking the phone. I thought there might be a simpler solution....

+1 from me, getting headache from running out of space, I read online saying EXT3 was the method to go, but how to do it with rooted stock rom? (I head the only way to root Desire 2.2 is unrevoked) , please help

hongkongtom said:
+1 from me, getting headache from running out of space, I read online saying EXT3 was the method to go, but how to do it with rooted stock rom? (I head the only way to root Desire 2.2 is unrevoked) , please help
Click to expand...
Click to collapse
Like I wrote in the earlier posts. Partition with AmonRA recovery, install Darktremors APPS2SD, modify the init.rc script located on the boot partition, flash the modified boot - just browse the earlier posts. There are links to threads containing all the info you need.

Related

Apps2SD on HTC Hero with default 2.1 ROM

Hi all, i've bought an HTC Hero with HTC's 2.1 ROM, and since it's still in warranty i don't want to flash it with a custom ROM now
I can't find a way to install apps on the SD, because all i find are cusom roms which already have apps2sd enabled...
What can i do if i want to keep my warranty?
Cero92 said:
Hi all, i've bought an HTC Hero with HTC's 2.1 ROM, and since it's still in warranty i don't want to flash it with a custom ROM now
I can't find a way to install apps on the SD, because all i find are cusom roms which already have apps2sd enabled...
What can i do if i want to keep my warranty?
Click to expand...
Click to collapse
no. you need root. If you like your warranty, and your phone gets broken in some way while rooting, you can just run the official RUU and return it back to stock state, and your provider will never know.
Cero92 said:
Hi all, i've bought an HTC Hero with HTC's 2.1 ROM, and since it's still in warranty i don't want to flash it with a custom ROM now
I can't find a way to install apps on the SD, because all i find are cusom roms which already have apps2sd enabled...
What can i do if i want to keep my warranty?
Click to expand...
Click to collapse
You can't enable app2sd without root, and if I am not mistaken, it's the rooting the will void your warranty....
I don't think you can mess with anything at the system level without voiding your warranty, which makes sense.
But, Andyt95 is right, if you mess something up, the RRU should restore it to the unrooted state.
I rooted it using this guide: http://forum.xda-developers.com/showthread.php?t=645253
I followed the first part up to the fourth point (i think recovery img is needed to flash, not to root, am i wrong?)
But, now?
ya recovery image needs when you want to flash something in your mobile . But to root your phone it don't need recovery
there are many apps out there which can give you root & most of them are compatible for Hero
Yes i rooted it
But what to do next to install apps on sd?
I can't find a tutorial, my mistake?
Cero92 said:
Yes i rooted it
But what to do next to install apps on sd?
I can't find a tutorial, my mistake?
Click to expand...
Click to collapse
You need to partition your card with a EXT 2 partition. Then install any custom ROM. Most support app2SD
nirmalv said:
You need to partition your card with a EXT 2 partition. Then install any custom ROM. Most support app2SD
Click to expand...
Click to collapse
Yes, but i'd like to jeep the default ROM for a while
Sent from my HTC Hero using XDA App
Cero92 said:
Yes, but i'd like to jeep the default ROM for a while
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
The problem is, its not a simple update, it needs support in the kernel ramdisk, busybox installed and some scripts.
Usually I don't like to recommend the Darktremor app2sd, because its a bit too bloated in my eyes, and I don't like things which are so complicated I can't understand them (and I have tried, but he has so much script for a relatively simple task...).
Anyway in this case, I think its your only bet.
DO A NANDROID BACKUP BEFORE YOU TRY ANYTHING - ESPECIALLY THIS!
EDIT: Taking another look, even it (the Darktremor app2sd) does not seem to fix the kernel's ramdisk. You might want to test it after a nandroid backup on the odd chance I am wrong (i.e. if your original ROM does run the init.d scripts - mine did not). I am afraid if I am right, the only way you can keep the original ROM and enable app2sd, is if you unpack the kernel ramdisk and edit the init.rc to run the init.d scripts - which is a bit more complicated than it sounds, but not that hard if you have the proper background....
erasmux said:
The problem is, its not a simple update, it needs support in the kernel ramdisk, busybox installed and some scripts.
Usually I don't like to recommend the Darktremor app2sd, because its a bit too bloated in my eyes, and I don't like things which are so complicated I can't understand them (and I have tried, but he has so much script for a relatively simple task...).
Anyway in this case, I think its your only bet.
DO A NANDROID BACKUP BEFORE YOU TRY ANYTHING - ESPECIALLY THIS!
EDIT: Taking another look, even it (the Darktremor app2sd) does not seem to fix the kernel's ramdisk. You might want to test it after a nandroid backup on the odd chance I am wrong (i.e. if your original ROM does run the init.d scripts - mine did not). I am afraid if I am right, the only way you can keep the original ROM and enable app2sd, is if you unpack the kernel ramdisk and edit the init.rc to run the init.d scripts - which is a bit more complicated than it sounds, but not that hard if you have the proper background....
Click to expand...
Click to collapse
I'm down to give this a try, my girl wants the stock rom and a2sd. Dam cake eaters! but is there a process to follow with this? I'm good enough to follow a process but not create it for a2sd. Any links to reference??
da-pharoah said:
I'm down to give this a try, my girl wants the stock rom and a2sd. Dam cake eaters! but is there a process to follow with this? I'm good enough to follow a process but not create it for a2sd. Any links to reference??
Click to expand...
Click to collapse
why stock though? have you considered that villainrom 13 is just like stock but better and has apps2sd? it's a full HTC sense 2.1 rom but rooted with apps2sd and a few small additions to ensure it runs as fast as possible and gives as much room as possible and runs a custom kernel ***
and you can revert by flashing an RUU which is super easy to do (I've done it before for warranty reasons) and the RUU (stock rom) works exactly the same, in fact IS exactly the same except for the features you're asking for.
***(which is pretty much required for apps2sd unless you want to hack it for a while and know how to do it yourself (it's a lot to ask the devs here to tell you everything you need to do if you're not a kernel developer already imho and even then there isn't a guarantee you wont' mess up your phone's stock rom).
dkelley said:
why stock though? have you considered that villainrom 13 is just like stock but better and has apps2sd? it's a full HTC sense 2.1 rom but rooted with apps2sd and a few small additions to ensure it runs as fast as possible and gives as much room as possible and runs a custom kernel ***
and you can revert by flashing an RUU which is super easy to do (I've done it before for warranty reasons) and the RUU (stock rom) works exactly the same, in fact IS exactly the same except for the features you're asking for.
***(which is pretty much required for apps2sd unless you want to hack it for a while and know how to do it yourself (it's a lot to ask the devs here to tell you everything you need to do if you're not a kernel developer already imho and even then there isn't a guarantee you wont' mess up your phone's stock rom).
Click to expand...
Click to collapse
Hi I am trying to find the step by step guide about how to setup Apps2SD working. But having tough time. I have done this with my HD2 but cant find much help for Hero.
I have Recovery image flashed with 8GB (class 6) SD Card.
Next I am looking to partition the card from recovery, but what should be the swap size?
Once partitioned I will try flashing Villainrom 13 ROM.
Thanks
nbhor said:
Hi I am trying to find the step by step guide about how to setup Apps2SD working. But having tough time. I have done this with my HD2 but cant find much help for Hero.
I have Recovery image flashed with 8GB (class 6) SD Card.
Next I am looking to partition the card from recovery, but what should be the swap size?
Once partitioned I will try flashing Villainrom 13 ROM.
Thanks
Click to expand...
Click to collapse
Swap does not seem to work well for the hero, therefore most ROMs will not enable it and I use 0 for the swap size when partitioning. If you still prefer to reserve room for it use something like 32 or 64.
dkelley said:
why stock though? have you considered that villainrom 13 is just like stock but better and has apps2sd? it's a full HTC sense 2.1 rom but rooted with apps2sd and a few small additions to ensure it runs as fast as possible and gives as much room as possible and runs a custom kernel ***
and you can revert by flashing an RUU which is super easy to do (I've done it before for warranty reasons) and the RUU (stock rom) works exactly the same, in fact IS exactly the same except for the features you're asking for.
***(which is pretty much required for apps2sd unless you want to hack it for a while and know how to do it yourself (it's a lot to ask the devs here to tell you everything you need to do if you're not a kernel developer already imho and even then there isn't a guarantee you wont' mess up your phone's stock rom).
Click to expand...
Click to collapse
thanks for the reply! but to answer your in short, My girl doesnt speak geek and gets pissed right away when the ROM she uses acts up. So in short stock roms is whats she likes. I have been trying to convince her to do another ROM but she is hard headed. I think i'll just flash the villainrom 13 and tell her its stock lol. Thanks again i'll check it out!
Tried multiple attempts from scratch every time.
Attempt 1 - Failed
Partitioned my SD Card for EXT 2 (512MB).
Tried flashing of Villainrom 13 ROM along with Dalvik2SD patch.
Installed bunch of apps. Checked size of EXT2 partition. Nothing changed. Its still same size as it was before installing apps. System memory reduced from its original value.
Attempt 2 - Failed
Partitioned my SD Card for EXT 3 (512MB).
Tried flashing of Villainrom 13 ROM along with Dalvik2SD patch.
Installed bunch of apps. Checked size of EXT3 partition. Nothing changed. Its still same size as it was before installing apps. System memory reduced from its original value.
Any suggestions?
nbhor said:
Tried multiple attempts from scratch every time.
Attempt 1 - Failed
Partitioned my SD Card for EXT 2 (512MB).
Tried flashing of Villainrom 13 ROM along with Dalvik2SD patch.
Installed bunch of apps. Checked size of EXT2 partition. Nothing changed. Its still same size as it was before installing apps. System memory reduced from its original value.
Attempt 2 - Failed
Partitioned my SD Card for EXT 3 (512MB).
Tried flashing of Villainrom 13 ROM along with Dalvik2SD patch.
Installed bunch of apps. Checked size of EXT3 partition. Nothing changed. Its still same size as it was before installing apps. System memory reduced from its original value.
Any suggestions?
Click to expand...
Click to collapse
System memory is still reduced with app2sd, since the /data/data folder is not moved to the SD.
Assuming you have adb working, check these two commands:
Code:
adb shell df -h
adb shell ls -ld /data/app
If you think you still have a problem please post the result of these two commands.
erasmux said:
System memory is still reduced with app2sd, since the /data/data folder is not moved to the SD.
Assuming you have adb working, check these two commands:
Code:
adb shell df -h
adb shell ls -ld /data/app
If you think you still have a problem please post the result of these two commands.
Click to expand...
Click to collapse
Do I run this command in terminal emulator on droid or use droid explorer > Terminal Command?
Can Root Explorer help? I am getting adb permission denied from terminal emulator.
nbhor said:
Do I run this command in terminal emulator on droid or use droid explorer > Terminal Command?
Can Root Explorer help? I am getting adb permission denied from terminal emulator.
Click to expand...
Click to collapse
well, I actually meant connecting the device w/ a USB cable to your computer and then from a command prompt (i.e. start -> run -> "cmd") using the "adb.exe" utility that comes with the android SDK (under the tools folder)....
You can run the same commands in a terminal windows just without the "adb shell":
Code:
df -h
ls -ld /data/app
Only problem is that then it you can't copy paste your result here.
for the "df -h" command take note of the mount of your sdcard which should start like this line:
Code:
/dev/block/mmcblk0p2 720.9M 506.3M 178.0M 74% /sd-ext
I would assume that for you the mount point (last value) would be /system/sd.
next check the "ls -ld /data/app" and make sure it is linked to the same location, in my case it is:
Code:
lrwxrwxrwx 1 root root 11 Apr 20 09:59 /data/app -> /sd-ext/app
erasmux said:
well, I actually meant connecting the device w/ a USB cable to your computer and then from a command prompt (i.e. start -> run -> "cmd") using the "adb.exe" utility that comes with the android SDK (under the tools folder)....
You can run the same commands in a terminal windows just without the "adb shell":
Code:
df -h
ls -ld /data/app
Only problem is that then it you can't copy paste your result here.
for the "df -h" command take note of the mount of your sdcard which should start like this line:
Code:
/dev/block/mmcblk0p2 720.9M 506.3M 178.0M 74% /sd-ext
I would assume that for you the mount point (last value) would be /system/sd.
next check the "ls -ld /data/app" and make sure it is linked to the same location, in my case it is:
Code:
lrwxrwxrwx 1 root root 11 Apr 20 09:59 /data/app -> /sd-ext/app
Click to expand...
Click to collapse
My results from above 2 commands
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.6M 0 95.6M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 170.0M 162.8M 7.2M 96% /system
/dev/block/mtdblock5 165.8M 11.2M 154.5M 7% /data
/dev/block/mtdblock4 130.0M 58.8M 71.2M 45% /cache
/dev/block/mtdblock4 130.0M 58.8M 71.2M 45% /data/dalvik-cache
/dev/block//vold/179:1
6.8G 4.0G 2.8G 59% /sdcard
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell ls -ld /data/app
drwxrwx--x 1 1000 1000 2048 Apr 22 01:34 ?[1;34m/data/app?[0m
nbhor said:
My results from above 2 commands
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.6M 0 95.6M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 170.0M 162.8M 7.2M 96% /system
/dev/block/mtdblock5 165.8M 11.2M 154.5M 7% /data
/dev/block/mtdblock4 130.0M 58.8M 71.2M 45% /cache
/dev/block/mtdblock4 130.0M 58.8M 71.2M 45% /data/dalvik-cache
/dev/block//vold/179:1
6.8G 4.0G 2.8G 59% /sdcard
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell ls -ld /data/app
drwxrwx--x 1 1000 1000 2048 Apr 22 01:34 ?[1;34m/data/app?[0m
Click to expand...
Click to collapse
Well, you really do *not* have app2sd enabled (I am sorry for my previous disbelief but I have seen many users in the past which only thought they did not have app2sd enabled).
From your previous posts I understand you are using VR13, so either ask on the VR13 thread how to enable app2sd (you can post the above as proof it is not working for you), or change to a ROM with more "stable" app2sd....

[Q] How to backup the radio to PC10IMG.zip

I'm runing on a Canada Bell Desire Z and I wanna backup the current radio to PC10IMG.zip. I've browsed the radio thread in dev. section and did not found the cooresponding radio file.
Can any body provide a tutorial on how to back up the current radio?
Edited.....
I would also love to know as my current radio is stock and I would like to try a newer Bell radio (after backup!)
Sent from my HTC Vision using Tapatalk
Found this page via the wiki.
http://shipped-roms.com/index.php?category=android&model=Vision
I've already found this website and my current ROM and RADIO is not included there...
This is the reason I wanna backup it.
What ROM are you using? What recovery do you have?
Sent from my HTC Vision using Tapatalk
I'm using stock Bell 1.34.666.5 with everything stock. This rom has not been posted in xda, so I wanna make a full backup of the rom and the radio.
I think I found something that gives some insight... It's not for the Desire Z but I think you could do something similar.
Read this:
http://forum.xda-developers.com/showthread.php?t=1146531
There is a Linux command "dd" which will copy something bit for bit, so in theory you could copy each partition of your phone to your sdcard, and when you want to restore you'd have to copy each partition back over. The dd command can be dangerous however, if you accidentally write the wrong data to a partition, you could easily brick your phone... You'd also probably need root, and the dd command would have to be on your phone, which I have in CM7, so it's in busybox, if not already on your phone.
You'll have to do some more searching for which partition is for what but this should work! There's another command to see what is mounted where are such, I'm just installing ADB on my new computer and will try to get some more useful information once it's good to go...
Edit: the "dd" command reads and writes bytes, not bits. Thanks riahc3!
AFAIK (I also saw this) it is impossible.
slopes said:
I think I found something that gives some insight... It's not for the Desire Z but I think you could do something similar.
Read this:
http://forum.xda-developers.com/showthread.php?t=1146531
There is a Linux command "dd" which will copy something bit for bit, so in theory you could copy each partition of your phone to your sdcard, and when you want to restore you'd have to copy each partition back over. The dd command can be dangerous however, if you accidentally write the wrong data to a partition, you could easily brick your phone... You'd also probably need root, and the dd command would have to be on your phone, which I have in CM7, so it's in busybox, if not already on your phone.
You'll have to do some more searching for which partition is for what but this should work! There's another command to see what is mounted where are such, I'm just installing ADB on my new computer and will try to get some more useful information once it's good to go...
Click to expand...
Click to collapse
This is the only "way".
I say that between " " because as slopes commented, dd reads bytes (not bits) of data from one source and writes it to a destination (or the same source can be its destination although somewhat pointless). This is NOT in any way the same as a copy and paste. Nothing to do with it
I do advice to use extreme caution with this command and DO NOT play around with it if you are unsure what it does exactly.

Installing Android without SD, to test NAND?

Is it possible to install Android on Kaiser without SD? Has anyone investigated bundling the /system partition with tinboot so the whole thing is installed with a single KAISIMG?
I ask because I have one Kaiser whose SD reader is broken. If I could install more than a kernel, I could try risky changes to fix the NAND driver. If I brick the phone or kill its flash, it's no big loss.
No, you can't do it now, maybe i can suggest you to look after a method do dump the nand after install and use it as kaiser image
Exactly what I was thinking, but how to negotiate the NAND into the proper size partitions? Write kernel for rom and hope you get the sizes right, or make a kernel that readjusts /system size based on install and leave remainder for /data?
PoXFreak said:
Exactly what I was thinking, but how to negotiate the NAND into the proper size partitions? Write kernel for rom and hope you get the sizes right, or make a kernel that readjusts /system size based on install and leave remainder for /data?
Click to expand...
Click to collapse
I don't think thats l1q1d idea... perhaps a complete nand dump, and reflash it to another kaiser.
The kernel and partitions must be configures before the dump...
I do intend to try, but have been distracted by Scoot's very stable kernel, and a very nice pre-beta that I'm testing on my HTC Wizards, Gandalf and Radagast.
This is possible, in fact there was a time where an empty img file was being incorporated into the NBH where on a windows NBH the system files would normally be copied. A windows NBH consists of a number of parts, I can't remember what they are all called right now, but they can all be merged using NBHmerge. I can't give you specific instructions but there's no reason why it can't be done, not sure it'll be much fun though!
n2rjt said:
I do intend to try, but have been distracted by Scoot's very stable kernel, and a very nice pre-beta that I'm testing on my HTC Wizards, Gandalf and Radagast.
Click to expand...
Click to collapse
pre-beta that you're testing on HTC What ??
daedric said:
pre-beta that you're testing on HTC What ??
Click to expand...
Click to collapse
HTC Wizard. I have two of them, which I have named Radagast and Gandalf. It's my all-time favorite smartphone, although it is obviously even more obsolete than the Kaiser. I use one of them as my primary phone whenever Android is giving me fits. Right now I'm testing H3r7 beta 2 preview where the cook has adeptly squeezed WM6.5 into a tiny, fast, stable package.
If I knew that I wouldn't have given my Wizard away...
I thought Ham3r was finished when he hit 6.1 but I stand corrected...pfft.
help androidinstall.tgz
please share for me : file androidinstall.tgz 2.1 or 2.2 but must run wifi and 3G.
Send for me by: [email protected] thanks i come from VietNam
I think with the proper memory map Android could be installed via FrankenKaiser or something of that sort. Something that addresses the NAND directly through OEMSBL, bypassing the need for a HardSPL. Of course the phone would have to be CID unlocked to do this, but I think it's possible to install via CustomRUU if the mapping was done beforehand.
I have read somewhere that NAND marked as bad in the map still gets "written" to, meaning whatever is supposed to go there is put there and never read. Once unmarked the written info comes back, but that requires a full format anyway.
I say very possible...
I have stopped trying to do this, but wanted to record my latest thoughts in case someone reads this in the future.
I think the best way to install Android on a Kaiser that can't read its sdcard is to edit the initrd then use recovery mode:
* install adbd so it gets started in recovery mode
* allow the menu when sdcard is not installed
* change scripts to look for /data/andboot
* change recovery mode to mount /data partition to usb
Then, of course, you boot the kernel, use the menu, enter recovery mode, transfer androidinstall.tgz and androidupdate.tgz to /data/andboot, then install system, install updates, clear data, and run. If something doesn't work, adb shell or adb push can help.
I think it's too much work to be worth it on this old phone.

[Q] S-off and recovery advice before flashing first rom

Sorry for being a noob, but the more I read the more questions I have.
I have a Orange UK branded desire not PVT4 if I remember correctly its PVT1
Android 2.2
Radio 32.48.00.32U_5.10.05.30
Have rooted with Unrevoked3 so have ClockworkMod version 2.5.0.7
I am not s-off as not sure if the benefits outweigh the risks (flashing with fast boot risking USB brick). Does access via fastboot make it easier to rectify problems if things go wrong?
I want to install a rom that will allow me to install more apps via one of the apps2ext/sd, data2ext etc methods (preferably one that supports ext4 as that seems to perform best) so I will probably be trying a few roms.
I was planning to start out with CyanogenMod 7.0.3 for which guides seem to suggest that installing from CWM 2.5.0.7 should work fine including installing the google apps addon. However I have read that CWM 2.5.0.7 wont be able to install the addon as it doesnt support ext4 as used in gingerbread. Also I am guessing that not supporting ext4 would mean problems for nandroid backup when apps are stored on an ext4 partition of the sd card.
So would I need to change recovery for CM7 and ease of use with most other roms, dont want to have to keep changing, if so what ext4 compatible one is recomended as stable?
I know there are newer unofficial CWM, think 3.2.0.8 is the new one, but Ive heard of them causing USB bricks. Not sure about Amon_ra's as thats no loger supported either and 4EXTRecovery looks interesting but seems thats been droped to.
All advice greatly appreciated, sorry if I've missed threads with obvious answers to these questions.
Well, it is a good idea to s-off your phone if you plan to change you partition layout in order to get more internal space for installing apps and there are some other benefits too... it is somewhat risky but in my experience the risk of something going wrong is very, very small... I s-offed my device with alpharev.nl live disk, everything went smoothly...
Most of the roms support at least one or two methods of app space expansion, you should bear in mind also that it is not obligatory for ext4 partitions to perform better... the difference between ext2 and ext4 filesystems as far as I know is journaling which is not supported on ext2 and in some other things... but you shouldn't be bothered with those, just format your sdext partitions in the way the developer of the rom you are installing specified and everything should be ok... I prefer roms with d2ext or d2sd because of really big space(up to 2 Gb) and very good performance and no limitations which exist in a2sd roms unless you moved dalvik to sd...
For recovery you don't explicitly have to stick to cwm you should experiment little and find the one that is best for your needs... I had a usb brick with cwm 3.2.0.8, though usb brick can be fixed fairly easy either via fastboot or fastboot commander or from some of those recently modded recoveries... If you plan to install a rom with d2ext then i'd recommend you install either 4ext recovery (which is a mod of cwm) or rmd recovery (which is a very good mod of amonra) because these two allow you to backup all the partitions and therefore recover them in the right way...
Sorry for lengthy reply... Hope this helped a bit, if you have more questions or I skipped something just shoot...
Thanks for the info.
I don't plan to manually change the partition layout, I'll leave that down to the rom developers. When you falsh a rom, if it flashes its own hboot, does thst mean you'll loose s-off as its not set in radio for the desire but patched in hboot to ignore the security flag?
I think I'll probably use alpharev to s-off as it looks like it will be easier to access the phone to fix things in case of a problem.
I've looked at fixing a usb brick so I'm aware what to expect if it did happen, I like to be prepared. I'm not sure how I'd create the mtd0.img for my current rom as hex editing the file or creating one via a site (cant provide links) assumes a software version number of 10 characters including dots, which mine is not. Its only 9 characters - 2.17.61.3. So the site gives an error, and in hex editing a file im not sure weather to replace the 10 characters with 02.17.61.3 or 2.17.061.3 or to blank the first or last digit so there are only 9 characters. Any ideas?
Any d2ext roms you'd recommend? Any with sense as I'll miss som of the features but its not a deal breaker?
And on the issue of ext4 to my knowledge it does generally perform the best in most cases and for the our usage journalling is best disabled.
I believe that none of custom roms install hboot on it's own, so if you install a rom that needs more space than the hboot you have installed has then you are destined for doom... just kidding, it really just won't boot... so if you for example install oxygen (which is very small) you can install it on any of the hboots, only difference will be in amount of free space that you will have afterwards...
Alpharev is the way to go for s-off... Install their custom hboots and you will have no problems... Occasionally, though it never happened to me, you'll have to install a downgrader hboot in order to change hboot to another layout, but that ain't too much of a hassle...
I don't think that there is a risk of losing s-off by installing any of custom roms, s-off gets lost after flashing any of official ruu_s which return your device to stock condition...
I'm pretty sure you won't need to make that mtd0.img because most of usb-bricks get resolved by entering the following in fastboot:
fastboot oem enableqxdm 0
fastboot reboot
fastboot oem eraseconfig
if usb-brick persist then proceed to making mtd0.img, and if I remember well it doesn't really matter what digits you changed (but don't trust me with this, I resolved my brick with fastboot commands )
Most of the time I interchange between CM7 with d2ext (you have to implement d2ext script by yourself) and Wmjan's version of RcMix S (it is Sense rom) with d2ext which works perfectly (at least it does for me)... Also damo's pyramid and kingdom ports have d2ext and perform very well, but for them you need custom hboot provided with rom and they are also Sense roms... And at last x-part Miui is very nice, so experiment with those and see what fits your needs...
And at the end, I agree with you that ext4 performs best, especially without journaling, but in some very, very rare cases ext2 can be better...
Hope this was helpful
I've sorted s-off and am about to try out CM7 I'll have to look into implementing the d2ext script, haven't come across that so any pointers/links would be appreciated. I'll have a look at the roms you've mentioned, have seen RcMix S mentioned as the base for another rom.
I backed up my /misc through adb shell
Code:
dd if=/dev/mtd/mtd0 of=/sdcard/misc.img bs=4096
mostly out of curiosity to see how it compared to the ones you can download and hex. It is spaced out slightly differently at the start
thanks again
I followed instructions in this thread for CM7 d2ext implementation - Data2ext CyanogenMOD - UPDATE 26/01/11 http://forum.xda-developers.com/showthread.php?t=902395
check it out, shouldn't be difficult to set up...

I have been Hacked!

Yeah..as the title says.. 3 weeks ago this hacker hacked into my network..
placed rootkits in all my 3 computers and then hacked its way to my Desire and my wifes iphone. good thing i had wireshark running same time.
So.. 5 units hacked with the method in like 1 houre. Bad luck for me i guess.
And kaspersky didnt give me any warnings at all. bye bye kaspersky.
Anyway... i flashed my desire's HBOOT just to be sure. after i did a check with "AutoKiller Memory Optimizer" all kinds of malware services was attached to most of my apps.
1- downgraded HBOOT
2- flashed stock HBOOT from alpharev
3- Changed recovery from CWM to 4EXT as i suspected the recovery being infected somehow.
I checkd my log... the hacker had removed some files and moved shell files from an folder to another as well as busybox and so on. it was so many i thought il be better of installing new ROM.
I tried with Gingervillain first... everything installed fine..
checking with "root explorer" i see same files that had been moved and added was still there.
OK.. i tried again..
full wipe with 4ext and then installed Runnymede.. still.. when i check my root partition most of the files still there and i get same results doing a root check.
any idees...? im not sure if my kernel is right. it should be, when i installed Runnymede. when checking kernel v.
it says.. "[email protected] #11"
May be kernel rootkit? does the kernel start before recovery?
can someone plz confirm this?
baseband seem to be the same
any advise as for how to start from scratch will be much appreciated.
Clawsman said:
full wipe with 4ext and then installed Runnymede.. still.. when i check my root partition most of the files still there and i get same results doing a root check.
Click to expand...
Click to collapse
Full wipe wipes /cache, /data and /sd-ext to my knowledge. There is a possibility some of the files remain on /system. Use 4EXT to manually format each partition using format option.
Clawsman said:
it says.. "[email protected] #11"
Click to expand...
Click to collapse
That seems in order. Long name in attach marks modules added to that kernel.
Sent from my HTC Desire using Tapatalk
Ok
well.. i did the format manually in 4EXT.
I suspect some files still to be there..also some boot files containing malware script.
what file contains the boot script? i mean.. what file is the first to be triggered when booting in HBOOT. because many things in the recovery doesnt seem right. and the hboot fastrecovery starts with a delay.
Like when i want to partition or when i want to format all partitions except sd. Acts like it doesnt want to.
Anyway.. was just wondering if i could just adb and delete every file folder that is in in my phone and then flash recovery and ROM again.
Is that what RUU does?
is that something to recomend?
RUU is complete wipe of everything. /system, /hboot etc.
Download the correct one for your phone, *follow its instructions* (may need a gold card - google it) and run it on a clean pc.
Clean your pc ie format and reinstall after taking backups.
Then start again wit ha new hboot/rom setup.
Is that even possible? Infecting an Android phone via a Wi-fi network?
And Recovery shouldn't be able to get infected. I think ONLY /data can, and eventually /system if it's mounted as RW.
But on a wipe data gets deleted, and on a ROM install /system and boot (which holds the kernel and ramdisk) is deleted anyway.
RADIO starts before HBOOT. And there's absolutely no way they can be infected.
To be safe:
fastboot erase cache
fastboot erase system
fastboot erase boot
fastboot erase recovery *OVERKILL*
Then just do fastboot flash recovery {RECOVERY}
And there's nothing more you must do. HBOOT reflashing is 100% pointless.
Maybe top-notch hackers are shifting their interest from hacking NASA, FBI and similar organizations in the US to hacking Android phones. Or maybe it's one of their favourite ways to have fun in their idle time. Who knows?
Anyways, here's a Thanks from me, mr. Andrei, for your contribution to this community.
TVTV said:
Maybe top-notch hackers are shifting their interest from hacking NASA, FBI and similar organizations in the US to hacking Android phones. Or maybe it's one of their favourite ways to have fun in their idle time. Who knows?
Anyways, here's a Thanks from me, mr. Andrei, for your contribution to this community.
Click to expand...
Click to collapse
I do what i can. There are many devs that know much more than me. Your thanks are appreciated
For me it's still strange, tho. Only data and system could be "infected"
Take a look at this: http://forum.xda-developers.com/showthread.php?t=1399076
It's a scheme i made on how HTC and Nexus devices work. (How they boot, what are the individual partitions, etc)
Clawsman said:
Yeah..as the title says.. 3 weeks ago this hacker hacked into my network..
placed rootkits in all my 3 computers and then hacked its way to my Desire and my wifes iphone. good thing i had wireshark running same time.
So.. 5 units hacked with the method in like 1 houre. Bad luck for me i guess.
And kaspersky didnt give me any warnings at all. bye bye kaspersky.
Anyway... i flashed my desire's HBOOT just to be sure. after i did a check with "AutoKiller Memory Optimizer" all kinds of malware services was attached to most of my apps.
1- downgraded HBOOT
2- flashed stock HBOOT from alpharev
3- Changed recovery from CWM to 4EXT as i suspected the recovery being infected somehow.
I checkd my log... the hacker had removed some files and moved shell files from an folder to another as well as busybox and so on. it was so many i thought il be better of installing new ROM.
I tried with Gingervillain first... everything installed fine..
checking with "root explorer" i see same files that had been moved and added was still there.
OK.. i tried again..
full wipe with 4ext and then installed Runnymede.. still.. when i check my root partition most of the files still there and i get same results doing a root check.
any idees...? im not sure if my kernel is right. it should be, when i installed Runnymede. when checking kernel v.
it says.. "[email protected] #11"
May be kernel rootkit? does the kernel start before recovery?
can someone plz confirm this?
baseband seem to be the same
any advise as for how to start from scratch will be much appreciated.
Click to expand...
Click to collapse
An example of those infecting file?? What file in your root partition?? What path? Rom files are only on /system
Inviato dal mio Galaxy Nexus usando Tapatalk
I never use a anti virus and until now never have a problem...As i know!
Well it happened to me..
I have deleted everything.. I remember i checkd my log, and busybox files was moved to the system folder.. And all kinds of services was attached to Google map, calender, Facebook, wifi apps, market, etc..
And new apps installed like vpn, cam apps, recorders.. etc
Im currently using the free lookout...
And want to Buy a security tool.
Any advice Will be much appreciated.
Sent from my HTC Desire using xda premium

Categories

Resources