Hi,
I want to share my experience about problems with persist file after going back to stock.
I played with some customs and always been something what was missed or not working. After few instalations i decide to go back. After that my fingerprint and camera stops working (errors or not even open). Its a popular problem here and solution is simple - just fastboot the backup persist.img file and ok, but i just lost my backup so tring other way. I spoke with some users to help me with it but always last chance was "go to service centre" (greetings to the greedy @pankspoo aka 4utech). Ok its a solution but even with warranty my service centre refuse repair after back crack and little bend of my phone. So last chance is to pay them or....
First you need to do is check that your engineermode on phone works - on dialer press *#899# We will need this to repair fingerprint.
1. Need to be on rom with fastboot working so Android 11 or 12 (to c.05 firmware).
2.
adb devices
adb reboot bootloader
fastboot devices
fastboot flashing unlock (previously unlock in developer options)
Remember it will erase your data so take backup of your files!
ok now in my case i use other user persist file and just flash it. Here you can download it : PERSIST FILE
fastboot flash persist persist.img
fastboot reboot
After this you are in half way because your camera will work but fingerprint still doesn't. You can in this place lock bootloader (if you want).
fastboot flashing lock (remember always factory data)
So you need something to repair fingerprint.
Solution for that is just simply calibrate fingerprint. For that you will need calibrator or at least "yellow-striped rubber" (in my case blue).
So you need to buy calibrator. You can find Relife RL-071B with all rubbers you need (i used that) or find that stripped one.
So now calibration :
1. On dialer press : *#899#
2. Go to AfterSale Devices Calibration - it will ask for code. Type ther 6776 and ok.
3. You need to skip all other calibrations until fingerprint. (you can just simply go back (previous button or guesture) and press "pass"
4. On fingerprint calibration press start and do what it says (yellow - yellow, black -black , and stripped (in my case blue). Last one is most required because that yellow and black you can do without calibrator. On yellow put your finger on black do not touch screen)
5. That stripped one can not work on first try. You need to have stripp in that way to screen ||||| . When i was trying i have error (Relative illiminance abnormal) but you can simply add some presure. After few tries it shoud work.
6. After calibration you can rebot phone and add fingerprint
(You can find video of calibration on youtube (type oppo finger..... .calibration)
So thats it. Maybe it will save someone. Cheers
!You do it at your own risk and take the responsibility upon yourself. !
Thank you, I hope I can find the calibration device cheap. The F****ing service center wanted 300€ to repair this (it's completely undamaged otherwise)
Will update when I'm done with this
chytrypch said:
Hi,
I want to share my experience about problems with persist file after going back to stock.
I played with some customs and always been something what was missed or not working. After few instalations i decide to go back. After that my fingerprint and camera stops working (errors or not even open). Its a popular problem here and solution is simple - just fastboot the backup persist.img file and ok, but i just lost my backup so tring other way. I spoke with some users to help me with it but always last chance was "go to service centre" (greetings to the greedy @pankspoo aka 4utech). Ok its a solution but even with warranty my service centre refuse repair after back crack and little bend of my phone. So last chance is to pay them or....
First you need to do is check that your engineermode on phone works - on dialer press *#899# We will need this to repair fingerprint.
1. Need to be on rom with fastboot working so Android 11 or 12 (to c.05 firmware).
2.
adb devices
adb reboot bootloader
fastboot devices
fastboot flashing unlock (previously unlock in developer options)
Remember it will erase your data so take backup of your files!
ok now in my case i use other user persist file and just flash it. Here you can download it : PERSIST FILE
fastboot flash persist persist.img
fastboot reboot
After this you are in half way because your camera will work but fingerprint still doesn't. You can in this place lock bootloader (if you want).
fastboot flashing lock (remember always factory data)
So you need something to repair fingerprint.
Solution for that is just simply calibrate fingerprint. For that you will need calibrator or at least "yellow-striped rubber" (in my case blue).
So you need to buy calibrator. You can find Relife RL-071B with all rubbers you need (i used that) or find that stripped one.
So now calibration :
1. On dialer press : *#899#
2. Go to AfterSale Devices Calibration - it will ask for code. Type ther 6776 and ok.
3. You need to skip all other calibrations until fingerprint. (you can just simply go back (previous button or guesture) and press "pass"
4. On fingerprint calibration press start and do what it says (yellow - yellow, black -black , and stripped (in my case blue). Last one is most required because that yellow and black you can do without calibrator. On yellow put your finger on black do not touch screen)
5. That stripped one can not work on first try. You need to have stripp in that way to screen ||||| . When i was trying i have error (Relative illiminance abnormal) but you can simply add some presure. After few tries it shoud work.
6. After calibration you can rebot phone and add fingerprint
(You can find video of calibration on youtube (type oppo finger..... .calibration)
So thats it. Maybe it will save someone. Cheers
!You do it at your own risk and take the responsibility upon yourself. !
Click to expand...
Click to collapse
After we do this fingerprint will work on other roms too right?
Yes. I think that operation repair persist file, which is hidden deep setting for device.
Give here fedback when you done it.
chytrypch said:
Yes. I think that operation repair persist file, which is hidden deep setting for device.
Give here fedback when you done it.
Click to expand...
Click to collapse
Okay I will, I've ordered the calibrator wich arrives in 4 April, I'll update y'all
okay so i actually received the calibrator today, and it worked! btw i ordered the rl-071A wich is enough, and also the stripped one i succeded with only one rubber in the actual square, because otherwhise it would give me an error telling me too much pressure, u may get an error telling u that u are not putting enough pressure, i just added some with my finger, but very little force, good luck to everyone who tries
Related
Hi there!
My girlfriend bought an LG Wine (the clamshell one with only one screen), branded by TIM. After using it for a couple of days, it requests a password to get in. She can't remember to have set one, trying all her usual passwords failed. She needs to get access to the phone again, but luckily it does not contain any data that can't be wiped.
Using Google, I could not find any how-to that worked, the tip stated in android-recovery.info/1776/recovery/LG/Wine didn't get my to a recovery screen. Instead the phone booted up almost normally and stated "safe mode" ("Abgesicherter Modus" as it is using a German localisation) on the bottom right corner of the screen.
I'm no Android expert, but I'm a developer for embedded systems, so I'm familiar with the command line and I'm pretty sure that I can follow any how-to to get either the password protection removed or the phone to do a factory reset. Downloading and installing any (free) developer tools (for Linux or Windows) should be also no problem.
So, how can I get this phone reset to factory defaults? Or is there an easier way to remove the password?
SvOlli said:
Hi there!
My girlfriend bought an LG Wine (the clamshell one with only one screen), branded by TIM. After using it for a couple of days, it requests a password to get in. She can't remember to have set one, trying all her usual passwords failed. She needs to get access to the phone again, but luckily it does not contain any data that can't be wiped.
Using Google, I could not find any how-to that worked, the tip stated in android-recovery.info/1776/recovery/LG/Wine didn't get my to a recovery screen. Instead the phone booted up almost normally and stated "safe mode" ("Abgesicherter Modus" as it is using a German localisation) on the bottom right corner of the screen.
I'm no Android expert, but I'm a developer for embedded systems, so I'm familiar with the command line and I'm pretty sure that I can follow any how-to to get either the password protection removed or the phone to do a factory reset. Downloading and installing any (free) developer tools (for Linux or Windows) should be also no problem.
So, how can I get this phone reset to factory defaults? Or is there an easier way to remove the password?
Click to expand...
Click to collapse
i dont know anything about your device, and couldnt seem to find anything to help me.
through a combination of buttons when off, you should be able to get into a download or fastboot mode (hopefully).
you will need to put fastboot on your machine. a quick search should find it.
while the phone is in the preboot mode i described, open a command prompt in the fastboot dir. you may have to wait for some drivers to install, you may also have to find some drivers if the next step fails to see the device.
in the command prompt enter, fastboot -w
hopefully you will see some dialogue indicating progress.
when its done remove the cable and force reboot the phone, or remove the battery and replace if need be.
if it worked, the phone will boot up and be clean like new.
as i said, this is mostly an assumption on my part that your phone can get into this mode and has fastboot capability, some dont.
as another possible option from this download screen would be to flash stock with the lg flash tool, but that would be dependent on you finding the proper stock file, and being able to enter download mode.
other than these possible options, i dont know what else you could try.
Hello,
I am encountering a strange problem with my new Redmi Note 2, purchased from Top One. Whenever it is off and the battery is in, every 30 seconds it will vibrate and momentarily flash the white Mi logo as if it is about to turn on, then it will go back to black, then do this again in ~30sec. I have tried removing the back of the phone to see if it is an issue with the power button but it continues to happen whenever the battery is in. If battery is removed for ten seconds and then put back, the issue stops -- but then as soon as I turn the phone on, and then power off, it starts again. Otherwise the phone seems to run normally.
I flashed it to Miui 7.2.2.0 global stable Rom immediately after receiving it, and the problem has been there from the start. I believe I had noticed it there even before I flashed the new rom but I'm not sure as I hadn't yet interacted with the phone much...
Any suggestions? If you could please give me your instructions as basically as possible, and for Mac, I would appreciate it as I am a newbie. I flashed the rom using my Mac following instructions from the MIUI forms that showed how to do it in terminal after installing "adb/fastboot."
Thanks!
Seems to me that it is going into bootloader mode, instead of powering off completely. I am not sure how this could have started - perhaps a partially failed ROM upgrade at some point. I think you should return it (after restoring the original ROM) because trying to solve the problem might have to involve doing some low-level and extremely risky stuff.
Or for some weird reason the buttons get stuck and restarts to recovery.
When you try to boot into recovery, you get black screen->vibration->MI logo, and if you continue pressing the buttons you repeat the pattern.
Remove the battery cover and check if there's something in the buttons for a start..
Thanks for your responses
DarthJabba9 said:
Seems to me that it is going into bootloader mode, instead of powering off completely. I am not sure how this could have started - perhaps a partially failed ROM upgrade at some point. I think you should return it (after restoring the original ROM) because trying to solve the problem might have to involve doing some low-level and extremely risky stuff.
Click to expand...
Click to collapse
Could you give me a sense of what the low-level/risky stuff would be? Is it something I might be able to get done at a phone repair shop in the UK (where Xiaomi of course is not sold)? I ask because I'm required to pay for return shipping to China if I'm going to return device, and god knows how long the whole return process will take -- so if it's not a major hardware issue it might be worth it for me to explore finding a fix.
tonydeli7 said:
Or for some weird reason the buttons get stuck and restarts to recovery.
When you try to boot into recovery, you get black screen->vibration->MI logo, and if you continue pressing the buttons you repeat the pattern.
Remove the battery cover and check if there's something in the buttons for a start..
Click to expand...
Click to collapse
I don't see anything unusual in the buttons. As I said, if I remove the battery for ten seconds and then put it back in, I don't get this problem. It's only after doing a successful boot/shutdown (which works normally) that it starts again. So as far as I can tell it doesn't appear to be a mechanical problem.
littleozzyman said:
Thanks for your responses
Could you give me a sense of what the low-level/risky stuff would be? Is it something I might be able to get done at a phone repair shop in the UK (where Xiaomi of course is not sold)? I ask because I'm required to pay for return shipping to China if I'm going to return device, and god knows how long the whole return process will take -- so if it's not a major hardware issue it might be worth it for me to explore finding a fix.
Click to expand...
Click to collapse
The low-level+very risky stuff would involve flashing a full ROM. By "full", I mean inclusive of preloader, uboot/lk, etc. This is what makes it very risky, because if something goes wrong with the preloader/lk flash, the device could be bricked beyond what normal people could recover. An example of a ROM that flashes everything is: http://www.needrom.com/download/miui-7-2-3-0-redmi-note-2/
My current ROM is based on an earlier version of this, and I noted at the time it was released that it installs a preloader - but I am not sure whether I installed it complete with preloader or not (I probably did). From what I can see, nobody's device got bricked by installing this ROM, which is actually excellent (so much so that I inevitably return to it after trying something else). However, it is still risky to upgrade a preloader. I suspect that this may be what you need - but it may not resolve your problem anyway.
PS: beware of more recent Xiaomi ROMs that lock the bootloader. If you tried to do this risky process, you would be best advised to make sure that you are not flashing a ROM that locks the bootloader (i.e., the most recent ROMs coming out from Xiaomi).
DarthJabba9 said:
The low-level+very risky stuff would involve flashing a full ROM. By "full", I mean inclusive of preloader, uboot/lk, etc. This is what makes it very risky, because if something goes wrong with the preloader/lk flash, the device could be bricked beyond what normal people could recover. An example of a ROM that flashes everything is:
My current ROM is based on an earlier version of this, and I noted at the time it was released that it installs a preloader - but I am not sure whether I installed it complete with preloader or not (I probably did). From what I can see, nobody's device got bricked by installing this ROM, which is actually excellent (so much so that I inevitably return to it after trying something else). However, it is still risky to upgrade a preloader. I suspect that this may be what you need - but it may not resolve your problem anyway.
PS: beware of more recent Xiaomi ROMs that lock the bootloader. If you tried to do this risky process, you would be best advised to make sure that you are not flashing a ROM that locks the bootloader (i.e., the most recent ROMs coming out from Xiaomi).
Click to expand...
Click to collapse
Thanks for this. Could you point me to how I might be able to install a full official Xiaomi rom? (One that won't lock the boot loader.) My preference would be to get the global stable rom running as normal so that I can have the standard working phone with OTA updates. Or, is it easier to install this rom you've suggested with preloader, and then afterwards I can flash the official rom (assuming this fixes the problem)?
Also, are there any tutorials/clearer instructions for how to do this kind of install? The instructions on the link you've provided don't seem very clear...
Not sure if I'm gonna try this yet but leaning towards it if I feel confident enough I can execute it without screwing anything up...
littleozzyman said:
Thanks for this. Could you point me to how I might be able to install a full official Xiaomi rom? (One that won't lock the boot loader.) My preference would be to get the global stable rom running as normal so that I can have the standard working phone with OTA updates. Or, is it easier to install this rom you've suggested with preloader, and then afterwards I can flash the official rom (assuming this fixes the problem)?
Also, are there any tutorials/clearer instructions for how to do this kind of install? The instructions on the link you've provided don't seem very clear...
Not sure if I'm gonna try this yet but leaning towards it if I feel confident enough I can execute it without screwing anything up...
Click to expand...
Click to collapse
I personally wouldn't touch official ROMs with a bargepole. At the very least, xiaomi.eu, or ROMs based on it (like the one linked to). But each to his own. With regard to installation, I don't think you can get more detailed instructions than those given, which I will now try to present in clearer English:
Reboot to Recovery ( TWRP only )
Wipe Dalvik/Art
Wipe cache
Wipe data (note that TWRP allows you to do 2-4 in one go - they are the same as resetting to factory defaults)
Install ROM
Wipe cache and Dalvik/Art again (but do NOT wipe data)
Reboot
Wait for about 20 minutes while it builds Dalvik/Art, and other stuff
Done
Hopefully, this will cure the problem. If so, then you can install whatever ROM you want, following the same process as above. If not, then you still have an excellent ROM anyway.
By the way, doing any of this presupposes that you have already installed TWRP recovery. If not, then that is the first thing to do.
DarthJabba9 said:
I personally wouldn't touch official ROMs with a bargepole. At the very least, xiaomi.eu, or ROMs based on it (like the one linked to). But each to his own. With regard to installation, I don't think you can get more detailed instructions than those given, which I will now try to present in clearer English:
Reboot to Recovery ( TWRP only )
Wipe Dalvik/Art
Wipe cache
Wipe data (note that TWRP allows you to do 2-4 in one go - they are the same as resetting to factory defaults)
Install ROM
Wipe cache and Dalvik/Art again (but do NOT wipe data)
Reboot
Wait for about 20 minutes while it builds Dalvik/Art, and other stuff
Done
Hopefully, this will cure the problem. If so, then you can install whatever ROM you want, following the same process as above. If not, then you still have an excellent ROM anyway.
By the way, doing any of this presupposes that you have already installed TWRP recovery. If not, then that is the first thing to do.
Click to expand...
Click to collapse
Thanks for the English translation haha, I'll give this a shot. Just one more question -- when you write "install ROM", I should just treat the ROM the same way that I would any other, by flashing it via fastboot (as I did in OSX terminal) right?
littleozzyman said:
Thanks for the English translation haha, I'll give this a shot. Just one more question -- when you write "install ROM", I should just treat the ROM the same way that I would any other, by flashing it via fastboot (as I did in OSX terminal) right?
Click to expand...
Click to collapse
No. Steps 1 to 7 inclusive are done from TWRP Recovery.
DarthJabba9 said:
No. Steps 1 to 7 inclusive are done from TWRP Recovery.
Click to expand...
Click to collapse
Well, thanks again for your suggestion, but unfortunately it didn't succeed. I managed to install the custom full ROM you suggested with TWRP, and the problem persists; when the phone is off, I get this strange problem with the Mi logo flashing.
I'm investigating how to make a return, but I thought I would ask: do you have any idea whether this problem will negatively affect the phone in any other way? Because, if I'm unable to make a return, I think it's an issue I can live with (I rarely have my phone switched off anyhow), so long as it won't cause more problems down the line...
Something else I just realised: Apparently the problem doesn't occur when the phone is plugged into the USB (both electrical socket and computer). Starts up again as soon as I remove the plug. Perhaps that provides more context...
littleozzyman said:
Well, thanks again for your suggestion, but unfortunately it didn't succeed. I managed to install the custom full ROM you suggested with TWRP, and the problem persists; when the phone is off, I get this strange problem with the Mi logo flashing.
I'm investigating how to make a return, but I thought I would ask: do you have any idea whether this problem will negatively affect the phone in any other way? Because, if I'm unable to make a return, I think it's an issue I can live with (I rarely have my phone switched off anyhow), so long as it won't cause more problems down the line...
Click to expand...
Click to collapse
Well, I would hazard a guess that this is not a software problem. Clearly, the phone is trying to boot into bootloader mode or into recovery mode when it is meant to be completely switched off. This implies;
a) that there is a possibly a hardware problem somewhere (eg., something short-circuiting somewhere?), or
b) a virus/rootkit trying to dial home?, or
c) some other unknown fault?
None of these options would give me any peace of mind. If the problem is (b) then a good anti-virus or rootkit remover program would solve the problem. Search the PlayStore for those. If that doesn't solve the problem, then it's either (a) or (c) - and that is not good.
DarthJabba9 said:
Well, I would hazard a guess that this is not a software problem. Clearly, the phone is trying to boot into bootloader mode or into recovery mode when it is meant to be completely switched off. This implies;
a) that there is a possibly a hardware problem somewhere (eg., something short-circuiting somewhere?), or
b) a virus/rootkit trying to dial home?, or
c) some other unknown fault?
None of these options would give me any peace of mind. If the problem is (b) then a good anti-virus or rootkit remover program would solve the problem. Search the PlayStore for those. If that doesn't solve the problem, then it's either (a) or (c) - and that is not good.
Click to expand...
Click to collapse
Nothing shows up on anti-virus/rootkit. I guess I should really insist on getting a return. Hopefully they will process it without too much fuss/expense. If any other suggestions come to anybody in the meantime, I'd be glad to hear them.
I just noticed as well that someone posted with what seems to be the same issue to mine last year: http://forum.xda-developers.com/redmi-note-2/help/phone-rebooting-shutdown-t3232941 , with no resolution. Perhaps this is some kind of occasional manufacturing problem.
littleozzyman said:
Nothing shows up on anti-virus/rootkit. I guess I should really insist on getting a return.
Click to expand...
Click to collapse
Absolutely.
HW problem: Power Management IC
I too faced this problem and I suspected Battery to be the culprit . Anyway , i got it checked and repaired at a local (non xiaomi) repair shop that claims it was the issue with PMIC power management IC and that he has replaced the IC .
Now the phone works fine and does not enter into that bootloop even when charger is disconnected and phone is rebooted manually. I hope the problem is resolved .
However , the other issue is still persistent which is : copper colored washed out MI logo constantly appears on the screen and reinstallation of sw did not help either . In india these repairmen usually cant explain the problem area if it is outside of "Try and test" scheme .
I spent 1000INR to get it repaired but I highly doubt that PMIC is replaced. Coz this repair guy did this replacement in just 6 work hours. probability of getting the right part at right time at his disposal is very slim. And I had seen his workstation once, where i di not see any SMT repair station either. Which means that he cannot replace BGA package IC at all. Anyway, I will receive the phone tonight. Lets hope it works fine and the other problem gets rectified by flashing.
Saurabh Srivastava, Noida , India
Hello guys,
I am really in need of help. For reason that does not matter any more I have tried to root my phone and now it is unable to start. I followed the steps listed in the below tutorial:
bbs.elephone.hk/thread-9919-1-1.html
However after following some steps, video tutorials and further confusions I ended up trying to "Firmaware Upgrade" my phone with SPFlash Tool, but unfortunately the process was ended prematurely and my phone is not able to start at all (black screen and no reaction from any button). I understand that everyone must take responsibility for the consequences followed by rooting a phone, but I wanted to ask you guys if I am able to recover the phone or I would need to buy a new one.
Here is more detailed information of what I tried and what is the problem I am experiencing:
- Error that I see when I try to "Format & Download" (or any other option / action that SPFlash tool has):
BROOM ERROR : STATUS_PRELOADER_INVALID (-1073545212)
[HINT]:
- What I tried:
1. Reinstalling the drivers because I tought that they are incorrect. Every downloaded dirver results to the same error and I believe that the issue is not related to the dirvers at all (I use Windows 7 Ultimate with the SP_Driver_v2.0).
2. Tried using different versions for SPFlash Tool, but it appears that only the latest ones works with the scatter file that I have (MT6755_Android_scatter.txt). Versions that I tried are - v5.1552; v5.1524; v5.1620; and after trying evrything I believe that the issue is not related to the used tool nor scatter file.
My conclusion is that somewhere along the way I re-formatted my phone, but since the processes ended prematurely this may have disrupted the correct format of the internal storage.
Is is possible to recover from this and if it is what steps / actions should I take to do so. I would really appreciated some help of you guys and will be glad if the phone is working back (promise to stop being a "hacker").
Best Regards,
A fellow that need helps or a new phone
I just wanted to add that I was able to recover my phone. YEY!!!!
For those of your who ran to the same problem here is what I did to restore the phone from the boot loop:
1. Remove the battery - this is quite a tricky part, but if you follow the steps and be careful there should not be any problems:
- Remove the back from the phone - since it is no meant to be easily removed you could use a plastic card and start from the top of the phone (where the ear jack is located).
- After that you would need to remove the top plastic cover - it is placed to protect the main board and all modules. You would need a small "Philips" screwdriver in order to remove all screws. Note that there is one hidden screw that is placed on the middle bottom part of the plastic cover. You could recognize it by the elephone logo placed on top of it.
- Once the plastic cover is removed you will see the connector of the battery. Remove so that the device is actually turned off.
2. Download a STOCK ROM for your device:
- The STOCK ROM for Elephone P9000Lite was downloaded from here:
4pda.ru/forum/index.php?showtopic=697579&st=20#entry47838700
All required images along with the scatter.txt file should present inside the downloaded archive.
3. Flash the ROM by using SPFlash tool:
- What I did here is to follow a tutorial that is specifically for hard bricked devices:
devs-lab.com/how-to-unbrick-mediatek-device.html
In my case I had to use the Format + Download option in SPFlash tool and select all images to be flashed. The important part was that the phone's battery had to be disconnected, all images selected by clicking the "Format + Download" option and finally hit the "Download" button. Once this is done you can connect the battery again and connect the device to your computer.
After the process is completed the device can be powered on and it should start booting.
I hope that I can help someone with these steps and that you do not give up on your phone.
Best Regards,
Happy fellow that resurrected his pone
I've bricked my other devices before and all i had to do to fix it, was remove the battery and format & download the original software. As you meantioned, with P9000 (same as with the Lite version), the problem is non-removable back cover and battery. Thank you for this tutorial, but it'd be better is somebody make a video tutorial or just add any media at all as many people might not want to do it, because of fear to break something under the back cover
Thanks for this, I am currently in the same position you were. I've cracked open the phone and am just trying to work out which connector feeds the power from the battery. I was pretty sure my problem was repairable so wasn't too stressed, but I hadn't thought to attempt to open the phone up like you did. It was surprisingly easy, and I don't think I'll have done any permanent damage. I'm hoping I can get the phone going again without any data loss, I was trying to flash recovery when I bricked it so hopefully I simply flash TWRP and she boots again.
awedxz said:
I just wanted to add that I was able to recover my phone. YEY!!!!
For those of your who ran to the same problem here is what I did to restore the phone from the boot loop:
1. Remove the battery - this is quite a tricky part, but if you follow the steps and be careful there should not be any problems:
- Remove the back from the phone - since it is no meant to be easily removed you could use a plastic card and start from the top of the phone (where the ear jack is located).
- After that you would need to remove the top plastic cover - it is placed to protect the main board and all modules. You would need a small "Philips" screwdriver in order to remove all screws. Note that there is one hidden screw that is placed on the middle bottom part of the plastic cover. You could recognize it by the elephone logo placed on top of it.
- Once the plastic cover is removed you will see the connector of the battery. Remove so that the device is actually turned off.
2. Download a STOCK ROM for your device:
- The STOCK ROM for Elephone P9000Lite was downloaded from here:
4pda.ru/forum/index.php?showtopic=697579&st=20#entry47838700
All required images along with the scatter.txt file should present inside the downloaded archive.
3. Flash the ROM by using SPFlash tool:
- What I did here is to follow a tutorial that is specifically for hard bricked devices:
devs-lab.com/how-to-unbrick-mediatek-device.html
In my case I had to use the Format + Download option in SPFlash tool and select all images to be flashed. The important part was that the phone's battery had to be disconnected, all images selected by clicking the "Format + Download" option and finally hit the "Download" button. Once this is done you can connect the battery again and connect the device to your computer.
After the process is completed the device can be powered on and it should start booting.
I hope that I can help someone with these steps and that you do not give up on your phone.
Best Regards,
Happy fellow that resurrected his pone
Click to expand...
Click to collapse
Hello all. I softbricked my phone while attempting to flash TWRP, and ended up with a phone that wouldn't present anything on screen. So I've located an old XP computer to rule out any driver issues, and using the battery removal mentioned above I was able to flash the factory 20160422 firmware which is what I believe my phone had before I started tinkering. I unticked the userdata box as I flashed it, and left the recovery box ticked which I thought would fix any corrupt recovery that my tinkering caused. The flash took some time, but I got the green tick indicating that it went well. However I still get nothing on screen, the only time I get anything is when I plug it into charge, I get a green battery charge icon for a few seconds before it fades away. If I leave it plugged in for a while, the screens starts to faintly flash sporadically. Does anyone have any advise for me? @awedxz, could you please confirm that the battery connection is on the far left, a shiny copper ribbon with a small silver rectangle plug that clicks into the board?
jiddahidda said:
Hello all. I softbricked my phone while attempting to flash TWRP, and ended up with a phone that wouldn't present anything on screen. So I've located an old XP computer to rule out any driver issues, and using the battery removal mentioned above I was able to flash the factory 20160422 firmware which is what I believe my phone had before I started tinkering. I unticked the userdata box as I flashed it, and left the recovery box ticked which I thought would fix any corrupt recovery that my tinkering caused. The flash took some time, but I got the green tick indicating that it went well. However I still get nothing on screen, the only time I get anything is when I plug it into charge, I get a green battery charge icon for a few seconds before it fades away. If I leave it plugged in for a while, the screens starts to faintly flash sporadically. Does anyone have any advise for me? @awedxz, could you please confirm that the battery connection is on the far left, a shiny copper ribbon with a small silver rectangle plug that clicks into the board?
Click to expand...
Click to collapse
Let it to charge more time
Thanks mate, this advise was spot on. It must have had 0% battery after fixing it! It's now alive and charging up. How neat that Mediatek devices can be unbricked so easily, although I'll have to be a bit more careful in future I think! My previous devices have been Motorola, HTC and Samsung devices, each with different tools and flashing techniques. Haven't bricked any of them in the past, but it's nice knowing this device will be hard to permanently brick.
chtsarts said:
Let it to charge more time
Click to expand...
Click to collapse
Had the same problem, a small cable that goes from the power button was disconnected. Connect the cable and it should run just fine
Just to chime in, I soft bricked my phone as well.
I managed to get it back to life, without taking the phone apart, so that is not a necessity.
Here's what happened: I had CM13 installed on the phone and wanted to go back to stock, so I flashed it according to the guides, also overwriting the preloader.
After that, the phone was dead, as in unable to turn on, no charger detection etc.
As is already known, this phone has an "emergency" line / device, that will turn on once you connect it to the computer and press the VOL+ button (the device will show up for a couple seconds in the Windows device manager).
So what I tried was to flash it again and again, to no avail; sp_flashtool reported the following error after trying to flash the preloader: "BROM ERROR - STATUS_EXT_RAM_EXCEPTION (-1073414139)"
Finally I tried different stock roms, from the Elephone forum.
The one that did the trick for me was the 20160304 - I loaded the scatter file into sp_flash tool and only flashed the preloader. After that, Windows suddenly recognized the phone as the preloader device, the screen turned on showing the charging image and the notification led lit up. I was able to flash the phone without errors again.
After that I flashed the rest of the stock firmware - without the preloader.
I then let the phone charge a little bit and it turned back on.
If that version of the preloader does not do the trick for you, try different ones.
No need to take the phone apart.
Good luck everyone!
For everyone's else information having this problem. I also bricked my P9000 whilst flashing TWRP and getting the RAM error. I tried every options possible but the only one that worked was to disconnect the battery. It is actually a very easy process as described as above. The battery connector is the small connector nearest to the volume buttons with the bronze coloured connector cable. It simply lifts up and your battery is disconnect. I changed the settings in SP FLASH to without battery and my phone flashed without any problems. Before this, it had been dead for over a week and all other methods failed to wake it up. Hope this helps.
---------- Post added at 11:36 AM ---------- Previous post was at 11:07 AM ----------
This video may help also
https://www.youtube.com/watch?v=irDOXh1QoKE
Hi everyone! I had the same problem (bricked phone not recognised by flash tool ecc ecc) and disconnecting the battery did the trick, but I may have messed up with some
The screen connectors and now the screen lits up but stays black. Sounds and touch screen work (I can unlock the screen because I hear the unlock sound), but the screen stays black... If I have damaged the connector (I think it's the one on the upper left, the thinner one that doesn't really click when inserted) there is not much to do, but I just wanted to know If anyone had the same issue and eventually resolved it.
I rooted my Tmobile LG k330 using kingroot and then unistalled it and replaced it with superuser. A couple weeks after, my camera stopped working and I couldnt even access my gallery at first. Wait.. It gets better. My sms starts continually alerting me that it has stopped and I had to use titanium pro to freeze the app so it would stop flashing . Eventually I uninstalled it and installed a non stock version from the playstore. All well and good but I have tried every trick out there on how to get my camera to start working again but every technique out there never worked for me. First off, superuser stops working and says that I have no bootlaoder on my mobile and the site it sends me to is of no use and is confusing to figure out how I lost booloader in the first place. Back to my camera.. So it says that it is unable to work even with other playstore camera apps bc another app was using camera but no matter what forum advice out there tells me to do to find out what maliscious app could be the culprit and even through process of elemination tactics using safety mode I cant locate the real issue. My software update wont update. It goes to restart and as its almost half way through installing it reads error and freezes so that I cant even do a hard reset. Im at the end of my ropes and dont know what to do. No factory reset bc of uninstalled stock with no back up. Cant I somehow reinstall stock apps from lollipop through a particular site? I would would wipe everything on my mobile just to return it to its original function. Is there a way to flash an LG Software system with the same original bootloader and stock apps thatI originally had on my phone
Hello, Damian0402.
I do not know what to say in regards to the camera / SMS suddenly not functioning. I'd assume that means you tampered with them or perhaps something else you installed tampered with them at some point (although that's moot at this point and really no sense in discussing it, unless it happens again).
Flashing the phone to factory stock:
I'd suggest you visit this link, download the image for your phone ("K330" f / h / i / j / k / L -- Which?): https://mega.nz/#F!sdwRDLbZ!yPOiRPv5QJS_9I4hzL4ptQ!YBRwWazA
You need to look up exactly what K330 image you need to flash with. I use MetroPCS and is listed as "m" in the software under "About" in my phone, but I actually run the "MS330 10i" shown in that website. Try Googling everything about your device.
Tool to use:
I can not say beyond a doubt that this will function with a T-Mobile version, but I have no reason to doubt it!
You can use the "LG UP" software to flash the stock ROM firmware (found at that link; The KDZ file is ~1GB or more).
You'll want to download the Lab v1.10 version of LG UP: https://www.mylgphones.com/download-lg-up-software
On the right panel, you'll see "LG USB drivers" hyperlink. This'll ensure you have the proper drivers.
Initiating "download mode":
Power down your device completely. Press and hold the "VOLUME UP" key; While holding the VOLUME UP KEY: Insert the USB cable (it should already be attached to the PC).
The phone will automatically power on and the "DOWNLOAD MODE" image should appear, nearly instantly. After this appears: Release the VOLUME UP key.
You should be able to place the phone down and run the LG UP software. You need to select "UPGRADE" (not "refurbished"), then locate the KDZ file (bottom right corner of the program is a vertical "3-dot" image; Used to navigate to your *.kdz file).
Merely hit "START" and wait about ~300s (~5m). The phone will reboot itself. You can exit the program at this point by pressing "Exit."
That's all.
Regarding Kingroot / Kingoroot:
I'm not entirely sure I trust those "one-click-root" programs. There's nothing harmful about them, however: You should be informed that you can root your own phone WITHOUT those programs!
Tools you'll need and use:
TWRP (Team Win Recovery Project)
SuperSU (SuperUser; The same type program Kingroot/KingOroot install)
ADB (Android Debug-bridge -- Which Kingroot uses remotely I suspect)
This is a thread I wrote last night; I use the MetroPCS variant, but the steps are identical: https://forum.xda-developers.com/lg-k7/how-to/guide-lg-k7-ms330-concise-tutorial-t3722050
You should be able to use the TWRP listed in the forum post (LG K7 (M1)). You might want to NOT erase/flash recovery partition first. Just live-boot it. If it works: Great! Decide if you want to flash it.
I hope this solves your issues! Also: TWRP / ADB can be used to create a FULL backup directly on your PC without using the phone's internal memory or external memory at all. Which is awesome if you have an 8GB (uncompressed) backup file to make.
My two cents: Rooting the phone yourself with ADB/TWRP/SuperSU is a very fun, interactive and easy process!
Hi, long story short, I bricked my phone due to a mistake from my part trying to install TWRP. I was on version V12.0.3.0.RFQEUXM, I have magisk installed and thus no access to OTA update. I saw that the V12.0.5.0.RFQEUXM was out, so decided to update. Before that, I had the bad idea to say to myself that I would take a backup with TWRP, and kabaaaam, I probably made something stupid and bricked my phone.
Luckily, plugging it to my computer showed me that it was in EDL mode. And thanks to the stupidity of Xiaomi at the end of 2020 when they bricked phones with the Android 11 update, I came across the guide of @nullby to unbrick it. Maybe I should have looked at this into more details and only use it to reflash the boot, but I flashed everything.
I followed this guide, except that at the end instead of flashing the repacked service ROM, I directly flashed the V12.0.5.0.RFQEUXM.
Hooray, the phone is unbricked, I reflashed magisk and everything is back to normal. Almost everything I should say, as the fingerprint sensor is not active anymore. Nothing happens when I try to add a fingerprint, so I suppose that it is something like a driver fault. When using Droid Info, I also see no reference next to FOD.
So now, how to resolve this ? My best guess would be to flash the latest firmware found here. It's only 69Mb and by looking at what's in it, there are definitively things that are not included in the full fastboot rom. But before I try, I prefer to ask for some advice instead of bricking it again…
Also, seen my last experience with TWRP, may I flash it with FK Kernel manager instead ? I've never used it, but from what I read, it should work.
Any ideas or suggestions ?
Thanks a lot.
I'm replying to myself in case anyone has the same issue in the future:
Enter the phone dialer and enter the following code: * # * # 64663 # * # * then press on the 3 points above and go to FingerPrint_C.
Press on start, then it will ask to put "FLESH_FLAT" you need to put a white sheet on the fingerprint sensor, in daylight and launch the test.
then you will ask to put "BLACK_FLAT". then you put something black and opaque on the fingerprint sensor and launch the test. Putting the phone upside-down on a table also work.
If you have the "performance_test failed", try again.
When successful, restart the phone and enjoy the fingerprint again.
Credit to u/danmech on reddit.