[Q] Device is NOT bigPart partitioned - Xoom Q&A, Help & Troubleshooting

hi everyone
I am new to this forum and I hope someone can help me with this
I am trying to install KitKat on my xoom M600 but I keep getting 'Device NOT bigpart partitioned...' and therefore failed to install
I have followed the steps in BigPart Repartition Upgrade and Resource Center, but still getting them same message
what I am i doing wrong and is there something wrong with the bigpart image that i have ?
your help will be greatly appreciated

xoom1425 said:
hi everyone
I am new to this forum and I hope someone can help me with this
I am trying to install KitKat on my xoom M600 but I keep getting 'Device NOT bigpart partitioned...' and therefore failed to install
I have followed the steps in BigPart Repartition Upgrade and Resource Center, but still getting them same message
what I am i doing wrong and is there something wrong with the bigpart image that i have ?
your help will be greatly appreciated
Click to expand...
Click to collapse
What model is your Xoom?
Sent from my Galaxy Nexus using xda app-developers app

webeougher said:
What model is your Xoom?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
thanks for replying
my model is the m600 verizon, but i got it solved
turns out that i had the wrong bigpart file
i got the correct file from dev-host and i am now up and running

xoom1425 said:
thanks for replying
my model is the m600 verizon, but i got it solved
turns out that i had the wrong bigpart file
i got the correct file from dev-host and i am now up and running
Click to expand...
Click to collapse
Hi. I am having the same problem. When I install bigpart partition it says successful. but when I try and install kitkat. I still get device is not bigpartitioned error message.
I also tried dev-host bigpart installation file first and then when i try the kitkat install it still says I am not bigpart partitioned.
Any ideas?

Well, my first bricked tablet I guess.. Followed this guide djsmobiles.com/2014/02/how-to-perform-bigpart-repartition-upgrade-on-your-motorola-xoom.html but after I complete partitioning wingray install fails. I have got these:
recovery.twrp.2.7.0.0.bigPart.img.zip
gapps-wingray-kk-20131223.zip
omni-4.4.2-latest-wingray-HOMEMADE.zip
Now I can't boot into my system and I can't install either because installer says that my device is not bigPart partitioned, even though I followed every step of the guide.. Help!

jack-black said:
Well, my first bricked tablet I guess.. Followed this guide djsmobiles.com/2014/02/how-to-perform-bigpart-repartition-upgrade-on-your-motorola-xoom.html but after I complete partitioning wingray install fails. I have got these:
recovery.twrp.2.7.0.0.bigPart.img.zip
gapps-wingray-kk-20131223.zip
omni-4.4.2-latest-wingray-HOMEMADE.zip
Now I can't boot into my system and I can't install either because installer says that my device is not bigPart partitioned, even though I followed every step of the guide.. Help!
Click to expand...
Click to collapse
lol, forgot to flash the bigPart version of twrp! Now all is good

jack-black said:
lol, forgot to flash the bigPart version of twrp! Now all is good
Click to expand...
Click to collapse
I did the same thing. Lol. At first I thought I screwed up my xoom lol

Related

[Q] Symlinks failed - status 7 - Paranoid Android

Hi Guys,
I've been using Paranoid Android for some time now and love it. I have just downloaded the latest version, performed Dragun's wipe script and when trying to install, I keep getting an error stating a status 7, some symlinks failed. I have tried re-downloading the rom, plus a previous version as well as full wiping everything and factory reset to no avail. Has anyone had this issue? Can anyone help?
I have just tried to install another rom to get past this for now, however it appears the phone is now stuck on the loading screen... Any help would be appreciated.
I would post in the development thread for the rom, however as I haven't posted before, I don't have sufficient permissions.
Cheers,
Mike
Mikeparakh said:
Hi Guys,
I've been using Paranoid Android for some time now and love it. I have just downloaded the latest version, performed Dragun's wipe script and when trying to install, I keep getting an error stating a status 7, some symlinks failed. I have tried re-downloading the rom, plus a previous version as well as full wiping everything and factory reset to no avail. Has anyone had this issue? Can anyone help?
I have just tried to install another rom to get past this for now, however it appears the phone is now stuck on the loading screen... Any help would be appreciated.
I would post in the development thread for the rom, however as I haven't posted before, I don't have sufficient permissions.
Cheers,
Mike
Click to expand...
Click to collapse
are you S-ON or S-OFF?
rzr86 said:
are you S-ON or S-OFF?
Click to expand...
Click to collapse
Hi
I'm S-OFF.
Mikeparakh said:
Hi
I'm S-OFF.
Click to expand...
Click to collapse
then check if you have the latest fw version
as far as i know paranoid android rom requires 3.32fw or 3.33fw
also what recovery do you have?
rzr86 said:
then check if you have the latest fw version
as far as i know paranoid android rom requires 3.32fw or 3.33fw
also what recovery do you have?
Click to expand...
Click to collapse
I'm on 3.33 and am using 4ext recovery touch. Thanks.
Mikeparakh said:
I'm on 3.33 and am using 4ext recovery touch. Thanks.
Click to expand...
Click to collapse
All fixed now thanks to the wonderful developers of PA. Thanks for your help though!
Mikeparakh said:
All fixed now thanks to the wonderful developers of PA. Thanks for your help though!
Click to expand...
Click to collapse
Can i please what steps you took to get this working again? I get same symlink error when trying to flash from CWM
midnight2065 said:
Can i please what steps you took to get this working again? I get same symlink error when trying to flash from CWM
Click to expand...
Click to collapse
flash the latest firmware if you do not have it(you have to be S-OFF)
also install 4ext recovery.it is better

[Q] Binary Failed (Flashing Rom)

Hi guys, I'm actually trying to get the pacman rom 4.2.2 But there's no way to get it, I've tryed with CyanogenMod and it doest work... I just get this image and i dont know what thell do because im noobie at this android thing! Just got 3 days with the phone,Its an htc one s, If someone can help me ill appreciate it and sorry for the english,Years without practice it
Its an odd one dude, try getting a fresh copy of the ROM, then shutting down your phone and repeat the wiping process and reflash ?
Sent from my One S using xda premium
I have had similar issues when a rom zip is corrupted. Like blackcell said you should try redownloading the rom or trying another rom just to check if that zip is the issue.
inXavier said:
Hi guys, I'm actually trying to get the pacman rom 4.2.2 But there's no way to get it, I've tryed with CyanogenMod and it doest work... I just get this image and i dont know what thell do because im noobie at this android thing! Just got 3 days with the phone,Its an htc one s, If someone can help me ill appreciate it and sorry for the english,Years without practice it
Click to expand...
Click to collapse
Use twrp 2.4.0.0 recovery. Rest of them have many bugs.
2.3.3.0 is best
Sent from my HTC One S using xda premium
vatsaman said:
Use twrp 2.4.0.0 recovery. Rest of them have many bugs.
Click to expand...
Click to collapse
It says the same thing, Failed with twrp 2.4.0.0 with that file that u says came a .MD5 file do i need to do something with that file? I think thats the problem but i was looking at google and i couldnt find anything about it..
inXavier said:
It says the same thing, Failed with twrp 2.4.0.0 with that file that u says came a .MD5 file do i need to do something with that file? I think thats the problem but i was looking at google and i couldnt find anything about it..
Click to expand...
Click to collapse
No need of MD5 files, what version of recovery are you on ?

[SOLVED] Hardware Brick flashing BootAnimation

Hello guys,
I´m using BlissPop with Metallized Kernel and after flash logo and move bootanimation and rbootanimation, my phone doesn´t boot. I can´t enter recovery or fasboot mode!!!! What can I do???, please help me.
I use bootanimation and logo from this post: http://forum.xda-developers.com/showthread.php?t=2768755&page=3#post60766600
Thanks in advance.
Hello again guys,
After read and use this gide http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 I finish with CM 11 (4.4.4) with TWRP 2.8.6.0.
I want to install CM 12S or BlissPop, preferably BlissPop but I can´t install any zip from TWRP, the flashing process always fail. Can anyone give me some advice? Or point me to a certain toolkit? I´m totally confussed right now... :S
Thanks in advance guys!!!
You need to provide more information. Exactly what error message are you getting when the zip install fails?
XDA Moderator
Transmitted via Bacon
Heisenberg said:
You need to provide more information. Exactly what error message are you getting when the zip install fails?
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
Hello and thanks for your answer.
The error message that I get is "E: Error executing updater binary in zip....." the next to this message is the path where I have the Zip for the rom in my SD card. I´m totally disoriented and I don´t know how to proceed, I appreciate any more help. Thanks in advance!!!
Istvan_86 said:
Hello and thanks for your answer.
The error message that I get is "E: Error executing updater binary in zip....." the next to this message is the path where I have the Zip for the rom in my SD card. I´m totally disoriented and I don´t know how to proceed, I appreciate any more help. Thanks in advance!!!
Click to expand...
Click to collapse
Ok. Are you checking the md5 after downloading the zip to ensure that it isn't corrupt? Are you wiping properly (system, data, cache, dalvik cache) before attempting the install? Since unbricking the phone have you flashed any firmware at all or is this your first attempt?
Heisenberg said:
Ok. Are you checking the md5 after downloading the zip to ensure that it isn't corrupt? Are you wiping properly (system, data, cache, dalvik cache) before attempting the install? Since unbricking the phone have you flashed any firmware at all or is this your first attempt?
Click to expand...
Click to collapse
Hi again,
md5 checked, full wipe done and after unbrick phone I just flash CM12 nightly.
Also note that I flash BlissPop and Metallized Kernel and everything was ok until I decide to change the bootanmation, rbootanimation and logo. I try to flash the ROM with the zip that I use the first time and also try with a new downloaded zip.
Thanks and regards.
Istvan_86 said:
Hi again,
md5 checked, full wipe done and after unbrick phone I just flash CM12 nightly.
Also note that I flash BlissPop and Metallized Kernel and everything was ok until I decide to change the bootanmation, rbootanimation and logo. I try to flash the ROM with the zip that I use the first time and also try with a new downloaded zip.
Thanks and regards.
Click to expand...
Click to collapse
Ok, that information probably would have been useful in your initial post. You're messing with things that can (and obviously do) cause major problems. Flash the stock images with fastboot, see section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
After that you should be able to flash and boot a ROM again, just don't go screwing with the boot logo.
Heisenberg said:
Ok, that information probably would have been useful in your initial post. You're messing with things that can (and obviously do) cause major problems. Flash the stock images with fastboot, see section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
After that you should be able to flash and boot a ROM again, just don't go screwing with the boot logo.
Click to expand...
Click to collapse
Really thanks again, I´ll check carefully your post and post the results here. Thanks.
P.S.: I never touch any bootlogo or logo again.
Hello again Heisenberg,
I follow all the steps of section 8 of your guide and I´m on CM OS 5.0.2 and an update of 598,4 MB is downloading right now, the name is Cyanogen OS YNG1TAS17L, can I install it and then flash again my BlissPop?
Really thanks for all your help.
P.S.: Are you watching Better Call Saul? xD
Hello again,
All works like a charm and I´m on BlissPop again.
Really really thanks Heisenberg, cheers.
Istvan_86 said:
Hello again,
All works like a charm and I´m on BlissPop again.
Really really thanks Heisenberg, cheers.
Click to expand...
Click to collapse
Excellent, glad to see you're up and running again.

Unable to update to 12.1

So today I saw that the 12.1 update is downloaded and asking me to install it. But, when I do try installing it the screen is stuck at the Cyanogen Recovery.
The usual options in recovery screen are displayed, why isn't the OS updating?
FYI - My OPO is rooted and also has TWRP recovery installed. I also tried disabling the Update Cyanogen Recovery option but the same option.
Any assistance would be great
SagarRox said:
So today I saw that the 12.1 update is downloaded and asking me to install it. But, when I do try installing it the screen is stuck at the Cyanogen Recovery.
The usual options in recovery screen are displayed, why isn't the OS updating?
FYI - My OPO is rooted and also has TWRP recovery installed. I also tried disabling the Update Cyanogen Recovery option but the same option.
Any assistance would be great
Click to expand...
Click to collapse
You can't flash the OTA with TWRP recovery. You can either flash the stock recovery and then install the OTA, or you can download the full ROM zip and flash that with TWRP.
Heisenberg said:
You can't flash the OTA with TWRP recovery. You can either flash the stock recovery and then install the OTA, or you can download the full ROM zip and flash that with TWRP.
Click to expand...
Click to collapse
Heisen
Sorry, a little question (and sorry to the OP)
Ive try to install the ota manually (i was rooted with twrp) flashing back the cm recovery, but it doesnt work still.
So ive flash the twrp 2.8.6 (for the baseband not installing prolems) and downloaded the full rom file, flashed in twrp without any wipes... Its all ok now, should i have problems with this method?
The baseband is 241,is correct?
Thx for helping
L.
lollaz said:
Heisen
Sorry, a little question (and sorry to the OP)
Ive try to install the ota manually (i was rooted with twrp) flashing back the cm recovery, but it doesnt work still.
So ive flash the twrp 2.8.6 (for the baseband not installing prolems) and downloaded the full rom file, flashed in twrp without any wipes... Its all ok now, should i have problems with this method?
The baseband is 241,is correct?
Thx for helping
L.
Click to expand...
Click to collapse
You shouldn't have any issues.
Heisenberg said:
You shouldn't have any issues.
Click to expand...
Click to collapse
Hi,
I am facing the same issue while updating the official update. I tried updating using the Cyanogen recovery but it is giving a failed error: "Unable to open the zip file" something like this. i have downloaded the 305 Mb update again manually but of no use.
Please help on this.
TIA
Nav07 said:
Hi,
I am facing the same issue while updating the official update. I tried updating using the Cyanogen recovery but it is giving a failed error: "Unable to open the zip file" something like this. i have downloaded the 305 Mb update again manually but of no use.
Please help on this.
TIA
Click to expand...
Click to collapse
Are you currently on the build directly before this one?
Heisenberg said:
Are you currently on the build directly before this one?
Click to expand...
Click to collapse
Dear, i am frankly not a techie. I am using the stock (default) RAM only. Would be great if you can help on this
Nav07 said:
Dear, i am frankly not a techie. I am using the stock (default) RAM only. Would be great if you can help on this
Click to expand...
Click to collapse
You don't need to be a techie to know that the updates must be taken in order. Go to Settings>About Phone, take screenshots of the info there and post here so I can see please.
Heisenberg said:
You don't need to be a techie to know that the updates must be taken in order. Go to Settings>About Phone, take screenshots of the info there and post here so I can see please.
Click to expand...
Click to collapse
Currently the Cyanogen version is 12.0-YNG1TAS2I3, OS version is 5.0.2, Build number is LRX22G
Nav07 said:
Currently the Cyanogen version is 12.0-YNG1TAS2I3, OS version is 5.0.2, Build number is LRX22G
Click to expand...
Click to collapse
You're on the right version. The zip must be getting corrupt during the download or something.
Heisenberg said:
You're on the right version. The zip must be getting corrupt during the download or something.
Click to expand...
Click to collapse
I have manually downloaded the zip file again apart from the Official update but it is still not getting through
Can anything else be done on this?
Nav07 said:
I have manually downloaded the zip file again apart from the Official update but it is still not getting through
Can anything else be done on this?
Click to expand...
Click to collapse
Try downloading the full zip from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that with recovery.

XT1039 bootloop after flashing CM13

Hi,
XT1039: bootloader unlocked, rooted, stock rom 4.4.4
TO: nightly
Flashed 4118 bootloader, as detailed in http://forum.xda-developers.com/moto...tions-t2996087
It was successful.
Followed https://wiki.cyanogenmod.org/w/Install_CM_for_peregrine
unlocked bootloader
installed cm-recovery from here: https://download.cyanogenmod.org/?type=nightly&device=peregrine
tried to flash cm, got a bootloader error,
followed this guide: http://forum.xda-developers.com/showpost.php?p=59520890&postcount=233
Now using bootloader 411A
flashed cm-13.0-20160121-NIGHTLY-peregrine.zip
from here: https://download.cyanogenmod.org/?type=nightly&device=peregrine
now the phone is stuck at the boot screen.
So I flashed twrp recovery, successful and reflashed cm-13.0-20160121-NIGHTLY-peregrine.zip
I tried several different guides that included all sorts of cache deletion and format orders but the result is still the same
(I am not using an sdcard but only the internal storage.)
After rebooting, the phone is stuck on the Cyanogenmod boot icon (blinking cat face) since past half hour.
Please guide how to debug/recover.
fastboot and recovery are working
Thanks,
[edit:]
The cm-13.0-20160121-NIGHTLY-peregrine.zip was transferred by mounting the internal storage on the PC and copying it manually. Just in case this matters
Hi,
Try to flash stock rom from here : http://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
satanas17 said:
Hi,
Try to flash stock rom from here : http://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
Click to expand...
Click to collapse
Thanks for the reply, but the goal is to get cyanogenmod on my phone. How does the stock rom help me with that??
Just for testing, I have installed the stock rom to see if it works and it does. I now have a Motorola Android 5.1 on my phone. But thats not what I wanted.
Anyone having any idea how to make cyanogenmod work?
karstenme said:
Thanks for the reply, but the goal is to get cyanogenmod on my phone. How does the stock rom help me with that??
Click to expand...
Click to collapse
Just to restoring a kernel on it...after restoring one, go to TWRP, make your wipes and flash again your CM
satanas17 said:
Just to restoring a kernel on it...after restoring one, go to TWRP, make your wipes and flash again your CM
Click to expand...
Click to collapse
WOW Thank you very much, its working
Maybe you can also explain to my why installing the custom rom mattered, since I wiped everything before installing cm again, I would assume there is nothing of the stock rom left on the device.
karstenme said:
WOW Thank you very much, its working
Click to expand...
Click to collapse
U're welcome
karstenme said:
Maybe you can also explain to my why installing the custom rom mattered, since I wiped everything before installing cm again, I would assume there is nothing of the stock rom left on the device.
Click to expand...
Click to collapse
Not really able to explain...sometimes sh*t happens...
But this procedure works almost every time.
Surely due to your bootloader error after your first flash with CM recovery...something was broken...
Most important, now, it's working...Enjoy
I install cm but google play is not working and sallular data also not working.. Plz any one help me please..

Categories

Resources