Database Info

P506 LG THRIVE Complete Emergency/Unbrick/revert to stock v11h/root & cwm

LG THRIVE EMERGENCY MODE/BRICK FIX/REVERT TO STOCK v11H Firmware/How to root after unbrick & revert/install CWM
***I want to make a few things completely clear:
1. THIS IS FOR THE LG THRIVE (P506GO) ONLY.
2. I AM NOT RESPONSIBLE FOR FURTHER BRICKING OF YOUR DEVICE (however I have not had any issues and I have done this many times)
3. I do not know where I found this procedure originally, however I have seen it posted around the web a few times. So I cannot actually give credit to anyone because I do not know who i got it from or who came up with it originally, So I apologize.
4. I did not make any of the files.
5. I did this because I am sure there are other people that have spent hours, upon hours, upon hours trying to figure this out, and my wife drives me nuts and I figure other spouces have been driven nuts, so here you go. If you like it, use it, if you dont, then dont.
This procedure will work for ANY LG THRIVE THAT STILL COMES UP IN EMERGENCY MODE, If your phone shows up as a QCUSB_DLOAD or something to that effect in device manager this will not work, This will also work for anyone wanting to fully revert back to stock 2.2.2 v11H. This is also safe to the effect it will not mess up your NV partition (there is another unbrick guide that you run the risk of screwing up your NV and then you wont have cell service after the unbrick).
That being said on with how to do it!
Download these files first
CUSTOM KDZ v11h
LGUnitedMobileDriver_S4981MAN38AP22_ML_WHQL_Ver_3.8.1.exe
LG_KDZ_FW-Update_OfflineFix
Unbrick Solution
1. If your phone is plugged in to the comp, unplug it. Remove the back off the phone and remove battery, do not worry it will be fine. Now set it to the side, we don't need it just yet.
2. Install the LG UNITED MOBILE DRIVER from the file you downloaded.
3. WE ARE NOT INSTALLING ANYTHING ON THIS NEXT STEP THIS IS MERELY TO HELP US ELIMINATE A PROBLEM. If your phone automatically boots into emergency mode then go ahead and plug it in (for those stuck in bootloop or just wanting to revert press and hold back + Volume up and then plug in the usb) and let the drivers install. Once that is done go to Device Manager (Start->run-> type devmgmt.msc and press enter.) expand the modems section and disable (DO NOT UNINSTALL) the LGE USB MODEM (See pic below). It will ask you to restart your computer, DONT.
{
"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"
}
4. Disconnect the phone from the computer.
5. Extract the contents of the LG_KDZ_FW-Update_OfflineFix to it's own folder.
6. open the folder to which you extracted those files then open the KDZ_FW_UPD_EN folder
7. XP Users: just double click the KDZ_FW_UPD.exe/Vista,7,8 users right click and run as administrator.
8. Set Type to 3GQCT and PhoneMode to Emergency (others tell you to set it to diag, dont.)
9. Click the little folder with the curved arrow above it to the right of the KDZ file and select the custom_lg_thrive.kdz file you downloaded earlier. Leave the program open.
10 EVERYONE MUST DO THIS STEP EXACTLY WHETHER YOU BOOT AUTOMATICALY INTO EMERGENCY OR NOT! Plug your battery back in, then press and hold the back button + Volume Up + Power. Release ONLY POWER once the thrive starts and then release back and volume up once your in emergency.
11. NOW PLUG YOUR PHONE BACK INTO THE USB!
12. Hit Launch Software update. If it says phone isnt found, first verify the LGE MODEM driver in device manager is still disabled, if it is disconnect phone and then plug it back in without rebooting and hit start upgrade again, it should work this time. IF THE WINDOW FREEZES DO NOT PANIC IF IT GIVES YOU A MESSAGE SAYING ITS FROZEN CLICK WAIT on VISTA/7/8 (on xp it should just revert back, once it does youll see in the dialog box it is flashing let it continue until it says it is complete (Your phone will reboot and you will be at the battery charging screen)
13. WE ARE NOT DONE JUST YET! Now we have to do a Factory(Hard) Reset SO with the device off press and hold the home + volume up + power. release all three once the device boots, let it do its thing. when the device reboots, it will seem to take forever. but it will finally get to the Android setup screen.
Walaa You are back to v11H stock firmware.
How to root after unbrick/revert to stock
1. After you setup your thrive go to settings->Applications and check unknown sources
2. in the same menu click on development and check all three settings in there.
3. Make it easy on yourself and just use the phone browser to come to this thread even easier here is a bit.ly link: http://bit.ly/14EbsSF
4. from your phone browser download the gingerbreak attachment.
5. Install it after its downloaded (if given the unknown sources dialog box refer to step 1
6. Hit Root Device, and let it do its thing, after it reboots, it will be rooted.
Install CWM
1. After rooting via the steps above, open up the play store.
2. In search type Rom Manager and install the Rom Manager from Clockworkmod
3. Open up rom manager and it should prompt you to install Clockworkmod Recovery. Click continue OR click the Flash Recovery button, it will search for your device, but it will pop up for the P500 (old Baseband) SELECT THAT ONE! then click normal install.
4. once it says it is successful go ahead and reboot into recovery via the menu in Rom Manager (allow superuser permissions), to verify that clockworkmod is installed. IT WILL HAVE MESSED UP COLORS, and may come up in the dialog box that an error occurred, THAT IS EXPECTED AND IS OKAY. Use the volume keys to navigate, power to select, and the back key to go back.
There, from this point you should be able to do whatever you want to your thrive that you want. I hope this helps.

Nice work. I have confirmed this method works very well on my thrive.
Thanks for your great work..

yoohath said:
Nice work. I have confirmed this method works very well on my thrive.
Thanks for your great work..
Click to expand...
Click to collapse
Thank you for posting this. I almost threw out the phone because none of the other suggestions seemed to work.
This worked for me, but some critical steps were not mentioned in the post.
My phone was automatically booting into emergency mode. After installing the LG UNITED MOBILE DRIVER, just plugging in the phone (in emergency mode) was not enough. It did not load the drivers, and nothing showed up under modems in Device manager. There seems to be different types of emergency modes. I had to do Back + Volume up + Power and then plug it in to get the phone drivers to install. Once it showed up, I disabled the LG modem.
I also had to install the "msxml.msi" program that you had in the same KDZ_FW_UPD_EN diretcory. Without this, the program was crashing with some error messages (sorry, I didn't write them down).
I also had to run "Windows Enabler.exe" in the same directory. I am not sure what this does, but without it, the program was crashing.
Once I got past all that, at first I thought the program froze because nothing was happening and windows complained that it was "Unresponsive". It took a couple of minutes for some log messages to show up. Once it got going it took about 5 minutes to complete.
Then the first boot took a very long time, around 5 minutes. It seemed stuck on the startup screen, but eventually it took me to the phone initializations etc.. and then it worked fine after that.

This works!!! Period. Surprised the hell outta me!!! I have two P506 that have been stuck in Emergency Mode for a couple years. I've tried countless combinations and KDZ's. It took less than 5 minutes to flash the KDZ per phone. Factory reset, and BAM!!! After about 3 minutes or so was welcomed by the Setup Wizard.
@aestivalisakito
Please add the extra things that were mentioned above by @asarangan to the OP. These are actually critical. I'm running Windows 7 64 bit Pro and KDZ Updater kept crashing without them. I enabled Windows Enabler and installed the XML 4 parser. Drivers were previously installed. Tried again and VOILA!!!!
Thanks again

asarangan said:
Thank you for posting this. I almost threw out the phone because none of the other suggestions seemed to work.
This worked for me, but some critical steps were not mentioned in the post.
My phone was automatically booting into emergency mode. After installing the LG UNITED MOBILE DRIVER, just plugging in the phone (in emergency mode) was not enough. It did not load the drivers, and nothing showed up under modems in Device manager. There seems to be different types of emergency modes. I had to do Back + Volume up + Power and then plug it in to get the phone drivers to install. Once it showed up, I disabled the LG modem.
I also had to install the "msxml.msi" program that you had in the same KDZ_FW_UPD_EN diretcory. Without this, the program was crashing with some error messages (sorry, I didn't write them down).
I also had to run "Windows Enabler.exe" in the same directory. I am not sure what this does, but without it, the program was crashing.
Once I got past all that, at first I thought the program froze because nothing was happening and windows complained that it was "Unresponsive". It took a couple of minutes for some log messages to show up. Once it got going it took about 5 minutes to complete.
Then the first boot took a very long time, around 5 minutes. It seemed stuck on the startup screen, but eventually it took me to the phone initializations etc.. and then it worked fine after that.
Click to expand...
Click to collapse
My pleasure I really want Thrive user (small polulation apart from P500) to have fully use this phone. Now I try to flash 4.4.2 Kitkat and battery drained was like froyo unless SElinus was disable from P505 kernel.

Hey nice thread !! Thanks.
I have a P500, and tried a lot of stuffs with KDZ and LGMDP,
your method is close to all of them with some more details,
that for ex :
10 EVERYONE MUST DO THIS STEP EXACTLY WHETHER YOU BOOT AUTOMATICALY INTO EMERGENCY OR NOT! Plug your battery back in, then press and hold the back button + Volume Up + Power. Release ONLY POWER once the thrive starts and then release back and volume up once your in emergency.
Click to expand...
Click to collapse
I'll try it !! I just think the step by step method is the same with my P500 ...
I, until now, got strange errors with KDZ ("Error upgrade - WPARAM : 100 - LPARAM : 4008") and LGMDP (Error AMSS writing),
have you already encoutered them ??
I'll try it tonight on my P500, with the good Drivers and stock Rom for the P500.
If you think you can help me or has another idea, look at my thread !
http://forum.xda-developers.com/showthread.php?p=49390595
Thanks.
Bestrau.

[23:14:54:328] : =============================================
[23:14:54:328] : Log is started on 13.01.2014, at 23:14:54:328,
executable: C:\***\LG_KDZ_FW-Update_OfflineFix\KDZ_FW_UPD_EN\UpTestEX_mod2_marwin.exe (ProcID: 0x00000b98),
compile time : Dec 8 2010 09:19:37
[23:14:54:328] : Version :
[23:14:54:359] : Get Usb Port
[23:14:54:359] : rsi.strFriendlyName=LGE Android Platform USB Serial Port (COM5)
[23:14:54:359] : FriendlyNameList[iii].szFriendlyName=LGE Android Platform USB Serial Port
[23:14:54:359] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 1 - COM5
[23:14:54:359] : Port = COM5
[23:14:54:390] : UNKNOWN : Req(12) -> Rsp(13)
[23:14:54:406] : UNKNOWN : Req(12) -> Rsp(13)
[23:14:54:421] : UNKNOWN : Req(12) -> Rsp(13)
[23:14:54:421] : >> DIAG_STATUS_F FAILED
[23:14:54:437] : >>Get Model Name [DIAG_VERNO_F]
[23:14:54:453] : BAD CONN MODE : Req(0) -> Rsp(3)
[23:14:54:468] : BAD CONN MODE : Req(0) -> Rsp(3)
[23:14:54:484] : BAD CONN MODE : Req(0) -> Rsp(3)
[23:14:54:500] : BAD CONN MODE : Req(0) -> Rsp(3)
[23:14:54:515] : BAD CONN MODE : Req(0) -> Rsp(3)
[23:14:54:531] : BAD CONN MODE : Req(0) -> Rsp(3)
[23:14:54:531] : FAIL (No Phone)
[23:14:54:531] : GetModelName() Operation Failed Check Diag CMD
[23:14:54:531] : EMERGENCY Booting Mode
[23:14:54:531] : >>Get Model Name in Emergency Mode [DLOAD_VERREQ_F]
[23:14:54:546] : BS/P500/7D1\Tom\LOCALS~1\Temp\DZ42.tmp
[23:14:54:546] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 0 - P500
[23:14:54:562] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[23:14:54:562] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[23:14:54:578] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[23:14:54:578] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[23:14:54:593] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[23:14:54:593] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[23:14:54:593] : NV Write Fail : NV ITEM 9028(9028)
[23:14:54:703] : >> GET DLOAD COMM MODE
[23:14:54:718] : [GetCommMode] Communication mode : 2
[23:14:54:734] : Pre Nand Download
[23:14:54:734] : >>Set Trusted Mode [DLOAD_NAND_SEC_MODE] sec_mode = 1 (1=trusted 0=NonTrusted)
[23:14:54:734] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - TRUSTED MODE
[23:14:54:750] : [COM5] >>NandFlashInitWithFile(PARTITION TBL)
[23:14:54:750] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - INIT PARTITION TBL
[23:14:54:875] : ¸Þ½ÃÁö º¸³¿ TYPE_WPARAM_WRITE_TO_SDRAM 3
[23:14:54:875] : [COM0] ¸Þ½ÃÁö º¸³¿ TYPE_WPARAM_WRITE_AMSS 15
[23:14:54:875] : [COM5] >>NandFlashInitWithFile(AMSS MODEM HEADER)
[23:14:54:890] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - INIT AMSS MODEM HEADER
[23:14:54:906] : [COM0] >>Dl_AsyncWrite()
[23:14:54:906] : >> AMSS FLASHING ...
[23:14:54:906] : ¸Þ½ÃÁö º¸³¿ ProgreassiveBar Init wParam TYPE_WPARAM_PROGRESSIVE_POS=5 lParam(pos)=0 nResult=0
[23:14:54:906] : Sending Pkt Seq : 0
[23:14:54:906] : Sending Pkt Seq : 1
[23:14:54:906] : Sending Pkt Seq : 2
[23:14:54:906] : Sending Pkt Seq : 3
[23:14:54:906] : Sending Pkt Seq : 4
[23:14:54:906] : Sending Pkt Seq : 5
[23:14:54:906] : Sending Pkt Seq : 6
[23:14:54:906] : Sending Pkt Seq : 7
[23:14:54:906] : Sending Pkt Seq : 8
[23:14:54:906] : Sending Pkt Seq : 9
[23:14:54:921] : Dl_AsyncWrite - ErrNo(45), Addr(0x00004800), NandErrNo(0x04)
[23:14:54:921] : [COM0] ERROR Dl_AsyncWrite() TYPE_LPARAM_UPGRADE_ERROR_WRITE_TO_FLASH
[23:14:54:921] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - Close Port
[23:14:54:921] : Close Port<<
[23:14:54:921] : TYPE_WPARAM_UPGRADE_ERROR
[23:14:54:921] : ¸Þ½ÃÁö º¸³¿ - TYPE_WPARAM_UPGRADE_ERROR Error Code = 4008
[23:14:54:937] : Log finished
Click to expand...
Click to collapse
It unfortunately didn't work for me ...
Any ideas of what the problem could be ?

@shinobisoft...feels good to have two bricks turn to gold again?
Sent from my LG-P500

Thank you so much for this!! I looked everywhere and tried multiple KDZ files with various computers and settings, but only this worked! Time to get CWM and Kitkat running on this thing. >

Hey guys I will add the aforementioned items to the original post. Sorry I have been away on deployment and have not been able to attend to this or any of my other threads. I'll get back on it
Website signature

[Solved] Help me root my Z3 (Unlocked BL, Android Ver. 5.0.2, Build 23.1.A.1.28)

Hey xda-community.
First of all, excuse me for my english, i'm from Switzerland and had an iPhone (jailbroken (much easier!))
I'm getting really confused, i'm trying to root my Z3 for 4 days! Tried out different tutorials on different sites (while looking at the Device, Buildnumber and Androidversion + Instructions on the sites & programs) but it's annoying with so much undetailed tutorials (where to get .ftf, where do i find a "boot.img" <-didn't download anything from here)...
What I did until now:
Looked on my device with *#*#7378423#*#* if BL unlock is possible. It is.
Then I unlocked it over http://developer.sonymobile.com/unlockbootloader/ and it worked.
After reading about the Flashtool, i found this one: http://developer.sonymobile.com/services/flash-tool/
Used it in hope that it will root it, which it didn't when looking in the Service Info on my Z3.
I found later the real Flashtool by Androxyde and downloaded with the integrated XperiFirm the .FTF (Xperia Z3, D6603, CDA: 1288-9930, Switzerland, Customized CH)
After downloading, it unpacked the files and then the Firmware Selector window popped up. I disabled on Wipe: "CACHE" and "DATA" and pressed on Flash.
The Debug info showed text like this:
Code:
. . .
- DEBUG - (USBFlashWin32.java:65) - IN : CommandID : 4 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
- INFO - (X10flash.java:558) - Flashing finished.
. . .
After starting my Z3, the root button (the open lock icon) enabled for me.
Clicked on it -> selected SuperSU -> Ok -> then this:
Code:
. . .
- INFO - (RootJob.java:112) - Running part1 of Root Exploit, please wait
- DEBUG - (AdbUtility.java:270) - Pushing C:\Flashtool\custom\shells\rootit_work to /data/local/tmp/rootit
- DEBUG - (ProcessBuilderWrapper.java:93) - 110 KB/s (678 bytes in 0.006s)
- INFO - (AdbUtility.java:348) - Running rootit
- DEBUG - (ProcessBuilderWrapper.java:93) - mmap() failed. Invalid argument
- INFO - (Devices.java:120) - Waiting for device. After 60secs, stop waiting will be forced
- ERROR - (RootJob.java:123) - The part1 exploit did not work
- INFO - (RootJob.java:124) - Cleaning files
- DEBUG - (AdbUtility.java:356) - Running rm /data/local/tmp/psneuter command
- DEBUG - (AdbUtility.java:356) - Running rm /data/local/tmp/busybox command
- DEBUG - (AdbUtility.java:356) - Running rm /data/local/tmp/Superuser.apk command
- DEBUG - (AdbUtility.java:356) - Running rm /data/local/tmp/su command
- DEBUG - (AdbUtility.java:356) - Running rm /data/local/tmp/rootit command
- DEBUG - (AdbUtility.java:356) - Running rm /data/local/tmp/rootit2 command
- DEBUG - (ProcessBuilderWrapper.java:93) - rm: /data/local/tmp/rootit2: No such file or directory
Can someone somehow help me?

You're not alone with having problems
I'm trying to root my phone, too, which is equipped with 23.1.A.1.28 firmware, but I'd like to avoid unlocking the BootLoader (though it's possible according to service menu). As far as I understand the various tutorials there's just one way to root my device - downgrade firmware to 23.0.A.2.93, root by using giefroot, then install a prerooted lollipop firmware.
Alas, downgrade didn't work for me -> http://forum.xda-developers.com/z3/help/flashtool-downgrade-t3122477

Ok i found a solution and worked very good (just took some time at giefroot). I did this tutorial ( http://forum.xda-developers.com/z3/general/guide-rootrecovery-how-to-root-install-t3017056 ). But before i began with it, i relocked my BL with Flashtool. I wonder if the Trimm Area isn't damaged after all

Vanta-Chan said:
Ok i found a solution and worked very good (just took some time at giefroot). I did this tutorial ( http://forum.xda-developers.com/z3/general/guide-rootrecovery-how-to-root-install-t3017056 ). But before i began with it, i relocked my BL with Flashtool. I wonder if the Trimm Area isn't damaged after all
Click to expand...
Click to collapse
Say bye bye to TA partition...now join petition that Sony support Android Camera API 2.0 so that you can have similar algorithm for real time photos enhancement...

Huawei Honor 3Xs ( CLONE ) SC6825C bricked HELP

I have this issue :
- the phone just went dead one day, doesn`t switch on, doesn`t charge, can`t load preloader, nothing...dead.
- it has SPREADTRUM SC6825c chipset
- driver on PC correctly installed and up to date
- when I try flashing using RESEARCH DOWNLOAD TOOL, I get this error message : OPERATION FAILED or `Download size file larger then it`s partition`
- I have tried using several PACs, everytime same ERROR
- I have tried flashing one file after another, same ERROR
- Research download tool is 2.9.8004.
Does anyone have an advice what to try next ?

Alcatel OneTouch Pixi 3 (8) WIfi [Model 8070 mt8127] - Custom Recovery [TWRP 3.0.2.0]

After some effort, I present you TWRP 3.0.2.0 custom recovery for Alcatel OneTouch pixi 3 (8) Wifi, model 8070.
The specific recovery is currently under some progress, but this build is working really well except from touch input.
CREDITS :
@yuweng for providing a convenient and automated way to build a twrp recovery -> twrp-build script.
Changelog:
- v2.2: Changes in partition scheme. Also the "wipe with rm -rf" instead of formating is now the default setting, for compatibility in restoring a backup.
- v2.1: Some minor changes in recovery.fstab. Thanks to @yuweng for mention it out!
- v2.0: Now the graphics are displayed in better resolution. Cpu temp is now working. Still touch is not fixed though
Things that work:
- Battery Percentage
- CPU Temp
- Installing superSU
- Installing xposed-framework
- full backup/restore process (explained at the end of the post)
Things that don't work:
- Touch (You'll have to connect a mouse through OTG cable in order to use the recovery)
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROM's have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledge about the phone and phone utilities also.
Make sure that whatever you do, you are doing it at your own responsibility.
In order to install it, you'll have to unlock the bootloader of the device first. Read the steps before procedure. Take a backup of your files before proceeding!
How to unlock bootloader:
- Power on device and boot into Android.
- Connect the device to PC through cable
- Go to settings -> storage and press the 3-dot menu and select "USB computer connection". Next, select connect as Built-in CD-ROM option.
- Now, go to My Computer and install the driver of the virtual disc that is mounted from device.
- Supposing that the driver is installed correctly, we activate adb for our device.
- Go to settings -> about tablet -> hit 7-8 times on "build number", congrats, you're now a developer!
- Go to settings -> developer options -> hit USB debugging and press OK on the popup window. If the connection is working, one more popup is going to appear asking you to allow the connection, Tick the box "always allow from this computer" and press OK.
- Open an adb terminal and check if the device is working properly typing "adb devices". The serial number of your device should appear, so everything is OK!
- Now, boot into fastboot typing "adb reboot-bootloader". The device is going to reboot and boot into fastboot mode, waiting for command.
- For the bootloader to be unlocked, you have to type "fastboot oem unlock". A warning message regarding bootloader unlocking should appear on the device, waiting for an answer. Press the volume+ key and the bootloader is now unlocked! WARNING! ALL DATA ON THE DEVICE IS GONNA BE WIPED, so backup your files before.
- Wait for the wiping of the device to be finished and then you're ready to install the twrp custom recovery!
How to install TWRP:
- We must be in fastboot mode once again. You can either boot holding power button & vol+ while the device is powered off, or type the command in the adb terminal "adb reboot-bootloader" while the device is connected to PC and is booted into Android.
- Assuming that you are in fastboot mode and the device is connected to the PC, you open an adb terminal and type "fastboot flash recovery /path/to/twrp-recovery".
Replace the path reflecting your path's downloaded twrp.
- Congrats! You now have your twrp custom recovery installed!
In order to operate the twrp, due to lacking of touch input, you'll have to connect a mouse using an OTG cable.
You can now install whatever you want, from supersu to xposed-framework, you can take full backups with restore capabilites, and many more interesting stuff!
I'll try to fix the bugs, but because I'm not a developer, I'm just a power user with some advanced linux knowledge, if any dev knows and willing to help me fix the touch screen issue, he's more than welcome!
Info about backup/restore process:
The specific device has one ubnormality. It stores some of the data in a separate partition called "custom". What I found out was that if you format this partition, even if you restore a backup image, the device doesn't boot, or it boots in boot loops.
So, after some testing, I found out that the process for a reliable and working backup image, is to do the next steps:
For creating a backup:
- Go to twrp settings and select use -rm instead of formatting
- You should only choose Data, Custom & System. No need for anything else, but if you want, you can backup the rest of the dirs, just in case.
For restoring a backup:
- Wipe the Dalvik Cache, Cache, System, Data, Custom partitions. You don't need to wipe the Internal Storage or/and External SDcard, if you don't want to lose your personal data like, photos, music, etc. But, you should always take a backup of these files at any case!
- Choose Data, System, Custom partitions from twrp backup dir
- Reboot

Can we get some screenshots?

kirito9 said:
Can we get some screenshots?
Click to expand...
Click to collapse
It's planned but I have to install a screenshot script first. But if you want to see, I'll take some shots in analogue way.

dam85 said:
It's planned but I have to install a screenshot script first. But if you want to see, I'll take some shots in analogue way.
Click to expand...
Click to collapse
Nicee .

@kirito9 You can see the images on the first post

dam85 said:
@kirito9 You can see the images on the first post
Click to expand...
Click to collapse
Good, you'll get your thanks tomorrow (ran out)

Can I use it on Pixi 3 (8) WiFi I220 model?

zakk87 said:
Can I use it on Pixi 3 (8) WiFi I220 model?
Click to expand...
Click to collapse
I'm not sure. Probably not. This build is for mt8127 cpu and the most important thing, is the partition scheme of your device. The recovery partition has to be in the same position with pixi 3 8 in order to not cause brick.
But I can help you. If you could post your dumchar_info (/dev/proc/dumchar_info), I can tell you if it's the same. Maybe you must to be rooted in order to view this file. Try with kingroot.

Unfortunlately i have a bootloop and I don't know how to recover this device. Alcatel upgrade tool say it's up to date.

zakk87 said:
Unfortunlately i have a bootloop and I don't know how to recover this device. Alcatel upgrade tool say it's up to date.
Click to expand...
Click to collapse
If it's already bricked, you could try it (won't get worse afterall). But you'll have to unlock the bootloader first, follow my guide to do this.
Mobile Upgrade tool doesn't work? Can you tell me the full model name, to have a look please?

Did you try with this one? I've just checked that it has your model in the list.

My device is i220 model. No 3G, wifi only. I think its mt8127 CPU and I'm wondering how can I recover software.

zakk87 said:
My device is i220 model. No 3G, wifi only. I think its mt8127 CPU and I'm wondering how can I recover software.
Click to expand...
Click to collapse
First of all, how did you get into bootloop? Did you try to install xposed framework? In order to restore your tablet, you have to get the stock rom, through a rom readback or through a custom recovery backup. For alcatel devices, through mobile upgrade tool. Try the one I posted and give me a feedback.

I have this update tool but doesn't work.
Now I'm trying backup but it's very slow.
This device is from Orange, my friend hit factory data reset button by menu and it's all. Device bricked.

zakk87 said:
I have this update tool but doesn't work.
Now I'm trying backup but it's very slow
This device is from Orange, my friend hit factory data reset button by menu and it's all. Device bricked.
Click to expand...
Click to collapse
Try with mobile upgrade 4.4.5 version. Uninstall the other one first.
I don't think that a read back of your already bricked rom is gonna make any good. You need a working rom
Basically, your device is not bricked. Your friend just wiped your rom from device, so there isn't any os to boot, that's why the boot loops.
Try to restore it through mobile upgrade tool 4.4.5 (uninstall all other versions), and give me a shot of the fail screen.

the fail screen and log:
The phone's cu is I220-2DRGPL1
The phone's IMEI is 94D85xxxxxxxxxxxx
The phone's version is D33EO30
The version in the server is NULL
Click to expand...
Click to collapse
2015/06/16 10:53:40 [DEBUG] Thread #0xe08 has been successfully started.
2015/06/16 10:53:40 [INFO] ############################################################
2015/06/16 10:53:40 [INFO] OTU DLL Version 3.1.8, Build Id=2015031600, Protocol Id=20130822.
2015/06/16 10:53:44 [INFO] Shutting down O.T.U. Library ...
2015/06/16 10:53:44 [DEBUG] Thread #0xe08 received shutdown request.
2015/06/16 10:53:44 [DEBUG] Thread #0xe08 terminated.
2015/06/16 10:53:44 [INFO] O.T.U. Library: Succeeded to join AM!
2015/06/16 10:53:44 [INFO] O.T.U. Library: Succeeded to join MD!
2015/06/16 10:53:44 [DEBUG] Request Executor Thread #0xde4 has been terminated.
2015/06/16 10:53:44 [INFO] O.T.U. Library: Succeeded to join ReqExecutor!
2015/06/16 10:53:44 [INFO] O.T.U. Library: Great! No timer exists in scheduler after shut down all threads.
2015/06/16 10:53:44 [INFO] O.T.U. Library has been shutdown!
2016/05/17 18:55:45 [INFO] ############################################################
2016/05/17 18:55:45 [INFO] OTU DLL Version 3.2.8, Build Id=2015052611, Protocol Id=20130822 SessionBackupFile path=downloaded/session_backup.txt.
2016/05/17 18:55:45 [ERROR] Failed to open file 'downloaded\E1\FE\E1FE54CF356003567A2579519EFE0582F6A1DA0A.bin' due to non existing path.
2016/05/17 18:55:45 [ERROR] Failed to open session file.
2016/05/17 18:55:45 [ERROR] load session from disk failed!
2016/05/17 18:55:45 [ERROR] Failed to open file 'downloaded\65\A2\65A22D35BB44A8D51AE2ECF8936A5B25C9763242.bin' due to non existing path.
2016/05/17 18:55:45 [ERROR] Failed to open session file.
2016/05/17 18:55:45 [INFO] O.T.U. Library has been successfully initialized!
2016/05/17 18:55:45 [DEBUG] Thread #0x4d4 has been successfully started.
2016/05/17 18:55:45 [DEBUG] Request Executor Thread #0x4f8 has been successfully started.
2016/05/17 18:55:45 [INFO] ############################################################
2016/05/17 18:55:45 [INFO] OTU DLL Version 3.2.8, Build Id=2015052611, Protocol Id=20130822.
2016/05/17 18:55:56 [DEBUG] GisusDllImpl::create_device_info...
2016/05/17 18:55:56 [DEBUG] Thread #0x4d4: Request Processing is Starting ...
2016/05/17 18:55:56 [DEBUG] Thread #0x4d4: We have to connect first to 184.73.174.232 ...
2016/05/17 18:55:56 [DEBUG] Thread #0x4d4: Successfully connected to 184.73.174.232!
2016/05/17 18:55:57 [DEBUG] AMConnection::TickVersionReq: Connection #0x4d4: to check report info !
2016/05/17 18:55:57 [INFO] Thread #0x4d4: Upgrade for current software is not available.
2016/05/17 18:57:27 [INFO] Shutting down O.T.U. Library ...
2016/05/17 18:57:27 [DEBUG] Thread #0x4d4 received shutdown request.
2016/05/17 18:57:27 [DEBUG] Thread #0x4d4 terminated.
2016/05/17 18:57:27 [INFO] O.T.U. Library: Succeeded to join AM!
2016/05/17 18:57:27 [INFO] O.T.U. Library: Succeeded to join MD!
2016/05/17 18:57:27 [DEBUG] Request Executor Thread #0x4f8 has been terminated.
2016/05/17 18:57:27 [INFO] O.T.U. Library: Succeeded to join ReqExecutor!
2016/05/17 18:57:27 [INFO] O.T.U. Library: Great! No timer exists in scheduler after shut down all threads.
2016/05/17 18:57:27 [INFO] O.T.U. Library has been shutdown!
Click to expand...
Click to collapse
I found i213 model ROM but i don't know is it fit -
Code:
[url]http://chomikuj.pl/marcin.l19/Alcatel+pixi+7+i213+MT8127[/url]

So, you have to get a working rom from another same, working device through read back. I suggest to mail alcatel support asking for an image, or for a working method of mobile upgrade tool, they should reply to you within 24-48 hours.
I'll have a look too. When you get a reply, post again on the thread.

zakk87 said:
the fail screen and log:
I found i213 model ROM but i don't know is it fit -
Code:
[url]http://chomikuj.pl/marcin.l19/Alcatel+pixi+7+i213+MT8127[/url]
Click to expand...
Click to collapse
Maybe it will. The cpu is the same. Try to flash only system partition to see if it works.

I flashed android but memory test gives me:
============ Memory Detection Report ===========
Internal RAM:
External RAM:
Type = DRAM
Size = 0x20000000 (512MB/4096Mb)
NAND Flash:
ERROR: NAND Flash was not detected!
EMMC:
EMMC_PART_BOOT1 Size = 0x0000000000400000(4MB)
EMMC_PART_BOOT2 Size = 0x0000000000400000(4MB)
EMMC_PART_RPMB Size = 0x0000000000080000(0MB)
EMMC_PART_GP1 Size = 0x0000000000000000(0MB)
EMMC_PART_GP2 Size = 0x0000000000000000(0MB)
EMMC_PART_GP3 Size = 0x0000000000000000(0MB)
EMMC_PART_GP4 Size = 0x0000000000000000(0MB)
EMMC_PART_USER Size = 0x00000000e9000000(3728MB)
UFS:
ERROR: UFS was not detected!
Click to expand...
Click to collapse

zakk87 said:
I flashed android but memory test gives me:
Click to expand...
Click to collapse
How did you try to flash it? Through sp flash tool? This tool isn't working properly on alcatel tablets. You should try through twrp, maybe it works.

[Completed] [X620] - Black Screen,no boot only Red Light

Hello Guyzs, i'm totally newbie on Leeco Phone. My phone (Leeco Le X620) does not start anymore. I have only charge indicator that lights up (RED LIGHT). I try to follow this Topic : red-light-recovery-process
1 - Open FLASH TOOLS and chose DA_PL_HIGH (in my case that one worked, if doesn't for you choose DA_PL).
2 - Choose the MT6797_Android_scatter.txt
3 - Choose the Authentication file.
4 - Keep in DOWNLOAD ONLY
5 - Uncheck BOOT and RECOVERY. Keep the rest.
6 - Click DOWNLOAD.
7 - Phone needs to be OFF. Plug the phone (no volume up or down required). Let the process finish.
That will bring the phone to live again but it won't boot. Let's move forward.
8 - Press CTRL-ALT-V and chose OPTIONS>>WRITE MEMORY
9 - Choose the RECOVERY_STOCK_WORKS _AFTER_BRICK.img
10 - Write to address 0x8000.
11 - Phone OFF again, click WRITE and plug the phone (no volume up or down required).
After that another process
12 - Open FLASH TOOLS and chose DA_BR (PAY ATTENTION, THE FILE CHANGED).
13 - Choose the MT6797_Android_scatter.txt
14 - Choose the Authentication file.
15 - Keep in DOWNLOAD ONLY
16 - Uncheck BOOT and RECOVERY. Keep the rest. (AGAIN)
17 - Click DOWNLOAD.
18 - Phone needs to be OFF. Hold VOLUME UP and plug the phone. Let the process finish.
Now after all of these, you should be ready for the BOOT and RECOVERY.
19 - Open FLASH TOOLS and chose DA_BR (PAY ATTENTION TO THE FILE)
20 - Choose the MT6797_Android_scatter.txt
21 - Choose the Authentication file.
22 - Keep in DOWNLOAD ONLY
23 - CHECK ONLY BOOT
24 - Click DOWNLOAD.
25 - Phone needs to be OFF. Hold VOLUME UP and plug the phone. Let the process finish.
Repeat 19 to 25 for RECOVERY.
Click to expand...
Click to collapse
BUT:
DOWNLOAD :
secureboot\DA_PL_HIGH.bin
+
secureboot\MT6797_Android_scatter.txt
+
Only PRELOADER check
=
WORKS
after Write Memory :
ecovery_stock_works _after_brick.img
+
0x8000
=
WORKS
After DOWNLOAD :
secureboot\DA_BR.bin
+
secureboot\MT6797_Android_scatter.txt
+
Uncheck BOOT and RECOVERY. Keep the rest.
=
FAILED
ERROR MESSAGE :
BROM ERROR :STATUS_OPEN_FILE_ERR (0xC001000E)
Click to expand...
Click to collapse
I try with Mediatek SP Tool V5.1612, V5.1628, V5.1636 or .....Do you have an IDEA please ?
And last news,my PHONE is not recognized by SP Tool. Drivers Preloader Vcom don't appear but i used mediatek-Driver_Auto_Installer_v1.1236.00
I need help

Littleminx said:
Hello Guyzs, i'm totally newbie on Leeco Phone. My phone (Leeco Le X620) does not start anymore. I have only charge indicator that lights up (RED LIGHT). I try to follow this Topic : red-light-recovery-process
BUT:
DOWNLOAD :
secureboot\DA_PL_HIGH.bin
+
secureboot\MT6797_Android_scatter.txt
+
Only PRELOADER check
=
WORKS
after Write Memory :
ecovery_stock_works _after_brick.img
+
0x8000
=
WORKS
After DOWNLOAD :
secureboot\DA_BR.bin
+
secureboot\MT6797_Android_scatter.txt
+
Uncheck BOOT and RECOVERY. Keep the rest.
=
FAILED
ERROR MESSAGE :
I try with Mediatek SP Tool V5.1612, V5.1628, V5.1636 or .....Do you have an IDEA please ?
And last news,my PHONE is not recognized by SP Tool. Drivers Preloader Vcom don't appear but i used mediatek-Driver_Auto_Installer_v1.1236.00
I need help
Click to expand...
Click to collapse
Greetings and welcome to xda, it is difficult to help if your phone is not recognised. Where did you get the mod ? I have seen a little development for your device and a custom rom/recovery but they need fastboot
Good Luck
Sawdoctor

THX Sawdoctor
SURE
it is difficult to help if your phone is not recognised.
Click to expand...
Click to collapse
I have uninstalled and reinstalled PRELOADER Drivers several times but they are never used. Only the "MediaTek USB Port" driver appears and is used.
I think the phone is dead
Unless you know of another solution.