Hi,
I have a Nexus S I9020T, rooted and running MIUI.
Today I rebooted my phone (after applying a new font via Font Changer), and it got stuck at the Google logo.
I have tried rebooting via fastboot, to no avail. I have also tried pulling the battery several times. I have even tried doing a full wipe and restoring a Nandroid backup that I made via ClockworkMod after it got stuck, but it still refuses to go past the Google logo.
Can anyone please suggest something? Thanks so much.
Edit: I forgot to mention that the device was plugged into the computer at the time, and I am not sure whether or not the SD was mounted. Could this be the cause?
If SD isn't mounting you wont get past the Google logo. See if it is mounted in recovery
Sent from my Nexus S 4G using xda premium
I bet if you reflash the original miui rom you were on you'll be good to go. Sounds like the font package messed up the miui system. Good luck.
And no need to wipe most likely. I've bootlooped my miui applying themes and such and just reflashed with no wipe and good to go.
Sent from my Nexus S 4G using Tapatalk
Related
I made the mistake of flashing a ROM that was still in beta testing. i downloaded it from the ROM manager app. i made recovery and wiped data then flashed the ROM.
Everything went fine til it rebooted and got stuck in a bootloop. I've tried wiping data again to fix the loop but it did nothing. I've tried renaming working ROM to update.zip and tried running it from recovery and it didn't work.
I'm stuck and have no idea what to do. any kind of idea or solutions would be greatly appreciated.
Especially since I'm stuck using a piece of crap blackberry storm
Sounds like you're going to have to SBF. Not really too hard and its good to know how to do. Search the DX forums for the files and how-to.
Sent from my ADR6300 using XDA App
Before you SBF
I was having the same problem and I did a factory reset and cleared the dalvic cache I am not certain I needed to do both but it worked. You have to boot into recovery in order to do so. See: droid-life.com/2010/07/21/how-to-boot-into-recovery-on-the-droid-x (I can't post links) Let me know if you need further help. I would try the davic cache first and then factory reset if that doesn't work.
I had been using Kang's CM7 for a while when I recieved a call and all of a sudden my phone looped. A friend suggested to reapply updates on CM7 through open recovery, which usually works on his XT720,... and so I did it. Unluckily, my phone ran out of battery in the middle of the reapplying process. When I turned it on again, it loops over and over again.
I somehow managed to get into the bootloader and flashed it with a CE stock rom. It went until the "please manually power up your phone" phase and my phone started looping back. I decided to try to flash it with some other roms but still succeeded only until the the "please manually power up your phone".
Tried to wipe data/factory reset from the system recovery (2e) but still it loops at the M logo. It cant find any update.zip too in the sd card (if it matters).
I did search the forum and tried a bunch of things, but to no avail. Any help?
PS: Sorry for the weird English
How certain are you that your battery was fully charged when you flashed sbf? I would start there. If you can't boot after sbf, I'm suspicious of battery. Some people might recommend removing sdcard.
Sent from my Milestone XT720 using xda premium
Well, the indicator showed 100% fully charged when I flashed it. I once put another better battery too but still it looped like hell. Tried removing SD card too but still didn't work a thing. Any other method?
Earlier today, my NS4G (running CM10 nightlies) rebooted itself (as it has been doing a good bit recently). I didn't think anything of it until it would not make it past the Google logo. I rebooted into CWM, and CWM could not read the sdcard. I tried this a few times, just to be sure. I even re-flashed CWM - still no sdcard access.
After this, I grabbed the factory images from Google (https://developers.google.com/android/nexus/images#sojus) and flashed them. Again, no dice. I can get into fastboot and recovery, but not even the factory ROM will boot (still stuck at the Google logo).
Is there anything I have missed? Is there any way to confirm whether or not my internal storage is dead via fastboot?
Any help is much appreciated - thanks!
Hi all
I’m a complete noob at this and it seems like I have got myself into a bit of a pickle. Sorry for the massive description but I thought it would make it easier to get a good answer.
My Phone:
Samsung Galaxy S4 GT 19505 LTE
PDA I9505XXUEMK8
CSC I9505BTUEMK5
MODEM I9505XXUEMK8
I successfully rooted my phone using Odin. In Odin I added the "CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5" file to the PDA field then rebooted the device. Then I added the "openrecovery-twrp-2.6.3.1-jfltexx" file to the PDA field, rebooted the device and the phone automatically opened in TWRP recovery. In recovery mode I wiped the cache, system and dalvik cache. I then went to install, browsed to the "I9505 Official_Google_Edition_4.3_by_Jamal2367_Finaly_v2.0" file on my SD card, rebooted the device and the Google logo came up on the screen for a few minutes and all was good. Got my new ROM, ran a root checker and all was good.
After some research I decided I wanted to use the Pacman ROM as it seemed to a lot more customisable. Using the same method I went to TWRP recovery wiped the cache, system, and dalvik cache. I then went to Install, browsed for the pacman ROM and the Gapps file on my SD card and everything installed ok, the phone restarted and the pacman logo came up everything was fine. Although I did notice on start up that I got this message.(and have had this error message ever since)
kernel is not seandriod enforcing
set warranty bit : kernel
After using the Pacman ROM for a day I noticed a lot of bugs like my apps would disappear, I couldn't use my banking apps and my phone was generally performing very badly. So I decided to remove the ROM and use CyanogenMod ROM under the recommendation of a friend. So again I pressed home+power+vol up to enter recovery mode but this time it didn’t enter the TWRP recovery it entered the stock recovery mode. This was slightly concerning but I proceeded to use the list menu and cleared the cache etc, browsed the SD card and went to the CyanogenMod 10.2 ROM I previously downloaded. It began to install but in red I got the error message stating that I didn’t have the right permission or signature. The phone rebooted back to the Pacman ROM. I tried the above three times and it still continued to boot back into Pacman ROM sometimes I struggled to even get back into recovery mode.
Soooooo I decided to try and go back to the Google Edition 4.3 ROM and play it safe, using the method from my first paragraph. But when it installed through TWRP I got an error message saying cant find MD5 file. The device rebooted and the Google edition logo came up on the screen but it seems to be locked in a loop. The Google logo wont go away and the phone vibrates once then three times quickly every 10 seconds.
I can still enter both TWRP recover and Download Mode. But I don’t want to mess around with it anymore without getting some advice. Any help would be much appreciated as I really need my phone working.
Thanks again
Aiden
Did you create a backup while on your first run with google edition? If so wipe cache, system, and dalvik and restore to your backup. Should put you back to where you began.
Sent from my LGMS769 using XDA Premium 4 mobile app
I know I should, but I didnt. Is it still fixable ?
*Update*
Couldnt help myself had to have a tinker around. Managed to get Cyanogenmod 10 working with Gapps. Gonna see how I get on with this. Although still would like to know I have been having all these problems.
Sometimes things just dont go as planned: p I have easily soft bricked my phone around 10 times and always able to fix it. You really should have made a stock backup before flashing anything. I recommend doing it now so you at least have a known working configuation backed up for future use. Trust me backups are your friends!
Sent from my LGMS769 using XDA Premium 4 mobile app
Thanks for your replies.
Ye gonna that right now Cyan Mod so far is running very smooth without any problems.
Regards
Aiden
Hi,
My HTC one mini has an unlocked bootloader, TWRP installed and S-off (i don't know if this will help)
I was trying to flash cyanogenmod 11 on my device via TWRP however it said that it had failed. Then when i rebooted my phone it showed the HTC logo but after a couple of seconds, the screen went black. Then the HTC logo popped up again, however, my phone had just booted back into my recovery.
I have tried to solve this by factory reseting however this did nothing, i have flashed a backup i had saved to my computer (that was saved by ROM manager) however there was no change, and i have switched off several times however i always end up in the TWRP recovery. I can boot into the bootloader but from there, i still can't get to the normal system.
This is a big problem as i can't find anything else on the internet that describes this problem and i think that my phone could be bricked. I can't access my apps or anything else. I don't think it is a bootloop as I can't even see the security screen and i don't have the option of entering my password which has happened in the past as it always goes straight to the recovery.
If anyone had any advice on what to do i would really appreciate it as I really need help!
Thanks
Seems you have no os loaded. I'm not sure why your backup does not work. I had an issue flashing cm11 originally, kept failing. Did you wipe data, cache and all and retry your backup again?
Sent from my One Mini using XDA Premium 4 mobile app
hi
dizzyman1180 said:
Seems you have no os loaded. I'm not sure why your backup does not work. I had an issue flashing cm11 originally, kept failing. Did you wipe data, cache and all and retry your backup again?
Sent from my One Mini using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i have the same issue..