Related
My Tegra Note 7 came with Android 4.2. I unlocked, rooted, and installed CWM via the instructional videos over at rootjunky.com. Then through CWM I installed De-Odexed Stock Rooted 4.3plus from this thread: http://forum.xda-developers.com/showthread.php?t=2627671
Once the install finished and I rebooted the device (the reboot took maybe 30-45 seconds) I came to the setup "Welcome" screen. It is here that the Tegra Note froze. I thought it may be because it takes upwards of ten minutes for the first boot to complete/install but 30 minutes later the screen is still frozen.
When I do a hard reboot a few times I'm able to make it through the welcome and setup screens and the device appears to work just fine. I'll be able to install apps, run the stylus software, etc but then every 5 or 6 minutes (maybe shorter, maybe longer) the device freezes again and I must do another hard reboot. This happens repeatedly. And I still can't use the device for more than a few minutes.
Any ideas/suggestions?
onyxkhan said:
My Tegra Note 7 came with Android 4.2. I unlocked, rooted, and installed CWM via the instructional videos over at rootjunky.com. Then through CWM I installed De-Odexed Stock Rooted 4.3plus from this thread: http://forum.xda-developers.com/showthread.php?t=2627671
Once the install finished and I rebooted the device (the reboot took maybe 30-45 seconds) I came to the setup "Welcome" screen. It is here that the Tegra Note froze. I thought it may be because it takes upwards of ten minutes for the first boot to complete/install but 30 minutes later the screen is still frozen.
When I do a hard reboot a few times I'm able to make it through the welcome and setup screens and the device appears to work just fine. I'll be able to install apps, run the stylus software, etc but then every 5 or 6 minutes (maybe shorter, maybe longer) the device freezes again and I must do another hard reboot. This happens repeatedly. And I still can't use the device for more than a few minutes.
Any ideas/suggestions?
Click to expand...
Click to collapse
I am having the same issue my Tegra Note keeps freezing after flashing either update, I only did this because the ota update was not hitting but now the tablet is unusable
Fixed
RimanX said:
I am having the same issue my Tegra Note keeps freezing after flashing either update, I only did this because the ota update was not hitting but now the tablet is unusable
Click to expand...
Click to collapse
I was able to finally fix mine and stop the freezing and locking up. What I had to eventually do was reflash the stock 4.2.2 image, reflash the stock recovery and then update as usual OTA and now I have an updated EVGA TN7 fully functional. Thankfully this forum helped a lot by having the resources needed to fix the issue.
RimanX said:
I was able to finally fix mine and stop the freezing and locking up. What I had to eventually do was reflash the stock 4.2.2 image, reflash the stock recovery and then update as usual OTA and now I have an updated EVGA TN7 fully functional. Thankfully this forum helped a lot by having the resources needed to fix the issue.
Click to expand...
Click to collapse
How did you flash the 4.2.2 image and the stock recovery?
Freeje said:
How did you flash the 4.2.2 image and the stock recovery?
Click to expand...
Click to collapse
Have to get into the bootloader which for some reason mine is still just a blank black screen even though it says it's unlocked. I used a program called Quick Boot which is mentioned in one of the tut videos, it took a while because of the freezing but once I had it installed I used it to boot back into recovery and bootloader. I did this because the method of holding down power and vol up was not working.
I also noticed that as long as you are moving the screen around with your finger on any screen it would not lock up. I used this to transfer the stock image and recovery over from my computer using the usb.
Once in bootloader you use fastboot to flash. ex. fastboot flash recovery stock_recovery.img from the windows cmd prompt.
I had CWM recovery flashed when this first started so I used Quick Boot to go into recovery to flash the stock 4.2.2 image first to even see if it would help the freezing and once it did I went back and did the above to flash stock recovery so I could let the tablet update using OTA updates.
RimanX said:
Have to get into the bootloader which for some reason mine is still just a blank black screen even though it says it's unlocked. I used a program called Quick Boot which is mentioned in one of the tut videos, it took a while because of the freezing but once I had it installed I used it to boot back into recovery and bootloader. I did this because the method of holding down power and vol up was not working.
I also noticed that as long as you are moving the screen around with your finger on any screen it would not lock up. I used this to transfer the stock image and recovery over from my computer using the usb.
Once in bootloader you use fastboot to flash. ex. fastboot flash recovery stock_recovery.img from the windows cmd prompt.
I had CWM recovery flashed when this first started so I used Quick Boot to go into recovery to flash the stock 4.2.2 image first to even see if it would help the freezing and once it did I went back and did the above to flash stock recovery so I could let the tablet update using OTA updates.
Click to expand...
Click to collapse
From where did you get the 4.2.2 image that you can flash from stock recovery? I have a problem of getting the 4.3+ installed since I flashed the CWM recovery. I tried flashing a stock recovery but failed every time. My question is, would flashing an earlier ROM such 4.2.2 enable me to get the 4.3+ update or do I still have to flash a stock recovery?
Got the same error after flashing 4.3 or 4.4.2 manually (since OTA halts with an error).
How to get rid of it?
Thanks!
4.3/4.4 crash. I fixed mine finally! 4.4 working great, no crashing!
astuermer said:
Got the same error after flashing 4.3 or 4.4.2 manually (since OTA halts with an error).
How to get rid of it?
Thanks!
Click to expand...
Click to collapse
I had the exact same problem as you... I finally got it working, up to date with 4.4 CWM recovery, rooted and sd card fix. All working great... but here's some history...
I had the same bootloader that never worked from Power on/Vol Up, but would work after an adb reboot into fastboot. (blank screen only)
I was on stock 4.2.2, then unlocked bootloader, then updated to 4.4 using Supertool 2.2, Root, Sd card fix, but stock recovery still. All installed fine, but I had the crashing problem. Factory reset, and reinstall.. didn't solve the problem.
So I went back to 4.2.2 using the "temp" cwm recovery (using the root option to get in the cwm recovery, but I flashed the 4.2.2 file from root junky web page instead of rooting)
So here I was at 4.2.2 stock (from rootjunky web site), and stock recovery. Still not bootloader screen from Power.Vol up.
4.3 OTA would not work (dead droid with red triangle,error),
So I used supertool 1.5, installed CWM recovery, then I installed 4.3. It worked and rooted automatically, but I still got the crashing, and no bootloader by Power/VolUP. 4.4 OTA wouldn't work even when I put stock recovery back.
Here's where I got it to work from 4.3 stock (with crashing still happening, blank bootloader):
So now I used Supertool 2.2 to flash its version of CWM recovery (I had to keep touching the screen to keep it from crashing until CWM was installed and rebooted).
I did NOT use Supertool 2.2 to flash 4.4 as it contains the OTA 2.1 with it!!! (We don't want that yet! You'll se why below) I copied the 4.4 file at rootjunky: "Stock-4.4.2-TegraNote7.zip, February 22nd 2014 460 MB" onto the internal sd card (NOT the external sd card)
I used adb commands to reboot tablet into cwm recovery (had to keep touching screen until it rebooted into recovery so it wouldn't crash). Then I flashed the above 4.4 file. Install went fine. Of course I I still had crashing with 4.4 stock again. However, I noticed that the OTA 2.1 update appeared! I tried to update, but of course it wouldn't with CWM installed. So I reflashed recovery back to stock using supertool 2.2
Guess what happened next? The OTA 2.1 downloaded, flashed and worked! This was the first time I was ever able to get ANY OTA update to work! The key was to flash a stock 4.4 that didn't contain the OTA 2.1, and have stock recovery (from supertool 2.2) first in order to allow the OTA 2.1 to install!
Guess what works now? 4.4 works with NO CRASHING! and my bootloader finally works by holding Vol Up and Power ON and fully function menus,etc..!!! The tablet runs beautiful! The 4.4 had no root, or sd card fix applied, and stock recovery, but it DID lock the bootloader!
So now I used supertool 2.2 to unlock the bootloader (which I could now do because my bootloader had working menus, and could be accessed by Power/Vol Up). Keep in mind that this does a factory reset and wipes user data. (I had not wiped ANY user data right from 4.3 up until now!)
After the bootloader unlock/factory reset, I then used supertool 2.2 to: install CWM recovery, install root, install sd card fix.
Now I have an EVGA Tegra Note 7 with a fully functional bootloader, 4.4 Kit Kat, CWM recovery, root, sd card fix. All running great with NO crashing!
This is what worked for me... proceed with caution and know what your are doing first. Good luck!
4.4.2 Freezing- FIXED!
TerryRed said:
I had the exact same problem as you... I finally got it working, up to date with 4.4 CWM recovery, rooted and sd card fix. All working great... but here's some history...
I had the same bootloader that never worked from Power on/Vol Up, but would work after an adb reboot into fastboot. (blank screen only)
I was on stock 4.2.2, then unlocked bootloader, then updated to 4.4 using Supertool 2.2, Root, Sd card fix, but stock recovery still. All installed fine, but I had the crashing problem. Factory reset, and reinstall.. didn't solve the problem.
So I went back to 4.2.2 using the "temp" cwm recovery (using the root option to get in the cwm recovery, but I flashed the 4.2.2 file from root junky web page instead of rooting)
So here I was at 4.2.2 stock (from rootjunky web site), and stock recovery. Still not bootloader screen from Power.Vol up.
4.3 OTA would not work (dead droid with red triangle,error),
So I used supertool 1.5, installed CWM recovery, then I installed 4.3. It worked and rooted automatically, but I still got the crashing, and no bootloader by Power/VolUP. 4.4 OTA wouldn't work even when I put stock recovery back.
Here's where I got it to work from 4.3 stock (with crashing still happening, blank bootloader):
So now I used Supertool 2.2 to flash its version of CWM recovery (I had to keep touching the screen to keep it from crashing until CWM was installed and rebooted).
I did NOT use Supertool 2.2 to flash 4.4 as it contains the OTA 2.1 with it!!! (We don't want that yet! You'll se why below) I copied the 4.4 file at rootjunky: "Stock-4.4.2-TegraNote7.zip, February 22nd 2014 460 MB" onto the internal sd card (NOT the external sd card)
I used adb commands to reboot tablet into cwm recovery (had to keep touching screen until it rebooted into recovery so it wouldn't crash). Then I flashed the above 4.4 file. Install went fine. Of course I I still had crashing with 4.4 stock again. However, I noticed that the OTA 2.1 update appeared! I tried to update, but of course it wouldn't with CWM installed. So I reflashed recovery back to stock using supertool 2.2
Guess what happened next? The OTA 2.1 downloaded, flashed and worked! This was the first time I was ever able to get ANY OTA update to work! The key was to flash a stock 4.4 that didn't contain the OTA 2.1, and have stock recovery (from supertool 2.2) first in order to allow the OTA 2.1 to install!
Guess what works now? 4.4 works with NO CRASHING! and my bootloader finally works by holding Vol Up and Power ON and fully function menus,etc..!!! The tablet runs beautiful! The 4.4 had no root, or sd card fix applied, and stock recovery, but it DID lock the bootloader!
So now I used supertool 2.2 to unlock the bootloader (which I could now do because my bootloader had working menus, and could be accessed by Power/Vol Up). Keep in mind that this does a factory reset and wipes user data. (I had not wiped ANY user data right from 4.3 up until now!)
After the bootloader unlock/factory reset, I then used supertool 2.2 to: install CWM recovery, install root, install sd card fix.
Now I have an EVGA Tegra Note 7 with a fully functional bootloader, 4.4 Kit Kat, CWM recovery, root, sd card fix. All running great with NO crashing!
This is what worked for me... proceed with caution and know what your are doing first. Good luck!
Click to expand...
Click to collapse
@TerryRed:
You saved my bacon! I was having a similar issue with a totally borked root attempt... I was frustrated with repeated attempts to recover from the freezing issue. I followed your instructions and recovered the Tegra. Like you, I discovered that if I continually the device active by tapping and moving the screen, I could use the device. My idle limit was about 5 seconds, though.
In a nut shell, and while pretending to be a poor excuse for DJ 'scratching' (or do they call them 'controllerists' now?) I:
* Made sure ADB Debugging was enabled
* Copied the 'Stock-4.4.2-TegraNote7.zip' archive to the device's internal storage
* Ran SuperTool 2.2 and ONLY flashed the stock recovery
* Rebooted
[Resume silly DJ motions, while frantically setting up WIFI]
* Checked for, and downloaded the OTA update manually [OTA FOUND!!!]
* Waited the agonizing 10 second countdown for the device to initialize the installation
* Let Android do it's thing
!! SUCCESS !!
Thank you, and all of the guys here at XDA who donate their time, talent, and valuable info that help us mere muggles free our devices and take them to new heights.
I bricked my while trying to get back to 4.3 and I really hope that this will still help me after all I've already done. Wish me luck(
Bricked as well
OrangeCalculator said:
I bricked my while trying to get back to 4.3 and I really hope that this will still help me after all I've already done. Wish me luck(
Click to expand...
Click to collapse
So yours bricked as well???
I had the same problems:
- Bootloader not working as expected (only black screen).
- After CWM and flashed 4.3 constantly freezing.
- OTA not working (it said something like "This is not Tegra Note, it is Tegra Tab")
So being desperate I flashed a deodex 4.3 from RootJunky's web.
Since then tablet in boot-loop and still no way to get into Recovery.
I can only access APX mode, but I am not sure, how to use it.
Any help appreciated.
Jaro
NVflash unbricked
jardam.cz said:
So yours bricked as well???
I had the same problems:
- Bootloader not working as expected (only black screen).
- After CWM and flashed 4.3 constantly freezing.
- OTA not working (it said something like "This is not Tegra Note, it is Tegra Tab")
So being desperate I flashed a deodex 4.3 from RootJunky's web.
Since then tablet in boot-loop and still no way to get into Recovery.
I can only access APX mode, but I am not sure, how to use it.
Any help appreciated.
Jaro
Click to expand...
Click to collapse
So, to fix the boot loop it is as simple as it can be. I can't believe I didn't find that earlier. (BTW I didn't find a clear answer in the forum until today, thanks to hacktrix2006)
Just download the NVflash and the image mentioned in post #2 in following thread. Follow the instructions to switch tablet into APX mode, install the driver and start the flashing. Flawlessly done. No problem. Got rid of the Chinese OS (not supporting Google).
Really cool!
Just in case anyone still has these issues I'm going to post how I found a way to resolve them. I had all the problems mentioned in the previous posts and more besides. The inability to apply OTA updates, the device would freeze after 5 seconds of inactivity, endless boot loops, failed recovery partitions etc etc etc.
I tried a butt load of different solutions but none worked for me. What did work is described below. Others have already mentioned that Advent has a stock rom recovery utility, however, even after flashing that my problems still remained. So I downloaded the Advent stock recovery util and documentation and modified it slightly to the latest Android release for the Tegra Note 7.
Do as follows:
1 - Go here and download both the Advent Vega Tegra Note Factory Image (4.3) util and the documentation.
2 - Extract the Advent Factory Image zip file (as described in the documentation) somewhere on your pc.
3 - Inside the extracted folder you'll see a bunch of files. The three files we're interested in are the "recovery.img", "system.img" and "boot.img". Select all three and delete them.
4 - Now download the Tegra Super Tool utility here. At the time of this post the latest version is 2.5.
5 - Extract the downloaded Supertool to a new folder on your pc.
6 - Inside the extracted folder there are another bunch of files. Again, we're only interested in three of them. You're going to rename three of the files and use them to replace the three files you deleted earlier. At present their names are "4.4.2-2.5recovery.img", "4.4.2-2.5boot.img" and "4.4.2-2.5system.img.ext4". The filenames will obviously change as time goes by, but a little common sense goes a long way at this stage. So "4.4.2-2.5recovery.img" is renamed to "recovery.img", " 4.4.2-2.5boot.img" is renamed to "boot.img" and "4.4.2-2.5system.img.ext4" is renamed to "system.img". Once you've renamed them, copy them into the folder for the Advent Vega Tegra Note Factory Image which you extracted in step 2.
7 - Now go and read the documentation for the Advent Vega Tegra Note Factory Image util. Just take your time and follow it to the letter. It'll tell you how to put your Tegra Note 7 into it's APX mode, install windows drivers for it and begin the recovery of your device. It's mostly an automated procedure and fairly simple to follow as long as you follow the documentation.
This method brought my Tegra Note 7 back when it had several of the problems mentioned earlier in this thread, all at the same time.
Hope it helps someone.
My Nexus 4 was previously running 4.4.2 ... I had a modified kernel patch (done via an app and I can't remember the name of it) and it was rooted. On occasion I would pickup the phone just to find out it had shut down. I would reboot it and it would be fine for days. One day it got stuck on the boot animation. It just wouldn't pass that point. Then the battery died (I assume) so I plugged it in via USB to both wall and PC and it would not charge. I had to put in on my wireless charging pad and it charged right up .. but still would not pass the animation.
Since then I have individually flashed each file manually from the newest lolipop ROM. Tried the nexus toolkit including most of the 4.X.X stock ROMS. Did a format and erase. Booted Clockwork Recovery and installed 5.0 from sdcard. (I can access the sdcard via USB on CWM). I flashed the kernel, Radio and bootloader several times each. I tried the Cyan ROM 10.x too
After the second attempt installing 5.0 (using the toolkit) I did get "Android is upgrading ... Optimizing apps" then it hung on "starting apps" and the animation continued for hours. I have had no other success since then.
I am at a complete loss. So I turn to the experts in hope of salvation.
Any idea what I'm doing wrong or what else I should be doing?
Your emmc chip is fried.. Take the phone to a service center
Sent from my Nexus 4 using XDA Free mobile app
http://forum.xda-developers.com/showthread.php?t=2964619
Well, here's a new twist. I'm able to flash 4.2 and 4.2.2 with no problems .. but 4.3 OTA and even manual flash will reproduce the stuck on animated logo problem.
I installed a sensor app and it seems like all sensors are working fine.
I remember that I was using the franco kernel before my problems started. Maybe I have a botched kernel. But I have flashed it when I did all the ROMs did I not?
What is the earliest kernel version that is compatible with 4.3, 4.4 and 5.0?
Does anyone know why I can't flash beyond 4.2.2?
Is there a way to systematically test each .img to discover the problem?
Also, even though I have USB debugging enabled, I can't use ADB to sideload at all. I keep getting ADB was not found. I can use ADB without problems on my nexus 5.
bump
Same issue here. Could flash 4.2.2 and update with ota to 4.4.4, after that the boot animation stay's for more then an hour. Any idea how to solve this?
Just to share my own experience on similar issue..
my N4 was official Lollipop 5.0.1 unrooted & locked.
Unlocked & installed clockworkmod & latest official pa rom -> stuck in boot screen. (had done all resets etc )
full wipe & latest official CM nightly -> stuck in boot screen.
full wipe & installed full official google 4.4.4 image -> phone booted ok.
full wipe & install cwm & latest official pa rom (same as earlier) -> phone booted ok.
So my conclusion was that it had something to do with lollipop modem etc part, that didnt quite work with roms i tried to run.
BTW for some reason wasnt able to get adb sideload to work for me neither, so installed the factory images on fastboot / flash-all.bat
If you have a backup with USB debugging enabled, you could restore it and try to take a logcat while booting. This would make finding the culprit a lot easier.
My nexus player is running android 6.0. I rooted it to remap the key of the remote to get the menu button.
However, the device will get into recovery mode over night due to failed OTA update, which is quite annoying.
How can I update the OTA so my device will not stuck in TWRP?
thanks much.
ericliquid said:
My nexus player is running android 6.0. I rooted it to remap the key of the remote to get the menu button.
However, the device will get into recovery mode over night due to failed OTA update, which is quite annoying.
How can I update the OTA so my device will not stuck in TWRP?
thanks much.
Click to expand...
Click to collapse
You have to flash the stock recovery (because you are using TWRP) and system (because you are rooted) from the factory image. If the OTA detects any changes to the system or recovery, it will fail. So you can either flash those for the current version you have now, and install the OTA. OR, you can flash everything (EXCEPT userdata) from the new factory image (the one you're trying to update to) to update. Pick your poison. However, do note that you will have re-root and flash TWRP again after updating (only if you want to, of course ).
charesa39 said:
You have to flash the stock recovery (because you are using TWRP) and system (because you are rooted) from the factory image. If the OTA detects any changes to the system or recovery, it will fail. So you can either flash those for the current version you have now, and install the OTA. OR, you can flash everything (EXCEPT userdata) from the new factory image (the one you're trying to update to) to update. Pick your poison. However, do note that you will have re-root and flash TWRP again after updating (only if you want to, of course ).
Click to expand...
Click to collapse
Hi, where do i get the latest factory image for nexus player? (the one that fixes the gray colors because of hardware decoders problems)
Also, how can i flash that factory image EXCEPT userdata? (i dont want to lose all my apps/games)
Im new to nexux player and Nexus family (i work with samsung and they use odin, its easier)
Thanks!
Bruno_Tec said:
Hi, where do i get the latest factory image for nexus player? (the one that fixes the gray colors because of hardware decoders problems)
Also, how can i flash that factory image EXCEPT userdata? (i dont want to lose all my apps/games)
Im new to nexux player and Nexus family (i work with samsung and they use odin, its easier)
Thanks!
Click to expand...
Click to collapse
Googling "Nexus factory images" will bring this link to the top of the search results: https://developers.google.com/android/nexus/images?hl=en#fugu.
The latest 6.0.1 build is on the bottom of that list (MMB29T) for Fugu. Since your player is rooted with a custom recovery, I'm assuming you're all set up with ADB/Fastboot.
You can follow Method 2 from this OP to flash the individual partitions (It's from the Nexus 6P forums, but all Nexus devices are virtually similar): http://forum.xda-developers.com/nexus-6p/general/tutorial-how-to-flash-factory-image-t3252931
Obviously, the factory image for the Nexus Player doesn't have all the same partitions as the Nexus 6P, so just flash the partitions that are in your factory image. I forget the factory image for the Nexus Player doesn't even contain the userdata image file, so you should be okay flashing the others one by one. As the last step, I would run "fastboot format cache". Then, reboot, and you should be good to go.
On a side not, I'm actually in the opposite camp as you. I use nothing but Nexus devices exclusively because they are so simple to tinker with. I've used Odin in the past on a couple Galaxy Notes, but wasn't a fan. Then again, I'm not a huge fan of toolkits either, so...
Hi everyone,
Got my 6P a few days ago. First thing I did was unlock the bootloader, flash the MTC20F image and get on with my day. Now I didn't flash the userdata file because well.. I just didn't.
Anyway, with every reboot now, I get the message about your device software can not be checked for corruption and it says to re lock my bootloader. Phone works fine though. I've left the BL unlocked.
Decided to venture into the world of Android N, enrolled my device into the beta program. OTA notification came. I hit restart and install. After 'Processing the update package', it rebooted into recovery and showed the green android guy with 'error' written underneath him.
Recovery log showed:
E: Failed to Map file
installation aborted
So I rebooted and I'm still in MM (obviously), and nothing happened except a huge waste of my time. This didn't happen on my Nexus 6 when I enrolled for Android N DP1 and it received and installed the OTA with an unlocked bootloader.
So what's up with this? Any ideas?
Is there a way I can get my hands on the NPD90G OTA and sideload through stock recovery without losing my data?
All replies will be appreciated.
Sent from my Nexus 6P
I have not tried yet but I would use Nexus Root Toolkit. Choose flash stock / unroot. In the workflow underneath where you choose the factory image there is a check box in Setttings for "No Wipe Mode". I would read up a bit and see if this grenades the install from 6 -> 7 but it is a good place to start.
Hi everybody,
I want to try some battery friendly rom based on android Marshamallow and currently I am on stock oreo.. The issue is I cant install android 6.0 and encounter error while flashing boot image in fastboot..
Can I directly flash 6.0 based rom through twrp on oreo?
And while I was doing this I wasnt even able to flash 8.0 boot img as well while I was able to install it through twrp..
Sorry If the question is not proper or I am unable to explain it properly
To be precise it gives fastboot: error: Couldn't parse partition size '0x'
joyyia said:
Hi everybody,
I want to try some battery friendly rom based on android Marshamallow and currently I am on stock oreo.. The issue is I cant install android 6.0 and encounter error while flashing boot image in fastboot..
Can I directly flash 6.0 based rom through twrp on oreo?
And while I was doing this I wasnt even able to flash 8.0 boot img as well while I was able to install it through twrp..
Sorry If the question is not proper or I am unable to explain it properly
To be precise it gives fastboot: error: Couldn't parse partition size '0x'
Click to expand...
Click to collapse
I think u also need to change vendor, radio, bootloader according to it. Or switch to stock mm first then flash
Sent from my angler using XDA Labs
Same problem, how I can fix it now? Pls someone help, I flash multirom recovery but I could not flash any rom so I decided back to stock and now I can’t flash boot.img same error help pls, I love my nexus
If you are experiencing what I am, this appears to be working...
In the old days, to flash a Nexus Device, wugfresh's Nexus Root Toolkit was what I used. With my current Nexus 6P, I'd recently been tinkering with a newer LineageOS unofficial ROM, and somewhere along the way, I ended up with that "Couldn't parse partition size '0x'" error, and sometimes others, when trying to flash the original ROM back, and was afraid my phone was history. However, I remembered wugfresh's Nexus Root Toolkit, and that it had options in it to "unbrick/debrick" a nexus device. So, I took my already downloaded latest official GOogle Nexus ROM, hunted down the wugfresh nexus root toolkit, and then it was readily able to restore my phone to its previously functioning state, just like in the old days. Now, at this very moment, I just did this... I don't know if anything else will pop up not right, but it didn't give any errors when it went to flash the official rom, it rebooted, and is now waiting for me to set up my nexus phone... lol... so it looks as though the crisis has been averted... Since it is no longer supported, and bitdefender throws up warnings when i try to go to their original website. I used the techspot's website to download the toolkit. And, of course, the official google android rom site for the latest official ROM.
1. Downloaded Wugfresh Nexus Root Toolkit.
2. Downloaded latest Nexus 6P (angler) official ROM.
3. Installed Wugfresh Nexus Root Toolkit.
4. Put phone in Bootloader and connected to computer.
5. Ran Wugfresh Nexus Root Toolkit
6. Manually selected Nexus 6P.
7. Selected any ROM version.
8. Under (Restore/Upgrade/Downgrade) - Flash Stock + Unroot ... I selected "Soft-Bricked/Bootloop ... and then hit "Flash Stock + Unroot"
9. Selected "Other/Browse... For use with any factory image package: zip/tgz"
10. Selected "I downloaded a factory image myself that I would like to use instead."
11. Clicked OK.
12. Selected the previously downloaded latest Nexus 6P (angler) official ROM.
13. Watched with gratitude as it seemed to resuscitate my favorite phone.
I hope this helps someone else who may have fallen into this... I'll post again if it turns out not to have solved the problem fully.
newcapricasean said:
In the old days, to flash a Nexus Device, wugfresh's Nexus Root Toolkit was what I used. With my current Nexus 6P, I'd recently been tinkering with a newer LineageOS unofficial ROM, and somewhere along the way, I ended up with that "Couldn't parse partition size '0x'" error, and sometimes others, when trying to flash the original ROM back, and was afraid my phone was history. However, I remembered wugfresh's Nexus Root Toolkit, and that it had options in it to "unbrick/debrick" a nexus device. So, I took my already downloaded latest official GOogle Nexus ROM, hunted down the wugfresh nexus root toolkit, and then it was readily able to restore my phone to its previously functioning state, just like in the old days. Now, at this very moment, I just did this... I don't know if anything else will pop up not right, but it didn't give any errors when it went to flash the official rom, it rebooted, and is now waiting for me to set up my nexus phone... lol... so it looks as though the crisis has been averted... Since it is no longer supported, and bitdefender throws up warnings when i try to go to their original website. I used the techspot's website to download the toolkit. And, of course, the official google android rom site for the latest official ROM.
1. Downloaded Wugfresh Nexus Root Toolkit.
2. Downloaded latest Nexus 6P (angler) official ROM.
3. Installed Wugfresh Nexus Root Toolkit.
4. Put phone in Bootloader and connected to computer.
5. Ran Wugfresh Nexus Root Toolkit
6. Manually selected Nexus 6P.
7. Selected any ROM version.
8. Under (Restore/Upgrade/Downgrade) - Flash Stock + Unroot ... I selected "Soft-Bricked/Bootloop ... and then hit "Flash Stock + Unroot"
9. Selected "Other/Browse... For use with any factory image package: zip/tgz"
10. Selected "I downloaded a factory image myself that I would like to use instead."
11. Clicked OK.
12. Selected the previously downloaded latest Nexus 6P (angler) official ROM.
13. Watched with gratitude as it seemed to resuscitate my favorite phone.
I hope this helps someone else who may have fallen into this... I'll post again if it turns out not to have solved the problem fully.
Click to expand...
Click to collapse
I tried this and flashed everything ok. But it´s still in bootloop. I did factory reset and same. idk what to do next.
herr.dalay said:
I tried this and flashed everything ok. But it´s still in bootloop. I did factory reset and same. idk what to do next.
Click to expand...
Click to collapse
Try flash "Blod Patch" after flashing everything
haitham0 said:
Try flash "Blod Patch" after flashing everything
Click to expand...
Click to collapse
Thnx! I used the BLOD patch and it´s back. No performance issues so far using havoc rom.
Thanks very much for pointing me towards Nexus Root Toolkit... its a great bit of software
newcapricasean said:
In the old days, to flash a Nexus Device, wugfresh's Nexus Root Toolkit was what I used. With my current Nexus 6P, I'd recently been tinkering with a newer LineageOS unofficial ROM, and somewhere along the way, I ended up with that "Couldn't parse partition size '0x'" error, and sometimes others, when trying to flash the original ROM back, and was afraid my phone was history. However, I remembered wugfresh's Nexus Root Toolkit, and that it had options in it to "unbrick/debrick" a nexus device. So, I took my already downloaded latest official GOogle Nexus ROM, hunted down the wugfresh nexus root toolkit, and then it was readily able to restore my phone to its previously functioning state, just like in the old days. Now, at this very moment, I just did this... I don't know if anything else will pop up not right, but it didn't give any errors when it went to flash the official rom, it rebooted, and is now waiting for me to set up my nexus phone... lol... so it looks as though the crisis has been averted... Since it is no longer supported, and bitdefender throws up warnings when i try to go to their original website. I used the techspot's website to download the toolkit. And, of course, the official google android rom site for the latest official ROM.
1. Downloaded Wugfresh Nexus Root Toolkit.
2. Downloaded latest Nexus 6P (angler) official ROM.
3. Installed Wugfresh Nexus Root Toolkit.
4. Put phone in Bootloader and connected to computer.
5. Ran Wugfresh Nexus Root Toolkit
6. Manually selected Nexus 6P.
7. Selected any ROM version.
8. Under (Restore/Upgrade/Downgrade) - Flash Stock + Unroot ... I selected "Soft-Bricked/Bootloop ... and then hit "Flash Stock + Unroot"
9. Selected "Other/Browse... For use with any factory image package: zip/tgz"
10. Selected "I downloaded a factory image myself that I would like to use instead."
11. Clicked OK.
12. Selected the previously downloaded latest Nexus 6P (angler) official ROM.
13. Watched with gratitude as it seemed to resuscitate my favorite phone.
I hope this helps someone else who may have fallen into this... I'll post again if it turns out not to have solved the problem fully.
Click to expand...
Click to collapse
thanks, man really appreciate it!
Sent from my angler using XDA Labs