Ok I tried using this All-in-one software to flash a kernel and it sent it over and wrote it but its stuck on the HTC logo, and yes I can boot into HBOOT and recovery, is there anyway I can restore straight back to everything factory?
Sounds like the wrong kernel for the Rom was flashed.
What rom/kernel were you trying to flash ?
I was trying to flash the holiradar Final rom, but it said I needed the newest kernel so, I didnt flash the rom yet but I went on the AIO program and flashed the holicakes 2.6.35.14 and when it wouldnt boot up after that...
So what do you suggest I do?
So you are going to need to flash the kernel that goes with the holicakes 2.6.35.14 rom.
Should be on the same site.
You can user CMD to fastboot flash boot boot.img and then the rom will boot.
From what I can tell on the rom page there is a kernel download section.
---------------------------------
Looks like he is instructing you to flash the kernel a different way than I have listed above, but both ways will work.
Riomaru said:
Ok I tried using this All-in-one software to flash a kernel and it sent it over and wrote it but its stuck on the HTC logo, and yes I can boot into HBOOT and recovery, is there anyway I can restore straight back to everything factory?
Click to expand...
Click to collapse
DO NOT TRY, FACTORY RESET WILL DO ABSOLUTELY NOTHING AND MIGHT ACTUALLY MAKE THINGS WORSE.
With that out of the way, don't use the AIO software, use fastboot.exe and flash a boot.img to fix the issue.
Riomaru said:
I was trying to flash the holiradar Final rom, but it said I needed the newest kernel so, I didnt flash the rom yet but I went on the AIO program and flashed the holicakes 2.6.35.14 and when it wouldnt boot up after that...
So what do you suggest I do?
Click to expand...
Click to collapse
No need to worry, you haven't had enough experience to know that it is normal. It is normal for the phone to not boot into the rom when the kernel doesn't match. since you have successfully flashed the kernel, you now need to boot into recovery (which I hope you have it installed at this point, if you have not, read how to do it and flash recovery) once in recovery, proceed to flash the HoliRaider rom and you'll be good to go.
in the same boat
Hi All,
I have a similar problem flashing the Kernal with the vivid toolkit (V 2.1) on my Vivid. I think there should be a big warning for that box. I tried flashing the Holicakes Kernal, and flashed it twice as it tells you to, and ended up with the white HTC screen. Then tried flashing back to the stock rom, more than twice now with no luck. In desperation I tried installing the RUU update 3.26.502.56_US but I now get error 150, which indicates a rom mismatch, and yet it is the update for the phone direct from htc.
What should I try next to get past the white screen?
Thanks
newbroman said:
Hi All,
I have a similar problem flashing the Kernal with the vivid toolkit (V 2.1) on my Vivid. I think there should be a big warning for that box. I tried flashing the Holicakes Kernal, and flashed it twice as it tells you to, and ended up with the white HTC screen. Then tried flashing back to the stock rom, more than twice now with no luck. In desperation I tried installing the RUU update 3.26.502.56_US but I now get error 150, which indicates a rom mismatch, and yet it is the update for the phone direct from htc.
What should I try next to get past the white screen?
Thanks
Click to expand...
Click to collapse
Did you install a recovery?
Also, it was not a good idea to try and install all different types of things once you thought it was messed up. Anytime you think you may have messed up, stop right then, read about the issue, and if you can't find the solution, ask a question. I think you can get out of this but some people aren't that fortunate.
vivid white screen
Thanks for the advice I will press on and do some more reading,
I can still get to CWM recovery and have tried restoring the backup image I made, with the same result.
During the kernal flashing process:-
- is the HTC dev lock supposed to be on or off? It is off and unlocked at the moment,
- is double flashing the kernal what is meant by the instruction 'if this is the first time you flash a kernal, make sure to reflash it', or as is suggested in esloan's post on this thread your supposed to flash a matching rom instead?
Thanks
You did the right thing by flashing the kernel twice. That is what those directions said. After you flash the kernel twice the next step would have been to flash a rom. I believe it is better to use the fast boot commands for doing this entire process. It sounds like you are still on the holicakes kernel.
What recovery do you have? 5.5.4 or WCX Recovery? You will have better results with WCX Recovery. Also watch this video:
http://www.youtube.com/watch?v=xEWa_lUd2bY&feature=youtu.be
That is by randog. He did a great video and he shows you how to install everything without a program. Do you have the holiradier rom on your phone?
I was on the CWM recovery.
Thanks for the link to Randog's video, I now have a working phone again.
The major difficulties I had was finding wildchild's webpage with the links shown on the video, mainly because searching for wildchild illuminati took me to a forum with no links to any thing vivid, until you register.
I was also a little worried that I wasn't getting ICS in the ATT_ generic rom, but I needn't have. The key seemed to be locking the phone again and running wildchild's PH39IMG.zip. After that the security warning on the Hboot screen disappeared.
I almost messed the rom flashing part. Randog's vivid does this really quickly, my phone was a good 3 minutes behind and the progress bar was stuck around the 10% way after his phone had finished.
Like Randog says in the video follow the steps and you wont brick and you'll have a working phone.
Thanks megatronisabeast
Glad you got it. Sorry, forgot to give out the link.
Sent from my HTC PH39100 using XDA
Afraid to screw up any further
Htc vivid. 1.2dualcore.ICS.*
unlocked boot loader.
Used all in one vivid *toolkit 2.1
http://forum.xda-developers.com/showthread.php?t=1498003.
There were two choices. After boot loader unlock, which I had already done. Using right reading logic, I went to the "next step". Didn't realize ICS meant ice cream sandwich. Dumbass. I used CWM 5.5.0.4. Then I tried to to update the kernel, to*Holicakes2.6.35.14. For some unknown reason. The result is the white screen of death.
.*
I have access to hboot. As well as the recover menu which has a backup and restore option.
NAND restore clockworkmod backup, is available. I'm not sure how proceed.*
At the bottom of the screen:*
RA Revamped
Build: made for the WCX ILLUMINATE SERIES by GINM
I studied quite a bit. Too dumb to get a clear picture of the necessary steps before I began, I guess. Again, what a Dumbass.
I *need a better understanding of the process.
I didn't know about the super guide until it was too late. Rather, I did not understand I had seen the super guide when I saw it. It was from December, called a Holliday guide, so I didn't read it. There were so many guides, it confused me pretty throughly. Sheesh.
I have the htc white screen, reboots every three minutes or so.
I would really appreciate someone who knows to give me some clarification on these issues.
I understand a lot of these issues have been dealt with in this thread. I'm just really apprehensive.
I hope I posted this in the right place.
Thanks in advance,
Microbot2
Microbot, you have done pretty much what I did. If you follow megatronis a Brady's advice you will have a working phone. In fact I'm using it right now. Use the generic att zip an you will have ICS less the ATT bloatware.
Okay mircobot, I am home and can help you. Here is what you should do:
http://www.youtube.com/watch?v=xEWa_lUd2bY&feature=youtu.be
Watch that video. Shows you what you will need to do to get everything working again.
The next thing, you need to download all of the files you will need for getting your phone working again. I would recommend going here:
http://www.wcxxperia-nce.com/index.php
You will have to register to see the vivid forums.
Next decide if you want to be able to tether (generic build) or if you want stock based rom (ATT vivid ics).
Download the zip file. Follow the instructions in the video and should get you up and running in no time. That would be the easiest way in my opinion.
If you can't get it figured out or need more help just post here and we will try to assist.
Microbot2--vivid
Hey guys, thanks for the prompt reply's and your general bad-assness.
I just woke and will Start on the instructions.
Megatronisabeast, really appreciate it. Newbroman, thank you.
I already feel considerably less worried about this already. I'll let you know how it works out.
microbot2_no PH39img.zip
Note: I updated to ICS from att before I unlocked the bootloader, which is still locked as now the phone can't be seen by the program.
Megatronisabeast, thanks for the link to the video. I am a little closer to understanding now. Unfortunately, I don't have direct access to the internal storage, like the guy in the video did. and I couldn't discern the website URL and he never tells you directly, except for "goto wildchilds site" which i couldn't locate.
I now know that I have access to wildchildes recovery. Unfortunately, I can only see the internal storage if I use WC recovery, ("windows wants to format it") then goto USB-MS. Otherwise the computers don't see it when its plugged up. It says "device not found when I try to do something in AIO_toolkit 1.2 Don't know if that helps.
I did find the wcxrecovery.img
It appears that you have to have access to internal storage to load an image to it. PH39img.zip, which I don't have. I can't seem to find the wildchild ICS image, either. when I start my phone, it looks for the ph39img.zip, doesn't see it, goes to the white screen.
I don't understand how to get the image back,Rather, how to access the internal storage again. is PH39img is the same thing as the ROM? Do I have to load PH39IMG.zip and the wilchild_vivid_ICS.ROM, which, again, I can't seem to find.
This feels like a comedy of errors. I wish I would have studied longer. I usually do. THEN, I find "newbie_proof" all in one toolkit.
I Just wanted it rooted. All I had to do was click "root" instead of "kernel". Man, what was I thinking?
If only I had taken the Red Pill.
Thanks again,
Look at my post above, the link for wild Childs site is there. You have to register to see the vivid forums. That is also where you will download the files needed to set up the ROM, etc. You won't need the Ph39.img since you already have ics. That is for the bootloader. You can actually send a file to your phone in the recovery. since you already have recovery you would need to download the Android sdk tools, so you will have fastboot. You use fastboot to send the boot image to your phone. Then you would go to recovery and send the .zip file to your phone and flash in recovery. Sorry these directions aren't better, I will try to assist more when I get home, Swyping right now.
Sent from my HTC PH39100 using XDA
Microbot,
The wildchild files you need are in the first link Megatronisabeast cites
wcxxperia-nce.com/index.php (I'm a newbie and cant post the full web address). You have to sign up to the forum to access the files. The vivid forum will appear once you have registered.
The PH391IMG.zip is not your normal PH39img.zip you have to use the one contained in the WCX_generic_ATT.zip on the WCX vivid forum page. You also need to relock the phone. You are probably better off using the fastboot and the windows command prompt for this.
Can you boot into recovery at all?
Do you have another phone? you could use that to copy the PH39img.zip over. Thats what I did.
Mcrobot2---
Hi guys,*
Here is what I think I know:
HBOOT is a bootloader, *like a BIOS.
PH39img.zip is the boot file. Like PH39IMG.zip which appears to be a modified version for WC.
Kernel *is the memory and CPU manager.
ROM is an operating system package, or file placed onto the erasable/programmable part of the phones memory. NAND, I think.
S-OFF/ON *is a security check.
.Apk: compressed java file.
.Jar: *java application file.
.odex *files: helper files with most relevant information to compile and run the concerned application as fast as possible, a JIT Kind of thing.
----
I was able to relock bootloader, Yea!
Thanks megatronisabeast and newbroman.
--history--I updated to ICS from AT&T.
I thought I could skip reading for another three weeks because of newbie-proof AIO 2.1. * wrong!
I wanted to root my phone. *I had unlocked the bootloader with htcdev.*
Found hasoons all in one vivid 1.2. Used WC's recovery. I then flashed with hollicakes kernel, twice. Wsod.
--
Megatronisabeast:*
You use fastboot to send the boot image to your phone. Then you would go to recovery and send the .zip file to your phone and flash in recovery.
-I'm not sure the exact boot img,*
- I think the zip file would be the rom?
Getting closer.
Thanks again guys. I'm feeling a little thick lately. Like freshman year of college! Weed out classes.
i search whole vivid forum about this problem
some guys (like me ) have problem with wifi on custom Roms
in some kernel wifi stuck on "wifi is turning on ..." and some kernel wifi could be on but it's crazy (like couldn't off) and couldn't find any wifi signal.
phone go to s-off but problem not solved
phone like Velocity 4G x710s
any body have a suggestion or help
when you flash any kernel, after that you have to push these file (bcmdhd.ko) which is in the kernel you download - to system/lib/module
and you will have wifi working with every kernel
mohamed_moscow said:
when you flash any kernel, after that you have to push these file (bcmdhd.ko) which is in the kernel you download - to system/lib/module
and you will have wifi working with every kernel
Click to expand...
Click to collapse
i found some "bcmdhd.ko" in some kernel
which is best for me
Cant wait for release!!
Can you upload that file for us?
Sent from my HTC Raider 4G LTE running ICS.
ideaLduK said:
Can you upload that file for us?
Sent from my HTC Raider 4G LTE running ICS.
Click to expand...
Click to collapse
yes, upload that for us
Every kernel has it's own specific modules.
Thats why if you're S-ON you have to flash a CWM Zip and fastboot the img.
If you're S-OFF both are done in CWM.
This thread should be moved.
ok i find working file
tested with kozmik RC1 kernel and work well
Nottach said:
Cant wait for release!!
Click to expand...
Click to collapse
Hehe awesome.
I experienced the issue you described as a separate error from the common issue solved by a manual adb push for the wireless module.
Even though my phone is S-Off, I'd receive the error consistently when installing certain ROMs (but not all ROMs).
After multiple wipes (including formatting all SD drives, data and system partitions), I finally fixed the issue on my phone by fastboot flashing the kernel for the specific ROM I'm installing after doing a re-format/wipe and before starting the ROM installer through CWM.
It's a strange error, especially because everything seemed to be installed properly (including proper kernel info in the system) and my phone is S-Off, but this is the method I've found that works.
If anyone experiences the issue, I'd recommend doing a back-up, full wipe and re-format (including internal and external SD, basically everything you can wipe); and then fastboot flash the boot.img pulled from your ROM zip before going into CWM and installing (always be careful when fastboot flashing; if you're new to it, you definitely need to familiarize yourself and read a tutorial or two; don't blame me if you're new to flashing, don't read tutorials and end up accidentally flashing a kernel to the wrong partition or some other problem).
Hope this helps out some of the people experiencing this issue.
I can relate
First let me say that kernels and ROMs are two different things.
Kernels are the base on which the ROM operates, they do include important information that can impact phone interoperability. They are required for a ROM to function. And they and ROMs do inter operate extensively.
ROMS are the added features and functionality that make our phones work as an actual appliance. They include software applications and compatibility feature that enable us to make and receive calls, and do all the other crazy things that we want in our phone, work.
I was experiencing similar issues recently. It turned out for me that if I didn't reflash the correct kernel after updating to a ROM that my MAC address would be missing. When that happened you will get the "turning on wireless" message that never completes, or your Wireless Networking switch in extended menu will be "ghosted" out.
Thanks to some great guys in TWRP, I got enough help to figure out what the right combination of "this and that" was. Now I am able to try and troubleshot mine effectively if I do it again.
Just my 3 cents guys, your mileage may vary!
daspazz said:
First let me say that kernels and ROMs are two different things.
Kernels are the base on which the ROM operates, they do include important information that can impact phone interoperability. They are required for a ROM to function. And they and ROMs do inter operate extensively.
ROMS are the added features and functionality that make our phones work as an actual appliance. They include software applications and compatibility feature that enable us to make and receive calls, and do all the other crazy things that we want in our phone, work.
I was experiencing similar issues recently. It turned out for me that if I didn't reflash the correct kernel after updating to a ROM that my MAC address would be missing. When that happened you will get the "turning on wireless" message that never completes, or your Wireless Networking switch in extended menu will be "ghosted" out.
Thanks to some great guys in TWRP, I got enough help to figure out what the right combination of "this and that" was. Now I am able to try and troubleshot mine effectively if I do it again.
Just my 3 cents guys, your mileage may vary!
Click to expand...
Click to collapse
How did you get it working
Sent from my ADR6410LVW using xda premium
So im jimmy. hey. Ive been on this site a while but never post anything. Why? because i can read directions and definitely am not a noob .
Anyways im stuck with my vivid.
I have HTC Unlocked it.
I successfully perm-rooted it.
I also have successfully S-off'd and installed the Juopunut H boot.
As well as sim unlocked my vivid.
I decided i didnt want to mess with any of the kernel mumbo jumbo or roms because i was happy with stock.
But the bluetooth glitch was driving me nuts so i decided to change roms.
I first experimented with a kernel just to see if i fully understood the procedure. Since i was s off i just flashed to CWM but it didnt work.
First, my wifi wouldnt work.
Then i tried the hboot method.
I got stuck in the boot loop. Cleared the cache and everything and nothing worked.
Tried fastbooting and its like it wants to work, it will load up to the preparing apps screen and then freeze on 1 of 8.
I tried flashing the stock rom over the kernel and the wallpaper comes up and the taskbar but thats it.
After that it restarts.
Ive read almost all the threads but no one seems to give a direct answer to this issue.
I REALLY WANT TO AVOID HAVING TO RELOCK AND RUU FLASH.
but if thats what i have to do then i have no choice.
Clearly if that is my only option how do i go about re installing the oem locked hboot?
EDIT:
Ok i got my phone to boot up again by installing the stock deodexed rom. But when i try to install the kernel by faux123 thats when my phone starts acting up.
Note that i am S OFF with the Juopunut hboot and the kernel should work with any rom.
I can flash this kernel through CWM or even fastboot it but no luck
Well ya can't use a different kernel than provided with the ROM for the stock rooted firmware. Extract the boot.img from the .zip and fastboot flash it and then flash the ROM after wiping all the usual partitions.
You should know this stuff if you've been lurking and reading for a while...
Sent from my HTC PH39100 using xda premium
Monkeymannnn said:
Well ya can't use a different kernel than provided with the ROM for the stock rooted firmware. Extract the boot.img from the .zip and fastboot flash it and then flash the ROM after wiping all the usual partitions.
You should know this stuff if you've been lurking and reading for a while...
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Youre right. I was able to do exactly that last night.
Thing is... i decided to go with the raiders rom, flashed it, installed the faux kernel then after reflashed the kernel after the install
via fastboot... it worked last night. wifi and everything.
BUT this morning i go to use my phone and the wifi was stuck yet again on turning on
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Jeffril said:
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Click to expand...
Click to collapse
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
NoDze said:
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
Click to expand...
Click to collapse
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Jeffril said:
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Click to expand...
Click to collapse
Okay, This is SFSP by @sgspluss which is a pretty fast, stable and battery-friendly slimmed down version of stock ICS. It is available for both Old and NewBL, so you might want to try that first. This is AIO Toolkit. I know that you've used it and bricked your phone, but try again, and for the love of God install the nvflash drivers because most people skip that part. You have to do it manually and if you're running Windows 8 you need to disable Driver Signature Verification. But yeah, you switch bootloaders with this.
i unlocked the bootloader and flashed 5.1 initially (it got some wifi connection problems) so flashed cm12 which makes my wifi to stuck at "Turning wifi on" same problem in cm11 also.
now to make things straight i went back to my stock version 4.4.4 which still doesn't fix my problem
My friend(nexus user) said to me tht there will be radio.img which will fix the wifi drivers but i did not find it any where in any rom
but for them it is included in the image provided by google.......
please someone give me radio.img to get my wifi back into working condition..................
himasagar said:
i unlocked the bootloader and flashed 5.1 initially (it got some wifi connection problems) so flashed cm12 which makes my wifi to stuck at "Turning wifi on" same problem in cm11 also.
now to make things straight i went back to my stock version 4.4.4 which still doesn't fix my problem
My friend(nexus user) said to me tht there will be radio.img which will fix the wifi drivers but i did not find it any where in any rom
but for them it is included in the image provided by google.......
please someone give me radio.img to get my wifi back into working condition..................
Click to expand...
Click to collapse
When you say you went back to 4.4.4, did you mean by flashing via SP flash tool or just restoring a backup using a custom recovery?
Download the stock images to your device and flash it using SP flash tool. IFAIK we don't have a radio.img. It seems like a bad flash so even if you flashed using SP flash tool, reflash your phone. It probably fix your problem with wifi. You'll loose everything stored in your phone except for what's in your SD card, so backup your stuff before flashing anything!
Dhamithl said:
When you say you went back to 4.4.4, did you mean by flashing via SP flash tool or just restoring a backup using a custom recovery?
Download the stock images to your device and flash it using SP flash tool. IFAIK we don't have a radio.img. It seems like a bad flash so even if you flashed using SP flash tool, reflash your phone. It probably fix your problem with wifi. You'll loose everything stored in your phone except for what's in your SD card, so backup your stuff before flashing anything!
Click to expand...
Click to collapse
well i tried both of them SP flash tool and also restoring the backup wifi did not work in both of them.i flashed using SP flash tool maybe like 4-5 times till now and still no change .
finally i have one question flashing stock with sp flash does it give back the warranty.????
i think it as some hardware defect i am going to give it to micromax customer care.
himasagar said:
well i tried both of them SP flash tool and also restoring the backup wifi did not work in both of them.i flashed using SP flash tool maybe like 4-5 times till now and still no change .
finally i have one question flashing stock with sp flash does it give back the warranty.????
i think it as some hardware defect i am going to give it to micromax customer care.
Click to expand...
Click to collapse
Then it probably IS a hardware problem. If you flashed stock rom and locked the bootloader, you wouldn't have any problems with customer care. Check everything on settings before though (Model name, imei etc.) Just say you tried factory reset and it didn't work.