Database Develop

Stuck on g1 logo

I followed the unlockr guide and did everything and now I am stuck on the g1 screen. I checked my radio and spl are the right number. I wiped everything then re-partitioned then re-updated it with the lastest rom and still stuck. Can anyone give me advice?

If you can get into recovery of bootloader than you aren't bricked.

I know it isn't bricked but it is still temporarily useless. I really want a custom ROM and I wish I knew why this thing was messing up.

You could always reflash using the .nbh file then go through the steps again =]

start from step 1 again

The only thing I could think of is when I updated the .spl I didn't wipe. Whenever I booted into the recovery (before using amon ra's, just the stock recovery) I didn't wipe the system before updating .spl. Whenever I wiped and tried to update .spl it would give me an error (I think the E:signature (5 files)). Anyways I will retry! Thanks for your help!

[Q] Moto Droid won't instal OTA updates via recovery?

Okay, where do I begin? The PSfreedom was released for droid and a friend said I can use one of her old droids which was 2.1update1. So in my haste to flash this thing I used EasyRoot, got it rooted (of course made a nandroid backup at least), installed cyanogen 6 (made a backup of this using clockwork recovery), installed the wrong kernel, then was stuck at a loop screen. Well I kept trying and trying to boot it to Clockworkmod Recovery and nothing was working until about the time I gave up and set it down...and WHAM! Clockworkmod Reovery! So I went to nandroid, restore and clicked on my clockwork cyanogen backup. And thus I was stuck on an endless loop of the Droid eye and the Droid logo. I assumed something went wrong and tried booting into clockwork recovery to no avail. Then it finally let me into the normal recovery and I decided I should find a way to start from scratch. Now I wiped EVERYTHING and still I have the endless loop, PLUS it wont let me update to another official firmware via update.zip.
This is the error it gives me:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/Phone.odex", "e619ca7905cd905cd9eeb429c96601b728667b30b94b7", "5d22b967c190356983966fa1f7901aeebdffaaaf")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Can anyone help me figure out what the bejeezus is wrong?

i would suggest u check to see if there is an option to "allow install of update.zip" and click on it before you do the update. i know sprecovery has it
if all else fails, flash the 2.1 sbf file and start over, its really easy

Can't flash Nexus

My nexus has been a great platform for running roms for quite a while now, but after installing CM6 as of late it has been really picky about what it can flash. For instance the only way I got it to install the normal stock rom afterwards was by putting it in as passimg.zip. Every time I try to flash something to it now, the signature verification fails. Anyone else have this problem?
Edit: If I install a rooted room, it gives me
"assert failed: !less_than_int(1277930906, getprop("ro.build.date.utc"))
E: Error in /sdcard/update blah blah .zip
(Status 7) Installation Aborted

Did you lose root?

I don't think so, I could try unlocking the boot loader again but it says unlocked at the top already...and it won't even flash normal signed passion roms...

what recovery do you have? have yopu tried fastboot flash recovery? like amon rah

I ended up using
http://forum.xda-developers.com/showthread.php?t=614850
to fix it.
It still refuses any update.zip file that isnt OTA...
every signature varification fails instantly. So I guess until I throw this phone in the trash pile or just use it for an MP3 player..its not going to be doing anything in the way of modding

If you've used the original shipping ROM tutorial/passimg, then you'll have a stock recovery that will of course only install released signed things.

Rusty! said:
If you've used the original shipping ROM tutorial/passimg, then you'll have a stock recovery that will of course only install released signed things.
Click to expand...
Click to collapse
right and I flashed clockworks recovery to get it off the standard. I guess I could go out and get Root again without it, but at this point I don't see the point with Gingerbread coming out. I'm just glad to not have a paper weight sitting next to my computer again.
btw Calling Tmo/HTC doesn't help. Most of the guys there don't have a clue what FRG83 is even lol

Keep in mind, if you have the stock on there, it will wipe out your custom recovery and restore it to the stock recovery every time you restart the phone.
So if you flashed Clockwork, after a reboot the stock recovery will be there again.

Yes amonra and cwr have options to toggle off verification best to start with amonra recovery then go through the steps

[Q] Flash error driving me crazy

OK, I guess I just have no idea what is going on. I'm running CM6.1.
About a week ago, my phone quit receiving text messages. From what I can tell, I just need to update the profile and PRL. I don't see that as an option on CM6.1. So, I try to flash over to a sense based rom.
Every rom I try gives an installation error:
Code:
Copying files...
E:Can't symlink /system/xbin/zcip
E:Failure at line 62:
symlink busybox SYSTEM:xbin/zcip
Installation aborted.
Upon more investigation, I found that a fix was to replace the SPL. I did that with Darch's ENG-SPL.
Still no worky. I can reload CM6, but that's all. Any ideas are much appreciated.

what exactly are you trying to do? flash a sense rom?
where do you get this error message? what recovery do you have?

I have the GodSpeed Recovery/Darchstar Edition. I have been running CM6.1. I am trying to flash any sense-based rom, so I can get in and update my profile and PRL. After I wipe everything, I flash the sense rom (tried 3 different roms).
As the rom is flashing, that error occurs and the rom fails to install.
Again from reading the forums, that error appears to mean that I needed a new SPL. I loaded Darch's ENG-SPL and flashed it. This did not fix the problem.
I noticed that after flashing the SPL, it calls for a reboot. When rebooted, it goes into a soft boot loop restarting at when the HTC logo appears. I can boot to recovery and then at the bottom is says:
Formatting CACHE:...
It stays that way and does not finish. This might be a problem, yet I don't know how to fix it.
So, at this point, I have access to Recovery and that is all.

Had that prob to try to reflash your recovery. If that does not work you might have to ruu and reroot. Ran into that error day before yesterday when trying to update prl/profile. Its a fastboot zip in the dev section. Hope it helps good luck.
Yea it's me Again. With the
Modified .HERO.

Are you running firerat mod?

[i9001] The phone will just load up (FeaCore Phoenix) CWM Recovery.how to get out?

Hi everybody.
In the past I already flashed custom ROM to routers, so I thought I had the skill to undergo the path of flashing ROM to a phone.
Wrong.
I have countless tabs opened tried to solve my stucked phone, and my PC is running out of memory; and I'm running out of hope.
I own a S Plus GT-i9001.
I wanted to get rid of all the bloatware present in the phone, so I gained root privileges.
Like explained here. It worked perfectly.
Since deleting all the unnecessary apps didn't look working, I thought "well, it is a rainy day, you had this device for a while, why don't you flash some ROM?"
So,
1. I followed this guide, but, needless to say, Rom Manager was not fulfilling to its duty. Indeed I backuped everything I needed, but the stock rom
2. I followed then this guide, point 3, to install ClockworkMod Recovery directly. Before, everytime I tried to enter the recovery menu, I was bounced to the original recovery menu, because ROM manager did not succeed.
With this guide, I managed to boot into ClockworkMod Recovery.
I then started backing up the ROM to the external SD, and it seemed working.
It was popping out with a message "E:Can't mount /cache/recovery/command", but since all the operations went successful, I did not care much (fail, I suppose)
3. I tried to boot back into the phone, before installing the new ROM, just to double check I saved everything, and then the drama began. I was just continuously bounced back at CWM Recovery menu, no way to get in the phone.
I tried anyway to install the AOSP 4.0.4. and all the steps went successful, but still nothing, I would always reboot automatically into CWM Recovery.
4. I tried restore from backup in external SD, it ran successfully, but still couldn't load the phone
5. I then googled into the "E:Can't mount /cache/recovery/command" error, so I ended up somewhere that they were advising to flash FeaCore Phoenix Recovery tool. Indeed it did not display anymore such an error
6. I tried again with he AOSP 4.0.4 ROM, but it showed then the following error
Code:
assert failed: getprop("ro.product.device") == "thunderc" || getprop("ro.build.product") == "thunderc"
so I ended up here and changed the zip accordingly.
7. I also tried this instructions here to perform the most ultimate massive wiping.
8. I installed the AOSP 4.0.4, and the update-Gapps-ICS-20712.zip, it worked, no errors.
Still, it reboots into the recovery menu.
I can't get out of this damned recovery menu, it is crazy! I have used so many recovery tools in PCs, you usually are able to leave them, maybe not able to restore the OS, but you never get stuck into a circle of hell like this!
Please, does anyone has some advice for me? I don't want to waste a 6-months old device
thank you!

You should reflash CWM with odin like this then try flashing a rom again.
If that doesn't work flash a stock frimware through Odin also with the AriesVE.ops file active.
All guides tell you to put the "recovery-clockwork-5.5.0.4-ariesve.tar.md5" or the stock firmware file as "one package". Doing that results into large file errors or odin getting stuck on "downloading..."
Putting the file under phone got my phone back to life, after softbricking it by using CWM 6 thouch.

switchboy said:
You should reflash CWM with odin like this then try flashing a rom again.
If that doesn't work flash a stock frimware through Odin also with the AriesVE.ops file active.
All guides tell you to put the "recovery-clockwork-5.5.0.4-ariesve.tar.md5" or the stock firmware file as "one package". Doing that results into large file errors or odin getting stuck on "downloading..."
Putting the file under phone got my phone back to life, after softbricking it by using CWM 6 thouch.
Click to expand...
Click to collapse
man, you saved my life!
you and the powerful, mighty Odin, god of the Valhalla!
oh, it feels so awesome!
but since I never learn (that was enough of a message to tell me to stop messing around)...
how do I install the ROM I'd like, go through the same process (my phone is now as as when I bought it) or can I use somehow Odin?

jv_guano said:
man, you saved my life!
you and the powerful, mighty Odin, god of the Valhalla!
oh, it feels so awesome!
but since I never learn (that was enough of a message to tell me to stop messing around)...
how do I install the ROM I'd like, go through the same process (my phone is now as as when I bought it) or can I use somehow Odin?
Click to expand...
Click to collapse
I realised that, since I flashed the recovery-clockwork-5.5.0.4-ariesve.tar you provided, if I would boot in recovery mode, it would be still there.
and it is.
but still it is showing the error
E:Can't mount /cache/recovery/command and, needless to say, it is not loading the ROM correctly, it stucked again
I don't get which part am I doing wrong!

jv_guano said:
I realised that, since I flashed the recovery-clockwork-5.5.0.4-ariesve.tar you provided, if I would boot in recovery mode, it would be still there.
and it is.
but still it is showing the error
E:Can't mount /cache/recovery/command and, needless to say, it is not loading the ROM correctly, it stucked again
I don't get which part am I doing wrong!
Click to expand...
Click to collapse
Well, I sorted it out (absolutely, in a mysterious way!!! )
I downloaded the recovery-clockwork-6.0.1.2-ancora.tar.md5 from here, and I followed again your instructions for flashing it with Odino (rigorously NOT ticking one package).
When rebooted, I had the AOSP 4.0.4 Stock, shiny and sparkling!
without even entering the recovery menu and reinstalling!
but I guess I will need to do a clean install again, now that seems that CWM 6 is digested by my phone