Hi,
I've flashed the official MIUI ROM. And I've tried to replace the standard arial.ttf and arial-bold.ttf in system/FONT with a other font but with the same name. That didn't work as planned so I changed it back to the original fonts which I backed up before. The strange thing is, when using the standard theme, the font does not work in settings menu e.g. So I decided to delete the arial and replace it again, but after deleting the fonts the phone shut down and now it's stuck at starting up, it shows the yellow triangle and it just stays there.
So.. it won't start up because it's missing the arial font.
How do I fix this?
Thanks in advance!
Reflash the ROM.
Either via Odin or CWM, w/e form the ROM comes in.
Do I have to do all the wipes again? As in data/factory, cache, dalvik and format system?
If you flash the same ROM you had before, you usually do not have to do the wipes.
That worked, thanks for your help.
To bad that tutorial on how to change font in MIUI brought me to this. But thanks again.
Not a whole stock ROM, only a stock kernel.
Then flash your custom kernel back via an app running on the phone, that doesn't trigger the triangle.
Check my kernel post (link in sig), there is a short and quick way described on how to do that.
Nope, if you flash via CWM or an app, no triangle.
The yellow triangle is only triggered when you flash a non-stock kernel via Odin and downloadmode.
Related
i was on comrom 2.1, went into cwm wiped data, cache, factory reset, then restored my stock verizon rom. my reason for doing so, is so that i can sell the phone with it looking as stock as possible without actually getting rid of cwm. so it works fine except for one issue, the custom boot screen (it just says android , except that it is messed up and instead of showing horizontally, it flashes vertically) that was on com rom is somehow stuck flashing over the stock boot screens (samsung galaxy s and the verizon logo), is there an easy fix for this? or should i return everything completely to stock?
Thanks for any help!!
You may have a problem if you were on a voodoo setup and just flashed the stock rom with out removing the lag fix...?
My suggestion is to odin dl09 with the atlas 2.2pit file and repartition checked and reboot when its done,
Then ota update to the one you want.
at this point you can power down and odin the recovery you want but you have to have a non stock kernel ready to go on your sd cause if you don't flash one the first time your in recovery, the stock kernel will overwrite it on boot. In the dev stickies there is a list of roms...you can find a non stock, non voodoo kernel to work with stock rom, flash that on there the first time you boot into recovery to make sure cwm sticks.
Sent from my SCH-I500 using XDA App
Hello everyone,
Am asking the above question because while backing up and restoring
my current ROM using ROM manager, the phone (Galaxy S2) restarts with
an exclamation mark above the android man (plz see attachment below).
It gets stuck at that screen and am forced to again restart the phone
after which the back and restore process goes smoothly.
1) My question is will flashing the original kernel solve the above problem?
2) Also will I be able to install apps requiring root permissions after I've
reflashed the original kernel??
3) And will I be able to restore my backed
up ROM if I've reflashed the original kernel??
Android: 2.3.3
FW: XWKF3
Please help
It should and it will get rid of the yellow triangle. just follow instruction in the second post of the thread from chainfire rooting thread.
Thanks for replying. Will it also solve the 2nd and 3rd queries??
2. yes, because your phoe will still be rooted.
3. yes, but you will lose any new apps that you have downloaded in te meantime because you are using a back up made from an earlier version.
Flashing the stock kernel via ODIN in Download mode will remove the Yellow Triangle.
After flashing stock kernel, you lose ROOT, so no, you cannot use applications that requires root.
If your kernel comes with CWM app, you can use that to install a rooted kernel again without incurring another tick at the Custom Binary Counter, and because of that the Yellow Exclamation will not appear.
Backing up with ROM Manager should not invoke the wraith of the yellow exclamation, and neither should restoring either, since it doesn't use Download mode. Are you sure you were using clockwork recovery to restore, and not ODIN to flash?
If the attachment is the blue triangle and not yellow, then it is not the same as the one that custom binary counter triggers.
That looks like 3e (Samsung's recovery)
Hi LiFE 1688,
I rooted my phone with an insecure kernel using this method:
http://forum.xda-developers.com/showthread.php?t=1125414
Then I downloaded ROM Manager, flashed CWM then backed up
my ROM using the option "Backup Current ROM". For restoration
purpose, I used "Manage and Restore Backups" option within
ROM Manager.
The problem is when I try to restore or take another backup
with ROM Manager the device boots up with the exclamation
mark (as seen in the attachment above) and it gets stuck
there.
Then am forced to shutdown and restart my device after which
the backup or restoration process goes smoothly. My question
is how do I remove that exclamation mark which I get after
my device reboots for back/restore purposes.
Note: The yellow exclamation mark which is shown underneath
the Samsung start logo also persists so it would be great that
the solution also removes that yellow exclamation mark as well.
Thanks for reading.
Please help
Tutorial to remove yellow triangle
Thanks alot Cosmic Blue and LiFE 1688
Hi Everyone! just a rookie here in need of a bit of advice.
I'm a Galaxy S II I9100 owner and have my phone rooted and all setup with custom roms and been comfortable with flashing for some time now. My ROM of choice recently was Vanilla Rootbox and have to say the ROM has been fantastic with very few bugs to report. Last night i recieved the OTA update via Goo Manager for Vanilla Rootbox 3.4. I downloaded the full update over wifi and flashed with all wipes no worries. Next step was to flash the latest GAPPS and i figured there would be nothing wrong with flashing the GAPPS zip i had on my sd card that i had downloaded the last time i was notified of a GAPPS update via Goo manager as well. After flashing, wiping everything and rebooting again. My phone then booted up to a series of dialog boxes indicating that many google processes had stopped functioning. apps.google.com etc etc. A similar error has been reported in the Vanilla Rootbox thread by another user but i wasnt able to report this bug their either because my post count is too low to post in a development forum. So after seeing this error i rebooted into recovery to flash my last backup but CWM recovery came back with an error messaging stating it couldnt mount either ext or int sdcard. i did a factory reset which made no difference to the problem whatsoever. I then downloaded ODIN and the latest stock ICS Rom and flashed it via ODIN with no reported errors. My phone now boots through the optus boot animation and is stuck at the Galaxy S 2 screen with the flashing red and yellow animation over the S. If i turn off the phone with the power button, the phone turns off and immediately starts again and gets stuck at the flashing s screen. I've taken the battery sim and ext sd card out and put it all back in only for the problem to persist.
If anyone could help me there's a donation and my thanks in it!
Much appreciated
Nick
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
gastonw said:
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
Click to expand...
Click to collapse
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
darkstar117 said:
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
Click to expand...
Click to collapse
wow wow, leave pit files alone for now, they are nasty.
What stock ROM did you flash? 4.0.4 or 4.0.3?
You can factory reset via recovery mode.
Try installing kies anyway, it can't never hurt. Just make sure all applications are closed before you re-flash.
here's jb leak, might help:
http://www.sammobile.com/2012/11/15/i9100xxlsj-%E2%80%93-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
darkstar117 said:
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
Click to expand...
Click to collapse
Tell me your:
Model
Firmware
Country
Carrier
Always mention this
try flashing jb leak (ROM, modem & kernel package).
Hey Folks,
I'm Freaking out atm -.-
On Saturday my Phone just shut down, restartet and hung in a bootloop. Doing Wipes and Factory Resets didnt helped me. So i pulled the last Joker and flashed as its metioned here. First few Times nothing happend (But ODIN gave me PASSED after Procedure).
Today I tried again with Odin 3.04, Firmware from the Thread (and Vodafone GER Firmware, Factory Reset / Wpies via Android Recovery) and Wooooooow, Phone is booting. BUT its just booting up, I can make some Settings like Choose Language, Connect to WiFi and so on. After ~30 Seconds the Phone reboots, 3-6 Times, then its stucks on Bootanimation (not looping). After a while Phone gets hot on the Bottom.
Soooooo, any can tell me whats wrong with my Buddy?
Cant send it to Service cause i cannot reset the flashcounter (cant install Apps due to the lack of time phone is active)
Im able to root Phone again / replace stock recovery with CWM -Maybe flashable Zip for resetting the counter?
Installing CustomRom will give me a Loop on Splash Screen
I need my freakin Phone
Cheers
try formatting entire phone(all the internal memory) from cwm recovery. then install a stock rom via odin.
sriram231092 said:
try formatting entire phone(all the internal memory) from cwm recovery. then install a stock rom via odin.
Click to expand...
Click to collapse
Okay What I did:
- Stock Vodafone Germany ROM is installed (but not booting right)
- Rooted with CF-Root 6.4 via Odin again - now i can access CWM Recovery
- Wiped everything (system, data, cache, dalvik, battery, preload)
- Flashed Stock ROM via Odin
- Recovery Droid showed up with blue loading bar under it
- Phone is running blue samsung bootanimation twice
- Phone gives me bootsplashloop twice
- Phone shows blue bootanimation and gets stuck on breathing samsung logo (last part of the bootanimation), blue notification LED is breathing
any guess?
after flashing stock ROM via Odin, go to the stock recovery and do a factory reset
Glebun said:
after flashing stock ROM via Odin, go to the stock recovery and do a factory reset
Click to expand...
Click to collapse
Now its looping the bootsplash 3 or 4 times and than Screen turns black.
After wiping Dalvik, and Factory Reset again Phone boots to Bootanimation (Samsung Logo breathing), Bootanimation starts a Second Time Without Sound, than Boot Splash, Bootsound and blue Bootanimation again.
Sometimes with Graphical glitches (the blue circle around samsung text)
But going not further than Bootanimation, no System showing up
is the phone model name (i9300) present in download mode?
aslo, does the recovery say anything about the efs folder?
Glebun said:
is the phone model name (i9300) present in download mode?
aslo, does the recovery say anything about the efs folder?
Click to expand...
Click to collapse
Yep, Model Name is visible in Download Mode.
Odin Mode
Product Name: GT-9300
Custom Binary Download: Yes (14 counts)
Current Binary: Samsung Official
Current Status: Custom
What should the Recovery say about EFS-Folder? Or where can I find some Info about?
-------------Edit--------------------
Oh, wow, cant enter Stock Recovery now...... god damnit -.-
------------Edit2------------------
Works again.... Strange
One Error Msg:
failed to comapre 'system/csc/common/system/app/AppSelect_v3_1_12_PRO_RC1_GA.apk' '/system/app/AppSelect_v3_1_12_PRO_RC1_GA.apk'(No data available)
No ption Found for getting EFS Info
I tried to install CWM using ODIN, and everything seemed to go well, but when I turned the phone up, it will show the model's name and a yellow warning sign, and then go black forever.
I thought it was because the CWM installation deleted the kernel (It was written somewhere in the guide) so I flashed a new kernel with ODIN, but the problem presists.
I tired to wipe it through recovery, and nothing. any help?