[Q] Oddities after reverting to stock. - Droid Incredible Q&A, Help & Troubleshooting

So, after a bunch of shenanigans involving Clockworkmod errors and busted wifi, I decided to revert my incredible back to stock from Cyanogenmod by flashing the PB31IMG.zip through hboot. Prior to this, I had tried to flash a fresh install of Cyanogenmod, which didn't fix my problems and produced errors in CWM along the lines of:
Code:
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
A quick search revealed that these errors pretty much rendered CWM useless for flashing, wiping, etc. so I didn't bother trying and just flashed the stock HTC rom.
The phone is working swimmingly so far, but I've noticed some oddities that I thought I should get sorted out before possibly going to another rom.
Booting into hboot reveals that I still have s-off. Shouldn't flashing the stock image give me s-on?
Booting into revocery gives me an image of a phone with a red triangle/exclamation mark. What does this mean?
Before I found these issues I was planning to run unrevoked to flash CWM and root again, but now I'm hesitant. Any help would be excellent.
PS. Here is a thread detailing the CWM issues I had prior to this, if that helps anyone.

Sounds like the stock Android recovery. You'll need to get a recovery from Doug Piston.com that you can flash the same way you just flashed the stock Inc image.
Sent from my ADR6300 using xda premium

So I could flash CWM through hboot without a problem? That sounds great, but I still have the s-off issue. I found that I have s-off, but I don't have root access. As far as I can tell, I think need to rerun unrevoked, is that right? Can I run it safely even though I already have s-off? It looks as though unrevoked forever has an s-on tool that I can flash through recovery-should I do that before running unrevoked?
UPDATE: I got a little impatient and took matters into my own hands. I managed to get Cyanogen up and running, and I'll list what I did for anyone with similar concerns. Thank you for the advice, RMarkwald.
1. Flashed CWM 3.0.0.8 through hboot (because 5.0.2.0 is what got me into this whole mess...)
2. Flashed Superuser through recovery (apparently s-off and root access are two different things. I had to flash superuser to gain root access.)
3. Rebooted into recovery, did a factory reset, wiped cache and dalvik cache.
4. Flashed Cyanogenmod, google apps, incredikernel, and superuser through recovery.

Related

Help needed flashing custom rom

OK, so first of all I apologize if this is a total noob question, becuase the EVO is the first phone I've rooted and I'm not too familiar with all of this yet. Anyhow, here goes: my Evo's rooted (Using Zikronix's methodas I've go a brand new EVO with Hboot2.02. I've confirmed that I'm rooted by checking for the # symbol in adb shell, and I've got Hboot 2.02 s-off. And I can get into either clockwork or amon Ra recoveries. The problem is, when I go into recovery and select a rom to flash from my SD card, I get the error message:
E:Can't open /sdcard/fresh-evo-3.4.0.1.zip
(bad)
Installation aborted
I just tried it now with the Fresh Rom, but it happens with Ava, baked snacks, and one other that I can't recall at the moment. Basically with anything I try to flash from recovery, and it occurs with both recoveries.
Any thoughts / suggestions?
Just a thought, but maybe the roms arent configured for the new hboot. Idk if it even makes a difference or not.

[Q] Locked out of my G2

Alright, so last night I saw that the CM nightly build had been working for others so I decided to try it. I wiped and flashed but got a boot loop. I went back to recovery to try to wipe and reflash but the flash failed halfway through. I go to hboot and see that I'm back to S-ON... So now I'm stuck with a phone that won't boot, won't let me flash a rom in recovery, and won't even let me install the stock rom with hboot. I spent about 4 hours on it last night messing around with fastboot and trying apache14's OTA rollback method but was never able to get it to work. The adb shell won't recognize that I have the edited misc.img on my sd, even with a newly formatted card with no other data. Before anyone states the obvious, I was using the first version of the G2 clockwork mod, and if there was an option for a backup in there, I didn't see it anywhere. Any help is appreciated. Thanks in advance.
man i've been trying to help someone in a similar spot for 2 days now. so do u still have a custom recovery on there now?
so hboot recognizes the stock rom? what exactly happens when you try to flash it?
Yeah I managed to get a newer clockwork on here. Turns out a friend of mine just bought a G2 so I'm going to attempt to make a nandroid backup of his and apply it to mine. Think that will work?
It recognizes it, but just says "Main version is older! Update fail!" after it scans the image. I assume that's because I had the ota applied before I flashed the cm rom.
thenpaxtongoes said:
Yeah I managed to get a newer clockwork on here. Turns out a friend of mine just bought a G2 so I'm going to attempt to make a nandroid backup of his and apply it to mine. Think that will work?
It recognizes it, but just says "Main version is older! Update fail!" after it scans the image. I assume that's because I had the ota applied before I flashed the cm rom.
Click to expand...
Click to collapse
you should be able to just flash a rom in recovery. do full wipe then apply one of these roms:
mine: http://forum.xda-developers.com/showthread.php?t=836042
pauls: http://forum.xda-developers.com/showthread.php?t=836784
btw-your alot better off then the guy im trying to help
Alright, I'm downloading it. I don't see why this would work when the desire rom and CM roms didn't but it's definitely worth a try. Thank you for the help. I'll post my results in a minute.
Edit: Nope
It starts to install and then:
Finding update package...
Opening update package...
Installing update...
Formatting SYSTEM:...
E:
"system" wipe failed!
E: can't format system:
E: Failure at line 6
format System:
installation aborted
thenpaxtongoes said:
Alright, I'm downloading it. I don't see why this would work when the desire rom and CM roms didn't but it's definitely worth a try. Thank you for the help. I'll post my results in a minute.
Edit: Nope
It starts to install and then:
Finding update package...
Opening update package...
Installing update...
Formatting SYSTEM:...
E:
"system" wipe failed!
E: can't format system:
E: Failure at line 6
format System:
installation aborted
Click to expand...
Click to collapse
hmm thats a little more info then u gave last time. which rom did u try?
Your odex rom. And I actually tried Paul's rom last night with the same results. I have to go to work right now so there's not much else I can do but I appreciate the help. I'm really banking on the nandroid restore of my friend's g2 backup working but we'll see what happens.
I had this happen to me also. Since you have clockwork recovery installed, you should be able to use the instructions in this post using adb while in recovery mode:
forum.xda-developers.com/showthread.php?t=831398
The only change you'll have to make is you need to mount the sdcard in order to follow the instructions.
mount -o rw -t vfat /dev/block/mmcblk1p1 /sdcard
/cache also has available space so you might be able to use that without mounting /sdcard.
Hope this helps!
remember that in his first post he said that the phone has reverted to s-on. you've tried the original unrooted stock ROM? because with s-on I don't think you'll be able to flash any of pre-rooted ROM.
Mine had clockwork installed when I tried to install the signed ship rom in order to revert back to stock so I was s-on also. It appears that mmcblk0p17 was not WP in clockwork recover in my case, so I was able to dd the modified image to that partition through adb and then the shipped rom was able to flash normally.
Thank you again for all your help guys, but the nandroid backup worked. Though I am stuck on baconbits and my wifi card is not working at the moment all I need to do is follow the unroot instructions and i'll be fine. I hope...
Sent from my T-Mobile G2 using XDA App

[Q] Won't boot after changing ROMS.

I was running Gingervillain 1.4 but wanted to try CM 6.1.1 with a theme I saw on a different forum. I used CW to flash to the CM rom and did nandroid backup and wipe before installing.
While installing the CM rom, it got to the end and gave me this:
e:can't open /cache/recovery/log
e:can't open /cache/recovery/log
e:can't open /cache/recovery/last_log
e:can't open /cache/recovery/last_log
I had a good recovery of my stock rom and tried to flash that, but it gave me the same error. If I tell CW to reboot system, it hangs on the HTC screen. I am able to get into hboot/recovery via Vol Down/Power and have tried wipe cache, wipe devlik cache, and even the wipe/factory reset and then it went past the HTC screen to the Tmobile G2 screen, but boot-looped on that screen.
After Vol Down/Power, this is my info:
Vision PVT ENG S-OFF
HBOOT-0.76.2000 (PC1010000)
MICROP-0425
RADIO-26.03.02.26.M
eMMC-boot
Aug 20 2010, 16:51:01
I read a few threads, and this one stuck out:
http://forum.xda-developers.com/showthread.php?t=842495
However, the links are now dead
I haven't used ADB, but I have it downloaded and installed since I figured I would need it.
What version of recovery are you using?? Also have you tried flashing latest cm7?? And get same errors
Im am using the latest CW mod. Like 3.0.5 or something. I havent tried CM7. Should I?
Yes try cm7 a try and see if you get same error
The latest recoveries 3..... are for 2.3 roms only. To go back to 2.2 you need one of the older ones again, the 2.9.... recoveries.
Sent from my HTC Vision using XDA App
wileykat said:
The latest recoveries 3..... are for 2.3 roms only. To go back to 2.2 you need one of the older ones again, the 2.9.... recoveries.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Yea what he said...I just wasn't sure what vz your other rom is/was.. but 2.2 roms need recoveris 2.XX and any rom that is 2.3+ need recovery 3.xx
Ok, i downloaded CM7 and gapps and am going to try those. I wonder why I was able to go back to my stock rom before...maybe just got lucky I guess.
i will post back in a few minutes and say whether it worked or not.
Ok, I downloaded CM7 and gapps to my computer, and turned the phone on to get into recovery. enable USB storage and transferred CM7's zip and gapps zip to my sd card. So far so good, CM7 is up and running... So if I ever want to go back to a Froyo rom, I just need to have a CW that is 2.xx, correct?
Indeed my friend, that is correct.
Sent from my HTC Vision using XDA App
wait what? the new recovery should let you flash 2.2 and 2.3 correct?

[Q] lost...after attempted rooting, stuck

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.

Status 7, installation aborted

Hello, I have successfully rooted my HTC Desire running android 2.2 with HBOOT V 0.93.0001 using the Unrevoked method. I Installed ROM Manager and installed ClockWorkMod V 2.5.0.7. I also made a backup.
The purpose was to install a custom ROM, in order to get rid of the Orange bloatware that is on the phone, as well as trying something new.
However whenever I try to instal any ROMS I get an error (Status 7 - installation aborted.)
I then updated the Radio to radio 5.10.05.30 and tried again, same error.
I've tried Cyanogenmod 7, as well as the Oxygen ROM and both aren't working.
I have spent most of today trying to get it to work, and googled alot however I just can't fix this error
Thanks.
you have to do a full wipe data and cache then go to advanced and erase dalvik cache. After all the above you can now install new rom. And if your trying to install new gingerbread you must s off your phone and then update the recovery to the latest one. which i believe is 3.2.0.2 i dunno something like that
When I do a factory reset it just says E: Can't find MISC
No app2sd partition found.
E:cant mount cache:recovery/log
etc etc
says the same thing with wiping the cache, although it does say "cache wipe complete"
when I select wipe Dalvik cache the screen just flickers and appears to do nothing...
What do you mean about updating the recovery, you mean the HBOOT?
Why can nobody answer this? I've literally been reading stuff ALL DAY just to fix this error, yet still can't solve the problem.
Didn't think installing a ROM could be so hard....
I get it you need to back everything up onto your pc from your sd card then go to market on your phone download rom manager and partition your sd with 512mb ext and 0mb swap. and then install any rom u like
Thanks for your help but that didn't work. Not sure what to do.
Which hardwarerevision does your desire have (boot into hboot and read the first line, number behind the word pvt)?
"bravo pvt4 shop s-on"
Just did a hard factory reset, installed ROM Manager and tried again, still didn't work
Also just tried to get my backup restored in the meantime (so I have contacts) oh no, "This does not seem to be a valid backup. The MD5 file is missing"
Can anything else possibly go wrong?
So your hardwarerevision is pvt4. You cannot use clockworkmod recovery and still less rom manager with this one. Download amonra recovery, integrate it in unrevoked (file>custom recovery>choose downloaded amonra recovery) and run unrevoked (like last time) again.
No warranty for any damage.
And a real good advice: Never use rom manager, it's a horrible software which mostly causes heavy and horrible problems!!! Run all operations directly in recovery instead.
Trying that now
MatDrOiD said:
So your hardwarerevision is pvt4. You cannot use clockworkmod recovery and still less rom manager with this one. Download amonra recovery, integrate it in unrevoked (file>custom recovery>choose downloaded amonra recovery) and run unrevoked (like last time) again.
No warranty for any damage.
And a real good advice: Never use rom manager, it's a horrible software which mostly causes heavy and horrible problems!!! Run all operations directly in recovery instead.
Click to expand...
Click to collapse
Are there known issues with revision pvt 4 and ROM manager/ClockWorkMod?
Did just what you said and it's working perfect, I performed a Nandroid backup so I can always go back to the stock ROM, I also unchecked unrevoked forever so the warrenty should be okay IF I go back?
Thanks so much!!!!
rmayling said:
Are there known issues with revision pvt 4 and ROM manager/ClockWorkMod?
Did just what you said and it's working perfect, I performed a Nandroid backup so I can always go back to the stock ROM, I also unchecked unrevoked forever so the warrenty should be okay IF I go back?
Thanks so much!!!!
Click to expand...
Click to collapse
Yes, there are known issues, especially the one you had, which is imho the most important and worst one, because you cannot flash anything.
This disclaimer was referred to me. But yeah, warranty of your provider should be okay if going back to stock.
No problem, happy I could help. Congratulations to you.
Swyped from my HTC Desire using XDA App
Hi there. This might be a bit late but I think I finally find out hot to solve it. It is all because you haven't S-Off your mobile.
so m not goin to get a solution over this,.,.

Categories

Resources