Hi,
I just packed out my old Moto 360 2nd Gen. which was Pre Unit Device with unlocked BL + already rooted.
I am currently connected over bluetooth debugging and pulled the build.prop from /system.
I wondered if it might be possible to lead to believe that it's not a developer-rom and actually update to latest firmware.
Do you think that might be possible?
Hi. i got the same watch. a pre-unit developer edition with these wierd stickers on the flat tire area. now, a few days ago, i assume the watch tried updating, and now it's stuck on the boot animation (the one with the four animated symbols) and won't proceed past that.
i've tried factory reseting, but nothing works.
as for your question, i was consistantly updating the watch, with no issues.
but as for me, i have a soft? bricked watch, and i don't know how to fix it. any suggestions?
Related
Hey There,
I need a little help with my Transformer Prime Tablet. A week ago I bought myself an new one. Since I am in China I got only the Chinese version of it. Which usually isn't a big deal but from time to time a few strange things happens with those devices. This time it's the fact that that there is now play store installed at the tablet. You can install the play store by yourself but since there is no option to add a google account the play store is useless and quits immediately without out any message or what so ever.
Ok, no big deal I thought. Just flash it and everything will be fine. Since I did do that already with plenty of different devices before I have been confident it will work this time as well. At least that's what I thought. I unlocked the tablet. After quite bit of trouble I could flash a new bootloader as well. But thats it then. I tried differend bootloaders like cwm and twrp, also in different versions.
The flashing itself is no problem but when I try to boot into bootloader it just shows that it will start the bootloader now and thats it. Then it just keeps showing this message and hangs. Android itself is booting flawlessly. I really don't know what to do anymore. Everything work like it should. Adb is working, fastboot works and Android as well. Only booting into bootloader is not working.
So here's my question: First, has anyone an Idea whats going wrong here and what I can try to do about? And second, is there any way to flash a new rom through fastboot or with adb or what so ever?
Any help would be much appreciated.
So bad news is I actually managed to brick my phone by trying to flash CM with CWM on my p769. I was sure I had unlocked my boot loader, but lo and behold it rebooted into a Security Error.
Hard reset? Nope, wouldn't work. Went to the Android, then rebooted into a Security error.
SW Update mode? Nope, just booted into security error.
Re-flash KDZ? Nope, utility wouldn't see it and the hardware kept connecting and disconnecting (with two diff cables and an on-board USB port).
It bricked so hard the guy at my local t-Mobile store couldn't even re-flash it. Bright side is the insurance gives it a lifetime Warranty, so $5 processing and my new phone should be waiting for me when I get home. I love my phone, despite some of its idiosyncrasies (No App2sd? Seriously?), so am nowhere near switching off the model, but figured I would share my tale for the benefit of others.
Just a cautionary tale for people. I just wish it was easier to root
ca not brick this phone
ErroneousBosch said:
So bad news is I actually managed to brick my phone by trying to flash CM with CWM on my p769. I was sure I had unlocked my boot loader, but lo and behold it rebooted into a Security Error.
Hard reset? Nope, wouldn't work. Went to the Android, then rebooted into a Security error.
SW Update mode? Nope, just booted into security error.
Re-flash KDZ? Nope, utility wouldn't see it and the hardware kept connecting and disconnecting (with two diff cables and an on-board USB port).
It bricked so hard the guy at my local t-Mobile store couldn't even re-flash it. Bright side is the insurance gives it a lifetime Warranty, so $5 processing and my new phone should be waiting for me when I get home. I love my phone, despite some of its idiosyncrasies (No App2sd? Seriously?), so am nowhere near switching off the model, but figured I would share my tale for the benefit of others.
Just a cautionary tale for people. I just wish it was easier to root
Click to expand...
Click to collapse
follow this thread and you will be ok... http://forum.xda-developers.com/showthread.php?t=2234665
Thx. My new phone is actually waiting at my door right now, but if I break that one... lol
So I've seen this question covered a few times but not sure if my situation is the same as the ones that have been answered prior.
I have a 1-1/2 year old S4 that I rooted when I received it, using whatever flavor of the day rooting method was out there. I have never used any kind of custom firmware with this device, just rooted and disabled some of the built in features like jedi hand wave mode, follow my eyes, etc. (yeah I know those aren't the real names)
Over the past few days I've been noticing apps not being able to open, the screen would go black for a second like the app was launching and then it would return to the home screen. Also a few times the notification bar would flicker while trying to open an app. So I decided to reboot today and now it is stuck at the verizon boot screen.
I've tried all of these options:
Pull battery for 30 sec, remove and replace sim card, replace battery boot.
go into recovery mode and wipe cache
go into recovery and do factory reset
Of course none of these options worked, which is why this thread exists.
now the next option I'm seeing when I'm looking for an answer is either
replace/update the firmware
return to verizon
I guess I'm wondering if the first option is even available to me since I never flashed anything custom before? If it is, I'm sure there's a wonderful thread here that would walk me through the process, if anyone would be so kind as to point me there. I'm just a little confused over what's available in my particular flavor of firmware.
Or, is there a verizon flavor that I could update to and be able to root as well? I remember when I originally rooted it was suggested to keep the older version so you wouldn't get locked in to not being able to do any custom stuff, but not sure if that's been overcome since. I don't need anything fancy, just a rooted phone works for me.
If updating is not an available option for me, is a verizon return my next step? And if so, can/should I remove signs of rooting before sending it in?
So I admit I am an idiot and did this to myself. I installed the latest FireOS OTA through TWRP then thought to keep TWRP I would install it before I rebooted. I know I probably should have read threads about keeping root and the horribleness of 5.6.0.1 but I did not. So I can boot into the OS and I can boot to bootloader but I have no recovery at all. Any one know how to recover from this? Found out the unbrick method I have used before does not work. Fastboot give me an error about locked hw.
Been working on this anyone know or have a fastboot zip or image. I am getting a errors trying to flash the amazon bin with fastboot.
I know I am the only one posting here. I read through a bunch of threads that seem to be people in the same issue. I have now managed to get it stuck in demo mode. I also cannot seem to accomplish much from fastboot because I get a locked hw error. Bought a couple for parts HD6s off ebay. So hopefully I can make something work and get at least one working tablet. This has really put a damper on trying to create a device tree to try and build cm12.
Closer to being a brick. Some how I managed to have root in adb and managed to wipe all. Which I guess really meant all. Now all I get is the amazon logo. No desktop. No adb. No way to get to fastboot.
So ebay tablets came in, bout a lot that had 2. The one was listed as a demo model, so a simple ;demo in the search and resell the device and viola fully working tablet. It still had 4.1.1 on it so a simple update to 4.5.3, Kingroot, and TWRP install and back on CM11. The second was "black screen" so I assumed bricked as it did not seem to turn on when plugged in, initially. Tried running through unbrick but nothing from ./reader.sh so assumed on newer FireOS that blocked that function. After setting the first up I was rearranging my stack on now 2, what I thought where, badly bricked devices. Hit the power button and booted to lock screen with 7% battery. So I now have an extra HD6 to mess with. Best part is I got both of them for $20 total.
I waited to write here, if the March 2020 patches solved the problem, but unfortunately it is not...
several nokia comunity users have the same problem and nokia is not responding about It.
having Nokia 8.1, I gave Nokia 7.1 to my girlfriend last year ... great smartphone, the Android 10 update work very well, but the February 2020 patch was a disaster!
Probably it didn't install well, and then the phone asked for a factory restart.
the problem is that the Factory reset did not come back to a pre-February patch state, but always brings it to the point of "restarting the phone to finish installing the February patch".
and immediately the restart is requested, which can be postponed, but not indefinitely, so after fifteen days the smartphone restarts by itself, and freezes again asking for a factory reset!
in an endless loop!
I think I have to do a system flash to bring the phone back to a previous stable state, right?
Can you help me on the procedure to follow?
I have never unlocked the bootloader and all the rest
thank you guys
My friend has the same issue.
well you have two solutions here
1) Pause your updates so your phone never installs them
2)Get your phone flashed with the stock firmware , and if you want get it unlocked.
I have spent about 2 months trying to fix the issue but in the end I got the phone flashed which fixed the problem.
The issue comes due to your phone not being able to verify the selected partitions for boot which is why it asks you to reset.
thanks for the answer!
the guarantee is still active,
I think I will send it to nokia assistance, as soon as next week I will be able to see my girlfriend (for the emergency covid19 I haven't seen her for 60 days, but next week there is the unlock down).
meanwhile I took for her a Nokia 4.2 to be used as a replacement.
I hope Nokia's lab assistance will flash the system quickly and better than what I could do
PCIHD said:
well you have two solutions here
1) Pause your updates so your phone never installs them
2)Get your phone flashed with the stock firmware , and if you want get it unlocked.
I have spent about 2 months trying to fix the issue but in the end I got the phone flashed which fixed the problem.
The issue comes due to your phone not being able to verify the selected partitions for boot which is why it asks you to reset.
Click to expand...
Click to collapse
Can you show me to a thread or video for option 2)?