Related
got my evo about a month ago. rooted lastnight since unrevoked finally pushed out their 3.3 version which is updated for my version of hboot (2.02). the root went very smoothly. i installed the latest cyanogenmod rom, only to discover there was no market or gmail app with the rom! wish i had known that before. after doing some research online, i found out i needed to flash or install a "gapps" apk. so, looked around for that for a couple hours and couldn't find it. i downloaded what i thought would be the right .zip file to get the market on my phone (a vending.apk that was listed in another thread having to do with this same issue). so anyway... downloaded that, moved it to the root of my sd card, flashed it through clockworkmod recovery (by the way, everything up until this point was perfect) and finally rebooted my phone... only it never rebooted. the white htc EVO 4G screen was there. then, black screen, as if it was about to begin the cyanogenmod boot screen and fully boot. but, no. it went from white evo screen to black screen... to OFF. after this, i couldn't even turn it on to get it into hboot or access recovery. tried to do that for two hours. and finally i was able to get in... so i tried doing a factory/data reset through recovery, then a cache clear, then reboot. nothing. same thing. went back into recovery, tried reflashing cyanogenmod rom again. nothing. tried flashing myn's rom. nothing. all i get is installation aborted.
i am pretty sure that this is not a complete brick since i am now able to access hboot and recovery. but if i can't flash anything... and i'm stuck in hboot and recovery and cant boot my phone... what the hell do i do now? please help me figure this out!! anybody have any good advice or a known fix...??
Boot into recovery. Do a factory reset. then wipe cache and dalvik catch. Re flash cynagon and let it boot. You then need to find gapps.zip. Boot into recovery flashing gapps.zip.
i did all that. step by step. and when i reflashed the rom, that is when it wouldn't install, saying installation aborted. but, i'm gonna do it again. let's see if my phone wants to play nice now...
brtnygrey said:
i did all that. step by step. and when i reflashed the rom, that is when it wouldn't install, saying installation aborted. but, i'm gonna do it again. let's see if my phone wants to play nice now...
Click to expand...
Click to collapse
If that does not work! you are going to have to update with sprint lovers rom, that is in a PCM36IMG.ZIP. Install it by holding the _vol and th power button, boot into boot loader, than it will search for the zip file and ask you if you want to update, say yes ans just weigh for it to be done. Its going to take few minutes first boot! just hold on. I hope this helps in anyway.
evolishesh said:
If that does not work! you are going to have to update with sprint lovers rom, that is in a PCM36IMG.ZIP. Install it by holding the _vol and th power button, boot into boot loader, than it will search for the zip file and ask you if you want to update, say yes ans just weigh for it to be done. Its going to take few minutes first boot! just hold on. I hope this helps in anyway.
Click to expand...
Click to collapse
do you think that sprintlovers rom will install even if no other rom will install? because... i was able to install Gapps.zip file just fine. but every rom i install is unsuccessful.
brtnygrey said:
do you think that sprintlovers rom will install even if no other rom will install? because... i was able to install Gapps.zip file just fine. but every rom i install is unsuccessful.
Click to expand...
Click to collapse
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk
mysteryemotionz said:
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
ok is the install through recovery supposed to be almost instantaneous? it didn't take a minute like every other rom. and after reboot (10 minutes ago) i'm still sitting on the white htc EVO 4G screen. i don't think this is working either. but i really do appreciate your help. any other suggestions? is there anything else through recovery that I can do (since i cant make it past that) that might fix my system? anything in partition? i'm so stuck!
mysteryemotionz said:
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
and also... when i go into hboot, and it runs through the "checking sd" thing before i can select options... it says "no image or wrong image". what?
Nothing is working!!
Did you try a rooted RUU yet?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs
Wipe everything twice first (just to be safe). Are you using Amon RA or Clockwork, by the way? The only other thing I can think of would be that your SD card isn't formatted properly, but that would have to mean you intentionally formatted it or put in a new one that didn't have the right files on it.
SilverZero said:
Did you try a rooted RUU yet?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs
Wipe everything twice first (just to be safe). Are you using Amon RA or Clockwork, by the way? The only other thing I can think of would be that your SD card isn't formatted properly, but that would have to mean you intentionally formatted it or put in a new one that didn't have the right files on it.
Click to expand...
Click to collapse
i am using clockwork. i've wiped so many times... but i can't make anything happen. and, i did format the sd card eventually, but not until a couple of hours ago... and only as a last resort because nothing else worked and i've been trying to fix this since last night, so i figured it couldn't hurt. but if that is part of the problem... how can i fix it? thanks for your response. i don't know what else to do other than take it in for a switch.l but if i can get into hboot... then sprint can too... and they will see that i'm rooted and void warranty. so am i completely screwed?
I had same issue.
I just reflashed the sprintlover rom (PC36IMG.ZIP) which came with Amon_RA recovery.
Then i installed the CM6 with Amon_RA recovery and everything works fine now.
Good that i did Titanium backup few days before
This is happening to me too. Almost everything he's describing is the same. Except I installed a gapps.zip and then it wouldn't boot after that. No matter what I flash, it either gives me a status 7 error and aborts the install or it may "install successfully" but it never boots. Also tried the pc36img.zip as well. I had a nandroid backup and tried to restore that, but that aborts saying cannot flash boot image. Tried a rooted and also an unrooted stock ruu, they won't work and the .exe version on a pc can't find my phone when I plug it in and power it on. Anyone have any Ideas for me. I can get more specific error messages and hboot numbers, etc. if needed.
I think you should get Amon recovery PCIMG zip file and change recovries and try everything again... IMO
Edit: I posted the Amon file and all you have to do is rename it to PCIMG.zip. Also I think the gapps you were looking for you can find on the cm site itself or within that thread. Sorry if it sounds like I a being negative but I see alot of people get on noob and I wondered why but unfortunately its because things like this happen. In the OP for CM6 it says to use Amon and backup your keys. Now if you get your phone backup you got to first check and make sure your RSA keys are in tact unless you backed them up already.
Joeykrim has a app on the market to check or there are numerous threads on what to do. Sorry and hope it works out for you if not INS is your friend
View attachment PC36IMG-Amon-V2.2.1.zip
playya said:
I think you should get Amon recovery PCIMG zip file and change recovries and try everything again... IMO
Click to expand...
Click to collapse
some people dont like clockwork with the evo's...thats just the general feeling im getting from the boards. i just got my evo rooted and what not. i use clockwork and it has worked well for what i need.
op, try amon like has been suggested.
tailsthecat3 said:
some people dont like clockwork with the evo's...thats just the general feeling im getting from the boards. i just got my evo rooted and what not. i use clockwork and it has worked well for what i need.
op, try amon like has been suggested.
Click to expand...
Click to collapse
Yea but have you tried Amon and from what I read and this is from developers Amon has a much better handle on things as far as backing stuff up, partitions and protection of keys.
I ran Clockwork on my wifes phone because to me its simple and works with Rom manager but after a while I just said F it and switched since it was messing up my backups. Hey to each his own..
Ok, I don't believe that your device is bricked. You may have flash the wrong gapps or something, but is should be easy to fix.
First, download these 3 files and put them on the root of your SD card:
Cyanogen 6 stable for evo
Latest gapps for HDPI
Calkulin's format all
Red through first, then follow my instructions EXACTLY:
1.) Boot into recovery.
2.) Flash Calkulin's all format. This will wipe everything that needs wiping. (everything but the SD card)
3.) Without exiting recovery immediately flash the CM6 .zip. Do not flash the gapps yet.
4.) Reboot the device now. It will boot into cyanogen, but will not have market or anything. Once fully booted, reboot to recovery.
5.) Do not wipe or anything, just flash the gapps HDPI.
6.) Boot the phone and enjoy.
Evo won't load any roms, can only get into clockwork recovery
Okay, so if I try your steps, just like before The install gets almost to the end, then I get:
"assert failed: write_raw_image ("/tmp/boot.img","boot")
E:Error in /sdcard/update-cm-6.1.2-supersonic-signed.zip
(Status 7)
Installation aborted.
Sorry Playya, I wanted to try this one more time first. I'm going to try loading Amon Ra now. do I need to rename it to pcimg.zip or should i just flash the current file name?
In case it helps anyone, I have
ClockworkMod Recovery v2.5.0.1
my boot loader screen shows
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.10.0001
MICROP-041f
TOUBH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010
Awesome, Amon Ra Worked, and now i'm up and running on cyanogen mod with google apps as well. My only problem now, is I can't backup, when I try it says oops... something went wrong! Please check the recovery log!
hcavlnch said:
Awesome, Amon Ra Worked, and now i'm up and running on cyanogen mod with google apps as well. My only problem now, is I can't backup, when I try it says oops... something went wrong! Please check the recovery log!
Click to expand...
Click to collapse
it may say oops if you battery level is low... I think Amon is so much better its just that Unrevoked puts Clockwork in with their root so people get lazy and leave it in... Amon - its the way to go.
1. Charge your battery and try again
2. Backup your wimax keys - then check how big the file is and hopefully its like 12 megs... If so keys may be ok
I'm pretty new to rooting and flashing, but did flash several ROMs over the period of a few months. Recently, I wanted to clean my phone up so I thought I'd start from scratch. I unrooted which which went well and then rooted again last night via Unrevoked (3.70). I used bootloader for AmonRa's 2.3 recovery which went well, made a nand, and flashed Miks 4.5 ROM. Since then, when booting into recovery, I see 'E: Can't open CACHE:recovery/log' and it worries me as I have no clue what it means. Also, and I'm unsure if it's even related, but my Market worn't download anything anymore.
Any thoughts/solutions?
Thanks in advance!
cdadams1223 said:
I'm pretty new to rooting and flashing, but did flash several ROMs over the period of a few months. Recently, I wanted to clean my phone up so I thought I'd start from scratch. I unrooted which which went well and then rooted again last night via Unrevoked (3.70). I used bootloader for AmonRa's 2.3 recovery which went well, made a nand, and flashed Miks 4.5 ROM. Since then, when booting into recovery, I see 'E: Can't open CACHE:recovery/log' and it worries me as I have no clue what it means. Also, and I'm unsure if it's even related, but my Market worn't download anything anymore.
Any thoughts/solutions?
Thanks in advance!
Click to expand...
Click to collapse
try booting into recovery and wiping your cache
I thought I tried that already per a suggestion I read somewhere, but it didn't work. Lemme try it again and I'll post back in a few.
Thanks!
if it doesnt work try downloading terminal emulator from the market (free) and run this command:
su
cd /cache
rm -rf *
do you have rom manager, believe rom manager lets you flash amon ra recovery, its an option at the bottom of the menu, if it lets you flash and you are able to go into recovery i would wipe cache, dalvik and data and the reflash the rom(you should probably download it again and put it in the root of your sd card, i say re-download just to make sure you didn't get a corrupted download the first time)
cdadams1223 said:
... Recently, I wanted to clean my phone up so I thought I'd start from scratch....
Click to expand...
Click to collapse
Next time just wipe EVERYTHING twice and flash THIS, then you will be stock and clean BUT still rooted
@blakeboys - Well, your suggestion worked. Apparently I tried wiping my Dalvik-cache and not just cache. This time I did both and voila...it worked. I'm now able to download apps from the market again. I haven't returned to recovery to see if I get that same error so I'm not sure about that.
@emcp422 - I do have ROM Manager, but I do not use it. It is not set-up yet to flash the latest AmonRA which is 2.3. I never had a problem of accessing my recovery. If it happens again, I will do as you suggested and re-download it and install it again.
Thanks for yall's help!
no problem, glad we could help ya
blakeboys said:
Next time just wipe EVERYTHING twice and flash THIS, then you will be stock and clean BUT still rooted
Click to expand...
Click to collapse
Will do...thanks man!
cdadams1223 said:
@blakeboys - Well, your suggestion worked. Apparently I tried wiping my Dalvik-cache and not just cache. This time I did both and voila...it worked. I'm now able to download apps from the market again. I haven't returned to recovery to see if I get that same error so I'm not sure about that.
@emcp422 - I do have ROM Manager, but I do not use it. It is not set-up yet to flash the latest AmonRA which is 2.3. I never had a problem of accessing my recovery. If it happens again, I will do as you suggested and re-download it and install it again.
Thanks for yall's help!
Click to expand...
Click to collapse
Actually ROM manager does flash Amon Ra 2.3 for some reason the app shows 2.2.2 or whatever but if you boot into recovery its actually 2.3
RileyGrant said:
Actually ROM manager does flash Amon Ra 2.3 for some reason the app shows 2.2.2 or whatever but if you boot into recovery its actually 2.3
Click to expand...
Click to collapse
That's good to know! Thanks!
Hi everyone... I have been doing a bit of searching with no luck so far. And I searched a lot but no luck in finding my stituation and don't want to screw up the phone completely...
I bought a D-Z used, Bell Rom. It showed to be S-Off, but when i checked to see if it was rooted with RootCheck, it said it wasn't. So I started the process of applying Visionary for Temprooting and then on terminal emulator, I got the error: exec format error...and, stupid me, decided to keep going. I followed the rest of the process, up to step 10 on http://theunlockr.com/2010/11/30/how...g2-htc-vision/.
But when i turned phone back on, it got stuck on the white screen with the green htc logo....
If I vol-down/turn on, i see:
Vision PVT ENG S-OFF
HBOOT-076.2000 (PC1012000)
MICROP-0425
RADIO-26.03.20.26_M
eMMC-boot
Aug 20 2010,16:51:01
HBOOT and the options:
FASTBOOT, RECOVERY, FACTORY RESET, SIMLOCK, SYSTEM INFO, IMAGE CRC
On system info it says
OS Ver.-1.34.666.5
When I put the battery in it, plugged into charger, it goes into ClockworkMod Recovery v3.0.0.5 and below the menu it says:
ClockworkRecovery v3.0.0.5
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
the phone says S-off: should I just copy some rom and launch the flashing? If so, a zip to the SD card is the way to go, right?
Or is something bad and should I attempt first loading a stock rom? (I guess not, because it says S-Off!).
It sounds like whatever you did in your rooting process wiped your system, causing the phone to be stuck at the htc screen. So yes, put a ROM zip on your sd card and try to flash it. I would wipe system before you do though. Again, it sounds like the systems already wiped, but it won't hurt anything to wipe again.
On another note, I don't know what the unlockr root process is, but afaik, the recommended rooting method is to stay away from Visionary and use the Gfree method in the G2 wiki. It's much safer than Visionary.
Sent from my HTC Vision using XDA Premium App
heybobitsme said:
It sounds like whatever you did in your rooting process wiped your system, causing the phone to be stuck at the htc screen. So yes, put a ROM zip on your sd card and try to flash it. I would wipe system before you do though. Again, it sounds like the systems already wiped, but it won't hurt anything to wipe again.
On another note, I don't know what the unlockr root process is, but afaik, the recommended rooting method is to stay away from Visionary and use the Gfree method in the G2 wiki. It's much safer than Visionary.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
What would you suggest? Any custom Rom as zip should do then? Any potential damage/ risk of bricking?
thanks!
santiargy said:
What would you suggest? Any custom Rom as zip should do then? Any potential damage/ risk of bricking?
thanks!
Click to expand...
Click to collapse
lucky you! - someone before you S-OFFed the phone!
read the stikies next time. http://forum.xda-developers.com/showthread.php?t=1025135
santiargy said:
What would you suggest? Any custom Rom as zip should do then? Any potential damage/ risk of bricking?
thanks!
Click to expand...
Click to collapse
first, download any untouched flashable sense rom (make sure it's not a full rom with hboot, radio etc, just /system)
place the rom.zip on your sd card
reboot with vol down
choose recovery
wipe cache and wipe data/factory reset
choose install zip form sd (not update), then select the zip and press trackpad
hopefully this is all you will have to do to make the phone functional again
here is a flashable rooted /system from a stock sense rom: http://forum.xda-developers.com/showthread.php?t=1012763
hope this will help
petarpLab said:
lucky you! - someone before you S-OFFed the phone!
Click to expand...
Click to collapse
thanks for you help. I'm trying it now.
I had tried the other method... but it didn't work out. I should have read more before going for what looked simpler - visionary.
I will report soon. Hopefully, i will have a phone and not a piece of wall...
THANK YOU!!!!! IT WORKED PERFECTLY. I GUESS I CAN NOW GO TO Cyanogen, right?
santiargy said:
at this point, I don't want to screw up anymore...
wipe cache, ok
wipe system? Not an option... got wipe data/factory reset. is that the option? you refer to?
Click to expand...
Click to collapse
yes, do this one.
p.s. sorry for the rant earlier.
Hmm.. maybe try this rom?
HTML:
http://forum.xda-developers.com/showthread.php?t=1074391
Someone on that thread mentioned fixing a bricked(or almost) phone with it..
Mkarin said:
Hmm.. maybe try this rom?
HTML:
http://forum.xda-developers.com/showthread.php?t=1074391
Someone on that thread mentioned fixing a bricked(or almost) phone with it..
Click to expand...
Click to collapse
this is a G2 rom, not DZ. it's dangerous to mix them if we are talking about full stock roms. bricks happen from such mixes.
santiargy, any success?
ah, i mised a post.
I am really glad to hear it worked.
I've been running 2.5.1.2 for awhile. Let ROM Manager install 3.0.0.8 for me, and now I get the dreaded "doesn't wipe ****" bug. No matter how many times I wipe, it doesn't wipe. I'm going to go back to 2.5.1.2 for now, but I don't want to be one of those guys holding up progress. So, what's the current flavor recovery that everyone likes?
Incredible w/Amoled screen.
jaykresge said:
I've been running 2.5.1.2 for awhile. Let ROM Manager install 3.0.0.8 for me, and now I get the dreaded "doesn't wipe" bug. No matter how many times I wipe, it doesn't wipe. I'm going to go back to 2.5.1.2 for now, but I don't want to be one of those guys holding up progress. So, what's the current flavor recovery that everyone likes?
Incredible w/Amoled screen.
Click to expand...
Click to collapse
Ain't seen you around these parts in awhile. The thing about the recoveries is since most Roms are now edify (do to gb) we have to use 3.X recoveries.
Generally 3.0.0.7 for Amoled and 3.0.0.8 for SLCD.
wildstang83 said:
Ain't seen you around these parts in awhile. The thing about the recoveries is since most Roms are now edify (do to gb) we have to use 3.X recoveries.
Generally 3.0.0.7 for Amoled and 3.0.0.8 for SLCD.
Click to expand...
Click to collapse
What he said
If ive helped you, please hit the damn thanks button!
jaykresge said:
I've been running 2.5.1.2 for awhile. Let ROM Manager install 3.0.0.8 for me, and now I get the dreaded "doesn't wipe ****" bug. No matter how many times I wipe, it doesn't wipe. I'm going to go back to 2.5.1.2 for now, but I don't want to be one of those guys holding up progress. So, what's the current flavor recovery that everyone likes?
Incredible w/Amoled screen.
Click to expand...
Click to collapse
Download vr superwipe, flash that after you wipe EVERYTHING, you will have no issues. I actually flash it, wipe, flash again, then flash rom. This wipin 3 times is a croc.
If ive helped you, please hit the damn thanks button!
I'm trying 3.0.0.7 right now. I'll report back if I still have wiping issues.
3.0.0.7 on my AMOLED works perfectly, not sure why anyone would wipe or flash multiple times. If your recovery isn't wiping properly, I don't see how executing the same command would yield different results. Although it does sound like the 3.0.0.8 recovery is bugged on AMOLED devices, not sure about SLCD.
To Jay, how do you know that the recovery isn't wiping correctly? Checking /system, /data, and /cache partitions in ADB after wiping them in recovery?
I've found this link helpful in understanding how CWM recovery works and what happens in the wiping process.
http://cvpcs.org/blog/2011-06-05/time_to_wipe_data/cache
To summarize, there's a 37MB difference in available space between flashing a ROM with 2.5.1.2, and flashing the same ROM with 3.0.0.x (7 or 8, tried both). For example, the ROM that I normally use gives me 679MB/748MB in available space. Flashing it with 3.x give me 642MB.
Any idea what's going on? I'm back on 2.5.1.2, and I'm happy with it. It works as I expect it to.
EDIT: Just wanted to state that reverting to 2.5.1.2 alone doesn't fix the issue. Once that extra 37MB is taken up, it's permanent. The only solution is to RUU back to 2.2, run unrevoked, and start over. This restores the lost space.
wildstang83 said:
Ain't seen you around these parts in awhile. The thing about the recoveries is since most Roms are now edify (do to gb) we have to use 3.X recoveries.
Generally 3.0.0.7 for Amoled and 3.0.0.8 for SLCD.
Click to expand...
Click to collapse
the 2.x versions flash both amend and edify, 3.x flashes only edify. No need to update for that reason and actually a good reason to stay with 2.x versions for the ability to flash new and old roms that haven't been updated.
Amend is old (abandoned back with cupcake I believe) so koush eliminated the ability to flash amend scripts in 3.x so that it would force devs to get with the times and use edify. Edify is not new, has nothing to do with gingerbread.
I use amon ra recovery and have had no issues, flashes both amend and edify still.
i need a recovery for my dinc the one i installed is not working. i can't do nothing when i enter into ClockworkMod Recovery v3.0.0.8
if i press reboot system now = nothing happen
apply update from sdcard = nothing happen
wipe data/factory reset = nothing happen
wipe cache partition = nothing happen
install zip from sdcard = nothing happen
backup and restore = nothing happen
mounts and storage = nothing happen
advanced = nothing happen
power off = same result nothing happen
can someone please tells me what's going on?
i need help with this now my phone do not work at all.
i use unrevoked 3 flash and root tool "everything was perfect" i installed room manager premium with recovery v3.0.0.8 with alt recovery 2.5.1.2 everything was good. after running the cyanogenmod 7 my phone now stay with the logo of the cyanogenmod 7 and do not enter to the main screen.. PLEASE HELP ME
airjordanmmix said:
i need a recovery for my dinc the one i installed is not working. i can't do nothing when i enter into ClockworkMod Recovery v3.0.0.8
if i press reboot system now = nothing happen
apply update from sdcard = nothing happen
wipe data/factory reset = nothing happen
wipe cache partition = nothing happen
install zip from sdcard = nothing happen
backup and restore = nothing happen
mounts and storage = nothing happen
advanced = nothing happen
power off = same result nothing happen
can someone please tells me what's going on?
i need help with this now my phone do not work at all.
i use unrevoked 3 flash and root tool "everything was perfect" i installed room manager premium with recovery v3.0.0.8 with alt recovery 2.5.1.2 everything was good. after running the cyanogenmod 7 my phone now stay with the logo of the cyanogenmod 7 and do not enter to the main screen.. PLEASE HELP ME
Click to expand...
Click to collapse
Don't use the power button. Use the optical joystick. Common mistake.
Sent from my Droid Incredible running a random CM7 nightly.
EDIT: Just wanted to state that reverting to 2.5.1.2 alone doesn't fix the issue. Once that extra 37MB is taken up, it's permanent. The only solution is to RUU back to 2.2, run unrevoked, and start over. This restores the lost space.
Click to expand...
Click to collapse
Jay, you're saying that once room has been taken up in data partition, it's for good? Even if you wipe? You have to RUU to get it back?
I'm only asking because I keep getting hit with a low space notification on every sense rom I've tried lately and am wondering if this is the cause?
Sent from my HTC Incredible
TheWhiteBandito said:
Jay, you're saying that once room has been taken up in data partition, it's for good? Even if you wipe? You have to RUU to get it back?
I'm only asking because I keep getting hit with a low space notification on every sense rom I've tried lately and am wondering if this is the cause?
Sent from my HTC Incredible
Click to expand...
Click to collapse
I apologize, I should elaborate. What I displayed was the only solution that worked for me. There may be other methods (like that program another poster mentioned). But no, I'm not going to flash something along with every recovery to make sure that everything was wiped properly.
If you want to test, click through to my links below. Install Liberation Enhanced 1.1 (nandroid first). Once you install, skip every part of the Sense startup process, and go straight to settings, then SD and Storage. See how much available phone storage you have left. You should have 677MB. If you have significantly less than that, then you've also been affected by this. If you fall into this, then do the following;
-Run the RUU back to 2.2
-Run unrevoked (this will install 2.5.1.2 as your recovery)
-Re-flash the same ROM, you should now be at 677MB. Problem solved until the next time you use CWM Recovery 3.x.
I don't know where the extra storage is going, but I don't think that it's in the /data/data partition, meaning that it wouldn't affect your low on space notification.
Just out of curiosity, did you format /system when you tried the 3.x recovery? I don't believe that /system is covered by the wipe data/factory reset.
It shouldn't be any different than the 2.x recovery though, going through the same steps should yield the same results. I would consider contacting Koush to see if there's an explanation for what's happening.
k_nivesout said:
Just out of curiosity, did you format /system when you tried the 3.x recovery? I don't believe that /system is covered by the wipe data/factory reset.
It shouldn't be any different than the 2.x recovery though, going through the same steps should yield the same results. I would consider contacting Koush to see if there's an explanation for what's happening.
Click to expand...
Click to collapse
I'll certainly bother him. I tried going into advance and formatting; system, boot, data, and cache. I also tried the "wipe 3 times" myth on all of them. Bottom line is, with 2.5.1.2, if you wipe data, it does so correctly without any further steps. That's the way it should be, so that's the recovery that I will use.
That's definitely odd. Have you figured out where the 37mb of files are that the 3.x recovery doesn't wipe?
k_nivesout said:
That's definitely odd. Have you figured out where the 37mb of files are that the 3.x recovery doesn't wipe?
Click to expand...
Click to collapse
Not yet. I'm curious, but lack the time. I might investigate it further at a later time.
jaykresge said:
I apologize, I should elaborate. What I displayed was the only solution that worked for me. There may be other methods (like that program another poster mentioned). But no, I'm not going to flash something along with every recovery to make sure that everything was wiped properly.
If you want to test, click through to my links below. Install Liberation Enhanced 1.1 (nandroid first). Once you install, skip every part of the Sense startup process, and go straight to settings, then SD and Storage. See how much available phone storage you have left. You should have 677MB. If you have significantly less than that, then you've also been affected by this. If you fall into this, then do the following;
-Run the RUU back to 2.2
-Run unrevoked (this will install 2.5.1.2 as your recovery)
-Re-flash the same ROM, you should now be at 677MB. Problem solved until the next time you use CWM Recovery 3.x.
I don't know where the extra storage is going, but I don't think that it's in the /data/data partition, meaning that it wouldn't affect your low on space notification.
Click to expand...
Click to collapse
Ah I see what you're saying now. I will give that a try when I get the chance! I always keep Liberation on my SD card anyway!
k_nivesout said:
Just out of curiosity, did you format /system when you tried the 3.x recovery? I don't believe that /system is covered by the wipe data/factory reset.
It shouldn't be any different than the 2.x recovery though, going through the same steps should yield the same results. I would consider contacting Koush to see if there's an explanation for what's happening.
Click to expand...
Click to collapse
/system is NOT covered by the wipe data/factory reset option. My only thought behind this is that it's meant to just remove your user data, but keep your ROM aka a factory reset. If you were to factory reset a normal, unrooted inc, you would be left with the stock OTA rom without any user data. I believe that is the same mindset.
I always go to mounts and storage and wipe /system before flashing a new rom
As I understand, formatting /system should be in the updater-script for whatever rom you're flashing, but isn't necessarily always included. Formatting /system should probably be mentioned in the OPs for most roms.
And Jay, I'd be interested if you find out what isn't being wiped on the 3.x recoveries that is on the 2.x.
Hi All, let me start with a warning…
total Android n00b here, doing his first ROM flash on a newly rooted T-Mobile G2. I’ve read and searched a bit in the forum threads to see if I could solve this on my own, but I do need help.
VISION PVT SHIP S-OFF
HBOOT - 0.82.0000 (PC1010000)
MICROP - 0425
RADIO - 26.02.01.15_M2
eMMC - boot
Aug 20 2010, 16:51:01
This is from using the instructions in Strawmetal’s PDF guide to Downgrading from Gingerbread to Froyo and Root. I am working with a G2 phone that was set to Factory Reset before rooting, so there is no user data to backup or worry about.
1. I downloaded the Andromadus Mimicry 1.1.2 ROM image, and verified the md5 checksum on my sdcard using the AFV Legacy application. The Gapps image also was verified as well.
2. Using ROM Manager 5.0.0.8 from the Google Market, I ran Clockwork Recovery to install the Andromadus image. I left all settings on defaults and the installer ran fine.
3. When it restarted, I was left stuck at the white HTC screen for ages… the longest I left it was 20 mins. After that, I pulled the battery and restarted. Same white HTC screen.
4. I tried using Volume (+) key and Power On to get back to Clockwork Recovery, but the phone vibrated (buzzed) 3x times quickly, and the Power LED lamp pulsed an amber color. Again, yank battery, restart, same white HTC screen.
5. finally I decided to read more of the help for adb, and found the command “adb reboot-bootloader”. This let me get into the default Recovery mode, and it proceeded to find the PC10IMG.zip I still had on the sdcard from doing the Froyo downgrade. Recovery checked it out, ran it and restored the stock Froyo image and my phone did a proper restart. WHEW.
After that, I had to run adb to install the hboot recovery image file, and the busybox checksums were valid according to Strawmetal’s PDF instructions to get permanent root back after restoring the stock Froyo image.
I have done this process about 4 times, and am really good at typing inside adb now
But I’m lost…
-did I pick a ROM that doesn’t work with the G2? Other posters to the forum thread appear to be using the HTC Vision or G2.
-is ROM Manager not a good way to install a ROM?
-when I tried to get back into Recovery, what do the 3x buzzes/amber power LED mean?
-I never got to install the Gapps image; was I supposed to install that first, then the ROM image?
I imagine I did something wrong (duh!), but I can’t spot it. If someone can help me through this, I’d appreciate some advice very much.
thanks!
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Hi Nospin,
Thank you very much for your suggestions!
I will revise my root and remove Clockwork, and switch to 4EXT instead.
I appreciate the idea of "superwipe"; I will look for that as well today.
If I understand everything right...
-replace CWM with 4EXT
-place superwipe.zip, Gapps.zip and the Mimicry ROM.zip on the top level of the sdcard first.
-reboot the phone and run 4EXT recovery
-select superwipe to run first, then the ROM and then Gapps
-then restart the phone
When I used CWM before to install the ROM, it rebooted on its own before I could install Gapps. Will 4EXT let me do each install right after each other or do I have to return to 4EXT for each separate install?
regards,
motionmonk
Nospin said:
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Click to expand...
Click to collapse
Hi blk_jack,
I went back to the Mimicry page and re-read the FAQ section.
I think what I got out of it the first time was that if the ROM flash failed, it could be a corrupt ROM image. I will definitely use 4EXT to repartition before I try again with a ROM flash.
I guess I am still getting used to the terms for everything; can 4EXT do the nandroid backup? or is there a better process for setting that up?
thank you!
motionmonk
blk_jack said:
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Yes, you should be able to flash the rom and then GApps without rebooting. Give me a few and I will send you a PM with a few links....
Shot you a PM.
Thanks! I'll check it out :good:
Nospin said:
Shot you a PM.
Click to expand...
Click to collapse
Update-not working
Ok...
I re-flashed back to stock Froyo, and did a permanent root.
Installed 4ext Recovery (instead of Clockwork), and got a copy of SuperwipeG2+ext4;
I copied new checksum'd copies of Mimicry 1.1.2 ROM and GApps to my sdcard.
Booted into 4ext Recovery and installed from .zip the SuperwipeG2+ext4 file.
System, data and cache are all converted to ext4 partitions.
Wiped the system and data and cache partitions.
Installed from inside Recovery the Mimicry ROM and then the GApps archives.
No errors reported.
Upon reboot, I still get the white HTC screen. UGH.
I've left it on in that state for 30 mins... I had to yank the battery after that in shame...
I have tried to make sure that I read up on background steps, and I feel I do understand the overall process, but something is still getting in the way. I am doing this as I mentioned in an earlier post on a factory reset G2 with a clean erased SD card (has the stock Froyo image, Andromadus Mimicry ROM and GApps only). There is no SIM card installed either, wifi is off (to avoid OTA upgrade requests).
Are there other things I can try, or info I can supply that would help? I think I'm so close to getting this done... I must be overlooking something obvious.
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Hi amogil,
Just to be sure I understand, are you saying you are swapping between Andromadus and CM9 beta on your phone?
Did you flash CM9 first? and then Andromadus?
or just carrying the CM9 beta image and running Andromadus?
Sorry, I'm all sorts of confused here lol
thanks
amogil said:
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
It's definitely a thought, and I believe that's what amogil is telling me too...
Ya, I can try a different ROM and report back.
I guess I should go back to stock Froyo and then start from CM7.2, and if that boots, try Mimicry again?
-from the Andromadus FAQ, it says it if a different ROM is based on ICS9, you shouldn't have to wipe. But with CM7, I'd have to wipe the Dalvik cache, yes?
-since CM7 is obviously not based on ICS9, would being able to launch into that show some details I can't see at present? Just was curious.
Or, do you think it better to go stock Froyo and then the older Mimicry ROM?
Either way, I'll make sure that I use the Superwipe to set things to ext4 first.
thanks guys for the ideas,
motionmonk
Nospin said:
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
Click to expand...
Click to collapse
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
SUCCESS!
Woohoo!
It works!
Since I had an ICS9 ROM already in place and was planning to wipe back to stock anyways, I tried flashing the older Andromadus 1.1.0 ROM.
What a surprise and treat to see the startup animation!
After poking around for an hour inside it, I then tried Recovery to reflash to the newest 1.1.2 ROM.
YAY! It works!
OMG, having a new ROM is like having a new phone-- there are so many improvements to the UI and it's quick and speedy versus GB. Dang, I'm happy now :victory:
Observations:
1. I did notice that inside Recovery, my touchscreen was barely functional when I tried to update from 1.1.0 up to 1.1.2-- I had to use the Volume +/- and the d-pad button to make selections. After the flash, the touchscreen is as responsive as ever.
2. it's got me thinking, that there must be a setting that is expected in the v1.1.2 ROM that the v1.1.0 ROM installed. Or could something else be the issue? I mean absolutely no disrespect to the developers... but on the technical side, I'm just curious what possibilities exist that might lead to this situation.
3. backup question... when I use MyBackup Pro, I know I can make an archive of the apps I've installed, and an archive of the data (documents, music, settings). Is a nandroid backup different from that? when I see the backup/restore options inside of 4ext Recovery, what are those doing that's different from what I get from MyBackup Pro?
thanks for all the help and encouragement. I have a new ROM installed! :good:
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Oooh, a possibility. We will see if he can boot a different rom.
Whenever you switch roms (even if they are using the same Android version as a base) I suggest a full wipe. (Wipe all user data + Dalvik Cache + Cache, or just flash the superwipe zip). When upgrading the rom you are currently on (say upgrading CM Nightlies or going from Mimicry 1.1.1 to 1.1.2) you only need to really wipe cache and dalvik cache. Unless the dev states otherwise of course.
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Thank You All!
A big shout out to:
Nospin
blk_jack
amogil
strawmetal
for taking the time out to help a total n00b stumble through his first ROM flash.
I really appreciate the points you guys made, and the help provided.
Thank you!
I hope that one day I can help someone else out with a problem and pass the kindness forward.
Yay! I have a working ROM!
motionmonk
motionmonk said:
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
Click to expand...
Click to collapse
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
WOW. i just realized there is SO MUCH I need to catch up on!
I'll have to look up some of these guides later today... but the RUU is the ROM upgrade, right?
Did you ever find a reason why you got the false S-OFF flag? It's clear that the way I was looking at the failed fre3vo exploit as proof of S-OFF isn't always going to be true... but how would you separate a false S-OFF flag from lets say a wrong hboot image?
BTW, your PDF on downgrading and rooting the G2 was a godsend. Very very helpful and clear.
One of the reasons why I took so long to try rooting was that I was confused by the different methods and the replies of X not working, Y is a better way... going through your guide and the info here on xda cleared alot of things up. :good:
strawmetal said:
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
Click to expand...
Click to collapse