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.
Hi guys,
Sorry to bother you with that but i have an issue with my Nexus 5 and i wanted to have more information about a " solution " i found on the web.
So First, my phone got a problem with the power button (on the motherboard). I managed to find a repair shop doing that kind of repair.
Now's the real problem !
The phone won't go further than the " Google " logo.
I can access Fastboot mode but not recovery mode.
The phone is not root, official stock rom, bootloader locked, usb debugging mode : OFF.
I find something on the web but it seems the guy who write it down skipped some steps. And i'm a total noob at that so i don't understand how he managed to do what he described.
Here's the link :
(Ok so i can't post link since it's my first post.... so i will C/P his method here)
METHOD :
Things you will need
Download the Stock ROM for your device- Just Google it, I am dam sure you can find it.
Download SuperSU from UPDATE-SuperSU-v1.65.zip
UPDATE-SuperSU-V1.65.zip contains :
Superuser boot permission manager.
Update script (important) etc.
Basic Knowledge of C++ or Java
Notepad++
WinRAR
Steps to Enable USB Debugging Using Recovery Mode
Unzip the stock rom.
Within the extracted folder you will find system.img well extract it too using Ext4 Unpacker
Also extract the Update-SuperSU.v1.65.zip file.
Now open the folder where you have extracted the system.img files
Grab any .apk file from this folder and change the extension from .apk to .zip
And Copy the RSA Certificated to the Update-SuperSU.v1.65 folder (delete previous files if exist)
Also copy the build.prop to the system folder located within Update-SuperSU.v1.65 folder
Located the update-script file within this folder and edit it using Notepad++
You need to update the build.prop file after adding the following line at the bottom
persist.service.adb.enable=1
Next step is updating SQLite Database
Which can be done by adding following code to update-script file
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "UPDATE global SET value=1 WHERE name='adb_enabled'"
Cheers! You have Enabled USB Debugging
Now you can install your custom or stock rom using ADB – USB Debugging.
So basically, i wanted to know if the " solution " was possible to achieve or if the guy is plain dope, so i can backup my personal data before doing a factory reset.
Or if there's another way to backup my data.
Ah ! When i plug my phone on my PC, it isn't recognised as a Nexus 5 but as a Android Interface Bootloader (or something like that).
Sorry for the long post !
Hi, I understand what you're trying to do but I think this is not possible. The tutorial you've find on the web seems pointless to me because it just say you to customize some system files of a stock rom downloaded from google repo without saying to flash anything (or maybe this is what I understood).
Anyway I'm sorry but the only solution to this is to unlock the bootloader and flash a new system image, of course if this is a softbrick.
Have you already repair the power button? And how the phone get stucked on the logo image, bootloop or just freezed?
Hi
Thank you for replying !
The power Burton is repaired.
And to answer your question, it just freeze.
The phone turns on, "Google" logo appears and it stays that way, and after waiting a few minutes it automatically reboot and freeze again when "Google" logo shows again
In my opinion this could be a softbrick caused by something, I don't see any way out exept flashing something new. Fastboot doesn't require usb debugging enabled to work properly but unlock the bootloader means wipe all your data.
Probably your recovery has gone o something is corrupted in the system startup sequence.
You could wait for someone that can help you in another way that I don't know I'm sorry.
Well, i think i will wait and continue to search until this weekend.
Anyway ! Thank you for answering me, that was very kind
Was there anything that could have been the cause if the bootloop? Have you tried wiping /cache & /data from the recovery? If not try booting into stock recovery and preforming a factory reset. Google: "how to open nexus 5 stock recovery" android.gs has good instructions on booting into recovery. After following those instructions navigate to factory reset, press the power button, then hold the up volume button. If this doesn't work then you'll have to unlock your bootloader. But I won't get into that now. Good luck.
FYI: Don't bother with the instructions outlined in your post, they don't pertain to your situation.
Also, I can't post links as this was my first time posting here.
Hi SuBAtomicFlux,
Like i said, i can't access stock recovery, when i'm at the step where the Android robot shows a red warning sign, nothing happens when i do the key combo to enter into the Stock Recovery Mode and after a few seconds, the phone reboots by itself.
But thank you for trying to help me !
Since i am afraid, that my Guide will dissapear in the other Thread,
i post this guide in a new Thread !
I have just uploaded a collection of, how i have named it, - s60 essentials - there are ALL files included to flash stock, update to .033, flash twrp recovery and root.
(this is for Win7 x86, you have to check if it works for other versions yourself, sy..)
Here is my collection
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 !!!
Thanks to everybody who contributed here in this thread (Cesarq, OpenMinded, Tuschi, BetonJohn, etc.......) the software in the link
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)
Prerequists
- install USB drivers (for recovery and adb)
- install "minimal ADB and fastboot"
- copy the two updates (update032 & update033) 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.
- connect a WORKING USB cable to your phone (Not to your PC atm !!!)
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, 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 !
- tick in QFIL 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+ 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 onces 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 at the first start, 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, but that's no issue either...)
- if it ends up in a bootloop, no worries, just continue ! Believe me, i did the 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 - RECOVERY MODE -
- 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 drivers are there, 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"
After updating to 033 your phone should boot up normally now, NO MORE BOOTLOOP !
getting twrp
- 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 !!!
Would a TWRP or fastboot flashable stock recovery let us apply future OTA updates without wiping and starting from stock 031 if we're using systemless root like Magisk?
From stock recovery you can reboot to bootloader which puts us in fastboot (you can select boot mode with Vol +/-), so I'm thinking if we could boot TWRP from fastboot (without flashing, obviously), we could back up the stock recovery. Then when the next update comes around, we flash stock recovery back, apply the update, then reflash TWRP.
I tried fastboot boot recovery.img from update-twrp-recovery-nobootpatch but I got
FAILED (remote: unknown command)
and rebooting into recovery from there just got me stock recovery which makes sense.
QCN please
Hi guys, can anyone share me QCN backup of S60 because i've lost it! Thanks.
Last update for Android 6.0 was from 766 days ago.
Any suggestions on how to patch?
Thanks a million
I've been trying to root my Ulefone armor 3WT for about a year now and still haven't gotten anywhere.
Here is how far I've gotten so far (with issues);
1. Fastboot commands - Cannot do fastboot commands in CMD, correct drivers are installed. Fastboot in CMD cannot find the device when the phone boots into fastboot mode. I can use ADB just fine.
2. The MediaTek flash tool - Cannot find a proper .scatter file to flash to the phone, nor can I create one.
People seem to be having lots of luck with number one, but I cannot figure out how they're getting fastboot to work in CMD.
Would like some help from anyone that has rooted this type of phone, or just any suggestions to help me with this thing.
Solved, (by radiomean-uk) follow this guide:
Here is the relevant post (hope I don't break and rules...)
=====================================================
=====================================================
Instructions:
1. Flash recovery.img via spflashtool or platformtools.
2. Boot to TWRP.
Touchscreen is not working properly in TWRP on our gadgets. You need to use OTG cable and mouse. Skip enter password form. Default language is russian so you can choose your in options.
3. Install disable force encryption and magisk (if you need root) via TWRP.
4. Boot to system. Enjoy.
Download link (merge go ogle together)
drive.go ogle.com/open?id=1J0HlsJYTyJUGAHjIXYMDUXye4DD9kEAC
Click to expand...
Click to expand...
Click to collapse
Here is a clickable download link: https://drive.google.com/drive/folders/1J0HlsJYTyJUGAHjIXYMDUXye4DD9kEAC
For anyone following these are the steps i did (assuming you unlocked bootloader already):
1. Copy both zips to external sd as internal storage wont work at first
2. adb reboot bootloader
3. fastboot flash recovery recovery.img
4. unplug usb and hold power button until screen turns off
5. let go of power button, count to 2, press and hold power button and volume up together until screen turns back on
6. let go of power button when screen turns on but keep holding volume up until you see TWRP screen
7. as above post said, cancel password and swipe to enter main menu and then one square above the bottom right to enter the language menu
8. flash both zips from external sd card
9. format data (not wipe but format to get rid of encryption) - i rebooted after flashing the zips and had to go back to recovery again to format the data !THIS DOES A FACTORY RESET!
10. reboot to system this will cause it to be set up as new
11. reboot to recovery again, this time there should be no password and in install you should be able to see internal storage of the phone
12. flash magisk / anything else you want
Click to expand...
Click to collapse
oh oh i know
I had the same problem
You need a linux terminal or a linux system to use fastboot commands!! I found that the hard way...
I don't use sp flash tool so idk about the other question
TOG_WAS_HERE said:
I've been trying to root my Ulefone armor 3WT for about a year now and still haven't gotten anywhere.
Here is how far I've gotten so far (with issues);
1. Fastboot commands - Cannot do fastboot commands in CMD, correct drivers are installed. Fastboot in CMD cannot find the device when the phone boots into fastboot mode. I can use ADB just fine.
2. The MediaTek flash tool - Cannot find a proper .scatter file to flash to the phone, nor can I create one.
People seem to be having lots of luck with number one, but I cannot figure out how they're getting fastboot to work in CMD.
Would like some help from anyone that has rooted this type of phone, or just any suggestions to help me with this thing.
Click to expand...
Click to collapse
have you run the 15 sec adb fastboot installers?
maybe you can try powershell also https://github.com/PowerShell/powershell/releases
you need to add .\ in front of commands though.
hellofriendlymanveriosns said:
oh oh i know
I had the same problem
You need a linux terminal or a linux system to use fastboot commands!! I found that the hard way...
I don't use sp flash tool so idk about the other question
Click to expand...
Click to collapse
Yeah, I was actually just about to do that tonight. Hopefully, that'll work.
jjgvv said:
have you run the 15 sec adb fastboot installers?
maybe you can try powershell also https://github.com/PowerShell/powershell/releases
you need to add .\ in front of commands though.
Click to expand...
Click to collapse
I never gave PowerShell a try. I'll have to try it out.
Okay, just tried it. Powershell doesn't work either.
TOG_WAS_HERE said:
1. Fastboot commands - Cannot do fastboot commands in CMD, correct drivers are installed. Fastboot in CMD cannot find the device when the phone boots into fastboot mode. I can use ADB just fine.
Click to expand...
Click to collapse
To get fastboot working requires the "Android USB Driver" suitable to your phone is properly installed, too.
jwoegerbauer said:
To get fastboot working requires the "Android USB Driver" suitable to your phone is properly installed, too.
Click to expand...
Click to collapse
Yeah, I forgot to say I have the manufacture's driver installed.
Then it might be fastboot didn't get inplemented by OEM/carrier because they want their own tools to get used, for example MTK Flash Tool and /or SP Flash Tool. Who knows that for sure? Me not.
hellofriendlymanveriosns said:
oh oh i know
I had the same problem
You need a linux terminal or a linux system to use fastboot commands!! I found that the hard way...
I don't use sp flash tool so idk about the other question
Click to expand...
Click to collapse
TOG_WAS_HERE said:
Yeah, I was actually just about to do that tonight. Hopefully, that'll work.
Click to expand...
Click to collapse
Linux works for anyone wondering.
TOG_WAS_HERE said:
Linux works for anyone wondering.
Click to expand...
Click to collapse
I mean works for me you could try live boot.
does adb work?
hellofriendlymanveriosns said:
I mean works for me you could try live boot.
does adb work?
Click to expand...
Click to collapse
adb works on Linux and windows.
I do not have a Live disk.
Well. Fastboot works. But how do I get this thing rooted now?
I've flashed the phone with two recovery.img files so far. It doesn't seem to root it or change anything.
Used these two guides:
Ulefone Armor 3/3T customization
I just received my Ulefone Armor 3 and started customization. (http://ulefone.com/products/armor3/features.html) So far I have came upon several issues, some of which you'll find below: 1) I have searched everywhere for a TWRP port and root...
forum.xda-developers.com
unofficial twrp 3.3.1 Root Ulefone Armor 3W - unofficial twrp
Download twrp 3.3.1 Root Ulefone Armor 3W, user who own Ulefone Armor 3W can root it by following the below instructions
unofficialtwrp.com
See this thread... On the first page are the files (TWRP etc) that you need, and the instructions. I have rooted my 3WT in the past two days sucessfully. Good luck.
Here is the relevant post (hope I don't break and rules...)
=====================================================
=====================================================
Instructions:
1. Flash recovery.img via spflashtool or platformtools.
2. Boot to TWRP.
Touchscreen is not working properly in TWRP on our gadgets. You need to use OTG cable and mouse. Skip enter password form. Default language is russian so you can choose your in options.
3. Install disable force encryption and magisk (if you need root) via TWRP.
4. Boot to system. Enjoy.
Download link (merge go ogle together)
drive.go ogle.com/open?id=1J0HlsJYTyJUGAHjIXYMDUXye4DD9kEAC
Click to expand...
Click to collapse
Here is a clickable download link: https://drive.google.com/drive/folders/1J0HlsJYTyJUGAHjIXYMDUXye4DD9kEAC
For anyone following these are the steps i did (assuming you unlocked bootloader already):
1. Copy both zips to external sd as internal storage wont work at first
2. adb reboot bootloader
3. fastboot flash recovery recovery.img
4. unplug usb and hold power button until screen turns off
5. let go of power button, count to 2, press and hold power button and volume up together until screen turns back on
6. let go of power button when screen turns on but keep holding volume up until you see TWRP screen
7. as above post said, cancel password and swipe to enter main menu and then one square above the bottom right to enter the language menu
8. flash both zips from external sd card
9. format data (not wipe but format to get rid of encryption) - i rebooted after flashing the zips and had to go back to recovery again to format the data !THIS DOES A FACTORY RESET!
10. reboot to system this will cause it to be set up as new
11. reboot to recovery again, this time there should be no password and in install you should be able to see internal storage of the phone
12. flash magisk / anything else you want
radiomean-uk said:
Here is the relevant post (hope I don't break and rules...)
=====================================================
=====================================================
Here is a clickable download link: https://drive.google.com/drive/folders/1J0HlsJYTyJUGAHjIXYMDUXye4DD9kEAC
For anyone following these are the steps i did (assuming you unlocked bootloader already):
1. Copy both zips to external sd as internal storage wont work at first
2. adb reboot bootloader
3. fastboot flash recovery recovery.img
4. unplug usb and hold power button until screen turns off
5. let go of power button, count to 2, press and hold power button and volume up together until screen turns back on
6. let go of power button when screen turns on but keep holding volume up until you see TWRP screen
7. as above post said, cancel password and swipe to enter main menu and then one square above the bottom right to enter the language menu
8. flash both zips from external sd card
9. format data (not wipe but format to get rid of encryption) - i rebooted after flashing the zips and had to go back to recovery again to format the data !THIS DOES A FACTORY RESET!
10. reboot to system this will cause it to be set up as new
11. reboot to recovery again, this time there should be no password and in install you should be able to see internal storage of the phone
12. flash magisk / anything else you want
Click to expand...
Click to collapse
This seems promising, this is the only image I've found that got TWRP installed. Although, It looks like the touch screen will not work in the TRWP recovery mode. I'll have to try to find a USB-C male to USB-A female adapter for a mouse.
radiomean-uk said:
Here is the relevant post (hope I don't break and rules...)
=====================================================
=====================================================
Here is a clickable download link: https://drive.google.com/drive/folders/1J0HlsJYTyJUGAHjIXYMDUXye4DD9kEAC
For anyone following these are the steps i did (assuming you unlocked bootloader already):
8. flash both zips from external sd card
Click to expand...
Click to collapse
So, I'm stuck here. I'm unable to get those .zip files to my phone. I've tried doing the SDcard like you said, twrp doesn't list it anywhere. (Maybe it only accepts a particular SDcard format?)
I have also tried an ADB Sideload which just gets stuck on 0% when transferring a file. Both on Linux Ubuntu, and Windows 10.
A flash drive or any USB storage isn't really an option as I have to use it for a mouse.
You need a usb hub so you can plug in a mouse and a flash drive - TWRP is a bit shaky!
Put the zip files on the (external) usb drive and you will be fine...
This is the full thread - https://forum.xda-developers.com/t/ulefone-armor-3w-3wt.3969217/page-8#post-84304395
Cheers!
radiomean-uk said:
You need a usb hub so you can plug in a mouse and a flash drive - TWRP is a bit shaky!
Put the zip files on the (external) usb drive and you will be fine...
Click to expand...
Click to collapse
To my surprise, I found a USB hub, however, I'm unable to find the USB drive. Where exactly do I find it?
I've looked through Select Storage, And Mount.
With some research, I've found that the USB is supposed to be under OTG. But it doesn't let me select it... So, I guess I'm SOL?
EDIT: With my stupidity at fault. I never checked if the USB drive had a secure connection... I didn't, I now reseated it properly and am now installing what is needed.
radiomean-uk said:
You need a usb hub so you can plug in a mouse and a flash drive - TWRP is a bit shaky!
Put the zip files on the (external) usb drive and you will be fine...
This is the full thread - https://forum.xda-developers.com/t/ulefone-armor-3w-3wt.3969217/page-8#post-84304395
Cheers!
Click to expand...
Click to collapse
Thank you for helping. My phone is now rooted!
radiomean-uk said:
Here is the relevant post (hope I don't break and rules...)
=====================================================
=====================================================
Here is a clickable download link: https://drive.google.com/drive/folders/1J0HlsJYTyJUGAHjIXYMDUXye4DD9kEAC
For anyone following these are the steps i did (assuming you unlocked bootloader already):
1. Copy both zips to external sd as internal storage wont work at first
2. adb reboot bootloader
3. fastboot flash recovery recovery.img
4. unplug usb and hold power button until screen turns off
5. let go of power button, count to 2, press and hold power button and volume up together until screen turns back on
6. let go of power button when screen turns on but keep holding volume up until you see TWRP screen
7. as above post said, cancel password and swipe to enter main menu and then one square above the bottom right to enter the language menu
8. flash both zips from external sd card
9. format data (not wipe but format to get rid of encryption) - i rebooted after flashing the zips and had to go back to recovery again to format the data !THIS DOES A FACTORY RESET!
10. reboot to system this will cause it to be set up as new
11. reboot to recovery again, this time there should be no password and in install you should be able to see internal storage of the phone
12. flash magisk / anything else you want
Click to expand...
Click to collapse
I'm also attempting to
TOG_WAS_HERE said:
I've been trying to root my Ulefone armor 3WT for about a year now and still haven't gotten anywhere.
Here is how far I've gotten so far (with issues);
1. Fastboot commands - Cannot do fastboot commands in CMD, correct drivers are installed. Fastboot in CMD cannot find the device when the phone boots into fastboot mode. I can use ADB just fine.
2. The MediaTek flash tool - Cannot find a proper .scatter file to flash to the phone, nor can I create one.
People seem to be having lots of luck with number one, but I cannot figure out how they're getting fastboot to work in CMD.
Would like some help from anyone that has rooted this type of phone, or just any suggestions to help me with this thing.
Solved, (by radiomean-uk) follow this guide:
Click to expand...
Click to collapse
I tried the steps that are mentioned in this thread with my Ulefone Armor 3W and was unsuccessful. I've been trying to attempt to root my phone for too long. I'm running a Linux Mint OS on both desktop/laptop and since I'm also a noob with Linux OS I've been struggling to make it work.
Any help is appreciated, especially since this thread is already solved.
Thank you in advance for any help