Database Users

[Q] Stuck at "Tattoo" splash, when trying Clockwork.

When i try to restart my phone or just startup my phone in recorvery, it gets stuck on the "Tattoo" screen.
I've got the Clockwork mod 5.0.20 or something like that installed...
What do i do?

-Bump-
Anyone?

same problem, 5.0.2.0, now i'm stuck on tattoo, easyest way to fix this or restore default?
EDIT: + i wiped data/factory reset ... so i dunno if tattoo's now empty or with unbootable android. cant boot it, how to restore 1.6 (got backup with rom manager)
(sry for my bad english)

Same issue here.
I was on CM7.0 stable. Today, I updated clockwork to actual latest version (same as the gentlemen above), flashed new recovery.
When I've tried to backup or reboot-to-recovery, infinite booting with TATTOO splash screen was all I've got. But after removing battery, I was able to boot with normal boot path.
Later today, I've tried to Fix Permissions through Clockwork and after reboot, I was stuck with TATTOO splash screen even after battery removal.
I've tried factory reset, it seemd to be successfull, but with no actual result - I'm still stuck with splash screen and cannot do anything.
Does somebody have any idea, what to try?

I was not able to recover the CyanogenMod, however downgrading to stock rom via GoldCard was possible. (reference is here: http://forum.xda-developers.com/showthread.php?t=1283429&highlight=stock+rom )

Try flashing cyanogenmod stable 7.1.0.1 and then re-install the recovery via rom manager...Tell me if it resolves

Try to get into recovery from boot loader or flash it manually with adb...

Flash ClockWorkMod a couple of times: See this:http://forum.xda-developers.com/showthread.php?t=1293096&page=2 and http://forum.xda-developers.com/showthread.php?t=1297141
Hope I helped you. Hit thanks if u liked it.

[Q] Recovery boot fail after updating to 4.1.2

Before the problem, I had a 4.1.1 rooted unlocked N7 with original ROM. I decided to apply the OTA update (03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip) from TWRP recovery using the option to manually install zip updates.
The tablet rebooted, and I used Voodoo OTA RootKeeper to regain root access. Everything worked fine, I had no error messages at any moment during the procedure and the 4.1.2 update was applied successfully, as I could verify in the info section and by testing the landscape mode.
But, when I try to reboot in recovery using the option in ROM Manager, all I get is the little robot on his back image without any message. The only way to get out of this screen is to press the power button for a few seconds until it reboots into Android. Everything is fine except the recovery mode.
I tried to reflash the recovery image using Wug's Toolkit to no avail. I tried CWM, TWRP and stock recoveries but none worked. I always get the same screen with the robot on his back when I try to boot into recovery. Booting normally is always fine, only recovery seems to be affected. If I use Wug's toolkit to boot a temporary TWRP recovery image, it works but I want to be able to boot as before, with ROM Manager.
Any ideas? Is there a solution other the wipe it all and restart from scratch?
[edit] I can start into Fastboot but if I try to go to recovery from there, the same thing happens...

I fixed it by flashing the older 3.34 bootloader. So something is wrong with the new 3.41 bootloader.

There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app

bagofcrap24 said:
There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Not true. I flashed the update through cwm and everything went fine. When you reboot the system, cwm asks if you want to flash recovery and keep root. I denied to flash the stock recovery and I kept the root. After that you can't get into recovery at all (stock or cwm or whatever). but if I downgrade my bootloader to 3.34 everything is ok. I also installed new bootloader through cwm manually again and after that I can't boot into recovery.
Btw... How to flash bootloader.raw with fast boot???
Sent from my Nexus 7 using Tapatalk 2

sikagoon7 said:
I think you are a bit misinformed. When you flash the OTA the recovery-from-boot.p is installed by default. It resets the recovery to stock every time you reboot. CWM does nothing to remedy this. The only way to fix it is to remove or rename the file to disable its function. After and ONLY after this will you be able to flash recoveries by choice and boot into them.
And while it is your choice to use whatever recovery you desire I personnaly think using stock recovery and adb sideload is the safest when it comes to signed stock OTA.zips. After that you can root and flash your recovery of choice as if you have a brand new device.
When it comes to the bootloader. Stock system, boot, and recovery verify which bootloader you are using. JRO03D looks for 3.34 and JZO54K looks for 3.41. I don't know the implications of switching them but I don't think I will test that. I've already had a bad experience with dismantling a bootloader. The bootloader is an IMG file. Download the JRO03D factory image from Google's website and extract it. Inside will be a file named bootloader-grouper-3.34.img. THAT is the stock JRO03D bootloader and that is what you need to flash using: fastboot flash bootloader bootloader-grouper-3.34.img.
Click to expand...
Click to collapse
Yes I know that and did that from the beginning (renamed the file) but the point is that you can't boot into recovery (stock or whatever). It tries to boot into recovery I think but it reboots again and loads the OS. I'm using 3.34 booatloader with 4.12 and haven't got any probs yet.

Finally Got it Working
I tried one last thing yesterday. I got into ROM Manager and used the option to flash CWM Recovery. Then I rebooted in CWM (using the ROM Manager option). All was fine and when I chose the option to reboot, CWM asked me if I would like to make the custom recovery permanent because it would otherwise be rewritten at boot (this is what caused my problems, I believe). I choose to do so and it worked normally after that.
I then downloaded the TWRP recovery (http://www.teamw.in/project/twrp2/103) and installed it with Wug's Toolkit using the option to flash a permanent Recovery from a file. I didn't modify the "recovery-from-boot.p" file because I thought that CWM already did that. Tested booting into recovery again and all is finally OK with TWRP.
One of the benefits of the 4.1.2 update is that I can now boot into recovery from the Fastboot menu.

I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m

diomark said:
I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m
Click to expand...
Click to collapse
There are mixed reports on bootloader 3.41 and booting recovery. I have not been able to properly boot recovery from 3.41 under any circumstances. If you have this issue as well, flash the 3.34 bootloader from JRO03D. Doing this has allowed me to use recovery again.

I was running 4.1.2 with old bootloader 3.34 and had a SOD while my Nexus was charging last night.
In Faux123's kernel thread, he told me:
You should use the new boot loader and stick with CWM for now until TWRP get their stuff compatible with 4.1.2. Boot loader initialize the power regulators to some know state for the machine to boot until the kernel takes over.. and the new kernel is expecting it to be initialize certain ways... This was the biggest difference between 4.1.1 and 4.1.2... so I HIGHLY recommend using the matching bootloader...
Click to expand...
Click to collapse
Steps I had to take to get 4.1.2 (rooted, stock rom, custom kernel):
flash stock 4.1.1 boot.img and recovery.img
flash 4.1.1 bootloader 3.34
flash recovery TRWP recovery
flash SuperSU (regain root)
flash CWM lastest recovery 6.0.1.5 (beta) based on Faux123 advice above
flash 4.1.2 bootloader 3.41
No problems so far. This whole process has taken days...
I'm finally where I want to be.

Oops, wrong thread...

4.2.2 recovery help

Hi! Im a noob with a couple of questions hope anyone can help me...
I was recently at 4.2.1 on my nexus 7 had twrp installed, and accidentally updated to stock 4.2.2 my cstom recovery wash flashed by a stock one and forced me to install another via fastboot, but this time i installed cwm then i decided to go back to twrp coZ i dont personally like cwm,. So here is my problem i used rom toolbox to reboot into recovery and it said that i have a cwm installed but when i rebooted i was on twrp, its confusing did i installed both? And made me decide to use rom manager it said that i have twrp and cwm already installed how can i uninstall cmw...
Hope u could help me.. Anyone?

ROM manager plays a clever trick where it temporarily replaces the recovery, even though it is not flashed into the recovery partition.
If you start the recovery from the bootloader, you'll see TWRP; and if you boot into recovery from ROM manager, you will (eventually) see the CWM recovery (you may see some graphics produced by TWRP first, though).
If you have a way (separate from ROM Manager) to boot from the OS into the recovery, you will get TWRP.

bftb0 said:
ROM manager plays a clever trick where it temporarily replaces the recovery, even though it is not flashed into the recovery partition.
If you start the recovery from the bootloader, you'll see TWRP; and if you boot into recovery from ROM manager, you will (eventually) see the CWM recovery (you may see some graphics produced by TWRP first, though).
If you have a way (separate from ROM Manager) to boot from the OS into the recovery, you will get TWRP.
Click to expand...
Click to collapse
Hi thnx for the help, actualy i was able to boot into twrp already and i belive i flashed it completely, my only concern is did i overwrite the cwm in my rec partition? Or it is still there?
Sent from my Nexus 7 using xda app-developers app

There can be only one bootable image in the recovery partition at a time.
If you boot from the bootloader into recovery, and you see TWRP... then that is what is flashed there.
If you want to see what I am talking about, go into ROM manager and select the menu item that causes a boot into recovery. What you will see (after a little bit) is the CWM U/I.
What is going on is that ROM manager boots whatever recovery is actually flashed in the recovery partition, and then immediately replaces /sbin/recovery with it's own version (CWM) and then kills & restarts that same program.
So - what you *see* is the CWM version of /shin/recovery - running on top of the kernel & ramdisk were provisioned by the whatever recovery was actually flashed to the recovery partition.
If you want to actually flash CWM to the recovery partition, ROM Manager has a menu item for that. I'm not sure what the exact wording is.
If you are confused by this, just read the first two sentences in this post.

Problem with installing TWRP

My phone came with version 66.77.... (MIUI 6) from the reseller.
I have installed TWRP, rooted the device using adb and then flashed 5.9.24. So far so good.
After some time i decided to try AOSP ROM. I made a backup in TWRP and then flashed AOSP using TWRP. No problems so far (cleared cache, dalvik etc)
Then I wanted to revert back to 5.9.24. I cleared cache dalvik etc, and then I cannot remember anymore if i have reflashed 5.9.24 or restored the backup made previously from TWRP, the thing I wasn't able to boot into recovery anymore. The phone was stuck on the teamwin logo if booted into recovery but normal boot was working fine.
Then i reflashed twrp using adb.
After doing that, my phone was still stuck on the teamwin logo when booting into recovery, but with normal booting i was getting infinite boot loops at Mi logo screen.
After several ours of tries, i was able to solve the normal booting problem by flashing the stock recovery (so the phone is now back on the 5.9.24 - and working fine) but when I try to flash twrp using adb the same symptoms as before:
- Recovery boot - stuck on teamwin logo screen
- Normal boot - boot loops
I already tried to flash via Updater app, Flashify and Windroid nothing worked.
Can anyone help me to get this custom recovery working, please?
Thanks
Regards,
Nick

lukke04 said:
My phone came with version 66.77.... (MIUI 6) from the reseller.
I have installed TWRP, rooted the device using adb and then flashed 5.9.24. So far so good.
After some time i decided to try AOSP ROM. I made a backup in TWRP and then flashed AOSP using TWRP. No problems so far (cleared cache, dalvik etc)
Then I wanted to revert back to 5.9.24. I cleared cache dalvik etc, and then I cannot remember anymore if i have reflashed 5.9.24 or restored the backup made previously from TWRP, the thing I wasn't able to boot into recovery anymore. The phone was stuck on the teamwin logo if booted into recovery but normal boot was working fine.
Then i reflashed twrp using adb.
After doing that, my phone was still stuck on the teamwin logo when booting into recovery, but with normal booting i was getting infinite boot loops at Mi logo screen.
After several ours of tries, i was able to solve the normal booting problem by flashing the stock recovery (so the phone is now back on the 5.9.24 - and working fine) but when I try to flash twrp using adb the same symptoms as before:
- Recovery boot - stuck on teamwin logo screen
- Normal boot - boot loops
I already tried to flash via Updater app, Flashify and Windroid nothing worked.
Can anyone help me to get this custom recovery working, please?
Thanks
Regards,
Nick
Click to expand...
Click to collapse
Tried this: http://en.miui.com/thread-152550-1-1.html?mobile=2
Sent from my 2014817 using Tapatalk

timberwolf60 said:
Tried this: http://en.miui.com/thread-152550-1-1.html?mobile=2
Sent from my 2014817 using Tapatalk
Click to expand...
Click to collapse
i saw the request of the message but i am not using a custom recovery on my phone,i use a custom dev rom made by miui france.
i think some china dev rom comes rooted by default with custom installer updater and gapps like mine.
i think twrp is not fully compatible with this device yet.

Have you try with sp flash tool method ?
http :// en.miui.com/forum.php?mod=viewthread&tid=156838&extra=page%3D4&mobile=2

I just installed TWRP for the first time ever. I used the Flashify App from the Play Store, installed it and gave it root permissions and just selected the TWRP image on the phones internal store. Seemed to work just fine and did not have to plug my phone into a computer

Question [CLOSED] Delete!

Delete

Just flash stock 1.0.1 boot and then try to install the update ?

Delete

Boot means you are just booting from it, there is no way u can install updates with that u have to flash the boot but not sure if 1.0.2 boot works with your 1.0.1 rom but you can try fastboot flash boot stock 1.0.2 or what ever the file name is for you

Think I was doing that anyway will it be best to uninstall magisk fully first then flash the stock boot and then try

fmotta61 said:
Solved by rebooting to bootloader, flashed stock boot image, rebooted.
Installed OTA.
Reboot to bootloader.
fastboot boot magiskpatched.img (or what is called). Attention: boot not flash.
Reboot and start Magisk, direct installation, reboot and voila.
Other method do not work because presumably you flashed magiskpatched.img directly and due to this Magisk cannot restore automatically boot image.
Click to expand...
Click to collapse
You can try to do it this way. Worked for me from 1,1,0 to 1.1.2

Delete

Mobilemandan1 said:
Tried that way I got to the install OTA part but that didn't work still gives me the download failed error
Click to expand...
Click to collapse
Then you probably need 1.0.1 boot too and i dont know where you can find that

Delete