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.
Related
Back story: Verizon Moto X, unlocked bootloader via China Middleman, running Eclipse ROM 4.4.2, TWRP 2.7.0.0 recovery
Objective: wipe everything and flash back to a (rooted) stock for device retail
Why I'm screwed: everything is wiped - phone has no OS, recovery, etc. It simply hangs out on the Motorola M at boot and doesn't move. fastboot loads and will flash recovery (seemingly successfully) but rebooting to recovery always gets stuck at the logo
How I got there:
1. Backed up with TWRP, then flashed new recovery CWM (the one here) and backed up again. Saved both folders of nandroid backups to my PC (yay)
2. Flashed back to TWRP (but this time the new one v2.8.0.1 here, which I downloaded and flashed via that fancy new TWRP app [I selected the "ghost" model]) clicked about every type of wipe option I could get my grubby little fingers on, then adb pushed the ROM and kernel/radio combo from here.
3. Attempted to flash the new ROM via TWRP. It failed. something about an "Error executing updater binary in zip". I sighed, said "meh", googled the problem a bit and figured I'd reboot the recovery and try again. This is where things get weird.
4. Phone hangs out at boot logo (that kaleidoscope "M"). Fine, I accidentally did a normal boot, and there's no OS installed. I go into fastboot and boot to recovery. SAME SCREEN. TWRP has apparently disappeared. No matter. I go into fastboot and flash it again, then boot to recovery. SAME SCREEN. Flash back to CWM. SAME SCREEN. Back to TWRP one more time just for giggles? SAME SCREEN.
No idea where to go from here. Anyone have any idea how this happened and what my options are at this point? Is there a way to manually flash a ROM via fastboot? Restore either my CWM or TWRP nandroid backups without access to the recovery? Any guidance would be appreciated.
Attachments:
a) boot logo I'm stuck on
b) command line log of commands from flashing recoveries
From fastboot, flash your recovery and then use the volume down button to highlight recovery and then volume up button to enter into recovery.
VerneVerne said:
From fastboot, flash your recovery and then use the volume down button to highlight recovery and then volume up button to enter into recovery.
Click to expand...
Click to collapse
Perhaps I didn't make that clear - that's exactly what I've been doing.
PHP:
gerodive said:
Back story: Verizon Moto X, unlocked bootloader via China Middleman
Click to expand...
Click to collapse
That is what I have.
gerodive said:
No idea where to go from here. Anyone have any idea how this happened and what my options are at this point? Is there a way to manually flash a ROM via fastboot?
Click to expand...
Click to collapse
Well I wiped my system partition when I must have been drunk or something b/c I still can't believe I did it. But I did. Then from bootloader mode, I ran the command mfastboot flash system system.img from a command shell on my PC using the system image from the sbf that my bootloader was currently on (in my case, it was 4.4.4). All was good.
Then I could restore my nandroids by moving them to my phone from my PC.
Wansanta said:
PHP:
That is what I have.
Well I wiped my system partition when I must have been drunk or something b/c I still can't believe I did it. But I did. Then from bootloader mode, I ran the command mfastboot flash system system.img from a command shell on my PC using the system image from the sbf that my bootloader was currently on (in my case, it was 4.4.4). All was good.
Then I could restore my nandroids by moving them to my phone from my PC.
Click to expand...
Click to collapse
Could you elaborate a little more on this? How do I get the system.img file to flash? I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check? Deleting the system partition was definitely what I did. Also, why mfastboot as opposed to just fastboot?
gerodive said:
Could you elaborate a little more on this? How do I get the system.img file to flash?
Click to expand...
Click to collapse
mfastboot flash system system.img
gerodive said:
I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check?
Click to expand...
Click to collapse
In bootloader mode it will tell you on the second line. 30:B7 is the 4.4.4 bootloader version.
gerodive said:
Deleting the system partition was definitely what I did.
Click to expand...
Click to collapse
As long as you can get into bootloader mode you can flash it back.
gerodive said:
Also, why mfastboot as opposed to just fastboot?
Click to expand...
Click to collapse
because the moto x system images are too large to flash with fastboot, you have to use mfastboot.
gerodive said:
Back story: Verizon Moto X, unlocked bootloader via China Middleman, running Eclipse ROM 4.2.2, TWRP 2.7.0.0 recovery
Click to expand...
Click to collapse
gerodive said:
I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check?
Click to expand...
Click to collapse
4.2.2 or 4.4.2?
nhizzat said:
4.2.2 or 4.4.2?
Click to expand...
Click to collapse
yeah he really needs to check b/c it really matters what version of the bootloader he is on.
Flashing the 4.4.2 system.img (and boot.img just for good measure) worked! I was then able to boot normally and then upgraded to 4.4.4. Oh happy day. Thanks for the help everyone.
Sorry, meant 4.4.2.
gerodive said:
Flashing the 4.4.2 system.img (and boot.img just for good measure) worked! I was then able to boot normally and then upgraded to 4.4.4. Oh happy day. Thanks for the help everyone.
Click to expand...
Click to collapse
So glad!! If you are unlocked, as long as you can get into a functioning bootloader mode and have access to the sbf for your version of the OS you haven't bricked.
I about near had a heart attack when I deleted my system, but no biggie to restore it. I think I only paid $35 to unlock b/c I did it straight through tao bao, but it was the best $35 I have spent in a long time. I drop $35 every time I go for sushi, so I can't imagine not paying to unlock if you have the option.
Hello mates,
I just want to switch back to stock firmware just downloaded the B133 maybe i will upgrade to EMUI.3.0 manually but i have twrp installed how can i flash the stock firmware? which is not in zip file its dload/update.app
can someone please guide me?
.
Thanks and blessing
Farrukh
FarrukhQadri said:
Hello mates,
I just want to switch back to stock firmware just downloaded the B133 maybe i will upgrade to EMUI.3.0 manually but i have twrp installed how can i flash the stock firmware? which is not in zip file its dload/update.app
can someone please guide me?
.
Thanks and blessing
Farrukh
Click to expand...
Click to collapse
Hello,
You must first install stock recovery in order to manually update through Updater > Local update, and yes update.app must be in the dload folder on the SD card. (connect your device to your PC, install adb, reboot it to bootloader using 'adb reboot bootloader', put 'recovery.img' into the same folder as adb, execute 'fastboot flash recovery recovery.img', then do 'fastboot reboot', once your device is fully booted go to the Updater app, and do a local update.)
B609 Stock recovery - Download here
Best regards,
James
Daentrod said:
Hello,
You must first install stock recovery in order to manually update through Updater > Local update, and yes update.app must be in the dload folder on the SD card. (connect your device to your PC, install adb, reboot it to bootloader using 'adb reboot bootloader', put 'recovery.img' into the same folder as adb, execute 'fastboot flash recovery recovery.img', then do 'fastboot reboot', once your device is fully booted go to the Updater app, and do a local update.)
B609 Stock recovery - Download here
Best regards,
James
Click to expand...
Click to collapse
Thanks a lot i will do it tonight
FarrukhQadri said:
Thanks a lot i will do it tonight
Click to expand...
Click to collapse
when i execute the adb reboot boat loader command my device won't gets into boat loader but it reboot i tried rebooting into boat loader by flashify app it shows a screen fastboot rescue mode. (phone is unlocked)
i can flash the recovery.
whats wrong ??
FarrukhQadri said:
when i execute the adb reboot boat loader command my device won't gets into boat loader but it reboot i tried rebooting into boat loader by flashify app it shows a screen fastboot rescue mode. (phone is unlocked)
i can flash the recovery.
whats wrong ??
Click to expand...
Click to collapse
That is exactly what you need - adb reboot bootloader (<- it's one word!) gets the phone into fastboot mode (same as flashify). From here you can flash the recovery. On the PC, run fastboot flash recovery <path-to-stock-recovery>. This will get you the stock recovery on the phone. Now you can use the 3 button method to flash the stock ROM.
g4b3rm4n said:
That is exactly what you need - adb reboot bootloader (<- it's one word!) gets the phone into fastboot mode (same as flashify). From here you can flash the recovery. On the PC, run fastboot flash recovery <path-to-stock-recovery>. This will get you the stock recovery on the phone. Now you can use the 3 button method to flash the stock ROM.
Click to expand...
Click to collapse
Can you please guide me a bit more actually now my device is not booting into recovery neither into system its stuck on logo and not going ahead. so should i follow these steps only flash stock recovery in fastboot then flash stock rom?
my phone is stuck on logo and it remains on the logo screen for a couple of seconds then it reboots itself automatically and keep doing the same..
Thanks
FarrukhQadri said:
Can you please guide me a bit more actually now my device is not booting into recovery neither into system its stuck on logo and not going ahead. so should i follow these steps only flash stock recovery in fastboot then flash stock rom?
my phone is stuck on logo and it remains on the logo screen for a couple of seconds then it reboots itself automatically and keep doing the same..
Thanks
Click to expand...
Click to collapse
You must get it into fastboot mode. If the phone restarts and does not boot into the OS, then it's a huge problem. You may try to restore the phone with HiSuite, but my bet is that you'd better get it to a service - you probably flashed the wrong bootloader.
You might have luck with the recovery though - hold down VOLUME UP and POWER when turning the device on. This might get you ADB, so you might boot into fastboot mode.
g4b3rm4n said:
You must get it into fastboot mode. If the phone restarts and does not boot into the OS, then it's a huge problem. You may try to restore the phone with HiSuite, but my bet is that you'd better get it to a service - you probably flashed the wrong bootloader.
You might have luck with the recovery though - hold down VOLUME UP and POWER when turning the device on. This might get you ADB, so you might boot into fastboot mode.
Click to expand...
Click to collapse
Let me have a try i will get back to you. i had this problem with my previous phone but this time its getting so long i'm worried of it, yes my bad i have flashed a wrong kernel mistakenly it was on the phone so i flashed the wrong file.
FarrukhQadri said:
Let me have a try i will get back to you. i had this problem with my previous phone but this time its getting so long i'm worried of it, yes my bad i have flashed a wrong kernel mistakenly it was on the phone so i flashed the wrong file.
Click to expand...
Click to collapse
You are right i have to get it to service its not working at all cant even find in fastboot neither in recovery .. this goes so expensive
Press power, volume-down and connect device to PC simultaneously. You will get into fastboot mode. Flash boot image and recovery image that was exactly from your firmware version.
Kostyan_nsk said:
Press power, volume-down and connect device to PC simultaneously. You will get into fastboot mode. Flash boot image and recovery image that was exactly from your firmware version.
Click to expand...
Click to collapse
can you please share drivers link? i have booted into fastboot and adb installed already but it cant find my device ..
Resolved
Thank you Everyone for helping and guiding issue is resolved your help is always appreciated...
how?
FarrukhQadri said:
Thank you Everyone for helping and guiding issue is resolved your help is always appreciated...
Click to expand...
Click to collapse
How?
jefpcbr said:
How?
Click to expand...
Click to collapse
THAT HOW , FORGET some crap TWRP ! it is no use with huawei devices !
Simona Simmy said:
THAT HOW , FORGET some crap TWRP ! it is no use with huawei devices !
Click to expand...
Click to collapse
but i think twrp is better than cwn
FarrukhQadri said:
but i think twrp is better than cwn
Click to expand...
Click to collapse
What ? In waht way god..
Same purpose .. no better at all it will destroy your phone soon..
killed my phone
Daentrod said:
Hello,
You must first install stock recovery in order to manually update through Updater > Local update, and yes update.app must be in the dload folder on the SD card. (connect your device to your PC, install adb, reboot it to bootloader using 'adb reboot bootloader', put 'recovery.img' into the same folder as adb, execute 'fastboot flash recovery recovery.img', then do 'fastboot reboot', once your device is fully booted go to the Updater app, and do a local update.)
Best regards,
James
Click to expand...
Click to collapse
Hi.
This killed my mobile.
Now I can't boot in, I i can have is the bootloader screen saying ur phone is locked
Please someone help.
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Try re download the zip (or try an other rom)maybe you just got an false download. i also had some trouble with my m7 back in the day.
But in your case now you are stuck with no os or bootloop, i give you as advice to follow an soft unbrick method it worked for me, or if you have an usb otg cable and usb or and usb otg thumbstick, put the rom on that usb and connect it to your phone and then try to flash it (if your using twrp you have an option to choose from wich storage you want to use)
Also a piece of advice, when flashing roms, kernels etc please have your phone charged above 50% (just in case).
Sent from my HUAWEI P7-L10 using XDA Free mobile app
---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------
its the peanut said:
Try re download the zip (or try an other rom)maybe you just got an false download. i also had some trouble with my m7 back in the day.
But in your case now you are stuck with no os or bootloop, i give you as advice to follow an soft unbrick method it worked for me, or if you have an usb otg cable and usb or and usb otg thumbstick, put the rom on that usb and connect it to your phone and then try to flash it (if your using twrp you have an option to choose from wich storage you want to use)
Also a piece of advice, when flashing roms, kernels etc please have your phone charged above 50% (just in case).
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Click to expand...
Click to collapse
Also make sure you downloaded the rom made for your phone model!
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Can you please post the output of
Code:
fastboot getvar all
please remove your imei and serial number.
Depending on which variant of the M7 you have you probably just need a different version of recovery to install a CM rom. I think they prefer TWRP 2.7.x.x. Post the getvar and we can see what you have. then I can give you a better informed instruction. :good:
P.s also check the md5 of the rom zip you downloaded. Use this tool www.winmd5.com the correct md5 should be listed with the link you downloaded the rom from
failed to mount /dev/block/blah blah blah = needs "block:by-name" support which twrp 2.6.3.3 doesn't have
everything explained here
So update your recovery
and do what danny said above so he can confirm you have the right rom/recovery for your device.
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Your getvar looks fine this rom should work fine with your device. Download this version of TWRP https://www.androidfilehost.com/?fid=23501681358561860 (2.7.1.2). dropthe file in your fastboot folder and flash it with fastboot.
Code:
fastboot flash recovery "name-of-recovery".img
fastboot erase cache
fastboot reboot-bootloader
Once thats done reflash the rom with the new version of TWRP. It should flash just fine :good:
iv managed to flash cm12.1 now, thanks guys, is there anyway i could get the HTC software back on.
Burky1996 said:
iv managed to flash cm12.1 now, thanks guys, is there anyway i could get the HTC software back on.
Click to expand...
Click to collapse
There are a number of ways to return to stock software. You can simply flash a stock rom through twrp or use a stock nandroid. look for rom that match your version main. 7.19.401.22
I think there is even an lollipop 7.19.401.22 RUU for your device but I'm not sure if it will work with s-on though because it's a zip but it certainly wouldnt hurt to try it though. You will need to relock your bootloader and flash it with fastboot.
I'll edit this post with links when I find them unless some one beats me to it
Hey Dan do you think we could skype and you could talk me through it, it would be much easier?
Burky1996 said:
Hey Dan do you think we could skype and you could talk me through it, it would be much easier?
Click to expand...
Click to collapse
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Danny201281 said:
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Click to expand...
Click to collapse
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
Burky1996 said:
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
Click to expand...
Click to collapse
Okay try this. Download the OTA but select the option "Install Later" connect your m7 to your pc and browse your storage. In the download folder on your phone you should find the OTA in zip format. Copy it to your pc.
Now open the OTA zip on your pc. Inside you'll find another zip called "firmware.zip" extract it then open it. Inside you'll find a recovery.img. extract the recovery file and flash it with fastboot. Now reboot to android and continue to install the OTA. :fingers-crossed:
Sent from my SM-T230 using Tapatalk
im going to have to unlock the boot loader again and then do it
Burky1996 said:
im going to have to unlock the boot loader again and then do it
Click to expand...
Click to collapse
Yes you will need to unlock the bootloader to flash the recovery, Dont forget to fastboot erase cache after flashing the recovery that is cruicial. You don't need to be relocked to install the OTA though.
When you select install now, the device should reboot to the Stock Recovery. At first the screen will just be black for a short while. Then you'll see an image of a phone with a Green ring and download arrow. If you hold Volume up and press the power button you will see the Stock Recovery and its progress in installing the OTA.
I'm not sure why your device was hanging on boot after installing the OTA. Maybe a bad recovery.img. that's why I say to get the recovery from the OTA file.
its still not working so i mite just install twrp and restore to cm12.1
Burky1996 said:
im going to have to unlock the boot loader again and then do it
Click to expand...
Click to collapse
Yes you will need to unlock the bootloader to flash the recovery, Dont forget to fastboot erase cache after flashing the recovery that is cruicial. You don't need to be relocked to install the OTA though.
When you select install now, the device should reboot to the Stock Recovery. At first the screen will just be black for a short while. Then you'll see an image of a phone with a Green ring and download arrow. If you hold Volume up and press the power button you will see the Stock Recovery and its progress in installing the OTA.
I'm not sure why your device was hanging on boot after installing the OTA. Maybe a bad recovery.img. that's why I say to get the recovery from the OTA file.
Danny201281 said:
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Click to expand...
Click to collapse
could it be not working coz my hboot has changed to 1.51.
Burky1996 said:
could it be not working coz my hboot has changed to 1.51.
Click to expand...
Click to collapse
Your still stuck with this? Try starting the process over, but do not relock your bootloader at any point.
Wipe system data and cache partitions with TWRP Advanced wipe
Flash the Rom with twrp as a clean install.
Reboot and download the OTA. Choose install later, then copy the OTA to your pc. Extract the Stock Recovery and flash it with fastboot. Reboot and install the OTA.
But do not relock your boot loader. Because when you unlock the bootloader, it wipes the device including the data/preload folder. If the preload folder is not intact the OTA will fail
Sent from my M7 Running ARHD 92.x
Hi guys, since the development is started i think that we also need a way to restore the watch to the stock FW.
HOWTO:
- download from the following links the boot, recovery and system image;
- reboot to fastboot and:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
and then go to recovery and do a wipe data / factory reset.
LINK:
Boot
Recovery
System
UPDATE: MarshMallow
system
boot
recovery
When I boot to recovery, all I get is the Android on it's back with the Red ! triangle.
Also, will I be able to re-lock the bootloader?
pTeronaut said:
When I boot to recovery, all I get is the Android on it's back with the Red ! triangle.
Also, will I be able to re-lock the bootloader?
Click to expand...
Click to collapse
Did u try to touch the screen?
Skin1980 said:
Did u try to touch the screen?
Click to expand...
Click to collapse
Yes. no response.
Skin1980 said:
Hi guys, since the development is started i think that we also need a way to restore the watch to the stock FW.
HOWTO:
- download from the following links the boot, recovery and system image;
- reboot to fastboot and:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
and then go to recovery and do a wipe data / factory reset.
LINK:
Boot
Recovery
System
Click to expand...
Click to collapse
can you please help me with the step by step guide of flashing LG Watch urbane. I have downloaded from all the links you have given.
I am new to flashing anything to Wear.
@pTeronaut From what I've read elsewhere on this forum, it seems that if the recovery is doing that after a flash, you should boot into the bootloader and you should be able to get into recovery through there.
Do you think that is possible to return to Android 5 from Android 6?
Do you known a site (official if possible) to download the Android 5 ROM?
Thanks
bartito said:
Do you think that is possible to return to Android 5 from Android 6?
Do you known a site (official if possible) to download the Android 5 ROM?
Thanks
Click to expand...
Click to collapse
The links i posted are for the Lollipop Rom
Is there any possibilites to lock bootloader? I tryed fastboot oem lock but i`ve got: FAILED (command write failed (unknown error))
Got it to work. Just installed latest adb and rebooted the computer.
Do we have md5sum's for these?
So if I have v6 on my watch can I downgrade back to V5 so I can have root? for some reason I unlocked the bootloader, but I can't get TWRP or root on the watch since the last update. I'm familer with android but this is my first smartwatch.
Anyone still on these forums? I bought this watch off swappa and the guy had AW 2.0 installed on it. I wanted to unlock the bootloader and stuff so I did. Once the watch rebooted it is now stuck on the bootanimation. It's not bootlooping because it's not going back to the LG logo. It's just staying on the Android bootanimation. Any help is greatly appreciated.
spc_hicks09 said:
Anyone still on these forums? I bought this watch off swappa and the guy had AW 2.0 installed on it. I wanted to unlock the bootloader and stuff so I did. Once the watch rebooted it is now stuck on the bootanimation. It's not bootlooping because it's not going back to the LG logo. It's just staying on the Android bootanimation. Any help is greatly appreciated.
Click to expand...
Click to collapse
1. Go to bootloader
https://www.youtube.com/watch?v=-BshOHvAKUw
2. Install this recovery: https://dl.twrp.me/bass/twrp-3.1.0-0-bass.img.html
3. format system and data partition to ext4 and go to sideload
4. Do only step 1 and 6 from this https://forum.xda-developers.com/showpost.php?p=71751597&postcount=5
I installed AsteroidOS and need the stock userdata partition, however I cannot find it. Do you know where can I get the img?
majekqwert said:
1. Go to bootloader
2. Install this recovery: https://dl.twrp.me/bass/twrp-3.1.0-0-bass.img.html
3. format system and data partition to ext4 and go to sideload
4. Do only step 1 and 6 from this https://forum.xda-developers.com/showpost.php?p=71751597&postcount=5
Click to expand...
Click to collapse
Same problem, how do I install the recovery I am very new to this
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
To clarify:
- I already tried erasing userdata and cache from fastboot
-I already tried flashing recovery images from twrp, stock and bluspark
Thanks in advance guys.
Pavononer23 said:
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
Thanks in advance guys.
Click to expand...
Click to collapse
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
rykanator said:
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
Click to expand...
Click to collapse
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Pavononer23 said:
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Click to expand...
Click to collapse
can you boot into the bootloader/fastboot?
rykanator said:
can you boot into the bootloader/fastboot?
Click to expand...
Click to collapse
Yes I can
Pavononer23 said:
Yes I can
Click to expand...
Click to collapse
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
rykanator said:
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
Click to expand...
Click to collapse
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Pavononer23 said:
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Click to expand...
Click to collapse
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
rykanator said:
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
Click to expand...
Click to collapse
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Pavononer23 said:
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Click to expand...
Click to collapse
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
rykanator said:
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
Click to expand...
Click to collapse
It is not working, I think I lost my Oneplus 3t...
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
I mean idk if you wanna do this, but you could always try to "format userdata", then flash the stock recovery, and then sideload OOS. but you would lose all of your data in your internal storage, and it's still not a guarantee. there are some posts about doing a full wipe and starting from scratch. I'd look into those. Best of luck reviving your OP3T
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
nicknacknuke said:
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
Click to expand...
Click to collapse
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
pitrus- said:
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
Click to expand...
Click to collapse
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Pavononer23 said:
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Click to expand...
Click to collapse
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
przemcio510 said:
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
Click to expand...
Click to collapse
I can't install the drivers:
-First, stupid Windows policy saying that its driver is the best one available.
-Second, choosing from a disk to avoid one saying that the driver is not a x64 one.
Pavononer23 said:
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Click to expand...
Click to collapse
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
redpoint73 said:
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
Click to expand...
Click to collapse
There were no errors when flashing TWRP. When I tried rebooting using fastboot(fastboot boot recovery.img) it got stuck in the message saying booting up... and the only thing that changed was that my phone left the bootloader screen to a screen with the Oneplus logo and a fastboot mode message under it.
The command I used was fastboot flash recovery recovery.img(Name of the actual recovery file)