Related
So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
nvertigo said:
So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
Click to expand...
Click to collapse
As far as I can figure, the only way would to use an app to backup the data, flash back to factory, re-root and restore the data. The OTA update will remove root access. I would do a backup with CWM first if possible.
nvertigo said:
So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
Click to expand...
Click to collapse
if you know what you actually changed with root permissions then you can just flash stock recovery onto the phone then remove all things root and put everything back to normal stock (like unfreezing things out of tibu or whatever) then take the ota. if you are not sure what you changed, you can flash recovery and system then take the ota (assuming you didn't flash new kernals or anything else major).
And if you just want to keep data then you can flash stock ota with rsdlite and remove the two entries that erase data and cache in the xml file. Then take the ota. or flash the fxz and remove the same data erasing entries in the xml
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Schaweet said:
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
robwege said:
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
Click to expand...
Click to collapse
This is what I did.
1. Download 4.4 stock files from Motorola (you need to request access and they will email you the link)
2. Extract recovery.img and system.img from the stock image and place them in your platform tools folder ( or where fastboot and adb are located)
3. Update your SDK if it is out of date.
4. Download and put mfastboot in your platform tools folder (or where fastboot and adb are within your sdk directory)
5. Boot phone into fastboot mode
6. open a command prompt and change directory to your platform-tools folder and type the following (7 & 8)
7. fastboot flash recovery recovery.img
8. mfastboot flash system system.img
9. Reboot
10. Accept and install OTA
11. Reboot into fastboot mode
12. Reflash TWRP and root phone.
13. Reboot
14. Open Xposed and reinstall framework
15. Reboot
You would be good to go at that point. You would still need to reinstall your logo as it would be reset
If you already unlocked your phone and didn't change anything, you shouldn't have much trouble with the commands
Schaweet said:
This is what I did.
1. Download 4.4 stock files from Motorola (you need to request access and they will email you the link)
2. Extract recovery.img and system.img from the stock image and place them in your platform tools folder ( or where fastboot and adb are located)
3. Update your SDK if it is out of date.
4. Download and put mfastboot in your platform tools folder (or where fastboot and adb are within your sdk directory)
5. Boot phone into fastboot mode
6. open a command prompt and change directory to your platform-tools folder and type the following (7 & 8)
7. fastboot flash recovery recovery.img
8. mfastboot flash system system.img
9. Reboot
10. Accept and install OTA
11. Reboot into fastboot mode
12. Reflash TWRP and root phone.
13. Reboot
14. Open Xposed and reinstall framework
15. Reboot
You would be good to go at that point. You would still need to reinstall your logo as it would be reset
If you already unlocked your phone and didn't change anything, you shouldn't have much trouble with the commands
Click to expand...
Click to collapse
Thank you for your help. The only things I changed were and boot logo and xposed. I also freezer some apps but that is an easy fix. You di this on a vzw Dev edition as well?
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
Click to expand...
Click to collapse
robwege said:
Thank you for your help. The only things I changed were and boot logo and xposed. I also freezer some apps but that is an easy fix. You di this on a vzw Dev edition as well?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you froze the OTA application, you need to unfreeze that first as you won't have root until after you take the OTA and then reinstall TWRP.
I have a VZW DE as well.
I'm not sure how the changed boot animation will affect the OTA.
Your safest bet is to just follow the process I wrote to ensure the OTA doesn't fail and create other problems. It really only takes like 5 minutes. It leaves your data intact, so you won't have to set it up again. It also leaves the Xposed app on your phone and you just need to open it and install it. All your modules will still be there and will work as they did before after a reboot.
Schaweet said:
If you froze the OTA application, you need to unfreeze that first as you won't have root until after you take the OTA and then reinstall TWRP.
I have a VZW DE as well.
I'm not sure how the changed boot animation will affect the OTA.
Your safest bet is to just follow the process I wrote to ensure the OTA doesn't fail and create other problems. It really only takes like 5 minutes. It leaves your data intact, so you won't have to set it up again. It also leaves the Xposed app on your phone and you just need to open it and install it. All your modules will still be there and will work as they did before after a reboot.
Click to expand...
Click to collapse
I kept the old boot animation file so I can just move it back.
Sent from my XT1060 using XDA Premium 4 mobile app
OK so then technically you can reinstall the old boot Ani, unfreeze all apps, disable xposed using the Xposed disabler zip that should be in your SD card root directory, and then flash stock recovery.
That should allow you to take the OTA as you would technically be stock at that point. I chose the other method to ensure I was 100% stock. This should get you to stock as well, but I guess I like to be certain.
Sent from my Dev Edition Moto X
Schaweet said:
OK so then technically you can reinstall the old boot Ani, unfreeze all apps, disable xposed using the Xposed disabler zip that should be in your SD card root directory, and then flash stock recovery.
That should allow you to take the OTA as you would technically be stock at that point. I chose the other method to ensure I was 100% stock. This should get you to stock as well, but I guess I like to be certain.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
OK. I think I will do your method instead. I will unfreeze the apps, install old boot logo and disable xposed just to be safe. Then I will do your method. Wish me luck.
Sent from my XT1060 using XDA Premium 4 mobile app
If you do my method with all the numbered steps, you don't have to mess with all the unfreezing and stuff. Flashing system.img overwrites all those changes for you.
Sent from my Dev Edition Moto X
Schaweet said:
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
You don't even need an unlocked bootloader, you can still flash stock images on a locked bootloader. Also the person obviously unlock the bootloader since TWRP is installed, unless I'm not aware of a way to install it without.
eksasol said:
Also the person obviously unlock the bootloader since TWRP is installed, unless I'm not aware of a way to install it without.
Click to expand...
Click to collapse
You are correct. You can only flash a custom recovery if your bootloader is unlocked. That is what unlocking your bootloader allows you to do - flash unsigned recovery files (i.e., custom recoveries) and obviously, TWRP is not signed by motorola. Then once you have a custom recovery, the custom recovery allows you to flash unsigned operating systems.
If your bootloader is locked, you cannot flash an unsigned recovery.
Schaweet said:
If you do my method with all the numbered steps, you don't have to mess with all the unfreezing and stuff. Flashing system.img overwrites all those changes for you.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Sent from my XT1060 using XDA Premium 4 mobile app
---------- Post added at 01:40 PM ---------- Previous post was at 01:40 PM ----------
robwege said:
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I meant step 7.
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Click to expand...
Click to collapse
fastboot is fine to flash recovery but you need to be in bootloader mode to use fastboot. You need mfastboot to flash system since it is so large. But mfastboot will work to flash recovery, too.
adb doesn't work in bootloader mode and fastboot doesn't work when you are booted into system. So if adb is working for you, you aren't in bootloader mode (note: bootloader mode is also called fastboot mode since for fastboot to work, you need to be in bootloader mode).
Go back to step 5 - boot into bootloader mode. Just type adb reboot bootloader. That will put you in bootloader mode.
NightThyme said:
fastboot is fine to flash recovery but you need to be in bootloader mode to use fastboot. You need mfastboot to flash system since it is so large. But mfastboot will work to flash recovery, too.
adb doesn't work in bootloader mode and fastboot doesn't work when you are booted into system. So if adb is working for you, you aren't in bootloader mode (note: bootloader mode is also called fastboot mode since for fastboot to work, you need to be in bootloader mode).
Go back to step 5 - boot into bootloader mode. Just type adb reboot bootloader. That will put you in bootloader mode.
Click to expand...
Click to collapse
OK. So if I am understanding you correctly. I boot the phone into fast boot. Then type your reboot bootloader cmd. Then from there I can do step 7 and 8 as typed above I. The thread where 7 uses fastboot and 8 uses mfastboot?
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
OK. So if I am understanding you correctly. I boot the phone into fast boot. Then type your reboot bootloader cmd. Then from there I can do step 7 and 8 as typed above I. The thread where 7 uses fastboot and 8 uses mfastboot?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The commands are written correctly. You have to be in bootloader/fastboot mode. I thought I said that.
Edit. I did see step 5.
Follow every step you don't want a brick.
Sent from my Dev Edition Moto X
Schaweet said:
The commands are written correctly. You have to be in bootloader/fastboot mode. I thought I said that.
Edit. I did see step 5.
Follow every step you don't want a brick.
Click to expand...
Click to collapse
This.
If I wanted to go back to stock from an aosp based ROM could I use the mfastboot recovery and system method or do I ha e to rsd.... I'm unlocked btw
Sent from my Moto X using Tapatalk
Right, so I've been following http://forum.xda-developers.com/xperia-z/orig-development/root-xperia-z-c660x-unlocked-t2154310 to root my xperia z. I followed the instructions but when I wrote the second image it refused to boot properly, looping constantly through the sony logo IIRC.
To fix this I used the recovery image. I can get into it just fine but when I try to install SuperSU-1.25-Busybox-1.20.2-UPDATE.zip it goes through the motions, but rebooting the phone just brings me back into recovery mode. Any ideas on what's wrong?
Rare Devil said:
Right, so I've been following http://forum.xda-developers.com/xperia-z/orig-development/root-xperia-z-c660x-unlocked-t2154310 to root my xperia z. I followed the instructions but when I wrote the second image it refused to boot properly, looping constantly through the sony logo IIRC.
To fix this I used the recovery image. I can get into it just fine but when I try to install SuperSU-1.25-Busybox-1.20.2-UPDATE.zip it goes through the motions, but rebooting the phone just brings me back into recovery mode. Any ideas on what's wrong?
Click to expand...
Click to collapse
there is only one image that you need to flash that is boot.img
after that flash advance stock kernel in recovery followed by super su make sure your bootloader is unlocked if you plan to flash custom kernel
what firmware you are on?
Unlocking bootloader invalidates warranty
androidtweaker1 said:
there is only one image that you need to flash that is boot.img
after that flash advance stock kernel in recovery followed by super su make sure your bootloader is unlocked if you plan to flash custom kernel
what firmware you are on?
Unlocking bootloader invalidates warranty
Click to expand...
Click to collapse
I'm not sure what firmware I'm on but I did update it just before I tried all this. I did unlock my bootloader and used boot.img to get into recovery mode. Super su is done through recovery mode right? Because every time I try to install it it just returns to recovery mode with no changes
Rare Devil said:
I'm not sure what firmware I'm on but I did update it just before I tried all this. I did unlock my bootloader and used boot.img to get into recovery mode. Super su is done through recovery mode right? Because every time I try to install it it just returns to recovery mode with no changes
Click to expand...
Click to collapse
Try twrp recovery you can download the .img from here
after flashing recovery try flashing SU from twrp.
post the results
androidtweaker1 said:
Try twrp recovery you can download the .img from
after flashing recovery try flashing SU from twrp.
post the results
Click to expand...
Click to collapse
Flashing that img gives me an error "writing: 'recovery' FAILED (remote: Command not allowed)
If you want to try TWRP, try Dual Boot recovery with Philz Touch CWM Advanced Edition and TWRP by shoey63.
Sent from my C6603 using Tapatalk
What do I specifcally type for that? From what I've seen different img files use different commands
Rare Devil said:
What do I specifcally type for that? From what I've seen different img files use different commands
Click to expand...
Click to collapse
fastboot flash boot boot.img
By the way, the guide you were following is outdated and has an old version of the kernel, that's why you went into a bootloop.
Sent from my C6603 using Tapatalk
kingvortex said:
fastboot flash boot boot.img
By the way, the guide you were following is outdated and has an old version of the kernel, that's why you went into a bootloop.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
It booted properly. Thanks. So from there it's just installing zip? Or are there any other steps?
Flash a SuperSu zip and you're rooted. Simple as that.
I suggest this one - SuperSU zip.
Sent from my C6603 using Tapatalk
kingvortex said:
Flash a SuperSu zip and you're rooted. Simple as that.
I suggest this one -
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
It still gives me a black screen when I reboot and go past the sony startup screen. How long does it usually take?
Rare Devil said:
It still gives me a black screen when I reboot and go past the sony startup screen. How long does it usually take?
Click to expand...
Click to collapse
http://d-h.st/UP0
this help me, but back me to KK 4.4.4, but i have my sony back
So I got my Z1 yesterday, was on 4.4.2 stock unrooted. I unlocked the bootloader using Sony's official website and fastboot, then I went on destroying the phone by flashing Philz touch recovery.img through fastboot.
And since then the phone has been bricked, I can only enter Fastboot through the blue led, while Flash mode doesn't show up any LED light and my PC sees the phone when on flashmode as n "S1 device with a parameter error".
I've tried all drivers, none worked, and the flashtool keeps suggesting I should update my drivers when connecting the phone on flash mode:
02/042/2014 22:42:11 - INFO - Device connected in flash mode
02/042/2014 22:42:30 - ERROR - Drivers need to be installed for connected device.
02/042/2014 22:42:30 - ERROR - You can find them in the drivers folder of Flashtool.
Click to expand...
Click to collapse
Is there any way I can recover from this through fastboot instead of the flashtool? I can still flash system.img and recovery.img through fastboot. I'd really appreciate any help right now.
Abu-7abash said:
So I got my Z1 yesterday, was on 4.4.2 stock unrooted. I unlocked the bootloader using Sony's official website and fastboot, then I went on destroying the phone by flashing Philz touch recovery.img through fastboot.
And since then the phone has been bricked, I can only enter Fastboot through the blue led, while Flash mode doesn't show up any LED light and my PC sees the phone when on flashmode as n "S1 device with a parameter error".
I've tried all drivers, none worked, and the flashtool keeps suggesting I should update my drivers when connecting the phone on flash mode:
Is there any way I can recover from this through fastboot instead of the flashtool? I can still flash system.img and recovery.img through fastboot. I'd really appreciate any help right now.
Click to expand...
Click to collapse
Xperia phones do not have a recovery partition to flash recovery to via fastboot.
If you can enter fastboot, then flash a stock kernel.elf with flashtool (In fastboot mode).
Then you can use flashtool to relock your boot (I imagine you have not even taken a TA backup and you are new to xperia devices, your post suggests so)
then you should be able to use pccompanion to repair, or flashtool to flash a FTF
However, by flashing a recovery image you may have bricked the phone. try what I have said, if it does not work get back in touch. (Do you have access to jtag and setool?)
gregbradley said:
Xperia phones do not have a recovery partition to flash recovery to via fastboot.
If you can enter fastboot, then flash a stock kernel.elf with flashtool (In fastboot mode).
Then you can use flashtool to relock your boot (I imagine you have not even taken a TA backup and you are new to xperia devices, your post suggests so)
then you should be able to use pccompanion to repair, or flashtool to flash a FTF
However, by flashing a recovery image you may have bricked the phone. try what I have said, if it does not work get back in touch. (Do you have access to jtag and setool?)
Click to expand...
Click to collapse
Can you link me to the files you suggested I try? There seems to be a truckload of them laying around the forum.
Also, yes, I am new to xperia phones. Didnt think they were this complicated to flash but I shouldnt have played with fastboot anyway. And no, sadly I dont have a jtag. Never needed one before.
Thanks for the help btw, I greatly appreciate this.
i dont think you have 100% installed the drivers, on windows 7 upwards you need to disable driver signature to allow any unsigned drivers to be installed
Look in the mega collection thread in the general section for a 442 ftf file. The kernel.elf will be in it
Sent from my C6903 using XDA Premium 4 mobile app
gregbradley said:
Look in the mega collection thread in the general section for a 442 ftf file. The kernel.elf will be in it
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright, but how do I extract it from the TFT file?
gregbradley said:
Look in the mega collection thread in the general section for a 442 ftf file. The kernel.elf will be in it
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
C6903_14.3.A.0.757_Global 1277-2880.ftf
Is this 4.4.2?
Ok here is an update; after messing with fastboot for so long and a couple of kernel flashes, I managed to boot the phone But now its stuck on the Sony logo.
A sign of hope though lies with the fact that I managed to enter recovery mode and found CWM hanging there. So now Im probably going to try ADB push a rom file to the SD and try to flash it through recovery instead.
@gregbradley
Sounds good. The reason forth hang at the sony logo will be that you have wiped the system partition. Flashing a rom based on the kernel you have will enable the phone to boot
Sent from my C6903 using XDA Premium 4 mobile app
gregbradley said:
Sounds good. The reason forth hang at the sony logo will be that you have wiped the system partition. Flashing a rom based on the kernel you have will enable the phone to boot
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Would flashing a custom rom zip from the CWM recovery, fix the bootloop? Or could it also be a baseband/firmware issue too?
Im not really familiar with Sony's bootloader unlock process, does it allow kernel flash from recovery or only through fastboot ala Htc style?
Abu-7abash said:
Would flashing a custom rom zip from the CWM recovery, fix the bootloop? Or could it also be a baseband/firmware issue too?
Im not really familiar with Sony's bootloader unlock process, does it allow kernel flash from recovery or only through fastboot ala Htc style?
Click to expand...
Click to collapse
first flash original stock rom, than root your phone and install dualrecovery... and if u relock your bootloader unlock it again... don't try custom rom before this steps
Abu-7abash said:
Would flashing a custom rom zip from the CWM recovery, fix the bootloop? Or could it also be a baseband/firmware issue too?
Click to expand...
Click to collapse
Yes, as long as the .zip contains a kernel, or id based on the same kernel you have installed now
Im not really familiar with Sony's bootloader unlock process, does it allow kernel flash from recovery or only through fastboot ala Htc style?
Click to expand...
Click to collapse
Yes, if you have an unlocked bootloader
gregbradley said:
Yes, as long as the .zip contains a kernel, or id based on the same kernel you have installed nowYes, if you have an unlocked bootloader
Click to expand...
Click to collapse
Alright thanks, gonna give it a go once im home. And yes, I already unlocked the bootloader through Sony's website and fastboot before this happened.
Vuja1 said:
first flash original stock rom, than root your phone and install dualrecovery... and if u relock your bootloader unlock it again... don't try custom rom before this steps
Click to expand...
Click to collapse
It already has the dual recovery on it but for some reason its stuck in a bootloop.
Abu-7abash said:
It already has the dual recovery on it but for some reason its stuck in a bootloop.
Click to expand...
Click to collapse
do u have any rom on it or u just have bootloop? i u can't access to rom, u need with flashtool to flash stock rom, when u do that u loose your root and lose your dualrecovery... u need to root it again and install dualrecovery
second is
if u can access to rom instal ndr utility and reboot in clockwork mod recovery...
third option si to install via fastboot advanced doomloader kernel which has clockwork mod and has root... after that to flash custom rom but stock version of custom rom
Any of you guys know of a Stock rooted 4.4.4 rom that comes with the stock kernel in a flashable zip? I have looked everywhere for one but I cant find any.
@gregbradley @Vuja1
Abu-7abash said:
Any of you guys know of a Stock rooted 4.4.4 rom that comes with the stock kernel in a flashable zip? I have looked everywhere for one but I cant find any.
@gregbradley @Vuja1
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2761614
try this one
Vuja1 said:
http://forum.xda-developers.com/showthread.php?t=2761614
try this one
Click to expand...
Click to collapse
Already did, not really what Im looking for. I want the stock rom but only rooted and in a flashable zip, can't believe there aint any around.
Abu-7abash said:
Already did, not really what Im looking for. I want the stock rom but only rooted and in a flashable zip, can't believe there aint any around.
Click to expand...
Click to collapse
I can think of at least 3 in the development section off the top of my head...
gregbradley said:
I can think of at least 3 in the development section off the top of my head...
Click to expand...
Click to collapse
You can? Link me Greg..link me
Hi. Last night I've updated to las OTA. After reboot and installation it make a reboot and never start again, it stopped in gear live initial logo and stay there until batteries end.
Now, when I plug the watch it show battery logo forever and if I press the bottom enough time it goes to startup infinite loop.
Some help?
Thanks!
Sent from my SM-N910F using XDA Free mobile app
Things that I've try:
Go into bootloader Ok.
Go into recovery fail: Do nothing and start to warmup.
Download twrp version 2.7.1.2-sp.img and twrp 2.8.6.0 and fastboot boot twrp.img: Nothing fastboot say ok and after that just nothing, watch start to warm
Download SamsungGearLive-sprat-ddPull-AdamOutlerDevice-24July2014.tar.gz ... inside lots of img's files, I've try to boot with recovery.img and.... nothing.
I'm soooo lost.
Mquinteiro said:
Things that I've try:
Go into bootloader Ok.
Go into recovery fail: Do nothing and start to warmup.
Download twrp version 2.7.1.2-sp.img and twrp 2.8.6.0 and fastboot boot twrp.img: Nothing fastboot say ok and after that just nothing, watch start to warm
Download SamsungGearLive-sprat-ddPull-AdamOutlerDevice-24July2014.tar.gz ... inside lots of img's files, I've try to boot with recovery.img and.... nothing.
I'm soooo lost.
Click to expand...
Click to collapse
Ok first things first: is your bootloader unlocked? if not then you can't flash/boot anything that is not signed by the Samsung/Google for our specific watch. So you can't boot into TWRP unless you unlock it. fastboot oem unlock will unlock it, but for security purposes, it will also reset your watch to factory.
Thanks Aligatror, it is not unlocked, i wish to restore to stock and I've tried to boot from external google//samsung recovery with out look.
Regarding the stock firmware i can't find anywhere instructions about how to flash everything and were to find factory images.
Thanks!
Sent from my SM-N910F using XDA Free mobile app
Did you try the Gear Live restore tool? It's in the gear live android development forum
Brendo said:
Did you try the Gear Live restore tool? It's in the gear live android development forum
Click to expand...
Click to collapse
Yes, it is a great tool, but there appears to be a broken bluetooth file in the v3 image which makes it impossible to pair watch to a phone. So, use V2 instead.
Brendo said:
Did you try the Gear Live restore tool? It's in the gear live android development forum
Click to expand...
Click to collapse
I do it and .... worst! now it still in boot loop but everithime show de lable "Recovery booting" Even in batery charge!
The only thing that works is bootloader.
Note I've unlocked and locked
Mquinteiro said:
I do it and .... worst! now it still in boot loop but everithime show de lable "Recovery booting" Even in batery charge!
The only thing that works is bootloader.
Note I've unlocked and locked
Click to expand...
Click to collapse
Which version did you download and what option did you select? Recovery boot message is normal when you do unlock since it erases the user partition. Select option to restore to stock or something like that in that program you downloaded. Just make you that you have version 2 and not 3.
I did with version 2 and 3 I do it by hand because linux script does not work.
I've flash boot recovery and system partitions included in the tool zip file.
And. ... nothing
Sent from my SM-N910F using XDA Free mobile app
Mquinteiro said:
I did with version 2 and 3 I do it by hand because linux script does not work.
I've flash boot recovery and system partitions included in the tool zip file.
And. ... nothing
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
Is it still stuck in bootloop? Can you boot into recovery from bootloader?
I can't boot into recovery. Only bootloader works.
Every time that I press recovery from bootloader I get an "recovering boot " forever
Sent from my SM-N910F using XDA Free mobile app
Mquinteiro said:
I can't boot into recovery. Only bootloader works.
Every time that I press recovery from bootloader I get an "recovering boot " forever
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
Lets try something more radical.
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
And then flash boot, recovery and system.
No, I can't go into recovery, just Bootloader. recovery hangs and normal boot hangs too.
I have take a look to update script and it have a new img for partitions associated with it.. I have flashed all of them and.... nothing.
Mquinteiro said:
No, I can't go into recovery, just Bootloader. recovery hangs and normal boot hangs too.
I have take a look to update script and it have a new img for partitions associated with it.. I have flashed all of them and.... nothing.
Click to expand...
Click to collapse
Try reflashing the bootloader itself. Download latest OTA update
sprat-LDZ22J-from-LWX49K.1e8de7cf.zip
Extract it and you'll see bunch of files "bootloader.xxxx.img". Flash all of the .img files.
fastboot flash apnhlos bootloader.apnhlos.img
fastboot flash aboot bootloader.aboot.img
.... and so on with all bootloader files.
Reboot bootloader and try booting into recovery or system.
aligatro2010 said:
Try reflashing the bootloader itself. Download latest OTA update
sprat-LDZ22J-from-LWX49K.1e8de7cf.zip
Extract it and you'll see bunch of files "bootloader.xxxx.img". Flash all of the .img files.
fastboot flash apnhlos bootloader.apnhlos.img
fastboot flash aboot bootloader.aboot.img
.... and so on with all bootloader files.
Reboot bootloader and try booting into recovery or system.
Click to expand...
Click to collapse
It is exactly what I did yesterday and no luck!
The only thing that I coulden't did was flash 5.1.1 recovery, and other partitions because it come like .p files (dif images)
But thanks
Mquinteiro said:
It is exactly what I did yesterday and no luck!
The only thing that I coulden't did was flash 5.1.1 recovery, and other partitions because it come like .p files (dif images)
But thanks
Click to expand...
Click to collapse
Well I guess your only option is to flash to 4.4, flash older bootloader and request repair service from Samsung.
aligatro2010 said:
Yes, it is a great tool, but there appears to be a broken bluetooth file in the v3 image which makes it impossible to pair watch to a phone. So, use V2 instead.
Click to expand...
Click to collapse
Is the watch effectively bricked once that image is flashed? I've come across your post too late after reading about the tool. Used v3, told the tool to restore to stock, the watch boots its image fine but the bluetooth is definitely broken now (phone won't connect to it). I can get to settings to enable ADB on wear but I can't authorize my PC it seems, never get the notification on the watch screen to allow the PC. It's just stuck at the initialization telling me to Install Android Wear on my phone.
naaaaail said:
Is the watch effectively bricked once that image is flashed? I've come across your post too late after reading about the tool. Used v3, told the tool to restore to stock, the watch boots its image fine but the bluetooth is definitely broken now (phone won't connect to it). I can get to settings to enable ADB on wear but I can't authorize my PC it seems, never get the notification on the watch screen to allow the PC. It's just stuck at the initialization telling me to Install Android Wear on my phone.
Click to expand...
Click to collapse
Its not bricked, but the bluetooth is not working due to corrupted file. You can flash v2 no problem. Just make sure to do reset after flashing.
So today I embarked on what seemed to be a fruitless journey as I tried to root the Infinix Hot 2 on the latest build (December Security Patch of course) and I observed the following:
1. Flashing TWRP Recovery that was previously made for this device doesn't Flash. SP/Infinix Flash Tool flashes the recovery quite alright but booting to recovery with ADB afterwards gives a "No command" screen.
2. Kingroot (PC & Mobile) can't root this device as of yet :'(
3. I think the bootloader can be unlocked using the Android One Toolkit that was created for 1st Gen Android One devices. Reason being the fact it booted to fastboot and prompted me with the option to accept bootloader unlock or not.
Should you come come successful with flashing recovery or rooting this latest build, please comment your method. Thank you...
Link to Android One Toolkit:
http://forum.xda-developers.com/crossdevice-dev/android-one-general/toolbox-android-one-toolkit-one-click-t3030165
recovery partition is protected, it will get back to stock recovery if you boot the system. so you really need to boot recovery as the first thing you do after flashing.
which because of the similar bug we can't unlock our bootloader, is impossible to do with default setting. flash your lk partition with this:
http://www80.zippyshare.com/v/X4etwppD/file.html
taken from: http://forum.xda-developers.com/hot-2/development/android-one-rom-recovery-twrp-root-sp-t3227682
sabcpj said:
recovery partition is protected, it will get back to stock recovery if you boot the system. so you really need to boot recovery as the first thing you do after flashing.
which because of the similar bug we can't unlock our bootloader, is impossible to do with default setting. flash your lk partition with this:
http://www80.zippyshare.com/v/X4etwppD/file.html
taken from: http://forum.xda-developers.com/hot-2/development/android-one-rom-recovery-twrp-root-sp-t3227682
Click to expand...
Click to collapse
Thanks I will try this in the morning...
One more question... Does this mean after flashing recovery I can boot directly into TWRP using key combo?
iAmWiz said:
Thanks I will try this in the morning...
One more question... Does this mean after flashing recovery I can boot directly into TWRP using key combo?
Click to expand...
Click to collapse
yes, you should be. and you need to
Alright then
sabcpj said:
yes, you should be. and you need to
Click to expand...
Click to collapse
there is no scatter file for the lk-recovery.. I do not think I can flash it directly with Flash Tool without the scatter file
iAmWiz said:
there is no scatter file for the lk-recovery.. I do not think I can flash it directly with Flash Tool without the scatter file
Click to expand...
Click to collapse
why do you think you need another scatter file. you already tried flashing twrp right? use that one. then change the location of partition named "lk" to point this file. that's all.
sabcpj said:
why do you think you need another scatter file. you already tried flashing twrp right? use that one. then change the location of partition named "lk" to point this file. that's all.
Click to expand...
Click to collapse
Alright. If I cannot get a workaround on this, I'll just Flash Infinix 5.1 ROM and wait till M
Try using towel root
https://towelroot.com/
Mysteryagr said:
Try using towel root
https://towelroot.com/
Click to expand...
Click to collapse
Thanks but towelroot didn't work out.
Root achieved... More at
http://forum.xda-developers.com/hot-2/development/root-recovery-xposed-successfully-t3276420
please can you help me sp flashtool stuck at 0 and nothing happens