Database Develop

Flashing trouble

Okay, i've been having a problem where my device gets stuck at the g1 screen after i flash ANY rom, i've given each rom i've attempted to flash up to 10 minutes each, i have to resort to a battery pull and nan restore to get my phone working again, i've tried flashing roms on two different cards, both with the same horrible end. I've tried reformatting, repairing partition, and wipe wipe wipeing, but nothing seems to work. Any ideas?
my specs:
OS: im running cyanogen's donut (which i have a nan backup of)
SD: 4gb class 6
Radio: latest
SPL: Danger
Recovery: Amon_RA's
Ext3: 1000mb
swap: 32mb

what rom are you tryna flash ill help you out.?
for example if you want the new cm508 t4 then u gotta download the following in the listed order:
1. download & install the newest radio for your device
2. download & install the danger( aka deathspl )\
3. download & install the latest version of cyanogen for your device.
that easy bro. HERE is a gide a friend of mine put together for me and its acurate and current. although there are nomore file links so u have to search google or xda search for the needed files.
good luck.

Requested to be moved to Q&A because this is NOT Development.

okay i've been trying to flash any non ram hack donut and any eclair, none of them make it pass the g1 screen, i've tried everything i have all the correct specs and use the correct procedures but nothing works
i've tired
the latest superD
the latest superE
the stable cyan Eclair
Chomatic Eclair latest
and even though i have it backed up and when
i restore it it works, the cyanogen donut, which i
cannot wipe and flash

xStuntmanEdx said:
okay i've been trying to flash any non ram hack donut and any eclair, none of them make it pass the g1 screen, i've tried everything i have all the correct specs and use the correct procedures but nothing works
i've tired
the latest superD
the latest superE
the stable cyan Eclair
Chomatic Eclair latest
and even though i have it backed up and when
i restore it it works, the cyanogen donut, which i
cannot wipe and flash
Click to expand...
Click to collapse
Why can't you wipe?
Do a fresh nandroid/bart backup of your current working system.
Backup your SDCARD FAT partition to your computer.
Reformat your SDCARD (completely, no ext partition or swap partition)
Make sure you have Amon_Ra 1.7.0 recovery installed
Restart your device in recovery.
Wipe data and dalvik-cache.
Repartition your sdcard
Convert ext2 to ext3
Convert ext3 to ext4 (optional)
Mount SDCARD from Recovery onto your computer.
Re-download your the rom that you want to install and gapps if applicable and place them on the root of your sdcard.
Safely remove the device from your computer
Unmount the SDCARD from the phone (may need a reboot)
Flash your desired rom (don't reboot yet)
Find ddms.bat in the tools folder with the AndroidSDK and run it.
Click logcat
Reboot your device and let it SIT and watch the logcat.
If it seems to stop for a long period of time highlight the lines at the bottom and save the file to your desktop. Open it to confirm that you have the log in your text file.
Upload it to pastebin and post the link in this thread for others to help you further.

[Q] Stuck at Nookie 'N'

Having successfully been using Froyo for a while, I decided to try the CM7 RC. After the flashing the ROM the Nook got stuck in a boot loop, after several attempts, I tried to go back to Froyo. Formatted the System and data under mounts and storage then flashed froyo, now stuck at the Nook N. Repartitioned the boot partition and tried to restore to stock no luck any help would be much appreciated.
- Stuck at Nookie 'N'

A couple questions first; did you reformat your eMMC to EXT-4 by formating system, data, and cache with CWM 3.0.1.0.? Which is required before flashing CM7. If you did then you cannot go back to froyo without reverting back to EXT-3, by formating system/data/cache with CWM 3.0.0.5.
You also may have a messed up boot partition, try flashing one of dalingrin's kernels for froyo or CM7, whichever one you're trying to recover. they are located here: http://forum.xda-developers.com/showthread.php?t=925451
That's about all I can say without knowing if you went to EXT-4

This will fix your problem....
Make a bootable SD immage of CWR. Burn it with a tool of your choice.
After that is done: Open up the sd card and toss the ROM that you want to flash in the root folder. (Hell, or make folders, thats what I do)
Next insert the SD card and restart your nook. You will have booted into CWR where you can then flash the Rom you stored on the SD card.
EDIT: Here is the link of the CWR images: http://legacyschool.us.to/nookdev/clockwork/0.7/

Thanks for the quick response, I am currently using CWM 3.0.0.6, I tried your suggestion of using dalingrin's kernel, no luck. One thing I failed to mention is when I attempted to flash froyo it aborted every time.
btw colbur87 I am using a bootable uSD card...

fpacheco1960 said:
Thanks for the quick response, I am currently using CWM 3.0.0.6, I tried your suggestion of using dalingrin's kernel, no luck. One thing I failed to mention is when I attempted to flash froyo it aborted every time.
btw colbur87 I am using a bootable uSD card...
Click to expand...
Click to collapse
Try getting the 3.0.5.0 CWM from this thread: http://forum.xda-developers.com/showthread.php?t=922870
Then flash it to your uSD card.
Boot to said uSD card
Format /data, /system, /cache
Flash Froyo.zip
Clear Davik-cache
reboot
install OC kernel
clear Dalvik-cache
reboot
I think when you formated with 3.0.6.0 you upgraded your eMMC to EXT-4, and froyo can only run on EXT-3. I may be wrong, but this should set you back up with froyo anyways.
If you're still stuck at the 'n' screen after this, then your /boot partition may be corupted, and someone might have to supply you with a proper one.

This helped a lot it turned out to be the incompatible file systems EXT-3 EXT-4.
I was able to restore my nook to stock. Now I will start over, again thanks a lot....

[Q] try to partition SD card for A2SD+ through clockwork.

Hi all,
my fist post on xda and a noob as well with my first android.
I had someone do my first root and put GEOs rom, as i wanted close to stock to learn android some more, I now want to jump on your rom. the A2SD version
so I try to partition SD card for A2SD+ through clockwork.Then download your rom. By rom manager.
before flashing rom phone info shows (android version 2.3.3 GRI40) and then after flash showing (android version 2.3.3 GRI40) ?
how can my phone be the same rom version pre & post flash with out doing nand back-up?
as that must mean I must have screwed up after flash ?
do I flash this as well ? GRJ22 system dump (boot.img/system.img):
if I do do I flash rom first or system dump first ?
as well not positive when partition SD card for A2SD+ through clockwork that it did partition sd card right way?
I am noob to use ADB and prompt commands and my micro sd slot on comp is not working
is there android app to partition SD card and or check if partition worked on sd card ?
sorry for long post
can anybody help
PS I am trying to flash this rom
[ROM] [GRJ22] N1 2.3.4 OTA ROM v5 (deodex, root, zipalign, busybox, A2SD, TBAlert
thanks in advance

danner_416 said:
Hi all,
my fist post on xda and a noob as well with my first android.
I had someone do my first root and put GEOs rom, as i wanted close to stock to learn android some more, I now want to jump on your rom. the A2SD version
so I try to partition SD card for A2SD+ through clockwork.Then download your rom. By rom manager.
before flashing rom phone info shows (android version 2.3.3 GRI40) and then after flash showing (android version 2.3.3 GRI40) ?
how can my phone be the same rom version pre & post flash with out doing nand back-up?
as that must mean I must have screwed up after flash ?
do I flash this as well ? GRJ22 system dump (boot.img/system.img):
if I do do I flash rom first or system dump first ?
as well not positive when partition SD card for A2SD+ through clockwork that it did partition sd card right way?
I am noob to use ADB and prompt commands and my micro sd slot on comp is not working
is there android app to partition SD card and or check if partition worked on sd card ?
sorry for long post
can anybody help
PS I am trying to flash this rom
[ROM] [GRJ22] N1 2.3.4 OTA ROM v5 (deodex, root, zipalign, busybox, A2SD, TBAlert
thanks in advance
Click to expand...
Click to collapse
If the custom ROM you flashed is base on the same Android version than it's still gonna be the same Android version.
What does the "MOD version" say?
You can partition SD card using CWM or Amon Ra recovery. This is not an app, it's your custom recovery. If I'm reading it right you already have CWM recovery.

baseballfanz said:
If the custom ROM you flashed is base on the same Android version than it's still gonna be the same Android version.
What does the "MOD version" say?
You can partition SD card using CWM or Amon Ra recovery. This is not an app, it's your custom recovery. If I'm reading it right you already have CWM recovery.
Click to expand...
Click to collapse
thanks fo reply baseballfanz
I am on GEOs rom Gingerbread 2.3.3 (GRI40)
and i want to flash this Gingerbread 2.3.4 [GRJ22] the App2SD one from this thread. http://forum.xda-developers.com/showpost.php?p=13430563&postcount=1
I went in to recovery to CW via rom manager and then run partition tool in
recovery, but when trying to DL a APP that needs sd card to be partitioned
it fails to run. saying sd card must be partitioned first.
so I take it CWM recovery failed to partition my sd card and I cant figer out how I my rom version stayed the same after coming out of flash ? with out having to do a droid back-up if I screwed up the flah process? afrer trying to flash a 2.3.4 rom. that is App2SD supported rom.

If you were trying to flash another ROM and it fail to flash for whatever reason, than you're still running your
current ROM. That's why when you left cwm and booted up, it just went back to whatever you had already.
Basically it never got to a point of writing anything, it did some check and found you didn't have correct partition
so it probably aborted.
Sent from my Transformer TF101 using Tapatalk

ok but status bar in recovery did its thing for around 5 minutes with no error message. So I take it CM recovery cannot partition SD card properly ?
is there away around it besides CW recovery and command promts via sdk on pc. like a APP?
or even a APP to check if CW is Partitioning sd card Properly ?
thanks for the help

ClockworkMod recovery should be able to partition your card without an issue. When doing it, it will wipe your card, so make sure everything is backed up. Pay attention to what is on the screen when you do this. It will show you any error messages that may occur. So, if you didn't see any error messages, your card should be partitioned. Same goes for when you flash. It should show you why it didn't flash (assuming it didn't).

You can use minitool partition wizard on your PC and it will preserve your data without wiping it out like Gparted/Unbutu.
To check your partitions download terminal from market or use adb and type
Su
Busybox df -h
It will show partitions fat, ext and swap sizes.

Woodrube said:
You can use minitool partition wizard on your PC and it will preserve your data without wiping it out like Gparted/Unbutu.
To check your partitions download terminal from market or use adb and type
Su
Busybox df -h
It will show partitions fat, ext and swap sizes.
Click to expand...
Click to collapse
thanks,Woodrube
I will give it a go tonight.

I had problems partitioning my SD card with CWM or rom manager... Installed Amon Ra recovery and first time I tried partitions were set

Having problems with ext3 for months now... help :(

Hey xda!
I keep losing my ext3 partition with all my apps every few boots.
It actually usually happens after I have trouble installing/uninstalling apps, which send my phone into softboot mania. A hard reboot usually fixes the app install problem, but every so often unmounts the ext3, which I then have to reïnstall.
Over the past months I've been moving dalvik around, flashing new ROMs, full wipes all the time, checking ext3 for errors, using different software to format re-partition,... The problem is that these issues are non-persistent and so very hard to check if it's fixed. So every time I have to reboot I'll clench my heart and full on rage when I lose ext again
So today after partitioning my SD card again and doing a full wipe, only to lose my ext3 again after hours of setting my phone back up it dawned on me... could this be my recovery??
I'm on CWM 5.0.2.0
It served me well for like a year until I got into the whole A2SD thing...
Problem is I wanna go back to AmonRA now (think that was my first recovery) but Mod Manager won't let me anymore. And I don't have adb anymore, nor the knowledge of how I rooted and did all of that stuff 2 years ago (scatterbrain).
So... Any thoughts on this, is my recovery the issue here? And can I flash AmonRA without having to go through adb and all that?
tl;dr
My ext3 is ****ed (sporadically), I THINK recovery is to blame. I suck at adb, how to flash AmonRA?
Any help will be greatly appreciated!

Yeah...quit using CW around version 3 due to the exact same BS...I found I had to actually repartion the whole SD card several times and even lost my backups once...
AmonRA was good but the newest greatest and most amazing recovery inho is 4EXT! http://forum.xda-developers.com/showthread.php?t=1291970 it has been the best recovery I have used bar none and the developer is awesome with support if needed!

Thanks for responding so quick, you did not lie about the awesomeness of 4ext!
I'm having a blast tinkering with the recovery control settings
Since we're in the same boat, maybe you can be of advice.. Would upgrading to ext4 do me any good? Any upsides to it?
When I got into A2SD, ext4 was too new and considered to be "DANGEROUS EXPERIMENTS" xD

EXT4 is the stock filesystem for all new Android phones.

Jack_R1 said:
EXT4 is the stock filesystem for all new Android phones.
Click to expand...
Click to collapse
Oh ok, so it would be ridiculous for me to get it now, thanks for clarifying
For the record, this issue has (as it seems for now) been resolved by flashing AmonRA and wiping -> repartitioning the card with that.

While AmonRA was great I found many advanced features in 4EXT. For instance you can go from ext3 to ext4 and back again with just the push of a button. EXT4 is a more efficient file system and most ROM's nowadays should support it...if not just switch back to ext3. Also 4ext will check for filesystem errors on your SD card and also check partition alignment. If you use 4ext to partition it will ensure proper partition alignment which the other recoveries don't do....

While I was impressed with ext4 features and all, I tend to go with stability over advanced features. Which is why I'm on Amon_RA's recovery, and also why I'm on an OTA build ROM, so ext4 support is ruled out for me. I want my phone just to have all the functionality I need, and have maximum reliability so I can always depend on it.
In the ext4 thread there's a good example of why I will mostly choose stability over extended functionality

Galloway said:
While AmonRA was great I found many advanced features in 4EXT. For instance you can go from ext3 to ext4 and back again with just the push of a button. EXT4 is a more efficient file system and most ROM's nowadays should support it...if not just switch back to ext3. Also 4ext will check for filesystem errors on your SD card and also check partition alignment. If you use 4ext to partition it will ensure proper partition alignment which the other recoveries don't do....
Click to expand...
Click to collapse
I confirm 4EXT is the best recovery (using it for few months now without any pbs) and ext4 partitions are reliable now! Don't hesitate.

[Q] Upgrading to Texas ICS p10 checklist

I've flashed custom roms many times, but I have a couple questions regarding Texas ICS p10.
Currently running:
MeDroid 4.1.
BlackRose with System 220MB Cache 16MB Data 200MB
Amon’s RA recovery
Here's a checklist of what I should do:
Backup everything.
Update Blackrose to system 210 / cache 8 / userdata 218.
Wipe everything / factory reset 3 times
What do I need to do regarding formatting/partitioning the sdcard? ext4? setting dalvik cache to use sdext or data partition? In Amon's RA recovery, I have a "partition sdcard" option, with options to
- Partition SD
- Repair SD:ext
- SD:ext2 to ext3
- SD:ext3 to ext4
Do I need to do anything to get a2sd working other than rebooting a couple times?
Flash Texas' p10.
Flash google apps.
Restore.
Done.
Thanks in advance.

Sounds like you got it
if you are ext4 from medroid, you should be fine--not sure, but ext3 may work too
your current partition sizes are ok
see this on a2sd
http://forum.xda-developers.com/showpost.php?p=21222591&postcount=1374
i think you only rin a2sd install one time
i went to p10 and tiamets kernel and had some issues, restored back to p9 and lost my app links--even a sdcard reformat didn't work with p9 so went back to a medroid nandroid
haven't had time figure it out
medroid 6.1 is pretty stable for me
Ken

How can I check if the sdcard is formatted as 4ext?

Isn't it dangerous having a cache partition of only 8 MB?
Sent from my Nexus One using Tapatalk

maybe gparted or a partition tool program
i am having sdcard issues atm so can't test--terminal em can check, forget command, but sometimes it wasn't accurate for me
i don't know that 8mb is dangerous--some larger apps may not work right--depends how rom handles them. cm7 handles them well--miui doesn't--or so folks say

Don't know about 8MB cache, but it's kinda vurnerable to have only 210MB system partition now. If you have any plan to switch to other ics rom, i.e. MeDroidMod, you'll only have a little size left, or even nothing left. I repartizied back to 220/16/200, which is acceptable for any rom.
Sent from my Nexus One

Ok, so I followed the checklist I listed above. p10 stalls at the blue X boot logo for 10 minutes now. Anyone know why it's doing this? I'm going to go do a full wipe/repartition/reinstall again. I left my hboot alone, as suggested twice.

Actually, I opened blackrose and it automatically installed the latest blackrose, which put my phone in recovery and apparently wiped the rom??? Anyway, now I couldn't change hboot partitions anyway, so I proceeded with the rest of the checklist...

Have a 220/16/200 partition?
Boot into recovery, if you have 4ext recovery, you can format everything except sdcard, then flash p10 & gapps.
Sent from my Nexus One

Yeah, I have that partition. I just wiped everything, repartitioned the sdcard and reflashed... currently 8 minutes in the boot animation...
Not sure what to do from here.

Installed latest medroid 1.3.2a and it just keeps booting back into recovery.... hrm.
Do I need to flash a boot img as described here?
http://forum.xda-developers.com/showthread.php?p=22731102#post22731102

Ok, it installed. Updating blackrose, which took out my ROM for some reason, reverted to the default hboot as far as I can tell. I put the 220 version back on wiped and reflashed and it booted just fine.

Ended up using Medroid 1.3.2a instead of TexasIce p10. Even though p10 has HWA, it has bugs (browser rendering on zoom takes 2 seconds, sometimes longer) and isn't as fast as Medroid in general.

just got 1.3.2a and is running great
samuaz is loading HWA version now, but may have same issues as T's

First boot on ICS may take a while ! Just chill out ^^