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.
Related
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
Hi guys. I don't really know what happened here. I've flashed a few different versions of Cyanogen's builds onto my MT3G without any problems. Today I flashed the official 1.6 dev build of Donut before doing Cyanogen's 4.2.3.1 flash. Well, the 1.6 seemed to go smoothly, but after the reboot, the recovery would no longer load. It's now giving me a picture of the phone with an exclamation point when I try to load the recovery.
How can I fix this? Anyone? Please?
taken from cyanogens website site instructions.
If you boot the 1.6 image it will install the HTC stock recovery. Booting back to recovery will show the /!\[] symbol. THIS IS NOT LOSING ROOT. You can still flash update.zip files from this recovery. Also, you can still flash a nicer (CM-1.4) recovery with fastboot, or flash_image inside the CM install once you get it installed.
thats what sounds like happen to me
How do I do anything though? I don't have the ability to do anything, it just sits there on that screen.
<edit> Also, I can't re-flash the recovery. I've tried, but it gives me the error:
Flash FAILED: The command could not be run
After figuring out how to install ADB and trying to fix it via that, it appears that I have somehow lost root. It's giving me Permission Denied or remote device not allow when I try to flash or use fastboot.
Got it fixed. Took me forever, but I made a goldcard and flashed with the stock ROM. Now I'm good to go again after installing CM recovery 1.4.
I dont know why but it seems like im the only person in the world who cant get his phone to work properly.
I rooted, got amonra recovery 1.7.0, partitioned ext2/swap/fat32, flashed newest radio, then flashed dangerspl.
And any rom I flash will never boot past the G1 logo screen.
I have only gotten jesusfreke's 1.5v2 rom to flash. it was the first rom i tried.
i rooted by doing the guide in "forum.xda-developers.com/showthread.php?t=548924", which asks me to go to g1upgrade.com and install root.apk, then use the telnetd method, and then protect root. to confirm i have root, when i go into terminal emulator, and use su root, it asks me if i want to allow application to run as root:root.
any attempt at getting a logcat using adb just says /sbin/sh: logcat not found.
it seems like everything i do always ends in an error noone understands.
can someone please help me before i give up on android forever?
Tatta_ram said:
I dont know why but it seems like im the only person in the world who cant get his phone to work properly.
I rooted, got amonra recovery 1.7.0, partitioned ext2/swap/fat32, flashed newest radio, then flashed dangerspl.
And any rom I flash will never boot past the G1 logo screen.
I have only gotten jesusfreke's 1.5v2 rom to flash. it was the first rom i tried.
i rooted by doing the guide in "forum.xda-developers.com/showthread.php?t=548924", which asks me to go to g1upgrade.com and install root.apk, then use the telnetd method, and then protect root. to confirm i have root, when i go into terminal emulator, and use su root, it asks me if i want to allow application to run as root:root.
any attempt at getting a logcat using adb just says /sbin/sh: logcat not found.
it seems like everything i do always ends in an error noone understands.
can someone please help me before i give up on android forever?
Click to expand...
Click to collapse
when it ask for allow root check remember and hit always
have you booted in bootloader to see if you have latest radio and SPL
what radio did you flash?
and what rom are you trying to flash..
How long have you waited on the g1 screen?
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!!!
Hi,
After successfully rooting a G1 stucked on TIM startup logo without any knowledge of versions with this method :
After downgrading using DREAIMG.NBH to:
Firmware 1.0
Radio 1.22.12.29
Build no. RC7
Amon recovery-RA-dream-v1.5.2.img
and I got old SPL and 1.22.12.29 Radio then I had installed JFv1.41 ADB ROM.
Then I had installed Hard SPL 1.33.2005 & 2.22.19.26I Radio to install CM6.1 or other newer ROMs:
But every time I install new rom via recovery manager (with power + holding home key) and not with fast boot, after restart it stuck in boot logo even I do Wipe data. I have tried with many type of ROMs.
So I reinstall JFv1.5 rom: it works!
Any solution for this issue ?? I want to get newest Rom on G1.
Also my recovery manager become : Android system recovery utility Built: JFv1.41. even I tried to reinstall Amon recovery-RA-dream-v1.5.2.img with terminal and telnet and no chance. (permission denied)
BR
Thanks in Advance.
Assuming you have sdk with fastboot set up properly to run fastboot commands. You should try this. Only if you understand the instructions and dont take shortcuts.
http://forum.xda-developers.com/showthread.php?t=831139
MAKE SURE YOU KNOW WHAT YOU'RE DOING THOUGH. Good luck