Database Info

[Q] Nexus S cannot unlock bootloader or flash with Odin

I've got a Nexus S that got screwed up from the 2.3.6 OTA. It can go into fastboot mode and recovery mode but it will not boot into Android. When you try to unlock the bootloader you get the unlock screen, can select yes but when you press power the device just hangs. If you go into download mode you get a screen about unlocking the bootloader. Odin detects the device, retrieves the pit, sends the image you want to flash to the phone and the phone says image verified. Then it just does nothing. Odin just sits there and there is no other feedback on the device. It looks like if the bootloader is locked you cannot flash with Odin either. Or at least if the device goes into the strange unlock bootloader screen instead of the true download mode screen Odin flashes fail. I have searched and searched and cannot find a resolution to this problem. Has anyone figured out why some devices hang when you try to unlock the bootloader and has anyone found a way to work around this problem. I am trying to help a guy out and don't want to give him back his phone telling him there is simply nothing I can do for him. He has a TMO device in Thailand. Samsung service here will only service phones sold in Thailand through authorized channels. Since it has a TMO model number they won't touch it.

push clockwork with fastboot

tylerwatt12 said:
push clockwork with fastboot
Click to expand...
Click to collapse
Can't. Clockwork recovery image is sent to the phone. Then it says failed because bootloader lockaed, use "fastboot oem unlock" to unlock the bootloader. And on the phone it says something like Flash FailedState LOCKEDbootloader.
Without being to unlock the bootloader no image can be flashed. I even tried a stock boot image just for a test and it was rejected in the same manner. With the bootloader being locked down it won't let me flash anything. I would need a stock signed rom with android-info.txt and android-product.txt files. I have yet to find one. I think that would flash the phone.
Odin is a no go also. The images are pushed to the phone, the phone verifies the images and then doesn't flash them due to the bootloader being locked. And in download mode I don't get the shovel guy I get a screen telling me to unlock the bootloader but I am connecting in the manner that Odin can see and talk to the phone. The phone just refuses to flash the images once they are downloaded to it.

same for my nexus s,how to solve it?thx

I'm also having the problems here.
However, I simply cant get fastboot to work. It is continually stuck on 'waiting for device' (since the 2.3.6 OTA update).
I tried to flash an old 2.3.4 stock ROM I had on my SDcard, but recovery wont let me. ClockworkMod also cant be flashed because of the fastboot problem.
Yes, I checked that my drivers are up to date, I've tried using fastboot from both windows 7 and Ubuntu 11.04.

splinter701 said:
I'm also having the problems here.
However, I simply cant get fastboot to work. It is continually stuck on 'waiting for device' (since the 2.3.6 OTA update).
I tried to flash an old 2.3.4 stock ROM I had on my SDcard, but recovery wont let me. ClockworkMod also cant be flashed because of the fastboot problem.
Yes, I checked that my drivers are up to date, I've tried using fastboot from both windows 7 and Ubuntu 11.04.
Click to expand...
Click to collapse
Do you mean getting stuck when you try to unlock the bootloader (fastboot oem unlock) or can you not even get into the bootloader at all.

I can get into the bootloader with "adb reboot-bootloader" or just holding the power and volumeup keys on. However, no fastboot commands work at all. My lock state = unlocked, but even though I have the superuser app installed, I dont have root access.
All the problems started when I foolishly applied the OTA update from 2.3.4 to 2.3.6.

maybe try on another pc?

splinter701 said:
I can get into the bootloader with "adb reboot-bootloader" or just holding the power and volumeup keys on. However, no fastboot commands work at all. My lock state = unlocked, but even though I have the superuser app installed, I dont have root access.
All the problems started when I foolishly applied the OTA update from 2.3.4 to 2.3.6.
Click to expand...
Click to collapse
Reinstall drivers?
Sent from my Nexus S 4G using xda premium

Had the same problem ... but there's a YouTube video where the guy shows how to root any nexus device... here's the link but view from the PC because within the video there's a link saying that this video is old and to click the box within the video screen
Also there should be a link that says Nexussrootnew ... click on it to download and extract it and move it to C drive... within the file Ull have the USB drivers superuser ... recovery. Once moved into C drive open Command Prompt and type:
>cd c:\Nexussrootnew "enter"
>Fastboot Device"s" < Forgot lol
>FastBoot OEM Unlock
Just Follow the step in the video and Ull be fine
"REMEMBER Watch Video Via PC"
http://m.youtube.com/#/watch?deskto...e.com/watch?v=xwe4sWH67dk&v=xwe4sWH67dk&gl=US
Sent from my Nexus S using xda premium

Thanks so much YourMainDude! I usually avoid videos for instructions on this kind of thing, but this one was actually good.
For anyone who comes across this thread again, the tools you need seem to be in the SDK but do not work. The tools that work are at the website of the above video-maker (I cant post links yet, but if you search google for 'nexussrootnew.zip' the first hit should be the website nexusshacks.com)
I'll be installing cyanogenmod I think, since I'd rather that I never again have an OTA update from google.

splinter701 said:
Thanks so much YourMainDude! I usually avoid videos for instructions on this kind of thing, but this one was actually good.
For anyone who comes across this thread again, the tools you need seem to be in the SDK but do not work. The tools that work are at the website of the above video-maker (I cant post links yet, but if you search google for 'nexussrootnew.zip' the first hit should be the website nexusshacks.com)
I'll be installing cyanogenmod I think, since I'd rather that I never again have an OTA update from google.
Click to expand...
Click to collapse
=] your most welcome sir
Sent from my Nexus S using xda premium

YourMainDude said:
Had the same problem ... but there's a YouTube video where the guy shows how to root any nexus device... here's the link but view from the PC because within the video there's a link saying that this video is old and to click the box within the video screen
Also there should be a link that says Nexussrootnew ... click on it to download and extract it and move it to C drive... within the file Ull have the USB drivers superuser ... recovery. Once moved into C drive open Command Prompt and type:
>cd c:\Nexussrootnew "enter"
>Fastboot Device"s" < Forgot lol
>FastBoot OEM Unlock
Just Follow the step in the video and Ull be fine
"REMEMBER Watch Video Via PC"
link
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I tried this but it still requires bootloader to be unlocked so it didn't work. My problem is similar to OP's. My phone appears to offer the bootloader unlock option, but selecting 'yes' to unlock fails to actually unlock. So nothing else works to restore the ROM. Though the phone does accept commands from adb just fine.
Anyway, I'm just posting this in case anyone else has the the same issue w/ bootloader not unlocking.

[GUIDE] How to recover from OnePlus soft bricked?

I decided to write a guide on how to recover from a bricked OnePlus One. This is my first guide.
About me: I am a newbie on Android.However, the XDA community has taught me a lot about my Android phone for the first month of using it. That's right! I have only been using Android for less than one month so take this guide with a grain of salt. But if you happen to soft brick your One, this is the guide to turn to. I have created two mind-bending/heartbreaking/frightening scenarios that I have experienced. Though, resolved thanks to this community.
Note: This will wipe your phone!
Scenario 1:
Soft bricked, (CM gear keeps spinning but won't boot to lock screen)
Scenario 2: Updated kernel on a non-compatible firmware.
Soft bricked, screen on 1+ logo and won't boot to lock screen.
Solution:
1. Download the toolbox from: (Make sure you download your version)
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
2. Install the file.
3. Disconnect your OnePlus One from computer and power off your phone.
4. Go into Fastboot Mode (Volume Up + Power button) wait on vibrate
5. Plug in your OnePlus One.
6. Locate and open the OPO Toolbox.
7. Click Flash CM XNPH22R.
8. You should see command prompt open, just wait until it finishes doing it's thing.
9. Unplug and power off your phone.
10. Power ON your phone and wait until it prompts you re-setup your phone.
Congrats you have just fixed your phone from a soft brick. Simply follow the video from the link provided on step 1 to re-root your phone.
Note: If you have unlocked your bootloader, you do not need to unlock it again.
How to find out if you have unlocked bootloader:
1. Locate the folder where you installed the OPO Toolbox.
2. Hold Shift and right click on ANY white area within the folder.
3. Left click 'Open command window here'
4. Type:
fastboot oem device-info
If it returns True on tampered. Then you have unlocked your bootloader.
I hope this guide helps solve your soft-bricked problem. Good luck!

I suggest that a mod moves this to the General section

pandasa123 said:
I suggest that a mod moves this to the General section
Click to expand...
Click to collapse
Report the thread if you think its necessary.

Well I got this FAILED in the command line, and afterwards didnt got a re- setup...
what am I doing wrong here?:crying:

Digital Arm said:
Well I got this FAILED in the command line, and afterwards didnt got a re- setup...
what am I doing wrong here?:crying:
Click to expand...
Click to collapse
You don't have an unlocked bootloader.
Transmitted via Bacon

timmaaa said:
You don't have an unlocked bootloader.
Transmitted via Bacon
Click to expand...
Click to collapse
Thx got it:cyclops:

Scenario 2: Updated kernel on a non-compatible firmware.
Soft bricked, screen on 1+ logo and won't boot to lock screen.
Solution:
1. Download the toolbox from: (Make sure you download your version)
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
2. Install the file.
3. Disconnect your OnePlus One from computer and power off your phone.
4. Go into Fastboot Mode (Volume Up + Power button) wait on vibrate
5. Plug in your OnePlus One.
6. Locate and open the OPO Toolbox.
7. Click Flash CM XNPH22R.
8. You should see command prompt open, just wait until it finishes doing it's thing.
9. Unplug and power off your phone.
10. Power ON your phone and wait until it prompts you re-setup your phone.
Congrats you have just fixed your phone from a soft brick. Simply follow the video from the link provided on step 1 to re-root your phone.
Note: If you have unlocked your bootloader, you do not need to unlock it again.
Hi i am stuck in scenario 2...I did all a u said but i cant flash CM XNPH22R ...where do i find this file...i cant find it on my phone either ..pls help ??

Thank god for this thread omg, saved my life

Locked Bootloader
This didn't work...
My phone is Soft Bricked (oneplus logo freeze) locked bootoader and usb debuging is not enabled.
What can I do to fix it??

RiccoSuave said:
This didn't work...
My phone is Soft Bricked (oneplus logo freeze) locked bootoader and usb debuging is not enabled.
What can I do to fix it??
Click to expand...
Click to collapse
But why happened this ? Whats the last actions attempted to do with the phone before the brick?
Tecleado desde mi 1+1.

Champi12301 said:
But why happened this ? Whats the last actions attempted to do with the phone before the brick?
Tecleado desde mi 1+1.
Click to expand...
Click to collapse
I did an ota update and it went in to a boot-loop, so I went into fast-boot and accidentally locked the boot-loader.
I think I have to try to hard-brick it and try the hard-brick solution with the qualcom drivers.

RiccoSuave said:
I did an ota update and it went in to a boot-loop, so I went into fast-boot and accidentally locked the boot-loader.
I think I have to try to hard-brick it and try the hard-brick solution with the qualcom drivers.
Click to expand...
Click to collapse
Then first you need to unlock the bootloader via fastboot,but that action erases all data. I assume,if you modified the boot via fastboot, USB DEBUGGING is working,so after try to do the softbrick tutorial of the thread.
Tecleado desde mi 1+1.

how do i know which tool box version is mine ?
---------- Post added at 07:42 PM ---------- Previous post was at 07:26 PM ----------
i tried the fastboot method, i successfully run alll the commands but still stuck in the bootloop.
i even tried adb, but i cant go into recovery mode for my computer to detect it. The weird thing is i can easily go into the fastboot mode but for some reason i can go into recovery mode. i tried turning of the phone by holding power button too long and then vol down + power button, still no luck, now im stuck with 2 options,
1. the toolkit solution
2. the qualcom thingy. It's been two days without my opo, and i feel so lost ! PLS if anyone sees my comments plss respond to me PLS! i willl forever be grateful to you!

deanwinchester370 said:
how do i know which tool box version is mine ?
---------- Post added at 07:42 PM ---------- Previous post was at 07:26 PM ----------
i tried the fastboot method, i successfully run alll the commands but still stuck in the bootloop.
i even tried adb, but i cant go into recovery mode for my computer to detect it. The weird thing is i can easily go into the fastboot mode but for some reason i can go into recovery mode. i tried turning of the phone by holding power button too long and then vol down + power button, still no luck, now im stuck with 2 options,
1. the toolkit solution
2. the qualcom thingy. It's been two days without my opo, and i feel so lost ! PLS if anyone sees my comments plss respond to me PLS! i willl forever be grateful to you!
Click to expand...
Click to collapse
Did you find a solution ?
I'm facing the exact same issue on my OPO.
>> bootloader locked
>> no recovery
>> impossible to unlock the bootloader
>> OPO stuck at 1+ logo and keep rebooting agin and again and again...
....i think my OPO is dead T_T
Is it a way to force the bootloader unlock ?
Please HELP !!!

Didn't work for me
I'll give the background first as it might help. I long while back I did a manual upgrade to CM12s using the guide in this video "How to Install CM12S on OnePlus One - No Root or TWRP Required, No Data LOSS" from the oneplus exclusive Youtube channel.
It worked great no problems.
I recently I got the OTA update to CM13. There were several features I didn't like so I decided to go back. I repeated the process shown in the video but now my phone gets stuck on the CM logo screen and won't go past. I tried again but the same result. Then (I can see heads shaking, sorry) I tried a factory reset from the recovery screen, still the same goes past the 1+ logo but gets stuck at the CM logo. Then I found this guide, downloaded the toolbox but when I try to plash it says "fastboot is not recognized as an internal or external command.
Any ideas?
Found a link on one of the threads here that said a guide on Reddit was useful, that didn't work as well. I am trying.

All done
davmeva said:
I'll give the background first as it might help. I long while back I did a manual upgrade to CM12s using the guide in this video "How to Install CM12S on OnePlus One - No Root or TWRP Required, No Data LOSS" from the oneplus exclusive Youtube channel.
It worked great no problems.
I recently I got the OTA update to CM13. There were several features I didn't like so I decided to go back. I repeated the process shown in the video but now my phone gets stuck on the CM logo screen and won't go past. I tried again but the same result. Then (I can see heads shaking, sorry) I tried a factory reset from the recovery screen, still the same goes past the 1+ logo but gets stuck at the CM logo. Then I found this guide, downloaded the toolbox but when I try to plash it says "fastboot is not recognized as an internal or external command.
Any ideas?
Found a link on one of the threads here that said a guide on Reddit was useful, that didn't work as well. I am trying.
Click to expand...
Click to collapse
No one replied to this but never mind, took me two days but I now have a working phone. So you can call in the dogs, cheers

hi davmeva
did you fixed your oneplus one till now or not because i have also same situation here and no success till now .
i did by mistake all this stuff and now nothing work still same condition
if you got any solution please share it

[guide] blu life xl (model: #l050u) [root / bootloader unlock / faq]

The BLU LIFE XL phone is an unlocked GSM platform device.
Currently there are absolutely no threads on the internet with information related to this device. I am not responsible for any damage done to your device, you assume sole responsibility for whatever you do to your devices. If you have questions, please reply to this or PM me, I'll be glad to help any of you!
================
Things you should know before you do anything listed in this post:
- Bootloader unlocking WILL ERASE USER DATA!!!!
- Successful root attempts disable OTA updates. (Unroot + Factory Reset MIGHT fix this)
- You must have OEM unlocking & USB debugging enabled in the developer menu.
- Common sense, don't flash anything you find on the internet randomly, you will cause irreparable damage, I learned that the hard way.
- Download & install the ADB Universal drivers & Android SDK tools (links @ bottom)
================
If you'd like to make a backup of your stock ROM, you can use romdump, it's a nifty tool that does exactly what it says, and it works on pretty much any rooted android phone. (yay) DL: http://d-h.st/ErS
- Download & extract to root directory of your sdcard.
- Open Root Browser (Or any file browser that's for rooted devices)
- Navigate to the path where you copied/downloaded romdump
- Move romdump to /data/local/
- Long press romdump and check all 3 rows of boxes above and press"OK"
- Open terminal emulator (or any equivalent terminal emulator app)
- Type "export PATH=/data/local/bin:$PATH"
- Type "su"
- Type "chmod 04755 /data/local/romdump"
- Type "/data/local/romdump"
- Wait until the process finishes, do NOT do anything with your device, set it down and leave it.
================
Rooting The Device:
- Have USB debugging, OEM unlocking & unknown sources enabled.
- Download & install the latest version of KingRoot.
- Swipe up three times, press "try it"
NOTICE: If your device restarts through the process, don't worry, your device isn't broken, but there's a good chance the root attempt failed.
================
Unlocking/Locking The Bootloader (THIS WILL ERASE ALL OF YOUR DATA!):
- Power off the BLU LIFE XL
- Hold down POWER + VOL UP until the phone turns on.
- Release POWER button, wait for the android to appear on your screen, it might say "No Command", in that case, just press the POWER button once to pull up the recovery menu.
- Use VOL DOWN to navigate down to "Reboot to bootloader" & Press VOL UP
- Plug your phone into your computer
- Navigate to your android SDK folder, and find fastboot. (If you don't have the android SDK downloaded, refer below)
- Type fastboot devices and see if your android device is recognized.
- Type "fastboot oem unlock"
- A menu should appear on your phone screen telling you about unlocking your phone, press VOL UP to unlock your bootloader, or VOL DOWN to cancel.
Alternatively, if you wish to re-lock your bootloader, follow these steps above, however type "fastboot oem lock" instead of "fastboot oem unlock"
================
FACTORY MODE & DEVICE TESTING MENUS:
- Power off BLU LIFE XL
- Press POWER & hold VOL DOWN until the phone turns on.
- Release grip of power button, whilst holding VOL DOWN.
================
Downloads:
Android SDK: https://dl.google.com/android/android-sdk_r24.4.1-windows.zip
ADB Universal Drivers: http://www.mediafire.com/download/uo3t409a9vz3kh3/adbdriver_v1.0.zip
KingRoot: https://androidmtk.com/download-kingroot-application
Romdump: http://d-h.st/ErS

My phone bricked while updating via OTA. It was a fresh L050U, so I don't know why it happened. The only existing stock firmware for repairing is behind a paywall, and I've only found a fw for L050L. Should I use them or what...?

redkvothe said:
My phone bricked while updating via OTA. It was a fresh L050U, so I don't know why it happened. The only existing stock firmware for repairing is behind a paywall, and I've only found a fw for L050L. Should I use them or what...?
Click to expand...
Click to collapse
I'm not sure what the differences are between the L050L & L050U. If you could provide me the ROM link, I'll peel through it and compare it to the dumped L050U rom that I have and get back to you.
By the way, I also replied to your comment on reddit.

TheDarknessz0rz said:
I'm not sure what the differences are between the L050L & L050U. If you could provide me the ROM link, I'll peel through it and compare it to the dumped L050U rom that I have and get back to you.
Really could use both those rom links. Can you guys help? rooted my phone and now OTA updates have been disabled.
Click to expand...
Click to collapse

blkkalel said:
TheDarknessz0rz said:
I'm not sure what the differences are between the L050L & L050U. If you could provide me the ROM link, I'll peel through it and compare it to the dumped L050U rom that I have and get back to you.
Really could use both those rom links. Can you guys help? rooted my phone and now OTA updates have been disabled.
Click to expand...
Click to collapse
The ROM I have dumped has personal applications and accounts integrated, I will get around to dumping a clean ROM for you guys soon.
Papa bless
Click to expand...
Click to collapse

BLU Life XL needs all that the mainstream devices have.
Thank you for the info above. It's such a shame this device has such limited info online. I'm not really a Noob, but also not close to a developer. How does one go about creating a custom recovery and a sweet ROM? Do you think you tube might have a how to that is on point or is there a spot here that we as users could request pros to check on it?

BLUE LIFE XL (L050U) has anyone else been successful using this root kit?
@do_root / TheDarknessz0rz, hey just wondering if the BLUE LIFE XL (L050U) you designed this tutorial for had a specific build that is needed to do this without bricking (like markressler/redkvothe whotf-ever did with his device)? In other words what was the build# of the L050U you designed this root process around? Just wondering man so I can get this done without any worries. I shouldn't have any issues using your root process on my BLU LIFE XL (L050u) Build: ALPS.L1.MP6.V2.15.2_6592.WET_P37 Custom Build version: BLU_L050U_V12_GENERIC, right? I've rooted every android device I've owned back to the original Droid1 without ever bricking during the flashing process. Just wondered if there might be a specific reason this other dude bricked his device.
Thanks in advance for even making a root kit for this device. Would appreciate any advice you have here.
-jim :fingers-crossed:
Edit: I'm ready to do this - just wanted to hear your feedback before I give it a rip.

@heatgap, I also have a L050U device. Where you able to unlock bootloader and root your BLU LIFE XL using the procedure desribed above? BTW, Thank you @TheDarknessz0rz
I am new at rooting, etc... Any additional steps you had to do? Or any advice you might give a rookie/noob to be able to get this done?
Many thanks!
Sisafokker

MOSTLY Stock images / Seeking assistance with recovery
Okay, I've dumped all of the raw images.
Most of them are stock, with the exception of system.img and recovery.img
recovery: insecure ADB, which really does no good until I can put together a custom recovery, or at least get a shell.
system: pre-rooted with SuperSU. Also, will NOT reflash recovery to stock on reboot.
Coming from stock, after you've backed up your user data (because it will be wiped), boot into fastboot mode.
Issue a "fastboot oem unlock-go" to unlock the bootloader. (This only has to be done once.) THIS WIPES EVERYTHING!
Then "fastboot flash system system.img" (This takes a while.)
After first boot and setup, download SuperSU from play store, install and update.
I'm working on putting together a working custom recovery, but I'm not an expert at this.

Succeded!!! Rooted device!
Following @TheDarknessz0rz initial post, plus some additional help from other posts (I am a noob, needed extra help) I was able to Root my Blu XL Life. Thank you @TheDarknessz0rz for you post, I took the liberty to expand on it in to make it more "Noob friendly" :
BTW, my Blu Life XL is:
Custom Build Version: BLU_L050U_V13_GENERIC
Android Version: 5.1
This is exactly what I did:
1 - Installed Android SDK on your computer: download the program, extract, Start the "SDK Manager" file and deselect everything except “Android SDK Platform-tools”)
2 - Power off the BLU LIFE XL
3 - Hold down POWER + VOL UP until the phone turns on.
4 - Release POWER button, wait for the android to appear on your screen, it might say "No Command", in that case, just press the POWER button once to pull up the recovery menu.
5 - Use VOL DOWN to navigate down to "Reboot to bootloader" & Press VOL UP
6 - Plug your phone into your computer with a USB cable. Your phone should indicate that the device is connected.
7 - On your computer, Navigate to your android SDK folder , open the "platform-tools" subfolder and Shift+Right Click on an empty area. Choose “Open a Command Prompt Here”
8 - On your computer, On the Command Prompt: Type "fastboot devices" and see if your android device is recognized.
9 - On your computer, On the Command Prompt: Type "fastboot oem unlock"
10 - A menu should appear on your phone screen telling you about unlocking your phone, press VOL UP to unlock your bootloader, or VOL DOWN to cancel.
11 - You should see on your computer´s command prompt "OKAY, Finished total time 20.4345 sec" (approx).
12 - Your phones screen should remain black, with a few rebooting options available. In my case, I had to type on the command prompt "fastboot continue" to make the phone reboot as the "volumen up or down" were not recognized when I pressed them on my phone.
13 - Phone will be hard rebooted. All data errased.
After you have successfully unlocked your Bootloader,
Download the Kingo Root and Root Checker apps
Run Kingo Root (I had to run it two times as the first time it rebooted when at 20% and it failed) and root the device
Run Root Checker to verify the device has been rooted.
CONGRATULATIONS, this is the first step.... read below.
Once your device has been rooted, then you need to:
1) Install Custom Recovery:
I was able to install a custom recovery on my device following a youtube tutorial: search on youtube for "CUSTOM RECOVERY TWRP PARA EL BLU LIFE XL" by Luis Robert (sorry, cannot post external links)
2) Update your SU Binary (you will be told about this when you open either SuperSu or Kingo Super User...
I had massive problems updating the SU Binary, tried 5 different methods but the only one that worked was this youtube tutorial: search for "How to Replace Kinguser KingRoot with SuperSU No PC" by Iron Tech. The tutorial was meant to replace KingoRoot by SuperSU, but in the process it updated my SU Binary (I spent at least a full day trying different methods that did not work for me)
In theory, now you can enjoy all the benefits and options that a rooted device provides...
Hope this helps
Thanks again for the help!
Cheers
Sisafokker

This is going to sound stupid, I screwed something up when I was editing a file in /system and now I'm in a boot loop. Also, when I went ot go try to download the raw stock roms images, the download would not initiate. Could you put the upload them somewhere else or is there anything that I can do with the stock recovery that could get me out? I also do not have like anything dumped or anything. L0051UU variant by the way. Thanks in advance

br21763 said:
This is going to sound stupid, I screwed something up when I was editing a file in /system and now I'm in a boot loop. Also, when I went ot go try to download the raw stock roms images, the download would not initiate. Could you put the upload them somewhere else or is there anything that I can do with the stock recovery that could get me out? I also do not have like anything dumped or anything. L0051UU variant by the way. Thanks in advance
Click to expand...
Click to collapse
I do not have any stock images, the images i have are for my device specifically, i'd have to rid the image of custom files first.

Okay, thanks I think I understand, but is there anything that you can think of that could help me in my situation? Or would I be best off contacting BLU?
Thanks again

br21763 said:
Okay, thanks I think I understand, but is there anything that you can think of that could help me in my situation? Or would I be best off contacting BLU?
Thanks again
Click to expand...
Click to collapse
well if you've got nothing to lose, I'd just try to flash the L050L firmware onto the device.

sisafokker said:
Following @TheDarknessz0rz initial post, plus some additional help from other posts (I am a noob, needed extra help) I was able to Root my Blu XL Life. Thank you @TheDarknessz0rz for you post, I took the liberty to expand on it in to make it more "Noob friendly" :
BTW, my Blu Life XL is:
Custom Build Version: BLU_L050U_V13_GENERIC
Android Version: 5.1
This is exactly what I did:
1 - Installed Android SDK on your computer: download the program, extract, Start the "SDK Manager" file and deselect everything except “Android SDK Platform-tools”)
2 - Power off the BLU LIFE XL
3 - Hold down POWER + VOL UP until the phone turns on.
4 - Release POWER button, wait for the android to appear on your screen, it might say "No Command", in that case, just press the POWER button once to pull up the recovery menu.
5 - Use VOL DOWN to navigate down to "Reboot to bootloader" & Press VOL UP
6 - Plug your phone into your computer with a USB cable. Your phone should indicate that the device is connected.
7 - On your computer, Navigate to your android SDK folder , open the "platform-tools" subfolder and Shift+Right Click on an empty area. Choose “Open a Command Prompt Here”
8 - On your computer, On the Command Prompt: Type "fastboot devices" and see if your android device is recognized.
9 - On your computer, On the Command Prompt: Type "fastboot oem unlock"
10 - A menu should appear on your phone screen telling you about unlocking your phone, press VOL UP to unlock your bootloader, or VOL DOWN to cancel.
11 - You should see on your computer´s command prompt "OKAY, Finished total time 20.4345 sec" (approx).
12 - Your phones screen should remain black, with a few rebooting options available. In my case, I had to type on the command prompt "fastboot continue" to make the phone reboot as the "volumen up or down" were not recognized when I pressed them on my phone.
13 - Phone will be hard rebooted. All data errased.
After you have successfully unlocked your Bootloader,
Download the Kingo Root and Root Checker apps
Run Kingo Root (I had to run it two times as the first time it rebooted when at 20% and it failed) and root the device
Run Root Checker to verify the device has been rooted.
CONGRATULATIONS, this is the first step.... read below.
Once your device has been rooted, then you need to:
1) Install Custom Recovery:
I was able to install a custom recovery on my device following a youtube tutorial: search on youtube for "CUSTOM RECOVERY TWRP PARA EL BLU LIFE XL" by Luis Robert (sorry, cannot post external links)
2) Update your SU Binary (you will be told about this when you open either SuperSu or Kingo Super User...
I had massive problems updating the SU Binary, tried 5 different methods but the only one that worked was this youtube tutorial: search for "How to Replace Kinguser KingRoot with SuperSU No PC" by Iron Tech. The tutorial was meant to replace KingoRoot by SuperSU, but in the process it updated my SU Binary (I spent at least a full day trying different methods that did not work for me)
In theory, now you can enjoy all the benefits and options that a rooted device provides...
Hope this helps
Thanks again for the help!
Cheers
Sisafokker
Click to expand...
Click to collapse
My device always returns status locked when I tell fastboot to dump the variables. I'm not sure why, bootloader unlock process says it's successful, however when it comes time to press VOL_UP to finish the process, none of the hardware keys are recognized, I've even issued fastboot continue from command prompt, yet the bootloader refuses to unlock. I'm going to try once more with "fastboot oem unlock-go" and see what happens from there.

TheDarknessz0rz said:
well if you've got nothing to lose, I'd just try to flash the L050L firmware onto the device.
Click to expand...
Click to collapse
Don't mean to sound so clueless but how would I go about doing that? I mean I couldn't find any firmware anywhere, even for other models so could you help me with that part? Also would I be flashing it from the "apply update from sd card" option on the stock recovery?
Thanks a lot

Never mind, I was able to figure out how to flash the system.img file onto my phone. Now it seems to be working perfectly. Thank you very much for all of the help and for uploading the img files, i really appreciate it.
Have a nice day

blu-life-xl Hard brick No problem !!!!!
blu-life-xl Hard brick No problem !!!!!
http://www.needrom.com/download/blu-life-xl-3g-l050l/
dont use the sp flash tool it has a virus only the img
download sp fflash tool from there own site

BLU download site
samgr said:
blu-life-xl Hard brick No problem !!!!!
http://www.needrom.com/download/blu-life-xl-3g-l050l/
dont use the sp flash tool it has a virus only the img
download sp fflash tool from there own site
Click to expand...
Click to collapse
Hey thanks for this link - - - - this site could help a lot of people
My phones backed up and i want to test the download file

hard brick NO! problem
Rickrocks013 said:
Hey thanks for this link - - - - this site could help a lot of people
My phones backed up and i want to test the download file
Click to expand...
Click to collapse
try it it works!!!!!!!!!!!!!!!!!!!:laugh:

i can install twrp.img adb & windroid

can anyone help me, i have this problem and i can install twrp.img i ty adb & windroid

fastboot flash recovery filename.img from bootloader to install recovery

gumymoty said:
can anyone help me, i have this problem and i can install twrp.img i ty adb & windroid
Click to expand...
Click to collapse
You need to post more info. The screenshots don't really tell us anything, and really are not that useful. In particular:
- What command you used. Fastboot is typically used to flash TWRP, not adb
- What outputs or error messages received.
- What version TWRP you tried to install (full filename)

redpoint73 said:
You need to post more info. The screenshots don't really tell us anything, and really are not that useful. In particular:
- What command you used. Fastboot is typically used to flash TWRP, not adb
- What outputs or error messages received.
- What version TWRP you tried to install (full filename)
Click to expand...
Click to collapse
https://youtu.be/mjC3fanJ4rQ
https://youtu.be/yVJcrii2HFA

gumymoty said:
Click to expand...
Click to collapse
Videos don't play. Are those videos that you made, and posted on YouTube? Don't understand why you would do all that, instead of just taking a few minutes to answer the questions I asked (cut/paste text from command prompt, if needed).

redpoint73 said:
Videos don't play. Are those videos that you made, and posted on YouTube? Don't understand why you would do all that, instead of just taking a few minutes to answer the questions I asked (cut/paste text from command prompt, if needed).
Click to expand...
Click to collapse
ok, i bay my tablet recently from a store come with unloked bootloder
i try to instal twrp imge using WinDroid+Universal+Android+Toolkit+ i try all the versions + nvidia shield drivers . dev mode on tablet setings
WinDroid+Universal+Android+Toolkit+ divaice online when i give the command flash recovery i select twrp-3.2.1-0-shieldtablet.img the tablet rebot by the app and go in to boot menu, on the WinDroid+Universal+Android+Toolkit+ showin the mesage flashing recovery , if I choose continue on tablet boot option cold booting linux apears and
tablet reboot normaly turn on , if I choose option fastboot protocol noting hapens

gumymoty said:
if I choose continue on tablet boot option cold booting linux apears and
tablet reboot normaly turn on , if I choose option fastboot protocol noting hapens
Click to expand...
Click to collapse
Nothing is supposed to "happen" when selecting fastboot protocol. It simply puts the tablet in bootloader-fastboot mode, which lets your computer talk to the device using fastboot.
If you want to boot recovery, select recovery from the bootloader selections.

i really hope what thT NICE PERSON SAID TO YOU HELPED IN SOME SIGNIFICANT WAY because i was pissed off by the time i realized you already deleted the videos posted on youtube . You leave them up after you use them in a forum or else it undermines the whole premise of having a forum discussing problems you are having on a device. I know you like your account to be all pretty and neat incase your girlfriend is snooping around in there or what ever but.. If your one of those video in a forum guys have some respect i mean its not like your aol or something. "wow we have the largest tresure trove of information ever ammassed in earths history all on our servers... well delete it nobody is ever "gonna look at it." I was very dissapointed when they blocked access but hey they werent asking for my help. Please don't be offended i like the video guy. its much easier to see and understand than try to explain something to somebody.

How to root Epson Moverio BT-300 security update 5.0

I have found an easier to follow way to root the version 5.0 security update, it follows basic logic for rooting with twrp and magisk after the bootloader is unlocked with the boot.img I patched based off of the most recent security update with the help of @tarkus1000
Reboot to the fastboot interface "adb reboot bootloader" or see my youtube video for the keystroke on the unit itself (useful if you break somthing, it happens)
flash the patched boot.img **see link bellow** now you must reboot to system and select the option in settings "allow oem unlocking"
reboot to fastboot using whichever method suits you, just remember this is an old boot-loader so be patient with it as always
1) enter the command "fastboot oem unlock" sometimes it reboots and you know you have success sometimes it says failed... but it is usually unlocked (The more I study this the more I think its a problem with the android 5.1 dalvik heap its interpreter sometimes skips lines of code)
reboot from the fastboot state is required for unlocking so you have to enter the command "fastboot reboot" even if you get the failed command then wait for about 30 seconds for the device to respond if it does not respond reboot using the power button
2) check for the orange state of the bootloader enter command "fastboot getvar all" if you have orange continue to flash the hacked recovery
3)if boot state is green flash the new boot.img again and repeat step 1, remember to be patient and use commands like "fastboot devices"..ect we are working with android lollipop after all
The bootloader is unlocked and you can flash twrp with "fastboot flash recovery (drag and drop .img here)"
Now we enter the hacky recovery by either going to system and "adb reboot recovery" or with fastboot via "fastboot boot (drag and drop .img here)"
Its a little difficult to have the recovery recognize your mouse I had luck with the logitech M100 doing this;
after you hear the device disconnect from your computer (chirp or whatever) plug in the mouse so the device boots up getting input from the mouse
Twrp will tell you it needs a password (will never be able to decrypt your partition no matter what you tell it ) hit cancel and navigate to the backup tile make a backup and include the recovery.img in your nandroid backup
now to root
flash dissable dm-verity/force encrypt (find on xda)
flash magisk (find on xda)
reboot to system. you may have to download magisk manager app to detect magisk and finish the installation
When you have success remember to reboot back to recovery and make a backup before you make any changes to the system or were gonna have to work something out
how to boot into fastboot manually https://youtu.be/766TR5hFEqs
patched v5.0 boot.img [url]https://drive.google.com/open?id=1KDpLxhYBa2Nto9dTaHFOqEKCfs6B1RjV[/URL]
check out the hacked recovery image (you must use mouse) https://drive.google.com/file/d/1fcLoHw0CTAs7qIYZi2xoaAgImVREHz8O/view?usp=sharing

awesome!

alecthenice said:
@amg314 pointed out to me that the most direct way to do this is through adb since any failure could be catastrophic... In the past we used a recovery that almost worked for Moverio Bt300s, I will link it bellow for academic purposes; anyways (fastboot under some situations requires something special...I really wanna know, I think I got it once by holding power and volume down as it booted and plugged into the computer, can't be replicated so idk what happened)
So start tutorial here
"adb devices"
"adb reboot-bootloader"
"fastboot devices"
"fastboot OEM unlock"
......
"fastboot reboot"
.......
"adb reboot-bootloader"
"fastboot devices"
"fastboot format user data" (all user data lost)
"Fastboot update /path_to_zip/DM-verity_force..." Drag and drop "payload" into cmd after space in update
"Fastboot update /path_to_magisk (same deal)
" fastboot reboot"
Like magic your rooted. Sometimes you have to download magisk manager from the aurora store in order to use all the features.
For this install you need a working adb environment
the latest Intel drivers
dm-verity dissable.zip
Magisk.zip
I believe this to be the cleanest safest way to achieve root (no zombie recovery.img) even though that recovery may be fine I'm cautious to use it more than I did. Anyways. I recommended this. I'll also advise on installing a google ecosystem without twrp if y'all would like. It would be great to grow this device's community
Now that we are rooted though we can combine our boot.img and stick recovery and make a twrp...I'll probably set that aside for another day since I don't have an immediate need for it (unless some genius makes a ROM)
check out the hacked recovery image (you must use mouse) https://drive.google.com/file/d/1fcLoHw0CTAs7qIYZi2xoaAgImVREHz8O/view?usp=sharing
Click to expand...
Click to collapse
Alec!!! You are a GOD in my eyes. I'll give this a go this weekend and report back.

chuck1026 said:
Alec!!! You are a GOD in my eyes. I'll give this a go this weekend and report back.
Click to expand...
Click to collapse
Not to shoot my own post in the foot here but we can install virtual xposed installer and then microg through an included module all without touching our computers. Have fun though guys hahaha I love finding work a-rounds.
https://forum.xda-developers.com/xposed/virtualxposed-xposed-root-unlock-t3760313/page39
^^^^This is pretty much cutting edge android software development so use this as a way to create the right environment on an app by app basis (no root or unlocked boot loader required) kids have been using this to cheat on mobile android games since they dont know how to root. this works for us because we want gapps and there is no hardware command for fastboot mode. be advised my root method still works if you are not intimidated by Epsons' annoying attempt to keep their hardware stock also if you mess up I was informed you are still covered under warranty for "damaged operating system" as if they know its buggy and annoying to work on

google services independent google.map.apk
Use this apk for an easy way to use google maps without google services (less background precessing=more flying) https://drive.google.com/file/d/1GqTrR27gpYXeRl-XtHPbojIwbg89X-9i/view?usp=drivesdk
(No root required)

bricked, thinking about warranty
So I downloaded the nanodroid MicroG installer from the magisk manager (I flashed gapps and google wouldn't whitelist the device ID so I went to microG) and it caused my device to boot loop. It seems my adb key was changed in my device as a result of the install. I don't think this device is worth having root access anymore since i only wanted google services. I do have a usable twrp but the device won't boot to it by default upon boot loop recognition. If I could find a way to tell the device to boot to twrp upon issues (some phones automatically go to recovery upon this situation) I could continue to find ways to make the device more useful. At this point the device responds to adb as (embt3c offline) thoes tricky guys locked me out of fastboot too. Upon boot loop it seems you can get to fastboot only once by repeating the same button inputs you would to get into recovery in the powered off state. Please offer any ideas you may have. Perhaps there is a way we can model the android environment the bt300s operate under with the SDK in order to test our mods? I want to continue but the lack of a button combination to get to recovery just kills me. I hope an engineer of some sort will offer me some guidance on how to proceed. I have seen references of a test plug in order to supply the correct voltage to the chip to trigger fastboot mode but at this point we might as well be hacking with JTAG? I have a small research budget... A spare unit may help development quite a bit. I believe I will use my warranty on this unit so i can continue to enjoy my drone but this is where I stand with this unit. I look forward to insight from the community.

transitioning from script kiddie to developer
So I decided I'm going to learn how to build what we need on this device.
We need
-more test pin info for the hardware fastboot mode (I can build but I'm not good with theory I need help here)
-I'm working on building a virtual moverio bt300. Some guides would be useful. I'm using the android development studio so I can test modules before I brick my device. These babies are too cool for my to resist really. I also downloaded droid explorer in hopes of manually uninstalling the magisk module that bricked my all time favorite waste of time.
-update exactly 24hrs from last time I was able to get into fastboot I was able to get in by holding power and volume down for 10 seconds. I was not able to replicate. Will try again in 24hrs. The device responded to my commands but did not carry them out

recovery mode
We need to find out how to manually put the device into recovery mode. I'm really frustrated this high end "developer" device is so hard to work on. Does anyone know how to do this with code? Idk where to even start my research

Fastboot mode and recovery fix
Hold volume down and power
When green light comes on click volume down while holding power and hold
After first vibration click volume down
Fastboot mode
Repair

My moverio Firmware (FULL ROM) v4.0
Here is a copy of the firmware I am running on my device right now https://drive.google.com/file/d/1xZx6xuubQ-P58LL_-vcuCjPkx-hPTk_v/view?usp=sharing
This is the stock recovery
https://drive.google.com/file/d/1uOofDprPNw4Dqy-euyQwpW3A0LWEZLpy/view?usp=sharing
Stock system
https://drive.google.com/file/d/1f3Xcr4gdKAkG_kiARB3NmEYyjPi41pxA/view?usp=sharing
Twrp prototype (use a mouse that supports linux)
https://drive.google.com/file/d/1fcLoHw0CTAs7qIYZi2xoaAgImVREHz8O/view?usp=sharing

alecthenice said:
Here is a copy of the firmware I am running on my device right now https://drive.google.com/file/d/1xZx6xuubQ-P58LL_-vcuCjPkx-hPTk_v/view?usp=sharing
This is the stock recovery
https://drive.google.com/file/d/1uOofDprPNw4Dqy-euyQwpW3A0LWEZLpy/view?usp=sharing
Stock system
https://drive.google.com/file/d/1f3Xcr4gdKAkG_kiARB3NmEYyjPi41pxA/view?usp=sharing
Twrp prototype (use a mouse that supports linux)
https://drive.google.com/file/d/1fcLoHw0CTAs7qIYZi2xoaAgImVREHz8O/view?usp=sharing
Click to expand...
Click to collapse
Alec, I have to commend you on what you have accomplished with the Bt-300's. Kudos Sir! Keep up the excellent work. :good: We have posted this thread in our facebook group so that all can benefit. If you haven't checked us out, please feel free. You probably have rock star status by now. lol. https://www.facebook.com/groups/269299563510341/
Thanks and Happy New Year!

dvegaman said:
Alec, I have to commend you on what you have accomplished with the Bt-300's. Kudos Sir! Keep up the excellent work. :good: We have posted this thread in our facebook group so that all can benefit. If you haven't checked us out, please feel free. You probably have rock star status by now. lol. https://www.facebook.com/groups/269299563510341/
Thanks and Happy New Year!
Click to expand...
Click to collapse
Thank you for the accolades I am flattered! As for development progress I am trying to figure out what google maps APIs are called upon in the "NLD DJI go 4.22" app developed by the No Limits Drones group. I need this information to know how to patch the system apks and apply the correct form of microG package (basically for google apps and related). On the topic of facebook I have yet to create one but am evaluating cost/benifit on an ongoing basis and will join your community if i do ever make one! I look forward to colaborating on the bt300s now that another creative avenue is unlocked with root access to this cool gadget. Happy new year!

Awesome work!
But I need help, because I am stuck.
I tried different ways with the on and down buttons, but it seems I am doing something wrong.
Everytime the Bt300 boots up normally.
I tried the adb reboot-bootloader, it restarts immediately, but then it`s getting stuck in a
Moverio Boot screen, with the note below "Is now under process"....!?!?! and nothing happens anymore, even after 5minutes it is stuck.
Also it isn`t shown in fastboot devices, just nothing there.
So it seems I can`t get into fastboot by adb command nor manually with the buttons.
ADB Debugging and untrusted sources are enabled, not my first device I try to root, did this on a couple of phones already and are familiar with the process.
But fastboot and the Moverio BT-300 seem to be special.
I tried it now more then 10 times and any hint or advise is greatly appreciated.
My Moverio has the 1.5.0 Firmware installed.

guili2 said:
Awesome work!
But I need help, because I am stuck.
I tried different ways with the on and down buttons, but it seems I am doing something wrong.
Everytime the Bt300 boots up normally.
I tried the adb reboot-bootloader, it restarts immediately, but then it`s getting stuck in a
Moverio Boot screen, with the note below "Is now under process"....!?!?! and nothing happens anymore, even after 5minutes it is stuck.
Also it isn`t shown in fastboot devices, just nothing there.
So it seems I can`t get into fastboot by adb command nor manually with the buttons.
ADB Debugging and untrusted sources are enabled, not my first device I try to root, did this on a couple of phones already and are familiar with the process.
But fastboot and the Moverio BT-300 seem to be special.
I tried it now more then 10 times and any hint or advise is greatly appreciated.
My Moverio has the 1.5.0 Firmware installed.
Click to expand...
Click to collapse
That "moverio is now under processes" screen is your fast boot interface. You should be able to adb pull any .img you need after you pull the boot.img, patch with magisk manager and flash patched_boot.img. Remember the twrp recovery image requires a linux compatable mouse. (You can get "adb su" with twrp recovery if needed) Lemme know if you have any other questions, epson didnt do the cleanest job of with their android implementation most likely for proprietary purposes, we expect better from the parent company Seiko. Have fun.

Yes thanks!
Figured this out in the same second.
I was under the impression that the intel usb/adb driver was already installed, but it wasn`t...
So now I can see it with fastboot devices
Got now the "too many links" message but I follow the guide, this was already explained.
Thanks!
---------- Post added at 02:30 AM ---------- Previous post was at 02:11 AM ----------
Ah now, I need your help/advise.
I need this android-help.text file, which need to be included into the DM-verity_force.zip

guili2 said:
Yes thanks!
Figured this out in the same second.
I was under the impression that the intel usb/adb driver was already installed, but it wasn`t...
So now I can see it with fastboot devices
Got now the "too many links" message but I follow the guide, this was already explained.
Thanks!
---------- Post added at 02:30 AM ---------- Previous post was at 02:11 AM ----------
Ah now, I need your help/advise.
I need this android-help.text file, which need to be included into the DM-verity_force.zip
Click to expand...
Click to collapse
Set the path according to this https://stackoverflow.com/questions/5846197/error-could-not-load-android-info-txt
Dont have android-info.txt? Ill track it down for you within the day. I got it from the original bt300 thread somewhere.
Flashing zips through Bt300 hacked recovery has been tested and is the easiest way to accomplish customization at this point. Please use caution to chose the hacked recovery rather than 4.0 stock. Check your work with "fastboot getvar all" as always.
-cheers

An update on how to manually boot to fastboot "incase you have issues"
Hold power and volume down button while device is powered off
You will feel a vibration and see the epson logo. In this same moment release volume down
Quickly press volume down again (hold power the whole time) and you will be brought to the "moverio is now under processes screen"
Here you will be able to flash/boot to the prototype recovery to rescue yourself.
****prototype is safe you just have to use mouse*****
It is possible to root this device classically with twrp and magisk as a flashable zip. Remember the order is DM-verity dissable, then Magisk.
prototype TWRP cannot decrypt the userdata partition so make sure you act accordingly

alecthenice said:
@amg314 pointed out to me that the most direct way to do this is through adb since any failure could be catastrophic... In the past we used a recovery that almost worked for Moverio Bt300s, I will link it bellow for academic purposes; anyways (fastboot under some situations requires something special...I really wanna know, I think I got it once by holding power and volume down as it booted and plugged into the computer, can't be replicated so idk what happened)
So start tutorial here
"adb devices"
"adb reboot-bootloader"
"fastboot devices"
"fastboot OEM unlock"
......
"fastboot reboot"
.......
"adb reboot-bootloader"
"fastboot devices"
"fastboot format user data" (all user data lost)
"Fastboot update /path_to_zip/DM-verity_force..." Drag and drop "payload" into cmd after space in update
"Fastboot update /path_to_magisk (same deal)
" fastboot reboot"
Like magic your rooted. Sometimes you have to download magisk manager from the aurora store in order to use all the features.
For this install you need a working adb environment
the latest Intel drivers
dm-verity dissable.zip
Magisk.zip
I believe this to be the cleanest safest way to achieve root (no zombie recovery.img) even though that recovery may be fine I'm cautious to use it more than I did. Anyways. I recommended this. I'll also advise on installing a google ecosystem without twrp if y'all would like. It would be great to grow this device's community
Now that we are rooted though we can combine our boot.img and stick recovery and make a twrp...I'll probably set that aside for another day since I don't have an immediate need for it (unless some genius makes a ROM)
check out the hacked recovery image (you must use mouse) https://drive.google.com/file/d/1fcLoHw0CTAs7qIYZi2xoaAgImVREHz8O/view?usp=sharing
Click to expand...
Click to collapse
Flashing zips through the prototype recovery is now the easiest way to make your A/R goggles custom. Im glad I initially did it the old school way for the sake of understanding epson file systems. This twrp works traditionally and has all partitions correct!!!

Bootloader unlock problem with v5.0
It has come to my attention that there is a problem with the bootloader unlock command for version 5.0 firmware
to solve this please boot this boot.img
use the command "fastboot boot boot.img"
****note the command "fastboot flash boot boot.img" may cause issues****
after you boot this boot.img
"fastboot oem unlock"
disregard the response. enter this command after to check your unlock status
"fastboot getvar all"
you should be in the orange state and this will be persistent upon the next reboot
DOWNLOADhttps://drive.google.com/file/d/1_2qwuL85SkirnEu7bHLRigBWrJlPnYXj/view?usp=sharing
Correct getvar all response[/B]https://drive.google.com/file/d/0BzLMyqznaCbVVnFXQ2NqNnppXzg4LVQ0ajNmMmU2c2hjTktJ/view?usp=sharing

Does anyone know where the ota updates are stored on this device? I will pull the updated boot.img and patch accordingly so the bootloader unlock is more simple if i can find the ota...OGs in the original hacking forum have fell silent on this, furthermore it seems that the epson file systems team only wants to utilize my input for their own development so I have stopped communications with the contact I had.
I can post a full nandroid backup on here if others would like to revert to software 4.0