If you dont have full ROM backup from your device or official ROM, dont do anything in terms of modding but to install vcom drivers (in my case they wont work without Virtual Serial Port Drivers) for bootloader, and adb/fastboot drivers, make sure theyre working, install Miracle Box / SPFlashTool (or similar ?) to be able to backup/flash your ROM/partitions from/to your device.
Check if it works for you (ie backup your ROM and try to flash something (cache) back.
Now when people are scared enough I want to tell you that it is almost impossible to kill (brick) your MTK phone, it happens mostly when people flash something that is not suppoused to be flashed (something from another device), the worst case if you flash wrong preloader or erase preloader but even after this there is a chance for resurrection. it takes time and efforts though.
++++++++++++++++++++++++++++++++++++
This is TWRP 3.2.2.0 recovery for Chuwi hi9 Pro.
Partitions available for backup:
boot, recovery, system, vendor, data (not incl. data/media = internal sd), cache and "para" (if you have got "recovery loop" - flash "para")
.img flashable - boot, recovery
look for detailed instructions for coomon things in other treads, like
- how to install bootloader vcom drivers and adb / fastboot drivers
- How to work with adb / fastboot command from your computer cmd window.
- how to use Miracle Box / SPFlashToll
This is detailed instruction how to make SPFlash backup out of your phone though Miracle Box does it in one click (well, almost)
- how to unlock bootloader (fastboot mode)
- how to use toilet paper (manual mode)
- how to install twrp recovery
- how to root
Unlock, Install, Root in one post
++++++++++++++++++++++++++++++++++++++
So, main point of this thread is TWRP, youll need:
- roll of toilet paper
- spflashtool backup (just in case)
- backup of your data (if you care) - your data will be erased during the process.
- unlocked bootloader
- twrp image
If something went wrong (highly unlikely), but "if".
Worst case scenerio: your phone will not boot into system / recovery
Solution: reflash (fastboot or flash tool): boot / recovery / system
Worst case scenerio: flash factory ROM (SPFlashTool)
Steps to do when you have all knowledge and all files ready.
IN YOUR CURRENT SYSTEM
In settings->System->About tablet -> click several times "build number" untill you see message "now you are developer"
In settings->System->Developer options: Enable USB debugging and OEM Unlock, connect cable
REBOOT INTO FASTBOOT
Power off, Power on holding "vol+"
Youll see black screen with 3 strings of menu (very small font):
- recovery
- fastboot
- system
use "vol+" for navigation, use "vol-" to confirm your choice (fastboot)
OR from your pc cmd window (shift+right click on adb folder -> choose "open command window here") type: adb reboot bootloader
press Enter
UNLOCK BOOTLOADER
on your pc (if cmd window is not ooened yet: shift+right click on adb folder -> choose "open command window here") type: fastboot oem unlock
press Enter
watch your phone and pc screen for messages
if you have vision problems, make sure you have a magnifying glass.
INSTALL TWRP
download hi9pro_twrp.img to your /adb folder
from the same cmd window type:
fastboot flash recovery hi9pro_twrp.img
*
Reboot into twrp and flash Magisk
*
Basically this is it
There is no command from fastboot to reboot into recovery (correct me)
You can power of, power on holding "vol+", choose "recovery" from menu
command to reboot into system: fastboot reboot
+++++++++++++++
* NEW *
Infect_Ed has posted TWRP recovery that he has compiled from source. DOWNLOAD FROM HERE
We don't know how to make twrp recovery work with encrypted data partition.
Read next paragraph if you are OK to trade security (encripred userdata) for functionality.
++++++++++
==========
In case you want to have your userdata decrypted (and full functional twrp), use following steps:
*** Please, note all userdata AND internal SD will be wiped during the process***
If you care
Save Internal SD card content to your ext.SD or computer
Make a Titanium backup of user apps (check Enable external data backup in Titanium settings)
If Titanium fails to write to your ext.SD than change Titanium backup folder location to int.SD
and after backup is done copy Titanium backup folder to ext.SD or PC.
Disable any passwords/pins from Settings->Security & Locations
(I know they are stored in /data/.. and will be erased anyway but just in case)
- Reboot into TWRP
- ftom TWRP -> Wipe ->Format userdata -> Confirm with "yes"
do not reboot into system
- flash encryption_prevener_hi9pro.zip to prevent system automatically encrypt userdata (it is used to insert modified fstab.mt6797 into vendor/etc)
- reboot system
- restore your int.SD content and apps
============
Link to official ROM/Firnware
*** Read this if you have Recovery Loop - no matter how you boot (buttons, from twrp recovery or from adb/fastboot shell) your device you always end up in TWRP recovery ***
- download 2018-09-29--para.zip
- unzip it - there is a folder 2018-09-29--para with 3 files inside
- connect your phone in twrp recovery mode to your computer
(you may need to turm "enable mtp" option in TWRP->mount)
- copy that folder into your sd card, the path is : TWRP/Backups/Hi9Pro
- click "Restore" (on the next screen make sure ExtSD is chosen as backup path)
- check checkbox "para", run restore, reboot
explanation: para is a partition contains last issued kernel reboot flag(command), like "reboot to recovery, reboot to system, etc." I think there is one flag that tells to kernel something like "reboot to recovery, do something untill its done", since this "something" never done, device reboots into recovery over and over again. This happend to me when I tried "factory reset" command from android settings, so android have sent my device into recovery mode where that "factory reset" command had to be performed but never done because its now not stock recovery but twrp.
**** If you have following problems:
Unknown Baseband -> Unknown IMEI -> NO sim card -> NO cell network
Look here first
****
***** If you came here from there.*****
and you are following their instructions, please, note, step 7. Unlock bootloader : DO NOT DO command "fastboot flashing unlock", just skip it.
Also, try to avoid "fastboot boot recovery.img" command to reboot into recovery (just use physical buttons for reboot). I'm not sure but something caused "recovery loop" in one case at least.
****** back-to-encr.zip if you want to encrypt your decrypted userdata (original fstab.mt6797 will be flashed, no data loss, you will not be able to mount userdata in TWRP, first boot may take long time due to encryption process - 10-60 min- depends how much data do you have)
******* twrp_recovery_chuwi-hi9pro_infectEd-XL is same Infect_Ed recovery adopted for our screen.
Hello. I made a mistake last week. I flashed accidently twrp with a scatter File from the HI9 Air through the spflashtool on the Hi9 Pro. Now it doesnt turn on etc. Is it hardbricked or can i still get it back to life?
No, its not complitely bricked if flash tool still recognizes your phone in bootloader mode. Most likely youve made same mistake I did. Depends of how you flashed that recovery - recovery only or full sisyem WITH new recovery. most likely you flashed only recovery partition. than, first, try to reflash backed recovery & next to recovery ("para") partition. in "download only mode" therell be an error "pmt has changed" than try "format & download" and "firmvare upgrade" - use scatter file contained only those two partitions. if you didnt make a backup ill put here that "para" partition and you can use hi9pro twrp img. in case this wont work, you may want to reflash the whole rom. We need to find factory rom image (from Chuwi or someone who did a back up prior he entered his credintals - thats another mistake Ive made Ive dumped a rom with all my logins information). if I have time I'll try "factory reset" to make a backup from "clean" system.
again, its almost impossible to brick mtk completely. even if flash tool doesnt recognize you phone (dead battery) there is a jump-pins method.
upd. Just looked @ Air scatter and found that Air recovery partition size is same as Pro (~16mb). now I dont know haw was that possible to overwrite next to recovery partition(s) and I think I used same Air img as you did and I've got size warning message when I flash it. anyway here is archive with scatter for recovery and para. just add twrp hi9 pro recovery (rename recovery.img to recovery.bin) and try to flash.
I didnt made a Backup (stupid me) i flashed the recovery file with a scatter file. When i plug the device in the pc the USB sound comes and its recognized as MEDIATEK USB PORT (COM8), but its removed automatic (USB Sound for disconnecting) The Screen stays black. So i have to wait for a Rom and a scatter File then?
---------- Post added at 19:50 ---------- Previous post was at 19:39 ----------
I tried your idea. I got an error Message: "Status Preloader Invalid" The Preloader File Format is invalid.
you know how to use flash tool , first you have to press "download" THAN connect usb cable.
but this is a good sign (pc recognize something), you may want to google for something like "unbrick mtk 6797 sp flash tool" for more info
this is archive w. 4 1st partitions (incl preloader)
Ive gotta go. Dont smash your tablet its 100% repairable, well 99.999%
thats how it looks
https://photos.app.goo.gl/9EK8vTwcTS3fDf1a7
---------- Post added at 20:21 ---------- Previous post was at 19:58 ----------
Still get an error Message for the PRELOADER. I read some Tutorials and dont find a Problem in my setup or my doing. Sucks :-/ But Thank you very much for your help
is it "MEDIATEK USB PORT (COM8)" appears for a second in the devices tree or "mediatek preloader usb vcom (android) (com8)"
if second, then everything is OK with the connection.
if its exactly MEDIATEK USB PORT (COM8) then there is something wrong
try to connect cable with diff buttons combination, i.e. "vol+" + connect cable .
try different "download agent" (DA_PL.bin ?)
Though I also used AllInOne_DA and flash tool V.5.1728
also, you might find Miracle Box Tool is easier to use
try "read" option first to backup your current rom
View attachment 4598709
I shoul ask this first:
- have you ulocked bootloader ?
- when your press "power" and "vol+" after some wait is anything appears on the screen
(boot menu: fastboot, recovery, regular boot) ?
- when your press "power" and "vol-" after some wait is anything appears on the screen
(chinese written) ?
Good Morning.
Bootloader is unlocked, no matter which key combinations ill try the screen stays black. When i have the usb cable at the PC (no matter which Port or cable) it the plugin - plugout sound plays every few seconds/minutes (not the same time in between). It is recognized as "MediaTek USB Port (COM4)" (different PC i tried). When ill try to install the vcom drivers i get the message that the best drivers are already installed and that are the mediatek usb port driver.
Image of the device manager: https://ibb.co/erkW6e
zelipukin said:
is it "MEDIATEK USB PORT (COM8)" appears for a second in the devices tree or "mediatek preloader usb vcom (android) (com8)"
if second, then everything is OK with the connection.
if its exactly MEDIATEK USB PORT (COM8) then there is something wrong
try to connect cable with diff buttons combination, i.e. "vol+" + connect cable .
try different "download agent" (DA_PL.bin ?)
Though I also used AllInOne_DA and flash tool V.5.1728
also, you might find Miracle Box Tool is easier to use
try "read" option first to backup your current rom
View attachment 4598709
I shoul ask this first:
- have you ulocked bootloader ?
- when your press "power" and "vol+" after some wait is anything appears on the screen
(boot menu: fastboot, recovery, regular boot) ?
- when your press "power" and "vol-" after some wait is anything appears on the screen
(chinese written) ?
Click to expand...
Click to collapse
---------- Post added at 07:34 ---------- Previous post was at 07:07 ----------
zelipukin i made a short Video about the behavior. The Device seems to activate when i push vol+ or power, but it looses connection when i stop holding the button or sometimes even when i hold the button.
https://drive.google.com/file/d/1m3YLrH5ZaVLttcSfDxx3RvL0DaXPcxzk/view?usp=sharing
...thinking
Just tried...seems like backups I made(and posted here) from Miracle Box is incompatible with SP Flash.
SP Flash doesn't like this and doesn't like that when tries to restore those backups but Miracle Box restores individual partitions or whole ROM w/o problem.
SP Flash is so inconvenient if you try to make a backup ... its also inconvenient when you try to restore.
Where did I get that Miracle Box for free ?
Let me figure out something...
....
This is something beyond my understanding but let me to describe what I did
- in SP Flash I choose scatter file and recovery.bin (like I sent to you)
- download only - no go
- download+format - no go
- firmware update - warning message about wrong partition size or something like this - Ignored - Flashed
- Bricked again (like yours - black screen - that's it)
- OK, I have several backups. Tried all of them - none of them works... except one
- Flashed that backup with SP Flash - no questions, no warnings, no errors - device came alive
- Flashed only recovery.bin - everything went fine
- Tried to find difference btw different backups - but couldn't find any
- So I tried to flash those files (to try 3.zip) several times and everything went OK, so this is 100% working backup.
Try it and see what happens, then we can go somewhere else. I still suspicious about those MTK Usb Com(8) instead of preloader usb. Also if you used "Firmware upgrade" option once, I beleive you'll need full ROM flash. Keep looking for it @ Needrom.com.
Strange things happen. Couple years ago I lost MTP connection with my MiMax. I tried everything possible but no luck - have to use UMS Enabler so I can read/write ExtSD at least, but MTP works with Chuwi.
I spent numerous hours trying to connect Chuwi in preloader mode until found that solution about Virtual Serial Port drivers.
Thanks for your help so far. Seems like my Device is half dead after 2 Hours of use
I'll tried to change the Drivers for the mediatek, it shows the device now with the preloader, but i think it doesnt work right. when i change the usb port it comes back as MediaTek USB Port (COM4). I made you a 15 Second Clip of the behavior.
https://drive.google.com/file/d/1m7wyIlIYJLN7ikmgUTzHBJtBdbZQrYaa/view?usp=sharing
Really weird. :-/
---------- Post added at 14:55 ---------- Previous post was at 14:40 ----------
and no chuwi hi9 pro rom at needrom yet. :-/
Sorry, haven't seen there is second page of this thread.
Saw a video where one guy showed how he changed drivers to right ones.
Main idea is in that short period of time when wrong drivers appear click right mouse button and choose "uninstall drivers"
after this in his video in next attempt system found usb vcomm by itself. worth to try
or other videos where guys catch a moment when this port appears in device tree but choose "update drivers"-> "browse my computer..."-> "let me pick from a list of device drivers" -> remove flag from "show only compatible.."->
I cleaned system, removed apps,accounts, etc. and made a backup of a "clean" ROM (well, almost). will put somewhere when/if I get good wifi somewhere (its 3GB.. w/o data partition) I'm on slow & limited mobile network.
but I don't think you need anything but recovery & para if you never used "format" & "firmware upgrade"
i think i used the upgrade one, after download only didnt work.
Ill tried the same method with changing drivers.
I will sit this one out, till you have uploaded the rom
Thanks for helping me out!
zelipukin said:
Sorry, haven't seen there is second page of this thread.
Saw a video where one guy showed how he changed drivers to right ones.
Main idea is in that short period of time when wrong drivers appear click right mouse button and choose "uninstall drivers"
after this in his video in next attempt system found usb vcomm by itself. worth to try
or other videos where guys catch a moment when this port appears in device tree but choose "update drivers"-> "browse my computer..."-> "let me pick from a list of device drivers" -> remove flag from "show only compatible.."->
I cleaned system, removed apps,accounts, etc. and made a backup of a "clean" ROM (well, almost). will put somewhere when/if I get good wifi somewhere (its 3GB.. w/o data partition) I'm on slow & limited mobile network.
but I don't think you need anything but recovery & para if you never used "format" & "firmware upgrade"
Click to expand...
Click to collapse
Just a few questions after using Hi9 Pro for about a week:
1) Where is the microphone ? Is it the small hole under the volume button ? (Strange position)
2) On the back side the two metallic stripes separating the plastic of the metal body are they something like antennas ? (LTE or WiFi or both ? )
3) What is the version of Bluetooth ? (4.0 or 4.1 or 4.2 ? )
4) Is it possible to use some kind of fast charging with a suitable charger or software app (firmware update) ?
MediaTek has a technology called "Pump Express" or something like that...
5) Do you have sudden, unexpected pop-ups of full screen advertisements while you are working with your tablet ?
How do we get rid of them ?
6) How do I find the LTE band the tablet is actually using while it's in use ?
I don't mean the table of supported bands, I mean the active band while using it.
Thanks!
1) looks like and its logical bc its close to mouth than if they put it in the bottom.
2) not sure, but most likely
3) according to this https://www.manilashaker.com/mediatek-helio-x10-vs-x20-vs-x30-chip-comparison-difference-specs/ its 4.2
4) too many different opinions, cant find the truth
5) none so far
6) you can try to find some info from mtk engineering mode *#*#3646633#*#* from you dialer
but its not intuitive and complicated
zelipukin said:
1) looks like and its logical bc its close to mouth than if they put it in the bottom.
Click to expand...
Click to collapse
Yes, it is a very small hole at the bottom right as you hold it, with a size of the edge of a needle!
zelipukin said:
1)3) according to this https://www.manilashaker.com/mediatek-helio-x10-vs-x20-vs-x30-chip-comparison-difference-specs/ its 4.2
Click to expand...
Click to collapse
Thank you.
zelipukin said:
5) none so far
Click to expand...
Click to collapse
But how did you do that ?
Did you add an Ad Block after rooting the tablet ?
The kind of ads I get, is more of suggested apps to install from Google Play.
It is literally bombarding me with an exhaustive rate.
I went to settings to "advertisements" of Google and it says that I can't turn it off.
Could it be some app that I installed that is spamming me this way ?
Can you suggest something to stop it ?
zelipukin said:
6) you can try to find some info from mtk engineering mode *#*#3646633#*#* from you dialer
but its not intuitive and complicated
Click to expand...
Click to collapse
I installed LTE Discovery and although I'm not rooted it seems that it works OK and it's showing me the bands.
The signal strength is lower than a mobile phone at the same position, same time, same provider.
Do you have an equal signal strength like your mobile phone ?
One more question:
7) Is it feasible for a developer to build a custom ROM for this device if he wants to or there are certain restrictions forbidding custom firmware ?
Is there any chance for a custom ROM in the future, because I don't think Chuwi will upgrade to 8.1 or better Android.
Thank you!
Regarding ads - I didn't do anything, I looked @ settings->google->ads and I can turn it on and then off w/o problem
Also I culdnt find any junk software so far, the phone came from GearBest factory sealed. I didn't do any system modifications except installing Magisk and modules - ExCard Access Enabler, init.d injector, Magisk SELinux Manager, ViperX (slightly better sound from speaker)
I didn't try the device as a phone, though it fit in a pocket of one of my jeans. I'd like to try but my current phone (miMax) has a micro sim.
7) Depends how popular is this device and who (developers) got it. Also, depends if this chipset is used in many other similar models (popular, prefferable) than you don't need to be a real "developer" to port ROM from a similar device and if you find that divice X is updated to 8.1 there is a chance someone will make a port (or you can try to do it yourself). I'm not a big fan of immediate upgrading to a newest version, for me they usually bring more limitations (you cannot let apps to modify files on your own sdcard f.e.) than benefits. I still use >2 y.o. andr. 6.0 custom rom on my MiMax.
zelipukin said:
Regarding ads - I didn't do anything, I looked @ settings->google->ads and I can turn it on and then off w/o problem
Also I culdnt find any junk software so far, the phone came from GearBest factory sealed.
Click to expand...
Click to collapse
Me too, I got a sealed and clean tablet from GearBest but If you look closer to that setting, it says that you can turn on or off the specialized ads for you, but you can't close ads completely.
For example, during web browsing do you see ads inside various sites ?
Or when opening apps on your tablet ?
I think we need an ad-blocker for this.
zelipukin said:
I didn't try the device as a phone, though it fit in a pocket of one of my jeans. I'd like to try but my current phone (miMax) has a micro sim.
Click to expand...
Click to collapse
I meant for mobile 4G data, not as a phone.
In my country we have three bands for LTE:
B3, B7, B20.
When the tablet rotates between 3 and 7, I have poor to zero signal.
But I saw with LTE Discovery that when it switched to 20 then the signal is very good.
So, with the help of MTK Engineering I disabled 3 and 7 bands and everything seems OK now.
I hope B20 to be used everywhere near to me.
zelipukin said:
7) Depends how popular is this device and who (developers) got it. Also, depends if this chipset is used in many other similar models (popular, prefferable) than you don't need to be a real "developer" to port ROM from a similar device and if you find that divice X is updated to 8.1 there is a chance someone will make a port (or you can try to do it yourself). I'm not a big fan of immediate upgrading to a newest version, for me they usually bring more limitations (you cannot let apps to modify files on your own sdcard f.e.) than benefits. I still use >2 y.o. andr. 6.0 custom rom on my MiMax.
Click to expand...
Click to collapse
I'm not familiar with Android internals so much, I am only using a Note II with TWRP and a custom 7.1.2 ROM and I'm missing some simple customizations not available with out Oreo 8.0 stock ROM.
I haven't even tried yet your first post regarding rooting and all the others because I'm not so sure where to find these tools and how to use them.
It could help a lot when you find some time to add more descriptions and links in your first post, if possible like Hi9 Air thread.
Thank you!
I dont know how and why, but I dont have any agressive advertisements. Checked Opera I'm using for webbrowsing - even "block popups" option wasn't checked. Had to download app yesterday (AutoNotification) from gp store and when I started it in a "free mode" there was a message like "to use this app in a free mode you have to agree to see ads", clicked "ok" , then message "downloading..." appeared...and nothing, no ads. I connect my tablet to the internet through my phone but dont think that matter.
Just a few more short questions:
8) Is there any other way to wake up the device instead of pressing the red button ?
For example double tap or maybe using the volume buttons or any other way.
Because I'm afraid of pressing the same button again and again.
9) Does this device have a WiFi 2x2 MIMO ?
I haven't found any particular info on this.
10) What is the kernel of the ROM ?
Is there any GUI compatible like Kernel Aiutor to make changes or take a look at info for the device ?
Thank you!
Related
I have a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
One day, after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images.
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it was crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it was useless.
I took the phone to an LG lab. They said I need to replace the motherboard. Costs about 200$ !!
I was about to get a new phone , but decided to try one more google search for a fix.
This guide is for any poor soul in the same state.
This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount.
I found out by trying to follow this guide: http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist".
This is a software problem.
Her's how to fix it (It's a long and detailed guide - but worth the result):
First, you must enable USB debugging mode , if it was not enabled (if it is enabled you can skip the first step of this guide) . The way to do that is to flash a stock image that will load, even if not fully working. In my case I could flash version 4.4x and get the phone to load. I am not aware of any other way to enable USB debugging, other than from within a working OS. If someone knows a way - please post it.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, it should load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new Developer Tools and enable usb debugging. Approve any popups.
*** I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.****
Next, you need to have ADB on your PC, and it should be able to reach your phone. If you already have - then skip to the next step. If you don't - then here is how to get the latest version:
Go here and download the installer https://developer.android.com/sdk/index.html#Other
Install the file and when it's done run SDK manager. Choose only the first 2 tools (Android sdk tools and Platform tools), this will install the latest adb and fastboot tools. To make sure all is installed open a command prompt (Click Start, type cmd in the search and run cmd.exe) and type adb. You should see all the adb possible commands typed. Now you can test if your phone can be reached by adb: connect your phone (remember usb debugging must be on!) and type: adb devices. After a few seconds you should see something like this:
List of devices attached
024703f599cc8feb device
If you get this, it means you have usb debugging enabled and a proper usb driver installed and you can go to the next step . If there is no device in the list you need to install/update the USB driver:
You have to make sure that when you connect your phone with USB debugging on, you have 2 entries in Winodws Device manager:
Under Portable devices >Nexus 5 , and under Android device> Android composite ADB Interface.
If the second one is missing, ADB will not work and you can't continue. There are 2 ways to fix that :
1. You can install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
The author of that guide states you need to uninstall any driver that already exists. This proved tricky because Windows would not uninstall the Nexus 5 driver. I decided to install it on a PC that has no android driver.
When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
2. If that does not work or if you don't have another "virgin" PC try this:
Run SDK Manager, under Extras mark Google USB driver. You don't need anything else marked. Install the driver.
Now connect your phone to the PC in normal mode (not bootloader!) . Open device manager. You should have two entries: Portable devices >Nexus 5 and Android device > Android Composite ADB Interface
If the second one is missing, but the Nexus 5 is properly installed, Right click on the Nexus 5 device >Update driver software > Browse my computer for driver software >Let me pick from a list. Now make sure that "Show compatible Hardware" is ticked . You should now have an entry called "USB composite device". Choose that and let it install. When it's done, if you still have an an Unknown device >Nexus 5 and no Android Composite ADB Interface in device manager, then unplug the phone and reconnect it again . You should now have both devices installed.
If by chance this does not work, and you have a Nexus 5 with a yellow error , right click it>update software driver> Browse my computer.> and point it to the Universal Naked Driver folder or the SDK>Extras>Google USB driver folder and it should update so both devices appear (Nexus 5 and ADB).
Once adb can see your pohne go here, to read bitdomo's guide to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work:
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode to be turned on, and the proper usb driver installed.
Second, you need to install a custom recovery image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Last, you need to root your device. There are many ways to do this. I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
I did not follow the steps for the wifi and BT fix , because they worked fine (and still do 4 months later) , but you can go ahead and do that too.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device. Done! Boot up the device and make sure it recognizes the right amount of RAM on your phone (16 or 32GB). If it does, then all is well .
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .
stuck at unlock step
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad
Thanks! Helped me to save my N5!
Do not need to exactly as it is posted but the directions is good!
Thanks again.
killian.1140 said:
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad
Click to expand...
Click to collapse
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck
Or just read the stickies.
I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers
Thank you so much for this! You saved my phone!
volvoxxda said:
I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers
Click to expand...
Click to collapse
But for that you have had to install TWRP in the first place...
Mine was stock.
Where is the backup saved?
Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..
volvoxxda said:
Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..
Click to expand...
Click to collapse
Flash drive? Do you mean the Nexus internal memory?
{
"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"
}
External, like on this picture.
Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue
volvoxxda said:
Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue
Click to expand...
Click to collapse
Did you just replace the button or did you have to replace something more?
Thanks
Just the button. You can DIY, it's easy.
worked
worked great. confusing in the start but got it working. Thanks for a life saving guide for nexus 5
incredible
Hi eross,
I registered and logged in just to say thank you for this amazing tutorial. I've been trying to repair my N5 for about 12 hours, and I was about to give up when I saw this post. You saved my Nexus!!
Thanks again. :victory::highfive::good:
eross said:
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck
Click to expand...
Click to collapse
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T
ambervals6 said:
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T
Click to expand...
Click to collapse
You can try to download the stock firmware that's installed on your phone and flash the recovery img, or flash twrp recovery.
help
eross said:
This is a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
Yesterday after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images. (can't post links yet...)
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it is crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it is useless.
I am wondering if it is a software or hardware problem. It appears as though part of the phone's memory is not functioning . Is there a way to check this? Is there a way to fix this?
Thanks
Edit: Just came back from an LG lab. Bad news. Need to replace the motherboard. Costs about 200$ !! Can't find anything cheaper on ebay. Guess it's time for a new phone
Edit #2 - SOLVED !!:laugh:
OK, this for any poor soul in the same state. This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount. Here is how I found it out, and how I fixed it:
First, try to flash a stock image that will load, even if not fully working. You will need this later. In my case I could flash version 4.4x and get the phone to load.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, if you are lucky it will load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new developer tools and enable usb debugging. Approve any popups.
I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.
Once this is done , boot the phone into debugging mode.
Read the guide here http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist". I then understood what the problem was. If you get the same error - you are in luck!
Then go here, to learn how to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work.
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode.
Second, you need to install a custom recover image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Third, you need to install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
Since the author of that guide states you need to uninstall any driver that already exists, I decided to install it on a PC that has no android driver. When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
Last, you need to root your device. (I think this can also be done from within TWRP , but I am not sure how...) I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt where adb.exe is located , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device.
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .
Addendum: According to bitdomo, installing a custom recovery like TWRP enables USB debugging by default even if the phone does not boot. I have not tried this myself, but this means you can foergo installing os 4.4x , and go straight to ADB and run the command that fixes the persist partition.
Go ahead and try it. It will save you a lot of time!
Click to expand...
Click to collapse
My N5 has exact problem as yours even same errors of camera and playstorw crashing when i loaded older android version.. now im positive your instructions will help me but im having some trouble with your steps i do not know how to type comnands with ADB .. im truly novice and dont want to damage the phone more could you simplify the steps or make a video please? Thank you
Sorry, I can't make it any simpler than that. I can't make a video now because my phone is fixed. Adb is very simple, it's like an old DOS window where you type the text. I would follow Bitdomo's advice and start by installing TWRP. This will get you USB debugging, and you can run ADB and follow his instructions to fix the persist partition.
I am not responsible for anything that happens in your life. Including what happens as result of following steps in this thread.
Hello all. After a long journey here, we figured a new thread would be in order for new comers not to have to read through fifty pages of information. Here you will find firmware to fix or update your Viking Pro. You will also find root methods, bootloader unlock and custom recoveries for this tablet. Lets start with ROOT...
Method 1: Kingroot. Kingroot works on this device. you can find it here. It's pretty straight forward, just download and install the apk and root.
Method 1.5: SuperSu. Kingroot works but it's not the best root out there. once you have root, follow the instructions here and Kingroot will be replaced with SuperSu.
Method 2: Su flash-able ZIP. This method requires you to follow steps in posts No. 3 and 4. Once you have custom recovery installed, You can flash This.
This method is a bit redundant. However, it does allow you to make a completely stock unooted backup of your rom before making any changes.
Check out posts 2, 3, 4 & 5 for the good stuff.
I'm gonna go ahead and thank everyone responsible and If I forgot to mention you, please don't hesitate to tell me and I will correct the situation:
@Bogram (Edited the bootloader so it could be unlocked on x.12.x versions)
@Jacube22 (Duplicated the method from Bogram to make the bootloader on x.9.x versions unlockable)
@vampirefo (Compiled a compatible CWM recovery for us)
@ewilley2008 (Found most of the firmware)
@mayzemay (Initial root thread)
@NepoRood
@jerryvail35
@Sir Jaxxy
@Snigglez
@Spartan Legionnaire
@bobl61
@csla
@Chainfire (For root)
FIRMWARE
There are two main branches of development for this tablet. It is very important to know which one you have because they are incompatible with each other. I personally bricked my first one with firmware from a x.9.x while mine is x.12.x. How do you check? Simple. In your build number, you can find it in "About tablet" in Settings or in the text at the top of the recovery screen. It's at the end of the number and it will look like 1.12.30, 10.12.20, 2.12.20, 1.9.1, 1.9.5, 10.9.1...etc The number in the middle is the important one.
Steps(Windows): For step 2 you will have five seconds. Preloader mode is only active for five seconds. So read first!
1- Extract the drivers to the destktop and open the device manager.
2- Plug your tablet in as such: turn off the tablet. Plug a male to male USB wire from the computer to the USB port on the tablet. now plug the power wire into the tablet. now very quickly in the device manager locate the new device and right click on it. select "update driver software" then select "browse my computer for driver software" and "browse". Now navigate to the driver folder, select the "CDC" folder and click on "OK" the "Next". The driver should install at this point. Once that is done, unplug the power cable from the tablet.
3- Extract the firmware and the sp flash tools to your desktop.
4- Start the sp flash tools and where it says scatter file loading click and navigate to the folder where you have the firmware and load the scatter file. You will see the firmware get loaded and a checksum check.
5- Once that is done, uncheck the preloader from the list and click on the download button.
6- Plug the power cable into your tablet. At this point the sp flash tool will load the firmware into the tablet. DO NOT UNPLUG ANYTHING UNTIL THE SP FLASH TOOLS SHOWS YOU A GREEN CHECK MARK TO INDICATE THAT IT IS DONE OR YOUR TABLET COULD BE HARD BRICKED AND UNREPAIRABLE.
7- Press the reset button and turn it on. Done!
Drivers: https://drive.google.com/file/d/0Bz4bOoJ_E5XzRWJCbGFINndmVmc/view?usp=sharing
SP Flash tools: https://drive.google.com/file/d/0Bz4bOoJ_E5Xzb0g3ZnlEcHE0bEE/view?usp=sharing
Firmware x.9.x:
RCT6303W87DK-ANDROID5.0-V37-V10.9.21-NFC-V2.3LA-20150820
RCT6303W87DK-ANDROID5.0-V32-1.9.1-20150409
Do not flash the preloader for the Surf1001 versions!!
Firrmware x.12.x:
RCT6303W87DK-ANDROID5.0-V77-V1.12.50-EMMC-user-Kingston-V6.1_20160316
RCT6303W87DK-ANDROID5.0-V70-V1.12.30-B-EMMC-user-Kingston-V6.1_20160121
SURF1001-ANDROID5.0-V11-V7.15.0_T8515B_V6.3_SAMSUNG2G_20151116 (Use method No.2 for root)
RCT6303W87DK-ANDROID5.0-V63-V10.12.0_T8515B_V6.3_PCDDR31G_20151106
SURF1001-ANDROID5.0-V07-V7.15.0_T8515B_V6.3_SAMSUNG2G_20151016
RCT6503W87DK-ANDROID5.0-V66-V20.12.20-B-Camera-2M_PCDDR_V6.3-20150928
RCT6303W87DK-ANDROID5.0-V63-V2.12.20-B-EMMC-user-Kingston-V6.1_20150811
Sources:
http://laurentiumihet.ro/technology/...test-versions/
http://www.needrom.com/download/mtk-...er-v5-1453-03/
http://pan.baidu.com/share/home?uk=2...ategory/type=0
http://baiduyun.57fx.cn/so-result.ht...7DK&type=share
And Google of course...
Bootloader
So the bootloader on this tablet is locked. To unlock the bootloader, in a perfect world, you would usually boot the tablet in fastboot and type the command "fastboot oem unlock" and then follow the instructions on the screen. However RCA did not code in the volume keys in fastboot mode so it was impossible to unlock the bootloader that way. So our friend Bogram edited the bootloader and now the volume keys are not needed. What swell guy eh?
Unlocking your phone’s bootloader completely wipes (formats) your Android phone’s internal memory including applications, contacts, SMS and MMS messages etc.
So what you need is a scatter file like this one and a patched bootloader like these: x.12.x or x.9.x .
You will also need ADB & Fastboot and the drivers.
1- Just like in the FIRMWARE section, install drivers and SP Flash Tools.
2- Open SP Flash Tools and load the scatter file and in the line where you see "uboot" on the right click in the blank field and a window will pop up. select the patched bootloader. Make sure it checked and click on the "Download" button.
3- Now plug the male to male USB cable and then plug in the power. SP flash tool will flash the bootloader and then show you a nice little green check mark.
4- At this point you need to unpack the adb folder from the RAR file and place it in the root of you hard drive(C: ) then open a command prompt and nvigate to you adb folder (cd c:\adb) and leave it there for just a second.
5- On your tablet unplug the power wire, hit the reset button in the back and boot it into recovery mode by pressing and holding the volume up and power buttons together until the RCA splash screen comes up then release them.
6- In recovery, use the volume keys to navigate to "reboot to bootloader" and use the power button to select.
7- At this point your tablet will be in fastboot and your computer should detect it and install the driver. If not, the driver is in the "Android" folder in the driver files you extracted.
8- In your command prompt you left opened earlier, type "fastboot oem unlock".
9-Your tablet will do some magic, summon a demon, banish it to the depths of hell, reboot a couple of times and then it will have a unlocked bootloader.
10- Done. now you ca move on the next post and flash recovery.
Bogram also created a tool that patches the bootloader automatically should you have a different version we don't know about or what not...
Code:
RCA LittleKernel Unlock Patcher
By Bogram (http://forum.xda-developers.com/member.php?u=7182821)
Tested models:
RCA Viking Pro (RCT6303W87DK), RCA Maven Pro (RCT6213W87DK)
USE THIS TOOL AT YOUR OWN RISK, NO WARRANTY IS PROVIDED.
License: http://www.gnu.org/licenses/gpl-3.0.html
Input file:
W:/HaxeToolkit/projects/patcher/lk.bin
Wrote to:
W:/HaxeToolkit/projects/patcher/lk_patched.bin
Press any key to exit.
https://drive.google.com/file/d/0Bz4bOoJ_E5XzSnJ2R3d2NkxlU0k/view?usp=sharing
RECOVERY
This section depends on a unlocked bootloader. If you did not unlock your bootloader in the previous post, do so before continuing to this one.
So what you need is a scatter file like this one and a recovery.
CWM + Carliv compiled by vampirefo: (x.9.x)Clockworkmod recovery (x.12.x)Clockworkmod recovery
TWRP V3.00 compiled by Neporood: (x.9.x)TWRP V3.00 recovery (x.12.x)TWRP V3.00 recovery(Coming soon)
- Open SP Flash tool and select the scatter file.
- in the recovery line, on the right side in the blank field, click and select your downloaded recovery.
- Click on the download button.
- Make sure your tablet is off, plug the USB cable first and then the power cable.
- SP Flash tool will flash the recovery and show you a lovely green check mark.
- Once that is done your recovery will be flashed.
** The stock system has a file in the system folder called "recovery-from-boot.p". this file flashes stock recovery randomly at boot so with a rooted system, navigate to the folder with a root capable explorer and delete the file so that your new recovery stays there.
** When rebooting from recovery, cwm will tell you to fix root. Don't. Select no every time.
For thos of you who want a file explorer in recovery, You can download this Aroma installer flashable
It's a nice tool to have...
Aroma comes from here: http://forum.xda-developers.com/showthread.php?t=1646108
ROMS
Not yet but soon.....
I'd swear I've seen all this somewhere before... lol
Good job, brother!
Now , let the roms...begin.....
woot ... just in time as I brought my Viking Pro home from Wallyworld Saturday night.
Any thoughts on ADB? I couldn't make it all the way through the other thread and eventually just gave up.... ended up figuring out Kingroot on my own and then just enabled ADB over wifi. Would much rather have a wired ADB solution as moving an APK (I'm a developer, duh) over wifi can be somewhat s-l-o-w.
Any plans to make a thread like this for the RCA Maven Pro (RCT6213W87DK)? It'd be really swell.
EDIT: Actually, with those sources you posted, I actually might be able to do this on my own.
thevypr said:
Any plans to make a thread like this for the RCA Maven Pro (RCT6213W87DK)? It'd be really swell.
EDIT: Actually, with those sources you posted, I actually might be able to do this on my own.
Click to expand...
Click to collapse
I've got a Maven, and I've already done the porting. I'll be posting a guide tomorrow morning sometime. For now, I've sent you a PM with links to the firmware. Check your firmware version, mine is V36-1.9.21 (as long as you have the "9", you should be ok) The zip file has everything in it, preloader, scatter, custom recovery, etc...
Maven Guide is up, find it here
Synman said:
woot ... just in time as I brought my Viking Pro home from Wallyworld Saturday night.
Any thoughts on ADB? I couldn't make it all the way through the other thread and eventually just gave up.... ended up figuring out Kingroot on my own and then just enabled ADB over wifi. Would much rather have a wired ADB solution as moving an APK (I'm a developer, duh) over wifi can be somewhat s-l-o-w.
Click to expand...
Click to collapse
Still working on adb... Trying to make a flashable ROM with the fixes... No timeframe tho..
smartmanvartan said:
Still working on adb... Trying to make a flashable ROM with the fixes... No timeframe tho..
Click to expand...
Click to collapse
I can't get the port(s) to light up under OSX. I've tried a couple build.prop changes, plugging in micro usb, usb type a, power connector, and various combinations but none of them appear to trigger registration of a usb device of any kind on the host machine.
I can't even get simple stuff like MTP to work.
Synman said:
I can't get the port(s) to light up under OSX. I've tried a couple build.prop changes, plugging in micro usb, usb type a, power connector, and various combinations but none of them appear to trigger registration of a usb device of any kind on the host machine.
I can't even get simple stuff like MTP to work.
Click to expand...
Click to collapse
Time is my issue but I'm looking at two things. there is a firmware package i found on the Chinese server for a tablet with the model number rct6603w47dk with the same board as the viking pro but with a 8163 instead of the 8127. i think its doable to port over to our tablet. it is android 6. also the maven pro(rct6213w87dk) which is really close to our tablet with the same board but a larger screen, has adb working on it...
You should be getting a reaction through the micro usb port... on windows it shows up as a malfunctioning device.
i get nothing when sniffing the USB bus on my MBP.
Synman said:
i get nothing when sniffing the USB bus on my MBP.
Click to expand...
Click to collapse
I does the same thing on Ubuntu 14.04, absolutely nothing shows with "lsusb" in the terminal, unless it's in fastboot mode. You can use fastboot to flash the device, if you don't have access to a Windows machine...
I tested the new 1.9.3 firmware on my tablet... and it just shows a black screen.
DO NOT FLASH IT. it didn't work
Jacube22 said:
I tested the new 1.9.3 firmware on my tablet... and it just shows a black screen.
DO NOT FLASH IT. it didn't work
Click to expand...
Click to collapse
Ill find you guys some newer software that boots...
What's the difference between sp_drive_v2.0_finally & mtk_sp_drivers_v2.0
Because I got the sp_drive install but having a problem with the mtk_sp , it keep popping up as incompatible software.... I'm stuck on the boot loader section
e923 said:
What's the difference between sp_drive_v2.0_finally & mtk_sp_drivers_v2.0
Because I got the sp_drive install but having a problem with the mtk_sp , it keep popping up as incompatible software.... I'm stuck on the boot loader section
Click to expand...
Click to collapse
What version of Windows are you running..the difference is the drivers are signed or unsigned.. This matters more on newer versions of Windows.
SPECIAL KNO'DIS: This Guide has been changed to refelct proper installation for both types of Maven Pro tablets, be Sure to follow the appropriate guide.
For the purpose of this guide, I'll assume you already have working ADB and Fastboot on your PC, if not, you'll need to set that up first. This guide doesn't cover installation of ether of those. If you're looking for the guide to the Viking Pro (RCT6303W87DK), go here.
KNO'DIS: I, OR ANYONE ELSE AT XDA, WILL NOT BE HELD RESPONSIBLE FOR "BRICKING" YOUR TABLET!! IF YOU MANAGE TO MAKE A BRICK, DUE TO YOUR "FUN-DA-MENTAL" INABILITY TO READ, GO BUILD A BBQ PIT WITH IT!! (Or ask for help, there's a lot of friendly people around here)
So, without further ado, lets get started. First, you'll need to know which version of firmware your device is running, this can be found in 2 different ways. From a running device go to: Settings/About tablet and look at the Build number. Or you can boot into stock recovery and the firmware version will be at the top left of the screen.
You should see something like the following, and note the 2nd number after the 2nd "V":
Code:
RCT6213W87DK-ANDROID5.0-V37-V1.9.30 <-- This is x.9.x version of firmware
or
RCT6213W87DK-ANDROID5.0-V68-V1.12.30-B <-- This is x.12.x version of firmware
Now that you know which firmware you have, follow the approriate guide below. I've broken this post into 2 different sections, as each tablet is just a little bit different.
About the Bootloader
This applies to both versions of firmware and tablet users. Turns out, the booloader doesn't have to be unlocked in order to install a custom recovery or root the device. So there's really no reason to unlock it, and I have removed that portion of this guide.
Installing MTK Preloader Signed Drivers
Drivers located Here
x.9.x Versions
Steps (Windows 8/8.1/10): For step 2 you will have less than five seconds. Preloader mode is only active for a few seconds. So read first!
1- Extract the drivers to the Desktop and open the Device Manager ("right click" on the Start button, select "Device Manager")
2- Plug your tablet in as such: turn off the tablet. Plug in the micro USB on the tablet, the other to the USB port on the PC, now very quickly in the device manager locate the new device and right click on it. For me, it showed up under "Other devices" and read MT65XX.
3- Select "update driver software" then select "browse my computer for driver software" (make sure "Include subfolders" is selected.
4- Click "Browse..." and navigate to where you extracted the driver zip. You "should" be at the following path: Desktop/MTK Preloader Signed Drivers
5- Click on "OK" then "Next". The driver should install at this point. Once that is done, unplug the usb cable from the pc (I find it easier to just keep the micro in the tablet).
x.12.x Versions (Requires Full size Male-to-Male USB Cable)
Steps (Windows 8/8.1/10): For step 2 you will have less than five seconds. Preloader mode is only active for a few seconds. So read first!
1- Extract the drivers to the Desktop and open the Device Manager ("right click" on the Start button, select "Device Manager")
2- Plug your tablet in as such: turn off the tablet. Plug in the full size USB cable to both the tablet and the PC.
3- Plug the micro USB into the tablet, the other to another USB port on the PC, now very quickly in the device manager locate the new device and right click on it. For me, it showed up under "Other devices" and read MT65XX.
4- Select "update driver software" then select "browse my computer for driver software" (make sure "Include subfolders" is selected.
5- Click "Browse..." and navigate to where you extracted the driver zip. You "should" be at the following path: Desktop/MTK Preloader Signed Drivers
6- Click on "OK" then "Next". The driver should install at this point. Once that is done, unplug both USB cables from the PC (I find it easier to just keep them in the tablet).
Installing TWRP
Firmware/TWRP Downloads
Maven x.9.x (Currently Contains: V37-1.9.30 and TWRP)
Maven x.12.x (Currently Contains: V63-V1.12.0-20150802 and V66-1.12.20-B-20150831 Firmware and TWRP)
Special Thanks to: @ShadowCX11 for testing for me.
Be sure you are using the appropriate TWRP for your version of firmware, and do the following:
1- Extract the firmware and the SP Flash Tool to your desktop.
2- Start the SP Flash Tool, and where it says "scatter file loading" click and navigate to the folder where you have the firmware and load the scatter file (depending on device, it could be in the "Images" folder).
3- Once that is done, uncheck everything, and select "recovery" only, from the list, navigate to the TWRP image file and click "Open", then click on the download button.
4- Plug the USB cable(s)* back into your PC. At this point the flash tool will load the recovery to the tablet. DO NOT UNPLUG ANYTHING UNTIL THE FLASH TOOL SHOWS YOU A GREEN CHECK MARK TO INDICATE THAT IT IS DONE, OR YOUR TABLET COULD BE HARD BRICKED AND IRREPARABLE.
5- After you get your check mark, unplug and boot into recovery, hold the Volume + and Power button. When splash screen comes up (the 2 dogs) release the power button.
6- Welcome to TWRP
*Remember, x.12.x requires 2 USB cables to work
ROOT
You can get root by flashing the latest SuperSu zip file located here, be sure to download the flashable zip.
Otherwise, for root, you can use the KingRoot app located here, (get the apk, or "Download for Android") and if you don't want a Chinesse Super User app, you can replace it with the ChainFire SuperSu by going here.
NOTE: This method of replacing KingRoot with SuperSu no longer works properly, and results in a bricked device.
Device Tree
GitHub
CREDITS
@vampirefo (for the CWM Recovery and teaching me about TWRP, there would be no recoveries if it wasn't for him!)
@Bogram (for the lk.bin patch trick)
@smartmanvartan (for the flashing guide)
Reserved
Reserved #2
Hello! I've had my Maven Pro for a couple months now and I still haven't rooted it like I have with the rest of my devices. I'd love to do it too, but reviewing your instructions, I found that my version number is way different. V66-V1.12.20-B. will that version patch tool still work for it? is there an update that it's refusing to download? Thanks!
Edit: on top of this, i can't get it to even connect (step 2) with any of my microUSB cables. (they work with my other devices)
equinox13 said:
Hello! I've had my Maven Pro for a couple months now and I still haven't rooted it like I have with the rest of my devices. I'd love to do it too, but reviewing your instructions, I found that my version number is way different. V66-V1.12.20-B. will that version patch tool still work for it? is there an update that it's refusing to download? Thanks!
Edit: on top of this, i can't get it to even connect (step 2) with any of my microUSB cables. (they work with my other devices)
Click to expand...
Click to collapse
Ooh, a v12, sorry friend, lol. Make sure the tablet is off, and be ready with "Device Manager" open, the preloader only shows up for a bit, then it disappears. The patch tool should still work for you, but the TWRP recovery may not. If it doesn't, the CWM recovery will after I modify it, because it's non-touch.
If neither recovery works for you, you can give me a copy of your "boot.img" file, and I can convert TWRP or CWM to work on your tablet. Also, I've changed the guide up top to include other root methods.
If you have any trouble, by all mean, post, and I'll try to help you through it
Regards,
Nepo
EDIT:
A friend found some V12 firmware, and I'll be uploading it soon. I can get a boot.img file from it to make a recovery.
My maven pro is stuck in a bootloop after I rooted now I don't know what to do. I can't even shut it down
GartimusPrime said:
My maven pro is stuck in a bootloop after I rooted now I don't know what to do. I can't even shut it down
Click to expand...
Click to collapse
You can reflash firmware while it is in a bootloop, I've done this many times. If you have everything set up, drivers, SP Flash Tool, firmware, etc..
Do the following:
1) Startup the Flash Tool and Load your firmware, as described in the OP (be sure to "uncheck" the Preloader)
2) Plug in your micro USB cable to both the PC and the tablet
3) Press and hold the "Reset" button located on the back
4) Click the Download button, then let go of the reset button, it should start flashing the firmware.
If it doesn't the first time, retry steps 3 and 4. I've had it fail the first time before, but work on the second.
Good Luck and let me know how it goes. Also, if the battery is completely drained by the time you read this, just flash firmware normally (again, uncheck the preloader). The tablet has to be powered off to flash it anyway.
Regards
Nepo
So after reflashing my tablet (a Canadian V12 that had V68, and flashed to V66 trying to unlock the boot loader and install CWM), USB doesn't work. The port doesn't output any voltage, and neither does the keyboard connector. The tablet acts like nothing is there, as does the PS3 controller I tried. Also, before, Firmware Update would say there's no updated firmware. Now, it doesn't seem to do anything. I flashed every partition except preloader, MBR and ebr, and the sec partitions. Do I have to reflash again, or is there something else I can do?
On a completely different note, I tried flashing a patched lk.bin, and it failed with an error I don't remember (I had temporary access to a PC).
One more thing that was quite interesting to me. It seems if you reboot into recovery or bootloader from Android (APM+ or root), you're then able to access the recovery with Power + Vol. Up. Is this known, or was it a fluke?
ShadowCX11 said:
So after reflashing my tablet (a Canadian V12 that had V68, and flashed to V66 trying to unlock the boot loader and install CWM), USB doesn't work. The port doesn't output any voltage, and neither does the keyboard connector. The tablet acts like nothing is there, as does the PS3 controller I tried. Also, before, Firmware Update would say there's no updated firmware. Now, it doesn't seem to do anything. I flashed every partition except preloader, MBR and ebr, and the sec partitions. Do I have to reflash again, or is there something else I can do?
On a completely different note, I tried flashing a patched lk.bin, and it failed with an error I don't remember (I had temporary access to a PC).
One more thing that was quite interesting to me. It seems if you reboot into recovery or bootloader from Android (APM+ or root), you're then able to access the recovery with Power + Vol. Up. Is this known, or was it a fluke?
Click to expand...
Click to collapse
No USB is a new one on me, I wish I had a x.12 version of this tablet to test on (mine's x.9) I'd try a re-flash, this time, do everything but the preloader, the reason for not flashing a preloader is because it sometimes semi-bricks one of these tablets.
Interesting note, there was a guy on the Viking thread (RCT6303W87DK) that flashed CWM without unlocking his bootloader, and everything is working fine for him...
Regards,
Nepo
PS, Power + Vol Up is the standard way to enter recovery on this device (I have the Xposed APM+ apk installed too)
NepoRood said:
No USB is a new one on me, I wish I had a x.12 version of this tablet to test on (mine's x.9) I'd try a re-flash, this time, do everything but the preloader, the reason for not flashing a preloader is because it sometimes semi-bricks one of these tablets.
Interesting note, there was a guy on the Viking thread (RCT6303W87DK) that flashed CWM without unlocking his bootloader, and everything is working fine for him...
Regards,
Nepo
PS, Power + Vol Up is the standard way to enter recovery on this device (I have the Xposed APM+ apk installed too)
Click to expand...
Click to collapse
So just a quick question: Is the device /dev/recovery for sure recovery? I want to see if I can just use dd to flash recovery.
ShadowCX11 said:
So just a quick question: Is the device /dev/recovery for sure recovery? I want to see if I can just use dd to flash recovery.
Click to expand...
Click to collapse
Yes, to pull a copy from a running tablet you use dd, and the path is: /dev/recovery
So, I'd do it this way, using adb:
Code:
adb push NAME_OF_RECOVERY.img /data/local/tmp
# Wait for it, then type:
adb shell
#Followed by:
dd if=/data/local/tmp/NAME_OF_RECOVERY.img of=/dev/recovery
#After it finishes:
reboot recovery
Okay, I got CWM installed! Now to see if I can find a way to build TWRP...
ShadowCX11 said:
Okay, I got CWM installed! Now to see if I can find a way to build TWRP...
Click to expand...
Click to collapse
Great! Is the CWM in portrait or landscape? You can always try to port the one I built for the x.9's, just unpack stock recovery, unpack TWRP, swap out the prebuilt kernel and repack.
NepoRood said:
Great! Is the CWM in portrait or landscape? You can always try to port the one I built for the x.9's, just unpack stock recovery, unpack TWRP, swap out the prebuilt kernel and repack.
Click to expand...
Click to collapse
It's in landscape, and works quite well! I just like the touch interface a bit more. I'll try the kernel replacement.
ShadowCX11 said:
It's in landscape, and works quite well! I just like the touch interface a bit more. I'll try the kernel replacement.
Click to expand...
Click to collapse
I prefer TWRP as well, that's why I built it
The only reason I don't have one posted for x.12 users is I can't test it. If you get it to work properly, let me know and I'll add it to the OP so others can benefit. :good:
If not, I can do some builds for you to test, if you don't mind. I have the x.12 kernel in my repo
NepoRood said:
I prefer TWRP as well, that's why I built it
The only reason I don't have one posted for x.12 users is I can't test it. If you get it to work properly, let me know and I'll add it to the OP so others can benefit. :good:
If not, I can do some builds for you to test, if you don't mind. I have the x.12 kernel in my repo
Click to expand...
Click to collapse
Yeah, I can't figure out how to extract the kernel, because I don't usually have access to a PC. However, I'll take some testing builds if you can make them.
Also, back to the USB issue, a reflash of everything except preloader didn't fix it. However, checking the firmware update now tells me that this is the latest version (which is definitely wrong, since I had v68). It must be an incompatibility between the USA and Canadian variants. If you find a Canadian firm dump, can you send me a link?
---
Hmm, okay.
So I just took a look at the model number on my box, and it's RCT5213W87DKF. That extra letter is what changes this a bit. I'll try seeing what I can dig up in terms of OTA updates, and I'll keep posting about what I find.
---
Okay, so after a few packet captures, I found the tablet makes a GET request to http://tablet12.gyrodock.com:2300/OtaUpdater/android?device=RCT6213W87DK with the User-Agent rk29sdk/4.0, but the server returns a 404 page. When I do this in the browser, however, I get something quite peculiar happen, which interests me. Most of the other places on the site return a Tomcat 404 that has the path in the parenthesis. However, for the OTA URL, it just has empty parenthesis. POST requests to that URL return a 200 OK with no return data, which is also interesting. I'll keep hunting around.
Some people might not have a PC to run flash_tool on, so here's how you can flash recovery/uboot/mbr/ebr2/logo/sec_ro from within Android
I'll use recovery as an example. I'm using a V12 tablet, so steps might be different if you have a V9. I tried to make this guide as revision-agnostic as possible, so correct me if I mess something up.
Root your device. The method I use is KingRoot, because it doesn't require any weird things. You can uninstall KingRoot and flash SuperSU later.
Download a recovery image. Make sure if you have a V12 tablet, you download a recovery image for V12, and a V9 recovery for a V9 tablet, or you'll brick your recovery. I personally prefer TWRP, because it has more features and a nicer UI, but CWM works too.
Get shell access. You can use a terminal emulator.
Type in su, and give the terminal superuser access on your device.
Type in dd if=/sdcard/Download/mavenVY_XXX.img of=/dev/recovery, where Y is 9 or 12, and XXX is CWM or twrp3.0.2. This will flash the recovery image.
Finally, type in reboot recovery. This should reboot into your custom recovery! It might also enable Power + Vol Up access to recovery, however, this hasn't been confirmed.
All the other partitions are similar, just replace the references to recovery images with the respective file names for the raw partition, and /dev/recovery with /dev/[PARTITION]. You can NOT flash the android or usrdata partition while in Android or you'll most likely soft-brick your tablet, however, you can boot into TWRP and go to the terminal and do the flash. You must copy your disk images to /tmp when doing so however, or you'll probably lose the disk image during the flash, effectively causing a brick.
Hope this helps people out!
ShadowCX11 said:
I've found out that it seems the v12 tablets strictly enforce the checksums of partition images, so flashing a custom recovery or uboot does not work with flashtool.
Click to expand...
Click to collapse
Nice addition, but all you have to do is disable it in the Checksum.ini file (change the 1 to 0):
Code:
[IsEnableChecksum]
CHECKSUM_SWITCH=0
I did that for the v9 versions, but only uploaded the v12 firmware...
NepoRood said:
Nice addition, but all you have to do is disable it in the Checksum.ini file (change the 1 to 0):
Code:
[IsEnableChecksum]
CHECKSUM_SWITCH=0
I did that for the v9 versions, but only uploaded the v12 firmware...
Click to expand...
Click to collapse
Oh... makes sense...
ShadowCX11 said:
Oh... makes sense...
Click to expand...
Click to collapse
I'm glad you posted that info, it'll be super handy for folks that may not have access to a PC, or would rather use their device instead of a PC :good:
EDIT 2019: rooting with TWRP from 038 read at the bottom of this post
HOW TO.... Stock, Update, custom recovery and root your s60 !!!!
Disclaimer: if you brick your phone, it's your fault, i have tested this way of rooting my s60 now for a several times and it works 100%
SO READ TWICE, CHECK TWICE, BEFORE YOU CLICK ONCE !!!!! i will not take any responsibility !!!
!!! ONCE AGAIN, READ THE WHOLE GUIDE BEFORE YOU START !!!
OK, now we start:
Thanks to everybody who contributed and made the root possible, here in this thread (Cesarq, OpenMinded, Tuschi, BetonJohn, etc.......) the software in the link further down, is the collected data, freely available in the net and linked in the original Thread several times, i have only bundled one package and wrote this, hopefully usefull guide.
in principle do as follows: (I will only explain once how to sideload or load via recovery, afterwards i will only state what kind and what file)
Prerequisites
- switch phone OFF
- download my collection of the essential s60 files : Here is my collection
EDIT 2019: - grap the 035 update here from the Thread: Thanks to tusch00101
i did not find the 038 update as a single zip file to download. if somebody could provide it ?
(there are ALL files included to flash stock, update to .035, flash twrp recovery and root.)
(this is for Win7 x86, you have to check if it works for other versions yourself, sy..)
- install USB drivers
(for recovery and adb !!! There are two different USB drivers needed)
- install "minimal ADB and fastboot"
- copy the two updates (update032.zip & update033.zip) into the folder, where you have installed "minimal ADB and fastboot" (makes live easier later)
- install QPST (the version of QPST is the one from Androidmtk and should be virusfree.)
(The version of QFIL in my collection is the one without reboot, so you have to reset/reboot your phone manually (resetbutton below hatchdoor on your phone) whenever stated in this guide.)
- format micro SD card in fat32 ! and copy SuperSU.zip onto it. Then insert microSD card into your phone.
- switch phone ON
- enable Developer Options, by going into the settings menu and go to "About Device". tip/touch/tap 7x the -build number- field. A message will appear: "You're now developer" (something like this)
- enable USB-debugging. Go again to settings, then "Developer Options" and enable USB-debugging.(flick the switch)
- connect a WORKING USB cable to your phone (Not to your PC atm !!!)
- dial *#06# to see the iMEI('s) of either one or both simslots. dial #02# to check what firmware version you are on
(just for your info: It looks like the "S" in the firmware version (LTE_X.....) indicates, that SingleSim only is activated, while the "D" stands for DualSim activated. my s60 had an "S"... )
(In my phone the second Sim slot (under the microSD card slot), was blocked with a small piece of, simcard shaped, black plastic. With the help of some tweezers the scrap
plastic was gone easily. Anyway --- BE CAREFULL --- when removing it.)
If you are allready on an LTE_D... Firmware version 033 or above (atm only confirmed up to 035) and you want to root with custom recovery, you only need to follow the last step in this guide ("getting twrp and Root") everybody else, continue reading...
getting twrp (for saving your old firmware only)
- power off phone.
- start minimal adb on your PC
- start QFIL (part of QPST) on your PC
- press VOL+ & VOL- simultanousely and connect phone with PC (it will vibrate once, top right LED starts blinking red, screen stays black) (- DOWNLOAD MODE -)
(just in case: to leave Download mode, disconnect phone from PC, press and hold power button for apprx. 15 seconds)
- as soon as you connect your phone to the PC, QFIL should show the Phone/port in the topline allready
(if not, either try to manually select the port, or you probably still have a problem with the USB drivers or the USB cable !)
- QFIL - tick "Flat Build" (top left)
- QFIL - select Programmer, "browse" to the saved location of "update-twrp-recovery-nobootpatch" and select the "prog_emmc.blablabla...mbn" file and doubleclick
- QFIL - "load XML" ,select rawprogramm, doubleclick, select patch0, doubleclick
- QFIL - click on "download"
- if everything was OK up till now, it should start download - BE PATIENT- and read the status window on QFIL, when it shows "finish download"....
- disconnect phone from PC
- press and hold simultanousely POWER and VOL+ (- RECOVERY MODE -) AND...
- ... use a small tool to push the reset button on the phone under the hatch, while still pressing Power and Vol+ !
- the phone should now be in twrp recovery. If so, do a full backup now to your (allready inserted and fat32 formatted) microSD card!!!
when done
- Power off your phone !
flashing stock 31.02
- enter download mode again (Vol+ & Vol-, connect phone to PC.......)
- this time in QFIL, browse in programmer path to "s60_stockFW_31.02" and select the programmer from there
- load XML's (the ones that belong to Stock31.02)
- start download... this will take a while !!!! BE PATIENT !!!!
- when QFIL status window shows finish download, push the reset button on the phone and let it reboot.
(it is normal, that the phone should restart itself 2, maximum 3 times during the first startup, but sometimes it ends up in a bootloop (Cat Logo, reboot, CAT logo, reboot, etc, etc, .......))
(The bootloop mainly happens, if you clear, in twrp recovery, the whole OS, or if you came from another firmware version (LTE_S... -> LTE_D... i.e., but that's no issue either...).
- if it ends up in a bootloop, no worries, just continue ! Believe me, i did this process now several times !
you are back on stock 31.02 !
- Power off your phone again
Updating to 032
- bring up minimal ADB sideload on your PC (start it, if not allready done in previous step (getting twrp)).
- press and hold POWER and VOL+ button on your phone
- when in stock recovery select (with Volume keys) "adb sideload" and click the Powerbutton
- connect your phone to the PC
- on PC, type into the black ADB Terminal window "adb sideload update032.zip" and hit enter
- if correct USB drivers are installed, phone will start downloading the update now.
- when complete, select clear cache, and clear data then reboot your phone.
(again, same as in the step (flashing stock), if bootloop, no worries, just continue, if it boots up, let it boot up and then..)
you're on 032 now
- Power off the phone again
Updating to 033
- do the same steps as described under "Updating to 032" only difference, type in adb window " adb sideload update033.zip"
EDIT2019: - do the same steps for 035 and 038
(After updating to 038, your phone should boot up normally by now. NO MORE BOOTLOOP !)
getting twrp and Root
- this is the same step as above "getting twrp" only difference, this time, no backup needed and...
- when in twrp-recovery, select "install" browse to your micro SD-card, and...
- install SuperSU.zip from SDcard.
- once more, clear cache and data and reboot.
The phone should boot up now, you should be on FW 033, with custom recovery and root !!!
That's all !!!
Oh, one last thing, whoever is having an s60, where only one simslot is working, this guide unlocks the second Simslot as well !!!
Also the problem, some people had, following the other guides (incorrectly) ! (me included) ! , by not using the right QFIL (the one without reboot), in the old Thread, resulting in a
not working WIFI is no issue anymore
EDIT 2019 !!!
Getting TWRP with stock 038 thanks to: CDMCCDMC for the addition !
https://forum.xda-developers.com/showpost.php?p=77978181&postcount=135
thanks for the awesome guide. works perfectly, but i will say every time I plugged my phone in it recognized it as a new device and had to reinstall drivers.... the first few times i did it i thought QFIL froze so i unplugged to reset, this caused an install failure that could not be rectified. I fixed this by uninstalling and reinstalling the drivers from step one and being more patient.
Dear adtbm,
the firmware updates (both) are extracted... became signature failure.
Please update your very useful package... thx
best regards
yanardag
Please i cant use my phone it hangs in a bootloop i need the update.zip 32 and 33
Yanardag said:
Please i cant use my phone it hangs in a bootloop i need the update.zip 32 and 33
Click to expand...
Click to collapse
Thanks for letting me know !
You can get the files from OpenMinded link here
You only need the two update files.
Untill i have updated my package.
EDIT: Package is updated now !
After flash 32 it is starting and i see the wizzard.
But after flashing 33 and rooting i have no wifi.
İ flashed 31.02 then update 32 and after this i update it ota
To 33 and last to 35 and everything is working root (supersu) (dont use magix)is working with 35 very well. Everything ok (xposed, gravity and so on) thx
Yanardag said:
After flash 32 it is starting and i see the wizzard.
But after flashing 33 and rooting i have no wifi.
İ flashed 31.02 then update 32 and after this i update it ota
To 33 and last to 35 and everything is working root (supersu) (dont use magix)is working with 35 very well. Everything ok (xposed, gravity and so on) thx
Click to expand...
Click to collapse
If you don't have Wifi after going to 033, you didn't followed the part of "getting twrp" correctly.
"...... - if everything was OK up till now, it should start download - BE PATIENT- and read the status window on QFIL, when it shows "finish download"....
- disconnect phone from PC
- press and hold simultanousely POWER and VOL+ (- RECOVERY MODE -) AND...
- ... use a small tool to push the reset button on the phone under the hatch, while still pressing Power and Vol+ !
- the phone should now be in twrp recovery. ....."
If you let the phone reboot after flashing the recovery, it will overwrite the boot and your wifi is gone !
But nice to hear, that everything is OK now. Do you have problems with 035 ? some people report, that they having issues with the display camera on 035 ...
Sorry for this silly question, but i´ve seen that in other models once you install twrp then you can flash super su, why here you have to downgrade to 0.31 first?
Thank you in advance.
javizap said:
Sorry for this silly question, but i´ve seen that in other models once you install twrp then you can flash super su, why here you have to downgrade to 0.31 first?
Thank you in advance.
Click to expand...
Click to collapse
Hi,
not sure, if you have read the complete guide, or if you have read through the 28 pages of the original Thread.
I think, it could be possible, (but i did not tested it) to flash the recovery via QFIL directly and then install SuperSU, without going back to 031. But since there are models of the s60 out, where only one Simslot is available (Please read my guide), to get the second slot activated you have to flash an LTE_D... firmware and, thanks to Cesarq, we (only) have atm his 031 firmware available, which is luckywise an LTE_D. firmware !
Like i mentioned in this guide allready, i did not found out the way how to root the s60 (the credit goes to Cesarq) and i also did not find out, how to update to 033 (this credit goes to OpenMinded), i have only collected the software & tools, bundled it and wrote this guide, with the available information written throughout the 28 pages of the original Thread.
So please feel free and test it and write us your result !
ok, just did my s60 last night, everything seemed to go just as described. i just checked and it seems it took the update and the dual sim activation. it didnt take root tho. i tried root checker and titanium and both say no root access. maybe i did the final step wrong? i tried it again with no success. am i supposed to be loading the nobootpatch recovery in qfil as the last step and then install su? thats how i attempted it. any help would be greatly appreciated. thanks in advance!
adtbm said:
If you don't have Wifi after going to 033, you didn't followed the part of "getting twrp" correctly.
"...... - if everything was OK up till now, it should start download - BE PATIENT- and read the status window on QFIL, when it shows "finish download"....
- disconnect phone from PC
- press and hold simultanousely POWER and VOL+ (- RECOVERY MODE -) AND...
- ... use a small tool to push the reset button on the phone under the hatch, while still pressing Power and Vol+ !
- the phone should now be in twrp recovery. ....."
If you let the phone reboot after flashing the recovery, it will overwrite the boot and your wifi is gone !
But nice to hear, that everything is OK now. Do you have problems with 035 ? some people report, that they having issues with the display camera on 035 ...
Click to expand...
Click to collapse
Nope everything is well. 35 runs without any bugs. For me is importend that xposed is running and that does.
yesca213 said:
am i supposed to be loading the nobootpatch recovery in qfil as the last step and then install su? thats how i attempted it. any help would be greatly appreciated. thanks in advance!
Click to expand...
Click to collapse
I asume, you have SuperSU copied onto your microSC card ?!
When you have finished flashing the nobootpatch recovery (QFIL shows finish download), you have to disconnect the phone from the PC, push Vol+ and Power and Reset (under the hatch) at the same time.
Otherwise Bootloader gets overwritten, your Wifi is gone, no custom recovery and no root.
If you are not using the version of QFIL from my package, you probably have a version that automatically reboots when download is finished and you're screwed !!!
If you did it correctly your phone should boot into twrp custom recovery and you should be able to install SuperSU from SD.
adtbm said:
I asume, you have SuperSU copied onto your microSC card ?!
When you have finished flashing the nobootpatch recovery (QFIL shows finish download), you have to disconnect the phone from the PC, push Vol+ and Power and Reset (under the hatch) at the same time.
Otherwise Bootloader gets overwritten, your Wifi is gone, no custom recovery and no root.
If you are not using the version of QFIL from my package, you probably have a version that automatically reboots when download is finished and you're screwed !!!
If you did it correctly your phone should boot into twrp custom recovery and you should be able to install SuperSU from SD.
Click to expand...
Click to collapse
Yes I did have it copied and installed it. I went back and did it again and hit wipe dalvic cache instead of going back in the recovery menu and wiping cache and data. Up and running 33 rooted, everything seems good so far! Thanks [emoji2]
Sent from my S60 using Tapatalk
adtbm said:
Hi,
not sure, if you have read the complete guide, or if you have read through the 28 pages of the original Thread.
I think, it could be possible, (but i did not tested it) to flash the recovery via QFIL directly and then install SuperSU, without going back to 031. But since there are models of the s60 out, where only one Simslot is available (Please read my guide), to get the second slot activated you have to flash an LTE_D... firmware and, thanks to Cesarq, we (only) have atm his 031 firmware available, which is luckywise an LTE_D. firmware !
Like i mentioned in this guide allready, i did not found out the way how to root the s60 (the credit goes to Cesarq) and i also did not find out, how to update to 033 (this credit goes to OpenMinded), i have only collected the software & tools, bundled it and wrote this guide, with the available information written throughout the 28 pages of the original Thread.
So please feel free and test it and write us your result !
Click to expand...
Click to collapse
I took your advice and rooted without downgrading firmware. My CAT is double SIM from factory and on 0.35 OTA.
I followed your guide but jumped from backup with twrp to install supersu, following all the steps from there.
Until now everything working fine with root.
One more time I can say that people on XDA is the best!
Regards
Dear friends,
How can i uninstall google assistant apk?
When i delete it the phone not restart and ended in a bootloop.
When i deactivate it the same bootloop.
very very good
Hello to this wonderful group. I did the rooting and it worked wonders, I was very disappointed with my Cat s60, for not being able to use the second sim and for the poor quality of the camera. After the root it became dualsim and the camera improved a lot. in addition to everything that means to be root. I am very grateful to ADTBM and to all those who made this possible. thanks thanks. regards
Yanardag said:
Dear friends,
How can i uninstall google assistant apk?
When i delete it the phone not restart and ended in a bootloop.
When i deactivate it the same bootloop.
Click to expand...
Click to collapse
Hi Yanardag,
i have the same problem. Unfortunatley Android IS Google . I really don't know how to disable it. Did you try to freeze it with Titanium ?
That's the only thing i could think of. I am annoyed by that Google stuff as well (especially the google assistant....)
This is one of the reasons, why i had to redo my s60 a several times.
So if anybody here finds a way to disable Google assistant, pleasse let us know !!!
@varonv: Nice to hear and thanks for the feedback !
Hi,
I am on 027 now. No OTA update available. Can I try this guide?
Thanks
freeze it with Titanium
adtbm said:
Hi Yanardag,
i have the same problem. Unfortunatley Android IS Google . I really don't know how to disable it. Did you try to freeze it with Titanium ?
That's the only thing i could think of. I am annoyed by that Google stuff as well (especially the google assistant....)
This is one of the reasons, why i had to redo my s60 a several times.
So if anybody here finds a way to disable Google assistant, pleasse let us know !!!
@varonv: Nice to hear and thanks for the feedback !
Click to expand...
Click to collapse
I froze it with Titanium: no problems whatsoever.
This Guide works on win 10 also. .. But ending in Win 10 Test mode
The BLU VIVO XL4 has arived.
Sorry this guide is not for very new users, it relies on certain amount of prior knowledge.
**NOTE**
Unlocking Bootloader WILL set warranty flag to "NO"
Make the read-back backup, BEFORE unlocking, so there is a possibility to restore warranty to "yes"
Getting SPFlash Tool to work on BLU VIVO XL4
I used sp flash tool version 5.18.28
Needs custom DA file and Auth file. Both have been found from a near clone device.
Open flash tool select the DA file and Auth file from the link below.
add the scatter file from archive. There is a preloader file in the archive also. This is needed for spflash tool to open the Auth file.
Stock Rom and Auth file
Then follow the guide found on youtube.
Not planning to go into too much detail about the actual pulling of the firmware, as there is already
a fantastic guide with step-by-step photos and also a video.
Just the basics
Pull stock rom with spflash tool once just from the "boot region" to get the preloader file.
Process that file with the Wwr_MTK tool to get partition table information.
And one more time pull as one large binary file from the "user region" then split it into
individual images using the tool called "Wwr_MTK" it can be found on other site(Hovatek). I cannot put a
link as it is against forum rules (no advertising other forums)
But there is a youtube video that describes the process. And gives link for download of the tool.
**NOTE-1**
The Wwr_MTK tool did not have the correct chip (mt6762 In fact the "family class" for the chip is mt6765) as an option. Because of this you will need to add it to the tool before using it. Open the downloaded zip.( I used "WwR_MTK_2.40_Eng" ). Open "Template.ini" with text editing software, in the section labeled "CPU" add "MT6765 2" , keep same format as the rest of the file. Save the changes and close Template.ini.
Now when you run the tool, you will be able to create the scatter file as you split the rom into files.
**NOTE-2**
The tool connects to internet and downloads fresh the files and scripts when you start it. There is a 30 second ad screen displayed. If you block internet to the tool, then the add screen turns into 2 minute wait screen. I am not suggesting that you hack the tool to by-pass it, just letting you know what to expect.
IT IS HIGHLY RECOMMENDED TO MAKE YOUR OWN FULL BACKUP BEFORE PERFORMING THESE STEPS
AFTER YOU HAVE MADE FULL BACKUPS
Now to start modifying
DOWNLOAD
UNLOCK BOOTLOADER
unlocking bootloader is no more complicated then then enabling OEM unlock toggle in dev options menu.
Then performing Command in terminal. Just like so many android devices.
Unlock Bootloader
1. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select more "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
2. Open cmd or power shell terminal
3. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
4.Once the phone has finished loading into fastboot mode type this command
Code:
fastboot oem unlock
I also did --MIGHT be an optional step
Code:
fastboot flashing unlock
Do not think both were needed.
After each command when phone was rebooted,
it took extra time to open. But did not show the normal recovery screen while
it did the factory reset. But a reset did happen both times,
as I had the setup wizard each time.
Even after unlocking bootloader, doing a "fastboot boot *xyz.img" (boot or recovery test images)
Phone would only cycle to off then do a full reboot. Doing "fastboot flash boot boot.img" does flash the boot.
And "fastboot flash recovery recovery.img" does flash the recovery.
TWRP
1. Download TWRP From Link above
2. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
3. Open cmd or power shell terminal
4. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
5. Now give the command to flash twrp, assuming you downloaded the file to default download folder
Code:
fastboot flash recovery %userprofile%\downloads\TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img
5. Reboot to twrp. Needed to boot directly to twrp, or stock recovery will be re-flashed by phone.
Code:
fastboot oem reboot-recovery
Once inside twrp It is asking for password to unlock (decrypt)***automatic decrypt not work on this device as of YET***
this is supposed to be same password used to unlock phone.
Because this twrp does not work with encryption, every time you reboot you will have to select language, if changed from default.
To get recovery to be functional, you need to make phone patched for both "DM-Verity" and "Force-encryption"
I do this with
"Universal Disabler"
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
There is similar utiliy built into this Recovery image.
to use the built in option , Select ADVANCED, Then RM Forceencrypt
This will flash the lazypatcher with options set to remove encryption both in boot.img and /vender/*fstab : remove dm-verity.
--OR-- manually do the following steps
Steps
1. Download Zip from Link above.
2. Open TWRP
3. Open Wipe menu
4. Select format /data
5. Key in "YES" and swipe
6. Return to Home Page of TWRP
7. Choose reboot menu then recovery
8. Recovery should now have access to Internal memory (temp for now)
9. Use abd push to put the zip file downloaded above to internal memory
Code:
adb push %userprofile%\downloads\Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip /sdcard/
10. Select install menu , and install the Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip
Do not rename the file. It installs and makes the patch base on the file name.
If you want to have root also, then flash Magisk at this point.
Now the dm-verity and force encryption are off. You can flash gsi custom rom, if you desire. At the moment, I have only been able to boot the phone with working cell data and calls on the PHH-Phusion --vanilla builds. Do not know why the gapps versions do not allow rill to function.
As of the writing of this I have put up V4 of the TWRP port. This version uses the correct mount points for this phone, not the ones from the source of the port. Also corrected the device name in default.prop, to match device name. Build fingerprint has been left as is. Fixed the micro sdcard name and OTG names. Added mipe to the "misc" /"para" partition to escape a factory reset recovery loop that [uu]could[/u] happen under certain situations.
And my prefered ported recovery from LRTeam TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img.
DOWNLOADS
Files
1. Sp Flash tool (v 5.18.28 or newer) https://androidmtk.com/smart-phone-flash-tool
2. stock XL4 ROM, DA file, TWRP all in shared folder https://androidfilehost.com/?w=files&flid=287088
3. stock Xi+ ROM, TWRP in shared folder https://androidfilehost.com/?w=files&flid=287703
4. Unviversal DM-Patch disable tool thread
5. Youtube Guide Video to use backup image splitter tool "WWR_MTK" https://www.youtube.com/watch?v=GMAytZ56hac
Kernel sources have been published 12-12-2018, by BLU
I have them synced to GitHub while I make test builds.
https://github.com/mrmazakblu/BLU-VIVO-XL4-kernel
Default defconfig should be arch/arm64/config/k62mv1_64_bsp_defconfig. Based off of build description in "getprop"
Built kernel has not been able to be booted yet.
TWRP is first ported and provided thanks to @Voinea12
.
placeholder not really welcomed here on XDA
just pm a moderator or report this thread when you`re ready to upload something, until then, thread closed
After seeing that the Blu vivo xl4 requires an "auth file" in order to flash with spflash tool, I asked BLU to supply the file.
They responded with a big fat NO.
.......
.......
THE NEXT DAY THE FILE WAS POSTED ON A DIFFERENT THREAD.
SO THERE HELP WAS NO LONGER NEEDED.
Just made successfull readback on preloader. and currently reading full rom.
will post link when done.
here is auth file and DA file I used.
pulled firmware is here.
there are more images in complete firmware, but the ones included should be enough , as long as you NEVER do format all from spflash tool.
STOCK ROM
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Working version is available now
Thread was opened.
mrmazak said:
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Click to expand...
Click to collapse
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
psychofad said:
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
Click to expand...
Click to collapse
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
mrmazak said:
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
Click to expand...
Click to collapse
No, I got the readback of the EMMC_USER just fine and ran it through the WwR MTK tool and it gave me the hex address to use for the full rom readback, t then told me
Code:
The file size is smaller than the start position of the LK (uboot). To determine the type of processor and memory, it is necessary to read the full firmware in the SP Flash Tool, specify the parameters for reading: Start address: 0x0, Lenght: 0x1D1EC00000.
So I entered those two addresses as EMMC_USER readback. If my phone is off and I just connect it to the usb without holding any keys it gives me another error.....and I'm an idiot. just figured it out as I was looking at logs, apparently I must have changed the usb speed in sp flash which changes it's pid causing it to try and read from another port. It's downloading now
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
******EDIT*****
Most of the following problems did not repeat in same way when I tried to repeat the install process.
Main issue was with simcard. But exact process to get installed and working is still not known.
-- install after already having rooted, encryption removed stock, seems to work.
-- fresh full stock rom, full encryption, then gsi seems to not work sim card.
PHH-treble gsi images do boot this device. I do not have a bug list as yet.
working:WITH encryption removed:
1. wifi
2. camera
3. fingerprint- unlock
4. music
5. video
NOT working :WITH encyyption removed:
1. cell signal
2. cell data
3. phone
4. sms
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------
working:WITH encryption enabled
1. phone
2. sms
NOT working:WITH encryption enabled
1.. everything else
EDIT
Much of the force closing problems were from a corrupted external sdcard. When I removed the card , the force close messages did not come.
Getting 4G data connection was not stable. after a full reset and rom re-install I was not able to get data connection, and only able to have connection to make calls when set to 3G connection only.
some bugs in vendor I assume will need some help solving this.
EDIT 2
Finally got around to trying again. his time I started with vanilla version of phh-treble gsi.
4G data and sms, calls in out all work. Camera , video both work.
WiFi tethering did not work.
Setup that worked :
force encryption removed with universal dm-verity patcher, ( bothboot.img and vendor partitions both edited).
magisk patched boot
Would this work on Blu Vivo XI since same chipset?
sinkoo1979 said:
Would this work on Blu Vivo XI since same chipset?
Click to expand...
Click to collapse
It should. I have been working with few users with Xi+ it works for them. And another user of Xi provided a twrp port, but no details on if this read-back worked. It must have, I suppose it must have.
Please do try to do the readback for your self, and share the files. will help with twrp if I can
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
mrmazak said:
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
Click to expand...
Click to collapse
Can any of this be done without a computer
Decaphyz said:
Can any of this be done without a computer
Click to expand...
Click to collapse
No, you need fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
mrmazak said:
No, need you fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
Click to expand...
Click to collapse
Oof
mrmazak said:
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
Click to expand...
Click to collapse
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
IndifferentBear said:
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
Click to expand...
Click to collapse
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
thanks dude! can you give me the command to run in terminal to do it? ill try that first, then ill try flashing stock recovery!
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
but i was required to wipe the sys, data, cache, and dalvik/art to have a clean install.
---------- Post added at 03:33 AM ---------- Previous post was at 02:47 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
YO! Oaky so basic laly when i flashed that misc recovery IT BOOTED!!!!! thank you soo much dude, your the best!