Database Users

Xoom memory/flash LOCKED ???

Ok i will explain ...
Got my Xoom ROOTED but decided to put it back to stock, so I UNROOTED by flashing my Canadian 3.0 version, boot it up update to the 3.1 OTA and then setup my market, the XOOM FC out alot so i want to try "hacked firmware".
Boot to fastboot to flash CWM recovery, all the flash show completed OK, reboot into recovery to only found out that it's not there ... ok, try factory reset from the Recovery, all good and then the Xoom reboot ... all my data is still there, then try Setting > Private > factory reset ... all OK, but can boot into the Recovery to fully reset ... no problem, i will reflash a different version via Fastboot.
Try the US-Wifi version, all the flash/erase when OK but still at Canadian 3.1 ... then try installing ROM manager, install fine and working (of cause no Root access). Reboot and the ROM manager is gone ...
Look like the Memory of the Xoom somehow is LOCKED?
Anyone have a idea? i'm taking out the battery for 1h now and hope to have some reaction ... but still nada!!!
Help!!! Thanks

y2k-inc said:
Ok i will explain ...
Got my Xoom ROOTED but decided to put it back to stock, so I UNROOTED by flashing my Canadian 3.0 version, boot it up update to the 3.1 OTA and then setup my market, the XOOM FC out alot so i want to try "hacked firmware".
Boot to fastboot to flash CWM recovery, all the flash show completed OK, reboot into recovery to only found out that it's not there ... ok, try factory reset from the Recovery, all good and then the Xoom reboot ... all my data is still there, then try Setting > Private > factory reset ... all OK, but can boot into the Recovery to fully reset ... no problem, i will reflash a different version via Fastboot.
Try the US-Wifi version, all the flash/erase when OK but still at Canadian 3.1 ... then try installing ROM manager, install fine and working (of cause no Root access). Reboot and the ROM manager is gone ...
Look like the Memory of the Xoom somehow is LOCKED?
Anyone have a idea? i'm taking out the battery for 1h now and hope to have some reaction ... but still nada!!!
Help!!! Thanks
Click to expand...
Click to collapse
When you flashed the stock Canadian images did you relock your bootloader?
If you followed Moto's instructions completely it ends with relocking.
It sounds like you need to unlock again and go from there. You will still get the OTA updates if you are unlocked as long as you are completely stock, if that's what you're worried about.

okantomi said:
When you flashed the stock Canadian images did you relock your bootloader?
If you followed Moto's instructions completely it ends with relocking.
It sounds like you need to unlock again and go from there. You will still get the OTA updates if you are unlocked as long as you are completely stock, if that's what you're worried about.
Click to expand...
Click to collapse
Yup! Locked up so i can get OTA, since instruction are differences from person to person ... now, no mater if i unlocked it, it's look like the memory locked out ... like i have copy some files over it, and upon shutdown and restart, the file are gone on the Xoom ... it's like your CMOS on your computer only save data when it on power but lost when you shut it down (is there a backup battery on XOOM?)
Thanks

please .... any one?

Start over from scratch. If you want stock U.S. then use the U.S. stock imgs. Make sure that you use no Canadian imgs. If you want Canadian use the Canadian stock imgs. It looks like you flashed the wrong files together. I see people flashing U.S. stock then trying to root with their country imgs and it messes up. Use adb and fastboot flash moto stock imgs again, boot img, recovery img, system, erase cache, etc. Just remember if you use canadian, the you have to root with a Canadian file as well.
Sent from my Xoom using xda premium

hammer4203 said:
Start over from scratch. If you want stock U.S. then use the U.S. stock imgs. Make sure that you use no Canadian imgs. If you want Canadian use the Canadian stock imgs. It looks like you flashed the wrong files together. I see people flashing U.S. stock then trying to root with their country imgs and it messes up. Use adb and fastboot flash moto stock imgs again, boot img, recovery img, system, erase cache, etc. Just remember if you use canadian, the you have to root with a Canadian file as well.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Been there, done that the fastboot flash toke all the flash steps but after it's just "like reversed back" to the original one ... i can even ERASE everything with fastboot and the Xoom still boot up with the "old image" is there a "Short or reset button" on the Motherboard? i have toke out the battery for 10h now
Thx

Sounds like you have not changed the files in your tools folder. I use a seperate folder for stock and root. Keeps me from flashing a file wrong. Make sure that is not happening. Did you try and oem unlock and reboot, then go back to fastboot and flash?
Sent from my ADR6400L using xda premium

done that but not work
C:\SDK_tools>fastboot oem unlock
... INFO To continue, follow instructions on the device's display...
OKAY [ 52.261s]
finished. total time: 52.261s
C:\SDK_tools>fastboot erase boot
erasing 'boot'... OKAY [ 0.289s]
finished. total time: 0.289s
C:\SDK_tools>fastboot erase system
erasing 'system'... OKAY [ 0.366s]
finished. total time: 0.366s
C:\SDK_tools>fastboot erase recovery
erasing 'recovery'... OKAY [ 0.294s]
finished. total time: 0.294s
C:\SDK_tools>fastboot -w
erasing 'userdata'... OKAY [ 13.663s]
erasing 'cache'... OKAY [ 0.529s]
finished. total time: 14.192s
C:\SDK_tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.637s]
writing 'boot'... OKAY [ 0.586s]
finished. total time: 1.224s
C:\SDK_tools>fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 16.741s]
writing 'system'... OKAY [ 7.270s]
finished. total time: 24.011s
C:\SDK_tools>fastboot flash recovery recovery.img
sending 'recovery' (12288 KB)... OKAY [ 0.894s]
writing 'recovery'... OKAY [ 3.590s]
finished. total time: 4.485s
C:\SDK_tools>fastboot flash userdata userdata.img
sending 'userdata' (139233 KB)... OKAY [ 8.946s]
writing 'userdata'... OKAY [ 8.166s]
finished. total time: 17.113s
C:\SDK_tools>fastboot erase cache
erasing 'cache'... OKAY [ 3.215s]
finished. total time: 3.215s
C:\SDK_tools>fastboot oem lock
... INFO To continue, follow instructions on the device's display...

Looks like this line:
C:\SDK_tools>fastboot oem lock
... INFO To continue, follow instructions on the device's display...
might be the cause of your problem. I think if you lock you can't write.

cadiken said:
Looks like this line:
C:\SDK_tools>fastboot oem lock
... INFO To continue, follow instructions on the device's display...
might be the cause of your problem. I think if you lock you can't write.
Click to expand...
Click to collapse
Yes, why lock?

Yep if you lock you can't flash. Go in and fastboot OEM unlock. Then you can update.
Sent from my Xoom using xda premium

problem is not if the Xoom is locked or not, i have tried all possibilities so far, but some place they tell to lock it for OTA.

If it is locked you can't load any cwm or custom firmware.
Sent from my ADR6400L using xda premium

Do you means the bootloader is locked? event "fastboot oem unlock" show successful unlock?
Please elaborate?
I wish there is nvflash that you can use like the Gtablet

Yeah bootloader locked. But if it says unlocked then try a different rom.
Sent from my ADR6400L using xda premium

I have done all the Fastboot things without luck, bootloader version 1045 if anyone know how this is can be fix?
like i said, all fastboot command response with success ... so only way now is to see how can i short the memory to wipe out and restart ... any idea?
Thx

I will clear something up for you. You absolutely do NOT need to lock the bootloader for a ota.
In fact there really is NO reason to re lock the bootloader unless you are sending it for repairs.
Where over or who ever said to re lock it you should ignore them from now on.

albundy2010 said:
I will clear something up for you. You absolutely do NOT need to lock the bootloader for a ota.
In fact there really is NO reason to re lock the bootloader unless you are sending it for repairs.
Where over or who ever said to re lock it you should ignore them from now on.
Click to expand...
Click to collapse
thanks for the heads up ... i think it's needed a jtag now

anyone know how to get the SFU file out from a working Xoom so it can be used be RSD Lite for restoring?

Possible Bricked Tablet - Please Help!

I think i may have bricked my nexus 10.. I was trying to install the chainfire3d application from the market, and when it rebooted, it wouldnt go past the X logo. waited for a long time, so i tried a hard reset, and still nothing. So i figured i would try using the toolkit to help fix. tried to relock, flash, and re-unlock, and it wouldnt work..after the step where you go into factory reset/wipe, it woudlnt go further. I cant get a custom recovery to install, it wont save the file. tried doing that step separately, and it seems to stick on sending the file over. this seems to be a common issue with anything i try.
The screen says:
"sending TWRP touch recovery..
sending 'recovery' (7246 KB) ...
and is just stuck there. this seems to happen in several places, with a few different things ive tried. When trying to flash the stock image, it will get stuck in similar places, perhaps not with the recovery step, but with a portion of the stock image. Been at this for a couple of hours... any help would be greatly appreciated!.
Also, as of now... it wont boot past the google logo. I can get it into fastboot by holding down the buttons, and I can get it into the stock recovery, but thats it. I don't even think adb is detecting the device. I have a feeling that may be a major roadblock to getting this thing fixed. Does anyone know how I can get the tablet to be detected by adb if i cant even get past the google logo screen at boot?
Update 1:
Still cant unbrick my device. any time i try to transfer or flash files to it... it stalls, and if i disconnect the device, i get this error:
FAILED (data transfer failure (too many links)).
Your Device will now boot into Android and detect ADB mode.
problem is, it doesnt reboot, and even if it did, it wouldnt be able to boot into android, since it wont go past the google logo when the device turns on. in fact, i cant even turn it off. only way to turn it off would be to wait for the battery to drain.
If this helps, here is what it says on the fastboot screen:
Device Information
Product Name: manta
Variant: wifi
H/W version : 8
Bootloader Version: MANTALJ12
Carrier Info: none
Serial Number: *********** (not going to publish that, lol)
LOCK STATE: Unlocked
Reboot Mode Flag: none.
anyone have any ideas at all how I can salvage this thing? Im kindof embarrassed honestly. Ive had 5 android devices prior to this one, and have rooted, flashed, and reflashed each of them countless times, and never, ever ran into this before. I could really use the help.
Quick note:
I just noticed that when i try to flash anything to the tablet, the following appears under the rest of the info i listed above.
FASTBOOT STATUS - DATA00713800 (this text is highlighted in light blue)
Update 2:
ok, so i tried to do the factory restore, and am running into the same wall as always. here is the text from the window, perhaps that may clue you into the problem:
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.tg
z
Extracting mantaray-jop40c-factory-0d641789.tar
Everything is Ok
Size: 329369600
Compressed: 326396069
Now extracting flashable Images
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.ta
r
Extracting mantaray-jop40c
Extracting mantaray-jop40c\image-mantaray-jop40c.zip
Extracting mantaray-jop40c\flash-base.sh
Extracting mantaray-jop40c\bootloader-manta-mantalj12.img
Extracting mantaray-jop40c\flash-all.sh
Extracting mantaray-jop40c\flash-all.bat
Everything is Ok
Folders: 1
Files: 5
Size: 329358105
Compressed: 329369600
Factory Images extracted. Starting Flash Process.
Now Flashing Bootloader Image..
sending 'bootloader' (1280 KB)... OKAY [ 0.232s]
writing 'bootloader'... OKAY [ 0.113s]
finished. total time: 0.345s
rebooting into bootloader... OKAY [ 0.001s]
finished. total time: 0.001s
Now Flashing Factory Image: Boot, Cache, Recovery, System and Userdata..
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product... OKAY [ 0.001s]
checking version-bootloader... OKAY [ 0.002s]
sending 'boot' (4606 KB)...
Its just stuck on that last part, sending 'boot' (4606 KB)...
and under all the info on the fastboot page, the following appeared while this was happening:
FASTBOOT STATUS - DATA0047f800 (this line is highlighted in light blue)

*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)

cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
can you link it?

cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
trying that....
so far so good... dont want to get my hopes up though... below is what ive got so far in the cmd screen:
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...

Its been about 30 minutes now... and its still stuck on "sending 'system' (528847 KB)..." in the cmd window.... not sure what that means... it did take about a minute for the recovery to get sent over, and its about 100x larger in size, so i guess i will leave it connected like this for the next hour or so... and hope that it is just going REALLY slowly. Got my fingers crossed...

Battery died while waiting.... this is the complete text of the CMD screen while i was waiting.. forgot that it doesnt charge while in fastboot. got it plugged into an outlet for faster charging while its off.... hopefully when its charged up, i can try again and ill continue to progress
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 3941.094s
Press any key to exit...

Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.

jodvova said:
Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.
Click to expand...
Click to collapse
I cant get it to load a custom recovery! any advice on how to get that going?

ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.

ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
Dumb question, if using a desktop PC are you using the front or rear USB ports? I had a similar issue where it would just get stuck on the "sending system" message. Switched the USB from front port to back port on my linux box and it solved my problem.
Sent from my Nexus 10 using Tapatalk 2

jodvova said:
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.
Click to expand...
Click to collapse
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.

ltracte said:
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.
Click to expand...
Click to collapse
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.

jodvova said:
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.
Click to expand...
Click to collapse
couldnt get the command to work via adb, so i tried it using terminal inside TWRP, and this what it spit back at me:
/dev/block/platform/dw_mmc.0/by-name/system: clean. 11/51296 files. 6651/204800 blocks
i have no idea what that means, nor what else to do....

Fixed it!!!!

ltracte said:
Fixed it!!!!
Click to expand...
Click to collapse
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.

mskip said:
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.
Click to expand...
Click to collapse
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!

Whew! So glad you finally had success & thanks for sharing. I'm reading up, research, etc. I received my N10 yesterday. I'm getting ready to unlock/root today.
Sent from my Nexus 7 using Tapatalk 2

ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
Hmm, did you try the flash-all.bat file that comes with the factory image? It does those 3 commands, + erases all partitions automatically.

ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
That's exactly what I did. Just followed the factory image flashing instruction on google's page(where you download the image file for N10). Did you figure out why it wassnt able to transfer the first time?

Marshmallow factory images are available.

Yeah, I think the title is enough. The factory images are live now for volantis and volantisg. Maybe we can collect here some first impressions. I am unfortunately not able to flash atm.

https://developers.google.com/android/nexus/images

Flash-all script worked like a charm, setting everything up right now

But it's not February yet.

maarten08 said:
Flash-all script worked like a charm, setting everything up right now
Click to expand...
Click to collapse
Cool man , I'm waiting for your review, , but I'm sure to flash this into my N9 tomorrow . I'm just too eager to wait any longer

Good thing I reverted my n9 back to stock. Will flash tonight. No Ota also.

Flash.sh fail
maarten08 said:
Flash-all script worked like a charm, setting everything up right now
Click to expand...
Click to collapse
Mine fails at sending 'system' (2245234 KB)...
FAILED (remote: data length is too large)
Trying to do a manual flash now... we'll see!

I'll be flashing my 9 tonight too.
I kept my 6 on Lollipop rather than running the preview on it, but yesterday I did flash the preview so that it would use M's auto backup. That way I can flash it this week and not worry about signing into apps.....which is nice during tax season.

PhoenixIce22 said:
Mine fails at sending 'system' (2245234 KB)...
FAILED (remote: data length is too large)
Trying to do a manual flash now... we'll see!
Click to expand...
Click to collapse
Do u have latest fastboot? That error was happening to others because of old fastboot. Otherwise maybe just make sure the hash matches and u have a good download and usb debugging is on.
Sent from my SM-G900V using Tapatalk

Anybody tried flashing yet? I keep getting 'system cannot be loaded' error whilst carrying out manual flash. i.e. fastboot flash system system.img etc etc

I flashed each .IMG file separately, formatted date to remove encryption, flashed TWRP, flashed fed-patcher them FIRE-ICE kernel. Running great here

I was on 5.1.1 (Latest Image). I applied the 6.0 update, now I am just sitting at the black Google Screen and it won't boot. Any suggestions???

Diesel779 said:
I flashed each .IMG file separately, formatted date to remove encryption, flashed TWRP, flashed fed-patcher them FIRE-ICE kernel. Running great here
Click to expand...
Click to collapse
Do u need fed patcher if u flash a kernel that does not force encryption? I thought you wouldn't. Haven't tried it though.
Brian
Sent from my SM-G900V using Tapatalk

Is the installing process for rooted devices the same as for the former builds?
like here:
http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
How To Flash the Factory Image, LONG METHOD
In this method each factory image is flashed separately. This should be used if you have problems with the short method and as you get more familiar with fastboot you’ll be able to flash only the images that you need for your specific requirement. For instance, you might want to only flash the stock recovery if you’re trying to take an ota and you’ve installed a custom recovery. The order that you flash the images is not important.
In the folder you extracted the factory image it’s easiest if you re-name the bootloader image file to simply bootloader and radio. Then open a Windows command window in that folder and use the fastboot commands:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w (NOTE, this command does wipe your device. It’s possible to flash the factory image without this command but if you’re going from different revision numbers of android it’s highly recommend to wipe the device)
Now open a Windows command window in the same folder that you extracted the zip file in, the one where you find recovery, system, etc. Then run the fastboot commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img [Note, flashing system takes a long time, so let it do it's thing]
fastboot flash vendor vendor.img

gt43aw said:
Do u need fed patcher if u flash a kernel that does not force encryption? I thought you wouldn't. Haven't tried it though.
Brian
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
You don't need FED patcher if you flash an already un-force-encrypted kernel. FED patcher just takes the stock kernel and un-force-encrypts it.

Haven't updated my flashing VM in a while, so likely not. I know my ADB is 1.0.32, not sure what version of fastboot I have on there. I'm a bit of a Ubuntu noob, so I'm doing lots of web researching, LOL

Be sure to update the bootloader if getting a system partition size error! For M-preview this went from 3.44.1.0123 (LMY48M) to 3.48.0.0135 (confirmed the factory image is still this for MRA58K)... Otherwise you get system partition size errors (BIG update).
I will be making a rooted/no-force-encrypt ROM and kernel as soon as I see the newer manifests on googlesource... I am assuming selinux to permissive is still required for root. Once you have it unpacked:
fastboot flash bootloader bootloader-flounder-3.48.0.0135.img
fastboot reboot-bootloader
Then flash the system and boot images:
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot flash system system.img
DO NOT DO THIS if your device is using a no-force-encrypt kernel! You WILL have to factory reset! Back up OFF the device to a PC or OTG FIRST... Then you can restore.
While flashing SYSTEM it will send the update in 5 chunks - from my device:
target reported max download size of 518205818 bytes
erasing 'system'...
OKAY [ 0.869s]
sending sparse 'system' (499853 KB)...
OKAY [ 26.326s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 19.701s]
sending sparse 'system' (495930 KB)...
OKAY [ 25.524s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 20.212s]
sending sparse 'system' (495450 KB)...
OKAY [ 25.732s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 19.792s]
sending sparse 'system' (443364 KB)...
OKAY [ 22.984s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 19.222s]
sending sparse 'system' (310634 KB)...
OKAY [ 16.188s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 12.593s]
finished. total time: 209.162s

NOOB Question:
where can I get the Information if my kernel is "no-force-encrypt kernel"?
I'm using the stock kernel 3.10.40 (28.jul) build LMY48M (rooted)
UDPATE:
in Settings -> security -> enrcypt tablet-> encrypted: means "force-encrypt kernel"?

Deleted

No force encryption stock kernel
For those who want to flash Marshmallow immediately but wanted to keep the device un-encrypted, download this zip, extract the boot image and flash through fastboot.

Can't get fastboot flash recovery twrp.img to TAKE after factory reset??? Help>

I originally did a boot unlock, a fash of twrp-2.8.7.2-angler.img, and when I could not get the pattern on twrp recovery to function, I did a sideload of the twrp.img instead of an install.
This failed in a boot loop.
SO I did a flash back to stock with angler-mdb08m-factory-dbc17940.tgz (after unpacking this).
Then I restored all my apk, etc.
BUT now when I do:
fastboot flash recovery twrp-2.8.7.2-angler.img, I SEE:
target reported max download size of 494927872 bytes
sending 'recovery' (16880 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.247s]
finished. total time: 0.809s
---- all looks fine, but the device itself does not seem to react and when I reboot, and select recovery, it just goes into Google recovery.
Has anyone else seen this, and do you know how to get past this?
I already tried to unlock again and it tells me error, already unlocked.
So my next step would be to do a lock and then an unlock again, but that would probably cause me to take several hours restoring after another flash to stock, and I fear that I will be back where I am now??? any thoughts??

SOLVED!
It seems that somehow, I just hadn't waited long enough. I was able to now reboot into recovery.
Thanks to any that looked at this issue.

fastboot flash boot failed

trying to flash boot.img even stock boot or patched image but got failed as message partition does not exist. The device is in fastboot mode with unlocked bootloader and rooted.
Tried Flashify, but freeze when tapping on Boot image.
command: fastboot flash boot boot.img
Result:
c:\adb>fastboot flash boot patched_boot.img
sending 'boot' (16852 KB)...
OKAY [ 0.382s]
writing 'boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.387s
Any idea?

Did you solve the problem?

i think you can try https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-restore-hard-bricked-lost-t3838461

ISCYamil said:
Did you solve the problem?
Click to expand...
Click to collapse
Nope. The reason I want to flash stock boot image or patch boot image because of every time flash new flyme rom via TWRP, the phone always rooted and Magisk is not working to hide root. Now I just use as is. The banking app cannot be working with rooted phone.

hall060679 said:
trying to flash boot.img even stock boot or patched image but got failed as message partition does not exist. The device is in fastboot mode with unlocked bootloader and rooted.
Tried Flashify, but freeze when tapping on Boot image.
command: fastboot flash boot boot.img
Result:
c:\adb>fastboot flash boot patched_boot.img
sending 'boot' (16852 KB)...
OKAY [ 0.382s]
writing 'boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.387s
Any idea?
Click to expand...
Click to collapse
I had the same problem just earlier today. What did the trick for me was installing the ROM using TWRP recovery. Move the stock ROM (you need to zip it for the process) into phone's root directory using your computer and then in TWRP tap on "Install" and find the zipped stock ROM and confirm. Let us know.

try fastboot flash bootimg instead.