[Q] some custom rom 911 Emergency number not working!! - Samsung Galaxy Nexus

Hi ,
a couple of days ago, during a small emergency, I tried to call 911, and the the phone was showing CALL ENDED , after 1 second . all the time.
Today after several tests, found out, that my GSM Samsung Galaxy Nexys I9250
1 - with STOCK ROM, 911 works.
2 - with Android Revolution Custom ROM, DOESNT WORK.
3 - with LIQUID ROM , doesnt work.
the baseband installed right now is : I9250XXLA2
has any other person report this ISSUE.
I was lucky that wasnt not a REAL EMERGENCY, but I will like to inform this.
and should be a sticky somewehere, so any one that try any rom know about this possibility.
could happen on another phones? or is related to the i9250 GSM.
cheers
Ezequiel

ezequielpelax said:
Hi ,
a couple of days ago, during a small emergency, I tried to call 911, and the the phone was showing CALL ENDED , after 1 second . all the time.
Today after several tests, found out, that my GSM Samsung Galaxy Nexys I9250
1 - with STOCK ROM, 911 works.
2 - with Android Revolution Custom ROM, DOESNT WORK.
3 - with LIQUID ROM , doesnt work.
the baseband installed right now is : I9250XXLA2
has any other person report this ISSUE.
I was lucky that wasnt not a REAL EMERGENCY, but I will like to inform this.
and should be a sticky somewehere, so any one that try any rom know about this possibility.
could happen on another phones? or is related to the i9250 GSM.
cheers
Ezequiel
Click to expand...
Click to collapse
I hope you post this in the respective rom threads, this is an important issue.
Sent from a phone...

You checked "yes this is a question"
Guess where it belongs?
Thread moved!
Sent from my SPH-D700 using xda premium

keep working on it .
Very strange, with the stock rom, the 911 works.
I have 2 galaxy nexus I9250 .
with the same custom rom, panandroid, all baseband, and all the same,
one of the phone still not working the 911 emergency call.
I will flash a baseband update, and see if is fixed.
may be was the way this phone is unlocked? ,
the phone that is working, I unlocked it with f##K cdomo, app.
but the one is not working the 911, was Unlocked, and permanent, with a not matching IMEI number to the PRINTED IMEI on the back.
I will post more if i have news.

app f##k kodomo, makes the 911 number not working
not sure, which combination of steps, or if it is the permanent unlock or temporary unlock, that changes imei number, and breaks the emergency call.
to fix it, I restore an OLD backup, with stock rom, and then used the f##k kodomo ap v2, with the option of make backup (wear condom item ) and then install any rom, install f##k kodomo , and restore the backup. (original IMEI will be restored )
now everything is working .
the main problem, is the app KODOMO, used to UNLOCK the GN I9250,
and only few people or no one test the 911 CALL .
please test it if you were messing up with Kodomo App/ Unlocking the GN.
as could be dangerous if is not working during an emergency.

Related

[Q] Permanent no service - tried multiple roms...revert to stock?

HI all,
First post, go easy on me!
I've searched the forums trying to find the answer to this problem but have been unsuccessful. I successfully flashed my Galaxy W with slimbean 3.1.0 and had been using it successfully for over a month. I put it in airport mode to save battery, as I had done many times before, but this time when I turned it off the service never came back. I haven't had service since.
I have tested the SIM in another phone and it is working fine. I have also tried flashing a different ROM (CM10 Alpha 1) with no luck. I would reflash the phone with the stock firmware if there is any chance that would help, but I haven't been able to figure out how to do that via CWM. At this point I'm not exactly sure what to do. Is it possible that the this is a hardware issue?
Any advice would be greatly appreciated!
mitchm said:
HI all,
First post, go easy on me!
I've searched the forums trying to find the answer to this problem but have been unsuccessful. I successfully flashed my Galaxy W with slimbean 3.1.0 and had been using it successfully for over a month. I put it in airport mode to save battery, as I had done many times before, but this time when I turned it off the service never came back. I haven't had service since.
I have tested the SIM in another phone and it is working fine. I have also tried flashing a different ROM (CM10 Alpha 1) with no luck. I would reflash the phone with the stock firmware if there is any chance that would help, but I haven't been able to figure out how to do that via CWM. At this point I'm not exactly sure what to do. Is it possible that the this is a hardware issue?
Any advice would be greatly appreciated!
Click to expand...
Click to collapse
Yes it´s possible it´s a hardware issue you got after a while.
First thing I would try is to flash back to stock ROM and see if this fixes your issue. (With Odin)
There is a guide about how to do that, but am sorry not to point you to it right now. Its 4am here righ now and I already am having difficulties to write correctly. (need to go to bed soon )
If this helps I would suggest to update the baseband and then to try again with CyanogenMod.
But if reflashing the stock ROM doesn´t help either, I would suggest to contact the Samsung Service Center.
By flashing back to the stock ROM make sure you are flashing the one used in your specific country, because in the first place it also inculdes the baseband used in your country and in the secound place it also inculdes the country code Samsung might look at while testing your phone.
In Germany for example most SGW´s were sold with it´s specific coutry code. But there were also a few sold with the county code for the whole EU.
So you must care about such things when flashing back to stock ROM. For fixing it the country code is not important. Only the baseband used in your region is important. But I case you need to contact the Samsung Service Center it will be important.
Hope this helps a bit. Now I really need to go to sleep.
Does your IMEI number still ok? Cause I lost my Efs folder with IMEI number some time ago, in another Galaxy fone i had.
you can check it in Settings / About fone / Status / IMEI
If you lost it, you will have no service, no matter what rom you try.
In this case, you can try to repair using this http://forum.xda-developers.com/showthread.php?t=1308546 , not simple but saved my fone.

Today,no mobile service - have worked hard for solution - no success

Hi there
I am in New Zealand, recently rooted with DR Ketan’s help and installed PhilzCWM. Also on Ketan’s advice, I backed up my EFS.
My problem: just today I realised I cannot send text, or make phone call. I am on X-Note ROM from 3-4 days ago. I am very sure that after installation, I had normal Mobile connectivity and was surprised to find I didn't. Not sure if my EFS became corrupted, or other ROM setting is wrong.
Under Settings About Device:
My SERVICE STATE says Out of Service
My Mobile NETWORK STATE says disconnected.
My phone number says UNKNOWN
What's weird is
My IMEI lists a long number, assumed correct and not corrupted
So if my EFS partition is corrupted I assume I wouldn't see any IMEI at all?
Far as I know my SIM is activated (I am on a company plan & coworker's phones are normal)
Just now I restored my stock nandroid and .... same thing! No service. So I doubt it's even a modem problem.
Guys I'm screwed, any tips what settings to check etc??
sounds like your IMEI is invalid. i had something random recently. all my flatmates use iphone 4s. they had no signal when @ home. cant send texts etc. wifi works.
then next day my LTE N2 did the same thing. I changed MODEM/BASEBAND problem corrected it self. went back to old MODEM/Baseband. no problems since.
only other thing i can think of is, someone has reported your IMEI to police or your provider..
does it say "NOT REGISTERED" ? or something similar where your provider name appears?
R0B3RTF1SH3R said:
sounds like your IMEI is invalid. i had something random recently. all my flatmates use iphone 4s. they had no signal when @ home. cant send texts etc. wifi works.
then next day my LTE N2 did the same thing. I changed MODEM/BASEBAND problem corrected it self. went back to old MODEM/Baseband. no problems since.
only other thing i can think of is, someone has reported your IMEI to police or your provider..
does it say "NOT REGISTERED" ? or something similar where your provider name appears?
Click to expand...
Click to collapse
Hey thanks for th tip.
My phone recognises Vodafone as my provider but still won't connect.
I will try flashing a different modem, I may not have paid enough attention to different versions when I flashed the aroma installer.
Thanks, I'll report back.
update: Vodafone shop confirms my SIM is 100% good, and it works in another phone. So I think you're right, my IMEI is fukt.
I was told by Voda that my proper IMEi is listed on my phone innards. The IMEI shown in phone settings is waaay different. So it's corrupted somehow. I gotta familiarise myself with how to flash my backup image. Damn just what I need on beer day Friday
I restored my backup image of EFS/IMEI - it solved my problem.
Because there was an IMEI listed in phone settings I wrongly assumed it was the correct one. So flashing ROMS can muck up your EFS.....thank god for backups
you can still use the custom roms. just if your IMEI stuffs up, there is methods to reset it. i had to do it once. wasn't that difficult but was rather troublesome. i just wanted to use the custom rom at the time.

[Q] Band Handover/voice network issues

So I have been waiting patiently for the 4.3 update to roll out to me OTA with hopes that it would fix my issues but my phone has been saying download interrupted and so I have gone back to completely stock and triangle away to get my device status back to normal but it still wont let me download. When looking around for other possible causes I saw that my build number is JRO03L.I747UCDLK3 which comes up as a build number for a nexus 7, the correct build number for my att should be JRO03C. I have no idea how it got that way but I am wondering if the person who bricked it might have put the wrong version of the bootloader or some other part of the firmware on and it somehow didn't brick but is detecting a conflict and not letting me OTA. Or that is what is causing my cell network issues as well. Wanting input from a a few devs as I am not 100% sure what the first part of the build number represents.
Ok guys and girl, I am having a really weird issue with my Att Gs3 that I wanted to see if anyone could help with. To start off a little bit of background. I Hard bricked my s3 in August, sent it for tag and got it back working and stock with no issues. All I did was root the phone for fear of messing it up again but it was running all stock without problems for over a month since the unbrick. About 3 weeks ago I went out of town within the state but a ways away, I was talking on the phone with a co-worker right before leaving town. At some point that evening I get a a text from my wife asking why I was ignoring her calls, I had never received them and according to my phone was in the middle of prime 4g lte zone in San Antonio but I was apparently only receiving that lte signal and the phone was not switching to the voice network on 4g to make or receive calls, I was even able to voice chat with my wife but I couldn't just call her normally. After returning home I was still unable to make or receive calls unless it was right after a restart and I had to try about 15 times, so I called att and tried all of their bs which didn't make a difference at all. Looking around on the internet I found the number that you can put in to get into service mode and switched it to gsm or wcdma only and voila I could make calls again. The only problem with that being that I travel within a city for work and move from 4g to 3g to edge all the time but if I have it set for wcdma only then I have no signal and have to take the time to pull up service mode to switch back and forth. So I tried going back to completely stock again by resetting/ formatting all and flashing the stock rom via odin, my issue persisted so I also decided to flash synergy rom (which I was running prior to the hard brick) and then intergalactic because I saw the fewest problems with it to no avail. I have flashed each stock modem new and old which made no difference at all. Today I was messing around in service mode and found an area that was called handover, in that subsection you have the option for checking the phones ability to switch from gsm to wcdma and back as well as to hspa, when I select any of those options I get the message "temporary block due to build e" or " temporary block code".
I was wondering if anyone has any ideas about what the possible problem could be, imei, modem hardware, or a stubborn stuck modem firmware setting.
I was also wondering if anyone had any experience with figuring out how to re-enable handover because that is where I feel my problem is, either through adb or any programs that let me force change the settings, I would also be happy if someone knew how to turn of only LTE and have both gsm and wcdma on at the same time.
Any help would be much appreciated, I have tried everything I know how to do, but am to the point where I am forced to look at new hardware because my wife is pregnant and I really needs to be able to get a hold of me any time.
Bump
Bump!...not looking good.
madnesshero86 said:
Ok guys and girl, I am having a really weird issue with my Att Gs3 that I wanted to see if anyone could help with. To start off a little bit of background. I Hard bricked my s3 in August, sent it for Jtag and got it back working and stock with no issues. All I did was root the phone for fear of messing it up again but it was running all stock without problems for over a month since the unbrick. About 3 weeks ago I went out of town within the state but a ways away, I was talking on the phone with a co-worker right before leaving town. At some point that evening I get a a text from my wife asking why I was ignoring her calls, I had never received them and according to my phone was in the middle of prime 4g lte zone in San Antonio but I was apparently only receiving that lte signal and the phone was not switching to the voice network on 4g to make or receive calls, I was even able to voice chat with my wife but I couldn't just call her normally. After returning home I was still unable to make or receive calls unless it was right after a restart and I had to try about 15 times, so I called att and tried all of their bs which didn't make a difference at all. Looking around on the internet I found the number that you can put in to get into service mode and switched it to gsm or wcdma only and voila I could make calls again. The only problem with that being that I travel within a city for work and move from 4g to 3g to edge all the time but if I have it set for wcdma only then I have no signal and have to take the time to pull up service mode to switch back and forth. So I tried going back to completely stock again by resetting/ formatting all and flashing the stock rom via odin, my issue persisted so I also decided to flash synergy rom (which I was running prior to the hard brick) and then intergalactic because I saw the fewest problems with it to no avail. I have flashed each stock modem new and old which made no difference at all. Today I was messing around in service mode and found an area that was called handover, in that subsection you have the option for checking the phones ability to switch from gsm to wcdma and back as well as to hspa, when I select any of those options I get the message "temporary block due to build e" or " temporary block code".
I was wondering if anyone has any ideas about what the possible problem could be, imei, modem hardware, or a stubborn stuck modem firmware setting.
I was also wondering if anyone had any experience with figuring out how to re-enable handover because that is where I feel my problem is, either through adb or any programs that let me force change the settings, I would also be happy if someone knew how to turn of only LTE and have both gsm and wcdma on at the same time.
Any help would be much appreciated, I have tried everything I know how to do, but am to the point where I am forced to look at new hardware because my wife is pregnant and I really needs to be able to get a hold of me any time.
Click to expand...
Click to collapse
if you have CM recovery or TWRP you can go back, wipe everything even twice could help, then flash a stock rom reboot and see what happens
if that doesnt work go back to odin and install stock firmware 4.1.2 from Samsung but again you have to wipe data/factory reset
3rd if that doesnt work, try to restore your EFS folder/files using this link http://forum.xda-developers.com/showthread.php?t=1725839
that link has everything, how to fix it, anything you need to know
BUY a new phone or use a different phone if all the options above fail
Tried
View attachment 2362929
winosxbuntu said:
if you have CM recovery or TWRP you can go back, wipe everything even twice could help, then flash a stock rom reboot and see what happens
if that doesnt work go back to odin and install stock firmware 4.1.2 from Samsung but again you have to wipe data/factory reset
3rd if that doesnt work, try to restore your EFS folder/files using this link http://forum.xda-developers.com/showthread.php?t=1725839
that link has everything, how to fix it, anything you need to know
BUY a new phone or use a different phone if all the options above fail
Click to expand...
Click to collapse
The backup restore/fix imei and data restore tools link doesn't go anywhere, does anyone have a link to the restore tool? The only version I can find is for the non us version of the s3.
I did at least use the tool for the 9300 to find out that I have some 000 for s/n and other numbers (see attachment)
is there a patch out for us gs3's to fix this like there is for the i9300?
madnesshero86 said:
View attachment 2362929
The backup restore/fix imei and data restore tools link doesn't go anywhere, does anyone have a link to the restore tool? The only version I can find is for the non us version of the s3.
I did at least use the tool for the 9300 to find out that I have some 000 for s/n and other numbers (see attachment)
is there a patch out for us gs3's to fix this like there is for the i9300?
Click to expand...
Click to collapse
I think I can help, I just need to pull up some files and I might get you the software or program I used to back -up and restore my EFS folder/files
Even fix it, so plz hang in there........will report back later on
Thanks a bunch, I am still trying all kinds of stuff but I feel pretty certain that the problem lies with a messed up efs and I don't think I have a backup unless doing a nandroid covers that as well, which I am not seeing that it does. Any further help is appreciated, is this something that a local cell repair shop can typically fix or is this a possible new phone situation?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
madnesshero86 said:
Thanks a bunch, I am still trying all kinds of stuff but I feel pretty certain that the problem lies with a messed up efs and I don't think I have a backup unless doing a nandroid covers that as well, which I am not seeing that it does. Any further help is appreciated, is this something that a local cell repair shop can typically fix or is this a possible new phone situation?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
this is the software/programme i used to back-up, recover or even fix my EFS files (if they are corrupt and can be used) NV items reader writer
type it on google and pretty sure you will find something , try different links and again am sure you will find a download
have you tried flashing the new 4.3 stock firmware and modem follow this link for everything http://forum.xda-developers.com/showthread.php?t=2498233 or you can wait for AT&T to release the official 4.3 firmware and that will be 100% satified to be stable and will fix all your EFS/IMEI problems FOR GOOD :laugh:
i have the NV items reader writer software that can fix your problems but i dont know how i can share it with you without breaking any rules
ULTIMATE/final solution send it to MOBILETECHVIDEOS and will fix it like its nothing, take it to samsung and have to play some ball, or BUY A NEW PHONE
tried kernels (idont think it will make any difference) but its good to check
I have tried all the other versions but will try the 4.3 what's the name of that software so I can try and find it or of you have drop box you could pm me the info and get it to me that way . In the meantime I found an fusion 2 for 38 bucks from att so I can get calls for the time being.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
madnesshero86 said:
I have tried all the other versions but will try the 4.3 what's the name of that software so I can try and find it or of you have drop box you could pm me the info and get it to me that way . In the meantime I found an fusion 2 for 38 bucks from att so I can get calls for the time being.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
NV items reader writer
type exactly as it is on google or here on XDA
New Info
See new info in OP Please, and before anyone says anything I have spent half the day searching with various keywords trying to find a fix so be kind if it seems obvious to you, I couldn't find it and I did try.
Bump

"No service"

Hello
I have LG G3 the international version with installed stock rom 5.0,
Before I install it, I backed up the previous kitkat rom.. When I installed the lollipop stock rom I decided to go back to my previous kitkat rom. After restoring it and booted it everything was ok but it says no service, emergency calls only. And the signal at the status bar was refreshing every second automatically. I tried to return to that lollipop rom to see whether the signal is ok or no but there was no problem with it. But I dont know whats the probkem in that kitkat rom.... Plzzzz helpppp mee!!
I have the same problem! I used a custom lollipop rom and messed with something so I had to restore the stock Kitkat.
Now it keeps searching for the signal and says "no service" It found the signal for a few times but lost it immidiately.. Wifi works fine.
i would be rly thankful if somebody can fix this.
Jatiska said:
I have the same problem! I used a custom lollipop rom and messed with something so I had to restore the stock Kitkat.
Now it keeps searching for the signal and says "no service" It found the signal for a few times but lost it immidiately.. Wifi works fine.
i would be rly thankful if somebody can fix this.
Click to expand...
Click to collapse
Flash suitable Kitkat modem for phone.
Im having the same issue i purchased a used G3 and it says " NO service" ive tried eveything and verified with sprint there is no block on the phone. got a new sim card from TING ... the phone will activate only over WIFI but i have never been able to get cell service Is this a hardware issue? im totally lost and TING is telling me to take it to a cell phone repair shop. ( i repair phones myself actually as part of my job but never run into this)
Ive flashed back to stock from via XDA instructions
Any help would be awesome!!
Thanks
I have found a lot of threads and people reporting this issue. Bought a D855 32Gb from China that has this problem...
Phone tries to get signal a couple of seconds and then a cross.. and so on..
I tried everything I think, I passed for all the bricks the phone can do: Automatic Reboot / Boot Loop / Fast Boot / Security Error / Factory Reset Status 2 / Dead (QHSUSB_DLOAD) - I can help anyone that has any of those problems : )
In one of the flashes my phone turned to D855RE, similar case to other people, also the message "Current version is not available for user. Can't find matched cust for NT-Code mcc/mnc".
Please if anyone was able to fix the problem report here, there is a lot of people waiting for the answer 20 threads in different networks, I will post the solution in each of those. Thanks!
Same happening with me,
I have LG G3 T-Mobile version, it keeps searching the service, sometimes it finds when there is very good signal, or when I am too close to the GSM antenna, I was thinking maiby there is problem with antenna contact, I have opened cleaned, but with no success. When is has service it does everything, calling, sms, 4G.
any help with this issue?
satrowii said:
Hello
I have LG G3 the international version with installed stock rom 5.0,
Before I install it, I backed up the previous kitkat rom.. When I installed the lollipop stock rom I decided to go back to my previous kitkat rom. After restoring it and booted it everything was ok but it says no service, emergency calls only. And the signal at the status bar was refreshing every second automatically. I tried to return to that lollipop rom to see whether the signal is ok or no but there was no problem with it. But I dont know whats the probkem in that kitkat rom.... Plzzzz helpppp mee!!
Click to expand...
Click to collapse
Get the modem from here for your firmware version (mine is 10M) and flash in custom recovery,i had the same problem after downgrading,all will be good
http://forum.xda-developers.com/lg-g3/general/radio-modem-lg-g3-t3110376
still no luck with modem/radio change
ludoke said:
Get the modem from here for your firmware version (mine is 10M) and flash in custom recovery,i had the same problem after downgrading,all will be good
http://forum.xda-developers.com/lg-g3/general/radio-modem-lg-g3-t3110376
Click to expand...
Click to collapse
HI. i tried to change to several radio but I still don't have a signal. I just can't find the thread from other site, that it could be a D850 not an D855 motherboard. He tried to change the ROM to D850 and finally got a signal.
I have the same problem, any help is welcomed.
PacMaNNNN said:
I have the same problem, any help is welcomed.
Click to expand...
Click to collapse
If you can, return the phone. As previous post suggested, its a popular thing from some chinese sellers to change the model. You will see the original model in your motherboard (you have to disassemble the phone) and have to flash the proper stock image. First confirm that the model is the model you ordered.
juanmazake said:
If you can, return the phone. As previous post suggested, its a popular thing from some chinese sellers to change the model. You will see the original model in your motherboard (you have to disassemble the phone) and have to flash the proper stock image. First confirm that the model is the model you ordered.
Click to expand...
Click to collapse
The phone was okay, this started happening when I flashed stock Marshmallow, then I flashed MIUI KitKat rom to see if its the the marshmallow that does that only, but it was on MIUI as well, after that I flashed Fulmics, but still the same. Now I'm on stock Marshmallow and it's doing it as well. I found a little "thing", when you set the network type to WCDMA/GSM there is no more no service, everything works. But when you put LTE it goes down.
If you suspect this can be the case of model tempering by seller, open your phone and unscrew the upper plastic cover, at the right you will see the Motherboard factory code with the phone model in it. Youll have to flash an according complete stock with flash tool.
juanmazake said:
If you suspect this can be the case of model tempering by seller, open your phone and unscrew the upper plastic cover, at the right you will see the Motherboard factory code with the phone model in it. Youll have to flash an according complete stock with flash tool.
Click to expand...
Click to collapse
and from where i can find japanese version of lg g3 sock firmware?

Elephone p8000. I think i messed up bad.

Ok so i got the phone is stock form with android 5.1 and a few bugs common to this phone( screen flicker and poor wifi speed). I read more than a few forum posts that said flashing the rom to various other roms would fix it and this wasn't my first modded phone so i did. I am not too sure these flashes took as android looked and acted the same as well as had some of the elephone software. It did however screw up the phones imei. after a google search i reset the imei. I no longer have the invalid imei message but now i have a big NO SERVICE message. This is the us market phone. I really hope you cant somehow change the frequncy bands by flashing the rom. any help would be awesome.
Ps. the screen still flashes.
edit: ok tookjfer671's advice and flashed the us rom. it killed the imei (again) so i reset the imei. now somehow the imei numbers got on the wrong sim cards. They are backwards. will this affect anything ? they wont reset at all.
Edit 2 I guess you can mark this one as solved. The reflash with the us ROM worked but the backlight still flickers. Not a launcher issue the entire screen goes dark and its random.
http://forum.xda-developers.com/ele.../rom-p8000-version-b-baseband-l1-mp3-t3322615
Yup, I believe the US version B doesn't have any other alternative custom roms to flash...although you can root. Version A (Asia/Europe) regions have a whole lot of roms to choose from...it would've been nice if we could flash those as well and keep the baseband out of it so we don't lose network connections.
Anyways...I flashed as well a version A rom and found myself with a no connection to my network (everything else worked fine), flashed the link above and got device back to full working order. Hope it helps you out.
jfer671 said:
http://forum.xda-developers.com/ele.../rom-p8000-version-b-baseband-l1-mp3-t3322615
Yup, I believe the US version B doesn't have any other alternative custom roms to flash...although you can root. Version A (Asia/Europe) regions have a whole lot of roms to choose from...it would've been nice if we could flash those as well and keep the baseband out of it so we don't lose network connections.
Anyways...I flashed as well a version A rom and found myself with a no connection to my network (everything else worked fine), flashed the link above and got device back to full working order. Hope it helps you out.
Click to expand...
Click to collapse
i'll give it one more shot. btw did you use flashtools or recovery?
Sorry for late reply...I was rooted with the A version and on TWRP recovery, flashed stock recovery then flashed B version and now on CWM recovery. All using flashtools.

Categories

Resources