I have had terrible luck flashing ROMs that are based on 2.x...I have only found 1 release that has worked, and that is the Intension branch. I have thought it was my SPL, but I have Haykuro's SPL on my phone...and I am using ramon's recovery image.
The errors I am having relate to Busybox closing (exit code 1)...this happens at the beginning of the boot process (before loading the frameworks), and shortly after 'attempting' to load up compache and ramzswap0....
Is this possibly related to an SD card issue? Right now I have a crappy 4GB Class 2 SDHC card. I have an 8GB Class 6 on its way (yay newegg.com), and I am wondering if the new SD card would possibly prevent these issues...even if it doesn't, the new SD card is going to work wonders.
But, if it is not the SD card, are there any other options I could be looking into to try to get things going?
ya i'd have to go with your current sd card causing the flashing problem.
Where would we get this ramon recovery :b?
JAguirre1231 said:
Where would we get this ramon recovery :b?
Click to expand...
Click to collapse
Ack, lets try that again: amon_ra's recovery
Related
hey everyone, im not usually quick to ask for help but i am absolutely frustrated and stuck.
trust me ive searched and read everything i need to and its just not working for me
i have a 8gb micro sd class 6 card.... everything was fine and working perfect until i did a nandroid backup
then my card started having errors when repairing ext filesystems
so i put the card in my computer and formatted it.
then i deleted and repartitioned the card
then i did the command in the recovery console to fix the filesystem error
reflashed the radio image
none of that is working for me
i have another 4gb class 4 card and its working perfect for me
but ever since my 8gb did a nandroid backup, the roms wont load at all and i get stuck in a boot loop with the second htc splash screen
PLEASE HELP THIS IS DRIVING ME MAD!!!! thanks a bunch in advance!!
im using jacxhero v2.1
and i use cyan 1.4 recovery img
After you partition in Recovery, you don't need to fix filesystems... just exit Parted and type upgrade_fs in recovery console to upgrade to ext3.
deanna619 said:
hey everyone, im not usually quick to ask for help but i am absolutely frustrated and stuck.
trust me ive searched and read everything i need to and its just not working for me
i have a 8gb micro sd class 6 card.... everything was fine and working perfect until i did a nandroid backup
then my card started having errors when repairing ext filesystems
so i put the card in my computer and formatted it.
then i deleted and repartitioned the card
then i did the command in the recovery console to fix the filesystem error
reflashed the radio image
none of that is working for me
i have another 4gb class 4 card and its working perfect for me
but ever since my 8gb did a nandroid backup, the roms wont load at all and i get stuck in a boot loop with the second htc splash screen
PLEASE HELP THIS IS DRIVING ME MAD!!!! thanks a bunch in advance!!
im using jacxhero v2.1
and i use cyan 1.4 recovery img
Click to expand...
Click to collapse
this is a fault with the rom, the nandroid backup shouldnt cause a bootloop.
did you make sure the partitions are in this order?: FAT32, ext, linux swap?
can you see the card on your pc?
yes i did those 3 in order, ive done it several different times
i make sure that i do the upgrade_fs to convert to ext3
everything goes well when i partition and i can see the sd card in my computer. but for some reason i cant get past the splash screen with this memory card... my other one is working perfect, and so was this one until i did the backup thing
when i flash, it finishes and i reboot and get stuck after the HERO splash screen, the first time it shows the little android guy and then the screen goes black and i see the same spash screen again but with no android
what happens if i repair filesystems after i repartitioned??
deanna619 said:
yes i did those 3 in order, ive done it several different times
when i flash, it finishes and i reboot and get stuck after the HERO splash screen, the first time it shows the little android guy and then the screen goes black and i see the same spash screen again but with no android
what happens if i repair filesystems after i repartitioned??
Click to expand...
Click to collapse
it wont hurt to repair it, but it seems that the problem is more likely the hero rom. something is causing the rom to bootloop. did you wipe before you flashed? try that if you havent.
also, set up adb using the stickys in this thread, then use
Code:
adb logcat
when it starts to boot. that way i can see whats happening thats causing it to bootloop
yes i definately wipe before flashing. i still think its the sd card since my other sd card works with the same rom
ill try out the abd thing... ive seen posts about it but never really read into it.
thanks for the advice! ill be right back with the results
right now that i tried again, i cant get passed the tmobile g1 screen... seems to be stuck =[
the card was formatted and partitioned and then i booted (the rom is already flashed on here, i just took out my 4gb card and switched it out for this one so i shouldnt need to reflash should i?
now i deleted all partitions in recovery mode and rebooted....
i got both splash screens hero with android and then the htc splash... now it went to a black screen and has been like this for about 5 or 6 minutes
with my 4gb card it shows the two splash screens and then the black screen comes on for no more than 30 seconds and then the phone loads
deanna619 said:
yes i definately wipe before flashing. i still think its the sd card since my other sd card works with the same rom
ill try out the abd thing... ive seen posts about it but never really read into it.
thanks for the advice! ill be right back with the results
right now that i tried again, i cant get passed the tmobile g1 screen... seems to be stuck =[
the card was formatted and partitioned and then i booted (the rom is already flashed on here, i just took out my 4gb card and switched it out for this one so i shouldnt need to reflash should i?
Click to expand...
Click to collapse
well the hero builds put some apps and configuration files on the ext partition. if your 4gb card has those on it, then you probably wont have to.
Can you see the partitions on your computer?
no i dont know how to see partitions on my computer
deanna619 said:
no i dont know how to see partitions on my computer
Click to expand...
Click to collapse
if your using windows, format the whole card to FAT32 and put it in your card reader to see if it shows up as a removable drive.
what are you using to partition the card? Try flashing another rom that doesnt need extra partitions (such as cyanogen) and see if that rom can see your card as well.
if it doesnt detect it, then your card may have gone bad
=[ looks like i got a bad card....
i appreciate you two helping me out! wish it could have worked... i guess im just gonna pick up a new card
this rom wont even load when i dont have an SD card in it... and when the phone is loaded with my 4gb card, if i take it out, the phone freezes
weird....
deanna619 said:
this rom wont even load when i dont have an SD card in it... and when the phone is loaded with my 4gb card, if i take it out, the phone freezes
weird....
Click to expand...
Click to collapse
like i said, important system files are on the sd card. you cant remove the sd card without crashing it. if you want a rom that you can use without an sd card, use JF or Cyanogen's rom. The hero roms have too much stuff to fit it all in the internal memory of the phone
what are those important files on the sd card?
are you talking about the partitions or something else?
if its something else like hidden files or something, then maybe thats what i need to fix my 8gb
deanna619 said:
what are those important files on the sd card?
are you talking about the partitions or something else?
if its something else like hidden files or something, then maybe thats what i need to fix my 8gb
Click to expand...
Click to collapse
they arent hidden, but thats what i was trying to say. after youve formatted your card, wipe and reflash the update. it will put those files on your card automatically.
they are located on your ext partition.
if you use adb, you can see them in
/system/sd/app_s
to get it to work, put the freshly partitioned sdcard into the phone.
press home+power to get to recovery. wipe the phone. flash the update (jachero2.1)
when it installs, it will find the ext partition and do it manually
I just got an A-Data Class 6 4 gig card. I can format 3 partitions, upgrade to ext3, copy update zips and files to it, but it boot loops when i try to load up a new rom (any rom). My old class 2 4 gig card loads everything fine. It even runs the latest king hero really well.
Any ideas?
robkoehler said:
I just got an A-Data Class 6 4 gig card. I can format 3 partitions, upgrade to ext3, copy update zips and files to it, but it boot loops when i try to load up a new rom (any rom). My old class 2 4 gig card loads everything fine. It even runs the latest king hero really well.
Any ideas?
Click to expand...
Click to collapse
How did you partition your card?
using parted in console. I've re-done it several times as well.
So no matter what rom you flash your getting a bootloop. Do you have a nandroid?
I do. Using Amon_Ra's 1.2.3
On 2nd thought, do you mean a nandroid of a bootloop instance?
robkoehler said:
On 2nd thought, do you mean a nandroid of a bootloop instance?
Click to expand...
Click to collapse
Naw a nandroid of a rom that was working before you started flashing.
unfortunately no. i got partition crazy and removed the fat32 it was on right before i thought "did i back that up?"
With my old class 2, i've been able to get up and running on 4.1.999 and this king hero rom with no troubles.
Can a taco be bad but not bad? like, it tastes good, but it was made with bad ingredeints or a horrible chef.....
It sounds to me like your wiping after flashing.
You wipe data, Wipe ext, fix ext, flash rom.
If you wipe after flashing, or flash without wiping you will always get a boot loop.
The image doesnt run from your sd card, so the only thing that would cause the loop is the data on your phone.
Find a tested and working rom (i suggest either Mligns newest or Kings newest)
Go into recovery and turn on USB.
Move rom to sd card.
Wipe data
Wip EXT and fix
REBOOT INTO RECOVERY
then go to flash any ZIP (if you dont reboot, the rom file will not be seen correctly)
flash the rom
Fix ext again just in case
Reboot and leave the phone alone for a few mnutes.
EVERY phone is different. Some take 2 min some take 10-20 min
But if you have flashed properly, the best way to know is the shimmer on the HTC will continue to flow and not stop.
Sometimes it will fade, sometimes the noti bar will appear for 5 min then boot...
Just have patience and try.
EDIT- You typed while I was typing, It sounds like then maybe that card is bad then. If all works with older card, then the flash may be bad on the newer card. may want to return it unless you have other uses for it.
Just to add a strange twist to this. Just reformatted card so it was all Fat32, wiped, and flashed 4.0.4. Everything went fine. What on an SD card could crash Apps2SD?
robkoehler said:
Just to add a strange twist to this. Just reformatted card so it was all Fat32, wiped, and flashed 4.0.4. Everything went fine. What on an SD card could crash Apps2SD?
Click to expand...
Click to collapse
Possibly the upgrade from ext2 to ext3. Thats why I like to do mine in Ubuntu. Format the card using linux for a linux phone.
Decided to go a step further and go back to parted and resize fat32 and add a 500mb ext2. Rebooted and it fired up and shows the ext2 in the settings screen.
All that and it's not even Halloween yet. I'm going to try to flash 4.1.11.1 just to see if i can break it again
I'm sending it back. wiped flashed 4.1.11.1. Got to setup screen but everything force closes. com.android.phone, com.google.process.gapps, com.android.setupwizard.
Skipped wizard.
signed in with google account.
no service connection ever made so no account sync.
time to email newegg and try this again
robkoehler said:
I'm sending it back. wiped flashed 4.1.11.1. Got to setup screen but everything force closes. com.android.phone, com.google.process.gapps, com.android.setupwizard.
Skipped wizard.
signed in with google account.
no service connection ever made so no account sync.
time to email newegg and try this again
Click to expand...
Click to collapse
lol.....you give up quite easily.. those problems arent related to the sd card (they are on your /system partition)
try to reflash your rom and repair ext partitions then fix_permissions in recovery
hmmmm.....got card #2 and it appears to be the same case....boot loops. i can't believe that 2 sd cards would be bad only when it comes to apps2sd.
got adb running on my work pc and uploaded a log of the fail
again, everything boots just fine (just booted king's new 1.0) with my lexar class 2
updated logcat - 1st one was when i couldn't get off of the g1 screen.
this logcat is of the bootloop. any help would be great
tried to flash a hero rom ,
di all the essential radio first spl wipe wipe repartition yada yada,,,,
when its finaly load i get crazy constant media force closes
the only thing i can think of is that i jus have a regular sd card not a sdhc class 2 even , jus a micro sd
does this sound like i need a class 6 to resovle the issue
i don't want to spend 30-40 $ on a class 6 if its not gonna get past this
um...what hero rom did you flash? that would be very helpful....there is a ton of em.
I won't be your card. We need to know what ROM you're using.
i tried king x , mighty max , sense hero
Any ideas . I got a new 8gb sdhc class6 wich is a big diff then my 2 gb sd ,so I'm gonna give it another go today if anyone has any suggestions I could always use n e advice givin
Hmmm odd.
How is your card partition? Could you post the exact text for the FC and when the occur?
Well when I attempted the flash it would load past the splash and boot image but when the home screen would load I would get media fc's. The status bar would be there but would be unresponsive the wallpapers wus black and no app tray ,the screen lock would work but constan acor's and media closes. I'll try it again later 2nite and get the exact error msg also I partitioned my 2gb sd. Using amon recovery but my card isn't high class I bought a new class 6 that I'm gonna use for 2nites attempt
Have you tried repartitioning, not just wiping the ext? That usually fixes most problems with KingxKxRom
maek_it_happen said:
Well when I attempted the flash it would load past the splash and boot image but when the home screen would load I would get media fc's. The status bar would be there but would be unresponsive the wallpapers wus black and no app tray ,the screen lock would work but constan acor's and media closes. I'll try it again later 2nite and get the exact error msg also I partitioned my 2gb sd. Using amon recovery but my card isn't high class I bought a new class 6 that I'm gonna use for 2nites attempt
Click to expand...
Click to collapse
Doesn't sound like you are doing a system wipe prior to flashing the ROMs. Make sure you wipe of the phone and the ext partition prior to flashing. I'm assuming you have your card partitioned with fat32/ext3/linux-swap partitions in that order...if not, that could also be your problem.
uansari1 said:
Doesn't sound like you are doing a system wipe prior to flashing the ROMs. Make sure you wipe of the phone and the ext partition prior to flashing. I'm assuming you have your card partitioned with fat32/ext3/linux-swap partitions in that order...if not, that could also be your problem.
Click to expand...
Click to collapse
i wus forgetting to wipe after repartioning , now im on mlign THANKS EVERYBODY UR HELP AND SUGGESTIONS ARE APPRECIATED !!!!!
Hello.
I have a black G1 that has been rooted, danger spl, latest radio, i followed everything from this forum. I currently have Super D 1.11 running on the phone. I decided that i wanted to run apps2sd and a swap partition so i went to micro-center and purchased a class 6 sd card. When I go and try and partition the card in the amon recovery 1.7 i keep getting this error.
Error: Input/output error during write on /dev/block/mmcblk0
Retry/Ignore/Cancel?
First I thought that the card was bad so i went back to micro-center and exchanged it for another one.
Still the same problem.
This only happens with this card, the class 2 cards i have work fine no problems at all.. What is going on here? Did anyone else have this problem? What can I do to fix it?
Chubb
T-Mobile G2 - Stock
T-Mobile G1 - Super D 1.11
chubb16 said:
Hello.
I have a black G1 that has been rooted, danger spl, latest radio, i followed everything from this forum. I currently have Super D 1.11 running on the phone. I decided that i wanted to run apps2sd and a swap partition so i went to micro-center and purchased a class 6 sd card. When I go and try and partition the card in the amon recovery 1.7 i keep getting this error.
Error: Input/output error during write on /dev/block/mmcblk0
Retry/Ignore/Cancel?
First I thought that the card was bad so i went back to micro-center and exchanged it for another one.
Still the same problem.
This only happens with this card, the class 2 cards i have work fine no problems at all.. What is going on here? Did anyone else have this problem? What can I do to fix it?
Chubb
T-Mobile G2 - Stock
T-Mobile G1 - Super D 1.11
Click to expand...
Click to collapse
when reading/writing files from your sd card while booted normally, does android give you errors? If not then I would assume its an issue with amon, try clockworkmod recovery and see if that works. If not then you can partition it with your computer, but you would need a linux live cd at the very least to format an ext partition.
Sent from my T-Mobile myTouch 3G Slide
I know, its not truly bricked. But as of right now it'll only power up if connected to USB power source and will only boot as far as landscape Android text with a blinking underscore. Part of why I didn't get it fixed last night was my unwillingness to leave and aquire a larger micro SD card. I'll be leaving work in a couple hours to go get some stuff to get this thing working again (its 2 days old) heres the recovery plan:
Aquire 4GB + MSD card
Flash a stock 1.1 ROM (the one thats pre-rooted here)
Install (sideload) that stock joint
Read that Elephant book that comes with the Nook because its working again
From there I'm a little confused. Can I flash Clockwork to a MSD and then use that to flash CM7? Or am I oversimplifying here?
From my trial and error the only thing I have gotten to "un-brick" is to boot into monsters pack then switch cards (i used the 128mb version and it removed the rest of the space on my 2gig card) then format cache and system in the mount section of clockwork. then head to install zip and installed a complete restore to 1.0.1. when thats done I head to BN site and got the side load to 1.1.whatever and let it do its thing. From there your up to date and just like new and can then try and "re-brick" it. Ive had mine for less than a week and done this a few times now cause I am never satisfied.........
The nook is never bricked unless it has a hardware failure. One of the great things about the nook is that it has a very early hook in the boot sequence that checks for presence of a bootable SD card. Creating a bootable SD card is easy. Follow the thread which instructs how to make a CWM bootable SD card. You need to choose between the EXT3 or EXT4 version depending on which ROM you will flash. CM7 requires EXT4 version of CWM. If you try to use the wrong CWM version you will get the outcome that you just observed, stuck at android text. If you want to flash the stock 1.1 rom, then you'll need the CWM EXT3 version.
I had the exact same issue. I used this:
The internal CWR workaround is ugly to say the least. So if you NC should refuse to boot or bootloops, which I hope won't, flash this boot repair that I'm adding just in case. Just flash it, no need for formatting.. Use a bootable CWR SD Card.
HCext4-boot-repair flashable zip: http://www.multiupload.com/LN64D4RXEY
6.8 MB
cf963da4043d91d7f4bf8f784cd02d95 HCext4-boot-repair.zip
from the HC v4 on eMMC thread and it solved the issue and I have since flashed just about everything available with success, including dual boot ROMs. I am using a 1gb card.
Calla969 said:
I had the exact same issue. I used this:
The internal CWR workaround is ugly to say the least. So if you NC should refuse to boot or bootloops, which I hope won't, flash this boot repair that I'm adding just in case. Just flash it, no need for formatting.. Use a bootable CWR SD Card.
HCext4-boot-repair flashable zip: http://www.multiupload.com/LN64D4RXEY
6.8 MB
cf963da4043d91d7f4bf8f784cd02d95 HCext4-boot-repair.zip
from the HC v4 on eMMC thread and it solved the issue and I have since flashed just about everything available with success, including dual boot ROMs. I am using a 1gb card.
Click to expand...
Click to collapse
I'll try this and see if I can get it booted. Thanks.
nswenson said:
The nook is never bricked unless it has a hardware failure. One of the great things about the nook is that it has a very early hook in the boot sequence that checks for presence of a bootable SD card. Creating a bootable SD card is easy. Follow the thread which instructs how to make a CWM bootable SD card. You need to choose between the EXT3 or EXT4 version depending on which ROM you will flash. CM7 requires EXT4 version of CWM. If you try to use the wrong CWM version you will get the outcome that you just observed, stuck at android text. If you want to flash the stock 1.1 rom, then you'll need the CWM EXT3 version.
Click to expand...
Click to collapse
That makes things much clearer for me. I knew CM7 required EXT4, but was unaware that the CWM flashed MSD would be properly formatted and couldent be bothered to boot in Linux to do it. Blame lack of sleep. Thanks!