Hi,
Need some help please.
Unlocked bootloader. Jellybean P769 V20F.
CWM is installed from what i can see from below.
:\Users\rj\Desktop\L769\fastboot\fastboot\yours>fastboot devices
09145AF61202200E fastboot
C:\Users\rj\Desktop\L769\fastboot\fastboot\yours>cd c:\android
c:\Android>fastboot flash recovery recovery-clockwork-touch-6.0.3.1-p760.img
sending 'recovery' (5898 KB)...
OKAY [ 3.036s]
writing 'recovery'...
OKAY [ 1.019s]
finished. total time: 4.063s
But i cannot get int recovery by pressing the key cominbation vol up+home+pwer. Phone just reboots
Thanks much!
ADB reboot recovery
So it tried adb reboot recovery. Boots into recovery. But the screen is upside down. I need to use a mirror to read the commands on the screen properly.
Interestingly screen is normal in regular mode
Touch is working.
Still wondering why key combination to boot into recovery is not working.??????
Thanks:fingers-crossed:
thankyouxda said:
Hi,
Need some help please.
Click to expand...
Click to collapse
Install busybox
Sent from my Nexus 7 using xda premium
you flashed the p760 recovery, you need the p769
http://forum.xda-developers.com/showpost.php?p=44300426&postcount=358
the key combination for twrp at boot is vol (-) + home + power (release power when lg logo appears)
the key combination for cwm is either vol up or down + plus the other two.
Another thing, fix the inverted lg logo (that's if you haven't done so already)
http://forum.xda-developers.com/showpost.php?p=44161955&postcount=310
Hi Kuma82,Thank you.
I'll try the 769 recovery you linked.and report.
Re: inverted logo. This is to fix Inverted logo in fastboot correct?, I do see inverted logo when i fastboot otherwise not.
Thanks!
---------------------------------------------------------------------------------------------------------------------------
Also jezus. Thanks for busybox suggestion. installed but didn't help in this case so far.
kuma82 said:
you flashed the p760 recovery, you need the p769
Another thing, fix the inverted lg logo (that's if you haven't done so already)
http://forum.xda-developers.com/showpost.php?p=44161955&postcount=310
Click to expand...
Click to collapse
Fastboot is suppose to be inverted. You must already be on the 20f u-boot, you don't need that zip.
CM 10.1 P769
1)Installled CWM and now the screen is not mirrored anymore. Thanks
Key combination to boot into recovery still not working. Phone gets to LG then splash screen comes and then shuts off.
ADB reboot recovery works though. Any ideas about why keycombo not working? Not sure if it is worth the time
2)TWRP installed. Works great. Key combination works. Guess i will keep TWRP
Thanks!
kuma82 said:
Fastboot is suppose to be inverted. You must already be on the 20f u-boot, you don't need that zip.
CM 10.1 P769
Click to expand...
Click to collapse
thankyouxda said:
1)Installled CWM and now the screen is not mirrored anymore. Thanks
Key combination to boot into recovery still not working. Phone gets to LG then splash screen comes and then shuts off.
ADB reboot recovery works though. Any ideas about why keycombo not working? Not sure if it is worth the time
2)TWRP installed. Works great. Key combination works. Guess i will keep TWRP
Thanks!
Click to expand...
Click to collapse
key combination o]n 20f uboot is "vol-" and "home"
never mind
Hellooo Lelus :laugh:
Thanks for dropping by. U have made life easier for a lot of L9 users.:good:
Respect!!
Lelus said:
key combination o]n 20f uboot is "vol-" and "home"
never mind
Click to expand...
Click to collapse
thankyouxda said:
Hi,
Need some help please.
Unlocked bootloader. Jellybean P769 V20F.
!
Click to expand...
Click to collapse
Hi! I am new to unlocking bootloaders. Can you pllease tell me how you unlocked your bootloader?
Hi.
Need some help please.
Sorry for my english, but don't say good English and writing by google translator.
I am new to the forum, but I've read tens of posts.
He writes here, because I have a similar problem.
I have a LG L9 P769 phone purchased in the USA. My soft it: T-Mobile V20f.kdz
For several days'm trying to install the Bootloader & CWM Recovery. But I can't run it.
I decided so to install TWRP, the same as "thankyouxda", because I can see that at him he is acting.
But after the installation and the restart I receive the LG screen with the Security Error.
I recovered the phone with UpTestEX_BY_BRIDE_ 2014 program, but still I don't have Bootloader & CWM Recovery.
What am I doing wrong?!
Any program that installs Recovery at normal operating your phone and waiting for 50 minutes for me does not work. Everyone is only restarting my phone.
Only this method applies:
I run phone C/W Update (Vol Up + plug USB cable). I install the drivers and I type this command:
Code:
Plug USB cable
wait 4 seconds and put battery back in.
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x4
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 9ed4cae7db55647eff3ed3cc853e28ece762f077
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 9c669ad9
CRC1: 682adccf
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-lelelel...
[*] msg size = 4
usb_write 21552[*] data size = 21552
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
Microsoft Windows [Wersja 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Wszelkie prawa zastrzeżone.
C:\fastboot\yours>
I have a mirror screen LG.
Now he is writing the command:
Code:
C:\fastboot\yours>fastboot devices
014FBECB02002010 fastboot
C:\fastboot\yours>fastboot flash recovery recovery.img
sending 'recovery' (6786 KB)...
OKAY [ 3.536s]
writing 'recovery'...
OKAY [ 1.756s]
finished. total time: 5.292s
C:\fastboot\yours>
But CWM does not start, any combination of the phone keys. I tried to install different cwm.img
So I downloaded the TWRP-769.zip, unpacked, moved twrp.img file to the directory of fastboot and I type:
Code:
C:\fastboot\yours>fastboot flash recovery twrp.img
.......
I'm sorry, but I did with this copy, but it looks like the CWM and writes OKEY, finished ...
It seemed, however, that everything went well. But the installed file is probably too large (10 240 kB)!?
Other CWM.img that I tried to install took only 6 500 - 6 900 kB.
What am I doing wrong that after reboot the phone getting the LG Security Error?
1) Should I install busyboox at first?
2) Should I install 20f_u-boot.zip first, to the mirror screen LG? How does it install?
3) What is the META-INF directory, and if it is needed for installation twrp.img?
Very much please help me.
thankyouxda said:
1)Installled CWM and now the screen is not mirrored anymore. Thanks
Key combination to boot into recovery still not working. Phone gets to LG then splash screen comes and then shuts off.
ADB reboot recovery works though. Any ideas about why keycombo not working? Not sure if it is worth the time
2)TWRP installed. Works great. Key combination works. Guess i will keep TWRP
Thanks!
Click to expand...
Click to collapse
In case anyone still has issue with key combo booting into cwm you must release volume up at vibrate on lg logo but keep holding the power and menu keys.
I guess I'll repeat it for the umpteenth time. You need to unlock the bootloader.
Sent from my LG-P769 using XDA Premium 4 mobile app
Related
My gtab starts up and displays the viewsonic logo but will not boot into the ROM and will not boot into recovery mode.
when it is powered on normally the viewsonic logo appears and a black bar shows at the bottom of the screen a few seconds later.
power & volume+ show "detect a recovery key pressed" and "booting recovery kernal image". nothing more happens, even with a recovery image loaded onto the sdcard.
I am quite sure that i need to repartition, but i am at a loss of how to do so.
things that i have tried:
1.http://viewsonic-gtablet-for-dummies.webs.com/
tried everything, even the 'nuke from orbit' option of FORMAT_nvflash. tried both 1.1 and 1.2 images, would not boot into any stock recovery rom. tried holding the volume+ key during flash, still would not boot into recovery.
2. http://forum.xda-developers.com/showpost.php?p=12220001&postcount=1
same results as above.
3.http://forum.xda-developers.com/showthread.php?t=1091304
same.
I'm down to the point where i'm going to open it up to see if there is a loose connector or something.
anybody have a better idea?
mrchew1982 said:
My gtab starts up and displays the viewsonic logo but will not boot into the ROM and will not boot into recovery mode.
when it is powered on normally the viewsonic logo appears and a black bar shows at the bottom of the screen a few seconds later.
power & volume+ show "detect a recovery key pressed" and "booting recovery kernal image". nothing more happens, even with a recovery image loaded onto the sdcard.
I am quite sure that i need to repartition, but i am at a loss of how to do so.
things that i have tried:
1.http://viewsonic-gtablet-for-dummies.webs.com/
tried everything, even the 'nuke from orbit' option of FORMAT_nvflash. tried both 1.1 and 1.2 images, would not boot into any stock recovery rom. tried holding the volume+ key during flash, still would not boot into recovery.
2. http://forum.xda-developers.com/showpost.php?p=12220001&postcount=1
same results as above.
3.http://forum.xda-developers.com/showthread.php?t=1091304
same.
I'm down to the point where i'm going to open it up to see if there is a loose connector or something.
anybody have a better idea?
Click to expand...
Click to collapse
It's not bricked.
No need to open at this point.
The links you have looked at are very good starting point.
you may need to put your tablet in APX mode to NVflash a recovery.
APX is power off. Power on with VOLUME (-) (not vol+) and hold until a black screen pops up.
If you have the correct drivers, your PC should recognize the tablet.
You can run the nvflash.bat at this point
I recommend using the method HERE. This is one of the ORIGINAL NVFlash posts for the GTab. I have also posted my own nvflash folder for windows users HERE there is both a 1.1 and 1.2 bootloader version up there.
APX mode blues
Thanks for the quick replies.
I have re-flashed the tablet using APX mode about 20 times already. Both 1.1 and 1.2 branches. With and without cwm. Multiple tries with each image to make sure that there wasn't an error.
I have used the "FORMAT" flash as well, received the mismatch error. flashed all four versions of roms (1.1, 1.1cwm, 1.2, 1.2cwm) after redoing the "FORMAT".
Still nothing. It hangs on the boot image. If I attempt to enter recovery mode it hangs after displaying the text. Even if I hold volume+ during flashing so that it will go directly into recovery mode after the flash.
I know that it is taking the flash, one of the images that I tried has the Tegra logo instead of the Viewsonic as the boot screen. NVflash completes every time without error.
I am really at the end of my rope here as I haven't been able to find anyone that couldn't get into recovery after flashing.
Thanks for the help, any further suggestions would be greatly appreciated!
p.s. I tried once more tonight using Roebeet's instructions and the NVflash Pixelrider provided just to make sure that i didn't miss a step. Still hanging on the boot screen...
Try this:
1. nvflash back to a stock ROM (1.1 or 1.2). I strongly recommend bekit's original 1.1 images.
2. power off before the gTab boots into the stock ROM you just nvflashed.
3. put gTab into APX mode and run this command:
Code:
C:\> [B].\nvflash --bl bootloader.bin --format_partition 7 --format_partition 12 --go[/B]
The tablet will try to boot into the stock ROM (for the first time).
still no luck!
Thank you very much for the reply. Something new to try! Unfortunately it still freezes up.
recap:
Downloaded the "bekit 1105" image (nvflash_windows_20100500.zip)from Roebeet's sticky and the windows version of nvflash. Unzipped both into a folder on my desktop. 30 files weighing in at 202MB. (ADX drivers for Windows7x64 were previously manually installed through Device Manager)
Started gtab with "volume-" button depressed. Screen flashed on with Viewsonic logo then flashed off. Attached usb cable. Heard connection sound from Windows.
Opened folder previously mentioned, double clicked nvflash_gtab.bat. Clicked "Run" on warning popup.
cmd.exe window pops up:
Code:
C:\Users\Desktop\Desktop\bekit1105>"nvflash.exe" --bct gtablet.bct --setbct --bl
bootloader.bin --configfile gtablet.cfg --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714118842bf5057
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: gtablet.bct
- 4080/4080 bytes sent
gtablet.bct sent successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBT
creating partition: BLO
creating partition: MSC
creating partition: OGO
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBT please wait.. done!
Formatting partition 6 BLO please wait.. done!
Formatting partition 7 MSC please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. done!
done!
sending file: part4.img
/ 2097152/2097152 bytes sent
part4.img sent successfully
sending file: part5.img
\ 131072/131072 bytes sent
part5.img sent successfully
sending file: part6.img
/ 4194304/4194304 bytes sent
part6.img sent successfully
sending file: part7.img
/ 16777216/16777216 bytes sent
part7.img sent successfully
sending file: part8.img
/ 33554432/33554432 bytes sent
part8.img sent successfully
sending file: part9.img
/ 16777216/16777216 bytes sent
part9.img sent successfully
sending file: part10.img
/ 16777216/16777216 bytes sent
part10.img sent successfully
sending file: system.img
\ 117292032/117292032 bytes sent
system.img sent successfully
Press enter to continue:
(did not press key yet...)
turned gtab off using power button. Disconnected usb and pressed key to exit NvFlash_gtab.bat window.
Turned gtab on whilst pressing "Volume-". Screen flashes on then goes blank. Windows plays connect sound.
Ran command:
C:\Users\Desktop\Desktop\bekit1105>nvflash --bl bootloader.bin --format_partition 7 --format_partition 12 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714118842bf5057
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Formatting partition 7 please wait.. done!
Formatting partition 12 please wait.. done!
C:\Users\Desktop\Desktop\bekit1105>
Click to expand...
Click to collapse
Tablet shows "Entering NvFlash recovery mode / Nv3p Server". Nothing else happens.
Waited 10 minutes. powered off using button, disconnected USB. Powered back on, Viewsonic logo appears, black bar flashes onto bottom of the screen, and...
Nothing else happens!
Waited another 10 minutes. Tried to get into recovery mode using "Volume+", still hangs, even with an image on the microsd card. Tried the whole thing over again, still nothing.
The fact that it never reboots after nvflash has me worried that there is something deeply wrong. Is there a way that I could repartition and totally wipe it via nvflash?
This thing is stubborn! Still hoping to find a solution...
Thank you again for the help!
mrchew1982 said:
Tablet shows "Entering NvFlash recovery mode / Nv3p Server". Nothing else happens.
Click to expand...
Click to collapse
The ``--go'' parameter to nvflash will cause the bootloader to try to boot into the ROM after the requested actions complete. Without a ``--go'' parameter, the bootloader will wait to further commands and you'll have to power off. If the gTab did not boot into the ROM with ``--go'' then something is wrong.
BTW, does adb work in recovery mode? Run this command:
Code:
C:\> [B]adb shell dmesg > dmesg.txt[/B]
and post that text file here if it was any output.
Right now it looks like I'll have to build a custom recovery for you to test things out. In the mean time, try the procedures in this post one by one. See if any of them help. And, stick to bekit's recovery until we resolve this.
Thank you!
Thank you!
I will setup adb later tonight and give it a try. I was reading up on it elsewhere. It will be interesting to see if it responds.
Would hitting the reset button on the motherboard do any good? I have opened the case before to re-solder the power connector...
Thank you, can't say that enough!
mrchew1982 said:
Would hitting the reset button on the motherboard do any good?
Click to expand...
Click to collapse
Try it.
I have opened the case before to re-solder the power connector...
Click to expand...
Click to collapse
Hmm. Now this can't be coincidence, can it? User raywaldo on this board is reporting the same problem after he soldered wires to fix his loose connector. See this thread where I mention this.
Ordinarily, based on the symptoms, I would've said that this was a bootloader incompatibility problem. But, both of you have done a full nvflash, so that's out. I'm leaning towards a HW fault right now, but, we'll need more data to make a definitive determination.
As I said, try out the other procedures first (and don't have a micro SD card with the CWM update file in it while you're doing those procedures--the stock recovery will try to install update.zip files if it finds them; CWM will not). If none of them work, then I'll send you a custom recovery image which will let us know if the bootloader did actually load and run the recovery/std kernel.
no adb. reset didn't change anything.
Thank you for sticking with me rajeevvp.
I installed the android sdk (and JDK) per the instructions:
http://www.androidtablets.net/forum/viewsonic-gtablet-technical/5377-adb-g-tab-step-step.html
I used SDK manager to download the platform tools and the google usb driver. Followed the instructions to uninstall the NvFlash driver and installed it as a composite ADB per the instructions. When i started the tablet normally it loads the usb storage device drive and assigns it drive letter E: (which never shows up in "My Computer" and says "Device not ready" from cmd prompt).
It would only connect as an ADB device when i put it into APX mode, which i don't think is right...
It showed up under USB deview, but said that the driver was winusb.sys, which doesn't sound right to me either...
used the echo command, ran "adb kill-server" and "adb devices". it didn't show anything connected.
next i tried the command that you posted and it said "access is denied".
so i went the other route and popped the case back open. tried all four methods for hardware reset (unplugging battery, shorting capacitors, reset button and shorting the four solder pads), no change in behavior...
The link from wroark is interesting. I am leaning towards hardware damage as well because i have never gotten a complete boot out of it since the repair. Maybe i bungled something up, and only made it worse with the flashing...
I am looking for damage on the PCB but haven't found any yet. I will desolder the power connector later tonight and give it a bath in some PCB cleaning spray.
Thanks for your help once again!
mrchew1982 said:
so i went the other route and popped the case back open. tried all four methods for hardware reset (unplugging battery, shorting capacitors, reset button and shorting the four solder pads), no change in behavior...
Click to expand...
Click to collapse
Try that adb command on Linux; Windows is too much pain--don't want to troubleshoot an "ADB is not working" problem too.
The link from wroark is interesting. I am leaning towards hardware damage as well because i have never gotten a complete boot out of it since the repair. Maybe i bungled something up, and only made it worse with the flashing...
Click to expand...
Click to collapse
Go through this thread as well.
OK. Now for some troubleshooting.
1. Remove any external microSD cards, as always.
2. Put gTab into APX mode and run this command:
Code:
C:\SOME\PATH> [B].\nvflash --bl bootloader.bin --format_partition 7 --format_partition 8 --format_partition 9 --format_partition 10 --format_partition 12 --download 9 recovery.img --download 10 recovery.img --go[/B]
This will format all the problemmatic partitions and then upload CWM-2.5.1.1-bekit-0.8 with a different kernel onto both the "recovery" and "boot" partitions. The kernel has been modified to print boot-up messages as it does on standard Linux. If the bootloader loads and runs either kernel ("boot" or "recovery") then you should see, first, the 2 penguins logo (one for each processor), and then, the kernel messages below that. After the kernel finishes, /init will run, clear the screen, and print "ANDROID" in small caps, and then CWM should start.
3. Use the bootloader.bin--which is from 1.1-3588, the last VS 1.1 update--and the recovery.img in the zip attachment.
surgery done...
I wasn't happy with the solder joints that I laid on last time, it looked like I might have bridged two of the pads... so I removed the power connector completely only to find that the housing was split down the middle. Found a new connector (perfect match here: http://www.dcpowerjacks.net/catalog/index.php?main_page=product_info&cPath=15&products_id=202), got it today. Cleaned the pads and carefully connected the new one. sprayed everything clean, it looked great afterwords, but no change in behavior... I didn't see anything loose or missing either when I went over it with the magnifying glass.
Ok, reflashed per your instructions. here is the output:
Code:
C:\Users\Desktop\Desktop\bekit1105>nvflash --bl bootloader.bin --format_partition 7 --format_partition 8 --format_partition 9 --format_partition 10 --format_partition 12 --download 9 recovery.img --download 10 recovery.img --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714118842bf5057
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928940/928940 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Formatting partition 7 please wait.. done!
Formatting partition 8 please wait.. done!
Formatting partition 9 please wait.. done!
Formatting partition 10 please wait.. done!
Formatting partition 12 please wait.. done!
sending file: recovery.img
| 3598336/3598336 bytes sent
recovery.img sent successfully
sending file: recovery.img
| 3598336/3598336 bytes sent
recovery.img sent successfully
C:\Users\Desktop\Desktop\bekit1105>
It rebooted into the screen that you described but stopped short of going into clockwork. for a long time the last lines were:
Code:
19.213803 so340010_kbd: probe of so340010_kbd failed with error -1
19.217161
19.217164 I2C Slave is *New*
19.820563 NvOdmMouseDeviceOpen failed
20.019509 android_usb Gadget: high speed config #1: android
I then heard the USB connection sound and windows notified me that a USB storage device had been installed (no drive shows up in "My Computer").
Then it started reprinting an error message about every 5 minutes:
Code:
257.010389 INFO: task cpufreq-dvfsd:286 blocked for more than 120 seconds.
257.013674 "echo 0 > /proc/sys/kernal/hung_task_timeout_secs" disables this message.
257.016995 cpufreq-dvfsd D c050ac38 0 286 2 0x00000000
{continued from reboot}
246.807349 Backtrace:
246.810534 (<c050a11c>) (schedule+0x0/0xc18) from (<c00e1680>) (kthread+0x70/0x90)
246.813892 (<c00e1610>) (kthread+oxo/0x90) from (<c00c8498>) (do_exit+0x0/0x73c)
246.817285 r7:00000000 r6:00000000 r5:0000000 r4:0000000
366.817615 INFO: {then it repeats verbatim}
After repeating 3-4times then it goes to a page with just a bunch of numbers inside of parenthesis on the left hand side (counter overran the buffer?) and no text on the right.
When I rebooted it without the USB attached the last message shown is "NvOdmMouseDeviceOpen failed" before it went into the "INFO" error messages.
Still think its a hardware problem?
I will get a linux boot CD setup to try ADB mode again, but i'm hoping that the messages above will be enough to figure this out.
Thank you, once again, for your time and help.
pictures...
Just in case I missed something, I attached some screenshots.
they are in chronological order, 989 is before the "INFO:" error messages pop up, 990 shows those error messages, and 991 is the final screen with no messages.
Thanks for the screenshots. Judging from the visible kernel messages, this looks very much like a hardware fault. The "so340010_kbd" is the driver for the soft keys to the right of the display. The error messages indicate a failure to communicate with the controller for those soft-keys.
I suggest that you start at those soft-key pads and trace the lines back to their controller chip then scrutinize the circuit traces from this chip all the way back to the CPU. See if everything looks OK.
Try ADB on Linux, but, I don't hold out much hope for getting anything out of it: The kernel looks like it is having serious problems with the hardware--I don't think it has even got around to starting up the user-land processes. And, don't worry about the INFO messages relating to cpufreq-dvfsd. You can disregard them for the moment.
EDIT: A thought just struck me. It's winter-time over there, right. Did you take the proper precautions while handling the board? It's very easy to fry a chip silently this time of the year over there using ESD: walk on the carpet, pick up a load of static electricity, then toast something with a simple touch. I borked a board like that one time I was there.
bricked
i have been having same problems with my g-tab, i tried the modified recovery and was able to get to clockwork. i tried updating to few roms, i have NVflashed 100 times. Everytime i NVflash, it shows the tapNtap boot screen, it cycles through this for 4 to 5 times, then just shuts off. Then i try to start again, get nothing, can only go into APX mode which i can only do NVflash and just does same thing. So i tried the modified recovery, goes to clockwork and tried installing other roms, installs without problem, but when restart system will not boot at all. Just black screen and can only do APX mode... also tried opening case unplugging battery, pressing reset button on motherboard... i think the internal SD needs to be completely wiped and no matter what tool i have used, there is still data there.
theterminator69 said:
i have been having same problems with my g-tab,...
Click to expand...
Click to collapse
If you can boot into CWM and install ROMs, then you don't have the same problem. And, that modified CWM was meant to be a diagnostic aid--it was not intended to be a cure for gTab illnesses.
i think the internal SD needs to be completely wiped and no matter what tool i have used, there is still data there.
Click to expand...
Click to collapse
Is the data still there after you "Partition SD card" in CWM? Make sure you remove any external microSD cards from the tablet first.
hi 4 all i have p768 y try to root but pc stuck and need restar after this phone only detect with omaap mode no power on no enter swupgrade mode nothing only omap pls aony one can help me with this phone ???
waltercell said:
hi 4 all i have p768 y try to root but pc stuck and need restar after this phone only detect with omaap mode no power on no enter swupgrade mode nothing only omap pls aony one can help me with this phone ???
Click to expand...
Click to collapse
there's a new routing method for our device... it's a simple to use app that does everything for you... follow the link forum.xda-developers.com/showthread.php?t=2338816
Swag-Mo said:
there's a new routing method for our device... it's a simple to use app that does everything for you... follow the link forum.xda-developers.com/showthread.php?t=2338816
Click to expand...
Click to collapse
thks brow 4 u reply but my phone dont power on more only detect omap mode i need repair firts
pls any can help me pls
waltercell said:
pls any can help me pls
Click to expand...
Click to collapse
use fastboot to flash ics xloader and uboot, put your phone into s/w upgrade mode(steps 1-5)
, try original lg tool
http://forum.xda-developers.com/showpost.php?p=39879519&postcount=10 or offline method to restore your phone
thhks y try now and post result
y try but now stuck on wait devices
waltercell said:
y try but now stuck on wait devices
Click to expand...
Click to collapse
try running it as an admin
Lelus said:
try running it as an admin
Click to expand...
Click to collapse
hi lelus y try wiht admin but same in 1 stage detect phone noormal rum soft but in 2 stage say waiting devica
ECHO está desativado.
Plug USB cable
wait 4 seconds and put battery back in.
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x4
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 8ba4bd0df0e467ec6459c7ecba88a3b048caa854
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 9c669ad9
CRC1: 682adccf
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-lelelel...
[*] msg size = 4
usb_write 21552
[*] data size = 21552
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
< waiting for device >
plss dont forgett me >crying:
waltercell said:
plss dont forgett me >crying:
Click to expand...
Click to collapse
Try different computer or are you familiar with Linux ?
Lelus said:
Try different computer or are you familiar with Linux ?
Click to expand...
Click to collapse
i dont have linux onyl xp and w7
pls is posible send to phone this Rooted_CWM_BACKUP_P768_V10A_by_BaLiSTa in this mode :
waltercell said:
i dont have linux onyl xp and w7
pls is posible send to phone this Rooted_CWM_BACKUP_P768_V10A_by_BaLiSTa in this mode :
Click to expand...
Click to collapse
When it says waiting for device, have you tried unplugging and plugging back in quickly?
jlirgg said:
When it says waiting for device, have you tried unplugging and plugging back in quickly?
Click to expand...
Click to collapse
yep y try unplugg and plug again but nothin pc no detect phone anything mode but i f take outo battery and put again find omap again
Did you install the omap4 driver twice?
Open an elevated command prompt and type
Code:
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
devmgmt.msc
Then open the Device Manager and see if you have the omap4 driver installed twice (in two locations)
Note: In Device Manager click the View tab and select Show hidden devices
If you don't see the omap driver installed twice, do this
Select the "other devices" and start deleting/uninstalling all of the devices you find here
Once you have uninstalled all of the unknown drivers you found, run the start.bat again.
Now go back to device manager and find the new unknown/other device created and install the omap4430 like you did the first time.
After you have done all this, rerun the start.bat and hopefully it will work for you.
Another thing, If you do see the omap driver installed twice, then it has to be your timing when you enter the battery. Keep trying different times to enter the battery
example. First try this, DON'T WAIT 5 sec ENTER THE BATTERY lol
Then try
wait 1 second and enter battery, if that doesn't work wait 2 seconds and etc.
Good luck
Try with xp
Sent from my LG-P760 using Tapatalk 4 Beta
hi thks 4 u times >) well in device manage show only omap driver but after 2 seconds disconect and conect again omap no show any driver with lg mobile only omap
here pics
waltercell said:
hi thks 4 u times >) well in device manage show only omap driver but after 2 seconds disconect and conect again omap no show any driver with lg mobile only omap
here pics
Click to expand...
Click to collapse
Okay tell me everything you did. It seems like you are missing a step or two. Did you do this?
and if you did, did you uninstall all of the "other devices"
As of right now, just tell me step by step of everything you did.
Update
sorry i forgot to give you an important step, you need to type devmgmt.msc after you type SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
So sorry I forgot i have my system setup so I don't have to enter it every time
I added a Environment Variable inside advance system settings, you don't have to do this part
first many thks kuma82 4 u time
but friend i think is no pc or drivers because i try with 6 pc diferent lol yep i goo to my friend hode and try i have other p768 work noormally and all succes problem is in my phone
Sorry to hear it's just your phone. ;(
Sent from my LG-P769 using xda app-developers app
Hi.
Similar problem like here: http://forum.xda-developers.com/showthread.php?t=2334337
I am fighting with this phone two days.
In the first phase ( 18h ago) i connected by omap4boot and tried this - http://forum.xda-developers.com/showpost.php?p=39732470&postcount=20
next i did all wipes, i tried by cwm install this rom - u2_v20o_signed_022314_123556.zip
I thought all is good, but ofc still was logo LG.
Anyone LG FLash tool didnt work (i will explain it with screens after, when will can run into S/W mode)
I tried this http://forum.xda-developers.com/showthread.php?t=2292828
and i had very weird error:
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x4
Checksum Subblock: 0x15
CHIP: 4430
IDEN: b1a3cecb3e5a097ee4d9313e2070f8863ca117f3
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 9c669ad9
CRC1: 682adccf
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-lelelel...
[*] msg size = 4
usb_write 21552
[*] data size = 21552
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
< waiting for device >
sending 'x-loader' (384 KB)...
OKAY [ 0.204s]
writing 'x-loader'...
OKAY [ 2.845s]
finished. total time: 3.050s
sending 'u-boot' (1024 KB)...
FAILED (status read failed (Too many links))
finished. total time: 107.422s
Done
Click to expand...
Click to collapse
Then i tried all ideas, which came to my head.
(Relock bootloader http://forum.xda-developers.com/showthread.php?p=44580559
p760-twrp-2.6.1-recovery.img
and much other, which i didnt remember...)
Finaly phone is bricking.
Any advices?
Edit:
Yesterday battery had 4.01 V, today has 3.7. I will try charge tomorrow.
Guys, what when i-loaded u-boot, x-loader after like i flashed JB rom by CWM ?
It can explain my current situation?
Look:
It are partiton for JB
View attachment 3762143
It are partition for ICS
View attachment 3762144
So i should now load some loader and boot file from JB?
Can U help me, pls?
I downloaded ICS stock rom. Exctracted it.
I made x-loader from file 0-gpt1.img. (256LBA-1023LBA). It is exactly same what file p1ics760.bin from fastboot by Lelus http://forum.xda-developers.com/showthread.php?t=2292828 )
once again i tried:
fastboot flash x-loader
fastboot flash u-boot
fastboot flash boot
fastboot flash recovery
All files are original from ICS stock rom.
No result.....
works only fastboot mode by software fastboot by Lelus.
Srsly this topic is so boring?
Edit:
Hm... u-boot file from here http://forum.xda-developers.com/showpost.php?p=39732470&postcount=20
is different from mine... x-loader is same like i wrote early...
It weird:
In Fastboot by Lelus - if i use any option between 2 and 7 - i get:
sending 'u-boot' (1024 KB)...
FAILED (status read failed (Too many links))
finished. total time: 107.422s
So i replaced file:
\fastboot\xu\p2ics760.bin
for original stock u-boot (in second try i replaced u-boot from this link http://forum.xda-developers.com/showpost.php?p=39732470&postcount=20)
(original p2ics760.bin i renamed to p2ics760.bin.old and u-boot.img i renamed to p2ics760.bin
and still is error - Too many links
But when i use:
fastboot flash u-boot u-boot.img - it hasn't error. It is same file!
Maybe the operation is successful, but in real it doesen't change anything? Is it possible?
Groszexxx said:
It weird:
In Fastboot by Lelus - if i use any option between 2 and 7 - i get:
sending 'u-boot' (1024 KB)...
FAILED (status read failed (Too many links))
finished. total time: 107.422s
So i replaced file:
\fastboot\xu\p2ics760.bin
for original stock u-boot (in second try i replaced u-boot from this link http://forum.xda-developers.com/showpost.php?p=39732470&postcount=20)
(original p2ics760.bin i renamed to p2ics760.bin.old and u-boot.img i renamed to p2ics760.bin
and still is error - Too many links
But when i use:
fastboot flash u-boot u-boot.img - it hasn't error. It is same file!
Maybe the operation is successful, but in real it doesen't change anything? Is it possible?
Click to expand...
Click to collapse
If you can enter in lelus fastboot, then flash a recovery wipe partitions and then with the recovery flash a rom....
My english is such bad or u didnt read the all posts? .
I flashed recovery partition much time. Telefon still is dead. Stock recovery, CWM, TWRP.
If I could flash recovery and after could "instal" rom - then it would not be problem .
Groszexxx said:
My english is such bad or u didnt read the all posts? .
I flashed recovery partition much time. Telefon still is dead. Stock recovery, CWM, TWRP.
If I could flash recovery and after could "instal" rom - then it would not be problem .
Click to expand...
Click to collapse
Then, If your L9 doesn't boot, it could be beacause a "IC power Cristal" or other hardware issue like EMM break (Eprom). In some case a box like http://octopusbox.com can solve the problem or in other case extract a log file with the exact issue details
A dead block of flash will produce CRC errors after or during the flash process and random lockups or reboots during operation. And if the fastboot problem strikes, you can issue commands via ADB, but after the necessary reboot there will be the PnP sound loop. If the phone is in Charge-only mode, ADB commands will be ignored, you can issue them, but **** happens.
Was there any positive feedback for the flash commands?
puntoazul said:
Then, If your L9 doesn't boot, it could be beacause a "IC power Cristal" or other hardware issue like EMM break (Eprom). In some case a box like http://octopusbox.com can solve the problem or in other case extract a log file with the exact issue details
Click to expand...
Click to collapse
It can be true. I received similar diagnosis about corrupt emmc. Anyway - for me it is possible but very unlikely (Ofc i havent experience).
lecorbusier said:
A dead block of flash will produce CRC errors after or during the flash process and random lockups or reboots during operation. And if the fastboot problem strikes, you can issue commands via ADB, but after the necessary reboot there will be the PnP sound loop. If the phone is in Charge-only mode, ADB commands will be ignored, you can issue them, but **** happens.
Was there any positive feedback for the flash commands?
Click to expand...
Click to collapse
Maybe i will show it on screens:
I run Fastboot by Lelus and set 2 option.
View attachment 3765116
And i get error:
View attachment 3765119
When i run fastboot by Lelus and set option 1 and type:
fastboot flash recovery 'filename'
View attachment 3765117
EHh, Finaly i think theory with emmc corrupt is are confirming.... after 30-40x flashed now i get one new and one very common error:
View attachment 3765322
View attachment 3765324
I am so sad! . But anyway, i am feeling much better when i know what is wrong with phone.
U-boot gets sent to the phone's RAM, but writing to its appropiate partition fails utterly. That is not necessarily hardware related. And nothing I've seen before. Either the partition got damaged or deleted, or it's in F2FS format. Artas' CM11 uses F2FS, EdwinMoqs CM13 as an option, and TWRP from 2.8.x can format partitions with F2FS.
But D/L mode is almost indestructible, only a bit tricky to invoke. And requires LG drivers. Even if the phone is no longer getting recognized by LG drivers and LG software because of a custom rom, when in D/L mode the LG driver should install a virtual COM port and the LG flash tool should now recognize the phone. Ihad difficulties flashing a KDZ file with LG Fladh Tool 2014,but the tool from the LG site, getting the stock rom directly from the server, works reliably, but it's best to flash twice in a row. If the phone auto-reboots into launcher, it's a success. If you see LG's stock recovery after the flash, flash another time.
Ok. if you run this command: "fastboot flash u-boot u-boot.img" (assuming that the u-boot.img file is for your l9 model), and result is cannot write in partition then EMMC is break (95% probability)
---------- Post added at 09:16 AM ---------- Previous post was at 09:13 AM ----------
lecorbusier said:
U-boot gets sent to the phone's RAM, but writing to its appropiate partition fails utterly. That is not necessarily hardware related. And nothing I've seen before. Either the partition got damaged or deleted, or it's in F2FS format. Artas' CM11 uses F2FS, EdwinMoqs CM13 as an option, and TWRP from 2.8.x can format partitions with F2FS.
But D/L mode is almost indestructible, only a bit tricky to invoke. And requires LG drivers. Even if the phone is no longer getting recognized by LG drivers and LG software because of a custom rom, when in D/L mode the LG driver should install a virtual COM port and the LG flash tool should now recognize the phone. Ihad difficulties flashing a KDZ file with LG Fladh Tool 2014,but the tool from the LG site, getting the stock rom directly from the server, works reliably, but it's best to flash twice in a row. If the phone auto-reboots into launcher, it's a success. If you see LG's stock recovery after the flash, flash another time.
Click to expand...
Click to collapse
Could be... perhaps if use Lg flash tool 2014 in emergency mode... (5% probability but is more than nothing) i hope @Groszexxx can revive his device
and if i was you... i try this... (see attach)
Yes, i talked about octoplus with someone, who has it. I never had anyone box . It is not my job . I was only curious what is it with phone my friend. I spend much hours on this issue. Anyway, i dont regret.
I will send phone to someone, who can flash it by some box like octoplus or jtag.
Thanks for lecorbusier post. I read much post, but this one is new for me.
So - time saying goodbye .
Maybe i will inform what will be next, maybe not ;p. We will see .
Thanks for all!
Hello,
I have problem with my Lenovo P1m. After changing unresponsive screen with aftermarket one, phone is not booting. To be explicitly specific, phone is booting OEM ROM correctly, but I was using custom ROM of LineageOS 14.1 before screen replacement and now it is not working. My problem is - I can compile my own kernel with different screen drivers / options / etc as I am familiar with linux kernel itself, BUT - how do I debug bootloop, when the only thing I can dig from phone via TWRP recovery is following line from /proc/last_kmsg which, honestly, tells me nothing
Code:
ram console header, hw_status: 2, fiq step 0.
(previously, I got some error message about wrong kernel header as I was trying to compile kernel myself, but this is solved now - but no luck with bootloop either)
Scenario is like this: after power on, I have vibration and normal white Android screen, which if normal boot, is followed by animation and OS welcome. But now, the screen after is black, and after few seconds everything starts from begining - vibration, white android screen etc...
I cannot use adb at all, as it is not catching the phone in this situation, probably kernel is failing before adbd itself starts. I am using TWRP to extract /proc/last_kmsg but as mentioned before, no usable information.
Is there any other way to get kernel messages from boot process? (It would be besto to have something like dmesg output)
So, I see that nobody knows or wants to help, so I helped myself. Made cable as seen here: h t t p: // w w w .stevenhoneyman.co.uk/2014/11/mtk-mediatek-debug-cable.html
And now I at least have serial console. BUT - all output ends exactly when kernel is loaded. Any ideas how to get verbose output from kernel to uart? I tried to add printk.disable_uart=0 ignore_loglevel into commandline arguments for kernel, but no luck.
End of console output looks like:
Code:
[5940] [PROFILE] ------- boot_time takes 3053 ms --------
[LK_ENV]get_env hibboot
[LK_ENV]get_env resume
[5940] booting linux @ 0x40080000, ramdisk @ 0x44000000 (1611013)
[5940] [LEDS]LK: leds_deinit: LEDS off
[5940] [LEDS]LK: red level is 0
[5940] [LEDS]LK: green level is 0
[5940] [LEDS]LK: PMIC Type: 7, Level: 0
[5940] [LEDS]LK: blue level is 0
[5940] DRAM Rank :2
[5940] DRAM Rank[0] Start = 0x40000000, Size = 0x40000000
[5940] DRAM Rank[1] Start = 0x80000000, Size = 0x3ffc0000
[5940] cmdline: console=tty0 console=ttyMT0,921600n1 root=/dev/ram vmalloc=496M androidboot.hardware=mt6735 slub_max_order=0 slub_debug=O bootopt=64S3,32N2,64N2 androidboot.selinux=permissive buildvariant=userdebug printk.disable_uart=0 ignore_loglevel lcm=1-ili
[5940] lk boot time = 3053 ms
[5940] lk boot mode = 0
[5940] lk boot reason = wdt_by_pass_pwk
[5940] lk finished --> jump to linux kernel 64Bit
[5940]
[LK]jump to K64 0x40080000
[5940] smc jump
Key to get kernel boot output was finally in console on ttyMT1 instead of ttyMT0 (console=ttyMT1,921600n1)and also nousb parameter, so usb port will not switch to real usb during boot and remains uart. Now, I have found out that my kernel is missing some LCM driver, which was then re-compiled and now I have to find out what else is wrong...
Running out of ideas. Phone boots with old broken OEM display. If I connect new aftermarket display, it bootloops. Kernel logs attached for every case: old display, new display. Any ideas what goes wrong with new display?
NEW: https://pastebin.com/Ewz8FF5h
OLD: https://pastebin.com/CjtmA0aB
Code:
[ 14.143167] (0)[1:swapper/0][FTS] Step 1:Reset CTPM
[ 14.243788] (0)[1:swapper/0]hidi2c_to_stdi2c successful.
[ 14.263168] (0)[1:swapper/0][FTS] Step 2:Enter upgrade mode
[ 14.313857] (0)[1:swapper/0][FTS] Step 3: CTPM ID,ID1 = 0x0,ID2 = 0x0
[ 14.314917] (0)[1:swapper/0]ft5x0x 1-0070: [FTS] Step 3 fail: CTPM ID,ID1 = 0x0,ID2 = 0x0, 0x54, 0x2c:
[ 14.423169] (0)[1:swapper/0][FTS] Step 1:Reset CTPM
[ 14.473714] (0)[1:swapper/0]hidi2c_to_stdi2c successful.
[ 14.493166] (0)[1:swapper/0][FTS] Step 2:Enter upgrade mode
[ 14.543852] (0)[1:swapper/0][FTS] Step 3: CTPM ID,ID1 = 0x0,ID2 = 0x0
[ 14.544707] (0)[1:swapper/0]ft5x0x 1-0070: [FTS] Step 3 fail: CTPM ID,ID1 = 0x0,ID2 = 0x0, 0x54, 0x2c:
[ 14.653167] (0)[1:swapper/0][FTS] Step 1:Reset CTPM
THIS is the reason of problems. When I deconfigure FT5446 driver from kernel, system boots without problems. Only thing is that touchscreen is inoperative because of disabled driver. How to debug this issue?
I have resolved this issue for me. Hardcode-edited driver for FT5446 IC touchscreen to workaround firmware upgrade checking. Now I have operational P1m with aftermarket display under LOS 14.1 on 3.18.19 kernel. If anybody interested, here is boot.img for darklords LOS14.1 ROM lineage-14.1-20171119_095733-UNOFFICIAL-P1m.zip but I think it will work also for his other versions
https://uloz.to/!cuEWkiCv9flq/boot-img
can you share the changes you made to the kernel source
i have compared some changes that you shared , they can be seen in here
I bricked my phone (XT2041-1 "sofiar") by flashing an unnoficial build of TWRP 3.5.0 downloaded from a Telegram channel by doing:
$ fastboot flash recovery_a twrp-3.5.0-0-rav-sofia.img
$ fastboot flash recovery_b twrp-3.5.0-0-rav-sofia.img
$ fastboot reboot recovery
Since then, my phone is hard bricked - won't boot, recognized on Linux in EDL Mode only (i.e. ID 05c6:9008).
I got the latest official stock firmware, named SOFIAR_RETAIL_11_RPES31.Q4U-47-35-12_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, from lolinet, and in its contents there's boot.img and recovery.img (among others).
I have qdl on my Arch Linux, and am wondering whether I can use it to flash the stock recovery image back to both slots and get my phone booting again.
How should I approach it?
P.s. I also got a blankflash from https://forum.xda-developers.com/t/...equest-solicitud-blankflash-g8-power.4431193/ that is supposed to get the phone working again, but am unsure whether using it will cause loss of data.
I absolutely cannot lose any data from internal storage.
Any help appreciated. Thanks in advance.
Ok, now we're rolling...
First things first. Motorola sucks because they only give you restricted Firehose loaders.
That means of the 70-odd partitions that you have you can only read/write about 1/3 of them using EDL.
If you post your Firehose loader I can tell you which ones you can read/write.
Second, are you sure that the only damage you did was by writing recovery_a and recovery_b?
And you're on Linux, *sad face*.
I was disassembling the Motorola Firehose for my Moto G (2021) and I discovered that they have more reboot options than stock.
There's reset-to-edl and reset-to-fastboot.
I've added those options to my edl.exe (in the sig) this morning. You need to download the very latest.
What may have happened is that you wrote a bad recovery which may have set the boot option in the BCB or misc.
Since the recovery is good enough to be recognized as an image but not good enough to reset this boot option you're stuck.
Your first recourse is flashing a proper recovery.
I'm not sure whether "blank flash" tries to wipe everything. In any case I wouldn't risk it.
Your first try should be to fix the broken things, not everything.
Yes, any edl client that supports ad-hoc xml should be able to get you to fastboot but I'll only answer for my code.
I've tested it.
Code:
C:\>edl /lwhatever.bin
C:\>edl /zf
C:\>fastboot flash recovery_a good_recovery.img
C:\>fastboot flash recovery_b good_recovery.img
C:\>fastboot reboot
I admit to not properly understand what a firehose loader is. :x
Second, are you sure that the only damage you did was by writing recovery_a and recovery_b?
Click to expand...
Click to collapse
Yes, 100%.
So, for now, I should try booting Windows, installing the 9008 driver and following your instructions... Will let you know how it goes.
Thanks a lot.
marc.2377 said:
I admit to not properly understand what a firehose loader is. :x
Click to expand...
Click to collapse
A Firehose loader is a replacement xbl/sbl secondary loader that has special sauce added to it to make it interactive.
It is not to be confused with a Windows driver (which, in this case is Zadig, as per the instructions on my web page).
In this case, your Firehose loader is packed in singleimage.bin in the RPE here: https://mirrors.lolinet.com/firmware/motorola/sofiar/blankflash/
I extracted it for you. I renamed it sofiar.bin
The extension name does not matter.
Code:
C:\>edl /lsofiar.bin
That's slash-ell-sofiar.bin
Edit: And yes, your Firehose loader has the reset-to-fastboot.
Right, thanks for the explanation. I figured that was programmer.elf from my files.
Ok, I got as far as:
> edl /l
Found EDL 9008
Serial: 69cccc95
HWID: 0010a0e102e80000, QC: 0010a0e1, OEM: 02e8, Model: 0000
Hash: 974359c4290cac7f-9f0dc9a802815b5e-2b376b7a7c1be92c-1e816b5287f18610
> edl /lsofiar.bin
Found EDL 9008
Resetting Sahara
Serial: 69cccc95
HWID: 0010a0e102e80000, QC: 0010a0e1, OEM: 02e8, Model: 0000
Hash: 974359c4290cac7f-9f0dc9a802815b5e-2b376b7a7c1be92c-1e816b5287f18610
Sending sofiar.bin 100% Ok
Waiting for Firehose... Ok
> edl.exe /zf
Found EDL 9008
Requesting reset to fastboot... Ok
But it doesn't boot to fastboot.
It seems to me that your tool, edl could be used to write the recovery partition directly, no?
I tried this:
> edl /w /precovery_a recovery.img
Found EDL 9008
Configuring... Ok
Requesting GPT 0 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting write recovery.img...
<log value="ERROR: range restricted: lun=0, start_sector=1591552, num_sectors=131072" />
Nope
P.s. curiously, the file I downloaded from https://raw.githubusercontent.com/b...a/0010a0e102e80000_974359c4290cac7f_fhprg.bin wasn't accepted as a valid firehose loader file.
Edit: nevermind. Had to restart the phone.
I believe that's an older loader, anyway.
How shall I proceed?
marc.2377 said:
But it doesn't boot to fastboot.
Click to expand...
Click to collapse
Hmm, the screen stays black?
Is it still in EDL mode or some other mode?
Does Windows "bong" when you pull the USB cable?
It's possible that this goes to a fastboot without a screen?
Try holding various buttons, both by long power button reset and /zf
marc.2377 said:
It seems to me that your tool, edl could be used to write the recovery partition directly, no?
Click to expand...
Click to collapse
Yes, it could if Motorola wasn't such a pain with the "range restricted".
They've really clamped down (that other file you mentioned is the same):
Code:
qcomview /r sofiar.bin
Addr LUN Start Count
------ --- -------- --------
007f10 0 0 256
007f28 0 256 78336
007f40 0 1609948 512
007f58 0 1610496 512
007f70 1 1 1
You can do this to see which partitions this means:
Code:
C:\>edl /lsofiar.bin
C:\>edl /g
I have a feeling that the Motorola "Blankflash" stuff writes something to those 3 areas that allow it to write everything.
But it probably wipes the userdata.
I'm not an expert on their tools.
Tell me what the GPT says (you only need to quote stuff in the area of that table).
Edit: It looks like in the multi GB zip there are two "instruction" files, flashfile.xml and servicefile.xml
They are mostly the same except that flashfile will wipe userdata!
Curious. The partition table is as follows:
Code:
Found EDL 9008
Configuring... Ok
Requesting GPT 0 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
# Name Start Count Type
-- ---------------- ---------- ---------- --------------------
1 xbl_a 256 9216 Inactive
2 xbl_b 9472 9216 Bootloader
3 tz_a 18688 8192 Inactive
4 tz_b 26880 8192 TrustZone
5 rpm_a 35072 1024 Inactive
6 rpm_b 36096 1024 Resource/power mgmt
7 hyp_a 37120 1024 Inactive
8 hyp_b 38144 1024 Hypervisor
9 devcfg_a 39168 256 Inactive
10 devcfg_b 39424 256 Device config
11 xbl_config_a 39680 256 Inactive
12 xbl_config_b 39936 256 Boot config
13 abl_a 40192 2048 Inactive
14 abl_b 42240 2048 Android bootloader
15 uefisecapp_a 44288 4096 Inactive
16 uefisecapp_b 48384 4096 be8a7e08
17 qupfw_a 52480 160 Inactive
18 qupfw_b 52736 160 QUP firmware
19 cmnlib_a 52992 1024 Inactive
20 cmnlib64_a 54016 1024 Inactive
21 cmnlib_b 55040 1024 Common lib
22 cmnlib64_b 56064 1024 Common lib64
23 keymaster_a 57088 1024 Inactive
24 keymaster_b 58112 1024 Key master
25 storsec_a 59136 256 Inactive
26 storsec_b 59392 256 Store secure
27 spunvm 59648 16384 Spun VM
28 uefivarstore 76032 1024 165bd6bc
29 multiimgoem_a 77056 64 Inactive
30 multiimgoem_b 77120 64 e126a436
31 multiimgqti_a 77184 64 Inactive
32 multiimgqti_b 77248 64 846c6f05
33 prov_a 77312 512 Inactive
34 prov_b 77824 512 d05e0fc0
35 modem_a 78336 368640 Inactive
36 modem_b 446976 368640 FAT32
37 fsc 815616 256 FSC
38 ssd 815872 16 Secure SW download
39 dsp_a 816128 65536 Inactive
40 dsp_b 881664 65536 DSP
41 ddr 947200 2048 DDR
42 utags 949248 1024 1dd40d18
43 utagsBackup 950272 1024 c490f39c
44 modemst1 951296 8192 Modem ST1
45 modemst2 959488 8192 Modem ST2
46 fsg_a 967680 49152 Inactive
47 fsg_b 1016832 49152 Modem storage
48 persist 1065984 65536 Persist
49 prodpersist 1131520 16384 Persist
50 frp 1147904 1024 FRP
51 cid 1148928 256 459abd04
52 carrier 1149184 32768 c63d32d8
53 metadata 1181952 32768 988a98c9
54 kpan 1214720 16384 56465e10
55 boot_a 1231104 131072 Inactive
56 boot_b 1362176 131072 Boot
57 dtbo_a 1493248 49152 Inactive
58 dtbo_b 1542400 49152 DTBO
59 recovery_a 1591552 131072 Inactive
60 recovery_b 1722624 131072 Recovery
61 misc 1853696 2048 Misc
62 logfs 1855744 16384 Log FS
63 apdp 1872128 512 APDP
64 msadp 1872640 512 MSADP
65 dpo 1873152 2 DPO
66 devinfo 1873160 8 Device info
67 bluetooth_a 1873168 9216 Inactive
68 bluetooth_b 1882384 9216 Bluetooth
69 logo_a 1891600 66848 Inactive
70 logo_b 1958448 66848 Splash
71 vbmeta_a 2025296 128 Inactive
72 vbmeta_b 2025424 128 Verified Boot meta
73 padA 2025552 6064 Empty
74 hw 2031616 16384 b2d77ec0
75 padB 2048000 16384 Empty
76 sp 2064384 16384 40aef62a
77 padC 2080768 16384 Empty
78 padD 2097152 32768 Empty
79 super 2129920 16973824 System
80 userdata 19103744 103038943 User data
Doesn't seem to match the output of qcomview.
Also, the file 0010a0e102e80000_974359c4290cac7f_fhprg.bin lists the following codenames:
Code:
QCA6390
QCS605
SA8150
SDA670
SDA845
SDA855
SDA855A
SDA865
SDC830
SDM450
SDM670
SDM830
SDM845
SDM855
SDM855A
SDM1000
SDX24
SDX24M
SDX55
SM6150
SM6150P
SM7150
SM7150P
SM_NICOBAR
While programmer.elf (same as sofiar.bin that you uploaded) lists, additionally, QCM_NICOBAR and QCS_NICOBAR.
I wonder whether this is actually the correct file for me...
Btw, before attempting any further writing strategies, I confess to being interested in pulling userdata. As I understand the real decryption key is stored in the TEE functionality of the chipset and such an image would be unreadable for me, except if I were to restore it later.
With your tool I got the "range restricted" for edl /r /puserdata parts\userdata.img /t too.
Code:
Addr LUN Start Count
------ --- -------- --------
007f10 0 0 256 - GPT
007f28 0 256 78336 - xbl_a to prov_b
007f40 0 1609948 512 - ??? random spot in recovery_a
007f58 0 1610496 512 - ??? random spot in recovery_a
007f70 1 1 1
So, basically, you have free read/write access to partions 1 to 34
Reading is always safe.
Also, you're on the B slot.
So why does reboot to fastboot fail?
It could be that it was never implemented correctly in this Firehose
It could be that this Firehose is not for your device
It could be that xbl and/or abl was damaged somehow
I'd do some checking, xbl_b and abl_b to start with.
Read 'em then compare them to the xbl and abl you have in your big packages.
Code:
C:\>edl /lsofiar.bin
C:\>edl /r /t /pxbl_b xblb.img
C:\>edl /r /t /pabl_b ablb.img
The /t will copy these ELF files only as big as they need to be (not all the blank space).
OTOH, they will enlarge to an exact number of 512 byte sector.
So they could be 511 bytes bigger than what comes out of that package.
If things are wacky, try without /t, but they'll be padded with all the zeroes in the partition.
If those files aren't in the big package, here's ones I extracted from the blankflash.
Check 'em all.
Also, it's possible that somehow the slots got switched.
While you're at it, look at xbl_a and abl_a also.
Hey, thanks for the continued efforts to help me. Sorry for absence for the past days, real life caugh in ^^
I'm glad to report that, amidst some binary checking and all that, I managed to resuscitate my phone using the blankflash strategy, after carefully revising it.
Strangely, it seems that TWRP got installed in the boot partition, such as that "normal boot" kept entering TWRP, despite I having flashed the stock recovery images to both recovery slots. I'll detail this all later.
At this point my phone is on and I backed up what I needed, and have been using it. A few strange glitches are present, i.e. battery charging is acting weird. I plan on doing a clean flashing of the stock ROM soon. Maybe I should take the opportunity to study how to make a fully working port of the latest LineageOS for this device, too.
Will get back within a few days with a detailed report of the endeavour
marc.2377 said:
Will get back within a few days with a detailed report of the endeavour
Click to expand...
Click to collapse
I'm looking forward to hearing how you got EDL mode working.
I bricked XT2041-3 Sofiar (downgrade to A10) and am stuck trying the phone to succeed at qboot blank-flash, but it hangs (on linux):
Code:
< waiting for device >
Motorola qboot utility version 3.86
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 0.002] ...cpu.id = 266 (0x10a)
[ 0.002] ...cpu.sn = 3773339940 (0xe0e89924)
[ 0.002] Opening singleimage
[ 0.002] Loading package
[ 0.004] ...filename = pkg.xml
[ 0.005] Loading programmer
[ 0.005] ...filename = programmer.elf
[ 0.005] Sending programmer
[ 0.178] Handling things over to programmer
[ 0.178] Identifying CPU version
[ 0.178] Waiting for firehose to get ready
With --debug=2 there can be seen some parsing errors in xmls being passed for about 13 more seconds. On Windows VM phone is recognized as a single QDLoader 9008 device, but qboot fails after half a minute with IO Errors. Is this even EDL mode?
A tried without luck Renate's edl tool. edl.exe /lsingleimage.bin:
Code:
Found EDL 9008
Could not open device
I was growing increasingly desperate, so I opened the phone and played with EDL points according to
MatiasLopezxD. No combination of vol-, power, shorting points, plugging usb seem to make a difference. I must be missing something simple.
Any help would be appreciated.
@ybea: Quick answer for now - I got into EDL mode by holding down VolDown+Power for about 8-10 seconds. Let me know if it works for you. What's your output for lsusb?
Same as yours - ID 05c6:9008 (Qualcomm, Inc. Gobi Wireless Modem (QDL mode)). It reconnects after pressing power for 9 seconds (with or without vol-), nothing new.
Try restarting it into EDL mode while it's plugged. I found that to be necessary sometimes.
Edit: Btw, I don't remember why exactly, but I only had success running the blankflash from Windows. Linux didn't do the magic, nor a Windows VM with USB redirection...
marc.2377 said:
Edit: Btw, I don't remember why exactly, but I only had success running the blankflash from Windows. Linux didn't do the magic, nor a Windows VM with USB redirection...
Click to expand...
Click to collapse
That was it! I didn't event try it on the metal, because Motorola driver installer and uninstaller crash for me for some reason. Should be straightforward from now.
Thank you so much. You saved the day.
ybea said:
A tried without luck Renate's edl tool. edl.exe /lsingleimage.bin
Click to expand...
Click to collapse
Sorry. edl.exe uses the generic Zadig (i.e. WinUsb) driver).
If you have the Qualcomm driver loaded it's stealing the poor WinUsb interface and forcing it into some bogus virtual com port.
Also, singleimage is Motorola's completely morally bankrupt idea of packing stuff in a file.
It is not a Firehose loader, although it contains one.
Add to all your miseries, Motorola is crap and releases only restricted Firehose loaders.
If you're still stuck, ship me the "single-and-totally-bogus.bin" and I'll extract the Firehose loader for you.
Better poke me or I won't see it.
No longer stuck. The problem for me was neither VM USB passthrough nor blankflash tools for linux did work, although both showed proper EDL mode. It seems it only works on native Windows. Thanks for your interest.