Related
Return to Contents Page - doubleshot Developers Reference
Before we even start the thread, I had zero to do with development of this tool. I'm just trying to make it available since the file is gone from where it used to be.
From the original thread:
jdmarko said:
Just to be clear, this is not my basework, but I've assembled all the pieces and instructions to make it work for the MT4GS! Thanks to revolutionary, modaco, teamWin, eugene373, idanfima, coolbho3000 and wisefire for the easyfrevo part!
Temp Root:
You must have the USB drivers installed for your MT4GS. (If you don't have them, you can always install HTC Sync for the Sensation, plug in your MT4GS, and it will install the correct drivers.)
You MUST exit from the HTC Sync application for this to work!! (Right-click on the icon in the taskbar, and select Exit)
You must also have USB Debugging enabled. (Settings, Applications, Development, USB debugging)
Broken Link - see below for new link
...This is the new version (14 August 2011) that has the most up-to-date SuperUser.apk...
Unzip, and run the batch file (Run_ME_Fr3vo_ROOT.bat)...
You'll get errors like "An error occurred while running the exploit (-1) (errno: 14)", but if it also says "Exploiting device" afterwards, then it was successful!
This is temp-root, meaning that you can run apps that require root, but it'll go away when you reboot. Run the script again to get root back.
Older (v1) of this temp-root can be found here:
http://www.multiupload.com/M0757JL5DX
...just in case you run into any problems.
Click to expand...
Click to collapse
So, the link is broken and the temp-root file is one I use a lot. The host is down and now what do you do? I have a copy of it so I got ahold of Wisefire and TeamWin who were on board with getting the file back up.
TeamWin is hosting the file here: Temp-Root <- For now use the mirror below - will remove this text when this one works.
Here is the TeamWin site in case you want to check out some of the other cool stuff they're doing.
Here's a mirror in case you can't get to their link above, but definitely try there first. They made the underlying tool that does the work, and author hosted is always my first pick. Wisefire streamlined the installer for us so definitely don't think I developed anything for this other then appreciation for a good tool.
Temp-Root Mirror
----
The most common time I use Temp-root is after flashing back to stock. While there are other ways to do what I did with Temp-root in the example below, the more options I have the happier I am.
1 - Fresh (S-OFF) ** for an already S-OFF device.
What you need:
- MicroSD card.
- Stock Image
How to make it:
1 - Download the Stock Image to your computer.
2 - Rename it to PG59IMG.zip
3 - Format your MicroSD card in the computer.
4 - Transfer the image from the computer to the MicroSD card.
How to use it:
NOTE: Make sure you have a full battery!!!
1 - Power off the doubleshot. Remove the battery and MicroSD card.
2 - Insert new card from above. ( or back up current card, make, and re-insert )
3 - Replace battery and backplate.
4 - Holding the 'Volume Down' button, press the 'Power' button.
5 - Wait for the loading bar to fill.
6 - When ready, it will ask you if you want to start the update.
7 - Select yes by pressing the 'Volume Up' button. Press 'Volume Down' if you just realized you have a low battery.
8 - Allow the update time to flash to your doubleshot.
9 - Let it sit for a minute or two after it says finished, then press power to reboot.
10 - Follow on-screen instructions until finished.
Then:
1 - Reboot the doubleshot.
2 - When fully booted, open the settings menu.
3 - Go to "SD & phone storage" and choose "Factory data reset"
4 - Yes, wipe the sdcard too.
5 - Follow on-screen instructions until finished.
----
You now have the doubleshot as close to factory as you can get for testing. You will still have S-OFF but stock recovery.
--------
Replacing Stock Recovery: Clockworkmod
If you have S-OFF but stock recovery, the easiest method is to:
1 - Follow the qouted instructions at the top of the thread to get Temp-root.
2 - Without rebooting, add your market account to the device.
3 - Install ROM Manager from the market.
4 - Flash Clockworkmod through ROM Manager.
5 - What you do next is up to you (but a clockworkmod backup isn't a bad idea.)
--------
There are other creative uses for Temp-root, but if it isn't floating around people won't discover them. At least now it's in a couple of places, so it's more likely to be available.
Losing tools is bad for development.
This is driving me crazy.
Windows just doesn't seem to want to recognize my phone as being connected
when in Fastboot.
Is there a way to do this via a Mac (I figure if the company is going to give me
one I might as try to find a use for it)
BlueWeasel said:
This is driving me crazy.
Windows just doesn't seem to want to recognize my phone as being connected
when in Fastboot.
Is there a way to do this via a Mac (I figure if the company is going to give me
one I might as try to find a use for it)
Click to expand...
Click to collapse
This may be a stupid question, but do you have the drivers installed?
Also, I think you can dual boot mac with linux...I think. Maybe you can try lol.
The temproot worked once, but I couldnt get anything else to work.
Nothing for getting the code to do the unlock.
Maybe I will try via knoppix since there are some linux drivers.
I have gone through so many websites about this I dont see how I could have missed anything at this point.
Forget all of that. Found an issue.
Teamwin is hosting the wrong package, not sure where the mix up happened.
I pm'd them about it - meantime, hit my mirror and you'll be okay.
I can understand your frustration - it even made everything look the way it was supposed to be but something isn't quite right. File might have gotten corrupted when I sent it to them.
Thanks for pointing that out, so post if you have any more issues, i'll try to pay attention to this for the night to see if anyone gets stuck.
--------
Some step by step:
Ran the instructions I put above for restoring to stock.
Once it booted back up, I was back to stock and had a stock recovery.
(not necessary to do temp root, just so you know where I was with it all.)
Okay, lucky day, a windows 7 computer in my house temporarily and the owner says I can use it for the temp root. Nothing Android has ever been installed on this pc. (no SDK or any other tools)
1 - Downloaded the fastboot drivers and HTC sync. Installed both. Rebooted the computer. Exited HTC Sync.
2 - Set "USB debugging" in settings, as well as turning "fast boot" off in settings. (on the phone)
3 - Plugged my phone in. Let it recognize and settle for a few minutes. When ready:
4 - Download/Unzipped the temp-root package into the C:\ drive of the computer.
5 - Opened the folder, double clicked on Run_ME_Fr3vo_ROOT.bat
5a - be patient
6 - Press key when instructed, then safely eject phone from computer.
7 - Without turning off the phone, entered my market account into it.
8 - Still without turning off the phone, downloaded and installed ROM Manager from the market.
9 - Still without turning off the phone, used ROM Manager to install Clockworkmod Recovery
(even though it gave me a warning about not having root when I first opened the ROM Manager application, it was a false reading because it's temp root.)
10 - Done. Now it doesn't matter if I lose root when I turn the phone off, because I have replaced my stock recovery with clockworkmod and can now flash whatever I want to the phone - as it should be. I bought the whole phone, not just a piece of it.
Found this online. *****this is not my work****** All credit goes to the author quattrodevelopment.blogspot.com
Here is a step by step with roms included for the 4.5 quattro Not the HD or 5.7 HD maybe soon.
Disclaimer: These ROMs/Recoveries are only intended for the BLU Quattro 4.5, or the K-Touch v9(which is the chinese version) These WILL NOT work on the 4.5HD or 5.7HD devices(I will release ROMs/Recoveries specifically for your device at a later time)
Drivers: https://copy.com/BUMmsS9rhLJe
English Recovery: https://copy.com/XZxTDht2lQiz
Gapps(4.2) https://copy.com/utkbZgwRpsVB
Gapps(4.1) https://copy.com/pSd8SsqU9pdI
ROMs With Less Bugs: MIUI v5 (4.1) https://copy.com/sbmcN6PHwFfi CM/AOKP Hybrid? JB (4.1) https://copy.com/VeLz1VLbkNNI Shendu ROM 4.1(Modified/Tweaked by me) https://copy.com/NwiFnlO8JAek
ROMs With More Bugs: Cyanogenmod 10.1 (4.2) https://copy.com/8kt2EAU2ll8y
1- Download the drivers from link posted above, and extract it to the folder of your desire. Now turn the phone off, and hold Vol+ (volume up button) and Power button at the same time until you see a green screen, then release both buttons immediately. You should now be in APX mode(nvflash) it will be a black screen
2- Connect phone to computer via usb cable. Now you should get a pop-up window about installing drivers, you're going to want to choose to browse computer for driver software manually. Then choose let me pick from a list of device drivers on my computer, and click have disk. Now you're going to browse to the location where you extracted the drivers to, and click on it(Ignore warning if it pops up, and choose install)
3- Assuming everything went as planned, now download the recovery and extract it to the location you desire(must be in a directory that you can issue adb commands from) inside of that folder, locate a file named recovery.bat. Double click on that file and a command prompt with a bunch of chinese pops up. Give it a second and press enter, it will go through the process and flash a recovery onto your phone
4- After everything is done, hold down the power button for about ten seconds(until the device powers off) Power the device back on normally, and download the ROM/ROMs if you haven't already and place them on the internal or external sd card(your choice) With device connected to pc, open command prompt and type in "adb reboot recovery" (without quotes) and the device will boot into recovery mode
5- Now that we have an English recovery, the translations below aren't really needed. However, I'm going to leave them up for a few days, just until everybody can transition to the English recovery. They will be deleted after that!
Recovery Main Menu: -Reboot -Install from SD card -Wipe Data/Factory Reset -Wipe Cache -Backup&Restore -Mount/Format -Advanced
Install From SD Card Menu: -Install zip from external SD -Apply update.zip -Unknown* -Install zip from internal SD
Backup&Restore Menu: -Backup -Restore -The rest are unknown*
Advanced Menu: -Reboot Recovery -Wipe Dalvik Cache -The rest are unknown*
To install ROM- In recovery mode, Factory Reset/Wipe Cache/Wipe Dalvik Cache. Then choose install zip from sd card(then choose internal or external and locate the ROM you want to install) After that you need to do the same thing to install the gapps package(you need the gapps package for google apps to function) once all is done, reboot and wait(it takes a while to boot the first time after flashing new ROMs, it has to rebuild the Dalvik cache)
NOTE: In case you aren't familiar with flashing ROMs, once you click on something( "backup" for example) a menu pops up pretty much asing you if you're sure you want to do that. It will have a bunch of lines of the same thing(which is no) and then one of the lines will have a bunch of writing beside it(which means yes). Also BEFORE you flash any ROMs, make sure you factory reset/wipe cache/and wipe dalvik cache, then you can flash the ROM and gapps package
*These will be updated regularly, as I discover what they are **More ROMs to come!
Internal Memory
The "BLU Quattro 4.5" has 4GB internal memory partitioned into 0.98GB for ROM and apps and an internal usb-memory of 1.63GB.
Is it possible to merge or resize the partitions?
I have 16GB external SD so the 1.63GB internal reserved usb-memory is useless and I still having trouble out of space in primary partition.
Thanks and sorry my english =/
TechSoft said:
Found this online. *****this is not my work****** All credit goes to the author quattrodevelopment.blogspot.com
Here is a step by step with roms included for the 4.5 quattro Not the HD or 5.7 HD maybe soon.
Disclaimer: These ROMs/Recoveries are only intended for the BLU Quattro 4.5, or the K-Touch v9(which is the chinese version) These WILL NOT work on the 4.5HD or 5.7HD devices(I will release ROMs/Recoveries specifically for your device at a later time)
Drivers: https://copy.com/BUMmsS9rhLJe
English Recovery: https://copy.com/XZxTDht2lQiz
Gapps(4.2) https://copy.com/utkbZgwRpsVB
Gapps(4.1) https://copy.com/pSd8SsqU9pdI
ROMs With Less Bugs: MIUI v5 (4.1) https://copy.com/sbmcN6PHwFfi CM/AOKP Hybrid? JB (4.1) https://copy.com/VeLz1VLbkNNI Shendu ROM 4.1(Modified/Tweaked by me) https://copy.com/NwiFnlO8JAek
ROMs With More Bugs: Cyanogenmod 10.1 (4.2) https://copy.com/8kt2EAU2ll8y
1- Download the drivers from link posted above, and extract it to the folder of your desire. Now turn the phone off, and hold Vol+ (volume up button) and Power button at the same time until you see a green screen, then release both buttons immediately. You should now be in APX mode(nvflash) it will be a black screen
2- Connect phone to computer via usb cable. Now you should get a pop-up window about installing drivers, you're going to want to choose to browse computer for driver software manually. Then choose let me pick from a list of device drivers on my computer, and click have disk. Now you're going to browse to the location where you extracted the drivers to, and click on it(Ignore warning if it pops up, and choose install)
3- Assuming everything went as planned, now download the recovery and extract it to the location you desire(must be in a directory that you can issue adb commands from) inside of that folder, locate a file named recovery.bat. Double click on that file and a command prompt with a bunch of chinese pops up. Give it a second and press enter, it will go through the process and flash a recovery onto your phone
4- After everything is done, hold down the power button for about ten seconds(until the device powers off) Power the device back on normally, and download the ROM/ROMs if you haven't already and place them on the internal or external sd card(your choice) With device connected to pc, open command prompt and type in "adb reboot recovery" (without quotes) and the device will boot into recovery mode
5- Now that we have an English recovery, the translations below aren't really needed. However, I'm going to leave them up for a few days, just until everybody can transition to the English recovery. They will be deleted after that!
Recovery Main Menu: -Reboot -Install from SD card -Wipe Data/Factory Reset -Wipe Cache -Backup&Restore -Mount/Format -Advanced
Install From SD Card Menu: -Install zip from external SD -Apply update.zip -Unknown* -Install zip from internal SD
Backup&Restore Menu: -Backup -Restore -The rest are unknown*
Advanced Menu: -Reboot Recovery -Wipe Dalvik Cache -The rest are unknown*
To install ROM- In recovery mode, Factory Reset/Wipe Cache/Wipe Dalvik Cache. Then choose install zip from sd card(then choose internal or external and locate the ROM you want to install) After that you need to do the same thing to install the gapps package(you need the gapps package for google apps to function) once all is done, reboot and wait(it takes a while to boot the first time after flashing new ROMs, it has to rebuild the Dalvik cache)
NOTE: In case you aren't familiar with flashing ROMs, once you click on something( "backup" for example) a menu pops up pretty much asing you if you're sure you want to do that. It will have a bunch of lines of the same thing(which is no) and then one of the lines will have a bunch of writing beside it(which means yes). Also BEFORE you flash any ROMs, make sure you factory reset/wipe cache/and wipe dalvik cache, then you can flash the ROM and gapps package
*These will be updated regularly, as I discover what they are **More ROMs to come!
Click to expand...
Click to collapse
Please rename this For Others Such as [GUIDE]BLU Quattro HowtoRoot/Rom list. Thanks for the awesome Guide!
alanfrank said:
The "BLU Quattro 4.5" has 4GB internal memory partitioned into 0.98GB for ROM and apps and an internal usb-memory of 1.63GB.
Is it possible to merge or resize the partitions?
I have 16GB external SD so the 1.63GB internal reserved usb-memory is useless and I still having trouble out of space in primary partition.
Thanks and sorry my english =/
Click to expand...
Click to collapse
I've found this: http://forum.xda-developers.com/showthread.php?t=1171531
Any idea if this can be used with another phone them the LG one he have used in the guide?
I cant post in the thread because Im new user here =/
problem
I have done everithing you said, and my cell freezes on boot forever, now what????
BLU Quattro 4.5 HD & 5.7
Need to know how to restore both devices to stock. Any aplication ODIN like to restore it back to stock from the download mode?
Please help me root, i try binary method but i just get boot loop.
Recovery + Root My experience
Hello... I got my BLU Quattro 4.5 (D440) a while back, didn't fuzz with it much right off. The Stock ROM was sluggish at best thought there was even an issue with the Digitizer/screen. But this thread was extremely helpful. I am now running Shendu ROM 4.1.2 one of the suggested ROM's above. I tried the other 2 first and they were mostly in Chineese and I had an especially hard time getting them switched over to English. Either way onward to the point. I have put together a few helpful tips-tricks for my experience with this phone and its phoenix transition to an awesome handset. Thats right now this is my daily driver and I love it! See below hope its helpful.
BLU Quattro 4.5 (440D) GSM Recovery+Root
These steps for this phone only!! Not responsible for any issues.
1. download ROM's, Recovery, & Driver from XDA (this thread)
http://forum.xda-developers.com/showthread.php?t=2327417
2. Enable USB Debugging! Go into Apps-Settings-DevOptions - Check box for USB Debug
3. Have original USB cord if handy! I tried with a Samsung OEM cable but no luck getting drivers to stick. Use original is best. (If you have one.)
Plug in USB Cord to PC then Phone and see if windows detects drivers. let it. It wont get the ones u need later, but what it does find is for USB storage. (you can move over your ROM's/Gapps to storage, downloads folder is a good spot).
4. Go to... http://junefabrics.com/android/downloadold.php to get pdanet software. Install it and it will give i the right drivers for ADB support. I used 4.01 to match the android version currently on my phone.
5. Extract the Driver provided from XDA. Put it in a folder with the ADB commands. Or you can get it all here... http://downloadandroidrom.com/file/GalaxyNexus/rooting/GalaxyNexusRootNew.zipn <-- I know this isn't for BLU but, if you extract this to a folder, and also add the drivers extracted to it as well this works! I've done it.
6. Extract the English Recovery to the same folder.
7. Turn off your phone. Hold down Vol up and Power button for about 5-9 seconds. Once you see a green screen let go of both. Screen may flicker then go black but the icons at the bottom will stay lit. You are now in APX mode (nvflash) mode. (as stated above in original post)
8. Check your Win 7 PC device manager. For a Phone device with ADB. If you you may need to update driver with the one that came from XDA, but the PDANet software should make it work.
8. Go to the folder and find Recovery.bat file (may have Chinese in file name. Double click and a command prompt window will pop up with a bunch of unknown characters, wait 5 sec then hit enter. The batch file should take of pushing the necessary recovery through ADB to the phone. It will error if it can't.
9. If completes OK. Push power for 7-9 seconds to power off the phone. Hit power like normal to turn it back on. It will boot up like normal (or it should).
10. USB is still connected this whole time and you can open a command prompt window. Navigate to the folder you placed the Recovery into. Something like user/username/desktop/BLU/recovery..etc)
Type ADB devices....it should show you that is is connected to your device. Then type " adb reboot recovery " and the device should reboot, give it some time.
11. Once in recovery. Best to do a backup of the original ROM & system. that way you can get back into recovery if anything goes wrong and wipe out the problem by restoring and starting again.
After you backup === you can get into recovery without the command being typed in or even being connected to your PC.... By holding Vol up + Power till you see the green screen then let go of power but keep holding Vol up till you see the BLU Products boot screen then let go ===
Clockworkmod Recovery should be on your screen.
you can reboot phone now and get back to original with no changes. Or you can venture into the world of loading ROM's (There in your downloads folder if you saved them in Step 3)
ROM 101
BACKUP-BACKUP-BACKUP 1st thing once in Recovery ...can't stress enough how much of trouble you can keep yourself out of by keeping an original backup.
As I stated before the Shendu ROM + Gapps is running smooth and all features I've been trying are working flawlessly!! Thanks to original post for getting me going. Just thought I'd add my 2 Cents.
Ok, here are the BEST 2 ROMS for this Phone:
Android 4.0.4(close to vanilla) : MEGA
Cyanogenmod 10.2 (Android 4.3.1) : (some audio and video issues, in BETA version ) MEGA
Need to merge internal partitions ? (merge memories) this one really "resize" the partitions (first one 1,7GB, another one new size is 2Mb) the flash.cfg file you need to flash:
This phone dont have notificaion led, fixed with this app: MEGA (flash the botton menu buttons)
Altomugriento said:
Ok, here are the BEST 2 ROMS for this Phone:
Android 4.0.4(close to vanilla) : MEGA
Cyanogenmod 10.2 (Android 4.3.1) : (some audio and video issues, in BETA version ) MEGA
Need to merge internal partitions ? (merge memories) this one really "resize" the partitions (first one 1,7GB, another one new size is 2Mb) the flash.cfg file you need to flash:
This phone dont have notificaion led, fixed with this app: MEGA (flash the botton menu buttons)
Click to expand...
Click to collapse
Can you explain the merge memories procedure? it will be reaaaaally needed!!
tryed from a spanish forum with no luck
thanks
dinizbruno said:
Can you explain the merge memories procedure? it will be reaaaaally needed!!
tryed from a spanish forum with no luck
thanks
Click to expand...
Click to collapse
Do you try the procedure posted in 3dgames . com . ar? ( its my work translated from the 592zn page, all the credits for the chinesse people)
Anyone tried the K-touch V9 kit kat in the BLU??
www
needrom
com/
download/
k-touch-v9-miui-v5-kk
Yes, those roms (v5) are very slow. Just use the 4.0.4 stock.
I want to try the JB stock, but i can´t find the official one anywhere.
Blu quattro 4.5 official rom to download, after you delete the bloatware and put a nice and clean theme you´ll get a nice speed.
orig D440 (quattro 4.5) rom
You can find the rom on google plus under BLU Products Development search for the model!
Hope that helps. I took your advice tonight and I am back running old school. Works ok husfar
I need phone.apk of this rom for Blu Quattro
Trozzul said:
Please rename this For Others Such as [GUIDE]BLU Quattro HowtoRoot/Rom list. Thanks for the awesome Guide!
Click to expand...
Click to collapse
I need phone.apk for blu quatro
please send me the file
[email protected]
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.
Files To Download:
*
Odin File *For Windows
*
TWRP-2.8.7.0-S820L File •UPDATED
*
SuperSU Root File
*
***ALSO DOWNLOAD SAMSUNG USB DRIVERS VIA ON THERE WEBSITE, if its your first time reboot your pc after you install them.
**********************************"**************************************"************
Directions To Install:
1. Download the given files ODIN & TWRP Recovery + SuperSU ZIP File
2. Put them where they're easy to access like in your deskop.
3. Make sure usb debugging is enable via your phone before connecting it into your computer.
4. Fire up odin program. Make sure reboot, partitioning isnt checked.
5. Put your phone into download mode by holding and pressing (volume down + home button + power button). Then hit volume up when prompt.
6. Connect your device into your computer with the usb cable that came with your device.
7. On the odin program you should see a yellowish box light up, if you see that, it means its recognized for flashing. *If you dont see it, you need to enable usb debugging in your phone or install samsung usb drivers, if not both.
8. On the odin program Click on the PDA box and find your twrp tar file that youve download.
9. Hit Start, and wait til its successfully installed. You should see a blueish box light up.
10. Disconnect your device from the usb cable. Take out the battery then put it back , or you can just go into recovery mode directly by holding and pressing the (volume up + home button + power button) hold it like for about 2-3 seconds then release just the power button.
11. You should be on the TWRP Recovery Main Menu
12. Congrats for reading the direction carefully.
-------------------------------------------
13. For already rooted users just extract the recovery.img from the tar file, put it into your external sdcard. you'll need terminal emulator, dl it via play store. Open terminal emu type:
su *for root perms
Later,
dd if=/storage/extSdCard/recovery.img of =/dev/block/platform/7824900.sdhci/by-name/recovery
hit enter *please make sure youve type it correctly before hitting ENTER*
Once finished turn off your device and go into recovery mode.
-------------------------------------------
14. If you want to root it just download the superSU flashable zip file, flash it via twrp recovery.
15. Success? Great! ENJOY YOUR NEW TWRP CUSTOM RECOVERY + ROOT!!
-------------------------------------------------------------------------------------------------------------------------
Im usin a straighttalk SM-M820L. Is there any way any of this can be done without a pc? My phone is rooted tho. I used the {yup you guessed it} kingroot method and then i did the "replace kingroot with supersu" no pc method. Is there any tips or pointers that you could give me? I'm not using a pc because it was stolen a little while back and I just haven't had the spare cash to get another. Plus I just started tinkering with this and it's super more interesting than I thought. I'm trying to learn all that I can. Thank you for any help you can offer.
None of them downloads are linked. Where are they?
galaxy core prime
PakRatt said:
None of them downloads are linked. Where are they?
Click to expand...
Click to collapse
go to area 51 site..its all in there...
Thanks, but im already done rooting it now...lol.
Sent from my SM-S820L using Tapatalk
will this by any chance allow the mobile hotspot feature that straight talk removed from there phones specifically the sm-s820l to be utilized
Area 51 wont let me join their site because i dont know the color of water! I really need a recovery for Sm S820L yesterday. No TWRP, I need one working for this phone without scouring having to the internet. Does anybody have one PLZ?!
They think water is Blue.
balrogs! said:
Area 51 wont let me join their site because i dont know the color of water! I really need a recovery for Sm S820L yesterday. No TWRP, I need one working for this phone without scouring having to the internet. Does anybody have one PLZ?!
Click to expand...
Click to collapse
They think water is blue, I guess it is in a toilet.
You guys can always check out my threads over at Needrom as well. I have 2 different posted threads there.
Here are the TWRP + Supersu files. FU Area52, with your dumb registration and all. And your stupid blue color.
Code:
https://goo.gl/hLaHCe
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.