Related
Hello all,
Anybody can help me, my problem is that my nexus 6p stuck on google screen (boot-loop), noting that unfortunately the boot-loader is locked . I've tried different solutions but non of the worked.
What to do please???
GlorySy said:
Hello all,
Anybody can help me, my problem is that my nexus 6p stuck on google screen (boot-loop), noting that unfortunately the boot-loader is locked . I've tried different solutions but non of the worked.
What to do please???
Click to expand...
Click to collapse
Install Wugfresh or any other toolkit of your choice to your PC, install drivers, install stock rom, follow onscreen instructions, done.
superviked said:
Install Wugfresh or any other toolkit of your choice to your PC, install drivers, install stock rom, follow onscreen instructions, done.
Click to expand...
Click to collapse
This won't work. The bootloader is locked and he has no way to unlock it.
GlorySy said:
Hello all,
Anybody can help me, my problem is that my nexus 6p stuck on google screen (boot-loop), noting that unfortunately the boot-loader is locked . I've tried different solutions but non of the worked.
What to do please???
Click to expand...
Click to collapse
Can you get into the stock recovery?
@GlorySy, you seem on the same issue as this. Please have a look and confirm it is what we got to worry. http://forum.xda-developers.com/nexus-6p/help/main-board-failure-story-t3409400
Not applicable
superviked said:
Install Wugfresh or any other toolkit of your choice to your PC, install drivers, install stock rom, follow onscreen instructions, done.
Click to expand...
Click to collapse
I cannot install any thing with locked boot loader :crying:
Yes
Heisenberg said:
Can you get into the stock recovery?
Click to expand...
Click to collapse
Yes I can, but can do nothing except for turn off the device. :crying:
GlorySy said:
Yes I can, but can do nothing except for turn off the device. :crying:
Click to expand...
Click to collapse
Go to my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 13 to adb sideload one of the full OTA zips.
Heisenberg said:
Go to my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 13 to adb sideload one of the full OTA zips.
Click to expand...
Click to collapse
I just started having this same issue.
I can't get into recovery from the bootloader in order to perform section 13. Once hit recovery, it's back to looping boot screen with white Google text.
Just got finished with Google phone support. They're sending me a new device. It must be a hardware failure.
Background: I got OTA notification on Friday night. I downloaded and hit install. Then after a while it said there was an upgrade error, and to please try again. But it was going to have to download the 1+ GB OTA file again, so I just said screw it, i'll do it later. Here am I 2 days later with a broken phone. Thinking this has to be related.
Stock phone, locked bootloader. Running 6.0.1
GlorySy said:
Hello all,
Anybody can help me, my problem is that my nexus 6p stuck on google screen (boot-loop), noting that unfortunately the boot-loader is locked . I've tried different solutions but non of the worked.
What to do please???
Click to expand...
Click to collapse
busbeepbeep said:
I just started having this same issue.
I can't get into recovery from the bootloader in order to perform section 13. Once hit recovery, it's back to looping boot screen with white Google text.
Click to expand...
Click to collapse
Please join this thread to help troubleshoot.
I am hoping to collect enough data to figure out a solution for all effected.
is your BL locked and device encrypted?
When you try to load recovery, does it ask for password?
try entering your last google account email password if so.
Help!! Stuck in Google screen
Heisenberg said:
Go to my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 13 to adb sideload one of the full OTA zips.
Click to expand...
Click to collapse
Hi Heisenberg,
I ran into this problem today with my phone stuck on Google screen. I tried to use your guide and put my phone in recovery but it just goes back to rebooting and just shows the "Google" logo so if I can't get the phone into recovery then I won't be able to use your guide right? Is these any other way to solve this problem or am I screwed?
Also how can this problem be prevented in the future if I got new phone under warranty? Do I root and flash pure Nexus ROM and backup images?
Thanks,
Azeem00 said:
Hi Heisenberg,
I ran into this problem today with my phone stuck on Google screen. I tried to use your guide and put my phone in recovery but it just goes back to rebooting and just shows the "Google" logo so if I can't get the phone into recovery then I won't be able to use your guide right? Is these any other way to solve this problem or am I screwed?
Also how can this problem be prevented in the future if I got new phone under warranty? Do I root and flash pure Nexus ROM and backup images?
Thanks,
Click to expand...
Click to collapse
Hello... Try to look here:
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
For your second question, it's hard to tell... Making regular backups may help protecting your datas, but can't help your new phone to start acting crazy...
I have been doing weekly backups to my pc. I backup my TWRP, TBU, Super Backup, DCIM and download directories.
Sent from my Nexus 6P using XDA-Developers Legacy app
Heisenberg said:
Go to my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 13 to adb sideload one of the full OTA zips.
Click to expand...
Click to collapse
Any ideas are any solution when I have custom rom?
EDIT: Not needed, seems that wife phone has motherboard problem because now it will stuck in TWRP screen.
I am pretty sure I had this problem before. Actually within hours of purchasing and rooting. Lol go into fastboot and install factory images. If you were able to get into recovery you could use adb to oem unlock.. but that doesn't sound like an option.
My phone died last night in a bootloop death. Thankfully here in the UK we have a 2 year warranty so Huawei are taking it back. I mentioned "bootloop issue" and the tech guy stopped asking the standard stuff and just sent me a returns bag.
Try this:
https://forum.xda-developers.com/nexus-6p/general/confirmed-hardware-defects-nexus-6p-t3610405
Quickly enable bootloader unlocking, then follow the tutorials already known for 4-core recovery
Well I've now got a different phone back from Huawei as they told me they no longer have replacement motherboards available.
Sent from my MHA-L29 using Tapatalk
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was the first boot I expected a decently long wait, after about 25 minutes I followed the guide's instructions for Verizon since it did say some Verizon users were experiencing long first boot times. I took the battery out like it said, put it back in, then proceeded to fastboot boot2.img, like the guide said. After letting it sit for an hour this time, I got the idea that something was obviously wrong. After multiple attempts with no success I tried to fix it myself. So far I have learned that on the fastboot screen it says my bootloader is locked again, even after unlocking it. I have tried flashing TWRP as a recovery, just to at least have a recovery boot, that does not work either unfortunately. So as of right now, all I have is a v20 that has no OS, a locked bootloader, no way of booting recovery, I can fastboot with no ADB, and its virtually a paperweight. If anyone has a solution to at least get back to Stock, I would greatly appreciate it! Thanks!
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Did you get it fixed?
frome901 said:
Did you get it fixed?
Click to expand...
Click to collapse
He has not responded to my pm
What roms can we use with dirty santa root?
me2151 said:
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Click to expand...
Click to collapse
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
TheDantee said:
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
Click to expand...
Click to collapse
In his case we needed to redo from step 3.
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc) http://www.hardreset.info/devices/lg/lg-v20/
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Bricked T-Mobile v20
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was flash a new rom on it then i get boot loop with TWRP. so i decide to OEM LOCK again after that everything was stuck on my phone just boot loop with LG so any solutions please help me...... THx u for help me.
Kinda nerve wrecking to read about all these "bricked" phones popping up after trying this method lol.. Perhaps I'll just wait until a more tried and true way comes out...
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
For anyone that isnt on sprint that has "bricked" their phone. There are kdz's that will allow you to reflash back to 'stock". Someone had an issue with the kdz, but it was an easy fix. If you failed the process, it can be restored. Just if it doesnt want to boot, just lock and unlock the bootloader...
If your phone doesnt have a kdz, I know TeamDev is working on a custom kdz for such phones. Don't bug him if it isn't finished as I type this.
Anyone that can't get into TWRP, or has failed the process. Either start back at step 3, or if you have TWRP installed but can't get to it, the manual way to get into TWRP is a pain.
Keep your back cover off and hold the volume down button for ease. Now press the power button and as soon as you see an LG logo, let go and repress the power button. Its tricky.... If you get the corrupted screen, pop your battery out and put it back in quick and repress volume down and power. Usually if Im quick enough the first LG logo will hang a lot longer than usual and that gives me time to enter TWRP. A factory reset screen will pop up. Hit Yes twice.
Please help urgent
lcovel said:
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc)
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Click to expand...
Click to collapse
Please can u help ke unbrick mine i bought this mobile in my country its expensive and has no support. I have tried all tools but still getting the error model unknown please help sir
Jaistah said:
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
Click to expand...
Click to collapse
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
yuppicide said:
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
Click to expand...
Click to collapse
it means dirty santa root got a high posibility rate of bricking a device compared to other root methods for other devices and if you have no experience in bricking phones before then you're screwed if it happens to you
Actually, if you follow the directions, almost none of the problems create a true brick-- which means unrecoverable. For most of the cases, you might get a soft brick, meaning you have to back out, use a KDZ to repair it or reflash something else, or start over from scratch and try again-- but usually (maybe with some help from here) you can pull the phone back into a usable state.
I would hazard to guess for the vast majority the process works fine, maybe with a hiccup, but I've not seen many reports of a truly unrecoverable brick from this method. It's complicated, yes, and you need to be ready to read a LOT to understand what's going on, but it seems pretty difficult to end up with a $700 paperweight with this.
So i have been trying tonroot my sprint lg v20 and everytime i try and go to the phone on mobile terminal to enter id
Then enter the apply patch /system/bin/atd /storage/emulated/0/dirtysanta i get this message and i cant go to step 2 to boot into recovery
Any help would be appreciated: i have a sprint v20 and i wanted to know if i have to flash the stock sprint rom or can i just flash lineage rom following this guide? I have it running on AT&T and i want to keep it on AT&T...
can you please assist
Could you help out, please? I don't believe I have hard bricked my LG V20 H910. However, I have read and tried all of the unbrick info out. It seems my screw up is unique. I completed dirty Santa then went to flash a custom. in the boot between that. I get a black screen and cant do anything even download mode will not come up. My PC does make its usual noises when i connect or disconnect, but my phone does nothing.
Ok, I managed to brick mine too. It's a VS995, it was running stock 1AC. I used the LGUP tool to downgrade it to VS99512A, and then did Dirty Sanata and TWRP. After booting into TWRP I decided to try lineage OS with Android 8.0, I did not make a backup of the Stock ROM, which was very stupid. Lineage OS 15.1 flashed but I had no cell service so I panicked and instead of wiping it in TWRP and using the backup of stock I should have created, I just opened LGUP and tried to downgrade it back to stock VSS99512A. Well LGUP said it worked, but when it went to boot it would hang at the Verizon logo with 4 pastel dots. Device manager could see an ADB device and I could connect to it with ADB. So I did and read the logcat. I could see it was trying to update as part of the rollback, but it appeared that some components from Android 8x could not be "upgraded" to Andoird 7.x. There was a repeated error about failing to update SQLite instance version from 3 to 1.
The one feature that could fix this is if the refurbish function worked with any of the VS995 KDZ files we all have access to. But alas, none work instead we only get the upgrade function... or so I thought. Somewhere in my search for the past 2 weeks I found a modified LGUP https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
**Please be warned what I did was absolutely ****ing stupid, and it was sheer luck I didn't screw anything up.**
From what I can tell if you only flash ("LGUP Upgrade") the KDZ from the same model it never clears the partition it just adds to it. My problem was there was stuff from lineage OS 15 stuck on one of the partitions that was making the rollback to stock fail because it kept saying it couldn't update the SQLLite DB from 3 to 1. So no "upgrade" within LGUP would work because the upgrade function does not clear internal storage. But the link above is to a version someone modded so you can force a partition update from any KDZ onto the system. So I started playing around with forcing KDZs from other models onto my VS995, and I noticed when using the Partion DL function with non-VS995 KDZ files it would say something about the partition changing. All I can assume is that the partition layout is so different on each model and it forces LGUP to re-partition the storage.
**Again I state for the record this was stupid, and I'm only fortunate it worked.**
I forced Partion DL of H91510d_00_VTR_CA_OP_1110.kdz, then H990N10b_00_OPEN_HK_DS_OP_1017.kdz, then back to VS99512A_06_1114_ARB00.kdz, then when it booted it gave the Verizon hello, and moved on finally but the setting service kept crashing while it was trying to load the Secure Boot screen. So I yanked the battery and went into the boot menu and did the Factory Reset function, and it worked.
Lesson learned, always make a backup and don't be so hasty to use tools that aren't fully functional (LGUP).
Perhaps what I've done may help others, maybe I've found out how to reimage or unbrick our V20s. Or maybe I just got really stupid lucky.
I have a xperia c4 e5303, is a awesome device and 5-6 days ago i wanted to use xposed firmware to enable a fake gyroscope.
AND THE HELL STARTED.
I had the device rooted with custom recovery twrp when i was in lollipop 5.1, i installed the firmware for xposed and the phone was stucked in "android optimization", for hours. I restarded it sometimes but nothing, so i formatted my device and when i rebooted it, i was stucked in "sony" logo screen, some minutes ago i founded that my phone was totally empty.
c: *internal screaming*
I waited the next day, i downloaded the ftf of original marshmallow 6.0 firmware for sony xperia c4 and i installed it on my device, then everything worked perfectly luckely.
Easy peasy lemon squeezy, or not?
Some hours after i founded that i couldn't use the recovery mode!
I searched and searched and i founded that the problem could be the bootloader,so i used a sony official guide to unlock that.
I couldn't finished that guide becouse with any connection, on any computer, android sdk can't install his components(such as google usb driver, that are required for that method), and the program just install everytime the same package in loop. I tried aaaallll the method in the universe for that, i tried also to install once per once the zip files of the downloaded package but it was totally useless.
So i founded another method after some days of searching (with flashtool) and now my bootloader is fully unlocked, if i use flashtool to unlock the bootloader, it says that is unlocked and ask me if i want to relock it so i think now the bootloader unlock is done. FINALLY.
Then, i turned off the phone and started it by pressing the volume down+power botton, and all the device did was reboot himself repitetly until i release hard keys and when i do it the phone start automatically.
I think my device now reboot himself instead of going in recovery mode.
What can i do i am totally frustrated about this and i really don't want to buy a new device becouse i don't have a gyroscope. I love my xperia c4, i just don't know why i can't get the recovery mode back to install twrp, for rooting the device, for retry to get xposed virtual sensor and then finally enjoy my vr experience...
In the end, i have a Xperia C4 5303 with original Marshmallow 6.0 firmware installed, that can't go in recovery mode in any ways.
Pls someone help me..
no one?..
No one here know hot to save my smartphone?
update: now i can use fasboot and adb commands becouse i installed the drivers properly.
but i still can't flash a custom recovery to get the root..
asnachan said:
update: now i can use fasboot and adb commands becouse i installed the drivers properly.
but i still can't flash a custom recovery to get the root..
Click to expand...
Click to collapse
Digging through XDA (next time use the website's search bar, tee hee hee) I found this thread:
https://forum.xda-developers.com/xp.../bootloader-unlocked-custom-recovery-t3285521
Edit: I know it says C5 Ultra whatever but the thread says it also works with your model (C4 E5303 no?)
Before trying anything, I'd seriously recommend reading all eleven pages so you don't miss anything and end killing your phone (or back at square 1).
I'm not an expert on Android or anything (I personally have only owned 1 device — a first gen Moto G), but the method presented in the thread is very odd. Are all Xperia phones this weird?
Read carefully — some steps might be unnecessary (after all, you already unlocked your bootloader [maybe?])
P.S. you lost the recovery because by installing the original firmware it basically got erased (original firmware didn't have TWRP after all!)
P.S.S. you should create a backup once you get TWRP up and running, just in case.
I can't help you more than this because I do not own the device, so I cannot share ~personal wisdom~ with you (beyond recommending the Moto G series).
Good luck!
( And search the forums and threads before posting — that's an XDA rule! )
Sent from my Motorola Moto G using XDA Labs
thx
Bludwurst said:
Digging through XDA (next time use the website's search bar, tee hee hee) I found this thread:
https://forum.xda-developers.com/xp.../bootloader-unlocked-custom-recovery-t3285521
Edit: I know it says C5 Ultra whatever but the thread says it also works with your model (C4 E5303 no?)
Before trying anything, I'd seriously recommend reading all eleven pages so you don't miss anything and end killing your phone (or back at square 1).
I'm not an expert on Android or anything (I personally have only owned 1 device — a first gen Moto G), but the method presented in the thread is very odd. Are all Xperia phones this weird?
Read carefully — some steps might be unnecessary (after all, you already unlocked your bootloader [maybe?])
P.S. you lost the recovery because by installing the original firmware it basically got erased (original firmware didn't have TWRP after all!)
P.S.S. you should create a backup once you get TWRP up and running, just in case.
I can't help you more than this because I do not own the device, so I cannot share ~personal wisdom~ with you (beyond recommending the Moto G series).
Good luck!
( And search the forums and threads before posting — that's an XDA rule! )
Sent from my Motorola Moto G using XDA Labs
Click to expand...
Click to collapse
Thanks a lot for your time, but i am using that thread to root this, and i am stucked at the last point becouse i don't know what he means with:
"THIS IS IMPORTANT
The rom has
Code:
recovery.from.boot.p"
I did all the steps except for that, and i get no errors but when i try to boot in recovery the phone just stay on the logo and then after some minutes reboot himself and starts normally.
i already ask what the last point is in that thread
p.s.: i know i will not have twrp if i reinstall stock fw, but the point is that i don't have also the normal recovery, i can't access to that via adb or via hard keys..
asnachan said:
Thanks a lot for your time, but i am using that thread to root this, and i am stucked at the last point becouse i don't know what he means with:
"THIS IS IMPORTANT
The rom has
Code:
recovery.from.boot.p"
I did all the steps except for that, and i get no errors but when i try to boot in recovery the phone just stay on the logo and then after some minutes reboot himself and starts normally.
i already ask what the last point is in that thread
p.s.: i know i will not have twrp if i reinstall stock fw, but the point is that i don't have also the normal recovery, i can't access to that via adb or via hard keys..
Click to expand...
Click to collapse
Ah. You should've mentioned it (i.e. linked to the guide). Sorry sorry!
Read further down. The "recovery.from.boot.p" is this thing that overwrites TWRP with the stock recovery. Following the «THIS IS IMPORTANT» indication are instructions to get rid of the thing, and so being able to keep TWRP permanently.
You need that last step to succeed.
Sent from my Motorola Moto G using XDA Labs
in the other thread they said to me to roll back to 5.1 i am doing it now
nvm i got hard brick, the phone is dead and i can't enter in download mode....
asnachan said:
nvm i got hard brick, the phone is dead and i can't enter in download mode....
Click to expand...
Click to collapse
I'm very sorry to hear that ?
Sent from my Motorola Moto G using XDA Labs
Is fine, i had to buy another phone that is why is tarted to root the xperia.
just..i'm out from the world of rooting i think. i broke 2 devices 1 by flashing a original rom with sony original flashtool and 1 by installing a root with kigroot, and now on that i can't read the sim.
i wait until the world of rooting will be more stable and with more official custom roms...
RIP
So yeah, that's the title. Stupidly tried to force my US996 to take the Oreo update by flashing the stock recovery (while using a rooted system) and installing the OTA afterward (which results in an error). At this point I started screwing things up by flashing TWRP (using fastboot) immediately after that (without booting to the system again) and ended up in a loop as a result.
Screwed mine up even further later on by using a misc partition-wiping command (from here: https://forum.xda-developers.com/lg-g5/help/stuck-twrp-recovery-t3587077/post71796008#post71796008) and ended up locking the bootloader + making TWRP unusable. Now, only fastboot and download mode works, and I'm seriously out of idea at this point.
I guess there's not much that can be done, but any help would be appreciated.
Also I made a Reddit post about this before, if it helps: https://www.reddit.com/r/lgv20/comments/ac6apr/got_stuck_in_an_endless_twrp_bootloop_tried/
phamanhvu01 said:
So yeah, that's the title. Stupidly tried to force my US996 to take the Oreo update by flashing the stock recovery (while using a rooted system) and installing the OTA afterward (which results in an error). At this point I started screwing things up by flashing TWRP (using fastboot) immediately after that (without booting to the system again) and ended up in a loop as a result.
Screwed mine up even further later on by using a misc partition-wiping command (from here: https://forum.xda-developers.com/lg-g5/help/stuck-twrp-recovery-t3587077/post71796008#post71796008) and ended up locking the bootloader + making TWRP unusable. Now, only fastboot and download mode works, and I'm seriously out of idea at this point.
I guess there's not much that can be done, but any help would be appreciated.
Click to expand...
Click to collapse
Start over with lgup and the oreo.kdz
Theirs forum post on both of these here, search or look around
If you can get into download mode your phone is not bricked
Sent from my PH-1 using Tapatalk
clsA said:
Start over with lgup and the oreo.kdz
Theirs forum post on both of these here, search or look around
If you can get into download mode your phone is not bricked
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I've already tried that when I locked my bootloader accidentally, and just tried it once again - doesn't work. The phone still boots into the recovery, with the "no command" error like before. I suppose that the phone is still trying to initialize the OTA update process at this point.
If it helps, flashing using DL Partition didn't work either. Still more or less the same.
phamanhvu01 said:
I've already tried that when I locked my bootloader accidentally, and just tried it once again - doesn't work. The phone still boots into the recovery, with the "no command" error like before. I suppose that the phone is still trying to initialize the OTA update process at this point.
If it helps, flashing using DL Partition didn't work either. Still more or less the same.
Click to expand...
Click to collapse
I'm in exactly the same boat. Let me know if you figure anything out and I'll do the same. Really frustrating problem.
txenglan said:
I'm in exactly the same boat. Let me know if you figure anything out and I'll do the same. Really frustrating problem.
Click to expand...
Click to collapse
I have a potential solution for you. I'll PM you.
Have you guys tried to wipe data from recovery
Did this solution work? Can you share it?
txenglan said:
I have a potential solution for you. I'll PM you.
Click to expand...
Click to collapse
merrickville said:
Did this solution work? Can you share it?
Click to expand...
Click to collapse
Yes, what I did was religiously follow what was posted at:
https://www.reddit.com/r/lgv20/comments/8b0c44/quite_hard_bricked_what_can_i_do_now/
Try that and let me know what happens.
txenglan said:
Yes, what I did was religiously follow what was posted at:
https://www.reddit.com/r/lgv20/comments/8b0c44/quite_hard_bricked_what_can_i_do_now/
Try that and let me know what happens.
Click to expand...
Click to collapse
Already tried that. My issue is 'no command', I can boot into Download Mode, and I can flash H915, US996, they all flash if I choose the Partition DL.
No matter what I try, LGUP reports my phone as US996, even after successfully flashing H915.
I'm stuck at 'no command' (without a recovery cuz I tried to get to it) and US996 apparently.
merrickville said:
Already tried that. My issue is 'no command', I can boot into Download Mode, and I can flash H915, US996, they all flash if I choose the Partition DL.
No matter what I try, LGUP reports my phone as US996, even after successfully flashing H915.
I'm stuck at 'no command' (without a recovery cuz I tried to get to it) and US996 apparently.
Click to expand...
Click to collapse
Strange. For me, the only thing that solved the issue was to purposely flash the wrong KDZ. I don't recall which one it was exactly but that's definitely what the solution was. Flashing the right ones lead to what you are describing.
txenglan said:
Strange. For me, the only thing that solved the issue was to purposely flash the wrong KDZ. I don't recall which one it was exactly but that's definitely what the solution was. Flashing the right ones lead to what you are describing.
Click to expand...
Click to collapse
My Hardware the U.S. AT&T H910, so both the H915 & US996 are both the wrong KDZ's
Okay, I'm not relegating this to a paper weight just yet.
merrickville said:
My Hardware the U.S. AT&T H910, so both the H915 & US996 are both the wrong KDZ's
Okay, I'm not relegating this to a paper weight just yet.
Click to expand...
Click to collapse
Definitely don't throw it away just yet. I'm certain it can be salvaged. I even had to save mine using the test points and qfil at one point and I've been so close to throwing it away on so many occasions. It's basically impossible to brick these phones
I just went back and re-read that Reddit post by that guy. It's all coming back to me. I have the US996. His post was more inspiration if anything. I think what I did is download every single firmware I could find on lg-firmwares.com (both before and after the Oreo update) and went through them until I hit the "right" wrong one lol. It took me hours but I eventually got one that magically got the phone or of the bootloop so that I could tell move on to flashing something else.
I can't find it now, but I followed a post Reddit post like that, and I had to use a LGUP_Hxxxx.dll file, his instructions were for two others (which provided the DLL's for), so I stopped there, because of the missing DLL file that I can't find with a search>
My phone is stuck at US996 (even when I sucessfuly flash H915 back to it, LGUP still shows it as US99610f).
Do you think I can find a LGUP_US996.dll file anywhere? No. And this post looked promising for getting me out of the 'no command' fix I'm in.
Edit: Here is the what I tried, not Reddit, but here. But, no LGUP_US996.dll. LGUP_common.dll, no, that does not work either.
txenglan said:
Definitely don't throw it away just yet. I'm certain it can be salvaged. I even had to save mine using the test points and qfil at one point and I've been so close to throwing it away on so many occasions. It's basically impossible to brick these phones
I just went back and re-read that Reddit post by that guy. It's all coming back to me. I have the US996. His post was more inspiration if anything. I think what I did is download every single firmware I could find on lg-firmwares.com (both before and after the Oreo update) and went through them until I hit the "right" wrong one lol. It took me hours but I eventually got one that magically got the phone or of the bootloop so that I could tell move on to flashing something else.
Click to expand...
Click to collapse
txenglan said:
Definitely don't throw it away just yet. I'm certain it can be salvaged. I even had to save mine using the test points and qfil at one point and I've been so close to throwing it away on so many occasions. It's basically impossible to brick these phones
I just went back and re-read that Reddit post by that guy. It's all coming back to me. I have the US996. His post was more inspiration if anything. I think what I did is download every single firmware I could find on lg-firmwares.com (both before and after the Oreo update) and went through them until I hit the "right" wrong one lol. It took me hours but I eventually got one that magically got the phone or of the bootloop so that I could tell move on to flashing something else.
Click to expand...
Click to collapse
merrickville said:
I can't find it now, but I followed a post Reddit post like that, and I had to use a LGUP_Hxxxx.dll file, his instructions were for two others (which provided the DLL's for), so I stopped there, because of the missing DLL file that I can't find with a search>
My phone is stuck at US996 (even when I sucessfuly flash H915 back to it, LGUP still shows it as US99610f).
Do you think I can find a LGUP_US996.dll file anywhere? No. And this post looked promising for getting me out of the 'no command' fix I'm in.
Click to expand...
Click to collapse
A couple of things come to mind
First off their only one patched LGUP for the v20
it works for all versions but maybe the H918 or Sprint LS997 model.
Make sure you install it in C:\Program Files (x86)\LG Electronics\LGUP or it will either read the wrong model file (if you had a previous installation of LG UP), or it will not be able to find the model file at all.
Click to expand...
Click to collapse
After using the H915_10e.kdz you have to flash the Full H910 rom on the phone
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
your choices are the rooted 10r rom or the unrooted 10q Stock rom
I also posted a back to stock Oreo 20G rom here > https://www.androidfilehost.com/?fid=1322778262903991071
Be sure and use TWRP for Oreo to flash it
After flashing those be sure and Format Data / Clear Cache and reboot
Damn....getting the right dll was also part of what I did IIRC. It's too bad it was such a long time ago else I'd have a more clear recollection of the exact steps I took. All I can say for sure, is that if you don't give up, you'll eventually stumble on the right solution.
Thank you for the suggestions.
This is the sequence I just did again as per your suggestion.
Install Patched LGUP (Phone recognized as US996 cuz I flashed that a while ago)
Flashed: H91510e_00_VTR_CA_OP_1205.kdz
Phone reboots to 'no command', injured reclining robot 'quick flashing'
At this point, both adb and fastboot do not see any devices.
End of story. I'm unable to sideload or flash the *.zip files, factory reset, wipe cache, all these options are not available to me due to 'no command' and no access to recovery, adb nor fastboot.
No matter which KDZ I flash, I only get 'no command', and I can always go into download mode.
Thanks again for the tips. I'm sure something will happen.
clsA said:
A couple of things come to mind
First off their only one patched LGUP for the v20
it works for all versions but maybe the H918 or Sprint LS997 model.
After using the H915_10e.kdz you have to flash the Full H910 rom on the phone
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
your choices are the rooted 10r rom or the unrooted 10q Stock rom
I also posted a back to stock Oreo 20G rom here > https://www.androidfilehost.com/?fid=1322778262903991071
Be sure and use TWRP for Oreo to flash it
After flashing those be sure and Format Data / Clear Cache and reboot
Click to expand...
Click to collapse
merrickville said:
Thank you for the suggestions.
This is the sequence I just did again as per your suggestion.
Install Patched LGUP (Phone recognized as US996 cuz I flashed that a while ago)
Flashed: H91510e_00_VTR_CA_OP_1205.kdz
Phone reboots to 'no command', injured reclining robot 'quick flashing'
At this point, both adb and fastboot do not see any devices.
End of story. I'm unable to sideload or flash the *.zip files, factory reset, wipe cache, all these options are not available to me due to 'no command' and no access to recovery, adb nor fastboot.
No matter which KDZ I flash, I only get 'no command', and I can always go into download mode.
Thanks again for the tips. I'm sure something will happen.
Click to expand...
Click to collapse
I have never seen the screen or error you described. Having a total of 4 v20 I thought I had seen everything.. guess not
Sent from my ONEPLUS A6010 using Tapatalk
merrickville said:
Thank you for the suggestions.
This is the sequence I just did again as per your suggestion.
Install Patched LGUP (Phone recognized as US996 cuz I flashed that a while ago)
Flashed: H91510e_00_VTR_CA_OP_1205.kdz
Phone reboots to 'no command', injured reclining robot 'quick flashing'
At this point, both adb and fastboot do not see any devices.
End of story. I'm unable to sideload or flash the *.zip files, factory reset, wipe cache, all these options are not available to me due to 'no command' and no access to recovery, adb nor fastboot.
No matter which KDZ I flash, I only get 'no command', and I can always go into download mode.
Thanks again for the tips. I'm sure something will happen.
Click to expand...
Click to collapse
I wonder if this might work for you:
https://forum.xda-developers.com/v20/how-to/9008-test-t3855777/page13
It's an annoying process to have to go through but I revived mine when it was completely bricked (I couldn't even get as far as you because the phone wouldn't even turn on).
couple of thing that may help
No command screen is stock recovery being confused.
Try doing a factory reset using the volume - and power method (hold volume -, press power until the screen turns on, then tap power repeatedly until the menu appears)
Hey, this is my first post on this forums so excuse me if there are some issues with the way I'm posting.
I have a rooted Nothing Phone (1) at version 1.1.4 (EEA). I got notified about the update to 1.1.6 and of course I wanted to update.
I don't have much experience at phone tinkering and after searching I tried these steps to update my phone. Step 1 and 2 were succesfully done. On step 3 the Updater in settings gave an error saying it couldn't update. I was stupid enough to reboot my phone at this point. At first I thought it booted normally but after 30 seconds or so the phone freezed up, resulting in a soft reboot about a minute later. It's stuck in this loop.
[EDIT] Not actually stuck as I can still use the phone until it freezes and it doesn't freeze in bootloader or recovery
What I've already tried:
- sideloading the update manually via Recovery/ADB. threw an error.
- using fastboot to boot with the rooted image. I thought maybe there is something that is expecting root that is freezing up the phone. Phone still freezed up.
- sideloading the 1.1.6 full update package. threw an kinstalldeviceopenerror
I'm a bit out of ideas how to save my new device. Does anyone have any suggestions?
Make sure you have the right update for your device version.
Nothing Phone 1 update tracker: Here are all the official Nothing OS builds to download and install
We tracked down all the Nothing Phone 1 updates so you don't have to.
www.xda-developers.com
You can try to install a magisk patched boot img
b_5.4.147-qgki-g3e5c6bfc5f18
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
How to unbrick Nothing Phone 1 fastboot bootloop
Welcome to this unbrick tutorial NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours. I do not suggest following this tutorial if...
forum.xda-developers.com
You will loose all data un your phone doing this.
xtcislove said:
Make sure you have the right update for your device version.
Click to expand...
Click to collapse
In recovery I found out that I have the SKQ1.211230.001/1663771117 (1.1.4 global hotfix) version even though I'm on a European device. Is it okay to try to update to 1.1.5 and then 1.1.6 or will ik mess with any settings?
xtcislove said:
You can try to install a magisk patched boot img
b_5.4.147-qgki-g3e5c6bfc5f18
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Done. Didn't change anything except bring my root back. Phone still freezes up.
xtcislove said:
You will loose all data un your phone doing this.
Click to expand...
Click to collapse
Isn't available for this version from what I know and I wanna first get the region problem sorted out.
The thing I find weird here is. The problem started after turning off all magisk modules, and removing the patched boot file via magisk. I reset root and turned on all modules again and the phone still freezes up. I don't know where to search.
EDIT: While pulling /sdcard/ with ADB I found that the command still pulls data while the phone freezes which I find very weird
JDeVries said:
In recovery I found out that I have the SKQ1.211230.001/1663771117 (1.1.4 global hotfix) version even though I'm on a European device. Is it okay to try to update to 1.1.5 and then 1.1.6 or will ik mess with any settings?
Done. Didn't change anything except bring my root back. Phone still freezes up.
Isn't available for this version from what I know and I wanna first get the region problem sorted out.
The thing I find weird here is. The problem started after turning off all magisk modules, and removing the patched boot file via magisk. I reset root and turned on all modules again and the phone still freezes up. I don't know where to search.
EDIT: While pulling /sdcard/ with ADB I found that the command still pulls data while the phone freezes which I find very weird
Click to expand...
Click to collapse
I guess there is something mixed up in your phone.
Since you can use adb pull, simply backup everything and do a reset.
I backup my phone daily do Google Drive, which is maybe not the case for you. I would simply follow the unbrick tutorial and go back to 1.1.3 EEA (You need to flash the super.img first). This will give you a clean device again so you can exclude that the freezing is a hardware error.
There is only one thing you can try:
Flash flash boot 1.1.6 and vendor_boot 1.1.6 and adb sideload full 1.1.6 eea via recovery.
I would go back to EEA.
There was something mixed up. I couldn't fix by sideloading 1.1.6 via recovery. I factory reset my phone via recovery which fixed the freezing. Then I pushed the 1.1.6 EEA rom to /sdcard/ota and dialed *#*#682#*#*. Installed the update from there and everything works again!