Related
Hello,
I own an HTC Desire Z (Europe), have root, and recently managed to get S-OFF with gfree 0.02 (at least that's what it says when I'm in the bootloader)
I downloaded ROM Manager, made the mandatory back-up, and thought I'd try out a custom ROM, see what all the fuss is about.
I got the .zip file, placed it in the root of my SD-card (still zipped ofcourse), installed it, but it got stuck and was constantly looping the CyanogenMod animation from the beginning..
Sooo I restored, relieved but also dissapointed..
Any idea as to what the problem was / what I can do about it?
Please keep in mind that I'm quite the n00b, thanks!
Bronz_Most said:
Hello,
I own an HTC Desire Z (Europe), have root, and recently managed to get S-OFF with gfree 0.02 (at least that's what it says when I'm in the bootloader)
I downloaded ROM Manager, made the mandatory back-up, and thought I'd try out a custom ROM, see what all the fuss is about.
I got the .zip file, placed it in the root of my SD-card (still zipped ofcourse), installed it, but it got stuck and was constantly looping the CyanogenMod animation from the beginning..
Sooo I restored, relieved but also dissapointed..
Any idea as to what the problem was / what I can do about it?
Please keep in mind that I'm quite the n00b, thanks!
Click to expand...
Click to collapse
How long have you kept it running?
Did you install it from ROM Manager ? Did you wipe the phone from there before flashing ?
No, I got it from the CM website, under stable Mods. I did not wipe the phone.
Bronz_Most said:
No, I got it from the CM website, under stable Mods. I did not wipe the phone.
Click to expand...
Click to collapse
That's your problem. You ALWAYS wipe when going to a new ROM, and since you're going to CyanogenMod, don't forget to flash the GAPPS .zip file.
Oh okay, thanks!
And I would flash this GAPPS file in the same way I flashed CM?
Bronz_Most said:
Oh okay, thanks!
And I would flash this GAPPS file in the same way I flashed CM?
Click to expand...
Click to collapse
1) Root. The "rage" method is recommended.
2) Wipe.
3) Flash Cyanogenmod.
4) Flash Gapps (yes, the same way).
5) OPTIONAL: Flash a theme.
6) Enjoy root.
I just installed cyanogen 6.1.1 for my first time on my phone everything went correctly and then when it went to boot up its stuck at the boot screen. What do I do???
Someone plzzz help idk what to do???
Sinistah_ said:
I just installed cyanogen 6.1.1 for my first time on my phone everything went correctly and then when it went to boot up its stuck at the boot screen. What do I do???
Click to expand...
Click to collapse
Sinistah_ said:
So I just installed cyanogen 6.1.1. And its stuck at the boot up screen... what do I do????
Click to expand...
Click to collapse
Please do not start new threads when people are trying to help you. Wait patiently for an answer before starting a new one. You have started 4 threads already about rooting your phone and the problems you have. Invest some time in reading, learning and understanding the wikis. Thank you.
Sorry. I'm just paniking for the fact my phone is stuck on the boot screen and I'm jusst trying to get help asap. And actually the other thread was about if my phone was rooted so this thread is on another topic.
Are you still able to boot into recovery? And if so, what is displayed in your screen?
So I took the battery out, put it back in.. held power and the volume button it took me to where it says s-off n did a system recover. It worked!!! Haha... now I wanna try again but can u tell me what I did wrong??? I downloaded the cyanogen 6.1.1 and just started it up with the google stuff. It rebooted did its thing n stayed at the boot screen... am I supposed to clear something?? I read somethin like that when I was on google with my gfs phone. (I'm out somewhere... made me panik more since I don't have access to a computer atm)
Sent from my T-Mobile G2 using XDA App
Which version of ClockworkMod are you using?
Since you trie to flash a CM6.1. rom (which is froyo, android 2.2 based) you must use a ClockworkMod 2.5.x or below (or compatible).
And did you install Engineering HBoot? Sorry for asking, but it's unclear to me what you exactly have been doing already.
I did the visionary/gfree root last night without the hboot. And I tried the cyanogen 6.1.1 which was suggested by another user on here in one of my threads.
Sent from my T-Mobile G2 using XDA App
Btw my clockworkmod says 3.0.0.5
Whatever version that was on the market is the one I downloaded.
Sent from my T-Mobile G2 using XDA App
Apart from the fact that it seems to me that you skipped a step (hboot), which you have to perform , you are also trying to flash a 2.2 rom with the wrong recovery. Try with the 2.5 version in the thread http://forum.xda-developers.com/showthread.php?t=898151
HLeenders said:
Apart from the fact that it seems to me that you skipped a step (hboot), which you have to perform , you are also trying to flash a 2.2 rom with the wrong recovery. Try with the 2.5 version in the thread http://forum.xda-developers.com/showthread.php?t=898151
Click to expand...
Click to collapse
First of all, flashing the engineering HBOOT is not required unless you want to use fastboot on your computer. Also, if you used ROM Manager to flash ClockworkMod Recovery, that version is supposed to support both 2.2 and 2.3 ROMs. It was only the beta version of the recovery that was on this forum that only supported 2.3 and not 2.2---unfortunately, it was also labeled 3.0.0.5 and caused lots of confusion).
As far as why you are stuck at the boot screen, did you wipe data/cache when you flashed the ROM? Whenever you switch to a completely different ROM (as opposed to simply upgrading one), it's a good practice to. Also, the first time you start a new ROM, it'll take longer to boot up since the phone will be rebuilding its dalvik-cache (on CM6.1, it's be at a CM animation).
Ahh yeahhh okay good. So u cleared it all up for me n now my phone is running great
Sent from my HTC Vision using XDA App
After installing Cyanogenmod 9 on the One X I started to notice extremely poor signal, Mobile and Wi-Fi. Also the phone would crash and randomly reboot when doing simple tasks such as opening messages etc.
Upon trying to get into recovery to install a different rom, the phone now flashes on a black screen and restarts the phone.
To try and solve this issue, I unrooted the phone and restored to stock recovery.
I then re-rooted the phone and installed clockworkmod recovery again.
I can now access clockworkmod recovery although it seems to have no effect. Installations of any rom fail and cyanogenmod always pops straight back up again after rebooting.
Has anyone else had this issue?
Does anyone have a way to fix this? Possibly to force the phone completely back to stock?
You can try first "SuperWipe" (from ARHD's thread) and flash a new ROM (don't forget boot.img before...)
Kamiil29 said:
You can try first "SuperWipe" (from ARHD's thread) and flash a new ROM (don't forget boot.img before...)
Click to expand...
Click to collapse
Thanks for your quick reply, how do I do the super wipe? and where can I download the One X stock roms from?
AndyB said:
Thanks for your quick reply, how do I do the super wipe? and where can I download the One X stock roms from?
Click to expand...
Click to collapse
Unfortunately I can't help you with SuperWipe, but you can find the HOX stock ROMs here.
Sent from my HTC One X using Tapatalk 2
Ran superwipe and tried to install the stock rom. Superwipe ran fine and did the job, although the rom installation still failed as it was doing before and I am now stuck with a htc bootloop. The device won't boot into recovery either. Any ideas anyone?
AndyB said:
Ran superwipe and tried to install the stock rom. Superwipe ran fine and did the job, although the rom installation still failed as it was doing before and I am now stuck with a htc bootloop. The device won't boot into recovery either. Any ideas anyone?
Click to expand...
Click to collapse
Did you try holding down the Power and Volume Down buttons while in the bootloop to enter the bootloader? Hold them down until the lights start to flash, the screen goes off and then the bootloader comes up.
If you can get into recovery with that, factory reset, clear cache and dalvik cache (under advanced) then try install the ROM.
I'm not the best person to be helping, but I hope that works for you!
I had a similar problem once where the phone would just sit on the HTC One X screen, and trying to go into recovery just put the phone back to the HTC screen. I fixed it by flashing the boot.img, factory reseting, clearing out caches and installing the ROM again. No problems since.
I'm afraid if this doesn't work, I may have to abandon you and let someone else take over, as I'm no expert, but I'll see what I can do to help.
Edit: sorry, it is 2AM here and I need some rest for an early start at 6AM. I will check up on this thread when I wake.
Sent from my HTC One X using Tapatalk 2
FIXED!!!
To anyone else having this problem, I downloaded ARHD Flashboot 7.0.0 and ARHD 7.0.0, followed the instructions on what to do and installed ARHD successfully.
This has now completely gotten rid of Cyanogenmod and seems to have got clockworkmod working again.
It's probably work using the "Fix Permissions" option in ROM manager before you attempt this as I believe that is what got clockworkmod working and able to install files again. (I may be wrong)
Thankyou for everyone's assistance.
AndyB said:
To anyone else having this problem, I downloaded ARHD Flashboot 7.0.0 and ARHD 7.0.0, followed the instructions on what to do and installed ARHD successfully.
This has now completely gotten rid of Cyanogenmod and seems to have got clockworkmod working again.
It's probably work using the "Fix Permissions" option in ROM manager before you attempt this as I believe that is what got clockworkmod working and able to install files again. (I may be wrong)
Thankyou for everyone's assistance.
Click to expand...
Click to collapse
Glad you got if working
Sent from my HTC One X using Tapatalk 2
Hi All, let me start with a warning…
total Android n00b here, doing his first ROM flash on a newly rooted T-Mobile G2. I’ve read and searched a bit in the forum threads to see if I could solve this on my own, but I do need help.
VISION PVT SHIP S-OFF
HBOOT - 0.82.0000 (PC1010000)
MICROP - 0425
RADIO - 26.02.01.15_M2
eMMC - boot
Aug 20 2010, 16:51:01
This is from using the instructions in Strawmetal’s PDF guide to Downgrading from Gingerbread to Froyo and Root. I am working with a G2 phone that was set to Factory Reset before rooting, so there is no user data to backup or worry about.
1. I downloaded the Andromadus Mimicry 1.1.2 ROM image, and verified the md5 checksum on my sdcard using the AFV Legacy application. The Gapps image also was verified as well.
2. Using ROM Manager 5.0.0.8 from the Google Market, I ran Clockwork Recovery to install the Andromadus image. I left all settings on defaults and the installer ran fine.
3. When it restarted, I was left stuck at the white HTC screen for ages… the longest I left it was 20 mins. After that, I pulled the battery and restarted. Same white HTC screen.
4. I tried using Volume (+) key and Power On to get back to Clockwork Recovery, but the phone vibrated (buzzed) 3x times quickly, and the Power LED lamp pulsed an amber color. Again, yank battery, restart, same white HTC screen.
5. finally I decided to read more of the help for adb, and found the command “adb reboot-bootloader”. This let me get into the default Recovery mode, and it proceeded to find the PC10IMG.zip I still had on the sdcard from doing the Froyo downgrade. Recovery checked it out, ran it and restored the stock Froyo image and my phone did a proper restart. WHEW.
After that, I had to run adb to install the hboot recovery image file, and the busybox checksums were valid according to Strawmetal’s PDF instructions to get permanent root back after restoring the stock Froyo image.
I have done this process about 4 times, and am really good at typing inside adb now
But I’m lost…
-did I pick a ROM that doesn’t work with the G2? Other posters to the forum thread appear to be using the HTC Vision or G2.
-is ROM Manager not a good way to install a ROM?
-when I tried to get back into Recovery, what do the 3x buzzes/amber power LED mean?
-I never got to install the Gapps image; was I supposed to install that first, then the ROM image?
I imagine I did something wrong (duh!), but I can’t spot it. If someone can help me through this, I’d appreciate some advice very much.
thanks!
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Hi Nospin,
Thank you very much for your suggestions!
I will revise my root and remove Clockwork, and switch to 4EXT instead.
I appreciate the idea of "superwipe"; I will look for that as well today.
If I understand everything right...
-replace CWM with 4EXT
-place superwipe.zip, Gapps.zip and the Mimicry ROM.zip on the top level of the sdcard first.
-reboot the phone and run 4EXT recovery
-select superwipe to run first, then the ROM and then Gapps
-then restart the phone
When I used CWM before to install the ROM, it rebooted on its own before I could install Gapps. Will 4EXT let me do each install right after each other or do I have to return to 4EXT for each separate install?
regards,
motionmonk
Nospin said:
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Click to expand...
Click to collapse
Hi blk_jack,
I went back to the Mimicry page and re-read the FAQ section.
I think what I got out of it the first time was that if the ROM flash failed, it could be a corrupt ROM image. I will definitely use 4EXT to repartition before I try again with a ROM flash.
I guess I am still getting used to the terms for everything; can 4EXT do the nandroid backup? or is there a better process for setting that up?
thank you!
motionmonk
blk_jack said:
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Yes, you should be able to flash the rom and then GApps without rebooting. Give me a few and I will send you a PM with a few links....
Shot you a PM.
Thanks! I'll check it out :good:
Nospin said:
Shot you a PM.
Click to expand...
Click to collapse
Update-not working
Ok...
I re-flashed back to stock Froyo, and did a permanent root.
Installed 4ext Recovery (instead of Clockwork), and got a copy of SuperwipeG2+ext4;
I copied new checksum'd copies of Mimicry 1.1.2 ROM and GApps to my sdcard.
Booted into 4ext Recovery and installed from .zip the SuperwipeG2+ext4 file.
System, data and cache are all converted to ext4 partitions.
Wiped the system and data and cache partitions.
Installed from inside Recovery the Mimicry ROM and then the GApps archives.
No errors reported.
Upon reboot, I still get the white HTC screen. UGH.
I've left it on in that state for 30 mins... I had to yank the battery after that in shame...
I have tried to make sure that I read up on background steps, and I feel I do understand the overall process, but something is still getting in the way. I am doing this as I mentioned in an earlier post on a factory reset G2 with a clean erased SD card (has the stock Froyo image, Andromadus Mimicry ROM and GApps only). There is no SIM card installed either, wifi is off (to avoid OTA upgrade requests).
Are there other things I can try, or info I can supply that would help? I think I'm so close to getting this done... I must be overlooking something obvious.
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Hi amogil,
Just to be sure I understand, are you saying you are swapping between Andromadus and CM9 beta on your phone?
Did you flash CM9 first? and then Andromadus?
or just carrying the CM9 beta image and running Andromadus?
Sorry, I'm all sorts of confused here lol
thanks
amogil said:
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
It's definitely a thought, and I believe that's what amogil is telling me too...
Ya, I can try a different ROM and report back.
I guess I should go back to stock Froyo and then start from CM7.2, and if that boots, try Mimicry again?
-from the Andromadus FAQ, it says it if a different ROM is based on ICS9, you shouldn't have to wipe. But with CM7, I'd have to wipe the Dalvik cache, yes?
-since CM7 is obviously not based on ICS9, would being able to launch into that show some details I can't see at present? Just was curious.
Or, do you think it better to go stock Froyo and then the older Mimicry ROM?
Either way, I'll make sure that I use the Superwipe to set things to ext4 first.
thanks guys for the ideas,
motionmonk
Nospin said:
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
Click to expand...
Click to collapse
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
SUCCESS!
Woohoo!
It works!
Since I had an ICS9 ROM already in place and was planning to wipe back to stock anyways, I tried flashing the older Andromadus 1.1.0 ROM.
What a surprise and treat to see the startup animation!
After poking around for an hour inside it, I then tried Recovery to reflash to the newest 1.1.2 ROM.
YAY! It works!
OMG, having a new ROM is like having a new phone-- there are so many improvements to the UI and it's quick and speedy versus GB. Dang, I'm happy now :victory:
Observations:
1. I did notice that inside Recovery, my touchscreen was barely functional when I tried to update from 1.1.0 up to 1.1.2-- I had to use the Volume +/- and the d-pad button to make selections. After the flash, the touchscreen is as responsive as ever.
2. it's got me thinking, that there must be a setting that is expected in the v1.1.2 ROM that the v1.1.0 ROM installed. Or could something else be the issue? I mean absolutely no disrespect to the developers... but on the technical side, I'm just curious what possibilities exist that might lead to this situation.
3. backup question... when I use MyBackup Pro, I know I can make an archive of the apps I've installed, and an archive of the data (documents, music, settings). Is a nandroid backup different from that? when I see the backup/restore options inside of 4ext Recovery, what are those doing that's different from what I get from MyBackup Pro?
thanks for all the help and encouragement. I have a new ROM installed! :good:
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Oooh, a possibility. We will see if he can boot a different rom.
Whenever you switch roms (even if they are using the same Android version as a base) I suggest a full wipe. (Wipe all user data + Dalvik Cache + Cache, or just flash the superwipe zip). When upgrading the rom you are currently on (say upgrading CM Nightlies or going from Mimicry 1.1.1 to 1.1.2) you only need to really wipe cache and dalvik cache. Unless the dev states otherwise of course.
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Thank You All!
A big shout out to:
Nospin
blk_jack
amogil
strawmetal
for taking the time out to help a total n00b stumble through his first ROM flash.
I really appreciate the points you guys made, and the help provided.
Thank you!
I hope that one day I can help someone else out with a problem and pass the kindness forward.
Yay! I have a working ROM!
motionmonk
motionmonk said:
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
Click to expand...
Click to collapse
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
WOW. i just realized there is SO MUCH I need to catch up on!
I'll have to look up some of these guides later today... but the RUU is the ROM upgrade, right?
Did you ever find a reason why you got the false S-OFF flag? It's clear that the way I was looking at the failed fre3vo exploit as proof of S-OFF isn't always going to be true... but how would you separate a false S-OFF flag from lets say a wrong hboot image?
BTW, your PDF on downgrading and rooting the G2 was a godsend. Very very helpful and clear.
One of the reasons why I took so long to try rooting was that I was confused by the different methods and the replies of X not working, Y is a better way... going through your guide and the info here on xda cleared alot of things up. :good:
strawmetal said:
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
Click to expand...
Click to collapse
Hey guys, got a problem here.
Today i wanted to try out the cyangenmod 10.1. I currently was on the icecoldjelly 421 2.0. After flashing the boot img and installing the cyanogen rom, after the reboot the rom keeps hanging on the load screen!
Tried erase cache but nothing worked. Flashed the boot.img from the rom(installer).
So that didnt worked. Brought back my phone to stock with a RUU. Everything works fine.
So again after this i installed cyanogen again... still the same problem, it hangs in the loading screen...
I thought maby the rom is faulty, so i installed the newest version of icecoldjelly 2.1, flashed the boot from the rom..... also with this rom it hangs on the loading screen.
Im no restoring my backup because i dont know what to do?
Im on hboot 1.36
pervious version of icecoldjelly 2.0 worked just fine.
So guys do you know what the problem could be? Never had thisbefore
tarreltje said:
Hey guys, got a problem here.
Today i wanted to try out the cyangenmod 10.1. I currently was on the icecoldjelly 421 2.0. After flashing the boot img and installing the cyanogen rom, after the reboot the rom keeps hanging on the load screen!
Tried erase cache but nothing worked. Flashed the boot.img from the rom(installer).
So that didnt worked. Brought back my phone to stock with a RUU. Everything works fine.
So again after this i installed cyanogen again... still the same problem, it hangs in the loading screen...
I thought maby the rom is faulty, so i installed the newest version of icecoldjelly 2.1, flashed the boot from the rom..... also with this rom it hangs on the loading screen.
Im no restoring my backup because i dont know what to do?
Im on hboot 1.36
pervious version of icecoldjelly 2.0 worked just fine.
So guys do you know what the problem could be? Never had thisbefore
Click to expand...
Click to collapse
After putting back my backup i tryed to install icecoldjelly 2.1 instead of cyanogen first.
What ive read and think i was forgotten was the full wipe of data before installing the rom. I now did this after reading again on the ICJ forum, and now the rom is working fine!!
CM should work too after a full wipe.
TToivanen said:
CM should work too after a full wipe.
Click to expand...
Click to collapse
I will try that out tomorrow , im done for today :laugh:
Just tried the cM10.1 rom with a full wipe and it worked!
Ofcourse it works........when TT says it works .... It works