I'm trying to return to stock without usb, but the links from this post don't work http://forum.xda-developers.com/showpost.php?p=34749844&postcount=2
I need a flashable .zip of the stock rom & recovery so that I can turn my phone in for RMA
studjuice said:
I need a flashable .zip of the stock rom & recovery so that I can turn my phone in for RMA
Click to expand...
Click to collapse
Right now there is no flashable image of the stock OS. Google pulled it from their site. But if you can't use USB, you can still use a computer to unzip the image into partitions, then use terminal and `flash_image` to flash each partition. (When I tried using flash_image, it didn't work, so be cautious. If you're rooted you can also use `dd` to flash images, but a typo could brick your phone so don't.)
I bet the easiest thing for you to do is to create individual flashable images for each partition, then boot into CWM and flash each (recovery last, obviously). But I don't know how. In any case, you'll need to wait until Google puts a new mako image on their site: https://developers.google.com/android/nexus/images
---------- Post added at 07:30 AM ---------- Previous post was at 06:56 AM ----------
Actually, depending on how desperate you are, I (or anybody else) could help you. I have a stock recovery installed right now (JOP40D) and I could pull the image with "dd". That won't be a flashable .zip, but you should be able to flash it from within the ROM. I could also get you a copy of my /system partition--there's nothing personal or private in there
If you have a .img, you could pack it into a flashable .zip and download it via dropbox.
Unless you have no access at all to a computer. In that case, you'll just need to wait for Google to release the next version of the image.
fenstre said:
Right now there is no flashable image of the stock OS. Google pulled it from their site. But if you can't use USB, you can still use a computer to unzip the image into partitions, then use terminal and `flash_image` to flash each partition. (When I tried using flash_image, it didn't work, so be cautious. If you're rooted you can also use `dd` to flash images, but a typo could brick your phone so don't.)
I bet the easiest thing for you to do is to create individual flashable images for each partition, then boot into CWM and flash each (recovery last, obviously). But I don't know how. In any case, you'll need to wait until Google puts a new mako image on their site: https://developers.google.com/android/nexus/images
---------- Post added at 07:30 AM ---------- Previous post was at 06:56 AM ----------
Actually, depending on how desperate you are, I (or anybody else) could help you. I have a stock recovery installed right now (JOP40D) and I could pull the image with "dd". That won't be a flashable .zip, but you should be able to flash it from within the ROM. I could also get you a copy of my /system partition--there's nothing personal or private in there
If you have a .img, you could pack it into a flashable .zip and download it via dropbox.
Unless you have no access at all to a computer. In that case, you'll just need to wait for Google to release the next version of the image.
Click to expand...
Click to collapse
I would love some help on packing into a flashable .zip. I found the images here, http://www.randomphantasmagoria.com/firmware/nexus-4/occam/ but I can't do anything with them without fastboot.
I found one guide for creating the flashable zip here: http://forum.xda-developers.com/showthread.php?t=1721680
And a better one here: http://forum.xda-developers.com/showthread.php?t=1949367
In principle, I think you could use your phone to do these, but it would be hard. The hardest step would be extracting individual files from .img files, and I don't know whether you can do that with your phone--it depends on the kernel and the "mount" utility--you would need to mount the .img files as a filesystem and extract from them. Obviously you should avoid flashing /data to ensure that you can keep /sdcard and your CWM backup. And flashing stock recovery should be your last step. In fact, don't flash your stock recovery. Flash the Nexus image version C, then reboot and let the image automatically reflash the recovery. This is safest. But if this step messes up, you will absolutely need to use a computer to fix it.
Actually, there's a far easier way. Somebody could create a CWM backup for you--a backup of version JOP40C. You download it to /data/media/clockworkmod/backups, then use CWM to recover it (use advanced options to recovery ONLY the /system partition (maybe others?), then clear the cache and dalvik cache). Then you OTA upgrade to JOP40D. This will involve downloading a flashable .zip (here). The key is that this will remove root and CWM when you next reboot! If it doesn't remove root, I think you can probably do that yourself.
The thing you can't do without a computer: lock your bootloader. Is using somebody else's computer really out of the question? I think "adb" and "fastboot" work without the rest of the Android SDK, so you could just download them and get to a computer just for the very final step of re-locking the bootloader.
I documented the process I went through to get it back to stock here for future reference:
http://forum.xda-developers.com/showpost.php?p=37064957&postcount=10
You can lock your bootloader without a computer using the BootUnlocker app
Related
Hello,
The home button of my device (Magic) does not work at all. So, I can not confirm to install the CyanogenMod in the recovery screen.
Am I able to install the ROM via fastboot? or does anybody has another suggestion?
Regards,
Omer
Yes, you can flash ROMs via fastboot, but you'll need a system and data img for the ROM, and I'm not aware of a method to package them up based on an update.zip.
I checked inside the archive and saw the images but there also some scripts need to run. That's why; I couldn't dare to flash.
Is there a method I can follow?
osaatcioglu said:
I checked inside the archive and saw the images but there also some scripts need to run. That's why; I couldn't dare to flash.
Is there a method I can follow?
Click to expand...
Click to collapse
You don't need any scripts, just a system and data to flash.
fastboot flash data.img
fastboot flash system.img
You wont find these images inside the update.zip, the sys/data-imgs need to be created from the sys/data folders. Best bet is to ask someone to perform a nandroid backup, backup the imgs, wipe, flash cyan, send you those imgs, restore their old imgs.
Thank you. But, the someone's device should be identical to magic, right? I have dream also. So, I can use the nandroid backups of it. However; I don't think this would be possible. what do you think?
osaatcioglu said:
Thank you. But, the someone's device should be identical to magic, right? I have dream also. So, I can use the nandroid backups of it. However; I don't think this would be possible. what do you think?
Click to expand...
Click to collapse
I'm really not sure, but I think the device would need to have the same size data and system partitions as the Magic, which the Dream doesn't.
Use mkyaffs2 to make the System and Data .img Files
What operating system do you have because if you have linux or a linux virtual machine you could extract the update zip and use the mkyaffs2 utility code.google.com/p/yaffs2utils/ to make the system and data images.
There is also a much easier program called yaffey http://forum.xda-developers.com/showthread.php?t=1645412 but it is windows only
So this thread is kind of old, but I stumbled upon it looking for stuff.
Im using a google galaxy nexus and have a strange issue where I cant connect it via usb when in a different state than fastboot mode. I replaced the usb port (flex cable) already, but it doesnt help (if you got any advice on that, please tell me)
What I actually want to say is that I can't install cyanogen from recovery because I can't connect my phone when in recovery, but I can flash firmware normally via bootloader, I tried that already, so how exactly do I get the images for cyanogen? Because I don't fully grasp it yet.
I can't post in the development forums so I figured I would ask here:
I understand how to use adb and fastboot, etc.. What I am missing is with the new ICS ROM it states that I must "fastboot flash system system.img"; however none of the ICS zip file I have seen come with a system.img file (just the boot.img).
Am I missing something? Any help would be greatly appreciated..
I used the version available on Rootzwiki... not sure if thats the answer you wanted. I'm running 4.0.3 ICS on my wifi XOOM OC to 1.54. No FC's, reboots or anything of the sort. You'll need to be sure that you have su-install.zip, and other img files needed. As I said, you'll find them all on the rootzwiki website under xoom hope this helps, if not good luck.
You are talking about two different things here. I don't know where to start here you're all mixed up. There are several ways to flash a ROM, you can fastboot flash the .img files such as what you are referencing to. Or you can flash an update .zip file from recovery. The way you flash the ROM depends on the source, if its a bunch of *.img files you use fastboot, if it's a *.zip file you use recovery. Just follow the directions given for installation that are provided with the ROM you are downloading.
sboehler said:
I can't post in the development forums so I figured I would ask here:
I understand how to use adb and fastboot, etc.. What I am missing is with the new ICS ROM it states that I must "fastboot flash system system.img"; however none of the ICS zip file I have seen come with a system.img file (just the boot.img).
Am I missing something? Any help would be greatly appreciated..
Click to expand...
Click to collapse
Hello, and welcome to XDA! =] Anyways on with your question. There are two ways to flash a ROM to your xoom. One being fastboot/adb, where you use the command line on your computer to send commands to your device and make it do stuff. This is where you use system.img, boot.img, recovery.img.
The second, is CWM (ClockWorkMod recovery) This, as far as im aware, is the most common way. This is where the .zip's come in. Because you take the .zip you put it on your external SD card. boot into recovery (after flashing CWM of course) and flash the rom. CWM is nice because you can also make a 100% snapshot of your internal memory state via making a nanodroid back up. That way if anything messes up you have a 100% backup you can restore at anytime if you need it.
In a nutshell, You use *.img files with fastboot and .zip files with CWM.
Anyways. If you're new to rooting. Please check out these two threads, They'll help you get started. =]
Xoom Heaven: Root+Non Root Users Are Welcome!
[Guide] Setting up and using adb/fastboot-unlock, flash custom recovery & root
The second guide I did use to flash my own zoom so I can assure you it does work.
Hi,
I don't know if this is the correct section to get this question answered, but I'll try:
I have a new tablet, which is not really known at the moment. I managed to root it and next step would be to port Clockworkmod Recovery to it. Since I only found guides where I always have to repo sync the entire CyanogenMod github (which is 19GB+ as I heard), I searched for an alternative where I could save some traffic
I found a clockworkmod recovery from another tablet and wondered if it was just possible to unpack it, modify the recovery.fstab and repack it again.
Is this possible or do I have to modify more than the recovery.fstab? If yes, could you point me to the right direction?
Regards
dump your stock recovery
unpack the stock recovery and save the vold.fstab somewhere.
upload the stock recovery here
http://builder.clockworkmod.com/
get the output and flash`it
if the key`s are not working, unpack the new cwm, and the old recovery, and put the keys from the old recovery.
if you get some mount points erros, you will have to upload also the saved vold.fstab on the clockwork site when you cook the image.
if this does not offer you a good result, you will need to find a similar device (processor, resolution) that has allready a cwm, and try it
the recovery file is ramdisk/sbin/recovery
Hi,
thanks for showing me a way. Unfortunately builder.clockworkmod.com says it didn't find Android magic. This makes sense, as the image is a uImage with lzma compressed data inside. It seems koush's builder handles only "plain" recoveries...
Bad luck
I guess I'll try your second advice and search for a CWM for a similar device, unpack it, replace the fstab file and repack it again.
Thanks again!
hello I have made the porting on http://jenkins.cyanogenmod.com/job/recovery/lastBuild/console
I end up having a zip archive, how can I make my tablet to read that. I have installed cwm recovery and it is rooted. Let me know how can install it and replace my recovery with this.
BTW I have the original stock firmware of my tablet.
let me know thanks
Hi everyone!
I have come to a slight problem, trying to flash an android L preview port for my N4. I rooted properly, but when CWM asked me if I wanted to fix boot, I unfortunately replied with Yes. After I lost my root, I tried rerooting, when I accidently selected a wipe all function. So, now I have no rom Just a CWM recovery.
I have downloaded a tar.gz factory image file for N4 (4.4.4) and tried adb pushing to the device. The transfer is successful, but when I try to install it from the sdcard (cwm), it reports failure. I googled and read a lot, but not much seems to be helping.
I am using a Mac, btw.
Thanks in advance!!
You cant install a .tgz via recovery. Instead you should download a flashable .zip of your rom. Try this.
CCody said:
You cant install a .tgz via recovery. Instead you should download a flashable .zip of your rom. Try this.
Click to expand...
Click to collapse
Yes, I keep trying to do that but without success.
O tried factory kitkat zip and I tried an L android I downloaded.
Could you provide me witha link to a flashable zip?
Then tell me what you want. A factory image or a custom rom. I would recommand you cyanogenmod. Downloaf the zip for your device. http://www.cyanogenmod.org/
To install stock do this:
Extract .tar.gz (using 7Zip) until you come up with folder named "occam-xxxxx"
Copy the files within it to your fastboot.exe folder
Reboot into boot-loader
Hit flash-all.bat
But you may download latest CM from https://download.cyanogenmod.org/?device=mako and install it via flash .zip in CWM (however I recommend Philz Touch Recovery)
I'd like to flash Nexus 4 port for Android L. I had downloaded android l zip file but when I try to flash it, installation aborted keeps popping up.
And once again, people keep mentioning fastboot.EXE and run a batch file, but again... I am on a Mac. It would mean a great lot if the instructions given were for a mac.
Thanks!
Here's what I did:
1. Install Wugfresh's NRT (search online for it)
2. Download the factory image from the Google website
3. Connect your phone in Recovery mode
4. Open NRT and let it update if it has to
5. Hit "Flash stock + Unroot"
6. The usage is clearly explained at every stage. You should ideally have no problems restoring your phone to a working state. Your data however is most likely lost. Sorry.
(PS: I don't usually recommend toolkits because they take away the fun in messing with the phone manually, but sometimes it becomes necessary to use them. This is one of those times )
I tried flashing CM 11 snapshot M8 release, but it gave me status 7, install failed. I tried to fix it by removing asserts and rezipping, and failed again, without a status.
I am trying to revert back to stock now, nothing else works, and neither will this, so it seems.
EDIT:
I flashed new bootloader and new radio, but when I tried to flash a stock rom, it failed again.
I don't know what to do anymore, I feel like throwing a phone against the wall and just getting a Nexus 5.
to flash the n4 L port, download the zip in the port thread and flash it in recovery. that's all. wipe before you flash.
there was no official L preview for the n4, so you can't flash it from the factory IMG, that's for the nexus 5.
simms22 said:
to flash the n4 L port, download the zip in the port thread and flash it in recovery. that's all. wipe before you flash.
there was no official L preview for the n4, so you can't flash it from the factory IMG, that's for the nexus 5.
Click to expand...
Click to collapse
Cwm reports unable to mount... i updated to 6.0.5.0 cwm, changed to twrp even using fastboot... But nothing is helping.
Was able to port twrp recovery of blitz smartwatch after unpacking and replacing the kernel file with the lemfo lem5's stock kernel file extracted from unpacking stock recovery of lemfo lem5 and then repacking and flashing it to lemfo lem5. The recovery got successfully installed and all features are working except the recovery screen is flipped / inverted but not the touch response. The touch inputs are the same as non inverted screen and using the touch is pain in the a**s. If the touch input field is at 45 degrees then to access it, need to tap at 225 degrees and on the same radius distance. Can anyone let me know how to flip the recovery screen without affecting the touch fields or is there a similar custom recovery for mtk6580 lollipop smartwatch with flipped screen.
I have not found solution
Same problem with kw88h
And all twrp apk from playstore does not recognize as twrp
Recovery
Flashify can make the job
Only commands from adb... for wipe.
There is not enough space to backup or restore and i think only root and flasify is all you need.
geowolf1000 said:
I have not found solution
Same problem with kw88h
And all twrp apk from playstore does not recognize as twrp
Recovery
Flashify can make the job
Only commands from adb... For wipe
There is not enough space to backup or restore and i think only root is all you need
Click to expand...
Click to collapse
I have got everything working in twrp recovery. The flip recovery is no more a problem now as with some practice now I am comfortably able to use this inverted twrp touch with ease. It works like a charm and just like the official twrp recovery. No problems at all. Now everything is set : bootloader unlocked, rooted with latest binary supersu, custom twrp recovery installed. I also have the stock recovery img backup file, hence can switch back and forth between stock and custom recovery whenever required. No space issue on lemfo lem5 as it has 8gb rom. lastly only xposed installer is to be installed which is not much of a problem as they are available for lollipop with supported sdk and for which as of now I don't see the use of xposed installer right now, hence will install when required. If I am able to somehow flip the recovery screen then that's it! ?
Gautam_Gundap said:
I have got everything working in twrp recovery. The flip recovery is no more a problem now as with some practice now I am comfortably able to use this inverted twrp touch with ease. It works like a charm and just like the official twrp recovery. No problems at all. Now everything is set : bootloader unlocked, rooted with latest binary supersu, custom twrp recovery installed. I also have the stock recovery img backup file, hence can switch back and forth between stock and custom recovery whenever required. No space issue on lemfo lem5 as it has 8gb rom. lastly only xposed installer is to be installed which is not much of a problem as they are available for lollipop with supported sdk and for which as of now I don't see the use of xposed installer right now, hence will install when required. If I am able to somehow flip the recovery screen then that's it! ?
Click to expand...
Click to collapse
If your rom size is not sufficient enough for backup then you can create full rom backup on pc and can restore the same from pc when the need arises. There are software packages available for the same
geowolf1000 said:
I have not found solution
Same problem with kw88h
And all twrp apk from playstore does not recognize as twrp
Recovery
Flashify can make the job
Only commands from adb... for wipe.
There is not enough space to backup or restore and i think only root and flasify is all you need.
Click to expand...
Click to collapse
Gautam_Gundap said:
If your rom size is not sufficient enough for backup then you can create full rom backup on pc and can restore the same from pc when the need arises. There are software packages available for the same
Click to expand...
Click to collapse
I have with chainfire but never had any problem to recover
Thanks
Gautam_Gundap, fantastic work - You've beaten me to the punch as I had been messing with this device since yesterday (already fixed two bootloops I had induced myself -_- ) and I've been looking for a method for porting a TWRP img that wouldn't brick the LEM5.
Would you mind sharing the port? ..Despite the mirrored display/input issues you have so far, having any recovery method right now is very appealing to me considering the hell I had luckily sidestepped, and want to dig further into their stock images: if only to rebuild them with better icons for starters....
If not, can you just run me through your steps for full-backup, and your modification of TWRP for use with LEM5? I don't mind doing the legwork but would rather not walk this firepath alone!
(After 4 years, finally signed up and posted. Feels good to be here, guys! )
cassettesgoboom said:
Gautam_Gundap, fantastic work - You've beaten me to the punch as I had been messing with this device since yesterday (already fixed two bootloops I had induced myself -_- ) and I've been looking for a method for porting a TWRP img that wouldn't brick the LEM5.
Would you mind sharing the port? ..Despite the mirrored display/input issues you have so far, having any recovery method right now is very appealing to me considering the hell I had luckily sidestepped, and want to dig further into their stock images: if only to rebuild them with better icons for starters....
If not, can you just run me through your steps for full-backup, and your modification of TWRP for use with LEM5? I don't mind doing the legwork but would rather not walk this firepath alone!
(After 4 years, finally signed up and posted. Feels good to be here, guys! )
Click to expand...
Click to collapse
There are many advantages of twrp custom recovery, one of them being very fast full rom backup and even faster full rom restore and that too with compression, the pc whereas takes at least 10 times the time to do the same. full rom restore for me does it within 4mins and backup size of full compressed rom is only 1.64GB whereas the pc takes 7GB for the same backup. Needless to say about advantages of other features like customized wipe, flash image and zip files etc. Now for the procedure for porting twrp custom recovery is as follows
Download latest version of mtk extractor for PC. I tried all other methods, but only this one worked for me.
Download custom twrp recovery of blitz or i2 smartwatch which you will find in this forum.
You will require your stock recovery image file for this method. Your watch needs to be rooted to extract the same. Flashify app from playstore will do the job.
Connect watch to pc. Hope you know how to do this. rename stock recovery img to boot. Open mtk extractor and unpack this renamed file. You will find the unpacked files in mtk folder.
Cut these files and paste in a new folder stock recovery.
now rename the custom twrp recovery img you are going to port to boot.
Unpack it, the files will be placed in mtk folder.
Now copy kernel file from the stock recovery folder and paste it in the new unpacked files of ported twrp. PC Prompts replace - yes.
Now repack and you will get boot.img. Rename to recovery.img.
Flash this via fastboot or Flashify. Done. You have now successfully installed twrp recovery.
Note: In the mtk extractor software use the boot feature for all above steps.
If you encounter any problems post here and I will fix it.
To use pc for full rom backup and restore and many other features use cracked version of miracle box v2. 27A. Mtk Droid tools and SP flash tools do not support this watch, so don't waste time trying with it.
Xposed framework installed successfully!
Anyone need full power button menu for lemfo lem5 install advance power menu app from playstore. It works well. Once you long press the power button you get options for power off, reboot, download, recovery, UI restart , screen shot, soft reboot and safe mode reboot. Select floating mode from settings. looks and works nice on smart watch display
Gautam_Gundap said:
There are many advantages of twrp custom recovery, one of them being very fast full rom backup and even faster full rom restore and that too with compression, the pc whereas takes at least 10 times the time to do the same. full rom restore for me does it within 4mins and backup size of full compressed rom is only 1.64GB whereas the pc takes 7GB for the same backup. Needless to say about advantages of other features like customized wipe, flash image and zip files etc. Now for the procedure for porting twrp custom recovery is as follows
Download latest version of mtk extractor for PC. I tried all other methods, but only this one worked for me.
Download custom twrp recovery of blitz or i2 smartwatch which you will find in this forum.
You will require your stock recovery image file for this method. Your watch needs to be rooted to extract the same. Flashify app from playstore will do the job.
Connect watch to pc. Hope you know how to do this. rename stock recovery img to boot. Open mtk extractor and unpack this renamed file. You will find the unpacked files in mtk folder.
Cut these files and paste in a new folder stock recovery.
now rename the custom twrp recovery img you are going to port to boot.
Unpack it, the files will be placed in mtk folder.
Now copy kernel file from the stock recovery folder and paste it in the new unpacked files of ported twrp. PC Prompts replace - yes.
Now repack and you will get boot.img. Rename to recovery.img.
Flash this via fastboot or Flashify. Done. You have now successfully installed twrp recovery.
Note: In the mtk extractor software use the boot feature for all above steps.
If you encounter any problems post here and I will fix it.
Click to expand...
Click to collapse
Very cool - seems straightforward enough. I'll see if I can find something to fix up or workaround to get the rotation back while I'm at it. First thing's first is to give this a shot though. Need to get a windows machine so I'll get it going at work tomorrow!
Will update again soon. Thanks so much for the steps!
Hi guys.. root + twrp ok.. but there are Custom ROM with full smartwatch function (not only standalone)? Or the only one solution (partial solution) is M2D?
Well done! :laugh: I've configured Lem5 TWRP how u can see here:
https://forum.xda-developers.com/smartwatch/other-smartwatches/twrp-lemfo-lem-5-twrp-t3544569
I think/hope i've solved recovery flipped screen issue, because X5 TWRP haven't this problem.
X5 TWRP + Lem5 kernel = solution? I hope so!
If someone want try, please post the result. Thanx at all...!
Sent from my S7 Edge using XDA Labs
I'm trying to flash the recovery through fastboot and I'm getting:
C:\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (9676 KB)...
OKAY [ 0.366s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 0.383s
I tried rooting with Kingroot and it really bloated up my device. Factory reset still keeps Kingroot, so I kinda want to start over fresh with TWRP and a clean image. How do you flash TWRP on this watch?
---------- Post added at 02:53 PM ---------- Previous post was at 02:39 PM ----------
Update: I made sure OEM unlock was checked in developer settings and eventually was able to flash TWRP via Fastboot.
My watch is now bootlooping over and over again in TWRP, says:
"Done processing script file, renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP."
dimex said:
I'm trying to flash the recovery through fastboot and I'm getting:
C:\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (9676 KB)...
OKAY [ 0.366s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 0.383s
I tried rooting with Kingroot and it really bloated up my device. Factory reset still keeps Kingroot, so I kinda want to start over fresh with TWRP and a clean image. How do you flash TWRP on this watch?
---------- Post added at 02:53 PM ---------- Previous post was at 02:39 PM ----------
Update: I made sure OEM unlock was checked in developer settings and eventually was able to flash TWRP via Fastboot.
My watch is now bootlooping over and over again in TWRP, says:
"Done processing script file, renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP."
Click to expand...
Click to collapse
if your bootloader is locked, it will not allow you to flash twrp recovery via fastboot . Use SP FLASH TOOLS for this purpose. Once you flash recovery do not reboot to system. Reboot to recovery for the first time and then it should be ok. Else root your watch first and flash recovery using Flashify. This method will also do the job.
Gautam_Gundap said:
if your bootloader is locked, it will not allow you to flash twrp recovery. Use SP FLASH TOOLS for this purpose. Once you flash recovery do not reboot to system. Reboot to recovery for the first time and then it should be ok. Else root your watch first and flash recovery using Flashify. This method will also do the job.
Click to expand...
Click to collapse
Did you read my update? It's bootlooping TWRP.
dimex said:
Did you read my update? It's bootlooping TWRP.
Click to expand...
Click to collapse
If you are unable to reboot to system, then you need to re flash complete stock rom. You can do this using cracked miracle software. I have already uploaded full stock rom for flashing via cracked miracle box software except data/userdata partition . you can find it in one of the lemfo lem5 threads here. After re flash you can use the steps explained earlier to flash twrp recovery
I just released a fully working TWRP 3.0.2 recovery for X5+ and LEM5 here:
http://roundandroidwatches.proboards.com/thread/1016/twrp-recovery-port-x5-lem5
Don't forget to read all the instructions.