Develop Bugs

Data recovery

I broke my screen a couple of days ago. I don't want to change the screen since i decided to buy a new phone. However, I'll like to recover my data from the phone.
Here's my phone condition before i messed it up a bit.
1) Screen cracked and digitizer completely non functional.
2) USB debugging off.
The first time i cracked my screen( yes this is the second time), i used my phone explorer to connect to my phone since my USB debugging was on that time, but this time it was off. So i decided to Google for solution and try to flash recovery and mount my memory in order to get back my media.
I used this: http://forum.xda-developers.com/showthread.php?t=2249500
teeny bin plus TWRP and try to go in to recovery. But the TWRP version was not for E975 and it has the password prompt problem. So i decided to fastboot CWM into it directly via adb. I downloaded the latest E975 non touch CWM and fast boot it.
I can control and access into the CWM menu but it keep giving me Error mounting /data! when i try to mount /data and the screen just flash once and go back to the mounts menu when i press mount USB storage.
I thought it was the ROM problem so i tried to flash the original ROM using LG support tool. It successfully flashed the ROM but it get stuck in the starhub logo ( a Singapore telecom and the phone is from Singapore). And then i try to flash E97510G_00.kdz(i'm not sure what version is this but it's a stock ROM) using kdz updater but it stuck in the LG logo too.
So now i'm wondering if my data are still there in the memory or already been wiped out during the process. If it isn't, it'll be really helpful if anyone can guide me through the data recovery process.

So no one can help?

zibion said:
So no one can help?
Click to expand...
Click to collapse
KDZ flashing delete all data.

artit said:
KDZ flashing delete all data.
Click to expand...
Click to collapse
Ahh i see, no hope in salvaging my contacts then. Thanks for the info. Appreciate it

noob to G Pro(E980) - SUCCESS!

Should get it tomorrow - used E980(ATT)
My plan is to OTA update (wifi) to the latest (May 2014 (h) I believe)
Then towel root to root it (latest I could find is 111KB)(2 locations including the lambda)
Then play install SuperSU and install that (I normally flash SuperSU from recovery after flashing a ROM(and gapps))
Then, if root tests okay:
install FreeGee from play and run it to unlock BL and flash recovery (probably Philz, or CWM since BlissPop seems to have trouble with TWRP)(or versa visa)(darn)
Intent is to then upgrade stock to make it usable (apps and all)(TiBkpPro, etc), and then back it up and play with BlissPop and/or CM11N, and whatever.
Anyone see any problems with my plan?
THANKS!!!
(coming from a year of Moto Atrix HD)
(Mod move to Q&A please )

KrisM22 said:
Should get it tomorrow - used E980(ATT)
My plan is to OTA update (wifi) to the latest (May 2014 (h) I believe)
Then towel root to root it (latest I could find is 111KB)(2 locations including the lambda)
Then play install SuperSU and install that (I normally flash SuperSU from recovery after flashing a ROM(and gapps))
Then, if root tests okay:
install FreeGee from play and run it to unlock BL and flash recovery (probably Philz, or CWM since BlissPop seems to have trouble with TWRP)(or versa visa)(darn)
Intent is to then upgrade stock to make it usable (apps and all)(TiBkpPro, etc), and then back it up and play with BlissPop and/or CM11N, and whatever.
Anyone see any problems with my plan?
THANKS!!!
(coming from a year of Moto Atrix HD)
(Mod move to Q&A please )
Click to expand...
Click to collapse
Dunno, yesterday I got a G Pro E988 on KitKat cannot be rooted via Towelroot keep saying device not supported. More worst I can't flash any ROM on it, not detectable by LG Mobile Flasher either. Luckily I got make a backup with TWRP.

soralz said:
Dunno, yesterday I got a G Pro E988 on KitKat cannot be rooted via Towelroot keep saying device not supported. More worst I can't flash any ROM on it, not detectable by LG Mobile Flasher either. Luckily I got make a backup with TWRP.
Click to expand...
Click to collapse
off topic.
but, since you've got TWRP, bootloader is unlocked, ergo, stock is rooted. Try install SuperSU from googleplay, and run it. Check with checkroot app. Dunno as I am not at all experienced with any LGOGP. Good luck!!!

KrisM22 said:
off topic.
but, since you've got TWRP, bootloader is unlocked, ergo, stock is rooted. Try install SuperSU from googleplay, and run it. Check with checkroot app. Dunno as I am not at all experienced with any LGOGP. Good luck!!!
Click to expand...
Click to collapse
It's rooted after I found a method. Using Korean G Pro root method than I manage to flash recovery via flashify. Other recovery that require's loki I am unable to use it, cannot flash CM11 ROM's on it.
Like this, if I can't put CM on it I leave it in drawer pending for selling. P/s: I didn't use the phone more than 4 hours. LOL
http://forum.xda-developers.com/optimus-g-pro/help/help-g-pro-t2974676

soralz said:
It's rooted after I found a method. Using Korean G Pro root method than I manage to flash recovery via flashify. Other recovery that require's loki I am unable to use it, cannot flash CM11 ROM's on it.
Like this, if I can't put CM on it I leave it in drawer pending for selling. P/s: I didn't use the phone more than 4 hours. LOL
http://forum.xda-developers.com/optimus-g-pro/help/help-g-pro-t2974676
Click to expand...
Click to collapse
Uh, yeah - you were off topic, HOWEVER, it appears that freegee is not working correctly as it failed on my E980. I used that app to send shellnut an email, so hopefully he sees that and fixes that if possible. (Note, my E980 arrived with 20h - ie - current.
So while waiting for that, at least I have root so I will go ahead and spruce up stock and back it up. if it doesn't get fixed, I will be relatively happy on stock as many seem to like that best.

KrisM22 said:
Uh, yeah - you were off topic, HOWEVER, it appears that freegee is not working correctly as it failed on my E980. I used that app to send shellnut an email, so hopefully he sees that and fixes that if possible. (Note, my E980 arrived with 20h - ie - current.
So while waiting for that, at least I have root so I will go ahead and spruce up stock and back it up. if it doesn't get fixed, I will be relatively happy on stock as many seem to like that best.
Click to expand...
Click to collapse
Well, anyway for some reason I have decided to keep it because now I am able to flash ROM's and root it already. My method is I downgraded from E98820b to E98820a firmware then I am able to root it and enter download mode.

soralz said:
Well, anyway for some reason I have decided to keep it because now I am able to flash ROM's and root it already. My method is I downgraded from E98820b to E98820a firmware then I am able to root it and enter download mode.
Click to expand...
Click to collapse
Yeah, keep it...
I on the other hand just hosed mine by trying to flashify a lokified recovery, so now all I get is a
Secure booting error
Cause: booting certification verify.
Any idea how I fix that? All I can find is tot files, no sdk or whatever that the program requires...
how did you downgrade from b to a?

KrisM22 said:
Yeah, keep it...
I on the other hand just hosed mine by trying to flashify a lokified recovery, so now all I get is a
Secure booting error
Cause: booting certification verify.
Any idea how I fix that? All I can find is tot files, no sdk or whatever that the program requires...
Click to expand...
Click to collapse
Do you still remember your build number and Android version?
Are you able to enter download mode? Vol up + down + USB Cable.

soralz said:
Do you still remember your build number and Android version?
Are you able to enter download mode? Vol up + down + USB Cable.
Click to expand...
Click to collapse
Just put it in DL mode - thanks!
as I recall: 4.4.2, 20h is all I remember.
it offers me ra,kdz or rc.kdz which one? or some other?

KrisM22 said:
Just put it in DL mode - thanks!
as I recall: 4.4.2, 20h is all I remember.
it offers me ra,kdz or rc.kdz which one? or some other?
Click to expand...
Click to collapse
Base on your region choose the appropriate *.kdz file. Then use LG Flash Tool 2014 to flaah it.

soralz said:
Base on your region choose the appropriate *.kdz file. Then use LG Flash Tool 2014 to flaah it.
Click to expand...
Click to collapse
need baby steps here. am US, Boston so do I choose A or C?
lg flash tool does not offer me place to select dll or tot files.

Choose your firmware.
http://lg-phone-firmware.com/mobile/index.php?mod=Lg+Optimus+G+Pro&paese=TWN/TAIWAN&id_mod=25
Then guide.
http://forum.xda-developers.com/showthread.php?t=2420219

soralz said:
Choose your firmware.
http://lg-phone-firmware.com/mobile/index.php?mod=Lg+Optimus+G+Pro&paese=TWN/TAIWAN&id_mod=25
Then guide.
http://forum.xda-developers.com/showthread.php?t=2420219
Click to expand...
Click to collapse
got it.
I used method 2 of http://forum.xda-developers.com/showthread.php?t=2420219
where did you get that recovery file you are using?

KrisM22 said:
Should get it tomorrow - used E980(ATT)
My plan is to OTA update (wifi) to the latest (May 2014 (h) I believe)
Then towel root to root it (latest I could find is 111KB)(2 locations including the lambda)
Then play install SuperSU and install that (I normally flash SuperSU from recovery after flashing a ROM(and gapps))
Then, if root tests okay:
install FreeGee from play and run it to unlock BL and flash recovery (probably Philz, or CWM since BlissPop seems to have trouble with TWRP)(or versa visa)(darn)
Intent is to then upgrade stock to make it usable (apps and all)(TiBkpPro, etc), and then back it up and play with BlissPop and/or CM11N, and whatever.
Anyone see any problems with my plan?
THANKS!!!
(coming from a year of Moto Atrix HD)
(Mod move to Q&A please )
Click to expand...
Click to collapse
"BlissPop seems to have trouble with TWRP"
Freegee TWRP + BOSP == no problems for me.

culot said:
"BlissPop seems to have trouble with TWRP"
Freegee TWRP + BOSP == no problems for me.
Click to expand...
Click to collapse
Hi, and thanks for that note.
However, I have no way to flash anything other than stock as freegee doesn't work and the thing, I think it was you, suggested(G Pro Recovery GK), didn't either.
Slightly bummed... LOL At least I have root and can run stock tailored.

KrisM22 said:
Hi, and thanks for that note.
However, I have no way to flash anything other than stock as freegee doesn't work and the thing, I think it was you, suggested(G Pro Recovery GK), didn't either.
Slightly bummed... LOL At least I have root and can run stock tailored.
Click to expand...
Click to collapse
Why doesn't Freegee work? I know I could never get it to work unless I flashed the Sphinx GPro recovery first, as Freegee wouldn't recognize my e980 as worthy until I did so. Then after that Freegee would open-arm me and let me pick between its CWM or TWRP recovery. (I don't bother with any of those anymore, as I've put together a batch file that does it all in one swoop, as I'm constantly flashing my phone, and I can't be bothered with Towelroot or Freegee's online-only crap. So there.)
The game goes:
- Root.
- (I always install the ADBD Insecure app here, as you can then remount the system as read/write, full root access via ADB, so no more clock-blocking to impede your dominance.)
- Flash Sphinx GPro Recovery, but *do not* reboot into it, as you *will* get errors when you try to flash most anything. Instead, directly after install the recovery from Sphinx GPro:
- Install Freegee and now that GPro recovery is flashed, Freegee will recognize your device and should work flawlessly.
There is also the option of flashing the TWRP 2.8 from the Sphinx GK Recovery, as it is by far the very nicest recovery option for this device. It is, however, buggy, and not rock-solid like the Freegee TWRP. There is also Philz recovery, which has a lot more features than CWM, but every time I've used it (many times), it has gave me problems and forced me to flash back to stock. IMHO: Freegee's CWM or TWRP is the way to go for stability, and the way to go for successful flashing.
(Note: this is for an e980, anything else is uncouth.)

Thanks for reply!
okay, what I did was
(run towelroot and install SuperSU (from play), run that and reboot)
install "adbd insecure" (from play) and checked both boxes
ran sphinx gpro recovery 6044 (link above) but didn't reboot.
ran freegee and had it install cwm6047
Now how do I boot into cwm : vol-up+power !
EDIT: don't forget to put this on your SD card http://forum.xda-developers.com/optimus-g-pro/help/guide-how-to-fix-recovery-bootloop-t2950716 so you can escape the boot to recovery loop.
PM me your paypal and I'll donate thanks!!!

KrisM22 said:
Thanks for reply!
okay, what I did was
install adbd insecure and checked both boxes
ran gpro kk recovery
ran freegee and had it install twrp 2633
Now how do I boot into twrp? power voldn?
I booted to twrp from stock but don't know how to get there from power off... vol-up+home+power?
PM me your paypal and I'll donate thanks!!!
Click to expand...
Click to collapse
From device off:
- Hold VOL+ and POWER key together until you the LG logo comes up, then briefly let go of the power button then immediately press down again, while still holding the VOL+ button, and hold it until the LG logo screen disappears, then let go of both of those buttons and tap VOL-, VOL-, POWER -- do not hold, just tap (I'm not certain this last step is needed, but it doesn't hurt, as long as you don't hold the buttons down, just tap, quickly press.
That'll get you into TWRP.
Or you can boot up the device entirely, normally and use ADB to do it,
via a shell/console/command prompt:
adb devices <---- this should read 'device' and not unauthorized.
adb reboot recovery <---- this will reboot your device in recovery mode.
If you get into TWRP and the touchscreen doesn't work, that can be fixed/bypass by initiating a device reset from a cold boot (holding down both volume buttons and power button until it asks for Reset, then pressing power again to go for it). Sometimes it's a problem, but since you did GPro over kitkat first, probably not.
EDIT: okay, I see CWM is now on the menu: same deal, just ignore the touchscreen TWRP part, as you'll probably be thankful to *not* use the touchscreen in CWM (it's a bit annoying and laggy, but usable, whereas TWRP w/o touchscreen is worthless).

culot said:
From device off:
- Hold VOL+ and POWER key together until you the LG logo comes up, then briefly let go of the power button then immediately press down again and hold it until the LG logo screen disappears, then let go of both of those buttons and tap VOL-, VOL-, POWER -- do not hold, just tap (I'm not certain this last step is needed, but it doesn't hurt, as long as you don't hold the buttons down, just tap, quickly press.
That'll get you into TWRP.
Or you can boot up the device entirely, normally and use ADB to do it,
via a shell/console/command prompt:
adb devices <---- this should read 'device' and not unauthorized.
adb reboot recovery <---- this will reboot your device in recovery mode.
If you get into TWRP and the touchscreen doesn't work, that can be fixed/bypass by initiating a device reset from a cold boot (holding down both volume buttons and power button until it asks for Reset, then pressing power again to go for it). Sometimes it's a problem, but since you did GPro over kitkat first, probably not.
Click to expand...
Click to collapse
Thanks! I had edited that post while you were replying.
I used freegee again to just flash cwm 6047 since twrp didn't seem to want to backup to external sd card. I just backed up with cwm and restoring now to check it...
Huge thanks!!!!
need paypal for small donate!

KrisM22 said:
Thanks! I had edited that post while you were replying.
I used freegee again to just flash cwm 6047 since twrp didn't seem to want to backup to external sd card. I just backed up with cwm and restoring now to check it...
Huge thanks!!!!
need paypal for small donate!
Click to expand...
Click to collapse
Thanks, but 'XDA Guidelines, Standard Conduct, and Practices, Vol. VI' maintains that all donations less than 6 digits in size, must be funneled into at least one of these prequalified outlets, and I quote,
- Taking mom out for pancakes.
- Spoonfeeding a homeless person two cheeseburgers (lullaby optional).
- Scratch & Lose lottery ticket surreptitiously deposited into a place where the results of discovery can be viewed and enjoyed.
- Chili dogs.
- Cat litter + shelter/pound = not quite chili dog-level, but quite admirable.
...
and it goes on, so forth, in that manner. I'd just dump it all into a Galaga machine anyways.

LG G3 Stuck In Bootloop

Hi XDA, many threads here have helped me in the past so time to ask another (probably stupid) question. It's a bit of a long story so I apologise in advance.
I've been running CM (one of the nightly builds from about 3 weeks back, don't have the file so I can't say which) on my phone for a while with no issues until a couple of nights ago when it was overheating (charging while playing a game, stupid I know) so I decided to turn it off so it could cool down without taking it off charge.
The following morning I turn it back on to find that it's getting to the blue android head logo of CM and getting stuck there. First thing I do is reboot into TWRP and flash my backup from right after I installed CM. Reboot and... same result. Okay, no biggie right? Time to reinstall CM (the latest nightly build from yesterday) and Google Apps (nano package) via TWRP and reboot again. Still stuck at the blue android head logo. The reinstall was handled after using the Wipe-Factory Reset function of TWRP, as the guide here explains.
At this point I decide to do a bit of research and learn that it's called a softbrick or bootloop and apparently flashing the stock rom can fix it. The LG software suite won't even recognise the device but a friend of mine found this guide so I attempted to run through it. All goes well until it comes time for the software to connect to the phone - I pop it in download mode while putting the USB cable in, the program says waiting for connection, runs for 14 seconds and says it's trying to put the phone into download mode, at this point it fails saying the phone can't be put into download mode.
Some of the comments beneath the article offer fixes like using USB 2.0 instead of 3.0, putting the program into compatability mode for Win7 and running in administrator mode. To be thorough I tried every USB port on my machine (both 2.0 and 3.0) and run the program in compatability mode (with and without admin mode) for several versions of windows. Same result every time.
Another friend then suggests that somehow permissions got borked and it might be worth reflashing SuperSU to the system but at this point I'm at a loss for how to do that. I have the one click root script that I got from god knows where (not this one because that didn't work for me) that has a SuperSU zip in it, presumably it flashes that to the phone when it runs (found this out the hard way because I've been a moron in the past and tried installing SuperSU through TWRP and broke the boot previously, fixed by re-running the one click root script - this was ages ago before even installing CM.)
So right now I can put the phone into download mode manually, get into TWRP and use all its functions as well as connect to my PC and use ADB functions while the phone's in TWRP but can't boot into CM or flash a stock rom. Any help would be appreciated, I've spent a whole day reading guides, asking friends and clumsily trying to fix this only to get nowhere.

Have u tried installing the stock via TWRP? Via zip ... Wipe cache delvik also..

jinderation said:
Have u tried installing the stock via TWRP? Via zip ... Wipe cache delvik also..
Click to expand...
Click to collapse
I haven't tried that, I didn't even know it was possible. Could you give me some more detailed pointers on how to do this? I noticed that the stock ROM I have cames as a .TOT file but CM is several files and folders in the zip. Will it install fine from that zipped up TOT file?
Thank you so much for your time.

When the rom is uploaded by the dev its also uploaded in .zip file place it ur system rom just go into twrp recovery flash the the zip file before flashing wipe cache n delvik too its easy as 1,2,3 search here on xda for ur compatible model

jinderation said:
When the rom is uploaded by the dev its also uploaded in .zip file place it ur system rom just go into twrp recovery flash the the zip file before flashing wipe cache n delvik too its easy as 1,2,3 search here on xda for ur compatible model
Click to expand...
Click to collapse
Thank you so much. I got it sorted. I really appreciate you taking the time to help me out with my stupidity.

[help] [oneplus3] [stuck in boot logo] [softbricked] cannot boot into system [solved]

Hey boss., after flashing open beta 12, the phone started hanging now and then. I tried to contact oneplus forums and they asked me to send the log files. Since they took too long to respond, I went to oneplus service centre. They flashed my phone with old oxygen os and the phone didn't start. It went into bootloop
Then I asked them, they said motherboard is corrupted. I left the place and I requested online customer support from oneplus. They too flshed and concluded the same. Can I know whether flashing/sideloading openbeta created this issue? If so, can you provide me support to avail the warranty on the phone? or recover it via any other method or process?
Please respond as soon as possible. My communication with the world has become limited after this issue. I hope there is some sort of support.
Also note that, the phone can boot into fastboot mode, but bootloader is locked. It can boot into recovery. I tried wiping everything, but the phone is not rebooting.
When I start the phone, it stucks in the boot logo and after a while, the screen becomes blank and a white color notification LED is glowing.
Kindly help me.

i had the same issue last week after updating to 13..and i tried to flash the black theme..it went black..i had nothing....it was like it was bricked... here's how after many failed attempt's..i had to clean out all files including backups.wipe data i had to wipe system i had to clean out all previous files.from TWRP recovery.then i had to download the latest software release then put the zip file in my phone storage not in the download file ..then i had to flash stock recovery.then install the new system..and i made the mistake of trying to use some of my app backups like for one estrong file ..all of them were corrupt.so start fresh.

You might try this unbricking method:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Though your device isn't hard-bricked, this would reset your device to the absolute factory settings (watch out, your data will be erased) on an older OxygenOS version.
I would recommend the 2nd Method, as it restores all partitions to factory settings.
I might also know where your issue came from:
Though you can flash the Open Beta (or any other ZIP from OnePlus) through the Stock Recovery, OnePlus states that you need to be on an unlocked bootloader for not bricking your device.

TimSchumi said:
You might try this unbricking method:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Though your device isn't hard-bricked, this would reset your device to the absolute factory settings (watch out, your data will be erased) on an older OxygenOS version.
I would recommend the 2nd Method, as it restores all partitions to factory settings.
I might also know where your issue came from:
Though you can flash the Open Beta (or any other ZIP from OnePlus) through the Stock Recovery, OnePlus states that you need to be on an unlocked bootloader for not bricking your device.
Click to expand...
Click to collapse
It worked, but no network connection or wifi connection!
Is there a way to bring them back?

SivaMaxwell said:
It worked, but no network connection or wifi connection!
Is there a way to bring them back?
Click to expand...
Click to collapse
You might try to unlock your bootloader (There are giudes to do this) and flash a OxygenOS package from oneplus.net through the stock recovery, to ensure the firmware is OK (Do a factory reset from recovery!). I don't know if the Unbrick Tool only restores corrupted partitions or all. It might have installed the wrong system over your previously installed firmware if only corrupted partitions are restored. Keep the bootloader unlocked to be on the safe side (After some time you will be able to just ignore the boot message and you have better access to fastboot and recovery)!
Also, GG to OnePlus for (fake) Motherboard corruption!
About warranty:
Warranty should be ok as long as you won't do hardware modifications (I think).
Bootloader unlocking is definitely safe

TimSchumi said:
You might try to unlock your bootloader (There are giudes to do this) and flash a OxygenOS package from oneplus.net through the stock recovery, to ensure the firmware is OK (Do a factory reset from recovery!). I don't know if the Unbrick Tool only restores corrupted partitions or all. It might have installed the wrong system over your previously installed firmware if only corrupted partitions are restored. Keep the bootloader unlocked to be on the safe side (After some time you will be able to just ignore the boot message and you have better access to fastboot and recovery)!
Also, GG to OnePlus for (fake) Motherboard corruption!
About warranty:
Warranty should be ok as long as you won't do hardware modifications (I think).
Bootloader unlocking is definitely safe
Click to expand...
Click to collapse
I tried to update to recent oxygen os. Then the original proble started again.
It is not booting up, again..

SivaMaxwell said:
I tried to update to recent oxygen os. Then the original proble started again.
It is not booting up, again..
Click to expand...
Click to collapse
No, reflash the OxygenOS package of the same Version that is installed by the Unbrick Tool (If you can still get itfrom oneplus.net) and then check if Network does work. Also, check your IMEI.

I think you might have a corrupted EFS partition. That's y you don't have a working network. Check whether your device show a IMEI under about phone.

m4manusraj said:
I think you might have a corrupted EFS partition. That's y you don't have a working network. Check whether your device show a IMEI under about phone.
Click to expand...
Click to collapse
EFS doesn't have an effect on WiFi.
That's why I think that it is a firmware issue

I think, I have solved it guys. I'll let you know once completely under control

So, Thank you very much for your support. With this little support from you and my previous Foresightedness helped me restore the phone.
So just in case if any one else faces the same or similar problem, this is the process:
STEP0: If there is any partition corrupted, the device don't boot properly. And, The customer care/ sevice centre guys state it as motherboard problem. Donot Panic. Always take TWRP backup whenever you change your ROM. This Backup helps you to restore whenever you're in trouble. In this particular case, ESF backup is required. So, take a complete backup (everything) in TWRP, it saves your ass.. keep the backup in your PC or any safe Storage (the complete TWRP Folder which is in Internal Memory) before flashing any custom ROM.
Step1: Follow method2 in this guide: https://forums.oneplus.net/threads/g...plus-3.452634/
Step2: if everything is alright, its done. Otherwise, The device boots up with some missing features and details. At this time, you have to unlock the bootloader. See The forum to know how to do it. Basic searching can give you the method.
If you can transfer the TWRP folder from PC to Phone, it's good. But the phone boots itself because of missing firmware. Even Bluetooth couldn;'t be used.
In my particular case, I couldnot copy from PC to mobile or viceversa. So, you cannot copy back your TWRP folder in this situation.
So, Unlock bootloader. Then reboot to system (without doing anything)
Step3: Reboot to bootloader and flash TWRP 3-0.2 version only. otherwise device will be encrypted.
Step4: download Ressurection Remix ROM version : ResurrectionRemix-M-v5.7.4-20161113-PUBLIC-ex-oneplus3 or you can experiment with any other custom ROM but only android 6 (*Marshmallow). Also make sure that you have universal adb drivers. install them if not (search in the forums.)
Step5: goto TWRP recovery, in this, goto wipe option. Drag the swipe to wipe button here. (normal wipe).
Step6: Now, in advanced options, select adb sideload option and select the two wipes in the next menu. Start ADB sideload in the TWRP.
Step7: Now, Start the adb sideloading the custom ROM from your PC. You donot Require Gapps for transferring a file. So donot flash Gapps.
Step8: After the sideload is complete, reboot into system. Now you can transfer files between phone and PC. Now, Copy the Complete TWRP folder into the internal memory. A pop-up asks for merging the folders. Allow the merging, even if you have another TWRP backup there. They don't overlap.
Step9: Now, Boot into TWRP and restore completely. The phone boots up properly, this time. Everything works as expected. every mysterious problem is solved. Now you will get update request if you are on previous version of OOS.
Last but not Least: Please do not use any app recovery tools. they may cause issues while following the above steps
Thank to every XDA member, helping us save the time and money we spend at service center.

m4manusraj said:
I think you might have a corrupted EFS partition. That's y you don't have a working network. Check whether your device show a IMEI under about phone.
Click to expand...
Click to collapse
TimSchumi said:
EFS doesn't have an effect on WiFi.
That's why I think that it is a firmware issue
Click to expand...
Click to collapse
Yes, boss. The EFS is corrupted. But, thanks to TWRP, it also has the option to backup EFS, modem. SO, I used my old backup from Jan2017 to restore it back.
But, TO place TWRP back in phone, the original OOS3.1.2, even after reflashing didn't support. I thought for a while and flashed the All loved RR (MM) . THen, it gave me the scope to t/f the folder to internal memory.
Now, I restored the EFS , Modem, sytem with data. and hell yea!! the phone is back to life.
Complete Backup, Atleast once for 3 months saves your ass..

I am glad it helped. That's the power of Xda.

My OP3 is stuck on the boot animation only while booting up Oxygen OS. At first I thought it was bricked but as I proceeded I found out that it isn't and i'm able to boot other OS on it. I've had Resurrection Remix which I had no problems flashing whatsoever. But I'm having this problem with Oxygen OS. Has anyone experienced this? What do I do? Please help.

TWRP recovery not working on Blackview BV9500

Hi everybody,
I try to root my Blackview BV9500 by installing first TWRP recovery. I use fastboot mode on a linux laptop to do that.
I successfully flash the twrp recovery image, but after that, the phone don't boot in recovery anymore.
It try to boot into recovery, but it reboot in normal mode a few second after.
I tried also with the cmd "fastboot boot recovery.img".
When i flash back the original recovery image, it work, i can boot the original recovery without any problem.
Does anyone have the problem?
Some one can help me to find a solution?

I, too, am trying to do this. I have not yet flashed it... I was going to use the fastboot boot command to boot the recovery kernel before permanently flashing it, to make sure it would work, and in my googling I stumbled across this post. Serendipity! [Edit 3: Although, reading your post again, I see you tried that as well and it didn't succeed for you. For me, it simply tells me remote: command not found, so how were you able to even get that to work?]
All that said... I have the BV9500 Pro, specifically for the two-way radio, so I'm going to try to keep that little tidbit of hardware working in the process. I mainly just want to tweak the menus a bit, tweak the quick settings, get root, delete the Google crapps I won't be using...
On to your problem, though, I can't help much but maybe if we post back and forth our successes and failures we might be able to stumble through it together?
First, I assume you already have unlocked your bootloader? [Edit: Honestly, I'm not sure flashing the recovery would be allowed without first unlocking the bootloader]
[Edit 2: Perhaps this thread might be of help. Different model, but often the hardwares used by manufacturers are similar enough that the same steps generally work. ]

Thank you for the link, maybe i need to flash the complete rom with the twrp recovery with spflash tools, and it will work.
I will try and let you know, but i will make a backup of my rom before flashing it!
For your problem with fastboot, maybee it's because you need to install it. You can use the command "sudo apt-get install fastboot" on a terminal window if you are on linux.
If you want to enter the recovery mode, you don't need to use fastboot, you can simply enter it by pressing Volume Up and Power buttons together for a couple of seconds when your phone is off.
When Boot Mode appears release all keys.
To flash recovery with fastboot, you need first to enable the developer mode on your phone (go to "Settings > About phone" and make 7th tap on the build number, the Developer options will be unlocked and available), and unlock the bootloader of course.
here what is the process i made to flash the recovery :
- i use the command "adb devices" to check if the phone is well connected. (response is like "BV9500S320001179 device")
- then i enter in fastboot mode with "adb reboot bootloader" (phone reboot and ask confirmation for fastboot mode)
- check with command "fastboot devices"
- unlock the bootloader with the command "fastboot oem unlock" or "fastboot flashing unlock".
- flash the phone with the twrp recovery with "fastboot flash recovery recovery.img"
- reboot the phone in recovery mode with "fastboot boot recovery.img"
Normally the phone boot in twrp recovery.
Hope that will help you too.

I am too facing this problem. In case you got any solutions please let me know too.

Yves596 said:
For your problem with fastboot, maybee it's because you need to install it. You can use the command "sudo apt-get install fastboot" on a terminal window if you are on linux.
Click to expand...
Click to collapse
Yup. Already had fastboot installed for the LG G5 this phone replaced, the Galaxy Note 4 the LG replaced, the MyTouch 4G Slide the Galaxy replaced, my wife's old Galaxy S5 I used in the interims... LOL, I've got a working install. No, the "Remote: command not found" was returned from within.... Whether fastboot or adb, I forget now, but I was able to get the file to flash eventually, after reading your first post, but unfortunately the phone would not boot to it (nor Android). I thought I'd bricked it. Twice this happened. Each time, after about 5 minutes, it eventually booted to Android.
I flashed the recovery from the ROM in the link Blackview sent me and was able to boot their recovery just fine, so there's something in the TWRP that my particular phone doesn't like.
If you want to enter the recovery mode, you don't need to use fastboot, you can simply enter it by pressing Volume Up and Power buttons together for a couple of seconds when your phone is off.
When Boot Mode appears release all keys.
Click to expand...
Click to collapse
Thanks, I keep forgetting which keys to hold for recovery versus bootloader, so I use the adb command to be sure without having to keep a notepad nearby.
Clearly I don't do this as often as I used to.
(snip)
- flash the phone with the twrp recovery with "fastboot flash recovery recovery.img"
- reboot the phone in recovery mode with "fastboot boot recovery.img"
Normally the phone boot in twrp recovery.
Hope that will help you too.
Click to expand...
Click to collapse
Now that was something I haven't done since the T-Mobile G1 days. My understanding was that you CAN boot a recovery without flashing it first if you"fastboot boot {image filename}" but that didn't work for me either. I'm also assuming that the filename to flash can be anything because the device stores it to a partition, so it shouldn't have to be specifically "recovery-verified.img".
The recovery you have... Were you ever able to boot to it? If so, would you be willing to share a link to its download source, please?
I've got to run for a prior engagement, I'll check back later.
Thanks!

veronicadavis said:
I am too facing this problem. In case you got any solutions please let me know too.
Click to expand...
Click to collapse
I guess i find the reason why the modified recovery image won't boot.
I find an interesting information in a post of osm0sis (https://forum.xda-developers.com/showthread.php?t=2073775) were he say : "some newer MediaTek (MTK) devices use special image signing that adds a "BFBF" pre-header signature, so images will unpack/repack but most likely won't boot unless run through their internal signing tool."
After more search, i find an interesting publication (http://www.lieberbiber.de/2015/07/04/mediatek-details-partitions-and-preloader/) witch confirm that.
They say in conclusion of the publication :
"Yes, I can confirm that SignTool is able to add digital signature information to firmware images. Signed images have an additional header “BFBF” and some fluff which SP Flash Tool checks on a secure device. Apparently some manufacturers merely used the default MTK key for signing the images, making them no better off than a typical insecure MTK device."
So we have to find another way to install magisk to root it.

Root 9500/pro
Mine rooted already....you guys can check on 4pda russian forum
Note : do not use the 17.1 version of magisk there because after reboot the device will freeze if you resboot after twrp 1st install...instead flash 17.3+ or 18+ right after first install of twrp...
EDIT : dont mind the russian language in TWRP as you can change it to english once there

Yves596 said:
Hi everybody,
I try to root my Blackview BV9500 by installing first TWRP recovery. I use fastboot mode on a linux laptop to do that.
I successfully flash the twrp recovery image, but after that, the phone don't boot in recovery anymore.
It try to boot into recovery, but it reboot in normal mode a few second after.
I tried also with the cmd "fastboot boot recovery.img".
When i flash back the original recovery image, it work, i can boot the original recovery without any problem.
Does anyone have the problem?
Some one can help me to find a solution?
Click to expand...
Click to collapse
Hello I have same problem... Do you have that original recovery file? I don't have and I would like to get that back. Thanks.

DL this:
needrom. com/ download/bv9500pro- bv9500-root/ (delete spaces)
- Copy Magisk-v18.0.zip and disable_encryption_9500.zip to external SD-Card or OTG device
- backup your data from internal SD-Card
- do a factory reset and turn off phone without entering the setup guide after reboot, or wipe via recovery and power off
- Flash recovery.img using scatter.txt with SP Flash Tool
- boot into recovery with hold down vol + and power
- switch TWRP to your language and install Magisk-v18.0.zip and disable_encryption.zip
- reboot and update or install MagiskManager-v6.1.0.apk
Thanks to Jemmini from 4pda.ru

kanadali said:
DL this:
needrom. com/ download/bv9500pro- bv9500-root/ (delete spaces)
- Copy Magisk-v18.0.zip and disable_encryption_9500.zip to external SD-Card or OTG device
- backup your data from internal SD-Card
- do a factory reset and turn off phone without entering the setup guide after reboot, or wipe via recovery and power off
- Flash recovery.img using scatter.txt with SP Flash Tool
- boot into recovery with hold down vol + and power
- switch TWRP to your language and install Magisk-v18.0.zip and disable_encryption.zip
- reboot and update or install MagiskManager-v6.1.0.apk
Thanks to Jemmini from 4pda.ru
Click to expand...
Click to collapse
Thank you for your help and Jemmini help too, it work fine.
But on the firmware version 20180629.

Yves596 said:
Thank you for your help and Jemmini help too, it work fine.
But on the firmware version 20180629.
Click to expand...
Click to collapse
you can just download latest firmware and simply backup NVRAM etc with sp flash tool also flash with sp tool, you will have then working twrp with disabled encryption. there are tons of post regarding using sp flash tool on this forum
im using same phone and did these actions on first day and did not have any problem with twrp or magisk

Hi,
I've bought this phone in Pro version. I rooted my phone using needrom.com/download/bv9500pro-bv9500-root/ and adb after unlocking bootloader. Then I failed with errors. Then I used SPFlashTool in root mode with official 2018092919_s32v63c2k_jk_pro.rar rom (I don't find it anymore on the net but 1) I got it on Blackview official forum and 2) I have the file on my own PC) with format+Download and replace recovery with TWRP from Jemmini from 4pda.ru before flashing. OK.
Then I rooted again: format /data with TWRP, then install disable_encryption.zip, wipe dalvik, reboot on TWRP, then install Magisk, wipe dalvik, reboot normally.
Beware: TWRP is in Russian language at first boot, so to get it in English, first slide the first slide (allowing writing), then select 'Настройки', then the globe on top, then English, then 'Установитъ Язык'.
Hope this helps.
Then, this is my first rooted phone, so I plan to make a custom rom without Gapps (then maybe without Mediatek Ones and agold too) and remake all functionning with apps from Fdroid. Help needed on a manner of removing a system/vendor app properly. Help needed too to add V4A, as I could see max version supported is Nougat. I announce this here as my first post, but my project will be a full post. If someone want help please ask here or MP me
Note: an update of magisk is out (official 18.1), I installed it and my phone tells me a message that facial recognition was not working anymore then it only boots on TWRP... I reflashed it and my phone boots normally again. Wait and see...
Thanks to Jemmini from 4pda.ru again.
Bests Regards

nr0000000 said:
Hi,
I've bought this phone in Pro version. I rooted my phone using needrom.com/download/bv9500pro-bv9500-root/ and adb after unlocking bootloader. Then I failed with errors. Then I used SPFlashTool in root mode with official 2018092919_s32v63c2k_jk_pro.rar rom (I don't find it anymore on the net but 1) I got it on Blackview official forum and 2) I have the file on my own PC) with format+Download and replace recovery with TWRP from Jemmini from 4pda.ru before flashing. OK.
Then I rooted again: format /data with TWRP, then install disable_encryption.zip, wipe dalvik, reboot on TWRP, then install Magisk, wipe dalvik, reboot normally.
Beware: TWRP is in Russian language at first boot, so to get it in English, first slide the first slide (allowing writing), then select 'Настройки', then the globe on top, then English, then 'Установитъ Язык'.
Hope this helps.
Then, this is my first rooted phone, so I plan to make a custom rom without Gapps (then maybe without Mediatek Ones and agold too) and remake all functionning with apps from Fdroid. Help needed on a manner of removing a system/vendor app properly. Help needed too to add V4A, as I could see max version supported is Nougat. I announce this here as my first post, but my project will be a full post. If someone want help please ask here or MP me
Note: an update of magisk is out (official 18.1), I installed it and my phone tells me a message that facial recognition was not working anymore then it only boots on TWRP... I reflashed it and my phone boots normally again. Wait and see...
Thanks to Jemmini from 4pda.ru again.
Bests Regards
Click to expand...
Click to collapse
It'd be great to have another rom but I'm facing a problem with battery life. Basically mobile network standby drains 5000mah battery every day i turned off from developer option but still problem is there. I have checked every single post on Google but nobody has solution for this. U guys face this problem too?

kanadali said:
It'd be great to have another rom but I'm facing a problem with battery life. Basically mobile network standby drains 5000mah battery every day i turned off from developer option but still problem is there. I have checked every single post on Google but nobody has solution for this. U guys face this problem too?
Click to expand...
Click to collapse
New update has been released today. It solves some battery issues, but be very careful.
I installed it, having TWRP and now I'm stuck in TWRP. I've tried to wipe everything but I'm still in TWRP.
I'll try SPFlashTool ... hope it works.

Everything restored & updated.
Using SPFlashTool I flashed all files included in 2018092919_s32v63c2k_jk_pro.rar (including original recovery instead of TWRP).
After that, Android booted and then, using OTA, I updated to latest version.

Reflected_God said:
New update has been released today. It solves some battery issues, but be very careful.
I installed it, having TWRP and now I'm stuck in TWRP. I've tried to wipe everything but I'm still in TWRP.
I'll try SPFlashTool ... hope it works.
Click to expand...
Click to collapse
Could you please send me the link? Can't find it on blackview forum

kanadali said:
Could you please send me the link? Can't find it on blackview forum
Click to expand...
Click to collapse
The latest version is not on the forum. I installed via OTA.
But if you mean the previous firmware, there is one link on the blackview forum: http://bbs.blackview.hk/viewtopic.php?t=480235#p795494
SP Flash tools are well documented here: https://forum.xda-developers.com/showthread.php?t=1982587
And a complete list of blackview bv9500 / bv9500 pro files and instructions (in russian): https://4pda.ru/forum/index.php?showtopic=931296
Hope you find what you are looking for.

@kanadali,
for the moment I'm not facing battery drain because there is not simcard in it at this state of my modifications, sorry.
@Reflected_God,
I think this is the link I used, I use the 2018092919_s32v63c2k_jk_pro.rar rom for base.
For all others who faces big problems like me (facial recognition not working then reboot on twrp only, I could reflash my phone with SPFlashTool, the rom and twrp from Jemmini/4PDA in russian only (others don't work for me). I used Format + Download in root mode on Linux. Then format /data with TWRP, then install disable_encryption.zip, wipe dalvik, reboot on TWRP, then install Magisk, wipe dalvik, reboot normally. Do other things. To remove gapps I disabled/force stop it before remove with TWRP. Others apps I can't disable simply remove with TWRP. I test if I encounter bugs but none for the moment. If someone wants to know what I do I've made a LibreOffice Calc sheet log, which evolve when I have time
Hope this helps
Bests Regards

Need Files or a GOOD guide. bv9500 NOT PRO.
If someone could upload the exact files that they used, and the exact same steps, that would be great. Please mention what stock version you have and a link to the image if possible as well. I've followed numerous different guides, with multiple different rom versions, multiple different recovery imgs, used sp flash tool and adb/fastboot multiple times, tried making sure everything was unlocked before each try, have all the necessary drivers, and the closest I get to a functional twrp recovery is a green line that appears at the top of the boot screen before it reboots. Ive tried going to the source, the russian site, but all of the links are 404ed. if not for me, then it would be great to just have this all in one place. Thank you please future hero.
Please include exact program versions (ex SP Flash) as well if not zips of them. I am sorry to be asking so much in one post however I truly didn't know what else to do. And I am typically very good with my google fu xD
I currently have build number BV_BV9500_V1.0_20181026. That seems to matter I believe.

I second the notion.
I have the pro model. I have considered rooting it, but honestly, the phone works well enough as-is without root (for me). However, I'd LOVE to be able to play with different ROMs on this device **AS LONG AS I CAN MAINTAIN THE TWO-WAY UHF TRANSCEIVER FUNCTIONALITY** (i.e. not some "needs-a-network-of-some-kind" "walkie talkie app" like Zello but the real UHF two-way), and I'd LOVE the ability to play with the files associated with the radio to really explore the hardware's capabilities.
Unfortunately, this phone seems more popular in [North]eastern Asia than anywhere else so I don't think we're likely to get much on this forum regarding it unless and until BV become a popular name in the western hemisphere.