Related
I've tried many different ways and many have failed me, so I'm documenting one way which worked for me.
You will need the Acura recovery
http://www.mediafire.com/?5io5b2r98nt28bb
and gazhead's SU zip
http://forum.xda-developers.com/attachment.php?attachmentid=1352095&d=1348524309
Preparation
Extract the recovery package
Step 1: Drivers
Make sure you have the OMAP 4430 drivers installed.
If you do, skip this step
Note: On windows 8, you will need to have rebooted your computer into a mode which lets you install unsigned drivers. Do a Google search to find out how.
To install the omap drivers:
Turn off the phone
Remove the battery
Open Windows' device manager
Connect the phone to the PC.
When OMAP4430 appears in your list of devices, double-click on it and select "update driver software"
When asked, pick the usb_drv_windows folder extracted from the recovery package and go through with the installation
When the installation has completed, you should have a new category called "Ti Boards" with the OMAP4430 USB device under it.
Step 2: Installing recovery
Disconnect the phone
Go to the recovery folder and launch "Instalar Recovery ICS Europeo.bat"
The script will be waiting for the phone to be connected.
Press "vol up"
Connect your phone, without any battery
As soon as the script does something, release the button and insert the battery
As soon as the script stops, disconnect the USB cable.
When you see the silver LG logo, connect the USB cable again
The script should complete its task soon after that.
Note: If the script is waiting for something, pay attention to your list of devices, you may have a LG COSMO device which has no drivers. If this is the case, install the OMAP4430 drivers and start the script again.
Step 3: Rooting
Put gazhead's file on your SD card
Turn off phone
Press "vol down" + 3D button + power to boot into recovery
Install the zip file from your SD card
Reboot
That's it. Help me improve this post by reporting any errors you see and I hope this will save people some time
All the information contained in this thread comes from this post in Spanish.
ofutur said:
I've tried many different ways and many have failed me, so I'm documenting one way which worked for me.
You will need the Acura recovery
http://www.mediafire.com/?5io5b2r98nt28bb
and gazhead's SU zip
http://forum.xda-developers.com/attachment.php?attachmentid=1352095&d=1348524309
Preparation
Extract the recovery package
Step 1: Drivers
Make sure you have the OMAP 4430 drivers installed.
If you do, skip this step
Note: On windows 8, you will need to have rebooted your computer into a mode which lets you install unsigned drivers. Do a Google search to find out how.
To install the omap drivers:
Turn off the phone
Remove the battery
Open Windows' device manager
Connect the phone to the PC.
When OMAP4430 appears in your list of devices, double-click on it and select "update driver software"
When asked, pick the usb_drv_windows folder extracted from the recovery package and go through with the installation
When the installation has completed, you should have a new category called "Ti Boards" with the OMAP4430 USB device under it.
Step 2: Installing recovery
Disconnect the phone
Go to the recovery folder and launch "Instalar Recovery ICS Europeo.bat"
The script will be waiting for the phone to be connected.
Press "vol up"
Connect your phone, without any battery
As soon as the script does something, release the button and insert the battery
As soon as the script stops, disconnect the USB cable.
When you see the silver LG logo, connect the USB cable again
The script should complete its task soon after that.
Note: If the script is waiting for something, pay attention to your list of devices, you may have a LG COSMO device which has no drivers. If this is the case, install the OMAP4430 drivers and start the script again.
Step 3: Rooting
Put gazhead's file on your SD card
Turn off phone
Press "vol down" + 3D button + power to boot into recovery
Install the zip file from your SD card
Reboot
That's it. Help me improve this post by reporting any errors you see and I hope this will save people some time
All the information contained in this thread comes from this post in Spanish.
Click to expand...
Click to collapse
This method not working for me :/
I do successfull step 2, but Recovery menu not working (i have balck screen)
animavitis said:
This method not working for me :/
I do successfull step 2, but Recovery menu not working (i have balck screen)
Click to expand...
Click to collapse
Are you sure that you pressed:
"vol down" + 3D button + power
?
It seems the combination changes depending on the recovery...
I tried this but when the phone rebooted and the script waits for device my phone is at the S/W screen with the korean writing. i didnt want to go any further, is this normal?
Mozzytm said:
I tried this but when the phone rebooted and the script waits for device my phone is at the S/W screen with the korean writing. i didnt want to go any further, is this normal?
Click to expand...
Click to collapse
Try releasing the vol key before inserting the battery. This worked for me.
Sent from my LG-P920 using xda app-developers app
Mozzytm said:
I tried this but when the phone rebooted and the script waits for device my phone is at the S/W screen with the korean writing. i didnt want to go any further, is this normal?
Click to expand...
Click to collapse
fastboot failed to load , try again until you get the fastboot menu , try to press vol- instead of vol+ or even no vol button at all
I cant enter recovery mode
i just installed and then pressed the buttons but it doesnt work
Edit: I rooted by installing TWRP recovery and it worked
Lets say i TOTALLY screw this up.. what is the absolute worst case scenario? Can i brick it or is soft brick worst case?
It can be fixed
Send from my XBSA ICS V7.2 P920.
Space for Apps
Good evening, the home version of SU760 had 2GB of space for installing applications ... Already the European version of the P920, only has 1GB of internal memory dedicated space .... Is there a way to change this? Well I tried to restore the apps that I had, and gave memory overflow ...
Thanks
Translate by Google
Is there any chance of "security error" with this?
Sent from my LG-P920 using xda app-developers app
I need help rooting my blu quattro 4.5 dd440 i install drivers via pdanet i tried many version of binary v30 15 31 etc and i get bootloop and system ui error all the time infinate times. I need phone rooted to unistall pre installed apps like facebook and other crap apps that take up ram. please help me if u can
BLU Quattro 4.5 (440D) GSM Recovery+Root
Hello... I got my BLU Quattro 4.5 (D440) a while back, didn't fuzz with it much right off. The Stock ROM was sluggish at best thought there was even an issue with the Digitizer/screen. But this thread was extremely helpful. I am now running Shendu ROM 4.1.2 one of the suggested ROM's above. I tried the other 2 first and they were mostly in Chineese and I had an especially hard time getting them switched over to English. Either way onward to the point. I have put together a few helpful tips-tricks for my experience with this phone and its phoenix transition to an awesome handset. Thats right now this is my daily driver and I love it! See below hope its helpful.
BLU Quattro 4.5 (440D) GSM Recovery+Root
These steps for this phone only!! Not responsible for any issues.
1. download ROM's, Recovery, & Driver from XDA (this thread)
http://forum.xda-developers.com/show....php?t=2327417
2. Enable USB Debugging! Go into Apps-Settings-DevOptions - Check box for USB Debug
3. Have original USB cord if handy! I tried with a Samsung OEM cable but no luck getting drivers to stick. Use original is best. (If you have one.)
Plug in USB Cord to PC then Phone and see if windows detects drivers. let it. It wont get the ones u need later, but what it does find is for USB storage. (you can move over your ROM's/Gapps to storage, downloads folder is a good spot).
4. Go to... http://junefabrics.com/android/downloadold.php to get pdanet software. Install it and it will give i the right drivers for ADB support. I used 4.01 to match the android version currently on my phone.
5. Extract the Driver provided from XDA. Put it in a folder with the ADB commands. Or you can get it all here... http://downloadandroidrom.com/file/G...usRootNew.zipn <-- I know this isn't for BLU but, if you extract this to a folder, and also add the drivers extracted to it as well this works! I've done it.
6. Extract the English Recovery to the same folder.
7. Turn off your phone. Hold down Vol up and Power button for about 5-9 seconds. Once you see a green screen let go of both. Screen may flicker then go black but the icons at the bottom will stay lit. You are now in APX mode (nvflash) mode. (as stated above in original post)
8. Check your Win 7 PC device manager. For a Phone device with ADB. If you you may need to update driver with the one that came from XDA, but the PDANet software should make it work.
8. Go to the folder and find Recovery.bat file (may have Chinese in file name. Double click and a command prompt window will pop up with a bunch of unknown characters, wait 5 sec then hit enter. The batch file should take of pushing the necessary recovery through ADB to the phone. It will error if it can't.
9. If completes OK. Push power for 7-9 seconds to power off the phone. Hit power like normal to turn it back on. It will boot up like normal (or it should).
10. USB is still connected this whole time and you can open a command prompt window. Navigate to the folder you placed the Recovery into. Something like user/username/desktop/BLU/recovery..etc)
Type ADB devices....it should show you that is is connected to your device. Then type " adb reboot recovery " and the device should reboot, give it some time.
11. Once in recovery. Best to do a backup of the original ROM & system. that way you can get back into recovery if anything goes wrong and wipe out the problem by restoring and starting again.
After you backup === you can get into recovery without the command being typed in or even being connected to your PC.... By holding Vol up + Power till you see the green screen then let go of power but keep holding Vol up till you see the BLU Products boot screen then let go ===
Clockworkmod Recovery should be on your screen.
you can reboot phone now and get back to original with no changes. Or you can venture into the world of loading ROM's (There in your downloads folder if you saved them in Step 3)
ROM 101
BACKUP-BACKUP-BACKUP 1st thing once in Recovery ...can't stress enough how much of trouble you can keep yourself out of by keeping an original backup.
As I stated before the Shendu ROM + Gapps is running smooth and all features I've been trying are working flawlessly!! Thanks to original post for getting me going. Just thought I'd add my 2 Cents.
I am not responsible for anything that happens in your life. Including what happens as result of following steps in this thread.
Hello all. After a long journey here, we figured a new thread would be in order for new comers not to have to read through fifty pages of information. Here you will find firmware to fix or update your Viking Pro. You will also find root methods, bootloader unlock and custom recoveries for this tablet. Lets start with ROOT...
Method 1: Kingroot. Kingroot works on this device. you can find it here. It's pretty straight forward, just download and install the apk and root.
Method 1.5: SuperSu. Kingroot works but it's not the best root out there. once you have root, follow the instructions here and Kingroot will be replaced with SuperSu.
Method 2: Su flash-able ZIP. This method requires you to follow steps in posts No. 3 and 4. Once you have custom recovery installed, You can flash This.
This method is a bit redundant. However, it does allow you to make a completely stock unooted backup of your rom before making any changes.
Check out posts 2, 3, 4 & 5 for the good stuff.
I'm gonna go ahead and thank everyone responsible and If I forgot to mention you, please don't hesitate to tell me and I will correct the situation:
@Bogram (Edited the bootloader so it could be unlocked on x.12.x versions)
@Jacube22 (Duplicated the method from Bogram to make the bootloader on x.9.x versions unlockable)
@vampirefo (Compiled a compatible CWM recovery for us)
@ewilley2008 (Found most of the firmware)
@mayzemay (Initial root thread)
@NepoRood
@jerryvail35
@Sir Jaxxy
@Snigglez
@Spartan Legionnaire
@bobl61
@csla
@Chainfire (For root)
FIRMWARE
There are two main branches of development for this tablet. It is very important to know which one you have because they are incompatible with each other. I personally bricked my first one with firmware from a x.9.x while mine is x.12.x. How do you check? Simple. In your build number, you can find it in "About tablet" in Settings or in the text at the top of the recovery screen. It's at the end of the number and it will look like 1.12.30, 10.12.20, 2.12.20, 1.9.1, 1.9.5, 10.9.1...etc The number in the middle is the important one.
Steps(Windows): For step 2 you will have five seconds. Preloader mode is only active for five seconds. So read first!
1- Extract the drivers to the destktop and open the device manager.
2- Plug your tablet in as such: turn off the tablet. Plug a male to male USB wire from the computer to the USB port on the tablet. now plug the power wire into the tablet. now very quickly in the device manager locate the new device and right click on it. select "update driver software" then select "browse my computer for driver software" and "browse". Now navigate to the driver folder, select the "CDC" folder and click on "OK" the "Next". The driver should install at this point. Once that is done, unplug the power cable from the tablet.
3- Extract the firmware and the sp flash tools to your desktop.
4- Start the sp flash tools and where it says scatter file loading click and navigate to the folder where you have the firmware and load the scatter file. You will see the firmware get loaded and a checksum check.
5- Once that is done, uncheck the preloader from the list and click on the download button.
6- Plug the power cable into your tablet. At this point the sp flash tool will load the firmware into the tablet. DO NOT UNPLUG ANYTHING UNTIL THE SP FLASH TOOLS SHOWS YOU A GREEN CHECK MARK TO INDICATE THAT IT IS DONE OR YOUR TABLET COULD BE HARD BRICKED AND UNREPAIRABLE.
7- Press the reset button and turn it on. Done!
Drivers: https://drive.google.com/file/d/0Bz4bOoJ_E5XzRWJCbGFINndmVmc/view?usp=sharing
SP Flash tools: https://drive.google.com/file/d/0Bz4bOoJ_E5Xzb0g3ZnlEcHE0bEE/view?usp=sharing
Firmware x.9.x:
RCT6303W87DK-ANDROID5.0-V37-V10.9.21-NFC-V2.3LA-20150820
RCT6303W87DK-ANDROID5.0-V32-1.9.1-20150409
Do not flash the preloader for the Surf1001 versions!!
Firrmware x.12.x:
RCT6303W87DK-ANDROID5.0-V77-V1.12.50-EMMC-user-Kingston-V6.1_20160316
RCT6303W87DK-ANDROID5.0-V70-V1.12.30-B-EMMC-user-Kingston-V6.1_20160121
SURF1001-ANDROID5.0-V11-V7.15.0_T8515B_V6.3_SAMSUNG2G_20151116 (Use method No.2 for root)
RCT6303W87DK-ANDROID5.0-V63-V10.12.0_T8515B_V6.3_PCDDR31G_20151106
SURF1001-ANDROID5.0-V07-V7.15.0_T8515B_V6.3_SAMSUNG2G_20151016
RCT6503W87DK-ANDROID5.0-V66-V20.12.20-B-Camera-2M_PCDDR_V6.3-20150928
RCT6303W87DK-ANDROID5.0-V63-V2.12.20-B-EMMC-user-Kingston-V6.1_20150811
Sources:
http://laurentiumihet.ro/technology/...test-versions/
http://www.needrom.com/download/mtk-...er-v5-1453-03/
http://pan.baidu.com/share/home?uk=2...ategory/type=0
http://baiduyun.57fx.cn/so-result.ht...7DK&type=share
And Google of course...
Bootloader
So the bootloader on this tablet is locked. To unlock the bootloader, in a perfect world, you would usually boot the tablet in fastboot and type the command "fastboot oem unlock" and then follow the instructions on the screen. However RCA did not code in the volume keys in fastboot mode so it was impossible to unlock the bootloader that way. So our friend Bogram edited the bootloader and now the volume keys are not needed. What swell guy eh?
Unlocking your phone’s bootloader completely wipes (formats) your Android phone’s internal memory including applications, contacts, SMS and MMS messages etc.
So what you need is a scatter file like this one and a patched bootloader like these: x.12.x or x.9.x .
You will also need ADB & Fastboot and the drivers.
1- Just like in the FIRMWARE section, install drivers and SP Flash Tools.
2- Open SP Flash Tools and load the scatter file and in the line where you see "uboot" on the right click in the blank field and a window will pop up. select the patched bootloader. Make sure it checked and click on the "Download" button.
3- Now plug the male to male USB cable and then plug in the power. SP flash tool will flash the bootloader and then show you a nice little green check mark.
4- At this point you need to unpack the adb folder from the RAR file and place it in the root of you hard drive(C: ) then open a command prompt and nvigate to you adb folder (cd c:\adb) and leave it there for just a second.
5- On your tablet unplug the power wire, hit the reset button in the back and boot it into recovery mode by pressing and holding the volume up and power buttons together until the RCA splash screen comes up then release them.
6- In recovery, use the volume keys to navigate to "reboot to bootloader" and use the power button to select.
7- At this point your tablet will be in fastboot and your computer should detect it and install the driver. If not, the driver is in the "Android" folder in the driver files you extracted.
8- In your command prompt you left opened earlier, type "fastboot oem unlock".
9-Your tablet will do some magic, summon a demon, banish it to the depths of hell, reboot a couple of times and then it will have a unlocked bootloader.
10- Done. now you ca move on the next post and flash recovery.
Bogram also created a tool that patches the bootloader automatically should you have a different version we don't know about or what not...
Code:
RCA LittleKernel Unlock Patcher
By Bogram (http://forum.xda-developers.com/member.php?u=7182821)
Tested models:
RCA Viking Pro (RCT6303W87DK), RCA Maven Pro (RCT6213W87DK)
USE THIS TOOL AT YOUR OWN RISK, NO WARRANTY IS PROVIDED.
License: http://www.gnu.org/licenses/gpl-3.0.html
Input file:
W:/HaxeToolkit/projects/patcher/lk.bin
Wrote to:
W:/HaxeToolkit/projects/patcher/lk_patched.bin
Press any key to exit.
https://drive.google.com/file/d/0Bz4bOoJ_E5XzSnJ2R3d2NkxlU0k/view?usp=sharing
RECOVERY
This section depends on a unlocked bootloader. If you did not unlock your bootloader in the previous post, do so before continuing to this one.
So what you need is a scatter file like this one and a recovery.
CWM + Carliv compiled by vampirefo: (x.9.x)Clockworkmod recovery (x.12.x)Clockworkmod recovery
TWRP V3.00 compiled by Neporood: (x.9.x)TWRP V3.00 recovery (x.12.x)TWRP V3.00 recovery(Coming soon)
- Open SP Flash tool and select the scatter file.
- in the recovery line, on the right side in the blank field, click and select your downloaded recovery.
- Click on the download button.
- Make sure your tablet is off, plug the USB cable first and then the power cable.
- SP Flash tool will flash the recovery and show you a lovely green check mark.
- Once that is done your recovery will be flashed.
** The stock system has a file in the system folder called "recovery-from-boot.p". this file flashes stock recovery randomly at boot so with a rooted system, navigate to the folder with a root capable explorer and delete the file so that your new recovery stays there.
** When rebooting from recovery, cwm will tell you to fix root. Don't. Select no every time.
For thos of you who want a file explorer in recovery, You can download this Aroma installer flashable
It's a nice tool to have...
Aroma comes from here: http://forum.xda-developers.com/showthread.php?t=1646108
ROMS
Not yet but soon.....
I'd swear I've seen all this somewhere before... lol
Good job, brother!
Now , let the roms...begin.....
woot ... just in time as I brought my Viking Pro home from Wallyworld Saturday night.
Any thoughts on ADB? I couldn't make it all the way through the other thread and eventually just gave up.... ended up figuring out Kingroot on my own and then just enabled ADB over wifi. Would much rather have a wired ADB solution as moving an APK (I'm a developer, duh) over wifi can be somewhat s-l-o-w.
Any plans to make a thread like this for the RCA Maven Pro (RCT6213W87DK)? It'd be really swell.
EDIT: Actually, with those sources you posted, I actually might be able to do this on my own.
thevypr said:
Any plans to make a thread like this for the RCA Maven Pro (RCT6213W87DK)? It'd be really swell.
EDIT: Actually, with those sources you posted, I actually might be able to do this on my own.
Click to expand...
Click to collapse
I've got a Maven, and I've already done the porting. I'll be posting a guide tomorrow morning sometime. For now, I've sent you a PM with links to the firmware. Check your firmware version, mine is V36-1.9.21 (as long as you have the "9", you should be ok) The zip file has everything in it, preloader, scatter, custom recovery, etc...
Maven Guide is up, find it here
Synman said:
woot ... just in time as I brought my Viking Pro home from Wallyworld Saturday night.
Any thoughts on ADB? I couldn't make it all the way through the other thread and eventually just gave up.... ended up figuring out Kingroot on my own and then just enabled ADB over wifi. Would much rather have a wired ADB solution as moving an APK (I'm a developer, duh) over wifi can be somewhat s-l-o-w.
Click to expand...
Click to collapse
Still working on adb... Trying to make a flashable ROM with the fixes... No timeframe tho..
smartmanvartan said:
Still working on adb... Trying to make a flashable ROM with the fixes... No timeframe tho..
Click to expand...
Click to collapse
I can't get the port(s) to light up under OSX. I've tried a couple build.prop changes, plugging in micro usb, usb type a, power connector, and various combinations but none of them appear to trigger registration of a usb device of any kind on the host machine.
I can't even get simple stuff like MTP to work.
Synman said:
I can't get the port(s) to light up under OSX. I've tried a couple build.prop changes, plugging in micro usb, usb type a, power connector, and various combinations but none of them appear to trigger registration of a usb device of any kind on the host machine.
I can't even get simple stuff like MTP to work.
Click to expand...
Click to collapse
Time is my issue but I'm looking at two things. there is a firmware package i found on the Chinese server for a tablet with the model number rct6603w47dk with the same board as the viking pro but with a 8163 instead of the 8127. i think its doable to port over to our tablet. it is android 6. also the maven pro(rct6213w87dk) which is really close to our tablet with the same board but a larger screen, has adb working on it...
You should be getting a reaction through the micro usb port... on windows it shows up as a malfunctioning device.
i get nothing when sniffing the USB bus on my MBP.
Synman said:
i get nothing when sniffing the USB bus on my MBP.
Click to expand...
Click to collapse
I does the same thing on Ubuntu 14.04, absolutely nothing shows with "lsusb" in the terminal, unless it's in fastboot mode. You can use fastboot to flash the device, if you don't have access to a Windows machine...
I tested the new 1.9.3 firmware on my tablet... and it just shows a black screen.
DO NOT FLASH IT. it didn't work
Jacube22 said:
I tested the new 1.9.3 firmware on my tablet... and it just shows a black screen.
DO NOT FLASH IT. it didn't work
Click to expand...
Click to collapse
Ill find you guys some newer software that boots...
What's the difference between sp_drive_v2.0_finally & mtk_sp_drivers_v2.0
Because I got the sp_drive install but having a problem with the mtk_sp , it keep popping up as incompatible software.... I'm stuck on the boot loader section
e923 said:
What's the difference between sp_drive_v2.0_finally & mtk_sp_drivers_v2.0
Because I got the sp_drive install but having a problem with the mtk_sp , it keep popping up as incompatible software.... I'm stuck on the boot loader section
Click to expand...
Click to collapse
What version of Windows are you running..the difference is the drivers are signed or unsigned.. This matters more on newer versions of Windows.
This Guide Tells You How To Update Your Lenovo Vibe X3 (X3a40 Variant) To The Latest Marshmallow Firmware
Warning
If This Bricks Your Phone I Am Not Responsible Although It Is Very Safe But If You Do Anything Stupid It May Brick The Phone If This Happens Repeat All The Steps Again Without Messing Up It Should Fix The Phone
List Of Things Required For Updating Your DeviceDrivers + QFIL - https://drive.google.com/folderview?id=0B5QzQ51ejd3rLWREYmNjWjNwV1U&usp=sharing
Lenovo Vibe X3 Marshmallow Firmware - https://drive.google.com/file/d/0B6fGoFSBPp8QcWtaUlcwVTMxMHc/view?usp=sharing
Lets Begin
Flashing Guide
WARNING: Everything apart from data in external SD card will be wiped. Make sure to backup everything.
1.Download the QFIL flash package ZIP and appropriate ZIP from Drivers+QFIL.
2.Extract the ZIPs to a folder whose complete path has no spaces (space characters) at all.
3.Make sure you uninstall any other phone's PC Suite/drivers as they may cause conflicts. Microsoft Emergency Driver (installed for restoring Lumia devices) is known to conflict, please uninstall it.
4.Go to Drivers+QFIL folder extracted in Step 2, run the appropriate 'INSTALL_DRIVERS_&_QFIL.bat' and follow the instructions.
5.Backup contacts, SMS, apps, etc. as well as the entire internal storage as they will all be wiped(you will setup a new phone). Internal storage WILL BE erased when using the QFIL flash method.
6.Run 'QFIL' program. (If Unable To Find It Search It In Start Menu You Will Find It There)
7.Select 'Flat Build' as build type.
8.Click on 'Browse', select the 'prog_emmc_firehose_8992.mbn' file from the 'X3a40_S217_160623_ROW_QFIL' folder which you extracted.
9.Click on 'Load XML' and select 'rawprogram0.xml' followed by 'patch0.xml'.
10.Make sure you completed each step precisely, the USB cable is connected ONLY to USB port (USB 2.0 preferably) of PC and not to device yet, the device is powered off and is charged (at least 40%).
11.Now boot into EDL by plugging in the USB cable to device and quickly pressing and holding power button for ~1 second. QFIL's 'No port available' text should change to 'Qualcomm HS-USB QDLoader 9008 (COMXX)'. The display will stay off so, don't worry about it.
12.Within ~5 seconds put the device on a stable surface (so that it doesn't move around or shake) and press the 'Download' button on QFIL. If you are late, the device starts to power on normally and you need to go back to Step 11 and continue.
13.Wait for the flash to complete and 'Download Succeeded' message appear at the bottom.
14.Unplug the USB cable from the device and press and hold the power button for ~10 seconds to power it off.
15.Now power on the device normally. If display doesn't turn on press and hold the power button again for longer time, it will boot.
16.Once you have finished the initial set up, open dialer, dial '####682#', choose your region (IN - For India) and confirm. [Don't Skip This Step Its Important]
NOTE - IF Having Trouble In Installing The Drivers Or Detecting The Phone In QFIL Google On How To Disable Signature Enforcement In Windows 8 or 8.1 or 10 And After Doing That Again Install The Drivers.
HIT Thanks Button If I Helped You It Will Keep Me Motivated In Helping Others
TIPS & INFORMATIONThe various modes X3a40 can boot into:
Recovery mode: Press and hold Volume up + Volume down + Power together until Lenovo logo shows up and flickers once. Release the buttons and you will reach the recovery. This opens up the recovery of the device.
Qualcomm Diagnostics mode: Press and hold Volume down + Power button together until Lenovo logo shows up and flickers once to boot into this mode. This opens up the Qualcomm Diagnostics screen which has a number of hardware testing and other tools along with ability to flash the stock ROM. It is also used for further Diagnosis using a PC.
Fastboot mode: Press and hold Volume up + Volume down and plug in the USB cable(already connected to PC). You may also use the ADB command "adb reboot bootloader". Obviously you need a working device with USB Debugging turned on and ADB installed on PC. This opens the traditional Fastboot interface.
EDL mode: Plug the USB cable and quickly press and hold the power button for a little while. Device stays in EDL only for ~5 seconds unless you start firmware flash via QFIL. You can also use ADB command "adb reboot edl". This will put your device in Qualcomm Emergency Download Mode which is meant to flash stock firmware using QFIL tool on working/bricked devices.
Normal mode: This is what you boot by normally pressing the power button. I don't need to say much about this one.
Keep your NV data (IMEI, Serial No., etc.) backed up from QFIL>Tools>QCN Backup Restore. Device must be in Qualcomm Diagnostics mode. There are many more ways to do this.
#Note- If Any Of The Link Goes Down Inform Me I'll Bring The Up As soon as Possible.
Will just flashing the SuperSU zip enable me to get root in Marshmallow rom?
Or should I do everything from this thread again to gain root? I already have root in my lollipop and want to update to Marshmallow only if I can get root in it.
This is stolen from this existing thread:
http://forum.xda-developers.com/android/development/rom-lenovo-vibe-x3-row-x3a40-stock-t3328461
Thread closed.
Hello, y'all,
... First of all, please read this whole post carefully, before starting to work on your phone! Thanks! ...
recently, I wanted to update the Android version of my old Z500 with the help of lineageOS and TWRP.
Please note, that I'm not at all an expert on this topic, and if I'm using specific terms like "bricked" or "APX mode" wrong, please forgive me.
So, on my device, I had the plan of installing Android 6.0 on this phone using TWRP and a copy of lineageOS.
However, the recovery partition turned out locked and I accidentally overwrote the boot partition with the twrp.img.
This is my first time doing this, ok, and I read on a oneplus forum, that the boot partition could also be used, blah, blah, blah, silly me.
Anyways, now my device wouldn't turn on. After a while charging, the display turned on, but there was always just the low battery screen. When I got to the "Boot Selector" holding the power and vol + button, selecting fastboot, recovery or normal boot just restarted the device.
Anyways, now what do you need to "unbrick" the device :
- A version of TWRP [dl.twrp.me/Z500/twrp-3.3.1-0-Z500.img.html]
- A version of your desired ROM, for me lineageOS [androidfilehost.com/?fid=889764386195903470]
- SmartPhone Flash Tool, for me v5.1912 worked like a charm [spflashtool.com/download/SP_Flash_Tool_v5.1912_Win.zip]
- A copy of the Firmware Acer_AV0K0_Z500_1.012.00_EMEA_GEN1 (... GEN1s for single SIM) [dl.dropboxusercontent.com/s/cin08ytkqmvr7c1/Acer_AV0K0_Z500_1.012.00_EMEA_GEN1.zip] (this was the hardest one to get because all the other downloads just included the .ispff dump file)
- A copy of the corresponding version of OpenGApps [opengapps.com]
- A copy of the MediaTek Driver Auto Installer (v5.1632.00; you know you have the right one when it resets the USB Ports in a CMD window at the end; INSTALL THIS FIRST) [mediafire.com/file/4ux1ytmzlxmpbjb/ROMProvider.COM_Driver_Auto_Installer_EXE_v5.1632.00.zip/file]
- A USB Charging Cable
- A PC
- Your Phone, obviously
Set up your PC :
1. Start by installing the MediaTek Driver Auto Installer. After that is finished, restart your PC.
2. Unzip the Firmware and the SmartPhone Flash Tool
3. Copy your ROM and OpenGApps on an SD Card.
Before you begin this operation, make sure you "get your device into APX mode".
Basically, it makes your device recognizable and flashable by the computer.
WARNING: DO THIS AT YOUR OWN RISK.
To do that follow these steps one after another :
- Plug your device into your wall power, NOT YOUR PC, and let it charge for about 30min, just in case. Turn it off if it's still on, although in my case, it turned off once I removed the charging cable.
- Remove the backplate of your device, unscrew the internal backplates 6 screws and carefully take the internal backplate off. If you're having trouble, just look for "Acer Z500 teardown" on YouTube.
- Carefully pull off the battery connector from the mainboard from up under. Be careful not to damage it!
- Once done, connect your device to your computer. You should now see the device as COM Connector in the Device Manager. If your device is disconnecting and connecting repeatedly, the driver must not be active. If you see no device connecting at all, remove it from your computer and after plugging it into the wall charger again, reconnect it to your PC.
- Once that's ok, disconnect the device again, and plug the battery back in.
- While disconnected, open up the SP Flash Tool, and under "Download", select the scatter .... .txt file from the Firmware Archive.
- Once that's done, all of the checkboxes in the ROM select should be active.
- Double Click on the Path of the "RECOVERY" row and select the TWRP.img. Then, change the mode from "Download only" to "Format All + Download" and hit the "Download" button.
- Plug your Z500 back in again, and you should see the flashing process starting.
- Once that's done, disconnect the phone and put the SD card with your ROM and OpenGApps in.
- Connect your phone to the wall charger again, and immediately hold the power and the vol + buttons down, till the Boot Options appear.
- Boot into recovery mode, and TWRP should start up. If it doesn't, reconnect your phone again and just let it boot for around 3min after terminating it by holding the power button and as soon as the screen goes black, also holding the vol + button. Once again select recovery mode, and now TWRP should defiantly show up.
- In TWRP, first, make a factory reset with the "WIPE" option. Then go to install and choose your SD card. First, install your ROM, then OpenGApps and reboot.
Now you should have a functioning Acer Z500 again!
Feel free to reply, if you have any questions!
Good luck,
Klydra.