Would appreciate the help
First the brief version;
Motorola droid (sholes) tried flashing a new rom and the touchscreen no longer works.
Have researched for days with no luck and have tried a restoring a back. No luck.
Now if your still reading this is the more in depth version;
Rooted my sholes (along with a thunderbolt) many months ago, enjoy being rooted. However recently the droid stopped connecting to wifi tether from thunderbolt. So I decided to try another rom. Well soon as I rebooted to the activation screen I realized there was an issue, the touchscreen did not work at all. At first I thought that the phone had finally given out as i had dropped it and cracked the screen months before.
As it happened I had another Droid laying around that was stock. So I rooted it and installed the same Rom (I don't mention the rom because I am not 100% sure which it was). Got to activation page and realized I had really messed up.
Can anyone think of a solution? (I believe I've narrowed it down to the kernel being the issue)
As the phones sit here is the software information I can tell you
Cracked Screen:
Android version 2.3.7
Baseband version C_01.43.01P
Kernel version 2.6.32.9-cm-stk [email protected] #1
CPU info ARMv7 Processor rev 3 (v71)
Mod version CyanogenMod-7.1.0-Droid
Build number Gwk74
*Phone keeps coming up with a force close for android.process.acore if that is helpful
Noncracked Screen:
Android version 4.0.3
Baseband version C_01.43.01P
Kernel version 2.6.32.9-cm-stk [email protected] #1
CPU info ARMv7 Processor rev 3 (v71)
Mod version CyanogenMod-9.0.0-RC0-Sholes-CDMA-KANG
Build number ICL53F
This is my first time posting here and I am fairly new to rooting so hope I have asked for help correctly and provided the information that is needed.
Thanks in advance
I had the same issue, and it's been touched on in threads of ROMs it affects in the dev section.
I've been told the touchscreen is stuck in bootloader mode. I was able to get mine freed up by restoring a backup. Not sure if if came free after the initial boot, or a reboot. YMMV, but worth a shot as restoring a backup won't worsen your situation and just may work!
Related
I have an SCH-i800 that I have CM9 (p1c 9.1.0) installed on. I have been using it for several weeks with no problem. Since I am planning on going on a trip, I decided to active pre-paid Verizon service for the tablet. At first, I attempted to activate the device. It went through the phone call but after a minute, it just sat at activating. That is when I noticed that the radio state in the status bar had an X on it. I rebooted the tablet to try again and got "com.android.phone has topped unexpectedly". I re-flashed CM9 (at the time I was using 9.0.0) and it worked again. Activation was not necessary. After a day, the error came up again and radio state went to off with an X. I tried 9.1.0, same problem after a day. I even tried a nightly CM10, same problem. Reboots, cache wipes, permission fixes do not make it work. The error persists until a re-flash of CM. I see on the Support Downloads for the Verizon Tablet, there are two modem files. My baseband version is currently S:I800.0.3V.EI04. I have attempted to "flash" these both via Odin (which failed after a couple minutes) and ZIP (which looked like it worked) to the EC02 on the site, but my baseband doesn't seem to change.
So my first question is, is there a how-to on flashing as I have searched high and low on one for the Verizon Tab specifically, and have yet to find one. Is there a ZIP file that is specifically meant for the i800? I am almost certain this is my problem and that a downgrade (this tablet when stock was updated to the latest Verizon image).
My second question is, has anyone else experienced this? Is there someone that is using a CM9 Verizon tab with EI04 baseband and not have this problem?
Is there a way I can track down what crashed the program? I have tried logcat, but it doesn't appear to give me much detail other than to tell me that it stopped.
And if you ask, no I did not use the Verizon service with this tablet before putting CM9 on it, so I wouldn't know if it worked before.
Any input that someone could provide would be useful. Thanks!
Hello XDA forum members,
I couldn't find my specific issue in the search so I thought this was the best place to ask.
I recently acquired my third A855 Verizon Droid from a family member and I can't get it to boot. He previously had it rooted, but I am not sure which firmware.
Upon start-up, at the activation screen, I get an unlimited loop of this error:
The application Dialer (process com.android.phone) has stopped unexpectedly. Please try again.
First off, I am not sure which rooting guide I should use on this phone that would be best, or which is the latest version of firmware that runs stable (my current build on my other phones is not very stable at all... Kernel: 2.6.32-lowV-1.0Ghz-ChevyNo1 #53111
Next, would rooting this new phone solve the problem? I tried to re-update the firmware with the same version, but the same issue persisted; don't think my version is good anyway...
Just looking for any help I can get! Thanks guys!
To the top!
Just a suggestion, but you might try taking the device back to stock first. If you don't know what firmware you're starting with (given unit age or previous operator skillz) then a fresh start might help you on your way. I've always found ChevyNo1 to be very stable on my D1, but take that FWIW. You might try Steel Droid, if you're looking for something fresh, but I'm not sure it's the ROM you're using. As for rooting, I just used super one click. real simple and yeah, that could help with your install if it's not already rooted.
Hi Guys,
Since last week I have been having the issue of 'not registered on network' and i have read every form and anything and everything google has to offer to fix this.
My trusty note has never given me any issues till this happened.
After reading threads extensively i have tried the various methods i came across.
I rooted the phone (originally it was all stock nothing changed till this problem) installed custom roms it made no difference,. Flashed various modem versions still no joy.
My imei is still the same as it should be no changes.
I have full signal strength. I have tried everything please advise!!
GT N7000
4.1.2
Base - n7000xxlb2
Kernal - 3.0.31-1103517 [email protected]
Build- jz054k.n7000xlt9
Is there an alternative to Ariza patch which will work on the orginal note ?
all suggestions welcome
Hello XDA
I bought a HTC Desire 626s from Metro about 3 months ago, and occasionally or about every 6-12 hours I get a crash that has some really odd side effects as well as being just plain annoying.
I've attempted to do research on "0x776655aa" but mostly what I see is kernel code and no description at all other than a post of Cyanogenmod Forums of what looks to be protected.
Here are some details about my phone's environment:
Rom: Stock 5.1 (RRU)
Rooted: Yes
Bootloader: Unlocked
Recovery: TWRP (twrp-3.0.0-1-a32e)
Thing's i've attempted to solve the issue:
Extensive amounts of googling with no luck
Flashing stock recovery, factory resetting twice, using someone elses boot.img
Side effects:
Sometimes WIFI credentials are forgotten
Rare "Android is upgrading": "App x of y"
Crash log: h t t p://hastebin.com/ixaqopipaw.md
Can someone shed any light on this issue?
Best regards,
Elycin
Hey all,
Looking for some assistance here. I apologize in advance for not having specifics on everything, but it's been a couple years since I've needed to do anything with this phone (SM-G900A). I picked it up used a couple years ago and shortly after, I did a NOX unlock and rooted the phone for two reasons - using Titanium Backup and to unlock the WiFi hot spot. I recently noticed that something had happened and my root access wasn't working correctly- guessing from one of the OTA updates that was attempting to occur on my phone. I say attempt, because I don't believe they ever successfully installed since they always seemed to error out. I'm currently on StraightTalk, not an AT&T customer. Something weird was up with it though, because I could never uninstall the Xposed Framework or app, yet Pokémon Go was recognizing it was rooted and blocking my access. I should also mention that I had towelroot running on the phone and it's showing the custom unlocked padlock on startup.
Fast forward to last night- I wanted to return it back to the stock ROM so I did my research, found a couple different tutorials that included the correct ROMs and applied one - G900AUCU1ANCE_G900AATT1ANCE_ATT.zip. After flashing, the phone will not boot and freezes halfway through the swirls around the Samsung logo, then goes blank. The blue notification light also stays lit on the phone.
Thinking it was most likely bootloader related, I found another ROM that included separate AP, BL, CSC files. I attempted to flash the bootloader, which failed and I got the following error on the phone - SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
At any rate, it seems like my boot loader somehow got corrupted or isn't compatible with this ROM, but I was hoping some of you experts out there could provide some answers. At this point my phone is dead, so I'm hoping I can get it restored very soon.
Thanks in advance guys!
The issue identified in this thread (http://forum.xda-developers.com/galaxy-s5/help/g900a-stuck-samsung-logo-black-screen-d-t3050369) seems very similar to mine as well as what's described on this website- http://www.galaxys5update.com/fix-black-screen-with-pulsating-blue-led-on-galaxy-s5-g900a/
I'm seeing the pulsing blue light as well. How do I find the 4.4.4 OA1 Kernel identified in the first link?