Hello everyone. I am an old member, seeing as I registered almost four years ago, but I guess either your database was refreshed and it lost my username, or I only lurked. So, as the title suggests I have one of those lowly, inexpensive, down right cheap Kyocera phones. Here is what I have figured out so far. I was able to root it using Kingroot. That went splendidly, though because of my over adventurousness I decided to swap some apps out. I added a new launcher to the /system/app folder and wanted to upgrade the com.android.settings.apk with one from a newer build. This phone (was) running Android 4.0.4 Kyocera release r77 build date 2013. Apparently Kyocera loves to lock the bootloader so if I was able to spin a custom system rom I wouldn't be able to flash it. Another thing which discovered was upon boot up the system checks the integrity of app the system apps. If one of them fails the check it will not boot the system fully. I was able to recover the stock boot/recovery/system roms from a thread on here, but I seem to be stuck in a soft brick loop. One thing that another thread said, the thread that had the rom images, it said that you could used ADB to flash the roms to the phone. Thing is, when I boot the phone it restarts, and if I put it into recovery mode (press and hold volume down plus power for ten to fifteen seconds) the only options I have are "reboot system now", "wipe data/factory reset", "wipe cache partition." There is no "flash update from sd card" or wipe dalvik cache option. As I have said before, I could try to flash the rom to it using adb but I believe that wiping the system partition unset the USB debugging setting. When I connect it to my computer windows device manager notices the kyocera removable device for a second then as the phone reboots it goes away. Setting it into recovery mode does not make it show up in windows. Is there any way I can flash the stock rom onto it? Any android sdk or adb trick I can use that can boot it into some recovery mode? I was trying to see if I can get it to boot into download mode but seeing as it has soft keys and not a physical home button I do not know if I can manage that. I was thinking that maybe they tied one of the physical keyboard buttons to the home button but I have yet to uncover that one. Any help would be appreciated.
Zestypanda said:
Hello everyone. I am an old member, seeing as I registered almost four years ago, but I guess either your database was refreshed and it lost my username, or I only lurked. So, as the title suggests I have one of those lowly, inexpensive, down right cheap Kyocera phones. Here is what I have figured out so far. I was able to root it using Kingroot. That went splendidly, though because of my over adventurousness I decided to swap some apps out. I added a new launcher to the /system/app folder and wanted to upgrade the com.android.settings.apk with one from a newer build. This phone (was) running Android 4.0.4 Kyocera release r77 build date 2013. Apparently Kyocera loves to lock the bootloader so if I was able to spin a custom system rom I wouldn't be able to flash it. Another thing which discovered was upon boot up the system checks the integrity of app the system apps. If one of them fails the check it will not boot the system fully. I was able to recover the stock boot/recovery/system roms from a thread on here, but I seem to be stuck in a soft brick loop. One thing that another thread said, the thread that had the rom images, it said that you could used ADB to flash the roms to the phone. Thing is, when I boot the phone it restarts, and if I put it into recovery mode (press and hold volume down plus power for ten to fifteen seconds) the only options I have are "reboot system now", "wipe data/factory reset", "wipe cache partition." There is no "flash update from sd card" or wipe dalvik cache option. As I have said before, I could try to flash the rom to it using adb but I believe that wiping the system partition unset the USB debugging setting. When I connect it to my computer windows device manager notices the kyocera removable device for a second then as the phone reboots it goes away. Setting it into recovery mode does not make it show up in windows. Is there any way I can flash the stock rom onto it? Any android sdk or adb trick I can use that can boot it into some recovery mode? I was trying to see if I can get it to boot into download mode but seeing as it has soft keys and not a physical home button I do not know if I can manage that. I was thinking that maybe they tied one of the physical keyboard buttons to the home button but I have yet to uncover that one. Any help would be appreciated.
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
If you can access your recovery it is already a good thing, try first to wipe data and see how it goes.
nilac said:
Hi and thank you for using XDA Assist
If you can access your recovery it is already a good thing, try first to wipe data and see how it goes.
Click to expand...
Click to collapse
So, I boot into recovery and I do the wipe data/factory reset then the wipe cache partition for good measure and it still halts on boot. Same thing. Boot, kyocera logo, virgin mobile boot splash, then it halts where it would normally go into android. Then it reboots. Rinse repeat.
Any suggestions? I sorta need the information off the phone.
Related
Alright. This is a 100% stock Nexus S- nothing "development" wise was done to the device, no system tools installed that could cause issues, basically nothing but basic apps loaded on the device.
It just started today. I was working on my bf's Vibrant (another, more successful story) and grabbed my Nexus and hit the power button and it did not turn the screen back on. Holding the power button down did not reboot the device, and none of the buttons would light up or function.
So, I pulled the battery. Now every time I try to boot, it hits the "Google" screen and stays put. I left it alone for 5 minuets hoping it would finish booting and nothing. The soft buttons will light up, and if I touch them they register the touch but it does not help the phone to boot.
I do know that the phone was basically dead right before this happened, and at first I thought it was just dead. However, its been on the charger for at least 30 minuets- which should have given it enough of a charge to boot up, and still nothing.
What could cause this issue?
I did install a couple of new applications today, and I know the market updated a bunch of them but they're all apps that I've had on several phones (minus the two new ones today) and have never had an issue with any of them. The two new ones I downloaded were OS Monitor, and a 2G/3G toggle for hopes of improving some battery life.
But those are the only two things I've done differently. I've only been using the phone for a week but I haven't had any problems at all, before this.
Now- if worst comes to worst I can seem to get into the bootloader, and through that, stock recovery. So I can try to do a factory reset and wipe cache but without a backup I really kinda hope thats a last resort.
Please help, and let me know if you need any more information.
Thank you!
I understand that you're fully stock which I assume means you have a locked bootloader (everything I say from here on out assumes as such)? First, I'm going to also assume that you didn't update to 2.3.3? If not, then follow the steps in this guide to boot into a custom recovery and from there go to backup and restore and do a NANDroid backup. Now go to mounts and storage and mount USB storage (or whatever its called, don't have my phone right here). Plug your phone into your comp and copy over whatever you'd rather not lose from your SDcard (just in case you have to wipe). Now download the 2.3.3 update from here and put it on the root of your SD card. Now go back and flash this. Reboot and see if you're golden. If so, great, if not try a factory reset.
If that doesn't work go through the steps again to boot into a custom recovery, you might have to unlock your bootloader and wipe all your data (again) and restore your backup and try doing a factory reset with that. Don't worry about unlocking the bootloader, it can be relocked with a simple command and it won't wipe anything to relock it.
Here is the command just in case:
Code:
fasboot oem lock
I got all the way to having clockwork recovery booted up on the phone, but nothing would mount. Everything gave me an error, and factory reset froze...
I don't think there is anything I can even do from here, is there?
Current Status of my TF700:
-Boot looping with Asus "Inspiring Innovation - Persisten Perfection" logo. Approximately 5 seconds between reboots, with a vibrate every time it reboots.
-It says "Device is Unlocked" in the top left.
-Holding power for a long time (over 20s) will shut it off, and vibrate, but then it immediately vibrates again and resumes the bootloop.
-I cannot get it into the bootloader with Power + Vol Down. That combination does nothing.
-If I use the pinhole button, as long as I hold it, the screen remains blank. As soon as I release it again, the bootloop resumes immediately.
-It does not get to the second "shiny" Asus logo.
-It doesn't get far enough to recognize a new firmware file on the microSD card.
How I got to this point:
Stock ever since I bought it up until a few days ago. I decided it was time to root, unlock, install TWRP, and install CWM. I never got that far.
1. I unlocked first. I believe it was successful because it has said "Device is Unlocked" ever since.
2. I tried to root with the debugfs method. It reported it was successful, but despite several attempts, it was unsuccessful.
3. I tried using GooManager to install TWRP. It never worked.
4. I discovered that I wasn't running the latest Asus firmware. I then upgraded it. It ran successfully. (V10.6.1.14.10)
5. I tried rooting with Motochopper. It reported success. But it didn't work. I then discovered it wouldn't work with V10.6.1.14.10.
6. I then tried installing TWRP via fastboot. It reported success, but Power+VolDown didn't get me into TWRP. Nothing seemed to load TWRP. In case it's relevant, I was having trouble where Windows was saying there was a problem with the Bootloader Interface Driver, and after several reboots, I was able to get fastboot to reportedly load TWRP. It reported success, but I never saw TWRP.
7. I booted into Recovery, the latest version that said something to the effect of, "USB recovery loaded" or something, with 3 icons: RCK, Android, and Wipe Data. This is the only recovery I was ever able to see, by the way. I then selected "Wipe Data" hoping it would give me a new starting point.
Once it rebooted, it has been stuck in this bootloop. Have I royally screwed myself, or is there a way to recover?
Please ask any questions, I will answer them to the best of my ability. In the meantime, I will hope to run the power down on the tablet in the hopes it will make a difference.
blauciel said:
6. I then tried installing TWRP via fastboot. It reported success, but Power+VolDown didn't get me into TWRP.
....
7. I booted into Recovery, the latest version that said something to the effect of, "USB recovery loaded" or something, with 3 icons: RCK, Android, and Wipe Data. This is the only recovery I was ever able to see, by the way.
Click to expand...
Click to collapse
Power+VolDown activates the bootloader menu - this is the screen with the 3 icons, where you can use fastboot. Since you needed to go there to install TWRP via fastboot, you should have known that Power+VolDown doesn't get you into TWRP - you'd have to press VolUp in the bootloader menu, to activate RCK.
blauciel said:
I then selected "Wipe Data" hoping it would give me a new starting point.
Once it rebooted, it has been stuck in this bootloop. Have I royally screwed myself, or is there a way to recover?
Click to expand...
Click to collapse
Selecting "Wipe data" from the bootloader menu with a broken recovery is the best known way to brick a TF700. This can only be recovered via nvflash, which you can't use since you never got far enough to extract the required files from your tablet while it still worked. Your only option now is a new mainboard.
Well, crap. RCK never did anything except show a loading bar then reboot.
Thanks for the reply.
...from my phone...
Anyone know of a place that sells 64gb mainboards? Not finding anything thus far...
...from my phone...
in case anyone cares, I swapped the motherboard out with one from ebay, and it booted right up.
so today i went to unlock and flash CM 10.1 on my tablet.
unlocking went smoothly
installing clockwork recovery went fine
installing cm10.1 and gapps went fine
once i booted into cm successfully, i checked the internal storage to see if it was clear. it wasn't, so i went to settings, backup and reset, and done a factory reset. now i'm stuck on this one screen and i dont know what it is.
i've held the power button and volume down until the tablet restarts and that results in the same thing.
i've tried power and volume up. that seems to start the tablet but the screen stays blank. i connected it to the computer and my computer installed an APX or APTX or something like that driver.
i've tried holding power, volume up and down, and that does the same as the power and volume up.
i'm very new to installing custom recoveries and roms. can anyone give me an idea on whats happened
Once you have a custom recovery installed you should NEVER wipe from the system settings or the bootloader menu. You wipe from your recovery.
If you do that, the bootloader seems to write a command to the misc partition to reboot into recovery.
And that is the loop you seem to be stuck in.
You can try _that's method to clear the misc partition from here: http://forum.xda-developers.com/showthread.php?t=2528313
Read the whole thread, salvation may be found in post 7.
If that does not work, you could try this:
http://forum.xda-developers.com/showthread.php?t=2399698
buster99's method may be another way to enable you to boot into the bootloader and flash a working recovery.
Good luck!
Thanks for the tip. I'll remember to do that next time. As of now it is fixed. I found a post on the cyanogen forum of someone who done the same thing. And he said he had to wait a painful 6+ hours of that screen I posted. Lucky for me it was only a ~45 minute wait. So all is good. Cyanogen is running. Recovery is working. All the stress is gone.
I have a Samsung Galaxy tab 2 GT-P5110 which I had successfully installed CM12 onto. I decided to set up work email which insisted that I encrypt the device. I believe that the process completed successfully.
At that point I decided that I would like to flash the device with CM12.1. Restarted the process (Factory reset, Wipe Cache, Wipe dalvik cache) and flash the new CM12.1 zip file from external SD card.
I cannot now get to the recovery mode and the device doesn't always boot into anything recogniseable. The screen goes black and blacker! I have manaed to get to the CM logo and then a screen asking me for the PIN for the encryption. The next screen tells me that the PIN is right but the data is corrupt. It gives me the option to "RESET TABLET" but that really doesn't do anything and won't let me in to the recovery menu.
I can get into the Download mode and connect Heimdall up to it.
Is there anything that anyone can point me at that will help me to unbrick it?
I hope I've passed on enough information to help. It seems to me I need to somehow re-format the internal SD but I can't get to any menu that will allow me to do that.
Any thoughts anyone?
Ta
Fixed It
I seem to have fixed it. I flashed the CWM Recovery rather than the recovery that I had been trying to use and I got control of the device back. Not sure why that made a difference but this time the Android Robot came on screen with the 3D polygon rotating inside it and it seems to be running correctly now and updated to Android 5.1 ... Magic!
Hello,
Anyone else having problems after this update? I did it now and my phone does not start anymore. Or at least it hangs in the loading screen with the red and 2 white dots.
I shut it down with power and vol + twice but with no effect. It does not react on the power cable being inserted. When it's powered off and I insert the cable it starts to the loading screen, currently showing 14 %.
How to solve this?
Thank you!
I can boot into recovery or fastboot. Not sure how helpful that is though.
try to format data if you're able to go to recovery. as long you have recovery and fastboot intact, it's basically not ****ed up yet
dewa5227 said:
try to format data if you're able to go to recovery. as long you have recovery and fastboot intact, it's basically not ****ed up yet
Click to expand...
Click to collapse
But how can I save my data? I mean when I'm in recovery I have to enter the password before, so the data gets decrypted. But with USB attached I can only see 5 files on my desktop computer.
I emptied the battery and loaded it fully, then restarted. After a long time it say "This device has entered an unstable state. Please try rebooting your device using the exit button below..." and so on.
I hope a data recovery company isn't the only solution.
Also, is there no way to repair it? Like running the update again or something?
Why is there no „apply update from adb“ option in the recovery menu of OnePlus? Apparently I could have used that to backup all my data from the phone.
I tried wiping the cache partition without success so far.
So did Android squeeze security so much that not even the owner can save his data in this status now anymore? A bit sad when they themself break the phone with an update then.
What about these recovery services that also recover data from harddrives? Do they break the phone when they do their thing?