Hello, I am trying to return to stock for Miitomo/Android Pay to work on my G3-VS985 from CM13 nightlies with the last LP radios and boostack of 35B
Essentially what happens on all flashing methods is it fails to install the mtp drivers, and fails to connect regardless of OS bitness and version (Win10x64 and Win7x32 tested) and does not change the COM number on the phone's screen,
on one of the flashes it deleted the bootloader flash partition, and i re-flashed it in TWRP3, alongside all the 47A partitions except system and recovery, blaming possibly dead partitions of previous flashes, in hope to fix the flash mode
and here i am, stuck on just 47A flash mode which doesnt seem to respond enough to flash a KDZ or TOT
in the flash mode's status box it states "VUSER B60"
How likely am i to get this back up and running? and if so, how would i go about this?
THIS HAS BEEN FIXED, BAD CABLE
Glad you solved your problem! In the future, please put questions in the Q&A section. I'll notify a mod to move it.
You can also edit the title of your thread in the Advanced edit view, and put "SOLVED" in the title.
Edit: Also, are you sure your HD2 is dead? Or just resting? (Sorry, Monty Python reference)
{
"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"
}
Related
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
Hi Guy's,
I think I may have made a really blooming stupid mistake. After re-flashing stock due to some funny errors in my rooted rom I attempted to enter the bootloader again and flash trwp without unlocking the bootloader. I had the same adb window open from my first root and cycled through the commands and simply pressed the wrong command
So I'm in the infamous yellow "lock the bootloader" problem wherein it simply boots me into the firmware update. I had tried to do my previous restore to stock with LGUP that was successful however it throws up an error now as I believe it doesn't like that I updated in the mean time from buggering my phone up. (see attached pic) I have also tried to use a kdz for the 10i found here from the forum to only have LGUP crash upon initiating usb connection at 3%.
I know of no way to go back at lock/unlock the bootloader and I do apologise for the inconvenience but any help or pointers would be greatly appreciated.
Thanks a million!
{
"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
Solved the problem now feel free to close this thread
ChrisNelson93 said:
Solved the problem now feel free to close this thread
Click to expand...
Click to collapse
For future people in your situation. Care to give details on how you fixed issue?
Nick216ohio said:
For future people in your situation. Care to give details on how you fixed issue?
Click to expand...
Click to collapse
"LGUP crash upon initiating usb connection at 3%..."
Maybe replacing dll file solved crash problem of LGUP and he flashed the stock Rom.
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
Hi! I'm posting here because of the low grade (xda doesn't allow me to post in the developing section).
I was running Lineage OS (2018-01-02) when I got an update notification (version 2018-01-23).
I tapped on "Flash" and it automatically rebooted into recovery (twrp-3.2.1-0).
Something went wrong, so I had to manually select the zip file from the lineageos_update directory (/data/lineageos_update).
The flashing process ended without any errors, but when it automatically rebooted it couldn't load boot: it rebooted into recovery.
I manually selected "Reboot into system" from the main menu, but it booted into recovery again.
Then I decided to restore my previous complete nandroid backup (Fulmics Rom, Stock based) but I got a bootloop.
I tried to full wipe the device using LGUP Store (version 1.14.3) combined with Uppercut (version 1.0.0.0) and the proper DLL extracted by the KDZ using a tool called LGFirmwareExtract-1.2.6.1, but the REFURBISH option gives me that error:
{
"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"
}
so that the only thing I've been able to do was choose the UPGRADE function in LGUP, but bootloop didn't solved and twrp recovery have been replaced with the stock one.
The KDZ files I tried to flash were:
H85020s_00_OPEN_EU_OP_1114.kdz
H85020a_00_OPEN_EU_OP_1030.kdz
H85010C_00_OPEN_EU_OP_0415.kdz
Can somebody please help me?
You already posted in the LOS thread, so why make a new one?
It may be that Lineage messed up your misc partition, think I've read about something like that before.
Yes and it has been answered in there a few times as well, the last time just yesterday: https://forum.xda-developers.com/showpost.php?p=75324443&postcount=2881
Hi,
Maybe, this could help: https://forum.xda-developers.com/showpost.php?p=71797169&postcount=2
I had the same problem with the stock ROM. My phone only booted to twrp.
Hello all I hope someone can help me out here?
I am trying to install Magisk on my Samsung A10S A107F device. I have got a stock set of firmware, which I have used with ODIN 3.14.1 to recover the phone after a couple of errors that I made during my learning process, so I know that ODIN and my stock F/W works. The stock F/W is Android 9.
Here's my problem, whenever I try to flash a Magisk patched AP to the device, ODIN stops at RQT_CLOSE!! and does nothing else. No success or failure, just stops there. I feel like it I am doing something obviously wrong but cannot figure it out. After around 5 minutes, it does timeout and then show a failure.
I've Magisk patched the whole AP file from stock and also extracted the boot.img only and patched a tar or that as well, but exactly the same result.
I've watched a number of videos on the process but can't see any difference.
Is there something security related that's being tripped in the Samsung F/W to prevent the new patched boot/AP flashing?
The OEM unlock option is on and greyed out in my phone's Developer Options menu.
After ODIN fails/stops, the phone can be restarted and is just the same as it was before.
{
"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"
}
Did you try another USB port or another USB Cable?
If yes, then try another ODIN version.
Final resolution is to try to flash from another PC or laptop.