Any news from people who received 2.006sp update

I pulled the update .... I selected the system update option, then selected update Kyocera software. It took about ten minutes from start to finish.
 
Let me know if anyone tries it with root access. I wanna know if it will brick or still retain superuser.

Sent from my Echo
 
It bricked my rooted echo but a sprint store tech was able to re-flash the system. The flash loaded the 2.006sp version of the rom and the phone is working fine. Except now the known rooting methods are not working. There is a bit a discussion starting at heretheecho about this issue.

It might get annoying trying to block the push from this point forward so a work-around would be appreciated.
 
The new update totally crashed my phone, I haven't been able to get to a Sprint store yet. Any idea how the tech got it going, Sabbys?
 
There pushing stock images to the phone.

If you have adb on your PC and get stock images from Kyocera, it could be done.
 
I decided to go for the update with my echo. I first defrosted all apps that were frozen. I then downloaded Vodoo OTA root keeper to have a backup of the SU binary. I temporarily removed root with the same app. I then tested to make sure I had no root and none of my apps that required it would work.

I went ahead with the update and of course still ended up with an error. Update not finished please contact sprint, or something like that. The phone was in endless boot loop and would not start. I did the power and volume up on restart for boot loader mode. I tried so many button combinations for manually entering recovery and could find nothing. I plug it in to my PC, try to get ADB to recognize it, and it won't see it. This is all being done with the notification light on and in yellow.

I unplug it and restart the phone. While its still booting over and over I connect it to my PC again. I notice when Kyocera comes on the screen my PC will pop up, removable drive found, and it would be there for about 2 to 3 seconds. Everytime the phone restarted my PC would see it for just a few seconds.

I open ADB, continually type adb devices in the command line and it comes back with the string I was waiting for. Now that I know it will be seen for those few seconds, I type adb reboot recovery over and over, and eventually got the command pushed to my phone.

I got into my custom recovery, restored my nandroid and I was back to good! The lesson of this story, enable USB debugging option in your settings and make backups often. I got lucky that I was able to restore my phone.

I just figured I would share this in case anyone else with root was thinking of trying.
 
I purchased this device just as a new toy/mini laptop. Im a big supporter of a nand backup before any rom push or any updating, but i figured an official update, hmmm nothing can go wrong, and wham, bricked device, it hangs at the kyocera logo screen I didn't root the device, it was basicly stock. I tried the fastboot -w through ADB, but that did nothing but tickle the beast. Does anyone have any ideas or suggestions, I would greatly appreciate it.

$aGe
 
If you didn't have USB debugging enabled then adb nor fastboot will see it. I think your going to need to go to the sprint store.

My PC only saw it for a few seconds everytime it restarted.
 

Latest posts

Trending Posts

Forum statistics

Threads
956,494
Messages
6,968,540
Members
3,163,555
Latest member
elementssupply01