Guest schenkelklopfer Posted August 18, 2010 Report Share Posted August 18, 2010 Okay, i did something really stupid, it looks like it killed my boot sector.... (i was deleting SD Card and so on) now, when i go to bootloader mode i get the following: a listing from 0-5: ptn0 name boot start=304 len=20 prn 1 name='system' start=324 len=880 ptn 2 name= userdata start 1204 len 642 ptn 3 cache = start 1846 len 160 ptn name=recovery start=2006 len 38 ptn 5 name=misc start 2044 len=4 CANNOT READ BOOT IMAGE HEADER i tried with fastboot flash recovery recovery-clockwork-2.5.0.4-pulse.img to repair it and get: sending "recovery (2758 kb) ....OK writing Recovery .... OKAY but nothing changes, it i press - power volume down red or power volume up red any idea? a link what to do? i'm googling and cant find anything... at the moment i have a 150,- brick next to me :D Link to comment Share on other sites More sharing options...
Guest BigBearMDC Posted August 19, 2010 Report Share Posted August 19, 2010 Okay, i did something really stupid, it looks like it killed my boot sector.... (i was deleting SD Card and so on) now, when i go to bootloader mode i get the following: a listing from 0-5: i tried with fastboot flash recovery recovery-clockwork-2.5.0.4-pulse.img to repair it and get: sending "recovery (2758 kb) ....OK writing Recovery .... OKAY but nothing changes, it i press - power volume down red or power volume up red any idea? a link what to do? i'm googling and cant find anything... at the moment i have a 150,- brick next to me :D Don't worry, you just flashed a corrupted boot image, or even another image. There are two ways to solve this problem: 1. Flash a custom ROM 2. Flash a new boot image manually I recommend you to install a custom ROM (like FLB MOD ;) ). Therefore you need to flash a custom recovery imagw (what you already did). Boot into it by pressing power + menu + red (end) key. Install then the custom ROM by selecting 'flash update.zip from SD card' or something similar. Don't worry, it's nearly impossible to brick a Pulse :D Best regards, BB Link to comment Share on other sites More sharing options...
Guest starkos Posted August 19, 2010 Report Share Posted August 19, 2010 (edited) but nothing changes, it i press - power volume down red or power volume up red any idea? a link what to do? i'm googling and cant find anything... at the moment i have a 150,- brick next to me :D You're also pressing the wrong buttons to get to recovery, try Menu + Red when powering on if you haven't Edit: BigBear already mentioned this above :D Edited August 19, 2010 by starkos Link to comment Share on other sites More sharing options...
Guest schenkelklopfer Posted August 19, 2010 Report Share Posted August 19, 2010 Don't worry, you just flashed a corrupted boot image, or even another image. There are two ways to solve this problem: 1. Flash a custom ROM 2. Flash a new boot image manually I recommend you to install a custom ROM (like FLB MOD :D ). Therefore you need to flash a custom recovery imagw (what you already did). Boot into it by pressing power + menu + red (end) key. Install then the custom ROM by selecting 'flash update.zip from SD card' or something similar. Don't worry, it's nearly impossible to brick a Pulse :D Best regards, BB thanks big bear, i flashed a boot from my nandroid... now i'm able to go back to recovery... is there anywhere mentioned how to set up my sd card with gparted? 1st partition ext2 1gb 2nd partion fat 32 13,7gb 3rd linux-swap 300 mb right? or better? Link to comment Share on other sites More sharing options...
Guest Holograph Posted August 19, 2010 Report Share Posted August 19, 2010 thanks big bear, i flashed a boot from my nandroid... now i'm able to go back to recovery... is there anywhere mentioned how to set up my sd card with gparted? 1st partition ext2 1gb 2nd partion fat 32 13,7gb 3rd linux-swap 300 mb right? or better? You should set swap to 0 MB, SWAP isn't supported yet. Link to comment Share on other sites More sharing options...
Guest schenkelklopfer Posted August 19, 2010 Report Share Posted August 19, 2010 You should set swap to 0 MB, SWAP isn't supported yet. ok, changed it my main problem, why i cant update a new zip, is that i cant mount my sd card....? i'm using the clockwork mod recoverey 2.5.0.4 in this i'm also missing the opportunity (like in the RA recovery) to partitonate the SD card over the recovery menu? (sorry, i was really looking old threads via search.. but its not easy to find the right in 149 pages (flb thread) maybe this would be good to have in a extra todo thread? Link to comment Share on other sites More sharing options...
Guest schenkelklopfer Posted August 19, 2010 Report Share Posted August 19, 2010 ok, changed it my main problem, why i cant update a new zip, is that i cant mount my sd card....? i'm using the clockwork mod recoverey 2.5.0.4 in this i'm also missing the opportunity (like in the RA recovery) to partitonate the SD card over the recovery menu? (sorry, i was really looking old threads via search.. but its not easy to find the right in 149 pages (flb thread) maybe this would be good to have in a extra todo thread? could it be, that the sd card is crashed? i switched now from Clockwork recvoery back to amon ra... now i try the partition sd card (16gb) 0 swap 1024 ext2 and the mobile restarts always while paritioning the ext.... :D do you know what to do, bigbear? would be leiwand :D Link to comment Share on other sites More sharing options...
Guest schenkelklopfer Posted August 19, 2010 Report Share Posted August 19, 2010 ok, re-partitionated it with linux gparted again... that works but if i try then: amon ra: partition sd - it reboots always... s*** Link to comment Share on other sites More sharing options...
Guest schenkelklopfer Posted August 20, 2010 Report Share Posted August 20, 2010 back on the map!!!!!!!!!! yeah!!!! now i'm loading the flb 1.4.1 - what a cool bootscreen problem was: partitioning without battery only with usb is NOT WORKING... what a shitty thing.... the problem in all the guides is: 140 page is much much to read.... anyway... now i can go to sleep!!! yeah Link to comment Share on other sites More sharing options...
Guest BigBearMDC Posted August 20, 2010 Report Share Posted August 20, 2010 back on the map!!!!!!!!!! yeah!!!! now i'm loading the flb 1.4.1 - what a cool bootscreen problem was: partitioning without battery only with usb is NOT WORKING... what a shitty thing.... the problem in all the guides is: 140 page is much much to read.... anyway... now i can go to sleep!!! yeah Well done! Hell if you mentioned that with the battery earlier... nothing works in recovery mode if you remove the battery :D 3:27 is pretty late :D Best regards, BB Link to comment Share on other sites More sharing options...
Guest schenkelklopfer Posted August 20, 2010 Report Share Posted August 20, 2010 Well done! Hell if you mentioned that with the battery earlier... nothing works in recovery mode if you remove the battery :D 3:27 is pretty late :D Best regards, BB i was working with only the usb power ;) s*** man.... Link to comment Share on other sites More sharing options...
Guest schenkelklopfer Posted August 20, 2010 Report Share Posted August 20, 2010 damned... i had partitioned my sd card before flb1.4 update then i was going into the rom manager....... clicked on SD partition in the rom manager... now i'm stuck into boot loader (i mean where the skating droid is in a circle) nothing happens since minutes... Link to comment Share on other sites More sharing options...
Guest REYJ MORDZ Posted May 15, 2019 Report Share Posted May 15, 2019 I have RELATED problem to this guy, sending and writing custom recovery went OK but rebooting into recovery shows Failed (remote:bad boot image header ).I'd tried compatible and updated twrp custom recovery for my device, googling/searching for it. My stock recovery dis appear now & I Dr dont backup it any more because of excitement that I can now flashed a custom recovery. For my opinion, maybe this is caused by mistake/wrongdata/corrupteddaya/invalid compilation in programs etc..I don't know what to do ,fortunately still I can access my device likewose that I can't see any image when I go to recovery just a white screen....!....help me on how to fixed this..I dont even unlocked my bootloader, tried many times but wont unlock bootloader..... My phone is spreadtrum s7731c chipset cloudfone go connect...Please help & notify me at [email protected]....... Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now