I just spent many grueling hours updating my stock, Android 1.5, Pre Rogers Radio update, Rogers Dream EBI1 to CyanogenMod.
After fimalising the last step in the Cyanogen guide, the phone loops the X logo from CyanogenMod. It says it takes up to 15 minutes to boot the first time... This has looped for more than15 minutes. (Using AmonRA recovery RA-dream-v1.7.0R)
Note I did nothing about partitioning my SD card as it was not mentioned in the CyanogenMod guide.
What did I do wrong? Should I nand Restore? Can I not Nandrestore someone else's working recovery?
Thank You
Miguel
solar_burn said:
I just spent many grueling hours updating my stock, Android 1.5, Pre Rogers Radio update, Rogers Dream EBI1 to CyanogenMod.
After fimalising the last step in the Cyanogen guide, the phone loops the X logo from CyanogenMod. It says it takes up to 15 minutes to boot the first time... This has looped for more than15 minutes. (Using AmonRA recovery RA-dream-v1.7.0R)
Note I did nothing about partitioning my SD card as it was not mentioned in the CyanogenMod guide.
What did I do wrong? Should I nand Restore? Can I not Nandrestore someone else's working recovery?
Thank You
Miguel
Click to expand...
Click to collapse
you probably don't have the 'required'* SPL
but a logcat will confirm
http://forum.xda-developers.com/showthread.php?t=668090
should help you out
please.. please be careful if you decide you need to flash 'danger', it can 'brick' your phone
I flashed the SPL in the Cyanogen guide which I assume is the danger SPL.
I found a guide on the cyanogen forum with the sane problem I had. I am currently in the midst of trying their solution.
This is what they say to do:
Full Wipe
full repartition. Swap/Ext2/Fat32.
upgraded from ext2 to ext3.
upgraded from ext3 to ext4.
shut down the phone.
I removed the SD card and put the zip files back on from my computer.
Put the SD card back in the G1 and booted into recovery.
flashed the CM5.0.8 update,
flashed the GApps file.
Then rebooted.
I will post my findings!
Thanks for the reply!
Didn't seem to work, I'm hanging at the Rogers Logo now.
PS I am using the SPL 1.33.2005...
Radio 3.22.20.17
Amon Recovery 1.70R
Pre Radio 911 Fix
Should I try using the Hard SPL? Different Recovery?
solar_burn said:
Didn't seem to work, I'm hanging at the Rogers Logo now.
PS I am using the SPL 1.33.2005...
Should I try using the Hard SPL?
Click to expand...
Click to collapse
no, that spl should be fine
I notice in your list that you did not flash an edi1 boot.img
cyanogen said:
Magic 32A/EBI1 Kernel Update:
Download: http://briancrook.ca/android/cm-ports/bc-5.0.8-ebi1-signed.zip
MD5Sum: a90a1350d14e2f0bfd2c5f673d230649
Click to expand...
Click to collapse
NB ^^ latest at time of typing, click the > in the quote to see the current
Mod. comment: I will delete your duplicate thread in rom dev
I did it in the first guide... the supplementary fix did not say to do so...
I will try fix again, finishing with the edi1 boot.img..
All i need to do to copy the file to the SD card and flash it within the Amon Recovery right?
IT WORKED!! thanks buddy!!!!
=D
Miguel
Related
Ok so I followed cyanogenmods wiki page on how to root and flash his rom to my MT3G(with the exception that after i flashed the DRC83 base zip file the phone rebooted automatically so I went into recovery mode as soon as it happend and flashed cyanogens build) and the phone booted up fine. the little android skater and everything. everything was running smooth(NOTE I DID NOT DO THE 10MB hack) but i tried setting up wi-fi and the phone just restarted. i thought it was probably the first time boot thing people talk about. but then the phone randomly turns off and on while doing diffrent things(such as download apps from market ... texting a message) so i tried flashing another ROM and same thing is happening(dwangs super d rom). is there a reason for this. the guide didnt mention having to change any SPL's or radio's or anything but I keep seeing this around the forum that it has to be changed. is there a guide on how to do that and if so why doesnt CyanogenMods own wiki not mention it?
do u have 32a or 32b?
the 32b. i have the original mytouch 3g
vampsandbats said:
the 32b. i have the original mytouch 3g
Click to expand...
Click to collapse
(im assuming you downgraded to 1.5 using sappimg.nbh from hboot mode, then rebooted and installed flash_rec, backed up image, and then flashed amon ra's recovery image correct?)
so if you did all of that,
do a wipe and then flash DRC83, after that reboot phone and check to see if you are getting any uncommanded restarts. if you are not then reboot into recovery and flash your rom.
what rom are you exactly trying to flash?
My mytouch 3g also got constant reboots, regardless of whether I was actively using the phone or not. This happened with cyanogenmod and with another eclair ROM, but does NOT happen with Enomther's TheOfficial rom. I switched back to that and fixed the problem. I don't know what was causing it for me with the other roms, but it happened fairly consistently every 1-3 hours.
OK CAN SOMEONE PLEASE TELL ME IF IM DOING SOMETHING WRONG HERE ILL DO A STEP BY STEP
-COPY SAPPIMG FILE TO SDCARD
-HOLD DOWN VOLUME DOWN AND POWER AND PROCEED WITH UPDATE
-BACK TO STOCK 1.5
-DOWNLOAD APPMANAGER
-MOUNT SDCARD AND COPY FLASHREC 1.1.3 APK FILE AND recovery-RA-sapphire-v1.6.2G-green FILE(CARE BEAR FILE)
-ALLOW UNKNOWN SOURCES TO INSTALL
-INSTALL FLASHREC
-BACKUP FLASH
-TYPE /SDCARD/recovery-RA-sapphire-v1.6.2G-green.IMG
-REBOOT IN RECOVERY(PROBLEMS START. RECOVERY MODE RANDOMLY KEEPS REBOOTING.SOMETIMES AFTER ONLY A COUPLE OF SECONDS)
-OPEN BATTERY COVER AND AND TAKE OUT SDCARD AND PUT IT IN SD ADAPTER AND CONNECT TO MY MAC
-COPY THE ROM I WANT TO USE WHICH IN THIS CASE IS SUPERD193 WITH 10MB RAM HACK
-INSERT SD CARD BACK INTO PHONE AND MANAGE TO WIPE AND FLASH ZIP FILE.
-ROM LOADS UP AFTER AWHILE BUT SEEMS LAGGY
-OCCASIONLY WILL REBOOT FOR NO REASON BUT NOT TO MYTOUCH LOGO BUT RATHER ANDROID SPLASH LOGO WHICH IN THIS CASE IS SUPER D ANDROID WITH ELECTRICTY.
heres my log
followed instructions for root -forum.xda-developers.com/showthread.php?t=442480
wiped
instead of trying the 3 mentioned roms in the writeup I tried supereclair community. didnt work
reboot to recovery
reboot to recovery
etc...
seems like no OS on phone
flash cyanogen 4.2.15
says install from sdcard complete
wont boot. stops on TMOBILE G1 screen
datawipe and reboot
still wont boot past G1 screen
tried to flash dreaimg.nbh but says no zip file on sd
wipe and flash radio update needed by JF rom
reboot and flash jf rc33
boots. says 1.1 firmware but build rc33
have root
tried supereclair again. still fails
wiped and flashed hardspl
still stuck with JF recovery utility
wiped and flashed some donut 1.3 rom
instalation complete. reboot
took 5 minutes to boot but works
Click to expand...
Click to collapse
heres the error it gives me for supereclair
E:cant symlink /system/xbin/bb/[
E:failure at line 61: symlink/xbin/busybox SYSTEM:xbin/bb/[
Click to expand...
Click to collapse
What do I do now? How do I get other roms to work?
I'm still trying different roms. the reason I'm doing this is because I want apps2sd, swap, multitouch, and to overclock. I guess the newer themes are just a bonus
Thanks
which recovery img are you using?
used this during the root process
recovery-RA-dream-v1.5.2.img
Click to expand...
Click to collapse
but the JF rom installed its own 1.41 I believe
ed1380 said:
used this during the root process
but the JF rom installed its own 1.41 I believe
Click to expand...
Click to collapse
have you partition you sdcard? you need 512mb for ext, 96 for Linux swap and remaining for fat32. This will erase all your data on the sdcard! so make a back up before doing this. you can partition you card through the recovery for sdcard
using a freshly formattd 4gb card with only the data im flashing on there which is less that 100mb
so with the supereclair I need to partition the sdcard before applying the rom?
ed1380 said:
using a freshly formattd 4gb card with only the data im flashing on there which is less that 100mb
so with the supereclair I need to partition the sdcard before applying the rom?
Click to expand...
Click to collapse
majority of the roms here require partitioned card's unless stated in the OP
So how exactly do I do that? the new recovery utility doesnt have an option to partition. also what format do I partition to?
I'm guessing partition into 3.4gb , 500mb, 100mb
This is nothing to do with partitions.. although if you get Amon-RA's recovery back on there's a menu to do all that easily. JF's stuff for the dream is all ancient now.
Your problem is that Supereclair requires the DeathSPL, or enough knowledge to hack your way round the requirement. The only safe way to flash the deathspl is through fastboot.. do you know how to use that? There's a guide around here somewhere. Whatever you do, DONT FLASH THE DEATHSPL FROM RECOVERY.
ed1380 said:
So how exactly do I do that? the new recovery utility doesnt have an option to partition. also what format do I partition to?
I'm guessing partition into 3.4gb , 500mb, 100mb
Click to expand...
Click to collapse
try this http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/
do you have the danger SPL and the required radio? I'm guessing you don't have that.
http://forum.xda-developers.com/showthread.php?t=625886
that thread has all the info and links you need.
REMEMBER:
1) FLASH RADIO
2)FLASH SPL
If you don't follow that order that means you have a fancy paper weight.
goldenarmZ said:
This is nothing to do with partitions.. although if you get Amon-RA's recovery back on there's a menu to do all that easily. JF's stuff for the dream is all ancient now.
Your problem is that Supereclair requires the DeathSPL, or enough knowledge to hack your way round the requirement. The only safe way to flash the deathspl is through fastboot.. do you know how to use that? There's a guide around here somewhere. Whatever you do, DONT FLASH THE DEATHSPL FROM RECOVERY.
Click to expand...
Click to collapse
I gues it's not worth it then. Then how come cyanogen wouldnt boot. it flashed succesfully, but never got past the G1 screen
card partitioned. I just want a rom that can do the things I mentioned. currently running donut by laszlo
I have hardspl now
EDIT:installing danger/death spl now
wait a minute. you say not to install deathspl from recovery where as the guide says to do it
ed1380 said:
I gues it's not worth it then. Then how come cyanogen wouldnt boot. it flashed succesfully, but never got past the G1 screen
card partitioned. I just want a rom that can do the things I mentioned. currently running donut by laszlo
I have hardspl now
EDIT:installing danger/death spl now
wait a minute. you say not to install deathspl from recovery where as the guide says to do it
Click to expand...
Click to collapse
Yes, but recently it has been found that the safest way (and least likely to brick) is through the spl (fastboot).... these guides were written before this was discovered
Since I cant find a rom I like 100% can I get a rom I like and then add app2sd, multitouch, swap, etc to it?
Also I can flash all the roms I want and not worry about a new spl or recovery being loaded. right?
I had Leak 2.1v3 on my phone, and following the XDA thread, I've successfully rooted my Eris using the stock 8gb card. Twice. I re did the root thinking I corrupted the RUU file, or something else during the initial root. I have Amon recovery installed and accessible at will.
I have full access to my phone with adb shell with SU access, but I'm unable to boot into any custom rom. So far I've tried Evil Eris 3.0 and Aloysius. They install without errors, but on reboot the phone to access the rom, the phone will freeze or loop. I've tried waiting over 20 minutes with the HTC boot screen flashing about every 15 seconds after installing Aloysius.
I'm still showing hboot 1.49.0000 S-ON. Is this what is stopping me from booting a custom rom? Or am I missing something that will change the security status to off?
Suggestions? What am I missing?
Thanks
Ok, looks like I got somewhere, I managed to install the grdlock beta rom. Not sure why the other roms wouldn't install tho. They all came from the same source. hboot is still 1.49.0000 S-ON tho.
NAA_Silent said:
Ok, looks like I got somewhere, I managed to install the grdlock beta rom. Not sure why the other roms wouldn't install tho. They all came from the same source. hboot is still 1.49.0000 S-ON tho.
Click to expand...
Click to collapse
The new rooting method ("Incredible/Slide") does not currently replace the S-ON bootloader, so phones rooted this way will not have 1.49.2000 S-OFF on them.
As for your troubles, you need to Wipe /data (FR) in Amon_RA recovery before you install a new ROM. Amon_RA does not enforce wiping of the /system and /data partitions before a new rom is loaded from the SD card, so you probably ended up with a mixture of old ROM and new ROM in a couple of places. (The dev can pre-clean those partitions in the update-script, but I'm not sure if that happens for the ROMs you mentioned.)
Always a good idea to wipe before a new ROM install (not necessary for a Nandroid restore, though, because it does a wipe itself).
bftb0
I thought I'd wiped those caches within Amon recovery. Good to know that I'm not going insane with the 1.49 S-ON tho! I couldn't find anything anywhere to let me know the S-ON was normal. After I get everything up and running with the grdlock rom, I'll back it up and try one of the other roms, being darn sure to wipe everything Amons will let me wipe first. Thanks for the info!
It appears that the rom files that I was using were corrupt. Without the md5 info for those files I had no way of checking. I went to a different site and downloaded Aloysius 12, and it's up and running just fine now
Thanks for the nudges in the right direction!
I checked through 100s of post tonight and could not find the answer to this and am in need of some help. I attempted to install a Cyanogen Nightly tonight through Rom Manager with no prior knowlege of the issues with CW 2.5 vs. CW 3.0. Stupid I know.
So natuaraly, when the download finished and Rom Manager tried to install, my MT4G just hung at the white boot screen. Through previous posts, the directions were simple to reflash the previous CW Recovery through Fastboot and reflash the Rom.
Well thats where the problem is.... When I attempt to flash ANY Rom earlier than 3.0.0.5, it will say OKAY in CMD, however the phone will never boot into the Recovery. I even tried fastboot erase recovery then reinstalled and still nothing.
So i decided to go a different root and reinstalled 3.0.0.5 to see if there was any work around through there. After i install 3.0 through Fastboot, I am able to go into Recovery, however when I select ANY option no matter what, the hat and the gear icon stay in the background and nothing happens.
I am very confused and lost and am hoping someone here will have had the same issue and can help me get my phone back in order.
Thanks in advance guys!
highrolla1866 said:
I checked through 100s of post tonight and could not find the answer to this and am in need of some help. I attempted to install a Cyanogen Nightly tonight through Rom Manager with no prior knowlege of the issues with CW 2.5 vs. CW 3.0. Stupid I know.
So natuaraly, when the download finished and Rom Manager tried to install, my MT4G just hung at the white boot screen. Through previous posts, the directions were simple to reflash the previous CW Recovery through Fastboot and reflash the Rom.
Well thats where the problem is.... When I attempt to flash ANY Rom earlier than 3.0.0.5, it will say OKAY in CMD, however the phone will never boot into the Recovery. I even tried fastboot erase recovery then reinstalled and still nothing.
So i decided to go a different root and reinstalled 3.0.0.5 to see if there was any work around through there. After i install 3.0 through Fastboot, I am able to go into Recovery, however when I select ANY option no matter what, the hat and the gear icon stay in the background and nothing happens.
I am very confused and lost and am hoping someone here will have had the same issue and can help me get my phone back in order.
Thanks in advance guys!
Click to expand...
Click to collapse
I havent had that issue exactly, but I might be able to help wlk you through getting this fixed. Ive had problems more than once myself on recovery, and helped a couple others solve other issues on here. If you want, add me on google talk (same username as on xda), and Ill walk you through it. Might have to wait till the morning, though, as Im probably gonna head to bed soon.
Fastboot 2.5 recovery and reflash froyo rom. If you decide to install CM7 again - read,search and make sure that you understand what you're doing. It has been stated at least few dozen times that Rom Manager is useless with gingerbread until Koush updates it.
Same Issue??
I believe my issue sounds similar.
I tried to go from Iced Glacier up to CM7. When I did I attempted to use the Clockwork Recovery 2.5 and of course it didn't work. Then I tried to upgrade it to 3.0.0.5. Now when I try to reboot into Clockwork recovery the phone just stays on the MyTouch 4G splash screen. The only way to get around it is use the Power/Volume down button and click on FASTBOOT and then select REBOOT.
The phone then boots in Iced Glacier. I have redownloaded ROM Manager and attempted to FLASH CLOCKWORKMOD RECOVERY. But it still won't load into recovery.
Essentially I need some step by step help to get back to clockworkmod recovery. I'm not too worried if I need to wipe everything. Just looking for the ability to restore again.
Alternatively I'm interested in upgrading to CM7 but not sure how I could do that without recovery working. I would also ask if you can give step by step instructions it would be much appreciated as I'm still pretty new to this.
Thanks!
I also have the similar problem. I have installed the Clockworkmod 3.0.0.5 and have rooted my phone before i was trying to install the gingerbread version. I made a recovery backup. i tried to restore the phone with that backup image but it still hung up with that "t-mobile mytouch " white splash screen.
What should i do now ? i have no idea how to bring my phone back to life :/
fosunite said:
I also have the similar problem. I have installed the Clockworkmod 3.0.0.5 and have rooted my phone before i was trying to install the gingerbread version. I made a recovery backup. i tried to restore the phone with that backup image but it still hung up with that "t-mobile mytouch " white splash screen.
What should i do now ? i have no idea how to bring my phone back to life :/
Click to expand...
Click to collapse
Jmg90300zx said:
I believe my issue sounds similar.
I tried to go from Iced Glacier up to CM7. When I did I attempted to use the Clockwork Recovery 2.5 and of course it didn't work. Then I tried to upgrade it to 3.0.0.5. Now when I try to reboot into Clockwork recovery the phone just stays on the MyTouch 4G splash screen. The only way to get around it is use the Power/Volume down button and click on FASTBOOT and then select REBOOT.
The phone then boots in Iced Glacier. I have redownloaded ROM Manager and attempted to FLASH CLOCKWORKMOD RECOVERY. But it still won't load into recovery.
Essentially I need some step by step help to get back to clockworkmod recovery. I'm not too worried if I need to wipe everything. Just looking for the ability to restore again.
Alternatively I'm interested in upgrading to CM7 but not sure how I could do that without recovery working. I would also ask if you can give step by step instructions it would be much appreciated as I'm still pretty new to this.
Thanks!
Click to expand...
Click to collapse
Sounds like both of you should of never of done this. This has been discussed a few times, and the end result is always the same.....
Download the correct Recovery image (which can be found in the Development section) and install it to your phone by using the ADB commands, in the fastboot mode. you can find a quick and painless way to set those up in my signature. Once you have installed the recovery image you can boot into hBoot and select recovery. from there you can flash CM7 and the gapps. Once you have done all that download the official clockwork ROM manager from the market and flash his current recovery image.
everytime I've tried to install Sense ROM(almost all new Sense ROM) on NAND its always bootloop or stuck on the android boot splash screen.
Have tried changing SD, task29, etc. but no luck with it.
does anyone have this problem?
I'm running Magldr 1.13, CWR 5.0.2.6 radio 2.15.50.14.
And this problem ONLY happen on Sense ROM, have tried others and all are working fine.
I'm not a dev or programer,so don't know much bout this.hopefully someone could help.thanks
[SOLVED]
Have tried most of the ROM install instruction (flash install task29) but with no success, then something old came across my mind, should try the old way, so I flashed WinMo stock ROM then install Magldr 1.13 directly and just follow with the instruction and its a success.
I think the ROM dev should put a Most recomended instruction with flashing stock ROM.thanks for the help to all
which Sense ROM you were using?
shankar10 said:
which Sense ROM you were using?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1316632
http://forum.xda-developers.com/showthread.php?t=1326217
http://forum.xda-developers.com/showthread.php?t=733649
okay, are you following the guide exactly as it says? I'm assuming you have a European model HTC right? You need to create Ext on SD card.
I've tried all of these ROMs and I never had any boot loops. Make sure you do partition as it says on each ROM.
So for example on the first ROM you need to create 5/220/5 if not it will do BOOT LOOP
shankar10 said:
okay, are you following the guide exactly as it says? I'm assuming you have a European model HTC right? You need to create Ext on SD card.
I've tried all of these ROMs and I never had any boot loops. Make sure you do partition as it says on each ROM.
So for example on the first ROM you need to create 5/220/5 if not it will do BOOT LOOP
Click to expand...
Click to collapse
I'm guessing, I did follow all of the guide and yup,got an EU here