I want to install cyanogenmod 7 on galaxy tab with Hemidall,I really don't know how can i install this rom using hemidall,I have also downloaded CWM one to install but it get stuck at screen logo.Please help me i have flashed my galaxy tab twice.
This isn't really helpful in figuring out what your problem is.
We need far more information in order to try to assist you.
What model you have (carrier), what you have done (checked bootloaders? unlocked them? Installed CWM properly? Followed the Guide?) etc...
Please provide more information.
Related
hi guys, i've been using Xperia x10 previously and i was able to install CFW and root on my x10.
I just upgrade to galaxy s2. It's with BELL but unlocked. now my question is :
where to begin to root? and install custom firmwares? what do i need?
your help woud be much appreciated!
You must flash a custom kernel which roots your device and installs clockworkmod recovery. From the recovery you can install than any custom ROM.
I think there are enough instructios how to do that.
ok done the rooting and clockworkmod recovery.
what is the best firmware out there? in case i fail to install new CFW, how to factory reset to stock firmware? Thanks.
Go to SII section please...
Galaxy S I9000 Q&A - :F
Hello all,
I am in need of some help. I am new to Android, and I have a Samsung Galaxy S2 Skyrocket with AT&T, but I managed to root my phone with Super One Click and install ClockWork Mod Recovery.
Now, when I try to download an OTA update (I am trying to go from Gingerbread to ICS), it boots into clockwork mod recovery and I can't complete the update.
Help! I just want to get my phone back to normal so I can get rid of clockwork mod. I don't even really care about root anymore.
I am not familiar with all of the fancy terms and lingo, so I need "dummy" instructions.
Thanks in advance!
-J
Try the galaxy s2 forum. This forum is for original galaxy s.
Sent from my GT-P7500 using Tapatalk 2
Hello there,
I may be new to this forum but I have plenty of experience playing about with computer and phone workings and have long had my Galaxy Ace routed and have had a number of custom ROM's installed over time. However, today, while upgrading my Galaxy Ace to 4.4, the phone failed to install it saying "Installation aborted" (status: 7). I have restored the original ROM and all that rubbish but when I went to reboot, it has bricked :crying: on the Galaxy Ace name screen....HELP!
I use my phone for everything and any help on how to sort this would be greatly appreciated.
Thank you in advance.
Kai Savage
KJS607 said:
Hello there,
I may be new to this forum but I have plenty of experience playing about with computer and phone workings and have long had my Galaxy Ace routed and have had a number of custom ROM's installed over time. However, today, while upgrading my Galaxy Ace to 4.4, the phone failed to install it saying "Installation aborted" (status: 7). I have restored the original ROM and all that rubbish but when I went to reboot, it has bricked :crying: on the Galaxy Ace name screen....HELP!
I use my phone for everything and any help on how to sort this would be greatly appreciated.
Thank you in advance.
Kai Savage
Click to expand...
Click to collapse
I think, it's a soft brick. You said that "I have restored the original ROM". How? Via Odin or CWM Backup?
You need to be more specific, then only we can help you... And also, you've created this thread in wrong section... Read this...
No need to panic! We are all here...
KJS607 said:
Hello there,
I may be new to this forum but I have plenty of experience playing about with computer and phone workings and have long had my Galaxy Ace routed and have had a number of custom ROM's installed over time. However, today, while upgrading my Galaxy Ace to 4.4, the phone failed to install it saying "Installation aborted" (status: 7). I have restored the original ROM and all that rubbish but when I went to reboot, it has bricked :crying: on the Galaxy Ace name screen....HELP!
I use my phone for everything and any help on how to sort this would be greatly appreciated.
Thank you in advance.
Kai Savage
Click to expand...
Click to collapse
Wrong section mate ...
You must read rules before posting nothing, so the next time go to Q&A THREAD, we need to contribute to keep clear General Thread
Anyways you can ask for this issue in the rom's thread
Thank you for understanding it
Don't worry, you can use Odin to flash a fresh Stock rom or try to do via CWM; wipe data/factory, wipe cache partition, wipe dalvik-cache and finally, restore your last functional backup. It should work
Use ODIN to flash the stock rom
Its also happened to my ace,try to relash it via odin to stock gingerbread and stuck at download mbib for 5 hours
Sent from my GT-P3100 using xda premium
nakbaliNe said:
Its also happened to my ace,try to relash it via odin to stock gingerbread and stuck at download mbib for 5 hours
Sent from my GT-P3100 using xda premium
Click to expand...
Click to collapse
If this problem arises, then try renaming the ops file to cooper_v1.0.ops. That should solve it.
Hello all,
I'm currently trying to install a ROM on my fathers Samsung Galaxy Note GT-i9220, I've been reading and apparently this is exactly the same as the N7000. I've attempted to install Hellybean and SpiritRom but I get a "This device is not N7000" and can't continue. I have Philz ready to go but it seems like there must be some differences between those two models for the ROM to fail the installation.
Can anybody direct me towards some ROMs to improve his phone?
Thank you very much.
Carlitomayn said:
Hello all,
I'm currently trying to install a ROM on my fathers Samsung Galaxy Note GT-i9220, I've been reading and apparently this is exactly the same as the N7000. I've attempted to install Hellybean and SpiritRom but I get a "This device is not N7000" and can't continue. I have Philz ready to go but it seems like there must be some differences between those two models for the ROM to fail the installation.
Can anybody direct me towards some ROMs to improve his phone?
Thank you very much.
Click to expand...
Click to collapse
It could be because of the updater script checking for assert device type.. either edit the script and push it back to the rom zip file, or edit the device build.prop to show the device as n7000. But please make sure you have the same hardware using some system info apps like quadrant.
nokiamodeln91 said:
It could be because of the updater script checking for assert device type.. either edit the script and push it back to the rom zip file, or edit the device build.prop to show the device as n7000. But please make sure you have the same hardware using some system info apps like quadrant.
Click to expand...
Click to collapse
That's all I have left to try, I attempted to install a N7000 ROM and it stated model was N7000 once i restarted it, it said GT-i9220 again...
Thank you very much, i'll try that!
@Carlitomayn almost 2 years I have been using N7000 firmwares on my phone with the same model as yours i9220.
I accidently updated an unrooted Samsung stock ROM that shipped with the phone with cyanogen_mod
_7_tass in my attempt to root my Samsung Galaxy mini s5570 using update.zip method.
I had intended to used the "update.zip" method to root the device. But the ROM MOD instead, sadly had also been "update.zip".There was a mix up of the two files.Theres unfortunately no Clockworkmod Recovery installed. (I was quite aware of this possibility if things were to go wrong.).
My Device runs on Froyo and now is in a bootloop.
I just only want to find out if there is the slimest chance of having my device back in shape again.
Thanks a bunch in advance !
I will be happy to hear theres some hope.
huffy808 said:
I accidently updated an unrooted Samsung stock ROM that shipped with the phone with cyanogen_mod
_7_tass in my attempt to root my Samsung Galaxy mini s5570 using update.zip method.
I had intended to used the "update.zip" method to root the device. But the ROM MOD instead, sadly had also been "update.zip".There was a mix up of the two files. Theres unfortunately no Clockworkmod Recovery installed. (I was quite aware of this possibility if things were to go wrong.).
My Device runs on Froyo and now is in a bootloop.
I just only want to find out if there is the slimest chance of having my device back in shape again.
Thanks a bunch in advance !
I will be happy to hear theres some hope.
Click to expand...
Click to collapse
You must reinstall again stock rom (programs needed: Odin,tass.ops and drivers for galaxy mini s5570). On xda you'll find step by step reverting back to stock rom your galaxy mini. Btw read carefully every step to understand those things and after you can practice. Check general section for Odin and installing stock rom.
Press thanks if helped you
am downloading .. s5570 galaxy mini firmware--- is that the same thing as stock ROM?
kyooby said:
You must reinstall again stock rom (programs needed: Odin,tass.ops and drivers for galaxy mini s5570). On xda you'll find step by step reverting back to stock rom your galaxy mini. Btw read carefully every step to understand those things and after you can practice. Check general section for Odin and installing stock rom.
Press thanks if helped you
Click to expand...
Click to collapse
After a whole day of no-work and goofing around the web yesterday i figured out somthing similar but just wasnt sure ...felt i needed to search some more. then your quote dropped in my inbox. Its made a lot of my confusion clear. I have tass, odin and ops. all the programs need already. At first i could access the stock rovery mode, but using odin again to try and get Clockworkmod made matters worse. I have with a bootloop and no where close to the recover mod any more just downloading mode. So I've kept reading and reading on to find out something useful. I guess that may be the sure way getting stock rom installed back.
Now i am just downloading .. s5570 galaxy mini firmware--- is that the same thing as stock ROM?
That's it man...Official firmware is called the stock rom...
Sent from my GT-S5570 using XDA Free mobile app
Im curious how did it go
Sent from my SM-N9005 using XDA Free mobile app