Related
Hey guys,
Got a very weird problem here. I have previously flashed a CM10 nightly to my One X (international) and everything has been fine for around 3 weeks. Decided i wanted to try our the ViperX ROM. Previously upon flashing this ROM it just bootlooped but after another try with a slightly different method, i managed to get it to boot and all was merry. After titanium restore i rebooted, and this once again put me into a bootloop. Cannot get the ROM to boot. Why is this!!! Switched back to CM10. :good:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
BenPope said:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
Click to expand...
Click to collapse
Still doesnt boot man, im sure i flashed the boot image properly. This is the rundown of my flash process:
1: install from sd
2: in recovery, factory reset, wipe cache, wipe dalvic cache
3: Boot into fastboot and flash the boot.img
4: Reboot.
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
I also tried "fastboot erase cache" to no avail
In fastboot type fastboot erase cache
Jamekerr said:
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
Click to expand...
Click to collapse
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
eyosen said:
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Sorry forgot to mention I also used the "fast book erase cache" command.
As for titanium I restored all user apps and data and now that you mention it that could be the problem. I'll have another crack tomorrow and let you know.
Main reason I want to switch is I need much better battery life than CM10 but only temporarily. Can anyone recommend viperx as being a significant improvement?
BenPope said:
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
Click to expand...
Click to collapse
It comes up with "HTC" vibrates then the viper crawls across the screen and it stops at the "htcONE" logo.
Restored apps and app data and guess what. Still doesn't boot. WHY! Going to just try apps, no data at ALL. Will report back.
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
same issue
Hi i am also getting the same problem, i used the viper rom and others but it goes past the HTC logo looks as though it works but the lock ring is froze up and then it reboots itself over and over doing the same thing each time. Ive tried One_X_All-In-One_Kit_v1.2 and the manual CMD fastboot tutorial i dont know what to do to fix this, can anyone help me please?
EDIT* I seem to have it working now (fingers crossed), i used 'Nocturnal_Special_Edition_4.0_Odex' so thx to their good work that i now have a working rom for my phone phew
EDIT 20 MIN LAter* OK looks like i did something i shouldnt, it seemed to work, i made a change in the settings and then it rebooted and continued to reboot over and over so i tried installing a rom again and now it just stays at the htc quietly brilliant screen, what have i done this phone is now not so brilliant as its looking more and more that ive goosed it Any help apreciated.
boot.img
Help please
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
BenPope said:
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
Click to expand...
Click to collapse
If I restore apps only it does boot however any sort of data and it refuses to. Very annoying as I am not able to retain texts accounts etc. I have a feeling it's because I originally backed up on a jellybean ROM and the data just doesn't want to work on ics
Squbbe said:
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
Click to expand...
Click to collapse
Try the fast boot erase cache command and see if that solves the boot issue. If not make sure in recovery your have cleared cache partition performed a factory reset and also cleared the dalvik cache. Again if none of these work try re flashing the boot.img or perhaps try another rom that is known to be stable.
Okay, I searched before posting. Here is my steps.
I was on SKYNOTE 8.2 and wanted to go back to stock and see what At&t's update was about.
Once back to stock, I rooted my phone and have been on this setup for about 2 weeks.
I was in the original thread and saw the new 4.2.2 Collective AoCP / CM10.1 ROM.
I wanted to try it out.
Using TWRP's latest, followed all instructions and when rebooting it still has stock root ROM.
What am I doing wrong?
I thought it was TWRP so I went to an earlier ver, still no change.
I've tried 4 times now to flash this 4.2.2 Rom and nothing.
Factory Reset
Wiped Dalvik
Install Zip
Install gapps
It says to wipe cache and data again
then boot up
It boots up alright, right into my old phone.
Any input I can get is appreciated guys !!!! Thanks.
Copy the ROM to your device (some storage folder)
Boot directly to TWRP
Manually install the ROM and the appropriate GAPPS
(watch the script window and see what it says.. look for errors)
Clear caches and dalvik
reboot
LuckyColdJohnson said:
Okay, I searched before posting. Here is my steps.
I was on SKYNOTE 8.2 and wanted to go back to stock and see what At&t's update was about.
Once back to stock, I rooted my phone and have been on this setup for about 2 weeks.
I was in the original thread and saw the new 4.2.2 Collective AoCP / CM10.1 ROM.
I wanted to try it out.
Using TWRP's latest, followed all instructions and when rebooting it still has stock root ROM.
What am I doing wrong?
I thought it was TWRP so I went to an earlier ver, still no change.
I've tried 4 times now to flash this 4.2.2 Rom and nothing.
Factory Reset
Wiped Dalvik
Install Zip
Install gapps
It says to wipe cache and data again
then boot up
It boots up alright, right into my old phone.
Any input I can get is appreciated guys !!!! Thanks.
Click to expand...
Click to collapse
Try wiping cache/delvik cache, then factory reset twice, then system wipe twice, Install .zip, Install GApps, then wipe cache/delvik again(don't wipe data after .zip is installed. That's how I always do it and it works great.
I think its my recovery Twrp. I changed something.
adam_wingert said:
Try wiping cache/delvik cache, then factory reset twice, then system wipe twice, Install .zip, Install GApps, then wipe cache/delvik again(don't wipe data after .zip is installed. That's how I always do it and it works great.
Click to expand...
Click to collapse
I have tried everything. Its got to be the recovery. No matter what I do in twrp, nothing changes. It says updating partitions and stimulating actions
. It also says successful. After updating to the newest twrp it started this. I changed something. ##[email protected] went into settings and reset....nothing. What if I flashed CWM and then went back to TWRP.
LuckyColdJohnson said:
I have tried everything. Its got to be the recovery. No matter what I do in twrp, nothing changes. It says updating partitions and stimulating actions
. It also says successful. After updating to the newest twrp it started this. I changed something. ##[email protected] went into settings and reset....nothing. What if I flashed CWM and then went back to TWRP.
Click to expand...
Click to collapse
Try cf auto root to reinstall stock then reinstall twrp through odin
Sent from my GT-N7105 using xda premium
What have I done ?
Android The Greek said:
Try cf auto root to reinstall stock then reinstall twrp through odin
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Okay guys....This has made me sick to my stomach.....I have tried all the different methods. I even soft bricked my phone today using CWM.
Kies wouldnt even fix my phone.
I had to download stock firmware and flash via Odin to get back.
Installed TWRP
Rooted
Went into recovery and wiped everything again
Installed the custom ROM
Rebooted
TWRP didnt do anything even though it says it did.
My phone boots up like normal with Att logo and works but no Custom Rom and no wipes.
What is this? Im going to try other things but wow, this is crazy.
On my SD card I have alot of stuff. I also have a folder named TWRP, it has a back up in there. I wonder if I should remove that?
IDK,,,,,Stuck with Stock root for now. Help If you can. Never had this issue before. What a day
LuckyColdJohnson said:
Okay guys....This has made me sick to my stomach.....I have tried all the different methods. I even soft bricked my phone today using CWM.
Kies wouldnt even fix my phone.
I had to download stock firmware and flash via Odin to get back.
Installed TWRP
Rooted
Went into recovery and wiped everything again
Installed the custom ROM
Rebooted
TWRP didnt do anything even though it says it did.
My phone boots up like normal with Att logo and works but no Custom Rom and no wipes.
What is this? Im going to try other things but wow, this is crazy.
On my SD card I have alot of stuff. I also have a folder named TWRP, it has a back up in there. I wonder if I should remove that?
IDK,,,,,Stuck with Stock root for now. Help If you can. Never had this issue before. What a day
Click to expand...
Click to collapse
Might as well try everything. wipe your sd card in twrp,if that doesn't work reformat through android when booted. Then copy the custom rom over and try again. Only other thing I can think to try is to check that all partitions that are needed are mounted, or try CWM instead.
Also, how did you install TWRP? Through the app? that is the best way to do it, I have had problems flashing twrp through CWM or through the computer. If you aren't already, use goomanager to install it. TWRP has instructions on their website
I figured it out!!!!!!!
Doggydude said:
Might as well try everything. wipe your sd card in twrp,if that doesn't work reformat through android when booted. Then copy the custom rom over and try again. Only other thing I can think to try is to check that all partitions that are needed are mounted, or try CWM instead.
Also, how did you install TWRP? Through the app? that is the best way to do it, I have had problems flashing twrp through CWM or through the computer. If you aren't already, use goomanager to install it. TWRP has instructions on their website
Click to expand...
Click to collapse
It was the settings in TWRP. One of the boxes was checked. Sim actions for theming. I unchecked that and was on my way. Rocking The Collective AoCP now !!!!! Yes.....Thanks to all of you for your input. I'm going back to each and will hit thanks right now! Thanks again XDA members.
Lucky
I'm glad things worked out... isn't it amazing how attached we get to our toys
Sent from my GT-N7105 using Tapatalk 2
Hey All,
Here's a basic synopsis of my issue: I just flashed CyanogenMod on my Sprint LG G2. Now when it boots - or attempts to - it hangs on the CyanogenMod Splash Screen with the spinning cyan arrow.
Here's some more detail:
I've been trying for a few days to get this to work, and I'm finally stumped. I learned the hard way about the LS980ZVA radio and how it's not compatible with non-ZVA ROMs, and whatnot, and I've restored my phone using a .tot 3 times. This most recent time I used the LS980ZV8.tot to enable me to flash CM.
Here's what I did:
Restored phone to LS980ZV8 using LG Flash Tools
Rooted using ioroot
Checked Root
Installed FreeGee Free
Used FreeGee to install CWM 6.0.7.4
Rebooted to recovery
Made a backup
Copied backup to PC
Copied CM-11-20140708-SNAPSHOT-M8-ls980.zip to root of internal storage
Flashed said CM-11.zip from 'sdcard' (It was in sdcard/0/ for some reason)
Rebooted
Got stuck at CM screen.
Did some research on Google
Went back into CWM
Cleared cache
Reflashed CM-11.zip from sdcard
Rebooted System
Stuck at CM screen.
Posted on xda-developers
Any ideas? I can't figure this out for the life of me. I've read something about flashing the boot.img from fastboot, but I can't figure out how to get into the fastboot on the LG G2, and besides that was for an HTC. If you need more info, let me know.
=====Phone Details=====
Carrier: Sprint
Model: LG-LS980
Software: LS980ZV8
Recovery: CWM 6.0.7.4
Rooted: Yes, with ioroot
ROM: Attempted to flash CyanogenMod (cm-11-20140708-SNAPSHOT-M8-ls980.zip)
official.xian said:
Hey All,
Here's a basic synopsis of my issue: I just flashed CyanogenMod on my Sprint LG G2. Now when it boots - or attempts to - it hangs on the CyanogenMod Splash Screen with the spinning cyan arrow.
Here's some more detail:
I've been trying for a few days to get this to work, and I'm finally stumped. I learned the hard way about the LS980ZVA radio and how it's not compatible with non-ZVA ROMs, and whatnot, and I've restored my phone using a .tot 3 times. This most recent time I used the LS980ZV8.tot to enable me to flash CM.
Here's what I did:
Restored phone to LS980ZV8 using LG Flash Tools
Rooted using ioroot
Checked Root
Installed FreeGee Free
Used FreeGee to install CWM 6.0.7.4
Rebooted to recovery
Made a backup
Copied backup to PC
Copied CM-11-20140708-SNAPSHOT-M8-ls980.zip to root of internal storage
Flashed said CM-11.zip from 'sdcard' (It was in sdcard/0/ for some reason)
Rebooted
Got stuck at CM screen.
Did some research on Google
Went back into CWM
Cleared cache
Reflashed CM-11.zip from sdcard
Rebooted System
Stuck at CM screen.
Posted on xda-developers
Any ideas? I can't figure this out for the life of me. I've read something about flashing the boot.img from fastboot, but I can't figure out how to get into the fastboot on the LG G2, and besides that was for an HTC. If you need more info, let me know.
=====Phone Details=====
Carrier: Sprint
Model: LG-LS980
Software: LS980ZV8
Recovery: CWM 6.0.7.4
Rooted: Yes, with ioroot
ROM: Attempted to flash CyanogenMod (cm-11-20140708-SNAPSHOT-M8-ls980.zip)
Click to expand...
Click to collapse
Did you do a full wipe? I would recommend TWRP recovery over CWM. I've used both, but for this phone I prefer TWRP. There are numerous threads with details on how to install it. If you prefer CWM make sure to factory reset/ wipe data, wipe cache, wipe dalvik cache, then flash your rom. Manually shut down your phone then reboot. I've flashed cyanogen Roms on several different phones and they can be finicky. if you choose TWRP then you would do wipe-advanced wipe- check boot, system, data, dalvik, everything except Internal storage. In same recovery session flash your CM rom. Hope this helps. Oh and I would recommend making a backup in TWRP as well if you choose it.
shouldbeshroomin said:
Did you do a full wipe? I would recommend TWRP recovery over CWM. I've used both, but for this phone I prefer TWRP. There are numerous threads with details on how to install it. If you prefer CWM make sure to factory reset/ wipe data, wipe cache, wipe dalvik cache, then flash your rom. Manually shut down your phone then reboot. I've flashed cyanogen Roms on several different phones and they can be finicky. if you choose TWRP then you would do wipe-advanced wipe- check boot, system, data, dalvik, everything except Internal storage. In same recovery session flash your CM rom. Hope this helps. Oh and I would recommend making a backup in TWRP as well if you choose it.
Click to expand...
Click to collapse
No I didn't do a full wipe. I'll take your advice and flash TWRP. I've been out of the Android scene for a couple years and I've had more experience with CWM, didn't know how well recommended TWRP was. I'll flash TWRP, make a new Nandroid, then follow your instructions. Thanks. I'll report back.
shouldbeshroomin said:
Did you do a full wipe? I would recommend TWRP recovery over CWM. I've used both, but for this phone I prefer TWRP. There are numerous threads with details on how to install it. If you prefer CWM make sure to factory reset/ wipe data, wipe cache, wipe dalvik cache, then flash your rom. Manually shut down your phone then reboot. I've flashed cyanogen Roms on several different phones and they can be finicky. if you choose TWRP then you would do wipe-advanced wipe- check boot, system, data, dalvik, everything except Internal storage. In same recovery session flash your CM rom. Hope this helps. Oh and I would recommend making a backup in TWRP as well if you choose it.
Click to expand...
Click to collapse
Awesome!! Thanks so much!! I got TWRP and wiped as you said, then I flashed the CM. It worked!! Thanks!
official.xian said:
Awesome!! Thanks so much!! I got TWRP and wiped as you said, then I flashed the CM. It worked!! Thanks!
Click to expand...
Click to collapse
You are most welcome
I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again. I've tried reflashing PA, but it gave me a "E: failed to set up expected mounts for install; aborting".
OMGMatrix said:
I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again.
Click to expand...
Click to collapse
I don't think the recovery was "restored" / flashed to the boot partition but maybe try just in case. Flash the boot.img for Viper ROM and see if it stops the bootloop. After that you can make a clean wipe and install the ROM again, not restore but INSTALL. You surely have the ROM's .zip still?
Reason I suggested boot.img: i cannot get anything to restore with the h3g__001 backups keep getting recovery.emmc.win' is larger than target device '/dev/block/mmcblk0p42 error
mmcblk0p42 is the boot partition, so I don't know why TWRP tried to restore/flash a recovery to boot partition. He solved it by manually flashing boot.img after renaming.
if anyone gets this error heres how i solved it.change the boot.emmc.win to boot.img and it let me restore
Just a suggestion...
So this has been thoroughly confusing.
It seems that I had to clear the cache several times in PhilZ in order to resolve the first error. I tried to flash the original rom zip for Viper, but it still failed even though the "E: can't mount" messages weren't showing any more. However, I was able to re-flash the rom zip for PA, and upon booting, I found that Many of my apps were still there dispite the fact that they should have not been.
I then was able to reboot to recovery and flash the zip for Viper.
No clue what happened, but at least if anyone else has this problem, they'll be able to see how I fixed it
OMGMatrix said:
So this has been thoroughly confusing.
It seems that I had to clear the cache several times in PhilZ in order to resolve the first error. I tried to flash the original rom zip for Viper, but it still failed even though the "E: can't mount" messages weren't showing any more. However, I was able to re-flash the rom zip for PA, and upon booting, I found that Many of my apps were still there dispite the fact that they should have not been.
I then was able to reboot to recovery and flash the zip for Viper.
No clue what happened, but at least if anyone else has this problem, they'll be able to see how I fixed it
Click to expand...
Click to collapse
The apps will be there if you restored without making changes to the data partition which contains the your userdata. I've converted and changed over from International to Developer edition quite a few times now and not once in all those times did I lose my data, I just never restored the data partition.
Not sure if you have to actively choose whether to flash over data or not, I'm not that big into custom ROMs, only tried Viper ROM and even then I kept my original data.
OMGMatrix said:
I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again. I've tried reflashing PA, but it gave me a "E: failed to set up expected mounts for install; aborting".
Click to expand...
Click to collapse
Had that exact same issue as you. What version of twrp were you running when the issue started? Also, did you make any firmware upgrades or downgrades recently?
I ended up just running an RUU and starting over. I was able to adb pull all my files from internal sd card before i ran it.
mattprice86 said:
Had that exact same issue as you. What version of twrp were you running when the issue started? Also, did you make any firmware upgrades or downgrades recently?
Click to expand...
Click to collapse
I was using a version of TWRP that had been bundled with a previous version of Viper that was supposed to have been newer, but was actually 2.7.0.1. I updated to the newest (2.8.0.3) from the TWRP site through fastboot, but that didn't change anything. I had somewhat recently updated to the 3.xxx.xxx.7 firmware, but had flashed other roms since that without issue.
BerndM14 said:
The apps will be there if you restored without making changes to the data partition which contains the your userdata. I've converted and changed over from International to Developer edition quite a few times now and not once in all those times did I lose my data, I just never restored the data partition.
Click to expand...
Click to collapse
I did a factory reset (cache, Dalvik, data) before attempting the nandroid restore.
It looks like TWRP failed to actually do the reset in the first place, which caused it to get hung up thinking that the storage was actually being used.
OMGMatrix said:
I did a factory reset (cache, Dalvik, data) before attempting the nandroid restore.
It looks like TWRP failed to actually do the reset in the first place, which caused it to get hung up thinking that the storage was actually being used.
Click to expand...
Click to collapse
Doesn't matter mate, if you restore the data partition the backup that you made of data gets restored, period. It'll be another issue worth interest if you deselected "data" while doing the restore. As you clearly stated yourself, you did a factory reset(wipe all) BEFORE you did the nandroid restore(In which case you might have restored "Data" as well), in that case the factory reset doesn't matter at all. If you did it after you restored then, again, it's something different.
BerndM14 said:
Doesn't matter mate, if you restore the data partition the backup that you made of data gets restored, period. It'll be another issue worth interest if you deselected "data" while doing the restore. As you clearly stated yourself, you did a factory reset(wipe all) BEFORE you did the nandroid restore(In which case you might have restored "Data" as well), in that case the factory reset doesn't matter at all. If you did it after you restored then, again, it's something different.
Click to expand...
Click to collapse
I don't think you understand.
The restore never happened. It rebooted before anything happened when I told it to restore. Nothing got restored.
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
MiePx3 said:
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
Click to expand...
Click to collapse
Did you boot into recovery and do a factory reset in there. Sometimes that works.
jsgraphicart said:
Did you boot into recovery and do a factory reset in there. Sometimes that works.
Click to expand...
Click to collapse
Yep, every time I try to restore something I wipe everything. Also tried to lock and unlock the bootloader. No Luck.
Also tried wipe and erasing every partition possible, flashing an older 6.0.1 build.
Am I SOL? I tried anything google would give me....
Hey, I'm currently in the very same situation. Was on 6.0.1 stock rooted, applied 7.0 OTA using the beta program. Then for various reasons wanted to roll back to where I was with 6.0.1, but now the device just constantly reboots. I have wiped everything I can, tried to flash the factory images multiple times, but nothing seems to do the trick.
same problem here
i was on rooted android n preview 5 with twrp recovery and root, i applied 7.0 ota and then it bricked
now it starts up till bootscreen with the 4 coloured dots it freezes and goes in a bootloop but fastboot and recovery working fine
flashed a factory image wiped everything tried diffrent things restored a twrp backup but nothing
now im going to try to flash 7.0 ota again
Also in the same situation :crying:. Gets to the boot animation for 1 second then freezes and restarts.
Updated to 7.0 and got stuck in a bootloop.
Then tried restoring my TWRP backup to no avail.
Then tried flashing 6.0.1 factory image and still no luck.
Done factory resets, wiped system, data partitions etc, and still same problem.
If anyone has any other ideas that would be greatly appreciated!
this is what i tried so far
-wiped and restored 3 diffrent backups
-full wipe and flashed diffrent roms
-flashed factory image 6.0 and 6.0.1
-flashed 7.0 ota zip in twrp (extracted and flashed system.img and vendor.img )
-flashed factory image and used stock recovery to flash 7.0 ota.zip trough ADB sideload
i think im going to relock the bootloader and just send it back to google for a repair
I'm on the same situation
32 hours after updating to final 7.0 from stock dp5 the device turned off and stuck on boot animation
it seems like google did something wrong...
Looks like some people with the 6P are having the same issue as well. Still no fix either.
http://forum.xda-developers.com/nexus-6p/help/botched-nougat-install-phone-boot-loop-t3445709
I've had the same problem. I was coming from from a Pure Nexus install and thought i'd have a look at 7 so I made a full backup in TWRP then installed the lastest TWRP (twrp-3.0.2-1-bullhead). Then did a full wipe all bar internal storage and flashed radio/bootloader zip and Stock+ rom from the tupac4u thread which worked fine. Upon deciding there were a few dealbreakers for me I decided to go back to PN. So I booted back into TWRP, wiped again and restored the previously made backup. that's when I was getting the boot to 4 dots and reboot bootloop. I tried everything flashing various MM roms, and flashing 7 again, different roms / vendor images / full wipes including int storage, all via TWRP and ADB to no avail.
Though this evening I decided to go to an even earlier version of TWRP (twrp-3.0.0-1-bullhead) and try everything again. I flashed that and tried the repair filesystem on all the partitons I could, one of them gave an error I can't remember what it was. After doing that I did a full wipe and restored my PN backup, everything ticked. I then rebooted with everything crossed and it worked, it booted without any problems! (apart from the fact i'd forgot to remove the pin security before backing up so had to reflash anyway! which also worked). I can't be sure which part of that fixed it but if it helps anyone else that's great!
People with this problem - Does flashing new Factory Image 7.0.0 (NRD90M) fix something?
Just curious.
zeesyl said:
People with this problem - Does flashing new factory image 7.0.0 (NRD90M) fix something?
Just curious.
Click to expand...
Click to collapse
Nope, changed nothing in my case at least. At this point I'm just going to use the warranty card to get out of this mess, as nothing seems to revive the device.
MiePx3 said:
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
Click to expand...
Click to collapse
Type fastboot -w flash falsh vendor vendor.img then restore from your twrp backups
neaznc021 said:
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
this worked for me
neree said:
Nope, changed nothing in my case at least. At this point I'm just going to use the warranty card to get out of this mess, as nothing seems to revive the device.
Click to expand...
Click to collapse
Did that yesterday (With my N6P), will see what will come out of it. (Service guys said, that ''Oh, it's nothing serious, tomorrow (today) you will get your phone back (hopefully in working condition)''. I'm not so sure about that
(EDIT: Before I took my phone to warranty service, I flashed latest MM factory image and locked bootloader, maybe it was unnecessary, but I wanted to be sure, that phone looks fresh, maybe it was a big mistake.)
I had the same Bootloop issue, and it's all because of TWRP 3.0.2-1 !!! I have just reverted back to TWRP 3.0.2-0, and my backup restored just fine. There's no point for all that flashing. Just revert the TWRP.
Oh my... Guess what? My backup is corrupted...
Edit: maybe this can help, before bricking with full factory image, I flashed bootloader, radio, boot, vendor, system, Elementalx and supersu, wiped data and booted and work.
But I had problems with suspersu installed as systemless (it didn't work), so I flashed factory image. And bootlooped.
So, I'd say that what's causing issue is userdata, recovery or cache.