Hi, Guest! Login / Register




Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

[Please help] MICROMAX BOLT A35 (SPD) NOT BOOTING

#1

HELLO EVERYONE ,
I HAVE A SMARTPHONE MICROMAX A35 FROM 2013 BUT I GOT A FEW PROBLEMS , I BREAKED IT WHILE ROOTING (BOOTLOOP).
WHEN I FLASHED STOCK ROM VIA RESEARCH DOWNLOAD(SPD) IT SHOWED ERROR " bkf_NV FAILED TO WRITED" . I SOLVED NV PROBLEM , GOT SUCCESSFULY FLASHED MY SMARTPHONE WITH BLUE SIGN (PASSED).BUT WHEN I POWERED IT ON IT STILL BOOTLOOPS(DOES NOT STARTS,JUST STUCK AT LOGO),WHILE CUSTOM RECOVERY BOOTS WELL.

CUSTOM RECOVERY BOOTS WELL BUT STOCK BOOT IMAGE NOT BOOTS INTO SYSTEM , I THINKS IT IS "NV" PROBLEM .
HELP ME !!!!! .

HELP ME EITHER MODIFY BOOT IMAGE OR SOME THING ELSE..

CPU - SC6880 (I THINK IT IS SAME OR GOOFLE IT)
android os - 2.3.5 GINGERBREAD
RAM - 256 MB 
STORAGE - 169 MB FREE ONLY
BRAND - MICROMAX
MODEL - A35


Reply
#2
(06-09-2017, 05:51 PM)Ankitnandgavia Wrote: HELLO EVERYONE ,
I HAVE A SMARTPHONE MICROMAX A35 FROM 2013 BUT I GOT A FEW PROBLEMS , I BREAKED IT WHILE ROOTING (BOOTLOOP).
WHEN I FLASHED STOCK ROM VIA RESEARCH DOWNLOAD(SPD) IT SHOWED ERROR " bkf_NV FAILED TO WRITED" . I SOLVED NV PROBLEM , GOT SUCCESSFULY FLASHED MY SMARTPHONE WITH BLUE SIGN (PASSED).BUT WHEN I POWERED IT ON IT STILL BOOTLOOPS(DOES NOT STARTS,JUST STUCK AT LOGO),WHILE CUSTOM RECOVERY BOOTS WELL.

CUSTOM RECOVERY BOOTS WELL BUT STOCK BOOT IMAGE NOT BOOTS INTO SYSTEM , I THINKS IT IS "NV" PROBLEM .
HELP ME !!!!! .

HELP ME EITHER MODIFY BOOT IMAGE OR SOME THING ELSE..

CPU - SC6880 (I THINK IT IS SAME OR GOOFLE IT)
android os - 2.3.5 GINGERBREAD
RAM - 256 MB 
STORAGE - 169 MB FREE ONLY
BRAND - MICROMAX
MODEL - A35

If a factory reset in recovery mode doesn't help then you'll need to try a different pac file
Need further assistance? Speak with a Hovatek Representative:
Working Hours: Mondays - Saturdays ; 09:00 - 18:00 (GMT +1:00)
Reply
#3
(06-09-2017, 11:22 PM)hovatek Wrote:
(06-09-2017, 05:51 PM)Ankitnandgavia Wrote: HELLO EVERYONE ,
I HAVE A SMARTPHONE MICROMAX A35 FROM 2013 BUT I GOT A FEW PROBLEMS , I BREAKED IT WHILE ROOTING (BOOTLOOP).
WHEN I FLASHED STOCK ROM VIA RESEARCH DOWNLOAD(SPD) IT SHOWED ERROR " bkf_NV FAILED TO WRITED" . I SOLVED NV PROBLEM , GOT SUCCESSFULY FLASHED MY SMARTPHONE WITH BLUE SIGN (PASSED).BUT WHEN I POWERED IT ON IT STILL BOOTLOOPS(DOES NOT STARTS,JUST STUCK AT LOGO),WHILE CUSTOM RECOVERY BOOTS WELL.

CUSTOM RECOVERY BOOTS WELL BUT STOCK BOOT IMAGE NOT BOOTS INTO SYSTEM , I THINKS IT IS "NV" PROBLEM .
HELP ME !!!!! .

HELP ME EITHER MODIFY BOOT IMAGE OR SOME THING ELSE..

CPU - SC6880 (I THINK IT IS SAME OR GOOFLE IT)
android os - 2.3.5 GINGERBREAD
RAM - 256 MB 
STORAGE - 169 MB FREE ONLY
BRAND - MICROMAX
MODEL - A35

If a factory reset in recovery mode doesn't help then you'll need to try a different pac file

I have tried every (all three ) available pac on my bolt a35 but it is not booting.Any custom recovery (cwm , miui,or other ) boots well, shows all sections (system , data  , cache ) . It shows  all files in system , data folder after flashing aroma file manager throough recovery.
Reply
#4
(06-13-2017, 07:29 PM)Ankitnandgavia Wrote:
(06-09-2017, 11:22 PM)hovatek Wrote:
(06-09-2017, 05:51 PM)Ankitnandgavia Wrote: HELLO EVERYONE ,
I HAVE A SMARTPHONE MICROMAX A35 FROM 2013 BUT I GOT A FEW PROBLEMS , I BREAKED IT WHILE ROOTING (BOOTLOOP).
WHEN I FLASHED STOCK ROM VIA RESEARCH DOWNLOAD(SPD) IT SHOWED ERROR " bkf_NV FAILED TO WRITED" . I SOLVED NV PROBLEM , GOT SUCCESSFULY FLASHED MY SMARTPHONE WITH BLUE SIGN (PASSED).BUT WHEN I POWERED IT ON IT STILL BOOTLOOPS(DOES NOT STARTS,JUST STUCK AT LOGO),WHILE CUSTOM RECOVERY BOOTS WELL.

CUSTOM RECOVERY BOOTS WELL BUT STOCK BOOT IMAGE NOT BOOTS INTO SYSTEM , I THINKS IT IS "NV" PROBLEM .
HELP ME !!!!! .

HELP ME EITHER MODIFY BOOT IMAGE OR SOME THING ELSE..

CPU - SC6880 (I THINK IT IS SAME OR GOOFLE IT)
android os - 2.3.5 GINGERBREAD
RAM - 256 MB 
STORAGE - 169 MB FREE ONLY
BRAND - MICROMAX
MODEL - A35

If a factory reset in recovery mode doesn't help then you'll need to try a different pac file

I have tried every (all three ) available pac on my bolt a35 but it is not booting.Any custom recovery (cwm , miui,or other ) boots well, shows all sections (system , data  , cache ) . It shows  all files in system , data folder after flashing aroma file manager through recovery.
When flashing any stock pac it shows NV error , so i skipped NV and flashed all files .
I think NV is causing problems during boot process.

CAn you help me to modify boot.img so that we can fix nv error .
Reply
#5
(06-13-2017, 07:29 PM)Ankitnandgavia Wrote: I have tried every (all three ) available pac on my bolt a35 but it is not booting.Any custom recovery (cwm , miui,or other ) boots well, shows all sections (system , data  , cache ) . It shows  all files in system , data folder after flashing aroma file manager throough recovery.

What did you do to fix the bkf_NV FAILED TO WRITED error?

Need further assistance? Speak with a Hovatek Representative:
Working Hours: Mondays - Saturdays ; 09:00 - 18:00 (GMT +1:00)
Reply
#6
(06-14-2017, 12:55 PM)hovatek Wrote:
(06-13-2017, 07:29 PM)Ankitnandgavia Wrote: I have tried every (all three ) available pac on my bolt a35 but it is not booting.Any custom recovery (cwm , miui,or other ) boots well, shows all sections (system , data  , cache ) . It shows  all files in system , data folder after flashing aroma file manager throough recovery.

What did you do to fix the bkf_NV FAILED TO WRITED error?

I just skipped nv file using settings and flashed remaining partitions like system,boot,uboot,recovery etc etc.
Can you tell why it is not booting
Reply
#7
(06-15-2017, 09:27 AM)Ankitnandgavia Wrote: I just skipped nv file using settings and flashed remaining partitions like system,boot,uboot,recovery etc etc.
Can you tell why it is not booting

That's the fix.
Have you tried backing up the phone in custom recovery to see if all partitions are correctly backed up? Also, is prodnv listed?
Need further assistance? Speak with a Hovatek Representative:
Working Hours: Mondays - Saturdays ; 09:00 - 18:00 (GMT +1:00)
Reply










Users browsing this thread:
1 Guest(s)