[MCPE-9013] "my world" can't be opened, Bad file number Created: 17/Jun/15  Updated: 04/Aug/15  Resolved: 04/Aug/15

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 0.11.1
Fix Version/s: None

Type: Bug
Reporter: mike reid
Resolution: Duplicate Votes: 6
Labels: None

Issue Links:
Duplicate
duplicates MCPE-8383 Can not create a new world Resolved
Confirmation Status: Community Consensus
Platform: Tablet - Android - Other (Specify in description)
CHK:

 Description   

Tablet is a cheap tablet model number L901 thats all I really know, my sons tablet wont open a new world or infact it wont open any world, this is the only app downloaded we have reset his tablet several times to see if we can sort this out.



 Comments   
Comment by Luis Robles [ 04/Aug/15 ]

Anything about "Bad File Number" can be found in this issue MCPE-8383, you can comment on it.

Comment by Carla Sills [ 02/Aug/15 ]

Same problem with daughter's phone. ZTE Whirl 2, model Z667G. Running Android 4.3. Minecraft version 0.11.1 alpha. "My world" can't be opened error. App totally unplayable.

Comment by Ilona Andrews [ 14/Jul/15 ]

We have the same problem. My daughter was bought a BTC Flame tablet for her birthday in June and we installed Minecraft PE on it. Every time we open the game, we get the same message "My World" can't be opened. Bad file number. We also have another tablet, a Tesco Hudl, and this is the tablet which Minecraft PE was initially installed on. The game works fine on the Hudl (running version 10.5 I think). The version on the BTC flame tablet is v0.11.1 alpha.

Comment by mike reid [ 18/Jun/15 ]

Hi there,

No he hasn't created any, he was playing it on an old tablet once this broke and we bought him a new one it hasn't work after re installing it

Comment by Mark Jarvis [ 17/Jun/15 ]

My son had the same problem with his old tablet. Has your son made a lot of worlds? I found deleting or cutting out of the 'games/com.mojang/minecraftWorlds' folder and pasting the in a back-up folder cleared the problem.

Generated at Sat Jan 11 14:42:44 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.