guys i just rooted my nexus s, went well and installed font installer root. my phone is stuck with the ics animation and wont boot up, what to do, i tried restore through recovery it says no files found
jafferkhan said:
guys i just rooted my nexus s, went well and installed font installer root. my phone is stuck with the ics animation and wont boot up, what to do, i tried restore through recovery it says no files found
Click to expand...
Click to collapse
Wipe Dalvik Cache. It's in the recovery menu @ "Advance". Maybe it'll work.
And what is "font installer root" ?!
devil188 said:
Wipe Dalvik Cache. It's in the recovery menu @ "Advance". Maybe it'll work.
And what is "font installer root" ?!
Click to expand...
Click to collapse
thanks man, i had to reinstall the entire system again but now i am on jelly bean... font installer root is an app which installs custom fonts on the system, as of now it's a no go app as far as i am concerned, it bricked my HTC One V and now also messed up my Nexus S so stay away from it
jafferkhan said:
thanks man, i had to reinstall the entire system again but now i am on jelly bean... font installer root is an app which installs custom fonts on the system, as of now it's a no go app as far as i am concerned, it bricked my HTC One V and now also messed up my Nexus S so stay away from it
Click to expand...
Click to collapse
I tried almost on every rom font installer which is included in ROM TOOLBOX PRO, but don't know why it's not letting you to install custom fonts
Related
I just flashed MIUI (latest version) and my DS is restarting repeatedly.I was at stock ROM before and i had factory reset it before I flash MIUI.
Anyone knows what happened?
EDIT: sorry for spamming...i got to CWM and i format again and it worked
ps. greate job with the ROM
are you using clockwork recovery?
barkermichaelj said:
are you using clockwork recovery?
Click to expand...
Click to collapse
would recommend that you install EXT4 recovery rather than CWM
simply download file onto SD
boot into CWM
and flash ZIP file
CWM works just fine, you just need to make sure you wipe everything before flashing new ROM, ie data, cache, dalvik cache, etc, then all is good
Just wanted to add that I to ended up in a bootloop, and I've had miui 1.8.5 installed since it came. It stopped after about 10 reboots. Dunno know what's up, had a lot of FC's as well these last few days.
Looking forward to tomorrow for am update! Cheers!
Sent from my HTC Desire S using XDA App
I also had some problems with 1.8.5 version (random reboots). I am still using the 1.7.29 version that is working great. Only theme chooser FC's.
I installed the full wipe rom and tried downloaded the steel theme zip and installed off off sd card in recovery and can't find it.
eman31872 said:
I installed the full wipe rom and tried downloaded the steel theme zip and installed off off sd card in recovery and can't find it.
Click to expand...
Click to collapse
Check your download folder maybe it downloaded to there.
Legend_3_Eyecandy_Theme
Flashed the eyecandy theme on top of Legend 3 ICS and now getting continuous boot screen. Please Help.
Tharavens said:
Flashed the eyecandy theme on top of Legend 3 ICS and now getting continuous boot screen. Please Help.
Click to expand...
Click to collapse
Try going to recovery, wiping cache, dalvic cache, then fixing permissions then rebooting...
If that doesn't help the reflash the Rom or go back to stock using Odin/heimdal
Sent from my HTC PH39100 using Tapatalk 2
Tharavens said:
Flashed the eyecandy theme on top of Legend 3 ICS and now getting continuous boot screen. Please Help.
Click to expand...
Click to collapse
I did not have any issue with this theme.
not sure why you boot looped.
If I was in your situation, I would boot into cwm as mg suggested.
Wipe all and factory reset.
Flash legend 3.
Boot into the ROM fully.
Wait 10 minutes.
Do your set up.
Boot back into recovery.
Flash the theme.
Flashing the theme right after your flash the ROM may cause some issues
Background details. I have TWRP 2.4.4.0 installed, rooted, S-OFF. I had Viper XL installed, but wanted to try a stock JB rom. I downloaded CleanROM, booted into recovery. From here:
-wiped cache
-wiped dalvik cache
-System reset
-wiped system
From here, I go to install CleanROM. It runs aroma installer, I choose my options, and follow on screen prompts. It seems to flash too quickly (like it's not installing). It says successful, and gives me the option to go home, wipe cache/dalvik, or reboot. If I click reboot, it says No OS installed, are you sure you want to reboot?
I tried rebooting, and it stops in the white bootup screen. Not sure what step I am missing here. I didn't think that I needed to flash boot.img since I have S-OFF, but is that the case? Any help would be great - THANKS!
opto_isolator said:
Background details. I have TWRP 2.4.4.0 installed, rooted, S-OFF. I had Viper XL installed, but wanted to try a stock JB rom. I downloaded CleanROM, booted into recovery. From here:
-wiped cache
-wiped dalvik cache
-System reset
-wiped system
From here, I go to install CleanROM. It runs aroma installer, I choose my options, and follow on screen prompts. It seems to flash too quickly (like it's not installing). It says successful, and gives me the option to go home, wipe cache/dalvik, or reboot. If I click reboot, it says No OS installed, are you sure you want to reboot?
I tried rebooting, and it stops in the white bootup screen. Not sure what step I am missing here. I didn't think that I needed to flash boot.img since I have S-OFF, but is that the case? Any help would be great - THANKS!
Click to expand...
Click to collapse
Flash twrp 2.3.3.1 and reflash rom. Also verify md5 of Rom download. And if you want a great jb Rom give magio Rom a run. It's my daily driver and is amazing
Sent from my HTC One XL using xda premium
THANKS! That seemed to work. Why do some roms work with newer versions of TWRP, and some do not? That's odd. I installed Viper XL with 2.4.
opto_isolator said:
THANKS! That seemed to work. Why do some roms work with newer versions of TWRP, and some do not? That's odd. I installed Viper XL with 2.4.
Click to expand...
Click to collapse
All versions of twrp past 2.3.3.1 have issues. Be it wiping or flashing on the evita.
And if it helped just hit the thanks button
Sent from my HTC One XL using xda premium
31ken31 said:
All versions of twrp past 2.3.3.1 have issues. Be it wiping or flashing on the evita.
And if it helped just hit the thanks button
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
This.... Reflash 2.3.3.1 or previous. Had ypur issue months back, drove me balls crazy for a few weeks.
Sent from my HTC One XL using xda premium
I succesfully added clockwork recovery, and installed the cyanogen mod 10.1 (4.2.2) to my phone, however when I click reboot, it gets stuck on the Samsung Logo
I then took the battery out and did a dalvic cache clear but the same issue occured... My install was succesfull, its just that it gets stuck on the Samsung Logo...
what have I done wrong?? Should I try install a different mod?? Or have I bricked my phone?? Or is there a foolproof way of installing a mod using Odin??
PS: (additional info)
I renamed the mod file before installing if that helps
I have no backup files
the only thing I can access on the phone atm is the Recovery Mode and Download Mode...
You would have backed up your previous rom..try fixing permissions....if not check cynogenmod is for your device or not.... If not download your device os reflash it by installing stock recovery.
Sent from my Micromax A110Q using xda app-developers app
I dont want to hijack this thread, but I have basically the same problem. I rooted my GT-I9300 phone and all was well, until I ran "NoBloat" to remove unwanted apps. Thereafter it runs up to the Samsung logo, then I get the following messages in succession: "Unfortunately messaging has stopped", "Unfortunately the process com.android has stopped", "smartcard service has failed" and "unfortunately the phone has stopped". I removed the battery, tried to flash the ROM again using the standard Samsung.tar file to restore to factory settings, but it made no difference. I am able to read the S3 files when linked to my Desktop and I can get it into download mode. I have run out of ideas and need help from the clever members.
If you get force closes fix permissions
Hit thanks if I helped
Sent from my Xperia Live with Walkman using xda app-developers app
Firstly, cwm doesn't work. Its garbage. I've semi bricked my phone well over 10 times trying to flash cm on it with cwm. Install goomanager and install TWRP to flash.
Secondly, once into TWRP recovery. Go to wipe>advance wipe> and select delvik cache, data, cahce, storage. Then go back to TWRP home and install the cm 10.1 and also the gapps package.
Sent from my SPH-L710 using xda app-developers app
Jeanrick said:
I dont want to hijack this thread, but I have basically the same problem. I rooted my GT-I9300 phone and all was well, until I ran "NoBloat" to remove unwanted apps. Thereafter it runs up to the Samsung logo, then I get the following messages in succession: "Unfortunately messaging has stopped", "Unfortunately the process com.android has stopped", "smartcard service has failed" and "unfortunately the phone has stopped". I removed the battery, tried to flash the ROM again using the standard Samsung.tar file to restore to factory settings, but it made no difference. I am able to read the S3 files when linked to my Desktop and I can get it into download mode. I have run out of ideas and need help from the clever members.
Click to expand...
Click to collapse
I think that bloatware app has taken away crucial files needed to keep the stability of an app up...
I don't know what I would do to fix that...
PS: please message me the samsung.tar file
dalton912 said:
Firstly, cwm doesn't work. Its garbage. I've semi bricked my phone well over 10 times trying to flash cm on it with cwm. Install goomanager and install TWRP to flash.
Secondly, once into TWRP recovery. Go to wipe>advance wipe> and select delvik cache, data, cahce, storage. Then go back to TWRP home and install the cm 10.1 and also the gapps package.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
if you dont like cyangenmod why did you brick your phone 10 times, why did you even go on after the second brick?
I love cm. I dislike cwm. I wanted the 4.3 jb on my phone.
Sent from my SPH-L710 using xda app-developers app
Hi guys
I keep getting stuck on the the htc boot screen with the red text underneath when trying to install the 4.3.1 carbon rom for my Htc one s3.
Steps I've taken not necessarily in this order:
]I've unlocked my bootloader.
Downloaded the rom and gapps cm 10.2 to my sd card
flashed twrp 2.7.1 recovery
flashed the boot file
entered recovery clicked the recommended option for wipe
installed the rom and then gapps
cleared cache
reboot (Although just before rebooting it says that my phone is not rooted, would I like to install supersu to root it, which I did)
Am i missing something?
You are maybe forget to intick the fast boot it always make problem
Just boot to recovery and do a full wipe data cash and dalvic and reboot your phone
Sent from my HTC J One using XDA Free mobile app
zivenchy said:
You are maybe forget to intick the fast boot it always make problem
Just boot to recovery and do a full wipe data cash and dalvic and reboot your phone
Sent from my HTC J One using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
I had to untick the fastboot as it wasn't loading the bootloader. I did a factory wipe, flashed boot image, factory wipe again, installed cm10.2 but during installation I'm getting a failed error. Anyone know why this is?
Could it possibly be because I have no superuser app on my phone? is superuser needed?
Because you are not rooted that's why
Sent from my HTC J One using XDA Free mobile app
zivenchy said:
Because you are not rooted that's why
Sent from my HTC J One using XDA Free mobile app
Click to expand...
Click to collapse
Haha thanks that's part of the problem, I'm a noob to all this. I am now rooted using superSU v1.9x but still getting same problems.
I'm also trying to use sideload but it's just stuck saying 'starting adb sideload feature stuck'
Sorry for spamming the forum, but I just don't seem to be getting anywhere after hours trying..
My plan now is to go back to the stock rom, I just want to make sure I'm flashing the correct one
I think my phone is actually an S4 rather than S3.
hboot: 2.13.0000
radio: 1.11.50.05.28
tmob005
would this RUU be the correct one to install:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4 .exe
You're on Tmobile, i gues...
Search one for you're phone company, for you're country.