Database Users

[FIXED] black screen on hboot/recovery and camera issue (FIXED)

During an update, (PASSIMG.zip) in hboot I selected yes (to install) then about a second later, my screen
turned black and now, the only thing I can do is to boot in the installed stock rom (FRG33).
My english is not perfect, i'm sorry for that.
1. I Removed my battery after a while. (about 10 minutes)
2. Inserted the battery back in his place
3. Power down + vol down and I'm stock, I can navigate in
the menu but I can't see anything...
Anyone know how I can get my screen back ? OLED vs SLCD ?
Note: I can boot in my rom, the rom is unrooted, my phone is unlocked.
(And yes, I tried to flash recovery and another rom without success. And I can't
find a way to flash hboot again (bad signature)
I'm using the last version of hboot and radio.
If anyone have an idea of how I can fix this, this will be really appreciated.
Thanks.

I'm starting to think than my /dev/mtd/mtd0 is screwed up.
Anyone know where I can get/or generate a image of a normal mtd0 ?
At the moment I'm running debian sid dand SuperOneClick seem to freeze
after trying to chmod rageagainstthecage or psneu..
Note: Yes my screen work when the boot is completed. (but not in hboot/recovery)
bad spl ?
fblodroid

Ok, sorry for the noise, I was able to perform an update via 766a101ae02c.signed-passion-ota-60505.766a101a.zip (renamed to update.zip) and I powered off my phone.
Removed the battery to be sure there is no power at all.
and using some screenshot found on the web.
I was able to perform the update (blindly, this word exist ?) and the phone rebooted
and asked me if I want to update again (google update) I selected yes, the phone rebooted
and, VOILA, I can see again the crappy X logo with an open lock at the bottom.
Thanks again (ok for nothing, but if than can help some people...)
Yes, shame on my english again.
fblodroid

My guess is that you have an SLCD Nexus One, and the passimg installed the .33 HBOOT which doesn't work for them.

I had the same problem when flashing the MIUI-AU rom, screen went black,removed battery and replaced but the phone was dead,I was already thinking which phone to buy then when I connected the N1 to my laptop miraculously the X logo appeared and the rom launched ok

At the moment my phone is working again but I'm still having a camera issue.
About a 1 1/2 month ago I experienced this problem, no flash, no camera, just
a black screen when I try to run anything than use the camera.
Then a day, I was walking on the street and I checked to see if the flashlight was
working and obscured magic occured, the flash was working again but not the camera,
I wiped my phone again, repartitionned my SD card and installed a new rom and the
camera was back to normal.
Now, about a month later, (the problem started yesterday) i'm having the same issue.
I'm persuaded than this problem is related to a firmware problem, something related to
my /dev/mtd/mtd0 (hboot, perpaps ?) I don't know exactly where the camera firmware
is writed in the phone memory (nand)
I wiped and flashed again and again a lot of rom last night and today and the problem
still exist.
No camera/flash at all.
I'm thinking about returning the phone for warranty issue but like I said before, the
phone is unlocked... perpaps I will try to black the screen again and send the phone for
warranty... this way they cannot see (without fastboot) if the phone is locked or not.
If anyone have an idea of what I can do... a rom to recommend ?
Today I tryed to revert hboot without success...
EDIT: At the moment I'm running a rooted rom based on FRG83G.
fblodroid...

Related to my camera/flash problem:
Hum, I think I found the problem, this is hardware related, something seem to be
badly connected in the phone, I tryed too apply some force on the right border of the
phone with the flashlight ON (I previously looked on the web to see where the "contacts/plugs"
are located on the pcb (teardown pictures) and after applying some pressure, the light came ON
and now I can open and stop the "flashlight" mode.
teardown on the way ? I'm thinking about it... but i'll try to flash another rom again to see
if my camera is back.. (like in the past)
EDIT: No camera for the moment and the flashlight app light on the LED only if I select
the option "High Brightnes", ON/OFF are working with this option selected.
fblodroid

FIXED
After a complete teardown of my phone, and a lots of cigarettes..
I found two cables not correctly connected to her pin.
I made a picture, hum, an ugly picture of which cables.
http://img121.imageshack.us/i/icedqlubgg4zzbv2huge.jpg/ (in the red circles, the two pink dots)
And yep, now my camera/flash are working perfectly.
NOTE: the phone is not easily to dismantle, this is at your risk and peril. (time: about ~25 min)
Thanks again and please, ignore my english. I'm thinking about starting a thread
related to this problem. Should I ?
fblodroid

Hi, I have a HTC Desire GSM PVT4 (HTC__203), with the exact same issue as what is described in the original post. When I boot in hboot or recovery the screen is completely black. When I boot in the normal rom the screen works fine. I reflashed a number of RUU's successfully, but the problem remains.
The misc partition is not part of the RUU images, and I did re-flash the misc partition in an attempt to downgrade. Any idea where I can get an image for the misc partition for my device, or where I can generate one?
Thanks,
Hans

fblodroid said:
After a complete teardown of my phone, and a lots of cigarettes..
I found two cables not correctly connected to her pin.
I made a picture, hum, an ugly picture of which cables.
/link/
And yep, now my camera/flash are working perfectly.
NOTE: the phone is not easily to dismantle, this is at your risk and peril. (time: about ~25 min)
Thanks again and please, ignore my english. I'm thinking about starting a thread
related to this problem. Should I ?
fblodroid
Click to expand...
Click to collapse
Hey. I have the same issue you had with the camera, black screen and forced to close when running it. My flashlight works perfectly thoug.
I tried wiping and reflashing diferent ROMs, stock and Cyanogen with no luck. I also followed your lead and disassembled the phone to check all the connectors but the problem persists.
Any idea for me to try? Thanks for your posts anyway.

soylapinta said:
Hey. I have the same issue you had with the camera, black screen and forced to close when running it. My flashlight works perfectly thoug.
I tried wiping and reflashing diferent ROMs, stock and Cyanogen with no luck. I also followed your lead and disassembled the phone to check all the connectors but the problem persists.
Any idea for me to try? Thanks for your posts anyway.
Click to expand...
Click to collapse
Did you managed to fix it ? Be sure to check all the plugs, at best unplug everythings
and disassemble the phone entirely.
Mine is still working perfectly after two years.
fb

[Q] LG G2 crashes after recovery problem

Hello everyone,
*
I have a little (big) issue with my LG G2 (International D802). Everything was fine until I decided to change rom ( the stock is nice, but has micro lags ). So I decided to change and move to the Carbon rom (nightly) .
*
But the phone battery life was not as good as before, and there was some missing features (complete LG Quickwindow support for exemple)
*
Then, I decided to test cyanogenmod , especially to see if the battery life is better . And then I did something wrong : I started the stock rom recovery (there was an old backup on my phone) .
*
I realized at the end, and the recovery did completely fail , leading to a bootloop .
*
I finally managed to get booting to the stock rom with a .kdz flash using LG FlashTool software.
However, the phone is no longer stable at all: the wifi is slow, it does not detect my sim card , and most importantly, the phone crashes regularly (~ every 5 minutes). I'm unable to access files from windows ( but the phone is detected, just not visible in the explorer) .
*
I also tested the rom 4.4 SFR (France) : no more crashes (at least much less) , but sim card and LG applications do not work.
*
I also managed to get in TWRP recovery : When I turn on the adb sideload function, the transfer is successful, the installation completes without any problems (although I feel it is really quick - I tested Carbon and Cyanogenmod -) but in the end the system refuses to boot ( freeze on the boot animation)
*
In your opinion, is it recoverable?
*
Thanks!

Kakawada said:
Hello everyone,
*
I have a little (big) issue with my LG G2 (International D802). Everything was fine until I decided to change rom ( the stock is nice, but has micro lags ). So I decided to change and move to the Carbon rom (nightly) .
*
But the phone battery life was not as good as before, and there was some missing features (complete LG Quickwindow support for exemple)
*
Then, I decided to test cyanogenmod , especially to see if the battery life is better . And then I did something wrong : I started the stock rom recovery (there was an old backup on my phone) .
*
I realized at the end, and the recovery did completely fail , leading to a bootloop .
*
I finally managed to get booting to the stock rom with a .kdz flash using LG FlashTool software.
However, the phone is no longer stable at all: the wifi is slow, it does not detect my sim card , and most importantly, the phone crashes regularly (~ every 5 minutes). I'm unable to access files from windows ( but the phone is detected, just not visible in the explorer) .
*
I also tested the rom 4.4 SFR (France) : no more crashes (at least much less) , but sim card and LG applications do not work.
*
I also managed to get in TWRP recovery : When I turn on the adb sideload function, the transfer is successful, the installation completes without any problems (although I feel it is really quick - I tested Carbon and Cyanogenmod -) but in the end the system refuses to boot ( freeze on the boot animation)
*
In your opinion, is it recoverable?
*
Thanks!
Click to expand...
Click to collapse
i would kdz again. it sounds like it did not install properly the first time making sure its the exact same kdz file you need. i have had to kdz more than once in the past for it to install properly.
http://forum.xda-developers.com/showthread.php?t=2432476

you can also try redownloading your kdz, might have had a bad dowload

XxZombiePikachu said:
you can also try redownloading your kdz, might have had a bad dowload
Click to expand...
Click to collapse
that 2

gentlemandroid17 said:
i would kdz again. it sounds like it did not install properly the first time making sure its the exact same kdz file you need. i have had to kdz more than once in the past for it to install properly.
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
XxZombiePikachu said:
you can also try redownloading your kdz, might have had a bad dowload
Click to expand...
Click to collapse
Thanks for the answers.
I tried flashing the kdz several times.
I tried 2 kdz: one with kitkat, and the other with jelly bean.
I'm sure that the jelly bean kdz is working, because I flashed it when I got the phone (Hong Kong Rom -> Europe Open)
I'll try the Kitkat Europe Open kdz when it will be available.

Okay... my phone is still buggy, I think the EFS is damaged. Is it possible to repair it ? (found backup and restore but not repair)

Error rom miui 11 stock

After having had a 1 month experience with the rom pixel experience I wanted to return to the rom stock of miui by downloading it from the official pages, I installed them normal as I would with a custom rom (clean installation) but at the time of starting the system at load the first steps and the different configurations the fps drops appear on the screen and it is blocked for 5 to 10 seconds.
I would like to know if I am doing something wrong and I need your help to return to the rom stock and that it works smoothly as before.
Thanks :'(

Download Mi flashtool and fastboot rom.
Here a good how to
https://in.c.mi.com/thread-714161-1-0.html

alejandr769 said:
After having had a 1 month experience with the rom pixel experience I wanted to return to the rom stock of miui by downloading it from the official pages, I installed them normal as I would with a custom rom (clean installation) but at the time of starting the system at load the first steps and the different configurations the fps drops appear on the screen and it is blocked for 5 to 10 seconds.
I would like to know if I am doing something wrong and I need your help to return to the rom stock and that it works smoothly as before.
Thanks :'(
Click to expand...
Click to collapse
As said by the other member (joke19), the best solution is to use the mi tool so as to bring the phone back to its original condition, certainly one of the partitions (probably The vendor partition or persist) (it's just a guess) but ... did you install the latest firmware available in the version of the rom that you then installed?(you said you did a clean install, which means formatting sistem data cache vendor ... And then before installing the new rom reinstalled the Appropriate firmware ...) Personally only once did I return from custom to MIUI (not MIUI stock, however, and at the time I lost the IMEI despite all the correct steps) but it was a long time ago However, these are things that can happen even when you switch from one custom to another, even if one does all the steps. Correct "formatting" from twrp is never a formatting Really clean ... only from fastboot or using the xiaomi tool you usually have a Complete formatting And I would like to underline COMPLETE because in twrp only some partitions are cleaned and this can sometimes lead to small problems

Popup camera not working on xiaomi mi 9t with custom ROM

After smashing my head against the limits of the MIUI again, i decided to say goodbye to my warranty and flash a custom rom. Via TWRP I flashed the latest (stable) version of Arrow OS based on android 10Q. Everything works perfectly aside from the popup camera, that appears to be firmly locked in place feeding live feed from inside the chassis. Thinking it was an error of that release, i tried other ROMs, both Android 9 and 10, ResurrectionRemix, Lineage. With RR the problem is the same, while with Lineage, the camera asks for a calibration: it actually pops out fully does two or three pops and then it says calibration failed. The servos are working, I've opened the chassis and found no dust at all, so I've looked for a fix online. The most common one is a flash of the stock 'persist.img' image, I've tried several times via TWRP, tried a few clean flashes (ROM+image) of different versions and nothing. Am I missing something? I don't want to get back to MIUI...

Did u backup your persist partition before ? if no u can flash any other one that comes in the fastboot stock rom but u will loose L1 (netflix in HD)

The problem persists.
Badis st said:
Did u backup your persist partition before ? if no u can flash any other one that comes in the fastboot stock rom but u will loose L1 (netflix in HD)
Click to expand...
Click to collapse
I did, but even when I tried flashing different versions of persist.img ranging from fastboot stock firmware 10 to 12, with and without backup, (clean wipe, fresh recovery) the problem was still present. I'm no expert but I'd guess the OS doesn't know how to: either tell the servos to pop the camera out (Arrow OS) or recognizing the camera working when calibrating (Lineage OS). I'm trying to dig my way to the cam app in the MIUI release and to install it in the custom ROM, but I don't think it works.

[Guide] Fix Yureka+ touch calibration issue.

Few days ago, while tinkering with my yu+, i decided to roll back to aosp kitkat (which came preinstalled). The ygpd flash was ok, except for the fact that my screen was all black (phone booted) and there was no yu logo. As usual, i booted to fastboot and flashed cm12.1. Booted, everything went fine only to notice that touch was not working properly. If i touched up it would register down. The main interesting thing was that, if i rebooted, the touch would work fine but as soon as i pressed the power button, it would malfunction. Same issue in twrp too.
These things mentioned below are the methods i tried to fix:
1) Flashing stock rom through YGPD again
2) Flashing stock rom through bootloader
3) Flashing rom through QFIL
4) Flashing stock touchscreen config though GptAdb Tool -reference link: https://forum.xda-developers.com/t/guide-fix-yureka-ao5510-touchscreen-calibration-issue.3488017/
As all hope was lost, i decided to contact our fellow hard working dev @abhishekt295
Back to the GptAdb tool, we tinkered and experimented all day, and found out that for some reason my yureka+ had the touch panel from "each" vendor, which comes with the yureka (AO5510), while the + variant( YU5510a) has the vendor "ofilm". They both have different values in their cfg.
Note: Check your touch firmware version in /sys/devices/virtual/touchscreen/touchscreen_dev/firmware_version file.
There are three vendors which are:
1) Each:GT970:0x1039
2) Ofilm:GT970:0x1039
3) Boen:GT970:0x1039:0x48
This post is applicable to those who have firmware version Each:GT970:0x1039
@abhishekt295 modified the cfg file, i flashed through gpt tool and DONE! My touch was back to normal.
Below is link for the modified cfg by @abhishekt295. You can find the tool and instructions in the reference link above, just be sure to use the cfg given here.
Link: https://androidfilehost.com/?fid=7161016148664782334
Endnote: While my device is working again, i would like to thank abhishek for his continuous efforts all day long. I gave up hope for my device, and was going to shell out money for new panel, but he didn't gave up and in the end fixed the issue. All credits to him.