ClockworkMod Recovery (Unofficial)Finally we have fully functioning CWM recovery for the LG C800, also known as the T-Mobile USA MyTouch Q, also known as the Bell/Virgin Canada Eclypse! After many said it couldn't be done... here we are!
{
"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"
}
How to Install
0. Prerequisites
You will need:
- ADB and fastboot (http://dottech.org/downloads/adb_fastboot_and_other_tools.zip)
- LG's ADB drivers, available here.
Optionally, you will need:
- Root. (Use SuperOneClick root) Note: Root is not required for flashing via fastboot, but may be required for recovering should anything go wrong!
1. Back up your old recovery! ROOT REQUIRED
Open up a shell on your device by using adb shell or running your terminal emulator.
If you see a $ prompt, type
Code:
su
to get root. Otherwise if you see a # prompt you are ready to proceed.
Type
Code:
dd if=/dev/block/mmcblk0p17 of=/sdcard/stock-recovery.img
to write the stock recovery to your sd card. This will take about 8 MB of space.
2. Prepare the phone for future awesomeness
First, we must get the device into fastboot mode. In order to do this you must be able to have ADB access to the device. ADB is accessible when you are on the charging screen and when the phone is fully booted. You can enable ADB (debugging) access in the Application settings to access the adb service while your phone is fully booted.
Get the phone to the charging screen or enable ADB in the OS. Now, plug in the phone and verify you have adb access from your computer:
Code:
adb devices
If your phone is not showing up, go into device manager and make sure the LG ADB drivers are properly installed.
Once you have ADB access, run this command on your computer:
Code:
adb reboot bootloader
This brings the device into fastboot mode. What does fastboot mode look like? Well, it looks like a whole lot of nothing, mainly. If your phone boots up at this point and hangs out at the LG logo for a while, you're in fastboot mode. To verify it's in fastboot mode, run
Code:
fastboot devices
it should show something like
Code:
C:\androidsdk\platform-tools\> fastboot devices
? fastboot
If you see this, you are ready to flash!
3. Flash!
To flash, first run
Code:
fastboot erase recovery
This erases the recovery partition and ensures that everything is zeroed out so nothing gets in the way.
Now run
Code:
fastboot flash recovery C:\Path\to\downloaded\lgc800-recovery-cwm-chui101.img
protip: Tab autocompletes. It saves a lot of key strokes if you have a lot of long folder names like I do!
It should almost instantaneously transfer the recovery image, and pause just a few seconds more to write the CWM recovery image. When done, you can type
Code:
fastboot reboot
to reboot the phone back into the main OS.
4. Reboot into recovery!
To reboot into recovery:
- Issue an adb reboot recovery from your computer wherever you have ADB access (charging screen, stock recovery, or the main Android environment if you have it enabled there.)
- Or, from the phone's powered off state, hold down VOL DOWN, F, and A, and press the power button. Once the LG logo appears, you can release the power button. Once the LG logo disappears and reappears, release all the the buttons.
Welcome to CWM recovery! You can take a nandroid backup, mount USB storage, and flash zips from here! Hopefully this opens the door to CM9 and other custom ROMs on this device!
Buttons are:
MENU or VOL+ = up
HOME or VOL- = down
GENIUS or ENTER = select
BACK or DEL = back
Note: If anything goes wrong, you can return to stock recovery by using
Code:
dd if=/sdcard/stock-recovery.img of=/dev/block/mmcblk0p17
, or by using the CWM flashable zip available below. Note: Above command REQUIRES ROOT.
Downloads
It is recommended that you check the MD5 sum of your downloads!
CWM 6.0.1.2 Fastboot Image MD5: b8d15a0ee9486f0a9662dd5747c50c43
CWM 6.0.1.2 CWM Flashable ZIP MD5: 44ec9d19d5814fcfac8397c7d9a77559
USB functionality has been fixed as of 25 August. If you downloaded 6.0.1.2 before then, you might need to flash the update! If you are having any additional issues with this recovery please let me know!
Older versions:
CWM 6.0.0.0 Fastboot Image MD5: 3f5661d6120eddfd7c436c439805a310
Stuff to Flash from CWM
CyanogenMod 9 (Unofficial) Thread
Stock 2.3.6 ROM (V10V) MD5: f71cac4b1b534d94bb29d5c21a4ed8a1
NOTE: You should perform a wipe/factory reset if you are coming from a ROM other than the stock 2.3.4 that shipped with the phone.
Stock 2.3.4 ROM (V10D, bloatware and CarrierIQ removed) MD5: b6d8c04fb19cd9847027930dfb9fa7e8
NOTE: This image contains issues due to CIQ removal such as unreliable MMS/SMS retrieval. This should be only used as a last resort.
Stock Baseband for T-MOBILE MyTouch Q ONLY MD5: 2c2dcaeb6d75b37ff0b41f311665814c
Stock Recovery (from LG V10V 2.3.6 ROM) MD5: c9f606bc9033264d967ae98516cc044b
Thanks to:
misterfamilyguy for getting the ball rolling
vtinoc for getting the ball rolling again
mudtub for helping build all those recovery images and deodexing
This is amazing. Thanks!
This is good news for Q users.
Sent from my LG-E739 using Tapatalk 2
Doing some digging in the kernel source, it seems like this device is related to the LG e510, which has CM7.2 currently. We may be able to flash the e510 builds. More to come...
Thanks for your contribution .
Nevermind, it's related in name only. The MyTouch Q has the code name "Univa Q" which is its only connection really to the e510 (Univa). That and its screen size. The system board seems to be more related to the e739.
Thanks chui101 for getting the ball rolling. Good work.
Is there a link to the kernel source for the LGE C800?
I would certainly be interested in compiling a kernel and CM7 or even CM9. I have all the proprietary files needed, just need to dig around in the source and I'll upload to my github repo.
Yeah they have a 2.6 series kernel for gingerbread posted:
http://www.lg.com/global/support/opensource/opensource.jsp
search for LGC800, and it should be there.
I'm trying to get CM9 to build and I think I'm way over my head with the kernel config!
Thanks for the link, I haven't seen the Open Source page for LGE before.
If you have time or a repo I would certainly like to help and get the proprietary and device libs setup for a build. Shouldn't be too much work for the initial compile.
The C800 and the E739 are basically the same, except the C800 has a slide out keyboard.
Maybe you can flash the E739 builds of CM7/9.
Sent from my LG-E739 using Tapatalk 2
It's not quite that simple, C800 is mdpi while E739 is hdpi. Also, the partition sizes are different, and the e739 kernel doesn't have the hardware keyboard. I'm pretty sure that's enough to require a completely different build.
The kernel builds fine from LG's source code, but I'm not convinced it'll be compatible with cm9. Also, I can't get a kernel config to build CM9 for me. I'm trying to adapt the /arch/arm/configs/univaq_perf_revc_defconfig that's used in LG's kernel build for the CM9 kernel but am not having much luck... Any ideas?
I was unaware that the Q was MDPI.
No, that much of ideas. I'm not a DEV, i just port ROMS to the E739
Our phones are identical, except for mine been HDPI and yours MDPI.
---------- Post added at 01:46 AM ---------- Previous post was at 01:39 AM ----------
You CAN try and port a rom from the e739.
You'll just have to resize the images to fit your screen.
http://forum.xda-developers.com/showthread.php?t=785864
Use your phone's kernel and such important files.
It might boot, but the differences do extend beyond screen size. The camera chips are different, there is an additional LED flash on the Q, and no front-facing camera. It seems the softkeys and touchscreen also may use different drivers if I am reading the kernel configuration correctly. Still, I am using the e739 as a jumping off point.
If you need help, just ask here or in a PM.
Boy do I need help! Lol. Would you happen to know what needs to be done to a gingerbread kernel to get it to work with ICS?
Cyanogenmod did that for us lol so I haven't really messed with the kernel.
Except for editing the BOOTCLASSPATH but that's bout it.
But if I were you I'll start working with a GB 2.3.7 rom.
Sent from my LG-E739 using Tapatalk 2
2b doesn't work, writes it out and when i reboot to check CWM, it's still stock recovery and wipes out the phone. How do I get this on my phone? Fastboot doesn't work on this device.
fastboot does work. You can also get it into fastboot by holding down home as you turn on the phone.
chui101 said:
fastboot does work. You can also get it into fastboot by holding down home as you turn on the phone.
Click to expand...
Click to collapse
Tried it. Just boots like normal, gotta do acrobatics holding home and plugging in USB cable because it'll draw power from USB and screw it up.
Let's just make an update.zip so we can go into stock recovery and just flash on the new zip and not fiddle around with fastboot and dd niether of which work.
Try porting some images from the P500. It MPDI.
Related
Here are the steps required to backup the Fuhu Nabi 2, install a custom recovery, root, and gapps using Ubuntu(12.10) Linux.
This also works on Windows(other than installing adb and fastboot) if you just remove the 'sudo' from the commands.
For a scripted Windows install, check out Nabi Lab: http://forum.xda-developers.com/showthread.php?p=36758895
Original root from jmztaylor, Includes the new gapps(t499user) and the new TWRP 2.3.3.0 from aicjofs(thanks!)
You should do all of the OTA updates before rooting(otherwise you might lose WiFi) When I posted this the latest version was 1.9.37. Settings>About Tablet>Update>Check Update
Download the needed files then extract all of the files to your home folder to begin. http://dl.dropbox.com/u/6529005/Fuh...Backup-Root-Recovery-Gapps 30December2012.zip
Open a terminal(ctrl+alt+t) and run the following command to install ADB and Fastboot (Universe).
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On the device, enable USB debugging in Settings>Developer options, then connect USB cable.
Just in case the adb server is already running, lets kill it using:
Code:
adb kill-server
Now we will start the server and reboot the device:
Code:
sudo adb reboot-bootloader
Once the device has rebooted into the bootloader, we will flash the new recovery image using fastboot:
Code:
sudo fastboot flash recovery recovery.img
When fastboot is finished, boot the new recovery kernel on the Nabi2 by pressing vol+ then vol-(down to recovery) then vol+ to select.
{
"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"
}
We will push the follwing files to the device.
First we will push the Root file.
Code:
adb push root.zip /sdcard/root.zip
Now we will push the Google Apps File
Code:
adb push gapps.zip /sdcard/gapps.zip
This is the script that will backup then install Root and Google Apps onto the device.(you can also skip the script and do it manually if you like, but make sure you do a backup)
Code:
adb push backup-root-gapps.openrecoveryscript /cache/recovery/openrecoveryscript
Now we will reboot the device and let the script do it's thing.
Code:
adb reboot recovery
Once you log into your device, start up SuperSU to make sure that root 'sticks'.
Your Fuhu Nabi2 is now rooted, w/gapps, and a custom recovery, Now click on the "thanks" button
NOTE: The following is if you ever need to do an OTA update, which requires the original Nabi2 recovery.
Download the original Nabi2 recovery image to your home folder https://www.box.com/s/9ogqkk8uu71bqrnpz9w1
Reboot the device into the bootloader
Code:
sudo adb reboot-bootloader
Finally we will flash the original recovery image to the device
Code:
sudo fastboot flash recovery nabi2_original_recovery.img
Thank you very much! In about 10 minutes, everything was the way things should be! Specifically, a nicely rooted tablet so that my son could thoroughly his tablet! Now if I can get XBMC working properly, then life would be perfect! Thanks again!!!!
Fuhu Nabi2 Common issues and FAQ.
Glad it helped you out! It's a great little tablet.
To make Nabi2 more like a regular tablet now that you have Root and Google Play, you can prevent the tablet from starting Nabi Mode/Monarch UI by checking the box in Settings>Security>'Set Parent Mode as default mode'.
You can also remove the files in the /vendor/app/ folder if you want to free up some space. Just make sure to have 'Parent Mode as default mode' checked before you remove these files, or when you reboot the tablet it will give you a blank screen.
Code:
NvCPLSvc.apk, fuhu_AddApps.apk, fuhu_AppZone.apk, fuhu_Books.apk, fuhu_ChoreList.apk, fuhu_Crafts.apk, fuhu_Fan-a-tech.apk, fuhu_KidzMode.apk, fuhu_NabiCare.apk, fuhu_NabiCloud.apk, fuhu_NabiSpinletsPlusICS.apk, fuhu_NabiSpinletsPlusParentICS.apk, fuhu_NabiSync.apk, fuhu_OOBE.apk, fuhu_ParentalDashboard.apk, fuhu_SpinletPlusVideo.apk, fuhu_SwitchKids.apk, fuhu_TreasureBox.apk, fuhu_University.apk, fuhu_Videos.apk, fuhu_Web.apk, fuhu_nabiMD.apk
I used ES File Explorer to remove the files. First you have to go into the ES File Explorer settings and check all the boxes in 'Root Settings'. Alternatively you could use the file manager in the custom recovery we flashed in the first post or any other file manager with root capabilities.
If you need to get into fastboot or recovery manually, turn off the Nabi2 and then hold the vol+ and power button until the menu comes up. You use the vol- to navigate and the vol+ to select.
Nabi2 Teardown Thread: http://forum.xda-developers.com/showthread.php?t=2024105
Technical Specs for the Fuhu Nabi2
Display: 7-inch, Capacitive, Multi-Touch Display, 1024 x 600 Resolution
CPU: NVIDIA® Tegra® 3, Super 4-PLUS-1™ Quad Core with 5th Battery Saver Core
Storage: 8 GB, Expandable via MicroSD (Up to 32 GB); Plus 2 GB FREE Cloud Storage
Memory: 1GB RAM
Camera: 2MP Front Facing Camera; 720p Video
Battery: 3,850 mAh Rechargeable Lithium-ion Battery
Size & Weight: (with Drop-Safe Bumper) Width: 8.69 Inches (220.8 mm) Height: 6.05 Inches (153.7 mm) Depth: 1.14 Inches (29.08 mm)
Weight: 1.31 Pounds (596 g)
OS: Android 4.0, Ice Cream Sandwich
Network: Wi-Fi 802.11 b/g/n Bluetooth 3.0
Input / Output: Micro USB 2.0 Port, Mini HDMI MicroSD Compatible Cartridge Slot, 3.5 mm Standard Audio Jack, Built-In Microphone, DC Connector
Audio + Video Format:
Audio: MP3, AAC
Video: MPEG-4, H.263, H.264
Charger Output: 5vdc 2000mA
Charger Plug: 2.35mm OD and 0.7mm ID
Gmail App will force close if you don't have gmail checked in Settings>Accounts&Sync>Click on email>Checkmark Gmail.
Some games on the Fuhu Nabi2 use openfeint, to disable/block this you can install AdAway https://play.google.com/store/apps/details?id=org.adaway and add the following to the blacklist. This prevents the program from contacting the openfeint servers.
Code:
openfeint.com
api.openfeint.com
scoreloop.com
Some Games that use openfeint:
Code:
Fruit Ninja, Tiny Wings, The Moron Test, Robot Unicorn Attack, Championship Manager series, Bomberman Touch 2: Volcano Party, Fieldrunners, geoDefense, geoDefense Swarm, Minigore, Pocket God, Rollercoaster Rush, Jetpack Joyride
Here is a copy of the build.prop http://pastebin.com/5hCHd4bb
If you really, really messed up and have to restore the device back to stock because you didn't follow directions and lost wifi etc etc, I created a thread for restoring to factory from scratch. http://forum.xda-developers.com/showthread.php?p=35287470
ANDROID UPGRADING MESSAGE:
If you used a different gapps other than the one posted above or http://forum.xda-developers.com/showthread.php?t=2065878 you will probably get an "Android Upgrading" message every time you reboot. This is caused by two stray odex files that need to be removed/deleted. You can just install the new gapps package or take care of the files manually.
Code:
/system/apps/Gallery2.odex
/system/framework/com.google.widevine.software.drm.odex
Thanks for this man. The only thing I'd recommend is adding a piece, or a URL, on how to add the repo's for apt to pull those adb packages. These commands you step through are handy in *nix or Windows(-sudos). Thanks again!
Thanks, I didn't even notice that adb and fastboot were in the Universe repos as I had it enabled already.
I'll go double check then. I am running Ubuntu 13 off USB stick now and had enabled universe repo but maybe didn't get a clean update before checking for pkg. Will try again and see what's up...
I thought it required some custom repos, nothing preconfigured. If it is in universe my bad.
Thank you, for this thread was able to root daughter tablet with this tutorial. Tried the script in other thread but did not help. Thanks again
Sent from my NABI2-NV7A
Yup, its in universe, my bad.
Sent from my SPH-D700 using Tapatalk 2
Here is a quote from tikiral on installing ADB and Fastboot on Windows.
tikiral said:
Speaking of posts
@shizzy t499's post is really an excellent guide. The only thing you'd change if you're on Windows is that instead of doing the 'apt-get' you'll just download and install the SDK Tools from Google (http://dl.google.com/android/installer_r21.0.1-windows.exe) > Start up the SDK Manager.exe file from the install directory > Scroll to the very bottom > Check off Extras>Google USB Driver > Click Install packages...
After install, you should be able to go into Device Manager and update the driver's on any stray android devices and bam, you should be all set to go.
Thanks again for all the info @t499.
Click to expand...
Click to collapse
Finally got a chance to perform this on my Nabi 2. Installed with no problems what so ever and was quick too. I performed the install using Ubuntu 12.10. I found it much easier and less stressful this way. Now I have to do this to both my daughters Nabi 2 tablets.
I just finished up removing the Monarch UI apps for a normal tablet. Man I really love this tablet. I have almost all my G apps installed which I have been wanting for some time now.
Just follow the instructions to the letter and you can't go wrong with Linux. Now if we could get Jelly Bean on this it would be awesome! I posted a question about the Nabi XD in the Q&A and posted specs comparing both if anyone caught it. I am pretty sure it's possible if someone can get a hold of the XD and port it over.
Thanks again t499user and all the devs that worked to make this tablet usable.
Glad it worked for you! I would love to see some JB action on here.
Just wated to shout out and say thanks many texts were sent over getting my sons tablet rooted but we got it finally no thanks to WINDOWS, Linux is the way to go! Thank you so much for the support and late night time spent working on this! :good::victory:
Hi,
Thanks so much for your new gapp package, got it working great now. Can I check if I install the default nabi recovery image again will I loose access to google play store...?
caughron01 said:
Just wated to shout out and say thanks many texts were sent over getting my sons tablet rooted but we got it finally no thanks to WINDOWS, Linux is the way to go! Thank you so much for the support and late night time spent working on this! :good::victory:
Click to expand...
Click to collapse
I am so glad that we got it working, after switching to Linux it was pretty easy eh
dave2986 said:
Hi,
Thanks so much for your new gapp package, got it working great now. Can I check if I install the default nabi recovery image again will I loose access to google play store...?
Click to expand...
Click to collapse
The default recovery would only be needed if you have to apply a new OTA update. Other than that, I would just leave the TWRP recovery, but it has no effect on the play store.
t499user;36219934
The default recovery would only be needed if you have to apply a new OTA update. Other than that said:
I have to say, that I have never been able to reflash the stock recovery after I first flashed TWRP. Every time I tried, all I got was the defective kernelpanic-Android lying on his back and I had to reflash TWRP via fastboot. So far I installed all updates from zip-files via TWRP. However, every update resulted in a defective recovery and after every update I had to reflash TWRP.
If you know that, it takes very little time but I wonder what might have gone wrong in the first place....
If some of you could spread some light, please feel free!
Cheers
DiePlage
BTW: I've tried the stock recovery from this thread http://forum.xda-developers.com/showthread.php?t=2041224
Click to expand...
Click to collapse
DiePlage said:
I have to say, that I have never been able to reflash the stock recovery after I first flashed TWRP. Every time I tried, all I got was the defective kernelpanic-Android lying on his back and I had to reflash TWRP via fastboot. So far I installed all updates from zip-files via TWRP. However, every update resulted in a defective recovery and after every update I had to reflash TWRP.
If you know that, it takes very little time but I wonder what might have gone wrong in the first place....
If some of you could spread some light, please feel free!
Cheers
DiePlage
BTW: I've tried the stock recovery from this thread http://forum.xda-developers.com/showthread.php?t=2041224
Click to expand...
Click to collapse
Have you tried to restore the unrooted stock backup that was made in the beginning of jmz rootpackage, if you didn't make 1 or use it. There are some stock posted. Unrar and put in TWRP/BACKUPS/your number folders and restore from TWRP recovery RESTORE. I have and was completely back to stock.
You can find stock in jmz files but it is any older version. Look thru the many post tho and others have posted stock 1.9.37
http://forum.xda-developers.com/showthread.php?t=1905674
ALD3 said:
Have you tried to restore the unrooted stock backup that was made in the beginning of jmz rootpackage, I have and was completely back to stock.l]
Click to expand...
Click to collapse
I have tried to just flash the stock recovery. I thought this should be enough to do OTAs. Maybe I could find another stock recovery besides the one noted...
DiePlage said:
I have tried to just flash the stock recovery. I thought this should be enough to do OTAs. Maybe I could find another stock recovery besides the one noted...
Click to expand...
Click to collapse
Forgot that I had 1 downloaded already. Try this 1 from my Box. Stock 1.9.37
https://www.box.com/shared/but3ihiutkw62pa4gayd
DiePlage said:
Android lying on his back and I had to reflash TWRP via fastboot.
Click to expand...
Click to collapse
That is the stock recovery, it will happen that way if you don't install root.zip, and possibly after an update.
To get to the menu of the stock recovery, after getting to android laying down, you push the vol buttons.
Really hoping someone can help me. Im trying to Root the Nabi 2 on my Mac. Im following the command lines, without the "sudo" text, and when i flash the recovery, my terminal says waiting for device, and nothing happens.
i know my adb is working, bc it detects the Nabi 2 when i run the ADB devices command, and it will reboot into the bootloader.
Any suggestions??
Edit
Found this link, and all worked out. Didn't have to root, or flash recovery or anything like that, but i only really need youtube as of right now, so it worked well for me
http://everythingnabi.blogspot.ca/2012/08/googlie-booglie.html
Dear open developers community I managet to fully root BlueBerry NetCat M-12 Tablet PC (a.k.a rebranded Cube H30GT) using "remount" exploit, here is my contribute:
{
"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"
}
REQUIREMENTS:
* Android SDK with ADB (guess you have this, if not, main files are included in permaroot.zip attached below)
* RockChip RK3066 USB Driver (see attachments below)
* Root/UnRoot script (thanks to Bin4ry from this thread, see attachments below)
* Micro USB Cable to connect Tablet and Windows Desktop PC (Linux is unsupported for now due to manufacturer limited driver distribution)
WARNINGS
1. Using this tutorial will make firmware/software changes on your device(s) but I am not responsible for any damage it could cause.
2. Following steps below will probably VOID YOUR WARRANTY. Read carefully your reseller warranty terms and conditions, and make your decision. It is all up to you.
3. I am not obligated to respond to future questions and/or support, it is my time and good will. If you must, ask here in this thread, there is no need to send me private messages to me because i wont read them at all.
4. You will spot that i dont recommend making any nand backups in this howto - is because I am not aware of any working method for backup M-12. I onlu can imagine dumping whole partition images to your EXTERNAL_SD and flashing back through bootloader but I did not tested that for now.
#GET ROOT
STEP-BY-STEP HOWTO
1. On your tablet PC go Settings -> Developer Options -> Turn on USB Debugging
2. Now You need to manage your Android Debug Bridge recognize your Tablet PC. You can check if it already works by typing this command in command prompt (in ADB folder, or wherever if you extracted adb into windows/system32)
Code:
adb devices
It should give you list of attached devices (something like this: 0123456789ABCDEF device) you should recognize your device if is connected. From my experiences it wont work the way manufacturer described, therefore you need to install patched RK3066 SoC driver you downloaded (this post below). To do so you must right click on My Computer -> Manage -> Device Manager, find your Unknown Device and install driver manually by selecting search folder manually, where you extracted RK3066_ADB_PATCHED.rar content respectively to your OS version (use correct 32-bit or 64-bit driver). Reboot your PC, go to device manager to check if Android Debug Bridge is there:
And You can repeat "adb devices" once again in adb to verify:
3. Now is time to obtain temporary root. To do so, simply navigate command prompt to wherever You extracted adb.exe and type following command:
Code:
adb remount
It uses common JB exploit, which exists in BlueBerry NetCat M-12, alowing you to get temporary root access via ADB shell until next reboot. You can stop at this point and push any system file You want (ie /system/etc/hosts) and set permissions. But if you want permanently rooted device, you need to push SuperSU.apk, su, busybox,... manually via adb before next reboot. Lucky for you, there is a script (permaroot.zip thanks to Bin4ry) which can do it all automatic with just few clicks. Download it from attachment below, extract somewhere on your hard drive run permaroot.bat and have fun.
Comming soon...
++ Flashing through Bootloader (via RockChip Batch Tools) HowTo ++
++ Illustrated Hardware disassembly guide ++
++ There is one custom ROM ported for another device and tested by me, which works in M-12 like a charm. It is purified JB ROM, rooted and without bloatware. I will post it ASAP ++
++ If i be able to obtain original Blueberry firmware dump, i will make CWM Touch based recovery image. Any interested owner of original BlueBerry NetCat should supply me with F/W dump, so if you are one, PM me please ++
++ If I be able to make Cube CWM Touch recovery work I will share (I managed to extract and install it from supersport900 ROM but it wont mount partitions for some reason) ++
BlueBerry NetCat M-12 Disassembly Guide
+++ BlueBerry NetCat M-12 HardWare Assembly +++
Tools needed:
1 x 1mm Torx Screwdriver (pictured below)
2 x sharp plastic departer for simultaneous two-side gently disassembling plastic parts (any Credit Card or guitar pick will do)
Step-by-Step Guide for servicing (H/W repairs, forced bootloader, etc) your BlueBerry NetCat M-12:
* Torx screws are located along port side, noted the difference on Torx and Cross screw types between some devices - Picture 5
* Some BlueBerry NetCats M-12 dont have left speaker - Pictures 20, 25 and 26
* BlueBerry NetCat M-12 has different stamp (OEM Logo) on backside - Picture 14
** Note LED and short circuit testpoint locations for forced bootloader mode which will be described later in more details - Pictures 25-32
Picture 1:
Picture 2:
Picture 3:
Picture 4:
Picture 5:
Picture 6:
Picture 7:
Picture 8:
Picture 9:
Picture 10:
Picture 11:
Picture 12:
Picture 13:
Picture 14:
Picture 15:
Picture 16:
Picture 17:
Picture 18:
Picture 19:
Picture 20:
Picture 21:
Picture 22:
Picture 23:
Picture 24:
Picture 25:
Picture 26:
Picture 27:
Picture 28:
Picture 29:
Picture 30:
Picture 31:
Picture 32:
Picture 33:
There is a PDF with all images in attached archive.
+++ClockWorkMod based recovery image for BlueBerry NetCat M-12+++
CWM Touch 6.0.2.7 (Thanks to Typhoon.X)
CWM Touch is Direct-Touch-Input CWM Recovery image: you can use touch gestures to navigate through menus, but I still prefer old-fashioned way of navigating through menus by using Volume +/- for <UP> and <DOWN>, and Power button as <CONFIRM> which is also available on our devices.
WARNINGS
1. Using this tutorial will make firmware/software changes on your device(s) but I am not responsible for any damage it could cause.
2. Following steps below will probably VOID YOUR WARRANTY. Read carefully your reseller warranty terms and conditions, and make your decision. It is all up to you.
3. I am not obligated to respond to future questions and/or support, it is my time and good will. If you must, ask here in this thread, there is no need to send me private messages to me because i wont read them at all.
4. You are welcome to make backup(s) before make any change to your device; You can export partition(s) dump or make nandroid backup via CWM based recovery image if you have it allrady installed.
Install:
1. Make sure you have installed RK3066 drivers;
2. Download ClockWorkMod.zip, extract, run RKAndroidTool.exe.
3. Reboot your BlueBerry NetCat M-12 in Flash Mode (turn on device by holding Volume- and Power Button or push "Reboot to Flash Mode" button in RKTool)
4. Push "Flash ROM" button like on image below (all settings are stored in config.cfg so You dont need to change anything):
After procedure is finished (cca 15 seconds), device will be automatically rebooted into CWM Recovery, so it's highly recommended making first nandroid backup.
Usage:
If your device is rooted, you can reboot your device into CWM recovery by typing following commands in terminal emulator:
Code:
su
reboot recovery
Or by using any 3rd party rebooting widget/app, which allows rebooting into recovery.
However, if your device is not-rooted, you can reboot into CWM recovery by typing following commands which exploit temporary root access via Android Debug Bridge (adb.exe on your PC, drivers must be installed):
Code:
adb.exe reboot recovery
or
Code:
adb remount
adb shell
su
reboot recovery
Download CWM Touch based recovery image from Google Drive: ClockWorkMod or attachment below.
Be aware that bootsplash will be changed as you need to replace misc.img, so dont panic if you see Cube logo instead of NetCat.
Hey, CyberianIce, thank you for your contribution for this device, since it's really hard to find anything verified out there, and xda is alwas the safest choice.
I wanted to ask you if you could share the info, or link maybe, to that ported ROM you tested on Blueberry, since I don't wont to brick my device by trying an untested ROM.
Thanks in advance!
I can re-upload from my HDD because I forgot original URL, when I got day off my work.
/CyberianIce via TapaTalk HD
That would be amazing, thank you! And if you could write something about the ROM (when you have free time, of course) just so that I know what I'm installing..
Hi, i wonder how to make a hard reset on this devices, i have tried the normal way, volume(-)(+) + power but nothing is working. Can someone help me? Thanks!!
Hi, CyberianIce, I was wondering if you'll have time soon to upload the ROM, if it's not too much trouble. Thank you!
So far I found this Firmware image working best on NetCat M-12: http://www.rockchipfirmware.com/sites/default/files/cube_u30gt-h_V1.11_TNT_R1.zip
For Flashing use this tool: http://www.rockchipfirmware.com/sites/default/files/RKBatchTool1.5en.zip
(Credits: http://www.rockchipfirmware.com/)
It is great because you can flash it vie Rockchip Batch Tool which means its very useful for debricking. It is 4.1.1 from Cube U30GT-H with all this tweaks:
Brief Description:
-Rooted
-Based on stock rom (2012.12.28)
-App partition is Larger
-Build.prop mod based on SGS II SGH-i777 for improved market
-Added Permission Files for improved market
-Removed Chinese Apps
-framework.jar mod for better gameloft compatibility (Asphalt 7 should now work)
-Added SuperSu, gallery with picasa support, ESfile Explorer, english dictionary fix
-Simplified and pretty boot animation
-Changed Annoying Keyboard Key-press sounds... now they are less annoying (based off Cyanogen sounds)
-Default Background should be changed
-Changed "browser" start page to our Google paid search. Use it (free to use for you) to search the web and you will be helping to support us as we release more free firmware. Can easily change this if you want.
Click to expand...
Click to collapse
Afterwards one can flash CWM based recovery image following tutorial from this post
[ROM][RK3066][U30GT-H]BlueBerry NetCat M12
Based on latest original Cube U30GT-H ROM debranded from BlueBerry NetCat M12
Tested on many CUBE U30GT-H devices
Debloated
Removed China
Custom tuned Kernel for optimum performance and stability (up to 15k points in AnTuTu Benchmark)
Increased /data partition size to 2GB instead of 1GB (reduced internal sdcard partition to 12.5GB instead of 13.5GB)
NetCat BootSplash
Custom android bootanimation.zip
Fully working CWM Recovery 6.0.2.7
HOWTO:
1. Shut down your tablet and start it by holding down Volume + button and insert USB Cable with PC. RK Device will apear, if you have no drivers you can find them in archive.
2. Navigate to RKDevelopTool_v1.35 folder and run RKAndroidTool.exe
3. Click Erase IDB and wait for finish
4. Click Run and wait for finish
5. After procedure is complete, if your tablet don't start automatically in CWM, remove USB and shut down tablet by holding POWER button for 8 seconds (you will hear silent *click* sound from tablet as signal it's off). Now download CWM Base from this XDA post put tablet in download mode (VOL+ and USB CABLE) and flash this recovery (run RKAndroidTool.exe, push Flash ROM button). It is very same recovery from this ROM, but after this flashing is finished, tablet will boot into CWM automatically on it's own.
6. Now install ZIP files from after_install folder via CWM recovery. Format NAND is required if you first time using 2GB Data mod, and int2ext is required for some devices which reported switch between internal and external SD card. You must use an external SD Card for flashing ZIPs and search for files in both internal and external sd card in CWM as you still dont know how CMW see your SD card.
7. Reboot System. All done!
DOWNLOAD
Note: If you are used increase /data to 2GB MOD before, you can just install this firmware via RKAndroidTool. If your /data partition was 1GB before, you may need to install patches from folder after_install via CWM recovery.
{
"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"
}
This method will, when completed, will provide you with root and an unlocked bootloader, with fastboot available. It is a somewhat involved process, but the majority of the process has been simplified as much as possible.
WARNING!!!!This replaces your current bootloader with a debug bootloader. If you attempt to lock this bootloader you may brick your device.
Currently AT&T(H910) and Sprint(LS997) cannot return to stock because no KDZ files are available.
Disclaimer:
Once your phone is unlocked, it will no longer be covered by LG warranty @me2151.
As we cannot guarantee the proper operation of our hardware with custom software, we are not able to maintain the full scope of warranty for your device after you have unlocked the bootloader.
Because of that we have a responsibility to let you know that defects which may result from, or were caused by custom device-software may not be covered by LG warranty @me2151.
LG @me2151 can no longer guarantee the full functionality of your device after you unlock the bootloader. Unlocking your device may cause unexpected side effects that may include but are not limited to the following:
***Your device may stop working.
***Certain features and functionalities may be disabled.*
***Your device may become unsafe to the point of causing you harm.
***Your device becomes physically damaged due to overheating.
***The behavior of your device may be altered.
***Some content on your device may no longer be accessible or playable due to invalid DRM keys.*
***All your user data, settings, and accounts may disappear. (Therefore, we recommend that*you*backup all your data).
** -*Software updates delivered via LG FOTA (Firmware Over the Air) or Web Download services may not work on your device anymore.
LG @me2151 will not be responsible for the damages caused by any*custom software being flashed to your phone.
Known Issues:
AM&FM Radio no longer works
Boot time higher
No way to revert to stock(LS997/H910)
Possible overdose of root awesomeness!
Maybe more. Let us know!
Links:
- v20-root.zip
- TWRP
- Terminal Emulator
- Newest SuperSU(SuperSU v2.78 SR5 or greater is needed)
-Stock LS997 rom. for Sprint users only. (Fix's numerous problems)
Pre-requisites:
- ADB and fastboot setup and Installed
- Terminal Emulator installed onto the phone.
- The above links downloaded and SuperSU placed on the SD Card.
Working Devices:
- Verizon (VS995)
- Sprint (LS997)
- ATT (H910)
- Korean(F800L)
Note: International Variants (E.g.H990DS) May get supported in the future, but are currently being worked on at the moment. If you attempt to use this method on Unsupported Devices(any V20 not listed in working devices) then you are in uncharted territory. It will almost definitely brick your device. YOU HAVE BEEN WARNED!!!!
This will tutorial will be broken up into 2 sections, during the second section the instructions will differ depending on the variant of the phone you are using.
- Unlocking the Bootloader:
1) Copy all the files from inside the "Required Files" (Inside the unzipped "v20-root" folder) and paste it into your active ADB directory. Then copy and paste twrp-3.0.2-1-us996.img to your active ADB directory.
2) If you currently don't have Terminal Emulator then go and download and install now.
3) Plug your device into the computer and verify ADB is working. Then;
On Windows, double-click "RUNMEFIRST.bat, DO NOT CLOSE THE LOG WINDOW THAT OPENS, then double-click "Step1.bat"
On Linux/MacOS ("#" Signifies a comment below)
Code:
./RUNMEFIRST.sh
# OR
bash ./RUNMEFIRST.sh
Open a Separate Terminal next to the RUNMEFIRST terminal, then type:
Code:
./Step1.sh
# OR
bash ./Step1.sh
When you run The sh or Bat files there will be a Permission denied error on 2 files: Flatland and Flatland64. This is normal and nothing to worry about.
3.5) Wait for a shell prompt, then type (or copy):
Code:
run-as con
chmod 0777 /storage/emulated/0/*
4) Open Up Terminal Emulator
Type:
Code:
id
Check if context is "Untrusted_app"
If "Untrusted_app" is displayed, Continue:
Type into Terminal Emulator:
Code:
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
If it doesn't show up as "Untrusted_app", repeat the above steps from Number 1
5) Watch the RUNMEFIRST dialog for when it tells you to run Step2. Then;
On Windows, double-click "Step2.bat"
On Linux/MacOS, type:
Code:
./Step2.sh
# OR
Bash ./Step2.sh
Once step 2 is completed, you'll be in bootloader, procced to "Flashing TWRP" section to continue.
Note/Warning: Verizon Users Vibrator will be constantly going off, until the whole process is complete (Past Android Setup Wizard).
- Flashing TWRP and Fixing Varient Issues:
1) Run Step3, so TWRP can be flashed and a working boot.img flashed (Fix's screen problem) by;
On Windows, double-click "Step3.bat"
On Linux/MacOS, type:
Code:
./Step3.sh
# OR
Bash ./Step3.sh
******Sidenote******
If you get message saying <waiting for device> on Step3.bat then you do not have the fastboot drivers installed(you may have the program but not the drivers).
To fix: Go to your device manager while the device is connected in fasboot and right click the item that says Android and select update drivers. Then select from internet. and let it install the drivers then try step3.bat again.
*************
2) After you're rebooted, and back at the main lockscreen, type;
Code:
adb reboot recovery
Your device will reboot to an LG screen. Keep checking adb devices for your device.
Then type:
Code:
adb reboot recovery
***********
Device should display a red triangle and say corrupt, then it will boot into TWRP.
3)Once in TWRP, Press Cancel on the password prompt and then swipe to allow system modifications.
Note:If you wish to make a back up now, you MUST save it to your SD card, and you cannot backup the data partition.
After the backup is complete, return to the main menu and hit wipe then select ?Format Data?, and follow the instructions there.
4) Steps below will differ, depending on what model you have, choose the correct model and follow its method.
- Verizon(VS995) and ATT(H910):
4.1) Flash SuperSU.zip
4.2) Go back to Main-menu > Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Wipe > Advanced > Check Dalvik, Data and Cache > Slide to wipe
4.4) Go back to Main-menu > Reboot > System
- Sprint(LS997):
4.1) Go to Wipe > Advanced > Check Dalvik, System, Data and Cache > Slide to wipe
4.2) Go back to Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Main menu > Install > LS997 Stock Rom then Flash SuperSU.zip
4.4) Go back to Main-menu > Reboot > System(you will get static on boot. this is normal)
4.5) Sprint users are Done at this point. You do not need anything else. Everything will work except static on boot.Note:Any following Instructions are for all devices again.
5) During reboot you will get a Red Triangle with a "!" inside, this is normal (First boot after flashing SuperSu will show the Red triangle twice.Wait for system to boot (this will take awhile). It may appear like the system has frozen but it has not. JUST WAIT!
*****VERIZON USERS******
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot bootbackup.img
fastboot reboot
**************
*****ALL USERS*****
If you encounter a "Secure Boot" Password then booting the first time you did not Format data properly.
To reiterate: To properly decrypt the device you need to boot into TWRP and go to WIPE->FORMAT DATA and you will be prompted to type "yes" to format and decrypt.
**************
Once you are booted and have proceeded through the setup wizard, re-enable Android Debugging (ADB) if not already enabled.
Type:
Code:
adb reboot bootloader
6) Once inside bootloader, Type:
Code:
fastboot flash boot bootbackup.img
When it says finished, Type:
Code:
fastboot reboot
The device will boot back into system.
WARNING:This is a required step for non sprint users, it prevents background crashes and fix's battery drain. If you do NOT follow this then the device will have bad battery life, be laggy and crashes will occur regularly.
7) Once full booted back into android, Type;
Code:
adb reboot recovery
8) Once TWRP loads, Then;
- Flash SuperSU.zip
- Go back to Wipe > Advanced > Check Dalvik and Cache > Slide to wipe
- Go back to Main-menu > Reboot > System
You now should have a rooted LG v20, download your favorite root checker app and verify root.
Note:For a root app to work, it will have to support Systemless root.
Contributers/Developers:
@me2151(General)
@glitschi667(General)
@EMSpilot(Debug device) #3
@elliwigy(Ideas and testing) #5
@Matt07211(Formatting this awesome guide and helping out with general stuffs)#4
@1619415(Awesome Santa Pic at the top!)#8
Alright guys. Its time for some fixes!!!
For our known issues:
Comfort view, youtube, boot time and possibly radio.
All fixed by flashing the AT&T H918 Konverged Kernel.
Keep in mind this is a temporary fix until I get a full custom kernel made for our devices(or at least a way to make the screen work out of box that we can use on other kernel sources).
To use this kernel on our phones you need to download the zip, Place on sd card, reboot to twrp, install the zip, wipe dalvik/cache then reboot.
You WILL GET STATIC ON EVERY REBOOT!
After the phone is booted put the screen to sleep by pressing the power button and cover your proximity sensor(so your 2nd screen turns off) then turn your screen back on. Your screen will work until reboot. If you reboot you will have the static again. Just follow the steps I just listed above to get the screen working again.
--------
Other Updates.
I believe I have finally found a way to revert sprint devices sprint devices to unrooted stock. I will be testing the method on my phone in the next couple days.
WooHoo!!!! I bricked attempting to revert!
So heres an update for you guys. Reverting has been confirmed possible using KDZ files for your specific models. Confirmed working for KDZs are H915, VS995 and some others. I do Have a new v20. I am going to pull the stock sprint files tomorrow and see what I can do about making that work.
Nicely done Guys.
@me2151(General)
@glitschi667(General)
@elliwigy(Ideas and testing)
@Matt07211(Formatting this awesome guide and helping out with general stuffs)
@1619415(Awesome Santa Pic at the top!)
I am extremely happy that the V20 User Debug I invested in worked out!
Enjoy everyone!!
Cheers
Reserved
Reserved lol
Awesome work guys!
Sent from my LG-LS997 using Tapatalk
reserved
---------- Post added at 04:51 PM ---------- Previous post was at 04:51 PM ----------
pdaddy said:
Awesome work guys!
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
****
Good job @me2151 !!!:good::good::good:
Awesome! Now all the fun can begin!
Thanks for all your hard wprk on getting us root!
Thanks,
Chaz187
Sent from my LG-LS997 using Tapatalk
So awesome to hear, you guys are amazing. Its possible the dev with the h915 is waiting for the firmware update (we're told in time for the holidays?!) that would enable LTE on wind to see if this still applies. Nevertheless, thanks, i dont remember the last time i read so much. Lol
Sent from my LG-H915 using Tapatalk
Ooo Santa you so dirty.. Can't wait to do this
Sent from my VS995 using Tapatalk
SHABBA JOTS said:
So awesome to hear, you guys are amazing. Its possible the dev with the h915 is waiting for the firmware update (we're told in time for the holidays?!) that would enable LTE on wind to see if this still applies. Nevertheless, thanks, i dont remember the last time i read so much. Lol
Sent from my LG-H915 using Tapatalk
Click to expand...
Click to collapse
From the last I hear from him. The bootloader unlocks and twrp installs BUT he has no service(he is Rogers) So he is looking into all that.
AWESOME job, everyone! Thanks so much for this-- I admit I may wait a little while for feedback before trying my own unit, but given that I jumped on the V20 early in hopes that if any version is hacked it'll be the earliest firmwares, I can't imagine it'll be too long before I'm back to enjoying my phone the way I like it!
Definitely will be sending some coffee money along, even though I wasn't in any of the bounties...
Damn I've been waiting for this soooo much but there's only thing. I don't now crap about LG phones I've been a Sammy fanboy for 7 years lol. Guess I'll have to wait till my boy can do it.
Sent from my LG-LS997 using Tapatalk
---------- Post added at 08:13 PM ---------- Previous post was at 08:06 PM ----------
EMSpilot said:
Nicely done Guys.
@me2151(General)
@glitschi667(General)
@elliwigy(Ideas and testing)
I am extremely happy that the V20 User Debug I invested in worked out!
Enjoy everyone!!
Cheers
Click to expand...
Click to collapse
And thank you for purchasing that expensive out of pocket device.
Sent from my LG-LS997 using Tapatalk
Subutek said:
Damn I've been waiting for this soooo much but there's only thing. I don't now crap about LG phones I've been a Sammy fanboy for 7 years lol. Guess I'll have to wait till my boy can do it.
Sent from my LG-LS997 using Tapatalk
---------- Post added at 08:13 PM ---------- Previous post was at 08:06 PM ----------
And thank you for purchasing that expensive out of pocket device.
Click to expand...
Click to collapse
to be honest theres nothing really lg specific besides the files themselves lol.. of course you never use Odin outside of Samsung lol..
majority of it is pc bat or adb commands and then you got your typical twrp stuff but hey, best to have your buddy do it if youre not comfortable
Hey guys I need a little help, last step I was able to complete was running "Step3.sh, after reboot I'm unable to get into recovery mode. does anyone know the manual steps to get to recovery mode?
I also continue to get the popup "com.android.phone" has stopped.
No mobile service
hoopsdavis said:
Hey guys I need a little help, last step I was able to complete was running "Step3.sh, after reboot I'm unable to get into recovery mode. does anyone know the manual steps to get to recovery mode?
Click to expand...
Click to collapse
I'm assuming you're on Mac/Linux. If so, in terminal verify connection with "adb devices". If you're connected fine, enter "adb reboot recovery"
I started but wouldn't get any feedback when I would double RUNMEFIRST or Step 1.... I don't know if windows 10 matters.
I'll try again a little later tonight.
My device was connected and found; adb devices
oh yeah, im also running minimal adb and fastboot.
http://forum.xda-developers.com/showthread.php?t=2317790
Thank you guys for the hard work. So happy to have hotspot working.
dc.wash95 said:
I'm assuming you're on Mac/Linux. If so, in terminal verify connection with "adb devices". If you're connected fine, enter "adb reboot recovery"
Click to expand...
Click to collapse
I'm actually on windows
hoopsdavis said:
I'm actually on windows
Click to expand...
Click to collapse
Well in that case, you probably should have executed the ".bat" not the ".sh"
I'm running Windows 10, and successfully followed the guide. My device is past boot currently, and is installing apps from a Google backup.
This tool is out of date. See the main R9S thread for an updated tool by Wu Xianlin which gives you an improved TWRP recovery and access to more ROMs.
Original post is below for historical purposes only.
Oppo R9S (Chinese version) TWRP installation tool
Only works on Chinese OS release 005 which can be downloaded here and flashed in stock recovery.
Earlier versions will not work, nor will later versions. It has to be this specific version.
P̶r̶o̶b̶a̶b̶l̶y̶ doesn't work on international editions either.
DOWNLOAD - R9S_TWRP.zip - V1.01
DOWNLOAD - R9S_TWRP.zip - V1.0
Changelog
1.01 - Tweaked timings to try and improve success rate
1.01 - Changed how text is output to hopefully improve appearance on Windows 7
This script uses an exploit by Chinese developer Wu Xianlin to gain temp root, then it flashes his TWRP build that works on the R9S despite the locked bootloader.
From there you can attempt to perma-root your phone, install a custom ROM etc. etc.
Thanks to the following XDA members, without whom this would not have been possible:
jacksmack
celoxocis
{
"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"
}
Antivirus issues
Some AV's may complain about this file containing a Trojan. They are technically correct. It's called "dirtycow" and is being used in the wild to hack into Linux systems. It cannot affect Windows systems, but I use it to hack a linux-based system (your phone)
If your AV refuses to let my script run you will have to disable it temporarily. Feel free to read through my script (root1.bat) to check what it is doing.
Useful things to flash in TWRP
CyanogenMod13 - by Wu Xianlin
Stock Recovery - by Wu Xianlin
GApps (ARM64) - by opengapps.org
Updated basebands, ripped from ColorOS
Use these only if you have issues with phone/GPS/etc. after installing CM. Otherwise leave alone.
[2017-01-11 v0180] - released ROM (China) - by me!
[2017-01-24 v1470] - ALPHA ROM (China) - by me!
Note: The version number on basebands stays the same, but the MD5s are different. No idea what has changed, but they work!
Unbrick instructions:
Does not work in Windows 10. Tested working in Windows 7
Download this unbrick package
Install the quallcommmtkdriver package
Run daanav-enabler as administrator
Run msmdownloadtool as administrator
Click through any timeout error you get
Click on the titlebar of MSMDownloadTool and press F6 to enable the options
Fully power down your phone by holding vol-, vol+ and power for 10 seconds
Hold vol- and vol+ while connecting the USB cable (use the stock Oppo cable)
MSM should now show your phone.
Press F5 to decide what to flash. For the first attempt choose "All except userdata".
Click the start button.
After 5 minutes your phone should reboot into ColorOS.
If ColorOS hangs on boot, then repeat the above staps and this time flash all, including userdata. This will wipe your photos etc. sorry!
This will leave you on V004 of the OS. You will need to upgrade to 005 before attempting to root again.
Can I request a version of this that stops at permanent rooting? Unless you think there would be a problem with the fact that I intend on using it on a r9s plus.
Or a link to what I maybe overlooked, in case it already exists.
Unfortunately this program doesn't perma-root. It gains a temp root and uses that to flash TWRP. TWRP can then be used to flash a custom ROM or a rooting tool.
It also doesn't unlock the bootloader. Wu Xianlin somehow managed to make a version of TWRP that the locked bootloader is happy with!
however if you edit root1.bat and scroll down to line 181. Change it from:
Code:
type root3.txt | adb shell /data/local/tmp/root2.sh
to:
Code:
adb shell /data/local/tmp/root2.sh
Then the script will just drop you to a root shell. Unfortunately you are then on your own as to how you get perma-root.
I have no idea whether this method will work on the R9SPlus. In theory it should do but I've not tried it. I won't be held responsible if you brick your phone and probably won't be able to help, though you should be able to do a three-finger reboot and then boot into recovery and reflash ColorOS.
Optional modifications you can make that will make the script neater:
You can also remove lines 178 and 179
Code:
echo Copying TWRP
adb push r9s-twrp-3.0.2.0-20170107.img /sdcard/twrp.img
and change line 184 from
Code:
pause
REM ---- CHINESE TWRP HELP ----
to
Code:
pause
exit
REM ---- CHINESE TWRP HELP ----
I will take your "I have no idea if this will work fo r9s+" at face value and try to be patient for something more certain, thanks for your contribution nonetheless
I saw the translation you posted and am a bit depressed Wu recommended to return the phone...
Oppo make amazing hardware but terrible software that is never updated. I used to be ok with this because they actively encouraged rooting and custom ROMs but this change in attitude from them makes it very hard to recommend the phone.
I would be interested to know if this exploit does gain root on the Plus. In theory it should work, and there's also a decent chance that TWRP will too as the hardware is very similar, but will require someone very brave/stupid to try it
BTW. Anyone who is going to try this on the Plus. Ensure you have a flashable .ozip of a working ColorOS (full install, not OTA) saved to internal storage as the stock Oppo recovery is a POS that doesn't provide ADB, MTP or USB.
If you end up wrecking your OS and don't have that image in place ready to flash from recovery you are screwed.
Likewise do not flash TWRP until you are sure that your OS is still bootable, and also take a dump of the stock recovery first! (and post it in the other thread as it's bloody useful to have!)
Sent from my OPPO R9s using XDA Labs
Hi the Unbrick pack RAR is corrupted and can not unzip.
Also there is Trojan in DOWNLOAD - R9S_TWRP.zip - V1.0 - Dirtycow file and the NOD Antivirus is deleting this file.
Please advice how to proceed ?
NOD is correctly detecting that this is a hacking tool using a well known exploit (dirtycow).
Since you actually want to do that, you're going to have to disable NOD until you're done.
Sent from my OPPO R9s using XDA Labs
Lum_UK said:
NOD is correctly detecting that this is a hacking tool using a well known exploit (dirtycow).
Since you actually want to do that, you're going to have to disable NOD until you're done.
Sent from my OPPO R9s using XDA Labs
Click to expand...
Click to collapse
Hi I got to somewhere but I am stuck now...
Please check the pic and advice how to install the CyangenMode. (I have uploaded the pic in your thread in Oppo Community forum please check it there because I am new here and can not post with external links..)
Sorry for the inconvenience. Looks like I am few steps away to finish the job but something is missing...
Goro1234’s image: http://s27.postimg.org/8usudi9g3/IMG_20170207_133854.jpg
You need to do a wipe data/cache/dalvik as CM won't install on top of incompatible data.
Note that this will wipe your installed apps, settings, app data, saved games etc. but will not wipe your photos, music, downloads or anything else saved to internal storage.
You may wish to take a backup from within TWRP first. Apps like Titanium Backup and Nandroid Manager are reasonably good at restoring apps and data from a TWRP backup.
Also don't forget to install GApps
Sent from my OPPO R9s using XDA Labs
For the unbrick package you need 7-Zip to extract it.
Lum_UK said:
`Also don't forget to install GAaps`
Hi I am on Cyanogen now !!! Thanks for the help. Can you please tell me now which is the correct gapps version for our device. I have installed random one which does not make connection with google. I have tried to install ARM 64, but cant flash because systems says that is incompatible... Thanks
Click to expand...
Click to collapse
Select ARM64, android 6.0 and whichever variant you like (I recommend the Pico version)
Sent from my OPPO R9s using XDA Labs
Sorry for the English, I made a mess with the phone, after unlocking everything, and held the phone for several days with CM13, I saw that GPS was not working, so vovelo return to the origin, but now I can not installing Stock Recovery more to put the stock rom, I tried to do unbrick, but when I press start of msmdownloadtool, the program stops and closes. If some kind soul gives me some advice. Done everything under win 7 reset. Thank you so much Gianfranco.
GPS should be working. I'm using it all the time on CM13 as my phone is my satnav.
Maybe wipe and reflash, or try one of the baseband updates?
Sent from my OPPO R9s using XDA Labs
Now, the problem is more to do so that I can not leave,
I installed through the files Stock TWRP Recovery as a boot, and I hand the boot source and installing the original rom, after the reboot remains on oppo screen. what can I do. Thank you so much Gianfranco.
hold all three buttons for 10 seconds to forceibly power off the phone and then try to boot to recovery.
If you get the Oppo recovery then try to do a factory reset and then flash the stock ROM,
if you get TWRP then try to flash Cyanogen.
If you can't do either then you're going to have to run the unbrick tool. Do you have another PC you can try it on?
Thanks, but I have tried various solutions, when I install the boot ROM from stock, is successful, the reboot hangs installation applications. I wanted to know if you can other software for unlocking. Thank you very much for giving me some advice, thanks ancora.Gianfranco.
Hey guys! Today is a big day for Alcatel 1 owners, since the root is possible. Follow my steps to root your device!
NOTE: This is using a treble gsi rom
[DISCLAIMER] . I am not responsible for dead phones, SD Cards, Alarm clocks failing, etc. You have been warned!
WARNING: Your data will be lost during the process!
=====================================================================================
[Unlocking The Bootloader]
1 - Open Settings, go to About Device and tap Build Number 5 times
2 - Go back, tap on System, Advanced and Developer Options
3 - Check OEM Unlocking
4 - Turn off your phone
5 - Hold down the PWR and VOL+ buttons until the alcatel logo appears
6 - When the logo appears release the PWR button, while holding the VOL+ button
7 - In the recovery menu select reboot to bootloader
8 - In your pc with Minimal ADB and Fastboot installed type "fastboot oem unlock" (w/out the quotes)
9 - On the phone click the VOL+ button
10 - Reboot your phone and wait until the phone factory resets
=====================================================================================
[Installing LAge 16 (Android Pie)]
1 - Go to settings, and search factory
2 - Tap on Factory Reset
3 - When the factory reset is done, turn off the phone
4 - Hold down the PWR and VOL+ buttons until the alcatel logo appears
5 - When the logo appears release the PWR button, while holding the VOL+ button
6 - In the recovery menu select reboot to bootloader
7 - Download https://sourceforge.net/projects/an...910-UNOFFICIAL-treble_arm_avN.img.xz/download to your computer
8 - Open Minimal ADB and Fastboot and type "fastboot -u flash system filelocation.img" (w/out quotes and replace filelocation.img with your "lineage-16.0-20190910-UNOFFICIAL-treble_arm_avN.img" file location
=====================================================================================
[Rooting]
1 - Open Settings, go to About Device and tap Build Number 5 times
2 - Go back, tap on System, Advanced and Developer Options
3 - Tap in Root Access and select ADB and Apps
=====================================================================================
If you have reached this part, congrats! You have successfully rooted the Alcatel 1
{
"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"
}
Thanks dude, that worked perfectly.
Any idea how to get GAPPs working?
What if I only want to root the phone without installing Lineage OS? I just want to remove the bloat apps that came with the phone e.g. Youtube Go, Asistent Go, etc.
I bought a cheap Alcatel 5033D-2BALWE1 from amazon warehouse deals and did not expect to be able to install a custom rom, very nice. But I do have few questions:
Does the rom you linked have some adjustments for this hardware or should any other GSI image work just as well?
Does all the important hardware work (basically LTE, wifi, bluetooth, gps, microphone + speaker + headphone jack, camera)?
Any trusted source for a stock rom that can be flashed with fastboot? There's one on alcatelfirmware.com but not sure how legit it is...
Because amazon warehouse deals sold them so cheap I bought 2, so after trying it I can answer some of my questions. First, my fastboot here (linux) doesn't have a -u switch, but it worked fine without it.
I tried andy yan's build first. Rotation sensor, display brightness, wifi, gps, audio output + micrphone + audio jack switching, camera works. I have not tried bluetooth yet, but the bluetooth settings are there, so there shouldn't be much of an issue. I have not tried a sim card yet.
I wanted something more well known, so I flashed system-quack-arm-aonly-vanilla.img.xz from https://github.com/phhusson/treble_experimentations/releases/tag/v204 and so far everything still seems to work fine. treble version is 27, so I guess all treble roms with support for this version should work. You will need the "aonly" variant, and not the ab one, and it probably has to be the arm (= all arm32?) variant, not the arm32_binder64 one.
ccxxx said:
Because amazon warehouse deals sold them so cheap I bought 2, so after trying it I can answer some of my questions. First, my fastboot here (linux) doesn't have a -u switch, but it worked fine without it.
I tried andy yan's build first. Rotation sensor, display brightness, wifi, gps, audio output + micrphone + audio jack switching, camera works. I have not tried bluetooth yet, but the bluetooth settings are there, so there shouldn't be much of an issue. I have not tried a sim card yet.
I wanted something more well known, so I flashed system-quack-arm-aonly-vanilla.img.xz from https://github.com/phhusson/treble_experimentations/releases/tag/v204 and so far everything still seems to work fine. treble version is 27, so I guess all treble roms with support for this version should work. You will need the "aonly" variant, and not the ab one, and it probably has to be the arm (= all arm32?) variant, not the arm32_binder64 one.
Click to expand...
Click to collapse
isnt the mediatek a 64bit cpu
Good question. /proc/cpuinfo says
Code:
Hardware: MT6739WA
which seems to be a Arm Cortex-A53, which seems to be a 64 bit cpu. I shall try the 64 bit variant of the rom.
ccxxx said:
Good question. /proc/cpuinfo says
Code:
Hardware: MT6739WA
which seems to be a Arm Cortex-A53, which seems to be a 64 bit cpu. I shall try the 64 bit variant of the rom.
Click to expand...
Click to collapse
right something going on after a few flashes, ive tried a few roms and my data in buggered cant get a mobile connection whatsoever ive tried getting into testing mode but no luck!
Any advice>?
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
also getting this quite alot on lots of different roms -FAILED (remote: 'sparse image size span overflow.')
fastboot: error: Command failed
With the arm64 build from https://github.com/phhusson/treble_experimentations/releases/tag/v204 I get this too:
Code:
$ fastboot flash system system-quack-arm64-aonly-vanilla.img
Sending sparse 'system' 1/13 (131068 KB) OKAY [ 38.967s]
Writing 'system' FAILED (remote: 'sparse image size span overflow.')
fastboot: error: Command failed
I guess the system partition is just too big:
1.7G system-quack-arm64-aonly-vanilla.img
1.1G system-quack-arm-aonly-vanilla.img
Are the arm64 binaries really 50% bigger, or is there more stuff in the 64 bit build, or is there empty space in the image?
Anyway, I put my sim card into slot 1 and immediately got a decent 4G connection, I didn't have to do any fiddling (O2/Eplus in germany). I only tried the AOSP image I linked, not the one from andy yan. It seems there are some issues with that image though, alarms and messaging notifications are two things that don't seem to work yet.
I keep getting this:
Code:
fastboot oem unlock
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
FYI i have enabled oem unlock. Any clues?
hello
can i have the source for this because i want to optimize it.
my reason is the boot time is very long.
Hi Guys,
I've been trying since yesterday and get a boot loop on the lineage os boot.
I haven't got past the boot animation.
I've tried to flash to stock with spflash tool. NO success so far.
I need help, please.
I'm running Linux i3.
Thanks a lot!
FNMONTEFALCONE said:
Hi Guys,
I've been trying since yesterday and get a boot loop on the lineage os boot.
I haven't got past the boot animation.
I've tried to flash to stock with spflash tool. NO success so far.
I need help, please.
I'm running Linux i3.
Thanks a lot!
Click to expand...
Click to collapse
Have you tried clearing the cache on the recovery menu and trying to boot again?
Sometimes the phone gets stuck on boot, any clues?
No success with rooting
Chinchila01 said:
Have you tried clearing the cache on the recovery menu and trying to boot again?
Click to expand...
Click to collapse
Dear Chinchila01,
Yes, and yes. I tried everything. The phone is now at my carriers tech support team. It's been more than a week and they can't fix it!!
I'm surprised, I must've really screwed it up somehow!
Well, I got a backup while they decide what to do and I've decided not to touch it.
I guess some phones are just not for fooling around with.
Hope this helps.
Best,
Facundo
I have much the same issues.
Lineage 16 works almost completely if it ever boots, sometimes you get lucky!
Lineage 17 usually boots but doesn't work really well, no gps, etc.
No GAPPS either way.
So close yet so far!
Solution
@caish5
@FNMONTEFALCONE
Hey guys, just to tell you:
Have been trying out this rom: https://github.com/phhusson/treble_experimentations/releases/tag/v32
And so far everything's good.
I installed system-arm-aonly-go-su.img.xz using the following method:
1. Extract it.
2. Reboot to fastboot.
3. fastboot flash system <file>
4. Reboot to recovery
5. Factory reset and cache clean.
6. Reboot.
Thanks, that worked. Even GAPPS!
Chinchila01 said:
@caish5
@FNMONTEFALCONE
Hey guys, just to tell you:
Have been trying out this rom: https://github.com/phhusson/treble_experimentations/releases/tag/v32
And so far everything's good.
I installed system-arm-aonly-go-su.img.xz using the following method:
1. Extract it.
2. Reboot to fastboot.
3. fastboot flash system <file>
4. Reboot to recovery
5. Factory reset and cache clean.
6. Reboot.
Click to expand...
Click to collapse
I've tried a lot of different GSI images, All Pie ones take a long time to boot or don't boot and have to restart until it does.
I got this phone few days ago, Surprised me that it can run GSI's been having a good time testing different roms.
Thought there would be a TWRP but haven't found one. Makes it hard to have a rom with play store and root.
That's what i'm trying to find.
Chinchila01 said:
@caish5
@FNMONTEFALCONE
Hey guys, just to tell you:
Have been trying out this rom: https://github.com/phhusson/treble_experimentations/releases/tag/v32
And so far everything's good.
I installed system-arm-aonly-go-su.img.xz using the following method:
1. Extract it.
2. Reboot to fastboot.
3. fastboot flash system <file>
4. Reboot to recovery
5. Factory reset and cache clean.
6. Reboot.
Click to expand...
Click to collapse
Does that rom have SuperSU ? it say's SU at the end but installed it and no SU app ?