Database Users

[Q] First Time ROM Flash - Stuck On Tattoo Boot Screen

Hi
Okay i am pretty much a complete noob at all of this.. so give us a fair chance.
Ive just attempted to install nFinityGB v0.6 on my HTC Tattoo - and failed, quite miserably.
I've followed the following tutorials:
Goldcard - http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
Rooting - http://theunlockr.com/2010/03/16/how-to-root-the-htc-tattoo/
Loading a rom - http://theunlockr.com/2010/03/30/how-to-load-a-custom-rom-on-the-htc-tattoo/
I downloaded, and moved the zip file across onto the SD card.
Turned off, Booted Recovery - made a back-up, wiped, reset and then installed flash.
Reboot > stuck on Tattoo screen.
Have tried re-install - no joy.
On the ROM's page it talks about a ClockworkMod - which i have no clue on, because the tutorial given; makes no sense to me; a noob.
(http://forum.xda-developers.com/showthread.php?t=892401)
Someone please help, im backing using my old Sony Ericsson C305...

You probably need to format system partition after doing wipe, and before flashing rom. Formatting system partition is not an option in AmonRa afaik, so you would need to install ClockworkMod.
http://forum.xda-developers.com/showpost.php?p=9192029&postcount=21
Once you have ClockworkMod installed, make a backup with it before flashing new rom, as I don't think backups from AmonRa can be used with it.

ok well ill try that

still got problems :/
ive installed ClockworkMod - latest one.
Wiped user data
Wiped partition data
Install .zip
Reboot
Once again hung on Tattoo screen.
Any ideas?

Mounts and storage -> format system?
First boot takes 3-4 minutes.

Broke my recovery

Nook was running cm7
I went here http://forum.xda-developers.com/showthread.php?t=958748 and downloaded recoveryfix.zip and installed it
that was silly
now nook is stuck at book
How can I reflash cwm 3.0.2.8?

mrkkk said:
Nook was running cm7
I went here http://forum.xda-developers.com/showthread.php?t=958748 and downloaded recoveryfix.zip and installed it
that was silly
now nook is stuck at book
How can I reflash cwm 3.0.2.8?
Click to expand...
Click to collapse
Do you remember what version of the stock OS you had before you installed CM7? What happened, was that file that you downloaded is specific to a version of the stock OS.
Make yourself a bootable CWM card by following the directions HERE
Then download the attached file that goes with your stock OS version, and put it into the root of the CWM card.
Boot the device with that card, and flash the file. Remove the SD card when done, and reboot. You should now be back into your CM7. At this point to can flash CWM back onto the NC, or leave it off.

GMPOWER said:
Do you remember what version of the stock OS you had before you installed CM7? What happened, was that file that you downloaded is specific to a version of the stock OS.
Click to expand...
Click to collapse
Any way to determine that now?

mrkkk said:
Any way to determine that now?
Click to expand...
Click to collapse
Not really, the version 1.1.0 update came out at the end of January, and the guide that you linked to was made in February, so I would say that there is good chance that you were not on version 1.1.0. I would start with the 1.2.0 package, and work my way down.

No luck
Got meself a monster root pack - http://code.google.com/p/monster-rootpack/downloads/list
1.2.0 and 1.1.0 gave me install failed after rebooting
1.0.1 its still stuck at "Touch the future of reading"
Dont I want to flash a good copy of CWM back so that it can boot cm7?

mrkkk said:
No luck
Got meself a monster root pack - http://code.google.com/p/monster-rootpack/downloads/list
1.2.0 and 1.1.0 gave me install failed after rebooting
1.0.1 its still stuck at "Touch the future of reading"
Dont I want to flash a good copy of CWM back so that it can boot cm7?
Click to expand...
Click to collapse
The NC does NOT need CWM installed on the device to install or run CM7. A lot of people don't install it because of problems like this. I just did a restore of my CM7 image, and took the same steps as you. When it reboots and says install failed, I just shut it down and restarted right back into CM7.
The problem with the package that you had started with was the fact that besides the recovery files it installed a version of u-boot.bin that does not seem to be compatible with your device. The packages that I put up include each version specific u-boot.bin and recovery files.
I would flash the 1.2.0 file again, this time when it restarts and says install failed, just reboot the device, and it should go into CM7. At the very least, at this point you could do a full factory restore.

Update
before seeing your last message I built cwm 3.2.0.1 card using http://www.techerrata.com/dl.php?path=15&file=1gb_clockwork-3.2.0.1-eyeballer.zip
downloaded cm7 latest nightly
flashed it
applied titanium backup
was up in about an hour
BTW I do like CWM recovery, I can take nandroid backups time to time
Thanks for helping

[Q] Tried and Failed, what should I do next?

Right basically if you've followed my last thread, http://forum.xda-developers.com/showthread.php?p=27975788#post27975788 it turns out I haven't got anywhere really. Today I managed to flash both froyo and GB but after trying to root both and install a custom ROM it would fail and I'd end up in a bootloop. Normally I'd just reinstall the dload files from the SD card and start again. Now however, when I go to boot the dload files, I get pink a screen (with usb plugged in I have the image folder with various files). When I try and boot recovery, nothing happens, I've tried replacing the recovery image, but no success. So now I'm left with a phone that does pretty much nothing other than bootloop or turn pink on command. Any suggestions on what I can do to install froyo or GB?
Sorry and thanks again.

Before root the rom(s) run ok?
And how you root the device? Also are you sure that the root have success? How you check it?

The root was fine, followed the instructions from the thread in dev section, ran the one click root everything was fine, swapped the recovery to get v5 used remount and astro explorer. went to CWM, made sure i had a rom that ran with the kernel, installed it everything said it was fine reboot into a loop. my options now are boot loop or pink screen, it wont even pick up the dload from the sd card.

So the bootloop happen with the custom rom you flashed from recovery mode?
Which rom you flashed? Did you wipe data/cache/dalvic_cache before the reboot?

Indeed I did. Something corrupted in the image folder. So I found a custom Image folder by the guy who's developed the v5.5 of CWM. In his signature theres a load of zip files one of them had a custom Image folder which Ive swapped in to which the phone has read the dload files now finally. Im hoping this will work.

If the device boots fine with the official roms, and bootloops with the custom, there is nothing wrong with the image file. The problem is with the rom that you try to flash and maybe with the recovery version.

For whatever reason ive tried multiple roms today none of which have booted, the closest i came was the oxygen rom but that failed at the oxygen splash screen. As for my problem, something had happened after i flash a rom, no idea what but a file in the image folder had gone bad. after swapping that out for one i found, dload from the SD card booted and installed. I now have a stock GB running which i think i'll leave it at that. i'm clearly missing something when i flash a custom rom whether it be bootloader related or a incompatible rom to kernel. either way now it works, i'll leave it as is. Thanks for the help though much appreciated. I'm hoping other will find the help they need here.

Dave759 said:
For whatever reason ive tried multiple roms today none of which have booted, the closest i came was the oxygen rom but that failed at the oxygen splash screen. As for my problem, something had happened after i flash a rom, no idea what but a file in the image folder had gone bad. after swapping that out for one i found, dload from the SD card booted and installed. I now have a stock GB running which i think i'll leave it at that. i'm clearly missing something when i flash a custom rom whether it be bootloader related or a incompatible rom to kernel. either way now it works, i'll leave it as is. Thanks for the help though much appreciated. I'm hoping other will find the help they need here.
Click to expand...
Click to collapse
The only cases I can think a custom ROM won't work are
- installing a .32 ROM over a ROM based on .35 and vice versa
- installing a custom ROM without wiping data and caches of the previous ROM, especially if they are not related, like not different builds of the same ROM
- installing a .32 ROM using cwm other than 5.0.2.6 and below
- installing a .35 or ics ROM using a cwm other than 5.5.0.4 or 5.0.2.7
Are you sure you did none of that?
Sent from my U8800

Recovery can't mount data

Hello, I am a novice at best when it comes to this. That being said I have successfully Unlocked my boot-loader, rooted and installed roms to my phone. Recently when using TWRP 2.7 I noticed that it would not mount data when restoring my backup. I then noticed it would not mount data when creating a new backup while using TWRP 2.7. I then installed CWM latest recovery. It does the same thing. In the process I got stuck in CWM and had to AP Fastboot to stock 4.4.2. Now with CWM it will not mount data when doing a backup. I cant load a rom without having a secure backup. What can I do? Need help! Calling all devs!

I'm pretty sure that the only recovery available is CWM for the RAZR HD. However, that recovery can't mount data. I don't think there is a custom recovery right now that had full functionality for the RAZR M.
With that said, the kernel sources have been released, so I would say its only a matter of time before an updated recovery is available that can support mounting data.
Sent from my XT907 using Tapatalk

queue72 said:
I'm pretty sure that the only recovery available is CWM for the RAZR HD. However, that recovery can't mount data. I don't think there is a custom recovery right now that had full functionality for the RAZR M.
With that said, the kernel sources have been released, so I would say its only a matter of time before an updated recovery is available that can support mounting data.
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
I have had TWRP work just fine in the past. Others are having no problem with them as I can tell. This is an original Razr M.

ehunter74 said:
I have had TWRP work just fine in the past. Others are having no problem with them as I can tell. This is an original Razr M.
Click to expand...
Click to collapse
There is no TWRP designed for the KK update, yet. CWM is only working aftermarket recovery right now. TWRP should be out any day.

OK let me give more details. I was running Beanstock Rom with Android 4.3 on my ORIGINAL XT907. I was running TWRP 2.6 flawlessly. I tried to load a new ROM (KitStock 4.4.2). When I tried to backup my current configuration with TWRP it would not mount data during the backup procedure. I panicked and backed out. I seen that CWM was a better choice and installed CWM v6.0.4.8 It also would not load data during backup. I then tried to back out of that and it got stuck on boot. would not go past no matter what. tried to load KitStock ROM anyway. Same effect. I could still get back into CWM recovery and also bootloader. I then installed the latest STOCK ROM I could find and it is version 183.46.10XT907.Verizon.en.US. Kernal is [email protected]#1. Build number KDA20.62-10.1 Android version 4.4.2

I think what I have discovered is that I must have a "working" corrupted file script whit this stock ROM. I discovered that if I formatted my SD card I could mount the data and backup my nandroid. So my SD card was corrupted??? Also after I knew I had a good backup when I tried to install CM10.1 it gave me a status 7 error. Ok did the status 7 fix by editing the script on two different ROMs. It still aborts installation. Now I consider myself a noob but I'm no stranger to the ROM installation process. I've done all the right steps. Backup. Wipe 3x, mount system, install. This seems like a deeper problem. Please HELP!

Huawei Ideos ROM Help

Hi all technical gurus and experts
I have the standard u8800 X5 and have managed to recover it after two weeks after bricking it quite properly. The question I have is that I am unable to get the official GB update to install correctly over the stock Froyo Rom.
I had the phone running on the official GB for a number of years unmodified without problems until I rooted the phone for the first time.
In an attempt to fix it I managed to remove the OS completely (I know I know). I have finally managed to recover the phone by flashing the stock 2.2.2 B138 rom. Next I attempted to upgrade to to the official 2.3.5 B526 I downloaded from the huawei site. Every time after it installed it boot looped. Pull the battery out and put back then I do a factory reset from the recovery and the phone would work. At next restart it would have multiple error messages about processes unable to start and would reboot back into the boot loop.
Back to square one and re flash the froyo.
Eventually I flashed oxygen 2.3.7 over the froyo, which is stable.
I have root access and CWM 5.0.2.6 installed.
Please help as I would like to install a newer Rom like Aurora ICS or CM10, what do I need to do to get it right?
Thanks in advance.

Bump for @Blefish

Its difficult to understand why this is happening. However, if you installed 2.3, your baseband is updated and theoretically you should be able to switch the ROM, even though the stock ROM is crashing. Huawei ROM is loading some of the items from the "cust" partition, it might happen this does not have the necessary items but I doubt it.

Thanks for answering. You are the foremost expert on the u8800 that I know of.

Blefish said:
Its difficult to understand why this is happening. However, if you installed 2.3, your baseband is updated and theoretically you should be able to switch the ROM, even though the stock ROM is crashing. Huawei ROM is loading some of the items from the "cust" partition, it might happen this does not have the necessary items but I doubt it.
Click to expand...
Click to collapse
If you mean amms.mbn it is not the thing which controls switching between roms.
OP should check partitions, I think all the problems are from them (and from appsboot.mbn too ).
Last time I bricked my phone, it refuses to install any roms (I was on B919 and was not able to install B919 :silly: ) except B939.
I have checked logs, located in /sdcard/dload, and found some "partition error", or "installing new partitions", etc.)
PS: Solved.
Cust partition is not a problem, I remember I cleaned it from my U8860 and everything was ok.
OP, try to install different mods and if nothing helps, ask someone to send you a dump.

What you said about the updated baseband gives me an idea. If I can install CWM 6 with es file manager, after updating to the GB. I can use your partioning tool and then install Aurora or CM10. Do you think that could work?

missioner said:
What you said about the updated baseband gives me an idea. If I can install CWM 6 with es file manager, after updating to the GB. I can use your partioning tool and then install Aurora or CM10. Do you think that could work?
Click to expand...
Click to collapse
I am quite sure it could work. But I would suggest installing B518 or at least install pink screen unlock before you do repartitioning.

Thanks I will keep that in mind.
I will install ES explorer tomorrow and see about an updating the recovery

I checked the size of the internal sd card as Jeka suggested and total size is 1.4Gb. I remember that the internal SD card should be 2Gb if the partition is stock. I did run the Blefish recovery repartitioning zip before I so wonderfully bricked the phone, it is most likely the partition size that is causing the error.
I have the 3 partition zips downloaded including the stock partition one, so I will give it a go this weekend if my son agrees. It is his phone and he appears to be enjoying the oxygen rom currently installed. Ultimately I want an ICS rom installed though.

After much time I have solved the problem.
The phone has been running for some time on oxygen 2.3.7 GB, but sadly started having problems again. This time due to the dodgy games my son had installed on to the phone.
I flashed the official GB to update the baseband and then realised I had made a small mistake as I had also unrooted the phone and replaced the cwm recovery with a stock one.
Some hasty searching later and installing ES FILE MANAGER I managed to find and install a rooted recovery. I did this as my other root methods were unsuccessful.
This allowed for me to install the Team Win U8800 recovery. As per the previous post the phones partitions had not been restored to stock, so I installed the Aurora ICS Lite Rom.
Very happy with the results and I have to say that the TWRP recovery is top notch.