Hi there Android people.
I am having some issues with running the current Cyanogen *4.2.11.1*.
Phone: G1 Drea100 PVT 32B with stock 1GB SD
using anmon RA 1.5.2 recovery image
-wipe all available in menu.
-created a new partition- FAT32, Ext1 (upgraded to 4), Swap 32MB
-wiped all again.
-repair SD: ext
-flash signed-dream-devphone-userbug-ota-14721
-Once the flash above completed I did not restart, I simply flashed to update-cm-4.2.11.1
-reboot
Once it boots, my home process stops responding if I touch anything. This last for about 15 seconds, after that it seems to responds fine, but the browser and market place seems to auto-close on me from time to time, and I get random phone reboots, after a few reboots my phone simply stops turning on. I have to wait about 10 minutes to get into recovery and try to flash all over again.
I tried fix_permissions in the terminal, no luck.
I did some reading and noticed a lot of people are running different Radio/SPL versions other than stock, I am no super user, so I don't know if any of this effects ROMs, or if I should be flashing either for any sort of benefits I am missing out on? could this be the issue? Current SPL/Radio below:
HSPL10.95.3000
CDLP-4
Radio-2.22.19.261
Any input would be much appreciated.
Thanks,
D3AD PIX3L said:
Hi there Android people.
I am having some issues with running the current Cyanogen *4.2.11.1*.
Phone: G1 Drea100 PVT 32B with stock 1GB SD
using anmon RA 1.5.2 recovery image
-wipe all available in menu.
-created a new partition- FAT32, Ext1 (upgraded to 4), Swap 32MB
-wiped all again.
-repair SD: ext
-flash signed-dream-devphone-userbug-ota-14721
-Once the flash above completed I did not restart, I simply flashed to update-cm-4.2.11.1
-reboot
Once it boots, my home process stops responding if I touch anything. This last for about 15 seconds, after that it seems to responds fine, but the browser and market place seems to auto-close on me from time to time, and I get random phone reboots, after a few reboots my phone simply stops turning on. I have to wait about 10 minutes to get into recovery and try to flash all over again.
I tried fix_permissions in the terminal, no luck.
I did some reading and noticed a lot of people are running different Radio/SPL versions other than stock, I am no super user, so I don't know if any of this effects ROMs, or if I should be flashing either for any sort of benefits I am missing out on? could this be the issue? Current SPL/Radio below:
HSPL10.95.3000
CDLP-4
Radio-2.22.19.261
Any input would be much appreciated.
Thanks,
Click to expand...
Click to collapse
Why did you use "signed-dream-devphone-userbug-ota-14721"
I'm no pro but I used the base image that cyanogen recommends on his wiki page. The DRC83 defanged located here:
http://wiki.cyanogenmod.com/index.php/Latest_version#Defanged_DRC83
staunty said:
Why did you use "signed-dream-devphone-userbug-ota-14721"
I'm no pro but I used the base image that cyanogen recommends on his wiki page. The DRC83 defanged located here:
http://wiki.cyanogenmod.com/index.php/Latest_version#Defanged_DRC83
Click to expand...
Click to collapse
He used that because it is the proper image to use. A defanged file simply means that it has been rendered safe to download with no fear of infection. The link on his site is to the file used by the OP, so no worries there. Also, your radio is good, so do not worry about that either.
I have to ask, because you did not mention part of the process that should be happening. You flash the HTC image, then you do not reboot and flash the CyanogenROM. At this point you reboot. What happens? It should flash the radio, go to an HTC screen, stay for awhile, then reboot itself back to recovery where it gives a message regarding the cache being cleared. At this point you reboot for the actual boot process. Is this not happening for you?
cloverdale said:
He used that because it is the proper image to use. A defanged file simply means that it has been rendered safe to download with no fear of infection. The link on his site is to the file used by the OP, so no worries there. Also, your radio is good, so do not worry about that either.
I have to ask, because you did not mention part of the process that should be happening. You flash the HTC image, then you do not reboot and flash the CyanogenROM. At this point you reboot. What happens? It should flash the radio, go to an HTC screen, stay for awhile, then reboot itself back to recovery where it gives a message regarding the cache being cleared. At this point you reboot for the actual boot process. Is this not happening for you?
Click to expand...
Click to collapse
You are correct- after flashing CM the phone will flash the radio and reboot to the recovery screen where I will reboot again. Sorry for not including that detail.
Home process hanging in the beginning is not a problem, most people have that happenning. Eventhough home screen is shown, Android is still booting up, you just have to wait a little bit for everything to finish up.
Problems with stock apps usually indicate that something went wrong with instalation of the rom (i.e HTC 1.6 rom was not installed properly) so you may want to re-flash that again followed by CM rom of your choice.
Next time you phone reboots itself, try to get a log (there's more on how to do it in Cyan's thread), it's the only way to find out what happens.
Last, but not least, stock 1GB card is not advised for swap/apps2sd because if it's slow speed (it's class 2). Get one that's faster (class 6 preffered) and try that out, it may be the source of your problems after all.
Good luck.
how do i install this Cyanogen on my G1 with 1.6 firmware ?
simple007 said:
how do i install this Cyanogen on my G1 with 1.6 firmware ?
Click to expand...
Click to collapse
http://tinyurl.com/yjuy6u3
But in all seriousness
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
This would work. Please use search, this is such a n00b question.
Did another fresh install, so far no issues.
I will get a log the next time I install to see if I can track down the issue.
Also had time to install Enoch 4.2.11.2 theme. <3 this theme.
I will be heading to Frys today to pick up some cooling fans for the old PC, I will take a look for new mini SD
thank you to everyone that responded.
Just got home from Frys Electronics.
Purchases an A-DATA 8GB Class 6 microSD.
wiping/flashing again.
I am having a hard time learning about the swap file part of all this... I can find guides on how to create a Swap Partition, but not sure how to make it work and/or optimize it.
So I created a 32MB Swap- Previously I read the commands to enable Swap through the terminal- "linux_swap_en=1" I have used this and it does indeed turn on swap, but is there some sort of command to optimize? I believe tweaking the swap files is adjusting the "swappiness"?
The other way I enabled the Swap file was from the spare parts menu- Enabling Compache enabled my Swap file. Does this need adjustment? for size? or any other parameters? Or is this kind of an auto on for Swap?
Sorry I am a total noob, and want to know if I am missing out, I just keep loving this phone more and more.
I will be buying Cyanogen some beer soon ^_^
I've played with swap a long time ago and never quite understood it neither. As of lately, I've been running 10mb hack (in the developement section) and it works great. If you're inclined to get the swap thing going I suggest you read this thread. This will give you an idea of how to enable and tweak swap-related tasks.
Glad to hear that you have original problems taken care of (so far at least).
Good luck.
I think I just may have bricked my phone...
I did all the steps stated in my first post while flashing to 4.2.12.2 and got things going great. Flashed Enoch's Theme 4.2.12.2. Everything was rocking.
Then today, it shut it self off, I rebooted. Got to Enoch load screen then shut off, tried it again, and it won't even get past the G1 splash screen. I have had this happen a few times before, where it would power off randomly and I had to pull the battery, wait like 5 minutes and then get into recovery and clear/flash again. Now I am getting into recovery but after a minute or so it just shuts itself off again.
Can't wipe, Can't flash, cant even get into Cam+power to flash back to previous RC...
Not really sure what to do at this point...
If I do manage to get it running again, I do wonder why its doing this.
I use Cachemate to clear my catche and task killer to kill apps. Could Cachemate be the culprit in this mess, its the only app that I own that uses root? Not sure what else to blame it on other than the G1 one being one big POS and is only good if you can even get a ROM to run on it. I am 5 minutes away from ordering a Nexus.
once again thanks in advance for any input you can provide.
D3AD PIX3L said:
I think I just may have bricked my phone...
I did all the steps stated in my first post while flashing to 4.2.12.2 and got things going great. Flashed Enoch's Theme 4.2.12.2. Everything was rocking.
Then today, it shut it self off, I rebooted. Got to Enoch load screen then shut off, tried it again, and it won't even get past the G1 splash screen. I have had this happen a few times before, where it would power off randomly and I had to pull the battery, wait like 5 minutes and then get into recovery and clear/flash again. Now I am getting into recovery but after a minute or so it just shuts itself off again.
Can't wipe, Can't flash, cant even get into Cam+power to flash back to previous RC...
Not really sure what to do at this point...
If I do manage to get it running again, I do wonder why its doing this.
I use Cachemate to clear my catche and task killer to kill apps. Could Cachemate be the culprit in this mess, its the only app that I own that uses root? Not sure what else to blame it on other than the G1 one being one big POS and is only good if you can even get a ROM to run on it. I am 5 minutes away from ordering a Nexus.
once again thanks in advance for any input you can provide.
Click to expand...
Click to collapse
This sounds like a hardware issue, and not a bricking. Try a new battery, this may fix it, otherwise I am not sure.
cloverdale said:
This sounds like a hardware issue, and not a bricking. Try a new battery, this may fix it, otherwise I am not sure.
Click to expand...
Click to collapse
I will try the other battery I have at home in my other G1 and report back
D3AD PIX3L said:
I will try the other battery I have at home in my other G1 and report back
Click to expand...
Click to collapse
I tried it.
Same issue.
I did noticed that the batter pins were abnormal... One was sticking out more which was normal according to my other G1, the other 2 were shoved down. I tried to mess with the 2 to get them to pop back up to their normal position with no luck.
I am thinking about ordering a replacement.
okay, so tonight I am going to take the G1 apart and see if I can get those pins straightened out. Not sure if it will help, but its better than declaring it a paper weight.
will post the outcome.
Just out of curiousity (and I don't exactly know where I'm going with this) will your phone turn on and stay on if you plug it in (usb or charger)?
borodin1 said:
Just out of curiousity (and I don't exactly know where I'm going with this) will your phone turn on and stay on if you plug it in (usb or charger)?
Click to expand...
Click to collapse
It does not.
I think i will take both phones apart and swap out the screen since that is why I don't use the one. I watched a visual walkthrough seems easy enough
Has anyone disassembled their G1 and reassembled successfully? any tips?
Started to take apart the non-cracked bricked G1.
Once I removed the motherboard and started on the next step, I realized how bad it would be to end up getting the parts swapped and then have it not work... Put it back together and loaded up the latest Cyanogen on my working cracked G1.
*shrugs* it will do for now.
Waiting till the end of next month to order my Nexus 1, then I will have fun ripping apart both G1's and hopefully end up with one great looking, fully functional G1 to possibly sell or keep as an extra phone...
thanks to all who replied!
Related
I did search, honest! I'm halfway thru rooting my phone (downgraded and hardspl's, now just trying to find an up to date image)
real quick - once i'm back up to date on a recent android build can I still:
1. use market?
2. buy apps?
3. use google apps (maps, gmail etc)?
seen various comments on these questions and just want to get the latest info...
thanks!
yes sir, you absolutely can. and if you have already purchased some paid apps, you will be able to recover them post upgrade via market without paying for them again. a very cool feature IMO
jomtones said:
I did search, honest! I'm halfway thru rooting my phone (downgraded and hardspl's, now just trying to find an up to date image)
real quick - once i'm back up to date on a recent android build can I still:
1. use market?
2. buy apps?
3. use google apps (maps, gmail etc)?
seen various comments on these questions and just want to get the latest info...
thanks!
Click to expand...
Click to collapse
IM me if you need help
Cheers guys really appreciate the help!
trying to choose a rom now - are the new ones based on the Hero stable on a G1/ worth trying yet? Any major advantage to them?
Thanks again
JACHero is definitely worth trying.. but to use that you need to upgrade your radio and spl.
Just in case it hasn't been said enough times yet, YOU MUST FLASH THE RADIO BEFORE THE SPL OR BRICK WILL ENSUE!
Ok cool - saw some comments about lag / RAM deficiencies on the G1 - have these been ironed out?
Mostly.. jachero uses linux swap now and it's running pretty fast. Just follow the instructions in the first post of the thread to partition your card.
Ok thanks. Are there major advantages in the Hero ROM? It looked a bit 'gloss' in the video if you know what I mean.
Also how's the battery life working out?
jomtones said:
Ok thanks. Are there major advantages in the Hero ROM? It looked a bit 'gloss' in the video if you know what I mean.
Also how's the battery life working out?
Click to expand...
Click to collapse
Main advantages to the hero rom are the swish interface, really useful widgets, integration with facebook, twitter and flickr, exchange imap and pop3 support, bragging rights.
I don't see much difference in battery life between this and cyanogen tbh.. but I keep my phone plugged in most of the day sp ymmv.
wow, sounds pretty good! I've started with a cyanogen just to begin with - weird though it's just been paused on the 'android' logo for about 15mins (still animating) ... he mentions:
17. It's taking forever to boot!
The first boot will take longer than normal because dexopt needs to run. If you are nervous, connect USB and run "adb logcat" to watch the progress.
Click to expand...
Click to collapse
in the FAQ but is this normal? (I haven't installed all that adb stuff) ... Wary of pulling the battery and screwing things up ...
Just let it load it does take a bit the first time.
If not, go into recovery again and do a wipe ALT+W and then update ALT+S
that's one thing i would go into the first few times.
Thanks wddglr ... trying that now (it was hung for like 20mins)
Great, that worked straight away! Looking good, I'm gonna give Hero a blast soon
Just make sure you follow the SPL upgrade instructions to the letter. That thing has caused enough bricks to defend china from the Mongols.
Heh, ok! Update radio 1st right? ... btw is there any way to exit the recovery console other than pulling the battery?
hmmm ... ok went here: http://code.google.com/p/sapphire-port-dream/
and installed radio, then rebooted and installed SPL - now it hangs on the G1 screen. Any ideas?
update: browsing another forum I tried booting with the camera button down and I get this skating android screen!
Home+power also works - Can I do an ALT+W without wiping the radio / SPL? ...
I got the same thing and I don't mind telling you that I was crapping myself
As long as you did the radio first (just in case there is anybody who didn't get that ) all I had to do was do another wipe (just wipes user data\apps etc - not radio or SPL or other "firmware stuff") and then that should work.
It didn't in my case but I just re-applied the ROM update and it worked OK but my heart was racing for a good 30 minutes
Also, you should look into flashing a recovery image onto there - I use Cyanogens (1.3.1 i think) and it's great - can do everything with the trackball etc...
Cheers,
Smiffy.
Home and back exits the recovery console and just incase you didn't know, the 2 phone buttons plus menu is like CTRL-ALT-DEL
Brilliant thanks Lordsmiff .. I just found these instructions along the same lines!
http://forum.xda-developers.com/showthread.php?t=534461
Nice one
'jacHero' didn't work the 1st time, trying a wipe and reinstall now...
what threw me was I expected it to reboot each time I made a change, didn't realise I had to use a card reader to add the main rom!
cheers
I posted this herehttp://code.google.com/p/cyanogenmod/issues/detail?id=329
This has been happening for me for a few cyan updates now, and also on the HTC 1.6
image currently
the g1 was "charged", when i got home i took it off the charger and cranked up all
the bells and whistles. within 5 minutes the g1 goes black except for the keys for a
moment and then they go dead as well. no reboot. just goes dead. when i do reboot it
it sometimes wont go throught the whole reboot without shutting back down. does not
happen when it is on the charger. really hard to calibrate the battery when your g1
wont stay on without the charger and when it is it says its charged! i would post it
on the bug tracker, but i can't tell if it's my battery or the rom
and i'm running the death spl 8g card, cyan recovery and newest update, with only a
fat32 and no ext or swap
an update.. maybe check into the device staying awake. seems like with everything
running(gps, 3g, blutooth, etc) and with the phone sleeping, it doesn't crash, but if
the settings to never timeout the screen are active and you leave it on, it crashes
within a few minutes.
you should have an ext partition (the swap is recommended but not required). I only say you should get the EXT because the problem may come when all your apps are in the fat32 drive... it doesn't unmount correctly when you shut down or reboot your phone so your apps / partition sometimes get messed up... this MIGHT be why you get the black screen because it's corrupting the running processes (that are running from the fat32 (apps2SD)) when you reboot the phone(or mount the drive on the computer through usb) while they're being used.... repartition your card to include a EXT3 partition and reinstall the rom... let me know if that works. Post #69 hope this post helps, lol
i have had an ext2 ext3, swap, no swap, all with fresh partitions.
jaaronmoody said:
i have had an ext2 ext3, swap, no swap, all with fresh partitions.
Click to expand...
Click to collapse
awww so i wasted post #69 lol... Did you keep the 1.6 HTC rom? or did you upgrade it to CM 4.2.3.1? Maybe it's the HTC rom that's the issue? install the 1.6 htc and move to cm 4.2.3.1 (you can go straight from htc1.6 to 4.2.3.1, just follow the instructions) and start with fresh fat/ext/swap partitions... i personally use 100mb for swap (just in case i try a rom that uses more than 32mb by default i don't have to repartition)
edit: sorry, just noticed you said it's been happening on a few CM builds already....
try this: make sure you have CM1.4 recovery, new radio and new spl... new partitions (fat/ext3/swap) install the HTC1.6 rom, as soon as it reboots into recovery install the 4.2.3.1CM update. reboot phone and boot everything up as normal....
If it doesn't work after 100% fresh install like that... then maybe it's just a phone issue?
mrandroid said:
awww so i wasted post #69 lol... Did you keep the 1.6 HTC rom? or did you upgrade it to CM 4.2.3.1? Maybe it's the HTC rom that's the issue? install the 1.6 htc and move to cm 4.2.3.1 (you can go straight from htc1.6 to 4.2.3.1, just follow the instructions) and start with fresh fat/ext/swap partitions... i personally use 100mb for swap (just in case i try a rom that uses more than 32mb by default i don't have to repartition)
Click to expand...
Click to collapse
thanks for your help, but I originally formatted and followed cyan's instructions for his newest legal rom. i had this problem still, and then tried to fresh install the stock 1.6 from htc, and still. i think it's an aosp thing. i have had everything running( 3g gps sync blutooth ) for a couple of hours while the phone has been asleep and i can wake it. but if i turn the screen on, its only a matter of minutes before a crash. it's all posted on the cyanmod code.google site http://code.google.com/p/cyanogenmod/issues/detail?id=329
Is anyone running Advanced Task Manager, someone typed in market that it was doing he black screen of death so I uninstalled it and reinstalled it and it was still acting weird so I unchecked "show Auto-End notification" and it seems to be working a lot better no black screen o death
i used to get the blackscreens. i dont get them anymore. turning off compatibility mode in spare parts helped. try that. untick and reboot.
AustinKnight45 said:
Is anyone running Advanced Task Manager, someone typed in market that it was doing he black screen of death so I uninstalled it and reinstalled it and it was still acting weird so I unchecked "show Auto-End notification" and it seems to be working a lot better no black screen o death
Click to expand...
Click to collapse
pershoot said:
i used to get the blackscreens. i dont get them anymore. turning off compatibility mode in spare parts helped. try that. untick and reboot.
Click to expand...
Click to collapse
I don't have advanced task manager or spare parts. thanks though
jaaronmoody said:
I don't have advanced task manager or spare parts. thanks though
Click to expand...
Click to collapse
your cyanogen build comes with the spare parts application.
pershoot said:
your cyanogen build comes with the spare parts application.
Click to expand...
Click to collapse
currently i'm on the stock 1.6 htc build
jaaronmoody said:
currently i'm on the stock 1.6 htc build
Click to expand...
Click to collapse
download spare parts from the market.
will try and report
jaaronmoody said:
death spl
Click to expand...
Click to collapse
Maybe the spl I just switched to the DEATHSpl last week and now this is happening
AustinKnight45 said:
Is anyone running Advanced Task Manager, someone typed in market that it was doing he black screen of death so I uninstalled it and reinstalled it and it was still acting weird so I unchecked "show Auto-End notification" and it seems to be working a lot better no black screen o death
Click to expand...
Click to collapse
advanced task manager does not attribute to the black screen of death. it works flawlessly on donut (from what i can see/observe).
pershoot said:
download spare parts from the market.
Click to expand...
Click to collapse
AustinKnight45 said:
Maybe the spl I just switched to the DEATHSpl last week and now this is happening
Click to expand...
Click to collapse
no go on the spare parts, maybe the spl??? doubt it though
AustinKnight45 said:
Maybe the spl I just switched to the DEATHSpl last week and now this is happening
Click to expand...
Click to collapse
it has nothing to do with the SPL. try the spare parts trick and see if that helps. even if it slows it down to once every 3-4 days would be an improvement.
pershoot said:
it has nothing to do with the SPL. try the spare parts trick and see if that helps. even if it slows it down to once every 3-4 days would be an improvement.
Click to expand...
Click to collapse
i did and it happened minutes after reboot, and i'm getting real close to a dreaimg.img test
jaaronmoody said:
i did and it happened minutes after reboot
Click to expand...
Click to collapse
wipe out your sdcard's ext partitions (not the fat32), and do a full wipe. reinstall the rom, get spare parts, untick compatibility mode, reboot, and then observe.
pershoot said:
wipe out your sdcard's ext partitions (not the fat32), and do a full wipe. reinstall the rom, get spare parts, untick compatibility mode, reboot, and then observe.
Click to expand...
Click to collapse
seriously, i installed the rom on a fresh wipe and format and i just installed spare parts and unchecked the box
lol dam ok..........what about your SD card could it be its going to crap out on you...
Hello all,
I'm curious about somethings for turning my g1 to the hero (rosie?) rom (wow it looks beautiful).
The first being Where can I actually find it? I found two sites that offer it but doesn't seem like its from the developer themselves (who I'd trust more).
Secondly, which developer has the best performance (e.g. speed, ect.). I've read that it is a deadly slow Rom and I already lack patience for my g1 now (It's the stock firmware). The hero its self looks much smoother, am I wrong?
If I can't risk my phone being bricked should I bother trying it? (I had it JF rooted in the summer which I did successfully on my first try, and I un-rooted it.)
Is there a text document with how to install with a video that coincides?
Lastly, Is Cyanogen a better rom? (this has next to nothing to do with the hero rom )
Hopefully I didn't miss a thread on this I searched for like an hour.
skratched1 said:
The first being Where can I actually find it? I found two sites that offer it but doesn't seem like its from the developer themselves (who I'd trust more).
Hopefully I didn't miss a thread on this I searched for like an hour.
Click to expand...
Click to collapse
You cant just start driving, you have to learn the basics.When you get in a car there a many things that you need to do first is learning and even taking test.
You must have root first and a recovery image and im guessing your all stock.The dream section has all the info needed to root now is up to you to decide if you want to read it.
-Best regards
Thank you. I am very comfortable with the rooting process. I just don't want to do it unless the rosie rom is worth it!
Basically, Hero is incomplete. It doesn't have Bluetooth nor full Google Voice integration, and it runs 1.5. However, at the rate the devs are going on Hero 2.1 the version it runs could change very soon.
For now, stick with Cyanogen as it is a better Rom. Hero doesn't really work on the G1, it's slow and there is a lot of core function missing. It will never be an everyday ROM. I think of it like a concept car. Its cool in a "look what we can do" sort of way, but just wait for the next HTC Android phone.
skratched1 said:
Thank you. I am very comfortable with the rooting process. I just don't want to do it unless the rosie rom is worth it!
Click to expand...
Click to collapse
video here:follow in order
1.http://theunlockr.com/2009/07/05/how-to-unroot-your-t-mobile-g1/
2.http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
3.http://theunlockr.com/2009/08/22/ho...ps2sd-onto-your-g1-or-mytouch-3g-best-method/
-Best Of Luck To You!
P.s. Better get started
Wii60 said:
Basically, Hero is incomplete. It doesn't have Bluetooth nor full Google Voice integration, and it runs 1.5. However, at the rate the devs are going on Hero 2.1 the version it runs could change very soon.
For now, stick with Cyanogen as it is a better Rom. Hero doesn't really work on the G1, it's slow and there is a lot of core function missing. It will never be an everyday ROM. I think of it like a concept car. Its cool in a "look what we can do" sort of way, but just wait for the next HTC Android phone.
Click to expand...
Click to collapse
Its not slow...You must be running a super old version..Hero 2.1 roms and 1.5 roms are both very fast...King's 2.1 is very fast and close performance to cyanogen, please dont misinform people.All current hero roms are fast, in a 2.1 rom you can achieve 20mb+ free ram which is about the same to a cyanogen rom. Maybe you used a old jac rom months ago.
-"Times are changing boy, you need to catch up"
Ace42 said:
Its not slow...You must be running a super old version..Hero 2.1 roms and 1.5 roms are both very fast...King's 2.1 is very fast and close performance to cyanogen, please dont misinform people.All current hero roms are fast, in a 2.1 rom you can achieve 20mb+ free ram which is about the same to a cyanogen rom. Maybe you used a old jac rom months ago.
-"Times are changing boy, you need to catch up"
Click to expand...
Click to collapse
I'm sorry to say, but no I have tried many Hero configurations on my class 6 as recently as a month ago. The fact is that even if there were drivers for all of the hardware over time Hero really starts to bog down. It will not always perform after that post-setup peak it has.
If you want working hero wait until the first 2 weeks of January when the Passion comes out.
Ace42 said:
video here:follow in order
1.http://theunlockr.com/2009/07/05/how-to-unroot-your-t-mobile-g1/
2.http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
3.http://theunlockr.com/2009/08/22/ho...ps2sd-onto-your-g1-or-mytouch-3g-best-method/
-Best Of Luck To You!
P.s. Better get started
Click to expand...
Click to collapse
Going to try this tonight. Read and watched the videos. seems very simple. thank you!
need help!
When following this guide http://theunlockr.com/2009/08/22/ho...ps2sd-onto-your-g1-or-mytouch-3g-best-method/ (I already did the one click root with no issues)
In part II of the guide
. Download the custom SPL for your device:
T-Mobile G1 – Here
MyTouch 3G – Unneccessary, skip this section and proceed to Section III.
3. Plug in your phone and mount the SD card (pull down on the notification bar and select the SD card notification then click Mount in the pop up window).
4. After the SD card shows up on the computer, put the SPL zip file on to the memory card.
5. Once it is done transferring to the memory card and you have renamed it, unplug the phone from the computer.
6. Turn off the phone and then turn it back on by holding down the Home and Power button to get to recovery mode (keep holding it until the recovery screen with the writing and black background come up). Here i get to the ! so I hit Alt + L to get to the recovery screen. It gives me the menu to reboot, apply zip, wipe. However at the bottom of the screen it says E: Can't open /cache/recovery/command
7. Once the recovery screen is up, click on Wipe Data. Once that is done, click on Apply Update.zip and wait for it to finish. I wipe the date and then apply zip. I then get this message __ Install from sdcard... Finding update package... Opening update package... Verifying update package... E: No signature (5 files) E: Verification failed Installation aborted
I'm assuming this means the SPL file is corrupt but I don't know much and probably am wrong.
How can I fix this? I got this far with no issues and so close to being done!
skratched1 said:
need help!
I'm assuming this means the SPL file is corrupt but I don't know much and probably am wrong.
How can I fix this? I got this far with no issues and so close to being done!
Click to expand...
Click to collapse
Just rename to update not update.zip and make sure the sd is Fat32 not Fat or NTFS.
radio goes first i think make sure you did that section.
Ace42 said:
Just rename to update not update.zip and make sure the sd is Fat32 not Fat or NTFS.
radio goes first i think make sure you did that section.
Click to expand...
Click to collapse
SD is fat32 and the update.zip just says update
My radio is 2.22.19.26I that is the most current, right?
tried again still the same message. Any other suggestions? should i unroot and start over again?
skratched1 said:
SD is fat32 and the update.zip just says update
My radio is 2.22.19.26I that is the most current, right?
tried again still the same message. Any other suggestions? should i unroot and start over again?
Click to expand...
Click to collapse
Yes you have current radio no need to flash it again unless you want a new paperweight.
Def no paper weight!
I tried again and Still the same message. What do I Do? thanks for all the help.
skratched1 said:
Def no paper weight!
I tried again and Still the same message. What do I Do? thanks for all the help.
Click to expand...
Click to collapse
Try to redownload the file.
did that twice once from the link in the video and once from http://code.google.com/p/sapphire-port-dream/
both gave me the same results.
UP AND RUNNING JACHERO
Thanks a bunch ace. In the two minutes its been up it's looked as good as I wanted it to!
so my son grabbed it this morning, it froze i took the battery out. Now it keeps going to the hero screens over and over again. what should I do?
If I were you I would try re-flashing. Do you have a custom recovery.img? Like Cyan's or Amon-Ra's? If you do, try wipe cache, wipe ext part, wipe cache, and then re-flash. That's always the first thing I do when my phone starts getting buggy.
i rooted my NC with 1.1.0 and everything was perfect. installed and backup with CWR v 3.0.0.5. I have been stuck in the two screens of cwr. I CANNOT TURN off the nc so 8 aborted on/off s do not work. I cannot restore from sd card since it boots back into cwr, so i have not been able to use any removal code. the Monster pack is not for 1.1. I think I may be bricked. How do I get out of this clockwork recovery program (i have tried all of the options in it too, including fixing permissions, recoveries and endless useless reboots. HELP!
Hold the power button and it will turn off.
i have done that but it turns itself right back on again. it will not stay off. when it does go back on, it goes right back into clockworkmod recover (orange menu screen, landscape only)
Try going here and see if that gets you out of trouble .. Hope it helps
I can't say for a fact that this will make a difference for you, but it certainly can't hurt. Make sure you plug in your Nook Color to the charger, then do the manual power off (as in hold the power button). That should force it to reboot.
Those were the instructions I was given when CWR froze up on me during a kernel flash and it worked. Good luck.
got any mortar-bricked!
got it tuned off. now totally dead.. does not respond to power switch at all now. beware of CWR!!!
Boot CWR off monsterpack SDcard and restore stock system.img/boot.img. This saved me. This is definitely auto-nooter 3.0.0 related because pre-rooted BN 1.1.0 flashable does not have this problem.
ddd22 said:
got it tuned off. now totally dead.. does not respond to power switch at all now. beware of CWR!!!
Click to expand...
Click to collapse
no can do...cannot be turned on. stone dead
It is not. Trust me, I've has this thing twice today. boot partition on emmc is messed up I guess. You CAN boot from CWR on SD card.
ddd22 said:
no can do...cannot be turned on. stone dead
Click to expand...
Click to collapse
With all due respect, I dont understand how that can be. When I press, or press and hold the power key, nothing at all happens. no screen or light activity of any kind... like someone removed a battery.
After your reply, thinking perhaps my removed micro sd card might make a difference, i put it back in and tried again to power on the NC.. nothing happens still. Are you telling me that somehow if i change the content of my SD card to the Monster Pack that somehow that firmware code is going to turn on the Nook even though i cannot power cycle it at all without that magic? I dont understand how this could be and creating that card is a fairly steep search and discovery mission for me which i am willing to do if it has a chance of working.
btw, the battery is fully charged according to the green N on the usb cable.
Thank you so much for your response.
zdrifter said:
Try going here and see if that gets you out of trouble .. Hope it helps
Click to expand...
Click to collapse
What he/she said.. Happened to me once today. Remove the CWR and you should be good to go
how do i do that when no matter what i do the NC will not power on at all...zero. I can no longer even establish a usb connection to the computer.. it detects something and then tries and fails to install required drivers (which were previously installed and previously working). As much as I wish you all are right and I am missing something, I think I may be the first fool to brick the unbrickable!
You will need to make a bootable SD card and boot off that.
i made a bootable cwr sd from the monster rootpack. same nothing happens. will not power on in any way shape or form. will now remake the card with the full rootpack and pray that i can eat my words.
chomp chomp chomp
(the glorious sounds of words being eaten). you both were 100% correct and trust you i should have even more. I followed your advice despite my doubts and I wrote the rootpack image to the sd card and held the power button for about 15 seconds and alive she came! now i am at least back to my cwr that i cant get out of. i now could use a little more of your wisdom as to the best next steps. should i remove cwr then reflash with say 1.1.0R2 or should i figure out how to use cwr to do that flash, and remove it after the flash is completed. obviously a newbee to flashing this device (less than a week old), but have been following Energy on HTC flashes for long times. There is so much information here, it is almost too much when you first step in and your collective willingness to help this doubting thomas is extremely appreciated. my apologies and my deepest thanks. more reading coming up..
resolved!
i added the zip for 1.1.0 -r2 to the monster sd boot card and installed the rom from there. setting it up now. thanks to all for not listening to my doubt and telling me to continue as instructed. forever grateful
ddd-22 - did you install from CWR after rooting 1.1 using the modified Autonooter, or did you sideload the rooted 1.1?
I installed CWR from a 1.1 that was rooted using Autonooter (modified for 1.1) and ended up in a CWR reboot loop similar to what you had.
Yeah- I attempted to run the OC rom after autonootered to 1.1 and got into the loop. Has anyone had succes in loading the OC rom after autonootering to 1.1? Thanks
Thank you for this thread. The exact same thing happened to me after trying to flash a kernel using CWR and autonooter3.0. Thought I was bricked for sure!
I am back to business and glad not to have an expensive paper weight!
though i am on the way to recovery, not fully there yet. the r2 prerooted version was great except i could not log onto gmail... it kept seeing the NC as a phone and was looking for a cellular network, and gave me the message "a reliable connection with google servers could not be made" or some such verbage.. In the pre rooted 1.1. r2, i followed the directions going through youtube etc, but that did not work. so i decided to try to restore the backup i made when i first got caught in the doloop. which i did again, so it is back to monster to start over again and clear out the NC. I have been scouring other sites and many people have been having this problem. I wish i could remember how i installed cwr (method) but cant. however, what i found fairly consistently, and i believe i made the same mistake, was not restarting the NC before i made the backup. seems that is what got a lot of folks into this doloop crisis. if anyone has a plan of how i should get back to my previous state of bliss, let me know. I am remaking monster pack again and clearing out my machine.
Ok, so i've spent a few hours at this already but let me give as much info as I can. I have read through many threads searching for info. I am no expert but I have had OG Droid, Incredible, and currently Thunderbolt all rooted so I am a novice.
This is my GFs phone and was previously bone stock, never rooted, no Roms nothing. So she gets the update recently and clicks yes and that is where the trouble began, phone constantly reboots and will not go past the language/activation screen. It never once went past that first screen, and she tried the hard reset and the battery pull.
So this is where I took over. I retried the hard reset (power + vol down) and also the battery pull. I also tried to activate in numerous other languages, all cause a reboot.
As per
http://forum.xda-developers.com/archive/index.php/t-1208713.html
I was finally able to get past the activation screen and make some progress. However after about a minute the phone always reboots, no matter what it is doing. I hard reset in the settings menu and that did nothing.
I next followed
http://forum.xda-developers.com/showthread.php?t=1326347
and got the phone rooted.
Installed
http://forum.xda-developers.com/showthread.php?t=1144951
and than installed CWR 4.0.0.4 ? (not sure the version whatever it comes with) Tested recovery and it it seems to stick even after rebooting several times, which the phone automatically does (maybe its a feature and not a flaw?) So I was unsure of what version of Android was even running because the phone will not allow me to go into about phone it always force closes *com.android.settings* but I figure what the heck and try my luck with a new Rom. I decided on
http://forum.xda-developers.com/showthread.php?t=1326542&page=11
So I did the usual. Rebooted into recovery, made a nandroid backup, wiped data, cache, davlik and even did /system for good measure. Than did the install and upon first boot all the same problems are there. It will not activate from the screen, it just reboots the phone eventually. I used the same method above to avoid the screen and now it will boot up and the phone is in fact running an AOSP Rom but it still reboots after about a minute. Oddly enough it also continues to refuse to let me open About Phone, in the settings menu. I also for good measure went into recovery and wiped everything again and also tried fixing permissions in recovery, all to no avail.
At this point I am thinking it is perhaps just a hardware issue, although the phone does not reboot itself in recovery. I would be willing to try a different Rom, however I don't think it would work. I am wondering if anyone has any other suggestions? Should I try this?
http://forum.xda-developers.com/showthread.php?t=1120062
Other info:
What does work is wifi, so i can get on the internet briefly. I can connect to google and get apps from the market.
I am leaving this for a few hours or I may have to re-title the thread "How do you put the LG Revolution back together after throwing it against a wall?"
Currently I'm sad face that you rooted and installed cwm but I think the update bricked it personally. Hopefully S.Meezy will see this as he has stock recovery. I would say just get back to bone stock and get it replaced. If anyone else knows how to get it fixed, my best guesses would be mt or S.Meezy, though adb that might work. I hope it all gets figured out. Someone needs to post stock GB without data or anything for people to flash to if need be. That might fix your issue.
My suggestion is to get the recover the whole phone...
http://forum.xda-developers.com/showthread.php?t=1211295
follow that but use the v6 TOT file. That will revert the phone to out of factory new, with updated radios. If you still have the issue then I would contact Verizon.
If everything works then you can re-run the update to Gingerbread.
Could be a long shot but I remember seeing something a little way back in another forum where a user w the same problem accidentially resolved his issue by restarting w the sd card out. For him it turned out to be a bad or incompatible sd card at the root of the problem.
If you have one in, pull it and restart. Hope thats it for you...
Sent from my VS910 4G using XDA App
Well i'm a glutton for punishment so i'm back.
I didn't want to bother with rooting it honestly but I did it out of desperation, figured a total wipe + brand new Rom would surely fix things.
Going to attempt the full recovery.
Tried pulling the SD card, than just the Sim card and finally without anything and none of the combinations worked.
Have you tried downloading a stock ROM to your PC/Mac and dropping that on your SD card and then flashing that ROM, after checking the md5? To me it sounds like your gf just had a bad download.
I think the issue is that you keep trying to flash the bad bits. Just my two cents...
Sent from my Dell Streak 7 using Tapatalk
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Haxcid said:
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Click to expand...
Click to collapse
What he said.
Remember: Absolutely do not, under any circumstance, unplug/turn off your phone once you start that process. It can take awhile, and might look like it froze, but just let it do it's thang.