Trying to revert to stock - G1 Q&A, Help & Troubleshooting

I followed first guide in the "informative threads" thread about reverting to stock up until this step:
5. Hit power to start the update DO NOT INTERRUPT!! i can not stress this enough.
Whenever I enter the bootloader it gives me a grey screen for a second and says "No Image Found" and then shows me the attached image.
Any ideas? I've been on the updating my phone with Cyanogen as often as he releases a new version of his rom.

How far are you trying to go back? Stock SPL and recovery? or just stock ROM? If you're going all the way backwards, change the SPL first, cause when you flash rc29 or rc7, it flashes an incompatible radio img.

Related

I upgraded to official donut build and lost root, someone help :(

I lost my root access and have been unable to get it back and install my old cyanogen rom. someone please help me try to get it back, ive been trying everything.
is it possible to root donut build once uve installed the real one? it keep aborting any installations i try to do, and doesnt let me flash the recovery img either. i dont know what to do.
Yea the official update will do that... but all is not lost. You can follow the guide here and downgrade to RC29 to gain root
http://forum.xda-developers.com/showthread.php?t=442480
you can follow those steps to regain root on your phone, when choosing which rom you'd like to run, if you'd still like to have root access but prefer the official builds you can check out this thread
http://forum.xda-developers.com/showthread.php?t=538456
if you still have an engineering or death spl, you can just flash recovery from fastboot.
Boot your phone while holding the camera, then press back button, you should see "fastboot usb" on the screen. Download amon_ra's recovery (look for it in android development) and flash it doing "fastboot flash recovery recovery-RA-dream-v1.2.2.img". After it's done you should have recovery back and now you can restore your nandroid or flash another update.zip
I downgraded back to RC29 successfully, but now its not letting me install any apps from the sdcard or online to the phone, it just keeps saying Install unsucccessful on any app. Wat could be causing this?
i ended up rooting the phone the old way, using telnet. now its working again

Cannot flash any update.zip due to ADP1 1.6

I tried upgrading from 4.1.1.1.1. to Cyan's most recent ROM and have locked my phone to ADP1 1.6 do to my phone giving some error and rebooting when it wasn't supposed to. I cannot install Any update.Zip files it gives me the following error (Install aborted) after trying flash any update.zip, i am at stock recovery, and i get permission denied on various commands Via ADB but it tells me i have root still. On top of that Fast boot isn't letting me install any type of recovery image giving me an error (cannot load "cm-recovery-1.4.img"). Can anyone help me out of this funk i am in and again i am not able to unroot my phone to stock. Thanks for the help in advance
T-Mobile G1
Hard SPL
ADP1 1.6 ROM(dream_devphone-userdebug 1.6 DRC83 14721 testkeys)
After you flashed the ADP1 1.6 did you reboot the phone or did you flash the cyan rom? I don't actually know what happens if you reboot before flashing the cyan rom but apparently it's not a good idea since the wiki guide says, in bold, not to reboot until after you flashed the new rom.
Well yes i was aware that i wasnt supposed to reboot but as the phone was doing something to the radio it went black next thing i know the phone goes through its normal process to boot up. But this was while i was trying to install 4.2.3.1.
The answer you seek kinda sucks, but it also has a very clear solution: you lost root.
Your fix: re-root and follow the direct instructions for getting to 4.2.3.1.

[Q] CM5 install prob- not booting into custom recovery?!

Hi,
I've owned and ROM'd two Android phones, but not a G1 and wanted to help out a friend to get her stock 1.6 G1 to CM5. We ran into problems which led me to not want to continue before they are sorted out. I looked for answers to this but couldn't find any, so please don't flame me if I overlooked any. I tried to go by the instructions in the CM wiki.
This is what we did:
- We installed ClockWorkMod Recovery through the ROM Manager app
- We rebooted into that recovery and via adb flashed AmonRA recovery
- we rebooted into the AmonRA recovery which worked (I *think* just regularly holding Home while powering on)
- we flashed the appropriate radio update for her US TMo G1
- the documentation said "phone will reboot during update". I think it did, but it seemed stuck on "formatting cache" in recovery.
- when holding Home on reboot after that, it did from there on NOT reboot into the custom recovery
- instead, it rebooted into what looks like "bootloader" mode on my Moto Milestone, a screen with a phone and an exclamation point. We could get into stock recovery with Alt-L, but I don't think that is what we wanted.
At this point, it seemed to not reliably boot into custom recovery, so I didn't want to continue the process. I assume I could have gone down the same of flashing a custom recovery, but I wasn't sure what would happen with/after installation of the DangerSPL if booting into recovery wouldn't work.
So - is the "booting into bootloader instead of recovery" a known issue? Am I too much of a noob on the G1 and did totally miss something? Could or should we proceed to the DangerSPL / CM5 installation with this going on?
Any help would be much appreciated!
W0nk0
Flashing a new recovery from CM5 or CM6 is not working well. Try flashing the recovery image / radio image / ... from fastboot and you should be fine.
Edit: I did not read well the first time. Now I notice, that you are still on stock SPL, sorry. But re-reading well I've got a question: Are you sure you flashed already successfully a new recovery? For me it seems you are still on a plain stock G1.
Sent from my Htcclay's Superfly G1 using XDA App
Thanks a lot for your help!
We _were_ on a custom recovery twice, after flashing it from ROM manager (Clockworkmod then) and on the AmonRA recovery after that. As the recoveries clearly had non-stock things like nandroid I'm quite positive.
The problem seems to be that they didn't "stick" - we flashed the radio ROM upgrade from Amonra recovery, but after a reboot with Home pressed landed in the exclamation point screen again (which seems to indicate stock recovery as you can get to that with Alt-L from there).
If fastboot is indeed the way to go, where do I get the drivers for the windows/pc side of it? The noob guide I found had no help there :/.
Thanks again,
W0nk0
Sent from my Dell Streak using Tapatalk
Few things;
1) if you have the OEM system image, then, indeed, the recovery will be overwritten by the OEM recovery image upon reboot into the system.
2) You say that you've written a RADIO image.... ***WHAT*** radio image did you write? You should have written a radio with a version number that starts with a "2".
3) Have you written a new SPL? The SPL you should write is 1.33.2003. DO NOT install deathSPL, no matter how many RETARDS suggest it. There is ABSOLUTELY NO USE in it. 1.33.2003 is SAFE to install (unlike 1.33.2005), and the ONLY benefit of 1.33.2005 has been GREATLY EXCEEDED, making that "benefit" entirely pointless.
Note that with the stock SPL (0.95.0000), there IS NO FASTBOOT. 1.33.2003 has a very strong fastboot capable of writing ALL partitions, including the radio image. Fastboot is the safest way to write the radio and SPL, but prior to installing an SPL with a strong fastboot mode, obviously you can't use this feature.
Steps:
1) Reinstall custom recovery,
2) reboot into recovery and write 1.33.2003 SPL.
3) DO NOT let it boot into regular system prior to installing 1.33.2003 SPL, or it will overwrite that custom recovery.
4) After installing the good SPL, it would still overwrite the custom recovery by booting into the regular system, but by this time, you will have FASTBOOT, so it doesn't matter.
5) Now do what you want... but once you have a 2.x radio and 1.33.2003, do NOT write any other radio or SPL, and for F SAKES DO NOT RUN ANY NBH FILES EVER NO MATTER WHAT!!!

[Q] Is Fastboot the answer to my woes?

I want to flash a new radio and kernel to my G1 that is running CM6. My signal is atrocious and I get a few random oddities each day.
I have tried the recovery flash for the radio at least 6 times now in various ways following various guides and every time I do it it crashes my phone and I end up flashing the image, rooting, etc, to get back to CM6. it takes me over an hour to get back to normal and it just plain sucks!
So my question is..... Can I use fastboot flash to flash the image files for the radio and the kernel without being on the special Hboot 1.33.0013d and such?
I was planning to use the instructions from the ezterry kernel page and just want to check that I wont bork up my phone. I seem to recall that the fastboot flash bypasses all the need for FR-remove and such but want a second opinion before I take the dive this way.
Not trying to drive you away from CM 6, but have you tested other ROM to see if it has the same problem or similar.
I personally myself could not get CM6 to work properly on my G1 back when I was trying to use it.
I couldn't get the radio to recovery flash even on the stock ROM after rooting.
I guess I could try a different ROM.
I just now have proven to myself that i cant flash the EzTerry kernel from Rom Manager and clockwork recovery as I am in the midst of yet another image flash, re-root, and such after it wouldn't go past the reboot screen afterwards
This phone is just an extra toy but I am determined to figure it out.
I suppose I will just try the radio.img flash from fastboot tonight when I get home.
As long as I dont brick it I can always start over from scratch.
so I copied the image I want to flash onto the root of my sd card
did the camera+power boot
pressed the back key and I am at the screen with the red fastboot usb box
I plug into the computer (adb already installed and working fine) and go to the command prompt and type
fastboot flash hboot hboot-1.33.0013d.img
the screen says error: cannot load 'hboot-1.33.0013d.img'
Did I put the image file in the wrong place?
Edit: I put it in the root of the computers c: drive and typed
fastboot flash hboot c:\hboot-1.33.0013d.img
seems to have worked.
FireRaider said:
so I copied the image I want to flash onto the root of my sd card
did the camera+power boot
pressed the back key and I am at the screen with the red fastboot usb box
I plug into the computer (adb already installed and working fine) and go to the command prompt and type
fastboot flash hboot hboot-1.33.0013d.img
the screen says error: cannot load 'hboot-1.33.0013d.img'
Did I put the image file in the wrong place?
Edit: I put it in the root of the computers c: drive and typed
fastboot flash hboot c:\hboot-1.33.0013d.img
seems to have worked.
Click to expand...
Click to collapse
do the same thing with the radio and recovery
maximo360 said:
do the same thing with the radio and recovery
Click to expand...
Click to collapse
I got the recoveryand the hboot to flash but damned if I can get any radio to flash.
I get
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
this is with both version of the radio downloaded from the links in the EzTerry thread
What in the world am I doing wrong that I cannot flash a new radio?
installed the spoofSPL... didnt help
edit: Started over again from scratch, rooted, flashed RA recovery, dangerSPL, then fastbooted and managed to install the hboot and the new radio. I guess CM6 hates the newer radios.
edit: Pretty sure CM6 does hate the radio because now its hung up on the install screen.
off to do more research.
People ... you should read before flashing around.
Ok, let me try to help.
1) As long as you have a fastboot enabled SPL, there is no need to 're-root'. Boot into hboot and flash the things you want.
2) Going to 1.33.0013d you *lose* most of your fastboot capabilities, e.g. flashing a new SPL/radio/recovery is no longer working. The only chance is to flash a signed nbh-file (e.g. fully signed rom)
I suggest you to read Terry' thread carefully (a link is in my signature) and then to retry ...
Btw: If you have installed the "new" radio/spl combo you need an adopted kernel, too, otherwise you will get bootloops.
Sent from my Gingerbread on Dream using XDA App
AndDiSa said:
People ... you should read before flashing around.
Ok, let me try to help.
1) As long as you have a fastboot enabled SPL, there is no need to 're-root'. Boot into hboot and flash the things you want.
2) Going to 1.33.0013d you *lose* most of your fastboot capabilities, e.g. flashing a new SPL/radio/recovery is no longer working. The only chance is to flash a signed nbh-file (e.g. fully signed rom)
I suggest you to read Terry' thread carefully (a link is in my signature) and then to retry ...
Btw: If you have installed the "new" radio/spl combo you need an adopted kernel, too, otherwise you will get bootloops.
Sent from my Gingerbread on Dream using XDA App
Click to expand...
Click to collapse
I managed to get everything work and am running CM6.1+2708 and 0013d with the .27 radio.
Why do we go to the 0013d if it screws up the fastboot? I notice in your signature you are running it also?
And say I want to flash a different rom now? I can only do it from RA recovery, Correct?
But as it stands now I ought to be able to experiment around with the other radio and other roms using recovery without any more issues? Or do they need to have certain parameters?
Once rooted, (to my knowledge) you do not required to re-root it again.
You can use RA Recovery to flash other ROMs with out having to re-root. (as to what I was told) And I recommend RA Recovery instead of ROM Manager/ClockMod Recovery (bad experience with it personnaly).
So as long as the ROM that you want to try is compatible with your current SPL/radio. You should be fine.

Need help troubleshooting

Hey guys i was hoping someone out there can help me out. My phone just got the message to update to 5.0.1, but when i tried to update it, it would reboot then load to around 40% of the update then say error with a little android on his back with a red triangle on his stomach. So i thought this was because of my phone being rooted and unlocked, so i unrooted it and locked it using Nexus Root kit, and when i tried to update the phone to 5.0.1 it still gives me that error message. Some things to note my phone was ATT and i did delete the ATT bootloader immage and all of there ringtones when my phone was rooted. Please help
You mean AT&T Boot animation image?
Thats exactly why your OTA failed because you did changes to your /system/.
This is why I say if someone is going to do changes to /system/, you may as well flash a custom ROM because when you get OTAs, you're going to end up in your current position. There are a number of ways to approach this issue,
1) Return back to stock by flashing factory images http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
2) Unlock your bootloader -> Flash TWRP -> Flash a custom rom, kernel (optional), gapps, supersu
Either or will get your phone booting again.
zephiK said:
You mean AT&T Boot animation image?
Thats exactly why your OTA failed because you did changes to your /system/.
This is why I say if someone is going to do changes to /system/, you may as well flash a custom ROM because when you get OTAs, you're going to end up in your current position. There are a number of ways to approach this issue,
1) Return back to stock by flashing factory images http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
2) Unlock your bootloader -> Flash TWRP -> Flash a custom rom, kernel (optional), gapps, supersu
Either or will get your phone booting again.
Click to expand...
Click to collapse
Will doing the first thing you say bring back the AT&T Boot animation image, because i think i need it to go get a new phone, i think my phone is defective because the speakers with make random popping noises and will have white noise coming out from them even when im not playing anything.

Categories

Resources