Related
I've been on XDA today for atleast 3 hours and havent gotten anywhere, I have owned my G1 since dec. 08, rooted it, and kept the firmware at 1.1. I have jesus freak recovery 1.41.
Like I said, I've been on XDA forums for 3 hours already and haven't had any clarity what so ever and am just frustrated right now. Without being 100% I managed to upgrade to 1.6 withy cyanogen 4.2.15.1 I lost everything that was on my phone, it hurts but I'm just frustrated to the point right now that the phone is functioning slower than before and theres lag between the screens and functions. With the upgrade, all of the phones original fucntions "contacts, alarm clock, calculator, etc." force closed and nothing worked, i tried to factory reset and because of the stupid sync issue from the begining skrewed me and about half of my info saved to my google account. I'm so frustrated right now.
I need to know how to install the newest recovery to hopefully work with Nand because I had to Manually rename the DRC83_base_defanged to update.zip and then had to manually rename update-cm-4.2.15.1-signed to update.zip to install each one at a time without having the ability to freely choose what zip i wanted to install.
I haven't been able to find what issues there are with using another phones firmware on the G1, i've seen the Hero firmware, the home screen looks gorgeous and runs like a dream, but I haven't been able to find anything saying that it is okay or a BAD idea to attempt to install it, also I havent been able to find any info on finding the newest g1 firmware or any mods to be able to make the g1 firmware look like the hero, or any other android platforms. I have just found constant cooked firmware after firmware with a hard time decyphering why one may be better than the other. If someone could help me, I would GREATLY appreciate it.
I continute to run into threads "how to root" or "down load this, and download this, and assuming you have something with options you dont have, make it work like this"
Please someone help.
First you need to upgrade your recovery b/c the one you have is very very Ancient with a capital A....You have to wipe before you flash the defanged then flash cyan w/o rebooting.
I want to upgrade my recovery, but I haven't found anything that can help me upgrade the thing. any links to tell me how to do it? and is there no order that I have to install the firmware? instead of having to go from 1.1 to 1.5 to 1.6, can i just go from 1.1 to 1.6 in one hit?
step 1: search the development forum for amon ra's recovery. read the instructions to flash it.
step 2: go to cyanogenmod.com and read the instructions for upgrading from scratch.
once you've done those two things, you'll be much happier.
maniacallyhappy said:
I want to upgrade my recovery, but I haven't found anything that can help me upgrade the thing. any links to tell me how to do it? and is there no order that I have to install the firmware? instead of having to go from 1.1 to 1.5 to 1.6, can i just go from 1.1 to 1.6 in one hit?
Click to expand...
Click to collapse
You don't re-root when you need to change roms you just wipe in recovery mode
You need amon_ra
http://forum.xda-developers.com/showthread.php?p=4647751#post4647751
Like the other guys have said, upgrade to Amon_RA recovery. This allows you to flash updates from any filename, not just update.zip. The link is in my signature, or it's on the G1 Dev Forum in the sticky threads.
After that, boot into recovery and go to the Wipe section. Wipe all the things there, not just data. I never used to wipe everything either and I found that was the source of alot of my problems when changing ROMs. Obviously if you have your SD card partitioned and you choose to wipe your ext then you will lose what is on there.
Cyanogen has good instructions on his Wiki, but basically you want to flash DRC83_base_defanged, DO NOT reboot, and flash CM over the top straight away, then reboot your phone and you'll have a nice clean CM install.
This flashes the HTC Developer image which includes legal Google apps (Gmail, Maps, etc) and then flashes CM over the top which includes all his cool changes but does not delete the Google apps which we aren't supposed to distribute because it's illegal. Perhaps you are not aware, but Cyanogen got a Cease & Desist letter from Google, which is why we now do the defanged base method. More ROMs are moving to this method as time goes on, Pay's ROM and Super D are two which do this.
As an aside, I have found CM is not the fastest ROM. Some people have had better success with a ROM called Super D which is quite popular and includes many of the Eclair bits and pieces which CM does anyway. I personally use Dwang's ROM which is a much more plain Donut image however it absolutely flies. Both of these are linked in my sig, and are usually within the first few pages of the G1 Dev Forum anyway.
Thank you guys so much! I really appreciate how helpful the community has been. I've been having some issues with the the upgrading and maintaining because of my memory card slot dying out. A lot of the times the system will not register that I have my micro sd card in it or it'll say the sd card is blank. I just hope the phone lasts the extra 6 months till the end of my contract
Sent from my T-Mobile G1 using XDA App
maniacallyhappy said:
I've been having some issues with the the upgrading and maintaining because of my memory card slot dying out. A lot of the times the system will not register that I have my micro sd card in it or it'll say the sd card is blank.
Click to expand...
Click to collapse
I used to have this problem too, but it went away when I moved to 1.6 (coincidentally the same time I replaced the SD Card that came with my phone with a new Class 6 card). So either the upgrade of the OS or the SD Card fixed it.
In going to have to try the new men card cause the system is already at 1.6 but the phone is still trying to kill itself.
Sent from my T-Mobile G1 using XDA App
Hello folks,
Well I recently made the switch from iPhone OS to Android , picked up a used Nexus One in pretty good shape, no scratches, like new and what not, the phone is amazing BUT I am having a hard time understanding some stuff (I thought I was getting a stock N1, and it seems it has been loaded w/ custom ROM and is rooted and unlocked. -which not bad in my opinion, but...
I still have some questions, I am trying to update to Froyo 2.2, and im not sure if I will ever get OTA since the phone has been messed around with and if i manually update to 2.2 it will cause trouble.
1) When I boot the phone it shows the "lock" to be opened, so I am assuming it is oem unlocked, the phone has working WiFi tethering (just like in 2.2)
2) also in the menu of the phone there is an app "superuser permission" which thats why assume the phone is also rooted
And finally In the "About phone" I get the following:
firmware 2.1-update1
baseband
32.36.00.28h_4.06.00.12_7
kernel
2.6.34-cyanogenmod
mod version
cyanogenmod-5.0.8-n1-test3
build
epe54b
I have reset the phone to factory settings, but the same info comes up everytime. the phone runs flawless, no lags, overall i love the phone.
And finally if anybody knows please feel free to share, I am trying to open port 80 on the N1 while it is running Wifi tethering and the only way i have found to do this is if the N1 is rooted, correct me if im wrong... i have a rovio that is refusing to connect to the N1s network...
Any positive input will be highly appreciated! thanks!
Your not very confused!
Your phone is unlocked and has root. its running cyanogenmod-5.0.8-n1-test3.
You can install a custom froyo rom without too much of a problem from recovery. Remember to nandroid-backup everything from recovery first.
Get into recovery by holding down the volume down button as you press the power button to power on the phone.
Heres an example of tethering via usb/forwarded port
http://blog.tangorangers.com/2009/02/tetherbot_android_and_slackware_how_to/
you can install 2.2 with no problem but you have to manually do it. you might get a notification for ota's but you won't be able to install them. just install it manually.
Man you guys are awesome! thanks for clearing this up for me.
atomoz said:
Man you guys are awesome! thanks for clearing this up for me.
Click to expand...
Click to collapse
Yeah man, you're money. For a used phone it is set up in possibly the best way possible for someone new to android and ready for you to throw the new CM6 ROM on there. You even have the proper radio already. You're good to go.
You can install Froyo in various ways. If you want total stock you can follow the instructions on this link and let OTA froyo install itself. If you need root you can download that from HERE
This method requires SDK installed with Fastboot on your computer with mandatory USB Drivers.
Or you can go the very easy way and use ROMs that is allready cooked, ready to flash in recovery right over your old ROM, like the link that is in my signature. It works great for me and is pretty much stock with root and a couple of extras you can delete via ADB if you don't need them..
Just download the Rom, drop it on the root of your SD Card and flash away in Recovery. all done!
What you are running is a test version of Cyanogen which is not the stable version. So it seems the previous owner didn't bother flashing it.
Hi. I have what seems like a rooted nexus one and I've been getting notifications for 2.2.1 update but keeps aborting when I attempt to. I don't care so much about this upgrade as I'm waiting for the gingerbread but would this problem also continue when gingerbread OTA appears?
Sent from my Nexus One using XDA App
Yes. If you want to receive OTA - you need to restore to stock recovery.
I barely got my N1 yesterday I didn't feel like been stuck in a 2 year plan for the nexus s I didn't think it was worth it. Any how Any tips on what should I do to my Nexus 1? is it worth rooting it and also I been looking for a carbon fiber case but can't find one
Options
If you update to a more recent version of custom ROM they have edited it to prevent the OTA notifications. If you can live with it for now then just update to a custom Gingerbread ROM you will be good to go. Otherwise I agree you have to restore to stock recovery.
Jack_R1 said:
Yes. If you want to receive OTA - you need to restore to stock recovery.
Click to expand...
Click to collapse
thanks. How do I restore to stock recovery?
I wouldn't normally disagree with Jack, but if you have a stock ROM, I would say that if you can look in your cache folder on the phone and find the update zip. Move the update to SD, and then flash through your custom recovery.
Depending on which recovery you have you may have to toggle signature verification...
Sent from my Nexus One using XDA App
Thanks danger-rat. I am very new to the smart phone world and to be quite honest with you not very savy when comes to tech related stuff. I came across this phone from craigslist which apparently is a dev edition phone and the only thing I know regarding this phone is build number frf91 kernel 2.6.32.9-27227-g3c98b0d android [email protected]#1.
The only thing I want to do is able to upgrade my phone OTA when it comes available.
Please provide detailed explanation if you don't mind as to how to do just that.
Thanks in advance
Lots of reading to do before you decide on anything.
http://wiki.cyanogenmod.com/index.php?title=Main_Page
http://en.wikipedia.org/wiki/Nexus_One
After researching, I believe my nexus is actually not rooted because I don't see any padlock when rebooting my phone so I'm wandering why when I do get the notification for update 2.2.1 it keeps aborting.....?
Padlock denotes an unlocked bootloader, which doesn't mean you are our aren't rooted, it just means you have more options to install your OS.
Rooting can be checked by opening terminal emulator apps, and typing "su" - if the prompt changes from $ to #, then you're rooted(i.e. You have root access to the file system).
Update requires stock recovery to update automatically, but you can install manually with a custom recovery.
If you really want just stock, the easiest way is to follow the unroot/restore guide in the wiki, but you will lose your data and settings...
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
If you want to keep your data, I can post other options...
Sent from my Nexus One using XDA App
Thanks. I'll try it.
Hi all,
I have a big problem. I have my old Nexus One that never I root or modify. Today, after more than 1 year of use and reading various root guides I decide root my phone. My phone are updated from Google to 2.3.3 and say that is version GRI40. After finish all process of root the phone boot perfect and run perfect. Later I install also the Recovery-RA to can make backups, etc.
After this the phone not boot any more... Keep frozen at main screen with the big "X" and the padlock at bottom.
I can´t use any more my phone... any ideas or help? I forget one step?
I can boot perfect and run the Recovery(*) mode with Recovery-RA and all these options of this application.
All help are welcome!
THANKS!
(*) Recovery version is: RA-Passion-v2.2.1
Try flashing a new ROM, it sounds like it got corrupted when you installed RA. If you made a backup try restoring it, if not just do a factory reset and flash whatever ROM you pick.
Edit: You might also get more help if you ask in the Nexus forum.
OK, thanks!. I make a nandroid backup, that is the first that I try restore, but this not work. Now I try download any other. You know if exist exactly the same 2.3.3 that I have unmodified on my phone before I install RA? Thanks again!
There might be, just search for "stock ROM" in the nexus forum.
Thanks dbz!, I already use the GRI40_rooted_deodexed_busybox_apps2sd.zip that I found here and run again!!!
One more question: if I like on next update receive the update from Google that automatically update my phone like in the past before root, I can?
If you want to get an update from google you'll have to unroot. Usually when an update is released it isn't too long before a rooted version is released so just be patient.
You don't have to unroot the phone to get and install the OTA's in the future.
But when you apply a stock update you will loose root.
Sent from my Nexus One using XDA App
Ok I tried using this All-in-one software to flash a kernel and it sent it over and wrote it but its stuck on the HTC logo, and yes I can boot into HBOOT and recovery, is there anyway I can restore straight back to everything factory?
Sounds like the wrong kernel for the Rom was flashed.
What rom/kernel were you trying to flash ?
I was trying to flash the holiradar Final rom, but it said I needed the newest kernel so, I didnt flash the rom yet but I went on the AIO program and flashed the holicakes 2.6.35.14 and when it wouldnt boot up after that...
So what do you suggest I do?
So you are going to need to flash the kernel that goes with the holicakes 2.6.35.14 rom.
Should be on the same site.
You can user CMD to fastboot flash boot boot.img and then the rom will boot.
From what I can tell on the rom page there is a kernel download section.
---------------------------------
Looks like he is instructing you to flash the kernel a different way than I have listed above, but both ways will work.
Riomaru said:
Ok I tried using this All-in-one software to flash a kernel and it sent it over and wrote it but its stuck on the HTC logo, and yes I can boot into HBOOT and recovery, is there anyway I can restore straight back to everything factory?
Click to expand...
Click to collapse
DO NOT TRY, FACTORY RESET WILL DO ABSOLUTELY NOTHING AND MIGHT ACTUALLY MAKE THINGS WORSE.
With that out of the way, don't use the AIO software, use fastboot.exe and flash a boot.img to fix the issue.
Riomaru said:
I was trying to flash the holiradar Final rom, but it said I needed the newest kernel so, I didnt flash the rom yet but I went on the AIO program and flashed the holicakes 2.6.35.14 and when it wouldnt boot up after that...
So what do you suggest I do?
Click to expand...
Click to collapse
No need to worry, you haven't had enough experience to know that it is normal. It is normal for the phone to not boot into the rom when the kernel doesn't match. since you have successfully flashed the kernel, you now need to boot into recovery (which I hope you have it installed at this point, if you have not, read how to do it and flash recovery) once in recovery, proceed to flash the HoliRaider rom and you'll be good to go.
in the same boat
Hi All,
I have a similar problem flashing the Kernal with the vivid toolkit (V 2.1) on my Vivid. I think there should be a big warning for that box. I tried flashing the Holicakes Kernal, and flashed it twice as it tells you to, and ended up with the white HTC screen. Then tried flashing back to the stock rom, more than twice now with no luck. In desperation I tried installing the RUU update 3.26.502.56_US but I now get error 150, which indicates a rom mismatch, and yet it is the update for the phone direct from htc.
What should I try next to get past the white screen?
Thanks
newbroman said:
Hi All,
I have a similar problem flashing the Kernal with the vivid toolkit (V 2.1) on my Vivid. I think there should be a big warning for that box. I tried flashing the Holicakes Kernal, and flashed it twice as it tells you to, and ended up with the white HTC screen. Then tried flashing back to the stock rom, more than twice now with no luck. In desperation I tried installing the RUU update 3.26.502.56_US but I now get error 150, which indicates a rom mismatch, and yet it is the update for the phone direct from htc.
What should I try next to get past the white screen?
Thanks
Click to expand...
Click to collapse
Did you install a recovery?
Also, it was not a good idea to try and install all different types of things once you thought it was messed up. Anytime you think you may have messed up, stop right then, read about the issue, and if you can't find the solution, ask a question. I think you can get out of this but some people aren't that fortunate.
vivid white screen
Thanks for the advice I will press on and do some more reading,
I can still get to CWM recovery and have tried restoring the backup image I made, with the same result.
During the kernal flashing process:-
- is the HTC dev lock supposed to be on or off? It is off and unlocked at the moment,
- is double flashing the kernal what is meant by the instruction 'if this is the first time you flash a kernal, make sure to reflash it', or as is suggested in esloan's post on this thread your supposed to flash a matching rom instead?
Thanks
You did the right thing by flashing the kernel twice. That is what those directions said. After you flash the kernel twice the next step would have been to flash a rom. I believe it is better to use the fast boot commands for doing this entire process. It sounds like you are still on the holicakes kernel.
What recovery do you have? 5.5.4 or WCX Recovery? You will have better results with WCX Recovery. Also watch this video:
http://www.youtube.com/watch?v=xEWa_lUd2bY&feature=youtu.be
That is by randog. He did a great video and he shows you how to install everything without a program. Do you have the holiradier rom on your phone?
I was on the CWM recovery.
Thanks for the link to Randog's video, I now have a working phone again.
The major difficulties I had was finding wildchild's webpage with the links shown on the video, mainly because searching for wildchild illuminati took me to a forum with no links to any thing vivid, until you register.
I was also a little worried that I wasn't getting ICS in the ATT_ generic rom, but I needn't have. The key seemed to be locking the phone again and running wildchild's PH39IMG.zip. After that the security warning on the Hboot screen disappeared.
I almost messed the rom flashing part. Randog's vivid does this really quickly, my phone was a good 3 minutes behind and the progress bar was stuck around the 10% way after his phone had finished.
Like Randog says in the video follow the steps and you wont brick and you'll have a working phone.
Thanks megatronisabeast
Glad you got it. Sorry, forgot to give out the link.
Sent from my HTC PH39100 using XDA
Afraid to screw up any further
Htc vivid. 1.2dualcore.ICS.*
unlocked boot loader.
Used all in one vivid *toolkit 2.1
http://forum.xda-developers.com/showthread.php?t=1498003.
There were two choices. After boot loader unlock, which I had already done. Using right reading logic, I went to the "next step". Didn't realize ICS meant ice cream sandwich. Dumbass. I used CWM 5.5.0.4. Then I tried to to update the kernel, to*Holicakes2.6.35.14. For some unknown reason. The result is the white screen of death.
.*
I have access to hboot. As well as the recover menu which has a backup and restore option.
NAND restore clockworkmod backup, is available. I'm not sure how proceed.*
At the bottom of the screen:*
RA Revamped
Build: made for the WCX ILLUMINATE SERIES by GINM
I studied quite a bit. Too dumb to get a clear picture of the necessary steps before I began, I guess. Again, what a Dumbass.
I *need a better understanding of the process.
I didn't know about the super guide until it was too late. Rather, I did not understand I had seen the super guide when I saw it. It was from December, called a Holliday guide, so I didn't read it. There were so many guides, it confused me pretty throughly. Sheesh.
I have the htc white screen, reboots every three minutes or so.
I would really appreciate someone who knows to give me some clarification on these issues.
I understand a lot of these issues have been dealt with in this thread. I'm just really apprehensive.
I hope I posted this in the right place.
Thanks in advance,
Microbot2
Microbot, you have done pretty much what I did. If you follow megatronis a Brady's advice you will have a working phone. In fact I'm using it right now. Use the generic att zip an you will have ICS less the ATT bloatware.
Okay mircobot, I am home and can help you. Here is what you should do:
http://www.youtube.com/watch?v=xEWa_lUd2bY&feature=youtu.be
Watch that video. Shows you what you will need to do to get everything working again.
The next thing, you need to download all of the files you will need for getting your phone working again. I would recommend going here:
http://www.wcxxperia-nce.com/index.php
You will have to register to see the vivid forums.
Next decide if you want to be able to tether (generic build) or if you want stock based rom (ATT vivid ics).
Download the zip file. Follow the instructions in the video and should get you up and running in no time. That would be the easiest way in my opinion.
If you can't get it figured out or need more help just post here and we will try to assist.
Microbot2--vivid
Hey guys, thanks for the prompt reply's and your general bad-assness.
I just woke and will Start on the instructions.
Megatronisabeast, really appreciate it. Newbroman, thank you.
I already feel considerably less worried about this already. I'll let you know how it works out.
microbot2_no PH39img.zip
Note: I updated to ICS from att before I unlocked the bootloader, which is still locked as now the phone can't be seen by the program.
Megatronisabeast, thanks for the link to the video. I am a little closer to understanding now. Unfortunately, I don't have direct access to the internal storage, like the guy in the video did. and I couldn't discern the website URL and he never tells you directly, except for "goto wildchilds site" which i couldn't locate.
I now know that I have access to wildchildes recovery. Unfortunately, I can only see the internal storage if I use WC recovery, ("windows wants to format it") then goto USB-MS. Otherwise the computers don't see it when its plugged up. It says "device not found when I try to do something in AIO_toolkit 1.2 Don't know if that helps.
I did find the wcxrecovery.img
It appears that you have to have access to internal storage to load an image to it. PH39img.zip, which I don't have. I can't seem to find the wildchild ICS image, either. when I start my phone, it looks for the ph39img.zip, doesn't see it, goes to the white screen.
I don't understand how to get the image back,Rather, how to access the internal storage again. is PH39img is the same thing as the ROM? Do I have to load PH39IMG.zip and the wilchild_vivid_ICS.ROM, which, again, I can't seem to find.
This feels like a comedy of errors. I wish I would have studied longer. I usually do. THEN, I find "newbie_proof" all in one toolkit.
I Just wanted it rooted. All I had to do was click "root" instead of "kernel". Man, what was I thinking?
If only I had taken the Red Pill.
Thanks again,
Look at my post above, the link for wild Childs site is there. You have to register to see the vivid forums. That is also where you will download the files needed to set up the ROM, etc. You won't need the Ph39.img since you already have ics. That is for the bootloader. You can actually send a file to your phone in the recovery. since you already have recovery you would need to download the Android sdk tools, so you will have fastboot. You use fastboot to send the boot image to your phone. Then you would go to recovery and send the .zip file to your phone and flash in recovery. Sorry these directions aren't better, I will try to assist more when I get home, Swyping right now.
Sent from my HTC PH39100 using XDA
Microbot,
The wildchild files you need are in the first link Megatronisabeast cites
wcxxperia-nce.com/index.php (I'm a newbie and cant post the full web address). You have to sign up to the forum to access the files. The vivid forum will appear once you have registered.
The PH391IMG.zip is not your normal PH39img.zip you have to use the one contained in the WCX_generic_ATT.zip on the WCX vivid forum page. You also need to relock the phone. You are probably better off using the fastboot and the windows command prompt for this.
Can you boot into recovery at all?
Do you have another phone? you could use that to copy the PH39img.zip over. Thats what I did.
Mcrobot2---
Hi guys,*
Here is what I think I know:
HBOOT is a bootloader, *like a BIOS.
PH39img.zip is the boot file. Like PH39IMG.zip which appears to be a modified version for WC.
Kernel *is the memory and CPU manager.
ROM is an operating system package, or file placed onto the erasable/programmable part of the phones memory. NAND, I think.
S-OFF/ON *is a security check.
.Apk: compressed java file.
.Jar: *java application file.
.odex *files: helper files with most relevant information to compile and run the concerned application as fast as possible, a JIT Kind of thing.
----
I was able to relock bootloader, Yea!
Thanks megatronisabeast and newbroman.
--history--I updated to ICS from AT&T.
I thought I could skip reading for another three weeks because of newbie-proof AIO 2.1. * wrong!
I wanted to root my phone. *I had unlocked the bootloader with htcdev.*
Found hasoons all in one vivid 1.2. Used WC's recovery. I then flashed with hollicakes kernel, twice. Wsod.
--
Megatronisabeast:*
You use fastboot to send the boot image to your phone. Then you would go to recovery and send the .zip file to your phone and flash in recovery.
-I'm not sure the exact boot img,*
- I think the zip file would be the rom?
Getting closer.
Thanks again guys. I'm feeling a little thick lately. Like freshman year of college! Weed out classes.