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.
Related
Hello. I'm annoyed
I rooted to get rid of problems... So
I followed these tasks: http://forum.xda-developers.com/showthread.php?t=1653566 and the root worked for a few days - then moved into a boot loop.... how/why... I don't know.
Ive tried many of the different .aos files to find a correct one for my 101g9 250gb, but I still can't get it out of the loop.
This is where I've been getting the different Aos files: http://forum.xda-developers.com/showthread.php?t=1468925
I get 2 different results 1)error 207 (update failed) or 2) boot loop.
One stange thing did happen once - It's managed to reload the android installer, I selected a language, then it crashed again. Of course I tried the same thing again, but it never got past the boot loop again.
After 2 weeks of trying, I'd like some help.
I always have it plugged in. It's not the battery. It's the HDD model and I don't know exactly which version came with the device. I think 4.0.25.. not 100% sure
Please help
I don't have the HDD model so don't know what to tell you exactly..
What I would do on my flash model is boot into recovery. completely reformat the system and use recovery to update the firmware with an Archos firmware (aos file) onto it.
Reformating it from recovery would bring the filesystem back to stock so it should fix anything wierd any of the other roms might have done. So dropping an Archos firmware on it should in theory fix it. Though you WILL lose your root and anything else you have on the drive.
Djirin said:
I don't have the HDD model so don't know what to tell you exactly..
What I would do on my flash model is boot into recovery. completely reformat the system and use recovery to update the firmware with an Archos firmware (aos file) onto it.
Reformating it from recovery would bring the filesystem back to stock so it should fix anything wierd any of the other roms might have done. So dropping an Archos firmware on it should in theory fix it. Though you WILL lose your root and anything else you have on the drive.
Click to expand...
Click to collapse
Thanks for your help, but no luck- that didn't work. I'm sure I lost all my data a long time ago with the amount of reformats I've done. What I'm curious about is, can the tablet actually become a brick just by using these rooted firmwares? I'm assuming that it's fine and that I just have to 'crack to code' to installing the right firmware in the right order.....
I'm still curious if anyone else has had this problem..
Hmm.. Try going back into recovery and try the Reset Android option?
Maybe do Reset Android. Reformat Device. Upgrade Firmware?
The device boots.. so it has to be something causing it.. Have you tried to see if you can use ADB to get into the device and look at any log entries?
Djirin said:
Hmm.. Try going back into recovery and try the Reset Android option?
Maybe do Reset Android. Reformat Device. Upgrade Firmware?
The device boots.. so it has to be something causing it.. Have you tried to see if you can use ADB to get into the device and look at any log entries?
Click to expand...
Click to collapse
ADB? ok, I didn't know what it was. But it's now installed and I followed a random setup on youtube, but when I type ADB devices, nothing comes up.
So now I have it installed, but I so far I can't get win7 to detect the tablet in device manager
Regarless, can the ADB detect problems on the tablet when the archos is only connected waiting for the AOS file (A101H-REC - 299MB)?
Btw, you've already got me waaaaay over my head on this stuff - but still, I'm learning.
pwnami said:
ADB? ok, I didn't know what it was. But it's now installed and I followed a random setup on youtube, but when I type ADB devices, nothing comes up.
So now I have it installed, but I so far I can't get win7 to detect the tablet in device manager
Regarless, can the ADB detect problems on the tablet when the archos is only connected waiting for the AOS file (A101H-REC - 299MB)?
Btw, you've already got me waaaaay over my head on this stuff - but still, I'm learning.
Click to expand...
Click to collapse
Let me join the conversation
Adb works only is it is enabled in developer settings.
What kind of system do you have in use?
In your case i would probably try exporting hdd in sde. This allows you to browse files inside your hdd in linux operating system through usb.
If it is empty, i would export data partition through sde. This allows you to see if there are any files in your data partition.
You said that the device bootloops, yes? That means that the reformat device is not working. It would remove the system, so you shouldnt even see the bootanimation.
Sent from my ME301T using xda app-developers app
julle131 said:
Let me join the conversation
Adb works only is it is enabled in developer settings.
What kind of system do you have in use?
In your case i would probably try exporting hdd in sde. This allows you to browse files inside your hdd in linux operating system through usb.
If it is empty, i would export data partition through sde. This allows you to see if there are any files in your data partition.
You said that the device bootloops, yes? That means that the reformat device is not working. It would remove the system, so you shouldnt even see the bootanimation.
Sent from my ME301T using xda app-developers app
Click to expand...
Click to collapse
Hi, thanks - any advice is welcome. I only have windows7 - Sorry.
As for the bootloop, yes that's the status. I hadn't even considered that the reformatting process wasn't actaully working [but it is] - I reformatted the device and didn't install an AOS. now every restart brings me straight into the Recovery menu [which should happen i assume].
So, with a "clean" but stubborn device, what would you advise to try to isolate the problem? (rather than me simply blindly trying random things)
Thanks
pwnami said:
Hi, thanks - any advice is welcome. I only have windows7 - Sorry.
As for the bootloop, yes that's the status. I hadn't even considered that the reformatting process wasn't actaully working [but it is] - I reformatted the device and didn't install an AOS. now every restart brings me straight into the Recovery menu [which should happen i assume].
So, with a "clean" but stubborn device, what would you advise to try to isolate the problem? (rather than me simply blindly trying random things)
Thanks
Click to expand...
Click to collapse
So reformat works. Have you tried to flash the official 4.0.28(http://update.archos.com/9/gen9/gen9_4.0.28/firmware_archos_it4.aos)?
After searching about your error 207, I found this:http://forum.archosfans.com/viewtopic.php?f=35&t=56037
Code 207 is issued by aosparser when the .aos upgrade file doesn't
pass the signature check.
...
There's more bad news... If the genuine original .aos files are also
giving the same error it means the signing keystore may also have been
damaged.
Click to expand...
Click to collapse
Of course, this is for Archos 5, so hopefully this is not the case.
julle131 said:
So reformat works. Have you tried to flash the official 4.0.28(http://update.archos.com/9/gen9/gen9_4.0.28/firmware_archos_it4.aos)?
After searching about your error 207, I found this:http://forum.archosfans.com/viewtopic.php?f=35&t=56037
Of course, this is for Archos 5, so hopefully this is not the case.
Click to expand...
Click to collapse
Yeah, I've used the aos from the archos site a bunch of times - still no luck. btw, that link to the 4.0.28 didn't work....
by "Flash" I hope you mean install.... not some other random process
pwnami said:
Yeah, I've used the aos from the archos site a bunch of times - still no luck. btw, that link to the 4.0.28 didn't work....
by "Flash" I hope you mean install.... not some other random process
Click to expand...
Click to collapse
Yeah... I just noticed it was broken. And yes, I meant install.
I am sorry, but I'm out of ideas.
Sent from my GT-I9100 using xda app-developers app
julle131 said:
Yeah... I just noticed it was broken. And yes, I meant install.
I am sorry, but I'm out of ideas.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
So, do you know if I can access/use ADB on a win7 pc when the archos doesn't have an aos on it?
http://forum.xda-developers.com/showthread.php?t=2104491&highlight=wlan
You could try this. it's written that it doesn't work on hdd model. but it can't get much worse it think. If I understand things correctly, you don't need to have installed any aos before installing this rom. with other roms you get a archos.ext4.update so you need a running system. yust give it a try but don't blame me if your tablet's completely dead afterwards. i don't know what will happen.
Or you could just follow the steps 1-7 (from link above!) to get cwm, maybe that helps for sth, but i don't know.
sry, but my writing style is bad. and do it on your own risk, I'm not that expirienced but that's what I would do...
Good luck
noaddress said:
http://forum.xda-developers.com/showthread.php?t=2104491&highlight=wlan
You could try this. it's written that it doesn't work on hdd model. but it can't get much worse it think. If I understand things correctly, you don't need to have installed any aos before installing this rom. with other roms you get a archos.ext4.update so you need a running system. yust give it a try but don't blame me if your tablet's completely dead afterwards. i don't know what will happen.
Or you could just follow the steps 1-7 (from link above!) to get cwm, maybe that helps for sth, but i don't know.
sry, but my writing style is bad. and do it on your own risk, I'm not that expirienced but that's what I would do...
Good luck
Click to expand...
Click to collapse
I gave up on this 6 months ago. but I turned it on 2 days ago and it magically worked.... Now, it's back in a bootloop again. Everything was working for two days, except sometimes the HDD wasn't reading the files, or the system wasn't detecting the HDD...
Could the HDD be damaged? If so, is there a way to check if it is (I was thinking about the ssd option)
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
Hello guys I have a serious problem
First of all my smartphone:
HTC One M7
I'm not that good at rooting an stuff so I try out alot of things. So I rooted my phone and put cyanogenmod on it with the special software from the main-site (thats the software for dummies where it does everything by itself)
so then it was rooted and unlocked and had cyanogenmod on it. The main reason for me to do this was to be able to delete those annoying preinstalled apps like the google app itself (seriously if I wanna google something I aniway open the browser...) aniway I also deleted a few other apps and it worked just fine for like a half year.
Then I decided to check if I could delete something else and decided to delete (I'm not a 100% sure if it was this but I'm pretty sure) a part of the google settings app with a root app deleting app.
afterwards everything was still working fine except that I cant open Play store, when I do try to open it it pops up and imediately closes again without a error message or anithying (its also still opened in the "taskmanager" but if i try to open it from there the same thing happens) also I cant create any more google accounts or can install any kind of app nothing of that seems working. So afterwards I decided to try many things out to get the probelm away myself, first attempt was to newly install the cyanogenmod, with didn't work because I couldn't install the neccessery app on the phone.
then I tried flashing new roms by downloading various snapshots and nightly versions of CM (I coudln't find a stable version of CM for my HTC One M7) onto my phone an flashing them using recovery.
this actually worked and In the end I had those versions on my phone but the problem with the playstore and installing apps was still there. also in the setup of CM it asks to create a google account and when i press the button I get habtic feedback that I pressed it but nothing at all happens and if i then try to create a new google account in the settings it also just doesn't open anithyng.
I think the only way would be to flash a rom from the PC by using something like Odin but I havent found any way to make it work so I'm asking you if any of you has an idea what to do...
o and another piece of information wich might be useful: the google settings app is still there but with alot less options.
thanks already for every answer I get
Sounds like you uninstalled something from the gapps package. Try reaching gapps and see if that fixes it.
Uzephi said:
Sounds like you uninstalled something from the gapps package. Try reaching gapps and see if that fixes it.
Click to expand...
Click to collapse
Thanks for your answer.
The question for me is how to install those Gapps I found some on the internet downloaded them and installed them from the recovery it aqctualli did something but the problem was still there.
was it the wrong way to install it over the recovery or is it something else?
Kyotai said:
Thanks for your answer.
The question for me is how to install those Gapps I found some on the internet downloaded them and installed them from the recovery it aqctualli did something but the problem was still there.
was it the wrong way to install it over the recovery or is it something else?
Click to expand...
Click to collapse
Be sure to download the ones suggested by CM for your Android version. Wipe /system, reinstall rom then flash gapps.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Be sure to download the ones suggested by CM for your Android version. Wipe /system, reinstall rom then flash gapps.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Thanks alot for the idea, I tried it out but sadly it didn't work, or better said it says it succesfully installed the Gapps but I dont have them...
Kyotai said:
Thanks alot for the idea, I tried it out but sadly it didn't work, or better said it says it succesfully installed the Gapps but I dont have them...
Click to expand...
Click to collapse
It might be something corrupt on your data partition then. Wipe data and start the rom fresh.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
It might be something corrupt on your data partition then. Wipe data and start the rom fresh.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Well... after wiping all data in the recovery I wanted to start up the phone again to put the roms on it again but now it gets stuck in the HTC startupscreen (the one where you see a fullbright white screen with the green HTC logo)...
Kyotai said:
Well... after wiping all data in the recovery I wanted to start up the phone again to put the roms on it again but now it gets stuck in the HTC startupscreen (the one where you see a fullbright white screen with the green HTC logo)...
Click to expand...
Click to collapse
Why would you boot to install the rom? You would flash in recovery.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Why would you boot to install the rom? You would flash in recovery.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
of course I would but I cant put the rom onto the phone via usb as long as it isn't started up (or is there a way to do this?)
Kyotai said:
of course I would but I cant put the rom onto the phone via usb as long as it isn't started up (or is there a way to do this?)
Click to expand...
Click to collapse
You could adb push the files while in recovery.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
You could adb push the files while in recovery.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
I know I know its my fault but isn't there an easier way to do this by just flashing FROM the pc with something like Odin or is this just not possible with my smartphone?
because it doesnt matter which rom I have on it later.
The reason I ask for this is, is because I never got an answer if its even possible because even setting up a connecting over adb seems like a lot of work after googling it
Kyotai said:
I know I know its my fault but isn't there an easier way to do this by just flashing FROM the pc with something like Odin or is this just not possible with my smartphone?
because it doesnt matter which rom I have on it later.
The reason I ask for this is, is because I never got an answer if its even possible because even setting up a connecting over adb seems like a lot of work after googling it
Click to expand...
Click to collapse
No system like Odin. You could run an ruu zip via fastboot and it would flash the stock image.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
No system like Odin. You could run an ruu zip via fastboot and it would flash the stock image.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
This sounds exactly like a good solution I googled around alot and found out many ways but sadly till now I havent figured out a way to make it work right now I tried out this two ways:
http://forum.xda-developers.com/showthread.php?t=2251800
and
http://forum.xda-developers.com/showthread.php?p=40712553#post40712553
I always succesfully got the phone into the RUU mode (where there is a silver HTC logo ond black ground) and then I tried flashing the stock RUU Rom but it somehow did not work I think its because my phone isnt the sprint one as suggested the problem is I have no Idea what kind of phone I have there are so freakin many when searching for the right rom I only know that I have a normal phone from Switzerland (in europa) without T-mobile sprint ATAT or whatever those things are called but there are like hundrets of versions there...
but like I said I'm going to try it out right now with another version which might be the right one gona write the feedback right after doing so.
Kyotai said:
This sounds exactly like a good solution I googled around alot and found out many ways but sadly till now I havent figured out a way to make it work right now I tried out this two ways:
http://forum.xda-developers.com/showthread.php?t=2251800
and
http://forum.xda-developers.com/showthread.php?p=40712553#post40712553
I always succesfully got the phone into the RUU mode (where there is a silver HTC logo ond black ground) and then I tried flashing the stock RUU Rom but it somehow did not work I think its because my phone isnt the sprint one as suggested the problem is I have no Idea what kind of phone I have there are so freakin many when searching for the right rom I only know that I have a normal phone from Switzerland (in europa) without T-mobile sprint ATAT or whatever those things are called but there are like hundrets of versions there...
but like I said I'm going to try it out right now with another version which might be the right one gona write the feedback right after doing so.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=60723956
That is the ruu for vzw. Use the zip to flash in ruu mode. Warning this will wipe your phone clean.
To know your phone model just type the below command and remove your info and serial from the string that prints in cmd and paste the info here. I can let you know the model through that command.
Fastboot getvar all.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
http://forum.xda-developers.com/showthread.php?p=60723956
That is the ruu for vzw. Use the zip to flash in ruu mode. Warning this will wipe your phone clean.
To know your phone model just type the below command and remove your info and serial from the string that prints in cmd and paste the info here. I can let you know the model through that command.
Fastboot getvar all.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
I tried out the getvar all command and it spit out this stuff:
http://snag.gy/weN0Z.jpg
then I went over here:
http://forum.xda-developers.com/showthread.php?t=2428276
And downloaded the first one with 6.09.401.11
But just as with the other ones it always got out the error message:
FAILED (remote: 12 signature verify fail)
Kyotai said:
I tried out the getvar all command and it spit out this stuff:
http://snag.gy/weN0Z.jpg
then I went over here:
http://forum.xda-developers.com/showthread.php?t=2428276
And downloaded the first one with 6.09.401.11
But just as with the other ones it always got out the error message:
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
You are s-on. Download a signed ruu for the cid HTC__102
Edit: try https://drive.google.com/file/d/0B17smFr95pleSFhvZHd2a0RkTFE/view?pli=1
Sent from my HTC6500LVW using XDA Free mobile app
Any luck?
Uzephi said:
Any luck?
Click to expand...
Click to collapse
Going to try it out right away
Kyotai said:
Going to try it out right away
Click to expand...
Click to collapse
Like written before I was sticking to this plan here: http://forum.xda-developers.com/showthread.php?t=2251800
And this is the whole outcome:
http://snag.gy/86bjp.jpg
the sending sparse zip and stuff never showed up before but it still gave out error messages and I dont know why...
Unfortunately if an ruu won't work, the next thing you can do it adb. It isn't that scary or difficult. Below is a very detailed guide that simplifies it. It helps you install ADB to your PC and gives the basic commands you can do. The one you want is: adb push filename /directoryonandroid while in recovery and it will send your rom zip to your phone then it is just a simple install.
http://forum.xda-developers.com/showthread.php?t=879701
EG: in this example the rom I want to install is in the directory c:/adb
Code:
CD C:/adb/
Adb devices
(Verbose showing the computer recognizes your phone)
Adb shell
su
Adb push rom.zip /sdcard/
(Verbose of the command working or failing)
Then you go to the root of your sdcard and install the rom like normal in recovery. Be sure you are in recovery when doing adb commands. The reason I did adb shell and su command is because I was sending a file to the root of SD and sometimes that would need root. You could try pushing the file without root.
Sent from my HTC6500LVW using XDA Free mobile app
https://developers.google.com/android/nexus/images?hl=en
Wow nice !!!
Let's Rock!
Can't wait for pure nexus to update to N
Sent from my Nexus 6P using Tapatalk
YES!
Is it possible to flash the factory image using flashfire?
Im currently using this ROM (Stock+Nougat-NRD90M Debloated-Prerooted-Odex-Busybox-Fast & Stable).
Vegeta700 said:
Is it possible to flash the factory image using flashfire?
Im currently using this ROM (Stock+Nougat-NRD90M Debloated-Prerooted-Odex-Busybox-Fast & Stable).
Click to expand...
Click to collapse
I only flash via fastboot and when going between versions I'd personally want to do a fully clean flash. Mind you I reverted to MM after trying N for a couple days, but again, I'd never flash a full factory image via Flashfire.
Vegeta700 said:
Is it possible to flash the factory image using flashfire?
Im currently using this ROM (Stock+Nougat-NRD90M Debloated-Prerooted-Odex-Busybox-Fast & Stable).
Click to expand...
Click to collapse
Unless a lot of users have certified that flashing via dlash fire works, I would recommend a clean flash via fastboot. This way you are flashing the images the most direct way possible. Doing this will also reduce possible entry points for issues.
First person to find an .mbn file in the boot.img or bootloader.img gets SO much cred.
Oh my .. Time to flashing silently
Is there a list of apps that currently don't work (or do work) with 7.0? I'm trying to switch over but there's a couple core apps that I need to know will work fine.
kaslopis said:
Is there a list of apps that currently don't work (or do work) with 7.0? I'm trying to switch over but there's a couple core apps that I need to know will work fine.
Click to expand...
Click to collapse
There's a thread called "Android N: What doesnt work" here in general
david279 said:
There's a thread called "Android N: What doesnt work" here in general
Click to expand...
Click to collapse
Most of the apps on that list that I use did not have the stated issues... None of them did.. I'm not sure if that list is up to date.
You're welcome.
I just finished flashing back to 6.0.1 and getting everything set up.
Of course now it gets released...
E30Nova said:
You're welcome.
I just finished flashing back to 6.0.1 and getting everything set up.
Of course now it gets released...
Click to expand...
Click to collapse
You aren't alone. Went back a day ago myself.
Sent from my Nexus 6P using Tapatalk
From what I've seen, this version isn't all that superb. Being on 6 isn't so bad
I've honestly had zero issues with the factory image for N. I wiped everything and clean flashed the image flat. Once I restored all my apps (around 80), so far it seems very smooth. No issues with lag in either the system or the fingerprint scanner.
I keep getting an error about not being able to find systsem.img in its package.. In thought they fixed this in the flash all script in 5.0 for factory images?
Soured Lie said:
I keep getting an error about not being able to find systsem.img in its package.. In thought they fixed this in the flash all script in 5.0 for factory images?
Click to expand...
Click to collapse
Flash-all is still broken afaik, better flash the individual img`s in fastboot.
Hey y'all,
Sorry to bother here. I looked around but couldn't find anything. I'm running NRD90M on my phone. I install TWRP and I rooted my 6P + unlocked bootloader. However I just downloaded the full image on google NRD90U. I'd like to put back my phone to stock with this new image and be able to just keep it stock and receive OTA. Can someone help me out or giving me a link where there's a tutorial. I already downloaded Fastboot/ADB and installed my drivers.
PS: It's find if it wipes everything. I just want it clean.
Thanks!
StangATX
Hello everyone.
I'm new in the forum and I'm looking for help.
Habitually I try to solve my problems by myself but this time I need your help.
I recently acquired a pixel 3. And everything works fine until I had to flash the factory image.
I find the factory image file on google dev website and I follow the instructions.
I also tried different tutos but I always have the same issues.
My pixel 3 restart but I can't turn on WiFi.
My Bluetooth is ok
Finally, it feels like the pixel is more slowly since I flash the factory image. (Setting app crash half of the time).
Is anyone had the same issues or have a solutions ?
Thanks by advance.
totib38 said:
Hello everyone.
I'm new in the forum and I'm looking for help.
Habitually I try to solve my problems by myself but this time I need your help.
I recently acquired a pixel 3. And everything works fine until I had to flash the factory image.
I find the factory image file on google dev website and I follow the instructions.
I also tried different tutos but I always have the same issues.
My pixel 3 restart but I can't turn on WiFi.
My Bluetooth is ok
Finally, it feels like the pixel is more slowly since I flash the factory image. (Setting app crash half of the time).
Is anyone had the same issues or have a solutions ?
Thanks by advance.
Click to expand...
Click to collapse
Make sure you have the latest sdk platform tools, r28.
Then download the factory image again, it might have been corrupted. Use 7zip to extract the zip file.
Flash the factory image again using the flash-all batch file. Note, this will wipe your device.
If that doesn't work then you might have a hardware issue.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Make sure you have the latest sdk platform tools, r28.
Then download the factory image again, it might have been corrupted. Use 7zip to extract the zip file.
Flash the factory image again using the flash-all batch file. Note, this will wipe your device.
If that doesn't work then you might have a hardware issue.
Click to expand...
Click to collapse
Thanks for your answer.
I will retry tonight at home.
One more detail : so I have to modified flash-all batch file ?
In some discussion I saw some people delete -w of the script.
I will inform if the process is ok
totib38 said:
Thanks for your answer.
I will retry tonight at home.
One more detail : so I have to modified flash-all batch file ?
In some discussion I saw some people delete -w of the script.
I will inform if the process is ok
Click to expand...
Click to collapse
If you delete the -w it will not wipe your device. You can try that, but if problem still is there then include the -w. Wiping your device is a better trouble shooting solution but you will have to setup your device like it was new. It's up to you.
Sent from my [device_name] using XDA-Developers Legacy app
Thanks for your support.
I just tried several flash factory image but the result is always the same.
I can't turn on wifi setting ....
Everything else seems to work.
I'm really disappointed and I don't know what to do.
It seems there is a issue with vendor.img
After my first boot, I download Es explorer and I navigate in :
'System>vendor>ECT>wifi' and it seems files are missing compare to my others devices.
Is there a way to modify the field with root permission?
Maybe you need to unlock the critical partition before flashing?
gm007 said:
Maybe you need to unlock the critical partition before flashing?
Click to expand...
Click to collapse
Hello gm007
How can I unlock the critical partition before flashing ?
Thanks by advance ?
totib38 said:
Hello gm007
How can I unlock the critical partition before flashing ?
Thanks by advance ?
Click to expand...
Click to collapse
fastboot flashing unlock_critical
Not sure if it's needed.
this will wipe ur phone same as unlocking bootloader.
gm007 said:
fastboot flashing unlock_critical
Not sure if it's needed.
this will wipe ur phone same as unlocking bootloader.
Click to expand...
Click to collapse
It's failed...
It's indicate 'Invalid argument unlock_critical'
totib38 said:
Thanks for your support.
I just tried several flash factory image but the result is always the same.
I can't turn on wifi setting ....
Everything else seems to work.
I'm really disappointed and I don't know what to do.
It seems there is a issue with vendor.img
After my first boot, I download Es explorer and I navigate in :
'System>vendor>ECT>wifi' and it seems files are missing compare to my others devices.
Is there a way to modify the field with root permission?
Click to expand...
Click to collapse
I don't know what you're seeing in the etc folder but this is what I have in the pixel 3,
jd1639 said:
I don't know what you're seeing in the etc folder but this is what I have in the pixel 3,
Click to expand...
Click to collapse
Ah .....
Ok so the vendor.img should be ok.
I'm completely lost .
Everything works except that. And the phone has just a week so I don't think it's a hardware issue.
If I don't find the solution i will keep this device in my desk ?
totib38 said:
Ah .....
Ok so the vendor.img should be ok.
I'm completely lost .
Everything works except that. And the phone has just a week so I don't think it's a hardware issue.
If I don't find the solution i will keep this device in my desk [emoji25]
Click to expand...
Click to collapse
Did the wifi work when you first got the phone? When you flashed the factory image did you wipe the device or use the flash all with the -w removed? If you wiped the device I'm guessing it is a hardware issue.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Did the wifi work when you first got the phone? When you flashed the factory image did you wipe the device or use the flash all with the -w removed? If you wiped the device I'm guessing it is a hardware issue.
Click to expand...
Click to collapse
Yes the wifi worked at the first boot.
I'm guessing I have wipe the device and that's the reason wifi there is a problem.
Is there any way to recover wifi drivers or anything else ?
What are my possibilities ?
Go on a sav and change wifi hardware ?
totib38 said:
Yes the wifi worked at the first boot.
I'm guessing I have wipe the device and that's the reason wifi there is a problem.
Is there any way to recover wifi drivers or anything else ?
What are my possibilities ?
Go on a sav and change wifi hardware ?
Click to expand...
Click to collapse
I don't know how flahing the factory image would cause the problem. But a couple of things to check. First, make sure you're using the latest sdk platform tools (fastboot and adb), r28. Then make sure you're using the correct factory image, there one for docomo or something like that which is for the Japanese variant, and redownload it in case you got something corrupted.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I don't know how flahing the factory image would cause the problem. But a couple of things to check. First, make sure you're using the latest sdk platform tools (fastboot and adb), r28. Then make sure you're using the correct factory image, there one for docomo or something like that which is for the Japanese variant, and redownload it in case you got something corrupted.
Click to expand...
Click to collapse
I will try again tonight but I have no hope
I use the last SDK platform tools r28.0.1
And I took the factory image from google devs website.
My Mac address is block on 02:00:00:00:00:00 to be more precise.
totib38 said:
It's failed...
It's indicate 'Invalid argument unlock_critical'
Click to expand...
Click to collapse
Seems you have outdated sdk try to remove and install the latest one as suggested above. Or try another pc.
gm007 said:
Seems you have outdated sdk try to remove and install the latest one as suggested above. Or try another pc.
Click to expand...
Click to collapse
It Is not because fastboot flashing unlock_critical is a command for pixel 3 XL ?
I got the pixel 3 device
totib38 said:
Hello everyone.
I'm new in the forum and I'm looking for help.
Habitually I try to solve my problems by myself but this time I need your help.
I recently acquired a pixel 3. And everything works fine until I had to flash the factory image.
I find the factory image file on google dev website and I follow the instructions.
I also tried different tutos but I always have the same issues.
My pixel 3 restart but I can't turn on WiFi.
My Bluetooth is ok
Finally, it feels like the pixel is more slowly since I flash the factory image. (Setting app crash half of the time).
Is anyone had the same issues or have a solutions ?
Thanks by advance.
Click to expand...
Click to collapse
I think you're platform-tools are not up to date. Download them from here:
https://developer.android.com/studio/releases/platform-tools
Put the facrory image in the same folder as the platform-tools and execute flash-all from there.
I thougt mine were up to date, but not everyting from the image got flashed.
With the latest platform tools everyting was ok.
rhino666 said:
I think you're platform-tools are not up to date. Download them from here:
https://developer.android.com/studio/releases/platform-tools
Put the facrory image in the same folder as the platform-tools and execute flash-all from there.
I thougt mine were up to date, but not everyting from the image got flashed.
With the latest platform tools everyting was ok.
Click to expand...
Click to collapse
Thanks for your help.
This is precisely the one I took yesterday and I always have the same issues
totib38 said:
Thanks for your help.
This is precisely the one I took yesterday and I always have the same issues
Click to expand...
Click to collapse
Then the only thing I can think of is for you to try another cable or computer.