Hello everyone,
Here is my problem of which I hope you can help me out.
I own a Allwinner A13 7 inch tablet, on which I installed the Cyanogen 10 mod (Due to restrictions I cannot place the link to the mod)
The problem is I probably installed the wrong touchscreen driver, so the tablet boots perfectly into the Mod but I can't do anything.
Normally it would be no problem to just put back my backup, but I can't get it to boot into CWM.
In the first place I rebooted into CWM to instal the mod by adding the following command through the "terminal app" before rebooting,
Command: "echo -e 'boot-recovery\0' > /dev/block/nandf; sync"
Now I cannot use the screen so i cant use the terminal.
I also cannot use ADB because USB debugging is standard switched of after flashing a new MOD.
Does anyone know if there is another way to get into CWM??
Thanks a LOT!
Thanks a lot!
I will have a look
Do you by change know where to get a working stock rom? I flashed one which i found using google a couple of times but it only results in a Boot loop (I have no luck at all!).
Thanks!
Update: found a stock version that works. But no my touchscreen is inverted.
Also I probably made another **** up, because I accepted the format option of Livesuit, so now I lost my backup.....
Related
So, it seems I've broken my android device down just right after I bought it.
I tried to enable connecting to AdHoc wi-fi network on my laptop following a guide from galaxytabhacks.com and in order to do that I needed my device to be rooted and busybox installed. There were no problems with the first step, but my device crashed after installing busybox: after Samsung logo appears, I see artifacts on the screen and nothing happens.
I performed wipe data/factory reset via ClockworkMod but it didn't help.
Now I've formatted /system and I'm gonna download full version of official firmware and flash it using Odin. Am I doing it the right way? Will my device survive after crash I've just described?
Thanks in advance.
Hi
Seems I have the absolute identical problem...
Did you find a way to solve it?
Thanx in advance!
Hi, If this thread is in the wrong forum,please move it.
I have a rooted Xperia Neo V (2.3.4 gingerbread). I started to do some changes to build.prop. I mistakenly changed the SDK version to 16 (although the original was 10 I think) and restarted. upon restarting,Google play and SuperUser crashed. I tried to launch some other apps but they crashed too. I could install ICS apps but they crashed as well.. only some small apps work including the stock apps. Now I can't reverse the change because whenever I open build.prop editor, it asks for root but SU crashes denying it..I tried factory reset,Unrooting and rooting again but same problem..I tried adb pull/push and successfully got the file but I can't send it back because the system is read/write protected or something...to change the read/write thing I need Su permission which I already can't get..I tried installing CWM recovery but now when the phone reboots a blue light flashes for some time and if I press a button(e.g volume down) the phone is stuck there until I take the battery out.The phone only boots up successfully If I don't touch it while it is booting up.
I have a backup of build.prop that I made with Romtoolbox.
What should I do now? Need some help.
Bump?
Help is needed Guys!
Seriously nobody on Xda forums can help me?
Wow. Nobody can help me here?(Bump)
this place is dead
So a friend of mine soft-bricked his old galaxy s2.
The phone is running a custom android 5.1 or 6.0 (I don't remember) that i flashed for him a few months ago.
He said he just disabled the google app (not sure why he did that) and the phone crashed and is now stuck in a bootloop.
I'm not sure why it would prevent the phone from booting at all, maybe the app is an essential part of the system now
Anyway I'm trying to enable the app back and hopefully fix the phone without having to wipe everything and flash back the system.
Does anyone know how/if it's possible from an adb shell in recovery mode ?
http://android.stackexchange.com/questions/56620/enable-and-disable-system-apps-via-adb#56621
thanks for the help but unfortunately i already tried it and the pm program doesn't work. Probably because i'm in recovery mode. Maybe i need to chroot or something?
Not sure how to do it on android
Hello!
My dad was using Nokia 7.1 for a while but recently he asked for help with his phone which is constanlty restarting... Looking into other threads, I can see it is kind of known problem, so I hope you can help me somehow. The phone is running now on 00WW_3_51F. He doesn't remember what was recently done with the phone but I guess he simply updated it do Android 9.0... When I power on the phone, it boots correctly but restarts after few seconds (sometimes it's longer, up to 1 minute).
- I have already reseted phone to factory default but problem remained.
- I have tried to boot it in safe mode but same problem occurred.
I managed to access Settings>Advanced>Updates and noticed that there is an update available (V3.54H) with size 1299.4 MB. When I started to download it, phone crashed...
I was able to download V3.54H OTA from another thread in this forum with size 119MB (pretty weird...) and I am wondering if there is any chance to update it manually from SD Card or Fastboot. Assuming there is V3.51F version installed, can I simply execute command fastboot update update.zip in fastboot? Will it install only this patch to exisiting OS or replace it?
Do you have any other ideas how to fix it?
Thanks!
Hi
Today after installing the update to xiaomi.eu rom, Android 10, my touch screen just died. I tried flashing 3 various roms by MiFlash with no success. I am able to use fastboot, adb and install TRWP but no matter what I do the touchscreen is dead making the phone useless.
When I boot it up I get asked to unlock it by providing the password to my mi account, which previously worked, but currently I'm unable to use my phone.
Anybody had a similar issue? any way to fix it?
Did you choose clear all option when flashing from fastboot
Yes, with no result unfortunately.
Can you use the touchscreen while in TWRP/recovery mode? If you have a OTG cable you can connect a normal USB mouse to your phone and use that to navigate. Maybe it is just locking up at the password boot stage?
Try to flash it back to stock with stock recovery with a different build date preferably 9 and see if you can wipe it that way......
will try both ideas later today
SOLVED
I finally managed to get it back to life. It turned out that I must have damaged the touch drivers and flashing the phone by fastboot didn't help at all as the drivers are located on prevent partition (as I was told by someone)
So the thing I did was to flash a custom kernel with touch drivers. I used franco kernel kernels.franco-lnx.net. First I installed (using physical mouse) xiaomi eu android 9 rom, than I flashed the franco kernel for android 9. At that point the touch screen came back to life. Afterwards I was able to update to xiaomi eu android 10 rom with no problem.
Hope it can be helpful for anybody with similar problem.