Develop Bugs

[SOLVED] Rooting HDC Galaxy Note 2 Mega (MTK6577)

Hi guys!
Just recently I bought the "HDC Galaxy Note 2" off of fastcardtech. I got it a few days ago, am fairly pleased with it except for the slight miscalibrated touch screen. There are some apps on various markets aiming to fix this by re-applying new calibrations. The problem is that you'll have to be rooted in order to run them.
The phone comes with a built-in calibration setting, called "Als_ps calibration", which you can utizile to correct the sensor. Alas, it only corrects the phone's recognition of obstacles placed above it, so that you accidentaly wouldn't press any undesired button during a call.
Phone: http://www.fastcardtech.com/Galaxy-Note-2-Mega
Here's what I've done so far!
Enabled USB-debugging and installed USB-drivers. [MT65xx_USB_Driver.zip]
Tried the bin4ry root method, normal mode. [Root_with_Restore_by_Bin4ry_v18.zip]
This method:
http://forum.xda-developers.com/showthread.php?t=1886460
Everything works just fine until the phone reboots. Bin4ry is then unable to mount or copy the last files needed to apply root permission, see attached picture.
I have attached my specs in a screenshot, nevermind the quality, t'was done by another crap-camera! Sorry ;]
Any kind soul who can help me root this thing?
Edit:
Rooting this device has been made possible by GT35pro. See posts below.

same problem
KristN91 said:
Hi guys!
Just recently I bought the "HDC Galaxy Note 2" off of fastcardtech. I got it a few days ago, am fairly pleased with it except for the slight miscalibrated touch screen. There are some apps on various markets aiming to fix this by re-applying new calibrations. The problem is that you'll have to be rooted in order to run them.
The phone comes with a built-in calibration setting, called "Als_ps calibration", which you can utizile to correct the sensor. Alas, it only corrects the phone's recognition of obstacles placed above it, so that you accidentaly wouldn't press any undesired button during a call.
Phone: http://www.fastcardtech.com/Galaxy-Note-2-Mega
Here's what I've done so far!
Enabled USB-debugging and installed USB-drivers. [MT65xx_USB_Driver.zip]
Tried the bin4ry root method, normal mode. [Root_with_Restore_by_Bin4ry_v18.zip]
This method:
http://forum.xda-developers.com/showthread.php?t=1886460
Everything works just fine until the phone reboots. Bin4ry is then unable to mount or copy the last files needed to apply root permission, see attached picture.
I have attached my specs in a screenshot, nevermind the quality, t'was done by another crap-camera! Sorry ;]
Any kind soul who can help me root this thing?
Click to expand...
Click to collapse
omg i have the exact same problem, did you get a solution? PLEASE i need to root it so bad

CWM installed and rooted the HDC galaxy note 2 MAGE / MEGA
rebmoe said:
omg i have the exact same problem, did you get a solution? PLEASE i need to root it so bad
Click to expand...
Click to collapse
I just created the cwm recovery and root. The link is on my blog. The zip file is password protected so be sure to get it from my blog page.
http://gt35pro-mobile-gadgets.blogspot.sg/2013/02/cmw-recovery-english-and-root-for-hdc.html
After you have clockwork mod recovery, use it to flash the root access into the phone.
Have fun!

KristN91 said:
Hi guys!
Just recently I bought the "HDC Galaxy Note 2" off of fastcardtech. I got it a few days ago, am fairly pleased with it except for the slight miscalibrated touch screen. There are some apps on various markets aiming to fix this by re-applying new calibrations. The problem is that you'll have to be rooted in order to run them.
The phone comes with a built-in calibration setting, called "Als_ps calibration", which you can utizile to correct the sensor. Alas, it only corrects the phone's recognition of obstacles placed above it, so that you accidentaly wouldn't press any undesired button during a call.
Phone: http://www.fastcardtech.com/Galaxy-Note-2-Mega
Here's what I've done so far!
Enabled USB-debugging and installed USB-drivers. [MT65xx_USB_Driver.zip]
Tried the bin4ry root method, normal mode. [Root_with_Restore_by_Bin4ry_v18.zip]
This method:
http://forum.xda-developers.com/showthread.php?t=1886460
Everything works just fine until the phone reboots. Bin4ry is then unable to mount or copy the last files needed to apply root permission, see attached picture.
I have attached my specs in a screenshot, nevermind the quality, t'was done by another crap-camera! Sorry ;]
Any kind soul who can help me root this thing?
Click to expand...
Click to collapse
Kristen, where you able to re-calibrate after rooting; I just ordered this phone last week so I want to be prepared if need be.

londonflu said:
Kristen, where you able to re-calibrate after rooting; I just ordered this phone last week so I want to be prepared if need be.
Click to expand...
Click to collapse
The one I got did not have that screen calibration problem. Everything works good. Anyway, root is available now.

Superb!
Thank you for sorting this out!
-KristN91

Extra Guide
Follow the link provided by GT35pro in his first post.
To everyone attempting this flash;
!! First of all, copy the Superuser.zip to the root of your internal phone memory or external SD Card.!!
* Use a high-quality mini-USB cable (The one that comes with your phone should work just fine)
* Connect your MEGA to your pc, without the battery inserted.
(This device will connect and disconnect, when it's visible, be sure to grab it and follow the next step)
* Make sure that you have the right drivers for MTK65xx preloader "mtk65xx Vcom driver" and install them through the Device Manager.
* Insert your battery again, with the cable still connected, and install the second MTK65xx preloader.
* Disconnect phone from pc and remove the battery
* Start up Smart flash Tool and select the scatter file included in the package.
* Now, select and tick the checkbox for Recovery only. Smart Flash Tool will complain about the flash, due to it not containing all the appropriate files needed for a "secure boot". Nevermind that pop-up and proceed with downloading.
* Start Download
* Insert the battery and connect your phone to your pc, with that, the flashing should start.
* Boot Phone into recovery mode (pwr button and vol - or vol +) and install superuser from ZIP-file.
* After reboot you should be rooted.
///////////////
Fun Fact!
I actually managed to install a pre-rooted HDC S7100 rom on my MEGA.
The port isn't 100% accurate
-Invalid IMEI, this was fixed by Talkingmobile's guide; " how to write imei number for MTK 65XX " -Just google it!
-Auto-rotation is unavailable, no fix yet.
-Als_pl calibration is unavailable (resulting in active screen during call)
Besides that, the rom is arguably better than the MEGA's original N7100 rom, in terms of visual presentation.
Smooth transitions, vivid and vibrant colors would be a good example of aspects that would come out as improved over the original rom.
Interested in the S7100 rom? Just PM me and I'll provide the link.
Cheers!

S_ft_need_download_all_fail (4050)
I'm trying for several days, but always get this error in the flash tool: S_FT_NEED_DOWNLOAD_ALL_FAIL (4050)
Tried on Windows 7 x64, Windows 7 x32 and Windows XP SP3 (x32). Only on the Windows XP computer I was able to make a backup with Flash Tool using the Read Back option.
When I try to flash the red bar goes to 100% then the error message shows...
Does anyone get this error aswell, and did someone manage to solve this?
Please help, I'm in desperate need for root because I need touch screen calibration.
Thnx!!

YES! SUCCES!! I managed to root my HDC Mage :laugh: Did use another method though, check http://forum.xda-developers.com/showthread.php?t=2160490 if you are interested.
Anyway, now back to calibrating the touchscreen. What tools are good do fix touchscreen issues? I already tried http://forum.xda-developers.com/showthread.php?t=934500, but I still am not satisfied.
Thnx :good:

Just curious, if anyone that owns an HDC, is actually located in the USA?

londonflu said:
Just curious, if anyone that owns an HDC, is actually located in the USA?
Click to expand...
Click to collapse
Nope, the Netherlands. Why do you ask?
Sent from my GT-I9000 using xda app-developers app

jg77 said:
Nope, the Netherlands. Why do you ask?
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Because I tried to order 5 different phones from China including Fastcardtech; they couldn't ship for some reason; even got an empty box from ZOPO mobile. I ended up buying the BLU here in the US, I'm kind of glad it happened, since now I have an N'vidia Tegra 4 CPU, that runs circles around the dual-core phones.
I did order one more phone on ebay from China, been waiting for 2 weeks now. MAKES ME WONDER IF THEY EVEN ACTUALLY SHIP TO THE US AT ALL?
Thank to Paypal I was able to get refunded everytime.

KristN91 said:
Follow the link provided by GT35pro in his first post.
To everyone attempting this flash;
!! First of all, copy the Superuser.zip to the root of your internal phone memory or external SD Card.!!
* Use a high-quality mini-USB cable (The one that comes with your phone should work just fine)
* Connect your MEGA to your pc, without the battery inserted.
(This device will connect and disconnect, when it's visible, be sure to grab it and follow the next step)
* Make sure that you have the right drivers for MTK65xx preloader "mtk65xx Vcom driver" and install them through the Device Manager.
* Insert your battery again, with the cable still connected, and install the second MTK65xx preloader.
* Disconnect phone from pc and remove the battery
* Start up Smart flash Tool and select the scatter file included in the package.
* Now, select and tick the checkbox for Recovery only. Smart Flash Tool will complain about the flash, due to it not containing all the appropriate files needed for a "secure boot". Nevermind that pop-up and proceed with downloading.
* Start Download
* Insert the battery and connect your phone to your pc, with that, the flashing should start.
* Boot Phone into recovery mode (pwr button and vol - or vol +) and install superuser from ZIP-file.
* After reboot you should be rooted.
///////////////
Fun Fact!
I actually managed to install a pre-rooted HDC S7100 rom on my MEGA.
The port isn't 100% accurate
-Invalid IMEI, this was fixed by Talkingmobile's guide; " how to write imei number for MTK 65XX " -Just google it!
-Auto-rotation is unavailable, no fix yet.
-Als_pl calibration is unavailable (resulting in active screen during call)
Besides that, the rom is arguably better than the MEGA's original N7100 rom, in terms of visual presentation.
Smooth transitions, vivid and vibrant colors would be a good example of aspects that would come out as improved over the original rom.
Interested in the S7100 rom? Just PM me and I'll provide the link.
Cheers!
Click to expand...
Click to collapse
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls

thank you

I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls

farazafs said:
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
Click to expand...
Click to collapse
Did you install all necessary drivers?
Sent from my GT-I9000 using xda app-developers app
---------- Post added at 08:21 AM ---------- Previous post was at 08:17 AM ----------
farazafs said:
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
Click to expand...
Click to collapse
Did you install all necessary drivers? How does sp flash tool respond when you download the recovery?
Sent from my GT-I9000 using xda app-developers app

jg77 said:
Did you install all necessary drivers?
Sent from my GT-I9000 using xda app-developers app
---------- Post added at 08:21 AM ---------- Previous post was at 08:17 AM ----------
Did you install all necessary drivers? How does sp flash tool respond when you download the recovery?
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I can Install all necessary drivers, when I Power OFF phone and connect it to my PC, in device manager it can show MT65xx Preloader (Com 9) connected n within 3 sec it can be disconnected.... in SP Flash Tool i can select recovery then press download button... then again i can connect phone, it's give me some 80xx error. it's mean that device not connect.

farazafs said:
I can Install all necessary drivers, when I Power OFF phone and connect it to my PC, in device manager it can show MT65xx Preloader (Com 9) connected n within 3 sec it can be disconnected.... in SP Flash Tool i can select recovery then press download button... then again i can connect phone, it's give me some 80xx error. it's mean that device not connect.
Click to expand...
Click to collapse
An 80Xx error does not always mean device not connected. It can also mean there is something not right in the scatterfile (error 8038). You should take a look at the sp flash tool logfiles. You can post them here so I can have a look.

jg77 said:
An 80Xx error does not always mean device not connected. It can also mean there is something not right in the scatterfile (error 8038). You should take a look at the sp flash tool logfiles. You can post them here so I can have a look.
Click to expand...
Click to collapse
Attached snapshot given below... always when I tried to flash Recovery from SP Flash Tool it's only give me this error.

farazafs said:
Attached snapshot given below... always when I tried to flash Recovery from SP Flash Tool it's only give me this error.
Click to expand...
Click to collapse
There is something wrong in the layout of the scatterfile. Can you post the logiles of sp flash tool? Just zip them all together.
I have had the exactly the same error with my HDC Mage. I just had to rename a small section of the scatterfile and then it was all good.

Storex Ezee'TAB901 root JB 4.1.1

hi,
After spending many time trying to root my storex tab 901 I bought in france (Already installed on 4.1.1 with google play), Iwas finnaly able to root it using adb and command line.
to do so:
- Download attached file
- Download from google SDK usb_adb_driver
- Go to your device parameters-> USB -> enable debbuging mode
- create a c:\root folder on your windows XP computer then Extract the zip file attached into it.
- Plugin your device to the computer, when prompted for driver, use google sdk USB_ADB_Driver
- When done, open a windows terminal command line
- type: c:
- type: cd \
- type: cd root
- type: cd rootkit
- type: go.cmd
If everything goes well, your tablet should reboot. you can try installing the free app from google store called "Root checker" to confirm your device is properly rooted.
Also, if you lost the original rom and live suite, here is the link to download the latest build from storex web site:
(I will post the link later when I find it)

JB 4.2.2
CAUTION: USE THIS ROM AS YOUR OWN RISK.......Be sure you have the official rom in case it is not working for you. It appears that even though you have the same tablet Reference, depending on when you buy it, hardware might be a bit different and most likely you will take the risk of having a unusable Touch screen or wifi...
I found out you can fully use your Ezee Tab 901 4.2.2
you can install rom from Manta MID 13.
You will be able to install the rom using Livesuite.
Gain:
- Android 4.2.2
- Root Access out of the box
- Play store installed.
Everything will be working
For the link type in google:
MID13 Android 4.2.2 Jelly Bean - Manta Multimedia Info
select google link called: manta.info.pl
select the link catshare or 4shared.
Start live suite 1.7, select the download img file, do a format when prompted. You done.
When the tablet restart, go to the parameter icon, and change language to French or english
Procedure on the Ezee tab 901 with livesuit:
- completly turn off the tablet, unplug cable
- start livesuite and select the downloaded image file
- keep the VOL- button pressed and plug the usb cable
- without releasing the VOL- button press the Power button 6 times.
- You should hear windows sound saying a USB device has been plugged
- if windows request it, install the driver from Livesuitefolder\usbdriver
- Livesuite should automatically start the flashing process.
- when prompted, "Format device" press YEs.
- When it s 100% you tablet should reboot.
Done.
Note: I did not invent anything, thanks to the good work of MANTA team members. I just found out this rom works on my tablet out of the box.

Hi,
Thanks for sharing these tips. I'm gonna try to update to 4.2.2, hoping this is going to fix some problems with this tablet.
I've been looking a lot for information about how to update ezee tab 901, so you did definitely a great work !
edit : iflash went well, but touch screen is not responding anymore. Any idea of how to solve it ?
Thanks.

samus64 said:
Hi,
Thanks for sharing these tips. I'm gonna try to update to 4.2.2, hoping this is going to fix some problems with this tablet.
I've been looking a lot for information about how to update ezee tab 901, so you did definitely a great work !
edit : iflash went well, but touch screen is not responding anymore. Any idea of how to solve it ?
Thanks.
Click to expand...
Click to collapse
Hi,
did you try going into recovery mode and factory reset? (shutdown tabel completely and keep press on volume+key then press power button)
in the menu, using vol+/- scroll down to wipe factory reset and validate by pressing the power key.
Let me know how it goes.
btw, are you sure your tablet is a Ezee tab 901 and not 971?
Cheers

Hi,
Yes I've got 901 and not 971 (written on the back of the device). I tried factory reset , but still the same problem. However, I flashed again with the original rom, and then touch screen went functional again but the wifi switch is kinda "broken" : it's impossible to turn on wifi from the Settings menu.
I returned the tablet where I bought it, seems there's a sort of material problem with it :/

samus64 said:
Hi,
Yes I've got 901 and not 971 (written on the back of the device). I tried factory reset , but still the same problem. However, I flashed again with the original rom, and then touch screen went functional again but the wifi switch is kinda "broken" : it's impossible to turn on wifi from the Settings menu.
I returned the tablet where I bought it, seems there's a sort of material problem with it :/
Click to expand...
Click to collapse
Im sorry to hear that, i dont think something is broken, i had the same issue with a memup tablet, even though it was a same reference, some model had different hardware, sonlike you after testing multiple rom i had only touch s creen and no wifi ( wifi switch went back to off when i tried to turn it on) or on other rom, i had working wifi but no touch screen.
I hope they will replace your device...
Cheers

pierrottls31 said:
Im sorry to hear that, i dont think something is broken, i had the same issue with a memup tablet, even though it was a same reference, some model had different hardware, sonlike you after testing multiple rom i had only touch s creen and no wifi ( wifi switch went back to off when i tried to turn it on) or on other rom, i had working wifi but no touch screen.
I hope they will replace your device...
Cheers
Click to expand...
Click to collapse
Yep the wifi switch is exactly what i've got on this storex. Thanks for your help anyway. Ho and by the way, I properly rooted it with you first tuto
Cheers.

Fast custom ROM 4.2.2 by TOxico for Ezee tab 901
Guys,
I manage to find a very fast and usable rom for our tablet: (THanks to Toxico.) this rom will change your life.
All information and download are in the thread here:
http://forum.xda-developers.com/show...php?p=42274265
It should basically work on any A13 device with livesuit (tested on my Ezee tab 901 and on my 704CET mem up)
This rom comes with no TS driver, but there is all explanation and download to install the needed driver.
note: you might loose the camera though. I encourage you to read the full thread before going further and flash your tablet.
If you want to know the driver used on your tablet, run a adb shell and type lsmod (You will have a list of loaded/used driver.)
Dont be scared, everything is written in the toxico's thread
My only advice, if you dont know how to use adb, do not try it, this is not that easy.
I hope this will help.
Best regards.
As usual do it at your own risk and even more: make sure you have the original rom... just in case

Tutorial for 971.
Hi there,
Does anyone know a tutorial like this one but for the 971??
My brother-in-law wasn't using is so I'm thinking in tweaking it to see how it gets.

MaedaKeiji said:
Hi there,
Does anyone know a tutorial like this one but for the 971??
My brother-in-law wasn't using is so I'm thinking in tweaking it to see how it gets.
Click to expand...
Click to collapse
Hi, sorry i cant help you, it looks like the 971 is using a10 cpu, sôit can be different.
If you know what you are doing, u can try to backup your original firmware and test the solution i have provided from toxico in py post above. But there is no warranty it s going to work.
Any case, donnot forget google is your friend
Good luck

Unfornetly it seems google doens't like this tablet...
I'll see what I can do with some backups and all.
Thanks anyway!

[Guide] How to fix a hard bricked Galaxy Nexus

I am writing this because I couldn't seem to find a guide to solve my issue of my Galaxy Nexus being completely bricked. It was literally dead, or so I thought. The first part of this guide will tell you how to recover from the following situation:
Before we begin, here are the names of the programs and files used:
Odin3
Android ADK
CF-Root-GGN_YAKJU_ICL53F-v5.1
Stock Galaxy Nexus ROM
OMAP
Situation 1:
The first situation is where your screen has gone completely black. You can't boot into anything and nothing is displayed on the screen. Your computer no longer recognises the device. It is literally a brick. If you are in this situation, please follow the solution 1 and 2 else skip to situation 2.
Solution to situation 1:
I was googling everywhere for a solution to this and it appeared that it was not a common problem and those who did face the problem simply returned their phone on warranty. It is now an old phone but I still like it (will be upgrading to nexus 5 in the next few weeks). I didn't want to waste such a good phone and just have it sit there so I researched.
My solution to this problem is omap. I would post a link but unfortunately I do not have the permissions (for the download link I will be uploading later).
Please note that I do not take any credit for any program used in this guide and I am simply putting together several other guides so that future users who have this problem can access them all in one place.
Here is the step by step guide:
1) Open OMAPFlash. Navigate to usb_drv_windows. *Right click on omap_winusb.inf and click install*.
2) Navigate to usb_drv_android. *Right click on android_winusb.inf and click install*.
*Note: On Windows 8 (8.1), you will have to allow all certificates to be installed.
3) Double click on the omap4460_tuna_hs_pro.bat and run it accordingly. You will have to disconnect the device and remove battery. Connect the device and then count to 5. Re-insert the battery.
4)Omap will now start doing its thing and you will be given situation 2.
Situation 2:
This situation is where you have a phone connected to a yellow exclamation mark which is connected to a computer. Mind my ASCII Art, but here is what it looks like: [] - - /_\ - - [ ]. You can't do anything with this either but ODIN (google it) will pick it up. This is a good thing. You won't be able to boot into recovery mode or download mode which makes it hard to flash a ROM to it or fastboot it. You will need CF-Root-GGN_YAKJU_ICL53F-v5.1 (Google it). Here is the step by step guide:
Solution To Situation 2
1) Open ODIN3. Select the CF-Root-GGN_YAKJU_ICL53F-v5.1 as the PDA file. If your phone is not being recognised (should say added! in the log), simply disconnect device, remove battery, reconnect device and then place battery back in and hold down the power + vol up + vol down buttons.
2) Press start. The log will start filling up and it should say DONE! You now have bootloader.
3) Now you will need to find the stock ROM for the galaxy nexus (google it). Now you will need to extract that the contents into your adb file (from the android sdk installation which hopefully you have,
4) Put your device into bootloader mode. Run the fastboot flash-all batch file that should be included with the custom ROM.
5) Your phone will now start doing stuff and constantly rebooting in and out of bootloader mode.
6) You should now have the stock ROM installed.
Again, I am sorry that I cannot post links but I do not have permissions due to lack of posts. I know this is an old phone but this guide may still be useful to someone. Also, feel free to ask any questions or point out any mistakes I have made.

no need that android adk. setup correctly adb & fastboot just enough. i think this type of threads already here..
* yeah.. but no sticky guide. maybe good to go. better make ' how to prevent gnex from bricks'
omap flash.exe ~
http://forum.xda-developers.com/galaxy-nexus/general/bricked-gnex-brought-to-life-t1760787
odin ~
http://forum.xda-developers.com/galaxy-nexus/general/guide-restore-to-stock-unbrick-galaxy-t2065470

I probably already know the answer to this but I want to make sure: can this procedure be applied to the Verizon Toro?
Update: Phone isn't responding to this fix... It was a long shot maybe in a week or two it'll turn on...
I'll write up a tutorial for us Toro kids... Thank you guys!
Sent from my VS980 4G using Tapatalk

who one have storage issue here is solution

Now dear friends I will give the solution of problems that occur after unbrick leeco pro3 who has internal storage problem like this
infinite thanks to my Chinese friend Hua found this solution by itself and thanks tora33 from leeco.re and mbtt from forum.one-teams(i use picture from him)
I'm not in charge of the operation to be performed, is designed to assist you in these processes
Charge your mobile phone
1) download : qfil, (that have correct partition) and put in C:/
https://yadi.sk/d/piVn4bpf3MqcHC
2) download : FlashOne1,9 , put in a folder and extract it ,
https://yadi.sk/d/PmVChpqZ3Mj2hz
3) download :fastboot rom
https://yadi.sk/d/uzdwFhie3MqcJs
4)download qq driver
https://yadi.sk/d/U4SIDH3B3Mixsh
run "FlashOne1,9"
How to qfil Flash
When select qfil flash type, press power key, volume up and volume down key at the same time, then the phone enter into qfil mode, connect USB cable with PC, wait for PC install driver automatically, then press ‘Refresh’ button on the tool, serial port will display on UI, select the port you want to flash, and make sure there is no other qcom device connected.
Select corresponding flash zip file, the path of zip file should not contain Chinese and special character. (Under qfil mode, the tool can’t get hardware information, you should check if the software and hardware is matching yourself.)
Press ‘Flash’ button, then start to unzip flash zip file to current folder, but if there is already a corresponding unzip file existing, ‘Decompression folder is exist, re-decompress or not?’ dialog will pop up, if select yes, will re-decompress, else not. After unzip finished, start to flash the phone automatically, and the progress bar display flashing progress(for me the bar not move stuck %1 i did wait 15minute then unplug phone and push power button long time, and at the same time, the flashing log will also be shown on UI.
After flash complete or error happened, a notification dialog will pop up.
after phone start go boot logo and wait by the way open fastboot rom and push le_zl1_fastboot
everyting go fine u get 24gb for 32gb phone and 54gb for 64gb phone
good luck i hope help you

Thanks
Work on x720 ...

Will this work on Custom OMNI rom please?

krugerbud said:
Will this work on Custom OMNI rom please?
Click to expand...
Click to collapse
Yes it should work
All you have to do is follow the steps.
Be careful, all your data will be erased!

lazye53 said:
Yes it should work
All you have to do is follow the steps.
Be careful, all your data will be erased!
Click to expand...
Click to collapse
But I already have 24GB out of 32GB , but still have storage issues when using the phone. APps and services randomly crash unable to fully use phone.
I guess I do not need this then, must be some other issue?

krugerbud said:
But I already have 24GB out of 32GB , but still have storage issues when using the phone. APps and services randomly crash unable to fully use phone.
I guess I do not need this then, must be some other issue?
Click to expand...
Click to collapse
This issue is only for those who are missing storage.
If you have another storage problem, look for another solution.

Storage Problem LeEco Le Pro 3 X720 - 4 GB/32 GB
I followed instructions but it didn't work.
What can I do in order to increase storage to 24 GB?

qfil mode error
Is it for restoring the original storge capacity for Le Pro 3? The reason why I'm asking this is becuase I am currently stuck on qufil rom because it keeps making error everytime I tried to go to the launcher. Will it work on my circumstance?

How to guide (9.0 Android) LVM Chinese Unification Storage Method

In this guide, I will show how to how to change from LVM to Chinese unification storage method. Windows OS Only.
This guide is specifically for Oppo Find 7(A/S).
The idea of changing to chinese unification storage method is to have access to 8.1 Android operating system and future Android OS builds.
Please follow these following steps in order be able to run 8.1 Android on your OPPO Find 7.
1) Back up only your internal storage because after you flash the following tools, the internal storage will be wiped completely.
2) Download this file (for OPPO Find 7s) and this file (for OPPO Find 7a) then run the following steps:
Extract the files, and locate the QcomMtk_Driver_Setup.exe (*install this driver*) and reboot your computer system.
After rebooting, take off the battery off the Oppo find 7 and press the volume up button and connect to the PC using a micro USB cable. Go to the device manager, open the ports tab and there should be something like qualcomm etc. If there is no warning sign then you are fine and you should proceed along the steps. If there is a warning sign, just right click on the driver and update by letting windows finding the appropriate drivers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then go back to the folder where you extract the zip file and locate (X9077_Android5.0_32G_20150520.exe) or X9007 respectively and run as administrator. rights only.
Agree with the licence. As shown in the image.
Now, again, make sure your battery is removed, hold volume up button and connect to the pc.
Click the first top left button as indicated in the image below.
Now, the software should do the rest so please be patient and wait until the green line has finished and the timeclock down on the bottom right as come to a halt.
After the green line has finished, please remove your device and plug back your battery. Let the device fully boot up before moving on the following steps.
After you get to the setup screen. Press and hold the power off button and shutdown fully before going back to the fast boot mode by pressing volume up and power button at the same time, the battery needs to be installed this time.
-
Now, flash the twrp modded image using fast boot flash and download the two files fastboot and twrp-modded img :
1) Have your phone in bootloader mode. (Turn off your phone, press volume up button and power button together and connect usb).
2) Navigate to the folder and click on the top left of the folder and copy that. e.g C:\Users\samgi\Desktop\platform-tools
3) Open cmd and type in: cd C:\Users\samgi\Desktop\platform-tools
4) In cmd type in: fastboot flash recovery image-modded.img
4) Remove USB and press power button and volume down button simultaneously.
-After you have flashed the recovery, boot into recovery and store the ROM, GAPPS and cm13 unified patch in the external sd card using your USB.
Download your favourite 9.0 ROM:
crDroid for example: https://androidfilehost.com/?w=files&flid=262369
Install GAPPS (only pico):
http://opengapps.org/
After you have downloaded all the files rom gapps cm13 patch etc. Make sure to flash each of the zip files one by one:
1) Flash ROM
2)Flash Pico Gapps
3)Flash CM13 Patch here
So basically, just head over to https://download.lineageos.org/find7 and download the latest Lineage OS 16 ROM. Then download the MindTheGapps (since pico OpenGapps can't work) from https://androidfilehost.com/?w=files&flid=170282 make sure to get 9.0.0arm.
Reboot to recovery, wipe the dalvik, system and cache. Then proceed with installing the the LOS 16 ROM. After that, you can flash the CM 13 patch and the gapps (MindTheGapps). It's ok to do gapps first before the CM 13 patch. I noticed that it makes no difference. Works the same every time.
Well, that's about it, reboot and enjoy. OTA should work after this. I think.
Good luck.
Then, simply clear cache and boot to your 9.0 OS. P.S don't forget to restore your data that you deleted in step one.
Optional: If you want to go back to Color OS or you have hard-bricked your OPPO Find 7(A/S) this tool will help you get back to stock firmware.
STOCK FIRMWARE (LVM)
Here are the instructions to unbrick your phone:
This is going to be a step by step guide on how to unbrick your OPPO FIND 7 (A/S)
Before attempting this guide, Windows is needed to be in "Test Mode".
To do this:
1) Open CMD with admin rights, and type "bcdedit /set testsigning on" without the colons.
2) Restart your computer.
End result:
This will check if this guide is applicable.
Note: Make sure your device has at least 70% battery. Charge it for an hour or so if you are not sure about the amount of battery left.
Note 2: I'll assume you are an admin of the computer you are using.
1) Disconnect your device from your charger/computer, etc.
2) Take out the battery and wait for 5 seconds.
3) Put the battery back in, hold the Power+Volume Up buttons and plug it into the computer.
4) Release your hands, and go to Device Manager. (How to go to device manager below)
1. Click the start menu
2. Right click Computer (Right hand side)
3. Click Properties
4. On the left hand side, click on Device Manager
5) Under Ports, you'll see either QHSUSB_BULK or Qualcomm *blah blah blah* 9006/9008
If you don't see any of the three, you're doing it wrong (Probably).
If you're not seeing it, try connecting your device without the battery.
Next, we uninstall the drivers. Simple enough.
WARNING: This part is only for people seeing Qualcomm 9006/9008 in Device Manager.
1) Uninstall the driver. (Right click your device, then click Uninstall. If prompted, delete driver software too)
2) Unplug your device.
3) Take out the battery and wait for 5 seconds.
4) Put the battery back in, hold the Power+Volume Up buttons and plug it into the computer.
5) Release your hands, and go to Device Manager.
You should see QHSUSB_BULK, if not, you might be doing it wrong.
Now we install the proper drivers.
NOTE: You should be seeing QHSUSB_BULK in your Device Manager, if not you're doing it wrong.
1) Download the Find 5 Drivers and unzip the file anywhere.
2) Right click on your device showing QHSUSB_BULK and click on Update Driver Software.
3) Click on "Browse my computer for driver software", and select the folder in which you extracted the drivers to.
4) It will install automagically. If prompted, click on Install the driver anyway.
After installing, your device should say Qualcomm *blah blah blah* 9006/9008.
The moment all of you have been waiting for. Unbrick!
NOTE: Your device should be connected at all times.
1) Download the tool that will save you below.
2) Extract the contents from the zip file.
3) Open the .exe file with admin rights.
4) There should be a line that is visibly different from others.
5) If there is, click start and wait till that line turns green. (It takes a few minutes. Generally nothing should go wrong at this stage.) If there isn't, you're doing it wrong.
6) After the line turns green, unplug your device and hold the power button until you see the Oppo logo.
7) If all goes well, you should be booted to ColourOS v1.2.5i.
If everything went through smoothly, you should be unbricked and ready to brick your device again.
Special thanks to:
@tashimotor https://forum.xda-developers.com/showpost.php?p=64149659&postcount=3
@Manas1796 thread: https://forum.xda-developers.com/find-7/general/7-dead-development-oppo-7-terminated-t3764649
@crdroid
@ akmlfhm https://forum.xda-developers.com/find-7/help/how-to-debrick-unbricka-oppo-7-7a-t3717802
@play8oy

A very helpful thread, my friend! Thanks for keeping us up to date that this is possible!

Glad to see a detailed method of Unification! Can't wait till you post one for the Find 7a

5ufy9n said:
Glad to see a detailed method of Unification! Can't wait till you post one for the Find 7a
Click to expand...
Click to collapse
Sure, I will let you know once I upload the file to Google Drive. :fingers-crossed:

Nice... looking this step... because last i try switch lvm to chns unified.. got bricked
So my question is ....
1. Support for find7 with this model X9076? Because the file download is X9077
2. What windows u running when u doing this?
3. Is possible support for windows 10.1 64 bit?
4. any suggest what custom rom ?
Cant wait u reply.....
Tq....

itmdn said:
Nice... looking this step... because last i try switch lvm to chns unified.. got bricked
So my question is ....
1. Support for find7 with this model X9076? Because the file download is X9077
2. What windows u running when u doing this?
3. Is possible support for windows 10.1 64 bit?
4. any suggest what custom rom ?
Cant wait u reply.....
Tq....
Click to expand...
Click to collapse
Sorry for the late reply,
Don't worry, I will upload the tool also that I managed to download when oppo forums was running and luckily saved that on my hard drive :') so if you do brick your phone, the software will put you back to default X9076 color OS software mode so you're safe.
1. This guide is for Oppo Find 7s. The 8.1 android OS does not recognise X9076 (LVM) and shows "encryption unsuccessful" whenever you boot into the OS. However, when your phone shows X9077 (Chinese unified method) the 8.1 recognises and lets you boot successfully. I'm not quite sure why OPPO had to make this sooooo confusing. Lol.
2. I am running the latest Windows 10 Anniversary Update.
3. I'm not sure what you're asking ? It does not matter 32-bit or 64 bit
4. I'm literally running CrDroid and its amazing, the latest update just got out online check it out.
Let me know if you need further help.

brownboy1289 said:
Sorry for the late reply,
Don't worry, I will upload the tool also that I managed to download when oppo forums was running and luckily saved that on my hard drive :') so if you do brick your phone, the software will put you back to default X9076 color OS software mode so you're safe.
sorry, is this your mean u will upload the X9076_Android5.0_32G_20150520 version?
or you are saying that files at OP is working for X9076 and X9077 ?
sorry .... cant wait anymore ... really need switch from lvm to chns unified and taste the Android 8.1
tq
Click to expand...
Click to collapse

i success do it, but now i got new problem, at my storage sdcard0 corrupted, tried format still no luck.
any help or suggestion ?
tq
---------- Post added at 08:33 AM ---------- Previous post was at 07:56 AM ----------
itmdn said:
i success do it, but now i got new problem, at my storage sdcard0 corrupted, tried format still no luck.
any help or suggestion ?
tq
Click to expand...
Click to collapse
already solved.
first try ... got problem sdcard0 corrupt.
so i do this step, boot to twrp, flash removesetuplvm.zip - done
repeat again the guide at OP and now sdcard0 corrupted problem is gone.
now ... time for me taste android 8.1 and restore all my data
tq for this guide

itmdn said:
i success do it, but now i got new problem, at my storage sdcard0 corrupted, tried format still no luck.
any help or suggestion ?
tq
---------- Post added at 08:33 AM ---------- Previous post was at 07:56 AM ----------
already solved.
first try ... got problem sdcard0 corrupt.
so i do this step, boot to twrp, flash removesetuplvm.zip - done
repeat again the guide at OP and now sdcard0 corrupted problem is gone.
now ... time for me taste android 8.1 and restore all my data
tq for this guide
Click to expand...
Click to collapse
I'm glad that it is working for you. :fingers-crossed::good:
Let me know if you have any problems

Sorry for those waiting on the OPPO FIND 7a files, I have really slow upload speed.

5ufy9n said:
Glad to see a detailed method of Unification! Can't wait till you post one for the Find 7a
Click to expand...
Click to collapse
Up and running: https://drive.google.com/file/d/1h74LKVucM4RoBJ-Bsgkmzdavzn_MbtPY/view?usp=sharing

Can some post thread in this xda where is crdroid oreo discussion? Because i have strange problem with crdroid...
Tq

itmdn said:
Can some post thread in this xda where is crdroid oreo discussion? Because i have strange problem with crdroid...
Tq
Click to expand...
Click to collapse
What's the problem? I think they had a 7.1 forum but I'm not sure if it's closed

If 7.1 i think no connection on this 8.1 version, right? But if u dont mind i wanna ask if u have this issues.
My problem is weird ....
1. Press long at recent button will appear some apps that we have opened.. at the top have lock button, right? I already press that button become lock. But that make it permanent... in no time will be unlock.
2. Last night when i sleep i leave my phone idle with battery 100%, at morning i woke up and see my phone low batt with 13%. Weird draining battery so fast. Nothing running only some email and chat that i haven' t read. Maybe the notification light?
Tq.

itmdn said:
If 7.1 i think no connection on this 8.1 version, right? But if u dont mind i wanna ask if u have this issues.
My problem is weird ....
1. Press long at recent button will appear some apps that we have opened.. at the top have lock button, right? I already press that button become lock. But that make it permanent... in no time will be unlock.
2. Last night when i sleep i leave my phone idle with battery 100%, at morning i woke up and see my phone low batt with 13%. Weird draining battery so fast. Nothing running only some email and chat that i haven' t read. Maybe the notification light?
Tq.
Click to expand...
Click to collapse
The first problem I'm not sure lol ?
The second problem is maybe most likely of background apps turn off any background apps that might be running i.e apps that run constantly Facebook Instagram others. One recommendation to turn off Wifi and mobile data so there is no data incoming/outgoing when you go bed.

brownboy1289 said:
The first problem I'm not sure lol ?
The second problem is maybe most likely of background apps turn off any background apps that might be running i.e apps that run constantly Facebook Instagram others. One recommendation to turn off Wifi and mobile data so there is no data incoming/outgoing when you go bed.
Click to expand...
Click to collapse
Maybe my english bad hehehehhe
I already attach the pic for first problem....
I cant make it stick locked ... in some how it will unlock itself... weird...
Also i cant play Mobile Legends anymore always force-close lol
Tq

That,s weird battery usage. When I leave a 100% battery at night, next morning ( about 8 hours) I have about 90+% left, and I leave WiFi and mobile data on all night. Though I use Servicely and Project Skynet Raising.

itmdn said:
Maybe my english bad hehehehhe
I already attach the pic for first problem....
I cant make it stick locked ... in some how it will unlock itself... weird...
Also i cant play Mobile Legends anymore always force-close lol
Tq
Click to expand...
Click to collapse
This is a strange problem I'm not quite sure how to help... sorry

Omg so frustrating ..... battery really draining... lol. In 1 day i can charge 3x .... any suggest official custom rom with android 8.1 for find 7s?
Tq

itmdn said:
Omg so frustrating ..... battery really draining... lol. In 1 day i can charge 3x .... any suggest official custom rom with android 8.1 for find 7s?
Tq
Click to expand...
Click to collapse
Best advice would be to reflash the ROM with pico gapps or at last change to another 8.1 ROM i.e lineage rom or omni 8.0