Related
I've been working on a step-by-step CLOSE-UP VIDEO guide to Flashing a ROM, including how to HARD SPL, to make available to users here. Here are things I'm still not clear on.
(These were posted recently to the Guide written by mskip in the Kaiser forums. He answered some questions, but these are still unanswered. )
Flashing via ActiveSync with USB Lead
2. Pull out the battery and reinsert it (this step IS important) *DONT turn phone back on yet*
Click to expand...
Click to collapse
** When is this step necessary & required (whether during initial HARD SPL or FLashing a ROM post-HardSPL) , as opposed to simply "Best Pratices"? What is this step accomplishing?
8. After a few seconds the tri colour screen will appear on the phone and "USB" will be displayed at the bottom
9. Unplug the usb cable for 30 seconds and then Replug (phone will not re-sync but still says "USB" on the screen)
Click to expand...
Click to collapse
** Please explain #9, what it is accomplishing & thus why recommended?
"Active Sync" vs "USB connection"
Please tell me if this is accurate or not:
(1)When installing via PC vs installing via Storage Card: After data has been backed up to PC by way of "Active Sync", thereafter, when performing any ROM updates (HardSPL or flashing a new ROM) the app "Active Sync" is technically no longer involved in the flashing process, but rather, what's necessary is simply having a USB connection from device to PC, correct? Is the distinction that Actice Sync can foul up the basic data connection from phone to PC necessary to flash a ROM. I want to be very clear. Is this accurate?
10. Right click on the Activesync icon in the bottom corner icon on the computer, goto connection settings, deselect "Allow USB connections" and click "ok"
11. Microsoft ActiveSync icon will now have a red cross in it and the program will say "Connection Disabled"
12. Run the ••••••RUU.exe file on your PC thats in the same folder as the HardSPL .nbh file and follow instructions (ticking boxes and clicking Next) *DO NOT reenable USB Connections in Activesync*
Click to expand...
Click to collapse
** same as above: Are these just more compensations in order to disable MS's incorrect assumption that the insertion of a USB cable always equals "launch an Active Sync session" ?
15. Unplug USB cable from phone then REPLACE SIM & SD CARDS !!
**Remember to re-enable "Allow USB connections" in Activesync connection settings after a successful flash**
Click to expand...
Click to collapse
Why, exactly, is it required to unplug the USB cable? Is it, again, a "Best Practices" precaution to prevent any kind of accidental read/write of data?
A few questions re entering Bootloader mode, various scenarios:
1. In some older guides, even for when flashing a rom to phone device from your PC , sometimes a step is specified to "enter Bootloader mode by holding & pressing the xxxx and xxx keys on your phone, and then xxxxx".
2. But if you have an RUU folder that includes the Bootloader.exe app, along with the RUU.exe and .nbh file, then by running the RUU.exe app, the entering bootloader mode is handled automatically, sending the commands to phone, which automatically place the phone into the tri-color screen mode? -- as opposed to one having to manually press xxxx and yyyy on phone to enter bootloader mode? Correct or not?
3. If correct: then, does it matter on which screen or in which mode your phone is currently on in order to begin the flash-ROM process? Could I just as well be on a Total Commander app screen or on a TouchFlo Today screen?
4. Some guide-writers recommend users hard reset their phones before starting a new flash-rom session, just for "best practices". Others consider this superfluous & irrelevant, and what matters most is a Hard-Reset be run immediately AFTER flashing a new ROM. ... Any opinion on this?
Flashing Via ActiveSync
<snip; this is deep into the flashing process >
2. Turn phone back on and wait until it syncs with your PC
Click to expand...
Click to collapse
** Would it be more accurate to say here "until your PC confirms it has a USB connection to your phone"? (You're not looking to run a sync session, but rather just getting a USB connection for files to be transferred from PC to phone.) I think the term "Active Sync" often creates more confusion than helpfulness in this whole realm of moving files from PC to phone. )
Question re RUU.exe file on PC:
From what I have seen in the ROMS I have used in years 2008-2009, the extracted ROM folders I've downloaded from the chefs have typically all had the file " Bootloader.exe " within the RUU folders, and that (in the case of mskip's Flash Guide for Kaisers) KaiserCustomRUU.exe calls the Bootloader.exe app which sets the phone into bootloader mode from the PC, without one needing to manually set the phone into bootloader mode.
But this is your response from your initial quick-reply, which confuses me"
The customRUU automatically puts the phone in bootloader mode thus there is no need for the seperate file (bootloader.exe).
Click to expand...
Click to collapse
** This confuses me. I am principally trying to distinguish between when one needs to manually set phone into bootloader mode -- and when this step is handled by the PC's RUU.exe process. In the older (around year 2007) "How to flash" guides, users were often told they needed to create a folder, make sure they have the correct RUU.exe file inside it, make sure they have the correct .nbh file, make sure they don't have files that are there for those with soft SPL phone, etc. And as far as I can recall, in those older Guides, this bootloader.exe file was not included. And thus users were instructed to manually put their phones into bootloader mode...
The difference being that for the past year or more, chefs currently are now providing the whole contents of the RUU folder in the .rar file, so that if you've hard-SPL'd, then that .rar file has eveything you need, and all you need to do is launch the RUU.exe -- never having to set your phone manually into bootloader mode.
Yet you are saying
Quote:
thus there is no need for the seperate file.
Click to expand...
Click to collapse
I'm not a coder, but I don't get this. Why would bootloader.exe be inside practically every RUU Folder nowadays if it were unnecessary to set the phone into bootloader mode to initiate the flashing process? You were saying the RUU.exe app itself would contain some method of setting phone inot bootloader mode without even needing that bootloader app present in the folder.
Could someone please clarify.
And secondly: Does it matter one bit of difference which screen your phone is on when you commence with running RUU.exe ?
And third : If users happen to be confused, and think they must manually set their phone into bootloader mode, as part of running RUU.exe, and they do manually set their phone inot bootloader mode and get the tri-color screen: Does that conflict with or hamper in any way the running of the RUU.exe program from the PC? Or does the RUU process just simply proceed, and send an "enter bootloader mode" instruction to the phone, which then causes the phone, already in tri-color screen, to be reset again into bootloader mode (and there is no problem that the phone was already in bootloader mode) ?
After New Rom is Completely Installed and You Have Customized Your Phone:
** I think it in dutty's guide where he says "after customizing your phone, power down your phone, then power it back up". Is this power-down/ power-up cycle equivalent to just doing a soft-reset? What is the difference as it pertains to that specific step after customization?
Quote:
Flashing Via MicroSD Card
<snip>
3. Goto the Roms Folder and rename the .nbh file to KAISIMG.nbh
4. Copy the KAISIMG.nbh file to your MicroSD Card
Click to expand...
Click to collapse
** Where does one get the correct 4-LETTER CODE for their phone if one has a DIFFERENT phone than Kaiser and wants to flash via MicroSD card?
-----
Thanks to anyone who can please clarify these points
2. Removing the battery is not required in any level of flashing a ROM. removing the battery for Hard-SPLing is not required on all devices. For instance, my polaris doesn't require removing the battery.
9. Not sure why you need to do that but it IS necessary (you can pm Olipro about it) but i'm pretty sure it has to do with updating the connection between the PC and the PDA since while in Bootloader the PDA doesn't act as a plug-and-play device.
11. I don't recall this being an important step as I flashed hard-spls and roms without changing the AS state. you HAVE to have an activesync connection with your PC in order to flash (doesn't have to be synced, but the PDA has to be recognized by activesync, hope this is clear).
15. Yes, it is not a MUST. you can flash roms and spls while leaving the cable connected.
---------------------------------------------------------------------------------------------------
2. Yes, if you have the full library containing bootloader and everything you can flash without entering bootloader manually prior to flashing.
3. flashing doesn't require a specific state. you can start the process whenever.
4. Hard-reseting before MIGHT make a difference... in some cases which i'm not familiar with. maybe there's an app which can disturb the flashing process.
Hard-reseting after is pointless as flashing a rom performs exactly that WHILE switching the OS.
-about the syncing.. yeah, you don't need an actual sync-session. a usb connection is enough (AS LONG AS the comp identifies the hardware of course)
-it doesn't matter if you have the bootloader.exe file inside or not (I assume it depends on your device as well.. but not sure). RUU runs bootloader automatically. about HARD-SPL.. yeah, i haven't seen a hard-spl which doesn't contain bootloader.exe.. (i again suggest you pm olipro about this)
-again, it doesn't matter which screen you're on when running the ruu
...
-about the phone codes for flashing... you can find all codes for all phones in the forum
for instance,
Polaris -> POLAIMG.nbh
Hermes -> HERMIMG.nbh
Blackstore -> BLACIMG.nbh
Diamond -> DIAMIMG.nbh
Raphael -> RAPHIMG.nbh
Trinity -> TRINIMG.nbh
yada yada...
you can search, and i'm pretty sure not ALL devices have this option..
the wifi also contains info about flashing from SD card.
also, wonderful initiative and i hope you will agree to post this in the GUIDES thread.
***ONLY FOR RELAYS RUNNING ICS 4.0.4***
Samsung had just released the official Jelly Bean 4.1 update for this phone on April 22 or so and this root method only works for Ice Cream Sandwich devices.
I know there's already a thread of how to root the ICS Samsung Galaxy S Relay 4G which is right here: http://forum.xda-developers.com/showthread.php?p=34515281 but I thought that it may be hard for some people to do it without a visual tutorial. Here's my helpful tutorial video of how to root the Samsung Galaxy S Relay 4G: https://plus.google.com/u/0/108388305247615258469/videos <-- You can easily find the video because it's the only video on that album.
Files Needed:
Winrar: http://www.win-rar.com/download.html?&L=0
Odin v3.07: http://www.4shared.com/zip/CGo6TP1O/Odin307.html? or for the latest and updated versions: http://forum.xda-developers.com/showthread.php?t=1738841
Rooted System IMG: http://www.4shared.com/rar/nhGK59WR/SGHT699_rootedtar.html?
CWM File: http://www.4shared.com/zip/wLHTlktW/cwmtar.html?
If none of the links above work, message me at [email protected] or reply to this topic and I will reupload the files.
Steps:
1) On your phone, go to Settings-->Developer Options and turn on USB Debugging.
2) Turn off your phone and put it in Download Mode/Odin mode.
3) Download the odin307, sght699_rooted.tar, and that cwm.tar files from the links given above.
4) Extract all the files with WinRAR or other file extracting programs.
5) Open Odin v3.07
6) Make sure that it says "Added!" on the bottom left box. If it doesn't say Added, unplug and plug your phone from the computer.
7) Deselect/Uncheck "Auto Reboot" and "F. Reset Time"
8) Click on Phone and a pop up should come up.
9) Find the SGHT699_rooted folder that you extracted in Step 4 and open the file inside it.
10) Click Start. This will take a while but it should not take more than 14 minutes.
11) Once it's done, click Reset.
12) Unplug and plug your phone again. It should say "Removed!" when unplugged and "Added!" when plugged on the bottom left box.
13) Deselect/Uncheck "F. Reset Time" but this time, keep the "Auto Reboot" marked/checked.
14) Click on PDA and a popup should come up.
15) Find the cwm folder that you extracted in Step 4 and open the cwm.tar.md5 file.
16) Click Start.
Once it finishes, your phone should reboot and be rooted. To check if it is actually rooted, go on Applications and find Superuser. If it is there, then you are rooted. Enjoy!!
Very nice. You are missing information, need to add the original posts/threads for the files that you mirrored so we can get version numbers and dates associated with the downloads. Feel free to edit the wiki in my sig if you want to help!
Ok. Thanks, but there's a problem. The files I mirrored other than Odin v3.07 are gone. The original link where the original tutorial was is gone. I had the link in my bookmarks but when I click on it, the webpage is unavailable. Ive tried viewing it from other computers and devices and it still wont work. So I decided to make a new one. Thanks again! The links should be updated in a few.
Sent from my SGH-T699 using xda app-developers app
Thanks.
Version is UVAMA2?
Sent from my SGH-T699 using xda premium
XIAOSpider said:
Thanks.
Version is UVAMA2?
Sent from my SGH-T699 using xda premium
Click to expand...
Click to collapse
What's UVAMA2?
USB won't connect properly; want to un-root
You're rooting video was very helpful.
However, now that the phone is rooted, when I try to connect to my computer with USB cable, I get error message to the effect that the computer can't recognize the hardware ID of the device, so can't back-up the files on the phone or the SD card. I have all the latest Samsung USB drivers, and the computer recognizes that a Samsung device is connected, but the USB connection fails anyway.
How do I un-root the phone - do I have to boot up in download mode and use ODIN? Will this wipe my data, or just go back to the unrooted ROM and keep my data intact?
-----------
Chrizuki said:
I know there's already a thread of how to root the Samsung Galaxy S Relay 4G which is right here: http://forum.xda-developers.com/showthread.php?p=34515281 but I thought that it may be hard for some people to do it without a visual tutorial. Here's my helpful tutorial video of how to root the Samsung Galaxy S Relay 4G: http://www.youtube.com/watch?v=GKgemJTeRWo
Files Needed:
Winrar: http://www.win-rar.com/download.html?&L=0
Odin v3.07: http://www.4shared.com/zip/CGo6TP1O/Odin307.html? or for the latest and updated versions: http://forum.xda-developers.com/showthread.php?t=1738841
Rooted System IMG: http://www.4shared.com/rar/nhGK59WR/SGHT699_rootedtar.html?
CWM File: http://www.4shared.com/zip/wLHTlktW/cwmtar.html?
If none of the links above work, message me at [email protected] or reply to this topic and I will reupload the files.
Steps:
1) On your phone, go to Settings-->Developer Options and turn on USB Debugging.
2) Turn off your phone and put it in Download Mode/Odin mode.
3) Download the odin307, sght699_rooted.tar, and that cwm.tar files from the links given above.
4) Extract all the files with WinRAR or other file extracting programs.
5) Open Odin v3.07
6) Make sure that it says "Added!" on the bottom left box. If it doesn't say Added, unplug and plug your phone from the computer.
7) Deselect/Uncheck "Auto Reboot" and "F. Reset Time"
8) Click on Phone and a pop up should come up.
9) Find the SGHT699_rooted folder that you extracted in Step 4 and open the file inside it.
10) Click Start. This will take a while but it should not take more than 14 minutes.
11) Once it's done, click Reset.
12) Unplug and plug your phone again. It should say "Removed!" when unplugged and "Added!" when plugged on the bottom left box.
13) Deselect/Uncheck "F. Reset Time" but this time, keep the "Auto Reboot" marked/checked.
14) Click on PDA and a popup should come up.
15) Find the cwm folder that you extracted in Step 4 and open the cwm.tar.md5 file.
16) Click Start.
Once it finishes, your phone should reboot and be rooted. To check if it is actually rooted, go on Applications and find Superuser. If it is there, then you are rooted. Enjoy!!
Click to expand...
Click to collapse
nosch454 said:
You're rooting video was very helpful.
However, now that the phone is rooted, when I try to connect to my computer with USB cable, I get error message to the effect that the computer can't recognize the hardware ID of the device, so can't back-up the files on the phone or the SD card. I have all the latest Samsung USB drivers, and the computer recognizes that a Samsung device is connected, but the USB connection fails anyway.
How do I un-root the phone - do I have to boot up in download mode and use ODIN? Will this wipe my data, or just go back to the unrooted ROM and keep my data intact?
-----------
Click to expand...
Click to collapse
Oops, sorry. Forgot the part of your reply that said you've installed all the drivers. What do you mean by it can't recognize it? Does the SGH-T699 still show up on your My Computer?
If you want to unroot, go here: http://forum.xda-developers.com/showthread.php?t=2166242
Just follow the steps and no, it won't wipe out all your data (Well, it didn't wipe mine, but I'm sure it won't.)
Sent from my SGH-T699 using xda app-developers app
Problems connecting with USB (MTP driver install failure)
Chrizuki said:
Oops, sorry. Forgot the part of your reply that said you've installed all the drivers. What do you mean by it can't recognize it? Does the SGH-T699 still show up on your My Computer?
If you want to unroot, go here: http://forum.xda-developers.com/showthread.php?t=2166242
Just follow the steps and no, it won't wipe out all your data (Well, it didn't wipe mine, but I'm sure it won't.)
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse
When I connect the USB cable, Windows has a popup message that says:
" Hardware ID missing
Windows cannot identify the device plugged into the Samsung Mobile USB Composite Device.
For assistance, contact the hardware manufacturer"
Sometimes it tries - and fails - to install the MTP device driver.
However, when I go into Windows Device Manage, it does list SAMSUNG Android Phone | SAMSUNG Android ADB Interface, and when trying to update its drivers, it says I have the most up to date ones installed.
- What does "Hardware ID missing" mean? How do I get the phone to communicate with the computer using USB?
I thought it might have to do with Android Ice Cream Sandwich and the media device (MTP) protocol for USB, but, I had no problems getting the computer to recognize my son's (unrooted) Galaxy S 3, which also has ICS and is pretty similar to the Galaxy S Relay 4G. That's why I suspect the problem is with my rooted version.
Is there anything else I should try before un-rooting the phone?
nosch454 said:
When I connect the USB cable, Windows has a popup message that says:
" Hardware ID missing
Windows cannot identify the device plugged into the Samsung Mobile USB Composite Device.
For assistance, contact the hardware manufacturer"
Sometimes it tries - and fails - to install the MTP device driver.
However, when I go into Windows Device Manage, it does list SAMSUNG Android Phone | SAMSUNG Android ADB Interface, and when trying to update its drivers, it says I have the most up to date ones installed.
- What does "Hardware ID missing" mean? How do I get the phone to communicate with the computer using USB?
I thought it might have to do with Android Ice Cream Sandwich and the media device (MTP) protocol for USB, but, I had no problems getting the computer to recognize my son's (unrooted) Galaxy S 3, which also has ICS and is pretty similar to the Galaxy S Relay 4G. That's why I suspect the problem is with my rooted version.
Is there anything else I should try before un-rooting the phone?
Click to expand...
Click to collapse
Install kies or the USB driver directly from samsung.com. Try the USB driver first, then kies if it doesn't work.
Nocturin said:
Install kies or the USB driver directly from samsung.com. Try the USB driver first, then kies if it doesn't work.
Click to expand...
Click to collapse
Already tried both. USB driver is OK, the problem is with MTP. Kies only works via WiFi; does not recognize device with USB. I also tried Samsung tech support's suggestions, none of which changed the situation
nosch454 said:
Already tried both. USB driver is OK, the problem is with MTP. Kies only works via WiFi; does not recognize device with USB. I also tried Samsung tech support's suggestions, none of which changed the situation
Click to expand...
Click to collapse
Have you tried downloading the SDK Manager from "http://developer.android.com/sdk/index.html"? Open the big file that you just downloaded and open up SDK Manager. Install the Google USB Driver and as well as the Android SDK Tools and Android SDK Platform-tools. Once downloaded, go back to the android-sdk-windows folder and go to the "platform-tools" folder inside and hold Shift and right click on "adb" and select "Open Command Window Here" of something like that. The command prompt will open. Type in "adb devices" and tell me what comes up. If you see your device(It should be a bunch on numbers and letters) on there, it means it is recognizable. This might not solve your problem as I do not know what "Hardware ID missing" exactly is. But I will do some research.
I did as you suggested, and was able to see my phone when I ran "adb devices" from the command prompt. And, Windows, recognizes it too, because when I click on the button to remove attached USB devices, it lists SAMSUNG_Android_SGH-T699. But, I still get the hardware ID missing message whenever I connect the USB cable. Frustrating! But, thanks for trying to help me - you seem very knowledgeable.
What you can try and do to fix the USB hardware error is go to control panel then go to "uninstall a program" and uninstall the samsung driver once you uninstalled it reconnect your phone and let it reinstal the files and i believe it should fix your problem
Samsung Noob here with a question.
Ok, I know this is gonna sound kinda noobish, but I come from HTC phones, and this is my first Samsung. Do I need to flash ClockworkMod Recovery on this, or do I flash a rom to the 4G Relay using Odin? If I use Odin, can someone give a quick overview on how?
Gh0sTly said:
Ok, I know this is gonna sound kinda noobish, but I come from HTC phones, and this is my first Samsung. Do I need to flash ClockworkMod Recovery on this, or do I flash a rom to the 4G Relay using Odin? If I use Odin, can someone give a quick overview on how?
Click to expand...
Click to collapse
you'll need to install a recovery as you did on HTC as ROMs usually come as recovery-flashable zips.
there's a cwm recovery available here which can flashed using Odin. If you don't like the cwm on the relay you can flash TWRP from cwm over it. TWRP comes with more options and the touchscreen-control you might be used to.
from (any) recovery you can just install update zip-files just as you used to on your HTC.
I had used the "howto root the Galaxy S Relay" thread, and then realized, I should just SU and reboot recovery. :victory:
nosch454 said:
I did as you suggested, and was able to see my phone when I ran "adb devices" from the command prompt. And, Windows, recognizes it too, because when I click on the button to remove attached USB devices, it lists SAMSUNG_Android_SGH-T699. But, I still get the hardware ID missing message whenever I connect the USB cable. Frustrating! But, thanks for trying to help me - you seem very knowledgeable.
Click to expand...
Click to collapse
If anybody else got this error do the following:
- uninstall all samsung drivers / software
- connect your phone to the pc
- the driver installation should 'fail', but you can access the storage
- install the samsung drivers now while phone is plugged in
After the installation the phone will be recognized and everything is fine - this worked twice for me now, so I guess it should do it.
Hello!, this is my first post so i hope it will help you
Links:
http://www.alcatelonetouch.com/nl/producten/smartphones/pop_c9.html#.VZw1Txvtmko (Alcatel messes with there links so tell me if the link is out-dated)
Step 1.
Download and install the program from the Alcatel website (Mobile Upgrade S).
Step 2.
Now open the program and select your language, now find your phone model in the list and select it. Mine is 'One Touch 7047' so i will be selecting that one. ( if your model number has a 'D' or 'A' after it, dont look at that, we only need the numbers!)
Step 3.
OK, for this you need your phone to be TURNED OFF, NOT CONNECTED TO YOUR PC YET,! It also says your phone needs to be fully charged so it cant interrupt the download, that depents on your Model and PC, my phone charges when connected to the PC, but if youre not sure, also CHARGE IT.
Step 4.
And now you have to connect your phone to the PC. Now it will search for the latest Android version compatible with your device (Dont think you can select a newer version phone, because you will probably and up with a bootloop again).
Once it found one it will start downloading the packets! (The servers are sometimes pretty fast, but most time it is a pain in the ass!
It will most time take about 2 to 3 hours to download.
If you experience any problems, please leave them down below!
-Remi
Hi,
My wife has broken the screen on her S6 and as a result it is completely dead. She now has a new phone and I've managed to connect to my PC to get all her old photos off.
However, I was hoping to sell it for spares or repairs with the dead screen but was wondering how I would go about clearing any personal information off it.
Do I have to delete all the necessary files off individually and of so which ones? or is there software that will do it for me.
Any help with this would be appreciated.
Steveh8204 said:
Hi,
My wife has broken the screen on her S6 and as a result it is completely dead. She now has a new phone and I've managed to connect to my PC to get all her old photos off.
However, I was hoping to sell it for spares or repairs with the dead screen but was wondering how I would go about clearing any personal information off it.
Do I have to delete all the necessary files off individually and of so which ones? or is there software that will do it for me.
Any help with this would be appreciated.
Click to expand...
Click to collapse
if you get an mhl cable you should be able to connect the phone to the tv and use that as your screen but only if the screen still responds to touch failing that use the samsung smart switch software and do an emergency firmware recovery I think that wipes your phone.
Sent from my [device_name] using XDA-Developers Legacy app
Cheers mate, looks like the software won't do it anymore. 'Device reset function is no longer supported' oh well.
Thanks anyway
Sent from my SM-T813 using Tapatalk
Apparently someone from Samsung Support said I can use a otg cable to connect to my TV...
http://www.samsung.com/uk/support/m...uchscreen-is-there-any-way-to-access-my-data/
But the ones on eBay haven't got a power input like the link suggests you might need. Has anyone got any experience with using a hdmi otg cable for connecting to a TV?
Sent from my SM-T813 using Tapatalk
this software might work https://skipsoft.net/skipsoft-unified-android-toolkit/
Sent from my [device_name] using XDA-Developers Legacy app
I wrote those instructions for G920F. If your device is not G920F, let me know so I can edit the instructions.
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920F
Region: PHN
Auto: Selected
Manual: Unselected
Binary Nature: Selected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Download" to download factory firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, download and run this Odin (even if you have another one);
https://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
When you open it, press BL and select file which starts with BL from downloaded (from Samfirm) and extacted zip folder.
Do the same thing for AP, CP, CSC.
When you set 4 files to Odin, press and hold volume down + home button + power button for 10 seconds. Then, press volume up button once. After you've done this, connect your phone to your PC. Make sure your phone has enough battery.
Wait for 1 minute. You can see some indications about your device (like "Connected!" on log which is left down corner of Odin).
After that, press Start. When Odin done the installation, phone will restart. When it is restarted, disconnect the cable.
After 1-2 minutes, phone will boot up as completely refreshed device.
I. INTRO AND SUMMARY: I decided to experiment with rooting on this phone, which was lying unused. I was successful, using KingoRoot but from a PC (the Android .apk version did not work for me). Below are the details.
II. NOTE ON MODEL: The "BLu Life One" nomenclature does not identify a specific phone since there were several branded with this name, sometimes but not always including extensions to the name like "XL." This guide is for the phone that, under Settings > About Device gives the following information: Model BLU LIFE ONE; Processor Qualcomm Technologies, Inc MSM8916; Android Version 5.0.2 (I had done an OTA update from 4.4.4 at some earlier point); Kernel Version 3.10.49; Build Number LRX22G release-keys; Custom Build Version BLU_X010Q_V11_L_GENERIC 20-01-2016 16:15. This phone is described at gsmarena dot com / blu_life_one_(2015)-6930 dot php with pictures, if you need to make sure.
III. PROCEDURE I FOLLOWED:
PART A: On Android Phone
1. Do a factory reset of the phone (after saving anything you may want from the phone beforehand to a different device, of course). Settings > Backup & reset > Factory data reset.
2a. Normally, I would do one more OTA update to get the latest Android version (if there was one) before rooting via Settings > About Device > Wireless Update. However, this crashed consistently and silently. My guess is that BLU changed their update server and the older models can no longer communicate with them, and the OTA update attempt fails (not very gracefully).
2b. When doing the initial setup of the phone coming out of reset, do NOT setup your WiFi yet (otherwise it will automatically try an OTA update and be in an endless loop trying to do so, owing to the problem mentioned above, and your phone will never initialize). Just choose your language and skip all other steps like WiFi, Google account login or setup, etc.
3. Once you have successfully initialized your phone in a clean state, then turn on WiFi and connect to a reliable network.
4. Become a developer on your Android (Settings > About device > Touch "Build Number" 7 times). Turn on USB Debugging (Settings > Developer options > USB Debugging).
5. Go to Settings > Display > Sleep and change to "30 minutes" or "Never" (you can change it back later, but I found the root process would suspend if the phone entered sleep).
6. Open the Play Store, set up your Google Account and download the app Root Checker (Joey Krim version), recommended by KingoRoot to verify that the rooting was successful. You may want to create a separate Google account for this purpose, otherwise if you connect to your primary one, it will attempt to sync your email, calendar, and all sorts of other stuff to your phone from your Google account, which you may not want at this point. Or you can try to disable all sync and all automatic App update from your Google account and Play Store as early in the process as it will let you.
PART B: On PC
** NOTE: You may want to read the section below IV. PROTECTING YOUR PC before doing this part! **
7. Connect your Android to your PC via the USB cable. It may try to download various drivers, some of which may be successful and others not, but don't worry if some driver installations appear to fail--Kingoroot apparently has its own ADB drivers that it installs during the early part of the rooting process.
8. On your PC, go to kingoapp.com (avoid downloading from other sites), and click on the "Download for Windows" link to download kingoroot.exe on your PC (I earlier tried the "Download for Android" link to sideload the KingoRoot.apk file, but this version stalled at 90% and did not work--the Windows version is stated as being more reliable and this turned out to be true for me).
9. Run kingoapp.exe on your PC with your phone connected, and let it install. Uncheck the box "Install Recommended App" when it appears and allow it to run. (The mysterious "Recommended App" turns out to be a sponsored "SuperBattery" App that's pretty useless. If you accidentally allow it to install, you get the option to uninstall it later.)
10. Accept installation of the Kingo Link App over the USB. Google "Play Protect" will try at least twice to warn you about the danger of allowing this, but if you want to root, you need to accept it.
11. The program will prompt you to enable USB Debug mode if you didn't already do it, then will install an ADB driver (which Windows Plug and Play was unable to install successfully in my case). You will then get a prompt on the phone to accept USB connection from the computer with signature specified. Check the box "Always Allow from this Computer" and allow.
12. Finally, the screen "BLU LIFE ONE / Root your Android. Make it more interesting!" screen will appear on the computer with a ROOT button. This means that the drivers installed properly and the KingoRoot PC program is communicating properly with the phone. Press the ROOT button, after unchecking the box "Install recommended app."
13. At various points, Google will ask to "check device activity for security problems, and prevent or warn about potential harm. / Learn more in the Google Settings App," which I always declined.
14. At various points, the phone screen will turn white and then return to the home screen. Finally, the computer should show "ROOT SUCCEED / Would you make a donation to support us?" You can close the PC program at this point.
PART C: On Android Phone
15. Reboot the phone (NOT a Factory Reset, just a simple Reboot). I found the Google Play would not work without this additional reboot.
16. Run the previously downloaded Root Checker App. A prompt from KingoRoot's SuperUser app will appear, asking you if you want to allow Root access to the Root Checker app, to which, of course, you must say "Yes." It should confirm that you have root access.
17. Do NOT uninstall the KingoRoot SuperUser App, otherwise you will lose root access. (It is possible to replace it with others like SuperSU, but that must be done and run FIRST, before uninstalling KingoRoot's SuperUser. I did not bother with replacing KingoRoot's SuperUser with another.)
IV. PROTECTING YOUR PC
Since I'm wary of installing software on my PC from sources that are by definition hacking sources, I took the following steps to protect my PC and it's data. You may wish to do the same, even though I have not read reports of KingoRoot, if downloaded from it's official site, containing Malware or covertly installed Adware. It IS suspicious, however, that the ADB driver installed by KingoRoot advertises itself as "Name: Google, Inc., Publisher: Finger Power Technology Co., Ltd." Clearly naming the driver "Google, Inc." is a way to reassure people who see the name "Google, Inc." on the screen without realizing that it's not in the "Publisher" field--one wonders why they would bother with this deception if there weren't an ulterior motive behind it.
1. I used an old netbook PC for the rooting, with no important data on it. I did NOT use my primary PC with my important data.
2. I ran the program under a non-administrative username. Of course, I had to provide an administrator password at two points, but at least I knew each time that administrative access was being requested.
3. I uninstalled the KingoRoot program from the PC after I was done with it and deleted the downloaded executable installation file, and confirmed that the installation folder was deleted as well.
4. Lastly, I did a system Restore to a point earlier than my installation of the KingoRoot program (you may want to create a Restore Point for this purpose beforehand), so that any other system files accidentally or intentionally corrupted or installed by KingRoot would also be restored to their original state or removed. Note that while System Restore often uninstalls programs that were installed after the Restore Point you go back to, it did NOT do so for KingoRoot.