Hi!
Recieved OTA, official update today. Europe. Do not have the details, as i updated it in a hurry. Still same sense/android version. It was minor (about 6mb) "performance" update.
Anyone have any details on this?
EDIT: The update is version 2.42.405.4
Sent from my HTC Vision using XDA
olavnn said:
Hi!
Recieved OTA, official update today. Europe. Do not have the details, as i updated it in a hurry. Still same sense/android version. It was minor (about 6mb) "performance" update.
Anyone have any details on this?
Sent from my HTC Vision using XDA
Click to expand...
Click to collapse
same for me. this the first time i received update while rooted. i downloaded that small update but still did not run it beacuse i am afraid of having S-ON.
The cynic in me think that this may satisfy various insane Apple vs Android things rather than be of any use.
Little sad its not a better version of Android, like 2.3.5.. That would have been nice. I'm happy with Sense 2.1 though.
Any chance of someone grabbing it off their phones and uploading it somewhere?
-Nipqer
Update Archive
I've just got this update, and uploaded it here:
www_filedropper_com/otavisiongingerbreadshtcwwe2424054-2424052release258556lmz8pa872xa8ocgl
I can't post it as a link to it as I'm a noob. Oh well.
thanks
It is clearly a Gingerbread update.
My assumption is, it is in the best case Sense 3.5. Maybe not even that
Software Information:
Android Version:2.3.3
HTC Sense Version: 2.1
Build number: 2.42.405.4 CL192788 release keys
never locked Desire Z
It's still Android 2.3.3 and Sense 2.1
But I think it's a really useful update, in my case I am not having Sense restarts anymore (well, just one, after closing Temple Run). The closing app/going back to homescreen process looks really more fluid now.
could someone please check /data/local.prop for ro.HOME_APP_ADJ=1??
EDIT: downloaded the file... nothing special found... just a bunch of blindness from all those Ps
Can anyone confirm whether its safe to flash if root / S-OFF?
Thanks in advance!
Craig
craiglay said:
Can anyone confirm whether its safe to flash if root / S-OFF?
Thanks in advance!
Craig
Click to expand...
Click to collapse
I'm just root and S-off on 2.3 HTC ROM and installation failed.
thunderbillo said:
I'm just root and S-off on 2.3 HTC ROM and installation failed.
Click to expand...
Click to collapse
Through recovery?
I've now had a look through the update.zip and it seems to patch a fair few system apps as well as firmware.zip which contains boot.img, rcdata.img and recovery.img. I'd suggest if these were successfully flashed we'd loose root and S-OFF as well as recovery (CWM or 4EXT).
I'm still really not sure what this update is about..
I have a question. Does this update eliminates resetting Sense?
craiglay said:
Through recovery?
Click to expand...
Click to collapse
I've seen the error message in CWM when i were pressed POWER because i were blocked.
as007 said:
I have a question. Does this update eliminates resetting Sense?
Click to expand...
Click to collapse
I have not seen the changelog, but on mine its almost gone. It happens less often after the update, in my opinion. And i also feel its running abit smoother. That might be a placebo effect
I have another bug, gallery not updating new pictures, so have to run sd scan to refresh it. The update did not fix this.
thunderbillo said:
I've seen the error message in CWM when i were pressed POWER because i were blocked.
Click to expand...
Click to collapse
I'd imagine because the certificates to flash have changed... I'm not too hot on Android hacking but depending on how you got root, the certs probably got changed or invalidated. It also looks like it flashes a new kernel which may part of the issue.
However, if you've flashed something like Unity v10 like I have, its still a higher version of kernel provided in the update!
---------- Post added at 10:04 PM ---------- Previous post was at 09:58 PM ----------
olavnn said:
I have not seen the changelog, but on mine its almost gone. It happens less often after the update, in my opinion. And i also feel its running abit smoother. That might be a placebo effect
Click to expand...
Click to collapse
I've not really seen the launcher reload issue at all before.. I've seen apps closed due to low RAM but the system stays rather stable, killing background apps. Maybe they've been playing with the figures from the Supercharger Mod which tweaks this very thing.
I have another bug, gallery not updating new pictures, so have to run sd scan to refresh it. The update did not fix this.
Click to expand...
Click to collapse
I've never had this bug.. on 2.42.405.2
I was offered the update today, and I installed it on my stock Gingerbread Desire Z. As far as I can see nothing much changed, but Windows 7 doesn't seem to find the device anymore when trying to connect it as USB mass storage device. Anyone else seeing this, or could I be having some other problem here?
Cheers,
Rob
craiglay said:
Can anyone confirm whether its safe to flash if root / S-OFF?
Thanks in advance!
Craig
Click to expand...
Click to collapse
i tried but the update failed may be because of S-OFF. i think phone should be s-on in order to run that update.
I just succeeded with the update on my rooted system.
Here is what can succeed for people with stock system, just with superuser+busybox installed.
Note that this update will unroot, so you have to re-install SuperUser ZIP package from the recovery menu.
These commands are needed on Linux system with root privileges (I a not sure, whether update images are UID sensitive.)
Code:
#!/bin/sh
rm -f update.zip
mkdir update
cd update
unzip -XK ../OTA_Vision_Gingerbread_S_HTC_WWE_2.42.405.4-2.42.405.2_release_258556lmz8pa872xa8ocgl.zip
mkdir firmware
cd firmware
unzip ../firmware.zip
rm recovery.img
#rm rcdata.img (this part is not needed, most people leave radio and rcdata in random state during the rooting process, this just sets it to value for WWE phones)
rm ../firmware.zip
zip -r ../firmware.zip *
cd ..
rm -r firmware
zip -r ../update.zip *
cd ..
rm -r update
Then flash update.zip from the recovery menu, and then the upper mentioned SuperUser package.
(Note: Not verified! I forgot to add firmware.zip to the image, so I needed to flash system.img separately as PC10IMG.zip.)
---------- Post added at 03:56 AM ---------- Previous post was at 03:42 AM ----------
If there is anybody with unchanged and unrooted stock system, then it would be nice to provide patched system.img as a strart point for modders.
Steps to do it. (It should be safe.)
1. Have at least 600 MB on the sdcard mounted on the phone (and not on computer).
2. Get fre3vo from the downgrade howto
Run this on your machine with adb:
Code:
adb push fre3vo /data/local/tmp
adb shell chmod 755 /data/local/tmp/fre3vo
adb shell /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
# Exploit should succeed.
adb shell
# You should get # prompt here
cat /dev/block/mmcblk0p25 >/sdcard/system.img
rm /data/local/tmp/fre3vo
Then reboot for dropping the temp root and post system.img somewhere for others.
Note: It is safe to apply this vendor update even if you plan to root sometimes in future. This update did not patch the security hole exploited by fre3vo, so this utility still works on HTC_WWE_2.42.405.4.
@qwasson: How did you get the file you posted?
Flashable ROM with this OTA merged in:
http://forum.xda-developers.com/showpost.php?p=26040258&postcount=6945
Just sharing.
Related
ATTN: My rom is bare basic, if your looking for a more streamlined rom
check out grdlock bluid based on the same source. Link removed because of assholes.
SNIP SNIP Several others released far more indepth and better roms, use them (like grdlock's).
http://www.androlib.com/android.application.com-hookerbots-rpics-twDt.aspx
I don't take donations. If you like my worth, the above app is from my favorite author, support him and of course XDA.
jcase said:
# id
uid=0(root) gid=0(root)
# busybox whoami
whoami: unknown uid 0
# busybox uname -a
Linux localhost 2.6.29-564a4a15 #1 PREEMPT Thu Feb 25 15:56:06 CST 2010 armv6l GNU/Linux
#
Just wanted to put that out there. If not one else puts out a better rom based on OTA tomorrow, I'll release it.
Its just bare OTA with su/superuser.apk.
Click to expand...
Click to collapse
That's exactly what i'm looking for an OTA with su added.
Thanks! can't wait for the upload.
i see you conquered the problem. MAGIC! well done
Thanks jcase! Will be testing tomorrow. Don't forget to rm /system/etc/security/otacerts.zip
flashing now. letting it run overnight should let me know if the stock Messages app bug is fixed. if not, Handcent it is!
So once again... no root for us that went to the 2.1 leak?
LexusBrian400 said:
So once again... no root for us that went to the 2.1 leak?
Click to expand...
Click to collapse
Nope. In order to flash a new rom without root, the HTC signature needs to be valid. In order to preserve root, the rom was modified by jcase to include su which breaks the signature hash. So, while you will be able to update to the official OTA update (assuming version is higher, which I believe to be the case), you can't install this rom.
Since most people will be updating to the OTA 2.1 away from the leak or away from 1.5, I'd personally recommend installing the OTA 2.1 directly from HTC. We'll likely be targeting it for root exploits next and abandoning version 1.5.
hoban_eris said:
Since most people will be updating to the OTA 2.1 away from the leak or away from 1.5, I'd personally recommend installing the OTA 2.1 directly from HTC. We'll likely be targeting it for root exploits next and abandoning version 1.5.
Click to expand...
Click to collapse
To be clear, install the otaroot rom released by jcase if you already have root. Install the OTA rom direct from HTC if you currently have the leaked 2.1.
hoban_eris said:
Nope. In order to flash a new rom without root, the HTC signature needs to be valid. In order to preserve root, the rom was modified by jcase to include su which breaks the signature hash. So, while you will be able to update to the official OTA update (assuming version is higher, which I believe to be the case), you can't install this rom.
Since most people will be updating to the OTA 2.1 away from the leak or away from 1.5, I'd personally recommend installing the OTA 2.1 directly from HTC. We'll likely be targeting it for root exploits next and abandoning version 1.5.
Click to expand...
Click to collapse
Thanks for the clarification. I really appreciate it. Can't wait for OTA root
The new 2.1 is exactly what I wished the last leaked 2.1 would have been. Its working so much better with no noticeable lag at all.
Thanks again guys!
wipe data
I have root now and am currently running the .3 rom, question
1. is this just an update to what i am running now?
2. Do i need to preform a wipe?
3. if i dont wipe does the phone maintain all my apps and settings i.e email google etc?
Damn, I was just uploading my all-in-one batch script and then I noticed this had been released... I started making a rom of it, then I noticed you already did! hah!
Thanks for being a night owl and already doin the work jcase. I'm gonna incorporate this into the all-in-one script.
mv error: cross-device link
i have updated this rom, works great!
bu i can't mv from /system/app to /sdcard
error message is "cross-device link"
but i had already remount the /system partion as rw, and i notice that rm is working fine - i can remove files in /system/app, but can't move to another directory!
before update to this rom, mv is working correct
any advice?
btw, there is no busybox in this rom
liushk said:
i have updated this rom, works great!
bu i can't mv from /system/app to /sdcard
error message is "cross-device link"
but i had already remount the /system partion as rw, and i notice that rm is working fine - i can remove files in /system/app, but can't move to another directory!
before update to this rom, mv is working correct
any advice?
btw, there is no busybox in this rom
Click to expand...
Click to collapse
same problem here. you can copy files and then remove the source. that's what I've been doing for my moves. As for busybox, I installed it myself, but I'm sure someone (if not me) will release an update.zip to install it sooner rather than later.
hoban_eris said:
same problem here. you can copy files and then remove the source. that's what I've been doing for my moves. As for busybox, I installed it myself, but I'm sure someone (if not me) will release an update.zip to install it sooner rather than later.
Click to expand...
Click to collapse
thanks for reply
I tried install busybox myself, but it dosn't work. this is my steps:
adb push busybox /sdcard/
adb shell
remount /system
mv /sdcard/busybox /system/xbin
failed
adb shell
remount /system
switch to another console
adb push busybox /system/xbin
failed
and, there is no "cp" command, I didn't find another way to copy from /system/app to /sdcard/
Wipe??
I just want to reiterate denonlake's question, does installing rooted OTA 2.1 require a wipe of DATA and CACHE partitions like the original root process? Can we preserve settings through this flash or is it best to go through the whole setup process again?
The mv and cp commands are in busybox. I did not install busybox, so you don't have them. The Toolbox that comes with the OTA is lacking them.
Install busybox yourself, or wait for grdlock or ivan's release.
in case anyone is interested, the Messages app bug and cell standby bugs are fixed in this release too (as well as the already known gmail login bug fix) the phone also seems to power down a lot faster than previous leaks.
havent tested google voice yet, probably cant till later today. someone else feel free..
shickfaced said:
I just want to reiterate denonlake's question, does installing rooted OTA 2.1 require a wipe of DATA and CACHE partitions like the original root process? Can we preserve settings through this flash or is it best to go through the whole setup process again?
Click to expand...
Click to collapse
I first tried installing from zip through recovery.
This did not appear* to work.
Next, wiped device and cache, then installed zip through recovery.
Success!
*My experience is limited. Maybe it did work, but nothing on the phone appeared changed.
Ok so this is just a rooted version of the Official OTA 2.1 right??? Nothing else has been done to it??
rustyman14 said:
Ok so this is just a rooted version of the Official OTA 2.1 right??? Nothing else has been done to it??
Click to expand...
Click to collapse
All this info is in the first post... X_X
jcase said:
This is the 2.1 OTA Rom with su, a modified sh, SuperUser.apk and spare_parts.apk added (root). Thats it, nothing else modified.
Click to expand...
Click to collapse
I noticed earlier that m:zombie and m:vampire are not in the market. Any other programs that any of you have noticed are missing?
jlem26 said:
I noticed earlier that m:zombie and m:vampire are not in the market. Any other programs that any of you have noticed are missing?
Click to expand...
Click to collapse
it's because the ruu is signed with test keys, not the release keys, so not everything is showing up.
regaw_leinad said:
it's because the ruu is signed with test keys, not the release keys, so not everything is showing up.
Click to expand...
Click to collapse
That's what I figured but these are the only two apps I have seen missing so far. I was just wondering if anyone else came across more.
jlem26 said:
That's what I figured but these are the only two apps I have seen missing so far. I was just wondering if anyone else came across more.
Click to expand...
Click to collapse
Most of my purchased apps are gone, and they include Basketball, Toss It, Flight Control, and a few others..quite disappointed as I did the RUU install via the .exe file and so far, haven't found a way to undo it and go back to DamageControl 2.1...
spatel9114 said:
Most of my purchased apps are gone, and they include Basketball, Toss It, Flight Control, and a few others..quite disappointed as I did the RUU install via the .exe file and so far, haven't found a way to undo it and go back to DamageControl 2.1...
Click to expand...
Click to collapse
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....
Kcarpenter said:
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....
Click to expand...
Click to collapse
lol very,very true!
RUU has test-key. thats means no protected apps. You should have flashed one of the many roms based on this RUU(damage,fresh or darchlegend even though its based on the Legend RUU). There already set to go.
Anyway I can do that now?
Lol, not to sound like a jerk but we knew this. I started the thread because I was wondering if anyone else knew which programs were affected. The whole idea behind loading the RUU was to test it out. It would be great if everyone didn't come in here and tell us how we should have loaded a custom ROM. Most of us probably came from a custom ROM to this, like myself.
jlem26 said:
Lol, not to sound like a jerk but we knew this. I started the thread because I was wondering if anyone else knew which programs were affected. The whole idea behind loading the RUU was to test it out. It would be great if everyone didn't come in here and tell us how we should have loaded a custom ROM. Most of us probably came from a custom ROM to this, like myself.
Click to expand...
Click to collapse
Sorry, that was just your first post to the forum, and it had no implications that you knew how to do anything whatsoever. I was just going on what I read from your post. I was guessing you just joined and saw the RUU and flashed it. I am sorry.
regaw_leinad said:
Sorry, that was just your first post to the forum, and it had no implications that you knew how to do anything whatsoever. I was just going on what I read from your post. I was guessing you just joined and saw the RUU and flashed it. I am sorry.
Click to expand...
Click to collapse
Don't be sorry, I wasn't really aiming that at anyone in particular, I was just hoping to head off the thread turning into a point and laugh at the RUU users.
spatel9114 said:
Anyway I can do that now?
Click to expand...
Click to collapse
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 back to your original build. You can even nandroid back to Fresh 2.0d and you will retain your new PRI.
If you have never made a backup, then download whatever ROM you want to try and use flash from .zip in recovery to flash the new ROM.
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
Well I modified the build.prop last night and now all the apps are showing up in the market.
jlem26 said:
Well I modified the build.prop last night and now all the apps are showing up in the market.
Click to expand...
Click to collapse
Wow, is this easily done? I'm missing root manager, but otherwise am liking the leak (minus sprint crap).
Also.notice quick boot isn't working, but I'm sure its fixable, I just haven't looked or may not have the experience to get it going.
MILH0U5E said:
Wow, is this easily done? I'm missing root manager, but otherwise am liking the leak (minus sprint crap).
Also.notice quick boot isn't working, but I'm sure its fixable, I just haven't looked or may not have the experience to get it going.
Click to expand...
Click to collapse
Yeah it is pretty easy, just need to get your build.prop, then in wordpad, if using windows use wordpad not notepad, just have to make a few changes. After that you clear the market cache. When I did this last night, none of the protected apps showed up, however this morning they all did. So for reason it may take a bit to work right but it did work. Just checked and root manager is showing in my market too.
I'll just post one I found online. If you adb push this to /system/ it should work.
Kcarpenter said:
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....
Click to expand...
Click to collapse
@Kcarpenter, maybe dont post inflammatory stuff like this and instead be helpful and we wont have drama?
@Jlem
Good to see you got it going. You should share your build.prop (or link to instructions) so others that may have made the early (and quite risky) install of the RUU could get it going. That would be a nice thing to do
Personally I think you're crazy for trying that RUU!!! hahaha ! I'm glad someone did, and I hope it all works out for you.
edit:And you did! good work
Kcarpenter said:
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....
Click to expand...
Click to collapse
+1 Truth.
I have a feeling many people will do this.
danknee said:
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 back to your original build. You can even nandroid back to Fresh 2.0d and you will retain your new PRI.
If you have never made a backup, then download whatever ROM you want to try and use flash from .zip in recovery to flash the new ROM.
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
Alright, so when I go to do that, I get an error "Read-Only File System"..How can I make it read/write?
spatel9114 said:
Alright, so when I go to do that, I get an error "Read-Only File System"..How can I make it read/write?
Click to expand...
Click to collapse
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
jlem26 said:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
or adb remount first.
As the title suggest, I have a 2.21 based Nexus One. And I use a Mac. Is ther an easy way to root it?
ajaffarali said:
As the title suggest, I have a 2.21 based Nexus One. And I use a Mac. Is ther an easy way to root it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=8315805&postcount=2
He's right. There is nothing really different about the mac rooting process since the SDK tools are generally the same.
efrant said:
http://forum.xda-developers.com/showpost.php?p=8315805&postcount=2
Click to expand...
Click to collapse
This guide was for the main 2.2.1 update. Since the last time that post was edited, there was a second 2.2.1 OTA pushed, which I believe was a small fix for adjusting partitions or something similar and gave a slightly different build number. You know if this still works for FRG83D?
Xel'Naga said:
This guide was for the main 2.2.1 update. Since the last time that post was edited, there was a second 2.2.1 OTA pushed, which I believe was a small fix for adjusting partitions or something similar and gave a slightly different build number. You know if this still works for FRG83D?
Click to expand...
Click to collapse
Rooting by the method quoted works on all Android builds to date.
Ok- finally found some time for this but I'm getting a permission error at the step:
./busybox cp busybox /system/bin
Everything above that works well but when I reach this step, it messes up.
ajaffarali said:
Ok- finally found some time for this but I'm getting a permission error at the step:
./busybox cp busybox /system/bin
Everything above that works well but when I reach this step, it messes up.
Click to expand...
Click to collapse
The guide is prob missing a step. Make sure you change the permissions on busybox to allow it to run before you try using it. Try chmod 755 busybox
ajaffarali said:
Ok- finally found some time for this but I'm getting a permission error at the step:
./busybox cp busybox /system/bin
Everything above that works well but when I reach this step, it messes up.
Click to expand...
Click to collapse
Make sure you actually did get root, I had to run the first step a few times until I got the root prompt on my friends phone.
efrant said:
The guide is prob missing a step. Make sure you change the permissions on busybox to allow it to run before you try using it. Try chmod 755 busybox
Click to expand...
Click to collapse
Thanks! That did the trick. Nexus One is now rooted. Now to make the hard decision on which ROM to flash it with
ajaffarali said:
Thanks! That did the trick. Nexus One is now rooted. Now to make the hard decision on which ROM to flash it with
Click to expand...
Click to collapse
First thing to do after rooting is to make a backup. You would be surprised as to how many people forget to do this.
ajaffarali said:
Thanks! That did the trick. Nexus One is now rooted. Now to make the hard decision on which ROM to flash it with
Click to expand...
Click to collapse
First, flash any custom recovery if you already hadn't.
Then make a nandroid backup. It's a 'must' so you can go back if custom ROM flashing goes wrong. Also, backup your applications and their data is recommended.
I called HTC support in Egypt about 10 days ago to ask about the update and they confirmed HTC Legend Froyo update is available with version 3.30.466.6 and the update is rolling in batches by the phone IMEI, please has anybody got this update? my phone is showing "Your phone is up to date" !!!
There is an update available already for 1.27.466.7 to 3.30.466.6 but we don't have the original ROM to make a custom ROM or extract the Arabic support!
zorbakun said:
There is an update available already for 1.27.466.7 to 3.30.466.6 but we don't have the original ROM to make a custom ROM or extract the Arabic support!
Click to expand...
Click to collapse
I called HTC Support to tell them about the problem with updating to Froyo, they told me: I have either update the phone within Safe Mode or take the phone to Support Center in Cairo and they will update it manually within 2 hours.
I guess there is a missing update my phone needs to get: 1.27.466.5 to 1.27.466.7 and that must be manually updated.
I hope this helps some one out there.
I have the same problem. so what is the solution only going to the software support for them to update.
You have two options actually:
1. Wait the update to come to your phone
2. Go to the support center and do the update
I went to the support center and upgraded my phone to froyo, It took 2 hours, and they did for free, I'm now a happy FroYo phone owner .
My phone now has SW# 3.30.415.6
Remember to backup all your data and apps before you go, they will do a factory data reset to the phone.
Working hours of the support center is from 11AM to 6PM.
Can you softroot it and make a dump of /system.
Sent from my HTC Legend
BlaY0 said:
Can you softroot it and make a dump of /system.
Sent from my HTC Legend
Click to expand...
Click to collapse
I tried already using "Universal Androot 1.6.2 beta 5", did not work, do you have another way that is compatible with FroYo 2.2?
Download Tools.zip
We will need to do a backup of the SYSTEM partition of your phone.
1- Use VISIONary to temp root your phone but make sure USB Debugging is enabled for it to work.
2- Extract the Tools.zip to c:/tools
3- use CMD command prompt and type below commands
cd c:\tools
4- push busy box to your phone
adb push busybox /data
adb shell chmod 755 /data/busybox
5- make a copy of the system parition
adb shell
su
/data/busybox tar -cv -f /sdcard/system.tar /system
6- finally upload the system.tar file from the root of your sdcard.
zorbakun said:
4- push busy box to your phone
adb push busybox /data
adb shell chmod 755 /data/busybox
Click to expand...
Click to collapse
I guess he will have to push it to /data/local or /data/local/tmp directory:
Code:
adb push busybox /data/local
adb shell chmod 755 /data/local/busybox
...and execute it from there:
Code:
adb shell
su
/data/local/busybox tar -cvf /sdcard/system.tar /system
Ok I'll try all of that, but I have 2 questions:
1. Is this a softroot and will go away once I restarted my phone?
2. Does this will collect my personal data with it when I TAR the system partition?
1. Yes.
2. No.
Sent from my HTC Legend
BlaY0 said:
1. Yes.
2. No.
Click to expand...
Click to collapse
ok, I'll enjoy a little adventure today
v77 said:
ok, I'll enjoy a little adventure today
Click to expand...
Click to collapse
thx alot we are waiting for you
P.S which branch u went in jovitronix,? or did u went to vodafone (which sell the phone on egypt) ? and which number did u called,I barely get any useful info from calling them.
I am done , I am uploading a 131.6MB system file (230 MB TAR compressed in zip), once it finished I'll provide a link to download it.
aelsharawi said:
P.S which branch u went in jovitronix,? or did u went to vodafone (which sell the phone on egypt) ? and which number did u called,I barely get any useful info from calling them.
Click to expand...
Click to collapse
Call HTC call center, not Vodafone's, and you just need to ask the right questions.
I went to Jovitronix Giza branch,
address: 17,El-mathaf el-zeraey& Dr.shahin street., Infrontt of Ezz El-arab, below 6th October bridge, El-Agouza,Egypt.
GPS: http://maps.google.com/maps?q=%2030.0476%20%2C%2031.2142
Thx a lot for help,u really saved lots of ppl on Thai from.
Viva Egypt !
Sent from my HTC Legend using XDA App
@ BlaY0
Kindly prepare a zip Rom update from this rpm ,I use ur B 0.7
Sent from my HTC Legend using XDA App
A very huge THANK YOU for your help man!
VIVA EGYPT
waiting the uploaded file
@aelsharawi and @mdableh
You are quite welcome, uploading still in progress, my ADSL upload is a little bit slow.
i keep refreshing this thread every 2 min
mdableh said:
i keep refreshing this thread every 2 min
Click to expand...
Click to collapse
U know what to do with this tar file,or shall we wait for BlaY0 ??
I cant wait testing arabib on froyo !
hi.. after following the instructions on how to downgrade my phone, and obtain root, i have, and after i had my foryo rooted, i downloaded RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2 because my original intent was to have a rooted gingerbread and it didn't make much sense to have roms provided by htc itself.
but now i see i don't have root, so oops, i guess i was wrong.
so do i have to go though the whole kaka procedure again, and then find a custom rom, because my end game, is to have as close as possible a rooted gingerbread as close as possible to the original HTC rom. where can i get one?
oh, and what's the difference between the asia and wwe? does any of them handle hebrew bidi writing correctly (without applying the patch?)
I think there is a way to root gingerbread, or you have to downgrade. At either rate, you want to get to a place where you can flash your own ROM. Having clockworkmod installed would be just fine.
Then you would take the stock gingerbread, extract and unzip it, add Superuser and su, make the boot insecure, repack it for flashing, flash via CWM, and presto- rooted stock gingerbread. If you want to build in hebrew bidi writing, you can add that too.
There might be a few rooted stock gingerbread roms out there, but it seems that the trend is toward cooked up versions, rather than stock.
AFAIK i don't there's a way to root gingerbreak, it's un-rootable, that's why i downgraded in the first place. i think i can do it again, question is:
where do i find the stock gingerbread rom? is it in the RUU exe? if so, how get it out from there, without installing it
second, how on earth would i do all the things you said (add su,make boot insecure,repack,flash cwm).
is there a guide out there for all there above?
I think there is a some software for windows that will allow you to extract the rom from the RUU. I don't use windows, so I don't know anything about it. I've seen some posts about it, so I can say it seems to involve using the RUU to almost install the ROM, but at the last minute, just stop and the ROM will be extracted into one of the temp directories. You just use the RUU to extract the rom, not install it.
As far as all those other steps, I think all the information is scattered about xda.
Here's some information about the insecure boot image. It's for the transformer, but it's essentially the same thing, except for the blob parts. You'll have to use something like splitbootimg or bootunpack, and mkbootimg (search for them) instead of blobunpack.
http://forum.xda-developers.com/showthread.php?t=1193737
This might be more helpful:
http://forum.xda-developers.com/showthread.php?t=1100189
As for the other parts, you can use some of the other updates and zip files as a guide to figure out how to unpack, mod them, and repack them. I think there might be a rom kitchen script that will do this too, but I can't speak to that either.
Sorry if this sounds so complex- it's not that bad once you've done it once. I have a rooted stock GB that I made this way from the GB update, but it's the US version. Let me know when you have the WWE version extracted.
ok, let's take it one step at a time, (maybe we'll make a guide out of it
i activated the but i never continued instead i used process explorer to find out which files it's holds, so i got the temp directory and extracted rom.zip a 260 mg file (containing various img files)
now what?
btw is this relavent? http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
yea, i've seen it is, but one issue is that where do i get the cpio and makebootfs, (if i need to compile stuff, this is where i stop, i allready downloaded the perl scripts, as well as GZIP
ok, so far so good.
That link is exactly what you need. You can use that info to unpack the boot.img and make it insecure "ro.secure=0" by editing the default.prop file in the ramdisk.
I think some of the links to the tools might not work, but these will work instead - https://github.com/AndroidRoot/BootTools
Use the guides to mod and then repack the ramdisk
put the kernel and the modded ramdisk back together with makebootimg. There might be some specific command lines and kernel addresses- the hdrboot tool will show you want they should be from the original boot.img
Also, could you upload the zip file or PM me a link? This would be a perfect project for a guide.
ok wait, which tools am i missing? i have a windows machine (ultimate 7 64 bit) and the boottools needs to be compiled, (i don't have developer studio installed just eclipse)
so far i have the following tools:
repack-bootimg.pl
unpack-bootimg.pl
split-bootimg.pl
cpio for windows
gzip
what zip file?
(i'm going to sleep now as i'm in israel,i will "boot" in 6 hrs, luckily i have a vacation tommorow, so i hope we'll have time to finish this.
I think you might need gunzip to extract the ramdisk. unzip might work, but I'm not sure with Windows.
The zip is the rom.zip which has the rom.
I seem to recall there being at least 2 rooted stock ROMs in the dev forum. I think the one I've used was posted by either suilmagic (may be siulmagic), or rmk40. Xboarder56 posted one some time ago, but he started stripping things out that I used, like QuickOffice. If nothing else, this finally drove me to use Titanium backup...
Sent from my HTC Vision using Tapatalk
Yeah, I guess a search would take some of the fun out of it....
http://forum.xda-developers.com/showthread.php?t=1169004
actually i DID google "rooted stock rom desire z"
but i could find anything for sure, that's why i posted this, is this rom appear in the developer list of roms linked in the downgrade wiki? because i couldn't find it there either, would be nice if it was added.
No worries- I didn't actually search for it- I just paged through some of the dev sections.
I think you'll have flash it using CWM recovery.
great, i'm assuming CWM is Clockwork something?
Yup- look for the 3.x version. There was a 5.x, but i think it has some issues.
ok, so now, i must re-downgrade, root,
http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
get rom manager, and ah... wait, what's the update.zip? is that actual image i need to place on the sdcard?
That wiki seems kinda old- I don't think the stock recovery will flash the update.zip
This is more up to date and specific for the G2/DZ:
http://forum.xda-developers.com/wiki/HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
yea i've read that one (that's how i rooted in the first place.
isn't there a way to short ciruit this somehow and instead of pc10img have the update itself installed ? or is it because it's a an OTA, i have to do the whole thing?
looking at the image, i think i'm missing someting it looks like i can somehow use the scripts inside the image when i get temp_root (meaning i won't have to update the original image. am i wrong?
ok i've gone through the motions over and over, finally rooted it, have rom manager, clicked flash recovery, copied the zip file for rom i wanted to the root of sdcard, selected it rom manager, rebooted, now i selected apply update from sdcard,
now i see the hat signal and nothing happens, (i also selected backup rom and wipe cache and data)
i also noticed that i have install zip from sdcard, but i didnt' select it, how long should it take?
ok i FINALLY managed to install (it actually i pressed power button again and immdietly returned the cwm main menu, from then on, i chose reboot, i think it's moved on.
problem is, some things looked odd, for example the phone bar on the buttom, looks distorted, when i click on the application list i can only see half the list (meaning half the screen shows the list although i can scroll up and down the buttom half remains blank..
never mind it's ok now after re-boot..
btw i tried creating a batch file like so:
adb shell cat /dev/msm_rotator
rem expected output
rem /dev/msm_rotator: invalid length
pause
rem temp_root
rem adb push fre3vo /data/local/tmp
rem adb shell chmod 777 /data/local/tmp/fre3vo
rem adb shell /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
echo wait for device to reconnect
pause
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/misc_version -s 1.00.000.0
adb shell sync
adb shell dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
rem expected output is:
rem 1.00.000.010+0 records in
rem 10+0 records out
rem 10 bytes transferred in 0.001 secs (10000 bytes/sec)
pause
rem downgrade
rem wget http://www59.multiupload.com:81/fil...118187CA1236F3BA6767A7/1.34.405.5_PC10IMG.zip
adb push 1.34.405.5_PC10IMG.zip /sdcard/PC10IMG.zip
adb reboot bootloader
but it didn't workout so much, don't know why it said something about it couldn't write recovery img file
Umm if you already rooted via the xda wiki then you should've had a bootloader that was engineering s-off right? Just saying because you could've flashed a custom rooted rom through bootloader and not had to re-root, that is unless the ruu applied an updated bootloader with s-on. Maybe boot into bootloader and see if the top line says PVT ENG S-OFF, worth a look anyway, could save you some headache
Sent from my Bulletproof G2
actually i'm haveing another headache a couple actually, for some reason, during the restore, it failed to download google maps among the gailion apps i downloaded, now i can't download no matter, i tried installing it manually, and it worked, but i can't see in the market.
the market on the web site says the application is not compatible.
also when i tried using anysoft keyboard and use the hebrew fonts, even though it installed i still couldn't get the keyboard.
right not i have no idea what's the state of my phone.