Related
hello all, just trying to get a little input on the correct procedures for clearing the cache inbetween roms. i recently swithed from cyanmod 4.1.6 to Drizzy's Hero-V1.2r1 . Ive tried several commands in console so far to wind up reading something along the lines of : not found. Could someone inlighten me with the correct commands to do this or even the correct steps such as wipe, flash , yada yada and then what commands. thanks in advance , veritas
ronrey, so ronreyyyy, so ronrey im all aloonnneeeee
When you switch roms the only thing you need to do is wipe your ext partition and wipe your phone (alt + w). I use Ubuntu to clear my partition, but there are commands to do it if thats what your asking.
supremeteam256 said:
When you switch roms the only thing you need to do is wipe your ext partition and wipe your phone (alt + w). I use Ubuntu to clear my partition, but there are commands to do it if thats what your asking.
Click to expand...
Click to collapse
when u switch roms a small trace of them remains behind in the dalvik folder in the internal that doesnt just get cleared using alt+w so there are a set of commands to handle this task and i believe they go something like this rm -rf system/sd/dalvik-cache. along with some pre and post commands, that are the ones im refering to.
actually here is a direct quote of what i found, i just couldnt get these commands to work, so im thinking maybe they differ when switching to hero, maybe not..but they didnt work for me>>>>>>>>>>>>>>>>>>>>>
Monday, 31 August 2009 18:51 by Simon Walker
--------------------------------------------------------------------------------
User Rating: / 1
PoorBest
--------------------------------------------------------------------------------
So I started running into some performance problems with the Enomther ROM and was considering removing it and going back to Cyanogen. I decided to have a quick chat with Enomther and he gave me some things to do. The results are even more amazing than the first install.
I found out that the dalvik-cache gets carried over between ROM installs and that it can cause problems and that I should delete it, wipe my phone and start again. Enomther gave me this little guide to follow:
Ok ... so reboot into cyanogen's recovery
Press (Alt+x) to enter the console
Enter the following commands ...
mount system
mount system/sd
rm -rf system/sd/dalvik-cache
umount system/sd
umount system
recovery
This will bring you back to recovery, from there perform the "Data Wipe" option in the menu.
When it's done reboot and you should be all good. Of course you'll have to redo your settings, but your apps will reinstall properly.
I am frustrated that everytime an new release is out gotta reprogram my phone.
rm -rf /system/sd/*
search
sillyshyme said:
I am frustrated that everytime an new release is out gotta reprogram my phone.
Click to expand...
Click to collapse
Wiping your ext should not be an issue unless you're using Drizzy's "builds". If you're switching ROMs then you will have to wipe - get over it, but there should be "no wipe" updates when updating the a new version of the same ROM.
sillyshyme said:
I am frustrated that everytime an new release is out gotta reprogram my phone.
Click to expand...
Click to collapse
so i just noticed you had 27 posts, and im pretty sure all 27 have been about not wanting to wipe when switching roms, or complaining that you keep getting a boot loop. its just the dirty truth, if you wanna avoid a bootloop follow the info in the thread in my signature. if you dont wanna wipe, then dont switch, plain and simple.
SEARCH!!!!
palosjr said:
so i just noticed you had 27 posts, and im pretty sure all 27 have been about not wanting to wipe when switching roms, or complaining that you keep getting a boot loop. its just the dirty truth, if you wanna avoid a bootloop follow the info in the thread in my signature. if you dont wanna wipe, then dont switch, plain and simple.
SEARCH!!!!
Click to expand...
Click to collapse
Oh snap tellin it like it is..
I feel nice today, you're in luck, but this is the only post I'm writing to explain this procedure to you:
1. Reboot into recovery (Home + Power)
2. Backup NANDROID (or switchrom if you know how)
3. Enter into the console (alt+x)
4.
Code:
mount /system/sd
rm -rf /system/sd/app_s
rm -rf /system/sd/dalvik-cache
5.
Code:
ums_enable
6. Go into sdcard thru windows or whatever and then grab the data.img from the nandroid folder or switchrom folder depending on which one you used and place it in the same folder as fastboot (Go search if you don't know how)
7.
Code:
ums_disable
8.
Code:
recovery
9. Repair Filesystems (alt+f) (I think...)
10. Wipe data (alt+w)
11. Flash ROM of choice. (I've done this with practically every Hero flavor out there, should be no problem unless you cut corners in my directions some where... shame on you...)
12. Reboot phone when it finishes.
13. Wait for phone to get to setup page. Then, once there, reboot your phone again, but this time into bootloader (Camera + Power). You must wait for it to load the setup or this won't work.
14. Once fastboot is connected to the phone and can detect it (From connected PC):
Code:
fastboot flash userdata data.img
fastboot reboot
15. Wait for phone to boot up.... and bam, all wallpapers, lockscreen, program settings, mms, sms, contacts, etc. are already set up and your old settings + new ROM is ready to rock.
1. I had a rooted phone with CyanogenMod 4.1.9999
2. I downloaded Original System Image (signed-dream_devphone_userdebug-img-14721.zip) from http://developer.htc.com/adp.html
3. I updated the phone with the zip file
Now I'm getting an exclamation screen when I try to get into recovery scree (Pressing Home button during boot)
I tried to downgraded using RC29 Image: http://android-roms.googlecode.com/files/DREAIMG-RC29.zip - Followed first 6 steps from http://forums.tmonews.com/index.php?topic=8970.0
I'm not able to update or do anything with the phone now.
PLEASE HELP!!!!
my guess would 2 be push alt+l and a list of options will come up! Also dont use the system image from htc.com use the recovery image 2 go back 2 whatever version you want it 2... make sure u wipe before you downgrade/upgrade
please move
sorry to be the one to point this out...but please ask these questions in the q&a section as it is not development related
garok89 said:
sorry to be the one to point this out...but please ask these questions in the q&a section as it is not development related
Click to expand...
Click to collapse
I'm sorry for posting it here. I'm not able to move it to Q&A section. If there is an option, please let me know how.
law_ren_ce said:
my guess would 2 be push alt+l and a list of options will come up! Also dont use the system image from htc.com use the recovery image 2 go back 2 whatever version you want it 2... make sure u wipe before you downgrade/upgrade
Click to expand...
Click to collapse
Thanks law_ren.
I get 3 options when i press Alt+L
1. Alt+L Toggle log text display
2. Alt+S apply sdcard:update.zip
3. Alt+W Wipe Data/factory reset
I renamed the android 1.6 system image to update.zip
[snap]
Verifying update package...
E:No signature (5 Files)
E:Verification failed
hifake said:
Thanks law_ren.
I get 3 options when i press Alt+L
1. Alt+L Toggle log text display
2. Alt+S apply sdcard:update.zip
3. Alt+W Wipe Data/factory reset
I renamed the android 1.6 system image to update.zip
[snap]
Verifying update package...
E:No signature (5 Files)
E:Verification failed
Click to expand...
Click to collapse
The same happens with recovery image signed-dream_devphone_userdebug-ota-14721.zip
I say flash another recovery.img via fastboot.
Hi I have a problem like you....my G1 load only in recovery mode(Hold power=recovery, hold home+power=recovery, camera+power=recovery)
Did you fix your G1??? Please help me fix it
EvGeNN2007 said:
Hi I have a problem like you....my G1 load only in recovery mode(Hold power=recovery, hold home+power=recovery, camera+power=recovery)
Did you fix your G1??? Please help me fix it
Click to expand...
Click to collapse
I haven't fixed it yet. Am not able to place the recovery image using fastboot - my phone is not recognized by the computer
Work around I've found for flashing the recovery image if you can't figure out fastboot (I've never got it to work) is like this:
1. Follow the root procedure.
2. Install the most recent CM rom without using the HTC image (reason I do this is he's got some linux commands built into his ROM that aren't installed in the vanilla android build).
3. Download the cm-recovery-1.4.img to your sd card (or whichever recovery image you like)
4. Run terminal commands like so:
$su root (the reason I do this is it gives you higher level access to the system than just su, and I've found it doesn't work with just su for some reason)
#flash recovery /sdcard/cm-recovery-1.4.img
#reboot
5. Hold your home key as it powers up, and you should have the new recovery image installed.
Of course, I'd say do a full wipe, then install the ROM, and go through the fix permissions and clear cache.
JonnyFlash said:
Work around I've found for flashing the recovery image if you can't figure out fastboot (I've never got it to work) is like this:
1. Follow the root procedure.
2. Install the most recent CM rom without using the HTC image (reason I do this is he's got some linux commands built into his ROM that aren't installed in the vanilla android build).
3. Download the cm-recovery-1.4.img to your sd card (or whichever recovery image you like)
4. Run terminal commands like so:
$su root (the reason I do this is it gives you higher level access to the system than just su, and I've found it doesn't work with just su for some reason)
#flash recovery /sdcard/cm-recovery-1.4.img
#reboot
5. Hold your home key as it powers up, and you should have the new recovery image installed.
Of course, I'd say do a full wipe, then install the ROM, and go through the fix permissions and clear cache.
Click to expand...
Click to collapse
Am not even able to access terminal. I get the following 3 options only
1. Alt+L Toggle log text display
2. Alt+S apply sdcard:update.zip
3. Alt+W Wipe Data/factory reset
hifake said:
Am not even able to access terminal. I get the following 3 options only
1. Alt+L Toggle log text display
2. Alt+S apply sdcard:update.zip
3. Alt+W Wipe Data/factory reset
Click to expand...
Click to collapse
You won't be able to use terminal from recovery until you have a thirdparty recovery image installed. The steps I've listed are for a working phone, and I'm sure that's where part of your problem is. I'd suggest doing a wipe (Alt+W) and going through the root process again. When you get the CM Rom, change the name of it to update.zip, then try the steps I mentioned. I'd suggest having a separate SD card with just DREAMIMG.nbh installed on it for emergencies (especially if you're going to partition your main card).
Thanks
2) Install the most recent CM rom without using the HTC image(What is it? Can explane?)
4) Terminal as i understand its Telnet?
Can i do works a boot mode and then downgrade it to RC29?? Because after it i'll know what to do... Thanks!
EvGeNN2007 said:
Thanks
2) Install the most recent CM rom without using the HTC image(What is it? Can explane?)
4) Terminal as i understand its Telnet?
Can i do works a boot mode and then downgrade it to RC29?? Because after it i'll know what to do... Thanks!
Click to expand...
Click to collapse
Basically to get this working you're going to need to downgrade to RC29 first - so follow the root instructions.
CM = CyanogenMod ROM. To get his working fully you need two roms, which are the HTC Developer ROM and the 4.x ROMs he created (reason being legal distribution of software), but for my instructions, on his ROM page, you're going to skip his instructions, just download his ROM, rename it to update.zip and just flash it from the stock recovery, just so you can get to the terminal once the phone boots up and load terminal (it's in the programs tray). When another screen pops up asking if you want to allow it to use SU functions (it will as soon as you type "su") hit allow.
Terminal is a program downloadable from the Market, it's included with the CM ROM.
His instructions for install are not going to work unless you have a thirdparty recovery image, which at this point from the description, the triangle with the exclamation point is the default system recovery image.
CM Rom page
You should be able to find the Root posts and choose a customed recovery image, there's about 4 or 5 really good ones, I use Cyanogen's, thus my instructions on how to flash it.
You're fortunate that you're getting to the stock recovery, means your phone isn't bricked.
JonnyFlash said:
You won't be able to use terminal from recovery until you have a thirdparty recovery image installed. The steps I've listed are for a working phone, and I'm sure that's where part of your problem is. I'd suggest doing a wipe (Alt+W) and going through the root process again. When you get the CM Rom, change the name of it to update.zip, then try the steps I mentioned. I'd suggest having a separate SD card with just DREAMIMG.nbh installed on it for emergencies (especially if you're going to partition your main card).
Click to expand...
Click to collapse
I have successfully installed RC 29
FW 1.0
Baseband 62.33.20.08H_1.22.12.29
Kernel: 2.6.25-01843-gfea26b0
Build: kila-user 1.0 TC4-RC29 115247
But Am not able to download telnet (or any other app) from market. I have tried several times with wifi & Cell data .
hifake said:
I have successfully installed RC 29
FW 1.0
Baseband 62.33.20.08H_1.22.12.29
Kernel: 2.6.25-01843-gfea26b0
Build: kila-user 1.0 TC4-RC29 115247
But Am not able to download telnet (or any other app) from market. I have tried several times with wifi & Cell data .
Click to expand...
Click to collapse
Not sure what you mean? Telnet for these intents and purposes is basically just a command. The page on how to root has become pretty convoluted at this point. The part where it tells you to type 'telnetd' is just running a script which is an exploit in the old releases of android. You won't be messing with Terminal really until you get to the point where you've updated the rom. From this point, I'd suggest downloading this root.apk from your browser, install it, allow it, follow the instructions step by step in the program.
My problem consist of that i can't turn on my phone and i can't get into bootloader...only recovery can you give me a link for RC29 download and then install it from recovery on my g1 from recovery.
Thanks!
EvGeNN2007 said:
My problem consist of that i can't turn on my phone and i can't get into bootloader...only recovery can you give me a link for RC29 download and then install it on my g1 from recovery.
Thanks!
Click to expand...
Click to collapse
You're probably going to need a card reader...here's the instruction for rooting with a download for the RC29.
http://forum.xda-developers.com/showthread.php?t=442480
I know all this steps but i Tell that i CAN'T get into boot mode and in boot downgrade from DREAMIMG.nbh to RC29... In that All my problem...
How can i flash to RC29 from Recovery Mode?
EvGeNN2007 said:
I know all this steps but i Tell that i CAN'T get into boot mode and in boot downgrade from DREAMIMG.nbh to RC29... In that All my problem...
How can i flash to RC29 from Recovery Mode?
Click to expand...
Click to collapse
You don't...with the DREAMIMG.nbh or any .nbh file you start up the phone holding power+camera. The recovery mode looks for an update.img file. You'll make it through, don't get frustrated.
Here's a more updated rooting guide:
http://forum.xda-developers.com/showthread.php?t=553416
Hello!
I followed this guide and read the comments of everyone, and it's a reliable guide to rooting and installing a new ROM. The rooting went perfect, so I decided to go further and load cyanogen's latest ROM.
Power off your phone.
Boot into recovery mode. (Press and hold the Home key, then hit the power button).
Before you flash a rom file, perform a wipe. Press Alt+W to wipe the data and cache folders. You must wipe when going form different builds of Android.
Wait for the wipe to finish and the recovery image to display again, then select “apply any zip from sd”. Flash the zip file of your choice.
After flashing any zip you should be able to reboot your system and watch it load to the home screen.
After changing Android builds, it came take several minutes for the first boot. If you phone hangs on the animated Android logo, this is because you did not perform a wipe. If you are stuck in a boot loop, return to the recovery image and make sure you wipe.
Click to expand...
Click to collapse
-Taken from the guide
At the first time I rebooted it took me back to recovery, so using logic I rebooted again and now it is stuck at the T-Mobile G1 screen (the one before it normally shows the android)...
I know it's supposed to take several minutes.. but 30minutes is ridiculous -.-"
Can somebody please help me out before I do something stupid and remove the battery? Thanks so much..
You need to read a bit more then, because you would have learned that you have to install the 1.6ADP fro Htc before installing a cyanogen rom, that is one of the things you would know if you followed the guide in his thread...
-Best Regards
http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
Don't think so It didn't say anything in this guide about that and several comments below recently show that they succeeded with the process..
tk112190 said:
http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
Don't think so It didn't say anything in this guide about that and several comments below recently show that they succeeded with the process..
Click to expand...
Click to collapse
You have to listen to cyanogen plus that might be a different rom like enom or something.Cyanogen has a different maybe tricky install method.
You need to goto his thread.
-Go to http://developer.htc.com/adp.html
-DL the 1.6 "recovery image" the file name is - signed-dream_devphone_userdebug-ota-14721.zip
-Then DL CyanogenMod-XXXX
-put them both on your SD card
-Boot up into Amon_RA recovery by rebooting and holding the home button, do a wipe.
-update using any zip to that "recovery image" (signed-dream_devphone_userdebug-ota-14721.zip)
(it should auto reboot install radio then reboot again and load back up to the CMrecovery img screen)
-Then update any zip usig CyanogenMod (update-cm-xxxx-signed.zip)
-Then reboot the phone
Thanks a lot man.
I found the 1.6 ADP file and I have it downloaded onto my computer. Is there anyway I can put this on my SD card? It won't let me.. :/ If I could somehow get this on there, run it.. and THEN run the cyanogenrom.zip I think it could work again?
You need to delete the partitions with console while in recovery mode.
1.console
3.parted dev/block/mmcblk0
4.print
rm 1
rm 2
rm 3
quit
reboot recovery
Dont rename any of the files just leave them.
Now try it on your pc.
You need to delete the partitions with console while in recovery mode.
1.console
3.parted dev/block/mmcblk0
4.print
rm 1
rm 2
rm 3
quit
reboot recovery
Dont rename any of the files just leave them.
Now try it on your pc.
Thanks a lot for the help, I really appreciate it.
I took your advice and did those steps and it rebooted me into recovery like you commanded. I plugged it via USB into my computer hoping that the computer would recognize it and let me put the file on the SD card - but to no avail.
What is the next step I can take?
http://code.google.com/p/sapphire-port-dream/
I loaded the radio first...
and then I loaded the SPL...
and then I loaded the ROM...
I didn't go out of order. Was the problem that I didn't have the 1.6 ADP on my SD?
@Ace42: If I get a card reader and add the 1.6 ADP (signed-dream_devphone_userdebug-ota-14721.zip) to my sd card.... and load it. Can you tell me what to do from there?
Do I load that zip and then reload the ROM?
You may want to try Dwang1.13 rom. I don't think his rom requires the extra step to get the google apps.
Phone will only boot into clockworkmod recovery, even after pulling battery and powering up using only the power button, it goes into recovery.
Here is what happend leading up to it:
- flash through rom manager the new clockworkmod
- used fireat's mod with mtd 125 2
- flashed aospCmod 2.3.3
- everything booted fine
- re-did firerat's mod with mtd 102 2
- now bootlooping into clockwork mod
I tried duplicating what worked initialy with no luck. Tried booting into hboot and htc reset menu (power + home + back) but not matter what it only goes to clockworkmod recovery.
For my install steps I followed romrepro "install from other rom" guide here: romrepo.info/wiki/index.php?title=Install_from_another_ROM
I have also tried the following:
- restoring through nandroid
- recovery flasher v1.3 to flash older version of clockwork
- lots of stinking google
All have resulted in no success.
Please help!
Are you s-off? You probably shouldn't mess with firerats if you're not. Mount your sdcard in recovery and change your mtd settings and then flash your rom and reflash fr boot.
~maybe I set it too high...
Thank you for responding. I am not s-off and I already tried changing the mtd part, flash rom, flash boot, and it still autoboots back into recovery.
I re ran the mtd part map with the following:
- 102 2
- 105 2
- 110 2
- 115 2
- 120 2
- 125 2
- 190 2
I also tried flashing aospMOD v9.2.2 (which is what I was originaly using) flashing boot and still no success.
Wait, so it opens recovery by just turning on your phone?
~maybe I set it too high...
bphem3 said:
Thank you for responding. I am not s-off and I already tried changing the mtd part, flash rom, flash boot, and it still autoboots back into recovery.
I re ran the mtd part map with the following:
- 102 2
- 105 2
- 110 2
- 115 2
- 120 2
- 125 2
- 190 2
I also tried flashing aospMOD v9.2.2 (which is what I was originaly using) flashing boot and still no success.
Click to expand...
Click to collapse
If you're changing mtdpartmap.txt (try 125 25) you need to wipe ALL, flash fr-recovery, wipe ALL again, reboot recovery (safely), flash rom/gapps, flash fr-boot, reboot. Once you're in the rom, open terminal (su) or adb shell and type "df -h" and it will show you how much system, data, and cache, are using, you then can change your mtdpartmap.txt accordingly, follow the steps I just listed.
Wait, so it opens recovery by just turning on your phone?
Click to expand...
Click to collapse
Yes, exactly.
If you're changing mtdpartmap.txt (try 125 25) you need to wipe ALL, flash fr-recovery, wipe ALL again, reboot recovery (safely), flash rom/gapps, flash fr-boot, reboot. Once you're in the rom, open terminal (su) or adb shell and type "df -h" and it will show you how much system, data, and cache, are using, you then can change your mtdpartmap.txt accordingly, follow the steps I just listed.
Click to expand...
Click to collapse
I will give this a try and report back. Will either be after lunch or this evening.
If you're changing mtdpartmap.txt (try 125 25) you need to wipe ALL, flash fr-recovery, wipe ALL again, reboot recovery (safely), flash rom/gapps, flash fr-boot, reboot. Once you're in the rom, open terminal (su) or adb shell and type "df -h" and it will show you how much system, data, and cache, are using, you then can change your mtdpartmap.txt accordingly, follow the steps I just listed.
Click to expand...
Click to collapse
Gave it a try, still boots directly into recovery.
bphem3 said:
Gave it a try, still boots directly into recovery.
Click to expand...
Click to collapse
what rom and gapps did you flash, and how are you "booting" - like with what buttons?
also, please list the EXACT steps you took. And what version of hboot do you have, and what recovery, and what version of firerat?
il Duce said:
what rom and gapps did you flash, and how are you "booting" - like with what buttons?
also, please list the EXACT steps you took. And what version of hboot do you have, and what recovery, and what version of firerat?
Click to expand...
Click to collapse
1. wipe data/factory reset
2. wipe cache partition
3. format /boot
4. format /cache
5. format /data
6. format /system
7. wipe dalvik cache
8. flash fr-recovery
9. repeat steps 1-7
10. reboot recovery (from advanced menu)
11. flash rom
12. flash gapps
13. flash kernel
14. flash boot
15. reboot system (from main menu)
aospCMod-HC-20110421-signed.zip
gapps-gb-20110325-signed.zip
aospCWMod-HC-20110421.img
DecaFuct-691.zip
FR-boot-v1.5.6.zip (I have tried both 1.5.6 and 1.5.3)
FR-recovery-v1.5.6.zip (I have tried both 1.5.6 and 1.5.3)
mtdpartmap.txt
Not sure on the hboot. When I simply turn the phone on it boots to recovery. I used to have to press and hold power + home to get into recovery. I also used to be able to press and hold power + home + back and get intot he htc reset menu (or whatever it is). Prior to this happening I never tried to get into hboot (vol up/dn + power) however if I try to now it just goes to recovery. All combinations I have tried it just boots to recovery.
bphem3 said:
1. wipe data/factory reset
2. wipe cache partition
3. format /boot
4. format /cache
5. format /data
6. format /system
7. wipe dalvik cache
8. flash fr-recovery
9. repeat steps 1-7
10. reboot recovery (from advanced menu)
11. flash rom
12. flash gapps
13. flash kernel
14. flash boot
15. reboot system (from main menu)
aospCMod-HC-20110421-signed.zip
gapps-gb-20110325-signed.zip
aospCWMod-HC-20110421.img
DecaFuct-691.zip
FR-boot-v1.5.6.zip (I have tried both 1.5.6 and 1.5.3)
FR-recovery-v1.5.6.zip (I have tried both 1.5.6 and 1.5.3)
mtdpartmap.txt
Not sure on the hboot. When I simply turn the phone on it boots to recovery. I used to have to press and hold power + home to get into recovery. I also used to be able to press and hold power + home + back and get intot he htc reset menu (or whatever it is). Prior to this happening I never tried to get into hboot (vol up/dn + power) however if I try to now it just goes to recovery. All combinations I have tried it just boots to recovery.
Click to expand...
Click to collapse
FYI step 13 is unnecessary, that kernel is already in aospCMod and boots at 691. I guess I would try FR-1.5.8 versions and see what happens (that's what I have), the steps look right to me. You could also try leaving out the gapps and see if just the rom boots, you could also try flashing the last working version of recovery you had (i.e. cwm 3.0.0.5). It's also possible you got a bad download of any one of the above items, so try new DLs too. Report back, I am now officially curious.
I am unsure how to flash another version of recovery, I always use RomManager and I am terrible with adb. I tried using some one of the herocimg.zip to "install from zip" and I kept getting "installation aborted".
I will try FR-1.5.8 and report back.
/me bangs head on keyboard
#eatshit1clickrootmethod!
/me bangs head on keyboard
#eatshit1clickrootmethod!
Click to expand...
Click to collapse
I first used adb and push and blah blah...... 8 months ago.
Then I discovered OneClick! I used to be way more into the technical side of this stuff and then got busy with work and now I am extra lazy!
FYI:
HERCIMG.zip is a partition zip flashable in hboot/bootloader and ONLY if you're s-off
HEROIMG.zip is the same thing, but for a GSM hero....
Hopefully you can figure it out. I hate to say it, but 99.9999999999999999% of the time something doesn't work that others have had success with, it's user error. I'm not trying to be mean, I often miss steps too and need to ask for help. I don't know what you COULD be missing since it sounded like you did everything right, but I would say re-read all the stuff you're doing and hope you see something you may have missed. Best of luck, and please report back if you fix it to help others who may see this thead in the future.
No offense taken. I have had plenty of practice with this with my phone and my wifes and never really had any problems other than user error that I usualy catch. And it's alwasy something silly like flash & wiping out of sequence.
Good information on the HERCIMG and HEROIMG, I did not know that.
Is there a way to RUU the phone from a recovery zip install, (seeming how that is all I can access).
bphem3 said:
No offense taken. I have had plenty of practice with this with my phone and my wifes and never really had any problems other than user error that I usualy catch. And it's alwasy something silly like flash & wiping out of sequence.
Good information on the HERCIMG and HEROIMG, I did not know that.
Is there a way to RUU the phone from a recovery zip install, (seeming how that is all I can access).
Click to expand...
Click to collapse
Not that I know of but you should be able to do it from the bootloader (hold volume down press power - from an off state) and run the RUU.exe from HTC.com.
lol, yeah, that just puts me back in recovery...
bphem3 said:
lol, yeah, that just puts me back in recovery...
Click to expand...
Click to collapse
Well that's nuts. I don't know how you don't have a bootloader, but you do have a recovery... anyway, I guess grab the FR-remove zip that correlates with whatever FR version you have and run the steps again, i.e. wipe all, flash FR-remove, wipe all, reboot recovery, etc. Hope that works. By any chance did you format /misc in the mounts & storage menu?
il Duce said:
Well that's nuts. I don't know how you don't have a bootloader, but you do have a recovery... anyway, I guess grab the FR-remove zip that correlates with whatever FR version you have and run the steps again, i.e. wipe all, flash FR-remove, wipe all, reboot recovery, etc. Hope that works. By any chance did you format /misc in the mounts & storage menu?
Click to expand...
Click to collapse
Format /misc is not listed anywhere. I'm at a loss. I have tried everything over and over and I am still getting the same results. The only thing left I can think of is to redo everything via adb. I'm not 100% on how these phones or linux devices work but it's as if there is something worng with the boot sector and/or sequence of the device.
It doesn't make sense that the first run at all this was flashing aospCmod (mtd 125 2, FR-1.5.3) and everything was working normal. I decided to go back and redo the process with (mtd 102 2, FR-1.5.3). Now this has to be where I or something screwed up. Maybe I did things out of order, got a bad flash, something but I do not know what. When I rebooted, just a normal reboot, it went directly into recovery. Now I have flashed a rom before and had the mtdpartmap.txt too low it caused it to hang on the first boot when the logo for the Rom was shown during loading. To fix this I just adjusted the mtdpartmap.txt.
This time things are different. When I power the hero up the phone vibrates, the white backdrop with green HTC comes up, it sits for approximately 5 seconds, then recovery loads.
bphem3 said:
1. wipe data/factory reset
2. wipe cache partition
3. format /boot
4. format /cache
5. format /data
6. format /system
7. wipe dalvik cache
8. flash fr-recovery
9. repeat steps 1-7
10. reboot recovery (from advanced menu)
11. flash rom
12. flash gapps
13. flash kernel
14. flash boot
15. reboot system (from main menu)
aospCMod-HC-20110421-signed.zip
gapps-gb-20110325-signed.zip
aospCWMod-HC-20110421.img
DecaFuct-691.zip
FR-boot-v1.5.6.zip (I have tried both 1.5.6 and 1.5.3)
FR-recovery-v1.5.6.zip (I have tried both 1.5.6 and 1.5.3)
mtdpartmap.txt
Not sure on the hboot. When I simply turn the phone on it boots to recovery. I used to have to press and hold power + home to get into recovery. I also used to be able to press and hold power + home + back and get intot he htc reset menu (or whatever it is). Prior to this happening I never tried to get into hboot (vol up/dn + power) however if I try to now it just goes to recovery. All combinations I have tried it just boots to recovery.
Click to expand...
Click to collapse
Something about these steps didn't seem correct to me, so went back and read.
After step 8. flash fr-recovery
It says you went back and repeated steps 1. - 7.
I believe you only need to repeat steps 4, 5, 6...the others are probably optional, but I'm pretty sure 3. format boot...is something you don't want to do AFTER doing fr-recovery. then again, I may be overthinking it, and might be completely wrong. I'm sure someone will tell me
My own personal rule is to not make any assumptions and follow the steps listed and don't add extras.
(also, I violate that rule occasionally and usually end up doing a lot more work)