Related
Hi guys,
I tried to update my Nexus 4 to 4.4 when Google pushed the update out for it yesterday, I forgot I had unlocked the phone (I don't have any custom ROMs on it, just SuperSU.)
Every time I try and power it on, the loading screen is endless, although I can hold power and volume down to enter recovery mode, nothing seems to be working.
I am a bit of a novice so any help or suggestions would be really appreciated!
Thanks.
The first few pages of the forum is littered with posts like this, i was in the same situation.
What i did was download the 4.3 rom from google, and flash /boot and /system onto the phone. I suspect the 4.4 rom would also work.
This got the phone booting without harming (most of) my data, but much of the UI was mangled and didnt work properly. I tried to backup my images over USB but it didnt work, you might have a better result. I also wanted to backup my SMS but they had all vanished.
I rebooted the phone to recovery (TWRP) and used adb to backup the sdcard (adb pull /sdcard sdcard) then did a full flash using the 4.4 rom downloaded from google and that got it working again. Then i reflashed the latest version of TWRP recovery and SuperSU.
Hope that helps.
That's really helpful, thanks! Is there ANY chance of a step-by-step? I'm a complete 'noob' probably a mistake to root in the first place :crying:
If you're busy don't worry, just don't want to **** things up more than I have haha.
Thanks, appreciate it.
GeorgeAmodio said:
That's really helpful, thanks! Is there ANY chance of a step-by-step? I'm a complete 'noob' probably a mistake to root in the first place :crying:
If you're busy don't worry, just don't want to **** things up more than I have haha.
Thanks, appreciate it.
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
gee2012 said:
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
Click to expand...
Click to collapse
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
arffrhn said:
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
Click to expand...
Click to collapse
Cheers guys, a lot more helpful than the bloke from Google. Will try it in the morning!
This will surely help
If somebody is facing boot loop after kitkat update on nexus 4 and no data backup can try to go to safe mode and backup their data. To goto safe mode on boot screen just keep pressing up and down volume button for some time phone will get into safe mode and can be backed up.
Hi,
It also happened to me, dont know if it is related to having ROOT or not, but i had to manually flash factory image (4.4) and it worked. I flashed everything except userimage.img but on first boot it took like 15 minutes to reboot and then all my personal data (photo, music...) was gone....
So just be cautious before upgrading!
Hi,
It also happened to me, dont know if it is related to having ROOT or not, but i had to manually flash factory image (4.4) and it worked. I flashed everything except userimage.img but on first boot it took like 15 minutes to reboot and then all my personal data (photo, music...) was gone....
So just be cautious before upgrading!
gee2012 said:
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
Click to expand...
Click to collapse
Yeah that is pretty much what I did to fix mine except that I did not flash the userdata (step 10 in chapter D) so that I would't loose my data.
arffrhn said:
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
Click to expand...
Click to collapse
What did you end up doing for your PC to detect your phone?
iamj00 said:
What did you end up doing for your PC to detect your phone?
Click to expand...
Click to collapse
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
arffrhn said:
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
Click to expand...
Click to collapse
I don't know what any of that means or how to do it...
iamj00 said:
I don't know what any of that means or how to do it...
Click to expand...
Click to collapse
This is sideload guide. And the is the rom I used to sideload before: Purity. After I had successfully booted into the system. I flashed 4.4 factory images using this awesome noob friendly guide for a clean kitkat update.
arffrhn said:
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
Click to expand...
Click to collapse
iamj00 said:
What did you end up doing for your PC to detect your phone?
Click to expand...
Click to collapse
Installing the driver. Refer to this thread http://forum.xda-developers.com/showthread.php?t=1992345
Boot to bootloader and connect to your PC, usually Windows will find the driver automatically
Hi all... I have an at&t d800 that was running stock, rooted, and using Xposed. I was at work when I noticed that it was on the recovery TWRP screen. Weird I thought as I didn't restart it. I was having no issues with it prior. When I tried to reboot to system, it went right back to bootscreen. So I did a complete wipe and tried a system restore to a nandroid stock backup. reboot continues to go to the TWRP home screen... anyone have suggestions? I have a feeling its going to take a factory restore of some sort, but wanted to see if anyone had any suggestions beforehand. I can turn it off and on, but cannot get past the recovery home screen.
Thanks...
mholmes05 said:
Hi all... I have an at&t d800 that was running stock, rooted, and using Xposed. I was at work when I noticed that it was on the recovery TWRP screen. Weird I thought as I didn't restart it. I was having no issues with it prior. When I tried to reboot to system, it went right back to bootscreen. So I did a complete wipe and tried a system restore to a nandroid stock backup. reboot continues to go to the TWRP home screen... anyone have suggestions? I have a feeling its going to take a factory restore of some sort, but wanted to see if anyone had any suggestions beforehand. I can turn it off and on, but cannot get past the recovery home screen.
Thanks...
Click to expand...
Click to collapse
try flashing another rom, if that doesnt work use the LG software from PC to recover
G1_enthusiast said:
try flashing another rom, if that doesnt work use the LG software from PC to recover
Click to expand...
Click to collapse
Yea that was the first thing I tried to do after the nandroid didn't work... still doesn't work. boots into recovery every time.
Didn't want to have to do the LG stock firmware but it looks like I'm going to have to... wish I knew what would've caused it to randomly do that. Wasn't playing with the phone or anything...
mholmes05 said:
Yea that was the first thing I tried to do after the nandroid didn't work... still doesn't work. boots into recovery every time.
Didn't want to have to do the LG stock firmware but it looks like I'm going to have to... wish I knew what would've caused it to randomly do that. Wasn't playing with the phone or anything...
Click to expand...
Click to collapse
Same thing happened to me, I rebooted and then noticed that the at&t update went through automatically without permission, popup said phone will reboot in 30 seconds, on reboot I am stuck on TWRP, every reboot is back to recovery screen.
Looking for a way now to get some kinda ROM on phone, at&t has really pissed me off.
ossito2012 said:
Same thing happened to me, I rebooted and then noticed that the at&t update went through automatically without permission, popup said phone will reboot in 30 seconds, on reboot I am stuck on TWRP, every reboot is back to recovery screen.
Looking for a way now to get some kinda ROM on phone, at&t has really pissed me off.
Click to expand...
Click to collapse
That's exactly what it is for me. Only they did the download while I was working. Bastards. I'm currently downloading the zip file from that link where we do the firmware reload and uproot and go back to stock... the host site is brutal... downloading at 115 kb/sec... once this is down I'll just stay unroot and get the update and move on for a bit. Wait until the kitkat alphas are in release mode.
I'll post with results when it's complete.
Man after reading Some of these horror stories I'm nervous about flashing twrp just got phone 2 days ago and I'm rooted with twrp ready to flash with flashify. I am brand new to this phone and Im not filmiliar with what some stuff you guys are talking about. I guess I should start with a lot if reading. Hope u guys fix your phone's..good luck.
Sent from my LG-D800 using xda app-developers app
I am currently hosed by this as well. Those bastards!
I can't even get to download mode to restore the stock tot file.
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
Can you guys get to download mode?
Barsky said:
I am currently hosed by this as well. Those bastards!
I can't even get to download mode to restore the stock tot file.
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
Can you guys get to download mode?
Click to expand...
Click to collapse
Can not get into download mode either, I tried sideload adb and was able to flash stock rom and I tried CleanROM 2.0, recovery bootloop anyways, I have a copy of backup lg g2 recovery from flashify but I have no idea how to flash that.
Starting to understand the main disadvantage to this phone when compared to Samsung and Nexus. Nexus 5 looking real good right about now.
wow. if they bricked our phones this will be the last business I ever do with att or lg. This is inexcusable.
Barsky said:
wow. if they bricked our phones this will be the last business I ever do with att or lg. This is inexcusable.
Click to expand...
Click to collapse
I can't get into download mode either.... This is surreal - Never had this issue before.. Am I without a phone right now? I can't do a damn thing here...
This seems malicious
I knew not to run the OTA - I chose to postpone or ignore the notice from AT&T -- it looks like they pushed it through without my OK and ended up bricking my phone.... can anyone verify a workaround to get into download mode??
I really hope there's a workaround here.... I can't belive that I would be the only one this happened to because I made no selection to run the OTA -- it pushed itself through without my authorization, so I gotta imagine it did the same to a lot of other people here.... Hoping for a response by morning.. Thanks!
Just to confirm some facts about this update....
Are you rooted?
Are you on a custom recovery. If so, twrp or cwm?
Barsky said:
Just to confirm some facts about this update....
Are you rooted?
Are you on a custom recovery. If so, twrp or cwm?
Click to expand...
Click to collapse
Rooted with latest twrp recovery. Cannot boot into download mode for the uproot post...
mholmes05 said:
Rooted with latest twrp recovery. Cannot boot into download mode for the uproot post...
Click to expand...
Click to collapse
Same. I have to believe cwm or twrp has no bearing on our situation. Hoping our very wise devs figure something out for us
mholmes05 said:
Rooted with latest twrp recovery. Cannot boot into download mode for the uproot post...
Click to expand...
Click to collapse
+1
This has happened to me also. With my s4 .att pushed update in middle of night and it messed my phone up. Anyhow after two days or so of arguing with att they agreed on a eairly upgrade replacement and I got brand new lg g2 instead of a refurbished s4 .so now I am learning about this phone and I just took the new update. I rooted and was getting ready to flash twrp threw via flashify but I think now im gunna chill with just being rooted until I get a chance to do a lot of reading I guess before I go flashing anything..
Sent from my LG-D800 using xda app-developers app
Isn't there something that could be froze to prevent OTA's from coming through?
EDIT: Also, what is the Software version for said update?
EDIT2: Nevermind, found that it's D80010o.. i'm still D80010d.
EDIT3: For those stuck in the bootloop, have you tried this? http://forum.xda-developers.com/showthread.php?t=2451696
Apparently the bastards will only allow you to decline downloading it up to 3 times at 4 hours per decline, then it 'automagically' downloads and installs itself.
I saw that info on the AT&T website for the LG G2 update, they are such asses.
I used Titanium Backup to search for 'update' and then froze that. That is the easiest way to fix it for now, but, will cost you some money to buy titanium backup. Other apps can probably freeze stuff too tho.
There are other apps/processes running in the background, but, the one I froze was the update after I d/l'd it to my phone, but, chose not to run it. Later on I will disable the rest of the BS on this phone so it won't be AT&T'ified.
There is a 'Cleantool' somebody here on XDA wrote that can run via ADB and remove all the AT&T crap, but, I wanted to make a nandroid backup of the configured initial setup before I start carving the turkey so to speak.
---------- Post added at 07:52 AM ---------- Previous post was at 07:50 AM ----------
btm fdr said:
EDIT3: For those stuck in the bootloop, have you tried this? http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
I'm not sure if that will work or not, my knowledge of Linux and the phones is too limited to say. It was however originally intended for Verizon phones as I'm sure you realize.
Just wanted to point that out so that nobody tries it and potentially messes up their D800 to a state that can't be fixed later on when hopefully some kind soul cleans up after AT&T flaming bag of dog poop they just left on our doorstep.
I recently bit off more way outside my realm by purchasing an LG G2 (verizon) off ebay that apparently already had Clockworkmod Recovery installed. I haven't done this rooting stuff before, but I figured this would be a good chance to start.
It seemed to have the stock rom on it as well, but I accidently click "yes" so some verizon update thing, and now it only boots up to the main screen of ClockWorkMod Recovery v6.0.4.4. I realize this was my first mistake.
So, I figured that I would install a custom rom, and I found the Gummy-2.1-12-30-13-NIGHTLY-vs980.zip as a good choice. I wiped all of the data and caches and begun. I did the install zip from sideload--> and followed the instructions with the "adb sideload <filename>" in windows command. It seemed to have installed correctly. The Gummy ASCII logo came up, as it said the kernal was flashed and installation was complete
However, when I reboot the system, it simply goes make to the main screen of the ClockworkMod Recovery screen. I have no idea what to do next. Any help would be very, very appreciated.
EDIT: I have progress with datechnerd's help.
First, I installed TWRP, which oddly enough CWM accepted an installiation of just fine. TWRP seems much better with more options.
Then I wiped all of the caches/system. Then I followed datechnerd as follows:
in twrp go to advanced
go to terminal
click select
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
afterwords try booting, if no boot go back to recovery and flash rom
The rom was the original Rom, not an altered one. Gummy now loads just fine.
Now my problem is that my sim card is not being recognized, but this is a great start at least. Thanks again.
ionvortex said:
I recently bit off more way outside my realm by purchasing an LG G2 (verizon) off ebay that apparently already had Clockworkmod Recovery installed. I haven't done this rooting stuff before, but I figured this would be a good chance to start.
It seemed to have the stock rom on it as well, but I accidently click "yes" so some verizon update thing, and now it only boots up to the main screen of ClockWorkMod Recovery v6.0.4.4. I realize this was my first mistake.
So, I figured that I would install a custom rom, and I found the Gummy-2.1-12-30-13-NIGHTLY-vs980.zip as a good choice. I wiped all of the data and caches and begun. I did the install zip from sideload--> and followed the instructions with the "adb sideload <filename>" in windows command. It seemed to have installed correctly. The Gummy ASCII logo came up, as it said the kernal was flashed and installation was complete
However, when I reboot the system, it simply goes make to the main screen of the ClockworkMod Recovery screen. I have no idea what to do next. Any help would be very, very appreciated.
Click to expand...
Click to collapse
try again? try a different rom? did you wipe system before flashing?
datechnerd said:
try again? try a different rom? did you wipe system before flashing?
Click to expand...
Click to collapse
Thanks for checking out this thread.
I have tried several time. With one rom, it would remain stock at the installing part. The Gummy Rom I have sideloaded several times, clearing the cache/data, etc between each time. Each time it says it is installed, but upon reboot it only goes back to CWM. I will try several other Roms, but I think I may either be messing up the process, or that the verizon update messed something up for me that I am unsure of
ionvortex said:
Thanks for checking out this thread.
I have tried several time. With one rom, it would remain stock at the installing part. The Gummy Rom I have sideloaded several times, clearing the cache/data, etc between each time. Each time it says it is installed, but upon reboot it only goes back to CWM. I will try several other Roms, but I think I may either be messing up the process, or that the verizon update messed something up for me that I am unsure of
Click to expand...
Click to collapse
sh*t it is the update... which rom do you want to use?
let me know and I'll throw a line in the rom to fix that for you
datechnerd said:
sh*t it is the update... which rom do you want to use?
let me know and I'll throw a line in the rom to fix that for you
Click to expand...
Click to collapse
Wow, that would be really nice of you. I'll use whichever ROM is the easiest for you to do this CM, ParanoidAndroid, whichever. The Team Gummy rom (Gummy-2.1-12-30-13-NIGHTLY-vs980) was one that seemed to at least in theory be loading on my device. Right now I just feel foolish like I've bricked my device, so anything that makes it usable would be really helpful.
ionvortex said:
Wow, that would be really nice of you. I'll use whichever ROM is the easiest for you to do this CM, ParanoidAndroid, whichever. The Team Gummy rom (Gummy-2.1-12-30-13-NIGHTLY-vs980) was one that seemed to at least in theory be loading on my device. Right now I just feel foolish like I've bricked my device, so anything that makes it usable would be really helpful.
Click to expand...
Click to collapse
alright im downloading the nightly gummy, says itll be an hour, then theres the time of the edit, then the time of the upload
hopefully I'll have it up before midnight central time
Sorry to hijack your thread, but I have a problem like this. I also accidentally got the Verizon software update before I rooted, and I'm trying to get the gummy lot last rom, but I am not even able to install the ROM. It gets to the end, and then says there is a Loki error. Any suggestions? Thanks.
datechnerd said:
alright im downloading the nightly gummy, says itll be an hour, then theres the time of the edit, then the time of the upload
hopefully I'll have it up before midnight central time
Click to expand...
Click to collapse
Damn, you've made quite an impression representing this community. I will stay and learn the ways of the wild.
Muffin man said:
Sorry to hijack your thread, but I have a problem like this. I also accidentally got the Verizon software update before I rooted, and I'm trying to get the gummy lot last rom, but I am not even able to install the ROM. It gets to the end, and then says there is a Loki error. Any suggestions? Thanks.
Click to expand...
Click to collapse
I have the Dec 28th nightly for 12b but I'll do Dec 30th here shortly
---------- Post added at 11:28 PM ---------- Previous post was at 11:27 PM ----------
ionvortex said:
Damn, you've made quite an impression representing this community. I will stay and learn the ways of the wild.
Click to expand...
Click to collapse
Yeah... I feel like I the g2 finally has the kind of support it needs with me here
datechnerd said:
I have the Dec 28th nightly for 12b but I'll do Dec 30th here shortly
Click to expand...
Click to collapse
Sweet! Thank you so much.
ionvortex said:
Damn, you've made quite an impression representing this community. I will stay and learn the ways of the wild.
Click to expand...
Click to collapse
here your fix http://www.mediafire.com/download/gcewqw5chc18tlt/Gummy-vs980.zip
hopefully, let me know if it doesn't work
ionvortex said:
Damn, you've made quite an impression representing this community. I will stay and learn the ways of the wild.
Click to expand...
Click to collapse
have to agree...
---------- Post added at 12:36 AM ---------- Previous post was at 12:35 AM ----------
datechnerd said:
alright im downloading the nightly gummy, says itll be an hour, then theres the time of the edit, then the time of the upload
hopefully I'll have it up before midnight central time
Click to expand...
Click to collapse
hey your awesome...We appreciate it..Hopefully they will hit the thanks button
datechnerd said:
[/url]
hopefully, let me know if it doesn't work
Click to expand...
Click to collapse
Thank you so much. It hasn't worked on my first try, but I will keep trying
During install:
E: Error in /tmp/update.zip
Status 6
Installation Aborted
ionvortex said:
Thank you so much. It hasn't worked on my first try, but I will keep trying
During install:
E: Error in /tmp/update.zip
Status 6
Installation Aborted
Click to expand...
Click to collapse
did you wipe cache, dalvik, and system before flash?
---------- Post added at 11:47 PM ---------- Previous post was at 11:45 PM ----------
Muffin man said:
Sweet! Thank you so much.
Click to expand...
Click to collapse
heres gummy nightly 12/30 for 12b
http://www.mediafire.com/download/2xe5cgf5k7kwj1r/Gummy-12-30-vs98012b.zip
datechnerd said:
did you wipe cache, dalvik, and system before flash?
Click to expand...
Click to collapse
Yes, I wiped all of those before doing the install. Maybe there is no turning back once someone clicks on the verizon update?
ionvortex said:
Yes, I wiped all of those before doing the install. Maybe there is no turning back once someone clicks on the verizon update?
Click to expand...
Click to collapse
there is i did it, but i had twrp so it was a lot easier
go to sideload again
but this time
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
if that works flash the rom that i didn't edit
datechnerd said:
there is i did it, but i had twrp so it was a lot easier
go to sideload again
but this time
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
if that works flash the rom that i didn't edit
Click to expand...
Click to collapse
I have been sideloading using the command prompt in windows with my device connected to my computer via USB. In CMR, when you click to "install zip from sideload," you can install a rom by simply writing "adb sideload <romhere.zip>". The above command that you have provided does not have any effect in windows command prompt/. I clearly have a lot of reading to do about this adb stuff, as there seems to be another way to load these roms. I apologize for being way out of my league with this stuff.
Edit: I wonder if it's possible for me to change over to TWRP. IT seems that is more stable and works with your "fix." Do you think the verizon update will prevent me from doing that as well?
ionvortex said:
I have been sideloading using the command prompt in windows with my device connected to my computer via USB. In CMR, when you click to "install zip from sideload," you can install a rom by simply writing "adb sideload <romhere.zip>". The above command that you have provided does not have any effect in windows command prompt/. I clearly have a lot of reading to do about this adb stuff, as there seems to be another way to load these roms. I apologize for being way out of my league with this stuff.
Edit: I wonder if it's possible for me to change over to TWRP. IT seems that is more stable and works with your "fix." Do you think the verizon update will prevent me from doing that as well?
Click to expand...
Click to collapse
You couldn't type
adb shell
Then the following two lines?
datechnerd said:
You couldn't type
adb shell
Then the following two lines?
Click to expand...
Click to collapse
Is that code for the command prompt in windows? adb shell says error: closed for me. I feel like I am just doing this all wrong
Edit: somehow, it let me switch over to TWRP. So I am going to figure out how that works, hoping it will work now. Thanks for your patience.
ionvortex said:
Is that code for the command prompt in windows? adb shell says error: closed for me. I feel like I am just doing this all wrong
Click to expand...
Click to collapse
Yeah...
http://techerrata.com/file/twrp2/g2vzw/openrecovery-twrp-2.6.3.3-g2vzw.zip
Try sideloading that
Hey there. I was wondering if anyone could help me out. I was running CM 13 on my Nexus 6P for a while but then I kept getting this message that said that there was something wrong internally and that I should contact the manufacturer. I just ignored it. I decided to download the latest nightly and try to freshly install it. I did a full wipe and installed the new CM13 nightly (7-1) and then gapps. When I tried booting the phone up it wouldnt go into the system. I went back into the recovery and tried installing a back up. I did that and tried booting up again into that restored backup and stilled didnt work. So I'm stuck right now with a non working phone. My bootloader is unlocked if that helps any.
XAL2 said:
Hey there. I was wondering if anyone could help me out. I was running CM 13 on my Nexus 6P for a while but then I kept getting this message that said that there was something wrong internally and that I should contact the manufacturer. I just ignored it. I decided to download the latest nightly and try to freshly install it. I did a full wipe and installed the new CM13 nightly (7-1) and then gapps. When I tried booting the phone up it wouldnt go into the system. I went back into the recovery and tried installing a back up. I did that and tried booting up again into that restored backup and stilled didnt work. So I'm stuck right now with a non working phone. My bootloader is unlocked if that helps any.
Click to expand...
Click to collapse
Have you tried flashing a factory IMG?
Sent from my Nexus 6P using XDA-Developers mobile app
XAL2 said:
Hey there. I was wondering if anyone could help me out. I was running CM 13 on my Nexus 6P for a while but then I kept getting this message that said that there was something wrong internally and that I should contact the manufacturer. I just ignored it. I decided to download the latest nightly and try to freshly install it. I did a full wipe and installed the new CM13 nightly (7-1) and then gapps. When I tried booting the phone up it wouldnt go into the system. I went back into the recovery and tried installing a back up. I did that and tried booting up again into that restored backup and stilled didnt work. So I'm stuck right now with a non working phone. My bootloader is unlocked if that helps any.
Click to expand...
Click to collapse
What options did you select when creating and restoring your backup? And, as above, have you tried flashing the factory images?
Heisenberg said:
What options did you select when creating and restoring your backup? And, as above, have you tried flashing the factory images?
Click to expand...
Click to collapse
I actually just did that. All is well. I was having trouble with fastboot commands because my phone wasnt being recognized but i just googled nexus 6p drivers installed them again and ran through the fastboot commands to get my phone back to stock.
XAL2 said:
I actually just did that. All is well. I was having trouble with fastboot commands because my phone wasnt being recognized but i just googled nexus 6p drivers installed them again and ran through the fastboot commands to get my phone back to stock.
Click to expand...
Click to collapse
Cool, glad you got it worked out. With your backup you may have selected the wrong options, have a look in my guide, there's a section dedicated to backups.
Heisenberg said:
Cool, glad you got it worked out. With your backup you may have selected the wrong options, have a look in my guide, there's a section dedicated to backups.
Click to expand...
Click to collapse
I actually have a question about that. When you say check vendor boxes are we supposed to check them both or just the vendor box and not the vendor image box to backup?
XAL2 said:
I actually have a question about that. When you say check vendor boxes are we supposed to check them both or just the vendor box and not the vendor image box to backup?
Click to expand...
Click to collapse
Only the ones that I mention, leave the system image and vendor image boxes alone.
Heisenberg said:
Cool, glad you got it worked out. With your backup you may have selected the wrong options, have a look in my guide, there's a section dedicated to backups.
Click to expand...
Click to collapse
Heisenberg said:
Only the ones that I mention, leave the system image and vendor image boxes alone.
Click to expand...
Click to collapse
Noted for sure. Thank you for your help. Oh hey can you answer one question for me though? When I was running CM13 how come I always got that alert that something internal was messed up and that I should contact my manufacturer? Also how come when I tried to do a clean install it wouldn't boot? Like that confuses me a lot because it was a clean install but I ran into problems.
XAL2 said:
Noted for sure. Thank you for your help. Oh hey can you answer one question for me though? When I was running CM13 how come I always got that alert that something internal was messed up and that I should contact my manufacturer? Also how come when I tried to do a clean install it wouldn't boot? Like that confuses me a lot because it was a clean install but I ran into problems.
Click to expand...
Click to collapse
Perhaps you had the wrong vendor image installed? Other than that I'm not sure. As for why the clean flash didn't boot I'm not sure either, there could be multiple causes for that so it's a bit hard to narrow down.
Heisenberg said:
Perhaps you had the wrong vendor image installed? Other than that I'm not sure. As for why the clean flash didn't boot I'm not sure either, there could be multiple causes for that so it's a bit hard to narrow down.
Click to expand...
Click to collapse
Oh man who knows. Thank you again though for the help and answering to quickly! Also thank you for that guide! Saved my phone's life. Lol
XAL2 said:
Oh man who knows. Thank you again though for the help and answering to quickly! Also thank you for that guide! Saved my phone's life. Lol
Click to expand...
Click to collapse
No probs, happy to help.
Hey everyone, I have a really frustrating problem, I am currently able to boot into TWRP via hardware method and ADB can see my device as well. However I have tried to install a stock system image through TWRP and I have also tried to install another TWRP backup that a user had posted in the Q&A forum. At one time I was able to successfully boot into the system but my device said encryption unsuccessful. After wiping the system partition and trying to install these images through TWRP I am still unable to boot into the system. Whenever I install them my phone will reboot into TWRP. I am at a loss as to what to do. If anyone has any ideas or suggestions I would appreciate it.
crazyc78 said:
Hey everyone, I have a really frustrating problem, I am currently able to boot into TWRP via hardware method and ADB can see my device as well. However I have tried to install a stock system image through TWRP and I have also tried to install another TWRP backup that a user had posted in the Q&A forum. At one time I was able to successfully boot into the system but my device said encryption unsuccessful. After wiping the system partition and trying to install these images through TWRP I am still unable to boot into the system. Whenever I install them my phone will reboot into TWRP. I am at a loss as to what to do. If anyone has any ideas or suggestions I would appreciate it.
Click to expand...
Click to collapse
I saw your other post in the other thread, but couldn't reply for some reason.. did you wipe the internal storage before restore?
Yes I did wipe the internal storage, I actually wiped everything the first time I tried to get everything in order and that was my original problem by wiping the system. I didn't realize that wiping internal storage would cause issues but that could have been one of the culprits. I think what finally solved my issue is I installed a deodexed rom and then powered down my device instead of rebooting and it booted up the rom. I had to flash SuperSU from a zip because for some reason the one that was preinstalled with that rom didn't install properly. So I installed the SuperSU zip and I am now officially rooted. Lesson learned DON'T WIPE SYSTEM OR INTERNAL STORAGE lol. I should have known better I have been rooting for awhile now, I just wasn't paying attention it happens to the best of us sometimes. Thanks for your help.
crazyc78 said:
Yes I did wipe the internal storage, I actually wiped everything the first time I tried to get everything in order and that was my original problem by wiping the system. I didn't realize that wiping internal storage would cause issues but that could have been one of the culprits. I think what finally solved my issue is I installed a deodexed rom and then powered down my device instead of rebooting and it booted up the rom. I had to flash SuperSU from a zip because for some reason the one that was preinstalled with that rom didn't install properly. So I installed the SuperSU zip and I am now officially rooted. Lesson learned DON'T WIPE SYSTEM OR INTERNAL STORAGE lol. I should have known better I have been rooting for awhile now, I just wasn't paying attention it happens to the best of us sometimes. Thanks for your help.
Click to expand...
Click to collapse
I've been rooting for a while myself but messed up I'm stuck in twrp and don't know how to get it the phone back on! your help would be glady appreciated .
ricosuave88 said:
I've been rooting for a while myself but messed up I'm stuck in twrp and don't know how to get it the phone back on! your help would be glady appreciated .
Click to expand...
Click to collapse
I used the deodexed ROM that is in the development forum. If I can upload it here I will if not just download it put it on your SD card and flash it. It may take a couple tries though I would suggest powering down your phone instead of rebooting it. Then turn it on and it should boot into the new rom. It's basically the same stock rom that our phone comes with. You may have to flash Chainfires SUPERSU zip that's in one of the threads. These steps should get you up and running again. Also if you can see your internal storage you're not encrypted. Hopefully that works for you. Let me know how it goes.
I wasnt able to upload the file from my phone. Just download it from here.
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423/page5
crazyc78 said:
I wasnt able to upload the file from my phone. Just download it from here.
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423/page5
Click to expand...
Click to collapse
Thanks for responding back. Man I'm still stuck in twrp I'm losing all hope at this point been at all day and can't figure out what Im doing wrong . I know you was stuck in the same situation did flashing that twrp back up help you out?
ricosuave88 said:
Thanks for responding back. Man I'm still stuck in twrp I'm losing all hope at this point been at all day and can't figure out what Im doing wrong . I know you was stuck in the same situation did flashing that twrp back up help you out?
Click to expand...
Click to collapse
Flashing the rom helped me out. It's a system image file. It's basically the stock rom for our device just deodexed. What exactly happened what did you wipe after your phone booted into
TWRP? If you still have TWRP you're not bricked. If you can flash that image from the thread I copied above then you should be good. You may have to flash SUPERSU to get root back. Also after you flash make sure you're not encrypted if you can see your internal storage partition then you're not encrypted.
crazyc78 said:
Flashing the rom helped me out. It's a system image file. It's basically the stock rom for our device just deodexed. What exactly happened what did you wipe after your phone booted into
TWRP? If you still have TWRP you're not bricked. If you can flash that image from the thread I copied above then you should be good. You may have to flash SUPERSU to get root back. Also after you flash make sure you're not encrypted if you can see your internal storage partition then you're not encrypted.
Click to expand...
Click to collapse
when I flashed the rom from your link above it just booted me into twrp again . I don't know what exactly I'm suppose to wipe. I can see internal storage tho so I guess that's a good sign but what's not good is that I can't use my phone :/ I've been rooting for years and can't seem to figure this one out.
ricosuave88 said:
when I flashed the rom from your link above it just booted me into twrp again . I don't know what exactly I'm suppose to wipe. I can see internal storage tho so I guess that's a good sign but what's not good is that I can't use my phone :/ I've been rooting for years and can't seem to figure this one out.
Click to expand...
Click to collapse
When you flashed the rom did you power the phone down and then try to boot into the rom? That's what I did and it worked for me. So don't select reboot into system, I'm not sure why it doesn't work that way. I had to power my device down and then boot into the room. Also if you can see your internal partition in TWRP then you should be good and encryption is not enabled. I know how frustrating this is. Just keep trying eventually that rom should stick.
crazyc78 said:
When you flashed the rom did you power the phone down and then try to boot into the rom? That's what I did and it worked for me. So don't select reboot into system, I'm not sure why it doesn't work that way. I had to power my device down and then boot into the room. Also if you can see your internal partition in TWRP then you should be good and encryption is not enabled. I know how frustrating this is. Just keep trying eventually that rom should stick.
Click to expand...
Click to collapse
Man, I have tried everything as well and I can't seem to get pass TWRP. Has anyone found a way around this problem? I have been looking around for an answer for 2 days and nothing has worked so far, any help will be greatly appriciated.
Thank you
kaiser10 said:
Man, I have tried everything as well and I can't seem to get pass TWRP. Has anyone found a way around this problem? I have been looking around for an answer for 2 days and nothing has worked so far, any help will be greatly appriciated.
Thank you
Click to expand...
Click to collapse
There a stock rom that I posted a link to a few posts back when I trying to help someone else. Download it put it on your SD card and install it. You don't need to wipe anything it will format things for you. After it installs don't reboot, power down the device and then turn it back on it should boot into the rom. That's what worked for me. I believe there was another way then what I just described it's in the same thread that I linked a few posts back. Good luck!!
crazyc78 said:
There a stock rom that I posted a link to a few posts back when I trying to help someone else. Download it put it on your SD card and install it. You don't need to wipe anything it will format things for you. After it installs don't reboot, power down the device and then turn it back on it should boot into the rom. That's what worked for me. I believe there was another way then what I just described it's in the same thread that I linked a few posts back. Good luck!!
Click to expand...
Click to collapse
Thanks for the help brother. However, it did not work for me. I flash the stock system, boot, turn device off and turn back on but I am still stock on TWRP. I will continue reading and hopefully I will find the answer soon.
thank you,:crying:
kaiser10 said:
Thanks for the help brother. However, it did not work for me. I flash the stock system, boot, turn device off and turn back on but I am still stock on TWRP. I will continue reading and hopefully I will find the answer soon.
thank you,:crying:
Click to expand...
Click to collapse
Np don't give up, I almost lost hope and then it worked for me.
Like I said there was another method that was discussed that worked for someone else. Try this thread, I know someone had the same issue that you and I had and they finally got it working.
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423
I'm here to the rescue! Follow this to the T! It worked for me! Let me know. http://forum.xda-developers.com/showthread.php?p=69685809
Sent by using the battery of my LG V20
im on the same boat as you. I am stuck in TWRP
tried all the methods i found so far and still stuck in twrp. i would greatly appreciate if someone can get me out of this bootloop!
hslayer said:
tried all the methods i found so far and still stuck in twrp. i would greatly appreciate if someone can get me out of this bootloop!
Click to expand...
Click to collapse
Same. Though I am on US996. Not sure what I did, was exploring some behind the scenes stuff using 'hidden codes' but didn't change any values as I didn't know what they meant in most cases. I rebooted my phone and it went straight to TWRP (3.0.2-1) and it will not boot past TWRP. Occasionally after I've flashed something, it will boot into TWRP and the screen will be unresponsive to touch so I have to pull the battery, but then it will be fine again.
I was in your position not to long ago, I'm currently working on getting a .kdz recovery file for the H918. My progress will continue on it later when finals are over.
netgar post 134
Restore H918 to 100% Stock (!!REQUIRES TWRP!!)