Related
I made the mistake of using samsung aps to update the camera firmware when it prompted me to.
Unfortunately this was not successful and the update FC so no my camera does not work properly.
Auto flash does not work, and the video only works at night (low light conditions). There is just a white screen in the day (normal light conditions)
There is the service menu to manually flash the firmware, just 2 (*#34971539#) issues with this:
1) I no longer have a fw that works.
2) My camera thinks it has the latest firmware so will not allow a reflash.
So can someone upload the files they have in : /etc/firmware
there should be 3/4 files:
RS_M5LS_OB.bin
RS_M5LS_OC.bin
RS_M5LS_TB.bin
qt602240.fw
The M5LS files look to be the firmware files for the camera.
Also does anyone know how I can update the version in these bin files from oced11 to a higher version oced12 maybe. So the camera firmware flash will allow the update? Or is there anyway that I can force the flash?
========================================================================================
Ok fixed it, for anyone else that has the issue with the Samsung App updater failing on the camera update here is how to fix it:
Copy /etc/firmware/RS_M5LS_OC.bin to the pc
open RS_M5LS_OC.bin in notepad++ and search for the version number (in this case oced11)
change the 11 to 12 (WARNING: only change the number do not add other characters adding even a space may corrupt the bin).
save RS_M5LS_OC.bin and copy it back to the phone in /etc/firmware
enter *#34971539# in the stock dialer.
select "Phone/CAM FW Ver Check" if you have done the previous steps correctly the versions will be different (phone version will be +1 on the camera version)
select "Phone to CAM FW Write"
Once this completes (takes 3min ish) the camera is now working correctly.
The files I used can be found: http://www.mirrorcreator.com/files/0PEES0BI/CamFW.zip_links
Thank you for sharing, might be helpful if something fails while updating.
Hi!
The cam update corrupted my camera, too. I tried to follow your tutorial but there's a little problem: I can't find the "/etc..." folder on my phone. I do have root access and dumped the cam firmware to the phone via the service interface. But still I cannot find it when I connect my phone to the pc. Can someone pleas help me? Thanks in advance!
Talpa85 said:
Hi!
The cam update corrupted my camera, too. I tried to follow your tutorial but there's a little problem: I can't find the "/etc..." folder on my phone. I do have root access and dumped the cam firmware to the phone via the service interface. But still I cannot find it when I connect my phone to the pc. Can someone pleas help me? Thanks in advance!
Click to expand...
Click to collapse
Don't look for it on PC , disconnect phone and download "Root explorer" from market ,then on phone itself with root explorer go to system/etc .
OK I found the folder with android mate. But there is no RS_M5LS_OC.bin only RS_M5LS_OB.bin, qt602240.fw and RS_M5LS_TB. I don't know what to do now.
edit: I'm not sure what happens if I took thelestat's file and put it on my phone. Maybe it's too risky...
Talpa85 said:
OK I found the folder with android mate. But there is no RS_M5LS_OC.bin only RS_M5LS_OB.bin, qt602240.fw and RS_M5LS_TB. I don't know what to do now.
edit: I'm not sure what happens if I took thelestat's file and put it on my phone. Maybe it's too risky...
Click to expand...
Click to collapse
Hi, looks like you are on the OB firmware, where I had an OC camera. you can check using the secret code in the OP.
Copy the RS_M5LS_OB.bin to your PC, Open itin notepad++ and search for the version the secret code shows you. Increment the number by 1, save it. Then replace it on the phone. Flash using the secret code.
If you want, post here the versions from the swcret code, and upload the file. I can do the editing for you.
Mine was dead too.I also can't find RS_M5LS_OC.bin,but i find RS_M5LS_OE.bin,OB,TB...but I open this 3 files,and I can't find the secret code(OCEE09).
Cam FW Ver: SCEF02
Phone FW Ver: TBEC28
Here are my files: w*w.mirrorcreator.com/files/1ONIHVSU/Camfirmware.rar_links
Hi,
It was in the RS_M5LS_TB.bin file. I updated the version to TBEC29.
The file is: http://www.mirrorcreator.com/files/QNQXTGZ8/RS_M5LS_TB.zip_links
Just replace the one on your phone and use the secret code to flash it.
I have OCEF02 as Cam fw and in firmware folder I have:
qt602240.fw
RS_M5LS_OB.bin
RS_M5LS_TB.bin
RS_M5LS_OE.bin
That's meaning I have installed RS_M5LS_OC.bin?
There is any chance to revert to TBEC28?
Thank you.
hi
i really can't believe it
i was flashing firmware update when THE ALARM RINGED!!!!!!!!
the flash app has crashed now i have a non working camera
do i need root to do this procedure?
I just updated my camera firmware through Samsung Apps. It all went fine, took a few minutes then I manually rebooted. Video, photos, flash all work fine.
Strange why it fails for some people. Maybe battery was too low ? Or different version of the camera hardware ?
btw now I have:
Cam FW Ver: SCEF02
Phone FW Ver: TBEC28
hi Thelestat
i rooted the phone now i'm stuck to the "version" part
would you mind to help me too please?
my files are these: htt p://w ww.mirrorcreator.com/files/0UIIP10D/
thelestat said:
Hi,
It was in the RS_M5LS_TB.bin file. I updated the version to TBEC29.
The file is: http://www.mirrorcreator.com/files/QNQXTGZ8/RS_M5LS_TB.zip_links
Just replace the one on your phone and use the secret code to flash it.
Click to expand...
Click to collapse
Is it based in TBEC28?
Cheers.
i REALLY don't know what happened
i managed to find that the firmware on camera was SCEF02
so i managed to put SCEF03 on the file
i tried to flash it started but crashed after 3 seconds
the i gave a punch to the table (i think it helped )
then i go to samsung apps redownloaded camera flash firmware and it said it was the latest version
uninstalled it
gone into the secret menu, and it said camera version SCEF02 and PHONE VERSIOn SCEF02
i gave ok and it started flashing
that were the longest three minutes of my life :O
i rebooted the phone and :O it is working now
it seems to me that downloading the camera firmware update left in /etc/firmware the "right one".... and even if it was the SAME version of the actual camera firmware, it worked
i'm really happy i was worried to have to send the phone to samsung.....
thank you thelestat... really, thank you!
akirax said:
Is it based in TBEC28?
Cheers.
Click to expand...
Click to collapse
yep, same file as the TBEC28 i just upped the version to
Hi everyone,
I recently bought a Galaxy S2 and I'm getting a "camera failed" error whenever I try to start the camera. I even tried to instal some other camera apps from the market but same error.
Can someone please guide me what is wrong with my phone?
Sent from my GT-I9100 using Tapatalk
faremoney said:
i REALLY don't know what happened
i managed to find that the firmware on camera was SCEF02
so i managed to put SCEF03 on the file
i tried to flash it started but crashed after 3 seconds
the i gave a punch to the table (i think it helped )
then i go to samsung apps redownloaded camera flash firmware and it said it was the latest version
uninstalled it
gone into the secret menu, and it said camera version SCEF02 and PHONE VERSIOn SCEF02
i gave ok and it started flashing
that were the longest three minutes of my life :O
i rebooted the phone and :O it is working now
Click to expand...
Click to collapse
I'm confused now, thelestat. This is the exact version of my cam firmware. Is the file you updated for me still the right one? Sorrry, but I'm a little bit frightened of flashing the file. Can this cause serious harm to my phone if something goes wrong? Thank you so much for your help.
Talpa85 said:
I'm confused now, thelestat. This is the exact version of my cam firmware. Is the file you updated for me still the right one? Sorrry, but I'm a little bit frightened of flashing the file. Can this cause serious harm to my phone if something goes wrong? Thank you so much for your help.
Click to expand...
Click to collapse
Yeah it is still the right version. It's the file you uploaded with the version number changed.
It is the exact same firmware as the samsung application tried to update, the change I made, just allows for the secret code flash option to work. It checks for a newer version before it allows the update.
It is unlikely to effect the rest of the phone, as it is only writing the camera firmware. I have used the secret codes to read an write a number of times, and have never had an issue.
I am not able to flash it: Invalid version TBEC29
Phone/CAM FW Ver Check:
Cam FW: SCEF02
Phone FW: TBEC29
By the way is it possible that there is no firmware version called TBEC29 out there? This would explain why it doesn't work.
This sucks...
I'm facing a problem my note 3 N9005 is hard bricked , my phone bootloops when i flashed a rom so i flashed a stock rom, then suddenly my PHONE CAMERA FAILED to open, NO SOUND AT ALL in the phone NOT EVEN THE RINGTONES SOUND (hangs when pressing volume key rocker), PHONE DIALER DOESNT OPEN black screen appears when i try to open it and i have laggy phone and it hangs alot, HOPE GOOD DEVELOPERS WILL HELP
Things I have Tried : Flashed Stock Roms, didnt work
Flashed Stock Rom and rooted, didnt work .
Flashed Stock Rom Rooted and installed cwm recovery philz edition, didnt work.
Flashed Stock Rom with a PIT FILE , that too didnt work...
KNOWN DEVELOPERS HELP PLZ...Thanks in advance.:crying:
Flash a rom first and flash the attachment will solve your problem
masrooraly said:
I'm facing a problem my note 3 N9005 is hard bricked , my phone bootloops when i flashed a rom so i flashed a stock rom, then suddenly my PHONE CAMERA FAILED to open, NO SOUND AT ALL in the phone NOT EVEN THE RINGTONES SOUND (hangs when pressing volume key rocker), PHONE DIALER DOESNT OPEN black screen appears when i try to open it and i have laggy phone and it hangs alot, HOPE GOOD DEVELOPERS WILL HELP
Things I have Tried : Flashed Stock Roms, didnt work
Flashed Stock Rom and rooted, didnt work .
Flashed Stock Rom Rooted and installed cwm recovery philz edition, didnt work.
Flashed Stock Rom with a PIT FILE , that too didnt work...
KNOWN DEVELOPERS HELP PLZ...Thanks in advance.:crying:
Click to expand...
Click to collapse
Quick FYI and correction -
Hard Brick = Won't power on or do anything.
Soft Brick = Can still access the device - bootloop/power up/bootloader/recovery.
masrooraly said:
I'm facing a problem my note 3 N9005 is hard bricked , my phone bootloops when i flashed a rom so i flashed a stock rom, then suddenly my PHONE CAMERA FAILED to open, NO SOUND AT ALL in the phone NOT EVEN THE RINGTONES SOUND (hangs when pressing volume key rocker), PHONE DIALER DOESNT OPEN black screen appears when i try to open it and i have laggy phone and it hangs alot, HOPE GOOD DEVELOPERS WILL HELP
Things I have Tried : Flashed Stock Roms, didnt work
Flashed Stock Rom and rooted, didnt work .
Flashed Stock Rom Rooted and installed cwm recovery philz edition, didnt work.
Flashed Stock Rom with a PIT FILE , that too didnt work...
KNOWN DEVELOPERS HELP PLZ...Thanks in advance.:crying:
Click to expand...
Click to collapse
Did You ever tried a full wipe several times before and after flashing?
Post some more information.
1. Where did you buy the phone
2. PDA/CSC/Baseband
3. IMEI still displayed as a number or is it null/null
4. Do you have EFS, FSC, and FSG backups
5. Which stock rom(s) did you flash
It sounds to me as though you have been flashing the wrong stock rom for your device. The behaviour you describe sits in line with that.
i bought it From official Samsung Shop, and it was running like normal before this problem.
IMEI is ok, not showing null or anything like that.
didnt help
bhasg1007 said:
Flash a rom first and flash the attachment will solve your problem
Click to expand...
Click to collapse
I tried to do this but this too didnt help brother. Now what do you suggest
masrooraly said:
i bought it From official Samsung Shop, and it was running like normal before this problem.
IMEI is ok, not showing null or anything like that.
Click to expand...
Click to collapse
Okey you need to get EFSBackupPro and use it to backup efs and fsc and fsg partitions. Just Google it and you will find a link to the thread here on xda.
After that you need to tell us what is the phone model. Look at my signature to see what a model looks like.
I think you flashed the wrong stock ROM. We need to find out which model phone you have so we can link you to the correct n9005 stock ROM.
You must make efs backup first. You can lose your imei and I have not seen a working method to fix the phone if that happens.
Efsbackuppro has bricked Note 3's previously. I wouldn't advise it.
Sent from my LG-D855 using XDA Premium 4 mobile app
radicalisto said:
Efsbackuppro has bricked Note 3's previously. I wouldn't advise it.
Sent from my LG-D855 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not sure about what happened in those case. It is quite literally a GUI that runs a few dd commands, that's it.
didnt help
bhasg1007 said:
Flash a rom first and flash the attachment will solve your problem
Click to expand...
Click to collapse
Tried this but didnt solve the prob brother, i have tried fashing several stock roms but still problem exits.. Phone has no sound at all , Camera Says error Camera Failed , Phone hangs like a hell lockscreen lag And Phone App is not working. when ever any call comes screen goes black and i cant access the call atend or decline it. please tell me any fix for these 3 things..
AO7 said:
Post some more information.
1. Where did you buy the phone
2. PDA/CSC/Baseband
3. IMEI still displayed as a number or is it null/null
4. Do you have EFS, FSC, and FSG backups
5. Which stock rom(s) did you flash
It sounds to me as though you have been flashing the wrong stock rom for your device. The behaviour you describe sits in line with that.
Click to expand...
Click to collapse
i have tried fashing several stock roms but still problem exits.. Phone has no sound at all , Camera Says error Camera Failed , Phone hangs like a hell lockscreen lag And Phone App is not working. when ever any call comes screen goes black and i cant access the call atend or decline it. please tell me any fix for these 3 things..
I have the exact same problem and I think it's a hardware problem. This was happening to me yesterday and is not related to software. I think it's the sound IC or dac.
Sent from my SM-N9005 using Tapatalk
After flashing stock rom, do FULL WIPE using recovery.
You did not mention doing it.
I did this and no change. As I mentioned I don't think this is a software problem. I did remove cameras and usb charging port even the upper hedfone port and is the same behaviour. One of the iC is malfunction . I did stop everything that is related to sound and I use now my phone as a tablet with no sound and recording capabilities.
Sent from my SM-N9005 using Tapatalk
L.E.
After I was looking over schematic of motherboard and online for similar hardware defect I think is the audio codec IC WCD9320 that need to be re-balled or replaced. On the MB it has the the code U707. I will try this tommorow.
CHECK
I did not seen any Note 3 with full sound hardware bullit , but I faced to not have sound when I flashed a different firmware and I tryed t update trough ODIN to the last firmware nf3 nf4 TRY THAT AND put your news here , DON'T TRY TO OPEN YOUR PHABLET DOES NOT HAVE PRB AND ALSO SAMSUNG INFO app from play... you will se your hardware is ok and also your sound codecs )::)) ODIN 3.07 is the most stable >LAST FIRMWARE (UPGRADE) PROBABLY TO TRY INSERT YOUR CSC AND PIT Country files ( AREA CODE for example XEO mine )
I did reheat al the components on the main board. Nothing happened. But... i did reflash (as a last try)with mobile odin the last build from south est of Europe and miracle happened is up and working well.
PLZ help me on this guys , im going mad on this
HOW TO SOLVE THE " DM-VERITY VERIFICATION FAILED NEED TO CHECK DRK FIRST " or when i install a stock rom this one first appears bUt not in reCovery " DEVICE DOESNT HAVE DRK , INSTALL DRK " ????????
it all happened after i deleted my imei then succesfully restored it with backup when downgrading from that god forsaken CM13 made by raymanFX (it was build 8 i think) , now OTAs and Security patches all face this issue in recovery when installing after being downloaded , now im in middle of nowwhere with no backup and ive tried everything but none works and im not a hacker nor an information thief just a member waiting for HELP... (SM-N910H)
:crying::crying::crying::crying::crying::crying:
! THERE IS NO OFFICIAL SAM CUSTOMER SERVICE IN MY CITY AND mobile merchants are not TRUSTWORTHY !
Someone told me that i need to find a cert file for my Phone and i found it , how is it related to DRK and what should i do with it??
Whatever happens to the phone, if the phone turns on, doesnt have any hardware issue it can be revived.
The universal method is flashing stock firmware through odin
Download your country's note 4 firmware from sammobile and flash it through odin
Works most of the time
For any more help pm m!
yeah. try flashing samsung stock firmware with odin. have you done it
Sent from my SM-N920G using Tapatalk
YEP Odin flash is most of the time a good fix.
ankahuja said:
Whatever happens to the phone, if the phone turns on, doesnt have any hardware issue it can be revived.
The universal method is flashing stock firmware through odin
Download your country's note 4 firmware from sammobile and flash it through odin
Works most of the time
For any more help pm m!
Click to expand...
Click to collapse
well . odin was the first thing to try i have gone even far far away from odin and non works . but a video on youtube got my attention , a guy with a s6 edge had this problem and fixed with some sort of software (i attached it) , a friend of mine says that its sth called BOX and i dont understand him !https://www.youtube.com/watch?v=HlMQQPpqELI
ArmanFGT said:
well . odin was the first thing to try i have gone even far far away from odin and non works . but a video on youtube got my attention , a guy with a s6 edge had this problem and fixed with some sort of software (i attached it) , a friend of mine says that its sth called BOX and i dont understand him !https://www.youtube.com/watch?v=HlMQQPpqELI
Click to expand...
Click to collapse
See here: http://forum.xda-developers.com/note-4/help/dm-verity-verification-failed-recovery-t2945531
Use google and search for
Note 4 DM-VERITY VERIFICATION FAILED
You get a 100 hits.
The same occurred for my LG G3 D855 which has erased its IMEI just for trying 'restore upgrade errors' in the LG mobile support tool. From that onwards I have firmly decided not to flash manually in any way except when official upgrades / uupdates are released via KIES or via OTA update.
Please do not flash by your own as it is always risky. It is not a PC where you can take out the affected hard disk and fix it in a working PC and backup the data.
To all manual flashing persons :
If your phone succeeds in manual flashing, donnot brain wash others to do the same. Not all persons always do R & D in android like you.
sudhakar35 said:
The same occurred for my LG G3 D855 which has erased its IMEI just for trying 'restore upgrade errors' in the LG mobile support tool. From that onwards I have firmly decided not to flash manually in any way except when official upgrades / uupdates are released via KIES or via OTA update.
Please do not flash by your own as it is always risky. It is not a PC where you can take out the affected hard disk and fix it in a working PC and backup the data.
To all manual flashing persons :
If your phone succeeds in manual flashing, donnot brain wash others to do the same. Not all persons always do R & D in android like you.
Click to expand...
Click to collapse
Thanks for the reply but the main problem is that any OTA that comes to note 4 i download them and the device says to restart to recovery to install the Update and i say yes but when it goes to recovery the recovery wont function well since it shows dm-verity error and supported API : 3 the update process fails to complete . My imei is as cool as always i havent had a problem with IMEI since i bought the phone
at least 10000 people have note 4 and none has had the problem ???? REALLY ?
seems like im pretty f***ed up
chappatti said:
See here: http://forum.xda-developers.com/note-4/help/dm-verity-verification-failed-recovery-t2945531
Use google and search for
Note 4 DM-VERITY VERIFICATION FAILED
You get a 100 hits.
Click to expand...
Click to collapse
dear chappati , according to that video i need a physical thing which is called a BOX and a software called GC PRO because that guy had my problem and fixed it with a clicking , but im reasearching for 5 months and nothing comes out . i need information PLZ
Hi, i used to had that problem too, when i first flash a custom rom to my N910G i back up my stock rom.. everthing including EFS.. after that then i wipe everything like normal procedure when u flash a rom. till then 1 day i wanna go back to stock rom i accidentally ticked EFS while i wanna restore that stock rom back up and then i thought it was nothing serious until i flash stock rom with odin and when i boot into stock recovery that dm-verity message was shown, did so much research but no luck. my n910G was on a Singapore firmware, that time it had a update i just try my luck by downloading the latest SG firmware and then that message was gone! m now already on MM no problems like that anymore
Deleted
hello everyone ! I'm facing some serious issue with my s7 edge with fingerprint not working. it gives this' An error has occurred with the fingerprint sensor. If this message appears repeatedly, restart your device.
It's NZ model G935F. So far I have done this but no luck:
1) restarted device
2) wiped cache and data resest
3)flashed stock rom with odin
4) rooted phone with chain fire, Installed titanium backup and from fingerprint app delete data and restart phone! No luck.
5) When i run *#0*# test fingerprint sensor test it says ' Fingerprint initializing Fail '
What else I can do ? I'm currently in India and can't access warranty as it was bought in New Zealand.
indergill said:
hello everyone ! I'm facing some serious issue with my s7 edge with fingerprint not working. it gives this' An error has occurred with the fingerprint sensor. If this message appears repeatedly, restart your device.
It's NZ model G935F. So far I have done this but no luck:
1) restarted device
2) wiped cache and data resest
3)flashed stock rom with odin
4) rooted phone with chain fire, Installed titanium backup and from fingerprint app delete data and restart phone! No luck.
5) When i run *#0*# test fingerprint sensor test it says ' Fingerprint initializing Fail '
What else I can do ? I'm currently in India and can't access warranty as it was bought in New Zealand.
Click to expand...
Click to collapse
I"LL provide DONATION to whosoever can help me !
Id be reflashing a stock rom if all else has failed. If that doesnt work then its a hardware fault. Have you flashed any custom kernels or mods? Have you wet the phone at all?
indergill said:
hello everyone ! I'm facing some serious issue with my s7 edge with fingerprint not working. it gives this' An error has occurred with the fingerprint sensor. If this message appears repeatedly, restart your device.
It's NZ model G935F. So far I have done this but no luck:
1) restarted device
2) wiped cache and data resest
3)flashed stock rom with odin
4) rooted phone with chain fire, Installed titanium backup and from fingerprint app delete data and restart phone! No luck.
5) When i run *#0*# test fingerprint sensor test it says ' Fingerprint initializing Fail '
What else I can do ? I'm currently in India and can't access warranty as it was bought in New Zealand.
Click to expand...
Click to collapse
Ausboy 2011 said:
Id be reflashing a stock rom if all else has failed. If that doesnt work then its a hardware fault. Have you flashed any custom kernels or mods? Have you wet the phone at all?
Click to expand...
Click to collapse
As I said in 3) I have already flashed stock rom and no luck. I just got it from someone so not aware of mods or custom kernels.
Hardware fault then best take it to samsung or refund it
Ausboy 2011 said:
Hardware fault then best take it to samsung or refund it
Click to expand...
Click to collapse
I wish I could ! I bought it from New Zealand but I'm in India now so need a solution!
indergill said:
I wish I could ! I bought it from New Zealand but I'm in India now so need a solution!
Click to expand...
Click to collapse
Hey, Did you fix it? if so, please let me know ..I have the same problem.
This happens to me when I downgrade to Marshmallow from Nougat. Reverting back to Nougat resolves the issue but I wish to downgrade, is there a solution to this?
i23u8 said:
This happens to me when I downgrade to Marshmallow from Nougat. Reverting back to Nougat resolves the issue but I wish to downgrade, is there a solution to this?
Click to expand...
Click to collapse
Yep same thing here. Appears to be an issue with newer hardware releases though the sensor firmware is the same. I wish someone could figure this out.
Hello
My phone suddenly faced a bootloop, i was on cyanogen 13. just looping the Lenovo logo. Not able to get into recocery.. But QFIL detecting phone, and i even flashed the kitkat version of stock.. The process shows success but still im stuck at bootloop, even tried various method.. Your valuable help appreciated here
any help ?
mjtirur said:
any help ?
Click to expand...
Click to collapse
I think it's some hardware problem. The phone when first came to market has one of the best specifications. Other players had significantly higher prices of their phones providing same hardware. So, I think that Lenovo compromised on the hardware components to provide the SD410 and 2gigs of RAM for this price. I many times had problems with proximity and light sensor. Also the battery sometimes awkwardly dies giving very bad backup and only when you decide to replace it, it automatically starts working fine, for some time atleast. Then same thing happens again.
So, I think its problem with some hardware component. Otherwise, flashing from QFIL successfully, would have unbricked the phone.
Im facing the exact same problem as of now...
Managed to boot into recovery somehow and flashed a ROM but then again it went back to bootloop while unlocking the lockscreen
i have solution.
First off all remove battery then insert it again , after this press vol. Up + vol. Down + power on button by doing this your device completely boot recovery which one is now installed with software.
You said previously that your device is on only showning logo , its mean you have 60℅ chance to get your device in working condition.
Bro if you flashed stock kikat firmware then without flashing any software again just simply flash kitkat twrp recovery through adb . After this flash any kitkat rom ( recommended cm 11 by ed300 ) , huree you get your device live.
OR
If you recently flashed stock lolipop then without flashing any software again just simply flash lolipop twrp recovery through adb . After this flash any lolipop based or marshmallow based or naughat based rom , after that any rom from these android version will work , hurreee you got your phone alive but remember dont again directly flash kitkat rom over any lollipop , marshmallow, naughat rom otherwise you will again got bootloop . But you can directly only flash stock kitkat over stock lolipop or stock lolipop over stock kitkat only . I hope you understand what to do :good:
If you have any problem you can simply tell me via my WhatsApp no. - +91 9205097520 (indian no.) Or simply reply me on xda or simply mail me - [email protected] . I have other tricky solution steps ,which were really used and tested by me. Bye friends.......... And Don't forget to tell me about your device problem .
sasukay said:
I think it's some hardware problem. The phone when first came to market has one of the best specifications. Other players had significantly higher prices of their phones providing same hardware. So, I think that Lenovo compromised on the hardware components to provide the SD410 and 2gigs of RAM for this price. I many times had problems with proximity and light sensor. Also the battery sometimes awkwardly dies giving very bad backup and only when you decide to replace it, it automatically starts working fine, for some time atleast. Then same thing happens again.
So, I think its problem with some hardware component. Otherwise, flashing from QFIL successfully, would have unbricked the phone.
Click to expand...
Click to collapse
Okey Bro
nk41319 said:
First off all remove battery then insert it again , after this press vol. Up + vol. Down + power on button by doing this your device completely boot recovery which one is now installed with software.
You said previously that your device is on only showning logo , its mean you have 60℅ chance to get your device in working condition.
Bro if you flashed stock kikat firmware then without flashing any software again just simply flash kitkat twrp recovery through adb . After this flash any kitkat rom ( recommended cm 11 by ed300 ) , huree you get your device live.
OR
If you recently flashed stock lolipop then without flashing any software again just simply flash lolipop twrp recovery through adb . After this flash any lolipop based or marshmallow based or naughat based rom , after that any rom from these android version will work , hurreee you got your phone alive but remember dont again directly flash kitkat rom over any lollipop , marshmallow, naughat rom otherwise you will again got bootloop . But you can directly only flash stock kitkat over stock lolipop or stock lolipop over stock kitkat only . I hope you understand what to do :good:
Click to expand...
Click to collapse
Thanks bro... i will try this and let you know !!!
AmythD said:
Im facing the exact same problem as of now...
Managed to boot into recovery somehow and flashed a ROM but then again it went back to bootloop while unlocking the lockscreen
Click to expand...
Click to collapse
yes man gonna try the above solution.. lets c