Develop Bugs

Android boot error "micropklt_lcd_ctrl: This function should no longer be used"

Android boot error "micropklt_lcd_ctrl: This function should no longer be used"
I've been battling this error again and again whenever I tried another Android release, and since there are no real answers around, but some others have the same problem, which according to searches mostly goes unanswered in bigger threads, I decided to go ahead and dedicate one thread to it.
Problem: After installing Android and running it, its boot ends up in an eternal loop displaying
Code:
micropklt_lcd_ctrl: This function should no longer be used
.
Setting: German Rhodium. Initially an Energy ROM. Since I thought it might be something from the ROM, the latest one is Energy.RHODIUM.21889.Android(ULTRA_LITE_ROM)_28.Jan.
8 GB SD from Kingston. Since this was named as a possible problem, tried with 1 GB SD (Kingston) as well.
Reformatted SD and restarted from scratch.
Tried Android versions:
Project Android 030810.cab
Project Android 033110.cab
[MJG]Rhod.Eclair.Rebuild033110.3.rar
plus various older ones (with different base name, xAndroid or something like that?) already deleted.
Tried to disable 3D Hardware during boot.
Another suggested workaround to use specific files from older releases; these I could no longer find on the net.
To sum attempts up:
Tried different (?) Android releases (xAndroid, Project Android) - fail
Tried small SD card (1 GB) - fail
Tried SanDisk instead of Kingston SD card - pending
Tried to reformat SD card (with SD card formatter) - fail
Tried to disable 3D Hardware - fail
Tried WinMo ROM labeled as created for Android (Energy.RHODIUM.21889.Android(ULTRA_LITE_ROM)_28.Jan) - fail
Tried to insert SIM card (was missing) - fail
Tried to update HardSSL (Rhodium-HardSPL_V2_00R3.exe) - fail
Information:
(forum prevented me from adding links to external information)
This forum, other members with same problem
Looking for: suggestions what else to try.

ItsReallyMe said:
I've been battling this error again and again whenever I tried another Android release, and since there are no real answers around, but some others have the same problem, which according to searches mostly goes unanswered in bigger threads, I decided to go ahead and dedicate one thread to it.
Problem: After installing Android and running it, its boot ends up in an eternal loop displaying
Code:
micropklt_lcd_ctrl: This function should no longer be used
.
Setting: German Rhodium. Initially an Energy ROM. Since I thought it might be something from the ROM, the latest one is Energy.RHODIUM.21889.Android(ULTRA_LITE_ROM)_28.Jan.
8 GB SD from Kingston. Since this was named as a possible problem, tried with 1 GB SD (Kingston) as well.
.
Click to expand...
Click to collapse
I have an AT&T Tilt2, stock rom, 8GB SanDisk. I see a very similar message when booting xdandroid, but mine continues to boot through, my boot sequence snippet runs like this:
Code:
[ 26.309173] Adding 102392k swap on /dev/block/ramzswap0.
Priority:-1 extents:1 across: 102392k
[ 26.484039]Something used micropklt_lcd_ctrl: This function should no longer be used
USING EXPERIMENTAL TILT2 LAYOUT
op: cannot stat '/init.etc/keymaps/tilt2_navi_pad.kl': No such file or directory
Touchscreen device directory is /sys/class/input/input2
Then continues to the screen calibration. I know I'm not helping directly, but perhaps can help lead others to clues ?

i already started a topic for this exact error....
http://forum.xda-developers.com/showthread.php?t=632128
So far no one has come up with a solution...

Oh, sorry, I searched the forum a few times, but mus have forgotten that thread, otherwise I would've posted there as well...
From what I can read there, maybe I should try a SanDisk instead of Kingston SD? Or is it SD vs. SDHC? Anyway, I just ordered a 2 GB SanDisk from Amazon (smallest one I could get ) and will try this next...

I managed to solve it by reflashing the newest HardSPL. (In my case I had a corrupt microp firmware, casuing all kind of problems in WM as well).
It might not solve the problem for you, but it can't hurt either

My SanDisk SD has not yet arrived, but I tried to insert a SIM card (phone currently has none, since I' using another one while testing) - no changes.
Thanks for the HardSPL hint - tried as well. No Luck, but at least another topic to add to the "things I tried" list

Okay.. So, i tried HardSPL.
Task 29
Reloaded my Rom
Hard Reset
Formatted Memory Stick
Followed ALL instructions!
Nothing happened.
I then went back and tried an old version of android from this thread
I used the 12/20 2.01 version.
AAAANNND..... it loaded right away....
WHY does this old version work, and the new ones wont?
what is different?

Update: my SanDisk SD card arrived, so I loaded [MJG]Rhod.2.1Sense.042310.rar, extracted it to the card, and started it. Same problem. This means it does not seem like a Kingston SD card problem.
So... I tested, and can confirm that the old build you linked solved the problem for me as well!

I have searched this ENTIRE FORUM and read EVERY SINGLE GOD FORSAKEN post about this error. I am at my whits end!
Someone said they got it to work with a more current package and an old rootfs.img
I didnt try the same two builds they did, i tried the sense ui one and the old rootfs. from the build i said works. it did not work.
so i figured i would compare the two rootfs.img to see what the difference is.
however, i cannot open the contents in windows (from what i understand)
so i install UBUNTU on my computer.
I cant for the life of me figure out how to mount the damn image!
PLEASE SOMEONE ELSE! please look this up. i am frustrated beyond words.
if you can give me a way to compare these files in windows, i will be glad to do it.
I just cant stand windows mobile crashing all the mother f-ing time and i REALLY REALLY REALLY want to use android. Im sorry for being so frustrated. i have spent literally HOURS on this...

Anyone, anything?

Mount rootfs.img
eternalcold said:
Anyone, anything?
Click to expand...
Click to collapse
You can mount image in terminal like this:
first create dir with:
mkdir /mnt/rootfs
then mount the image:
mount rootfs.img /mnt/rootfs/ -o loop
then change dir to /mnt/rootfs and you have the android FS.
i will also compare old and new rootfs so maybe we will found something!
BR

I still have this problem.

I tried what you said, but i keep getting errors. I cant seem to get it to work. I will again look through all the threads again, as well as the different websites i found from google. i will link them tomorrow when i get a chance. If anyone else has found anything, please let me know.

The latest kernel has the following commit message
"rewritten micropklt_lcd_ctrl calls to micropklt_set_misc_states calls"
So this might fix it for you guys?
It seems to have some other problems with sleep etc, but if it boots it is something

I see, thanks for looking, however, i still cant figure out how to mount and change things in ubuntu (sorry, i know i am a newb) would you be able to repackage it with the line changed to the old one? and upload it? i will check it out to see if it works.

It's alive!!
Download latest Android build with latest kernel from hxxp://glemsom.anapnea.net/android/htc-msm-android/ and replace zImage and modules and thats it.
i didn't test it full, but it starts!
Thanks to Star-Lite for info!!!
BR

Ah yes it works! Beautiful beautiful!

Don't thank me, thank CaptNoord for fixing this in the kernel
I'm sure he has a donate button somewhere

I will donate as soon as the bills are past this month (a couple more days)
Out of plain curiousity, is there a reason why this error only happened on some devices and not others? Could it be from a hardware difference between maybe different revisions of the device?

use the right starup.txt file

Lingering EVO issues (SD Card, Camera, etc.)

I'm having some lingering issues with my EVO even after running OTA updates. I am running a rooted stock ROM, currently software version 1.32.651.6 (I have not attempted the latest OTA update yet).
In particular are two problems - SD card issues have remained even after the OTA update. This was present even before rooting but after installing the first update (I went to a "full-service" store on opening day and they set it up themselves, assuming everyone would want it - luckily I could still get root). Issues include the Camera application reporting permissions problems randomly when trying to save pictures to the SD card, HTC's music application freaking out and coming to a near freeze trying to crawl the SD card during one of its troublesome spurts, and files disappearing from file explorers. So basically run of the mill, pre-first-OTA sd card problems. But occurring after the update and both before/after rooting.
Second is a problem with the camera itself. When first booting, HTC's included photo/video application will instantly crash after showing the camera icon on the black background. Google Goggles freezes for about 10 seconds then reports it was unable to connect to the camera. After the phone being on for about half an hour, these issues (seemingly) go away until the next reboot.
Last, and least frequent but still troubling, is a problem with the device powering on. At least twice I have been unable to get the device to turn on after powering it off, forcing a pull and replace of the battery to get it working again.
As far as I know, all of these issues could be either hardware or software. Even the power problem - my best guess is that the phone never powers off fully, but is instead locked inside of a deep sleep state and thus can not turn on until a battery pull forces the entire system off.
The questions being - first, are there any known solutions to the above problems? I have found many threads in particular regarding SD card issues, but none that seem to report these problems post-update. The others I have seen little to nothing about.
Second - if there are not known solutions, would it be prudent to return the phone as it may likely be a hardware problem?
Since it seems I'm forced to take the last update if I get a replacement, I may likely have problems getting a full root back. I'd like to avoid that if possible - having root works wonders for doing application development using non-native (unexposed) API's (Which - side note - since I'm developing for 2.1 at the moment, other than hacking for direct access to a Surface, does anyone know of a _fast_ way to do direct blits from native code? glTexImage2d is insanely slow).
Thanks all any help. Again, apologize if any of these are solved and gone problems, but I wasn't able to procure anything myself.

I'd go for the replacement, sounds like a defective unit..
Be sure that the folks here at xda will get root working regardless of OTA.

replace the unit, i'm very particular about my phones, if there is anything wrong with it I replace it.

I too have the SD card issue, I have updated, i have rooted, re-rooted, flashed new rom, different roms (fresh and sd) and it has always given me the sd card issue. Sometimes it wants to be a pain and not work at all, sometimes its good for at least a week or two. I am waiting for a little longer to make sure when I get a replacement its a newer version.

SD card permission errors --- POSSIBLE FIX
I hope/think/believe I fixed this error for those interested, I use my EVO for work and need it to work without a hitch....
Here goes (**Note i am a noob with smartphones with a dangerous amount of IT knowledge - disclaimer for those brave enough to browse around the root files and SD card files; I am not responsible for you bricking your phone, I am only trying to help those in need and putting in my 2 cents_)
Download and open the app ---> Root Explorer (or any other root explorer for that matter) from Android market.
Once Root Explorer is open (look up top/left it will say) Mounted as r/o (means read only) - press the white button to mount it as r/w (read & write)
Press and long hold on the SD card directory (folder) - you will get another window from which you must select the permissions option.
Under top option USER - check all marks -- READ WRITE AND EXECUTE & click OK.
VERY IMPORTANT - Click on the (white button) Mount as r/o to write protect your root files on your phone again.
I just applied this fix about 45 mins ago and seems to be working......updates to come if issues persist or re-surface. (**Note I could not see photos or play music and some apps were also giving me FCs (intermittently) due to permission or write errors to SD card; and now it seems to be working like nothing ever happened.)
What I have ::: stock ROM on EVO supersonic with recent HTC updates applied - standard 8Gig SD card provided with phone / had rooted but put back stock ROM for preference issues.
Hope this info helps some folks...very frustrating issue.
Cheers

SD card permission errors --- POSSIBLE FIX
ONE LAST SIDENOTE COMMENT -
I transfer data to my PC often (running Win 7 32bit_)
It is crucial that you right click on "safely remove hardware" icon on the lower right side (next to date and time) and WAIT until windows tells you
..."It is now safe to remove your hardware" --- I was just taking the plug out when done and it appears as if that could have started or compounded these issues with the SD card.

I too get the could not connect problems at times. And I have lost access to the SD card a few times. Some say its Fring that causes the problem. But after removing it I still have camera issues. I noticed that having the LED Light on while trying to open the camera will cause this problem.
I am running CM6 RC1 so this is to be expected from Release Candidates. Sit tight. It will get fixed.

Well after a full 24 hrs...no issues with the read write error on my EVO SD card, I think that when the phone is removed from PC incorrectly (i.e. pulling USB cable out in mode other than "Charge only" i.e. HTC sync, Disk Drive, Internet sharing - it causes it to "corrupt" the permissions on the SD card - It is still working like a champ and i am waiting impatiently for my EVO Froyo update ... feedback appreciated for those whom tried this fix and had it work....txs

@LF142
Hi there. So I followed all of your instructions above and downloaded Root Explorer. However, every time I change the permissions, they don't save. User, Group and Other is always switched off at root level. Do you think this may mean my SD card is corrupted?
I rooted it with BakedSnack.
I now want to un-root it as I miss taking shots, looking at my shots, listening to my tunes etc.
But I want to keep all my apps. All my texts and everything else. Whats the best way to go about this? I am also a bit of a n00b and I apologize if this is in the wrong forum, but when Froyo releases tomorrow (apparently) do I have to unroot to receive the update?
Thanks

[Q] Woes of the S4 mini SCH-I435 (several questions about it)

I was recently given a new SCH-I435 from a family member. This is my first time having an android in a very long time(Switching from an iPhone 4s). I have a few questions about it. (this may be a lengthy post)
First I know that you cannot flash custom ROMs to it, as the bootloader is still locked. I have heard that there are some de-bloated stock ROMs out there, but have entirely failed to find any. I can probably get by without it, as I already have it rooted, but there are several things I am attempting to do, and every time I look up how to do it, step one is having a custom ROM.
If anyone can point me to a de-bloated stock ROM I would greatly appreciate it (or at least one that is compiled to not be a "production build" as I keep running into "adbd cannot run as root in production builds" and it is severely limiting what I am trying to do, and what I am going to want to do in the future)
What I am trying to accomplish next is taking over the "connected as installer" feature that Verizon has on it when you plug it into USB (I am using linux exclusively so have absolutely no use for their software). I figured I may as well put this feature to good use. I am attempting to swap the ISO file in /system/etc for a CrunchBang LiveCD.
This has only been a partial success, apparently /system is it's own partition, and there is not enough room to fit the whole ISO (It is 739mb and it stops at 423mb) Even though it does not get the whole ISO copied, if I reboot my computer the ISO does indeed boot into the options, but fails to load the live session (no brainer there) so I know I am on the right track. I don't want to use DriveDroid for this, as it is very very finicky, and only seems to work 1 out of 6 times (and that is a kind guesstimate) My guess it that the "connected as an installer" is messing with it, so I would hope to turn the problem into the solution.
So I either need to find a de-bloated ROM that can free up ~ 400mb on /system, find a way to link the ISO from elsewhere on the device (I tried a soft symlink from my SD card and that did not work, it opens the ISO as an archive and not a file system), find a way myself to free up ~400mb on /system, or find a way to re partition /system to be larger (I have the 16gb S4, so I have plenty of room to spare).
I would prefer the debloated ROM(I don't know if that will free enough room), but finding a way to re-partition would be a close second (Every guide I have found for re-partitioning starts of with "First you need cyanogen(or another custom ROM)") I may need to re-partition it anyway. (Honestly I would like to learn how to do all of these, as they would be valuable tools in the future)
I had more questions, but got kinda lost writing this up, I will append them to this post later when I remember them... Thank you in advance for any help you may send my way.
**edit**
Oh yea, my other issue is accessing the files on the phone under Debian Wheezy. I have tried mtpfs, jmptfs, ptp mode, mtp mode, go-mtpfs (that one somewhat works, I can see *some* of the files, and probably take them off the device, but I attempted to add a file to the SD card and it corrupted the entire card, had to reformat it, just glad I did not do that to the phone)
ADB partially works, but only for taking files off the device, or putting them onto the device in non root areas, I get stuck with "adbd cannot run as root in production builds". I have tried almost everything I can find under the sun in regards to USB access.

Bricked Oppo Find 7

Hello,
I have an Oppo Find 7 for a while and I always thought that the Color OS is not very good, and specially, it comes with a very limiting partition division.
So, when I could no longer decide on which Apps to keep and which to uninstall, since I had no longer space left on my phone due to the stupid small partition for applications, I decided to format my phone, reconfigure the partitions and install a new ROM (CM 13).
I had done it often on my lapton, how difficult could it be to do it on the phone?
It all seemed to work fine, but when I started my "new" phone with CM I noticed that something was wrong. I tried to use the camera and it showed an error saying I did't have a storage device.
Well, I was sure I had left enough space for photos in the other (not OS) partition, and I had also the SD card.
I went to Settings->Storage and I saw that my phone was recognising the OS partition only (about half of all internal storage) and had a portable storage device called "sdcard0" (not the actual SD card) reading "Damaged" below.
I've tried to erase and format that partition, but it shows an error reading "command '41 volume partition disk: 179_0 public' failed with '400 41 Command failed'".
I've tried to rearrange the partitions again, to reinstall CM13, but nothing worked, so I just accepted that my phone could not take pictures. Everything that did't require to have a file system worked fine (well, I cannot see the naked ladies pictures my friends share on whatsapp). This was a few months ago, so I don't remember precisely what I did.
Recently I decided that I actually need a phone that takes pictures, so I went back to trying to fix it.
Unfortunately, I can't. At least without some custom help. I've read plenty of tutorials, forum pages, but there's always something that doesn't work in my case.
Here's what I can do with my phone:
- It boots
- It works
- Computer recognises it
- adb recognises
Here's what I can't do:
- Have any files (the file system is broken)
- Take photos
- Restart with bootloader - when I tried, the screen just shows a sitting penguin for a few seconds and then turns off. I do remember to be able to do so, but I can't now.
I've tried to load bootloader though the phone's interface, through the power+volume down button combination and through adb. They all had the same result. The stupid penguin and then darkness.
Can someone help me?

Hello, you're phone is not bricked. What is the exact name of you're ROM ? Do you have make LVM, or chinese storage partion?

/storage/emulated/0 disappeared

Hello forum,
Title says it all.
More details. A couple of weeks ago, /storage/emulated/0 disappeared. I was then running the latest lineage. No problem until then with previous versions. I have tried everything I could think of:
- looked for my data to see if it had disappeared. No. Everything was still in /data
- scoured the internet for people with the same problem. A few interesting posts, but no solutions.
- recreating the links through a terminal with root access. No luck.
- reflashed stock ROM. Same problem. Impossible to launch the file manager.
- reinstalled twrp and lineage. No help.
Note that twrp in recovery, storage manager in lineage settings all see the internal storage.
I am at a complete loss.
I was thinking it could be a lineage problem but reflashing versions that had been working didn't help. Problem remained with the stock ROM.
I attach a picture of the filesystem as xplore with root access sees it. (No screenshot since android can't access the card to save at the usual pla
Link: //drive.google.com/file/d/1HwEeKj5nPFtFRcmkOOe-6IgY9T_I_HbT/view?usp=drivesdk/