Related
Can someone help please? I installed CWM Recovery thru ROM Manager. Rebooted in recovery to back up my ROM and now I can't get out of recovery. Every time I select Reboot System it reboots me into recovery.
Try here (if you can use NVFlash)
http://forum.xda-developers.com/showthread.php?t=1519635&highlight=boot+into+cwm
Like many others, When I saw the thread over in the Dev section about the 5.5.0.4 recovery, I jumped right in and fired up Rom Manager before reading any further in the thread.
Unlike many others, I don't get the same results. My TF101 reboots to the OS with no problem. However trying to reboot to recovery from recovery doesn't work. I have to hold the vol. down button just like a cold boot into recovery.
The only difference might be, that I had stock recovery prior to installing 5.5.0.4, due to having to recover from another soft brick condition after trying to install the CM9 Nightly that is now available over on the official Clockworkmod site. That one had failed miserably for my device.
Good luck with solving your problems with the new recovery. Wish I could explain exactly why mine seemed to work as advertised when most others didn't. But I don't know.
I do have the problem with the Removable MicroSD not being visible. Only the built in "Fake" SD Card.
Update:
I now have the reboot into recovery problem. I used the wipe data option from the VOL DWN/PWR button start up, and now have that annoying boots into recovery problem like everyone else. I hope that and the SD card problem gets fixed in the next version.
Thanks, got everything back to normal with NVFlash method I found by watching this :http://www.youtube.com/watch?feature=player_embedded&v=VMHXeYMgPy4
Lesson learned!! :/
Curious where the thread in the Dev section went to, I cant find it this morning...
Unfortunately, some of us cannot use NVFLash to fix this problem.
So, is it too much to ask that the Dev who wrote Rom Manager and CWM actually look in to this for us?
I too installed the newer CWM through Rom Manager and need to cold boot to get in to the OS otherwise it recovery boot loops.
sandiegopaneraiguy said:
Curious where the thread in the Dev section went to, I cant find it this morning...
Unfortunately, some of us cannot use NVFLash to fix this problem.
So, is it too much to ask that the Dev who wrote Rom Manager and CWM actually look in to this for us?
I too installed the newer CWM through Rom Manager and need to cold boot to get in to the OS otherwise it recovery boot loops.
Click to expand...
Click to collapse
Thread was closed. I was on it this morning and wanted to post a reply saying NV Flash work for me and I couldn't because it said the thread was closed.
I read the whole thing and apart from NV Flashing the was no other solution
How do you know you can't NVFlash?
yea , this morning the thread in the Dev section went to general , and now closed.
Perhaps we should follow this until everything is clarified.
the nvflash only work for b60 and some b70 tablets , most of b70 and b80 cant be flashed with this tool
I'm working on something to fix this, but I still need a little more testing.
gee one said:
I'm working on something to fix this, but I still need a little more testing.
Click to expand...
Click to collapse
ok, then waiting
any clue where to attack the problem?
Some people reported the new recovery worked when flashed over stock recovery.
any help you can supply on this would be greatly appreciated. it's very uncomfortable not being able to count on your recovery.
Sent from my Inspire 4G using XDA App
robb13 said:
Some people reported the new recovery worked when flashed over stock recovery.
Click to expand...
Click to collapse
too late for us
I was up until 1am following the thread and posting my process, specs.
I am even more curious as to how the thread which was still pretty calm turned in to something that deserved being deleted.
In any event, I think we all understand that what we do is at our own risk. But CWM and Rom Manager have been the gold standard of reliability for quite some time. Once something is a trusted means by which to do something its even more disappointing to see that it no longer works.
the first post was moved because it was not exactly a development post
then, in the general section, I do not know why it closed, there is no explanation
so if microsd is not recognized, i can install rom from internal, right?
gandda12 said:
so if microsd is not recognized, i can install rom from internal, right?
Click to expand...
Click to collapse
Install what??
Sent from my Transformer TF101 using XDA Premium HD app
yeah, check out the troubleshooting thread here
http://forum.xda-developers.com/showthread.php?t=1530337
Hi everybody,
after endless nights and days of experimenting and crying I ask for your help.
My Aim: rooting my HTC One S C2.
So here is my story:
In my first attempt I unlocked my bootloader and tried to put a Custom Recovery on my phone. It failed. I got always stuck at the HTC screen with the red writing underneath the logo ("This build is for ...").
I then found out that I need the superboot.bat to root my phone.
So I proceeded to re-lock my phone and put a RUU on it to get back to the original Recovery.
All went well, so I unlocked my phone again via htcdev.com.
After that I tried to run the superboot.bat but again I am stuck at the HTC screen with the red writing!
I know that this screen should only appear for a few seconds and the phone should go into recovery but I am always stuck endless in this screen. To get out of it I have to soft reset my phone.
So I am not able to root it.
In a video I saw that on other phones the HTC screen with red writing has some kind of a "loading bar" on the upper right which appears after trying to access the recovery.
Well this bar doesn't even appear on my phone
Please help me I really don't know what to do further
same issue here, so subscribing to thread!
If you can get to download mode try to flash stock firmware with Odin. Search for a guide on youtube.
--------------------------------------------
Sent from my GT-S5830 running ImaGinary ICS.
Thank if it helped.It's there for a reason
Ähm isn't Odin for Samsung devices?
This is about HTC... Or does it work for both?
i recommend reading through this guide to rooting the one s. i've rooted quite a few phones using this method and it has worked flawlessly every time
http://forum.xda-developers.com/showthread.php?t=1583427
@HidaKureku - thats where i've got stuck; end of part two.
the recovery image seems to flash fine (both of them), and i've done the CWM recovery multiple times (some sites sugest that it works on the second attempt).
try to boot to recovery, and as per the OP it just sits there saying that it's for "This build is for HTC use only..." or whatever it says. no further. I've left it for 10mins in this state have have to power it off.
i have found that when i boot back to the UK retail ROM, it comes up with an error and wants to send it to HTC (i haven't yet been able to grab the error though).
has anyone sucessfully flashed recovery with the hboot 9.02.0001 image? i've seen a post on modaco with a user having the same problems as in this thread....
are you sure you're model has the S4 processor? if not, try this thread
http://forum.xda-developers.com/showthread.php?t=1785777&highlight=twrp
looks like i'm on the s3 version! twrp2 doesn't work either - same issue. (using openrecovery-twrp-2.2.2.0-ville.img)
seems the UK is one of these 'select' countries.
anyway - even an S3 compatible recovery isnt working....
I hope in not threadjacking here. @OP - if im intruding let me know and i'll create my own thread
No you are not intruding as I have exactley the same problem as you!
I'm glad that I'm not the only one I started to think I'm doing something completely wrong.
It's like the stock recovery is damaged even with the RUU version.
I just cannot get past this screen with the red warning!
My HTC One S is kind of new (about 3 weeks old). Maybe something changed with new models?
good news; i'm recovery-ed
you need 'openrecovery-twrp-2.2.2.1-villec2.img'.
It was 'tricky' to find, as the 'villec2' image doesnt appear to have any public links. As per the thread http://forum.xda-developers.com/showthread.php?t=1785777, Get 'goomanager', allow it to find and download recovery image, however, it wont sucessfully apply with goomanager (you dont have root yet).
It will download this recovery image to to /mnt/sdcard/goomanager/ (you can change/confirm it in goomanager menu options)
mount storage & copy this to your computer. Use fastboot to flash as per the unlock/recovery/root guide.
i dont mind hosting the file, but the above should be the quickest way
Yes!!!
That's it!!
Thank you so much
You made my day
Thread can be marked as solved!
now that you know you have the s3 processor be careful which roms you flash, make sure they are compatible with your version. the rom i'm running (check my signature for the link) is supposed to be compatible with both. but just read carefully and flash responsibly
HidaKureku said:
now that you know you have the s3 processor be careful which roms you flash, make sure they are compatible with your version. the rom i'm running (check my signature for the link) is supposed to be compatible with both. but just read carefully and flash responsibly
Click to expand...
Click to collapse
Thanks for the heads up, although that JB ROM in your sig says S4 in the title (thats about as far as i got )
@Schlengge - glad your sorted too i didnt even realise i was on s3 untill tonight; i thought all UK HOS's were s4's - seems not.
yeah XD i went back and looked at it and realized i got it confused with one rom i saw that was supposedly compatible with both processors (which struck me as odd) but there are a few roms out there for the s3, sadly not as many as for the s4, but you should be able to find one you're happy with. best of luck
veehexx said:
good news; i'm recovery-ed
you need 'openrecovery-twrp-2.2.2.1-villec2.img'.
It was 'tricky' to find, as the 'villec2' image doesnt appear to have any public links. As per the thread http://forum.xda-developers.com/showthread.php?t=1785777, Get 'goomanager', allow it to find and download recovery image, however, it wont sucessfully apply with goomanager (you dont have root yet).
It will download this recovery image to to /mnt/sdcard/goomanager/ (you can change/confirm it in goomanager menu options)
mount storage & copy this to your computer. Use fastboot to flash as per the unlock/recovery/root guide.
i dont mind hosting the file, but the above should be the quickest way
Click to expand...
Click to collapse
well, thanks for that advice. It is kinda confusing to find a recovery for c2 version of the ONE S, cause any other recovery will not work with it. The twrp-team should definatly add the link to that on their website.
I just wanted to share the big mistake I made because I didn't realize that there were more then one variants of my phone...
My wife bought me a new HTC One X for Christmas at full retail so we didn't have to extend our contract. I activated it December 26th.
I rooted it the same day and unlocked the bootloader the following day with no problems.... I didn't do anything else to it for 3 weeks.
Night before last I followed instructions I found online here: http://theunlockr.com/2012/04/28/how-to-install-clockworkmod-touch-recovery-on-htc-one-x/ to install Clockwork mod.
Everything seemed to install and everything seemed fine until I got to the end where I was to type in the command prompt to reboot. The phone shut down and will not reboot. No charge indicator anymore nothing! Won't even go into bootloader now with the Vol- and power button.
After all this I realized (thanks to members on here) that I had installed the wrong version of clockwork mod... I installed the version for the endeavoru when I appearently have something else.
So it probably is/was a stupid mistake on my part for not researching more....I just wanted to tell the other noobs doing this stuff to just please read read read!!!!
I have rooted and replaced the ROM's on all my previous phones and tablets with no problem but I do not do this everyday....Just when I get a new phone so I guess I got cocky and just assumed this one would be just as easy....
So I now have a 3 week old $599.99 paper weight.....
Please be careful and avoid the same mistake I made....
I find myself saying this over and over again on this forum: Don't Google around to random websites for phone mods.
This is a perfect example why. Those websites are not well organized, and therefore will easily mislead you into installing mods to your phone that are not meant for your version of the One X.
Plus, almost all of these "unlock" or "root" webites just steal content from XDA. Look at the webpage the OP linked. It just gives credit by giving a link that goes right back here to XDA. These random websites don't create their own content, they just steal from XDA, and add a few sentences of text that any moron can type, and call the work theirs.
Stick to XDA. As long as you are in the forum that says "AT&T", any ROMs, mods, etc. you find will be safe for the AT&T version of the One X, and its other dual core S4 variants.
There are a few other reputable websites with Android mods. But unless you know for a fact they are legit, its better to assume they are not, and stick to XDA.
Its really that simple.
I agree however I didn't just "Google" the recovery install instructions. I got to this page from a link in an XDA post I had read. Problem was I was apparently in the wrong HTC ONE X Forum. The instructions listed on the site are correct for the "Other" version of the phone.
It's an easy mistake to make with the way this site delivers a search. Example: Go up to the top of the page where it has a search box and says "Find your device"
Type in HTC ONE X. Look at which model the search returns. The International model, Not our AT&T version. Granted I should of read a little more closely, I didn't. The picture was my phone so I scrolled down and began reading threads.
If there are more then one variant of the same phone then both should appear when you search for a device so we can pick the correct version. I was unaware there were different versions of the HTC One X until today....
so it is what it is, I can't go back and do it all over and It's been a very expensive lesson learned so my post was to encourage other noobs to read read read so this doesn't happen to somebody else.
I'll eventually go buy another One X and might even go extend my contract and get one sooner.....either way, next time I'll know.
(Going back to my shattered screen Inspire has not been a pleasant experience, makes me really miss the One X)
Take care.
Man that sucks soooooo bad... Which rom did you pick? It sucks you used cwm.. If you would have used twrp there's a 94% chance it would have just failed instead of flashing.... Sorry for your luck bro.
Sent from my One X using Tapatalk 2
InflatedTitan said:
Man that sucks soooooo bad... Which rom did you pick? It sucks you used cwm.. If you would have used twrp there's a 94% chance it would have just failed instead of flashing.... Sorry for your luck bro.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
i think he bricked by flashing wrong cwm, not rom.
Honestly, how ridiculous is it that AT&T called the One XL variant the One X. Poor name choice has lead to problems like OP experienced.
ethantarheels123 said:
i think he bricked by flashing wrong cwm, not rom.
Click to expand...
Click to collapse
The problem isn't with cwm... You can run cwm all day everyday. Problem is its not supported, people been getting their sdcard wiped and what not. The problem with running cwm is that it doesn't restrict what's being flashed IF its not supported. He would have flashed an international rom, and cwm let it happen.
The international Devs worked in their ROMs to fail in twrp for our device..
Sent from my One X using Tapatalk 2
Hmm I wonder if the jet tool could help unbrick it, or is after flashing a wring recovery it to late? I don't have experience unbricking phones, just throwing out there.
scribed on my soon to be sold for note 2 one x!
jessepatty said:
I agree however I didn't just "Google" the recovery install instructions. I got to this page from a link in an XDA post I had read.
Click to expand...
Click to collapse
I find it odd that an XDA post links to the page you posted, since that page just links back to XDA, and doesn't seem to contain any unique or original content. That's why it seemed that you had "Googled" for that webpage, which seems to be what too many people are doing. My apologies since this is not the case, so maybe I should make my font smaller in the post above! ;-P
jessepatty said:
Problem was I was apparently in the wrong HTC ONE X Forum. The instructions listed on the site are correct for the "Other" version of the phone.
Click to expand...
Click to collapse
Yes, its still easy to confuse the variants on XDA, but at least XDA has the forums split apart at all, and makes the distinction between the dual and quad core versions (not the case on most other fly-by-night "root" or "unlock" websites).
Its too late for your current phone. But if you replace it with another AT&T One X, in the future just stick to this forum section and you will be safe from flashing the wrong mods: http://forum.xda-developers.com/forumdisplay.php?f=1538
Use the button "SEARCH THIS FORUM" button instead of the one at the top of the webpage, and you will always stay within the forum for the AT&T version.
And as I mentioned in my previous post, make sure the webpage you are looking at makes mention of "AT&T, Rogers etc." at the top of the page, and you are sure to be in the correct forum section.
You can also take a look at my Index thread, which has most any resource you will ever need: http://forum.xda-developers.com/showthread.php?t=1671237
Everything listed on this Index is specific to the dual core AT&T version and its variants.
jessepatty said:
If there are more then one variant of the same phone then both should appear when you search for a device so we can pick the correct version. I was unaware there were different versions of the HTC One X until today....
Click to expand...
Click to collapse
I've had 5 different smartphones/tablets going back to old Windows Mobile days, and every one of them has had multiple variants, some even having CDMA and GSM variants in the same forum section (but with seperate subforums). In the past you often had to be very careful and verify that you weren't flashing a ROm for the wrong variant (such as flashing a CDMA ROM on a GSM phone). The way XDA is organized for the variants of the One X is actually less confusing than many other devices.
Its good to keep in mind on any smartphone device to research as much as possible, and make sure you are doing mods specific to your version, before doing anything.
ethantarheels123 said:
i think he bricked by flashing wrong cwm, not rom.
Click to expand...
Click to collapse
InflatedTitan said:
The problem isn't with cwm... You can run cwm all day everyday.
Click to expand...
Click to collapse
Actually, if you flash CWM Touch Recovery from inside ROM Manager, you can get a brick. The version in ROM Manager is for endeavour, and it bricks largely for the same reason the endeavour roms do.
iElvis said:
Actually, if you flash CWM Touch Recovery from inside ROM Manager, you can get a brick. The version in ROM Manager is for endeavour, and it bricks largely for the same reason the endeavour roms do.
Click to expand...
Click to collapse
Oh... Ill respectively take my foot out of my mouth lol.
Sent from my One X using Tapatalk 2
To help everyone (Put this in your OP) if you want
Just type : fastboot getvar all
into the Command Prompt before you DO ANYTHING!
This will tell you all your information you need to know about your phone. For ex if its Evita or endevou
InflatedTitan said:
Man that sucks soooooo bad... Which rom did you pick? It sucks you used cwm.. If you would have used twrp there's a 94% chance it would have just failed instead of flashing.... Sorry for your luck bro.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Thanks, it is what it is
ethantarheels123 said:
i think he bricked by flashing wrong cwm, not rom.
Click to expand...
Click to collapse
This is true. I hadn't made it to installing a rom yet.
unitedatom said:
Honestly, how ridiculous is it that AT&T called the One XL variant the One X. Poor name choice has lead to problems like OP experienced.
Click to expand...
Click to collapse
I couldn't agree more (now) LoL
redpoint73 said:
I find it odd that an XDA post links to the page you posted, since that page just links back to XDA, and doesn't seem to contain any unique or original content. That's why it seemed that you had "Googled" for that webpage, which seems to be what too many people are doing. My apologies since this is not the case, so maybe I should make my font smaller in the post above! ;-P
Yes, its still easy to confuse the variants on XDA, but at least XDA has the forums split apart at all, and makes the distinction between the dual and quad core versions (not the case on most other fly-by-night "root" or "unlock" websites).
Its too late for your current phone. But if you replace it with another AT&T One X, in the future just stick to this forum section and you will be safe from flashing the wrong mods: http://forum.xda-developers.com/forumdisplay.php?f=1538
Use the button "SEARCH THIS FORUM" button instead of the one at the top of the webpage, and you will always stay within the forum for the AT&T version.
And as I mentioned in my previous post, make sure the webpage you are looking at makes mention of "AT&T, Rogers etc." at the top of the page, and you are sure to be in the correct forum section.
You can also take a look at my Index thread, which has most any resource you will ever need: http://forum.xda-developers.com/showthread.php?t=1671237
Everything listed on this Index is specific to the dual core AT&T version and its variants.
I've had 5 different smartphones/tablets going back to old Windows Mobile days, and every one of them has had multiple variants, some even having CDMA and GSM variants in the same forum section (but with seperate subforums). In the past you often had to be very careful and verify that you weren't flashing a ROm for the wrong variant (such as flashing a CDMA ROM on a GSM phone). The way XDA is organized for the variants of the One X is actually less confusing than many other devices.
Its good to keep in mind on any smartphone device to research as much as possible, and make sure you are doing mods specific to your version, before doing anything.
Click to expand...
Click to collapse
Thanks....I too have done something, root, unlock bootloaders, install roms, etc over and over going back to win mobile as well and I've never been this careless before. I was in a hurry to get all the AT&T bloatware off it and make it more user friendly so I let my guard down and now have to live with my actions.
ronnyg12 said:
To help everyone (Put this in your OP) if you want
Just type : fastboot getvar all
into the Command Prompt before you DO ANYTHING!
This will tell you all your information you need to know about your phone. For ex if its Evita or endevou
Click to expand...
Click to collapse
THANK YOU!
I will let everyone know that when I got home from work today I found a box at my front door. I opened it up and found a replacement HTC One X. I call and spoke with AT&T questioning why and they said that they went ahead and did a warranty defect on the original phone due to it only being 3 weeks old. So I am excited to say I have a new one in my hand at this time.
Now I just need to start from scratch and figure this out without doing this again. If anyone wants to help walk me through it step by step, I will be forever grateful
Jess
jessepatty said:
I will let everyone know that when I got home from work today I found a box at my front door. I opened it up and found a replacement HTC One X. I call and spoke with AT&T questioning why and they said that they went ahead and did a warranty defect on the original phone due to it only being 3 weeks old. So I am excited to say I have a new one in my hand at this time.
Now I just need to start from scratch and figure this out without doing this again. If anyone wants to help walk me through it step by step, I will be forever grateful
Jess
Click to expand...
Click to collapse
Your new ATT one x probably came with 2.20 software and a new Hboot. I would start reading here:
TOOL KIT NOOB PROOF
Nice all in one tool kit!
eraste said:
Your new ATT one x probably came with 2.20 software and a new Hboot. I would start reading here:
TOOL KIT NOOB PROOF
Nice all in one tool kit!
Click to expand...
Click to collapse
Yes, 2.20...Old one was 1.85
That is what I have, that I used on the first phone.
Thank you
Im having issues with HTCdev.com loading.....keeps timing out. I'm not sure what is up with that.
Gonna try it again tomorrow. Seems like the server is either down or swamped right now.
I did the perm root command in the tool kit which pushed SU to the phone and it says to boot in recovery and run it. I can't seem to get the command line correct to unzip and install SU now. Can somebody post the correct command line to unzip and install SU.
Thanks
jessepatty said:
Im having issues with HTCdev.com loading.....keeps timing out. I'm not sure what is up with that.
Gonna try it again tomorrow. Seems like the server is either down or swamped right now.
I did the perm root command in the tool kit which pushed SU to the phone and it says to boot in recovery and run it. I can't seem to get the command line correct to unzip and install SU now. Can somebody post the correct command line to unzip and install SU.
Thanks
Click to expand...
Click to collapse
The HTCDev.com website is having some serious issues the last few days. Several different users have posted on various posts about the website not working. One user contacted HTC, and they said they are working on getting it back up and running.
You need to unlock the bootloader and install TWRP (custom recovery) before you can flash SU. Once you do those things, just go into recovery, select the install option, and select the SU zip. Its a flashable zip, not something you are supposed to unzip.
redpoint73 said:
The HTCDev.com website is having some serious issues the last few days. Several different users have posted on various posts about the website not working. One user contacted HTC, and they said they are working on getting it back up and running.
You need to unlock the bootloader and install TWRP (custom recovery) before you can flash SU. Once you do those things, just go into recovery, select the install option, and select the SU zip. Its a flashable zip, not something you are supposed to unzip.
Click to expand...
Click to collapse
Thanks....
Yeah I keep submitting my token ID and I get the page that says it was successfully submitted and that I will receive an email with the unlock file attachment but I never get the email... I've submitted it like 4 times now...
I can't do anything else without that file attachment it says I need. I thought I may be able to use the Unlock_code.bin file from my previous phone that died but it says that they are specific to the token ID generated so I guess that is out.
Gonna have to wait until their site is fully functioning before I can proceed.
jessepatty said:
Thanks....
Yeah I keep submitting my token ID and I get the page that says it was successfully submitted and that I will receive an email with the unlock file attachment but I never get the email... I've submitted it like 4 times now...
I can't do anything else without that file attachment it says I need. I thought I may be able to use the Unlock_code.bin file from my previous phone that died but it says that they are specific to the token ID generated so I guess that is out.
Gonna have to wait until their site is fully functioning before I can proceed.
Click to expand...
Click to collapse
Looked in you bulk or spam folders? First time I did it ny email put it there didn't know it twittled my thumbs for almost 2 hours until I noticed it lol. Yea I know I'm an idiot.
Sent from my HTC One XL using Tapatalk 2
I am stuck in a strange problem. I have LG P500 which i have rooted with superoneclick and it is rooted now. I have 2.3.3 V20d (India) which i upgraded a year back.
Now the problem is that according to everyone mine is a new baseband but when i use Rom Manger to install custom recovery it shows my phone but in brackets it says 'old BB'..There were just two options,one was my phone and the other to click the box down if my device is not shown in the above list. I am stuck as can't find any solution and i am a newbie.I did ask some senior members and contributors/devs and waiting for the help,so i thought i will post it here also in case someone has faced this problem before.
Screen capture attached as well.....Just do not know where to go from here.Thanks a lot
MORE INFO: I just downloaded XDA ASSISTANT app to check and in software section it mentions about baseband also. The reading is: V07u-000-000 (MAR-23-2009). Can't say if it is of any help
kitu34 said:
I am stuck in a strange problem. I have LG P500 which i have rooted with superoneclick and it is rooted now. I have 2.3.3 V20d (India) which i upgraded a year back.
Now the problem is that according to everyone mine is a new baseband but when i use Rom Manger to install custom recovery it shows my phone but in brackets it says 'old BB'..There were just two options,one was my phone and the other to click the box down if my device is not shown in the above list. I am stuck as can't find any solution and i am a newbie.I did ask some senior members and contributors/devs and waiting for the help,so i thought i will post it here also in case someone has faced this problem before.
Screen capture attached as well.....Just do not know where to go from here.Thanks a lot
Click to expand...
Click to collapse
and yes that is your phone lg p500 old bb, it doesn't matter, RomManager doesn't discover your phone, it is just a list that you have to choose
from
Are you sure?
grigtm said:
and yes that is your phone lg p500 old bb, it doesn't matter, RomManager doesn't discover your phone, it is just a list that you have to choose
from
Click to expand...
Click to collapse
Are you sure it doesn't matter? But why would Rom Manager mention that? That means it is misleading the user and the user can think esp a newbie that his is a old baseband therefore he will not go with the new baseband and land in trouble.
More Info In Case It Is Helpful
I just downloaded XDA ASSISTANT app to check and in software section it mentions about baseband also. The reading is: V07u-000-000 (MAR-23-2009). Can't say if it is of any help
My advice: don't use Rom Manager to install a custom recovery (or even a Rom); there have been many reports of people bricking their devices that way. A safer way of installing a recovery would be to use LGMDP or adb/fastboot -- instructions should be in a sticky somewhere; I can't search for it at the moment since I'm on mobile. Anyway, good luck.
Edit: Corrected typo -- it's LGMDP.
____________________
Sent from the moon.
Thanks a lot! So kind of you
Syd_M said:
My advice: don't use Rom Manager to install a custom recovery (or even a Rom); there have been many reports of people bricking their devices that way. A safer way of installing a recovery would be to use LGDMP or adb/fastboot -- instructions should be in a sticky somewhere; I can't search for it at the moment since I'm on mobile. Anyway, good luck.
____________________
Sent from the moon.
Click to expand...
Click to collapse
OMG now i have to start all over again,and being a newbie it is not easy at all.Does rooting etc means spending half the time in the forum?Since yesterday my eyes and back are paining just coz of this hehehee
Ok i will check that brother,thanks a lot seriously.
On what basis you say that?
grigtm said:
and yes that is your phone lg p500 old bb, it doesn't matter, RomManager doesn't discover your phone, it is just a list that you have to choose
from
Click to expand...
Click to collapse
I mean you have encountered that or something yourself or any body else? We have to be sure otherwise the phone will be bricked or ruined and i am not a rich person,therefore god is great hehehe
kitu34 said:
OMG now i have to start all over again,and being a newbie it is not easy at all.Does rooting etc means spending half the time in the forum?Since yesterday my eyes and back are paining just coz of this hehehee
Ok i will check that brother,thanks a lot seriously.
Click to expand...
Click to collapse
Well, I know that I spent a few days reading the sticky threads before I rooted my phone, but even then I managed to softbrick it for a couple of days (though it was sort of my fault, since I was using Linux at the time and all the instructions were for Windows, so I had to improvise). You shouldn't need to read every thread, though -- just the stickies should do.
Anyway, regarding Rom Manager, there's a warning in this thread (post #2) not to use it to install a recovery since the CWM version isn't compatible with our devices. As for a recovery you should use, I strongly recommend AmonRa 3.0.6 for a stable and bugfree recovery.
Edit: Just FYI, I installed my recovery using ADB and fastboot. It was quick and easy, the hardest part was installing the LG drivers and ADB (via installing the Android SDK).
____________________
Sent from the moon.
kitu34 said:
I mean you have encountered that or something yourself or any body else? We have to be sure otherwise the phone will be bricked or ruined and i am not a rich person,therefore god is great hehehe
Click to expand...
Click to collapse
I installed my first time recovery by RomManager on O1 3 years ago, I cannot realy remember how was it but it worked, but first go to settings, apps development(or something, you are on GB) and check ANDROID DEBUGGING, now use this tool from here http://forum.xda-developers.com/showthread.php?t=1827723 all credits to shinobisoft
you can find recovery's here http://forum.xda-developers.com/showthread.php?t=1523050 this are flashable zips
or search Optimus One android develepment and original android development threads
I personaly use CWM 5.0.2.7 but my favourite is TWRP (after I'll change rom I'll go back to TWRP)
---------- Post added at 09:54 PM ---------- Previous post was at 09:35 PM ----------
RomManager doesn't suport anymore old phones like O1, that's why it appears with old bb, anyway, allot of ppl flash first time recovery with RomManager, and because it is first time, there must be some fails, not all made it first time, and RomManager is to blame ?? no, worked for me, worked for milions and for a few thousants didn't, and it depends by allot of things but in most cases the people are to blame
grigtm said:
I installed my first time recovery by RomManager on O1 3 years ago, I cannot realy remember how was it but it worked, but first go to settings, apps development(or something, you are on GB) and check ANDROID DEBUGGING, now use this tool from here http://forum.xda-developers.com/showthread.php?t=1827723 all credits to shinobisoft
you can find recovery's here http://forum.xda-developers.com/showthread.php?t=1523050 this are flashable zips
or search Optimus One android develepment and original android development threads
I personaly use CWM 5.0.2.7 but my favourite is TWRP (after I'll change rom I'll go back to TWRP)
---------- Post added at 09:54 PM ---------- Previous post was at 09:35 PM ----------
RomManager doesn't suport anymore old phones like O1, that's why it appears with old bb, anyway, allot of ppl flash first time recovery with RomManager, and because it is first time, there must be some fails, not all made it first time, and RomManager is to blame ?? no, worked for me, worked for milions and for a few thousants didn't, and it depends by allot of things but in most cases the people are to blame
Click to expand...
Click to collapse
Thanks,but what am i suppose to do with this tool? What about rom manager?Shall i go with it?I am sorry i am a newbie so you can lose patience hehehe
kitu34 said:
Thanks,but what am i suppose to do with this tool? What about rom manager?Shall i go with it?I am sorry i am a newbie so you can lose patience hehehe
Click to expand...
Click to collapse
No, don't use ROM Manager. 3 years ago when @grigtm used it, it was fine. These days, however, the CWM version in ROM Manager is incompatible with our device. You will risk bricking your phone if you use ROM Manager. Personally, I advise against it.
As for the Android Flash Recovery program that was linked earlier, I haven't used it personally, but it seems easy enough to use. Just
1. Download Android Flash Recovery
2. Install the LG drivers (it's packaged with the program in a subfolder called "USB")
3. Enable USB debugging on your phone (Settings > Applications > Development > check USB debugging)
4. Start your phone in Fastboot Mode.
5. Connect your phone to the PC.
6. Start Android Flash Recovery and follow the instructions.
Confused
Syd_M said:
No, don't use ROM Manager. 3 years ago when @grigtm used it, it was fine. These days, however, the CWM version in ROM Manager is incompatible with our device. You will risk bricking your phone if you use ROM Manager. Personally, I advise against it.
As for the Android Flash Recovery program that was linked earlier, I haven't used it personally, but it seems easy enough to use. Just
1. Download Android Flash Recovery
2. Install the LG drivers (it's packaged with the program in a subfolder called "USB")
3. Enable USB debugging on your phone (Settings > Applications > Development > check USB debugging)
4. Start your phone in Fastboot Mode.
5. Connect your phone to the PC.
6. Start Android Flash Recovery and follow the instructions.
Click to expand...
Click to collapse
This is the first step after rooting.Ok
Fastboot mode is Home + Power i just have to do that? Like in rom manager we could do backup of stock can we do all that also with this?
Actually i read at two places how to go step by step,when to backup,going into recovery and wiping & reset the phone then again into recovery and navigate to the zip file of the rom and extract.But i do not know if it is same with Android flash recovery.
New Words For Me...........OMG why i came here hehehe
Syd_M said:
Well, I know that I spent a few days reading the sticky threads before I rooted my phone, but even then I managed to softbrick it for a couple of days (though it was sort of my fault, since I was using Linux at the time and all the instructions were for Windows, so I had to improvise). You shouldn't need to read every thread, though -- just the stickies should do.
Anyway, regarding Rom Manager, there's a warning in this thread (post #2) not to use it to install a recovery since the CWM version isn't compatible with our devices. As for a recovery you should use, I strongly recommend AmonRa 3.0.6 for a stable and bugfree recovery.
Edit: Just FYI, I installed my recovery using ADB and fastboot. It was quick and easy, the hardest part was installing the LG drivers and ADB (via installing the Android SDK).
____________________
Sent from the moon.
Click to expand...
Click to collapse
Dear you mentioned 'FYI', 'ADB' & 'Fastboot'..... i just heard about them once twice but don't know what are they. I am sorry this can be irritating for you and for me as well heheehe.Only lucky people can go through this smoothly otherwise i do not think i will recommend this to anyone at least before 7 years lol. But seriously i am confused
One more important thing
Syd_M said:
No, don't use ROM Manager. 3 years ago when @grigtm used it, it was fine. These days, however, the CWM version in ROM Manager is incompatible with our device. You will risk bricking your phone if you use ROM Manager. Personally, I advise against it.
As for the Android Flash Recovery program that was linked earlier, I haven't used it personally, but it seems easy enough to use. Just
1. Download Android Flash Recovery
2. Install the LG drivers (it's packaged with the program in a subfolder called "USB")
3. Enable USB debugging on your phone (Settings > Applications > Development > check USB debugging)
4. Start your phone in Fastboot Mode.
5. Connect your phone to the PC.
6. Start Android Flash Recovery and follow the instructions.
Click to expand...
Click to collapse
I have LG United Mobile driver already installed,that is enough?
kitu34 said:
Dear you mentioned 'FYI', 'ADB' & 'Fastboot'..... i just heard about them once twice but don't know what are they. I am sorry this can be irritating for you and for me as well heheehe.Only lucky people can go through this smoothly otherwise i do not think i will recommend this to anyone at least before 7 years lol. But seriously i am confused
Click to expand...
Click to collapse
There is absolutely no need to learn all of the language, especially when you're just starting out. It's enough in the beginning to just follow instructions, and only go into the details of the Android environment later as you gain more experience. No one becomes an expert overnight, after all.
As for the terms I used... FYI simply means "for your information", nothing to do with Android at all. ADB is the Android Debug Bridge, and like the name implies, it's like the "bridge" that connects your PC to your phone. Any desktop-based program or tweaking tool that communicates with your phone most likely uses ADB (such as SuperOneClick, which you used previously). Fastboot is one of the debugging modes available on the P500. There's no need to concern yourself with exactly what it does (and explaining it in detail is beyond the scope of this post); you simply need to know how to enter that mode when the instructions call for it. Basically, what I'm saying is that you don't need to understand things in detail, you just need to follow instructions. All the instructions you need are in the stickies; for now, ignore anything else that's not there (it'll only confuse you).
The LG Mobile United driver should work. If it doesn't simply install the other drivers.
Thanks alot for the concern
Syd_M said:
There is absolutely no need to learn all of the language, especially when you're just starting out. It's enough in the beginning to just follow instructions, and only go into the details of the Android environment later as you gain more experience. No one becomes an expert overnight, after all.
As for the terms I used... FYI simply means "for your information", nothing to do with Android at all. ADB is the Android Debug Bridge, and like the name implies, it's like the "bridge" that connects your PC to your phone. Any desktop-based program or tweaking tool that communicates with your phone most likely uses ADB (such as SuperOneClick, which you used previously). Fastboot is one of the debugging modes available on the P500. There's no need to concern yourself with exactly what it does (and explaining it in detail is beyond the scope of this post); you simply need to know how to enter that mode when the instructions call for it. Basically, what I'm saying is that you don't need to understand things in detail, you just need to follow instructions. All the instructions you need are in the stickies; for now, ignore anything else that's not there (it'll only confuse you).
The LG Mobile United driver should work. If it doesn't simply install the other drivers.
Click to expand...
Click to collapse
I really appreciate your concern for the safety of my phone.Thanks a lot.
Actually i was to read and follow the instruction as you told but since yesterday i was having headache coz of this and it was severe this morning and still can't open one eye heheehe Anyway i went with the Rom Manager coz of this even though it showed my phone as old BB.It was flashed in less than a minute.Then i switchd off the phone to enter into recovery by holding down Home Button + Volume Down + Power Button(button to switch off) but phone just reboots normally,no recovery set up. The thread i am following for instructions at XDA's How to's says i should not boot into recovery from thr rom manager and use only the buttons combination. But it is not happening,can you help in this?
Thanks again
kitu34 said:
I really appreciate your concern for the safety of my phone.Thanks a lot.
Actually i was to read and follow the instruction as you told but since yesterday i was having headache coz of this and it was severe this morning and still can't open one eye heheehe Anyway i went with the Rom Manager coz of this even though it showed my phone as old BB.It was flashed in less than a minute.Then i switchd off the phone to enter into recovery by holding down Home Button + Volume Down + Power Button(button to switch off) but phone just reboots normally,no recovery set up. The thread i am following for instructions at XDA's How to's says i should not boot into recovery from thr rom manager and use only the buttons combination. But it is not happening,can you help in this?
Thanks again
Click to expand...
Click to collapse
open RomManager and it should detect if you have or no recovery, it says under flashing recovery, if not use that tool I was directing you to and flash recovery, it is a safe tested tool
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
and do not ever boot into recovery from RomManager, actually after you flashed recovery, uninstall RomManager
---------- Post added at 12:11 PM ---------- Previous post was at 12:09 PM ----------
maybe you did not pushed corectly the buttons, keep pressed home+vol down+power, after LG logo appears release power button
Stuck in fastboot mode
grigtm said:
open RomManager and it should detect if you have or no recovery, it says under flashing recovery, if not use that tool I was directing you to and flash recovery, it is a safe tested tool
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
and do not ever boot into recovery from RomManager, actually after you flashed recovery, uninstall RomManager
Click to expand...
Click to collapse
I pressed the buttons this time after the lg logo and it went in fastboot mode.What to do now?
kitu34 said:
I pressed the buttons this time after the lg logo and it went in fastboot mode.What to do now?
Click to expand...
Click to collapse
power off, boot into rom, and verify if recovery was flashed, if not do it again and not from RomManager
I just followed the instructions at XDA
grigtm said:
open RomManager and it should detect if you have or no recovery, it says under flashing recovery, if not use that tool I was directing you to and flash recovery, it is a safe tested tool
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
and do not ever boot into recovery from RomManager, actually after you flashed recovery, uninstall RomManager
---------- Post added at 12:11 PM ---------- Previous post was at 12:09 PM ----------
maybe you did not pushed corectly the buttons, keep pressed home+vol down+power, after LG logo appears release power button
Click to expand...
Click to collapse
Instructions said to hold these buttons that's it.Now i read somewhere here to do it after LG logo. Fastboot mode started, udc_start()
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