[GUIDE] How To Root Lollipop 5.0 Dell Venue 8 7000/7840 - Dell Venue

So I was poking around all over and there really isn't a good guide on how to Root the Dell 7840 after the Lollipop update. So I figured i would make one so others don't have to piece together info like i did.
NOTE: Dell just released LL 5.1 to the 7840!!! You can root it using xBIGREDDx's method here http://forum.xda-developers.com/showpost.php?p=62013578&postcount=43
You can use this guide for social-design-concept's method that xBIGREDDx mentions in his new method! PLEASE SHOOT HIM A THANKS!!!!
Before we start:
A. the info in this article is collected from several other users hard work I am just trying to make the process simple i would like to thank the developers/testors that have gotten us this far
Especially social-design-concepts and his work here:
http://forum.xda-developers.com/showthread.php?t=2975096
Please shoot him a thanks! We owe him for the mad skill!
B. If your device gets bricked for some strange reason or overheats and burns your house down again, for some strange reason. I TAKE NO RESPONSIBILITY, DO THIS AT YOUR OWN RISK.
So to start, download this:
https://www.androidfilehost.com/?fid=23991606952604606
And this:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
And this:
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Install the Intel Android Drivers first, worked fine for me on Windows 10, should work fine on 8 and 7.
Plug your 7840 into your computer and do three things:
1. COPY the UPDATE-SuperSU-v2.46.zip to your devices EXTERNAL SD CARD not the internal memory!!!
2. Enable USB Debugging after enabling debug mode (tap the Build Number under About Tablet til it says your a developer)
3. Disable MTP mode by going into the Storage setting menu option clicking the options button at the top right and unchecking MTP
Extract the IntelAndroid-FBRL-05-16-2015-PTR archive to your desktop (or where ever you want to open it from)
Open the folder and run the Launcher.bat file
Everything should be installed correctly as long as the Intel Drivers installed properly.
It will bring you to this screen:
{
"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"
}
Just type T4 and hit enter
Your device should reboot to this screen:
This is where it gets tricky, if you go into the device manager on your computer you should see this:
You will need to right click it and click Update Driver Software
Then click this:
Then this:
Select the one in the list that says this:
Then select the one that says Intel Android Bootloader Interface:
It should install properly, close all the windows and if you go back to your command prompt (the thing you typed T4 into and hit enter) you will notice it is already copying stuff:
When its done you will see it setting up the temporary recovery, looks like this:
Your device will boot into Clockwork Mod Recovery using the Up and Down Volume buttons and the Power button to select, select "Install Zip"
Then "Choose Zip from External SdCard"
Select the SuperSu Zip you put on here earlier
When it gets done go back to the first menu and select "Reboot System Now"
it will ask if you want to "Fix Root"
select yes
When you get into Android you will need to install Busybox for root to work:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
And you should be rooted!! Worked for me no hiccups. I'm definitely no programming wiz but I'll try to help if something isn't working.

BTW just tested after rooting and Xposed and GravityBox both work just fine.... Thank you Dell for making this thing mostly AOSP

You may want to credit some folks in your original post, for example (at a minimum) link to the place where you got the androidfilehost link, and mention the developers who created the tool.

Chyrio said:
So I was poking around all over and there really isn't a good guide on how to Root the Dell 7840 after the Lollipop update. So I figured i would make one so others don't have to piece together info like i did.
Before we start:
A. the info in this article is collected from several other users hard work I am just trying to make the process simple i would like to thank the developers/testors that have gotten us this far
B. If your device gets bricked for some strange reason or overheats and burns your house down again, for some strange reason. I TAKE NO RESPONSIBILITY, DO THIS AT YOUR OWN RISK.
So to start, download this:
https://www.androidfilehost.com/?fid=23991606952604606
And this:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
And this:
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Install the Intel Android Drivers first, worked fine for me on Windows 10, should work fine on 8 and 7.
Plug your 7840 into your computer and do three things:
1. COPY the UPDATE-SuperSU-v2.46.zip to your devices EXTERNAL SD CARD not the internal memory!!!
2. Enable USB Debugging after enabling debug mode (tap the Build Number under About Tablet til it says your a developer)
3. Disable MTP mode by going into the Storage setting menu option clicking the options button at the top right and unchecking MTP
Extract the IntelAndroid-FBRL-05-16-2015-PTR archive to your desktop (or where ever you want to open it from)
Open the folder and run the Launcher.bat file
Everything should be installed correctly as long as the Intel Drivers installed properly.
It will bring you to this screen:
Just type T4 and hit enter
Your device should reboot to this screen:
This is where it gets tricky, if you go into the device manager on your computer you should see this:
You will need to right click it and click Update Driver Software
Then click this:
Then this:
Select the one in the list that says this:
Then select the one that says Intel Android Bootloader Interface:
It should install properly, close all the windows and if you go back to your command prompt (the thing you typed T4 into and hit enter) you will notice it is already copying stuff:
When its done you will see it setting up the temporary recovery, looks like this:
Your device will boot into Clockwork Mod Recovery using the Up and Down Volume buttons and the Power button to select, select "Install Zip"
Then "Choose Zip from External SdCard"
Select the SuperSu Zip you put on here earlier
When it gets done go back to the first menu and select "Reboot System Now"
it will ask if you want to "Fix Root"
select yes
When you get into Android you will need to install Busybox for root to work:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
And you should be rooted!! Worked for me no hiccups. I'm definitely no programming wiz but I'll try to help if something isn't working.
Click to expand...
Click to collapse
Please update your post

social-design-concepts said:
Please update your post
Click to expand...
Click to collapse
Updated, sorry man I had to run out the door right as I finished the post didn't look over the thing well enough. Please let me know if I missed someone else, I'll add them in there!
Sent from my Venue 8 7840 using Tapatalk

Chyrio said:
BTW just tested after rooting and Xposed and GravityBox both work just fine.... Thank you Dell for making this thing mostly AOSP
Click to expand...
Click to collapse
How do you install xposed?

Flash the zip for the x86 based device located here http://forum.xda-developers.com/showthread.php?t=3034811 in social-design-concepts recovery, reboot and install the apk in that forum as well.
Sent from my Venue 8 7840 using Tapatalk

I just got this tablet yesterday and updated to Lollipop (it arrived with Kitkat still loaded) and then headed over to the forum to find out it was a 5.1 update that had just came out!
Saw this thread, got really happy, and now I'm bummed to hear people are having a little trouble getting rooted on 5.1. Chyrio, I'm really new at this but I've rooted a Galaxy S4 and a Oneplus One by unlocking and flashing TWRP and installing custom roms from there. I don't know anything about the Intel architecture at all, how does this differ in terms of unlocking and rooting?

3itmn said:
I just got this tablet yesterday and updated to Lollipop (it arrived with Kitkat still loaded) and then headed over to the forum to find out it was a 5.1 update that had just came out!
Saw this thread, got really happy, and now I'm bummed to hear people are having a little trouble getting rooted on 5.1. Chyrio, I'm really new at this but I've rooted a Galaxy S4 and a Oneplus One by unlocking and flashing TWRP and installing custom roms from there. I don't know anything about the Intel architecture at all, how does this differ in terms of unlocking and rooting?
Click to expand...
Click to collapse
I'm kinda new to it as well, but as far as I can tell, there isn't to much of a difference with how the android file structure is built. The hardware is different (obviously) creating the need for different drivers and new software. I know there is some kind of emulator for ARM architecture based apps in the OS itself but Recoveries and bootloader exploits are going to require redesign from the standard ways. Which social-design-concepts is hard at work on. Hopefully he can cook up something for us soon. I'm holding off on the 5.1 update for now waiting for the devs to work their magic.
Sent from my Venue 8 7840 using Tapatalk

Any root method for Mac osx or linux?

NEED HELP!
when launching "launcher.bat, its giving me a message that states "the device can not work in this locked state"
not sure what is locking it from advancing. no passcode, debugging is on
Any suggestions would be greatly appreciated?
---------- Post added at 11:17 PM ---------- Previous post was at 10:48 PM ----------
testastrettaR6 said:
NEED HELP!
when launching "launcher.bat, its giving me a message that states "the device can not work in this locked state"
not sure what is locking it from advancing. no passcode, debugging is on
Any suggestions would be greatly appreciated?
Click to expand...
Click to collapse
the launcher shows:
Device Status: FASTBOOT - ONLINE
Why is this differ than the screen shots? could this be the reason why it can not get past this stage?

Same here... Device state: Locked.
Have you solved your problem?
Anyone had the same issue?
UPDATE: Bootloader unlocked. Device State: Unlocked. But know when I try to insert T4 it copies the files and on the tablet is says "Okay." The cmw does not open. Please help!
testastrettaR6 said:
NEED HELP!
when launching "launcher.bat, its giving me a message that states "the device can not work in this locked state"
not sure what is locking it from advancing. no passcode, debugging is on
Any suggestions would be greatly appreciated?
---------- Post added at 11:17 PM ---------- Previous post was at 10:48 PM ----------
the launcher shows:
Device Status: FASTBOOT - ONLINE
Why is this differ than the screen shots? could this be the reason why it can not get past this stage?
Click to expand...
Click to collapse

Related

Asus Zenfone C bootloop

I tried to flash latest rom from Asus website to my new Zenfone C because it had a weird issue, it came the user interface in taiwanesse, but when trying to change to english, it stayed in taiwanesse, so I wasnt able to setup it in first place.
Then, it came to my mind to flash the latest rom, and I used this guide in absence of a Zenfone C guide for flashing:
http://en.zenfoneasus.com/zenfone-recovering-returning-stock-rom-downgrade-clean-update-guide/
I did all the steps listed there first, and then tried the steps but with the red marked steps, flashing the dnx and ifwi also, no result.
The problem is that now im stuck in a bootloop, and cant advance from there, the Asus logo stays there forever.
What happened during flashing is this:
When I sideloaded the update.zip containing latest rom from Asus website, it said:
-Installing update
-Device image SKU: ww
OTA image SKU: WW
and suddenly after that it restarted, showed a huge Intel Inside logo that I never saw and then went to the dead android image. After waiting a while, the phone restarts, this time only showing the Asus logo with the Intel Inside logo beneath it (not the Intel Inside logo only that I mentioned earlier), and stays there forever.
I dont know what else to do, I dont know if Im doing something wrong.
Were you ever able to fix the problem?
No, until now, no
Sent from my Nexus 5 using Tapatalk
Solved!!!
Hey Spartan!
I was searching online about nexus 5 to buy one but I found something else randomly in an Indonesian blog and was able fix my phone! Hardly took about 15 minutes
I will be posting the solution soon... I hope you are still in need?
kkdevta said:
Hey Spartan!
I was searching online about nexus 5 to buy one but I found something else randomly in an Indonesian blog and was able fix my phone! Hardly took about 15 minutes
I will be posting the solution soon... I hope you are still in need?
Click to expand...
Click to collapse
I still need the fix man, I will really appreciate the posting of the solution! thanks in advance!
Sent from my Nexus 5 using Tapatalk
The Fix!
First Download: -
USB Drivers: http://www.asus.com/in/Phones/ZenFone_C_ZC451CG/HelpDesk_Download/
Asus Flash Tool v1.0.0.11: https://drive.google.com/file/d/0B7cZB2l2IKlKMENKUWlVaHJ3ZHM/view
Signed Rom zip image: https://drive.google.com/file/d/0B__oiYlSY-brdHFWMy1OWXNrajg/view
The Process: -
Get your phone to boot into fastboot mode by pressing [vol -] button and power button simultaneously for few seconds.
Connect to your PC and install USB drivers if not done already. The phone should show up as an "ASUS Android Composite ADB Interface" in the Device Manager.
Now, open ASUS Flash Tool :-
{
"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"
}
It should detect your phone with serial number and blue orb in front of it.
Select your phone model i.e. ZC451CG
Choose if you want to wipe data or not. I chose "Wipe Data" since I had everything backedup on asus web storage.
Click that box icon and browse for the signed zip image file you downloaded earlier.
Select your device on the ASUS flash Tool by clicking on the serial number like shown in the picture below.
( It had me scratch my head after one failed attempt because I didn't select it the first time! :silly
Click on the green start button, be patient, stay calm and cross your fingers. This could take 10-20minutes or so.:fingers-crossed:
If everything went well your phone should bootup to the welcome screen like the day 1 you got it.
Now, the zip image is quite old so after the initial setup the phone would prompt you with lots of system and app updates. Go with it and enjoy! :victory:
Lastly, don't be shy of pressing that " :good:Thanks! " button if this post helped you.
Thanks man, I will try tonight. Do you know if this works under Windows 8.1 64bits??. I see the screenshots are from windows 7.
Spartan Legionnaire said:
Thanks man, I will try tonight. Do you know if this works under Windows 8.1 64bits??. I see the screenshots are from windows 7.
Click to expand...
Click to collapse
Hopefully it should, I did it on a Windows 7 Professional 64 bit machine.
The USB drivers you download has Windows 8 drivers in it. I think that's all that is needed.
Yeah, I will try it then, and report back, thanks again.
Sent from my Nexus 5 using Tapatalk
kkdevta said:
First Download: -
USB Drivers: http://www.asus.com/in/Phones/ZenFone_C_ZC451CG/HelpDesk_Download/
Asus Flash Tool v1.0.0.11: https://drive.google.com/file/d/0B7cZB2l2IKlKMENKUWlVaHJ3ZHM/view
Signed Rom zip image: https://drive.google.com/file/d/0B__oiYlSY-brdHFWMy1OWXNrajg/view
The Process: -
Get your phone to boot into fastboot mode by pressing [vol -] button and power button simultaneously for few seconds.
Connect to your PC and install USB drivers if not done already. The phone should show up as an "ASUS Android Composite ADB Interface" in the Device Manager.
Now, open ASUS Flash Tool :-
It should detect your phone with serial number and blue orb in front of it.
Select your phone model i.e. ZC451CG
Choose if you want to wipe data or not. I chose "Wipe Data" since I had everything backedup on asus web storage.
Click that box icon and browse for the signed zip image file you downloaded earlier.
Select your device on the ASUS flash Tool by clicking on the serial number like shown in the picture below.
( It had me scratch my head after one failed attempt because I didn't select it the first time! :silly
Click on the green start button, be patient, stay calm and cross your fingers. This could take 10-20minutes or so.:fingers-crossed:
If everything went well your phone should bootup to the welcome screen like the day 1 you got it.
Now, the zip image is quite old so after the initial setup the phone would prompt you with lots of system and app updates. Go with it and enjoy! :victory:
Lastly, don't be shy of pressing that " :good:Thanks! " button if this post helped you.
Click to expand...
Click to collapse
IT WORKEEEED!!!! I dont know how to thank you man!. Thank you so much, I was going to give up on this device!. Its working really well.
The only thing I came into trouble, was to install the USB drivers included in the Asus Flash Tool. I did the following (on Windows 8.1 64bits):
I disabled driver signature check first on windows.
I went to the USB drivers folder inside the ASUS Flash tool folder on Program Files.
I went here C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller\devcon\x64
On that folder, there is a program called devcon.exe, right click on it, and select properties.
On compatibility tab select Run as Administrator, click ok.
After this, reinstall USB drivers by going to C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller and here execute install_drivers.bat
Thats it, the phone now should be recognized by the Asus Flash Tool.
I always failed when downloading Signed Rom zip image.. Someone please provide mirror... Thanks
Tjecing said:
I always failed when downloading Signed Rom zip image.. Someone please provide mirror... Thanks
Click to expand...
Click to collapse
Use a download manager like "free download manager" or something. I am on a slow network to re-upload it else where.
kkdevta said:
Use a download manager like "free download manager" or something. I am on a slow network to re-upload it else where.
Click to expand...
Click to collapse
I don't know how to thank You.. But thanks a lot you safe my days..
Can any one plz give me the link of any custom recovery for asus zenfone c.....i badly need it plz help me...thnks in advance.....plz give me..and tell me how to flash it.....
do you know where i can find the correct .raw file for asus zenfone 5 A501CG ? i use lollipop, i dont know if that's matter =s
Anyone help me When I press volume- and power, it can't enter to fastboot. And when I plug the cable, the flash tool can't detect it
Sent from my Mi 4i using XDA Free mobile app
hello brother...can you help me...
my zenfone 5 a500cg has been softrick and bootloop to...
if i'm turn on my phone
logo asus and then usb logo and then dead again...
i can't log into fastboot(power on+vol up)..
but i can log into cwm philz...
i try flash via adb sideload but always error bla bla bla tmp/updated.zip
if i try other ROM always like this ( please upgrade to image 4.3 first)
i try xftsk but always windriver error( i am use notebook win7)
i try asus flashtool with .raw zip rom but my serial number error just 12345678abcdef...
if i click start always device not detect...
help me bro
disappear3896 said:
Anyone help me When I press volume- and power, it can't enter to fastboot. And when I plug the cable, the flash tool can't detect it
Click to expand...
Click to collapse
power and volume up (+)
Spartan Legionnaire said:
IT WORKEEEED!!!! I dont know how to thank you man!. Thank you so much, I was going to give up on this device!. Its working really well.
The only thing I came into trouble, was to install the USB drivers included in the Asus Flash Tool. I did the following (on Windows 8.1 64bits):
I disabled driver signature check first on windows.
I went to the USB drivers folder inside the ASUS Flash tool folder on Program Files.
I went here C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller\devcon\x64
On that folder, there is a program called devcon.exe, right click on it, and select properties.
On compatibility tab select Run as Administrator, click ok.
After this, reinstall USB drivers by going to C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller and here execute install_drivers.bat
Thats it, the phone now should be recognized by the Asus Flash Tool.
Click to expand...
Click to collapse
First and foremost, follow Spartan about how to deal with the driver install error. Read above. Second, those are the links for the raw images:
ww_A500CG_3.23.40.60_20150630.raw and many other phones. It was posted by thanhthuy. 500CG Lollipop: https://mega.nz/#!jwBDUKzJ!x3VD9VJrMe0CBs353DVnXlHr2dHQXepjcqtrR0gQDdU
500CG kitkat:
https://mega.co.nz/#!H8YkyLba!4Ye52JKAjzogGRVvCx2r9XoJIhou_uY3z6YH1xBges8
400CG 6.6.3 - https://mega.co.nz/#!HoRRnLCL!CV-iCMEUgRd_LwDc4QgNkevxKIGOKtFGDYrytt59EVE
400CG 7.3.3 - https://mega.co.nz/#!G8hRwYqR!Eu_l6r_6QSbhjID-MtYQU3v0q0voQ0GYkFeayy-3MFI
451CG: https://mega.co.nz/#!794U1TpT!rermqclZOpPKcYZY8z2YezUkQE-MWjYJgqyKMUAjYDo
600cg Kitkat: https://mega.co.nz/#!S1wlnYhC!doCPvf7ukeEFStcJPgqaEViE5oiHb_hpGSGnIh3n1IQ
Here for 600cg lollipop: https://mega.co.nz/#!3p4wBQAY!KUx26zaGdCBU6CGa4g68zT_iX9NxmIQCUvHiolfa_Oo
ZE550ML Lollipop 40.23 : https://mega.co.nz/#!HgBSySZA!EOxpsmPvHgCfl-9jUVRAv624Uq9LG4uvxuN83j6-P-k
ZE550ML Lollipop 40.40: https://mega.co.nz/#!P4RmXIwb!-xrDe8AYXdprZgUG4Ehs8fLNHhrdKpXdmaV3FBWPC_0
ZE551ML Lollipop: https://mega.co.nz/#!i4JRAQDR!9DzxtSd1oxDuCV6oc0rEhm-1sF4SA-94YPG9fLVw_lw
Source using Google cache (Vietnamese): http://webcache.googleusercontent.com/search?q=cache:w5AS-N1JrAoJ:zenphoneviet.com/threads/all-zen-stock-rom-firmware-kk-l-update-hang-tuan-chay-bang-asus-flash-tool.7066/+&cd=1
---------- Post added at 07:31 AM ---------- Previous post was at 07:29 AM ----------
Those raw files are extremely difficult to find so if you pretend to have any of those phones i recommend to download. It works easily if you have fastboot. If you only have adb i did not saw working but i am trying.
---------- Post added at 07:38 AM ---------- Previous post was at 07:31 AM ----------
If you try to do that under adb they give a serial number mistake.
4 days trying to solve this bootloop using adb. At least one person here saved his phone with the raw links i found using google webcache in this vietnamese link so it was worth it. Looks like i will need to lose 40 days sending to Asus in Sao Paulo. What a hell folks, those asus firmwares are really crap. Set a great hardware for set poor software.
why my phone does not give any reaction when press power button+vol
I had same problem but different situation....I tried to make an experiment by changing systemui and I had done it with a wrong step .lucky I make a backup and tried to recover it.
But Things get worst when it failed to backupbang now my phone get stuck to Asus logo.I tried to follow the method that your all give in this thread but I can go to fastbootode with it must press power button+col down button.
CAN ANYBODY HELP ME WITH THIS PROBLEM
Sorry for my bad English
And I'm a newbie and try to learn something from pro

Easiest [GUIDE] to ROOT Dell Venue 8 Tablet 3840 and 7840

Easiest [GUIDE] for Newbies to
ROOT Dell Venue 8 Tablet 3840 and 7840
with Android 4.4.4
TETHERED CWM METHOD​ ** Disclaimer: This is not my work. I have just consolidated all information and files together into one simple STEP BY STEP GUIDE.
** Do at your own Risk. I am not responsible if you mess up your tablet. The method works perfectly on my 3840 and a fb friend 7840 without any issues and should work for everyone.
** This may work for some other Intel Chipset devices/tablets too. Inform me if it works for your model
** ALL THE CREDIT GOES TO AMAZING DEVELOPER @social-design-concepts Thanks pal
=====================================================================
Visit and read this thread by @social-design-concepts Please read carefully once before proceeding. You dont need to download anything from this thread. Download everything from this thread only.
WHAT IS TETHERED CWM?
Remember this is called "TETHERED CWM" method. Tethered means wired. Everytime when you want to use Recovery Mode, you need to use this tool by connecting tablet to pc, which copies recovery files "temporarily" in Tablet Memory and then you can use this temporary Custom CWM Recovery to do the Recovery tasks. When you reboot phone back to normal the CWM is removed from memory and you are back on that useless stock recovery. YES, its temporary and everytime you want to use Custom CWM, you need to use this tool. Quiet Annoying but hey, some things in life are bit difficult and you have to stay with it.
Preparations
==========
1) You must take full backup of your data in phone in sdcard or internal memory. No cry and complain later if you lose data.
2) Run Software Update (twice or more times) so you will be on latest Android 4.4.4 and there will be no update shown after that. I did exactly same.
3) Your PC must be installed with ADB and Fastboot Drivers already. You can Download Driver HERE or HERE or find it on Dell / Intel Driver Website.
* Drivers can be easily installed and tool can work on any Windows Version. I did this on Windows 8.1 64 Bit Version without any issues. PIECE OF CAKE. If you have any problem installing then check FAQ section below.
You must connect Phone to PC to test, so windows will finish installing drivers after detection of phone. (recommended)
4) Now on Tablet Open >>> Settings >>> About Tablet >>> Press "Build Number" several times to enable "Developers Options" in Settings. Now go back and again Open >>> Settings >>> Developers Options >>> Enable "Debugging Mode"
5) Download THIS TETHERED CWM/TWRP FLASHING TOOL and copy and extract on any disk in your PC, but not on DESKTOP or C drive. I mean copy and extract anywhere on D or E or F drive onwards but not on C drive, to avoid permission issues of Windows 8.1
6) Download UPDATE-SuperSU-v2.46.zip (3.83 MB) and copy, as it is, on EXTERNAL SDCARD (recommended) or Internal Memory (not recommended). This exact file works for me and everyone. *Do not change it with other versions.
Now you are totally ready to ROOT.
LETS START.....
STEPS OF ROOTING
===================
Step1) Switch on Table/Phone Normally and connect to PC with USB cable. If it is first time, then PC will install ADB Drivers automatically.
Step2) Open folder on your PC where you extracted files of ROOTing Tool. Select "launcher.bat" and RUN AS ADMINISTRATOR. It will open Command Prompt Box with a Tool Menu as shown below.
Step3) The tool menu will ask you to ACCEPT the terms, where you need to type "ACCEPT" in capital letters and press enter key to proceed
{
"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"
}
Step4) After ACCEPTing terms, on next menu, type "5" to select "CWM" as Recovery to load.
*Do not select TWRP right now as there could be some confusion later in this guide.
Step5) Now check that the tool running on command prompt box on PC is reporting as either :
DEVICE STATUS: ADB-ONLINE
DEVICE STATUS: FASTBOOT-ONLINE
*If device status is "Unknown" You may need to carefully start again from beginning.
Now tool will be showing you three TRIGGER options to root. You need to type "T3" and start third trigger.
Tablet will immediately boot into "FASTBOOT" mode (DroidBoot mode). If it is first time, then PC will install Fastboot drivers to recognize device and in FASTBOOT mode, tool will copy TETHERED CWM on tablet and will show lots of text flowing on tablet screen and on PC too.
*Ignore error on last line in above image, its normal.
When done, phone will show you Fastboot menu. Now remove cable from tablet.
Step6) On Fastboot Menu, you need to press volume up or down to select "RECOVERY" option and press <Power> key to start phone in NEW CWM RECOVERY MODE. This time you will see completely different CWM "Vampirefo Venue8 Ver 6.0.3.7" with grey color background and with more working features of CWM.
Step7) Now select "Install Zip from SDCard" and select and flash "UPDATE-SuperSU-v2.46.zip" file.
YOU HAVE ROOTED YOUR TABLET DELL VENUE 8 LTE 3840 MERRIFIELD (India Version) or 7840.
Good Luck guys
Frequently Asked Questions
=================================
1) How to install Fastboot/Bootloader/ADB/Android USB drivers,etc in Windows 8/8.1/10?
Answer: Most Important Info: Many pals here get stuck while installing drivers in Win8+(32/64bit), especially FASTBOOT and BOOTLOADER MODE drivers. These drivers are not Digitally signed, hence Windows8/8.1 does not allow them to install as its standard feature. May be they did it for extended security of windows. So NO PROBLEMO!!! In such case, you can DISABLE DRIVER SIGNATURE ENFORCEMENT feature in simple steps as shown in this video. After these steps when PC starts you will find no difference but then drivers will start installing "obediently" like they did install in XP
https://www.youtube.com/watch?v=gmw86KplqmU
2) WHAT IS TETHERED CWM?
Answer: Remember, this is called "TETHERED CWM" method. Tethered means wired. Everytime when you want to use Recovery Mode, you need to use this tool by connecting tablet to pc, which copies recovery files "temporarily" in Tablet Memory and then you can use this temporary Custom CWM Recovery to do the Recovery tasks. When you reboot phone back to normal the CWM is removed from memory and you are back on that useless stock recovery. YES, its temporary and everytime you want to use Custom CWM, you need to use this tool. Quiet Annoying but hey, some things in life are bit difficult and you have to stay with it.
Post reserved for more Screenshots.
Help with Windows 10
Hi cmahendra,
Thanks for your sharing, I'm facing a problem with installing the ADB drivers on Windows 10. Could you please to look at it.
Have you tried to root the venue 8 3840 on win 10? I'm also DISABLE DRIVER SIGNATURE ENFORCEMENT as you suggested but the issue seems still there.
Thank you & Regards.
JPham said:
Hi cmahendra,
Thanks for your sharing, I'm facing a problem with installing the ADB drivers on Windows 10. Could you please to look at it.
Have you tried to root the venue 8 3840 on win 10? I'm also DISABLE DRIVER SIGNATURE ENFORCEMENT as you suggested but the issue seems still there.
Thank you & Regards.
Click to expand...
Click to collapse
Are you using the latest Intel drivers?
JPham said:
Hi cmahendra,
Thanks for your sharing, I'm facing a problem with installing the ADB drivers on Windows 10. Could you please to look at it.
Have you tried to root the venue 8 3840 on win 10? I'm also DISABLE DRIVER SIGNATURE ENFORCEMENT as you suggested but the issue seems still there.
Thank you & Regards.
Click to expand...
Click to collapse
xBIGREDDx said:
Are you using the latest Intel drivers?
Click to expand...
Click to collapse
Thanks @xBIGREDDx I was going to suggest him same. To install latest drivers from Intel Website. Link updated in Opening post.
Thanks!
I just wanted to say a quick thanks for posting this! I tried to root my Dell Venue 8 3840 once before but was unsuccessful. I followed your instructions, and though the steps at the end were just a little different for mine, it worked! I noticed you also mentioned your 3840 was for India, and I wanted to mention that I'm in the United States and it still worked, and I verified root access with Root Checker Basic. That way other people know it should work for their device.
Thanks again! :good:
johndavisjr77 said:
I just wanted to say a quick thanks for posting this! I tried to root my Dell Venue 8 3840 once before but was unsuccessful. I followed your instructions, and though the steps at the end were just a little different for mine, it worked! I noticed you also mentioned your 3840 was for India, and I wanted to mention that I'm in the United States and it still worked, and I verified root access with Root Checker Basic. That way other people know it should work for their device.
Thanks again! :good:
Click to expand...
Click to collapse
Sorry for late reply, but thanks for confirming that it worked for US version too. Actually I did not wanted people to blame me for any unexpected issues, therefore I mentioned its tested on Indian Version perfectly. Others can still try it because technically there is no risk at all, even if rooting fails. In fact, I succeeded after many failures with this tool itself.
Thanks for your instruction, but at step 5, the status is "unknow", should I do next step? my device is LTE version. Thanks!!
Dell venue 10 7000
cmahendra said:
Post reserved for more Screenshots.
Click to expand...
Click to collapse
Will this method work for dell venue 10 7000 ?
It has the same processor
hksingh said:
Will this method work for dell venue 10 7000 ?
It has the same processor
Click to expand...
Click to collapse
No idea! But Dell makes unbrickable devices. You can restore to stock rom again so no harm in trying. I am taking risks since last 7/8 years and not a single phone is hard-bricked . Always recovered.
But Do at your own risk because everyone's fighting spirit and knowledge is different
It works on Win 7, have the problem whit win 10..WTF you are not reply my question , though thanks for your post!!
I pair flashing of the SuperSU file with a flashable BusyBox maintained in the Android dev thread. Check it out here:
http://forum.xda-developers.com/showthread.php?t=3219431
It eliminates the need to download BusyBox Installer (unless you're looking for a particular flavor)
Thanks for the instructions! I had to do the instructions twice. First so the tablet could get to the droidboot screen so I could install the google inc adb interface drivers. On the second go everything worked as it should. Thanks again!
cmahendra said:
No idea! But Dell makes unbrickable devices. You can restore to stock rom again so no harm in trying. I am taking risks since last 7/8 years and not a single phone is hard-bricked . Always recovered.
But Do at your own risk because everyone's fighting spirit and knowledge is different
Click to expand...
Click to collapse
Please help me uncle! i just have a tablet dell 3840 lte and try to root it step by step like the topic but i have stuck at step 4,the status device is unknow,and then i tried again severals time so carefully but it still like that,i also did the step in the youtube video to DISABLE DRIVER SIGNATURE ENFORCEMENT,i did it on my pc with window 8.1,what can i do now,uncle,please help me,it is too slow and forgive me pls if i have any mistake in using english,i'm from vietnam,and thank agians,i'm looking forward to have your help ^^
phucvn93 said:
Please help me uncle! i just have a tablet dell 3840 lte and try to root it step by step like the topic but i have stuck at step 4,the status device is unknow,and then i tried again severals time so carefully but it still like that,i also did the step in the youtube video to DISABLE DRIVER SIGNATURE ENFORCEMENT,i did it on my pc with window 8.1,what can i do now,uncle,please help me,it is too slow and forgive me pls if i have any mistake in using english,i'm from vietnam,and thank agians,i'm looking forward to have your help ^^
Click to expand...
Click to collapse
Did you install adb/fastboot? My pc wouldn't let me download the file from the link for some reason, but there is another thread on xda website on how to install it. It's called 15 sec fastboot/adb install.
phucvn93 said:
Please help me uncle! i just have a tablet dell 3840 lte and try to root it step by step like the topic but i have stuck at step 4,the status device is unknow,and then i tried again severals time so carefully but it still like that,i also did the step in the youtube video to DISABLE DRIVER SIGNATURE ENFORCEMENT,i did it on my pc with window 8.1,what can i do now,uncle,please help me,it is too slow and forgive me pls if i have any mistake in using english,i'm from vietnam,and thank agians,i'm looking forward to have your help ^^
Click to expand...
Click to collapse
I am not sure but there is some difference in 3840 and 3840 LTE. You are adviced to look all threads in this tablet section for more information on rooting and flashing this tablet.
tictac02_02 said:
Did you install adb/fastboot? My pc wouldn't let me download the file from the link for some reason, but there is another thread on xda website on how to install it. It's called 15 sec fastboot/adb install.
Click to expand...
Click to collapse
yes,i downloaded the zip file from a link in the topic and extract it,is it exactly an adb/fastboot?
---------- Post added at 05:25 AM ---------- Previous post was at 05:21 AM ----------
cmahendra said:
I am not sure but there is some difference in 3840 and 3840 LTE. You are adviced to look all threads in this tablet section for more information on rooting and flashing this tablet.
Click to expand...
Click to collapse
yes,i'm looking for some topic to know more but it so hard to find more helpful infor,it seem to be very few user with this tablet
phucvn93: yes,i downloaded the zip file from a link in the topic and extract it,is it exactly an adb/fastboot?
Yup, it will ask you after downloading the program if you would like to install fastboot, then ask you if you want to install adb drivers. Then I did all the steps in this thread twice. Once to get the tablet to boot in droidboot to install adb drivers and then again for it to run fastboot. I also had to update my tablet drivers and select the adb drivers. I'm sure the steps I took was a lot more work then most maybe. Not sure if what I did will work for you since mine is not a 3840 lte. But would be happy to post the steps I took.
tictac02_02 said:
phucvn93: yes,i downloaded the zip file from a link in the topic and extract it,is it exactly an adb/fastboot?
Yup, it will ask you after downloading the program if you would like to install fastboot, then ask you if you want to install adb drivers. Then I did all the steps in this thread twice. Once to get the tablet to boot in droidboot to install adb drivers and then again for it to run fastboot. I also had to update my tablet drivers and select the adb drivers. I'm sure the steps I took was a lot more work then most maybe. Not sure if what I did will work for you since mine is not a 3840 lte. But would be happy to post the steps I took.
Click to expand...
Click to collapse
oh may be i'll try adb/fastboot 15sec tonight,do u try it or know other topic,forum that discuss about our problem? pls pm me if you know

Lenovo Tab a10-30 bricked or fixable?

Hello everyone,
I will share my experience with you, and I hope for a solution!
A few days ago I rooted my Lenovo tab 2 A10-30 successfully using Kingroot. Then, I tried to change Kinguser with SuperSU, which I also successfully did. However, I noticed that although the main root app was SuperSU, Kingroot was still on my phone, so I deleted it using a bloatware removal app and restarted the tablet. Now it won't turn on. It gets stuck at the Lenovo loading screen, and that's about it. When I press the power button + volume down button, it gets me to a Chinese menu that is not the recovery mode (there is no MMC, just options about voloume, colors, mic test etc). If I press the volume up+ volume down + power button, it just brightens the screen and shows nothing.
I tried flashing the stock ROM using the Smart Phone Flash Tool, but the PC does not recognize fully the tablet (it just prompts me to install the Lenovo USB drivers, and I cannot access the tablet's internal storage). Moreover, the Lenovo windows applications do not recognize the tablet when I connect it to the PC.
I really do hope that there is a way I can fix it.. Thank you all in advance.
Hi,
I did almost exactly the same... Kingroot, tried to remove bloatware with another app, and ended up with a bricked tablet I can still access the bootloader, but flashing the tablet from there is to no avail.
I am still looking for the original ROM, which seems nowhere to be found. Did you, by any chance, make a backup first?
Another one here But I'am able to go into recovery and into adb sideload, from there I can view internal memory(/system). And it looks like system is trying to load supersu-daemon which was removed and it can't get past that. I tried to recover paths (to original ones), but it still wont go past loading screen. (it is just restarting the app_process32).
Now if we only could get the hold on original factory firmware... from there one we can sideload it via fastboot.
And for the drivers you need andorid usb drivers https://developer.android.com/studio/run/win-usb.html#top
TLDR; we are looking for TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip
So, I have spent about 5 hours attempting to find a way to dump the firmware without first rooting the device, so that I could share it with you guys (and have a backup for myself in case I attempt to root it myself.) Unfortunately it seems like it needs to be rooted before I can create a nandroid backup through adb. Unfortunately the tablet is not based on mtk, and I cannot find any qualcomm utils that can dump the firmware.
The one Qualcomm util I found (QFIL) seems like it is only for flashing, and for backing up some individual data for the tablet (I assume it may contain such as license keys for the commercial features in the recent phones such as Sony Xperia Z3). I also looked into fastboot, and that too can only flash a new firmware.
So, unless the tablet gets rooted I don't see any way to make a proper backup.
I am unable to post links in messages, so you need to do some manual editing.
dz0ny said:
TLDR; we are looking for TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip
Click to expand...
Click to collapse
This however seems like very valuable information, unfortunately the only places I can find that has this available for download is charging money for access to the file.
50$ at dlgsm,com www DOT dlgsm DOT com/register.php?file=TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip&dir=%2FFLASH-FILES%2FLENOVO%2FT_Series%2FTB2-X30F
or from 10$ at pars-hamrah,com: www DOT pars-hamrah DOT com/%D8%A7%D8%AE%D8%A8%D8%A7%D8%B1-%D9%85%D8%B1%DA%A9%D8%B2-%D8%AF%D8%A7%D9%86%D9%84%D9%88%D8%AF-%D8%A7%D8%AE%D8%AA%D8%B5%D8%A7%D8%B5%DB%8C-%D9%BE%D8%A7%D8%B1%D8%B3-%D9%87%D9%85%D8%B1%D8%A7%D9%87/38027-%D8%B1%D8%A7%D9%85-%D8%A7%D9%88%D8%B1%D8%AC%DB%8C%D9%86%D8%A7%D9%84-%D9%84%D9%86%D9%88%D9%88-lenovo-tb2-x30f-%D9%86%D8%B3%D8%AE%D9%87-s000015-%D8%A7%D9%86%D8%AF%D8%B1%D9%88%DB%8C%D8%AF-5-1-1-%D8%AF%D8%B1-%D9%85%D8%B1%DA%A9%D8%B2-%D8%AF%D8%A7%D9%86%D9%84%D9%88%D8%AF-%D9%82%D8%B1%D8%A7%D8%B1-%DA%AF%D8%B1%D9%81%D8%AA.html"]Here[/URL]
It might also be available www DOT fars-gsm DOT com/75531-tb2-x30f_usr_s000015_1601151950_q8009_row_qpst-zip.html, at least they list the changelog for the firmware.
Since I have no use for a firmware right now, I will not be buying access to one (unless I at some point manage to brick mine as well). But if anyone decides to do so, please share it so others can enjoy it as well. I also suspect that if the file was available, it would increase the probability of someone attempting to make a custom rom at some point as well, it is a very cheap tablet when on sale, so it should have good potential for a community.
PS: I also stumbled over something called vRoot, that might be an alternative to Kingroot, although I have no idea whether it is as good at rooting and not installing unwanted extra apps. I guess someone who has used it on a tablet/phone that has a backup available might be able to shed some light on that.
---------- Post added at 08:08 PM ---------- Previous post was at 08:02 PM ----------
omrtpsycho said:
If I press the volume up+ volume down + power button, it just brightens the screen and shows nothing.
Click to expand...
Click to collapse
This is the QFIL (Qualcomm Flash something system) mode, however I do now know whether that helps anything at all. Since it seems to me it probably wont accept the TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip file mentioned in the thread. It seems to expect some xml file, maybe the zip file contains that?
Hi guys i have been strugling with this unit The last 3 days. I have eksakt same problem. I found these files: lenovo-forums.ru/files/category/106-прошивки-lenovo-tab-2-a10-30/
I extracted Them but dont know how to flash Them ?? Hope u guys Can help (sorry for bad english)
To Download files from Lenovo-forums.ru i logged in with my Google account
[PUT ROM TEMPORARILY HERE: https://www.wetransfer.com/download...024ee2974a44f8aa50e3dcd120160615184237/a84735 ]
Wow, suddenly action! With the help of Dead2 and Andersbp I have made some progress. Here are my steps:
I purchased the ROM from the Iranian site, and downloaded the other from the Russian forum. So now I have 2 ROMs:
65M TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip (Russian)
1.1G TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip (Iranian)
The smaller one is simply an update, which you could install easily:
1) boot into Recovery Mode
2) select "Apply Update from ADB"
3) run: adb sideload TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip
Which works... UNLESS YOU ROOTED THE DEVICE. Then it fails, and does not want to update. Thanks Lenovo
So, the larger one is a different type of ROM. This one will not load with adb sideload (gives footprint and signature error). But it DOES contain all the files to flash with QFIL (Qualcomm Flash something system).
Here I'm stuck. I followed this guide:
http://guidebelajar.blogspot.nl/2016/03/guide-how-to-flash-firmware-lenovo-vibe-p1.html
and tried to install these packages:
1) You must download and install USB Driver for Lenovo on your windows computer or PC.
2) QPST-2.7.422-qfil-qcom-Upgrade-Tool-20140422
3) Download Qualcomm HSUSB USB COM Drivers
(Note that you need to register and log in to needrom.com FIRST. Then click the link, but it will give an access error. Remove all in the URL after needrom.com (so go back to the main site), then go back to the download link, and it will work - the file is there.)
1) and 2) install pretty fine, but 3) is just a zip with a lot of drivers, no installer. I have no clue on how to install the proper driver...
Furthermore, the site suggests to install something on the device itself:
5) Create a folder with the name sdfuse in the root of the SD-card phone
6) Put the qsb-firmware (file with the extension .qsb) in the folder sdfuse.
Here I have 2 problems: First, my device does not boot, so I cannot create/copy files. Seconly: I cannot find qsb-firmware.qsb anywhere...
@ Dead2: How did you go through these steps?
Zwartoog said:
I purchased the ROM from the Iranian site, and downloaded the other from the Russian forum. So now I have 2 ROMs:
65M TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip (Russian)
1.1G TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip (Iranian)
Click to expand...
Click to collapse
Great, thanks for sharing the firmware, I hope you and everyone else with a softbricked tablet can get it fixed now
I am sure some of those would be willing to donate a couple of bucks to you if they get theirs working again.
Zwartoog said:
3) Download Qualcomm HSUSB USB COM Drivers
(Note that you need to register and log in to needrom.com FIRST. Then click the link, but it will give an access error. Remove all in the URL after needrom.com (so go back to the main site), then go back to the download link, and it will work - the file is there.)
1) and 2) install pretty fine, but 3) is just a zip with a lot of drivers, no installer. I have no clue on how to install the proper driver...
Click to expand...
Click to collapse
Ok, I used a LenovoUsbDriver_v1.0.12.exe driver installer, and that includes the HSUSB drivers needed, and I can confirm that windows recognizes the tablet as being in HSUSB mode with those. Whether QFIL does I have not tested.
I got the driver package from here: www DOT teamandroiders DOT com/lenovo-usb-drivers-download/
Zwartoog said:
@ Dead2: How did you go through these steps?
Click to expand...
Click to collapse
After you get past installing the HSUSB driver, you are officially the one that has gotten furthest on this.
I will assist in any way I can, but I will not attempt flashing my own tablet until I actually need to
Dead2 said:
After you get past installing the HSUSB driver, you are officially the one that has gotten furthest on this.
Click to expand...
Click to collapse
We'll get this working
Dead2 said:
Ok, I used a LenovoUsbDriver_v1.0.12.exe driver installer, and that includes the HSUSB drivers needed, and I can confirm that windows recognizes the tablet as being in HSUSB mode with those. Whether QFIL does I have not tested.
Click to expand...
Click to collapse
I tried that one too, but to no avail When I try to execute the executable, it ask for administrator permission, and after that vanishes...
I am running Windows 8, 64 bit. You?
Other question: when is your tablet recognised by Windows? Also in Recovery Mode?
Thanks!
Great work so far guys ! I Will try tomorrow with The new information! Mine is rootet so dont look good for me :/
Zwartoog:
The russian site also have Big files (1gb)
You Saw Them ?
Andersbp said:
Great work so far guys ! I Will try tomorrow with The new information! Mine is rootet so dont look good for me :/
Zwartoog:
The russian site also have Big files (1gb)
You Saw Them ?
Click to expand...
Click to collapse
No, I have spent too many hours translating Farsi today, was quite happy to find this one easily accessible on the Russian site
Can you check one of the bigger files? Might come in handy if my version seems incompatible for some reason...
Zwartoog said:
No, I have spent too many hours translating Farsi today, was quite happy to find this one easily accessible on the Russian site
Can you check one of the bigger files? Might come in handy if my version seems incompatible for some reason...
Click to expand...
Click to collapse
Sure Will try tomorrow
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
First i followed this guide:
https://2.bp.blogspot.com/-YxnBnMMx7Xg/VnaiVim76VI/AAAAAAAAURo/pz5IiaVdlcQ/s320/qfil.jpg
But insted of this:
9. Now, enter your Lenovo Vibe P1 into recovery mode. you can do it by :
Press the Volume Up button and keep holding it while connecting it to the computer/laptop using USB cable.
Lenovo Vibe P1 will vibrate one time, and you will see black screen.
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
{
"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"
}
Now you can continue with the guide, and use QFIL.
I used this firmware: https://drive.google.com/open?id=0B9affStJ4JQ1U3JXUTZFTDJ6NU0
Extract the rar file. Inside you will find the files needed in QFIL.
Hope this helps you guys
Andersbp said:
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
First i followed this guide:
https://2.bp.blogspot.com/-YxnBnMMx7Xg/VnaiVim76VI/AAAAAAAAURo/pz5IiaVdlcQ/s320/qfil.jpg
But insted of this:
9. Now, enter your Lenovo Vibe P1 into recovery mode. you can do it by :
Press the Volume Up button and keep holding it while connecting it to the computer/laptop using USB cable.
Lenovo Vibe P1 will vibrate one time, and you will see black screen.
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
Now you can continue with the guide, and use QFIL.
I used this firmware: https://drive.google.com/open?id=0B9affStJ4JQ1U3JXUTZFTDJ6NU0
Extract the rar file. Inside you will find the files needed in QFIL.
Hope this helps you guys
Click to expand...
Click to collapse
Super! Will try this tonight. Just in case: which Windows version are you using?
Zwartoog said:
Super! Will try this tonight. Just in case: which Windows version are you using?
Click to expand...
Click to collapse
I use windows 10
Andersbp said:
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
Click to expand...
Click to collapse
Great work! I am glad I was able to help you guys get this fixed
Andersbp said:
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
Click to expand...
Click to collapse
Yep, its at the bottom of my first post also, found that out by accident while trying to get into the normal recovery.
Now, hopefully someone will want to port TWRP and CM13 or Paranoid to this tablet
Doh i did not see that Dead2
Thanks everybody together we defeated the problem !
SUPER! Succes here as well! The trick was indeed to hold both vol UP and DOWN
Now: brand-new unrooted device
Thanks
Btw: I noticed that the rom from Andersbp is a TB2-X30L rather than the TB2-X30F. I used my F file (paid for it, dammit ), and that one also works well.
I am currently checking if I can modify the stock ROM to enable root / mult-user. Any hints?
Nice zwartoog !
I Can root with kingroot.. Are there better alternatives ? Kingroot is Full of bloatware
Andersbp said:
Nice zwartoog !
I Can root with kingroot.. Are there better alternatives ? Kingroot is Full of bloatware
Click to expand...
Click to collapse
Noo, no Kingroot. That's where all the disasters began. It is full of bloatware. Trying to uninstall Kingroot lead to bricking the device
Personally I am only interested in re-enabling the multi-user feature from lollipop. WHICH IS FOR SOME REASON DISABLED BY LENOVO Even when rooted and modifying the system/build.prop did not re-enable it.
I'm giving up now. At least I have a workable device. Restored pride. And more important: 3 happy kids
I think the TB2-X30L is the LTE version of the tablet, while the TB2-X30F is the wifi-only version. If correct, then there should be no problem
when using the LTE on a non-LTE model, but the other way around could potentially cause LTE to not work. The LTE firmware might have some
extra apps and settings enabled to cater to this ability, but it might also be completely identical. Btw, what does the model information say
after being flashed with the L firmware? In any case it is useful to know that they are cross-compatible, since sometimes there can be differences
in chipsets or screens that can cause minor or major problems.
As I mentioned earlier, another root alternative to kingroot seems to be vRoot, but I have not tried it myself. But now that it is possible to
recover a bricked tablet, it is also less risky to test such things.
BTW: Please remember to use the "Thanks!" button on posts you find helpful, I have tried to do so myself on the posts that I find helpful

Goclever Zoom.me adb connection

Hi Team,
Long story short - I have a problem with adb connection to Android device. And details below.
I've got a Goclever Zoom.me - Android 4.2.2 based photo frame. Really crappy device by the way... but, I really need to install some apk to have a possibility of remote connection to this device (FTP or SMB, or at least just create some network-shared directory). It would be also perfect to have any launcher with android menu and so on...
The issue is that it's impossible to connect to this device via adb. I remember that with old firmware it was actually possible, but long time ago (2015) I upgraded it to newer software, and official instruction to click 8 times a serial number in a device's software to enable USB debugging doesn't work anymore... I thought it had enabled debugging permanently but it seems to be not true, as adb nor fastboot don't see the device. PC recognizes it as a camera allowing to transfer files only.
Device doesn't have any hardware buttons except power and hard reset buttons. I was looking for any possibility to solder volume buttons, but didn't find a spot for them (mainboard is marked as: e351308 topwise-014).
I can connect OTG keyboard and mice instead, which may be helpful... but escaping nor ALT+ESC in the best case moves me to black screen with mouse cursor only...
Can you advice anything to connect to device via adb? What else can I try?
Modify the update perhaps? Seems to work.
GoClever Zoom.me and GApps
I need some help. I own a digital photo frame GoClever Zoom.me which is based on Android 4.2.2. It is rooted and USB debugging is on. I managed to install standard launcher but unfortunately there is no GApps installed on this device. I'm able...
forum.xda-developers.com
Still available
http://downloadfiles.goclever.com/Tablet/Zoom_me/ZOOM.ME_WiFi_Zmiana_Oprogramowania.pdf
80 page manual for a photo frame? LOL!
http://zoom.me/files/manual_en.pdf
Well, some say repetitio est mater studiorum, so they have put it there twice...
LOL! 40 page manual for a photo frame...
CXZa said:
Modify the update perhaps? Seems to work.
Click to expand...
Click to collapse
What do you mean by modifying the update? To modify /system/build.prop ?
I saw that thread, but the issue is that I can't update device again... PhoenixSuit nor adb can see it connected - seems like USB debugging is not enabled anymore and I can't enable it anyhow.
CXZa said:
80 page manual for a photo frame? LOL!
(...)
LOL! 40 page manual for a photo frame...
Click to expand...
Click to collapse
That frame was released with a huge marketing action...but it became a failure as it's a terrible design in total - from housing to software...
matisys said:
Hi Team,
Long story short - I have a problem with adb connection to Android device. And details below.
Can you advice anything to connect to device via adb? What else can I try?
Click to expand...
Click to collapse
That's really weird, because ADB since ever is integral part of every Android distribution. May be in the ROM your device is running on either ADB in fact isn't implemented or USB.debugging isn't allowed or ADB isn't bound to Android's USB-service.
matisys said:
What do you mean by modifying the update? To modify /system/build.prop ?
Click to expand...
Click to collapse
Meant flashing. So, do you have the MTK or Allwinner?
With one button it might be difficult to enter the update mode, but if opened you could possibly connect some pins to make boot to fail thus making it to boot such mode... IDK.
Other possibility is to make your wifi to connect to your own server instead of http://ota.zoom.me/ and let it "update" itself.
Their update zips are signed using test keys so you can make your own. (If recovery keys aren't changed when updated.) Or if you can enter the recovery mode then install it from sdcard.
I have multiple tools, but none can see the device without debugging on.
It's actually easy to open, but I didn't find a proper spot to enforce recovery mode...
CXZa said:
Other possibility is to make your wifi to connect to your own server instead of http://ota.zoom.me/ and let it "update" itself.
Their update zips are signed using test keys so you can make your own
Click to expand...
Click to collapse
How do you know that?
Running an own server is actually an easy part for me, but I'm not sure how to prepare a proper package...
There is actually an update package available to download:
http://downloadfiles.goclever.com/Tablet/Zoom_me/ZM7WIFI_20150717.img
But I couldn't modify it using Dragonface...
matisys said:
How do you know that?
But I couldn't modify it using Dragonface...
Click to expand...
Click to collapse
I checked the recovery in case build.prop lies.
Then again is their update a zip? Might be something exotic.
I also checked their ota apk and tested it.
It didn't download. Sent a lot of info from my tab. Some didn't match (faked what I easily could)... or no updates anymore...
Gave 502...
matisys said:
I didn't find a proper spot
But I couldn't modify it using Dragonface...
Click to expand...
Click to collapse
Another soc and device, but might work.
Entering to Flashing/Adfu mode (and Recovery mode too) - Actions Semi ATM7029 Quad-core ARM CPU devices
Entering to Flashing/Adfu mode (and Recovery mode too) - posted in Actions Semi ATM7029 Quad-core ARM CPU devices: The instructions given in this thread should work, but still as always, you use them at your own risk!If there is a hardware problem then the tablet probably is bricked for good...
www.slatedroid.com
Battery removing might be the safest...
Try imgRePacker...
OK, I managed to unpack the img file and to edit build.prop - Thanks fot that info One small step forward.
I added:
qemu.hw.mainkeys=0
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=ptp,adb (this one already exists)
Hoping it will allow me to access the system via adb or screen directly after reflash.
I didn't pack it back yet as I still didn't manage to access this device from computer...
I tried to find a spot on mainboard - I've made a connection on two spots:
{
"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"
}
But no luck...
There is more spots however, but none marked as recovery, ADFU, or similar...
And still no USB debugging, nor adb connection...:/
Tried of course some tricks with power button holding, clicking, reseting while hold, etc...
Any further suggestions...?
Maybe some ideas to enforce upgrade via wifi? I can establish a server, but not sure what exactly server should serve...? Just an img file is rather not enough...
Below that E351308 text, or above if other way around, is the target for those pin suggestions. But try battery, you can always solder it back together,.. or just let it go empty - might work...
> what exactly server should serve...?
yeah, there probably is some data exchange before the download..
BTW, this img appears to have adb enabled, so it's not the last one... Or it's disabled by other means...
Data it sent:
{"genderId":-1,"email":"","Locale":{"L":"eng","S":"en_US","C":"USA"},"deviceInfo":{"TIME":1419244414000,"FINGERPRINT":"ZOOM_ME\/ZM7WIFI\/ZM7WIFI:4.2.2\/JDQ39\/20141222:eng\/test-keys","HARDWARE":"gs702a","VERSION.SDK_INT":17,"BOARD":"exdroid","PRODUCT":"ZM7WIFI","DISPLAY":"ZM7WIFI_20141222","VERSION.INCREMENTAL":"20141222","DEVICE":"ZM7WIFI","TAGS":"test-keys","MODEL":"ZM7WIFI","BOOTLOADER":"unknown","CPU_ABI":"armeabi-v7a","CPU_ABI2":"armeabi","VERSION.CODENAME":"REL","MANUFACTURER":"ZOOM_ME","BRAND":"ZOOM_ME"}}
Click to expand...
Click to collapse
That hardware exposed me. It didn't get that from *.prop files.
OK, so currently it's like below.
I already tried some tricks with battery - disconnecting, connecting while booting, and no luck...
I tried with all spots marked below - one by one, and some combinations of few of them...
And the status is like that - spots 2 and 3 - seems to be ignored when connected - device behaves like nothing happened. It's more interesting when I connected 1 or 4. Device didn't start, and in a computer it appeared as unknown winusb device or Billboard device when connected 4 (USB\VID_1F3A&PID_EFE8&REV_02;3).
Universal ADB driver installer doesn't recognize it...
The only driver I managed to install was Allwinner driver and it appeared as USB Device(VID_1f3a_PID_efe8).
But still no luck with adb connection... Phoenix suite also doesn't recognize the device... In this state screen remains black and AXP223 (Power management) quickly becomes hot as hell (battery unplugged)...
Once unsoldered - it went back to life.
I also realized that my device says that it is version ZM7WIFI_20150717... what is confusing a bit because in other place it says it's 2.2 23-5.03.2015 software version...
But still no connection or any option to flash it
Can you tell me how do you run this software/hardware to see what does it send?
I can still use OTG keyboard and mouse - maybe there is some option to enter android settings and simply enable USB debugging?
Those pins that I mentioned at slatedroid are on the sides of that chip.. and don't solder, just place some tool - a needle between them. And if recognized remove it as after error it must function again in order to flash or what ever..
Here is one older post showing pin connecting for Amlogic,
that other was Actions Semi. Both go a mode that enables flashing when device looks dead. I don't know about Allwinner, is it similar...
How To Unbrick Your Amlogic AML8726-MX Series Tablet - v2.0 - Ainol Novo 7 Crystal
Page 1 of 47 - How To Unbrick Your Amlogic AML8726-MX Series Tablet - v2.0 - posted in Ainol Novo 7 Crystal: How To Unbrick Your Amlogic AML8726-MX Series Tablet - v2.0If Ive helped you unbrick your device please consider a donation, even if it is small it will help!My laptop is currently all...
www.slatedroid.com
So it seems that would be all, and the device got bricked...
I started the device with 7 and 8 pin of Flash memory connected - it was connected to PC and PhoenixSuite with original img loaded was running.Phoenix asked me immediately if I want to format the device - I clicked no, and it still started to flash the memory... It finished succesfully, device restarted and...now it freezes on initial logo.
Phoenix and adb recognize the device now, but adb shell doesn't work:
- exec '/system/bin/sh' failed: No such file or directory (2) -
and when I try to repeat flashing, phoenix recognizes device, but once I click upgrade - device resets, and upgrade is not performed...
EDIT: It's not that bad... I managed to make it working again on original software, and after one more reflash - ADB works well
Thanks a lot for all your help!
Did the reset hole fix it?
Maybe you should have formatted it in case the data is the reason to the freeze. But how it recovered?...
This Allwinner seem to be quite good.
Open source and giving info.
FEL - linux-sunxi.org
linux-sunxi.org
Installing to NAND - linux-sunxi.org
linux-sunxi.org
FEL/USBBoot - linux-sunxi.org
linux-sunxi.org
matisys said:
after one more reflash - ADB works well
Thanks a lot for all your help!
Click to expand...
Click to collapse
Great! Now disable that ota updater apk so it doesn't update it again...
It's actually hard to tell how it got fixed... instruction tells to not format the storage to not loose the unique device number - so I didn't, but it seems that it got formatted by itself as I lost all my pictures, but number remained untouched.
Now adb is enabled and I can freely connect to it - seems that something simply went wrong during previous upgrade years ago.
build.prop file gets restored after every reboot, so I can't put and store any changes there...
And OTA is not an issue as this device is not supported for a long time now And I'm not exactly sure how to do it, and feel a bit afraid of touching it when it finally works...
But just to finish entire project - can you recommend some reliable android SSH and FTP server? Or maybe something to share a folder via SMB?
matisys said:
But just to finish entire project - can you recommend some reliable android SSH and FTP server? Or maybe something to share a folder via SMB?
Click to expand...
Click to collapse
Not really but that android version limits the choices nicely...
Here is one saying it's open source.
swiftp
A FTP Server for your Android device.
ppareit.github.io
I think I once tested cifs in that Action Semi but it was long ago and was ready made in that test boot img...
[HOW TO] 2-way network file sharing on Android
Hi everyone, just thought I'd write up some quick instructions on how to set up file sharing between Android and a PC - both mounting Windows shares on Android, and Android on Windows. I was always frustrated by iOS's inability to do this easily, and it was one of the major reasons I switched...
forums.androidcentral.com
Thanks. Finally, after some trials I used SSHDroid and it's quite decent...
Can you also tell me how to permanently edit build.prop file? Mine is reverted to original after reboot. Device is factory rooted.

[GUIDE] REALME 7 RMX2155 GLOBAL BOOTLOADER UNLOCK

WELCOME, ALL.
After a very tiring process of swapping between ROMs and changing regions, APKs, et cetera, we have finally been able to perfect the method for unlocking the bootloader of the RMX2155! This is a detailed guide aimed to give you an easy time!​​----------------------------------------------------------------------------​​I AM NOT LIABLE FOR ANY DAMAGES, BRICKED PHONES, OR ANYTHING ELSE THAT HAPPENS. IT IS YOUR CHOICE TO FOLLOW THIS GUIDE, AND THE CONSEQUENCES ARE YOUR RESPONSIBILITY.​​----------------------------------------------------------------------------
FILES NEEDED:
So that you don't need to go through the irritating process of downloading everything, extracting the OFP, and going to sketchy places to try and find a stock ROM, you can now download everything from either one of the links below:
7.26 GB folder on MEGA
mega.nz
RMX2155UBL.zip | by OrthodoxOxygen for Realme 7
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Both links contain the same content: everything needed for this guide. It'll save you a lot of time.
----------------------------------------------------------------------------
PROCEDURE:
1. Download the .zip file from either of the links above, and then extract the files from inside.
2. Navigate to the "MTK Drivers" folder, extract the files, and then install them. For ".inf" files: You must right-click, and then select "Install" from the drop-down menu. You may have to disable a Windows setting for this to work, however, as they are unsigned drivers. You can learn how to do this here: https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
3. Install Python if you haven't already. MAKE SURE TO ADD TO PATH.
4. Hold "shift" on your keyboard, and right-click on the Windows home-key. Click "Command Prompt (Admin)".
5. Type in the command "pip install pyusb pyserial json5", and then close your command prompt once it is done installing.
6. Extract the "Bypass Tools.zip" into a folder, and then navigate to the "Driver" folder within. Right-click on the file named "cdc-adm.inf" file, and select "Install". Wait for it to finish - though, it shouldn't take any longer than a second.
7. Install libUSB, and then open it. Power your phone off, and keep it that way. LibUSB should be called "Filter Wizard" in your start-menu. Right-click on it, and run it as an administrator. Have your RMX2155 and a trusty MTP cable on-hand. Click on "Install a device filter", then connect your Realme 7 with both volume-buttons pressed. Select and install the device that appears. It should have something like "MTK" in its name. Do this quickly, as it usually disappears after a few seconds. Once that is done: Unplug your phone.
8. Head to the folder with the bypass tools inside, and open "brom.bat". Connect your device with both volume buttons pressed. It should say something along the lines of: "Protection disabled" if it is successful. Disconnect your phone again.
9. Open the flash-tool folder, and launch the application inside. It is named: "flash_tool.exe". Select the scatter file inside the "OFP Contents" folder within the ROM folder, and un-check the following boxes: "Opposerver 2", "Special preload", "My custom", and "Cdt engineering".
10. Make sure that the box above where it lists all those files says: "Download only". This is very important. After you've verified that those boxes are without check-marks, and that the method is "Download only": Press the "Download" button at the top, connect your phone, and then press the volume-buttons. Once your phone is done flashing and a green check-mark is displayed: It will then boot. If it doesn't boot automatically, wait a few more seconds, and then hold the power key until it turns on. Give it some time.
11. Once it starts, and after you've gone through the main set-up process, you'll need to change your region to "Vietnam". This is a very important step to get your bootloader unlocked. For the sake of making this short: Follow the link. It will take you to a guide that should work for all OPPO devices. Please, read it carefully. From top to bottom. https://forum.xda-developers.com/t/...dated-instructions-now-working-again.4143415/
12. Move the Deep Test .APK file to your phone. Install it, and then open it. Submit your application, and wait. After: Just follow the directions given, and use ADB to unlock that bootloader. Use the following video to help you out if you don't already know how to unlock your bootloader with ADB! It also shows you how to flash a recovery, which will be useful if you wanna do that sorta stuff.
13. Success!
----------------------------------------------------------------------------
If you find that your phone won't connect through fastboot or SP Flash Tools after you've finished unlocking your bootloader, uninstall the LibUSB filter for your device (not the program), and then reinstall it.
For those of you wondering, YES, your phone can be flashed with GSIs, as it is a treble phone. However, you should download the "Treble Check" app off of the Playstore, as it supplies you with important information relating to which ROMs you can use with your device. IF YOU DO NOT MAKE SURE TO FLASH THE CORRECT GSI FILE TO YOUR PHONE, YOU MAY HARD-BRICK IT. Take a look at the guide below. Happy flashing!
https://forum.xda-developers.com/t/...n-realme-7-using-super-gsi-installer.4280785/
----------------------------------------------------------------------------
If you need help, just ask below!
----------------------------------------------------------------------------
EXTRA SPECIAL THANKS TO:
@albatron34000
@SwizzRM7
Working with you has been great!​
All has been confirmed to work. Your bootloader is now unlockable. Have fun!
Hello
Thanks for the info
Someone already tried it, did it work?
vehare1129 said:
Hello
Thanks for the info
Someone already tried it, did it work?
Click to expand...
Click to collapse
Yes. According to the person who sent me these instructions: It does unlock the bootloader, which allows you to flash Magisk, TWRP, and ROMs. I haven't tried it myself, and this method has only recently become public due to my post - meaning that we need to wait for a brave soul to risk their Realme 7 for further development. Let's hope somebody tries this out soon. I'd be absolutely ecstatic if we could get one or two more people to confirm that it works.
Got it, thanks again to you and "Albatron34000" for the method
Hope there will be brave souls to test this method
It's just ridiculous that version 2155 still won't let you unlock the bootloader
All that remains is to wait...
OrthodoxOxygen said:
Yes. According to the person who sent me these instructions: It does unlock the bootloader, which allows you to flash Magisk, TWRP, and ROMs. I haven't tried it myself, and this method has only recently become public due to my post - meaning that we need to wait for a brave soul to risk their Realme 7 for further development. Let's hope somebody tries this out soon. I'd be absolutely ecstatic if we could get one or two more people to confirm that it works.
Click to expand...
Click to collapse
vehare1129 said:
Got it, thanks again to you and "Albatron34000" for the method
Hope there will be brave souls to test this method
It's just ridiculous that version 2155 still won't let you unlock the bootloader
All that remains is to wait...
Click to expand...
Click to collapse
Make sure you give full credit to Albatron34000. All I did was write the guide. But: Yeah. It seems we'll just have to wait for now. If we can get confirmation from one or two people that it really does work: I'll remove a good amount of the warnings, and make the final version of this guide.
So, does this method work?
Has anyone tried it yet?
EssauRojas said:
So, does this method work?
Has anyone tried it yet?
Click to expand...
Click to collapse
tryed by many and it work. any problem just ask.
Question:
I need exactly the version from this post "RealmeUI Version RMX2151PU_11.A.87"?
Or can I download the version from https://www.realme.com/ph/support/software-update ?
{
"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"
}
vehare1129 said:
Question:
I need exactly the version from this post "RealmeUI Version RMX2151PU_11.A.87"?
Or can I download the version from https://www.realme.com/ph/support/software-update ?
View attachment 5294155
Click to expand...
Click to collapse
No, this is the OTA file. You need the full stock ROM, which is around 8 GB. Give me some more time, and I will bundle all these files together for an easier process. Also: The guide is not 100% complete. I'd say it's about 90% done. By the end of today or tomorrow, the guide should be fully done.
OrthodoxOxygen said:
No, this is the OTA file. You need the full stock ROM, which is around 8 GB. Give me some more time, and I will bundle all these files together for an easier process. Also: The guide is not 100% complete. I'd say it's about 90% done. By the end of today or tomorrow, the guide should be fully done.
Click to expand...
Click to collapse
Ah, I got it.
Thanks for your work!
vehare1129 said:
Ah, I got it.
Thanks for your work!
Click to expand...
Click to collapse
No problem! Make sure to thank @albatron34000 , too.
The guide should now be complete, and is awaiting testing. All I ask for now (although it may be a bit pushy) is that somebody tries this method - understanding that they may brick their phone in the process. Any volunteers will be very greatly appreciated.
I have no problem trying but, does anyone have a guide to unbrick the RMX2155? (Just in case)
EssauRojas said:
I have no problem trying but, does anyone have a guide to unbrick the RMX2155? (Just in case)
Click to expand...
Click to collapse
Should be the same way you flashed it, but just with RMX2155 firmware. Only problem is finding it. I remember someone sent me a link for it. I'll send it to you in a second. Just let me find it.
OrthodoxOxygen said:
Should be the same way you flashed it, but just with RMX2155 firmware. Only problem is finding it. I remember someone sent me a link for it. I'll send it to you in a second. Just let me find it.
Click to expand...
Click to collapse
It's a sketchy site, but these are usually the only places you'll find firmware files for these kinds of phones, unfortunately. https://easy-firmware.com/index.php?a=downloads&b=folder&id=70767
OrthodoxOxygen said:
THIS GUIDE NOW NEEDS TO BE TESTED BY A READER.
Yes, you read that title right. This method unlocks the bootloader of the RMX2155 (Global Version) of the Realme 7.
I cannot say with certainty that this works because I haven't tried it for myself, but - according to @albatron34000 - it allowed them to successfully use the apk method of unlocking the bootloader, and subsequently root the RMX2155 (Although, it reportedly does not pass the safety-net check). The instructions are below.
I AM NOT LIABLE FOR ANY DAMAGES, BRICKED PHONES, OR ANYTHING ELSE THAT HAPPENS. IT IS YOUR CHOICE TO FOLLOW THIS GUIDE, AND YOUR RESPONSIBILITY.
FILES NEEDED:
So that you don't need to go through the irritating process of downloading everything, extracting the OFP, and going to sketchy places to try and find a stock ROM, you can now download everything right here:
File folder on MEGA
mega.nz
Contains everything needed for this guide. It'll save you a lot of time.
PROCEDURE:
1. Download the all the files above from the MEGA link.
2. Install Python if you haven't already. MAKE SURE TO ADD TO PATH.
3. Hold "shift" on your keyboard, and right-click on the Windows home-key. Click "Command Prompt (Admin)".
4. Type in the command "pip install pyusb pyserial json5", and then close your command prompt once it is done installing.
5. Extract the "Bypass Tools.zip" into a folder, and then navigate to the "Driver" folder within. Right-click on the file named "cdc-adm.inf" file, and select "Install". Wait for it to finish - though, it shouldn't take any longer than a second.
6. Install libUSB, and then open it. It should be called "Filter Wizard" in your start-menu. Have your RMX2155 and a trusty MTP cable on-hand. Click on "Install a device filter", then connect your Realme 7 with both volume-buttons pressed. Select and install the device that appears. Once that is done: Unplug your phone.
7. Head to the folder with the bypass tools inside, and open "brom.bat". Connect your device with both volume buttons pressed. It should say something along the lines of: "Protection disabled" if it is successful.
8. Open the flash-tool folder, and launch the application inside. It is named: "flash_tool.exe". Select the scatter file inside the "OFP Contents" folder within the ROM folder, and un-check the following boxes: "Opposerver 2", "Special preload", "My custom", and "Cdt engineering".
9. Make sure that the box above where it lists all those files says: "Download only". This is very important. After you've verified that those boxes are un-ticked, and that the method is "Download only": Press the "Download" button at the top, and connect your phone using the volume-buttons. Once your phone is done flashing and a green check-mark is displayed: It will then boot. Give it some time. Once it starts, select "Vietnam" as your region.
10. Finally: Enable MTP to your phone through developer options, and move the Deep Test .apk file to your phone. Install it, and then open it. Submit your application, and wait. After: Just follow the directions given, and use ADB to unlock that bootloader.
11. Success!
------------------------------------------------------------------------------------------------------------------------------
If you need help: Just ask!
SPECIAL THANKS TO:
@albatron34000 ​
Click to expand...
Click to collapse
Tested this today, and every step worked until i reached step 10. I installed the apk and it just refuses to work. Once i hit "Start Applying" and agreed to the content it fails after clicking on "Submit application" Saying it 'failed to submit application, This model does not support in-depth test'
SwizzRM7 said:
Tested this today, and every step worked until i reached step 10. I installed the apk and it just refuses to work. Once i hit "Start Applying" and agreed to the content it fails after clicking on "Submit application" Saying it 'failed to submit application, This model does not support in-depth test'
Click to expand...
Click to collapse
Hey. Thanks a lot for testing this! Can you try and change your region to "India", please?
OrthodoxOxygen said:
Hey. Thanks a lot for testing this! Can you try and change your region to "India", please?
Click to expand...
Click to collapse
Okay sure, i will try that.
Edit: Sadly that didn't work either. Same results.
Thank you anyways for taking the time of making this guide, if there's any other solutions i could try, please let me know.
SwizzRM7 said:
Okay sure, i will try that.
Edit: Sadly that didn't work either. Same results.
Thank you anyways for taking the time of making this guide, if there's any other solutions i could try, please let me know.
Click to expand...
Click to collapse
Hold on. Watching someone else unlock the Indian variant. It seems they are using the a.43 stock ROM. I'm going to upload a deep-test apk that should be compatible. If that doesn't work: We'll have to try a different ROM. The one I had you flash was a.87 - which might have fixed the vulnerability, if that's how people are getting around to unlocking their bootloaders. I'll reply to you again once I upload it.
EDIT: Nevermind. I can just attach it here!
EDIT #2: AH. Did you turn on "OEM Unlocking" in the developer options?

Categories

Resources