Can't get past first update - Nexus 9 Q&A, Help & Troubleshooting

This evening i've made a factory reset of my nexus 9 and now i can't get past the first update because when it reboots it gives me the "error" that was giving when trying to update using the OTA. When i reboot it, it still tells me to update the device.
I have an unlocked bootloader so i think i should be able to flash the updated official rom from the bootloader but i don't know how and all the guides i've found told me to "select" things that i couldn't find.
I am stuck at the first update so i don't have the usb dabugging enabled but i still can load things using the usb.
Should i send it back? (The device was rooted but i think the factory reset should have removed it)
Please help me i'm desperate! (and sorry for my bad english)

Aleschio said:
This evening i've made a factory reset of my nexus 9 and now i can't get past the first update because when it reboots it gives me the "error" that was giving when trying to update using the OTA. When i reboot it, it still tells me to update the device.
I have an unlocked bootloader so i think i should be able to flash the updated official rom from the bootloader but i don't know how and all the guides i've found told me to "select" things that i couldn't find.
I am stuck at the first update so i don't have the usb dabugging enabled but i still can load things using the usb.
Should i send it back? (The device was rooted but i think the factory reset should have removed it)
Please help me i'm desperate! (and sorry for my bad english)
Click to expand...
Click to collapse
Try flashing the factory image. This is for the n5 but will work for the n9. Look at method 2. Use the correct bootloader and radio names for the n9, they'll be different than the examples given. Also in method 2 there is one command that is different for the n9. Instead of fastboot flash userdata userdata.img use fastboot flash vendor vendor.img. Google nexus factory image for the factory image for the n9
http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Try flashing the factory image. This is for the n5 but will work for the n9. Look at method 2. Use the correct bootloader and radio names for the n9, they'll be different than the examples given. Also in method 2 there is one command that is different for the n9. Instead of fastboot flash userdata userdata.img use fastboot flash vendor vendor.img. Google nexus factory image for the factory image for the n9
http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the fast reply!
It worked! Thanks a lot for you help! You saved my file

Related

Fastboot issue

Just got my N9 today. When I ADB devices, i see the serial # of my device properly. If I go into bootloader, when I fastboot devices, it comes up as all question marks (??????????????? fastboot). Windows properly sees my device as "Android Bootloader Interface". I am able to do basic commands (oem unlock, reboot-bootloader, etc). However I cannot push any files (root or custom recovery.) My DOS window just hangs and nothing transfers.
I googled for three hours and can't find if this is fixable or if I have to RMA. (And if I do RMA, how would I? I can't say I am having issues pushing custom recoveries to the device LOL)
Thanks in advance!
Have you tried flashing the factory image? That should not void your warranty
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Have you tried flashing the factory image? That should not void your warranty
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I wish I could. I can't push any files to it via fastboot, cant push a custom recovery, nothing. I did a factory reset, i erased the cache via stock recovery, nothing. But it boots fine into Lollipop and functions fine that way
PaisanNYC said:
I wish I could. I can't push any files to it via fastboot, cant push a custom recovery, nothing. I did a factory reset, i erased the cache via stock recovery, nothing. But it boots fine into Lollipop and functions fine that way
Click to expand...
Click to collapse
Then I'd say you rma it. Just tell them you didn't get the ota to 5.0.1 and you were trying to flash the factory image and nothing works in fastboot. You definitely have a hardware issue.
Just to be clear, when you tried to flash a custom recovery you fastboot flash recovery customrecovery.img?
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Then I'd say you rma it. Just tell them you didn't get the ota to 5.0.1 and you were trying to flash the factory image and nothing works in fastboot. You definitely have a hardware issue.
Just to be clear, when you tried to flash a custom recovery you fastboot flash recovery customrecovery.img?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
yes. fastboot flash recovery *.img
I've owned every Nexus device (except the Nexus S), and this is the only one that is throwing me for a loop! lol And I am surprised that the bootloader isnt the standard Nexus bootloader.
PaisanNYC said:
yes. fastboot flash recovery *.img
I've owned every Nexus device (except the Nexus S), and this is the only one that is throwing me for a loop! lol And I am surprised that the bootloader isnt the standard Nexus bootloader.
Click to expand...
Click to collapse
Bootloader surprised me too. Not like the other nexus devices
Sent from my Nexus 9 using XDA Free mobile app
I have the same problem that 'fastboot devices' return question marks. I have drivers up to date. I just checked on my friends PC and thank God 'fastboot devices' works on his PC. So I now wonder and think how could I debug that on my PC and get it working. Maybe go through some logs? Or export drivers?
JacKalPin said:
I have the same problem that 'fastboot devices' return question marks. I have drivers up to date. I just checked on my friends PC and thank God 'fastboot devices' works on his PC. So I now wonder and think how could I debug that on my PC and get it working. Maybe go through some logs? Or export drivers?
Click to expand...
Click to collapse
Don't plug it into a USB 3.0 port. that was my issue all along. Use a USB 2.0 port.
It's a cable fault. In my Redmi 3 on a cable from old Xperia P i've had question marks,
replaced the cable to a newer cable from Redmi Note 2 and voila - the correct number displays instead of the question marks.

[Q&A] [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42)

Q&A for [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
hhzznn said:
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
Click to expand...
Click to collapse
Hello there,
If not using the "adbsetup" drivers or the ones off the ASUS website (sorry, couldn't find the ASUS drivers when I looked ), use one of the above. If using one and still not connecting, try the other option.
Also, check your USB ports to make sure you are not connecting via a USB 3.x standard. Android (or at least some Android devices) don't like those.
If all else fails, you may need a Linux build
Hope this provides a head start.
Sent from my LG-D520 using XDA Free mobile app
help me please
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
hhzznn said:
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
Click to expand...
Click to collapse
Looks you got a little further... :good:
From what I remember when I followed the guide, there was no feedback (nothing on the screen, and tablet remains black) on when you issue the unlock commands - which by the way, are:
Code:
fastboot oem unlock61646
fastboot oem unlockD696E
Then, reboot the bootloader and install CWM (first line may be substituted with rebooting into fastboot by hand):
Code:
fastboot reboot-bootloader
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
You shouldn't get a write-protect error this time around. Hope this helps.
By the way, your SKU is WW version, right? If not, my ROM may not help you (without going the long way around of instead of flashing the ROM, copying the odex files back into /system/app using CWM's ADB push command). Just a warning. If you are not WW, and insist on flashing anyway, I would highly recommend a nandroid backup (and probably copied) to MicroSD to protect your original (broken) ROM.
help me
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
hhzznn said:
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
Click to expand...
Click to collapse
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
the code:fastboot unlock oem61646 worked but fastboot oemD696E not working
in stock recovery i cant install rom.zip
and in fastboot when install recovery cwm answer bootloader lock
any offer for me?
---------- Post added at 09:14 AM ---------- Previous post was at 09:07 AM ----------
**you may need a Linux build **
i have a linux base ,, may you help me??
hhzznn said:
**you may need a Linux build **
i have a linux base ,, may you help me??
Click to expand...
Click to collapse
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
i have ubuntu....what should i do?
hhzznn said:
i have ubuntu....what should i do?
Click to expand...
Click to collapse
In a terminal...
apt-get install android-tools-fastboot
...would be a good start. You may need to register the device vendor in your configuration, which I can research later if...
fastboot devices
...lists nothing. Hope this helps.
Sent from my LG-D520 using XDA Free mobile app
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Syncline said:
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Click to expand...
Click to collapse
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
joel.maxuel said:
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
Click to expand...
Click to collapse
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Syncline said:
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Click to expand...
Click to collapse
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
joel.maxuel said:
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
Click to expand...
Click to collapse
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Syncline said:
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Click to expand...
Click to collapse
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
joel.maxuel said:
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
Click to expand...
Click to collapse
No I wasn't encrypted before but from what I read it seems to involve a failure to mount the DATA partition correctly, and the Android OS erroneously assumes it's encrypted. I'm not overly concerned about setting up apps by hand, I do have a titanium backup of my apps and data. As I'm still at work, I can't do too much playing around on my tablet. I don't have access to my personal computer that has all my tools like adb, fastboot, etc. until the work day is done. I've said it a couple of times, but I truly appreciate the assistance that you've provided.
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Syncline said:
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Click to expand...
Click to collapse
That's an interesting side effect...never had that happen before.
You can try it, and let me know. Hopefully your CWM is still kicking around, or else you will have to reinstall via fastboot. Or alternatively, just re-root normally (like with Kingo).
By the way, before you do that, does /system/xbin/su exist? Or what you could answer, is you could download Voodoo OTA RootKeeper and report back which values are not checked off. I think SuperSU update.zip places the su binary, nothing else. But we shall see.
Sorry Joel, I didn't see your reply before I flashed the SuperSU zip but it did work, my tablet is rooted again.

[Q] FAILED (remote: data length is too large)

Hi Internet,
I was trying to flash Android M on my Nexus 9 (Wi-Fi only) today and ended up with errors such as: "system.ui has stopped working" or "android.process has stopped" because I wanted to see if I actually needed to do a factory reset for it to work properly (turns out I do). After that I've tried again and have run into some issues.
Firstly, after that Android M wasn't flashing at all and I have decided to abandon the idea of M and just go back to Lollipop. Now, I am trying to flash 5.1.1 and I keep on getting FAILED (remote: data length is too large) error when flashing my system partition. I'm flashing everything separately because if I try to do it as one image because I keep getting error: update package missing system.img errors. I have no trouble with flashing my bootloader and other partitions(boot, cache, recovery, etc), but that system partition just won't flash! I've tried 5.0, 5.1, 5.1.1 and I keep on getting these errors.
I have no idea what to do. Please help. I've spent the last 5 hours trying to figure it out and nothing has yet came up. I'm using a Mac, but I don't see how this might be causing an issue.
If you have any valuable information - please help!
I'm very comfortable with flashing and ROMs, in fact I've updated my N5 to M in 5 min, but I've never seen this error before and have no idea how to fix. All I found out is that, I think, it only happens on HTCs...
Solved: http://forum.xda-developers.com/showpost.php?p=61354553&postcount=14
I can't help you but I can tell you I had the same problem. After much frustration and many attempts to flash 5.1.1 it finally worked. I was ready to rma the device as I was sure something was wrong with it. Sorry I can't be more help as getting it to work was so random.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I can't help you but I can tell you I had the same problem. After much frustration and many attempts to flash 5.1.1 it finally worked. I was ready to rma the device as I was sure something was wrong with it. Sorry I can't be more help as getting it to work was so random.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Did you by any chance use any special image or was it a normal image from Google?
tarasmuz said:
Did you by any chance use any special image or was it a normal image from Google?
Click to expand...
Click to collapse
No,I used the factory image from Google. There were a number of times I got the image to flash, I flashed images separately, but got boot loops even after factory resets. Even got it to boot a couple of times but couldn't sign into Google. Wi-Fi would keep resetting and bring me back to the Google sign in. I'm still not convinced that there isn't something wrong with the device, bad nand? But it's working now. I haven't tried to flash anything since.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
No,I used the factory image from Google. There were a number of times I got the image to flash, I flashed images separately, but got boot loops even after factory resets. Even got it to boot a couple of times but couldn't sign into Google. Wi-Fi would keep resetting and bring me back to the Google sign in. I'm still not convinced that there isn't something wrong with the device, bad nand? But it's working now. I haven't tried to flash anything since.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm pretty sure that the device is fine. I flashed images before and had no problems at all.
If you haven't already, make sure nothing is running in the back ground on your pc that might be using ram. The complete system image has to load into ram and it's a pretty big file.
jd1639 said:
If you haven't already, make sure nothing is running in the back ground on your pc that might be using ram. The complete system image has to load into ram and it's a pretty big file.
Click to expand...
Click to collapse
I've just restarted and closed all the programs, but it didn't help. Going to be trying and will post if I manage to make it work. Thanks for your help!
You might have already tried this too, but re-download the factory image, check it's md5, then extract it. Might be a bad download or extraction. Then follow the long method in this, http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
jd1639 said:
You might have already tried this too, but re-download the factory image, check it's md5, then extract it. Might be a bad download or extraction. Then follow the long method in this, http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Click to expand...
Click to collapse
Yeah, I've tried all of that. Also checked MD5 and it matches to the one on the website. The only thing I could think of is bad extraction. Will try another unarchiver.
tarasmuz said:
Yeah, I've tried all of that. Also checked MD5 and it matches to the one on the website. The only thing I could think of is bad extraction. Will try another unarchiver.
Click to expand...
Click to collapse
Just tried another unarchiver - no difference.
tarasmuz said:
Just tried another unarchiver - no difference.
Click to expand...
Click to collapse
What are you using? Use winrar or 7-zip
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
What are you using? Use winrar or 7-zip
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I'm on a Mac, so The Unarchiver and Archive Utility.
tarasmuz said:
Hi Internet,
I was trying to flash Android M on my Nexus 9 (Wi-Fi only) today and ended up with errors such as: "system.ui has stopped working" or "android.process has stopped" because I wanted to see if I actually needed to do a factory reset for it to work properly (turns out I do). After that I've tried again and have run into some issues.
Firstly, after that Android M wasn't flashing at all and I have decided to abandon the idea of M and just go back to Lollipop. Now, I am trying to flash 5.1.1 and I keep on getting FAILED (remote: data length is too large) error when flashing my system partition. I'm flashing everything separately because if I try to do it as one image because I keep getting error: update package missing system.img errors. I have no trouble with flashing my bootloader and other partitions(boot, cache, recovery, etc), but that system partition just won't flash! I've tried 5.0, 5.1, 5.1.1 and I keep on getting these errors.
I have no idea what to do. Please help. I've spent the last 5 hours trying to figure it out and nothing has yet came up. I'm using a Mac, but I don't see how this might be causing an issue.
If you have any valuable information - please help!
I'm very comfortable with flashing and ROMs, in fact I've updated my N5 to M in 5 min, but I've never seen this error before and have no idea how to fix. All I found out is that, I think, it only happens on HTCs...
Click to expand...
Click to collapse
Your Android SDK (fastboot) probably needs to be updated. Depending on how old it is, Google updated the SDK and fastboot to allow flashing these very large system.img files in early November, 2014.
cam30era said:
Your Android SDK (fastboot) probably needs to be updated. Depending on how old it is, Google updated the SDK and fastboot to allow flashing these very large system.img files in early November, 2014.
Click to expand...
Click to collapse
Yes! It worked! Turns out I was using this outdated fastboot file which wasn't allowing flashing newer system partitions. Fun fact: outdated fastboot file worked with N5, but didn't work with N9. Anyway, I updated my SDK though Android Studio and everything flashed perfectly. Many thanks to cam30era and jd1639.
tarasmuz said:
Yes! It worked! Turns out I was using this outdated fastboot file which wasn't allowing flashing newer system partitions. Fun fact: outdated fastboot file worked with N5, but didn't work with N9. Anyway, I updated my SDK though Android Studio and everything flashed perfectly. Many thanks to cam30era and jd1639.
Click to expand...
Click to collapse
I'm glad this worked out for you.

no system, no recovery, device locked, what can i do ?

hi,
i wanted to flash stock android (used an rom before) so i erase recovery system etc.. and when i want to flash the system img it says "
(bootloader) Device State : Locked
FAILED (remote: Can not flash any images while device state is locked!)
-.- what can i do ?
any solutions ?
thanks
Not much. Only thing you can do with a locked boot loader is flash OTA updates, and they don't have an OTA that will flash the full system. OTAs only update an existing system. You shouldn't have erased your system.
You need to return your N9 to HTC for a replacement.
Sent from my Nexus 9
enriquejones666 said:
Not much. Only thing you can do with a locked boot loader is flash OTA updates, and they don't have an OTA that will flash the full system. OTAs only update an existing system. You shouldn't have erased your system.
You need to return your N9 to HTC for a replacement.
Sent from my Nexus 9
Click to expand...
Click to collapse
hmm okey, so send it back to HTC (or amazon cause i buyed it there)
but it should be no problem cause its locked and therse no sign that it was/is rooted, right?
also i have buyed an insurance for 2 years so i think it should be okey... i hope so
So I'm in a similar pickle, with one huge difference: my bootloader is unlocked, and reflects such in the fastboot menu.
Long story short, I have no image of any kind on it at this point. All attempts with any interface to flash either 5.1.1 or 6 fail. When attempting to flash the system.img, I get the "too many links" error. I've not found a solution that works.
At this point, I have no recovery and no image. I can't successfully flash one either. Not sure what to do from here...
Sent from my LG-H810
disturbd1 said:
So I'm in a similar pickle, with one huge difference: my bootloader is unlocked, and reflects such in the fastboot menu.
Long story short, I have no image of any kind on it at this point. All attempts with any interface to flash either 5.1.1 or 6 fail. When attempting to flash the system.img, I get the "too many links" error. I've not found a solution that works.
At this point, I have no recovery and no image. I can't successfully flash one either. Not sure what to do from here...
Sent from my LG-H810
Click to expand...
Click to collapse
are you using the right fastboot commands? Eg. not something dumb like fastboot flash boot system.img. Also are you flashing your stuff in the correct order? Make sure to grab a good copy of whatever version of android you're trying to flash from here
tdct12 said:
are you using the right fastboot commands? Eg. not something dumb like fastboot flash boot system.img. Also are you flashing your stuff in the correct order? Make sure to grab a good copy of whatever version of android you're trying to flash from here
Click to expand...
Click to collapse
Thanks, I ended up getting it in a workable state last night. Ran a temporary recovery via Wug's toolkit, got TWRP installed, and went from there. I now have Marshmallow on it via AOSP, but I think the bootloader might still need updating.
Sent from my LG-H810
disturbd1 said:
Thanks, I ended up getting it in a workable state last night. Ran a temporary recovery via Wug's toolkit, got TWRP installed, and went from there. I now have Marshmallow on it via AOSP, but I think the bootloader might still need updating.
Sent from my LG-H810
Click to expand...
Click to collapse
Just download the newest build and fastboot flash bootloader bootloader.img :good:
oediv said:
hmm okey, so send it back to HTC (or amazon cause i buyed it there)
but it should be no problem cause its locked and therse no sign that it was/is rooted, right?
also i have buyed an insurance for 2 years so i think it should be okey... i hope so
Click to expand...
Click to collapse
Definitely send it back to Amazon. They are very good about taking returns. You can just say you tried to update the OS, and now the device doesn't boot (i.e. product is defective).
Sent from my Nexus 9
enriquejones666 said:
Definitely send it back to Amazon. They are very good about taking returns. You can just say you tried to update the OS, and now the device doesn't boot (i.e. product is defective).
Sent from my Nexus 9
Click to expand...
Click to collapse
2 people 1 idea
It's on the way, I said " want to update the OS and Made a factory reset before"
Have you tried flashing the factory images with fastboot? Pretty straight forward...
For future reference, how did you erase things with the bootloader locked?

[Guide] [How To] Android Nougat Developer Preview with Root/Encryption/Data

I've been meaning to write this guide for a little while now, but I've only just gotten around to it. Basically, I had wanted to try the N preview, but TWRP didn't play nice with it, so until now, it has been impossible to run N with encryption, root, and without wiping your data. In the interest of full disclosure, I found the basis for this solution while down a Reddit rabbit hole in a very short post at the end of some thread that I've been unable to find again, so I can't take full credit. Many thanks to this random Redditor.
I originally posted this solution in another thread, but the tl;dr version is this: you have to wait to flash the vendor image from N until you're all done with twrp, but other than that, it's just like you're updating with a monthly security patch. This doesn't require any sort of toolkits or anything else either, so that's always a plus. I'm assuming this would work on the N5X as well, but I don't have one to test this on.
1. Download the factory image of DP4 from here.
2. We're basically going to be following step 9 of @Heisenberg 's guide. So unzip the download as you normally would to update your security patch, and put it in the directory you normally would.
3. Now flash everything EXCEPT the recovery and vendor image. I've copied the code from Heisenberg's guide here for your convenience so you don't have to keep switching pages. If you're going to copy and paste that into your command prompt, don't forget to take out the images I listed.
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Click to expand...
Click to collapse
4. Now that that's done, we're going to go to your phone. Use the fastboot menu to boot into twrp. At this point, you should be able to enter your lock pattern/pin/whatever, and then flash SuperSu as you normally would. IIRC, you'll need v2.74 or higher, which you can download from here.
5. Now using twrp, reboot back into your bootloader. Fastboot flash the DP4 vendor image that we left out earlier, otherwise your phone won't boot.
That's it! You can now boot into system, and you'll be running Nougat DP4! The first boot took a while, and looped a couple timed for me, but it worked, and I've been running DP4 without wiping my data, without decrypting, and with root for a couple weeks. Remember, twrp won't work with the N vendor image installed, so if you want to use twrp again, you'll have to reflash the M vendor image, and then reflash the N one after you're all done. I haven't tried this yet, but that's what I intend to do when it comes time to update to DP5, whenever Google releases that. Happy flashing!
UPDATE: Confirmed, this method does work to update to DP5 from DP4.
Reserved
I'm going to try this.
Really want root on my sh**t.
But, theoretically, when DP5 is out, you'll have to do everything again, but with the Vendor image from DP5?
asj0422 said:
3. Now flash everything EXCEPT the recovery and vendor image. I've copied the code from Heisenberg's guide here for your convenience so you don't have to keep switching pages. If you're going to copy and paste that into your command prompt, don't forget to take out the images I listed.
Click to expand...
Click to collapse
By how some people roll around these forums, I'd remove the lines from the copy/paste box-thingy you did... haha.
Edit: fell on my a**. Reminder for me to be more helpful
Quite honestly if someone needs a guide they don't need to be flashing.
They need to do the proper research and understand what each image is. Just my opinion
Sent from my Nexus 6P using Tapatalk
superchilpil said:
Quite honestly if someone needs a guide they don't need to be flashing.
They need to do the proper research and understand what each image is. Just my opinion
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I agree on this, but you know how it is, people just come in, ask, find, copy/paste and that's it.
1day old accounts with 2/3 posts.
Edit: fell from my pedestal, note to self: be more helpful.
asj0422 said:
I've been meaning to write this guide for a little while now, but I've only just gotten around to it. Basically, I had wanted to try the N preview, but TWRP didn't play nice with it, so until now, it has been impossible to run N with encryption, root, and without wiping your data. In the interest of full disclosure, I found the basis for this solution while down a Reddit rabbit hole in a very short post at the end of some thread that I've been unable to find again, so I can't take full credit. Many thanks to this random Redditor.
I originally posted this solution in another thread, but the tl;dr version is this: you have to wait to flash the vendor image from N until you're all done with twrp, but other than that, it's just like you're updating with a monthly security patch. This doesn't require any sort of toolkits or anything else either, so that's always a plus. I'm assuming this would work on the N5X as well, but I don't have one to test this on.
1. Download the factory image of DP4 from here.
2. We're basically going to be following step 9 of @Heisenberg 's guide. So unzip the download as you normally would to update your security patch, and put it in the directory you normally would.
3. Now flash everything EXCEPT the recovery and vendor image. I've copied the code from Heisenberg's guide here for your convenience so you don't have to keep switching pages. If you're going to copy and paste that into your command prompt, don't forget to take out the images I listed.
4. Now that that's done, we're going to go to your phone. Use the fastboot menu to boot into twrp. At this point, you should be able to enter your lock pattern/pin/whatever, and then flash SuperSu as you normally would. IIRC, you'll need v2.74 or higher, which you can download from here.
5. Now using twrp, reboot back into your bootloader. Fastboot flash the DP4 vendor image that we left out earlier, otherwise your phone won't boot.
That's it! You can now boot into system, and you'll be running Nougat DP4! The first boot took a while, and looped a couple timed for me, but it worked, and I've been running DP4 without wiping my data, without decrypting, and with root for a couple weeks. Remember, twrp won't work with the N vendor image installed, so if you want to use twrp again, you'll have to reflash the M vendor image, and then reflash the N one after you're all done. I haven't tried this yet, but that's what I intend to do when it comes time to update to DP5, whenever Google releases that. Happy flashing!
Click to expand...
Click to collapse
Kudos. Always good to have a write up with steps for folks. Thanks for contributing. [emoji6]
Thanks for this post; I think it really helps having a quick reference for something like this. I can confirm that if you need to re-access TWRP, you can just flash the marshmallow vendor.img over adb, boot to TWRP, do what you have to do, return to bootloader, flash the nougat vendor.img in adb, and continue using your device. I had to use TWRP to flash the Adaway systemless support zip and doing that sequence I listed above worked as expected. It's not as ideal as having TWRP function with an encrypted device as it does on marshmallow, but at least it works.
superchilpil said:
Quite honestly if someone needs a guide they don't need to be flashing.
They need to do the proper research and understand what each image is. Just my opinion
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
benleonheart said:
I agree on this, but you know how it is, people just come in, ask, find, copy/paste and that's it.
1day old accounts with 2/3 posts.
Click to expand...
Click to collapse
I hope you guys don't fall off your pedestal way up there above everyone else.
Everyone has to learn somewhere and the guide above is a nice start for the noobiez on the forum.
SyCoREAPER said:
I hope you guys don't fall off your pedestal way up there above everyone else.
Everyone has to learn somewhere and the guide above is a nice start for the noobiez on the forum.
Click to expand...
Click to collapse
Worry not, dear friend as I was also a noob back in '08/'09.
We all learn new things every day. I'm just saying that there are dedicated threads to help with newcomers and guide them step by step.
Edit: You're right. Thanks.
When booting into twrp, will it prompt you for a pin/password? I never set one and I'm afraid it will make me have to completely wipe my phone.
Sent from my Nexus 6P using XDA-Developers mobile app
Sweet! This was easy peasy and didn't lose my data. No serious issues, either. Thanks for sharing this info.
Cheers
Sent from my Nexus 6P using XDA-Developers mobile app
crossen0 said:
When booting into twrp, will it prompt you for a pin/password? I never set one and I'm afraid it will make me have to completely wipe my phone.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
To be honest, I'm not sure. I've never had to deal with twrp and no password. I wouldn't think it would reset anything; I assume you just won't have to enter a password..?
What do you normally do for twrp?
thanks for the guide. Do you think if I'm already on DP4 I could flash the vendor image from an M build and continue from there?
edit: it worked!
Thank you this worked like a charm! Switched from a rooted+busybox stock build to rooted DP4. Now waiting for DP5
No problem! Glad it worked for you!
asj0422 said:
No problem! Glad it worked for you!
Click to expand...
Click to collapse
Just upgraded from my stock M + rooted + busy boxed + xposed build to DP5. TWRP and SU both working. Thanks for the guide.
Just updated to DP5 using this method (all flashes but vendor and recovery, flash M vendor, boot into TWRP, root, reboot to bootloader, flash DP5 vendor). Works perfect.
Works on un-encrypted as well. Flashed bootloader, radio, boot, cache and system, reboot TWRP to allow modification-back to bootloader and flashed modified boot.img. Then boot to TWRP, adb sideload SuperSU-2.76, reboot bootloader and flash vendor.img then reboot system. Profit! Still unencrypted with no loss of data and root retained.
mtw4991 said:
Works on un-encrypted as well. Flashed bootloader, radio, boot, cache and system, reboot TWRP to allow modification-back to bootloader and flashed modified boot.img. Then boot to TWRP, adb sideload SuperSU-2.76, reboot bootloader and flash vendor.img then reboot system. Profit! Still unencrypted with no loss of data and root retained.
Click to expand...
Click to collapse
Thanks for the extra info!
Question: doesn't twrp work with N as it did with M if you're not encrypted? I thought the issue with twrp and N was due to twrp's code not being able to decrypt - and that was the whole reason people were using the modified boot.img and decrypting was so twrp would work.
I can also confirm that this works with DP5. Will be updating OP shortly.

Categories

Resources