So I tried to black list some icon via adb and it seemed to work fine. Until a few hours late I restarted my phone for whatever reason and the UI crashed and i had to Factory reset from recovery. Any ideas what went wrong?
Related
I tried out rooting my phone earlier today, and it was working fine, I then got the TW4 launcher, installed that and then it showed me as stuck on my contacts screen and I couldn't get off, I rebooted my phone and now I'm stuck on the galaxy s plus boot logo, but the phone is actually on in the background because I can hear it getting texts, what do I do to fix this? I'm a complete android noob and have no clue what to do now and because I've rooted it I've voided the warranty, help would be greatly appreciated!
I had exactly the same thing (4 times lol) because of TW4manager and I don't think we are the only
I just reflash the rom but you lose all your data
http://forum.xda-developers.com/showthread.php?t=1297400
Same problem.
Solution is flash new rom with odin.
Next time use this TW4 luncher, it works
http://forum.xda-developers.com/showpost.php?p=13435895&postcount=21
It seems to me there IS another way to fix this. However, I was stupid enough to make it impossible to try in my case.
If your device is rooted (has su), and has USB debugging enabled already, you may try to do the following:
pcuser$ adb shell
$ su
At this point, if you have the confirmation dialog appearing, that dialog will appear and "stop" the boot animation. You will be able to use the contacts app and the notification area...
Then, with adb, you should be able to uninstall TWManager and install the newer version. The notification area should show that a new app has been installed and you should be able to start it from there (and update the TW to a workable version).
However, I clicked Deny on the su prompt, the checkbox was checked and now I can't get su in the shell...
Could someone test this and post back results?
thank you for the replies! I flashed another rom and it fixed it and because it's on 2.3.5 now I have no battery issuses.
Starting this morning, my Nexus S is stuck in landscape mode.
When I fist boot up the phone, it seems to launch directly to the desk cradle mode, but it has never been connected to one.
Everything is landscape even the launcher. I can't use the phone because I can't reach the OK button for the SIM card PIN enter screen.
Factory reset didn't help. The inital setup is portrait, but after that it reverts to landscape.
Any ideas? Might this be a hardware problem?
EDIT: Android 4.0.3
EDIT2: I applied the VQ8PQk_V.zip OTA update manually to my stock 2.3.6 version. After a factory reset, the phone works as normal until the first reboot. The accelerometer is still working, i tested it after a factory reset before rebooting the phone.
Up
Sorry me for waking up this thread from his graveyard after 3 month.
I have an i9023 with the same issue of Tocharius:
my device is stucked in landscape mode and when i try to turn on it I cannot enter PIN code because OK button is outside the screen. The only way I have to make it works is to wipe data partition and everything works fine until first reboot.
In addition to this problem fastboot has stopped recognizing my phone, while ADB still recognise it.
When the issue firstly appears I was under CyanogenMod 9 v6.0 (Kalimocho).
I tried to flash other ROMs, but nothing has changed.
I tried to revert to stock, but nothing has changed.
I tried to open the phone, clean every connector i found, but nothing has changed.
Someone can help me?
I got this problem too. Lately I installed CodeNameAndroid 2.0 http://forum.xda-developers.com/showthread.php?p=25941996#post25941996 and after reboot my phone got stuck in landscape mode. I tried to reflash the rom and everything was fine until a reboot. Wiping data and resetting factory helps until reboot. I flashed another rom http://forum.xda-developers.com/showthread.php?t=1588799 and again the phone was stuck in landscape after reboot. I tried all rotation settings but nothing changes.
I was browsing settings searching for something that could fix it and turned adb debugging off and on and now it is stuck in portrait mode.
So when trying to install the drivers to root the nexus 5 using the multitool (http://forum.xda-developers.com/showthread.php?t=2509428) I realised that I could no longer get to the recovery menu, instead my phone would show "qhsusb_bulk" in the device manager. So I tried to factory reset the device and it's now stuck at the screen with the android with the "erasing" text beneath it and the blue line. I'm not sure if it's actually doing anything but it has been like this for about 30 minutes now.
Couldn't find a similar answer so I had to post. Phone was working fine until today although I've been having more frequent reboots. Was on 38R with AK Kernel v.75. While browsing chrome, the screen suddenly went black. I thought it was a reboot but the screen never turned on again. Trying to see if there is a way to just soft reboot using ADB, but I'm not seeing the ADB Fastboot screen at all. Anyway around this?
Edit: Not sure what I did, but I tried fastboot reboot and it seemed to work again. Looks like I'll have to nandroid back.
sounds like a partition borked.
Just restore nandroid like you said and hopefully that fixes any issue.
Well here is how to do a soft reboot wth adb
adb shell
su
pkill zygote
How to do full reboot with adb
adb reboot
Hello, so i was using my phone last night browsing instagram, when all of a sudden it froze and restarted(happened to me from time to time), so i thought it will bootloop for a few times and it will boot up just fine. But no. It got stuck there and i could access recovery only when my phone has been off for 10 minutes, and fastboot was accessible at will. I accessed recovery a few times, and i tried:
Wiping cache and delvik cache - No luck
Let it charge into recovery to 100% overnight and try flashing in the morning
Wiping data - no luck
Re-flashing sultan rom - no luck, phone just freezes halfway into installation and restarts
Since i can only access fastboot, i tried some fastboot commands, but nothing serious(like flashing, formatting, wiping...), and cmd shows that they were successfully executed, but nothing happens with phone ("fastboot reboot" cmd)
Removing sim card - no luck (but i am desperate)
Usually when reboots happen, i can plug it in a charger, and it will power on with battery charging animation, but not these times, it just reboots at oneplus logo
On one occasion it got past the oneplus logo, and showed a small blue cyanogen circle, but it froze there as well.
I did not try sideloading, and nothing with adb, since i am not experienced in those fields
I had similar thing happen to me the night before, but it eventually turned on and i could use it whole day without reboots
Also it seems to have happened both times while battery was at around 15%
I live in a small city in Serbia where there are no professional who know these kinds of phones, so i can't take it to repair shop.
EDIT: I can enter sideload if that matters, and my pc seems to detect it, because i can hear windows chime
EDIT 2: i can no longer enter recovery, it just wont enter there anymore
Tried flashing twrp via fastboot but i get (command write failed too many links) error
I tried some repair shops they said it's the motherboard, so is it really dead, because i still have oneplus logo
Any suggestions?
MY FIX
I connected my phone to friends laptop and flashed stock cyanogen os 6.0.1, fastboot worked like charm and phone booted up just fine