Related
Hi,
what I've done so far :
rooted my phone (Doomlord's tool)
updated ROM .42 (via x10flashtool.exe - which is in fact GUI for fast boot as I understood)
rooted again
wanted to go to FXP045, but stuck with flash - system response was that the phone needs to be rooted first (+some issues with drivers)
refreshed ROM via Companion (.42)
rooted again
...and still same issue during flash (with -w option)
either failed bcz not rooted (not true)
or stops at sending boot (nothing happens) and then fail because i disconnect device "status read faled(too many links)"
Anyone able to advise if I missed sthg?
thx, M.
same for me on st15i.
gvuzd said:
Hi,
what I've done so far :
rooted my phone (Doomlord's tool)
updated ROM .42 (via x10flashtool.exe - which is in fact GUI for fast boot as I understood)
rooted again
wanted to go to FXP045, but stuck with flash - system response was that the phone needs to be rooted first (+some issues with drivers)
refreshed ROM via Companion (.42)
rooted again
...and still same issue during flash (with -w option)
either failed bcz not rooted (not true)
or stops at sending boot (nothing happens) and then fail because i disconnect device "status read faled(too many links)"
Anyone able to advise if I missed sthg?
thx, M.
Click to expand...
Click to collapse
unlock bootloader and flash phone....
FreeXperia PROJECT need unlocked bootloader
---------- Post added at 02:32 PM ---------- Previous post was at 02:29 PM ----------
alexderb said:
same for me on st15i.
Click to expand...
Click to collapse
your bootloader is locked too...
hi everyone
last week i was root and install recovery on my z2 (with 4.4.2 bulid 314 rom)
last night i backup TA partition and open the bootloader to have multi rom function.
after successfully open the bootloader everything on phone deleted but still rooted and have SuperS & NDR Utils ,
i want to flash eXistenZ v4.5.0 for first rom but i can`t go to recovery
after showing sony logo no matter how much i press up or down volume it is not going into recovery
when i doing root and install recovery again, i got that massege says recovery files exists
this image attach from my log when install recovery again:
Have you tried rebooting from the NDRutils app? I find that easier on my Z2
---------- Post added at 09:48 PM ---------- Previous post was at 09:47 PM ----------
I just read through that more easily, you are trying to install a very old version of XZDualRecovery, download 2.8.3 installer from [NUT]'s website
My XT1521 is stuck at Fastboot, after trying to install last night's OTA update. The Bootloader Logs screen says "failed to validate system image" followed by "Boot up failed".
All of my important data is backed up. I don't care about preserving any data on the phone; I just want to get it working again.
The attached photo shows what I can see.
After connecting the USB cable, "fastboot devices" returns TA38502SB6 fastboot
Is this something I can fix myself, with appropriate software? Will I need to approach Motorola? Is it beyond help?
Flash the twrp recovery using fastboot, install a rom and the squid kernel. The Rom is pretty stable now..
---------- Post added at 09:05 PM ---------- Previous post was at 08:33 PM ----------
Or else you can download the stock Rom
http://motofirmware.center/files/fi...2_lxi2250-531_cid7_subsidy-default_cfcxmlzip/
And the guide is : http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3044936
rushabshah32 said:
Flash the twrp recovery using fastboot, install a rom and the squid kernel. The Rom is pretty stable now..
---------- Post added at 09:05 PM ---------- Previous post was at 08:33 PM ----------
Or else you can download the stock Rom
http://motofirmware.center/files/fi...2_lxi2250-531_cid7_subsidy-default_cfcxmlzip/
And the guide is : http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3044936
Click to expand...
Click to collapse
Those look very useful, thank you. Gives me something to do this evening!
Loganberry said:
My XT1521 is stuck at Fastboot, after trying to install last night's OTA update.
Click to expand...
Click to collapse
Was it the stock 5.1 update???
Software status: modified
How did you get the OTA update and what did you do previously ?
Recovery log says you had a modified software. So there was no hope to apply patch properly. And it bricked your system
rushabshah32 said:
Was it the stock 5.1 update???
Click to expand...
Click to collapse
Not sure. It was only around 20-30MB or so; can't remember the exact size.
PsyClip-R said:
How did you get the OTA update and what did you do previously ?
Recovery log says you had a modified software. So there was no hope to apply patch properly. And it bricked your system
Click to expand...
Click to collapse
OTA update was advertised through the normal Motorola OTA feature. All I did was to tap on "Yes, I'm in" to accept it when it was offered.
If my phone's ruined, then it's ruined. Irritating, but not the end of the world; a new Moto E2 isn't expensive. I'd just prefer not to have to buy a new one if there's any hope of resurrecting this one. As I indicated in my first post, the important data is safe; I just want a working phone again.
Edit: just re-read your question; realised I might have misunderstood part of it.
My phone had previously been rooted; before accepting the OTA update I went through the steps to unroot the phone before taking the OTA update; looks like something went wrong somewhere along the way.
Loganberry said:
My XT1521 is stuck at Fastboot, after trying to install last night's OTA update. The Bootloader Logs screen says "failed to validate system image" followed by "Boot up failed".
All of my important data is backed up. I don't care about preserving any data on the phone; I just want to get it working again.
The attached photo shows what I can see.
After connecting the USB cable, "fastboot devices" returns TA38502SB6 fastboot
Is this something I can fix myself, with appropriate software? Will I need to approach Motorola? Is it beyond help?
Click to expand...
Click to collapse
i got the update yesterday too on my X1521 but it was working fine.after immediate reboot it was lagging like hell but rebooting solved it
Guys don't panic. What I would do is unlock the bootloader and flash TWRP, after that just download any custom ROM and TWRP lets you get on MTP so you can transfer the ROM to the internal storage.
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
Also there's plenty of stock ROMS out there like SuperR's Stock Roms
I have a similar issue, I just accepted the OTA update from Motorola on my XT1511(otus), It was stock/rooted. The phone went into boot loop. Tried these things to remedy
1) tried booting to TWRP from fastboot. I'd get the TWRP splash screen, but no functionality
2)flashed TWRP - now have functioning recovery, but during rom flash get "error, cant mount /data
3)fastboot -w successfully wiped data, but couldn't format partition, still raw
4)From twrp "mount" screen couldn't check the box for mounting data
5)from twrp wipe>format data was able to format the partition
6) I've flashed a couple of twrp recovery images, and a couple of different roms, I don't get error messages, but now when the phone is powered on it always boots into recovery, even when reboot>system or reboot power off is selected. I can still access fast boot.
Any suggestions? I'm going to try returning to stock at this point'
Update: Downloaded stock recovery here:
http://forum.xda-developers.com/devdb/project/dl/?id=11977
Installed with fastboot, phone boots properly now!
I downgraded my Fire HD 6 to 4.5.3, rooted it using Kingroot and installed TWRP using Flashify (couldn't flash TWRP because the bootloader/fastboot was locked ("Failed:...locked hw")) . After rooting, I blocked OTA using the adb command lines.
Then I updated to the latest Fire OS using http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449. After step 2A (flash the respective Amazon ROM 4.5.x update (the latest one? [so I tried 5.5.4)), I thought I was home free. But upon rebooting, I found root was gone. Not sure what I missed and when I missed it but that's not the point now. [Upon much reflection, it was probably not issuing the block OTA commands again, duh.]
Now, I have no recovery; TWRP is gone. Stock recovery is gone. I can't flash TWRP using fastboot because bootloader is still locked. Flashify needs root to work. Help greatly appreciated.
I tried to unbrick (even though it's not bricked but I'm at a loss as to how to get a recovery back on it) using Imma Wake's Linux but it just hangs on ./reader.sh . I'm really at a loss but it's not for not trying. I've got to reroot this thing cuz I hate hate hate amazon. Can't do it without a recovery. Well, really, is there no one who can help me?
bleak93 said:
I tried to unbrick (even though it's not bricked but I'm at a loss as to how to get a recovery back on it) using Imma Wake's Linux but it just hangs on ./reader.sh . I'm really at a loss but it's not for not trying. I've got to reroot this thing cuz I hate hate hate amazon. Can't do it without a recovery. Well, really, is there no one who can help me?
Click to expand...
Click to collapse
Why don't you try unlocking the bootloader so you can flash TWRP, bleak?
bleak93 said:
Why don't you try unlocking the bootloader so you can flash TWRP, bleak?
Click to expand...
Click to collapse
Well, that's a damn good idea, bleak. I wish I thought of it.
So I tried using the python/cublock.py method. I'm on Windows 7 so I installed Python. I get the two codes, run cublock.py [XXX] [SSS] and I get a file called "unlock.img" but after that, it hangs when I run adb reboot bootloader / fastboot -i 0x1949 flash unlock unlock.signed. I tried fastboot -i 0x1949 flash unlock unlock.img cuz that's what the file is called but it just says "[WAITING FOR A DEVICE]" or something like that after both of those commands. I think it doesn't reboot into the bootloader after adb reboot bootloader ; it shuts down because there are no signs of it in the device manager.
bleak93 said:
Well, that's a damn good idea, bleak. I wish I thought of it.
So I tried using the python/cublock.py method. I'm on Windows 7 so I installed Python. I get the two codes, run cublock.py [XXX] [SSS] and I get a file called "unlock.img" but after that, it hangs when I run adb reboot bootloader / fastboot -i 0x1949 flash unlock unlock.signed. I tried fastboot -i 0x1949 flash unlock unlock.img cuz that's what the file is called but it just says "[WAITING FOR A DEVICE]" or something like that after both of those commands. I think it doesn't reboot into the bootloader after adb reboot bootloader ; it shuts down because there are no signs of it in the device manager.
Click to expand...
Click to collapse
Did you just reply to yourself? ???
I'm stuck in the same crappy situation
I'm in this situation too...
I'm no expert, but I think I know what happened. For whatever reason, TWRP doesn't play nice with 5.x bootloaders. 4.x is fine but 5.x is a no-go. I'm assuming that when you flashed TWRP you overwrote your stock recovery. This would have been fine, but the wording in the tutorial you were following is a bit misleading. When he said flash the 4.5.x update (the latest one) he meant the latest 4.5.x (eg 4.5.3, 4.5.4, etc) but not anything above 4.5.whatever. When you flashed 5.5.4 you updated the bootloaders to 5.x so TWRP no longer works and you've lost your stock recovery. Not sure what happened to your root though. It's possible it's still there and there's just not a manager app installed? Try installing Kingroot again and using its root check function to see. If it really is gone, then I have no idea how to fix it.
@bibikalka any help please?
---------- Post added at 11:55 PM ---------- Previous post was at 11:49 PM ----------
Killa8;72047553 [user=6680544 said:
@bibikalka[/user] any help please?
Click to expand...
Click to collapse
@powerpoint45
similar situation
I havea fire hd 6 (4th generation) running 5.3.1.0 no recovery but I do have root via kingroot so I have flashify and rashr. I have tried flashing TWRP using flashify and rashr, and no error but it wont boot to twrp. Any way to flash stock recovery or is there another option for 5.3.1.0 as far as recover??
bleak93 said:
I downgraded my Fire HD 6 to 4.5.3, rooted it using Kingroot and installed TWRP using Flashify (couldn't flash TWRP because the bootloader/fastboot was locked ("Failed:...locked hw")) . After rooting, I blocked OTA using the adb command lines.
Then I updated to the latest Fire OS using http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449. After step 2A (flash the respective Amazon ROM 4.5.x update (the latest one? [so I tried 5.5.4)), I thought I was home free. But upon rebooting, I found root was gone. Not sure what I missed and when I missed it but that's not the point now. [Upon much reflection, it was probably not issuing the block OTA commands again, duh.]
Now, I have no recovery; TWRP is gone. Stock recovery is gone. I can't flash TWRP using fastboot because bootloader is still locked. Flashify needs root to work. Help greatly appreciated.
Click to expand...
Click to collapse
Hi I am having the same exact problem and I would just like to know if you have found a fix for this problem yet. I'm stuck on cm11 rom which has a bunch of bugs and I would like to go back to fire os but I have no root and can boot into fast boot or recovery. Any help would be appreciated. Thanks.
---------- Post added at 02:10 AM ---------- Previous post was at 02:08 AM ----------
Killa8 said:
I'm stuck in the same crappy situation
Click to expand...
Click to collapse
Hi have you found a fix for this situation yet I'm stuck in it too. Tried to re flash the device using powerpoints tutorial but gets stuck on reader.sh. Any help would be appreciated thanks.
---------- Post added at 02:11 AM ---------- Previous post was at 02:10 AM ----------
Killa8 said:
I'm stuck in the same crappy situation
Click to expand...
Click to collapse
Hi have you found a fix for this situation yet I'm stuck in it too. Tried to re flash the device using powerpoints tutorial but gets stuck on reader.sh. Any help would be appreciated thanks.
kyle12345109876 said:
Hi I am having the same exact problem and I would just like to know if you have found a fix for this problem yet. I'm stuck on cm11 rom which has a bunch of bugs and I would like to go back to fire os but I have no root and can boot into fast boot or recovery. Any help would be appreciated. Thanks.
---------- Post added at 02:10 AM ---------- Previous post was at 02:08 AM ----------
Hi have you found a fix for this situation yet I'm stuck in it too. Tried to re flash the device using powerpoints tutorial but gets stuck on reader.sh. Any help would be appreciated thanks.
---------- Post added at 02:11 AM ---------- Previous post was at 02:10 AM ----------
Hi have you found a fix for this situation yet I'm stuck in it too. Tried to re flash the device using powerpoints tutorial but gets stuck on reader.sh. Any help would be appreciated thanks.
Click to expand...
Click to collapse
Just so I have a clear understanding: you're running cm11 but you have lost root and recovery. Can you get into fastboot? I think you wrote you can boot into fastboot and recovery.
Kindle fire no twrp
Drunkpilot said:
Just so I have a clear understanding: you're running cm11 but you have lost root and recovery. Can you get into fastboot? I think you wrote you can boot into fastboot and recovery.
Click to expand...
Click to collapse
Ok so yes I am on cm 11 and i cannot boot into recovery but I can boot into fast boot using the adb commands so does this mean I can flash twrp using fast boot?
Also I have used kingo root and have now gained root access.
kyle12345109876 said:
Ok so yes I am on cm 11 and i cannot boot into recovery but I can boot into fast boot using the adb commands so does this mean I can flash twrp using fast boot?
Also I have used kingo root and have now gained root access.
Click to expand...
Click to collapse
Good deal on the root. Yes, you should be able to flash TWRP using fastboot. You need to have the fastboot drivers installed and rename the recovery image to recovery.img. I believe the command is: fastboot flash recovery recovery.img. now that you are rooted though, you can use Flashify to flash TWRP. Flashify would be the easiest and quickest solution. Flashfire might be another option, but I don't know if it would recognize the Kingo root.
Drunkpilot said:
Good deal on the root. Yes, you should be able to flash TWRP using fastboot. You need to have the fastboot drivers installed and rename the recovery image to recovery.img. I believe the command is: fastboot flash recovery recovery.img. now that you are rooted though, you can use Flashify to flash TWRP. Flashify would be the easiest and quickest solution. Flashfire might be another option, but I don't know if it would recognize the Kingo root.
Click to expand...
Click to collapse
Thanks I tried flash fire and it didn't regonize the kingo root, also tried flashify and it just rebooted the tablet and didn't work. So I will try with the fast boot.
---------- Post added at 06:17 PM ---------- Previous post was at 05:47 PM ----------
Drunkpilot said:
Good deal on the root. Yes, you should be able to flash TWRP using fastboot. You need to have the fastboot drivers installed and rename the recovery image to recovery.img. I believe the command is: fastboot flash recovery recovery.img. now that you are rooted though, you can use Flashify to flash TWRP. Flashify would be the easiest and quickest solution. Flashfire might be another option, but I don't know if it would recognize the Kingo root.
Click to expand...
Click to collapse
Right now I remember I tried to flash twrp using fast boot and it gave me an error saying :FAILED (remote: flashing not allowed for locked hw).
Does this mean my bootloader is somehow locked? If so how do I unlock it?
kyle12345109876 said:
Thanks I tried flash fire and it didn't regonize the kingo root, also tried flashify and it just rebooted the tablet and didn't work. So I will try with the fast boot.
Click to expand...
Click to collapse
Maybe try flashing a chainfire SuperSU.zip through flashing so that you can replace the kingo SU, then use the SuperSU app to clean up some of the kingo root remnants and have something recognizable when flashing TWRP. I have been doing a lot of Fire flashing work lately as I just used my warranty for a brick I replaced. Then, within a couple hours bricked the replacement due to me not turning off the OTA sufficiently while running 4.5.2 and used the Powerpoint45 technique (which worked brilliantly on the new Fire) and then stupidly lost root and had to revert back to 4.5.3. Needless to say, I have been reading and executing a lot of different actions. Currently, I'm on 4.5.3 with TWRP and finally getting the Google Play store to work.
Drunkpilot said:
Good deal on the root. Yes, you should be able to flash TWRP using fastboot. You need to have the fastboot drivers installed and rename the recovery image to recovery.img. I believe the command is: fastboot flash recovery recovery.img. now that you are rooted though, you can use Flashify to flash TWRP. Flashify would be the easiest and quickest solution. Flashfire might be another option, but I don't know if it would recognize the Kingo root.
Click to expand...
Click to collapse
Does it help if I say before all this happened I had installed fire os 5 from twrp but i didn't boot it right after I cleared cache and dalvik and then flashed cm11. When I then booted the cm11 the twrp dissapered. Does this mean that I would have to flash the fire os 4 bootloader or something since fire os 5 can't doesn't work with twrp cause I'm sooo lost right now and would just love to get to any stable fire os.
kyle12345109876 said:
Does it help if I say before all this happened I had installed fire os 5 from twrp but i didn't boot it right after I cleared cache and dalvik and then flashed cm11. When I then booted the cm11 the twrp dissapered. Does this mean that I would have to flash the fire os 4 bootloader or something since fire os 5 can't doesn't work with twrp cause I'm sooo lost right now and would just love to get to any stable fire os.
Click to expand...
Click to collapse
Look at the TWRP thread for our Fire. I think it has the dd commands to install the recovery now that you are rooted once again. It sounds like you didn't install the 5.x.x uboot and recovery zip along with the update and lost recovery. I think you said you used the unbrick method and you just hung on the reading.sh. that method would give you TWRP and nothing else, but from there you could them flash the 5.x files in the thread. I used Flashify to get TWRP yesterday, and I think I had kingroot at the time. I know the is a zip only containing the 4.5.3 bootloader's, but I can't remember where I saw it right now, and if it would work or not. I'm still in learning more as well.
Drunkpilot said:
Look at the TWRP thread for our Fire. I think it has the dd commands to install the recovery now that you are rooted once again. It sounds like you didn't install the 5.x.x uboot and recovery zip along with the update and lost recovery. I think you said you used the unbrick method and you just hung on the reading.sh. that method would give you TWRP and nothing else, but from there you could them flash the 5.x files in the thread. I used Flashify to get TWRP yesterday, and I think I had kingroot at the time. I know the is a zip only containing the 4.5.3 bootloader's, but I can't remember where I saw it right now, and if it would work or not. I'm still in learning more as well.
Click to expand...
Click to collapse
Hi thanks for the help turns out I managed to brick the device once again so I just used powerpoints video to unbrick and now I have twrp again. Question though I tried to install fire os 4.5.3 in twrp but it give me an error sayingI have the Omni Ariel not the full Ariel so I can't flash the file. Anyone know how to fix it?
kyle12345109876 said:
Does it help if I say before all this happened I had installed fire os 5 from twrp but i didn't boot it right after I cleared cache and dalvik and then flashed cm11. When I then booted the cm11 the twrp dissapered. Does this mean that I would have to flash the fire os 4 bootloader or something since fire os 5 can't doesn't work with twrp cause I'm sooo lost right now and would just love to get to any stable fire os.
Click to expand...
Click to collapse
Hi the process should be fairly simple. Use the tutorial from the unbricking thread to get your device back to normal. It will be long but it works unless you have fire os 5(like me). Otherwise there's literally no other option you can use
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
kyle12345109876 said:
Hi thanks for the help turns out I managed to brick the device once again so I just used powerpoints video to unbrick and now I have twrp again. Question though I tried to install fire os 4.5.3 in twrp but it give me an error sayingI have the Omni Ariel not the full Ariel so I can't flash the file. Anyone know how to fix it?
Click to expand...
Click to collapse
Did you download the correct file? Check again
dear developers i hv lyf f1 ls-5505 device i want to root it i hv tried king root, kingo root,i root,srs root , one click root, fram Root but nothing working.please help me i want to root it any how.it has msm8952 processor 3gb ram 32 internal.
raj2k8 said:
dear developers i hv lyf f1 ls-5505 device i want to root it i hv tried king root, kingo root,i root,srs root , one click root, fram Root but nothing working.please help me i want to root it any how.it has msm8952 processor 3gb ram 32 internal.
Click to expand...
Click to collapse
Same problem with me...and also when i try to unlock bootloader or do anything with fast boot it returns {remote:unknown command}.
also i want a recovery for that if any of the members can give please...
Jackbolt said:
Same problem with me...and also when i try to unlock bootloader or do anything with fast boot it returns {remote:unknown command}.
also i want a recovery for that if any of the members can give please...
Click to expand...
Click to collapse
i hv also tried fast boot but same error even i hv tried contacting lyf people but they are noob
lyf water f1
yes fastboot is not working even after turning on oem unlocking in the developer settings
---------- Post added at 01:59 PM ---------- Previous post was at 01:57 PM ----------
raj2k8 said:
i hv also tried fast boot but same error even i hv tried contacting lyf people but they are noob
Click to expand...
Click to collapse
If u find anything then please send the method to me also..
From adb cosole this command "adb reboot-bootloader" can probably take it to fastboot mode.
---------- Post added at 12:47 PM ---------- Previous post was at 12:46 PM ----------
---------- Post added at 12:50 PM ---------- Previous post was at 12:47 PM ----------
But I have been searching for almost a week to get a back up of the stock rom,get root access,get any custom recovery (TWRP if possible) ,still have not found any solution,do you have any?
---------- Post added at 12:51 PM ---------- Previous post was at 12:50 PM ----------
Tried iroot,kingo root,king root,towel root every single one of them failed.
---------- Post added at 12:53 PM ---------- Previous post was at 12:51 PM ----------
Yes no help for weeks.
Yes no solution for months
"Z Camera" app is taking best pictures and best videos in LYF F1,I have personally tested.
CF-Auto-Root can root many devices,I have found a Samsung device named "Samsung Galaxy C5" which is similar to LYF F1 in that its Platform is MSM8952 , CPU is Octa-core (4x1.5 GHz Cortex-A53 & 4x1.2 GHz Cortex-A53) and GPU is Adreno 405.If any one can take the risk then he/she can try this link
https://download.chainfire.eu/1031/CF-Root/CF-Auto-Root/CF-Auto-Root-c5ltechn-c5ltezh-smc5000.zip
I asked the customer care executives to unlock the bootloader of this phone through this email "[email protected]",they advised me to go to the nearest service centre to unlock it.They said
"Thank you for writing to us.
I understand you wish to unlock the bootloader of your handset.
However I wish to inform you that, to unlock the bootloader kindly visit the service centre.
Note: Rooting or booting of LYF handset will void the warranty.
If you are unaware of the nearest service centre, I request you to help us out with the location so that we can guide you to the service centre.
Be assured, our device specialist at the service centre will assist you to get the issue resolved at the earliest.
Note: Please carry the Invoice of your handset while visiting the service centre.
If you have any further queries, please contact us on 1800-890-9999 or write to us on [email protected].
I appreciate your time and patience.
Thank You
Neha Mishra
Team LYF"
i hv tried service center...but they dont know anything about it
Im trying to port custom recovery.
I found a device moto g4 plus with exact chipset,specifications and got custom recovery of that model...so im going to port it to lyf water f1..lets see.
Good news for all the users of LYF F1 who want to have twrp and root access.
I found the stock rom at link "http://www.smartfirmwares.com/forum1/index.php?topic=189.0"
I extracted the stock rom and got the stock recovery,then I got the twrp recovery of ZTE Axon 7 Mini.
I ported the twrp by replacing only the zImage from the stock to the twrp,and kept the ramdisk the same in twrp.
It booted up well but I got a error that twrp could not mount any partition except the recovery.
I then got the twrp of Moto G4 Plus,but the twrp did not have the ramdisk,it only contains zImage,so I could not port it.
I then got the twrp of Samsung Galaxy C5 and ported it in the same way,but it put the phone into recovery bootloop,phone was booting into twrp,then switching off,then again booting to twrp,at one moment when phone was switched off for one second,I flashed again the previous working recovery.
I then ported the twrp recovery of ZTE Axon Max but it gave the same error that it could not mount any partition except the recovery.
Then I ported the twrp recovery of ZTE Nubia Z11 Mini and this one was successfull without any error,but the recovery was in chinese.I can not remember the whole thing but the first window appeared in front,I touched the lower right conrer and changed the language to english,since then everything is in english.The link of that recovery is "https://drive.google.com/open?id=0B2iZIwRNj3bpaEl3dWR1eXRsalk" and password is "Created-by-Tarasantan"
Now How did I flashed the twrp,I downloaded and extracted the stock rom,then I found a "_qcMUP.zip" within the zip "LYF F1 LS-5505 TOOL & DRIVERS.zip",then extracted the zip _qcMUP.zip,there in the support folder I found some windows softwares,I ran all of them to install the drivers and neccessary files.
Then in the "LYF F1 LS-5505 PC SW VER 01_06 By Gsm_F!rmwares_Tm" folder I replaced the stock "recovery.img" with the twrp "recovery.img".And then I ran the "qcMUP.exe" in the _qcMUP folder which I previously extracted.
Now I clicked the do button in the upper right corner of "qcMUP.exe",then clicked upgrade,then I selected the "LYF F1 LS-5505 PC SW VER 01_06 By Gsm_F!rmwares_Tm" folder.
Now I switched off the phone,then I pressed and hold volume up and down at the same time,and pluged the phone into the computer and the flashing started on qcMUP.exe window with a light blue bar filling up with a deep blue colour as the flashing was going on.
This will clear all the apps and data you previously have had in your internal memory.So you can back up all the installed app with es filexplorer,or super backup,and all the contacts and smses with super backup,then you must move all the backed up things and other neccessary things to the sd card.At the end put the latest supersu.zip in your sd card.
The next part is very important,when flashing is passed,you will unplug the phone from the computer,then press and hold the power and the volume up at the same time.You will be booted up into twrp then somehow change the language to english from chinese,then flash the supersu.zip from your sd card,if you do not boot into twrp and flash the supersu.zip then whenever you will boot into the system,the twrp recovery will be replaced with the stock recovery,when you flash the supersu.zip,it patches the boot.img so that it does not replace the twrp recovery with the stock.
Alternatively
you can use the following method.I have not tested this method,but this should work.In this method you just need to download this file "TWRP For LYF F1.7z",from https://drive.google.com/open?id=0B2iZIwRNj3bpanRsaUM0OEdYV3c ,password is Created-By-Tarasantan .This recovery is made for exactly LS-5505,that means ro.product.device is LS-5505 ,ro.product.locale is en-IN and other properties are also changed for LS-5505.
Download and Extract the "TWRP For LYF F1.7z" file,then install the given drivers,then run the "qcMUP.exe".
Now Click the do button in the upper right corner of "qcMUP.exe" window,then click upgrade,then select the "LYF F1 LS-5505 TWRP 3.0.2" folder.
Now switch off the phone,then press and hold volume up and down at the same time,and plug the phone into the computer and the flashing should start on qcMUP.exe window with a light blue bar filling up with a deep blue colour as the flashing is going on.
This will not clear any apps and data that you previously have had in your internal memory.So you do not need to back up anything.But you need to put a supersu.zip in your sd card.
The next part is very important,when flashing is passed,unplug the phone from the computer,then press and hold the power and the volume up at the same time.Your phone should be booted up into twrp,then flash the supersu.zip from your sd card,if you do not boot your phone into twrp and flash the supersu.zip then whenever you will boot into the system,the twrp recovery will be replaced with the stock recovery,when you flash the supersu.zip,it patches the boot.img so that the boot.img does not replace the twrp recovery with the stock one.
One help
That firmware not downloading bro...do you have direct link.
---------- Post added at 05:43 AM ---------- Previous post was at 05:39 AM ----------
https://drive.google.com/uc?id=0B2rMyFgEtXoKa1pfT29PeTQtU2c&export=download
You guys can try this code to unlock bootloader.try to type fastboot OEM unlock-go then see what happens I unlocked my Lyf water 8 with it hope this helps.if it don't work with this code then try again with fastboot OEM unlock only don't type go then see
all_tricks_zone said:
That firmware not downloading bro...do you have direct link.
---------- Post added at 05:43 AM ---------- Previous post was at 05:39 AM ----------
https://drive.google.com/uc?id=0B2rMyFgEtXoKa1pfT29PeTQtU2c&export=download
Click to expand...
Click to collapse
The link you mentioned I have not provided that,and I checked the link,the download is starting immediately.
Link of a image of the window which will come when you first time boot into twrp
https://drive.google.com/open?id=0B2iZIwRNj3bpbTgySjdfRFZKUzg
Tarasantan said:
Good news for all the users of LYF F1 who want to have twrp and root access.
I found the stock rom at link "http://www.smartfirmwares.com/forum1/index.php?topic=189.0"
I extracted the stock rom and got the stock recovery,then I got the twrp recovery of ZTE Axon 7 Mini.
I ported the twrp by replacing only the zImage from the stock to the twrp,and kept the ramdisk the same in twrp.
It booted up well but I got a error that twrp could not mount any partition except the recovery.
I then got the twrp of Moto G4 Plus,but the twrp did not have the ramdisk,it only contains zImage,so I could not port it.
I then got the twrp of Samsung Galaxy C5 and ported it in the same way,but it put the phone into recovery bootloop,phone was booting into twrp,then switching off,then again booting to twrp,at one moment when phone was switched off for one second,I flashed again the previous working recovery.
I then ported the twrp recovery of ZTE Axon Max but it gave the same error that it could not mount any partition except the recovery.
Then I ported the twrp recovery of ZTE Nubia Z11 Mini and this one was successfull without any error,but the recovery was in chinese.I can not remember the whole thing but the first window appeared in front,I touched the lower right conrer and changed the language to english,since then everything is in english.The link of that recovery is "https://drive.google.com/open?id=0B2iZIwRNj3bpaEl3dWR1eXRsalk" and password is "Created-by-Tarasantan"
Now How did I flashed the twrp,I downloaded and extracted the stock rom,then I found a "_qcMUP.zip" within the zip "LYF F1 LS-5505 TOOL & DRIVERS.zip",then extracted the zip _qcMUP.zip,there in the support folder I found some windows softwares,I ran all of them to install the drivers and neccessary files.
Then in the "LYF F1 LS-5505 PC SW VER 01_06 By Gsm_F!rmwares_Tm" folder I replaced the stock "recovery.img" with the twrp "recovery.img".And then I ran the "qcMUP.exe" in the _qcMUP folder which I previously extracted.
Now I clicked the do button in the upper right corner of "qcMUP.exe",then clicked upgrade,then I selected the "LYF F1 LS-5505 PC SW VER 01_06 By Gsm_F!rmwares_Tm" folder.
Now I switched off the phone,then I pressed and hold volume up and down at the same time,and pluged the phone into the computer and the flashing started on qcMUP.exe window with a light blue bar filling up with a deep blue colour as the flashing was going on.
This will clear all the apps and data you previously have had in your internal memory.So you can back up all the installed app with es filexplorer,or super backup,and all the contacts and smses with super backup,then you must move all the backed up things and other neccessary things to the sd card.At the end put the latest supersu.zip in your sd card.
The next part is very important,when flashing is passed,you will unplug the phone from the computer,then press and hold the power and the volume up at the same time.You will be booted up into twrp then somehow change the language to english from chinese,then flash the supersu.zip from your sd card,if you do not boot into twrp and flash the supersu.zip then whenever you will boot into the system,the twrp recovery will be replaced with the stock recovery,when you flash the supersu.zip,it patches the boot.img so that it does not replace the twrp recovery with the stock.
This is the end of the post.Good Bye.
Click to expand...
Click to collapse
Its working...yeepee
Lyf is indian mobile it is not internation you will find some expert in this forum which have custom rom and rooting detail but they dont share publically this i dont know why. In one of my post or comment I come across on senior who ask me to contact on his email you go throght my post comment find that senior.
Can't mount system as writable on LYF water F1
Please help me.
I can't mount my system as writable on lyf water F1 after rooting by above process.
I did flash the firmware by replacing recovery and then I flashed SuperSU 2.82.zip but even if my phone is rooted I can't mount my system as writable by any app on play store or commands in terminal emulator.
Please reply some one.