Database Info

Error Manual Installing RC29 (No Signature)?

I was trying to manually install RC29 and for some reason when it goes to install it says that there are "No Signature" and that it cant update. Anyone have a way to fix this or had this issue?
Even when I tried to manually update to that it gave me the same No Signature error and wouldnt update it. Basically I cant get passed the Google log in because something must have happened to the phone because when I restored my phone and went to set it up with my new gmail account it wont get passed that screen and wont connect to the servers. So basically I wanted to update it again with a full install of RC29 in hopes of it fixing the problem.

ballaholyk84 said:
I was trying to manually install RC29 and for some reason when it goes to install it says that there are "No Signature" and that it cant update. Anyone have a way to fix this or had this issue?
Even when I tried to manually update to that it gave me the same No Signature error and wouldnt update it. Basically I cant get passed the Google log in because something must have happened to the phone because when I restored my phone and went to set it up with my new gmail account it wont get passed that screen and wont connect to the servers. So basically I wanted to update it again with a full install of RC29 in hopes of it fixing the problem.
Click to expand...
Click to collapse
Have you edited anything on the phone? Have you touched the OTAcerts.zip file?

neoobs said:
Have you edited anything on the phone? Have you touched the OTAcerts.zip file?
Click to expand...
Click to collapse
Yes I did. I did the mod hack that JesusFreke posted and looking to add them back or reverse the process.

ballaholyk84 said:
Yes I did. I did the mod hack that JesusFreke posted and looking to add them back or reverse the process.
Click to expand...
Click to collapse
That is why you get the no signature file error. OTAcerts.zip is the signature file.

neoobs said:
That is why you get the no signature file error. OTAcerts.zip is the signature file.
Click to expand...
Click to collapse
So is there a way that I can get those back on the phone?

ballaholyk84 said:
Yes I did. I did the mod hack that JesusFreke posted and looking to add them back or reverse the process.
Click to expand...
Click to collapse
to reverse look in that AndroidMod.zip JesusFreke posted look for update - Restore Orginial RC29 Boot Image.zip. hope i helped
"Finally, the "update - Restore Original RC29 Boot Image.zip" file is an update.zip file signed with the test keys, which will restore your boot partition back to the stock RC29 image. Useful if you accidentally hose your boot partition.."-JesusFreke

humble said:
to reverse look in that AndroidMod.zip JesusFreke posted look for update - Restore Orginial RC29 Boot Image.zip. hope i helped
"Finally, the "update - Restore Original RC29 Boot Image.zip" file is an update.zip file signed with the test keys, which will restore your boot partition back to the stock RC29 image. Useful if you accidentally hose your boot partition.."-JesusFreke
Click to expand...
Click to collapse
I see that but How do I apply it since I cant get into the phone?

ballaholyk84 said:
I see that but How do I apply it since I cant get into the phone?
Click to expand...
Click to collapse
try naming it update.zip and updating it from the sdcard.

neoobs said:
try naming it update.zip and updating it from the sdcard.
Click to expand...
Click to collapse
Got that to work thanks! Now if only I can transfer this damn RC29 to my card without some part being corrupt. I Have tried about 5 times with something being corrupt

Help i need to restore the recovery.img for the G1 RC29
I mest up my G1 it no longer could take my RC33 update, i get an error
E:Failure at line 5 assert getprop("ro.build.fingerprint")== "tmobile/kila/dream/trout:1.0/TC4-RC30/116143:users/ota-rel-keys,release-keys" l l getprop("robuild.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC29/115247:user/ota-rel-keys.release-keysInsta
i was going to do the multitouch on my G1 but when i started to follow this link
http://hehe2.net/gadgets/howto-multitouch-tethering-task-manager-for-android-g1/
i got stuck on the telnet command for the
rm -f /system/recovery.img
it would not accept it, andy my Dumass decided to skip that step and enter the
flash_image recovery /sdcard/recovery_testkeys.img
since i knew that i had the recovery_testkeys.img in my sdcard
(to be honest, i dont know squad about telnet with the G1, i am familiar with the linux terminal but its not the same)
so i stop there because i started to get nervous about my G1 getting **** up, i figure that i would just do a factory reset and wala ill be back in business but nah, after the factory rest i obiously was going to be in the RC29, so i tried doing the manual update to the RC33 but now it will not take it, i keep on getting the message that is in the beginning of this post, i know the update file i am using is not corrupt or incorrect, i had my girls G1 that i just purchase for her and i decided to test out the update in hers, since its still on the RC30, and it work fine.
Please Someone help, i know i should had tough my firmware.....

lost internal memory after flash

ok so i was on rc33, flashed to the appstosd rc33, ran the appstosd program and it erased my apps and then i reset my g1 and it was stuck in a boot loop, so i then flashed to haykuro latest appstosd H rom, and ran the appstosd program again, same thing happened. so i flashed again, but now my internal memory is at 48mb, i have not installed anything yet. any ideas?

no /system
Both haykuro build versions G & H take up space in /system . The H version takes more because it has more apps and things to install, so everybody's has lower mem, but thats the whole point of apps-to-sd is so you dont have to worry about low internal memory

ahh ok thanks, i dont know if i should make a new topic for this, but everytime i run the appstosd program it erases my apps and then i reset my g1 and it gets sent into a bootloop and i have to reflash, i have partitioned my card and have the appstosd rom, am i doing something wrong?

Can any one help with apps 2 sd. Every time i try to do adb remount on my desktop command prompt I get "error: device not found" What to do?

Nikeem24 said:
Can any one help with apps 2 sd. Every time i try to do adb remount on my desktop command prompt I get "error: device not found" What to do?
Click to expand...
Click to collapse
lol... join the club... I can't do it either, no one is really looking into this either cause it is only affecting a few users for some reason.

SolemnWishing said:
lol... join the club... I can't do it either, no one is really looking into this either cause it is only affecting a few users for some reason.
Click to expand...
Click to collapse
its probably a user error forsure..
I can help out with adb to those who use Mac

jak33 said:
ahh ok thanks, i dont know if i should make a new topic for this, but everytime i run the appstosd program it erases my apps and then i reset my g1 and it gets sent into a bootloop and i have to reflash, i have partitioned my card and have the appstosd rom, am i doing something wrong?
Click to expand...
Click to collapse
can anyone tell me what im doing wrong, i tried like 4 times and keep get stuck in in boot loop when i reset. is there a step im missing or something?

jak33 said:
can anyone tell me what im doing wrong, i tried like 4 times and keep get stuck in in boot loop when i reset. is there a step im missing or something?
Click to expand...
Click to collapse
do you mind posting the steps you did jak? it would help us determine during what part of the process u made an error.

andonnguyen said:
do you mind posting the steps you did jak? it would help us determine during what part of the process u made an error.
Click to expand...
Click to collapse
ok so,i installed the haykuro appstosd rom, i had some trouble partitioning my card, i always got errors in ubuntu live cd but after like 4 tries it mysteriously worked i think. then i downloaded the appstosd program and ran the program, when i did, it didnt look like it did anything, it just went back to the app and the when i went back home, all my apps were gone so i reset my g1 and was sent into a boot loop, this happened 4 times, and i also tryed the rc33apptosd rom also and the same thing happened

psfMod - project abondoned

After waking this morning and seeing the length's SCEA are going to to halt the PS3's jailbreak I am reluctantly withdrawing from the distribution of PSFreedom in any form.
You can see more of what SCEA are doing here: http://psx-scene.com/forums/showpost.php?p=535680&postcount=1
Keeping my Family intact is more important to be than hacking a games console.
Klutsh

nice work dude

GREAAT !!!

hats of chap great work going to install this later thanks

thanks Klutsh, your awesome
time for me to start tinkering with dev_flash... hehe
"An error occured while loading PSFreedom./tmp/recovery.log was copied to /sdcard/psf/recovery.log.
Please report the issue on XDA"
gonna get the log file for you now
edit: herp derp, my phone refuses to boot
great stuff...

Thanks for all your hard work, guys! Fantastic stuff!
Do you think we'll ever see this as a "fake flash"?

Great work!! Let's try!
" including ABD and Mass storage toggle." Simply awsome

Excuse my lack of knowledge, but what exactly is the difference or advantage to the PSFreedom App you created?
Keep up the awesome work!

yeah.. after rebooting to try and get you that log, my phone seems to be stuck in a HTC logo -> off -> reboot -> HTC logo -> off loop, any suggestions? I can go back into recovery/hboot fine... but not my phone

@stoker25, This should not effect your normal rom in any way.
mrmeotz said:
Excuse my lack of knowledge, but what exactly is the difference or advantage to the PSFreedom App you created?
Keep up the awesome work!
Click to expand...
Click to collapse
It's ROM independent, so sense users can use it too

Klutsh said:
@stoker25, This should not effect your normal rom in any way.
It's ROM independent, so sense users can use it too
Click to expand...
Click to collapse
how come I can't boot back into my rom then? now i've got to reflash, great...

stoker25 said:
how come I can't boot back into my rom then? now i've got to reflash, great...
Click to expand...
Click to collapse
try taking your SD card out.
But honestly this does not touch your /system, /data or /boot partitions at all

Really? That is ****ing sweet!
So you're saying that i could jailbreak my PS3, even though im running i.e. FroYo 2.2 ? Sounds swell..although i grew pretty fond of Open Desire..
Big thx @ klutsh

Klutsh said:
try taking your SD card out.
But honestly this does not touch your /system, /data or /boot partitions at all
Click to expand...
Click to collapse
still doesn't fix it :/
heres the recovery log:
http://stoker25.com/files/recovery.log

stoker25 said:
still doesn't fix it :/
heres the recovery log:
http://stoker25.com/files/recovery.log
Click to expand...
Click to collapse
Typical recovery log shows that everything worked, although it still flagged an error.
The log is the ONLY file that my code additions write anywhere on the device other then the recovery img flashing.
I am honestly at a loss to what can cause your main rom to fail booting.
What rom do you normally run?

Klutsh said:
Typical recovery log shows that everything worked, although it still flagged an error.
The log is the ONLY file that my code additions write anywhere on the device other then the recovery img flashing.
I am honestly at a loss to what can cause your main rom to fail booting.
What rom do you normally run?
Click to expand...
Click to collapse
i was using ieftm's rooted 2.2 rom (the first one he made, it's probably outdated now), i'm thinking it might have something to do with the symlinked bootanimation, since it reboots before it shows it. gonna reflash now anyway, since i've been meaning to for a while...

can anyone upload unrEVOked for desire???
and can i use HTC sense rom?

So let me get this right, now we can have this with any rom and keep all usb usage (I'm using leedroid 2.1) within our roms? Just adds an extra menu in recovery?

TheIntruder said:
So let me get this right, now we can have this with any rom and keep all usb usage (I'm using leedroid 2.1) within our roms? Just adds an extra menu in recovery?
Click to expand...
Click to collapse
Yes
10char

Fantastic work! Another question I have never used unrevoked, rooted it another way can i do it via clockwork recovery or rom manager?
Sent via smoke signals

[TOOL][ACS]One Click Odexer and Restoration Tool for Samsung Epic 4G

ACS Presents:​One Click Odexer and Restoration Tool​version 1.0 - by tanimn
*** PLEASE NANDROID BACKUP ***​
DETAILS:
OneClickOdexer is an odexing and restoration tool for deodexed roms. It will determine if it has been previously run and automatically odex your rom or restore it to a deodexed state. If a critical error occurs, it will return your phone to it's previous state. Care has been taken to only odex apps that come stock with an odex file.
With one click, it odexes.
With one click, it restores.
Complete details are available in the included README.TXT, including instructions for manual operation and running from the handset instead of through adb.
By changing from a deodexed to an odexed system you are modifying the method in which your dalvik virtual machine works. PLEASE backup your phone before using! I will accept no responsibility for your failure to follow this basic safety tenet.
PROS:
Increases speed by about 15%
Reduces memory usage
More space available on /data
Reduced use of dalvik-cache
CONS:
You might need to re-add some widgets and home screen icons after applying
You will need to restore your deodexed system to make any theme swaps (But that's just one click away...)
Exclusively for Samsung Epic 4g. Tested on DK28 and DI18 roms. Contact tanimn for porting instructions.
Thanks to raiderep for the idea, Paul O'Brien for the commands, and ACS for the help and support.
Downloads: (Please report mirrors)
MultiUpload

Sweet idea!
Sent from my Nexus S with a keyboard

Nice, thanks!

Alot of work went into this and its well worth it.
Sent From Da Hood.

hi, i am rooted with cwm 3.0.0.5(ext4).... is this program not compatible with that? it is saying it did not find root.... but i am definitely rooted and running cwm 3. thx

As always amazing work. Thank you the hard work long hours and dedication to your project and getting this out to the users benefit. I know everyone will enjoy the performance boost and ease of file conversion on the fly.... look out for some more great releases from ACS!

Looks really cool. I look forward to reviewing this tool!

yogi2010 said:
hi, i am rooted with cwm 3.0.0.5(ext4).... is this program not compatible with that? it is saying it did not find root.... but i am definitely rooted and running cwm 3. thx
Click to expand...
Click to collapse
When using the one click you neef to have your screen set to always on. Adb ask for su permission. You'll get a su pop up on your phone and you have to hot allow
Sent From Da Hood.

mysteryemotionz said:
When using the one click you neef to have your screen set to always on. Adb ask for su permission. You'll get a su pop up on your phone and you have to hot allow
Sent From Da Hood.
Click to expand...
Click to collapse
thx. got it to run but the phone seems to be not rebooting.... stuck at Samsung screen, then goes off and hangs at Samsung screen, etc etc.

yogi2010 said:
thx. got it to run but the phone seems to be not rebooting.... stuck at Samsung screen, then goes off and hangs at Samsung screen, etc etc.
Click to expand...
Click to collapse
If the script gets interrupted while it is going through the framework, this can happen. THIS is why you have that nandroid backup in cwm, right...?
If the script doesn't cause the phone to reboot on it's own, rerun the script before rebooting by hand, and restore a backup if your handset has stopped responding.

tanimn said:
If the script gets interrupted while it is going through the framework, this can happen. THIS is why you have that nandroid backup in cwm, right...?
If the script doesn't cause the phone to reboot on it's own, rerun the script before rebooting by hand, and restore a backup if your handset has stopped responding.
Click to expand...
Click to collapse
yep, i have the backup. the script did finish and start the reboot itself... the reboot just keeps getting stuck at Samsung screen, then turning off, and getting stuck again and turning off. no biggie, i can always restore, just lettin ya know what happening.

What rom are you running
Sent From Da Hood.

Thanx for doing this for us. It will really come in handy for re-odexing after adding mods and/or theming to a deodexed system.

mysteryemotionz said:
What rom are you running
Sent From Da Hood.
Click to expand...
Click to collapse
been running Viper 4.0.3 ext4.

yogi2010 said:
yep, i have the backup. the script did finish and start the reboot itself... the reboot just keeps getting stuck at Samsung screen, then turning off, and getting stuck again and turning off. no biggie, i can always restore, just lettin ya know what happening.
Click to expand...
Click to collapse
Yeah, what he said...
Thanks. What rom is this happening with? I'd like to be able to reproduce it and find out what's going on...

tanimn said:
Thanks. What rom is this happening with? I'd like to be able to reproduce it and find out what's going on...
Click to expand...
Click to collapse
Look up
Sent From Da Hood.

tanimn said:
Thanks. What rom is this happening with? I'd like to be able to reproduce it and find out what's going on...
Click to expand...
Click to collapse
no prob... it's happening with Viper 4.0.3 ext4. i just odined back to stock tho, and flashed Syndicate 1.0.2, because i wanted to check that out for fun anyway, lol. the only thing is i'm having a problem with my touchscreen now.... the physical buttons work, but the touchscreen mostly doesn't work... just sometimes. touchscreen sometimes does work after a reboot, then goes out, etc/

yogi2010 said:
no prob... it's happening with Viper 4.0.3 ext4. i just odined back to stock tho, and flashed Syndicate 1.0.2, because i wanted to check that out for fun anyway, lol. the only thing is i'm having a problem with my touchscreen now.... the physical buttons work, but the touchscreen mostly doesn't work... just sometimes. touchscreen sometimes does work after a reboot, then goes out, etc/
Click to expand...
Click to collapse
Sounds like it's still settling, TBH. Could you pastebin a logcat?

tanimn said:
Sounds like it's still settling, TBH. Could you pastebin a logcat?
Click to expand...
Click to collapse
sorry, not sure what you mean by pastebin a logcat... i closed all the screens of the program by now.
btw, touchscreen working fine now .

Just installed on Nebula v1.0.6 with EXT4. Seems to be running normally, I'll play with it some more.

[Q] Strange bootloop issues

Kinda new to this so forgive me if i miss something somewhere and if i need to give more information somewhere just let me know.
With that out of the way I'd like to start with the fact that this is my first rooted device. Currently on C-spire (cellular south) if that matters.
A few days ago before the phone was rooted or even unlocked i went to make a phone call and the screen blacked out and a few seconds later went into a reboot loop where it would get to the Motorola Logo for about 6 seconds or so then shut off and try again ad nauseam until the battery died. After letting the battery die and connecting it to the charger it continued the loop so after a quick gogle search I began fiddling with buttons and realized i could boot into fastboot and recovery modes. I decided i might as well root since it couldnt get a whole lot worse and after a quick look around the forums and a trip to motorola to unlock my phone i was able to flash TWRP recovery, after which i accidentaly wiped the os, managed to find any number of replacement roms none of which solved the boot issue. I eventually found the stock Sprint roms which allowed the phone to boot and work for the most part, but it wont send media messages and has trouble picking up 4g service. I am also forced into using the sprint updater among other things which include having sprint plastered everywhere I have tried flashing several custom roms (pacman, paranoidandroid, and cyanogen) all of which get hung up booting just like the phone did before but the sprint stock rom will reload and work just as before. I'm not sure what would be causing this or if there is a way to fix it and i apologize for the wall of text. If any more info is needed let me know and ill provide ot to the best of my knowledge. Thanks in advance :fingers-crossed:

So all ROM's fail to boot?
Are you doing a factory reset in TWRP before you boot?
Are you flashing gapps? Although that shouldn't cause the phone to fail at booting...

Correct. All roms except the stock sprint rom fail to boot.
Now that i have everything backed up on my external sd I've tried factory reset using twrp as well as wiping everything prior to flashing a ROM as well as after but
Before booting. And the many combinations thereof
And yes i am flashing gapps.

You don't get any errors when it flashes?
Did you check the md5sums?
I flash around a lot, and just got another Q - latest ROM's are not a problem here.

arrrghhh said:
You don't get any errors when it flashes?
Did you check the md5sums?
I flash around a lot, and just got another Q - latest ROM's are not a problem here.
Click to expand...
Click to collapse
I haven't gotten any errors while flashing. Not quite sure how to check the the md5 sums though

AMerexican said:
I haven't gotten any errors while flashing. Not quite sure how to check the the md5 sums though
Click to expand...
Click to collapse
Every ROM should include a md5sum with it. If you're on Windoze, use a program like WinMD5 - check the md5sum locally, and compare it to what is on the server. If they match, the download is probably good.

So after checking the pacman rom matched up (it's the most recent one I've tried), the cyanogen didnt
but i recently redownloaded it and its better now (haven't tried flashing yet), and I can't seem to find the MD5sum for
the paranoid android rom on here.
Anything else i should try?

AMerexican said:
So after checking the pacman rom matched up (it's the most recent one I've tried), the cyanogen didnt
but i recently redownloaded it and its better now (haven't tried flashing yet), and I can't seem to find the MD5sum for
the paranoid android rom on here.
Anything else i should try?
Click to expand...
Click to collapse
The PA build I think is "blind", I don't know if anyone has tried it - additionally, the individual who built it does not own this device... So it's double blind? Haha
The CyanogenMod ROM's, however, are official and work great - many others have confirmed this.
If you had a bad download, that would explain it.

arrrghhh said:
The PA build I think is "blind", I don't know if anyone has tried it - additionally, the individual who built it does not own this device... So it's double blind? Haha
The CyanogenMod ROM's, however, are official and work great - many others have confirmed this.
If you had a bad download, that would explain it.
Click to expand...
Click to collapse
I tried flashing the good download this morning, it hung up just like the others.
I get the bootloader unlocked screen then it'll show the cyanogen logo for roughly 24 seconds the first time before hanging up,
after which it reboots to the bootloader unlocked screen, but when it gets to the cyanogen logo each time gets subsequently shorter between hangups...
Any ideas?

AMerexican said:
I tried flashing the good download this morning, it hung up just like the others.
I get the bootloader unlocked screen then it'll show the cyanogen logo for roughly 24 seconds the first time before hanging up,
after which it reboots to the bootloader unlocked screen, but when it gets to the cyanogen logo each time gets subsequently shorter between hangups...
Any ideas?
Click to expand...
Click to collapse
I suppose some sort of hardware issue. Like I said, I've flashed most of the newest ROM's here for the Q - all work fine. Hell, some I even ported myself...
I'm kind of at a loss. Can you get adb? Not even sure what to check for next... if you are wiping properly in recovery, that should be sufficient.
Hm, I guess that brings up a good point. Have you tried wiping system, flashing, doing a factory reset, then booting? Most, if not all of the ROM's should wipe /system before flashing... So it probably won't do anything different.

AMerexican said:
I tried flashing the good download this morning, it hung up just like the others.
I get the bootloader unlocked screen then it'll show the cyanogen logo for roughly 24 seconds the first time before hanging up,
after which it reboots to the bootloader unlocked screen, but when it gets to the cyanogen logo each time gets subsequently shorter between hangups...
Any ideas?
Click to expand...
Click to collapse
After the crash during CM bootanimation, boot to recovery and
Code:
adb pull /data/dontpanic/apanic_console
apanic_console should contain the log of the kernel panic, post it here.

kabaldan said:
After the crash during CM bootanimation, boot to recovery and
Code:
adb pull /data/dontpanic/apanic_console
apanic_console should contain the log of the kernel panic, post it here.
Click to expand...
Click to collapse
For my own personal edification, /proc/last_kmsg would work in this instance as well?
Just curious why you went for the apanic_console instead

arrrghhh said:
For my own personal edification, /proc/last_kmsg would work in this instance as well?
Just curious why you went for the apanic_console instead
Click to expand...
Click to collapse
Yes, /proc/last_kmsg would work as well.
Though there's a scenario were it wouldn't be the same - if the user would miss the right time to hold 'volume up' (to get to the recovery after crash) and pressed "power+volume down" to force reboot and try to enter recovery again. In such case, /proc/last_kmsg would not contain the panic from previous boot, the panic would be only in /data/dontpanic/apanic_console.
/proc/last_kmsg - log from the last boot
/data/dontpanic/apanic_console - log from the last crashed boot

kabaldan said:
Yes, /proc/last_kmsg would work as well.
Though there's a scenario were it wouldn't be the same - if the user would miss the right time to hold 'volume up' (to get to the recovery after crash) and pressed "power+volume down" to force reboot and try to enter recovery again. In such case, /proc/last_kmsg would not contain the panic from previous boot, the panic would be only in /data/dontpanic/apanic_console.
/proc/last_kmsg - log from the last boot
/data/dontpanic/apanic_console - log from the last crashed boot
Click to expand...
Click to collapse
Ah, that makes sense - I was not aware of this apanic_console
Thank you!

arrrghhh said:
Ah, that makes sense - I was not aware of this apanic_console
Thank you!
Click to expand...
Click to collapse
I'm getting an error from the forums saying the text is too long. any way around that? or do i need to divide into multiple posts?

AMerexican said:
I'm getting an error from the forums saying the text is too long. any way around that? or do i need to divide into multiple posts?
Click to expand...
Click to collapse
Pastebin.com, hastebin.com, pastebin.ca, heck even put the file in .txt format and attach to this post, upload it dropbox...
Thanks!

arrrghhh said:
Pastebin.com, hastebin.com, pastebin.ca, heck even put the file in .txt format and attach to this post, upload it dropbox...
Thanks!
Click to expand...
Click to collapse
Thanks wasnt sure of the forums rules as far as that was concerned
http://pastebin.com/QFq1naK0

Any ideas?
Or anything else i need to do?