IMEI Issue after flashing JRO0L3 ROM - Galaxy S I9000 General

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

Related

Huge Problem to change to custom rom.

Currently I am using Rom Eclair 2.1, build number 2.1.1.A.0.6, Kernel version 2.6.29,
Baseband ver M76XX-TSNCJOLYM-53404015 and my model no E15i
The problem is. I've installed superuser, xRecovery and rooted already my phone.
1st, I installed custom Rom GingerDX 2.37. Everything works fine except my SD card not detected. Again i restore to Eclair and download Stornmix 2.20 android 2.37. Also works fine but sd card again not detected. Idk where the heck is the problem? is it my sd card? but it seems works properly in eclair.
you will need to wipe /data , cache and dalvik-cache.... before that, if the rom is supplied with vold update zip or whatever, apply that fixes
so all i need just to wipe all that before install custom rom or after?
Before. But if a new version of the ROM you are using is released, just install it. No need to full wipe.
Hit the THANKS button if I helped!!
Sent from my W8 using Tapatalk
Emcee_Freeze said:
so all i need just to wipe all that before install custom rom or after?
Click to expand...
Click to collapse
I alwys do it before installing rom after rom just to be sure that everything is good

[Q] Restoring clockoworkmod backup

I'm sorry in advance if it has been asked already.
Do I need to perform any wipes before restoring a backup? I'm currently on CM7.2 RC1 and made a backup of it and want to switch to Defy+ CM9 build for a while then go back to CM7.2. Last time I did it (restored CM7 backup after installing CM9) it just stuck on Boot logo and couldn't move on so I had to start from scratch (new installation). Any guides just mention clicking on restore and that's all. Thanks in advance for an answer!
Can anyone help me? I did as I wrote (switched for a while to CM9 GB build from CM7.2 FROYO) then wanted to restore CM7 backup, tried both with and without wipes (data, cache, dalvik) but it just gets stuck on boot logo and won't move on. What am I doing wrong?
You don't need to do a wipe for restoring a nandroid..
I assume you're using the same recovery with which you made the backup..
neo.ank said:
You don't need to do a wipe for restoring a nandroid..
I assume you're using the same recovery with which you made the backup..
Click to expand...
Click to collapse
Thanks for an answer! I made a backup with CM7 (froyo) recovery and was restoring with the one that was installed along with CM9 (gb). So that was the cause?
You flashed the CM9 ROM through recovery.. right??
ROM's do not change recovery.. Its the same for both..
MarcinRN said:
I'm sorry in advance if it has been asked already.
Do I need to perform any wipes before restoring a backup? I'm currently on CM7.2 RC1 and made a backup of it and want to switch to Defy+ CM9 build for a while then go back to CM7.2. Last time I did it (restored CM7 backup after installing CM9) it just stuck on Boot logo and couldn't move on so I had to start from scratch (new installation). Any guides just mention clicking on restore and that's all. Thanks in advance for an answer!
Click to expand...
Click to collapse
Why don't you try Dual Boot...
refer to the below mentionedlink:
http://forum.xda-developers.com/showthread.php?t=1364659
However, to install CM9 I'm not sure if someone uploaded itsnandroid backup. Please note that to use the backup and restore youcan only use a Nandroid backup as ROM.zip file can not be restored.
What I understand from your post is that you have CM9 rom in zipformat; if this is the case then you can only install it usingInstall from SD card option from Custom Recovery.
---------- Post added at 11:09 PM ---------- Previous post was at 11:09 PM ----------
neo.ank said:
You flashed the CM9 ROM through recovery.. right??
ROM's do not change recovery.. Its the same for both..
Click to expand...
Click to collapse
Wiping data removes Custom recovery. If the new ROM has aCustom recovery then only it appears otherwise we have to reinstallthe Custom recovery.
neo.ank said:
You flashed the CM9 ROM through recovery.. right??
ROM's do not change recovery.. Its the same for both..
Click to expand...
Click to collapse
Yes, i flashed CM9 through recovery.
Rajneeshgadge17 said:
Why don't you try Dual Boot...
refer to the below mentionedlink:
http://forum.xda-developers.com/showthread.php?t=1364659
However, to install CM9 I'm not sure if someone uploaded itsnandroid backup. Please note that to use the backup and restore youcan only use a Nandroid backup as ROM.zip file can not be restored.
What I understand from your post is that you have CM9 rom in zipformat; if this is the case then you can only install it usingInstall from SD card option from Custom Recovery.
Wiping data removes Custom recovery. If the new ROM has aCustom recovery then only it appears otherwise we have to reinstallthe Custom recovery.
Click to expand...
Click to collapse
I think you got me wrong. I was using CM 7.2 Froyo build and made a backup of it through recovery. Then I installed CM9 GB build (wiped data, installed rom, kernel, gapps) and have been using it for a while then I wanted to switch back to my CM7.2 backup (went to the recovery, choosed restore) and it said restoring was succesfull but when I rebooted it just stuck on bootlogo and couldn't move on. Any idea what am I doing wrong?
MarcinRN said:
Yes, i flashed CM9 through recovery.
I think you got me wrong. I was using CM 7.2 Froyo build and made a backup of it through recovery. Then I installed CM9 GB build (wiped data, installed rom, kernel, gapps) and have been using it for a while then I wanted to switch back to my CM7.2 backup (went to the recovery, choosed restore) and it said restoring was succesfull but when I rebooted it just stuck on bootlogo and couldn't move on. Any idea what am I doing wrong?
Click to expand...
Click to collapse
Technically, you haven't done anything wrong. What I've learnt from my experience and posts, this is one heck of a weird phone.
Might be a chance your backup is corrupted or incomplete (highly unlikely bt I've seen it in a device)
Or some other glitch which m nt sure of..
Sent from my MB526 using Tapatalk 2
Wiping data removes Custom recovery. If the new ROM has aCustom recovery then only it appears otherwise we have to reinstallthe Custom recovery.
Click to expand...
Click to collapse
Well as I said..this phone definitely acts senseless sometimes.. a data wipe in my case didn't remove the recovery or bootmenu.
Even reported it in the app thread..
Sent from my MB526 using Tapatalk 2
neo.ank said:
Technically, you haven't done anything wrong. What I've learnt from my experience and posts, this is one heck of a weird phone.
Might be a chance your backup is corrupted or incomplete (highly unlikely bt I've seen it in a device)
Or some other glitch which m nt sure of..
Click to expand...
Click to collapse
It was second time it failed to restore a backup I was trying to do the same a while ago and was unsuccesfull too. Seems like my phone is cursed
Thanks for trying anyway!
MarcinRN said:
Yes, i flashed CM9 through recovery.
I think you got me wrong. I was using CM 7.2 Froyo build and made a backup of it through recovery. Then I installed CM9 GB build (wiped data, installed rom, kernel, gapps) and have been using it for a while then I wanted to switch back to my CM7.2 backup (went to the recovery, choosed restore) and it said restoring was succesfull but when I rebooted it just stuck on bootlogo and couldn't move on. Any idea what am I doing wrong?
Click to expand...
Click to collapse
Now, I understand your issue.
Try using below mentioned steps:
1. Boot into latest/custom recovery;
2. Wipe data/cache;
3. Restore the complete Nandroid backup;
4. Now from advance wipe dalvik cache and battery logs;
5. Now reboot the phone.
Please use above mentioned steps and share the results.
Hope this helps!!
Also try to install latest clockwordmod backup.
check this website for more detail http://www.clockworkmod.com/
@MarcinRN
I think your problem is kernel related, if you switch to CM7 from CM9 with GB-Kernel you must restore the froyo-kernel for CM7.
RATTAR said:
@MarcinRN
I think your problem is kernel related, if you switch to CM7 from CM9 with GB-Kernel you must restore the froyo-kernel for CM7.
Click to expand...
Click to collapse
That's the problem. You can find the kernels on epsy's site. Flash the kernel and restore the nand (there are also options in advanced restore if it still doesn't work, don't know if you need them)
Sent from my MB525 using XDA
Thanks guys I'll try it next time. However, I read somewhere that backup contains kernel too, don't know how much true is in that.

Need help installing CWM

Okay so i'm not new to flashing just made a stupd mistake, i have a Bell i9000M and installed CM9.1 and everything went fine and then installed the S3 addon pack that caused a bootloop so went into recovery and flashed back my nandroid here is where i made the mistake and restored back to GB and caused all sorts of problems but long story short I am now 100% stock running GB 2.3.3 and for the life of me cannot get CWM recovery on the phone.
Everytime i install a kernal it bootloops and looks like I can't even get into stock recovery now. I used odin and flashed PDA,CSC,PHONE and tried using 512 pit file.
The phone works just can't get recovery to work or even install a custom kernal like hardcore speedmod.
Tried follow the CM wiki and no luck, that just causes a bootloop on the startup screen.
Firmware:
GT_I9000M_UGKG3_UGKG3_BMCKG3_Sbl
jebise101 said:
Firmware:GT_I9000M_UGKG3_UGKG3_BMCKG3_Sbl
Click to expand...
Click to collapse
you need root, use UGKG3 rooting kernel from My Android Collections
Thanks, I was able to get back to CM9 and finially installed the correct NANDROID using this, which is for my device

Wifi problem on stock de odexed

Hey guys need a help
Just don't slap me with - noob search this that blah blah (i know I'm one still read patiently)
Well i flashed a stock de odexed rom today via (hells kernel) cwm
When wifi was toggled it scanned for a while and then rebooted...
I flashed wifi drivers, re flashed kernel etc. Yet rom rebooted. Back to Evo X and wifi is fine (so i assumed it's a problem in software not my mobile)
I actually tried flashing drivers, setting permissions and re flashed kernel..
I searched on XDA and majority of posts were ICS and JB roms.. Hence I posted this. Thanks in advance
If you're using hells fusion #50 kernel Flash dhd1.1 in cwm with system mounted
if you are using most other stock based kernels flash dhd-stock in cwm with system mounted
marcussmith2626 said:
If you're using hells fusion #50 kernel Flash dhd1.1 in cwm with system mounted
if you are using most other stock based kernels flash dhd-stock in cwm with system mounted
Click to expand...
Click to collapse
Thanks a lot sir i didn't know about the two different files. I had oly dhd
And thanks for uploading it too ^_^
marcussmith2626 said:
If you're using hells fusion #50 kernel Flash dhd1.1 in cwm with system mounted
if you are using most other stock based kernels flash dhd-stock in cwm with system mounted
Click to expand...
Click to collapse
Sir it didn't work... After i flashed drivers(with system mounted) and toggled wifi, it detected network but then rebooted (actually it was more like hot boot)... Just as it was before. I guess i didn't download a proper de odexed rom.
tony_stark_noob said:
Sir it didn't work... After i flashed drivers(with system mounted) and toggled wifi, it detected network but then rebooted (actually it was more like hot boot)... Just as it was before. I guess i didn't download a proper de odexed rom.
Click to expand...
Click to collapse
if you have rom problems
download any stock based custom rom from dev section and put on root of sd card
go into recovery
flash temp cwm zip if using a kernel that doesn't already have cwm
goto mounts and storage
format system data and cache
mount system data and cache
flash rom zip
restart
at the moment you cannot download stock roms to flash via odin as hotfile has been closed down although I have uploaded a stock rom firmware to dev host which you can find on or near the last page of dokys firmware thread on dev section - it will boot your phone but its European firmware so may not work on your network but at least it will boot your phone if flashing a custom rom with the method above doesn't work
marcussmith2626 said:
if you have rom problems
download any stock based custom rom from dev section and put on root of sd card
go into recovery
flash temp cwm zip if using a kernel that doesn't already have cwm
goto mounts and storage
format system data and cache
mount system data and cache
flash rom zip
restart
at the moment you cannot download stock roms to flash via odin as hotfile has been closed down although I have uploaded a stock rom firmware to dev host which you can find on or near the last page of dokys firmware thread on dev section - it will boot your phone but its European firmware so may not work on your network but at least it will boot your phone if flashing a custom rom with the method above doesn't work
Click to expand...
Click to collapse
No worries sir, i have Evolution X rom and 2 other in my sd card. Also i have 2 backups.. I just wanted to experiment and probably try to solve the issue on stock. I'm in evo x and everything is working fine.
Thanks a lot for assisting me immediately (pressed the button too )
The thing is i don't have a comp. So i was trying out different stock (cwm flashable) . I will just download one from doky's thread after the website issue has been sorted out
tony_stark_noob said:
No worries sir, i have Evolution X rom and 2 other in my sd card. Also i have 2 backups.. I just wanted to experiment and probably try to solve the issue on stock. I'm in evo x and everything is working fine.
Thanks a lot for assisting me immediately (pressed the button too )
The thing is i don't have a comp. So i was trying out different stock (cwm flashable) . I will just download one from doky's thread after the website issue has been sorted out
Click to expand...
Click to collapse
flashing a stock cwm zip doesnt actually give you stock rom as such - think of it more like a custom rom with no changes made to any files
To make it work properly you really in the case of flashing a deodex stock rom via cwm you need to be on the same baseband as the stock rom
To actually flash stock rom and to change basebands you needs to flash the stock rom firmware via odin
marcussmith2626 said:
flashing a stock cwm zip doesnt actually give you stock rom as such - think of it more like a custom rom with no changes made to any files
To make it work properly you really in the case of flashing a deodex stock rom via cwm you need to be on the same baseband as the stock rom
To actually flash stock rom and to change basebands you needs to flash the stock rom firmware via odin
Click to expand...
Click to collapse
Sir i have indian version. I didn't change basebands but ya i didn't know about the odin thing which u mentioned. Thank u

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.

Categories

Resources