In need of help, upgrade failure from AT&T model to Google Fi Pie version - LG V35 Guides, News, & Discussion

Do you need to Upgrade or Refurbish in LGUP when moving to Pie?

X-Nemesis said:
I followed the instructions for updating via LGUP with the modded 1.14 version.
I placed the KDZ in the common folder and also extracted the .dll from that KDZ into the same folder, renaming it to LGUP_Common.dll, and replacing the version that was in there.
I then began the upgrade process which failed at 74%, and upon trying to load up LGUP again, I get the following error now.
DLL for 350AWM10i is invalid. Please, install valid DLL package(*.msi). for the model.
My phones screen says COM 10 and is stuck at 91%
Any suggestions?
Click to expand...
Click to collapse
Make sure you grant permissions to dll file you placed. Might be problem.

dave71670 said:
Make sure you grant permissions to dll file you placed. Might be problem.
Click to expand...
Click to collapse
Thanks, I'll try that out.
Another error I'm getting from LGUP at 74% failure is
Error: 0x2000, Invalid command response code = 0x80000001

X-Nemesis said:
Thanks, I'll try that out.
Another error I'm getting from LGUP at 74% failure is
Error: 0x2000, Invalid command response code = 0x80000001
Click to expand...
Click to collapse
Are you using the patched version of LGUP?

Shawnashley said:
Are you using the patched version of LGUP?
Click to expand...
Click to collapse
Yes, the latest development though is that I've lost download mode and the phone is stuck in fastboot. I'm now looking to see if there's a way to get download mode back using fastboot, but the V35 doesn't have root so not sure if that's a problem.
I found this thread, https://forum.xda-developers.com/android/general/unbrick-lg-model-download-recovery-t3060184
But since there is no AT&T KDZ available, can I use one of the Unlocked versions to restore download mode following that guide?

X-Nemesis said:
Yes, the latest development though is that I've lost download mode and the phone is stuck in fastboot. I'm now looking to see if there's a way to get download mode back using fastboot, but the V35 doesn't have root so not sure if that's a problem.
I found this thread, can I follow the instructions in this thread for restoring download mode using the Pie KDZ for Fi or Amazon?
https://forum.xda-developers.com/android/general/unbrick-lg-model-download-recovery-t3060184
Click to expand...
Click to collapse
I'm not ?% sure. I've never had to do that myself, so I have no first hand knowledge. Maybe someone else in the community has. Good luck though. If I find any info I'll surely pass it along.

Shawnashley said:
I'm not % sure. I've never had to do that myself, so I have no first hand knowledge. Maybe someone else in the community has. Good luck though. If I find any info I'll surely pass it along.
Click to expand...
Click to collapse
Thanks for that, this is a learning experience for sure.

X-Nemesis said:
Thanks for that, this is a learning experience for sure.
Click to expand...
Click to collapse
I'm assuming you have tried adb commands. There is a tool that may be of some assistance to you here:
http://forum.gsmhosting.com/vbb/f606/coming-android-multi-tools-v1-02b-special-gsmforum-1633070/
Hopefully, it helps. Good Luck.

Yeah I came across that program in my searches but didn't see any way to restore download mode. I'm still trying to locate how to restore download mode through ADB/fastboot. I'm definitely over my head in this one.

X-Nemesis said:
Yeah I came across that program in my searches but didn't see any way to restore download mode. I'm still trying to locate how to restore download mode through ADB/fastboot. I'm definitely over my head in this one.
Click to expand...
Click to collapse
Have you tried using Cmd prompts? Just a thought. You did say you are stuck in fastboot?

Yeah, it's stuck in Fastboot. From what I've read so far, the only way to get back into download mode is to reflash certain files, using ADB, from a partition file found in the KDZ but that's about as far as I've gotten. I'm also not sure if not having an AT&T KDZ is a problem and that I could use any of the other unlocked versions. But looking in the KDZ's I did download with the Extractor tool, I wasn't able to figure out which partition file I was supposed to extract the needed files from.

Need help
My lg v35 at&t stuck in fastboot mode

X-Nemesis said:
Yeah, it's stuck in Fastboot. From what I've read so far, the only way to get back into download mode is to reflash certain files, using ADB, from a partition file found in the KDZ but that's about as far as I've gotten. I'm also not sure if not having an AT&T KDZ is a problem and that I could use any of the other unlocked versions. But looking in the KDZ's I did download with the Extractor tool, I wasn't able to figure out which partition file I was supposed to extract the needed files from.
Click to expand...
Click to collapse
I believe it's the laf partition that contains download mode. I read somewhere around here that even a G7/V40 laf partition will work. Interesting that you can get into fastboot without getting someone with an Octoplus to flash the engineering boot partition. I wonder, if you had had the precognition to enable oem unlock, if you could unlock your bootloader now. That'd probably be too easy though.

Eric janaika said:
I believe it's the laf partition that contains download mode. I read somewhere around here that even a G7/V40 laf partition will work. Interesting that you can get into fastboot without getting someone with an Octoplus to flash the engineering boot partition. I wonder, if you had had the precognition to enable oem unlock, if you could unlock your bootloader now. That'd probably be too easy though.
Click to expand...
Click to collapse
I believe I did have that enabled yes, but as for how I'd unlock the bootloader I'm clueless. You've probably seen the big thread regarding unlocking the bootloader for the V35, and I seem to remember that nobody had had any luck yet. I'd probably blow the darn thing up lmao.

X-Nemesis said:
I believe I did have that enabled yes, but as for how I'd unlock the bootloader I'm clueless. You've probably seen the big thread regarding unlocking the bootloader for the V35, and I seem to remember that nobody had had any luck yet. I'd probably blow the darn thing up lmao.
Click to expand...
Click to collapse
Could it be as simple as fastboot oem unlock? It's not like people could even run that command since fastboot is normally disabled.

Eric janaika said:
Could it be as simple as fastboot oem unlock? It's not like people could even run that command since fastboot is normally disabled.
Click to expand...
Click to collapse
So I tried fastboot oem unlock but got the error 'FAILED (command write failed (Unknown error))'

X-Nemesis said:
So I tried fastboot oem unlock but got the error 'FAILED (command write failed (Unknown error))'
Click to expand...
Click to collapse
No such luck huh? I guess that would've been too easy. Can you try a different USB port, particularly a 2.0 (or 3.0 if you're already using 2.0)?

Eric janaika said:
No such luck huh? I guess that would've been too easy. Can you try a different USB port, particularly a 2.0 (or 3.0 if you're already using 2.0)?
Click to expand...
Click to collapse
Thanks for helping me out btw. Regarding this process, is it necessary when running fastboot commands that the phone is recognized in Device Manager (which it isn't)?

X-Nemesis said:
Thanks for helping me out btw. Regarding this process, is it necessary when running fastboot commands that the phone is recognized in Device Manager (which it isn't)?
Click to expand...
Click to collapse
When my V35 in fastboot is connected to my computer, it shows up under the category "Kedacom USB Device" as "Android Bootloader Interface". Is your phone recognized when you type "fastboot devices"? When I run that command, my output is "LMV350AWMb075fc5f fastboot".

I think I'm just spiraling down into a hole here. I was following some advice in another thread where I extracted the laf.img file and ran the fastboot boot laf.img And now the phone is displaying a 'Firmware Update' screen. The device still does not show up in my device manager.
But when I did type in fastboot devices it did show something similar to what you have there.

Related

BRICKED Galaxy Nexus - please help me restore/advice

Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
This ISN'T Resolved. I get errors when attempting to fastboot the stock image
~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'
If anybody has any ideas please let me know, I really don't know what to do at this point.
grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Okay your bootloader is unlocked which is good, but your MAC doesn't see your phone in bootloader mode?
grnmons said:
Plan B is to use a PC which I can only access later in the week.
Click to expand...
Click to collapse
Can you bootcamp or use a virtual machine?
grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Wrong section..but
I would def use a PC and use Odin ! Make your life easier...it takes like 3-5 Mins..takes it to stock!
Sent from my Galaxy Nexus using xda premium
All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Sent from my Galaxy Nexus using Tapatalk
Please uninstall and reinstall your phones drivers. Your just soft bricked is all. Once your computer sees the device you should be good.
sent from the Almighty One himself....
borgey said:
All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Click to expand...
Click to collapse
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?
grnmons said:
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?
Click to expand...
Click to collapse
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html
zephiK said:
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html
Click to expand...
Click to collapse
Thanks. Can you confirm that these are the steps?
1) Download the latest stock image( i will leave finding that image to you since this post can become outdated)
2) Unzip the files, and place the images into the adb-fastboot folder you created on your desktop above.
3) Open a terminal and use the following commands:
Code:
~/Desktop/adb-fastboot/adb reboot bootloader
4) Wait for bootloader to reboot on phone.
5) Then, in terminal use the following commands:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
~/Desktop/adb-fastboot/fastboot flash system ~/Desktop/adb-fastboot/system.img
~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/recovery.img
~/Desktop/adb-fastboot/fastboot flash userdata ~/Desktop/adb-fastboot/userdata.img
~/Desktop/adb-fastboot/fastboot erase cache
~/Desktop/adb-fastboot/fastboot oem lock
6) Reboot to System, and you should be returned to Stock and Unrooted
~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'
anybody have any other suggestions to this? or a follow up?
It should be easy to fix. You do not seem to have the correct driver installed.
Sent from my Galaxy Nexus using xda premium
Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.
grnmons said:
Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.
Click to expand...
Click to collapse
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)
ogdobber said:
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)
Click to expand...
Click to collapse
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?
grnmons said:
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?
Click to expand...
Click to collapse
download the gnex-su.zip and put in in the root of your sd card. then in recovery select "-install zip from sdcard" then "-choose zip from sdcard" then select the gnex-su.zip. this will give you root and install the superuser app
not to get ahead (previous post), but after your computer recognizes the phone you need to flash clockwork recovery
you need to open a terminal in the platform-tools folder of the sdk (also put the recovery.img there) and then
Code:
fastboot flash recovery name-of-recovery.img
Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Just got your last post, I'm unfamiliar with SDK but I've since put the recovery file in there, not sure how to flash recovery. I have tried flashing recovery through terminal and surprisingly it says "-bash: fastboot: command not found"
grnmons said:
Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Click to expand...
Click to collapse
that is for the nexus s
check your pm
ogdobber said:
that is for the nexus s
check your pm
Click to expand...
Click to collapse
If you are still having problems ...like I said before ...use Odin......since the simple process of fastboot is not working properly for you.Odin makes things so Much easier
Sent from my Galaxy Nexus using xda premium

Purchased an AT&T M* unlocked with S-ON and want to restore to factory / stock

I have read many different methods on how to restore a phone back to original OEM specifications but seem unable to complete the process.
I downloaded the Nandroid for my CID, copied the files to the SDCARD but the installation failed with TWRP. Not sure if someone has a good tutorial on how to get the device back to factory specs. Doesn't HTC have an application that can restore a phone? When I worked at Motorola years ago we had a home grown utility that could restore a device entirely including firmware, software, boot images and such.
I am new to HTC devices and appreciate assistance with this. Thank you.
Run the official ATT ruu bro. Give me a sec and I'll edit this post with the link. Quick question, can you tell me if the phone is still unlocked or relocked?
InflatedTitan said:
Run the official ATT ruu bro. Give me a sec and I'll edit this post with the link. Quick question, can you tell me if the phone is still unlocked or relocked?
Click to expand...
Click to collapse
It is still unlocked. When I boot to recovery it shows tampered, unlocked, s-on.
Ok hopefully you know how to execute fastboot commands. You'll need to simply boot into boot loader, fire up command prompt and enter this command.
fastboot oem lock
Once locked you need to download this and run it as any other program on your computer.
http://dl3.htc.com/application/RUU_M...5_signed_2.exe
InflatedTitan said:
Ok hopefully you know how to execute fastboot commands. You'll need to simply boot into boot loader, fire up command prompt and enter this command.
fastboot oem lock
Once locked you need to download this and run it as any other program on your computer.
http://dl3.htc.com/application/RUU_M...5_signed_2.exe
Click to expand...
Click to collapse
I know fastboot and adb very well. The URL you provided does not resolve:
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
ngerasimatos said:
I know fastboot and adb very well. The URL you provided does not resolve:
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
Click to expand...
Click to collapse
Sorry brother it was a direct dl link and I wanted to try my luck with copy and pasting lol. Here's the link to the thread instead. http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Now mind you I'm not sure if you planning on hacking it or not, but if you do that ruu the only way to s-off is to pay $25 for the sunshine app.
InflatedTitan said:
Ok hopefully you know how to execute fastboot commands. You'll need to simply boot into boot loader, fire up command prompt and enter this command.
fastboot oem lock
Once locked you need to download this and run it as any other program on your computer.
http://dl3.htc.com/application/RUU_M...5_signed_2.exe
Click to expand...
Click to collapse
Yeah you copied and pasted directly instead of right clicking on the link and selecting "copy link address"
http://dl3.htc.com/application/RUU_...20.51A.4198.01L_F_release_387305_signed_2.exe
InflatedTitan said:
Sorry brother it was a direct dl link and I wanted to try my luck with copy and pasting lol. Here's the link to the thread instead. http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Now mind you I'm not sure if you planning on hacking it or not, but if you do that ruu the only way to s-off is to pay $25 for the sunshine app.
Click to expand...
Click to collapse
Honestly., the phone is going to be a gift and the last thing I wanted was them to panic when they booted it and saw the red HTC disclaimer at the bottom of the screen, or if they have issues with the device and AT&T gives them grief that the ROM is not factory.
It seems to be currently running Android Revolution HD 11.2 and the ROM doesn't really have any issues that I have seen, but in the end its not going to be my device to support to I want to keep it simple for the user who is technologically challenged (ex iPhone user)
That's perfect then. Just run that ruu and it'll be like a fresh device.
InflatedTitan said:
That's perfect then. Just run that ruu and it'll be like a fresh device.
Click to expand...
Click to collapse
Awesome. Just finished and it is like brand new again. Thanks!

Find 7 (x9076) soft bricked, misread by device manager,

Hey Everyone,
I have a Find 7 (X9076). A while back I updated to the "stable version " of ColorOSi and ever since my usb doesn't charge the phone and vol down key doesn't work. Additionally it is being misread by the computer device manager as a "Samsung Android Device" when it is in boot loader mode.
I suspected it was a software/kernel issue because when I checked the registry I found the original oppo drivers, so I attempted to flash a new kernel to the device and ended up soft bricking it (no image). Now even though it is soft bricked I am still able to get into boot loader mode (no image). Please Help?
I have used Find 7 recovery installer and FASTBOOT (CMD) as well as trying to use ADB and a Find 7 unbricking tool in Windows 7 test mode the last two didn't work/didn't recognize my phone at all. I refuse to abandon my device so what do I do?
Given you have adb access, you could extract the contents of the current (2.x?) color os image, and fastboot flash the partitions manually.
I recently did this and 'recovered' my device.
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Midnight247 said:
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Click to expand...
Click to collapse
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
ADB, FastBoot and the USB
I don't know if I was clear in my explanation as to how and when my device (FIND7 X9076) is recognized ONLY by the following: my Computer (Windows 7), the Device Manager, Fast-Boot and on the FIND7 Recovery Installer. I have been able to enter fast-boot mode on any version of the ColorOS I flashed, 1.2 - 2.5.1, (stable version) and work within the confines of that mode. However when the USB is connected in anything other mode (recovery-main OS) it ceases functionality (sending information to comp for recognition, charging, etc.). Also the charger doesn't work and nor does the notification light. Now I may be wrong, but for these reasons I believe the problem is likely software related. I am open to any opinions and advice.
-Thank You Everyone
tropical cactus said:
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
Click to expand...
Click to collapse
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Midnight247 said:
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Click to expand...
Click to collapse
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
tropical cactus said:
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
Click to expand...
Click to collapse
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Midnight247 said:
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Click to expand...
Click to collapse
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
tropical cactus said:
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
Click to expand...
Click to collapse
hmm okay, i see I will keep you posted
**IMPORTANT UPDATE**
***MAKE OPPO FIND 7 OPERABLE****
following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
By using the afformentioned commands in fastboot (of course) I was able to restore my phone to almost full functionality. It operates noramally and I fixed the notication light, But I say almost because I cannot charge my phone or have it recognized by my computer through any charger or usb connection when it is on normally or in recovery mode so if any one is familiar with this problem please respond or simply voice ideas.
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
RobboW said:
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
Click to expand...
Click to collapse
I do, have full functionality : ) everything but the USB is performing properly, but to be honest I dont know what AOSP is.....also this will repair functionality to the USB?

Secure Booting Error! Cause: boot certification verify

Good day mate. My brick phone is F460S variant. I got this error when I tried to go back to Lollipop using Lg flash tool 2014, it got stuck on 5% and remove usb cable and start again, after that I got this error Secure Booting Error! Cause: boot certification verify.
No download mode
No recovery
anyone can help me please?:crying:
anyone?
You have triggered the downgrade QFUSE. There is nothing you can do apart from trying to unbrick it like it was dead, but that's not guaranteed to work. You should have researched more before attempting this. My prototype doesn't have a QFUSE, so i am free to downgrade via TOT to kitkat or lollipop.
西村大一 said:
You have triggered the downgrade QFUSE. There is nothing you can do apart from trying to unbrick it like it was dead, but that's not guaranteed to work. You should have researched more before attempting this. My prototype doesn't have a QFUSE, so i am free to downgrade via TOT to kitkat or lollipop.
Click to expand...
Click to collapse
What does QFUSE mean?
anmino said:
What does QFUSE mean?
Click to expand...
Click to collapse
I second you on this. I just uninstalled MultiROM and got the secure booting error. Depending on the ROM you have, find a bumped kernel and flash it. Most of the kernels on XDA are pre-bumped unless the developer states so. Boot into recovery, tutorials on the internet, then flash the kernel and voila.
if you can use twrp or you're able to flash, use mr_bump.zip: https://mega.nz/#!DNwhRBrK!Ki6zIzXca0KjPShi6L2oaCYIr0CkmH8sEymEt-0Q3ys
oh sorry, I didn't see "no recovery".
HardStyl3r said:
if you can use twrp or you're able to flash, use mr_bump.zip: https://mega.nz/#!DNwhRBrK!Ki6zIzXca0KjPShi6L2oaCYIr0CkmH8sEymEt-0Q3ys
oh sorry, I didn't see "no recovery".
Click to expand...
Click to collapse
Yes, no DOWNLOAD mode and RECOVERY mode.. Anyone have an idea how to fix this?
anyone?
Hello, i got the same probleme and i've trying a lot of things but not resolved..
My phone is a LG G3 Beat F470s..
Please help us..
Dowblnload adb and fastboot drivers
Download laf.img for your device
Download LG Drivers
Get you G3 to fastboot mode. Hold volume up and connect it to PC
Open fastboot and adb folder in PC, ctrl+shift+right click and open cmd. Type fastboot devices...if ur device is listen then proceed, if not u did not do something cotrectly...if yes just flash laf img to your G3 and voila
I remember me that I was in the same situation:
No TWRP, no download mode, so i have use in pat this thread:
https://forum.xda-developers.com/showthread.php?t=1752270
And an other that i haven't found again (xda thread), in some lines:
=> download the last img file from: https://eu.dl.twrp.me/d855/
=> no download mode available so no possibility to flash manually twrp file from an LG Flash Tool
==> so setup an adb connexion to the phone, cp command to copy the img file on the sdcard or where you want
=> command: "flash recovery twrp-2.8.x.x-xxx.img" (https://www.xda-developers.com/how-to-install-twrp/
=> if it's as worked, you could reboot manually in twrp, make again the partitions if needed and flash any ROM.

Please Help [Stuck on boot logo, can't boot to recovery or ROM]

Stuck on boot logo !!!!! :crying:
Can't :
1. Can't boot to ROM (as doing so just stays on boot logo)
2. Can't boot into recovery (as doing this gets me to either black screen or just boots back to the boot logo)
Can :
1. Can enter bootloader
2. Can able to use fastboot commands
Tried:
1. flashing stock ROM several times,
2. flashing stock recovery
3. flashing twrp recovery
:crying:
Check my guide. It might come handy.
https://forum.xda-developers.com/le...-lenovo-p2-t4006405/post80955105#post80955105
alirazaagha said:
Check my guide. It might come handy.
https://forum.xda-developers.com/le...-lenovo-p2-t4006405/post80955105#post80955105
Click to expand...
Click to collapse
Friend thanks for the reply but your link just says "Duplicate thread. "
hackiee said:
Friend thanks for the reply but your link just says "Duplicate thread. "
Click to expand...
Click to collapse
Yes, it was. Check this one.
https://forum.xda-developers.com/lenovo-p2/how-to/guide-unbrick-unlocked-lenovo-p2-t4006401
alirazaagha said:
Yes, it was. Check this one.
https://forum.xda-developers.com/lenovo-p2/how-to/guide-unbrick-unlocked-lenovo-p2-t4006401
Click to expand...
Click to collapse
Thanks for your post friend, but, your guide doesn't fulfill my situation.
As, I am stuck on bootliader or boot logo.
I have flashed all firmwares s048,s233,s244,s51 through fastboot but none of them able to get me out of it.
Even tried flashing various recoveries both stock and twrp but neither of them helped
If, anyhow I can be able to enter into TWRP. It will solve the problem. But, I don't know nothing seems to work.
Even tried corrupting the bootloader and then flashing blankflash, but that too didn't able to get me out of the bootlogo.
Please help ?
alirazaagha said:
Yes, it was. Check this one.
https://forum.xda-developers.com/lenovo-p2/how-to/guide-unbrick-unlocked-lenovo-p2-t4006401
Click to expand...
Click to collapse
Hey, can you please do 1 thing.
Can you provide an image of the bootloader mode of your lenovo p2, if, there's something to lookup idk
I am attaching image of my bootloader, if you can look into it.
Thanks
hackiee said:
Hey, can you please do 1 thing.
Can you provide an image of the bootloader mode of your lenovo p2, if, there's something to lookup idk
I am attaching image of my bootloader, if you can look into it.
Thanks
Click to expand...
Click to collapse
It's alright.
alirazaagha said:
It's alright.
Click to expand...
Click to collapse
nothing strange ? Ok thanks
hackiee said:
nothing strange ? Ok thanks
Click to expand...
Click to collapse
Yep. Go ahead. You can try S244 firmware to try and boot your phone. If it boots then update accordingly as I mentioned in my guide.
alirazaagha said:
Yep. Go ahead. You can try S244 firmware to try and boot your phone. If it boots then update accordingly as I mentioned in my guide.
Click to expand...
Click to collapse
Still no luck! :crying: flashed S244 several times but nothing.
Can you confirm one more thing.
When I give
"Fastboot format system" I get :
"Formatting is not supported for file system with type 'raw'."
screenshot attached. Please check
hackiee said:
Still no luck! :crying: flashed S244 several times but nothing.
Can you confirm one more thing.
When I give
"Fastboot format system" I get :
"Formatting is not supported for file system with type 'raw'."
screenshot attached. Please check
Click to expand...
Click to collapse
OK so you are not following my guide Check .txt file attached in that guide and if you are still unsure then ask me.
alirazaagha said:
OK so you are not following my guide Check .txt file attached in that guide and if you are still unsure then ask me.
Click to expand...
Click to collapse
I have checked the text file of your guide, and they are the same instructions which I have been following since start. :silly:
The "fastboot format system" is a command which I used to do on my Moto G, and was able to format system successfully.
But, I don't remember if it used to work on P2 or not , that's why I asked you. If, you can use that command to check the output on your device.
Thanks
hackiee said:
I have checked the text file of your guide, and they are the same instructions which I have been following since start. :silly:
The "fastboot format system" is a command which I used to do on my Moto G, and was able to format system successfully.
But, I don't remember if it used to work on P2 or not , that's why I asked you. If, you can use that command to check the output on your device.
Thanks
Click to expand...
Click to collapse
Hmmm so you haven't read .txt file carefully. Command is:
Fastboot ERASE system
See the difference now? :silly:
Please, discuss it on that thread if need so others could also benefit from it.
alirazaagha said:
Hmmm so you haven't read .txt file carefully. Command is:
Fastboot ERASE system.
Click to expand...
Click to collapse
OMG, yes brother, I already know the command, and I have used it several times, the fastboot ERASE command, but, as mentioned several timesin the past, it is not solving my problem.
As, I am still not able to enter into any recovery(neither stock nor twrp), and not able to boot and OS.
That's why, I wanna try "Fastboot format system" command.
If, somehow that solves my problem
hackiee said:
OMG, yes brother, I already know the command, and I have used it several times, the fastboot ERASE command, but, as mentioned several timesin the past, it is not solving my problem.
As, I am still not able to enter into any recovery(neither stock nor twrp), and not able to boot and OS.
That's why, I wanna try "Fastboot format system" command.
If, somehow that solves my problem
Click to expand...
Click to collapse
OK. I though that you only tried Format command not erase. You should skip this command and do the whole process. I have added this command so that previous system files are erased. But, I booted my phone without using this command first time. Second time, I tried to see if I can do it all in a single process then I added this command and it worked without any issues and all the process went smooth and phone booted like a new one.
Try all commands but skip erase system command.
stuck on logo , have access to fastboot only
My phone stuck on logo when i open it or when i insert charger
when i try to open recovery(volume up + down) it turned off and i can't open recovery by any way
i can access fastboot
i tried your instruction and Lenovo+P2+UnBrick+OneTeam-EypCnn and all other fastboot roms
i tried install Twrp and stock recovery
i tried blankflash
that didn't help ,i can only access fastboot
what is your recommendation ? it's a hardware issue ?
DrGhost001 said:
stuck on logo , have access to fastboot only
My phone stuck on logo when i open it or when i insert charger
when i try to open recovery(volume up + down) it turned off and i can't open recovery by any way
i can access fastboot
i tried your instruction and Lenovo+P2+UnBrick+OneTeam-EypCnn and all other fastboot roms
i tried install Twrp and stock recovery
i tried blankflash
that didn't help ,i can only access fastboot
what is your recommendation ? it's a hardware issue ?
Click to expand...
Click to collapse
Did you find any solution?
Same issue here, I guess it's a hardware issue: SSD is damaged ?
fastboot erase system
fastboot format:ext4 system
Maybe related to the file system ?
i have the same probelm, do you guys find any solution ?

Categories

Resources