Related
My Nexus 10 stopped working after I've transferred about 14gb of movies on it. I copied them in windows 8 when nexus was plugged in USB.
It doesn't boot pass Google logo now, doesn't even reach Nexus symbol.
I can boot device in a bootloader and load a recovery. I did wipe/factory reset and also cleaned the cache, but that didn't help to solve the problem.
I have a suspicion that a filesystem is corrupt and e2fsck needs to run and fix the problems but I don't know how to start it.
I'm running a stock 4.2.1 not rooted or unlocked.
The battery level is above 70 and devices has been charging from the wall for 2 hrs at least.
Can anyone advice something to resolve the problem?
well, you still have a warranty.
that'd be my best bet, since if you hack it and its' still broken, you *might* not have a warranty.
Did you try flashing a stock image off the forums?
Sent from my Galaxy Nexus using Tapatalk 2
Less than a month old too..
Sent from my HTC PH39100 using xda app-developers app
I would replace it. It would suck to tinker with it and find out you can't fix it and the warranty is void.
Either get it replaced, or attempt to root it and flash a new ROM. I know you said wiping didnt help, but when you unlock it does a complete wipe of EVERYTHING so it might make a difference.
THe faster option to try is obviously rooting it, the safer option is probably just to get it RMA'd
Guys, Thanks for replies and suggestions.
So what I tried to do in last few days was:
I downloaded official 4.2 stock Rom and tried to reflash it together with a bootloader. I used "fastboot" to erase all partitions first, then flashed a bootloader and then flashed Rom. I had to run "oem unlock" otherwise fastboot didn't want to perform an operation.
The tablet still doesn't work, it's stuck on Google logo on a boot stage, not even reaching nexus symbol.
I didn't try to root it and install a custom Rom, because I'm afraid that I with loose a warranty. I believe the procedure above does wipe everything possible on a filesystem so I didn't go for a custom Rom solution.
I don't see a possible solution to restore a device now so I will return it on a warranty.
jodvova said:
My Nexus 10 stopped working after I've transferred about 14gb of movies on it. I copied them in windows 8 when nexus was plugged in USB.
It doesn't boot pass Google logo now, doesn't even reach Nexus symbol.
I can boot device in a bootloader and load a recovery. I did wipe/factory reset and also cleaned the cache, but that didn't help to solve the problem.
I have a suspicion that a filesystem is corrupt and e2fsck needs to run and fix the problems but I don't know how to start it.
I'm running a stock 4.2.1 not rooted or unlocked.
The battery level is above 70 and devices has been charging from the wall for 2 hrs at least.
Can anyone advice something to resolve the problem?
Click to expand...
Click to collapse
If you want to try e2fsck look at this quote/post: http://forum.xda-developers.com/showpost.php?p=34865732&postcount=162
wptski said:
If you want to try e2fsck look at this quote/post: http://forum.xda-developers.com/showpost.php?p=34865732&postcount=162
Click to expand...
Click to collapse
As I understand I need to be rooted with a custom recovery?
Can I run "adb" under a stock recovery?
jodvova said:
Guys, Thanks for replies and suggestions.
So what I tried to do in last few days was:
I downloaded official 4.2 stock Rom and tried to reflash it together with a bootloader. I used "fastboot" to erase all partitions first, then flashed a bootloader and then flashed Rom. I had to run "oem unlock" otherwise fastboot didn't want to perform an operation.
The tablet still doesn't work, it's stuck on Google logo on a boot stage, not even reaching nexus symbol.
I didn't try to root it and install a custom Rom, because I'm afraid that I with loose a warranty. I believe the procedure above does wipe everything possible on a filesystem so I didn't go for a custom Rom solution.
Click to expand...
Click to collapse
A custom ROM wouldnt help I dont think. The procedure you did is the important part before flashing a new ROM so if it didnt work then dont bother with anything custom.
jodvova said:
As I understand I need to be rooted with a custom recovery?
Can I run "adb" under a stock recovery?
Click to expand...
Click to collapse
ADB commands are run when you are booted into the tablet if I remember right.
Now that you've installed a stock ROM, go into recovery and factory reset. This may help your bootloop issue.
Sent from my Galaxy Nexus using Tapatalk 2
Blueback22 said:
Now that you've installed a stock ROM, go into recovery and factory reset. This may help your bootloop issue.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I did that couple of times, it didn't help.
Guys,
Looks like a partition table got screwed up, because when I run e2fsck on any of partitions (system, userdata, boot), it says: "attempt to read block from filesystem resulted in short read".
Does anyone know how to fix it?
Or where can I find Nexus 10 PIT file?
jodvova said:
Guys,
Looks like a partition table got screwed up, because when I run e2fsck on any of partitions (system, userdata, boot), it says: "attempt to read block from filesystem resulted in short read".
Does anyone know how to fix it?
Or where can I find Nexus 10 PIT file?
Click to expand...
Click to collapse
Have you tried to go into stock recovery, and select the adb side load and try manually push the files like that?
Sent from my Nexus 10 using xda app-developers app
evolishesh said:
Have you tried to go into stock recovery, and select the adb side load and try manually push the files like that?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Can you elaborate here?
Which files should I push? A Rom?
I am facing the same situation and it is not going past the nexus logo screen lol. I tried flashing factory images from here in fastboot mode but its still not working. In recovery, its showing can't mount SD card even after I tried mounting SD card and i tried wiping, factory reset and nothing. SD card still can't mount also and I wonder if that is the problem. I'm try some more.
So, I just fixed it and my nexus 10 boots up and all good again. Basically in bootloader, you just need to flash the userdata.img and cache.img also from the extracted files of the factory image file as I noticed it wasn't flashing those 2 files when I just flashed/updated the image.zip file with this command fastboot -w update image-mantaray-jop40c.zip and it was only flashing the system.img, recovery.img, boot.img so I extracted this image-mantaray-jop40c.zip file and I flashed the userdata.img and cache.img files manually and rebooted and its all good again back to stock.
NeverAlwaysEver said:
So, I just fixed it and my nexus 10 boots up and all good again. Basically in bootloader, you just need to flash the userdata.img and cache.img also from the extracted files of the factory image file as I noticed it wasn't flashing those 2 files when I just flashed/updated the image.zip file with this command fastboot -w update image-mantaray-jop40c.zip and it was only flashing the system.img, recovery.img, boot.img so I extracted this image-mantaray-jop40c.zip file and I flashed the userdata.img and cache.img files manually and rebooted and its all good again back to stock.
Click to expand...
Click to collapse
Just to clarify did you use fastboot to flash userdata.img? Which command did you use "fastboot -w update userdata.img"?
Also where did you find userdata.img ???
It doesn't come in nexus 10 factory image. It only has boot, cache, recovery, system and a bootloader.
Hi guys im sort of new to the android scene and im having problems with my nexus 4, i downloaded the newest cyanogenmod nightly and flashed it, it messed up part way through. i rebooted the phone and now its just stuck at boot animation. i have wiped the cache the dalvik cache and done a factory restore.
i have tried reflashing the nightly but it stick stops part way through, i want to add the new rom to the /sdcard but i dont know how, its not showing in android file manager and i have tried using adb push command.
im sure its a noob question but any ideas?
P.s sorry i know there are posts similar to mine but tried them and wont work
If adb push won't work in recovery you might try flashing the factory images with fastboot. System.img is really all you'd need.
estallings15 said:
If adb push won't work in recovery you might try flashing the factory images with fastboot. System.img is really all you'd need.
Click to expand...
Click to collapse
sorry i have no idea how to do that, i just need to access the file system so i can dump a rom to install
AW: [Q] Nexus 4 wont work after new cyanogenmod update
You can try to sideload a new ROM via 'adb sideload' in the recovery.
Sent from my Nexus 4 using xda premium
TobiS87 said:
You can try to sideload a new ROM via 'adb sideload' in the recovery.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
i have tried to side load a rom onto it but that didnt work adb gave a error
http://forum.xda-developers.com/showthread.php?t=2010312
Follow the steps, but only flash the system.img. Once it boots, move your ROM over. Reboot into recovery. Flash.
Hopefully this helps people in my situation.
So on the first day of having my nexus 7 i found a way to have no OS and 0MB internal storage showing in TWRP. Yah i suck.
I tried tons of things but knew a system image was needed.
HOW: I was about to flash the superuser root for 4.3 newly released and forgot to put it on nexus so i then proceeded to exit TWRP, however upon exiting TWRP the recovery detected i havent installed supersu and asked do i want to install superuser? I though why the hell not!
I confirmed to install superuser and then tried to reboot but for 20 minutes device could not boot. TWRP showed 0MB internal storage and pushing adb files in this state yielded nothing as there was no directory
This is how i managed to have a working tablet again
1. FORMAT DATA in TWRP - after doing this your internal storage should be back and not show 0MB
2. reboot to the bootloader
3. On your computer download this file kindly given to us by phuduong and uploaded by Nburnes
https://mega.co.nz/#!PBIiEbBJ!bKpdHxegOVlde12nsu_ulEyRq7UsANLLQab1IZjLIGc
Credit to Nburnes http://forum.xda-developers.com/member.php?u=2918596[/QUOTE]
4. Once downloaded move that system.img file to your adb directory
5. With you nexus 7 in the bootloader, adb open, and file downloaded copy and paste this command into adb terminal
fastboot flash system system.img
6. Now you have an OS but it still would loop and wouldnt start
7. Boot into recovery and Format Data again, because for me 0MB interal storage was back again
8. Then Factory Reset
FINALLY YOUR DEVICE SHOULD BE BACK TO ITS ORIGINAL STATE!!!!!
Is that the factory image? Have you tried going from unlocked bootloader & rooted back to factory using that image?
plbelanger said:
Is that the factory image? Have you tried going from unlocked bootloader & rooted back to factory using that image?
Click to expand...
Click to collapse
Google has yet to release the official factory image for the new N7. However, a kind user was gracious enough to make their own. It is likely to be almost identical to what Google will eventually release and should work the same way.
Thank you! Thank you!
good stuff OP. glad you got it working again
You all are life savers! 1000X Thanks!
I tried running through this, but it didn't work for me. I think my situation is different though because I tried to install a factory image for the 2012 nexus, and during part of that process I ran the "flash-all" script which starts by deleting boot, cache, recovery, userdata, and system.
I think deleting boot screwed me up, because even though I can go into recovery now after reinstalling twrp and I can restore my system using system.img, I still can't boot (get stuck on the google logo). Any way to fix that?
So you first tried to restore from the OLD Nexus 7 Image?????
Sent from my Nexus 7 using xda app-developers app
petersellers said:
I tried running through this, but it didn't work for me. I think my situation is different though because I tried to install a factory image for the 2012 nexus, and during part of that process I ran the "flash-all" script which starts by deleting boot, cache, recovery, userdata, and system.
I think deleting boot screwed me up, because even though I can go into recovery now after reinstalling twrp and I can restore my system using system.img, I still can't boot (get stuck on the google logo). Any way to fix that?
Click to expand...
Click to collapse
So you first tried to restore the OLD nexus 7 factory image? Probably gonna have to wait for factory image or exchange yours
Sent from my Nexus 7 using xda app-developers app
jporter396 said:
So you first tried to restore from the OLD Nexus 7 Image?????
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I tried to restore from the old image. Obviously fastboot wont let you install the old image, but I didn't realize that until boot, system, cache, etc. were deleted
THANK YOU!!!
This worked perfectly! I had a wiped system folder (no ROM), and obviously no USB debugging enabled. And with the lack of a factory image, I've been counting seconds to seeing somebody post this!
Just follow the instructions carefully. Thank you guys!
petersellers said:
Yes, I tried to restore from the old image. Obviously fastboot wont let you install the old image, but I didn't realize that until boot, system, cache, etc. were deleted
Click to expand...
Click to collapse
You can flash old and new image through fastboot. I did 2 times ^_^
This is boot.img for who need
BOOT.IMG HERE
It gives me a fail when I try to wipe data.
Edit: never mind
jarjar124 said:
It gives me a fail when I try to wipe data.
Edit: never mind
Click to expand...
Click to collapse
How did you fix it? I still cant wipe data.
Balsta said:
How did you fix it? I still cant wipe data.
Click to expand...
Click to collapse
Have you formatted first?
Sent from my Nexus 7 using xda app-developers app
jporter396 said:
Have you formatted first?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I can't, get an error with that too
Sent from my SCH-I545 using Tapatalk 4 Beta
OP and nburnes saved my butt!
I did this and now it seems my device is booting and it shows up as N7 when I attach it to my PC. But the display shows nothing at all. It just goes blank after the Google screen. Any ideas?
After flashing everything I could think of and banging my head and the device against the wall for two hours, I finally got it to work. Not sure how exactly but the last thing I did was reflashing bootloader. So if anyone has the same problem, try that.
Thank you.
Note:
Give step 6 a little time be patient.
All main JSS15J .IMGS here: http://forum.xda-developers.com/showthread.php?t=2381438
Glad this helped some of you guys!
Earlier today my phone was working fine running Stock 4.4.1/Kernel. I decided I wanted to get the franco kernel so I got the .img file from the xda thread. I flashed the .img file onto the boot partition using fastboot, and restarted my phone. After a few minutes of sitting at the "Google" screen I rebooted into the bootloader. I tried flashing the 4.4 factory image using the "flash-all.bat" without wiping anything. My phone continued to get stuck at the "Google" screen after multiple reboots. I then tried to wipe my device using fastboot. However, when using the command "fastboot erase system" I got an error that said "Failed: unknown chunk type." I kept on retrying the wipe to no avail. I found this thread: http://forum.xda-developers.com/showthread.php?t=2347060 and followed the steps. All the steps seemed to work up until I had to flash the given factory image using fastboot. I got the same "Unknown chunk type" when the cmd was trying to write files to the "system partition." Before you ask, yes my fastboot/adb is updated to the newest version. (I triple checked) And all my drivers work properly. I just flashed the 4.4.1 firmware 3 days ago using fastboot and everything went perfectly, including the wipe. Please offer any solutions you think could get me out of this situation. Thank you.
PandemicHD said:
Earlier today my phone was working fine running Stock 4.4.1/Kernel. I decided I wanted to get the franco kernel so I got the .img file from the xda thread. I flashed the .img file onto the boot partition using fastboot, and restarted my phone. After a few minutes of sitting at the "Google" screen I rebooted into the bootloader. I tried flashing the 4.4 factory image using the "flash-all.bat" without wiping anything. My phone continued to get stuck at the "Google" screen after multiple reboots. I then tried to wipe my device using fastboot. However, when using the command "fastboot erase system" I got an error that said "Failed: unknown chunk type." I kept on retrying the wipe to no avail. I found this thread: http://forum.xda-developers.com/showthread.php?t=2347060 and followed the steps. All the steps seemed to work up until I had to flash the given factory image using fastboot. I got the same "Unknown chunk type" when the cmd was trying to write files to the "system partition." Before you ask, yes my fastboot/adb is updated to the newest version. (I triple checked) And all my drivers work properly. I just flashed the 4.4.1 firmware 3 days ago using fastboot and everything went perfectly, including the wipe. Please offer any solutions you think could get me out of this situation. Thank you.
Click to expand...
Click to collapse
Never encountered something like this, but maybe from bootloader u can get into ur stock recovery & wipe cahce & wipe data.
once again I never had that issue...so its upto u...but might be worth a try...if u had made a backup or dont care about the data in ur phone then it did be easier for u u to try
Flash the factory images and erase all partitions on the device. If you want to get some data from the internal memory you could pull it through recovery. Next time read more do less. Franko's kernel uses different ram disk than the stock one. You could also try to flash a full stock kernel for your build first. Get it from the factory images and flash it through fastboot.
Sent from my Nexus 4 using xda app-developers app
i have the exact same problem here ! and i dont know what to do! its still stucked on the google logo!!!
alexvck said:
i have the exact same problem here ! and i dont know what to do! its still stucked on the google logo!!!
Click to expand...
Click to collapse
What's the exact same problem? Did you flash Franko kernel too. If so just dirty flash your current rom.
jd1639 said:
What's the exact same problem? Did you flash Franko kernel too. If so just dirty flash your current rom.
Click to expand...
Click to collapse
no i just had rooted it and loadedcwm and i was ready to flash paranoid anroid rom! and when it rebooted it stuck on the google logo! then i tried to reset my phone and load the official factory image with nexus root toolkit but when it did the usual procces with the command prmpt in some point after trying to write the new system it said "Failed: unknown chunk type." ! after that it rebooted and got stucked again in google logo!!
alexvck said:
no i just had rooted it and loadedcwm and i was ready to flash paranoid anroid rom! and when it rebooted it stuck on the google logo! then i tried to reset my phone and load the official factory image with nexus root toolkit but when it did the usual procces with the command prmpt in some point after trying to write the new system it said "Failed: unknown chunk type." ! after that it rebooted and got stucked again in google logo!!
Click to expand...
Click to collapse
Use this to flash the factory image http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
jd1639 said:
Use this to flash the factory image http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
my device is bricked i cant do these stuff :/
alexvck said:
my device is bricked i cant do these stuff :/
Click to expand...
Click to collapse
Can you get into bootloader mode. It's worth a try. Your not bricked if it can turn on. Your emmc may be bad and flashing the factory image won't work. But if that's the case then warranty or replacement are your only options.
jd1639 said:
Can you get into bootloader mode. It's worth a try. Your not bricked if it can turn on. Your emmc may be bad and flashing the factory image won't work. But if that's the case then warranty or replacement are your only options.
Click to expand...
Click to collapse
yes i can get in bootloader! but i cant do sth :/ ... whats the emmc ?!
Originally Posted by jd1639<br />
Can you get into bootloader mode. It's worth a try. Your not bricked if it can turn on. Your emmc may be bad and flashing the factory image won't work. But if that's the case then warranty or replacement are your only options.
Click to expand...
Click to collapse
<br />
<br />
yes i can get in bootloader! but i cant do sth :/ ... whats the emmc ?!
Click to expand...
Click to collapse
Emmc is the flash memory.
jd1639 said:
Emmc is the flash memory.
Click to expand...
Click to collapse
oo okay.. so is there sth else that i can try?!
alexvck said:
oo okay.. so is there sth else that i can try?!
Click to expand...
Click to collapse
have you tired the the toolkits?
I had problem with flash system.img, solved changing usb port. I hope help you.
Inviato dal mio Nexus 4 utilizzando Tapatalk
I'm currently having a boot loop problem on my nexus 10 device, where the boot animation goes on forever.
I was on android 5.01, then downloaded 5.1.
I Followed the instructions to apply the upgrade and everything look like it was fine. Tried to reboot the device and all I get is the spinning balls.
I didn't want to lose my data/wipe the device so I DID NOT use the -w command on the fastboot update command. I've done that before and it worked.
Can you someone give me advice on how to fix the problem.
Also, can it be fixed without doing a factory reset?
Thanks
bflatmajor said:
I'm currently having a boot loop problem on my nexus 10 device, where the boot animation goes on forever.
I was on android 5.01, then downloaded 5.1.
I Followed the instructions to apply the upgrade and everything look like it was fine. Tried to reboot the device and all I get is the spinning balls.
I didn't want to lose my data/wipe the device so I DID NOT use the -w command on the fastboot update command. I've done that before and it worked.
Can you someone give me advice on how to fix the problem.
Also, can it be fixed without doing a factory reset?
Thanks
Click to expand...
Click to collapse
How long did you let the boot go for? The first boot takes a REALLY LONG time.
over 15 minutes..
Im rebooting it now.. lets see what happens
after more than 30 minutes, still no change in behavior
bflatmajor said:
over 15 minutes..
Im rebooting it now.. lets see what happens
after more than 30 minutes, still no change in behavior
Click to expand...
Click to collapse
You wouldn't happen to have an old ROM on your device would you? If so, maybe flash that and see if you can at least boot. If you can't even boot you may have to do a full wipe.
bflatmajor said:
I'm currently having a boot loop problem on my nexus 10 device, where the boot animation goes on forever.
I was on android 5.01, then downloaded 5.1.
I Followed the instructions to apply the upgrade and everything look like it was fine. Tried to reboot the device and all I get is the spinning balls.
I didn't want to lose my data/wipe the device so I DID NOT use the -w command on the fastboot update command. I've done that before and it worked.
Can you someone give me advice on how to fix the problem.
Also, can it be fixed without doing a factory reset?
Thanks
Click to expand...
Click to collapse
I noticed this has happened to me before when I would flash all the images (except userdata) and elect to only erase cache, and not flash the cache image. It would be stuck in the bootanimation forever. Once I started flashing the cache image when upgrading, I've never had an issue since. So my advice to you is to flash the cache image from the factory image and see if that fixes it. All your data will still be intact.
charesa39 said:
I noticed this has happened to me before when I would flash all the images (except userdata) and elect to only erase cache, and not flash the cache image. It would be stuck in the bootanimation forever. Once I started flashing the cache image when upgrading, I've never had an issue since. So my advice to you is to flash the cache image from the factory image and see if that fixes it. All your data will still be intact.
Click to expand...
Click to collapse
How did you do this exactly? My phone is in that exact cycle...
gundamslicer said:
How did you do this exactly? My phone is in that exact cycle...
Click to expand...
Click to collapse
You may also need to wipe dalvik if you have not tried that already.
The factory cache image is in the same zip file with system.img, boot.img, etc. You need to boot back to fastboot and do
Code:
fastboot flash cache <path_to_cache_image>
I recently upgraded to 5.1 by flashing only system.img and boot.img and wiping only cache and dalvik and I didn't have any issues.
gundamslicer said:
How did you do this exactly? My phone is in that exact cycle...
Click to expand...
Click to collapse
I usually follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. Obviously, just make sure you have the correct factory image files for the Nexus 10. MAKE SURE NOT TO FLASH USERDATA. If you do, you will wipe your device and you will lose all your data. So I always just skip that command when I'm flashing the image files. After you're done flashing the cache image, just unplug your device and select "Start" from the bootloader menu. It will boot up normally and then you will see the "Android upgrading app ## of ##" message. That means everything worked.
Same problem happened with me. After applying the ota update for 5.1, I got locked in the boot animation.
Tried to reinstall the 5.1 manually, same thing happened.
I also tried to downgrade to 5.0.2 and 5.0.1 with no lucky. Now the tablet is useless.
Anyone else is experiencing this problem. Any suggestion to solve it?
luizm.jr said:
Same problem happened with me. After applying the ota update for 5.1, I got locked in the boot animation.
Tried to reinstall the 5.1 manually, same thing happened.
I also tried to downgrade to 5.0.2 and 5.0.1 with no lucky. Now the tablet is useless.
Anyone else is experiencing this problem. Any suggestion to solve it?
Click to expand...
Click to collapse
How are "reinstalling 5.1 manually"? Are you following the steps (Method 2) in the link I posted in the post above yours?
No. I ran the batch on the original rom downloaded from google.
Sent from my HTC One_M8 using XDA Free mobile app
luizm.jr said:
No. I ran the batch on the original rom downloaded from google.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Ah. That's what I had thought. That could be your problem right there. Unfortunately, the batch process hasn't worked properly since 5.0. Not sure if Google fixed this with 5.1, but I doubt it. Try flashing all of the images manually. DON'T FLASH USERDATA, unless you don't care about losing your data.
charesa39 said:
Ah. That's what I had thought. That could be your problem right there. Unfortunately, the batch process hasn't worked properly since 5.0. Not sure if Google fixed this with 5.1, but I doubt it. Try flashing all of the images manually. DON'T FLASH USERDATA, unless you don't care about losing your data.
Click to expand...
Click to collapse
I followed the method 2 and flashed everything except userdata and radio (bootloader, system, boot, recovery and cache). Still locked in the boot animation.
I noted that before accepting any flash command I sent, Nexus screen displayed "FASTBOOT STATUS - FAIL Invalid Partition". But at the end of flash it was displayed "FASTBOOT STATUS - OKAY"
luizm.jr said:
I followed the method 2 and flashed everything except userdata and radio (bootloader, system, boot, recovery and cache). Still locked in the boot animation.
I noted that before accepting any flash command I sent, Nexus screen displayed "FASTBOOT STATUS - FAIL Invalid Partition". But at the end of flash it was displayed "FASTBOOT STATUS - OKAY"
Click to expand...
Click to collapse
Hmm. That invalid partition message is odd. Were you stock before? Did the command window show "OKAY" after each image was flashed? I'm wondering if your userdata partition is messed up as well. Not sure if all your stuff is backed up, but I would probably flash everything again, including userdata to start fresh. Obviously, you would lose all your data.
I never had unlocked the bootloader before in this device.
Yes, I got an OKAY after every flash. But also the invalid partition message at the beginning.
I'll try to flash everything again, including user data and let you know.
Thanks
Sent from my HTC One_M8 using XDA Free mobile app
It worked! However I lost all my data. I thought the new lollipop cloud backup would restore the app data but it was a fresh install for everything including the Google Now launcher.
Thanks
Sent from my HTC One_M8 using XDA Free mobile app
luizm.jr said:
It worked! However I lost all my data. I thought the new lollipop cloud backup would restore the app data but it was a fresh install for everything including the Google Now launcher.
Thanks
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
That sucks about losing your data... But at least you have a functioning N10 now. :good: I'm thinking the data partition may have somehow got corrupted, which is why it wasn't completing the boot process. Glad it worked out for you in the end though.