Related
Hi all, i have been having a very bazaar problem lately...When my phone boots up i get a pop-up message indicating that the gapps process shutdown unexpectedly...and sometimes i may even get a acore crash too. Applications from the market do not download...when i select my download i will end up getting a gapps crash and then the supposed download just sits there saying "starting...". Google talk doesn't even open! It will just say that the process quit unexpectedly. Even after a fresh install with factory data reset all these problems will continue. The initial boot up screen/tutorial will even show a gapps crash. I have tried with 3 different versions of cyanogenmod all with the exact same problem..Each version i've tried with a2sd enabled and disabled, formatting the partition each time before a new install to ensure no data carry-over issues. I don't know what to do. To me it seems like it make be something on googles side...but i can't for the life of me figure out whats causing these wild problems. Help would be very much appreciated.
ANDROID Market problems
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
six6star said:
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
Click to expand...
Click to collapse
I have searched and it seems many people have the Market/Gtalk problem.
I have the same problem (with an Eclair 2.1 Cyanogenmod rom) and I've not been able to find a solution. Wiping the cache makes nothing.
Anyone knows how to solve it?
Huh. I had a problem with the market at first with cyan 5.0.8 . I went in the terminal and ran fix_permissions after su and haven't had any problems since. Might try that
Sent from my HTC Magic using XDA App
Hey guys!
Got a little problem here!
Here's the situation, I'm perfectly able to flash CM6.10 (? - The latest stable for Wildfire anyway), but I've had no luck when trying to flash CM7. Either, it gets stuck at the white HTC splash after flashing and rebooting, or it gets stuck at the CM splash screen. The arrow just stops moving around in circles and freezes!
Not completely sure what this could be, I clear everything before I flash CM7 so ... And I ofc admit that I'm no sort of expert in this area, as almost every single flash has been perfectly fine to me, so I thought that you guys could figure this one out .
Regards
Try flashing kernel v4.1 from the HCDR.Kernel thread from the Wildfire Android Development Zone. Since you say you have cleared everything as stated by the first post in CM7, guess I wont be going into that.
I actually tried that as a last resort before going to bed yesterday, and that solved the problem! So thanks anyway, you were right !
Later on I installed the Gapps for CM7, but then when i booted my phone, i got the "Low Memory"-warning that wants you to remove some apps, and all the apps started to crash all the time. Especially the browser, not entirely sure of what's causing all this!
Hi,
I had the same boot problem and 4.1 also fixed it for me. I've not had any low memory issues but I only really have the google applications... One problem I do have is that I don't seem to be able to pair with any Bluetooth devices, I just don't get long enough to type in the PIN!
Can't post a report on the dev thread as I'm new here...
Andy
PS Which 6.10 have you been using? Did you have any Bluetooth issues?
3rd thread, about 4th rom flashed
constant issues with builds. have gone from stock to:
cm 6.1.3 -apps crashing, random crash notices i.e "phone book has crashed force close" - "the process com.android.phone has stopped unexpectedly"
cm 7 - random reboots, opening browser caused power cycle, wifi issues, lag (thread posted, no solutions at the forefront)
currently on tripnraver pre release. now another issue. no signal what so ever.
original baseband on this xperia x10a is .55. it is suggested to use with bands 52 or 49.
loading either of these basebands. which ive done. doesn't seem to fix the no signal problem. the description states should be backwards compatible even if appropriate bb is not installed on device. yet no luck.
attempting to flash either baseband fails to resolve this problem. currently trying to flash back to stock and try another full reinstall and baseband flash in flashtool.
any ideas would be a great help. having to flash x number of times between roms is getting quite time consuming
thanks everyone.
if you want to stay on the miui rom, you can flash the baseband patch located here and stay on whatever baseband works best for you (I'm on .55 and find it fantastic), then when you load the rom, go to dev tools>bad behaviour>crash the system server.
http://forum.xda-developers.com/showthread.php?t=1011608
Otherwise, I would recommend wolfbreaks cm 6.1.3, as it is the most stable. You must have done something wrong during installation as I never had an issue with his roms.
The only issue I have ever had with any rom is MiUi and thats because I used the wrong baseband. You must be doing something wrong for you to be having problems
if you want, try this flash, it's trips miui pre-final with the baseband patch implemented.
http://www.multiupload.com/KCKE9K2WKN
worked with my .54 baseband
thanks so much for the links to the baseband patches. i remember coming across a thread that posted it but unfortunately forgot to book mark. so im definitely going to go ahead and try with the patch installed. hopefully all works well
each rom ive flashed has been done properly according to instructions. cache wiped, dalvik, and full reset as per menu options in xrecovery.
one way or another i experienced lag for the most part, and as mentioned some random crashes. never had reset on wolfs rom just error messages at times. trips rom worked excellent, smooth and quick. hopefully with the patch implemented everything will work flawlessly
thanks you guys
*Updated
Flashed over rom with baseband patch. signal working. everything running smooth.
except for when using camera zoom. zoom default displays 0x. as soon as the option is selected it spawns an immediate force close
any patches? or similar outcome for anyone else?
i will outline my steps below so everyones up to speed on how i performed this flash.
- flashed back stock in SEUS
- root with one click (success)
- installed busy box (market)
- installed xrecovery apk
- booted into xrec
1. full factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
5. install custom zip from sd card
6. selected trips rom with bb patch implemented
5. reboot
Camera zoom doesn't work in most ROMs yet and the lag you were experiencing was likely just the FW "settling" it can take a little bit and a couple reboots sometimes for the phone to calibrate itself properly.
Sent from my X10i using XDA Premium App
thanks cmoney. maybe ill try my luck with cm7. give it a few reboots and hope for the best. great rom. im really loving trips iphonesque style
clean smooth and quick. everythings working great. hoping the zoom may get fixed soon enough. only other inquiry i have with regards to this rom is the apps2sd.
this feature is essential to myself personally. and it is not working as ive noticed on this rom. ive read a thread with regards to a fix for the last release. i checked the settings for an enable option in case the feature requires being manually set as active but nothing listed. within sd settings state reads as unavailable. if anyone has an answer as to whether this fix will function with the current pre release. ill be going ahead with completeling the flash and reporting what i find back on this thread.
thanks again everyone
Try Wolfbreaks rom. It's very very stable for me. It has cam and everything upto date.
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
thesoundofsilence said:
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
Click to expand...
Click to collapse
works for me on trips newest....
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
thesoundofsilence said:
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
Click to expand...
Click to collapse
I dunno man, it works fine for me, but I copied data from my 0.3.2 xrecovery image, so that might be why. try flashing that apps2sd fix for 0.3.2, should work fine
damn it. i just found that thread. found the links to the fixes. so far ive tried miui32_a2sd_fix.zip. and flashed that over with xrec prior to reboot. which did nothing.
there are two more links so im going to try those two flashes as well and hope that one of them will do the trick. if its working when utilizing .32 patches then ideally the bloody thing would have to work here. thanks for the input though dtox. much appreciated
I don't know what else to suggest man
From the feedback I see in the miui thread, everyone else is reporting it working!
Did you factory wipe, wipe cache partition, and wipe dalvik cache before install? then flash the miui 1.0.zip, and flash immediately the baseband patch then reboot into the rom.
Remember not all apps allow apps2sd so use something like android system info, go into the applications tab click on one, click manage and then see if the option "move to sd" is highlighted. Like I said check a few though, not all apps can be moved
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
thesoundofsilence said:
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
Click to expand...
Click to collapse
Try it again but without the fix...
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
thesoundofsilence said:
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
Click to expand...
Click to collapse
No idea man, like I said it is fine for everyone else so I'm so no big development will arise that will make it function with your phone....
maybe it has something to do with 10a. i dont know. but the point is it shouldn't even be doing this regardless. hypothetically if its froyo and it has apps2sd built in. it should work. its not the way ive flashed. the phone supports it. so my only conclusion the rom must not be as compatible as stated. and from reading different posts about the prev builds sometimes the patches worked at other times they didnt. and also the fact that the rom is claimed to work without the need for a bbpatch. yet without the patch instaled phone caught no single. i guess certain unexplainable glitches can be bound to happen at times but any how ill give it one last go.
if nothing comes out of that then im giving up on that build because it seems relatively hopeless.
lol I'm using an x10a...
Still man you're the only person reporting this. Don't you find that strange? What baseband are you using anyhow?
Hi all, I was wondering if you could help with an annoying issue I'm having.
I made a big mistake by updating to an ICS Rom, it worked fine apart from the accelerometer which stopped 100%. I did a backup, but system crashed and that's the end of that backup
1: I've since downgraded to Honey Comb Acer_A500_7.14.14_COM_GEN1, but Accelerometer still won't work, I don't know why, is there some fix or file to replace or anything like that.
2: Second question, because I updated to ICS the boot loader got updated also, is there a way to revert the boot loader back to the original so the end product would be a 100% original
This is a 16GB UK version of the A500, so any help would really be grateful. Even if I can get both the boot loader and OS to original I can then send it off to Acer for repair.
Kindest Regards to all
Garret
Man, I don't have an Acer iconia, but I have a Samsung galaxy player 5.0 and I just experienced the same issue after trying an ICS ROM.
When I searched for a way to solve my problem, I've seen many many users (increasingly, indeed) with the same kind of problem. It's hard to think that so many users are having accelerometer hardware fail. I believe it's not physical problem, mostly because this kind of issue happens after ppl try modding their phones/tabs or changing roms. I've seen some users talking about removing a sensorfile yamaha.cfg and trying to reboot the device. That didn't solve my problem, or executing:
"sensorcalibutil_yamaha"
It is under /system/bin/, you can see that with root explore.
Unfortunately, didn't work for me. Hope it works for you.
Best regards.
Thanks for your reply, I found a way of down grading the bootloader and OS to 3.0.2 which fixed it, then updated the odds to the latest and back working 100%.
Hello, same issue for me, accelerometer doesn't work anymore! I had yesterday the official ICS fota. Is there a patch somewhere for this problem?
after official Acer ICS update - Accelerometer quit?
My A500 pad just quit doing auto-rotate just about 30 mins after I applied the "official" ICS update to my device. I haven't done anything different, I did lock the pad into portrait to read some stuff, but unlocked it (manual switch) and it was fine then all of a sudden - it stopped rotating between portrait and landscape. The switch now has no effect on it. Of course there's not a setting to change the rotation either. Argh? I was so excited to get ICS - not this goofs on me? I see quite a lot of posts about people who experience this from hacking around on their tablet or phone - I haven't hacked on this one at all - its the "official" stuff... Reset didn't help.
bthorsberg said:
My A500 pad just quit doing auto-rotate just about 30 mins after I applied the "official" ICS update to my device. I haven't done anything different, I did lock the pad into portrait to read some stuff, but unlocked it (manual switch) and it was fine then all of a sudden - it stopped rotating between portrait and landscape. The switch now has no effect on it. Of course there's not a setting to change the rotation either. Argh? I was so excited to get ICS - not this goofs on me? I see quite a lot of posts about people who experience this from hacking around on their tablet or phone - I haven't hacked on this one at all - its the "official" stuff... Reset didn't help.
Click to expand...
Click to collapse
This is the same issue I have on the leak version.
Sent from my PC36100 using XDA
gbyrne2011 said:
Thanks for your reply, I found a way of down grading the bootloader and OS to 3.0.2 which fixed it, then updated the odds to the latest and back working 100%.
Click to expand...
Click to collapse
I need to do the exact same thing. Could you please let me know what you did to start all over and get all the OTAs?
Thanks!
One could conjecture that if the accelerometer is stuffed, so would the orientation detection be.
Cause and effect?
Z.
Sent from my A501 using Tapatalk 2
Same here but a reboot cured it.
anyone find a fix for this ? im on the official with no root ics update and mine has also stopped auto rotating.
What did you use to do the downgrade back to 3.0.2?
gr8buddha said:
anyone find a fix for this ? im on the official with no root ics update and mine has also stopped auto rotating.
Click to expand...
Click to collapse
The only solution I found so far is keepin rebooting, eventually at some point accelerometer starts to work.
Best regards.
Sent from my GT-I9000 using XDA
If any off you had a leak and altered boot loader prior to install, it may have caused that. You should have had a 2 step optimizing process in the update, when I tested it on a leaked/flashed back version the bootloader was wrogn and that issue resulted. The stock had no issue and went through the full hardware optimizing process.
Also you shoudl have applied the market place update first, it has a pre fix to prepare it for patching.
Hey guys, i also have the same issue with accelerometer. I downgraded the a500 to Honeycomb and it fixed now.
I followed this guide: http://forum.xda-developers.com/showthread.php?t=1516012
Rollback OS + Bootloader back to Rooted HC 3.2.1
Use this to Rollback OS + Bootloader back to Rooted HC 3.2.1
WARNING EXTREMELY DANGEROUS | YMMV | WARNING EXTREMELY DANGEROUS
http://forum.xda-developers.com/showthread.php?t=1516012
WARNING EXTREMELY DANGEROUS | YMMV | WARNING EXTREMELY DANGEROUS
the guides to rollback posted above can be used on an official pad , with no hack or root stuffs ?
No, it rolls you back to rooted 3.2.1. with stock bootloader. Once ur back, you can load your official 3.2 rom on an SD, use Pwr + Volume down to update to it. Then OTA to ICS.
Just saw a guy posted a system of methods to completely wipe all the system files (not just most) and clean install ICS which supposedly fixes the accelerometer problem.
Accelerometer / ICS
I sent my tab back to Acer for repair, they say they replaced the "motherboard" and it did work fine on stock ICS as returned for a while. Periodically it would stick in orientation and not auto-rotate, but a power cycle with a few minutes in between seemed to always bring it back ok. NOW - nothing I do brings it back - its working the very same way it was when it originally experienced this issue. I don't want to send this slab back to Acer every couple of months and deal with setting it back up when they ship it to me a week or so later. This is rediculous or am I just being picky?
Anyhow - How bout a reference or link for the info on downgrading, wiping ICS and re-installing from scratch as mentioned above? That would be helpful if I knew where to look.
UPDATE: This morning, based on another post about finding errors in the bootlog, I downloaded the bootlog capture app, ran it, and poof - the auto-rotate function came back to life - like magic. I'm sure it was NOT the app, but rather the fact that I had powered down the unit and let it sit all night long without touching it or powering it on/off, etc. so at least for now, I won't be sending it back to Acer for Warranty repair (AGAIN). BUT I might be listing it rather quickly on ebay and shopping for another tab that doesn't have this issue....
I have had this issue and normally a power cycle fixes it. I did have one time where it did not but I found an article that said to do a hard reset. You do this with a paper clip pushed into the very small hole. I did not lose any data.
Marc
Sent from my A500 using xda app-developers app
take a look at this. It work for me.
http://androidforums.com/acer-iconi...veral-a500-ics-related-symptoms-problems.html........
delete the last dots.
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Hi:
simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
I'm in the same situation. I think these screens are not 100% compatible so it seems a hardware issue.
Maybe using vendor partition but i'm so stucked as you.
My phone can't hotboot any official recovery although i can boot flashed recovery only if i boot slot a not slot b.
Stock roms boot always using slot a but tried Lineage (thats uses slot b) and got always black screen.
I'll keep reading and trying to solve it.
Regards.
simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
Have you made any progress?
gsausalito said:
Have you made any progress?
Click to expand...
Click to collapse
Thanks for your interest but I've made no progress and actually given up on it. I'm sure the issue could be resolved by buying a new, more compatible screen but I'm not going to put any more money into the phone.
As far as the software solution goes, I've tried almost every combination of ROM + Kernel i can think of but the only thing that works is the stock ROM.
I'm going to close this thread as I don't think it's much use to anyone.
Regards
Sorry for posting here, but i am in the same and i noticed that flashing canting 4.9 kernel gives display for like 8 seconds after screen turns off. May it be a kernel config issue? if anyone in this forum could answer this i could try and change it. Also flashing stock kernel on custom rom solves the problem but makes other thing fail
Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.
Hello Mi A1 friends.
So yesterday I decided to change my crack LCD screen and to my surprise the phone boots into Xiaomi Logo and then after that its just a black screen. Message and other notifcation sounds still come in which means that the phone mange to boot into home screen, just with nothing to display. At the time of changing screen, I am on stock kernel and Pixel Experience 10.
Gonna flash back to stock pie(9) rom and see how it goes from there.
Deezio said:
Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.
Click to expand...
Click to collapse
Sry for reply to an old post, but how did you do it? How did you flash kernel when you can't enter twrp because of screen issues? I have exact the same problem, where stock rom works but everything else cause blank screen. Also can't boot to twrp - probably the same reason.