[Q] set_perm (status 7) error - Fascinate Q&A, Help & Troubleshooting

I am getting the following error when installing hellybean.
Finding update package...
Opening update package...
Installing update...
set_perm: some changes failed
E:Error in /sdcard/Hellybean-201
30205-fascinatemtd.zip
(status 7)
Installation aborted.
I have followed install instructions from here: http://forum.xda-developers.com/showthread.php?t=1238070
Installed hacksung ics 1 no problems. Go back into recovery, triple wipe, and try to install hellybean. It boots into devil touch recovery 6.0.2.7. and from here I get the same error above even after triple wipe, fix permissions, format /system, replaced sd card (started install all over again from stock), multiple downloads of hellybean, all of which is to no avail. Anyone have any other suggestions of how to fix??
sd card is 16 GB class 10.
I would post this under development for hellybean where other users have had similar issue but nobody has given a new response and I am not allowed to post in that thread because I'm a noob.

You should flash helly a total of 3 times if coming from ths-1
Sent from my SCH-I500 using xda premium

hhp_211 said:
You should flash helly a total of 3 times if coming from ths-1
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
The installation is aborted after the error so it doesn't matter how many times I try it I get the same result.

ulnevrwalkalone said:
The installation is aborted after the error so it doesn't matter how many times I try it I get the same result.
Click to expand...
Click to collapse
well just make sure you are following section 4 to the "T"
Step 3: Power off phone and pull battery.
Step 4: Open odin on your computer.
Step 5: Plug in factory usb cable and hold the volume down button. Yellow
triangle should appear saying "download mode".
Step 6: Click on PDA in odin and find the stock EH03 rom you downloaded to your computer in step 1.
Step 7: Click on PIT in Odin and select the atlas 2.2 pit you downloaded in step 1(make sure repartition is checked).
that is a combined step before proceeding
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 8: Click start and wait 5min, box in left hand corner of odin will say PASS, then click reset.
Step 9: Unplug usb cable, put battery back in and boot phone.
Step 10: Power off phone and pull battery.
Step 11: Plug-in the factory usb cable and hold the volume down key, get into "download mode".
Step 12: Open Odin, click PDA and select cwm4 fixed for cm7 you downloaded in step 1, hit start, should only take 10 sec, then say pass. Click reset.
Step 13: Close and open odin to reset connection. click on the PDA function and find the GB bootloaders.tar that you downloaded in step 1 and hit start.
Step 14: Unplug usb cable and insert battery.
Step 15: With three fingers hold the power, and both vol. up/down until you see the samsung logo appear the second time and let off. you should be in blue recovery 4.
Step 16: Wipe Data/Factory reset, then under the "advanced" menu wipe dalvik cache
Step 17: Use soft menu key on bottom left of phone and get back to main page in cwm. Find and select install zip from sd, then select chose zip and find the rom you pushed to your sd card in step 2. Select it and it will take you to a secondary menu, arrow down select yes.
Step 18: Once the rom finishes installing reboot.
You are currently now on ICS Team Hacksung build 1 or 2 . Continue following instructions below for upgrading to a custom ICS or JellyBean rom
Step 19: Download one of the roms below to the root of your sd card.
Step 20: Download latest GAPPS package to root of sd card
Step 21: Reboot recovery via the power menu.
Step 22: Wipe Data/Factory reset and Install .zip from sd that you downloaded in step 19. Then Install gapps zip from sd that you downloaded in step 20 and reboot.
I had to do step 22 --3 times --- 1st time gives you a warning,,, 2nd time appears to install but on reboot takes you back to new updated recovery menu,,, 3rd reflash zip one more time, reboot ,,, good to go
.

Update: tried to install CM 10.1 nightly with same result, tried installing from stock, then tried intalling from HSM-1 and both times got the same set_perm (status 7) error.
I also noticed that after failed installation attempts the sd card has bad sectors on it (from chkdsk). So I do a reformat and fresh copy of ROMS and still get back to same error. I am 95% sure its not an sd card issue because as I said before this is the second card I am using on this phone with the same result
HSM-1 installs from CWM 5.5.0.2 and as far as I can tell this is the only recovery that actually allows me to install a ROM on this phone. Does anyone have a link for a CWM 5.5.0.2 that I could flash from ODIN??

ulnevrwalkalone said:
Update: tried to install CM 10.1 nightly with same result, tried installing from stock, then tried intalling from HSM-1 and both times got the same set_perm (status 7) error.
I also noticed that after failed installation attempts the sd card has bad sectors on it (from chkdsk). So I do a reformat and fresh copy of ROMS and still get back to same error. I am 95% sure its not an sd card issue because as I said before this is the second card I am using on this phone with the same result
HSM-1 installs from CWM 5.5.0.2 and as far as I can tell this is the only recovery that actually allows me to install a ROM on this phone. Does anyone have a link for a CWM 5.5.0.2 that I could flash from ODIN??
Click to expand...
Click to collapse
what class is your sdcard? it's recommended to use a class 6+ sd card. this may be causing your error. but if recommend flashing back to stock and try ths b2.

hhp_211 said:
I had to do step 22 --3 times --- 1st time gives you a warning,,, 2nd time appears to install but on reboot takes you back to new updated recovery menu,,, 3rd reflash zip one more time, reboot ,,, good to go
.
Click to expand...
Click to collapse
When you say 2nd time it appears to install do you mean it actually takes a bit of time and shows a progress bar? Because after 2nd try it gets into recovery 6.0.2.7 and if I triple wipe from there I just get the same status 7 error.
ztotherad said:
what class is your sdcard? it's recommended to use a class 6+ sd card. this may be causing your error. but if recommend flashing back to stock and try ths b2.
Click to expand...
Click to collapse
its a class 10 16 gb card.

ulnevrwalkalone said:
When you say 2nd time it appears to install do you mean it actually takes a bit of time and shows a progress bar? Because after 2nd try it gets into recovery 6.0.2.7 and if I triple wipe from there I just get the same status 7 error.
its a class 10 16 gb card.
Click to expand...
Click to collapse
once you boot into recovery the second time, try not wiping and just install. see if that fixes it

ztotherad said:
once you boot into recovery the second time, try not wiping and just install. see if that fixes it
Click to expand...
Click to collapse
Another weekend of testing and still same result. I have managed to get aokp ICS on with devil kernal. Is jellybean significantly better than ICS, or put another way, is jellybean going to be worth the headache its causing?

ulnevrwalkalone said:
Another weekend of testing and still same result. I have managed to get aokp ICS on with devil kernal. Is jellybean significantly better than ICS, or put another way, is jellybean going to be worth the headache its causing?
Click to expand...
Click to collapse
i think jelly bean is a lot better than ICS, but when i got this fascinate ics was already out, so i didn't have to much problems with it. i do like the three button press to enter recovery.

ulnevrwalkalone said:
Another weekend of testing and still same result. I have managed to get aokp ICS on with devil kernal. Is jellybean significantly better than ICS, or put another way, is jellybean going to be worth the headache its causing?
Click to expand...
Click to collapse
which exact version / file of aokp ICS are you on now?
Like ztotherad said,, I also feel jellybean is a lot better than ICS and worth any effort needed to get up and running
.................
could you explain exactly which step you got to,,, It sounds like maybe you did not get the Team Hacksung build 1 or 2 installed from steps Step 17 and 18
that is a crucial part of the process..
I found for me to print out the instructions and physically cross off the steps as I went along (way back in the day) when I was having issues and sure enough I was missing part of a step I thought I was doing...
also don't try to do anything extra with clearing/rebooting/wiping that is not listed
or
either that or Step 6 and 7 were botched up,,, ,,,,or Step 13 missed, although quite a few are up and running with-out the GB bootloaders...
or
"" When you say 2nd time it appears to install do you mean it actually takes a bit of time and shows a progress bar? Because after 2nd try it gets into recovery 6.0.2.7 and if I triple wipe from there I just get the same status 7 error. ""
remember "also don't try to do anything extra with clearing/rebooting/wiping that is not listed"" IE: into recovery 6.0.2.7 and if I triple wipe from there ... dont do that
Just
do step 22 --3 times --- 1st time gives you a warning,,, 2nd time appears to install but on reboot takes you back to new updated recovery menu,,, 3rd reflash zip one more time, reboot ,,, good to go,,, ,,, back into recovery and then on to flash gapps
meaning once you boot into the new recovery,, you still need to flash the install 2 more times then reboot and wait
.

hhp_211 said:
"" When you say 2nd time it appears to install do you mean it actually takes a bit of time and shows a progress bar? Because after 2nd try it gets into recovery 6.0.2.7 and if I triple wipe from there I just get the same status 7 error. ""
remember "also don't try to do anything extra with clearing/rebooting/wiping that is not listed"" IE: into recovery 6.0.2.7 and if I triple wipe from there ... dont do that
Just
do step 22 --3 times --- 1st time gives you a warning,,, 2nd time appears to install but on reboot takes you back to new updated recovery menu,,, 3rd reflash zip one more time, reboot ,,, good to go,,, ,,, back into recovery and then on to flash gapps
meaning once you boot into the new recovery,, you still need to flash the install 2 more times then reboot and wait
.
Click to expand...
Click to collapse
OMG it worked !! I got fresh downloads and followed instructions and before I had tried it but everytime I would factory reset I would wipe cache (not davlik) literally only did factory reset and installed. First time got the warning, second time got my status 7 error and was worried. Went ahead and insalled rom again, it went through, installed again, reboot and I am now in CM 10.1.
THANKS!
Do you think I should mention to the OP of the instructions to make this more explicit because I have seen other users with my same issue...

Related

No Phone Service after loading MIUI

I went from stock Froyo 2.2 to MIUI v3 using the following link.
http://forum.xda-developers.com/showthread.php?t=992251
Now when I startup my phone...
For one, it won't connect me to a network so I can't get phone calls or texts etc.
Also my volume up button is switched with my volume down button.
Trying to make a phone call it says "Mobile network not available".
Does anyone have any information to help me fix this problem? I am stuck.
Yea flash the miui version made for the vibrant in our development section
http://forum.xda-developers.com/showthread.php?t=992302
The one you flashed is for the International galaxy S
bfranklin1986 said:
Yea flash the miui version made for the vibrant in our development section
http://forum.xda-developers.com/showthread.php?t=992302
The one you flashed is for the International galaxy S
Click to expand...
Click to collapse
Ok sooo...
I downloaded
kernel-cm-7-INITIAL-Vibrant-signed.zip
renamed it to update.zip
copied the update.zip along with the MIUI 1.5.20 english pack one to the root of my SD card (internal sd root)
Went into recovery mode, and tried to flash update.zip. It gave me some assert error right away. Now my phone is in a cycle of rebooting where it reboots into the flashing thing, tries to load real quick and then reboots itself.
Any tips? I'm kinda scared.
Odin back to stock and then try again, this guide by s15274n has all the files you need and step by step instructions.
http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
The vibrant files you flashed probably weren't compatible with the I900 kernel/recovery you had flashed.
GTASouthPark said:
Ok sooo...
I downloaded
kernel-cm-7-INITIAL-Vibrant-signed.zip
renamed it to update.zip
copied the update.zip along with the MIUI 1.5.20 english pack one to the root of my SD card (internal sd root)
Went into recovery mode, and tried to flash update.zip. It gave me some assert error right away. Now my phone is in a cycle of rebooting where it reboots into the flashing thing, tries to load real quick and then reboots itself.
Any tips? I'm kinda scared.
Click to expand...
Click to collapse
odin jfd, root, flash recovery then start over with the cm7 kernel then mui.
I'm having a problem following the guide...
Under 2 - Download 3 files..
Mount your phone and move the rom to the internal
AND the UPDATE.ZIP << DOWNLOAD
file if you wiped both internal/external or need to root.
Power down the phone, or pull the battery.
Click to expand...
Click to collapse
I don't know how I can get my phone mounted. Whenever I plug my phone into my computer (with the battery in), it automatically reboots itself and starts the crazy reboot thing. I also can't get back to recovery or downloading mode, it automatically goes back into the reboot thing.
And then in step 3 where it says start Odin, plug in your usb cable. With the battery out of your phone hold both volume buttons for a couple seconds and then plug in your USB cable. That doesn't take me to downloading mode.
EDIT:
Okay I figured out how to get it into downloading mode again. I need to do what it says above by holding the volume buttons with the battery out etc. Then you add the battery.
Hi guys. I got Odin to work. got back to stock.
Then got back into recovery mode to flash the cm7 kernel...
It is the same error as last time. Here's the actual error this time.
-- Installing: /sdcard/update.zip
Finding update package...
Opening update package...
Installing update...
assert failed: is_mounted("/mnt/sdcard")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
GTASouthPark said:
Hi guys. I got Odin to work. got back to stock.
Then got back into recovery mode to flash the cm7 kernel...
It is the same error as last time. Here's the actual error this time.
-- Installing: /sdcard/update.zip
Finding update package...
Opening update package...
Installing update...
assert failed: is_mounted("/mnt/sdcard")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Are you going under install zip from sdcard or just pressing reinstall packages? Instructions say to select reinstall packages after you rename it update.zip
bfranklin1986 said:
Are you going under install zip from sdcard or just pressing reinstall packages? Instructions say to select reinstall packages after you rename it update.zip
Click to expand...
Click to collapse
I boot into recovery mode. It takes me to the stock recovery mode. Then (with the update.zip and the miui zip in the root) I hit reinstall packages. It takes me to the clockwork recovery. Then I do install zip from sdcard. Trying to install the update.zip or the miui at this point gives me an error and then any kind of restarting will throw it into the reboot cycle.
EDIT:
When do I remove the battery? I do reinstall packages, and then after about a second or two it goes to the clockwork recovery, and then I removed the battery like it said. After I booted into recovery again and it took me to the clockwork recovery again, and then I tried to load the miui and again an error flashing.
EDIT 2:
For some reason Odin back to stock changed my phone to 2.1.. I upgraded it to version 2.2.1 (not using keis). I was able to get much further than normal when flashing the miui.zip.
My phone tries to startup, it gets to the Samsung loading image (which says i9000 under the samsung logo).
After that the screen goes (and stays) black. When I hit any of the buttons on the bottom, they glow white so I know that it is turned on.
I can't see anything on the screen, but I must be able to get it into downloading mode because I can get it to say 'added', and get try to start loading things, but then it starts never actually connets, it just hangs. Any ideas? Getting it back to stock right now would be fine so that it is usable again.
EDIT 3:
Ok, now I can see things again. For those who are wondering...
I had downloaded the 'Galaxy One Click Root' thing to try to root my phone before installing miui like it says. Well there's also a unroot button. I clicked that and I got it to go back into this custom recovery image. Once I did that, I navigated around a little and found something that said switch to Downloading mode. I did that, and then was able to use Odin to get back to stock. The screen is working, and so does the radio. It's back to 2.1 though. hmm..
ok so lets try this from the beginning
go ahead and odin to stock jfd (2.1)
now let phone boot as normal
no worries about letting it sit 10 mins or anything.
ok so you have the cm7 initial kernel as an update.zip correct?
3 button into recovery reinstall packages twice that should load you into clockwork
(orange clockwork menu)
1 Mounts and storage menu
Format system/cache/data (do all 3)
+Go Back+
wipe data/factory reset
Pull battery Or just press and hold all vol up + down + power
back in recovery.
install zip from sd Card
Install the Miui ROM reboot system.
lemme know how it goes.
boystuff said:
ok so lets try this from the beginning
go ahead and odin to stock jfd (2.1)
now let phone boot as normal
no worries about letting it sit 10 mins or anything.
ok so you have the cm7 initial kernel as an update.zip correct?
3 button into recovery reinstall packages twice that should load you into clockwork
(orange clockwork menu)
1 Mounts and storage menu
Format system/cache/data (do all 3)
+Go Back+
wipe data/factory reset
Pull battery Or just press and hold all vol up + down + power
back in recovery.
install zip from sd Card
Install the Miui ROM reboot system.
lemme know how it goes.
Click to expand...
Click to collapse
I was back at stock (which I'm not sure is 100% stock because when I turn on my phone, it has a samsung GT-i9000 image on the screen for a second or two before saying vibrant).
I have the update.zip and the miui on my internal sd root.
To get into recovery it's just the 2 button combo (volume - and power) for me.
I only have to hit reinstall packages once, and it takes me into clockwork.
I format the things you said and did the factory reset....
Pulling the battery and then trying to get back into recovery mode put my phone into a reboot cycle. (screen where it looks like after you do wipe data/factory reset) and then I have to odin back to stock.
The three button combo does the same thing. I can't get to the next step.
EDIT:
After the reboot cycle thing. I was able to get back into recovery mode even after it started its reboot cycle deal. Then I was able to install the miui rom. My phone has been on the Samsung Cyanogenmod boot screen for about 5-10 minutes. Not sure if it is trying to boot up miui or just stuck. I'll let it sit for another 15 minutes before thinking its stuck.
EDIT2:
Yep, It's been about half an hour. My phone is stuck on the cyanogenmod boot screen. I can't get it back into recovery or downloading either.
EDIT3:
After some serious playing around. I was able to get it back into recovery mode. Wipe everything, apply the update.zip again... and then was able to get back into downloading mode and reflash it to stock.
Does anyone know how to get to true stock, so I don't have the Galaxy-S GT-i9000 Samsung boot screen. I think that this has to do with why it is failing.
After searching around a lot more...
accidentally flashing an i9000 rom flashed the boot.bin and sbl.bin.
The files to odin back to stock jfd doesn't include the boot.bin or sbl.bin so that's why I get the extra boot screen, and why I 'brick' my phone everytime I try to flash another rom.
Apparently I will brick my phone anytime I try to flash a rom from now on, and that I need to find a boot.bin and sbl.bin combo for the vibrant if I want to be able to flash anything again or get any update past 2.1.
If anybody has any info on how to get this boot.bin and sbl.bin combo could you let me know. I can't find the files anywhere.

[Q] 3e recovery - ran out of ideas

After spending two whole days trying to flash my Galaxy S2 with MIUI 2.1.6 (also tried the latest Cyanogenmod and DarkyROM) and with nothing to show for it, it's time to ask for help.
My main goal is to install MIUI 2.1.6. The starting point is stock Gingerbread 2.3.5 (XXKI3). This is what I did:
- flashed stock 2.3.5 (XXKI3) via Odin
- rooted XXKI3 with CF-Root
- copied MIUI 2.1.6 on SD card (the zip file)
After that comes the part where I have to flash ClockworkMod Recovery and that's where the troubles start. My phone comes with 3e recovery which gives me the "failed to verify whole file signature" error after I try to flash CWM via the ROM Manager.
After browsing XDA forums, a lot of reading and trying both methods of overriding that bloody signature check (Untermensch's script method and Existenz's method of placing the Recovery file in /system/bin), none of them worked for me.
Untermensch's script method starts doing its thing but at one point it gives me an error message and suggests that my phone isn't rooted (which it definitely is, as I'm able to use Superuser, Root Explorer, AdBlock and every other root-only app).
Existenz's method of manually putting the Recovery file in /system/bin swaps the 3e recovery with CWM (orange letters, if I recall correctly), but after doing all the neccessary wipes and installing MIUI (or Cyanogenmod) from a zip file on my SD card, all I get is a boot loop. DarkyROM won't install at all, it simply gives me an error at the very beginning of the installation process.
At this moment I'm running stock Gingerbread 2.3.5, rooted by CF-Root and flashed with SpeedMod kernel. When I try to enter recovery, I'm getting CWM Recovery 5.0.2.3 (blue letters). However, if I try to wipe the phone and install MIUI from zip, all I get is another boot loop. And I'm back on 3e recovery.
Perhaps it's also worth mentioning my 3e recovery menu has no "reinstall packages" option which was mentioned in several threads on this forum that were vaguely related to my issue.
Anything I'm missing? Any ideas at all?
Thanks in advance and kind regards!
YouLaxy said:
My main goal is to install MIUI 2.1.6
Click to expand...
Click to collapse
Try the MIUI forums for support.
1) Flash CF-root
2) Copy the Miui zip into the sdcard
3) flash the Miui zip twice
4) reboot into CWM recovery
5) Flash the miui zip again
6) wipe cache/data
7) reboot into miui
oinkylicious said:
Try the MIUI forums for support.
Click to expand...
Click to collapse
The thing is, I'd ultimately like to be able to install any custom ROM, not just MIUI. So far none of them worked (MIUI, Cyanogenmod, DarkyROM), I'm guessing due to that nasty 3e recovery (nothing else comes to mind)
veyka said:
1) Flash CF-root
2) Copy the Miui zip into the sdcard
3) flash the Miui zip twice
4) reboot into CWM recovery
5) Flash the miui zip again
6) wipe cache/data
7) reboot into miui
Click to expand...
Click to collapse
I'll give that a go later today and post back the results. Cheers!
Nope, that didn't work. After flashing with MIUI twice via CWM and powering the phone off, I'm unable to enter recovery to flash MIUI for the third time, as the phone goes into boot loop.
Any other ideas, anyone? Thanks in advance!
Your not using rom manager are you?
Maybe its a bad miui download, where did you get the zip from?
Nope, I'm flashing the zip via CWM recovery, so after turning the phone off and doing the three-key thingy. I got the MIUI zip from MIUIAndroid.com and downloaded it three times, just to be sure there's not an issue with the zip.
YouLaxy said:
Nope, I'm flashing the zip via CWM recovery, so after turning the phone off and doing the three-key thingy. I got the MIUI zip from MIUIAndroid.com and downloaded it three times, just to be sure there's not an issue with the zip.
Click to expand...
Click to collapse
I have no clue then, it should work
Maybe you could try galnet miui?
Have you tried flashing other custom roms, eg hyperdroid or checkrom?
I did try to flash CyanogenMod (ended up with a boot loop, just like MIUI), as well as DarkyROM (got an error shorty after the start of the installation, can't remember what it was anymore). Seems my SGS2 simply isn't up for anything but stock ROMs. Bastard.
YouLaxy said:
I did try to flash CyanogenMod (ended up with a boot loop, just like MIUI), as well as DarkyROM (got an error shorty after the start of the installation, can't remember what it was anymore). Seems my SGS2 simply isn't up for anything but stock ROMs. Bastard.
Click to expand...
Click to collapse
CM7 does need doubleflashing, so when you go into CWM double flash the zip before wiping/rebooting.
And what was the error on the stock rom? Have you tried others.
Try this.
Its the resurrection edition of darkyrom. Its something to fall back on when other roms failI, it completely repartions your phone and should replace 3e with CWM and you'll have a nice darky custom rom
Make sure you follow the instruction to the letter
http://www.darkyrom.com/community/i...arkyrom-hd-v1-0-r5-resurrection-edition.6565/
veyka said:
CM7 does need doubleflashing, so when you go into CWM double flash the zip before wiping/rebooting.
And what was the error on the stock rom? Have you tried others.
Click to expand...
Click to collapse
Just tried to doubleflash CM7 and then do the wipe. Ended up in yet another boot loop (and unable to get into recovery). Then I restored the stock 2.3.5, rooted with CF-Root and tried to flash DarkyROM (via CWM recovery, of course). This is the message that it gives me:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So now I'm back on stock 2.3.5 once again. Blimey.
thteddieboii said:
Try this.
Its the resurrection edition of darkyrom. Its something to fall back on when other roms failI, it completely repartions your phone and should replace 3e with CWM and you'll have a nice darky custom rom
Make sure you follow the instruction to the letter
http://www.darkyrom.com/community/i...arkyrom-hd-v1-0-r5-resurrection-edition.6565/
Click to expand...
Click to collapse
I'll give it a go in a couple of minutes and post back with the results. Thanks for your input!
Wait you have an sgs 2? Well the darkyrom your trying to flash in your pic is for the galaxy one
This will seriously mess up your phone.. try the link.I posted should work
thteddieboii said:
Wait you have an sgs 2? Well the darkyrom your trying to flash in your pic is for the galaxy one
This will seriously mess up your phone.. try the link.I posted should work
Click to expand...
Click to collapse
Hahah, really? wow, hes lucky it didnt brick it, good old status 0 (oops should have noticed that, it means that the firmware isnt for this the phone you are trying to flash it on)
veyka said:
Hahah, really? wow, hes lucky it didnt brick it, good old status 0 (oops should have noticed that, it means that the firmware isnt for this the phone you are trying to flash it on)
Click to expand...
Click to collapse
Yeah I noticed cause it was darky 10.2.2 which I remember from my s1 days of flashing.. I was wondering why the 0 was there. Very lucky its not bricked
Let us.know how you go with the darkyrom HD resurrection.. darkyrom HD is for galaxy s 2 just in case you wanted to update in future and so you don't get confused
Feeling like a bit of a dumbass right about now. And just when I thought I tripple checked everything... Okay, that explains the DarkyROM issue, however still no clue what's wrong with MIUI and/or CM7. I'm sure I downloaded correct versions of those
I'm downloading the ROM from your link at this very moment, trying it shortly.
YouLaxy said:
Feeling like a bit of a dumbass right about now. And just when I thought I tripple checked everything... Okay, that explains the DarkyROM issue, however still no clue what's wrong with MIUI and/or CM7. I'm sure I downloaded correct versions of those
I'm downloading the ROM from your link at this very moment, trying it shortly.
Click to expand...
Click to collapse
All good. Its not hard to get mixed up. I remember how overwhelming it was when I first started learning to flash
Bit scary for a while til I learnt more and understood things better
Hmm I'm not to sure about the miui issue or cm7
Never used them, except for cm9 cause I like the aosp ICS..
Let us know how darkyrom HD goes for ya
Well, that worked. Had to flash twice to get it to work, though (got stuck on step #14 for 10 scary minutes and then just turned the phone off an reflashed)
I'll give DarkyROM a go. I do have one more question though. If I decide to try to flash MIUI once again, would it be enough to boot into CWM recovery and try to install it from zip (so, without doing anything to my DarkyROM installation) or do I have to go back to stock ROM for that?
Thanks a ton for your help guys, my SGS2 can run custom ROMs after all! Horray!

please help! BOOTLOOP Problem with CyanogenMod

Hey Folks,
Yesterday i tried installing CM9 Nightly on my SGS2 (no root). I followed the "Full Update Guide at the CyanogenMod-Forum but ended up with the bootloop problem even though i precisly followed the steps here: http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_II:_Full_Update_Guide
Now my s2 wont boot and is showing the yellow triangle. I can get into Recovery Mode which shows "CWMR Touch v.5.5.0.4.".
i downloaded the latest nightly build but when i tried flashing CM9 as described i got an error message "verification failed".
any help is appreciated!
hi
try putting the phone in odin mode and install another rom
Factory reset first when you have bootloop.
no need to worry.
get the nightly again dont use the torrent. it should be 118 mb.
using cwm format system, data, preboot, cache.
now flash again. you should have the file on ur ext sdcard already.
If worst comes to worst then download a offical samsung firmware from http://forum.xda-developers.com/showthread.php?t=1075278 or from http://forum.xda-developers.com/showthread.php?t=1113928 if carrier branded phone then open odin and flash the files within download mode. If you don't know how to use odin then follow the guide within the first link
How come there will be a boot loop if everything is followed precisely?
You can try flashing the same again
#*posted on the move *#
Do This
the_goat said:
Hey Folks,
Yesterday i tried installing CM9 Nightly on my SGS2 (no root). I followed the "Full Update Guide at the CyanogenMod-Forum but ended up with the bootloop problem even though i precisly followed the steps here: http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_II:_Full_Update_Guide
Now my s2 wont boot and is showing the yellow triangle. I can get into Recovery Mode which shows "CWMR Touch v.5.5.0.4.".
i downloaded the latest nightly build but when i tried flashing CM9 as described i got an error message "verification failed".
any help is appreciated!
Click to expand...
Click to collapse
Bro just remember that you must never flash a rom from within CWM or Rom Manager with our sgs2. I also did that and had same issue. Now, you can get into recovery mode and that is awesome. First things first, wipe everything, full system wipe, full wipe cache, full wipe sd card(format), next, attach your sgs2 to your pc and mount usb storage, transfer your chosen rom to sd card(I use Hydrogenics which is awesome). Next, unmount sd card, now flash hydrogenics. Now reboot system once hydrogen is finished flashing. You should never have issues like this again, especially with Hydrogenics. Also, do not forget to put gapps ics on sd card and flash it after you have flashed Hydrogenics. You can also use yellow triangle away app to remove the stupid leftover triangle from your previous rom flashing attempts, if you got LPB. Anyways bro, have fun and do not stress too much because the sgs2 is really hard to brick. Also, remember to check the md5 sum when downloading a rom, this lets you know it has not been tampered with and the entire rom is there.

[Q] Motorola Atrix 4G Stuck on M Screen With UNLOCK

Hello!
I need help
I unlocked bootloader and rooted phone with this http://forum.xda-developers.com/showthread.php?t=1182871
1) When I unlocked bootloader Android starts as usual and when asked MotoBlur accaunt I turned off phone
2) When I rooted phone Android starts as usual and when asked MotoBlur accaunt I turned off phone
After this I started Recovery Mode (in recovery mode I saw goapk.com instead of Clockworkmod (?) )
I Wiped Data and Cache and flash this zip ROM http://download.cyanogenmod.com/?device=olympus&type=stable When ROM Installation is complete I Rebooted phone and since then stucks this screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and it's turn on automatically when I put battery in the phone
and when I hold Vol Down button and at this same time put battery in phone it doesn't turn on automatically, only when i pressed power button or plug cable
Sorry for my bad english
Thanks
The bootloop could be cause by several things. Try to make a wipe data/factory reset and wipe caché from the android recovery.
If you dont know how to access the Android recovery mode here are the instructions:
1.- Turn on your phone holding down the Vol(-) key
2.- Once it says "Fastboot" press several times vol(-) until you see "Android Recovery" label
3.- Press vol(+) and it'll enter the recovery
4.- Navigate through the vol up and down keys and confirm with the power button
If the problem persists you'll need to change the kernel, pick one compatible with the rom you are running and install ir through the recovery mode(CMW is the most common)
have you tried cold booting linux OP? i had the same problem and booting without BP solved it for me
try to flash rom via recovery or RSD
I faced similar problem with my Atrix 4G (unlocked bootloader, SIM unlocked from AT&T)
Tried to flash epinter's CM10 on my stock 2.3.6. Stuck at 'unlocked' screen with M symbol.
Restoring backup from CWM does not seem to work.
Tried cold-booting Linux, but no use.
EDIT: Problem arose because of older version of CWM. Flash the latest CWM through old CWM and retried. Worked.
You can find it here.
factory reset and wipe dalvk and try flashing another rom from CWM
And make sure you flash latest recovery FIRST. Looks like you flashed a new Rom from an outdated recovery.
Sent from my MB860 using Tapatalk 2
Did you change already the kernel? Just search for faux cm7 on the forums and you'll find one, i'm sure that must be the reason for not booting, some kernels are not compatible with all the roms out there
consolation said:
And make sure you flash latest recovery FIRST. Looks like you flashed a new Rom from an outdated recovery.
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
i think i did this please let me know how to fix this i dont have a back up rom in the internal storage
EDIT- no worries i found a way to get through that now im running cm 7 with twrp recovery
Please help me.
sylar73 said:
I faced similar problem with my Atrix 4G (unlocked bootloader, SIM unlocked from AT&T)
Tried to flash epinter's CM10 on my stock 2.3.6. Stuck at 'unlocked' screen with M symbol.
Restoring backup from CWM does not seem to work.
Tried cold-booting Linux, but no use.
EDIT: Problem arose because of older version of CWM. Flash the latest CWM through old CWM and retried. Worked.
You can find it here.
Click to expand...
Click to collapse
I am a noob can you guide me step by step into flashing the latest CWM.
starman5 said:
I am a noob can you guide me step by step into flashing the latest CWM.
Click to expand...
Click to collapse
There are guides and tutorials here designed especially for noobs, did you go over them?
I have the same issue.
Blaster_David said:
Hello!
I need help
I unlocked bootloader and rooted phone with this http://forum.xda-developers.com/showthread.php?t=1182871
1) When I unlocked bootloader Android starts as usual and when asked MotoBlur accaunt I turned off phone
2) When I rooted phone Android starts as usual and when asked MotoBlur accaunt I turned off phone
After this I started Recovery Mode (in recovery mode I saw goapk.com instead of Clockworkmod (?) )
I Wiped Data and Cache and flash this zip ROM http://download.cyanogenmod.com/?device=olympus&type=stable When ROM Installation is complete I Rebooted phone and since then stucks this screen
and it's turn on automatically when I put battery in the phone
and when I hold Vol Down button and at this same time put battery in phone it doesn't turn on automatically, only when i pressed power button or plug cable
Sorry for my bad english
Thanks
Click to expand...
Click to collapse
I have the same issue. Did some one fix your problem? If so can you tell me how you fixed your Atrix 4g.
---------- Post added at 10:01 PM ---------- Previous post was at 09:41 PM ----------
ravilov said:
There are guides and tutorials here designed especially for noobs, did you go over them?
Click to expand...
Click to collapse
I am searching over Xda forums right now. Can you post the best link to fix my problem? I rooted and unlocked my bootloader on my Atrix 4g. Things went wrong when I installed CM9 through CWM recovery 4.0.1.4. I read that a person on xda was able to flash the newest cwm and that fixed his phone. I want to see if that can work for me.
Again I greatly appreciate you responding to my question!
starman5 said:
I have the same issue. Did some one fix your problem? If so can you tell me how you fixed your Atrix 4g.
---------- Post added at 10:01 PM ---------- Previous post was at 09:41 PM ----------
I am searching over Xda forums right now. Can you post the best link to fix my problem? I rooted and unlocked my bootloader on my Atrix 4g. Things went wrong when I installed CM9 through CWM recovery 4.0.1.4. I read that a person on xda was able to flash the newest cwm and that fixed his phone. I want to see if that can work for me.
Again I greatly appreciate you responding to my question!
Click to expand...
Click to collapse
you didn't say what happens when you hold the volume down button when turning your phone on... do you get 'fastboot'?
the order that you should install any rom using CWM is -
turn phone off (battery pull if necessary)
turn phone on, holding volume down (you should see 'fastboot' under the unlocked sign)
press the volume down till you come across 'android recovery' the press 'volume up' (this should take you to the CWM menu
(if you press the wrong button or select another command then battery pull and repeat steps)
assuming you have already installed your preferred rom on your phone I would recomend a full system wipe
to do this use your volume down/up button to goto 'mounts and storage' and select this by pressing the power button
using your volume down/up goto the 'format' group and format the following:
/preinstall
/system
/osh
/data
/cache
after you have completed these tasks select 'go back' and you should be on the first CWM page
select 'install zip from sd card'
depending on where you have installed the rom zip (usually it is on the internal sd card)
if internal select 'choose zip from internal card'
select your rom and install
when the installation has finished reboot your system
hopefully you should have a phone that works
good luck.
Here is a more detailed information on happened.
barry_ said:
you didn't say what happens when you hold the volume down button when turning your phone on... do you get 'fastboot'?
the order that you should install any rom using CWM is -
turn phone off (battery pull if necessary)
turn phone on, holding volume down (you should see 'fastboot' under the unlocked sign)
press the volume down till you come across 'android recovery' the press 'volume up' (this should take you to the CWM menu
(if you press the wrong button or select another command then battery pull and repeat steps)
assuming you have already installed your preferred rom on your phone I would recomend a full system wipe
to do this use your volume down/up button to goto 'mounts and storage' and select this by pressing the power button
using your volume down/up goto the 'format' group and format the following:
/preinstall
/system
/osh
/data
/cache
after you have completed these tasks select 'go back' and you should be on the first CWM page
select 'install zip from sd card'
depending on where you have installed the rom zip (usually it is on the internal sd card)
if internal select 'choose zip from internal card'
select your rom and install
when the installation has finished reboot your system
hopefully you should have a phone that works
good luck.
Click to expand...
Click to collapse
I thought i posted this but it is not showing up. So im re posting my response.
Yes I can get fastboot.
I have rooted my Atrix4g running Gb 2.3.4 several months ago. Earlier this week i installed CWM 4.0.1.4. Then I unlocked the bootloader by watching Johnny Phung's youtube video "How to Unlock the Bootloader for Atrix 4G Running GB 2.3.4 and 2.3.6 4.5." Then I rebooted the phone into the CWM Android recovery and wiped data/ factory reset. Then Wiped the dalvik chache. After that I installed from zip card CM9 "update-cm-9.0.0-RCO-Atrix-KANG-singed-8.zip" and rebooted my phone. After that the phone got stuck at the boot loading screen and I believe I soft bricked my phone. I read some where on XDA that installing CM9 from a older CWM recovery may cause this stuck in boot loading issue.
Did I permanently messed up my phone? Can I fix it or do I need to send it to Motorola for a new one.
Also thanks to everyone for helping me.:highfive:
starman5 said:
I thought i posted this but it is not showing up. So im re posting my response.
Yes I can get fastboot.
I have rooted my Atrix4g running Gb 2.3.4 several months ago. Earlier this week i installed CWM 4.0.1.4. Then I unlocked the bootloader by watching Johnny Phung's youtube video "How to Unlock the Bootloader for Atrix 4G Running GB 2.3.4 and 2.3.6 4.5." Then I rebooted the phone into the CWM Android recovery and wiped data/ factory reset. Then Wiped the dalvik chache. After that I installed from zip card CM9 "update-cm-9.0.0-RCO-Atrix-KANG-singed-8.zip" and rebooted my phone. After that the phone got stuck at the boot loading screen and I believe I soft bricked my phone. I read some where on XDA that installing CM9 from a older CWM recovery may cause this stuck in boot loading issue.
Did I permanently messed up my phone? Can I fix it or do I need to send it to Motorola for a new one.
Also thanks to everyone for helping me.:highfive:
Click to expand...
Click to collapse
As you are able to see 'fastboot' are you able to access 'android recovery' ?
I think my phone is soft bricked
barry_ said:
As you are able to see 'fastboot' are you able to access 'android recovery' ?
Click to expand...
Click to collapse
I see fastboot and I am able to access android recovery. The android recovery is CWM 4.0.1.4.
starman5 said:
I see fastboot and I am able to access android recovery. The android recovery is CWM 4.0.1.4.
Click to expand...
Click to collapse
I see that you think that your problem might be connected to using an older version of ClockwordMod. Although this thread (http://forum.xda-developers.com/showthread.php?t=1138541) is outdated, you might find some help in the issues that people have encountered in the past.
Here > http://forum.xda-developers.com/showthread.php?t=1204500 is the more up to date recovery that people use.
You can either install it using the fastboot method (I have never used that so you will have to get some help from the tutorials that are available - just google 'install CWM via fastboot atrix' and you'll find plenty)
OR...
as a workaround (if you still think it's CWM related) you can use your external sd card to install the latest CWM and/or another Rom.
To do this, you'll need to take your external sd card out of the phone and install what you need (using a card reader) from your PC onto the sd card.
After you have downloaded/installed what you need...
replace the sd card into the phone
boot the phone into 'android recovery'
select 'install zip from sd card'
select 'choose zip from sd card' (as opposed to 'choose zip from internal')
you should then be able to see the zip files that you placed onto your external sd card
install what you want
this is the method I would use but as with all things there are no guarantees
If it were me, I would install a stable rom CM 7.2 (http://download.cyanogenmod.com/?device=olympus&type=stable) onto your external and then do a full system/format wipe (as explained earlier) and try and install that as well and see where you go from there.
I hope this helps you get your phone back up and working. :good:
You are very helpful!
barry_ said:
I see that you think that your problem might be connected to using an older version of ClockwordMod. Although this thread (http://forum.xda-developers.com/showthread.php?t=1138541) is outdated, you might find some help in the issues that people have encountered in the past.
Here > http://forum.xda-developers.com/showthread.php?t=1204500 is the more up to date recovery that people use.
You can either install it using the fastboot method (I have never used that so you will have to get some help from the tutorials that are available - just google 'install CWM via fastboot atrix' and you'll find plenty)
OR...
as a workaround (if you still think it's CWM related) you can use your external sd card to install the latest CWM and/or another Rom.
To do this, you'll need to take your external sd card out of the phone and install what you need (using a card reader) from your PC onto the sd card.
After you have downloaded/installed what you need...
replace the sd card into the phone
boot the phone into 'android recovery'
select 'install zip from sd card'
select 'choose zip from sd card' (as opposed to 'choose zip from internal')
you should then be able to see the zip files that you placed onto your external sd card
install what you want
this is the method I would use but as with all things there are no guarantees
If it were me, I would install a stable rom CM 7.2 (http://download.cyanogenmod.com/?device=olympus&type=stable) onto your external and then do a full system/format wipe (as explained earlier) and try and install that as well and see where you go from there.
I hope this helps you get your phone back up and working. :good:
Click to expand...
Click to collapse
I am one step closer to having my Atrix 4g working again!
I was able to install CWM 5.0.2.7. However the atrix4g is still stuck at Motorola loading screen. Also when I boot into android recovery using CWM 5.0.2.7 I receive the text "E: cant mount/cache/recovery/command" Then it says "E: cant mount/cache/recovery/log" Then it say "E: cant open/cache/recovery/log"
Should I be worried about this? Should I fix the 3 "E: cant" prompts before I proceed to installing CM9? I want Cm9 because some apps in the play store (for example Google chrome) only run on ICS and above. Barry I want to thank you for your help.
starman5 said:
I am one step closer to having my Atrix 4g working again!
I was able to install CWM 5.0.2.7. However the atrix4g is still stuck at Motorola loading screen. Also when I boot into android recovery using CWM 5.0.2.7 I receive the text "E: cant mount/cache/recovery/command" Then it says "E: cant mount/cache/recovery/log" Then it say "E: cant open/cache/recovery/log"
Should I be worried about this? Should I fix the 3 "E: cant" prompts before I proceed to installing CM9? I want Cm9 because some apps in the play store (for example Google chrome) only run on ICS and above. Barry I want to thank you for your help.
Click to expand...
Click to collapse
How's everything going?
It would appear that you've got some issues with your CWM but whether or not they would affect a ROM installation? I don't know.
Personally, I would try to install a Rom and see what happens... if it doesn't work then go back to installing CWM again and try again?
About to fix my phone hopefully.
barry_ said:
How's everything going?
It would appear that you've got some issues with your CWM but whether or not they would affect a ROM installation? I don't know.
Personally, I would try to install a Rom and see what happens... if it doesn't work then go back to installing CWM again and try again?
Click to expand...
Click to collapse
I wiped the Dalvik-Cache and the 3 "E: cant" prompts went away. About to do a nandroid backup and flash CM9. Also thanks for checking up on me Barry. It shows how caring Xda member treat each other.

[Q] Flashing to CM11 from Stock EH03

I'm going from stock to 11
I follow the steps in this guide
I'm trying to install CM10.1 before installing CM11. From what i've read this is ideal
The problem occurs when I go to install cm 10.1
-push EH03 via odin
-reboot
-push cwm4 fixed for 7 via odin
-push GB Bootloaders
-3 button into recovery
-wipe (recover-factory reset / wipe dalvik cache)
*** I get an E: unkown volume for path [/sd-ext] when clearing dalvik cache. I don't know if this is normal***
-install zip -> CM-10.1-xxxxx.zip
This is where i get stuck
load screen starts then reads "bml/mtd..."
reboots into cwm v6.0.2.2
immediately flashes META-INF... with error droid background (cant read the error flashes to fast)
repeats this error 3-5 times then loads into cwm 6.0.2.2
If i try to reinstall zip from there it just blinks then goes back to cwm home.
I cant do anything from this point and I have to reload EH03
Any ideas or help would be appreciated.
Have you verified the MD5 of your CM10.1 download. Could just be a bad download.
Read this thread and see if it helps.
http://forum.xda-developers.com/showthread.php?t=2551041
tsdsbrk said:
Read this thread and see if it helps.
http://forum.xda-developers.com/showthread.php?t=2551041
Click to expand...
Click to collapse
yes I've referenced that thread and posts in the original guide as well.
I've tried many different install methods and guides and I either get a status 7 error or install immediately resets the recovery and fails to load.
I've spent all day and a good portion of last week on this and its super frustrating
reloaded all the downloads from the guide this morning to make sure I didn't end up with a bad file same result.
I did get a cm7 rom working this weekend and one ICS(CM9?) rom working but when I would try to move on from there im ending up in this position.
just tried to flash hellybean 4.2.2 and im getting status 7 error.
saw a post that said to install zip again after first 7 error and still the same result, cant get past status 7 error.
I did a few other searches for status 7 fixes and im not coming up with anything definative.
I had a similar problem a while back that was due to the SD card. Let me see if I can find the thread...
http://forum.xda-developers.com/showthread.php?t=2407858
Try flashing this rom after the EH03 stock rom and before the 4.2.2 rom
http://d-h.st/ih2m13vt442z/sc3_milestone2_full.zip
SupraLance said:
I had a similar problem a while back that was due to the SD card. Let me see if I can find the thread...
http://forum.xda-developers.com/showthread.php?t=2407858
Click to expand...
Click to collapse
sounds exactly like my problem, I did just buy a sandisk class 10 last friday after an old class 4 became currupt.
I'll try it with a diffrent sd card and see where that gets me.

Categories

Resources