Related
i would like to install the Danger SPL i just have a few questions before i attempt this. I would like to avoid bricking my phone if possible.
I have already looked at this and see how to install it. I was just wondering how i would install it seeing as i already have my mod and have the newest Radio. I am currently running CyanMOD 4.0.4 with the Hard SPL. Would i just simply put the Danger SPL's zip. on my root SD and recovery boot and run the zip?
I have checked and I do have the PVT that is mentioned in the thread listed above.
I want to make sure I have everything clear 100% before i attempt this. I guess it is called Danger SPL for a reason.
raysilverstone said:
i would like to install the Danger SPL i just have a few questions before i attempt this. I would like to avoid bricking my phone if possible.
I have already looked at this and see how to install it. I was just wondering how i would install it seeing as i already have my mod and have the newest Radio. I am currently running CyanMOD 4.0.4 with the Hard SPL. Would i just simply put the Danger SPL's zip. on my root SD and recovery boot and run the zip?
I have checked and I do have the PVT that is mentioned in the thread listed above.
I want to make sure I have everything clear 100% before i attempt this. I guess it is called Danger SPL for a reason.
Click to expand...
Click to collapse
Looks like your setup for the installation of it. Just place the SPL Update.zip onto the root of the sd card and install like you would a rom. But there is a catch. After the installing is complete, YOU HAVE TO manually reboot it by pressing Home+Power or whichever one reboots it, you can't use the trackball to select reboot. Once you do that it should go about its way on installing it.
Yes you are right. Just might want to put another rom you want on your sd card to to flash right away after flashing the spl because when you flash the new spl it will overwrite your existing rom causing you to be stuck at the g1 screen. Thats when you here all the idiots say I bricked my phone but fixed it.
Also, be careful to be sure that your /sdcard is mounted when you go to do that update. Sometimes when you flash Haykuro's SPL, it won't mount the sdcard properly, without being instructed to do so. ("mount /sdcard" when you drop into the terminal is all it takes). Dunno what caused that... but because of it, it wasn't reading the update.zip file I had.
Since you are using cm recovery 1.4, you can not use apply any zip for the spl, you must name it update.zip and than apply it that way with the option for update.zip, odd yes, but true, I suggest putting back on a rom that you already have that works for you, boot it up and than do a nandroid backup in case of future boot loops.
Hey supreme let's try not to hijack another thread...................
Hey supreme do get the ad here on xda for the goth dating site, if so wow does she got some amazing eyes, if that is goth this days maybe I am running with the wrong crowd
IConrad01 said:
Also, be careful to be sure that your /sdcard is mounted when you go to do that update. Sometimes when you flash Haykuro's SPL, it won't mount the sdcard properly, without being instructed to do so. ("mount /sdcard" when you drop into the terminal is all it takes). Dunno what caused that... but because of it, it wasn't reading the update.zip file I had.
Click to expand...
Click to collapse
By terminal i take it as the "go to console" or "ALT+X" option. If so once i am in terminal how do i leave it. Every time I go to it I have to remove my battery to get back to the recovery options.
raysilverstone said:
By terminal i take it as the "go to console" or "ALT+X" option. If so once i am in terminal how do i leave it. Every time I go to it I have to remove my battery to get back to the recovery options.
Click to expand...
Click to collapse
type recovery
Or type reboot to you guessed it REBOOT!!!!!!!!!!
gridlock32404 said:
Or type reboot to you guessed it REBOOT!!!!!!!!!!
Click to expand...
Click to collapse
He's trying to mount /sdcard. Rebooting would undo that. If you just type recovery it will take you the recovery screen no reboot
um of course i don't try the obvious solution lol. thanks i will try to install the Danger SLP later.
should i do i a wipe before i install the danger spl?
raysilverstone said:
should i do i a wipe before i install the danger spl?
Click to expand...
Click to collapse
The new spl will do it anyways so it doesn't matter
Hey folks,
i`m glad to found that thread about dangerspl...i`m loosing to many nervs because of that...
i`ve downloaded the spl file from these forum (http://forum.xda-developers.com/showthread.php?t=548924), renamed it to update.zip und applyed it at cm recovery 1.4.
i have the latest Radio, i`ve checked this a 1000 times...
everytime i want to install that dspl it`s extracting and installing very very fast (2-3sek), than reboot, it reboots in recovery...then i reboot the system, erverything is normal...the rom is starting...no stuck @ g1 logo...
the only effect is the missing of some internal memory mb`s...
so, what to do `??? was this file i`ve downloaded the correct DSPL??
Recovery shows "installing hboot"?!
i hope someone can understand my bad english...
forget about it !!!!
only my dumb fault.....
gridlock32404 said:
Since you are using cm recovery 1.4, you can not use apply any zip for the spl, you must name it update.zip and than apply it that way with the option for update.zip, odd yes, but true, I suggest putting back on a rom that you already have that works for you, boot it up and than do a nandroid backup in case of future boot loops.
Click to expand...
Click to collapse
Totally incorrect. I've flashed this SPL several times, and using Cyan's recovery you don't have to rename it.
The Ape said:
Hey folks,
i`m glad to found that thread about dangerspl...i`m loosing to many nervs because of that...
i`ve downloaded the spl file from these forum (http://forum.xda-developers.com/showthread.php?t=548924), renamed it to update.zip und applyed it at cm recovery 1.4.
i have the latest Radio, i`ve checked this a 1000 times...
everytime i want to install that dspl it`s extracting and installing very very fast (2-3sek), than reboot, it reboots in recovery...then i reboot the system, erverything is normal...the rom is starting...no stuck @ g1 logo...
the only effect is the missing of some internal memory mb`s...
so, what to do `??? was this file i`ve downloaded the correct DSPL??
Recovery shows "installing hboot"?!
i hope someone can understand my bad english...
Click to expand...
Click to collapse
I got the same problem I have the had newest radio and flashed to danger spl the spl worked but now it hangs @ g1 screen never gets past it... i am trying to install cyanogen 4.2.3.1 if that makes a difference? help plz
GaMePwNz said:
I got the same problem I have the had newest radio and flashed to danger spl the spl worked but now it hangs @ g1 screen never gets past it... i am trying to install cyanogen 4.2.3.1 if that makes a difference? help plz
Click to expand...
Click to collapse
Try using three finger mary (talk+menu+power) to reboot and hold home to get into recovery. Flash the ROM you should have already put on your sd card beforehand since as Supreme already said, the SPL will overwrite the existing ROM...
evry1sgirl said:
Try using three finger mary (talk+menu+power) to reboot and hold home to get into recovery. Flash the ROM you should have already put on your sd card beforehand since as Supreme already said, the SPL will overwrite the existing ROM...
Click to expand...
Click to collapse
I've done that and after I flashed the rom it always hangs on g1 screen on reboot... I finally was like f it and just re did everything from rc29 but now like half the roms wont install themes mess up and its all screwed up
GaMePwNz said:
I've done that and after I flashed the rom it always hangs on g1 screen on reboot... I finally was like f it and just re did everything from rc29 but now like half the roms wont install themes mess up and its all screwed up
Click to expand...
Click to collapse
Did you repartition your sd when you did all of this?
evry1sgirl said:
Did you repartition your sd when you did all of this?
Click to expand...
Click to collapse
no i tried 2 partion my sd but my phone kept sayin there wasnt a sd
Hi guys im wondering if any of you can help me out here.
I have been on cyanogen (latest) for a while but decided to have a go at puting the ''donut'' rom in the android development bit of this forum (eu version as im in uk) on my phone this evening.
I flashed the base version fine and it started up great. Then I flashed the extention (add on) part and it started up but after the ''android'' screen it just went black and nothing happend. So i did a hard reset and tried again, same problem occured.
I then tried to put the latest cyanogen rom back on my phone, put to root, started it up then BAM stuck on g1 screen. Didnt get passed it. So put other roms later cyan roms on and still same problem occurs.
I then freeked out and tried to go back to RC29, so i deleted everything of my sdcard and put the dreming file on, pressed power and camera button and then BAM it comes up with some sort of cyanogen screen and not the rainbow screen. So havent got a clue how to install the dreming file. So gave up there
So this is where im at. Nothing on my sd card. Still got cyan on my phone but cant get it started up, no matter what rom I try it keeps getting stuck on g1 screen.
I know this is completly retarded but I really need help to get this sorted.
ANY HELP WOULD BE GREAT
Thanks
Have you been wipping?
Wiped before flashing donut rom...And when trying to put cyanogen rom back on...
If you can boot into recovery or into fastboot then you should be fine.
Wipe, if you use appps2sd the wipe your ext partition as well.
Flash base defanged rom from Cyan's site and flash Cyan's latest (Check md5 sums of both to make sure that your downloads are not corrupted. Fix permissions and you should be ok. If you still can't boot up (and it will take a while to boot up after a wipe) then you can go back to RC29. Just make sure that your nbh file is named exactly Dreaimg.nbh and your card is formated to FAT32, otherwise fastboot will not find it.
Good luck.
borodin1 said:
If you can boot into recovery or into fastboot then you should be fine.
Wipe, if you use appps2sd the wipe your ext partition as well.
Flash base defanged rom from Cyan's site and flash Cyan's latest (Check md5 sums of both to make sure that your downloads are not corrupted. Fix permissions and you should be ok. If you still can't boot up (and it will take a while to boot up after a wipe) then you can go back to RC29. Just make sure that your nbh file is named exactly Dreaimg.nbh and your card is formated to FAT32, otherwise fastboot will not find it.
Good luck.
Click to expand...
Click to collapse
Wow lots of help there thanks.
Firstly tho I cant find this ''base defanged rom'' from cyans website? Can you give me a pointer as to where it is? Is that its name on the website or is that it in short?
Forget that I found ''DRC83_base_defanged.zip''. Downloading it now.
Ok, I'm guessing I misunderstood something. I'm a "noob" so bear with me...
here's what I did.
I was running cm v 4.2.9.1 and decided to try and upgrade to the latest version. I wiped and reflashed and got 4.2.14.1 running, but I felt it was slow (the reason I didnt use any other new version), so I came here looking to see any new roms.
I decided KiNgxKxlicK AOSP 2.1 rom looked cool, so I downloaded it and flashed it (yes I wiped first). I'm guessing this is where it went wrong. The rom took 30 mins to finally boot to home (longest ever) but the sweet nexus screen made it easier to bear. I DID NOT do anything with an spl or any radio (that part still kinda confuses me to be honest). I'm guessing this is why I am in the predicament that I am.
The KiNgxKxlicK AOSP 2.1 rom loads fine, but was VERY slow. I decided I'd just go back to cm v 4.2.9.1. I went to wipe and reflash, but the G1 screen never disappeared. I let it load for about 30 minutes and decided that was a bit ridiculous before removing the battery (mind you, it never got past the T Mobile G1 screen). I was, however, able to reflash KiNgxKxlicK AOSP 2.1 rom and run it. This is all I am able to do. When trying to reflash cyonagen it just hangs on the G1 screen.
I'm a noob so I don't know what went wrong or what I missed.
Can someone PLEASE help me out here and tell me what I need to do to fix this. Thanks
Additional Notes:
Can't get to settings running KiNgxKxlicK AOSP 2.1 AT ALL, and a lot of programs Force Close on the rom.
Thanks for any help/input you guys can provide.
Thanks
Do you have Amon Ra recovery?
No I do not believe so, as I am not exactly sure what that is?
UPDATE: I should also note I checked my SPL and Radio, both were very old (as I realized I followed an OLD guide when I rooted my phone)
I upgraded to the latest radio and SPL and still have the same problem...except King's rom doesn't force close when I go to "settings".....thats about the only difference (still slow/laggy, lots of programs still FC)
When you boot into recovery (holding home+power) it should tell you what recovery image you are using. (i.e. mine says v1.5.2 down at the bottom of the screen) I ran into a similar issue when I attempted to jump between roms without taking all the appropriate steps; all I did was reformat my sd card, wipe the phone, and reflashed my rom and it worked great after that.
I tried reformatting my sd card, even re-partitioned it and I'm still having the same problems:
CM wont get past g1 screen after flash, King's rom still pretty slow....
What do you gys recommend I do next? This is getting really frustrating
1st: Check if youre Formatting is correct
2nd: Wipe EVERYTHING
3rd: Re-Format
4th: Try downloading the ROM again. It could be an issue with the ROM's
5th: Check you have proper radio and SPL (1.33.2005 and 26I)
6th: Pray
Try them all hope one of them works for you dude.
why is it that that 99% of newbs are on cyanogen
@Macrophage001
1. how do I CHECK my formatting to see if its correct?
2. Doesn't formatting do this automatically? I also "wiped" in recovery...
4. Not the roms, I have multiple CM roms, one of which I've had for some time with no problems and have re-flashed over and over
5. As stated above, I did not have the latest at first, i did upgrade to the latest radio and hakyuro(sp) spl to no avail.
@zachattack052
We've all been told it's THE BEST, much before even making the decision to root. I honestly thought CM was the only rom available, that's how much he's praised around here and other forums.....it's just what everyone tells us.
Here's what i suggest you do:
1> Download Amon_RA's recovery from here
here is a link to his thread
2> Transfer the file you just downloaded to the root of your sd
use this code to mount your sdcard from recovery console itself if needed
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
3>Disconnect usb and reboot to recovery (keep home pressed while powering on) or just type
reboot recovery if you are already in recovery console
4> Flash Amon's recovery:
Code:
#mount -a
#flash_image recovery /sdcard/recovery-RA-dream-v1.5.2.img
when complete, reboot to recovery again
5>Partion your sd using amon's recovery (All data on SD will be lost so backup if needed)
[Alt+P] then [Alt+0] or scroll down using the trackball or the volume keys
follow the prompts, set your swap-size to 96 MB (use the vol keys) and 512 MB ext2. when done use the back button to go back and reboot
The above step will give you the partitions required to run any rom. Please make sure you meet the radio and SPL requirements before flashing a rom.
6>Transfer the latest CyanogenMod rom to your SD and flash it.
I would suggest that you try bbuchacher's SuperD rom (it requires Haykuro's Danger SPL)
make sure you flash the radio first and then the SPL if you dont already have it
P.S. When anyone says full wipe, they mean doing a factory reset, wiping your ext partition and wiping the dalvik-cache. These are the first 3 options in Amon_RA's recovery's wipe menu
what i would do....
make sure you flash the HTC recovery files first before you flash the CM rom
go for the defanged version of HTC
so...(once u have amon ra's latest recovery installed)
wipe everything
flash htc / defanged (DO NOT REBOOT!!!)
flash cm latest rom
ALLOW IT TO LOAD FULLY
reboot (personal preference)
create a nandroid backup for future **** ups
enjoy ur rom!!
j.
airmcnair06 said:
@Macrophage001
1. how do I CHECK my formatting to see if its correct?
2. Doesn't formatting do this automatically? I also "wiped" in recovery...
4. Not the roms, I have multiple CM roms, one of which I've had for some time with no problems and have re-flashed over and over
5. As stated above, I did not have the latest at first, i did upgrade to the latest radio and hakyuro(sp) spl to no avail.
@zachattack052
We've all been told it's THE BEST, much before even making the decision to root. I honestly thought CM was the only rom available, that's how much he's praised around here and other forums.....it's just what everyone tells us.
Click to expand...
Click to collapse
1: Go to recovery console and type parted. A list will show up with your fat32,ext2/3/4,linux-swap settings.
2: Yes it does but you can never be too sure.
4: ok
thanx guys I followed the instructions MrBurrito and cqms13 gave and am now running the Super D rom just fine.
Thanks again!
very quick question..
did you wipe dalvik-cache?
Firerat said:
very quick question..
did you wipe dalvik-cache?
Click to expand...
Click to collapse
After installing the RA recovery, yes. I was running CM Recovery though when I began this thread, which is why I was not able to wipe dalvik
Hi,
I tried flashing the brand new CyanogenMod 5 with Eclair for G1, and I seem to be in "serious" trouble now.
Before flashing:
I had already installed DangerSPL for a few months with no issue
Had the latest radio
Was happily running SuperD1.9.3 with WG Kernel and JIT enabled
Made a Nandroid backup just in case I wished to go back
Wiped Dalvik-cache and Data/Cache to avoid boot loops
All of this with Cyan's Recovery 1.4.
After flashing the ROM and the Gapps, my phone restarted and got stuck on the G1 screen (no boot screen) for, maybe 15 to 30 minutes, which seemed a bit long for me... I finally decided to remove the battery, went back to recovery and made a Nand restore.
But after the restore, rebooting had the same effect : stuck on G1 screen.
I tried flashing several custom roms with no luck (all stuck on G1 screen).
I finally decided to flash the official ADP1.6 ROM from HTC (signed-dream_devphone_userdebug-ota-14721.zip) which installed fine (and updated the radio by the way), and it finally booted on stock Donut.
I tried then to reinstall custom roms but get stuck on G1 screen everytime I try... and flashing Amon_RA's recovery won't work (i keep booting on the stock recovery). But as a workaround, I can use fastboot to boot into Amon_Ra's recovery.
The questions now are :
did I lose root access, thus preventing from installing custom ROMs ?
if so, is it possible to downgrade while being under DangerSPL ? Won't it brick the phone ?
Is there anybody else who had the same problem with upgrading to Cyan's 5 ?
I really need to get custom roms back, stock sucks on G1... but there is no way i can afford bricking my phone.
Thanks for help guys!!
As long you can get to your custom recovery menu, you still have root access.
Keep the Danger SPL, not worth changing it and the Danger SPL has fastboot also.
It takes a while to boot into a newly flashed ROM so just wait 5-15 min.
Do these steps:
1)Do a FULL WIPE of the phone (data, dalvik-cache, ext, battery stats, and rotation ****You won't have some of these options with Cyanogen's recovery. Just wipe what you can****)
2)Repair the ext partition
3)Flash CyanogenMod 5.0.7-DS-Test 1 (this is the g1/mt3g version)
4)Without wiping or rebooting, flash the gapps .zip file
5)Reboot and set up the ROM
6)Flash the latest Amon_RA recovery for your device. Cyanogen uses Amon-RA's recovery now.
1. Upgrade your recovery....cyanogen stopped working on his a while ago, upgrade to Amon_RA's recovery.
2. You only have to wipe data/dalvik, and maybe sd-ext. you do NOT have to wipe battery stats or rotation EVER.
3. Flash CM Rom
4. Flash gapps
Unfortunately, exact same thing.
Stuck on G1 screen.
Reverted back again to adp 1.6
Any other suggestions ?
alou2 said:
Unfortunately, exact same thing.
Stuck on G1 screen.
Reverted back again to adp 1.6
Any other suggestions ?
Click to expand...
Click to collapse
Give us your spl (hboot) and radio. Go into fastboot and type exactly what you see.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA20000)
CPLD-4
RADIO-2.22.19.26I
Good ?
alou2 said:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA20000)
CPLD-4
RADIO-2.22.19.26I
Good ?
Click to expand...
Click to collapse
Try upgrading your radio? You shouldn't HAVE to, but it might work.
Are you on Amon_RA's recovery now?
I'll try upgrading radio, but it's weird I can't switch back to other custom donut builds...
I've used Amon-RA's recovery to wipe and install the ROM this time.
For some odd reason though, it seems i can't "install" Amon_RA recovery (it seems to switch back to stock recovery), but just boot it through fastboot...
alou2 said:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA20000)
CPLD-4
RADIO-2.22.19.26I
Good ?
Click to expand...
Click to collapse
make sure you're flashing the right recovery. dream still has two options. just like mytouch has H or G.
the one with "R" on the end of it is for rogers, one without it is for USA ones.
What files are you flashing? It sounds like you're flashing an old 1.6 base that has a recovery image included. Are you flashing the DRC83 Defanged as a base?
OK so I tried to take a fresh start on this.
I installed Amon_RA's 1.6.2 as recovery (not the Roger's one, I'm in France and the US tools always worked)
did a nandroid backup to stop reinstalling everything over again each time I want to make a phone call...
used it to repartition the SD (FAT / EXT2 / SWAP), thus formatting everything
wiped everything (except battery and orientation)
Flashed DRC83 Defranged
Without rebooting flashed CM5.0.7-t1
Without rebooting flashed Gapps
And it still gets stuck on the first boot screen (left it for about 20mn on it)...
Then I tried installing DRC83 defranged and it still gets stuck on the damned boot screen !!!
Through adb I can get to shell while on recovery, but the su command prints out :
/sbin/sh: su: not found
Is it normal ?
I can't find the /proc/last_kmsg file (just /proc/kmsg). Is there any log file that could help here ?
I'm going to nand back to stock 1.6, hoping it will start without having to flash the radio+recovery one again...
I noticed something weird when i nand back to my pre-CM5 WG-SuperD backup :
when it boots, it gets to the first boot screen and if USB is connected, i get a "fastboot usb" in a red box on top left of the screen.
To sum up :
phone's definitely not bricked, but won't run any custom rom anymore, but it still permits custom recovery installation/boot.
Something must have been broken/deleted somewhere.
Still asking the (dumb?) question : do I still have root, since su doesn't works (even using terminal server) ?
By the way, I really appreciate you guys taking time to read and answer my posts. Really
alou2 said:
OK so I tried to take a fresh start on this.
I installed Amon_RA's 1.6.2 as recovery (not the Roger's one, I'm in France and the US tools always worked)
did a nandroid backup to stop reinstalling everything over again each time I want to make a phone call...
used it to repartition the SD (FAT / EXT2 / SWAP), thus formatting everything
wiped everything (except battery and orientation)
Flashed DRC83 Defranged
Without rebooting flashed CM5.0.7-t1
Without rebooting flashed Gapps
And it still gets stuck on the first boot screen (left it for about 20mn on it)...
Then I tried installing DRC83 defranged and it still gets stuck on the damned boot screen !!!
Through adb I can get to shell while on recovery, but the su command prints out :
/sbin/sh: su: not found
Is it normal ?
I can't find the /proc/last_kmsg file (just /proc/kmsg). Is there any log file that could help here ?
I'm going to nand back to stock 1.6, hoping it will start without having to flash the radio+recovery one again...
I noticed something weird when i nand back to my pre-CM5 WG-SuperD backup :
when it boots, it gets to the first boot screen and if USB is connected, i get a "fastboot usb" in a red box on top left of the screen.
To sum up :
phone's definitely not bricked, but won't run any custom rom anymore, but it still permits custom recovery installation/boot.
Something must have been broken/deleted somewhere.
Still asking the (dumb?) question : do I still have root, since su doesn't works (even using terminal server) ?
By the way, I really appreciate you guys taking time to read and answer my posts. Really
Click to expand...
Click to collapse
I run into the same issue, I was upgrading from the latest cm 1.6 and after trying a few different things, after wiping with alt+w, I reinstalled danger-spl then installed the cm update, then the google apps; after doing this, it worked fine. BTW, it took about 15 mins to boot up though.
alou2 said:
OK so I tried to take a fresh start on this.
I installed Amon_RA's 1.6.2 as recovery (not the Roger's one, I'm in France and the US tools always worked)
did a nandroid backup to stop reinstalling everything over again each time I want to make a phone call...
used it to repartition the SD (FAT / EXT2 / SWAP), thus formatting everything
wiped everything (except battery and orientation)
Flashed DRC83 Defranged
Without rebooting flashed CM5.0.7-t1
Without rebooting flashed Gapps
Click to expand...
Click to collapse
There is your problem. DO NOT FLASH THE DRC83 BASE!!!
Just repartition your sdcard (if you want to), upgrade to ext3 or ext4, then follow the last 2 steps.
Hi UberMario,
I just reinstalled DangerSPL using Amon_ra's recovery, and then directly flashed CM5 + Gapps (no reboot inbetween).
It's been stuck on the 1st splash screen for 30 minutes now...
I'm letting it for another 30mn (although I think it's useless) and will eventually revert back to stock 1.6... again...
I just don't get what's wrong...
I'm going to try redownloading the archives in case they would've been corrupted, but being unable to install anything else than an official htc firmware seems like a symptom to me... isn't it ?
alou2 said:
Hi UberMario,
I just reinstalled DangerSPL using Amon_ra's recovery, and then directly flashed CM5 + Gapps (no reboot inbetween).
It's been stuck on the 1st splash screen for 30 minutes now...
I'm letting it for another 30mn (although I think it's useless) and will eventually revert back to stock 1.6... again...
I just don't get what's wrong...
I'm going to try redownloading the archives in case they would've been corrupted, but being unable to install anything else than an official htc firmware seems like a symptom to me... isn't it ?
Click to expand...
Click to collapse
I'm not sure if this will make a difference, but flash Gapps first then flash CM5 then reboot and everything should work...
or
You might want to check and make sure your MD5 is correct too..
why would you flash gapps first? you have to flash it on top of cm5.
Yeah... quite sure this won't help.
What could prevent the phone from booting custom firmwares but still allowing to install them ? (and finally I can still run the su command through adb, and get root access, but apps can't get root...)
tehseano said:
why would you flash gapps first? you have to flash it on top of cm5.
Click to expand...
Click to collapse
I rooted my G1 for the first time. I flashed CM 5.0.7 then GApps (no reboot in between). When the phone booted, none of the Google Apps were on the phone. Went back to recovery and did a wipe and flashed GApps then CM (no reboot) and everything installed correctly. Someone said to flash CM first then GApps, but that didn't work for me. Weird.
I've installed Amon Ra on my Nexus One as part of the process to get cyanogen running on it. I did the fastboot oem unlock + flash amon ra + manual update zip process.
Part of the reason was that for some reason I could never boot into clockwork recovery (yes I followed the wiki to the letter), and could only access the standard recovery (which doesn't allow custom roms, says the signature is invalid), the one in blue font. So I flashed amon ra instead and that worked fine.
Can I now flash back to clockwork, and even better, just do it via rom manager? Is there any risk or downside?
This is because I'm reading that amon ra doesn't have a wipe option, and that its better to wipe when you upgrade roms (or is that another fallacy or am I mis interpreting things)
cheers
1. If you didn't find and delete recovery-item-boot.p and install-recovery.sh, they will restore stock recovery when boot, regardless of what custom recovery you flashed.
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
Click to expand...
Click to collapse
2. You can change your recovery via ROM Manager, or manually. By the way, Amon RA Recovery has wipe option, of course. Where did you read that from?
LFact said:
1. If you didn't find and delete recovery-item-boot.p and install-recovery.sh, they will restore stock recovery when boot, regardless of what custom recovery you flashed.
2. You can change your recovery via ROM Manager, or manually. By the way, Amon RA Recovery has wipe option, of course. Where did you read that from?
Click to expand...
Click to collapse
1.) I'm pretty sure I'm booting into amon_ra, it has a nandroid backup option.
My attempt (fail) to install clockwork was exactly the same as how I successfully installed amon: via fastboot flash recovery /path/to/recovery-RA-nexus-v2.1.1-CM.img after unlocking the bootloader. I didn't manually find and delete those files you specified (wouldn't even know how TBH), just followed the Cyanogen wiki.
2.) Cool good to know. I suppose then there's no point in changing really. I was just reading posts and saw it referenced several times. Maybe they were out of date or early on in the piece.
Out of curiosity, is it worth wiping if you're just upgrading between the same version e.g. cyanogen 7.03 to future 7.04?
I much prefer Amon 2.2.1 It is 2.2.1 which is the latest version, not 2.1.1
Stay away from CW 3.+
Amon has a Data/Factory reset wipe for installing new roms, I wipe 5X with it. And, a Dalvik Cache and Cache options. Do those 5X also
If doing nightlies, just wipe the caches
Here is a link to a System Wipe zip you can flash from recovery. That is probably what they were taliking about. CW has that option and Amon will on the next version, I think.
http://forum.xda-developers.com/showthread.php?t=723844&page=1767
Ken
PS:
Otherwise, like mentioned you will default back to CW even if you flashed 2.2.1 thru Rom Manager on reboot.
Or, you can flash Amon thru fastboot and remove the two scripts mentioned above by LFact
Thanks mate I'll just keep using Amon
So you're saying to wipe I have to flash that zip, there's no way of just wiping it from the menu options before flashing the relevant ROM?
But in any event since I'm on CM7 I'll only be doing minor version bumps for the foreseeable future lol
I"m confused about the reboot issue: I can reboot into Amon at any stage. I haven't deleted those scripts. But you guys are telling me that unless I delete those scripts if I reboot I'll go back to stock recovery?
Sorry wrong thread.
Sent from my PC36100 using Tapatalk
@wintermute000
Yes, flash the system wipe zip from recovery like any zip. Only a few seconds. Hopefully , it will be in next Amon version.
Never an issue with Amon--
Get Quick System from market and use it to boot into recovery--exc app
Then you don't need Rom Mgr or CW--better that way
If you install Amon thru Fastboot or Terminal, it will not be erased on reboots--you still need to delete the two scripts mentioned before any rebooting
See post three on this link--DR has a flash able zip to do it--nandroid always first on this stuff
http://www.nexusoneforum.net/forum/...330-custom-recovery-wont-stick.html#post99962
wintermute000 said:
Thanks mate I'll just keep using Amon
I"m confused about the reboot issue: I can reboot into Amon at any stage. I haven't deleted those scripts. But you guys are telling me that unless I delete those scripts if I reboot I'll go back to stock recovery?
Click to expand...
Click to collapse
If you type
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
Click to expand...
Click to collapse
in terminal and it shows error message such as 'no file or directory', it means they were already removed. (I think ROM manager automatically remove them when flashing Clockwork recovery. When I changed to RA recovery, I found out those 2 files were gone)
If you're still curious about changing recovery, you can. I accomplished this yesterday by using Amon to flash a ROM with root access, then I downloaded CwM from the market. Installed the recovery using CwM. It's a simple process as long as you have root. As for going back to Amon, I haven't tried that.
Those files are gone (I didn't do rm, I just did basic ls in those directories). So I guess somehow during my Amon flashing it deleted it. Good to know.
Thanks for your patience all, I think I'll just stick to Amon then if I can just as easily wipe using a zip file if I need to. From what I've read I won't need to wipe anyway if I'm upgrading minor versions (i.e. CM7.03 to say 7.04 or nightly) and that's all I'm interested in doing. Hopefully by the time CM8 comes around I'll have taken the plunge on something dual core!!!
The whole reason I started investigating root/flash etc. was to give my N1 more legs until the price/performance point for the dual core phones gets to a better state, and its more than done that, I'm kicking myself for not doing it earlier. I guess once you're familiar with it then its a piece of cake, but I was reluctant for ages as I didn't want to screw up my PHONE (as opposed to say a tablet).
You don't need to remove those files since after you loaded Amon_RA, you installed CyanogenMod. Those files are used in Stock Android to replace whatever recovery you may have with the stock recovery on every boot.
I would still download the flashable zip that rugmankc linked to for formatting /system. Like I said in the CM forums, it normally isn't necessary when upgrading from minor versions, but sometimes it is the only thing you can do to fix a phone. I figure it is better to download it and never use it, then need it and having a hard time finding it.
+1 bass
@wintermute000,
I still wipe Dalvik Cache and Cache between nightlies. Seemed like the time or two I didn't do it, I had an issue.
The deal on using System Wipe if flashing new rom or if a lot of versions in between is:
When you flash a new rom it wipes system, but backs up some files from old rom first and reinstalls them as part of the new rom. After while things get cluttered, so a system wipe prolongs more serious issues. It has reduced the amount of times I need to do a complete wipe and/or sd card redos.
All Props to Temasek on this stuff
Ken