Database Info

Updating ROM with CWM just reverts to menu?

Hey,
I'm trying to install the [ROM] Team Tiamat Xoom Rom 2.2.2 - Moray [9/10/11].
I've got CWM installed (version recovery-Tiamat-R4c-100611-1150-cwm.img but also tried latest version from ROM Manager).
Each time i try to install the .zip it get's to opening package and then just exits to the CWM menu?
It's probably a common thing, but couldn't find anything from a search? Anyone got any ideas?

This has been covered many times so take the time to do a search.

Muffycheeks said:
This has been covered many times so take the time to do a search.
Click to expand...
Click to collapse
I had to thank you Muffycheeks for your excellent answer. I am not sure why you did not at least give an indication about where to find the answer or what the issue is? Lucky this was posted in Q&A and not in the dev thread!
I am new to Xoom (only got it since yesterday) and have managed to get the bootloader unlocked and custom recovery installed. For some reason when I reboot the device the recovery is flash back to 3e (I suppose this has been also debated millions of times but I cannot find it yet...)
I had been able to flash one of the custom roms but it gets stuck in bootscreen. I wiped everything I could think of and followed a couple of advices and still not working.
I am downloading the other rom (as far as I can tell there are only 2 customs with one of them based on the other one) and will see if that works.
Sorry Addicteddddd for highjacking your thread but I have been searching for a while until I found your thread and I thought my issues were over to find the standard helpful XDA answer. Some people might have had their device for years but some other are quite new to this.
K.
EDIT: It seems that one of the recoveries do not advise if a ZIP file is bad and therfore comes back with no message. I suppose this is why this is happening.
I downloaded 3 ZIP files and they are all corrput. Not sure what is happening here but anyway.

kar200 said:
I had to thank you Muffycheeks for your excellent answer. I am not sure why you did not at least give an indication about where to find the answer or what the issue is? Lucky this was posted in Q&A and not in the dev thread!
I am new to Xoom (only got it since yesterday) and have managed to get the bootloader unlocked and custom recovery installed. For some reason when I reboot the device the recovery is flash back to 3e (I suppose this has been also debated millions of times but I cannot find it yet...)
I had been able to flash one of the custom roms but it gets stuck in bootscreen. I wiped everything I could think of and followed a couple of advices and still not working.
I am downloading the other rom (as far as I can tell there are only 2 customs with one of them based on the other one) and will see if that works.
Sorry Addicteddddd for highjacking your thread but I have been searching for a while until I found your thread and I thought my issues were over to find the standard helpful XDA answer. Some people might have had their device for years but some other are quite new to this.
K.
EDIT: It seems that one of the recoveries do not advise if a ZIP file is bad and therfore comes back with no message. I suppose this is why this is happening.
I downloaded 3 ZIP files and they are all corrput. Not sure what is happening here but anyway.
Click to expand...
Click to collapse
I don't know if you used this guide but there is a bit of discussion of some issues regarding cwm recovery versions and some pitfalls while trying to flash.Check it out if you haven't
http://forum.xda-developers.com/showthread.php?t=1249798
Also, how are you downloading the file? Are you getting the right version? If you are using the R4c v3.2.0.0 it should be called solarnz, not tiamat. The guide has the correct link.

okantomi said:
I don't know if you used this guide but there is a bit of discussion of some issues regarding cwm recovery versions and some pitfalls while trying to flash.Check it out if you haven't
http://forum.xda-developers.com/showthread.php?t=1249798
Also, how are you downloading the file? Are you getting the right version? If you are using the R4c v3.2.0.0 it should be called solarnz, not tiamat. The guide has the correct link.
Click to expand...
Click to collapse
I just ralised tnat my sd card was screwed (very old 1gb i found lying around). The files on the pc were fine.
I used a different card and now typing from a custom rom! All good.
K.
Sent from my Xoom using xda premium

Need help to get my Infuse from GB to ICS then JB

I was wondering if someone could detail to me a sure-fire way to make the jump from GB to ICS. I've tried twice now and both times I got stuck booting into a blue CWM without being able to load a ROM at that point. I was able to boot Aroma but after trying to recover from there I got stuck at the Galaxy S screen. Yes I followed the instructions very carefully. Is there a way to do this via Odin or Heimdall?
Any help would be tremendously appreciated.

Stock GB with CWM > CM 9 flash twice first from red recovery and then again from blue > then JB.
Do a full wipe before and after all the flash.
I know u said u tried this way buy it did not worked for u just give it a try from scratch one more time.
Sent from my MB855 using Tapatalk 2

rkkaranrk said:
Stock GB with CWM > CM 9 flash twice first from red recovery and then again from blue > then JB.
Do a full wipe before and after all the flash.
I know u said u tried this way buy it did not worked for u just give it a try from scratch one more time.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
Thanks rkkaranrk. The one thing I didn't do in your instructions was a wipe before and after each flash. Instead I wiped once before I began. Could this be the problem? Is this a common problem? I've seen some mention the same issue in the Dark Knight ROM thread that said they have the same issue but wasn't sure this has to do with the ROM or the migration from GB to ICS in general.

It could be any thing which cause bootloop so its always better to wipe, I always do anand never faced any bootloops Just give it try.
Sent from my MB855 using Tapatalk 2

I'm going to give it a go today too. I've had a hard time convincing myself to leave Aeon though. It's been a rock solid / stable ROM..............

D-Trixxx said:
I was wondering if someone could detail to me a sure-fire way to make the jump from GB to ICS. I've tried twice now and both times I got stuck booting into a blue CWM without being able to load a ROM at that point. I was able to boot Aroma but after trying to recover from there I got stuck at the Galaxy S screen. Yes I followed the instructions very carefully. Is there a way to do this via Odin or Heimdall?
Any help would be tremendously appreciated.
Click to expand...
Click to collapse
it does sound as if you missed a step. OP states you wll get stuck at Galaxy S screen.
you then pull battery and reflash again along wth the wipes.
i did wipes in recovery, then on second flash (in Aroma) did the full wipe version. install went exactly as described.
loving 99.9% of the Paranoid Android ICS. may want to take that for a test drive for a bit first beings they can be similar from what i know (which isnt much) from flasing one of first versions of JB
thanx for all efforts in development, biting my lip on flashing JB.

captemo said:
it does sound as if you missed a step. OP states you wll get stuck at Galaxy S screen.
you then pull battery and reflash again along wth the wipes.
i did wipes in recovery, then on second flash (in Aroma) did the full wipe version. install went exactly as described.
loving 99.9% of the Paranoid Android ICS. may want to take that for a test drive for a bit first beings they can be similar from what i know (which isnt much) from flasing one of first versions of JB
thanx for all efforts in development, biting my lip on flashing JB.
Click to expand...
Click to collapse
Thanks for all the replies so far.
@captemo: I followed the instructions in the Dark Knight thread exactly but maybe those instructions need to be updated because they never mentioned multiple wipes. There is no mention of getting stuck @ Galaxy S screen either but that isn't what happened at first. It kept bootlooping into blue CWM. It was only after that I tried to recover with Aroma that I got stuck, probably not the the wisest move on my part however.
I will try the Paranoid ICS build next since it sounds like you have had success with it and it looks like a good one. Just so I am clear on doing this can you list the steps you took to load this ROM? I noticed there are two variants, one with and one without the Aroma installer.
Thanks in advance!

The Aroma installer is nice but in my opinion, based on my experience and reports from others it is too problematic on the Infuse. Would really suggest not using versions with it, at least not on your first flash.

Pony Express said:
The Aroma installer is nice but in my opinion, based on my experience and reports from others it is too problematic on the Infuse. Would really suggest not using versions with it, at least not on your first flash.
Click to expand...
Click to collapse
Thanks Pony. I'll heed that advice and wait on captemo has to say regarding the steps he took to upgrade. I really don't feel like recovering a third time.

D-Trixxx said:
Thanks Pony. I'll heed that advice and wait on captemo has to say regarding the steps he took to upgrade. I really don't feel like recovering a third time.
Click to expand...
Click to collapse
+ 10.

I had another thought, could Voodoo lagfix be the source of my issues? At the time I had the /Voodoo/disable-lagfix folder on my SDCard

D-Trixxx said:
Thanks Pony. I'll heed that advice and wait on captemo has to say regarding the steps he took to upgrade. I really don't feel like recovering a third time.
Click to expand...
Click to collapse
WOW, somebody waiting for MY advice??? are you sure you havent been sipping on grandpa's cough syrup?
Pony i'm sure has more experience than myself and is merely expressing experiences that others and maybe he himself have had. truth is every phone is different and will react different.
i do like the Aroma myself. allows you to install some apps automatically.
i did nothing special than follow OP slowly and carefully to the T. doing this, i have never had problems flashing anything.
if i do anything special it is carefully choosing what i wish to flash. when lookin for new ROM, i go to the last page and start reading backwards. that shows me the most recent problems and issues people may be having. if its a problem i cant handle, i dont flash.
i am not taking away from developers here because they are ALL amazing and i wish i could do some of these things. as for the Dark Knight rom, i download, but never flashed. i just didnt think the development was progressing enough for me.
thats just me.
good luck hope you like Paranoid Android. i like the tablet mode, though print can be small for old eyes like mine just changed the font to something BOLD.

captemo said:
WOW, somebody waiting for MY advice??? are you sure you havent been sipping on grandpa's cough syrup?
Pony i'm sure has more experience than myself and is merely expressing experiences that others and maybe he himself have had. truth is every phone is different and will react different.
i do like the Aroma myself. allows you to install some apps automatically.
i did nothing special than follow OP slowly and carefully to the T. doing this, i have never had problems flashing anything.
if i do anything special it is carefully choosing what i wish to flash. when lookin for new ROM, i go to the last page and start reading backwards. that shows me the most recent problems and issues people may be having. if its a problem i cant handle, i dont flash.
i am not taking away from developers here because they are ALL amazing and i wish i could do some of these things. as for the Dark Knight rom, i download, but never flashed. i just didnt think the development was progressing enough for me.
thats just me.
good luck hope you like Paranoid Android. i like the tablet mode, though print can be small for old eyes like mine just changed the font to something BOLD.
Click to expand...
Click to collapse
The reason I wanted your advice was because you had successfully made the jump from GB to ICS. The Paranoid thread assumes you are starting from ICS so there are no instructions to go from GB to ICS even thought the ICS ROMs are still there.

D-Trixxx said:
The reason I wanted your advice was because you had successfully made the jump from GB to ICS. The Paranoid thread assumes you are starting from ICS so there are no instructions to go from GB to ICS even thought the ICS ROMs are still there.
Click to expand...
Click to collapse
anybody on ICS or JB as made that jump, obviously with sucess. since Paranoids development has jumped to JB there are a couple of small differences in install (GAPPS for ex.) the first 80 pages still deal with the ICS developments of the ROM.
even though the OP has changed to address install of JB, if you go past the first couple of pages and all the congrats of the new ROM, you will get to where any of your questions will be answered. Scott and team are very attentive and if you read read read, questions and concerns are all addressed.
if then you are happy with ROM and are dying to try JB, i think page 80 is where JB discussion begins.

The GB to ICS process should be the same for any rom. You can use cm9 or uniyumaporn to get to ics and then flash jb.
First, be aware once you are in ICS, your recovery will be filled with rainbows due to the lack of GB bootloaders (I'm assuming you don't have those).
1) wipe data, cache, dalvik (format /system is optional)
2) flash ics rom
3) reboot (Not "reboot into recovery")
4) you should hang at kernel splash (galaxy s screen).. remove battery and use 3 finger combo to boot into recovery.
5) wipe again and flash
Sent from my sweet & buttery Infuse

I did this process two days ago. I went from factory att GB to ICS following the instructions for uniporn. Once I had uniporn fully booted and running I then rebooted back into CWM and followed the instructions in the cm10 thread.
The only thing to watch for is in the uni instructions. It still says to flash gapps. You don't have to do that now because they are included in build 40.
How did you update to GB by the way? That will tell us if you have GB or froyo boot loaders
Sent from my SGH-I997 using xda app-developers app

Goneeuro said:
I did this process two days ago. I went from factory att GB to ICS following the instructions for uniporn. Once I had uniporn fully booted and running I then rebooted back into CWM and followed the instructions in the cm10 thread.
The only thing to watch for is in the uni instructions. It still says to flash gapps. You don't have to do that now because they are included in build 40.
How did you update to GB by the way? That will tell us if you have GB or froyo boot loaders
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
Hi Goneeuro,
I just saw your post but I did exactly what you did. Basically I read the instructions of a bunch of ROMS and decided to follow uniporns steps and it worked just fine including the gapps installation. Seems to be working fine still but I wonder if its a matter of time if I see issues.
I don't recall how I went to GB, its been so long ago but I don't have the rainbow CWM. Probably because I loaded them during a recovery.
Anyway all is good now. Big THANKS to all of you.
D

Dude thank you so much!
captemo said:
it does sound as if you missed a step. OP states you wll get stuck at Galaxy S screen.
you then pull battery and reflash again along wth the wipes.
i did wipes in recovery, then on second flash (in Aroma) did the full wipe version. install went exactly as described.
loving 99.9% of the Paranoid Android ICS. may want to take that for a test drive for a bit first beings they can be similar from what i know (which isnt much) from flasing one of first versions of JB
thanx for all efforts in development, biting my lip on flashing JB.
Click to expand...
Click to collapse
Really awesome I've been working on this for like 4 hours and all it took was pulling the battery instead of rebooting to get out of the bootloop. really appreciate it.

[Q] Omega custom ROM installation GT-N8013 installation bar stuck at 0%

Hey all,
With great hesitancy I am asking this question, as I know people generally frown upon questions that has already been asked before. But I have searched on this forum and online and have not come across a solution for my particular device/problem. I own a Samsung Galaxy Note 10.1 GT-N8013 and decided to install the Omega custom ROM. I followed the instructions from DroidView's Omega installation webpage (sorry could not post link as this is my first post, but a google for Omega custom ROM galaxy note 10.1 would give the link).
After selecting the apps that I wanted installed, I tapped on the install button. I saw a bunch of "Wiping" output (preload/dalvik cache/cache) formating system. However, the installation bar is not moving past 0.00%. The screen is not frozen as I can see the color move from left to right in the installation bar, but bar itself is not moving. It has been like that for the past 1.5 hours during which I have been searching for a solution on what to do next. As the installation instructions suggested, I made backup of my current ROM on my external SD card. Preferably, I would like to try the installation process again, but I am not sure how to get out of this "installing" screen. If using a custom ROM is not possible for me, I would like to know how to go back to the stock ROM from the backup I made.
Any help is greatly appreciated. Also, I hope I am at the right place to ask this question, if not some please let me know.
Thanks,
Shaun.

Update:
After waiting for nearly 2 hours, I pressed the VolumeUP+Power button to get to the recovery menu to try to do the installation process again. It worked and I went through the whole procedure again. However, this time the screen froze at the "Select apps you want to install - Default install or remove bloatware" screen after I tapped on remove bloatware. I once again pressed VolumeUp+Power button to get back to the recovery mode.
Now all I see is my the "Samsung Galaxy Note 10.1" logo on my screen and it just sits there. If I press the power button long enough the device seems to turn off but the logo comes on back again on my screen. Does this mean I have bricked my device??? Is there way to get back to a working version of my tablet again?
Thanks,
Shaun.

Update:
I have gotten back on the recovery mode and restored the stock ROM. I am going to try to install the Omega custom ROM again. I will update here how it goes.
Sorry to have so many posts in a short while, I am not trying to bump my own posts. I am just trying to provide as much information as possible on the stuff that I have tried so that people who are kind enough to help me will know exactly what I have been upto. If this is a problem please let me know and I will tone down my posting frequency.
Thanks,
Shaun.

Which recovery r u using? Ive had good luck with twrp.

rail205 said:
Which recovery r u using? Ive had good luck with twrp.
Click to expand...
Click to collapse
I am using CWM 6.0.3.1. Forgive me, I new at this, but does this mean I need to root my tablet again and install a new recovery if I want to use this TWRP? Also, isnt the problem with Arora and not the recovery? Do you think changing the recovery will solve this problem?

Hi mate...
First., THIS is the Official thread of Omega for the Note 10.1... so please download the rom HERE to be sure..
Second., not all recoveries works with aroma., so i suggest you use Philz instead of cwm....
flash Philz first then flash Omega....
Installation Instructions can be found HERE..

NadMaj said:
Hi mate...
First., THIS is the Official thread of Omega for the Note 10.1... so please download the rom HERE to be sure..
Second., not all recoveries works with aroma., so i suggest you use Philz instead of cwm....
flash Philz first then flash Omega....
Installation Instructions can be found HERE..
Click to expand...
Click to collapse
Hey,
Thanks for your reply. I guess I am going for the philz_touch_5.08.5-n8000.zip. Also can just flash this directly from CWM just like any other zip?
I'm also guessing the backups from the recoveries are not compatible with each other.

shaun_android said:
Hey,
Thanks for your reply. I guess I am going for the philz_touch_5.08.5-n8000.zip. Also can just flash this directly from CWM just like any other zip?
I'm also guessing the backups from the recoveries are not compatible with each other.
Click to expand...
Click to collapse
yes.. you can also download the tar file and flash it via Odin/Mobile Odin..... then flash Omega and that's it...
for further questions regarding Omega you can ask in the Omega thread..

Update:
Thanks all for the help. I installed Philz and was able to install the Omega custom ROM on my galaxy note 10.1.

[Resolved] [Q] Karbonn A1+ Soft Brick - Backup ROM Needed

Hi There,
I am in a crisis situation here. I have owned this Karbonn A1+ for about 10 months now. Never attempted anything as I dont use it majorly. Recently I rooted it with Z4root. It was successfull.
Later as i was going through the forums about Karbonn, found that there is a custom ROM (Xperia ROM) for it and hence went ahead in trying the same. Since then, the phone will not go beyond the Karboon Logo. I tried various methods by trying to flash the stock from http://forum.xda-developers.com/showthread.php?t=2279278
Even that didnt help. Screen is stuck at checking Baudrate but does nothings even after 30 min and I still have Karbonn logo on phone. then I found http://forum.xda-developers.com/showthread.php?t=2405153
When I tried that the phone goes beyond the logo and gives a white screen and thats it. when i press the power button the screen goes off and on. so i am guessing the phone booted to OS but not giving me any thing to work on.
Meantime I learned how to create custom ROM. I built one but even that doesnt help as I am again stuck at the Karbonn Logo.
Presently I am able to go to CWM ver 6.0.3
The phones H/W ver is 4.0.0 and the S/W version is 1.0.6
Can somebody help me with the flashable version of Stock Rom or the Backup....
Sorry for a Verbose thread, I tried to be as clear as I can....

JadhavN said:
Hi There,
I am in a crisis situation here. I have owned this Karbonn A1+ for about 10 months now. Never attempted anything as I dont use it majorly. Recently I rooted it with Z4root. It was successfull.
Later as i was going through the forums about Karbonn, found that there is a custom ROM (Xperia ROM) for it and hence went ahead in trying the same. Since then, the phone will not go beyond the Karboon Logo. I tried various methods by trying to flash the stock from http://forum.xda-developers.com/showthread.php?t=2279278
Even that didnt help. Screen is stuck at checking Baudrate but does nothings even after 30 min and I still have Karbonn logo on phone. then I found http://forum.xda-developers.com/showthread.php?t=2405153
When I tried that the phone goes beyond the logo and gives a white screen and thats it. when i press the power button the screen goes off and on. so i am guessing the phone booted to OS but not giving me any thing to work on.
Meantime I learned how to create custom ROM. I built one but even that doesnt help as I am again stuck at the Karbonn Logo.
Presently I am able to go to CWM ver 6.0.3
The phones H/W ver is 4.0.0 and the S/W version is 1.0.6
Can somebody help me with the flashable version of Stock Rom or the Backup....
Sorry for a Verbose thread, I tried to be as clear as I can....
Click to expand...
Click to collapse
All you have to do (given your situation) is perform a complete wipe (using a custom recovery: in your case, CWM) before trying to install anything. Remember, you need to install the specified/correct Kernel to work with a given ROM.

jay_r95 said:
All you have to do (given your situation) is perform a complete wipe (using a custom recovery: in your case, CWM) before trying to install anything. Remember, you need to install the specified/correct Kernel to work with a given ROM.
Click to expand...
Click to collapse
Thanks for the reply. However I am well aware of wiping data before installing, and the same was done before trying the Xperia ROM. Presently I am in need of a Flash-able stock ROM or Custom ROM or even a backup that will work with the hardware and software versions I have....

JadhavN said:
Thanks for the reply. However I am well aware of wiping data before installing, and the same was done before trying the Xperia ROM. Presently I am in need of a Flash-able stock ROM or Custom ROM or even a backup that will work with the hardware and software versions I have....
Click to expand...
Click to collapse
Well, I hope you find what you are looking for. But I can say, after downloading the Xperia ROM for your device, I wasn't able to find a Kernel in it. As I said in the previous post, you need to install the specified/correct Kernel to work with a given ROM. Just remember that the next time you go ahead and flash something.

some questions.
can you still boot to recovery?
did you took complete backup before messing with it (using cwm)?
what is h/w and s/w version IN the phone and behind your mobile battery?
Sent from my A1+ using xda app-developers app

.::MAX::. said:
some questions.
can you still boot to recovery?
did you took complete backup before messing with it (using cwm)?
what is h/w and s/w version IN the phone and behind your mobile battery?
Sent from my A1+ using xda app-developers app
Click to expand...
Click to collapse
Thanks for replying back MAX. i did take a nandroid backup before flashing. however i failed to verify if it actually did it or not. when i screwed up and looked for restore files they werent there.
yes i am able to boot to recovery via CWM
The phones H/W ver is 4.0.0 and the S/W version is 1.0.6

jay_r95 said:
Well, I hope you find what you are looking for. But I can say, after downloading the Xperia ROM for your device, I wasn't able to find a Kernel in it. As I said in the previous post, you need to install the specified/correct Kernel to work with a given ROM. Just remember that the next time you go ahead and flash something.
Click to expand...
Click to collapse
Hi Jay, My apologies if my previous statement sounded like a teenager. this thing is just driving me crazy as i never had any issues with other phones. i have rooted Motorola, samsung, htc and never faced any issues like this.
what you are saying about kernal totally makes sense, however i was under the impression that boot.img may contain this already and tried putting that file in the ROM and flashed it when it didnt work for first time. which again didnt help much. if you know how kernals works. Please tell me what to look for in them....

JadhavN said:
Hi Jay, My apologies if my previous statement sounded like a teenager. this thing is just driving me crazy as i never had any issues with other phones. i have rooted Motorola, samsung, htc and never faced any issues like this.
what you are saying about kernal totally makes sense, however i was under the impression that boot.img may contain this already and tried putting that file in the ROM and flashed it when it didnt work for first time. which again didnt help much. if you know how kernals works. Please tell me what to look for in them....
Click to expand...
Click to collapse
The problem is not on your behalf mate; it's just that the ROM you obtained didn't come with all the necessary/correct files. I also presume Karbonn is not a very big company (I've personally never heard of it), and it's immediately obvious that there are not many developers that are working on this device - probably why you can't find any proper ROMs, kernels etc.
I guess I'm not really helping you in any way and I'm sorry about that - I don't know of any ROMs or kernels for your device. When I first replied to your thread, I was under the impression that you had that covered. However, I can say, loosely, that there are two main types of kernels - one type for proprietary OEM ROMs, and the other type for AOSP ROMs. Most custom ROMs are based on AOSP (I am under the impression that the ROM you obtained is too), so OEM kernels will not work these ROMs. I really hope this helps, in the future at least, if not now.

Hi Max, any update?

jay_r95 said:
The problem is not on your behalf mate; it's just that the ROM you obtained didn't come with all the necessary/correct files. I also presume Karbonn is not a very big company (I've personally never heard of it), and it's immediately obvious that there are not many developers that are working on this device - probably why you can't find any proper ROMs, kernels etc.
I guess I'm not really helping you in any way and I'm sorry about that - I don't know of any ROMs or kernels for your device. When I first replied to your thread, I was under the impression that you had that covered. However, I can say, loosely, that there are two main types of kernels - one type for proprietary OEM ROMs, and the other type for AOSP ROMs. Most custom ROMs are based on AOSP (I am under the impression that the ROM you obtained is too), so OEM kernels will not work these ROMs. I really hope this helps, in the future at least, if not now.
Click to expand...
Click to collapse
So this is the change i see. when i connect my phone to computer and open shaume or MyMobiler. i am able to see the OS. i am able to go to settings to but later the inputs wont work.... any idea...???

try this
http://forum.xda-developers.com/showthread.php?t=2405153
---------- Post added at 06:02 AM ---------- Previous post was at 06:00 AM ----------
try this
http://forum.xda-developers.com/showthread.php?t=2405153

I had a link of your solutions but its not working.
you should search for your backup if it is successfully done.
because your sw version is 1.0.6 and xperia rom is based on 2.0.2.
so the your old kernel is not accepting new rom.
so you should try link given by zerocool.( I was going to provide you the same link)
Its best rom until now. I have no issues with it. Just replace the kernel and bootloader to your kernel from your nandroid backup.
But since you dont have one, you should try it whole as it is.
Sent from my A1+ using xda app-developers app

.::MAX::. said:
I had a link of your solutions but its not working.
you should search for your backup if it is successfully done.
because your sw version is 1.0.6 and xperia rom is based on 2.0.2.
so the your old kernel is not accepting new rom.
so you should try link given by zerocool.( I was going to provide you the same link)
Its best rom until now. I have no issues with it. Just replace the kernel and bootloader to your kernel from your nandroid backup.
But since you dont have one, you should try it whole as it is.
Sent from my A1+ using xda app-developers app
Click to expand...
Click to collapse
So it was a Kernel issue after all. I hope JadhavN finds what he is looking for. :good:

zerocool420 said:
try this
http://forum.xda-developers.com/showthread.php?t=2405153
---------- Post added at 06:02 AM ---------- Previous post was at 06:00 AM ----------
try this
http://forum.xda-developers.com/showthread.php?t=2405153
Click to expand...
Click to collapse
Thanks zerocool420
this is the same link i tried and its the same. it boot beyond the logo and all i have is a white screen.

.::MAX::. said:
I had a link of your solutions but its not working.
you should search for your backup if it is successfully done.
because your sw version is 1.0.6 and xperia rom is based on 2.0.2.
so the your old kernel is not accepting new rom.
so you should try link given by zerocool.( I was going to provide you the same link)
Its best rom until now. I have no issues with it. Just replace the kernel and bootloader to your kernel from your nandroid backup.
But since you dont have one, you should try it whole as it is.
Sent from my A1+ using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply max. however i tried everything to unpack my boot.img but it woudnt work for some reason. most of the posts i found were users using linux. i am working on windows. even my adb started acting up it wont start the deamon now.... so i have no access to kernal

jay_r95 said:
So it was a Kernel issue after all. I hope JadhavN finds what he is looking for. :good:
Click to expand...
Click to collapse
Hi Jay, thanks for following up :good:

There is nothing left to extract from your phone since you have flashed everything from that backup rom. :banghead:
Now there is only one way to search for older roms, extract bootloader and kernel, replace in that rom and try to restore.
You can start from google.
There are some old files in karbonn a1+ wiki post, you can try them.
Also dont forget to replace recovery file to your working cwm recovery.
Sent from my A1+ using my finger tips.

is there no1 who has the backup of flashable stock ROM??

How do you start to cwm
JadhavN said:
Hi There,
I am in a crisis situation here. I have owned this Karbonn A1+ for about 10 months now. Never attempted anything as I dont use it majorly. Recently I rooted it with Z4root. It was successfull.
Later as i was going through the forums about Karbonn, found that there is a custom ROM (Xperia ROM) for it and hence went ahead in trying the same. Since then, the phone will not go beyond the Karboon Logo. I tried various methods by trying to flash the stock from http://forum.xda-developers.com/showthread.php?t=2279278
Even that didnt help. Screen is stuck at checking Baudrate but does nothings even after 30 min and I still have Karbonn logo on phone. then I found http://forum.xda-developers.com/showthread.php?t=2405153
When I tried that the phone goes beyond the logo and gives a white screen and thats it. when i press the power button the screen goes off and on. so i am guessing the phone booted to OS but not giving me any thing to work on.
Meantime I learned how to create custom ROM. I built one but even that doesnt help as I am again stuck at the Karbonn Logo.
Presently I am able to go to CWM ver 6.0.3
The phones H/W ver is 4.0.0 and the S/W version is 1.0.6
Can somebody help me with the flashable version of Stock Rom or the Backup....
Sorry for a Verbose thread, I tried to be as clear as I can....
Click to expand...
Click to collapse
Bro I am not able to even boot to CWM, how do you do that

JadhavN said:
Hi There,
I am in a crisis situation here. I have owned this
evn I hv the same handset with same h/w & s/w vrsion... I flashed d experia rom too.... evn v1 rom & custm rom too... nthng happnd now it says.... SD-EXD not found.... wht to do plz hlp if sm1 knows
---------- Post added at 04:51 PM ---------- Previous post was at 04:07 PM ----------
JadhavN said:
Hi There,
I am in a crisis situation here. I have owned this Karbonn A1 for about 10 months now. Never attempted anything as I dont use it majorly. Recently I rooted it with Z4root. It was successfull.
Later as i was going through the forums about Karbonn, found that there is a custom ROM (Xperia ROM) for it and hence went ahead in trying the same. Since then, the phone will not go beyond the Karboon Logo. I tried various methods by trying to flash the stock from http://forum.xda-developers.com/showthread.php?t=2279278
Even that didnt help. Screen is stuck at checking Baudrate but does nothings even after 30 min and I still have Karbonn logo on phone. then I found http://forum.xda-developers.com/showthread.php?t=2405153
When I tried that the phone goes beyond the logo and gives a white screen and thats it. when i press the power button the screen goes off and on. so i am guessing the phone booted to OS but not giving me any thing to work on.
Meantime I learned how to create custom ROM. I built one but even that doesnt help as I am again stuck at the Karbonn Logo.
Presently I am able to go to CWM ver 6.0.3
The phones H/W ver is 4.0.0 and the S/W version is 1.0.6
Can somebody help me with the flashable version of Stock Rom or the Backup....
Sorry for a Verbose thread, I tried to be as clear as I can....
Click to expand...
Click to collapse
i'v the same device with d same problem I tried many roms frm d forum .. nthng has worked fr me.... if u got a solution thn plz tell me... I m getting an error SD-EXT not found.... and I m unable to mount SD-EXT under CWM menu
Click to expand...
Click to collapse

[Q] [Question][//Solution] Reverting from Oxygen OS to CM11 using CM Installer

I'm just curious and haven't browsed XDA for a while. My curiosity got me to the point of posting in G+ and Twitter about CM installer reverting Oxygen OS to CM11. So many people installed Oxygen OS and because of missing features, they want to revert back to CM. I manually flash and root my devices. I know about CM installer which installs a stable version on a device without you doing anything but I've never used it. My question is, can a CM installer be used to revert back to CM11 without any issues. I don't have a problem flashing Oxygen or reverting or even bricking my device, it's just that I'm curious. If somebody could answer this, it will help a lot of newbies and others who are afraid of bricking their device or doesn't feel safe to go with the hand on method of flashing, fastboot techniques etc... and clear my curiosity too.

You can't just use CM Installer. We're already discussing this here:
http://forum.xda-developers.com/oneplus-one/general/oxygen-os-released-download-t3072259
See the OP for instructions.

CafeKampuchia said:
You can't just use CM Installer. We're already discussing this here:
http://forum.xda-developers.com/oneplus-one/general/oxygen-os-released-download-t3072259
See the OP for instructions.
Click to expand...
Click to collapse
I know how to flash and root.. I'm curious about this one and this hasn't been answered yet..

caspertechno said:
I know how to flash and root.. I'm curious about this one and this hasn't been answered yet..
Click to expand...
Click to collapse
If you read up on how to downgrade from OxygenOS or even CM12, you'll find out why you can't just reflash CM11 with CM Installer. Both O2OS and CM12 flash a new modem that won't work with CM11. The modem has to be reverted manually.

CafeKampuchia said:
If you read up on how to downgrade from OxygenOS or even CM12, you'll find out why you can't just reflash CM11 with CM Installer. Both O2OS and CM12 flash a new modem that won't work with CM11. The modem has to be reverted manually.
Click to expand...
Click to collapse
ok.. now, just assume that can be done by a newbie.... can someone downgrade with or without the modems? or might get stuck in a boot loop ?

caspertechno said:
ok.. now, just assume that can be done by a newbie.... can someone downgrade with or without the modems? or might get stuck in a boot loop ?
Click to expand...
Click to collapse
Anything can be done by a newbie willing to read, and that's how one goes from being a newb to becoming proficient. That's why I don't like tools and video tutorials--more often than not, they leave people ignorant.
Yes, it will bootloop because the Lollipop modem doesn't play nice with CM11/11s.

CafeKampuchia said:
Anything can be done by a newbie willing to read, and that's how one goes from being a newb to becoming proficient. That's why I don't like tools and video tutorials--more often than not, they leave people ignorant.
Yes, it will bootloop because the Lollipop modem doesn't play nice with CM11/11s.
Click to expand...
Click to collapse
I agree... I don't like tools either.. But I have seen people asking on FB if the service center can do an upgrade for them... this installer if it properly works could help those guys... does the installer wipes everything and installs them from scratch, the modems too, I meant. I haven't used it, that's why...

I'm not getting proper answers here or anywhere.. sorry guys... It's already understood that Oxygen and CM12 flashes a new modem, but when the installer flashes a stable version, will it remove or wipe everything and start from scratch? Oxygen OS may be a different thing, if and when CM12 arrives, which is going to be a stable one, can the installer be used to switch...?