Hi I have a serious problem,
So the other day my lg l9 (P760) die completel. Ii try almost everything but my phone continue to had black screen, won't enter in s/w mode and won't hard reset.
Flash boot have this log at the end:
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.201s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.208s
sending 'u-boot' (1024 KB)...
OKAY [ 0.528s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.535s
Done
When i put it in usb the device connect and disconect continuosly. Only if i try to boot fastboot with vol+ pressed i can see the devices but the screen still black and after a couple of minute it disconnect. So i can't use the lg mobile tool. I try KDZ off-line and on-line procedure but the sw crah or do not recognize the phone.
Can someone help me please?
Flash with fastboot u-boot and x-loader there are some tutorials for fastboot for our device.
LG L9-P760 /TapatalkVIP 4.7.3 /4.4.4KK AxxionKat 1.4.0 by @Xerdox
Cytrus224 said:
Flash with fastboot u-boot and x-loader there are some tutorials for fastboot for our device.
LG L9-P760 /TapatalkVIP 4.7.3 /4.4.4KK AxxionKat 1.4.0 by @Xerdox
Click to expand...
Click to collapse
Thank you for your answer Cytrus224, but i try to flash with fastbot using this guide (http://forum.xda-developers.com/showthread.php?t=2411265) but flashbot log still the same as the post below.
Can you suggest me something or a better guide?
Thank you
Had same problem yesterday, after changing philz touch to new artas182x twrp by Flashify flashing. Phone stock on LG logo, s/w not working. I used this method found on polish forum
http://forum.android.com.pl/f764/re-lock-bootloader-l9-328381
1. Download omap4boot
2. Download ics u-boot and x-loader.
3. Install fastboot drivers(all tutorials linked in post #1 in upper link)
4. Flash u-boot and x-loader.
5. Now you can turn again phone into s/w and flash stock roms
Sorry for my bad English
LG L9-P760 /TapatalkVIP 4.7.3 /4.4.4KK AxxionKat 1.4.0 by @Xerdox
Cytrus224 said:
Had same problem yesterday, after changing philz touch to new artas182x twrp by Flashify flashing. Phone stock on LG logo, s/w not working. I used this method found on polish forum
1. Download omap4boot
2. Download ics u-boot and x-loader.
3. Install fastboot drivers(all tutorials linked in post #1 in upper link)
4. Flash u-boot and x-loader.
5. Now you can turn again phone into s/w and flash stock roms
Sorry for my bad English
LG L9-P760 /TapatalkVIP 4.7.3 /4.4.4KK AxxionKat 1.4.0 by @Xerdox
Click to expand...
Click to collapse
Doesn't work.. this is the result:
C:\omap4boot-for_optimus-v1.21>fastboot flash x-loader p1.bin
sending 'x-loader' (384 KB)...
OKAY [ 0.200s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.208s
C:\omap4boot-for_optimus-v1.21>fastboot flash u-boot p2.bin
sending 'u-boot' (1024 KB)...
OKAY [ 0.528s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.535s
Related
Hi all.
Last night, for an unknown reason (no flash, etc), my phone refused to boot. With a powered USB-Hub, I can access to fastboot, or SW Upgrade Mode (Phone screen keeps off in both, but is showed in Windows). I've setup OMAP4430 drivers (from Optimus 3D) and fastboot using OMAP4Boot. As I can read from Optimus 3D, my bootloader is corrupted.
I think I can revover my phone using fastboot, no ? SW Upgrade mode doesn't work ("Your phone doesn't support upgrade"), but maybe fastboot will working... ? How and where I can flash a new bootloader ?
Thx for help...
EDIT : I've tried a reflash of CWM, and this is what fastboot responds :
sending 'recovery' (5898 KB)...
OKAY [ 3.022s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.028s
Anyway to recover that ?
EDIT 2 :
A try with "fastboot boot cwmtouch.img" doesn't boot recovery... I need help ! Please !!
I've also tried with CyanogenMod boot.img (extracted from the RC5 zip), but no more success... Is my phone dead ? If I send it to LG, will them see the unlocked bootloader and other things ? If yes, they will refuse to repair my device ?
RL77LUC said:
Hi all.
Last night, for an unknown reason (no flash, etc), my phone refused to boot. With a powered USB-Hub, I can access to fastboot, or SW Upgrade Mode (Phone screen keeps off in both, but is showed in Windows). I've setup OMAP4430 drivers (from Optimus 3D) and fastboot using OMAP4Boot. As I can read from Optimus 3D, my bootloader is corrupted.
I think I can revover my phone using fastboot, no ? SW Upgrade mode doesn't work ("Your phone doesn't support upgrade"), but maybe fastboot will working... ? How and where I can flash a new bootloader ?
Thx for help...
EDIT : I've tried a reflash of CWM, and this is what fastboot responds :
sending 'recovery' (5898 KB)...
OKAY [ 3.022s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.028s
Anyway to recover that ?
EDIT 2 :
A try with "fastboot boot cwmtouch.img" doesn't boot recovery... I need help ! Please !!
I've also tried with CyanogenMod boot.img (extracted from the RC5 zip), but no more success... Is my phone dead ? If I send it to LG, will them see the unlocked bootloader and other things ? If yes, they will refuse to repair my device ?
Click to expand...
Click to collapse
Probably the nand is crapping out. Try refreshing xloader and uboot http://forum.xda-developers.com/showthread.php?p=41768774 or possibly see Kuma82s last post in the same thread.
LG will be able see that you've unlocked the bootloader but who knows if they check it.
Lelus said:
Probably the nand is crapping out. Try refreshing xloader and uboot http://forum.xda-developers.com/showthread.php?p=41768774 or possibly see Kumar82s last post in the same thread.
LG will be able see that you've unlocked the bootloader but who knows if they check it.
Click to expand...
Click to collapse
Thanks a lot for your help. I've tried, but I get that :
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: 81eb9bc20de7a195ecaf96582c4197f74c1763
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74
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.200s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.206s
sending 'u-boot' (1024 KB)...
OKAY [ 0.528s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.534s
Done
Click to expand...
Click to collapse
And, I've tried a "fastboot oem format", no more success :
...
FAILED (remote failure)
finished. total time: 0.001s
Click to expand...
Click to collapse
I think my phone's memory is dead, no ? But it's weird, I've purchased it two months ago...
RL77LUC said:
Thanks a lot for your help. I've tried, but I get that :
And, I've tried a "fastboot oem format", no more success :
I've think my phone's memory is dead, no ? But it's weird, I've purchased it two months ago...
Click to expand...
Click to collapse
Yes I think it is,
don't mention anything about the bootloader when you send it to LG
Lelus said:
Yes I think it is,
don't mention anything about the bootloader when you send it to LG
Click to expand...
Click to collapse
Thanks for your help, very appreciated. I will don't send it directly to LG but to my carrier (He do the work, according of documents), and they will send to LG.
Anyone have a last chance idea ?
Kumar lol =)
Once they see it's really a hardware failure, they shouldn't look any further (hopefully)
Good luck
Sent from my LG-P769 using xda app-developers app
kuma82 said:
Kumar lol =)
Once they see it's really a hardware failure, they shouldn't look any further (hopefully)
Good luck
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
I hope... Thx.
EDIT : I've gived it to my carrier. They will send my phone to LG. They will give me back in about 3 weeks...
Hi, well a friend of a friend gifted me an LG L9 Model P778G (Carrier: Personal Telecom Country: Argentina). The only thing that he told me was that he dropped his phone and it didn´t turn on back anymore. I externally charged the battery. The phone doesn´t turn on, sometimes when I connect it to my PC (windows XP) it recognizes it as OMAP4430 but only when battery is not connected (when I connect battery it says unrecognized usb device, when I press Vol+ and Vol- with or without battery it also says unrecognized device. Already tried to flash with LG Mobile Support and KDZ but it says phone not connected. I would like to know how can i get the phone back working and if possible with Jelly Bean (I don´t know if phone had JB or ICS, but of what I almost certain is that it was never modified because it belonged to an old person). Please explain with detail though I'm not used to LG (HTC & Samsung owner) and don't know much of it.Thanks to everyone!
USB connection is unstable, it comes nad goes
philohtc said:
USB connection is unstable, it comes nad goes
Click to expand...
Click to collapse
Hi philohtc, you could read and try thishttp://forum.xda-developers.com/showthread.php?t=2677611
Cheers. Good luck.
BajoPrimate said:
Hi philohtc, you could read and try thishttp://forum.xda-developers.com/showthread.php?t=2677611
Cheers. Good luck.
Click to expand...
Click to collapse
Hi, my device doesn´t turn on at all, the only signal i have is the OMAP driver coming and going and sometimes staying a little while, the LG Mobile Support Tool doesn't see the cellphone, hope you can help me, thanks!
philohtc said:
Hi, well a friend of a friend gifted me an LG L9 Model P778G (Carrier: Personal Telecom Country: Argentina). The only thing that he told me was that he dropped his phone and it didn´t turn on back anymore. I externally charged the battery. The phone doesn´t turn on, sometimes when I connect it to my PC (windows XP) it recognizes it as OMAP4430 but only when battery is not connected (when I connect battery it says unrecognized usb device, when I press Vol+ and Vol- with or without battery it also says unrecognized device. Already tried to flash with LG Mobile Support and KDZ but it says phone not connected. I would like to know how can i get the phone back working and if possible with Jelly Bean (I don´t know if phone had JB or ICS, but of what I almost certain is that it was never modified because it belonged to an old person). Please explain with detail though I'm not used to LG (HTC & Samsung owner) and don't know much of it.Thanks to everyone!
Click to expand...
Click to collapse
I believe you still need to install the fastboot driver again.
Take a look at lelus fastboot script thread here - http://forum.xda-developers.com/showthread.php?p=41768774
Read the part in the thread about installing the drivers and about the original fastboot thread.
That should get you ready to be able to do the offline or online kdz flash
xdrc45 said:
I believe you still need to install the fastboot driver again.
Take a look at lelus fastboot script thread here - http://forum.xda-developers.com/showthread.php?p=41768774
Read the part in the thread about installing the drivers and about the original fastboot thread.
That should get you ready to be able to do the offline or online kdz flash
Click to expand...
Click to collapse
Hi, now the phones stays for a while, but still can't get it recognized at KDZ or LG MST.
PS: when installing fastboot drivers after connecting battery it says an LG Logo should appear on screen but it doesn't, thanks for your support
philohtc said:
Hi, now the phones stays for a while, but still can't get it recognized at KDZ or LG MST.
PS: when installing fastboot drivers after connecting battery it says an LG Logo should appear on screen but it doesn't, thanks for your support
Click to expand...
Click to collapse
Use the fastboot script and flash the ICS Uboot and Xloaders
xdrc45 said:
Use the fastboot script and flash the Uboot and Xloaders
Click to expand...
Click to collapse
Sorry to bother, could you give me links to those files for this model? It's my first LG
philohtc said:
Sorry to bother, could you give me links to those files for this model? It's my first LG
Click to expand...
Click to collapse
It's in the lelus fastboot script, option #4
http://forum.xda-developers.com/showthread.php?p=41768774
xdrc45 said:
It's in the lelus fastboot script, option #4
http://forum.xda-developers.com/showthread.php?p=41768774
Click to expand...
Click to collapse
I selected option 6 because option 4 gaved error
This is my log
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
[* said:
read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x4
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 2f8a54c5c2fdd39e7dbe73b14991c29b1b9d0ec8
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.203s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.219s
sending 'u-boot' (1024 KB)...
OKAY [ 0.531s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.547s
Done
Click to expand...
Click to collapse
philohtc said:
I selected option 6 because option 4 gaved error
This is my log
Click to expand...
Click to collapse
OK so you flashed the JB Uboot and Xloader? I'm not at my PC to see the screen options. Try running the kdz now.
xdrc45 said:
OK so you flashed the JB Uboot and Xloader? I'm not at my PC to see the screen options. Try running the kdz now.
Click to expand...
Click to collapse
This happened when I flashed the JB Uboot and Xloader
< waiting for device >
sending 'x-loader' (384 KB)...
OKAY [ 0.203s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.219s
sending 'u-boot' (1024 KB)...
OKAY [ 0.531s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.547s
Done
-----------------------------------------------------------------
I ran KDZ and got the following as usual:
[R&D Test Tools Log File]
21:58:55 : Launching SW update
21:58:55 : Unpacking KDZ
21:59:12 : KDZ file extraced
21:59:30 : Files were extracted.
21:59:30 : LGMobileDL Load.
21:59:30 : Port = -1
21:59:30 : Connecting to phone
21:59:30 : PHONE WAS NOT FOUND!
21:59:32 : ===FINISHED===
philohtc said:
This happened when I flashed the JB Uboot and Xloader
< waiting for device >
sending 'x-loader' (384 KB)...
OKAY [ 0.203s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.219s
sending 'u-boot' (1024 KB)...
OKAY [ 0.531s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.547s
Done
-----------------------------------------------------------------
I ran KDZ and got the following as usual:
[R&D Test Tools Log File]
21:58:55 : Launching SW update
21:58:55 : Unpacking KDZ
21:59:12 : KDZ file extraced
21:59:30 : Files were extracted.
21:59:30 : LGMobileDL Load.
21:59:30 : Port = -1
21:59:30 : Connecting to phone
21:59:30 : PHONE WAS NOT FOUND!
21:59:32 : ===FINISHED===
Click to expand...
Click to collapse
Run the lesus fastbot script again and select option 1 and make sure the drivers are installed. Then try running option #4 again... If successful then try the offline flash here - http://forum.xda-developers.com/showthread.php?t=2085344
And check out this thread - http://forum.xda-developers.com/showthread.php?p=48834061
xdrc45 said:
Run the lesus fastbot script again and select option 1 and make sure the drivers are installed. Then try running option #4 again... If successful then try the offline flash here - http://forum.xda-developers.com/showthread.php?t=2085344
And check out this thread - http://forum.xda-developers.com/showthread.php?p=48834061
Click to expand...
Click to collapse
It says
waiting for 2ndstage response...
usb_read 4
usb_read got: 0, expected: 4, errno: 31
usb_read got GEN_FAILURE - got: 0, expected: 4, errno: 31
usb_read failed: 31
usb read = 0
unexpected 2ndstage response
< waiting for device >
AND STAYS THERE ??
philohtc said:
It says
waiting for 2ndstage response...
usb_read 4
usb_read got: 0, expected: 4, errno: 31
usb_read got GEN_FAILURE - got: 0, expected: 4, errno: 31
usb_read failed: 31
usb read = 0
unexpected 2ndstage response
< waiting for device >
AND STAYS THERE ??
Click to expand...
Click to collapse
Ok have you tried put the device into S/W mode now and see if it's detected? Power off the device, press and hold the volume (+) up button and connect the USB cable from the PC to the device.
xdrc45 said:
Ok have you tried put the device into S/W mode now and see if it's detected? Power off the device, press and hold the volume (+) up button and connect the USB cable from the PC to the device.
Click to expand...
Click to collapse
I could complete step 4 it sended uboot and xloader but it gaved error when it tried to write them, I dont know when it is in S/W mode though Screen is always black. In the offline method I deactivate the wifi card and get the connection in line error but it doesn't appear the pop-up of the language.
philohtc said:
I could complete step 4 it sended uboot and xloader but it gaved error when it tried to write them, I dont know when it is in S/W mode though Screen is always black. In the offline method I deactivate the wifi card and get the connection in line error but it doesn't appear the pop-up of the language.
Click to expand...
Click to collapse
You can try to run the B2CAppSetup.exe, after opening the app, select you phone model and letting it install the drivers, then unplug and plug the USB cable back in and see what happens.
Edit - Also when you connect the device to your PC when in fastboot mode what does it show up as in the PC's device manager?
xdrc45 said:
You can try to run the B2CAppSetup.exe, after opening the app, select you phone model and letting it install the drivers, then unplug and plug the USB cable back in and see what happens.
Edit - Also when you connect the device to your PC when in fastboot mode what does it show up as in the PC's device manager?
Click to expand...
Click to collapse
Under Android Phone > OMAP4430FastBoot USB Device. Can't see where to select model, apparently is automatic recognition
xdrc45 said:
You can try to run the B2CAppSetup.exe, after opening the app, select you phone model and letting it install the drivers, then unplug and plug the USB cable back in and see what happens.
Edit - Also when you connect the device to your PC when in fastboot mode what does it show up as in the PC's device manager?
Click to expand...
Click to collapse
any idea?
philohtc said:
any idea?
Click to expand...
Click to collapse
I'm not sure yet... We need to get the ICS Uboot and Xloaders to install so that you can get into S/W mode.
I'm trying to research on an answer for you.
These L9 are a real pain in the butt.
---------- Post added 30th March 2014 at 12:06 AM ---------- Previous post was 29th March 2014 at 11:47 PM ----------
philohtc said:
any idea?
Click to expand...
Click to collapse
Run the lelus fasrboot again and flash the JB Uboot and Xloader and show mW the log again
I used the files from dell opensource and did the bootloader unlock and flashed a rooted boot image and now my tablet wont load to the os. it juszt goes to a black screen that say [email protected]:/ in upper left hand corner? I dont know what to do now. help!
It appears that you are trying to root the device. Please review [GUIDE] How to root Android 4.4.4 on the Dell Venue 3840
(Merrifield) Tablet
You may post there if you need additional information.
I did
Perseus said:
It appears that you are trying to root the device. Please review [GUIDE] How to root Android 4.4.4 on the Dell Venue 3840
(Merrifield) Tablet
You may post there if you need additional information.
Click to expand...
Click to collapse
I did go there and used those instructions. and the file that was provided. thats when it all happened. I have since flashed the boot.img from opensource back onto it and it works again. and used kingo root program. so it is showing rooted. but now I see that I am no longer running kitkat 4.4.4 but kitkat 4.4.2. I want to upgrade back but I am having the hardest time finding roms for my tablet. and I notice that so much of the main stuff like google play services take way too much ram, leaving me with barely 200 mb ram left to work with. and its a 1 gb. hmmm and I wanted to change my recovery to clockworkmod but it says my device isnt supported yet. I really am coming against roadblocks to optimizing the tablet. I cant even run my fb games cuz they wont sign into fb. they just keep restarting. grrrr any thoughts or ideas? thanks. also I could never get xfstk to work.
xFSTK downloader
I am trying to follow the tutorial but the xFSTK downloader is not working. It says "Details: No provisioning activities in progress..."
Anyone know what could be causing this issue?
Thanks in advance,
tomasro27 said:
I am trying to follow the tutorial but the xFSTK downloader is not working. It says "Details: No provisioning activities in progress..."
Anyone know what could be causing this issue?
Thanks in advance,
Click to expand...
Click to collapse
Post a screenshot of your computer showing this message.
turn off device
plug in
hit begin button
press volume up and power
takes like 3-5 seconds and goes as told to?
Perseus said:
I will request to have this thread moved to appropriate forum so other experts for that device may be of help.
Click to expand...
Click to collapse
Hi Perseus,
I am wondering if you know where this thread has been moved thus I could check for more updates. I have the same issue after following this - http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
Presently my tablet goes black and I can see only "[email protected]:/" on top left.
Thanks!
3480
You can always flash back the original rom 4.4.4
https://www.androidfilehost.com/?fid=95784891001602440
did you manage to get your tab rooted with kingo on 4.4.2.
hamzilla said:
Hi Perseus,
I am wondering if you know where this thread has been moved thus I could check for more updates. I have the same issue after following this - http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
Presently my tablet goes black and I can see only "[email protected]:/" on top left.
Thanks!
Click to expand...
Click to collapse
---------- Post added at 11:39 AM ---------- Previous post was at 11:11 AM ----------
You have to select those 4 files downloaded from here (opensource.dell.com/releases/Venue_8_3840_Merrifield/developer-edition/A195/OTA/)
FW DnX= dnx_fwr_*.bin
IFWI= ifwi_*.bin
OS DnX= dnx_osr_*.bin
OS Image= droidboot.img.POS.bin
then put your tablet into fast boot mode
1. Enable fastboot mode
1) Open “xFSTK Downloader 1.5.1”.
2) Select the second “MRD AO/BO + MOOR AO + CRC” tab as the following................................
tomasro27 said:
I am trying to follow the tutorial but the xFSTK downloader is not working. It says "Details: No provisioning activities in progress..."
Anyone know what could be causing this issue?
Thanks in advance,
Click to expand...
Click to collapse
HELP
after writing system in fastboot mode this gets me error
C:\Users\home\Desktop\Venue 8 1.22>fastboot oem start_partitioning
...
(bootloader) Start partitioning
OKAY [ 1.016s]
finished. total time: 1.016s
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash /tmp/partition.tbl partition.t
bl
sending '/tmp/partition.tbl' (1 KB)
fname=partition.tbl...
1 KB / 1 KB
OKAY [ 0.766s]
writing '/tmp/partition.tbl'...
OKAY [ 1.031s]
finished. total time: 1.797s
C:\Users\home\Desktop\Venue 8 1.22>fastboot oem partition /tmp/partition.tbl
...
OKAY [ 1.156s]
finished. total time: 1.156s
C:\Users\home\Desktop\Venue 8 1.22>fastboot erase system
erasing 'system'...
OKAY [ 55.253s]
finished. total time: 55.253s
C:\Users\home\Desktop\Venue 8 1.22>fastboot erase cache
erasing 'cache'...
OKAY [ 9.079s]
finished. total time: 9.079s
C:\Users\home\Desktop\Venue 8 1.22>fastboot erase data
erasing 'data'...
OKAY [ 26.158s]
finished. total time: 26.158s
C:\Users\home\Desktop\Venue 8 1.22>fastboot erase logs
erasing 'logs'...
OKAY [ 11.329s]
finished. total time: 11.344s
C:\Users\home\Desktop\Venue 8 1.22>fastboot oem stop_partitioning
...
(bootloader) Stop partitioning
OKAY [ 0.984s]
finished. total time: 0.984s
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash boot boot.img
sending 'boot' (8342 KB)
fname=boot.img...
8342 KB / 8342 KB
OKAY [ 1.235s]
writing 'boot'...
OKAY [ 1.422s]
finished. total time: 2.657s
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash fastboot droidboot.img
sending 'fastboot' (11114 KB)
fname=droidboot.img...
11114 KB / 11114 KB
OKAY [ 1.375s]
writing 'fastboot'...
OKAY [ 1.594s]
finished. total time: 2.985s
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash recovery recovery.img
sending 'recovery' (10202 KB)
fname=recovery.img...
10202 KB / 10202 KB
OKAY [ 1.313s]
writing 'recovery'...
OKAY [ 1.531s]
finished. total time: 2.860s
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash system system.img
sending 'system' (728453 KB)
fname=system.img...
102400 KB / 728453 KB
204800 KB / 728453 KB
307200 KB / 728453 KB
409600 KB / 728453 KB
512000 KB / 728453 KB
614400 KB / 728453 KB
716800 KB / 728453 KB
728453 KB / 728453 KB
OKAY [ 50.565s]
writing 'system'...
OKAY [ 45.752s]
finished. total time: 96.317s
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash splashscreen_7 oemlogo_7.bin
error: cannot get size of 'oemlogo_7.bin'
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash splashscreen_8 oemlogo_8.bin
error: cannot get size of 'oemlogo_8.bin'
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash dnx dnx_fwr_0003_20CA_YT2_TB2_
signed.bin
error: cannot get size of 'dnx_fwr_0003_20CA_YT2_TB2_signed.bin'
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash dnx dnx_osr_0003_20CA_YT2_TB2_
signed.bin
error: cannot get size of 'dnx_osr_0003_20CA_YT2_TB2_signed.bin'
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash ifwi for_product_ifwi_0003_20C
A_YT2_TB2_signed.bin
error: cannot get size of 'for_product_ifwi_0003_20CA_YT2_TB2_signed.bin'
C:\Users\home\Desktop\Venue 8 1.22>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Renz Kell said:
HELP
after writing system in fastboot mode this gets me error
Click to expand...
Click to collapse
It's been a while since I had those tablets I had three of them I remember having a similar problem I tried lots of times to reflash so I started over I redownload the tablets images again and the Odin and I dont know which one was at fault but that did the trick also made sure I was using 7zip on my PC rar or zip won't work 7zip I seem to recall having a big issue there as the images I downloaded were zipped up and I had to convert to 7zips to work anyways I hope that helps a little good luck
Hello everyone! I have the phone in hard bricked, I read on the forums that you can solve, not my model (xt1524) but other models. I tried some procedures but has not been able to solve anything. Can someone tell me how to call the files I have to try. I tried with Motoflasher but still not valid for my model. So I would try to look for files that I need but do not know their names. Thank you! I read somewhere that would serve certain files that are called programmer.mbm and singleimage.bin. Can someone tell me exactly what they're called to my phone.? Thank you!
Maybe is usefull :
- http://forum.xda-developers.com/moto-e-2015/general/stock-firmware-images-t3049047
- http://techtrickz.com/how-to/reinstall-stock-firmware-on-2nd-generation-moto-e-2015/
thanks, but the firmware is I, I can not install it because not light! I can only access it via the "Qualcomm HS-USB QDLoader 9008". Reading the various forums say that you need the program Motoflasher and certain files to switch it on and enter Fastboot. The problem is that I do not know which files I need.
anyone knows why I get this error?
**** QBOOT SELECTION STARTED: ****
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT: opening device: \\.\COM9
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: OKAY [ 0.001s]
OUTPUT: identifying device
OUTPUT: ...serial = 0x63000FE
OUTPUT: ...chip-id = 0x705
OUTPUT: ...chip-rev = 0x0
OUTPUT: ...sv-sbl = 0x0
OUTPUT: OKAY [ 0.002s]
OUTPUT: finding files
OUTPUT: ...programmer = programmer.mbn
OUTPUT: ...singleimage = singleimage.bin
OUTPUT: OKAY [ 0.001s]
OUTPUT: validating files
OUTPUT: OKAY [ 0.002s]
OUTPUT: switching to download mode
OUTPUT: OKAY [ -0.000s]
OUTPUT: greeting device for image downloading
OUTPUT:
OUTPUT: OKAY [ -0.000s]
OUTPUT: sending programmer
OUTPUT: Unexpected packet: 4. Was expecting: 3
OUTPUT: FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)
OUTPUT:
hemikranion said:
anyone knows why I get this error?
**** QBOOT SELECTION STARTED: ****
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT: opening device: \\.\COM9
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: OKAY [ 0.001s]
OUTPUT: identifying device
OUTPUT: ...serial = 0x63000FE
OUTPUT: ...chip-id = 0x705
OUTPUT: ...chip-rev = 0x0
OUTPUT: ...sv-sbl = 0x0
OUTPUT: OKAY [ 0.002s]
OUTPUT: finding files
OUTPUT: ...programmer = programmer.mbn
OUTPUT: ...singleimage = singleimage.bin
OUTPUT: OKAY [ 0.001s]
OUTPUT: validating files
OUTPUT: OKAY [ 0.002s]
OUTPUT: switching to download mode
OUTPUT: OKAY [ -0.000s]
OUTPUT: greeting device for image downloading
OUTPUT:
OUTPUT: OKAY [ -0.000s]
OUTPUT: sending programmer
OUTPUT: Unexpected packet: 4. Was expecting: 3
OUTPUT: FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)
OUTPUT:
Click to expand...
Click to collapse
Navigate in your bootloader to factory mode and then press the power button around 20-40 times before it boots up...Then unlock the bootloader and flash the Stock ROM for your model
the device does not start at all, there just led blinking on moto g4 plus
bsuthar said:
the device does not start at all, there just led blinking on moto g4 plus
Click to expand...
Click to collapse
Just flash your device with stock rom using sp flash tools .your device will start.
What he said ^^ Download the latest Stock ROM for your device, and issue the commands mentioned in @fratellos link one after another most likely you should get it back up.
skkethwas said:
Just flash your device with stock rom using sp flash tools .your device will start.
Click to expand...
Click to collapse
plss help me....
i have moto e4 and i don't know which file flashed first preloader.bin or pgpt.bin
first of all i flash preloader.bin and other factory images when i am going to flash pgpt.bin command ended up with error like this "PGPT: partition table not found" . after this wiped userdata and relock the bootloader. on fastboot reboot device cannot boot into system, no bootlogo, no fastboot, no recovery but recognized by PC and Miracle tool also charging led blink.
is this a softbrick or hardbrick.
Moto E4 won't power on. only white light led comes up when connecting with pc or charger. device recognized by pc.
kartik verma said:
plss help me....
i have moto e4 and i don't know which file flashed first preloader.bin or pgpt.bin
first of all i flash preloader.bin and other factory images when i am going to flash pgpt.bin command ended up with error like this "PGPT: partition table not found" . after this wiped userdata and relock the bootloader. on fastboot reboot device cannot boot into system, no bootlogo, no fastboot, no recovery but recognized by PC and Miracle tool also charging led blink.
is this a softbrick or hardbrick.
Moto E4 won't power on. only white light led comes up when connecting with pc or charger. device recognized by pc.
Click to expand...
Click to collapse
I think this can help you
https://forum.xda-developers.com/moto-e4/how-to/moto-e4-guide-stock-firmware-restore-t3661684
Hi everyone,
I am having a problem to my moto G xt1032 which i recently updated through OTA. afetr I installed it dies. never turning on. but the led light will blink after i charge a few minutes. but never turn on.
Do anyone have an idea?
please help me.
I would really appreciate and commend.
thank you.
Firstly I flashed it with a xt1033 firmware 4.4.4 which has a dual sim flatform due to I cannot flash it with its own xt1032 firmware. maybe its a corrupt file.
After done flashing with xt1033, the phone work perfectly. it only happens after i recieved the system update from android system update
It is recognized by your PC ?
Sent from my SM-T116 using XDA Free mobile app
Soufiansky said:
It is recognized by your PC ?
Sent from my SM-T116 using XDA Free mobile app
Click to expand...
Click to collapse
Qualcomm HS-USB QDLoader 9008
on device manager
skripton78 said:
Qualcomm HS-USB QDLoader 9008
on device manager
Click to expand...
Click to collapse
Can you try to flash again the stock firmware ?
no display at all. i had try 2 and 15 minute method, even i tried removing and draining the electrons lift on the board no effects.
i cant put to recovery and fastboot mode. but the phone was detected as Qualcomm HS-USB QDLoader 9008. but commands is only waiting for device.
in short, dead.
skripton78 said:
Qualcomm HS-USB QDLoader 9008
on device manager
Click to expand...
Click to collapse
its bricked. you need blank flash files to flash the bootloader again, here try this http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
blank-flash
nk-flash
opening device: \\.\COM11
OKAY [ -0.000s]
greeting device for command mode
OKAY [ -0.000s]
identifying device
...serial = 0x485D868
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ -0.000s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ -0.000s]
validating files
OKAY [ 0.080s]
switching to download mode
OKAY [ 0.010s]
greeting device for image downloading
OKAY [ 0.000s]
sending programmer
OKAY [ 0.010s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error reading packet)
C:\Users\khyrt klyetz\Downloads\Compressed\blankflash\blankflash>pause
Press any key to continue . . .
skripton78 said:
nk-flash
opening device: \\.\COM11
OKAY [ -0.000s]
greeting device for command mode
OKAY [ -0.000s]
identifying device
...serial = 0x485D868
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ -0.000s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ -0.000s]
validating files
OKAY [ 0.080s]
switching to download mode
OKAY [ 0.010s]
greeting device for image downloading
OKAY [ 0.000s]
sending programmer
OKAY [ 0.010s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error reading packet)
C:\Users\khyrt klyetz\Downloads\Compressed\blankflash\blankflash>pause
Press any key to continue . . .
Click to expand...
Click to collapse
FYI : this is already unlocked : status code 3 last time i'd flashed the firmware.
skripton78 said:
FYI : this is already unlocked : status code 3 last time i'd flashed the firmware.
Click to expand...
Click to collapse
do anyone have? here.