Database Users

Issue with [ROM] CM 6.1.3 [V006] Kernel-010

Hi,
I've flashed my X10 with [ROM] CM 6.1.3 [V006] Kernel-010 [13-05-11]
and now it don't stop rebooting.
Someone know why it doing it??
My baseband is .58
Ps. I'm posting here because i'm new in forum and can't reply the post [ROM] CM 6.1.3 [V006] Kernel-010 [13-05-11] [Tweaked+Theme+Extras]
Thanks

This is probably because custom kernels ( i.e. if you have flashed the custom kernel ) work on baseband 52.
P.S Should be in the Q&A section.

Sorry!!
Next question will be there.
I'll try change BB now.
Be right back.
Edit: I tried this and nothing... continuous reboot...
another idea?

sbr.anderson said:
Sorry!!
Next question will be there.
I'll try change BB now.
Be right back.
Edit: I tried this and nothing... continuous reboot...
another idea?
Click to expand...
Click to collapse
Reflash the rom.

OmegaRED^ said:
Reflash the rom.
Click to expand...
Click to collapse
^What he said.
1) First wipe everything, factory reset, cache partition, format cache, dalvik cache.
2) Flash the ROM : http://www.mediafire.com/?7xwcdvyx8fw6cr0
3) If you are on baseband 52, flash the baseband patch http://www.multiupload.com/U020F08R3N
4) Then flash the hotfix http://www.mediafire.com/?2c27ssr123e7rrv

kozxmartt said:
^What he said.
1) First wipe everything, factory reset, cache partition, format cache, dalvik cache.
2) Flash the ROM : http://www.mediafire.com/?7xwcdvyx8fw6cr0
3) If you are on baseband 52, flash the baseband patch http://www.multiupload.com/U020F08R3N
4) Then flash the hotfix http://www.mediafire.com/?2c27ssr123e7rrv
Click to expand...
Click to collapse
Doing it now.
Edit: The problem continues...rebooting...
And I see the baseband appears "unknown baseband"

Install rom
Then bb52
Bbpatch
Reboot phone get signal
Install kernel
Reboot phone and let it reboot a few times it will get stable after about 5 times
Sent from my X10i using Tapatalk

WB's rom is using baseband 54 and above, meanwhile K010 needs baseband 52. Here are the steps :-
1. Fresh install the stock rom with SEUS.
2. Root & install xrecovery using flashtool.
4. Flash the X10_52_ChangeBaseband.ftf using flashtool.
5. Reboot into recovery and wipe everything.
6. Install CM_6.1.3_[v006].zip.
7. Install CMFix_v6_v61.zip.
8. Install bb patch cm5bb49.zip.
9. Install 2.6.29.6 FX k010 froyo FXR busybox in xbin v06.zip (get it on the first page of WB's thread).
10. Reboot.

I may be wrong, but shouldn't you just install bb patch?
If you have a memory card reader, use it to save the baseband patch via pc and then just apply it via xrecovery.
I'm sure this would work, try before reflashing rom.
Remember to backup just in case anything horrible happens.
Edit: when it says "unknown baseband" use dev tools-bad behaviour-crash system server. nd wait got reboot.
Sent from my X10i using XDA App

guys i have this ron in bb 54 (stock)... is it better on bb 52 and k010??? what does k010 will give me more than what i have now (stock kernel)??

Well..
I've tried a lot of times to do this rom run but no success...
Now i'm using another rom in .52 BB.
Thanks for help.

[HELP] Moving from Lite'ning To Miui Galnet

Ok, so I inatalled lite'ning v6.1 and it root my phone 2.
Now I want to move to MIUI Galnet 1.9.9 for SGS2.
can i ignore the part when i need to root my device and install the rom over the lite'ning rom?
and if not, how should i do that?
tnks ;]

Perperz said:
Ok, so I inatalled lite'ning v6.1 and it root my phone 2.
Now I want to move to MIUI Galnet 1.9.9 for SGS2.
can i ignore the part when i need to root my device and install the rom over the lite'ning rom?
and if not, how should i do that?
tnks ;]
Click to expand...
Click to collapse
Probably but you need to read the instructions for the rom you install .
jje

if you have root then you most probably have cwm recovery. go there and just flash the galnet over litening

Yep just make sure you factory reset, wipe data/cache etc (note, make sure to back up apps, SMS etc, as they will be wiped)

you will need to format /system, and preferably /sdcard also. This is not optional.

fyre31 said:
if you have root then you most probably have cwm recovery. go there and just flash the galnet over litening
Click to expand...
Click to collapse
OK, I searched a little bit in the web and i found up that the lite'ning comes with a cwm, root, and build recovery mode. so all i got to do is to wipe and instal.
thanks for your help guys ; ]

Perperz said:
i don't know if i have cwm.
does it matters if i'll install it again?
so what you are saying is to skip the part of the root and install the rom over lite'ning yes?
Click to expand...
Click to collapse
yep. just turn off your phone and press volume up+home+power buttons to boot into cwm recovery. from there you can wipe /data, format /system then flash galnet miui update .zip
you don't have to install cwm afaik litening has it already

MIUI ROM installed sucssesfuly

m2smoe said:
you will need to format /system, and preferably /sdcard also. This is not optional.
Click to expand...
Click to collapse
Where did you get the kernal?

From Official 2.3 to old MIUI?

Hello. I downgraded from MIUI to the 2.2.2 (dload folder on sd card method)
then i upgraded to official 2.3 using dload on sdcard method.
How to i revert this?
I have tried using the 2.2.2 dload method, then boot into pink screen to install newest recovery, the recovery works and i can restore my old MIUI, BUT it wont boot. just stuck on the new Huawei logo.
and yes i have tried let it boot right after the 2.2.2 dload method is complete but it then enters recovery and some error massaged are displayed, and it wont boot the rom, just recovery..
Any Suggestions?

lobfredd said:
Hello. I downgraded from MIUI to the 2.2.2 (dload folder on sd card method)
then i upgraded to official 2.3 using dload on sdcard method.
How to i revert this?
I have tried using the 2.2.2 dload method, then boot into pink screen to install newest recovery, the recovery works and i can restore my old MIUI, BUT it wont boot. just stuck on the new Huawei logo.
and yes i have tried let it boot right after the 2.2.2 dload method is complete but it then enters recovery and some error massaged are displayed, and it wont boot the rom, just recovery..
Any Suggestions?
Click to expand...
Click to collapse
Why did you upgrade back to 2.3 if you were planning to install .32 Miui? You have to have .32 ROM installed when you install Miui .32, .35 when you install .35 Miui. If I misunderstood and you have .32, try Fixing permissions in CWM.

Moved To Q&A​
Please post all questions in the Q&A section​

sbasil said:
Why did you upgrade back to 2.3 if you were planning to install .32 Miui? You have to have .32 ROM installed when you install Miui .32, .35 when you install .35 Miui. If I misunderstood and you have .32, try Fixing permissions in CWM.
Click to expand...
Click to collapse
Currently i have the Official 2.3 because i cant get any other rom to work..
But i want to get back MIUI, my question is How?
I upgraded because i wanted to try the Aurora 4.0 rom, but i gave up as i couldnt get root on the official 2.3 with superoneclick or any other app.
Thanks
btw. How does the U8800 work? I cant flash MIUI on top of the official 2.3 because of the kernel not compatible right?
and in pink screen, is the Boot.img the kernel? if so can i just replace that one with an older kernel and MIUI will work?

Go to settings/backup reset
There's an option install update from sdcard
That should do it
Sent from my U8800 using XDA Premium App

I see you're familiar with the "usual" way of downgrading...try doing it again, or a couple more times. When I upgraded to .35 to try Aurora ICS I had to flash the rom (ICS) like 3 times before it booted properly (was getting a bootloop before). Also if you don't apply the update (downgrade) more than once you can get a few "traces" of .35 system apps in your .32 rom (I downgraded applying the update only once and now have apps like 2.3.5's file manager, notes app, appinstaller, in my .32 rom.I didn't notice any problems apart from that though.). Hope it helps.

going back
Hi there - I had similar troubles after I updated to stock 2.3.5 (latest edition) bootloader is now locked and previous exploits no good
Here is what I did:
Reflashed with 2.3.5 beta using vol+vol- I found it on XDA, can't remember where at the mo
then used superoneclick -worked fine
However my phone got stuck in boot loop after I tried to install CWM however I found that adb still worked and I used that to mount .cust_backup as rw and copied CWM recovery.img on there then took battery out and rebooted in to CWM and did factory reset and personally i installed aurora ICS 2.0 (2.02 gave me simcard issues) it all worked fine - took some fiddling for me but I hope this would make it easier for you

IMEI Issue after flashing JRO0L3 ROM

Sorry for posting it here but i do not have enaough post to post in the JRO0L3 ROM
I've got the same IMEI issue, I've noticed that after installing CM10 NIgthly so I've downgraded to darky rom 10.2 via ODIN, after that I've flashed JRO0L ROM 4.1.1 RC10 and I was able to See the right IMEI (same as on the sticker behind the battery).
Then i've installed RC11 and IMEI erro Keeps popping up.
After installing the Darky I've done NAND backup.
What is the procedure to restore the IMEI and have the RC11 installed ?
Shall do the full wipe and to NAND restore and then install the RC 11 ?
any help appreciated

I've been experiencing troubles with my IMEI after flashing CM10. I flashed a three-part-firmware with repartition ticked via ODIN and after that CM9 via CWM and afterwards CM10 and everything was super. Just try flashing your JB rom after you flashed CM9. Hope it works for you.

frenetico said:
I've been experiencing troubles with my IMEI after flashing CM10. I flashed a three-part-firmware with repartition ticked via ODIN and after that CM9 via CWM and afterwards CM10 and everything was super. Just try flashing your JB rom after you flashed CM9. Hope it works for you.
Click to expand...
Click to collapse
Can the EF be copied over using root explorer ? or Something like that, don't really want to flash rom again

ptothej said:
Can the EF be copied over using root explorer ? or Something like that, don't really want to flash rom again
Click to expand...
Click to collapse
I've found the solution
http://forum.xda-developers.com/showpost.php?p=30644270&postcount=116

Phone doesnt like cutom roms :)

Hi my phone seems to hate custom roms like cyamogenmod and gapps because everytime i flash them a bootloop inevitably comes to haunt me. Other roms like Albe95 Ports work. http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-albe95-lollirom-official-1-0-t3049564
My current rom is Phoenix Rom. http://forum.xda-developers.com/showthread.php?t=2349584
The roms listed above work flawlessly.
A rom that I wanted to try was cyamogenmod 12.1 optimized by JDC team but it wouldnt boot. I followed exact instructions for each rom. Every time i used TWRP.
Could my problem be that gapps screw with the custom rom ?
Google apps are integrated in phoenix rom and albe95.
Maybe thats why they work ?
Please help.
Thank you for youre time.

JaguarBeast said:
Hi my phone seems to hate custom roms like cyamogenmod and gapps because everytime i flash them a bootloop inevitably comes to haunt me. Other roms like Albe95 Ports work. http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-albe95-lollirom-official-1-0-t3049564
My current rom is Phoenix Rom. http://forum.xda-developers.com/showthread.php?t=2349584
The roms listed above work flawlessly.
A rom that I wanted to try was cyamogenmod 12.1 optimized by JDC team but it wouldnt boot. I followed exact instructions for each rom. Every time i used TWRP.
Could my problem be that gapps screw with the custom rom ?
Google apps are integrated in phoenix rom and albe95.
Maybe thats why they work ?
Please help.
Thank you for youre time.
Click to expand...
Click to collapse
You can easily test that theory by not flashing Gapps. Just only flash the rom and try to boot it.
Also are you running a Lollipop bootloader and modem?

Ive tried flashing only custom rom but the bootloop comes back. Right now i am running a lollipop modem and bootloader.

JaguarBeast said:
Ive tried flashing only custom rom but the bootloop comes back. Right now i am running a lollipop modem and bootloader.
Click to expand...
Click to collapse
Ok do this:
Backup everything that you want to save stored on your internal storage.
1. Make sure you are running the latest TWRP. This is important because using an outdated version will not let you boot the rom.
2. Start TWRP and do a advanced wipe. Format /data (this will wipe your internal storage), format /system, format /cache and /dalvik.
3. Flash the rom.

Unfortunately that does not help. I have advanced wiped ever time before flashing rom. Maybe permisions are the problem ?

JaguarBeast said:
Unfortunately that does not help. I have advanced wiped ever time before flashing rom. Maybe permisions are the problem ?
Click to expand...
Click to collapse
What version of TWRP are you using? And did you try booting it without simcard and sd card?

Im using 2.8.7.2 twrp. I havnt tried to boot without sd or sim. Would that be the problem ?

JaguarBeast said:
Im using 2.8.7.2 twrp. I havnt tried to boot without sd or sim. Would that be the problem ?
Click to expand...
Click to collapse
No idea. I'm just guessing because that rom should just boot.
Are you sure the file you downloaded is not damaged? Check the MD5 signature. For example, the latest version of the JDC CM rom has MD5:
3a1af890b87c11256c943759459ec3e4
So transfer the file to your phone. Then download a MD5 checker from the market and compare it.

Md5 matches. Looks like the insides of my phone are screwed up

Reparation your device
As those are caused by a screwed partition
As a reparation fixes this
You are going to need :-
0.a PC
1.a PIT file for your Galaxy s4 (depending on your variant)
2.Odin
3.Samsung USB drivers installed in the PC
Sent from my GT-I9505 using Tapatalk

Start with flashing the stock rom using odin. Then go for root,then recovery and then try flashing. I had the same problem but it never bothered me after flaahing the stock.