First I apologize for using the google but I do not speak English very well.
I just installed the ROM CM 10 Temasek's UNOFFICIAL and everything was ok but my phone is not receiving the signal operator I installed the basebands V30A and V30B by SmartFlash but after installing the phone is in the loop on the logo cyanogenmod what do I do?
Help =(
anyone? :crying::crying::crying::crying:
Try a wipe all(data/cache/system) via cwm and reflash the rom.
Sent from my LG-P990 using xda app-developers app
What rom were you on before cm10.1?
When you flashed cm10.1 you had no signal right after the flash?
Did you tried to enter recovery and do factory reset?
If you can boot into cm10.1 after the factory reset in recovery, then check your imei by typing *#06# in the dialer
If it shows this: 350305260000001, then you have to restore your imei.
If you have to restore your imei or you were unable to boot into cm10.1, then flash stock rom with smartflash.
Download v10d or v20s or v30a from here.
Extract the downloaded rar file.
Download USB drivers for smartflash from here.
Download smartflash.
Extract smartflash.
Start smartflash.
Select ROM copy D/L tab in smartflash.
Select the .fls file from the extracted rar file as CP bin.
Select the .bin file from the extra rar file as Ap bin.
Turn off your phone.
Connect the USB cable while you press and hold the volume_down key.
Release the volume_down key when you see S/W upgrade screen.
Click on Start in smartflash.
Look at the picture for more help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you choosed v10d or v20s you are on old bootloader and partition layout, so you have to download cm for old bl.
If you choosed v30a you are on new bootloader and partition layout, so you have to download cm for new bl.
If you have to restore your imei:
Check the sticker on you phone under the battery for your imei or on your phone's box. Imei is a 15 digit long number.
Download putty.
Connect phone to the computer.
If you flashed v10d or v20s type 1809#*990# in the dialer. If you flashed v30a type 3845#*990# in the dialer.
Tap on Port Setting
Tap on CP USB
Tap on OK
Start putty.
Click on Serial at the Connection type section in putty.
Write 115200 in the Speed section in putty
Open device manager on your computer. (You can find help for it here.)
In the device manager open up the Ports (COM and LPT) section
Look at the end of LGE Mobile USB Serial Port device. At the end of it you see COMXX in (). XX is meaning number. Maybe you see (COM4) or (COM12) at the end of LGE Mobile USB Serial Port device
Type the it to the Serial line section in putty without the (). So if you see (COM10) just type COM10 to the Serial line section in putty.
Click on Open in putty.
Look at the picture for more help.
Type AT. If the respons is OK then everything is okay.
Type AT%IMEI=X,X,X,X,X,X,X,X,X,X,X,X,X,X,X. The X is your imei number. If your imei is 123456789123456, then type AT%IMEI=1,2,3,4,5,6,7,8,9,1,2,3,4,5,6 and press enter.
If the response is IMEI WRITE OK, then restart your phone and you get back your imei.
If the response is IMEI WRITE ERROR, then enter the command again and again until it says IMEI WRITE OK, then restart your phone and you get back your imei.
Look at the picture for more help.
I had to X out my imei because if it ends up in bad hands I have to buy a new phone
If you still don't have signal, then it is time to buy a new phone or keep it on stock rom and send it to service.
THANKS!!!!
Thank you bitdomo you saved me =)))))))))
My problem was the IMEI which for some reason was different from the original, did the procedure you went through and the signal returned thanks!:laugh::laugh::laugh::laugh:
DouglasNickson said:
Thank you bitdomo you saved me =)))))))))
My problem was the IMEI which for some reason was different from the original, did the procedure you went through and the signal returned thanks!:laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
Your wellcome my friend.
Sent from my LG-P990 using xda app-developers app
Related
So I just installed Gingerbread on my new Galaxy Tab (AT&T). As per the instructions, in Odin I used the JK3 modem file. However my T-mobile prepaid sim card isn't working. I'm assuming I need to re-connect (in download mode or upload mode?), start Odin, and choose the JPZ modem file. Is this correct?
Will this wipe the Overcome ROM, or will that still remain?
Thanks.
lollavid said:
So I just installed Gingerbread on my new Galaxy Tab (AT&T). As per the instructions, in Odin I used the JK3 modem file. However my T-mobile prepaid sim card isn't working. I'm assuming I need to re-connect (in download mode or upload mode?), start Odin, and choose the JPZ modem file. Is this correct?
Will this wipe the Overcome ROM, or will that still remain?
Thanks.
Click to expand...
Click to collapse
If you download only the modem file, with odin without repartition, then it will work, choose the one you need correctly. It will not destroy overcome,
So I use the same PIT and PDA from the first time (from GB Stock Safe), but substitute the Phone file for the JPZ modem? and I also unclick repartition? Is that correct?
No, you only load up the modem.bin file to flash. Nothing else.
When it is done loading and the SGT resets, then go check your APN settings for your carrier. i.e. google APN settings for carrier
Okay, I tried that. I found info on the APN settings here:
http://androidcommunity.com/forums/f4/t-mobile-us-apn-settings-please-help-41160/
However, when I put my T-mobile SIM card in and start the phone, I get the message:
"enter network lock control key"
Okay, so I followed the tutorial here:
http://forum.xda-developers.com/showthread.php?t=843323
I am now stuck with adb and getting my system to reboot. Here is a screenshot of the occurrence in under the cmd prompt:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It looks like the script didn't run properly for you and I wouldn't let it delete the /efs/nv_data.bin file if I was you.
I hope you made a manual backup of the /efs folder before you started this.
Looking at is more closely I see you werent running in root mode because you still have the $ prompt instead of the # prompt
BTW, i did unlock on the phone using the Hexeditor app fromt he market and also using Root Explorer to make backup copy of the /efs folder.
If you still need help you would be better off posting in the original unlock thread:
http://forum.xda-developers.com/showthread.php?t=843323
I think I need 10 posts before I can post in that thread.
So I guess...
That's 10.
It's dumb crap like this that is keeping people away from xda - too many thoughtless posts to sift through.
hi,
I followed the tutorial correctly http://forum.xda-developers.com/showthread.php?t=1928551
and my razri not start ..
* "M" written in the middle and "unlocked"
and is restarting ..
help
ty
Don't worry you just Bootloop.
What you have to do is download rsdlite, the motorola driver and the firmware were you come from (EU, GB, DE...), it's an ".xml" file.
Install the driver and rsdlite 6.0.4 on your computer.
After, you have to power on your phone in fastboot mode so press the volume down button and power on in the same time during 5s or 6s, your phone will boot in fastboot mode, stay in this mode and connect your phone to your computer.
To finish, open rsdlite, (you'll see your phone connect) select your ".xml" file and click start.
That's all
If it's not working there's an other solution but normally it'll work like charm!
Sent from my XT890 using xda premium
PELLET Nolwenn ty,
I tried 3 times, but I was stuck in this part...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and he keeps rebooting, and "M" written in the middle and "unlocked"...
Help :crying::crying:
ty.
I managed, appeared "FINISH" and "PASS"
but, he keeps rebooting, and "M" written in the middle and "unlocked"...
:crying::crying::crying:
pablopvh said:
I managed, appeared "FINISH" and "PASS"
but, he keeps rebooting, and "M" written in the middle and "unlocked"...
:crying::crying::crying:
Click to expand...
Click to collapse
I'm new to this phone, but my old motorola defy, when in bootloop, need cache/data wipe.
Start with cache, if still don't work, wipe all data.
Hope it works.
Try this:
Download fastboot file here:
http://koushikdutta.blurryfox.com/G1/
Dezip your xml file which you download before ( http://forum.xda-developers.com/showthread.php?t=1933308 ), take the file "boot.img" and put it on your desktop.
Dezip the files from fastboot.zip on your desktop
On your phone go into fastboot mode and connect it to the pc.
Open a terminal (right click, as administrator), write:
"cd desktop"
and after:
"fastboot flash boot boot.img"
Press enter, wait....
your phone reboot!
Hi,
diogo.sena not work :crying:
PELLET Nolwenn
What do I wrong? PELLET Nolwenn
error: cannot load 'boot.img'
:crying:
pablopvh said:
Hi,
What do I wrong?
error: cannot load 'boot.img'
:crying:
Click to expand...
Click to collapse
I can't see the file boot.img in your directory
The file boot.img is named boot_signed so rename it.
If you don't arrived download the firmware where you come from and dezip it (you'll see it that's obliged)
Sent from my XT890 using xda premium
I discovered what I was doing wrong,
I was with the sd card ...
and he ended up burning :/
Thanks PELLET Nolwenn i love you
Bye :laugh:
I have M7 without SD slot and I made USB OTG cable.
Phone accept to read Config.dat, but without success or to be more precise, process with green confirm IMEI and COnfig.dat, but with red letters state that can't access to some archives (something like MDNC or simmilar and some other files also).
I tried to do with Cyanogen 11 and also with stock 4.1 (also stock rooted), Unlocked with S-OFF and Relocked With S-OFF.
What is the problem???
Any idea?
komitaltrade said:
I have M7 without SD slot and I made USB OTG cable.
Phone accept to read Config.dat, but without success or to be more precise, process with green confirm IMEI and COnfig.dat, but with red letters state that can't access to some archives (something like MDNC or simmilar and some other files also).
I tried to do with Cyanogen 11 and also with stock 4.1 (also stock rooted), Unlocked with S-OFF and Relocked With S-OFF.
What is the problem???
Any idea?
Click to expand...
Click to collapse
as this method completely takes place in the bootloader the OS on the phone has nothing to do with it.
Get the proper cable and choose Amaze as your device and it works like a charm.
I used this one
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and this OTG adapter
clsA said:
Get the proper cable and choose Amaze as your device and it works like a charm.
Click to expand...
Click to collapse
Where I live is impossible to get proper Y cable and I used ordinary (simple) OTG from tablet, I opened access to red and black wires (power and ground), connected with other USB red and black, and now I'm 100% POSITIVE that cable works proper, as I.m able to install (e.g.) CM11 from that home made Y-OTG.
Also, I wrote that process start fine, but with message's:
SD init OK (green)
Reading config.dat [37]Bytes (blue)
Read MCCMNC file success (green)
Open CID file fail (red)
Open IMEI file fail (red)
Open SF file fail (red)
Open NAME file fail
Get device IMEI success (green)
IMEI checking .... PASS! (green)
Process done, reboot device? (blue)
As far as I understand, communication is perfect. I just don't know what files are process unable to open - on phone or on config.dat. I think that config.dat looks something like corrupted (but I requested it twice), as IMEI appear in text twice and for me appear that process can read IMEI on device, but not some other IMEI (??? - logical IMEI from config.dat). I'm just confused as it also try to read other files and I recognize just CID, what config.dat should not to have as they didn't ask for it. So, it appear that process can't read some files from phone and can read some other files from phone.
It will be more easy to detect problem if somebody knows did config.dat contain MCCMNC file, as for me looks that it is some strange mix.
Process check IMEI PASS (can read device IMEI obvious and looks that can compare with IMEI from config.dat).
Whatever, I'm confused.
Any idea?
I have a serious problem, I installed the B133 and now the update and has left me a window constantly open
"Sorry, Unfortunaly the process com.android.phone has stopped." and do not let me do anything
I already restored but I get the fine not to the cust, any ideas?
how the Reverting back 2.3
I got the same problem and I can't go back to 2.3,pls someone help us :/
GuyS
Try to flash 2.3 recovery and dload it..
How do I flash it?I don't understand how because of huawei that is too complicated..
You need adb tools, google how to install them and enable USB debugging. After installing put the recovery image into the adb folder and type
cd c:/[position of the adb folder]
adb devices
adb reboot bootloader
Fastboot flash recovery recovery[name of recovery].img
Fastboot reboot
The problem is that I simply can't do anything when my phone is on!I only get a message that says "unfortunately com.android.phone has stopped" so I can't go to the settings and enable the usb debug mode
Boot the phone pressing volume down and power let's you directly get into the bootloader.. So just use the two Fastboot orders
So,I'm on the bootloader..Now when I try to open fastboot on my pc,only a black tab appears and disappears after a sec,is that normal?
Gaudhier said:
So,I'm on the bootloader..Now when I try to open fastboot on my pc,only a black tab appears and disappears after a sec,is that normal?
Click to expand...
Click to collapse
downl this https://www.sendspace.com/file/uhv7n4
u need to get 2.3 recovery from somewhere I dont have it.. put it in there in folder and flash it there is command first one..
if u want u can force 2.3 ROM via adb .. with second command
I think I have a recovery from huaweiupdateextractor..
This is what I get,and it seems like fastboot doesn't recongnize my phone..
View attachment 3078581
Gaudhier said:
I think I have a recovery from huaweiupdateextractor..
This is what I get,and it seems like fastboot doesn't recongnize my phone..
View attachment 3078581
Click to expand...
Click to collapse
u need to be in bootloader.. and those your typed commands are nonsense .. type ; fastboot flash recovery recovery.img (when u copy your 2.3 extracted ..
Edit : Sorry, nonsense. Didn't saw post above
This is what i get.. View attachment 3078641
And by bootloader you mean the system recovery?Where I can do a factory reset?
Type: Fastboot flash recovery recovery.img
Then you are able to flash another firmware or to do a Factory reset
I typed it several times,but I don't understand why it always shows "cannot determine image filename for recovery.img" like on the screenshot I posted earlier,I don't understand because I moved the recovery into the ADB folder
edit:It worked when I deleted the second adb folder I had earlier..But now the thing is that it stays on "waiting for device" even if I'm in recovery mode
You wrote a couple of things, but not those four words...??!
---------- Post added at 07:40 PM ---------- Previous post was at 07:33 PM ----------
I think I mentioned the mistake. You need administrator rights for this procedure, it looks like if you run cmd as a normal user..?
l3Nni said:
You wrote a couple of things, but not those four words...??!
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This time I wrote the whole thing,but it still says "waiting for device"
And well I run it with administrator rights but it's still waiting for device :/
I added something to my last post.. Tried as admin?
l3Nni said:
I added something to my last post.. Tried as admin?
Click to expand...
Click to collapse
I'm already running it as admin
Hello guys (and girls) and welcome to (probably) my first guide
!! Be aware, I have tried the following procedure and am using S5 Elite Lite ROM by MaHo_66 !!
To start the unlocking procedure, first see if your device is actually sim-locked by inserting another sim-card from another provider and see if it asks for a code. If it asks, press on dismiss. Now, the actual steps:
Take a note of your CSC and MODEM with the help of Phone INFO.
Download from my GDrive I9305XXALI5_I9305EVRALI5.zip and copy it to either an USB OTG drive or to a MicroSD card (if you have one).
Make sure you have a custom recovery installed. Boot into it with the VOL UP+HOME+POWER button combination and make a nandroid backup of your current ROM. Make sure to do it on the MicroSD if you have one.
Go and do an advanced wipe and only wipe the following partitions: Cache, Dalvik Cache, Data and System.
Now install the zip file you previously copied on either an external USB OTG drive or on the MicroSD card.
While the rom is booting, search around on XDA for the aforementioned CSC code and a suitable modem for your BACKED UP rom.(The ZIP file I provided you will have changed the modem and CSC, so make sure you noted the CSC and modem before)
After the rom is done booting, skip the set-up wizard and the network lock screen. Now, go to the dialer and type *#197328640#
Here, go this way: [1] UMTS > [1] Debug Screen > [8] Phone Control > [6] Network Lock > [3]Perso SHA256 OFF > and wait for around 30 seconds. If you see at the Network Lock screen 4 options, you are good to go.
Press on the menu button (device) and tap on Back. Then, choose [4] NW Lock NV Data INITIALLIZ. After about 30 seconds, you should see PERSO_NV_INIT is SUCCESSFUL. From this point , you are unlocked. You can use any sim card in the device. If you have a third carrier sim card, test it out.
Reboot the phone and enjoy your unlocked phone. NOT SO FAST.
Reboot back to recovery and do an advanced wipe (the following partitions: Cache, Dalvik Cache, Data and System). Restore your nandroid backup now. Don't reboot the device to system, but go and flash the MODEM and CSC. Now, you are ready to reboot back to system and enjoy your KitKat or Lollipop ROM.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
12.
Go to UMTS-COMMON-NV REBUILD and then tap Erase only Backup, then after it is done head back and tap on Make Back-up. You are all set now in case you restore the NV again by mistake, the simlock status will remain OFF.
The sim-unlocked devices do not really exist, they are just unlocked from the factory after a NV backup. If you restore the default NV, it simlocks it.
Click to expand...
Click to collapse
That's it. Now you are SIM UNLOCKED, have your device the way it was before and with a backed up NV in case something goes horribly wrong. Special thanks to @LucasBass for his thread, to RCS&RDS for their internet, and to Enel Energie Muntenia for not failing on me.
P.S. I didn't find the zip somewhere, so credits to @lamahgra for lamahgra-rom.v1.4-lite. All i did was download I9305XXALI5_I9305EVRA5_EVR.zip and extract&replace the system folder, the baseband.bin, boot.img and hidden.img and edit CSCVersion.txt and SW_Configuration.xml.
Must try that..
How can I do step 12 after I've restored my lollipop rom?
@Vvaheed, @singhdhirendra28, @Geofftey, @ZoranAncev, @newstead01, @senpdy:
Ladies & gentlemen, please be aware that this thread is for the Samsung Galaxy S3 LTE (aka GT-i9305). If you posted due to post #4 please be aware that the account of the user who posted that is already disabled.
I don't intend to ask why you need the codes or ouvertly publish IMEI's.
Thread cleaned!
Be aware that if you share your IMEI this can be used by other users and your device turns into a ded piece of hardware.
NEVER SHOW YOUR IMEI!
did not work for me
i just tried this now, it did not work for me
it had some "could not map..." error
Thank God i had a Backup, the process left my phone without an OS