[Q] Flashing Basics, who can tell? - Android Q&A, Help & Troubleshooting

HI,
After flashing a numerous HTC HD2 and Note N7000 i got now stuck with a Chinese Clone.
I flashed a lot of ROM on this phone and finally i got one working with playstore and working IMEI (which disappeared after the first flash)
I probably made a mistake to choos Format All in SP Flashtool and flashed the latest ROM that was working. All went fine and he started.
Then something strange happened. The whole touchscreen is working but on the wrong places, i can activate all menu's etc. But i have to click in the middle to get up and the back and menu touch are just on the screen not on the bottom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looking at flash tool it has a warning with manually format that calibration could be lost, is that what happend ?
I tried numerous other roms the install and work but not the touchscreen.
I found out which displaydriver i got (1-nt35590_hd720_dsi_cmd_truly) but no corresponding ROMS for my phone but ROM for other phone
Can somebody tell me if they should be mergable? Or how to flash the calibrationdata ? I inserted other nvram.img files with succes to get an IMEI. Is there a files i have to insert to get the correct LCD/Touchscreendriver?
I know that there are 2 preloader type that make my phone alive. After reading many hours i suspect that uboot.img could be the file, althugh i now come across ramdisk.img
(YES I WAS STUPID ENOUGH TO FORGET TO MAKE A BACKUP OF THE ORIGINAL ROM)
After four week straight in a row testing more that 50 ROM and not getting the original from seller the phone is send back to china. I looks like a hardware failure

Related

[Q] brick? modem n/a

hello everybody.
Here is the story, a friend of mine tried to install a custom rom on its brand new galaxy s3 and messed all things up. He came to me and we installed back an original rom, but we got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
for what I understand, he isn't able to make the modem work, and the camera maybe. He told me he have done "something" to the efs partition, so I thought he messed up that. But esf files are all there and it seems the phone still have a valid imei (353*********151).
We were unable to recover it so we restored everything, resetted the counter, and bring it to assistance for warranty. They told us that there is a crack in the main board and they have to change it
They also said that there is a problem with the screen and it has to be changed. But it seems fine to us!
They also told us that those operations are not covered by warranty, and we have to pay 270 euros!!
Now we are looking for an alternative solution. It sound strange to me that is a hardware problem, because it happened when my friend started to play with the OS. Any suggestion? anything we can try before changing the mainboard?
any help will be appreciated!!
this is factory mode, use search
Glebun said:
this is factory mode, use search
Click to expand...
Click to collapse
LOL
thank you!! I managed to fix it, saving 270 euros !!
XDA vs samsung assistance 3 - 0

[Q] Hard brick Blu Dash 5.0, SP Tools doesn't work. Drivers issue?

Hey guys, how are you?
I will try to explain what suceed to me yesterday...
My wifey Blu Dash 5.0 was on KitKat original rom, and since she doesn't liked it I tried to restore to a 4.2.2 backup. First thing I did was root it using VRoot. Using Mtk Droid Tools I did a rom and IMEI backup. So far so good...
Next thing I did was trying to install a custom recovery to be able to flash 4.2.2 rom. And here started the cause of all of my problems! At first I noticed every recovery I flashed wasn't compatible with KK. After flashing, when I tried to boot in recovery I always ended with a black screen and the phone booting normally after a few seconds. At this point I was becoming a little concerned about this, but it's ok... I had my phone backup. What could go wrong? My mistake. When I tried to download my backup back to the phone using SP Flash Tool v5.13 I received an error message like the one in the picture above and the phone didn't powered on anymore. When connected to the charger battery indicator didn't showed anymore...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried every button sequence I heard about while powering on the phone but nothing actually works. Already tried to remove all the MTK drivers using usddeview and reinstalling again but at this point I'm not sure drivers are being installed correctly.
There is any way to unbrick this? Anything I should try? USB jig maybe?
Any good soul could help me, please?
Thanks in advance and sorry for my bad english
Try my thread to see if that helps if not I will see what I can do to help.
Thread is below:
http://forum.xda-developers.com/and.../blu-dash-5-0-d410a-stock-rom-images-t2967900

Lg K7 Unstable connection avoid flashing

Hi , I think I probably f*kc up something. My sister just changed his phone to a new one so I borrowed his old Lg K7 x210 3G (I just post all the info I have about the model cause I don't really know exactly which one is) Well I unloaded the Bootloader and tried to change the recovery. I fallowed the steps of the guide but at the end I finished having the "No Command" error . This got me nervous and I started to touch things without knowing what I was doing (really, REALLY bad idea )
So the phone got stuck on a bootloop , well time to flash to get rid of the loop. The main problem is that I can't flash anything (except for the preloader) because it disconects all the time. I installed 20 different drivers and Sp Flash Tools versions (erasing the old ones with USBDeview )
These are the two states that jumps every 2 seconds.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What can I do to avoid this "jumps" and flash the rom correctly to the phone?
I tried 2 different pc , all the ports in this pc and all the cables I could find at home
PS: This are the different guides and tutorials I tried but failed.
https://forum.xda-developers.com/showthread.php?t=1982587 (It can't connect to the lg app because the "jumping" issue )
https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033 (Tried these on a W10 computer but again the device cant stay connect for more than 2 seconds )
https://www.youtube.com/watch?v=A3TmXtOA0IA
Thanks for your help . I don't want to give so early I think it could be fixed.

LG Stylo 3 Plus stuck at boot

So, I decided to delete some bloatware, ended up deleting the bloatware that kept my phone running and now I can only go on TWRP, I have no backup and LG hasn't released the stock yet so I guess I have to wait for my dead phone to get a stock rom? That is unless there's another way?
Welcome Back...
Calcious said:
So, I decided to delete some bloatware, ended up deleting the bloatware that kept my phone running and now I can only go on TWRP, I have no backup and LG hasn't released the stock yet so I guess I have to wait for my dead phone to get a stock rom? That is unless there's another way?
Click to expand...
Click to collapse
1) Download The Latest LG Drivers For Your Computer..
2) Install The LG Tool Software..
3) Connect With Your Original Charge / Data Cable..
4) Select "Update Recovery"..
5) Relax... It Will Be A While..
Welcome Back To The World Of The Living Phones.... And To *10c*...
I did the same thing. spent a couple hours trying to fix it. LgTool tells me phone is on current software and refuses to do an update even from the recovery console. scratching my head on this one...
LG Mobile Support Tool Errors out. Extracted KDZ image for system.img cant be flashed with TWRP (Something along the lines of the file being too big).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Problem solved:
https://forum.xda-developers.com/android/development/guide-restoring-soft-brick-mp450-stylo-t3681130

Note 5 possibly bricked/droidcam

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have an old Note 5 lying around with a cracked screen. Not worth using except as a backup, not worth selling. I had a great idea: use it as a webcam!
I downloaded droidcam, used it a few times, forgot all about it. Until yesterday.
I turned on the phone and the screen was as in the attachment. I used Android Control to mirror the screen to my PC (effortlessly) and make sure the phone was actually working. I figured that the last time I used the phone, I had actually left the phone connected to droidcam for a long time (forgot about it) and it may have done something to the display driver or some such. No biggie, I'll just reflash, maybe it'll solve the problem, maybe not.
After some struggle, got the phone into download mode and used Odin to attempt to flash 3 different firmwares, all for my SM-920 XSG (UAE firmware). The first time it made it all the way to the end when it failed to write. The other two fail early on. I even attempted to flash a PIT, which worked and then everything failed after just as fast as before the PIT flashing.
So, anyone have any idea what's wrong with the phone's screen? It was working before and literally had been left alone on a table undisturbed. Also, it would be nice to unbrick the phone, so that I can donate it (as a working phone sans screen) or at least try to sell it online to someone who would fix the screen (or a local shop).
You don't tell me nevermind

Categories

Resources