A A A
Please consider registering
guest
sp_LogInOut Log In
Register | Lost password?
Advanced Search
Forum Scope


Match



Forum Options



Minimum search word length is 3 characters – maximum search word length is 84 characters
sp_Feed Topic RSS 02-yellowpac
Image wont boot please help
January 9, 2021
4:18 am
PrettyGoodd
Member
Members
Forum Posts: 2
Member Since:
December 31, 2020
sp_UserOfflineSmall Offline

Image: [512gb]-Retro-Bliss-Revolution.Pi.4.RE-LOADED.Playbox.v1.5-4.5.18-VIRTUALMAN

Pi 4 8GB, booting from micro SD 512 card, 4K OLED TV

Hey guys noob here, I’m at a total loss and need help :/ I burned this image to my micro SD, put it in my Pi 4 8GB, connected to my TV and it wont boot at all. I get some kind of generic Raspberry Pi error message that says (amongst other things) recover4.elf not found and start4.elf not found and Firmware not found ERROR: 00000004 Insert SD-Card. I have a photo of it but I don’t see how I can upload a photo to this post. I also tried to boot this same image on my Pi4 4GB with same result. It doesnt even load anyting, goes right to this error. I’m so excited to try this image because it looks so sick! Thoughts?

January 12, 2021
5:15 am
PrettyGoodd
Member
Members
Forum Posts: 2
Member Since:
December 31, 2020
sp_UserOfflineSmall Offline

Update.. this is fixed. I had a bad image, downloaded it again and it works great. 

 

Not sure if this is the appropriate place but I just wanted to give a HUGE shout out to Virtualman and Arcade Punk for this excellent image! This this is so good! All the little things like the attention to detail, the way the music fades out when a rom loads.. stuff like that make for a solid experience. Absolutely love it, thank you guys.Laugh

January 12, 2021
9:46 pm
Avatar
Ninja UK
Admin
Forum Posts: 2237
Member Since:
May 14, 2015
sp_UserOfflineSmall Offline

PrettyGoodd said
Update.. this is fixed. I had a bad image, downloaded it again and it works great. 

  

glad it sorted 🙂 

January 25, 2021
10:23 pm
deego
Guest
Guests

i keep getting this exact error screen. i have tried 3 different images. so you just redownloaded an image and it worked the second time?

March 13, 2021
2:16 pm
j Mart
Member
Members
Forum Posts: 1
Member Since:
March 13, 2021
sp_UserOfflineSmall Offline

Got the same problem here, downloaded different images for my Rpi 4 2Gb, and the raccoon 32 and the 16 gb emulga lockdown are both giving the above mentioned problem” no recovery.elf and start.elf found (error 00000044)….

Doid download the emulga twice, used different cards (32 and 200 gb). The retropie did it perfectly btw…..

March 28, 2022
8:40 pm
Peter Bach
Member
Members
Forum Posts: 2
Member Since:
March 28, 2022
sp_UserOfflineSmall Offline

Hello,

I am trying to get this to work for weeks now. I downloaded the Rick_Dangerous_Pure_500FFE.img and RickDangerous2021PureEdition.img and I used Etcher and Win32DiskImager on Windows 10 and Etcher for Ubuntu 20.04 together with an original SanDisk 512GB Extreme Pro for a RPI4 4GB. Also an internal and external card reader.

I burned the images several times. The validation always fails. The image is then not bootable and corrupted.

Before using fdisk it will boot forever, maybe hours, green and red lights are blinking. And at some point this comes: 

 

4107.5867051 EX14-fs error (device mmcblkOp21: htree_dirblock to tree:1030: anode *314: block 8382: comm dpkg: bad entry in directory: rec_len z 4 f= 0 – offset=76, inode=1714319203, rec_len=26473, name len=45, size t 41011.4536811 EX14-fs error (device mmcblkOp2): ext4_ext_check_inode:459: ‘node *378: comm dpkg: pblk 0 bad header/extent: invalid magic – magic b32a, entries 1, max 4(0), depth 0(0) 4111.8973761 EX14-fs error (device mmcblkOp2): htree_dirblock to_tree:1030: Spode *314: block 8382: comm dpkg: bad entry in directory: rec_len Z 4 f= 0 – offset=76, inode=1714319283, recien=26473, name_len=45, size= t 4113.3902901 EX14-fs error (device mmcblkOp2): ext4_ext_check inode:459: ‘!rode *378: comm dpkg: pblk 0 bad header/extent: invalid magic – magic b32a, entries 1, max 4(0), depth 0(0) 4133.9296561 EX14-fs error (device mmcblkOp2): htree dirblock-to_tree:1030: anode *314: block 8382: Comm dpkg: bad entry in directory: rec_len z 4 t= 0 – offset=76, inode=1714319203, rec_len=26473, name_len=45, size=4 t 4134.9453381 EXI4-fs error (device mmcblkOp2): ext4_ext check inode:459: anode *378: corn dpkg: pblk 0 bad header/extent: invalid magic – magic b32a, entries 1, max 4(8), depth 0(0) 4184.4178291 EX14-fs error (device mmcblkOp2): htree dirblock-to tree:1030: anode *314: block 8382: corm dpkg: bad entry in directory: rec_len z 4 1= 0 – offset=76, inode=1714319203, rec_len=26473, name 1en=45, size=40 4185.1630151 EX14-fs error (device mmcblkOp2): ext4 ext check inode:459: anode 1078: comm dpkg: pblk 0 bad header/extent: invalid magic – magic b32a, entries 1, max 4(0), depth 0(0) t 4188.1106161 EX14-fs error (device mmcblkOp2): htree dirblock-to tree:1030: anode *314: block 8382: comm dpkg: bad entry in directory: rec_len X 4 f= B – offset=76, inode=1714319203, rec_len=26473, name_len=45, size=466 t 4188.8535171 EXI4-fs error (device mmcblkOp2): ext4 ext check inode:459: anode *378: comm dpkg: pblk 0 bad header/extent: invalid magic – magic b32a, entries 1, max 4(0), depth 0(0) 4205.7218521 EX14-f* error (device nneblkOp2): htree dirblock:to_tree:1030: !node *314: block 8382: comm dpkg: bad entry in directory: rec_len z 4 f= B – offset=76, imode=1714319283, rec_len=26473, nanc_len=45, size=4094 4206.4108981 EX14-fs error (device mmcblk8p2): ext4 ext check Inode:459: anode *378: corm dpkg: pblk 0 bad header/extent: invalid magic – magic bra, entries 1, max 4(0), depth 0(0) t 4213.9383331 EX14-fs error (device mmcblk0p2): htree dirblock-to tree:1030: anode *314: block 8382: comm dpkg: bad entry in directory: rec_len X 4 t= 0 – offset=76, inode=1714319283, rec_len=26473, name_len=45, size=4096 t 4215.3603901 EX14 -fs error (device nmcblk0p2): ext4 ext check inode:459: anode *378: corm dpkg: pblk 0 bad header/extent: invalid magic – magic b32a, entries 1, max 4(0), depth 0(0) 4218.2371931 EXI4-fs error (device mmcblkOp2): htree dirblock-to tree:1030: anode $314: block 8382: comm dpkg: bad entry in directory: rec_len z 4 1= 0 – offset=76, inode=1714319283, rec_len=26473, name_len=45, size=4096 9218.9826181 EX14 -fs error (device mmcblkep2); ext4 ext check_inode:459: triode *378: corn dpkg: pblk 0 bad header/extent: invalid magic – magic b32a, entries 1, max 4(8), depth 8(0) 4239.4652621 EX14-fs error (device mricblkOp2): htree dirblock to tree:1030: triode *314: block 8382: comm dpkg: bad entry in directory: rec_len x 4 f= 8 – offset=76, inade=1714319203, rec_len=26473, name_1en=45, size=4096 4248.8109031 EXI4-fs error (device mmcblkOp2): ext4 ext check inode:459: !node 4378: corm dpkg: pblk 0 bad header/extent: invalid magic – magic b32a, entries 1, max 4(0), depth 0(0) t 42% 6474201 EX14 -fs error (device mmellk0p2): htree dirblock-to tree:1038: anode *314: block 8382: comm dpkg: bad entry in directory: rec_len Z 4 I= 0 – offset=76, inode=1714319283, rec_len=26473, name_1en=45, size=4096 4257.2403811 EX14-fs error (device mmcblk0p2): ext4 ext check_inode:459: triode *378: comm dpkg: pblk 0 bad header/extent: invalid nettle – magic b32a, entries 1, max 4(0), depth 0(0) t 4260.3940681 EX14-fs error (device nnebikepz): mite dirtlock to_tree:1030: anode 8314: block 8382: corn dpkg: bad entry In directory: rec_len x 4 I= 0 – offset=76, Imode=1714319283, rec_len=26473, name_len=45, size=4096 t 4262.7676561 EX14-fs error (device nmcbikep21: ext4 ext check_Inode:459: Sale *378: con* dpkg: pblk 0 bad header/extent: invalid magic – magic 632a, entries 1, max CO), depth 0(0) 4274.1079861 EX14-fs error (device uncbil9p21: ktree dIrblock to tree:1038: (node *314: block 8382: comm dpkg: bad entry in directory: rec_len z 4 f= 0 – offset=76, inode=1714319203, recJen=26473, nene_len=45, sir:y=4096 I 4274.8483791 EX14-fs error (device anctlikep2): ext.4_ext r.heek inode:459: triode 1$378: corn dpkg: pblk 0 bad header/extent: Invalid magic – magic b32a, entries 1, max 4(0), depth 0(0) 4281.6871341 EXI4-fs error (device minebihep2): htree alrbIock-to_tree:1030: (rode $314: block 8382: corn dpkg: bad entry In directory: rec_len z 4 f= B – offsetm76, inode=1714319203, rec_1en=26473, nanc_lelp45, size=4096 4283 1093211 EX14-fs error (device nmeblkOp2): ext4 ext check inode:459: !made *378: can dpkg: pblk 0 bad header/extent: invalid magic – magic 632a, entries 1, wax 4(0), depth 0(8) t 4285.9342081 EXT4-fs error (device onclik8y21: htree dirblock-to tree:1030: anode $314: block 8382: corn dpkg: bad entry in directory: rec_len x 4 I= 0 – offset=76, inode=171431920, recien=26473, nane_1em=45. site=4096 4288 3666891 EX14-fs error (device mmebikOpZ): ext4 ext checic inode:453: anode $378: corn dpkg: pblk 0 bad header/extent: invalid magic – magic b32a, entries 1, wax 4(0), depth 0(9) I 4311.0847001 El(S4-fs error (device actilk(tp2): litter dirblock-to_tree:1030: anode 4314: block 8382• core dpkg: bad entry in directory: rec_len z 4 la 0 – offset=76, Inode=1714319203, rec_ien=26473, name_len=45, size24096 t 4311.8238391 EX14-fs error (device minchillk0p2): ext4 ext check_inode:459: (node 4378: coma dpkg: pblk 0 bad header/extent: invalid magic – magic 632a, entries 1, max 4(01, depth 0(0) t 4317.9300941 EX74-fs error (device Inscbliap2): haree_dirblock to_tree:1030: Spode *314: block 8382: corn dpkg: bad entry in directory: rec_len x 4 I= 0 – offset=76, inode=1714319203, rec_1enC6473, none_len=45, size-40% t 4319.3756411 EX14-fs error (device ext4 ext chech_inode:459: (node 8378: COMA dpkg: pblk 0 bad header/extent: invalid magic – magic 632a, entries 1, max 4(0), depth 0(0) t 4322.630E081 1X14-fs error (device menchlkOp2): btree dIrbloch to tree:1030: tnode $314: block 8382: corn dpkg: bad entry in directory: rec_len z 4 f= 0 – offset=76, Inode=1714319203, rec_len=26473, nanc_lena45, slic=4096

After using fdisk the image is unusable, probably because of millions of EX14-fs error.

I regulary use several different images for RPI. Retropie, Raspian, Ubuntu I have never encountered so many failed burns. I also tried another 512GB SD card different OSs and Burn Apps. I takes about 8 hours to burn an image with my setup so I gave up at some point.

Does anybody know what the problem is?

Thanks a lot!

May 16, 2022
8:49 pm
Peter Bach
Member
Members
Forum Posts: 2
Member Since:
March 28, 2022
sp_UserOfflineSmall Offline

Anybody?

Forum Timezone: Europe/London
Most Users Ever Online: 3117
Currently Online: chrky2005, James Carrico
Guest(s) 33
Currently Browsing this Page:
1 Guest(s)
Top Posters:
canter6: 134
Jaz808: 121
davep180: 74
SteelCityJJ: 74
kme2019: 61
Misa Misa: 58
-x-: 53
MyRetrozz: 51
sergiohyperspin: 45
hipp0: 40
Member Stats:
Guest Posters: 122
Members: 125979
Moderators: 31
Admins: 2
Forum Stats:
Groups: 7
Forums: 35
Topics: 3514
Posts: 10858
Newest Members:
g t_2, Samuel Stephano, Andre Hennig, Miguel Chang, Andy marogy, Martin Santoro, alessandro carvalho, D DLSG, lucas santos, Tom Ebling
Moderators: aladdin: 0, Arcade Man: 0, Arcade Punk: 0, CP78: 0, ETA PRIME: 0, Ghost Lost: 0, Harrison Hacks: 0, T.K.O. Cinematics: 0, kiodiekin1: 0, level1online: 0, hursty1: 0, Neighbourhood Techie: 0, Maria: 0, PatmanQC: 0, Restalgia: 0, RetroHumanoid: 0, Simply Austin: 0, titipilas: 0, Titi Ober: 179, Enkak: 28, leepspvideo: 0, _RetroTech100: 0, Guest Post: 0, Mark Blackwood: 0, Frankie Wilde: 0, Jeremy Reynolds: 0, Leslie Alexander: 0, Jason Copley: 0, Eleonora: 0, Joshua Robinson: 0, James Collins: 0
Administrators: Ninja UK: 2227, peter laws: 0

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More