[Q] Is this a hardware problem? - LG Optimus L9 P760, P765, P768, P769

After screwing up when flashing the wrong u-boot and xloader in fastboot, my phone won't connect in debug mode and the notification bar crashes on 15% battery. I've tried everything imaginable to fix this, factory reset, flashing almost every kdz, updating through ota, completely removing everything through fastboot and reflashing a stock kdz. Please help, i've had this problem for 3 months and nobody else has this. I just need an estimate, does it sound like a hardware problem or a software problem?

Try flashing my persist image with fastboot and see if it fixed adb.
https://mega.co.nz/#!8pt0xCqA!3-uV70G_ItL46LwE8mYCQ7FUYMEXGYNU0KDUqQRVVbo
Messing with the persist image will mess up adb
Sent from my LGMS769 using XDA Premium 4 mobile app

kuma82 said:
Try flashing my persist image with fastboot and see if it fixed adb.
https://mega.co.nz/#!8pt0xCqA!3-uV70G_ItL46LwE8mYCQ7FUYMEXGYNU0KDUqQRVVbo
Messing with the persist image will mess up adb
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OMG, Kuma you are god sent. Thank you so much, I almost cried just seeing that device in adb. My phone is scanning the sd but if the camera and battery percentage works, everything will be fixed. No doubt thanked your post. Haha, again thanks soo much!!

If anyone else has this same problem this is what I did:
1.Downloaded kuma's persist.img
2.Moved the persist.img to the fastboot yours folder
3.Opened fastboot selected option 1, then used the command (fastboot flash persist persist.img)
4.reboot

Thank you both. This fixed my issue with ADB not showing up. Yay I have ADB back!
Sent from my LGMS769 using Tapatalk

can you reupload please mega link isn't working. thank you very much

tatsuyin said:
can you reupload please mega link isn't working. thank you very much
Click to expand...
Click to collapse
Hi tatsuyin, mega link has worked fine for me just now.
Cheers . Good luck.
Sent from my LG P76020L-EUR-XX unlocked and rooted

tatsuyin said:
can you reupload please mega link isn't working. thank you very much
Click to expand...
Click to collapse
If you're trying to download the mega file from your phone, once the web page loads press the menu button and select/check "request desktop site" and you should be able to download it.

OMG !! I cant belived.
Thank you !!!!

Almost . . . . . . . .
AlbinoCookie said:
If anyone else has this same problem this is what I did:
1.Downloaded kuma's persist.img
2.Moved the persist.img to the fastboot yours folder
3.Opened fastboot selected option 1, then used the command (fastboot flash persist persist.img)
4.reboot
Click to expand...
Click to collapse
So i thought it wad gonna work. Then at the end....it says this.....
writing 'recovery'...
C:\Users\Weldon Evridge\Android-Mobile-Phone-Tools\droid manager\Android_AIO_Flasher_1.00_by_Fonehacker\Android_AIO_Flasher\tools>
FAILED (remote: partition does not exist)
finished. total time: 2.275s

Hi, I think I might have a similar problem. I was running on stock JB for a while and then decided to give a try to CM10 or 11. I tried to flash CM11 without artas's recovery, so it did not work. So I've tried CM10, which seemed pretty buggy and camera was not working. Then I did all the reading etc and tried about 10 different roms based on 4.3, .4.4 and even stock rom, camera did not work anywhere.
Every time I try to open an app using camera, it reports: Unfortunately: com.android.camera has stopped. I have tried all kinds of resets (everything available in both CWM and TWRP), online kdz fix, back to stock rom (tried multiple versions of JB) but nothing seems to help. Any ideas? I've tried to flash this persist.img using adb but I got the same error saying that there is no such partition.
Thanks for response.

WeldonEvridge said:
So i thought it wad gonna work. Then at the end....it says this.....
writing 'recovery'...
C:\Users\Weldon Evridge\Android-Mobile-Phone-Tools\droid manager\Android_AIO_Flasher_1.00_by_Fonehacker\Android_AIO_Flasher\tools>
FAILED (remote: partition does not exist)
finished. total time: 2.275s
Click to expand...
Click to collapse
I'm not sure if you have fixed your phone yet, but try having a fresh offline flash, then copy the persist img.

Help bro
It (persist image) use only LG L9 .
Can I use for my motorola razr. Because I have same problem on my phone.

kuma82 said:
Try flashing my persist image with fastboot and see if it fixed adb.
https://mega.co.nz/#!8pt0xCqA!3-uV70G_ItL46LwE8mYCQ7FUYMEXGYNU0KDUqQRVVbo
Messing with the persist image will mess up adb
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hello, can you upload again this file?
Thanks!

Related

Contacting Network problem

Hi
deleted the following apps as it was nagging while restarting the phone.
SprintZone_SZ_2.5.15.apk
Sprint_InstallerNC_2.1.0.apk
SprintMobileWallet_1.5.apk
vtt-sprint_T.5.1.0.74.apk
I have a backup of these apps
now when I start the phone, it continuously shows "Contacting Network" then fails
then after a while it shows "Hands Free Activation"
Your activation could not be completed. Please try again later.
if I press "OK" it shows
Sorry!
The application SprintOmaDm (process com.motorola.android.sprintomadm) has stopped unexpectadly. Please try again
ROM details
45.4.13.MB855.Sprint.US
Androd 2.3.5
Baseban Ver N_01_29.10R
Kernel 2.6.32.29
Build No: 4.5.1A-1_SUN-254_13
the phone is rooted
please help
Did you try restoring the apps you deleted to see if that fixed it?
Sent from my MB855 using xda app-developers app
Shad0wguy said:
Did you try restoring the apps you deleted to see if that fixed it?
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
can't access the home screen. it is constantly trying to connect to the network and will not go further.
it restarts the network search after it fails. loop.
problem got worse.
tried fastboot recovery and flashed cg59.smg boot
now the phone shows "Failed to boot 2
Starting RSD mode
please help
From where did you take that cg?
Cg59 is not recovery. How did you got such idea?
peetr_ said:
From where did you take that cg?
Cg59 is not recovery. How did you got such idea?
Click to expand...
Click to collapse
followed this thread.
http://forum.xda-developers.com/showthread.php?t=1573727
You probably mean this...
scottgl9 said:
Confirmed! I got rid of the aweful 2.3.5 electrify bootloader. Just did this:
[email protected]:~/Desktop/SMG_BP011UP$ fastboot flash boot CG59_0x00000130.smg
sending 'boot' (3294 KB)...
OKAY [ 0.206s]
writing 'boot'...
OKAY [ 0.734s]
finished. total time: 0.940s
Click to expand...
Click to collapse
That was last post from scottgl9...
And there is written fastboot flash boot, not recovery. And noone knows, where did he take that.
You need to take and try 2.3.5 recovery dump.
peetr_ said:
You probably mean this...
That was last post from scottgl9...
And there is written fastboot flash boot, not recovery. And noone knows, where did he take that.
You need to take and try 2.3.5 recovery dump.
Click to expand...
Click to collapse
looks like I may have to wait a long time if I am lucky! otherwise parts for sale! new phone just two weeks old from ebay India about $500 wasted.
You need to read all over here, download the dump and try flashing things with fastboot (in your case, just recovery), if you find a solution, you will help others too.
peetr_ said:
You need to read all over here, download the dump and try flashing things with fastboot (in your case, just recovery), if you find a solution, you will help others too.
Click to expand...
Click to collapse
thanks peetr
I am prepared to try any options available. but the thing is I have only two weeks familiarity with Android and this is my first Android phone.
hope I can get some help with flash mem dump using RSD
found a solution
its here
http://forum.xda-developers.com/showthread.php?t=1785561
portman said:
can't access the home screen. it is constantly trying to connect to the network and will not go further.
it restarts the network search after it fails. loop.
problem got worse.
tried fastboot recovery and flashed cg59.smg boot
now the phone shows "Failed to boot 2
Starting RSD mode
please help
Click to expand...
Click to collapse
i got past this error, you need to get a few files for the photon, one is an sbf (511 mb), another is the stock rom 2.3.5 which you will install through bootstrap, and third when you finally boot into the rom itself, another sbf through rsd and you're good to go. check the "revive the photon from grave" thread, it is all there
say thanks, it helps motivate :angel:

[fastboot] l9 p760 p765 p768 p769

I take no responsibility for any damages incurred to your phone
Please use this script only when necessary
Here is a little script I put together to fastboot L9s with ability to flash/restore ics xloader and uboot (p760, p765, p768, p769) jb (p760)
*I've only tested it on Win 7, but it should work on Vista , not sure about XP and 8
Very useful post about installing the drivers
*Some phones may need a different timing, 4 seconds won't work, worth to try between 0 to 4s and see what works best
Original thread about fastboot
http://forum.xda-developers.com/showthread.php?t=2119090
It's based on wpark - [DEV][Bootloader] u-boot / omap4boot for P920/P720/P940 and its variant
update: file updated, mylk Thanks for catching the mistake!
update2: added p769 20f
Thanks, I'll try this out once I'm home, maybe my phone will finally let me fastboot. Whenever I've tried before, it just normally reboots, doesn't switch to fastboot mode.
Sent from my LG-P768
i think there is some errot in your start.bat .
IF /I '%INPUT%'=='6' GOTO Selection5 ( i think it should be Selection6 , right ? )
and here is my p1.bin an p2.bin . mine is P765 JB (HongKong V20D) . hope you can put this into your file . and may help others .
View attachment 1986726
Tried the method in the link in the 1st post, didn't work. Tried this, still nothing. I get the same "unexpected 2ndstage response" error.
is there somebody who has tried fastboot ?
how is the screen like of the phone ?
is it just a black screen ?
and why the cmd just go to the folder of "yours" then i cant find anything in this folder .
sorry for my nood question ......
cris7i said:
Tried the method in the link in the 1st post, didn't work. Tried this, still nothing. I get the same "unexpected 2ndstage response" error.
Click to expand...
Click to collapse
Both work the same under the hood. Perhaps you've wrong drivers if you get same error msg.
mylk said:
is there somebody who has tried fastboot ?
how is the screen like of the phone ?
is it just a black screen ?
and why the cmd just go to the folder of "yours" then i cant find anything in this folder .
sorry for my nood question ......
Click to expand...
Click to collapse
#1 is just a general fastboot, you can put whatever (boot.img, recovery.img, etc) you want to flash via fastboot in "yours" folder - type: fastboot devices and you'll see if your phone is recognized
and the rest is mainly for recovery, ics xloaders and uboots work nicely with offline flashing method also several people mistakenly soft bricked their phones with omap4boot by flashing prada files which can't happen with this tool
For me general fastboot works on ArchLinux. But I only put recovery with it...
Rixx666 said:
For me general fastboot works on ArchLinux. But I only put recovery with it...
Click to expand...
Click to collapse
of course if you have functional rom and unlocked bootloader you don't need it
Hi there, its been a while since I tried fastboot again, but I have good news. Fastboot worked on my P768 using this method, I selected option 1. Then I was able to send recovery to my phone and then root the phone using a flashable SuperSU zip! 'adb reboot recovery' takes me straight into CWM!
I have some questions though.
Is fastboot permanently on the phone like it is on the P760 now? or do I have to use this program each time to send fastboot commands?
Does this mean that I could potentially flash a custom rom to my phone now? I know all the custom roms out there are not for the P768, so I will get camera problems. But is this the missing piece of the puzzle for custom rom development/testing?
Thank you lelus for this great tool!
donk165 said:
Hi there, its been a while since I tried fastboot again, but I have good news. Fastboot worked on my P768 using this method, I selected option 1. Then I was able to send recovery to my phone and then root the phone using a flashable SuperSU zip! 'adb reboot recovery' takes me straight into CWM!
I have some questions though.
Is fastboot permanently on the phone like it is on the P760 now? or do I have to use this program each time to send fastboot commands?
Click to expand...
Click to collapse
Fastboot is definitely there but something doesn't get passed along during adb reboot bootloader or oem-unlock and phone just reboots instead of booting to fastboot.
Does this mean that I could potentially flash a custom rom to my phone now? I know all the custom roms out there are not for the P768, so I will get camera problems. But is this the missing piece of the puzzle for custom rom development/testing?
Click to expand...
Click to collapse
I'm pretty sure* you can use Android Kitchen to replace these files in latest Cyanogenmod zip with ones from p768 jb and have camera working.
*i might be wrong
Lelus said:
Fastboot is definitely there but something doesn't get passed along during adb reboot bootloader or oem-unlock and phone just reboots instead of booting to fastboot.
I'm pretty sure* you can use Android Kitchen to replace these files in latest Cyanogenmod zip with ones from p768 jb and have camera working.
*i might be wrong
Click to expand...
Click to collapse
great, keep it up @donk165
Thanks. When I find the time. I'm going to make a guide for unlocking the boot loader, pushing CWM with fastboot and rooting.
I'm not confident in building CM, but I did see another user who was willing to try but was stuck with a locked boot loader. Hopefully together we can get the ball rolling for P768 development.
Sent from my LG-P768 using xda app-developers app
donk165 said:
Thanks. When I find the time. I'm going to make a guide for unlocking the boot loader, pushing CWM with fastboot and rooting.
I'm not confident in building CWM, but I did see another user who was willing to try but was stuck with a locked boot loader. Hopefully together we can get the ball rolling for P768 development.
Sent from my LG-P768 using xda app-developers app
Click to expand...
Click to collapse
i think we need help from devs to port camera from official p760 cm to p768 maybe @markolino631 can do it for us, seen we had unlocked bootloader and able to push cwm using fastboot.
I got a P769 from a friend and it is total dead,black screen, no SW update or hard reset key combinations works, only can fastboot and shows a mirrored LG logo , on top right it says V0.5, but unable to flash x-loader, u-boot or recovery, always show the error "remote partition does not exists", i tried to erase the partitions with fastboot but still the error is same. does somebody experienced the same? they call this phone un-brickable
AttiqAamir said:
I got a P769 from a friend and it is total dead,black screen, no SW update or hard reset key combinations works, only can fastboot and shows a mirrored LG logo , on top right it says V0.5, but unable to flash x-loader, u-boot or recovery, always show the error "remote partition does not exists", i tried to erase the partitions with fastboot but still the error is same. does somebody experienced the same? they call this phone un-brickable
Click to expand...
Click to collapse
My guess is corrupted nand or partition table.
What did your friend do to the phone?
Well I don't know, he just sent me that it is not booting. Is there any tool / way to initialize the nand?
AttiqAamir said:
Well I don't know, he just sent me that it is not booting. Is there any tool / way to initialize the nand?
Click to expand...
Click to collapse
Not that I know of
Hey I know this has been a long time to reply but since nothing is working try this command in fastboot
fastboot oem format
I found this information here
http://www.omappedia.com/wiki/Android_Fastboot
The website has a lot of information
Sent from my LG-P769 using xda app-developers app
kuma82 said:
Hey I know this has been a long time to reply but since nothing is working try this command in fastboot
fastboot oem format
I found this information here
http://www.omappedia.com/wiki/Android_Fastboot
The website has a lot of information
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Just heads up, the fastboot files are from lg prada p940 which has somewhat different partition setup but it's definitely worth trying as a last resort if nothing else works.
Thank you for your help, i tried as you advised but it failed it replied as
FAILED (remote failure)
finished. total time: 0.001s

[Q] How to Fix Booting Failed - Nexus 7 Error

Hi,
Does anyone know how to fix the problem in the attached pictures?
Thanks,
Seems to be an issue with your bootloader, try flashing a new one through fastboot
fastboot flash hboot hboot.img
Sent from my Nexus 4 using xda premium
i got same problem, Does anyone know how to fix it?
Fastboot flash a Google stock image for it. Worked for me..... twice
Sent from carbon note 2 on XDA premium app
Booting Failed
Im having the same problem, Can someone help me? I am a bit of a noob. i did download nexus root tool kit. But now i cant even get it to be seen on the computer. all i can hit is restart bootloader or power off. Everything else leads to booting failed.please help need tablet for school.
Help!!!
Okay. i messed up somewhere when trying to flash back to factory rom and completely restore my Nexus 7(I had rooted it and flashed to a custom rom perfectly fine, just wanted to go back to factory just because). Because now whenever i turn on my nexus it says booting failed. Can someone use team viewer or something with me to help me get this fixed. i really need my Nexus for school...
If you need teamviewer I'll be at a PC soon but you should be able to do all this yourself quite easily
Which model do you have 2012? 2013? WiFi? Gsm?
Do you have adb and fastboot set up on PC?
Windows? Linux?
Bootloader locked or unlocked right now?
Boot to bootloader and write down everything on screen here
Let me know and I'll get you the proper software
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thanks for replying
demkantor said:
If you need teamviewer I'll be at a PC soon but you should be able to do all this yourself quite easily
Which model do you have 2012? 2013? WiFi? Gsm?
Do you have adb and fastboot set up on PC?
Windows? Linux?
Bootloader locked or unlocked right now?
Boot to bootloader and write down everything on screen here
Let me know and I'll get you the proper software
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have the 2012 wifi version of the Nexus 7. i have ADB set up on my computer but i'm not sure about fastboot... Bootloader is unlocked. just booted to bootloader, it says google in the middle, a little unlocked lock at the bottom, and with the volume up and down i can choose start, restart bootloader, recovery mode, and power off. When i press start, nothing happens, the screen flashes though for half a second.... Sometimes it will say boot failed at the top left.
Thanks in advanced. i would extremely prefer to do this in team viewer because i'm good with electronics most of the time, but when it comes to this stuff i have no clue what to do. i have watched countless videos with no success.
You'll need to download factory image here
https://developers.google.com/android/nexus/images
Unzip it
Run flash all.bat from fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
I won't be near a PC for about 7-8 hours. If your stuck let me know around then and I can help
Sent from my Nexus 4 using XDA Premium 4 mobile app
THanks!
demkantor said:
You'll need to download factory image here
https://developers.google.com/android/nexus/images
Unzip it
Run flash all.bat from fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
I won't be near a PC for about 7-8 hours. If your stuck let me know around then and I can help
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok so i did the flash all thing and it worked!!! Now do i follow the custom recovery steps? because still when i press start it says booting failed
Edit: i went ahead and did the recovery thing from the one i downloaded from the site you told me to go to. and i still get booting failed
Try this
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now double check you downloaded the correct factory image probably a good idea to check md5sum as well
Then run flashall.bat again
Let me know if that works
Sent from my Nexus 4 using XDA Premium 4 mobile app
errors
demkantor said:
Try this
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now double check you downloaded the correct factory image probably a good idea to check md5sum as well
Then run flashall.bat again
Let me know if that works
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
when typing in the first command it gave me all okays until erasing 'cache'...
Failed <command write failed <No such device or address>>
After that i thought "hmm maybe thats supposed to happen?" so i went ahead to the erase boot command, again
erasing 'boot'...
Failed <command write failed <unknown error>>
Please help. im soooo confused im about to explode... haha
Thanks
EDIT: i realize whenever i run the flash all file, it says
sending bootloader
Failed <command write failed <Invalid argument>>
and then bootloader reboots fine...
then
checking version-bootloader...
Failed
Device version-bootloader is '4.18' .
Update requires '4.23' .
Is this why its not working?? if so how do i update my bootloader?
Can you either attach a pic or write down everything from bootloader screen line by line
Sent from my Nexus 4 using XDA Premium 4 mobile app
Pics
demkantor said:
can you either attach a pic or write down everything from bootloader screen line by line
sent from my nexus 4 using xda premium 4 mobile app
Click to expand...
Click to collapse
View attachment 2551680
View attachment 2551681
First Picture is the flashall file
Second picture is when i type the fastboot erase system -w command
xlilCHeesEitxX3 said:
View attachment 2551680
View attachment 2551681
First Picture is the flashall file
Second picture is when i type the fastboot erase system -w command
Click to expand...
Click to collapse
If you meant the bootloader screen of my nexus im sorry!!
okay so it has the volume rocker buttons and stuff at the top right as usual.
now in order from top to bottom
Fastboot mode (red letters)
Product Name - grouper
Variant - grouper
HW Version - ER3
Bootloader Version - 4.18
Baseband version - N/A
Serial Number - 015d24a42b23ea09
Signing - not defined yet
Lock State - Unlocked (red letters)
hope this is what you were looking for
well I'm at a PC if you want to use team view, if you don't get this until later what I would do is flash everything separate
fastboot flash bootloader bootloader-grouper-4.23.img
(or whatever it is labled)
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash boot boot.img
if this doesn't work than put up the screenshots of cmd again
Team Viewer
demkantor said:
well I'm at a PC if you want to use team view, if you don't get this until later what I would do is flash everything separate
fastboot flash bootloader bootloader-grouper-4.23.img
(or whatever it is labled)
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash boot boot.img
if this doesn't work than put up the screenshots of cmd again
Click to expand...
Click to collapse
I really hope you are still able to use Team Viewer at the time. I tried flashing everything separately but still a no go ....
Thanks so much for all the help so far.. i really appreciate it.
Screenshots
xlilCHeesEitxX3 said:
I really hope you are still able to use Team Viewer at the time. I tried flashing everything separately but still a no go ....
Thanks so much for all the help so far.. i really appreciate it.
Click to expand...
Click to collapse
View attachment 2552860
View attachment 2552861
1st image is when i flash the system
2nd is when i flash the bootloader
Yeah this is not looking too good, I've seen a few times that people have gotten there nexi working when the failed boot pops up but when all these flashes fail it becomes unlikely. Is warranty up? If it is we can try when I get to a PC again but that may not be for a while.
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Yeah this is not looking too good, I've seen a few times that people have gotten there nexi working when the failed boot pops up but when all these flashes fail it becomes unlikely. Is warranty up? If it is we can try when I get to a PC again but that may not be for a while.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think my warranty is up... but alright. maybe im doing something wrong? who knows hopefully we can get it fixed
---------- Post added at 10:54 AM ---------- Previous post was at 10:26 AM ----------
xlilCHeesEitxX3 said:
I think my warranty is up... but alright. maybe im doing something wrong? who knows hopefully we can get it fixed
Click to expand...
Click to collapse
i finnaly got the bootloader to flash. so now everything works except when i try to flash the system... it says
erasing 'system'...
OKAY ( 0.095s)
Sending 'system' <471804 KB>...
FAILED <unknown status code>
finished. total time: 61.355s
hopefully you know of a fix

[Q] Built a CWM recovery, black screen when boot into it

Forgive me if this is the wrong place for this. I followed a few different guides on xda and managed to build a cwm recovery from source. I can fastboot boot into my recovery image and it works fine, makes backups etc. But when i fastboot flash the .img and reboot into recovery it boots to a black screen. Im just not sure where to start in diagnosing the issue. I managed to get a few other issued solved like DTB and malformed fstab, but im stumped here. It might be something silly i did or didnt do. This is for a new device the lg ls740. I can post the recovery.img or the split files from unmkbootimg it it helps, thanks!
I'm having the same issue
Sent from my LGLS740 using XDA Free mobile app
notreal456789 said:
I'm having the same issue
Sent from my LGLS740 using XDA Free mobile app
Click to expand...
Click to collapse
because you were using my recovery, the recovery that doesnt work right! Im asking here for help on what i need to do differently before i compile it.
Ya I figured that out lol ; ) and sorry..I think?I mean, didn't mean to upset you?
Sent from my LGLS740 using XDA Free mobile app
danhalen1 said:
Forgive me if this is the wrong place for this. I followed a few different guides on xda and managed to build a cwm recovery from source. I can fastboot boot into my recovery image and it works fine, makes backups etc. But when i fastboot flash the .img and reboot into recovery it boots to a black screen. Im just not sure where to start in diagnosing the issue. I managed to get a few other issued solved like DTB and malformed fstab, but im stumped here. It might be something silly i did or didnt do. This is for a new device the lg ls740. I can post the recovery.img or the split files from unmkbootimg it it helps, thanks!
Click to expand...
Click to collapse
I think it's because of a brightness problem. You need to enable brightness permanently. For enabling it you need to follow these steps:
1.Unpack your builded recovery(with kitchen)
2.Place "qrdsys.sh" in /ramdisk/sbin/<here>
3.Add the following line into init.rc:
"service qrdtrd /sbin/sh /sbin/qrdsys.sh
oneshot"
4.Repack and flash
Source I got this from: https://github.com/dhinesh77/device_micromax_a57
Get the "qrdsys.sh" file from here: https://github.com/dhinesh77/device_micromax_a57/blob/cm-10.1/recovery/qrdsys.sh
Thanks to dhinesh77 :good:
Try it, if it don't work, report it to me.
GeekyDroid said:
I think it's because of a brightness problem. You need to enable brightness permanently. For enabling it you need to follow these steps:
1.Unpack your builded recovery(with kitchen)
2.Place "qrdsys.sh" in /ramdisk/sbin/<here>
3.Add the following line into init.rc:
"service qrdtrd /sbin/sh /sbin/qrdsys.sh
oneshot"
4.Repack and flash
Source I got this from: https://github.com/dhinesh77/device_micromax_a57
Get the "qrdsys.sh" file from here: https://github.com/dhinesh77/device_micromax_a57/blob/cm-10.1/recovery/qrdsys.sh
Thanks to dhinesh77 :good:
Try it, if it don't work, report it to me.
Click to expand...
Click to collapse
Thanks for the reply, i just tried it here this morning and i still have the same black screen result. Thanks for your help!
danhalen1 said:
Thanks for the reply, i just tried it here this morning and i still have the same black screen result. Thanks for your help!
Click to expand...
Click to collapse
No problem. Actually I thought it would fix it!
Well, what about you try to monitor your screen through ADB to your desktop?
If the recovery works, but has graphical issues, it should show there. If not, it's actually not booting or either not working.
Maby? We haveto zero out the recovery?? Just like the laf partition to access fastboot?
Sent from my LGLS740 using XDA Free mobile app

No wifi after flash factory image

Hello everyone.
I'm new in the forum and I'm looking for help.
Habitually I try to solve my problems by myself but this time I need your help.
I recently acquired a pixel 3. And everything works fine until I had to flash the factory image.
I find the factory image file on google dev website and I follow the instructions.
I also tried different tutos but I always have the same issues.
My pixel 3 restart but I can't turn on WiFi.
My Bluetooth is ok
Finally, it feels like the pixel is more slowly since I flash the factory image. (Setting app crash half of the time).
Is anyone had the same issues or have a solutions ?
Thanks by advance.
totib38 said:
Hello everyone.
I'm new in the forum and I'm looking for help.
Habitually I try to solve my problems by myself but this time I need your help.
I recently acquired a pixel 3. And everything works fine until I had to flash the factory image.
I find the factory image file on google dev website and I follow the instructions.
I also tried different tutos but I always have the same issues.
My pixel 3 restart but I can't turn on WiFi.
My Bluetooth is ok
Finally, it feels like the pixel is more slowly since I flash the factory image. (Setting app crash half of the time).
Is anyone had the same issues or have a solutions ?
Thanks by advance.
Click to expand...
Click to collapse
Make sure you have the latest sdk platform tools, r28.
Then download the factory image again, it might have been corrupted. Use 7zip to extract the zip file.
Flash the factory image again using the flash-all batch file. Note, this will wipe your device.
If that doesn't work then you might have a hardware issue.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Make sure you have the latest sdk platform tools, r28.
Then download the factory image again, it might have been corrupted. Use 7zip to extract the zip file.
Flash the factory image again using the flash-all batch file. Note, this will wipe your device.
If that doesn't work then you might have a hardware issue.
Click to expand...
Click to collapse
Thanks for your answer.
I will retry tonight at home.
One more detail : so I have to modified flash-all batch file ?
In some discussion I saw some people delete -w of the script.
I will inform if the process is ok
totib38 said:
Thanks for your answer.
I will retry tonight at home.
One more detail : so I have to modified flash-all batch file ?
In some discussion I saw some people delete -w of the script.
I will inform if the process is ok
Click to expand...
Click to collapse
If you delete the -w it will not wipe your device. You can try that, but if problem still is there then include the -w. Wiping your device is a better trouble shooting solution but you will have to setup your device like it was new. It's up to you.
Sent from my [device_name] using XDA-Developers Legacy app
Thanks for your support.
I just tried several flash factory image but the result is always the same.
I can't turn on wifi setting ....
Everything else seems to work.
I'm really disappointed and I don't know what to do.
It seems there is a issue with vendor.img
After my first boot, I download Es explorer and I navigate in :
'System>vendor>ECT>wifi' and it seems files are missing compare to my others devices.
Is there a way to modify the field with root permission?
Maybe you need to unlock the critical partition before flashing?
gm007 said:
Maybe you need to unlock the critical partition before flashing?
Click to expand...
Click to collapse
Hello gm007
How can I unlock the critical partition before flashing ?
Thanks by advance ?
totib38 said:
Hello gm007
How can I unlock the critical partition before flashing ?
Thanks by advance ?
Click to expand...
Click to collapse
fastboot flashing unlock_critical
Not sure if it's needed.
this will wipe ur phone same as unlocking bootloader.
gm007 said:
fastboot flashing unlock_critical
Not sure if it's needed.
this will wipe ur phone same as unlocking bootloader.
Click to expand...
Click to collapse
It's failed...
It's indicate 'Invalid argument unlock_critical'
totib38 said:
Thanks for your support.
I just tried several flash factory image but the result is always the same.
I can't turn on wifi setting ....
Everything else seems to work.
I'm really disappointed and I don't know what to do.
It seems there is a issue with vendor.img
After my first boot, I download Es explorer and I navigate in :
'System>vendor>ECT>wifi' and it seems files are missing compare to my others devices.
Is there a way to modify the field with root permission?
Click to expand...
Click to collapse
I don't know what you're seeing in the etc folder but this is what I have in the pixel 3,
jd1639 said:
I don't know what you're seeing in the etc folder but this is what I have in the pixel 3,
Click to expand...
Click to collapse
Ah .....
Ok so the vendor.img should be ok.
I'm completely lost .
Everything works except that. And the phone has just a week so I don't think it's a hardware issue.
If I don't find the solution i will keep this device in my desk ?
totib38 said:
Ah .....
Ok so the vendor.img should be ok.
I'm completely lost .
Everything works except that. And the phone has just a week so I don't think it's a hardware issue.
If I don't find the solution i will keep this device in my desk [emoji25]
Click to expand...
Click to collapse
Did the wifi work when you first got the phone? When you flashed the factory image did you wipe the device or use the flash all with the -w removed? If you wiped the device I'm guessing it is a hardware issue.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Did the wifi work when you first got the phone? When you flashed the factory image did you wipe the device or use the flash all with the -w removed? If you wiped the device I'm guessing it is a hardware issue.
Click to expand...
Click to collapse
Yes the wifi worked at the first boot.
I'm guessing I have wipe the device and that's the reason wifi there is a problem.
Is there any way to recover wifi drivers or anything else ?
What are my possibilities ?
Go on a sav and change wifi hardware ?
totib38 said:
Yes the wifi worked at the first boot.
I'm guessing I have wipe the device and that's the reason wifi there is a problem.
Is there any way to recover wifi drivers or anything else ?
What are my possibilities ?
Go on a sav and change wifi hardware ?
Click to expand...
Click to collapse
I don't know how flahing the factory image would cause the problem. But a couple of things to check. First, make sure you're using the latest sdk platform tools (fastboot and adb), r28. Then make sure you're using the correct factory image, there one for docomo or something like that which is for the Japanese variant, and redownload it in case you got something corrupted.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I don't know how flahing the factory image would cause the problem. But a couple of things to check. First, make sure you're using the latest sdk platform tools (fastboot and adb), r28. Then make sure you're using the correct factory image, there one for docomo or something like that which is for the Japanese variant, and redownload it in case you got something corrupted.
Click to expand...
Click to collapse
I will try again tonight but I have no hope
I use the last SDK platform tools r28.0.1
And I took the factory image from google devs website.
My Mac address is block on 02:00:00:00:00:00 to be more precise.
totib38 said:
It's failed...
It's indicate 'Invalid argument unlock_critical'
Click to expand...
Click to collapse
Seems you have outdated sdk try to remove and install the latest one as suggested above. Or try another pc.
gm007 said:
Seems you have outdated sdk try to remove and install the latest one as suggested above. Or try another pc.
Click to expand...
Click to collapse
It Is not because fastboot flashing unlock_critical is a command for pixel 3 XL ?
I got the pixel 3 device
totib38 said:
Hello everyone.
I'm new in the forum and I'm looking for help.
Habitually I try to solve my problems by myself but this time I need your help.
I recently acquired a pixel 3. And everything works fine until I had to flash the factory image.
I find the factory image file on google dev website and I follow the instructions.
I also tried different tutos but I always have the same issues.
My pixel 3 restart but I can't turn on WiFi.
My Bluetooth is ok
Finally, it feels like the pixel is more slowly since I flash the factory image. (Setting app crash half of the time).
Is anyone had the same issues or have a solutions ?
Thanks by advance.
Click to expand...
Click to collapse
I think you're platform-tools are not up to date. Download them from here:
https://developer.android.com/studio/releases/platform-tools
Put the facrory image in the same folder as the platform-tools and execute flash-all from there.
I thougt mine were up to date, but not everyting from the image got flashed.
With the latest platform tools everyting was ok.
rhino666 said:
I think you're platform-tools are not up to date. Download them from here:
https://developer.android.com/studio/releases/platform-tools
Put the facrory image in the same folder as the platform-tools and execute flash-all from there.
I thougt mine were up to date, but not everyting from the image got flashed.
With the latest platform tools everyting was ok.
Click to expand...
Click to collapse
Thanks for your help.
This is precisely the one I took yesterday and I always have the same issues
totib38 said:
Thanks for your help.
This is precisely the one I took yesterday and I always have the same issues
Click to expand...
Click to collapse
Then the only thing I can think of is for you to try another cable or computer.

Categories

Resources