Hello, I tried yesterday to install miui v5, before I had cwm rec, and cyanogenmod 10.2 i think. But when I was doing first instalation/flash I forgot to do the "swap" so i thought this time it will be great, and also got another "great" idea to clean phone memory. I tried everything, flashing, installing, jb, gb, rooted gb, now i flashed the "...XXLL2_rooted" or "...XXMG_JB_SER" I am not 100%. And telephone "hangs" on the samsung logo for half and hour and nothing happens. Please can someone would like to explain me how I can fix the phone?
tldr: I have broken my phone, tried to install clean stock rom but phone just hangs on the samsung logo.
I would like to have miui v5 and swapped memory, gapps, and themes.
Thanks in addition for the help!
EDIT: WORKS!
thread to close.
Related
Hello,
I've got a branded HTC Desire. I rooted it with Unrevoked, created a Goldcard before but since I've only got one SD Card, I now use it as a normal SD Card, it certainly dismissed it's "gold" propertie I guess...
I wanted to install a MIUI rom, so I first went for the MIUI_Au ROM one of my friends has. As a consequence, I've been following their instructions. But, being unable to download their rom, since their download links are dead, I went for the UK version of the rom, as well as the MIUI-XJ ROM. I wiped everything, reseted the phone to the factory thing, then installed the radio version 32.44.00.32U_5.09.05.30_2. The Recovery didn't recognize it so I had to desactivate the signature check. After that, I rebooted, and tried to install the UK MIUI. After installing it, I rebooted the phone, but then it got stuck on the MIUI screen (where you have, at the top, "MIUI" and "Android ROM" written under, in chinese, and waves at the bottom at the screen). At first, it stayed on it, so I waited, since I read it was slow to boot the first time. But after around 3-4 min, it started to blink black every 10 seconds, as if it looped on this screen. After 10 mins I recovered my backup and erased the ROM.
I tried the same thing with this ROM, the MIUI XJ, but I got the same result at the same time. I also had to untoggle the signature check as well.
I don't understand where the problem comes from, but since I got the same on two roms, I'm starting to think I forgot to do something and it blocks the booting of the ROM... Any idea ?
Thanks.
Try a newer radio. No issues here. (check signature)
Yep, I also recommend to flash newest radio.
Miui roms
Install this radio 5.17.05.23 for miui roms. I'm using miui roms ( i've tried all version) and i have no problem...
I've been trying to figure out for the last hour or so why this rom hasn't been flashing correctly.
1. I've already loaded DZ HBoot onto the phone with S-OFF and had loaded the SenseGinger 3.0 Rom. Loved the layout but it was kinda slow for me. So that's when i was looking up other roms and found RunnyDrOiD v5.0 By PVTEAM.
2. next thing I did was download the Rom Manager, Flashed ClockworkMod Recovery sucessfully and selected install rom from sd card, (in which I had loaded the RunnyDroid rom on my sd card already.
3. Im in Recovery, wiped data, and the installation started. The problem I'm facing is that the installation says it was sucessful and says Rebooting, but the progress bar in the background is still going (looks like it was at 25%). Phone Reboots. Now it'll first start up with the HTC Logo, shuts off, then reboots again with the HTC Logo then goes back to clockworkmod recovery. I attempted to do it again, but still have the same results.
Anyone have any idea that I'm facing this problem? I really hope I can get this on my phone as the RunnyDroid rom looks really clean looking, and with other users reporting it to be fast, It's driving me nuts that I can test this rom out! *sad panda*
Anyone's help or support is greatly appreciated.
actually lock this thread. found out what the problem was. I flashed the wrong hboot. Be sure to use the DZ HBOOT FOR ANYONE HAVING THIS PROBLEM. Thank you all anyway.
Hi there!
I installed
http://forum.xda-developers.com/showthread.php?t=1912187
with basbeand 77 instead of the recommended ones, and it appeared to work just fine for two days.
Today, I installed the LBE Guard, and so my Desire was stuck in bootloop, which I could get out of after a fullwipe and a new install.
So, then, I installed the LBE privace Master (v4.3.2738),
http://forum.xda-developers.com/showthread.php?t=1422479
because I read it was okay for JB. While configuring it, my phone crashed, and I was again stuck in a bootloop. I tried to make a fullwipe again, and a new install, but I have still these random (but appearing soon after booting) crashings and then a bootloop. It even appears when I use the Aroma Installer, but not in the CWM.
So my question is - what went wrong and more importantly, how do I get my phone to work again?
Thanks for replying.
The part with the baseband is wrong - that was my other phone.
I am quite the noob-cookie, I also have the problem with random reboots and freezes. I have been messing around with the new Nikez 4.2 Jellybean Rom, i thought that could be the reason why. But now I am also experiencing it with the old Nikez 4.1 Rom that used to be very stable for me. Anyone know a good solution? I have done several full wipes..
Cheers!
Hi, I flashed CM 10.2 on my Galaxy S4, and I used titanium backup to restore all my apps, only apps I didn't choose was TouchWiz and the TouchWiz simpler one. And it said I needed to reboot my device for the changes to apply, so I did that. When I rebooted it said everything stopped working. Even the core thing. Screen went black. Then I took out the battery and when I tried to go to my custom recovery, it just skipped the recovery screen and booted into cm again and same thing happened. Everything just stopped working. Help please. Also I am able to get into download mode. I just don't know how to recover from this. I am running 4.3.1 cm nightly, well I was. I don't know if I could count it was 4.3
if you are able to access the download mode then flash a stock rom. then root your device again.
Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!