Hi guys, I'm trying to flash this ROM on a Dual coming with a Django 1.6.5
I tried everything, but at the first boot the device stuck on CM logo.
I used the TWRP recovery. The device said p99030a so, I think that have the newbl. Used all the wipe avaiable, I tried to flash the ROM with and without the kernel, tried also to remove SD card...
The only way to boot the device is to flash django.
What can I do? I'm going mad.......
Thank you for every reply.
And sorry for my bad English, I'm an Italian user...
PROBLEM SOLVED!
Oh yeah, after about 15 hours of tries I solved my problem flashing a CWM 6.0.2.5 instead of TWRL with the help of AIO toolkit 5.5! Wiped, and flashed without problems!
I hope that this "fix" can help somebody to solve this problem.
Related
Hello.
I wanted to flash the new KL7 and I did the normal procedure with CWM. I had a KL3 stock (no custom kernel) and a KJ4 before.
After the procedure the Note started to boot continuously in loop. After that I tried to flash again with Odin in download mode but the phone is goin' on again in loop after reboot.
I tried then this procedure as in http://bit.ly/sKDXde but nothing again. Always in loop. I am not a developer and I am starting to worry a lot.
Is there anybody here able to help me?
Thanks to all.
Did you try to do a factory reset in the recovery (VolUp+Home+Power) ?
It solved my bootloop issue when I moved from KL3 to KL7!
well man. I tried and it did not work. Now after your msg I tried again and at the third attempt it worked again...I don't know what to say...never had these problems with windows mobile 6 (even if it sucks now compared to the new OS) and I flashed a LOT!
Thanks anyway.
Hello guys,
I have a very biug problem now.
I was with TeamICSSGS and I decided to move from it to Slim ICS.
But because I wanted to be fast I didin't read correctly and I didin't flashed the correct thing.
I flashed the I9000 Essentials and not the base which made the phone bootloop with the touch recovery.
Then I did a factory/data wipe and after the reboot there was no recovery and only bootloop.
Then I decided to flash a gingebread bootloader in the panic, don't know why I falshed it and it bringed me CWM Recovery of which I installed several ROM's with fail because they just stop installing when reac the kernel installation.
Then I downloaded http://forum.xda-developers.com/showthread.php?t=1685040 and flashed it, but with some recovery errors and bootloop again.
Can someone help me, please.
EDIT: I did that http://forum.xda-developers.com/forumdisplay.php?f=657 and it worked.
Hi, i'm new in the android scene and need your help. I flashed my phone with CM9 (Wisp) and i got "encryption unsuccessful" error, so decided to install other rom, the problem is that any rom i install get stuck in the boot logo (i've waited like 30 min to see if boots). Only cm9 boots, but still having the encryption issue. It would be nice to get your help people. Thanks
supermd said:
Hi, i'm new in the android scene and need your help. I flashed my phone with CM9 (Wisp) and i got "encryption unsuccessful" error, so decided to install other rom, the problem is that any rom i install get stuck in the boot logo (i've waited like 30 min to see if boots). Only cm9 boots, but still having the encryption issue. It would be nice to get your help people. Thanks
Click to expand...
Click to collapse
I need to ask these question :
a. Did you already upgraded your Mini into Gingerbread ?
b. Did you already have ClockWorldMod 5.0.2.8 / 6.0.1.5 (Recommended 5.0.x.x Touch )
c. Did you already rooted your device
F4uzan said:
I need to ask these question :
a. Did you already upgraded your Mini into Gingerbread ?
b. Did you already have ClockWorldMod 5.0.2.8 / 6.0.1.5 (Recommended 5.0.x.x Touch )
c. Did you already rooted your device
Click to expand...
Click to collapse
a. Used to have Stock Gingerbread, after the encryption issue i tried flashing with some gb roms based on cm7.2
b. I have CWM 5 Touch
c. Already rooted
Thanks
he said he tried encrypting that means he had atleast ics rooted with cwm recovery
@op
data partition may have got corrupted or something like that so I will suggest you to flash a 4 package firmware through odin
Hi everyone, I´ve read all of the posts relating to stuck at boot, but there´s no problem like the one I´m having.
First I installed a safe firmware so I can then install Live Note ROM, everything worked fine but after a day of use it restarted for no reason and got stuck at boot like if it was a bad flash. Then I thought maybe it was the ROM, so I installed another one, this time SuperBean v1.3.1 XXLT4 and again everything worked fine until after two days it froze and restarted and now I´m stuck at boot again, I know that I can flash again and it will work, but this should not happen. Just to clarify it doesn´t loop in boot it´s tuck at the Yellow triangle and won´t do anything after that, I can get into recovery and do all things before boot, but it doesn´t start the ROM installed in the memory ever again.
I´ve been flashing since HTC Magic and I have a Nexus 4 with a custom ROM without any problems like this, would anyone know whats going on, or someone have a similar problem?
did you do a thorough wipe before installing the new rom?
nokiamodeln91 said:
did you do a thorough wipe before installing the new rom?
Click to expand...
Click to collapse
Yes I followed all the instructions, the thing is that everything works fine for a day or two and then after a random restart it won´t boot again, this problem did not happen after a flash.
try flasing a stock JB rom.. make sure you format system, data cache & preload .. then boot inot download mode and flash stock jb rom. any region rom should do.
Hi all,
I have a problem with my phone, I just install a new custom rom from Kreator, but I get a loop in M loco, the phone is rebooting all the time, I can use the recovery and restore a backup from Omar's rom and works fine, even with RSD and the original Firmware, but when I try to install the Kreator rom still gor a loop.
The very first time I install Kreator rom I format system, data, davik, panic and pds, this is wrong? If is the case, why works fine with Omar and original firmware?
I'm a little bit confused here.
Thanks.!