Related
Hey guys
I thought I'd just let you all know that my ambition to get 4.3 and lack of knowledge, led to my phone getting bricked today. I'm so devastated. I was following efrant's guide and flashed everything correctly and then as usual I lost half my storage and I followed the other guide to restoring the lost storage, once again i followed everything but i didn't get the storage back, then i did some cmd commands like the guide did. Next thing you know I may have done something wrong and I was at the bootloader screen and I couldn't reboot or go to recovery. Read and read nothing helped, called Google and they couldn't help me. I am now getting a replacement. SO there you go guys, just the greed of getting 4.3 caused me to brick my phone as well as my lack of knowledge I guess. Can't complain. Thought I'd share this with you all.
Div
P.S Moderators if this isn't suitable you guys can delete it no harsh feelings
Hey don't feel bad we all learn the hard way at some point. 4.3 is a minor update not worth it.
Sent from my Nexus 4 using Tapatalk 2
If you can still access bootlader just download the toolkit and download the 4.2.2 image and flash it back to stock via toolkit...
Sent from my Nexus 4 using Tapatalk 4 Beta
Just flash the stock android image again, after all you have access to the bootloader, everything is fine
teambestyrandy said:
If you can still access bootlader just download the toolkit and download the 4.2.2 image and flash it back to stock via toolkit...
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
fabrizziop said:
Just flash the stock android image again, after all you have access to the bootloader, everything is fine
Click to expand...
Click to collapse
This. You're totally not bricked.
Please follow the instructions in this thread:
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus⁴ using Tapatalk 4 Beta
Yeah, Nexus is hard to brick.
What is the best way to brick the Nexus 4? Maybe trying to flash HTC bootloader on it?
Fataldesain said:
Hey don't feel bad we all learn the hard way at some point. 4.3 is a minor update not worth it.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
it's totally worth it
nqk said:
Yeah, Nexus is hard to brick.
What is the best way to brick the Nexus 4? Maybe trying to flash HTC bootloader on it?
Click to expand...
Click to collapse
Perhaps
Code:
# dd if=/dev/zero of=/dev/block/mmcblk0
Thats not greedy, your just too excited for 4.3
teambestyrandy said:
If you can still access bootlader just download the toolkit and download the 4.2.2 image and flash it back to stock via toolkit...
Click to expand...
Click to collapse
So I tried doing this but, in the command prompt window that opens up with the toolkit when unrooting and going to stock it says
Archive not found recovery.sig
Archive not found system.sig etc.
and it fails....
Dvash27 said:
So I tried doing this but, in the command prompt window that opens up with the toolkit when unrooting and going to stock it says
Archive not found recovery.sig
Archive not found system.sig etc.
and it fails....
Click to expand...
Click to collapse
In this particular situation i wont recommend you using a toolkit. Is much esier with a good guide if it fails with the toolkit (btw while i flashed 4.3 factory image the cmd told me also about "missing recovery and system.sig" but now ive got a fully working 4.3 ROM on my N4.
You can do it via ADB. You just setup ADB on your computer. And put all the files from the factory image in the "platform-tools" adb folder. If your phone is in the bootloader menu and its recognized by your computer you just run a file that is called "flash-all.bat" and it should flash the 4.2/4.3 image on your phone. Thats how i did it a few hours ago.
Have a look at this guide: http://forum.xda-developers.com/showthread.php?t=1907796
But remember all the files in this guide are for the Nexus 7 so use the N4 factory images and the proper commands for your device (i mean the last step of this guide which shows various commands. you shouldnt use them becuz they are for the N7 and the proper commands for the N4 are written in the "flash-all.sh" use those commands or use the "flash-all.bat" which is included in the 4.3 factory image [i dont know if its included in the 4.2. f.i.]. All those files have to be in the "platform-tools" folder in order to let the .batch file do its job.
I hope u understood what i wrote. If not let me know.
miniAndroidian said:
In this particular situation i wont recommend you using a toolkit. Is much esier with a good guide if it fails with the toolkit (btw while i flashed 4.3 factory image the cmd told me also about "missing recovery and system.sig" but now ive got a fully working 4.3 ROM on my N4.
You can do it via ADB. You just setup ADB on your computer. And put all the files from the factory image in the "platform-tools" adb folder. If your phone is in the bootloader menu and its recognized by your computer you just run a file that is called "flash-all.bat" and it should flash the 4.2/4.3 image on your phone. Thats how i did it a few hours ago.
Have a look at this guide: http://forum.xda-developers.com/showthread.php?t=1907796
But remember all the files in this guide are for the Nexus 7 so use the N4 factory images and the proper commands for your device (i mean the last step of this guide which shows various commands. you shouldnt use them becuz they are for the N7 and the proper commands for the N4 are written in the "flash-all.sh" use those commands or use the "flash-all.bat" which is included in the 4.3 factory image [i dont know if its included in the 4.2. f.i.]. All those files have to be in the "platform-tools" folder in order to let the .batch file do its job.
I hope u understood what i wrote. If not let me know.
Click to expand...
Click to collapse
THANK YOU SO MUCH!!! It WORKED! I realised that I didn't flash the zip, I was flashing the the individual images in the zip and that wasn't working. THANK YOU, I couldn't even sleep knowing I potentially bricked my phone
Dvash27 said:
THANK YOU SO MUCH!!! It WORKED! I realised that I didn't flash the zip, I was flashing the the individual images in the zip and that wasn't working. THANK YOU, I couldn't even sleep knowing I potentially bricked my phone
Click to expand...
Click to collapse
Glad to know that it helped you mate
What about content on phone
I have also a phone that is dead after the upgrade. It was just "looping" on the "Updating Apps" screen, so I turned it off, now it won't start. When the "Nexus X" apperas, it just loops on this screen and nothing happens...
I would very much like to keep pictures and texts before resetting the phone! Can I do that in any way??
leiftorem said:
I have also a phone that is dead after the upgrade. It was just "looping" on the "Updating Apps" screen, so I turned it off, now it won't start. When the "Nexus X" apperas, it just loops on this screen and nothing happens...
I would very much like to keep pictures and texts before resetting the phone! Can I do that in any way??
Click to expand...
Click to collapse
Is your bootloader unlocked? Was your phone 100% stock before updating? How did you update? Can you reach bootloader by holding power and volume down button?
Sent from my Nexus⁴ using Tapatalk 4 Beta
TToivanen said:
Is your bootloader unlocked? Was your phone 100% stock before updating? How did you update? Can you reach bootloader by holding power and volume down button?
Sent from my Nexus⁴ using Tapatalk 4 Beta
Click to expand...
Click to collapse
My phone was stock, it is locked in all mathers I can reach the bootloader...
And I have ADB installed....
---------- Post added at 10:45 AM ---------- Previous post was at 09:46 AM ----------
leiftorem said:
My phone was stock, it is locked in all mathers I can reach the bootloader...
And I have ADB installed....
Click to expand...
Click to collapse
I can see my phone listet under "Advanced Utility, but I cannot seem to pull the files from my phone!
I am getting really frustrated here now!
Anyone??
leiftorem said:
I have also a phone that is dead after the upgrade. It was just "looping" on the "Updating Apps" screen, so I turned it off, now it won't start. When the "Nexus X" apperas, it just loops on this screen and nothing happens...
I would very much like to keep pictures and texts before resetting the phone! Can I do that in any way??
Click to expand...
Click to collapse
Flash ClockworkMod or TWRP and using one of them wipe cache, dalvik cache and data (not storage). Apps and settings will be gone, but your music and pictures will still be there.
Mr. Kostik said:
Flash ClockworkMod or TWRP and using one of them wipe cache, dalvik cache and data (not storage). Apps and settings will be gone, but your music and pictures will still be there.
Click to expand...
Click to collapse
This sounds GREAT! Where can I download them! And, will my texts be gone?? (That is not the worst thing, still annoying...)
leiftorem said:
This sounds GREAT! Where can I download them! And, will my texts be gone?? (That is not the worst thing, still annoying...)
Click to expand...
Click to collapse
Oh well you should look in one of those threads on how to root and so on, flashing a recovery using a toolkit should also work. Texts will be gone.
Or from this thread: http://forum.xda-developers.com/showthread.php?t=2010312
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
Click to expand...
Click to collapse
But at some point you'd need a custom recovery anyway.
I have a stock unrooted Nexus 4 that is caught in a bootloop after trying to install Android 4.3 from the OTA that was sent out. The phone was fully stock, nothing was done since it was pulled from the box and turned on.. So far I have done a cache wipe and factory reset via stock recovery and nothing worked. Any help trying to recover from this would be greatly appreciated.
I'm installing ADB on the new computer as I type this.
Thanks in advance for all the help.
I think you should flash the factory image following efrant's guide if a cache wipe doesnt help.
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
I think you should flash the factory image following efrant's guide if a cache wipe doesnt help.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I can't power the phone on to turn on debugging so ADB is not recognizing the device being attached to the computer. Any ideas?
ignitros said:
I can't power the phone on to turn on debugging so ADB is not recognizing the device being attached to the computer. Any ideas?
Click to expand...
Click to collapse
Follow this guide http://forum.xda-developers.com/showthread.php?t=2010312
You only need fastboot to work to return to stock
From my BLACKED OUT N4
spaceman860 said:
Follow this guide http://forum.xda-developers.com/showthread.php?t=2010312
You only need fastboot to work to return to stock
From my BLACKED OUT N4
Click to expand...
Click to collapse
I tried going through the guide but I still could not get ADB to recognize my device. As I am reading the guide it even says that I need to type in command fastboot devices to verify that my device is being recognized which it is not so I'm not sure what to do. I didn't get very far with Google tech support and the warranty replacement center wants to put a hold on my credit card for the amount of a new phone till mine gets returned. They won't just let me send mine in and then send me a new one which is ridiculous in my opinion. They are telling me that my only recourse is to send it to LG and have them fix it. Very frustrated with Google right now.
ignitros said:
I tried going through the guide but I still could not get ADB to recognize my device. As I am reading the guide it even says that I need to type in command fastboot devices to verify that my device is being recognized which it is not so I'm not sure what to do. I didn't get very far with Google tech support and the warranty replacement center wants to put a hold on my credit card for the amount of a new phone till mine gets returned. They won't just let me send mine in and then send me a new one which is ridiculous in my opinion. They are telling me that my only recourse is to send it to LG and have them fix it. Very frustrated with Google right now.
Click to expand...
Click to collapse
Download these drivers http://forum.xda-developers.com/showthread.php?t=199605 extract them get your phone in fastboot mode then open device manager on your PC plug in the cord and you should see it pop up in Device Manager cancel it from getting updating from the web and guided to go drivers you download it manually
From my BLACKED OUT N4
My sprint LG G2 was boot looping into TWRT after I accepted an OTA.
I've read several posts, http://forum.xda-developers.com/showthread.php?t=2477595 and this one http://forum.xda-developers.com/showthread.php?t=2448960,
the problem I get is I can not get into download mode, well, I did enter it, but it stuck at 0%, and my computer don't recognize it. Can not find the phone in "devices", installed the driver and still no avail. BTW, when I boot into TWRT, my computer can recognize the android device and ADB works then.
Since I cannot get past the download mode, I can not use the LG flash tool.. it says "LG USB/Parallel lock key is not detected".
Any suggestion is deeply appreciated.
Try this http://forum.xda-developers.com/showthread.php?t=2451696
[FIX] Installed TWRP and now you're stuck after OTA?
Sent from my LG-G2 using XDA Premium 4 mobile app
prking07 said:
Try this http://forum.xda-developers.com/showthread.php?t=2451696
[FIX] Installed TWRP and now you're stuck after OTA?
Sent from my LG-G2 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried, use ADB while the phone is in TWRT, went through and restarted, still boot into TWRT.
The command line in TWRT will pop up an error message saying "not enough space", although I do have enough space. So it didn't work either.
Sounds like you just need to keep messing with it until you can get it to recognize it in download mode and go back to stock. What Windows version do you have? i had some issues with 8 but 7 worked fine.
thenewak said:
Sounds like you just need to keep messing with it until you can get it to recognize it in download mode and go back to stock. What Windows version do you have? i had some issues with 8 but 7 worked fine.
Click to expand...
Click to collapse
I have Windows 7 64bit with all the latest patches.
Utahnewbie said:
I tried, use ADB while the phone is in TWRT, went through and restarted, still boot into TWRT.
The command line in TWRT will pop up an error message saying "not enough space", although I do have enough space. So it didn't work either.
Click to expand...
Click to collapse
Well, that Fix clear FOTA with zeros and it should end with "not enough space", this is normal.
I guess when your phone restarted into download mode and got stuck on 0%, it already overwrite maybe part of system partition, this is why only download or recovery works.
Did you made any nandroid backup before? If yes, restore at least boot & system from it. It should help, so you can boot normally. If you do not have any backup, well, maybe some other fellow Spring user can give u his boot & system backup files so you can restore them.
p.valenta said:
Well, that Fix clear FOTA with zeros and it should end with "not enough space", this is normal.
I guess when your phone restarted into download mode and got stuck on 0%, it already overwrite maybe part of system partition, this is why only download or recovery works.
Did you made any nandroid backup before? If yes, restore at least boot & system from it. It should help, so you can boot normally. If you do not have any backup, well, maybe some other fellow Spring user can give u his boot & system backup files so you can restore them.
Click to expand...
Click to collapse
Yes, I have a full nandroid backup before. I did a full restore from it after the boot-looping, but it didn't work, I still boot into TWRP and unable to boot into system.
Utahnewbie said:
Yes, I have a full nandroid backup before. I did a full restore from it after the boot-looping, but it didn't work, I still boot into TWRP and unable to boot into system.
Click to expand...
Click to collapse
so you followed that fix to clear FOTA, restored from backup, but when do "REBOOT SYTEM" from TWRP it ends again in recovery?
hmmm, how about these steps:
http://forum.xda-developers.com/showthread.php?t=2432476
using Flash Tool to restore stock ROM.
p.valenta said:
so you followed that fix to clear FOTA, restored from backup, but when do "REBOOT SYTEM" from TWRP it ends again in recovery?
hmmm, how about these steps:
http://forum.xda-developers.com/showthread.php?t=2432476
using Flash Tool to restore stock ROM.
Click to expand...
Click to collapse
No, it doesn't work, because my phone stuck at 0% in download mode and it doesn't show up in my device manager on PC.
I had the same problem
Utahnewbie said:
No, it doesn't work, because my phone stuck at 0% in download mode and it doesn't show up in my device manager on PC.
Click to expand...
Click to collapse
I used the fix from http://forum.xda-developers.com/showthread.php?t=2448960
except that I used the sprint .tot file. (http://storagecow.eu/index.php?dir=Xda/LG+G2/Stock/Sprint+LS980/)
Did you try to reinstall the drivers or use a different cable?
I encountered the same issue last night. I reinstalled the Verizon united drivers and rebooted my machine. The next time that I connected the device in download mode, device manager picked up the device. I had to re-run the LG tool, but it eventually progressed past 0% and my issue was fixed. You can reinstall the verizon drivers using the following link.
http://wacomalt.com/dropbox/LGG2/StockRevert/LG VZW_United_WHQL_v2.11.1.exe
I'm having the same issues with D802b after doing the 60mb OTA update. My phone didn't get a chance to actually do the download as on first restart it just went straight into TWRP and I haven't been able to get back since.
It's just looping back into TWRP each time. I've now completely wiped all parts of the phone including the internal SD card, I've even re-installed a new kernel and rom (The custom one I was using before this happened, from http://forum.xda-developers.com/showthread.php?t=2505682) from an attached USB (sd card reader) with successful installs through TWRP (including wiping cache etc), still reboots into TWRP on restart. I've also done a hard reset that was supposedly successful, still boots into TWRP.
Same as the OP, it won't 'install itself' properly in windows while in TWRP mode or in 'Software Download' mode (turn on with up and down buttons pressed down and plug data cable in). I've tried in vain to hunt down a specific D802 inf as pointing it at the universal driver didn't detect either.
I have installed the Android SDK, LG Suite, LG Universal drivers. I've then tried the B2CAppSetup (which works, but won't detect the device). I've then tried the FlashTool 1.0.54 and it gets all the way through but can't communicate with the device.
The only thing I haven't managed to do yet is to decompress the official kdz into a zip so I can flash it through TWRP. Haven't had much luck with LGExtract as of yet.
Rather baffled actually, as I'm sure the OP is.
Any thoughts?
---------- Post added at 08:55 PM ---------- Previous post was at 08:11 PM ----------
Having just posted all that above, I look further down the forum and someone linked to this thread below.
Fixed my issue, so I imagine it will sort yours out too.
http://forum.xda-developers.com/showthread.php?t=2451696
Update: I don't want to deal with this issue anymore.. just replaced it and got a new one
Utahnewbie said:
Update: I don't want to deal with this issue anymore.. just replaced it and got a new one
Click to expand...
Click to collapse
That is excellent, did they give you a hard time replacing it?
thenewak said:
That is excellent, did they give you a hard time replacing it?
Click to expand...
Click to collapse
No, because I microwaved it.
prking07 said:
Try this http://forum.xda-developers.com/showthread.php?t=2451696
[FIX] Installed TWRP and now you're stuck after OTA?
Sent from my LG-G2 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried that method many times and it does not work on the Sprint version. If you read through the thread you'll noticed that others with Sprint devices can not get that method to work.
The only method that worked for me was to use the LG Flash tool and flash the Sprint tot file and follow the instructions for the Verizion method for going back to stock.
---------- Post added at 01:41 AM ---------- Previous post was at 01:22 AM ----------
Utahnewbie said:
My sprint LG G2 was boot looping into TWRT after I accepted an OTA.
I've read several posts, http://forum.xda-developers.com/showthread.php?t=2477595 and this one http://forum.xda-developers.com/showthread.php?t=2448960,
the problem I get is I can not get into download mode, well, I did enter it, but it stuck at 0%, and my computer don't recognize it. Can not find the phone in "devices", installed the driver and still no avail. BTW, when I boot into TWRT, my computer can recognize the android device and ADB works then.
Since I cannot get past the download mode, I can not use the LG flash tool.. it says "LG USB/Parallel lock key is not detected".
Any suggestion is deeply appreciated.
Click to expand...
Click to collapse
Not really sure if this would've solve your problem but here's my possible theory to why you couldn't get it to work:
I was in the same situation. Took the OTA update and was boot looping into TWRP. Just like you, nothing in TWRP would fix it. I think you probably panicked and rush through the instructions and forgot some important steps. Make sure you did not install the Verizon driver by accident because that will cause problems with your Sprint phone not being properly detected by your computer. I did panicked and started to try to many things and somehow got a copy of the Verizon driver and installed it. ADB was able to see my phone but when I tried to sideload something through TWRP it would generate an error. I found out that I had both drivers(LG USB driver and the Verizon USB driver) installed and after removing the Verizon USB driver my computer was able to detect my phone properly. It's really important that after making any changes or installations of drivers you will need to reboot your PC to get the new changes to take effect.
You got the "LG USB/Parallel lock key is not detected" error is because you forgot to copy and overwrite the "MegaLock.dll" that's located at "C:\LG\LGFlashTool" directory.
To get into download mode you just need to press the +volume button only(do not hold or press the power button) and plug in the USB cable that's attached to your computer and Download Mode should come on. It will stay on 0% until the LG Flash tool flashes the Sprint stock rom onto the phone.
Once I got the phone to come up in Download Mode I had to go into Device Manager and find the device and then change the COM port to COM 41 then everything went smoothly as the instruction indicated. If you were not able to change the COM to COM 41 then it will never work.
If you're not sure that you have all the files then this is where I got mine from:
http://forum.xda-developers.com/showthread.php?t=2486738&page=7
or
http://forum.xda-developers.com/showpost.php?p=47849315&postcount=9
After I got the file above I followed the directions for the Verizon method below:
http://forum.xda-developers.com/showthread.php?t=2448960
Utahnewbie said:
No, because I microwaved it.
Click to expand...
Click to collapse
How long for? Thanks,
Sent from my Nexus 7 using Tapatalk
RedMist said:
How long for? Thanks,
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
four seconds
Utahnewbie said:
four seconds
Click to expand...
Click to collapse
That was enough to stop it booting? Cheers,
Sent from my Nexus 7 using Tapatalk
hey guys
I decided to flash back to stock today and recovered my backup but it wouldn't boot so I turned the tablet off and put it into it's bootloader and tried to flash a stock image but fastboot refuses to flash anything to the tablet at all :/ i can't at this point boot into anything any help?
I can for some reason put the userdata on and off but nothing else will flash onto the tablet :S
Check out the 2nd and third post here
http://forum.xda-developers.com/showthread.php?t=2670400
Also please write down all info from bootloader and input/output from terminal when running any commands
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Check out the 2nd and third post here
http://forum.xda-developers.com/showthread.php?t=2670400
Also please write down all info from bootloader and input/output from terminal when running any commands
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah I know all the commands and stuff and how it all works I've been using fastboot and adb etc since launch of the nexus 4. There's no output the commands just stop for instance when I use the flashall.bat from the factory images it wipes everything but won't put anything actually on the tablet it just hangs at the first sending and never finishes it just hangs there.
I've tried flashing the files manually swell but again they won't go on. The only thing that does finish is userdata.img but nothing else finishes going on the tablet at all turning on the tablet it vibrates twice and just boots onto the bootloader and nothing else opens not even the recovery
EDIT: Hooooly smeg it actually started working! it's alive again
Not trying to say you don't know, but the more information you give the better your help would be
Knowing what bootloader you have and if unlocked or not will help determine proper steps
Knowing the exact input/output can help as well as knowing the os you are using
Also if tab was working 100% before the attempt to return to stock, prior recovery and rom, any other issues you have had, etc
But its fine if you don't want to post this
Next steps would be
Make sure fastboot binaries on PC are up to date
Quality USB cable
Check md5sum for files you are to flash
If manually flashing stops at sending what happens when you manually erase?
What happens if you just try and boot a recovery through fastboot?
The more info you are willing to give the better your answers will be
Best of luck
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Not trying to say you don't know, but the more information you give the better your help would be
Knowing what bootloader you have and if unlocked or not will help determine proper steps
Knowing the exact input/output can help as well as knowing the os you are using
Also if tab was working 100% before the attempt to return to stock, prior recovery and rom, any other issues you have had, etc
But its fine if you don't want to post this
Next steps would be
Make sure fastboot binaries on PC are up to date
Quality USB cable
Check md5sum for files you are to flash
If manually flashing stops at sending what happens when you manually erase?
What happens if you just try and boot a recovery through fastboot?
The more info you are willing to give the better your answers will be
Best of luck
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh I apologize if I came across as being rude it wasn't my intention
It's all ok for some strange reason on the 50th odd attempt it finally started taking the data from fastboot. for some reason before hand when I tried manually the command would just sit there as "sending recovery" or whichever i tried and wouldn't move even waited 20 mins earlier just incase. i'm not sure at all what was happening there but now it's booted and fine
I need information, programs, files to boot up my new sweetheart, Elsa.
She is a tmobile h918 v20. I last saw her in Stock 10j then I rooted her on 2/2/17. We played around together for a bit and got disinterested with what we had.
We then decided to abandon Nougat 7.0 for Lineage v7.1.1 which went real good. Then I wanted to use gaps kernel which I flashed and put Elsa into a coma.
I did surgery on my dearest Elsa with TWRP resizing formating and wiping. Delvic/Art was a bane. So I brought out the heavy guns and used F2fs on him. For over an hour dalvik and twrp battled. As the battle raged on it looked as if twrp would win and dalvik submit.
The last 20 minutes I had to keep Elsa cool due to the raging fever produced within from the warring factions. Fearing the worst I pulled her battery... Nooo! I feared that Dalvik or Art used their Nuclear bomb in their defeat.
Booting Elsa into recovery with volume down+power I got back to Team twrp. Over and over I asked what happened... Please answer me... WAKE UP!!!
Twrp didn't wake up. It was just an image with no life left. That was the last time I seen team twrp.... I've tried all day to recall them back into service. Nothing... Cry cry...
Now I research. I believe that if I can produce a Bootable micro SD card I can use it to reanimate my sweetheart Elsa and we can frolic with Andy and all the wondrous realms.
Please help me... resurrect Elsa
I need files, instructions, links, programs.
twidledee said:
I need information, programs, files to boot up my new sweetheart, Elsa.
She is a tmobile h918 v20. I last saw her in Stock 10j then I rooted her on 2/2/17. We played around together for a bit and got disinterested with what we had.
We then decided to abandon Nougat 7.0 for Lineage v7.1.1 which went real good. Then I wanted to use gaps kernel which I flashed and put Elsa into a coma.
I did surgery on my dearest Elsa with TWRP resizing formating and wiping. Delvic/Art was a bane. So I brought out the heavy guns and used F2fs on him. For over an hour dalvik and twrp battled. As the battle raged on it looked as if twrp would win and dalvik submit.
The last 20 minutes I had to keep Elsa cool due to the raging fever produced within from the warring factions. Fearing the worst I pulled her battery... Nooo! I feared that Dalvik or Art used their Nuclear bomb in their defeat.
Booting Elsa into recovery with volume down+power I got back to Team twrp. Over and over I asked what happened... Please answer me... WAKE UP!!!
Twrp didn't wake up. It was just an image with no life left. That was the last time I seen team twrp.... I've tried all day to recall them back into service. Nothing... Cry cry...
Now I research. I believe that if I can produce a Bootable micro SD card I can use it to reanimate my sweetheart Elsa and we can frolic with Andy and all the wondrous realms.
Please help me... resurrect Elsa
I need files, instructions, links, programs.
Click to expand...
Click to collapse
Lol Well.. This turned out to be an interesting reading. What about fastboot? can you go into fastboot? does the phone even turns on at least?
jinkerz9430 said:
Lol Well.. This turned out to be an interesting reading. What about fastboot? can you go into fastboot? does the phone even turns on at least?
Click to expand...
Click to collapse
Hello.Hello
:silly:
She does turn on. There's 3 stages currently. A .001 (seconds)LG gif splash followed with the orange google boot (4 seconds) corruption warning ending with the Life's Good tm (hours). That's all. It will not advance any further.
It won't go back into twrp recovery except the initial showing I mentioned in my previous post. The Imei splash appears on que with the upvolume+power button.
I can't get to it with adb or fastboot.
Sent from my Samsung SM-G925T using XDA Labs
I have an idea on using Rufus to make a Bootable USB drive converting twrp, Nougat+ lg firmware+whatever with PowerIso, using ubuntu Linux as the os of the Bootable USB under fat32. Which Ive been tackling all day. _shrug
Sent from my Samsung SM-G925T using XDA Labs
twidledee said:
Hello.Hello
:silly:
She does turn on. There's 3 stages currently. A .001 (seconds)LG gif splash followed with the orange google boot (4 seconds) corruption warning ending with the Life's Good tm (hours). That's all. It will not advance any further.
It won't go back into twrp recovery except the initial showing I mentioned in my previous post. The Imei splash appears on que with the upvolume+power button.
I can't get to it with adb or fastboot.
Sent from my Samsung SM-G925T using XDA Labs
Click to expand...
Click to collapse
But here is my idea. You have done the process of rooting before already (which included going into fastboot mode) >> unless there is another way now. and also of pushing TWRP by using ADB. Now, if you can go into fastboot mode once again, that is: http://www.hardreset.info/devices/lg/lg-v20/fastboot-mode/ >> to make it easier to do, then you just have to repeat the steps to push the TWRP into the system once again and chances are somewhat high that it would fix the issue. If it doesnt, you wont lose anything.
jinkerz9430 said:
Lol Well.. This turned out to be an interesting reading. What about fastboot? can you go into fastboot? does the phone even turns on at least?
Click to expand...
Click to collapse
Oop. A video of it didnt post.
Sent from my Samsung SM-G925T using XDA Labs
twidledee said:
Oop. A video of it didnt post.
Sent from my Samsung SM-G925T using XDA Labs
Click to expand...
Click to collapse
I take it that the video (which is not posted) showed that you couldnt go into fastboot. right?
jinkerz9430 said:
I take it that the video (which is not posted) showed that you couldnt go into fastboot. right?
Click to expand...
Click to collapse
Well.... to shorten up the details lol yeah
Sent from my Samsung SM-G925T using XDA Labs
twidledee said:
Well.... to shorten up the details lol yeah
Sent from my Samsung SM-G925T using XDA Labs
Click to expand...
Click to collapse
so. You cant go into fastboot, recovery, nor download mode?
jinkerz9430 said:
so. You cant go into fastboot, recovery, nor download mode?
Click to expand...
Click to collapse
Correct
jinkerz9430 said:
But here is my idea. You have done the process of rooting before already (which included going into fastboot mode) >> unless there is another way now. and also of pushing TWRP by using ADB. Now, if you can go into fastboot mode once again, that is: http://www.hardreset.info/devices/lg/lg-v20/fastboot-mode/ >> to make it easier to do, then you just have to repeat the steps to push the TWRP into the system once again and chances are somewhat high that it would fix the issue. If it doesnt, you wont lose anything.
Click to expand...
Click to collapse
Omg OMG OMG...
I hadnt seen this previously.
I bow to you Good Sir
twidledee said:
Omg OMG OMG...
I hadnt seen this previously.
I bow to you Good Sir
Click to expand...
Click to collapse
I assume it did work out. Right? If so, glad to know the problem has been solved
jinkerz9430 said:
I assume it did work out. Right? If so, glad to know the problem has been solved
Click to expand...
Click to collapse
Thank you for the save. I been up all night actually unpacking 91810j kdz and reading.
So in fastboot in order for me to get those files into my i tried i did
fastboot flashall -p GENERIC_ANDROID_DEVICE /sdcard/ [twrp.img]
I pissed off adb and fastboot both who slammed the door on my face.
twidledee said:
Thank you for the save. I been up all night actually unpacking 91810j kdz and reading.
So in fastboot in order for me to get those files into my i tried i did
fastboot flashall -p GENERIC_ANDROID_DEVICE /sdcard/ [twrp.img]
I pissed off adb and fastboot both who slammed the door on my face.
Click to expand...
Click to collapse
DId it worked? when you pushed twrp.img , did it say wait for it to complete? and did it finish?
jinkerz9430 said:
DId it worked? when you pushed twrp.img , did it say wait for it to complete? and did it finish?
Click to expand...
Click to collapse
Adb wouldnt look at elsa.
Fastboot saw but push wouldnt work so i tried flashall, flash -p /sdcard
Spent majority of the time surfing and reading.
whats the a cmd on fastboot to push twrp.img in or is it twrp.zip?
twidledee said:
Adb wouldnt look at elsa.
Fastboot saw but push wouldnt work so i tried flashall, flash -p /sdcard
Spent majority of the time surfing and reading.
whats the a cmd on fastboot to push twrp.img in or is it twrp.zip?
Click to expand...
Click to collapse
wait. what method are you using? because i was refering to try from step 3 and beyond from jcadduono's thread to root the v20.
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
jinkerz9430 said:
wait. what method are you using? because i was refering to try from step 3 and beyond from jcadduono's thread to root the v20.
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Click to expand...
Click to collapse
Trying to get a adb to establish a connection with Elsa. Fastboot recognizes Elsa. Thats the only update right now.
Ill keep plugging in some prompts... oh well... adb knows that something is nearby and I just says unknown adb devices -l
twidledee said:
Trying to get a adb to establish a connection with Elsa. Fastboot recognizes Elsa. Thats the only update right now.
Ill keep plugging in some prompts... oh well... adb knows that something is nearby and I just says unknown adb devices -l
Click to expand...
Click to collapse
have you installed the lg v20 h918 driver on your computer? go to device manager and see if it is there. if it is not then install the lg v20 driver, then reboot your computer just in case, and see if then it does detects the driver. If you already have the drivers uninstall it and install it back again
jinkerz9430 said:
have you installed the lg v20 h918 driver on your computer? go to device manager and see if it is there. if it is not then install the lg v20 driver, then reboot your computer just in case, and see if then it does detects the driver. If you already have the drivers uninstall it and install it back again
Click to expand...
Click to collapse
I have the drivers on this pc.
jinkerz9430 said:
have you installed the lg v20 h918 driver on your computer? go to device manager and see if it is there. if it is not then install the lg v20 driver, then reboot your computer just in case, and see if then it does detects the driver. If you already have the drivers uninstall it and install it back again
Click to expand...
Click to collapse
Im literally having a panic attack....
Well I've played around with the drivers. Uninstalling reinstalling drivers... rebooting pc. Ive eradicated Lg completely Ugh hehe... im in allot of emotional turmoil? Yeah. Sigh
So android and google is the dominators.
Lets retract a bit ,!,
I root h918j stock with dirtycow method. I played around with overclocking and benchmarked really well. Got bored and wanted to see what 14.1 lineage 7.1.1
So I wiped 7.0. Flashed lineage and mistepped flashing gaps which looped me with my custom bootloading screen (i replaced tmos) Effed with the partioning, battled with delvik/art cache in ext4fs format with threw it into a formating loop.
Now phone boots into recovery. Only way in is with fastboot..
Ive tried
Fastboot flash -p /data twrp.img
/data twrp.zip
/data recovery.img
/data recovery.zip
/storage
/system
Im exhausted