hi to everyone.
have a little trouble, but first, my phone specs:
Model: Sk17a
Rom: Xperia Mini Pro_4.1.B.0.587_Generic.
Root: yes
CWM Recovery: V5.5.0.4 by pvyPar
BL: locked
Well i want to flash this rom "[ROM][ICS] Revolution ICS HD™ [Build 8.0][Super Silk] 11.07.2013 Final Release" credits to : saqib nazm
I already flashing two times, in the first time was restarted after pass sony logo, on the second time he stayed in the sony logo.
qualify and follow the instructions for installing this ROM, contact the dev of the rom and I said no matter which model is sk17a or SK17i, works both.
what will be the problem that I can not install this rom??
Thanks and good day.
problems with flashing roms
hi there,
i'm not entirely sure if this will help you but generally speaking i came made a few observations about the fact that some people, mostly repeatingly the same users, encounter problems with their custom roms and/or flashing them, while others don't, albeit they are using the same devices.
i my selfe use 3 different devices, all rooted and running on pac 4.3, always lates nightly, as there are GT-N7100 - GT-I9100 - Nexus 4
not to the point
a) other than most other users i usually clean cache and dalvik cache as well before and after flashing the new rom and/or new nightly
and never encountrer any problems except those which everybody, using the same rom and nightly encounters.
b) whenever i flash an totally different rom and/or upgrade and/or downgrade to another level of android os, i.e. from 4.2.2 to 4.3, i perform
a clean install, including not only a factory reset, but as well a format sd-card, format cache and format system etc., again i cannot proof
which of these steps make a or the differnce but however, i never have problems others than thosw which everyone has with a version.
c) when using cusome kernels and due to the fact that some roms come with a kernel included, as well as with a custom recovery included,
it is strongly recommended not to forget to flas the kernel again after each flashing the new rom. one good example ist dorimanx kernel
for GT-I9100 which will not boot into recovery and reluctantly boot at all after a new flash of a pac nightly without reflashing the kernel.
d) try to fix permissions on reboot instead of doing it from recovery. one reason is that not every recovery has this option and further i
found that when fixing permissions before the first boot after flashing a new rom, there might be bootloops, albeit i cannot explain exactly
why that should, but however, sometimes it's better to be on the safe sid.
e) try to run whether the lastes version of custom recovery for your device, and or the use the included custom recovery of the rom or the
kernel. this again is one thing that can help to avoid some unexpected and hard to explain bootproblems and/or fc's etc.
hope that i could give you some new ideas how to avoid trouble while using custom roms and other hacks
Good point at the nex time i clean the dalvik caché afther flash Thanks bro
Sent from my SK17a using xda app-developers app
Related
Hi All
Finally plucked up the courage to register and ask a question after lurking for the good part of 2 years.
I've an i9020A and have flashed CyanogenMod 9 v4.0.3 v1.0 which is great, however I wanted to try Steve Garon's kernel which just wont take.
I reboot into Recovery, wipe Dalvik Cache a couple of times, install Steve's kernel which apparently flashes no problem.
I reboot and get the optimising Android applications screen then check my kernel under settings.
It is still the original KalimochoAz kernel and I cannot turn on my wireless.
Now this has happened previously when trying to also update my kernel under CDTDroid's AndroidMe 1.2 which I could only fix by restoring back to 1.1.
Any idea on what may be wrong here guys?
Appreciation in advance.
Lally
Have you tried just flashing again? A bad flash often results in wifi not working and may be the cause of the about page showing the old kernel. Remember to wipe dalvik cache again, too.
Thanks for the reply Harbb, do you mean a re flash of the Kernel or ROM? If Kernel then yeah I have done, same scenario. I'll also try a re download of the Kernel to see if that improves anything but this is much akin to me trying to update from Speedy3 to Speedy4 under AndroidMe 1.2 which was unsuccessful.
Just the kernel, as you've already tried. Just remember to do a NANDroid backup (CWM --> backup & restore --> backup) when you have a stable, working ROM. Can save you alot of trouble if you don't have a relatively recent one.
Also, are you using CWM 5.0.2.0? And could it be that your phone isn't particularly happy about the 1100mhz OC with Steve Garon's kernel?
I'd suggest updating CWM recovery to the latest version.
Sent from my Nexus S using xda premium
Cheers for the help guys.
Yes, using 5.0.2.0, but something is not right cause I just tried to flash CWR again from within Rom Manager (4.8.1.3) and it gets to around 95% and the app gives 'Rom Manager is not responding.
Looks like I'll have to try a complete wipe and reflash.
Will report back the results.
Forget rom manager all together.
Download the recovery you want to use.
Flash it via fastboot
flash kernel.
I'd do what albundy said - flash a new recovery through fastboot and make sure the bootloader is unlocked (vol. up + power --> bootloader: unlocked)
Ok, downloaded CM9 1.1, redownloaded Steves kernel, reinstalled recovery from fastboot.
Wiped and formatted everything twice then installed from scratch.
So far everything is good, still getting errors on Superuser, but installing again via recovery seems to fix that issue.
Cheers chaps.
Good to know Lally, happy you got it sorted out.
Cheers Harbb, the test will be when I want to change the kernel again I suppose, one complete wipe and install a day is enough
I'm having a problem flashing marmite 4.4 to the newest miui build (2.9.7).
Basically in cwm recovery and flashed the kernel.
Will say "ununderstandable message 3" and "lid is licked"
Reboot the device and it will get stuck on the miui boot screen.
Tried installing both the "stock OTA" and "All other ROM" version of marmite.
Same message comes up.
Already tried performing a full wipe (actual full restore, format system, format boot), reload the ROM.
Tried wipe cache and dalvic (even though it is not needed)
Just wondering if there is something incompatible or not.
I was able to flash air kernel without issues.
I haven't tried an older version of marmite yet, but will try later.
I'm not blaming marmite, it could be miui as well, or it could be just me.
I'm certain I'm flashing correctly.
I read bedalus' marmite post and saw 2 others with this issue (not same version of kernel or ROM).
The suggestion was that they didn't use the correct kernel for ROM.
I would assume miui would not be categorized as "stock OTA", so I tried "all other ROM" version first"
Am I doing something wrong?
There is a new version 4.5 the message you get I believe is like a joke. It does show however that the installation was successful.
Never experienced boot loops flashing his kernels.
Sent from my Nexus S
Actually, I downloaded that one just now to try and same issue.
It will just stall at the miui (ROM) boot screen.
I am trying some other stuff right now as well.
Really want to use this kernel. :good:
I'll report back later.
Thanks for the help.
Good luck. His kernel offers great speed and stability!
Sent from my Nexus S
For marmite 4.5, did a full wipe again, even formatted the SD partition.
So flashed miui 2.9.7.
Booted to the ROM.
Made sure things seem normal in the ROM.
Restarted just to be sure.
Boot back to recovery.
Flashed marmite 4.5
And it is stuck on the miui loading screen again.
Only thing I haven't tried this time is to fix permissions. (didn't wipe cache or dalvic either)
I'll try it again. :laugh:
Since I formatted the SD partition, it should rule out that it was something on the SD card right?
It's time consuming to copy things back to the NS.
I'll try an older version of marmite afterwards and then an older version of miui.
It should tell me what is causing the lock up by then. I think. :silly:
.... yes I have a lot of time ....
I forgot to mention one thing.
I'm flashing the official Chinese version of miui 2.9.7.
Wonder if that's the cause.
I guess I will download the US or UK version to try as well.
Well if your phone boots with original kernel, it must be kernel related. There's no need to wipe anything before flashing a kernel. Just flash it. It could be that the Chinese rom is different from the others, but that's a guess I'm no expert on compatability.
Sent from my Nexus S
kwibis said:
Well if your phone boots with original kernel, it must be kernel related. There's no need to wipe anything before flashing a kernel. Just flash it. It could be that the Chinese rom is different from the others, but that's a guess I'm no expert on compatability.
Sent from my Nexus S
Click to expand...
Click to collapse
Took some time to test, but sort of found my answer.
It's the official Chinese miui that's causing the issue.
Well at least some component in the ROM.
I tested with the MIUI UK (miuiandroid) version 2.9.7 and it installed like a charm.
Before flashing the UK version, I tested with earlier versions of marmite (4.3 and 3.5) on the Chinese 2.9.7.
All failed at the ROM boot screen.
I should check with the miuiandroid team and see what they changed that made it different.
When I was testing I did a full wipe, installed ROM, booted ROM, boot to recovery and flashed the kernel.
I didn't even wipe cache or dalvic (which is not needed anyways).
I had to do a full wipe because the ROM just wouldn't boot back up afterwards.
I'm tempted to test with an earlier version of the official Chinese miui and see if it makes any difference.
... too much time and/or no life ... :laugh:
Lol, well it's good you found your answer So its not a waste lf time as you learn from this
Sent from my Nexus S
If you flash air kernel, and if it worked, I guess marmite's boot.img type can cause a problem.
Sent from my Nexus S using Tapatalk 2
Articudos said:
If you flash air kernel, and if it worked, I guess marmite's boot.img type can cause a problem.
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
Not sure what the boot.img type is, but I'll look it up. Thanks.
I posted on miuiandroid forums and someone replied saying that the Chinese version is odexed and not busyboxed.
UK and US version is definitely deodexed, I downloaded them and checked. I haven't found out how to check busybox.
I have a few choices.
1. I can use the UK or US version, since I was able to flash marmite on them... easy way out.
2. Find out how to deodex the ROM and, I guess, how to add busybox (?)... I get to learn more stuff.
3. Use a way faster ROM (eg. Paranoid Android - great ROM by the way!) and flash marmite on it as well... but really want to use miui again.
Thanks guys for your help though. Really appreciate the information. :good:
Glad you found a solution
Sorry if this has already been asked before. If you already have a custom ROM with stock kernel, and now you want to install a custom kernel, would you just boot into custom recovery then flash it on top of the existing ROM just like flashing Gapps? or do you have to wipe the ROM first, flash the kernel then ROM after that? Here's another question. Custom ROMs come with their own kernels, would my custom kernel get overwritten when I upgrade my ROM to a newer version (for example from cm10.1-20130226 to cm10.1-20130309?
k20- said:
Sorry if this has already been asked before. If you already have a custom ROM with stock kernel, and now you want to install a custom kernel, would you just boot into custom recovery then flash it on top of the existing ROM just like flashing Gapps? or do you have to wipe the ROM first, flash the kernel then ROM after that? Here's another question. Custom ROMs come with their own kernels, would my custom kernel get overwritten when I upgrade my ROM to a newer version (for example from cm10.1-20130226 to cm10.1-20130309?
Click to expand...
Click to collapse
Correct just copy the kernel to your sdcard clear cache in recovery and flash away.
I tried your ROM and rebooted twice and still looking good. Hope it'll still survive after the 3rd reboot. However, I notice some delay before the first ring back, probably due to weak signal in my area. I'll try more at different locations in the next few days to see how it goes. I really appreciate your contribution and all coders with TeamChopsticks who have nailed down the root cause of audio loss in the cm10.1 nightlies for skyrocket.
I'm having problem with Carbon ROM. My video doesn't playback I only see purple screen. However taking pictures is fine but both the qualities are low. I already set to HD. I flashed AOKP from toyes and REVOLT they had no problems with the video.
sent from Skyrocket
hi folks,
Need information on how to load CM 10.1 Android 4.2.2 on my Samsung Galaxy S Plus.
Currently i have the CM 10 Beta 4 (JB 4.1.2) installed. Current recovery is Recovery-clockwork-5.5.0.4-ariesve.
I've downloaded these files.
cm-10.1-20130622-dev_connection_team-release2-ariesve.zip
DevCon-gapps-jb-20130622-signed.zip
cwm6032-Build2-ariesve-alireza7991.zip
Kernel_JB-4.2.2_3.4_20130622_Google-4.6_Stock_Signed.zip
When i checked the AriesDevCon team's link and XDA Wiki Samsung SGS+ link there was some confusion.
The Wiki link doesn't say anything about the recovery installation. Should i use Odin to install the CWM6032 or just put it in the SD card and reboot into recovery? I'd used Odin for the 5.5.0.4 recovery.
From the XDA forums on recovery (alireza7991's) saw that i could use Odin to install the recovery first.
Also, what do i do with the 3.4 kernel ? Should i load that too in the SD card before recovery mode for the installation?
My current kernel is 3.0.70.
Could someone with the proper knowledge please guide ? And please provide the exact steps and the files needed.
I've done the CM 10.1 already and it worked pretty well, but was not able to do any upgrade later (to release 2.5 etc). Had my phone soft-bricked two times and had to install the stock Gingerbread ROM to come back to JB 4.1.2 ROM.
regards,
Anoop
The files you got are .ZIP files.
It should be possible to flash these using the recovery. I have To check back for further instructions cause i'm not familiar with the s+ but cwm should be installed automatically when the kernel has be installed.
Sent from my GT-I9100 using xda app-developers app
Did it work?
Sent from my GT-I9100 using xda app-developers app
Hey dude...u must wipe data,dalvik....maybe it can help u...
Sent from my HTC ChaCha A810e using xda app-developers app
lil.masoud said:
Hey dude...u must wipe data,dalvik....maybe it can help u...
Sent from my HTC ChaCha A810e using xda app-developers app
Click to expand...
Click to collapse
You have to wipe data and cache, wiping dalvik cache is useless.
anoopgkris said:
hi folks,
Need information on how to load CM 10.1 Android 4.2.2 on my Samsung Galaxy S Plus.
Currently i have the CM 10 Beta 4 (JB 4.1.2) installed. Current recovery is Recovery-clockwork-5.5.0.4-ariesve.
I've downloaded these files.
cm-10.1-20130622-dev_connection_team-release2-ariesve.zip
DevCon-gapps-jb-20130622-signed.zip
cwm6032-Build2-ariesve-alireza7991.zip
Kernel_JB-4.2.2_3.4_20130622_Google-4.6_Stock_Signed.zip
When i checked the AriesDevCon team's link and XDA Wiki Samsung SGS+ link there was some confusion.
The Wiki link doesn't say anything about the recovery installation. Should i use Odin to install the CWM6032 or just put it in the SD card and reboot into recovery? I'd used Odin for the 5.5.0.4 recovery.
From the XDA forums on recovery (alireza7991's) saw that i could use Odin to install the recovery first.
Also, what do i do with the 3.4 kernel ? Should i load that too in the SD card before recovery mode for the installation?
My current kernel is 3.0.70.
Could someone with the proper knowledge please guide ? And please provide the exact steps and the files needed.
I've done the CM 10.1 already and it worked pretty well, but was not able to do any upgrade later (to release 2.5 etc). Had my phone soft-bricked two times and had to install the stock Gingerbread ROM to come back to JB 4.1.2 ROM.
regards,
Anoop
Click to expand...
Click to collapse
It is not necessary to install recovery before every ROM installation. CWM 5.5.0.4 is a stable and safe recovery for our device.
According to the kernel i recommend you to use K^Kernal 3.4.x. It is more battery friendly with good performance.
The procedure is as explained in there
1. Boot in to recovery and
2. flash CWM 6.0.3.2 (if you want to, otherwise skip this) and reboot in to recovery.
3.Wipe data(not necessary when you are coming from a previous build of the same ROM, but recommended), wipe cache, and wipe dalvic cache
4. Flash ROM, Flash Gapps and flash kernel and reboot,
You are done.!
[SOLVED] How to install CyanogenMod 10.1 on my Samsung Galaxy S Plus
Hey folks,
Thanks to all of you for the kind advises!
In fact, i checked for any reply one hour after posting my question and only H3llwar's one reply was visible.
Was too impatient and thought to go ahead with the Modding.
First tried to flash the latest recovery cwm-emmcbrickedpatch-ariesve-6.0.3.2-alireza7991.img using Odin.
This one stuck at one stage (<1> recovery.img download) and didn't move further. So disconnected the USB and removed the battery (I forgot though in what sequence). I expected this to happen since it had happened two times before when trying to flash a non-tar recovery. Also I expected my phone to be soft-bricked, but luckily it did'nt. :good:
Then went through some more info on XDA and other forums and found a WORKED.rar solution.
from http://forum.xda-developers.com/showpost.php?p=30015714&postcount=22
Used that AriesVE.ops version and the recovery-clockwork-6.0.1.0-ariesve.tar.md5 and was able to flash the new recovery.
The reason i flashed the new recovery is that because i always used to find on these forums to use a specific recovery for a specific ROM.
Anyway, then i loaded the CM 10.1 and Gapps into the SD card, set debugging mode on and restarted in Recovery mode.
Then backed up data (Nandroid). Then wiped data/factory reset and wiped cache partition.
Then asked recovery to install from zip card selecting the CM10.1 ROM followed by Gapps. These processes happened very fast this time.
Then rebooted and there it was, a new magenta Cyanogen footer logo along with with the Samsung logo.
Skipped the initial parts and went to the About Phone section with the Android 4.2.2 indication.
Was very happy to also see my Kernel updated to 3.4.49. Three days now on the new ROM and loving it, battery life improved by at least 5% (from the 4.1.2). But missing the 4.1.2 fonts for the clock etc. Although the other internal fonts are smoother and easier on the eye.
Pasting the info screenshot here.
anoopgkris said:
Hey folks,
Thanks to all of you for the kind advises!
In fact, i checked for any reply one hour after posting my question and only H3llwar's one reply was visible.
Was too impatient and thought to go ahead with the Modding.
First tried to flash the latest recovery cwm-emmcbrickedpatch-ariesve-6.0.3.2-alireza7991.img using Odin.
This one stuck at one stage (<1> recovery.img download) and didn't move further. So disconnected the USB and removed the battery (I forgot though in what sequence). I expected this to happen since it had happened two times before when trying to flash a non-tar recovery. Also I expected my phone to be soft-bricked, but luckily it did'nt. :good:
Then went through some more info on XDA and other forums and found a WORKED.rar solution.
from http://forum.xda-developers.com/showpost.php?p=30015714&postcount=22
Used that AriesVE.ops version and the recovery-clockwork-6.0.1.0-ariesve.tar.md5 and was able to flash the new recovery.
The reason i flashed the new recovery is that because i always used to find on these forums to use a specific recovery for a specific ROM.
Anyway, then i loaded the CM 10.1 and Gapps into the SD card, set debugging mode on and restarted in Recovery mode.
Then backed up data (Nandroid). Then wiped data/factory reset and wiped cache partition.
Then asked recovery to install from zip card selecting the CM10.1 ROM followed by Gapps. These processes happened very fast this time.
Then rebooted and there it was, a new magenta Cyanogen footer logo along with with the Samsung logo.
Skipped the initial parts and went to the About Phone section with the Android 4.2.2 indication.
Was very happy to also see my Kernel updated to 3.4.49. Three days now on the new ROM and loving it, battery life improved by at least 5% (from the 4.1.2). But missing the 4.1.2 fonts for the clock etc. Although the other internal fonts are smoother and easier on the eye.
Pasting the info screenshot here.
Click to expand...
Click to collapse
You tried to flash .IMG recovery file via Odin. That won't work.! You need a .tar or .tar.md5 file to flash via odin.
Sent from my GT-I9001 using xda premium
Good battery life - CM 10.1
Hey Jabrief, thanks for the advise, I'll note it.
Until now, CM10.1 - 4.2.2 is running very smooth on my SGS+. Getting a very good battery life too. GPS is somewhat slow but maybe it's because odd the cloudy weather all the month.
Attaching a battery stats pic.
Got 32 hours and 40 mins on single charge.
About 16 mins of call, 45 mins of browsing in all.
thanks,
Anoop
i installed cm 11 unofficial from this thread http://forum.xda-developers.com/showthread.php?t=2608377 but when i turn my moto g on it gets stuck in the cyanogenmod loading screen if anyone can help it will be great
You didn't want to post your issue in that thread?
I'm having same problem.. Also same problem for bam ROM
Sent from my XT1032 using xda app-developers app
managed to get out of the CM11 bootloop after applied Fix Permissions (or something similar) in TW's Custom Recovery.
Seems that only TW recovery can fix this through a permissions fix.
Got the same problem last night and the only thing to do to get it works was to re-flash the stock firmware, flash the recovery and reinstall the CM build. Latest build seems to be pretty good.
Simply wiping the cache before and after flash worked for me.
Sent from my XT1032 using Tapatalk
imxdot said:
Simply wiping the cache before and after flash worked for me.
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Not for me, sadly.
I've also tried to re-flash the rom through the recovery but the only fix that worked for me was to flash the stock firmware and then install the CM via recovery.
Same here, had difficulties getting Cyanogen to boot.
What I did is :
- roll back to stock 4.3 : http://forum.xda-developers.com/showthread.php?t=2546251 (yes, you can roll back, read the end of the post)
- allow OTA update to 4.4.2
- install CWM
- in CWM : format /system, /data and /cache, install cyanogen from ZIP, wipe dalvik cache
Mysteriously it worked like a charm after many unsuccessful tries and a softbrick ^^
Btw, no need to root the stock ROM to install CWM or a custom ROM, just skip this step
Do you have the XT1032 version?
xavier66 said:
Same here, had difficulties getting Cyanogen to boot.
What I did is :
- roll back to stock 4.3 : http://forum.xda-developers.com/showthread.php?t=2546251 (yes, you can roll back, read the end of the post)
- allow OTA update to 4.4.2
- install CWM
- in CWM : format /system, /data and /cache, install cyanogen from ZIP, wipe dalvik cache
Mysteriously it worked like a charm after many unsuccessful tries and a softbrick ^^
Btw, no need to root the stock ROM to install CWM or a custom ROM, just skip this step
Click to expand...
Click to collapse
I´m tired of the mess made it because of the three different Moto G versions, i'm waiting for official Recovery from CWM, maybe 3 months it's to early but I wanna try this method. (I hope to don´t hardbrick haha)
I was having the same problem with every rom i tried. After going back complete stock with Alonsoch's tool in the original Dev thread, I was then able to get past the boot on any rom
Sent from my XT1034 using Tapatalk
stuck in loop after installation
Hi everyone
I have tried to install cyanogen mode date : 23, 22 nightly roms on my moto g xt1033 KK vesion using twrp as well as cyanomod recoveries but after installation my phone stuck on boot window. I waited for 20 min but nothing happens. I read throgh so many posts and orignal rom thread and found that its supporting 4.3 and 4.4 both versions and I want to test it with only 4.4. (Dont want to downgread).. Any solution?
I am newbee and want to take part in rom devlopment as tester. Sorry if i asked somethin silly or may be twice.
sandeepg9 said:
Hi everyone
I have tried to install cyanogen mode date : 23, 22 nightly roms on my moto g xt1033 KK vesion using twrp as well as cyanomod recoveries but after installation my phone stuck on boot window. I waited for 20 min but nothing happens. I read throgh so many posts and orignal rom thread and found that its supporting 4.3 and 4.4 both versions and I want to test it with only 4.4. (Dont want to downgread).. Any solution?
I am newbee and want to take part in rom devlopment as tester. Sorry if i asked somethin silly or may be twice.
Click to expand...
Click to collapse
please use the thread for the ROM you have issues with.
thread closed