Database Users

[Q] Can you help me to justify the phone is unlock able ?

hi all,
as title mention....... sorry for asking stupid question.
but i really did research from xda although its really make me confusing.......
and i did OTA update last 2 weeks, and my phone bought from singapore
come with HD dock also.
is it able to follw this thread
http://forum.xda-developers.com/showthread.php?t=1202883
thanks, if someone enlighten me.....
here is my phone info
system version
45.0.20.MB860.AsiaRetail.en.03
Model number
MB860
Android Version
2.3.4
BaseBand version
N_01.100.00R
Webtop version
WY-1.2.0-133_22
Kernel version
2.6.32.9
[email protected] #6
APflex version
GAS_ASIA_USAOLYGBSEARET_P011
GAS_ASIA_USAOLYGBSEARET_A003
GAS_ASIA_USAOLYEMSEARET_M001
Build number
4.5.2A-74_OLE-20

Yes. Use this thread and download the Orange/Bell/Telestra/Latin America/International users ONLY file. The file should be named IHOP_Bell.rar . Flash it with RSDLite. Done.
I know you are new, but next time, questions go in the Q&A section. Thanks!

Also @OP, make sure that you indeed want to unlock your phone, because once you unlock your phone it stays unlocked forever.
A lot of people get excited about unlocking their phones, and start a thread later on how they can lock it back up because for whatever reason they changed their minds...
Sent from my MB860 using xda premium

ccrows said:
Also @OP, make sure that you indeed want to unlock your phone, because once you unlock your phone it stays unlocked forever.
A lot of people get excited about unlocking their phones, and start a thread later on how they can lock it back up because for whatever reason they changed their minds...
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
ha??
change it back to lock status??
why??
i cant guess it what reason make them do that....
but for me, i just curious for unlock and trying for other roms....and may be for further ICS preparation.
and actually currently official roms quite good enough for me.
thanks for you notice....

matthew5025 said:
Yes. Use this thread and download the Orange/Bell/Telestra/Latin America/International users ONLY file. The file should be named IHOP_Bell.rar . Flash it with RSDLite. Done.
I know you are new, but next time, questions go in the Q&A section. Thanks!
Click to expand...
Click to collapse
Sorry.... i will do it on Q&A section next times.
Thanks. for guidance......

GT-i9505 not detetcing my SIM card

I recently got a GS4 in my hands. The details are mentioned below:
Model: GT-i9505
Android version: 4.2.2
Baseband: I9505DXUAME2
Build number: JDQ39.I9505DXUAME2
kernel: 3.4.0-526204
I pulled the source code for the same from the Samsung website. Compiled and deployed it without making any changes to the stock code (ensuring that the instructions are followed neatly...I have been doing it successfully on other Samsung models). My device boots fine but stops detecting the SIM card. I don't know what may be wrong here.
I am not sure if it has to do something with the code which I picked from the Samsung website. I tried using two different source codes but the result remained the same. I see in the kernel logs that exfat_fs and exfat_core drivers are not being loaded due to version mismatch. But I don't think it could be the reason behind my problem.
Any hints as in how can I debug this issue? What can I check in the kernel logs to get to the root cause of this issue?

epitoro said:
I recently got a GS4 in my hands. The details are mentioned below:
Model: GT-i9505
Android version: 4.2.2
Baseband: I9505DXUAME2
Build number: JDQ39.I9505DXUAME2
kernel: 3.4.0-526204
I pulled the source code for the same from the Samsung website. Compiled and deployed it without making any changes to the stock code (ensuring that the instructions are followed neatly...I have been doing it successfully on other Samsung models). My device boots fine but stops detecting the SIM card. I don't know what may be wrong here.
I am not sure if it has to do something with the code which I picked from the Samsung website. I tried using two different source codes but the result remained the same. I see in the kernel logs that exfat_fs and exfat_core drivers are not being loaded due to version mismatch. But I don't think it could be the reason behind my problem.
Any hints as in how can I debug this issue? What can I check in the kernel logs to get to the root cause of this issue?
Click to expand...
Click to collapse
Flash stock rom via odin.

I want to modify one of the drivers in the stock code and that is why I downloaded and compiled the kernel code. But before making my changes, I tried to do a sanity and ran into this problem. Going back to stock is not going to help me. So, essentially I have to find out the reason as in why it is not working with the stock code. Any clues for debugging this issue?

epitoro said:
I want to modify one of the drivers in the stock code and that is why I downloaded and compiled the kernel code. But before making my changes, I tried to do a sanity and ran into this problem. Going back to stock is not going to help me. So, essentially I have to find out the reason as in why it is not working with the stock code. Any clues for debugging this issue?
Click to expand...
Click to collapse
Oh understood. Unfortunately Im not good with that, but you can open thread here http://forum.xda-developers.com/forumdisplay.php?f=2321 Im sure devs will help you.

thanks!!
But I am not allowed to post in that forum as I am a new joinee and only experienced users may post. If that is the case, how can I reach out to the developers?

epitoro said:
thanks!!
But I am not allowed to post in that forum as I am a new joinee and only experienced users may post. If that is the case, how can I reach out to the developers?
Click to expand...
Click to collapse
Is type imei still there or is it corrupted?
Sent from my GT-I9505 using xda premium

sxi200 said:
Is type imei still there or is it corrupted?
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
good point

No. Settings menu doesn't show imei as well as the baseband version once i flash the compiled kernel. But both return as soon as i flash back the stock kernel. Shall i try to recover imei as it essentially doesn't get lost. I believe the real problem is somewhere else and loosing imei is just a side effect of that.
Sent from my GT-I9300 using xda app-developers app

I have verified that the contents of the efs folder don't change between the two kernels.
I mentioned in my first post that ext_fs drivers are not being loaded by the new kernel. Are these two things somehow correlated: efs and ext_fs. Namewise it seems that ext_fs driver reads efs folder. Its just a guess. Does it makes sense to someone else?
Sent from my GT-I9300 using xda app-developers app

Any comments please.
Sent from my GT-I9300 using xda app-developers app

epitoro said:
Any comments please.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I come from an i9000, where imei issues like these are always solved by flashing the stock rom again. Then you can make a backup of your efs folder and start your iterations again. Might also work this way for the s4.
Verstuurd van mijn GT-P5100 met Tapatalk

I was using a wrong config file for the kernel.
Sent from my GT-I9300 using xda app-developers app

One may use the following cmd to genrate the correct config:
make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig SELINUX_DEFCONFIG=jfselinux_defconfig ARCH=arm
Sent from my GT-I9300 using xda app-developers app

Hi im having this issue recently, im not very gppd when it comes to this sort of thing have u sorted out? & if so how did u resolve the issue?
Sent from my GT-I9505 using Tapatalk

eddie500_1 said:
Hi im having this issue recently, im not very gppd when it comes to this sort of thing have u sorted out? & if so how did u resolve the issue?
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
You need to compile the source code available from Samsung Open Source with the attached config file. Steps will be:
1) Goto to the root of your kernel source tree and run this cmd:
make mrproper
2) Extract .config file from zip and place it in the root dir or your kernel source tree
2) Compile using gcc for ARM architecture (ARCH=arm) using the toolchain

[Q] Can I root and unlock the bootloader on 98.16.1 ?

Can I root and unlock the bootloader on 98.16.1 ?
Thanks, and sorry if this qualifies as a "use the search function" question - for the record I tried that route.

Okay, 96 views and no responses, so it must be a stupid question... I just don't know if that's a yes or no, and I've been Googling, but no one talks in terms of Moto firmware when talking about the bootloader...

Looks like that's the older firmware, so you should be able to. Try rooting it first. If that works, you ought to be able to unlock the boot loader as well.
Sent from my Droid Razr M using Tapatalk 4 Beta

Thanks, I eventually came to that conclusion as well, since the update everyone says to avoid is a higher number than what I'm getting.
Sent from my Galaxy Nexus using xda app-developers app

root/bootloader unlock for 4.4.2

hey guys, im terrible with Motorola phones for some reason and i cant find a root method for my droid razr m, im looking at tons of threads with "Root 4.4.2" in the title but none of the methods work, im on System version: 182.46.15.xt907 Build number : KDA20.62-15. could i be able to downgrade? thanks guys, sorry for sucking at finding threads...... i use the "Search" Tool like everyone complains but still can never find anything.

Locked bootloader or not? (Go to fastboot mode to check)
If locked, then you're doomed.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

AndyYan said:
Locked bootloader or not? (Go to fastboot mode to check)
If locked, then you're doomed.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
yeah dang it looks like im doomed, so i read that the update to .15 basically had all the security updates that 4.4.4 had, so Jcases Sunshine does only work on 4.4.3 devices and below (moto x/moto g/mini/ultra) currently 4.4.4 is not supported on shunshine (my moto x has 4.4.4) do you think sunshine would work if we get it updated and try it on .15?

Trozzul said:
yeah dang it looks like im doomed, so i read that the update to .15 basically had all the security updates that 4.4.4 had, so Jcases Sunshine does only work on 4.4.3 devices and below (moto x/moto g/mini/ultra) currently 4.4.4 is not supported on shunshine (my moto x has 4.4.4) do you think sunshine would work if we get it updated and try it on .15?
Click to expand...
Click to collapse
Might as well try, but I think if there's already a working root method then the forum wouldn't have been silent like this.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

Yea it wouldn't hurt to try as it says 1.6 doesn't need root and it won't charge you if it doesn't work...
We cannot teach people anything; we can only help them discover it within themselves.

ezknives said:
Yea it wouldn't hurt to try as it says 1.6 doesn't need root and it won't charge you if it doesn't work...
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
ill try my best to find v1.6 and give feedback, i didnt even think of v1.6!

For anyone reading this in the future, the sunshine bootloader unlock did work on my .15 Razr M, and like it says if it doesn't work it won't charge you.

Galaxyninja66 said:
For anyone reading this in the future, the sunshine bootloader unlock did work on my .15 Razr M, and like it says if it doesn't work it won't charge you.
Click to expand...
Click to collapse
I'd reflash stock firmware, Factory reset, and retry Sunshine
Sent from my sailfish using XDA Labs

Escape from 182.46.15 / 183.46.15 ?

Is not there a possibility to totally wipe/blank the phone (bootloader, kernel) and back to epoch, then start from scratch?
Think about these are as:
- radiocomm
- qflash
- or something else ...
even if it is very difficult?

I guess the updated, locked bootloader won't even allow you to do any of that, just like how it rejects flashing custom system/recovery images.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

Was thinking to "force bricking" and then somehow unbricking... in any way destroy or replace the current bootloader in order to not be able to prevent the intervention. What do you think about the "blank bootloader", what are the possibilities it gives?

Replace BL -> supposedly not allowed by current BL
Destroy/clear BL -> unable to boot up & lose access to fastboot flash mode -> no way to flash in anything
...at least these are what I think.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

The boot loader is locked this means we do not have access to this. We cannot downgrade the boot loader period if you are on .15 and not previously unlocked
Sent from my XT907 using XDA Free mobile app

Well, that sounds pretty bad. Although this was a very good device, I have to look for other, probably Nexus, which is open ... It was not a good move from Motorola.

I agree it was a bad move but it seems to be the nations standard these days
Sent from my XT907 using XDA Free mobile app

What do you think about the bugreport? Already occurred twice since the KK update (never occurred in JB).
~7MB txt file, the the beginning of the file looks like this:
bugreport-2014-10-13-10-15-59.txt:
========================================================
== dumpstate: 2014-10-13 10:15:59
========================================================
Build: KDA20.62-15
Build fingerprint: 'motorola/XT907_verizon/scorpion_mini:4.4.2/KDA20.62-15/15:user/release-keys'
Bootloader: 0x109B
Radio: msm
Network: Telekom XX
Kernel: Linux version 3.4.42-g46d4525-00001-ga9305fd ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Jul 29 02:16:18 PDT 2014
Command line: console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 vmalloc=400M androidboot.emmc=true androidboot.serialno=TA59707LSY androidboot.baseband=msm androidboot.mode=normal androidboot.bootloader=0x109B androidboot.cid=0x2 androidboot.hwrev=0x82A0 battery= mot_sst=1 androidboot.carrier=vzw product=smq androidboot.device=smq androidboot.secure_hardware=1
------ UPTIME (uptime) ------
up time: 5 days, 14:59:52, idle time: 1 days, 03:29:45, sleep time: 4 days, 09:13:57
[uptime: 0.1s elapsed]
...
...

RAZR M towelroot not working
i update razr m from 4.1.2 to stock kk by rsd lite now i want to do cutom rom towelroot giving error this phone isnt supported b\c as geohot says it works on build date prior to 3 june 2014 but my build date is 29 july 2014 with system version 183.46.15.xt907 .verison..... i also try to downgrade to jellybean by rsd lite but my bootloader is locked plz tell me is their any way to unlock the bootloader by any method that i can instal custom recovery. or i need to wait untill geohot release new app to support further builds after 3 june....

abifahad said:
i update razr m from 4.1.2 to stock kk by rsd lite now i want to do cutom rom towelroot giving error this phone isnt supported b\c as geohot says it works on build date prior to 3 june 2014 but my build date is 29 july 2014 with system version 183.46.15.xt907 .verison..... i also try to downgrade to jellybean by rsd lite but my bootloader is locked plz tell me is their any way to unlock the bootloader by any method that i can instal custom recovery. or i need to wait untill geohot release new app to support further builds after 3 june....
Click to expand...
Click to collapse
You're stuck, you can't root .15, you can't unlock it, and you can't downgrade if you're locked. This has been discussed a billion times.
Sent from my HTC6525LVW using Tapatalk

sympatex said:
Well, that sounds pretty bad. Although this was a very good device, I have to look for other, probably Nexus, which is open ... It was not a good move from Motorola.
Click to expand...
Click to collapse
mrkhigh said:
I agree it was a bad move but it seems to be the nations standard these days
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
its more verizon wanting the locked bootloader then motorola

After about a month of use after the experience 183.46.15 verizon update:
- constant cracking sound from the speaker in any event
- 3 random shutdown (while running with endomondo, the result is of course lost)
- 2 random reboots
- continuous battery drain
The latter is probably due to the fastdormant apk, but since there is no root, nothing can be done.
In summary, due to the new update the device completely unusable. Previously, in JB, none of the above error occurred (after >600 miles running with same device)
We can say that Verizon only create the update to prevent the root, and nothing else test the software.
I wonder why it was so urgent to send the .15 OTA? Maybe in order to "destroy" the devices as soon as possible people having to buy another one?

.15 sucks big time
sympatex said:
After about a month of use after the experience 183.46.15 verizon update:
- constant cracking sound from the speaker in any event
- 3 random shutdown (while running with endomondo, the result is of course lost)
- 2 random reboots
- continuous battery drain
The latter is probably due to the fastdormant apk, but since there is no root, nothing can be done.
In summary, due to the new update the device completely unusable. Previously, in JB, none of the above error occurred (after >600 miles running with same device)
We can say that Verizon only create the update to prevent the root, and nothing else test the software.
I wonder why it was so urgent to send the .15 OTA? Maybe in order to "destroy" the devices as soon as possible people having to buy another one?
Click to expand...
Click to collapse
Really bad decision by me not to unlock bootloader. Paying the price now with the update.
For me,
- Phone display or power button stops responding at least 2-3 times a day. This is followed by an automatic reboot
- Battery drains really quickly - clearly because of the Modem FastDormancy Monitor
Things I have tried so far:
- Factory Reset
- Modify the NVM to accommodate GSM
- Kept phone in GSM only mode
- Disabled Modem FastDormancy App
- Kept phone in safe mode
Nothing works. Same behaviour.
Will try to flash 183.46.15 over my 182.46.15 with a complete data wipe. Not many hopes left. :crying:

Changi said:
Really bad decision by me not to unlock bootloader. Paying the price now with the update.
For me,
- Phone display or power button stops responding at least 2-3 times a day. This is followed by an automatic reboot
- Battery drains really quickly - clearly because of the Modem FastDormancy Monitor
Things I have tried so far:
- Factory Reset
- Modify the NVM to accommodate GSM
- Kept phone in GSM only mode
- Disabled Modem FastDormancy App
- Kept phone in safe mode
Nothing works. Same behaviour.
Will try to flash 183.46.15 over my 182.46.15 with a complete data wipe. Not many hopes left. :crying:
Click to expand...
Click to collapse
Me too. I am not stuck I can go back to JB..but can't for few weeks as laptop is not currently here...
So following things are helping me right now to keep my bettry a little (it won't last more then 5-7hrs) but these things helped some
=Iam keeping my phone on safemode
=I am keeping brightness at lowest
=I am using du bettary saver
=most best I am using greenify
Better way to use greenify:
use greenify every time before pressing screen lock button...it closes all apps..allow greenify to auto kill apps (no root need) create a shortcut.. And just bang this shortcut one it will force close each application running automatically... It worked for me a lot saved something like 6hrs on standby and a lot time while using.thanks

RikRong said:
You're stuck, you can't root .15, you can't unlock it, and you can't downgrade if you're locked. This has been discussed a billion times.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
people talk like this too much its like you have seen it so you think we must have seen it

doshjaniels said:
people talk like this too much its like you have seen it so you think we must have seen it
Click to expand...
Click to collapse
I'm not going to argue about it, but it's been discussed in every thread about .15 and there have been many threads about .15.
Sent from my HTC6525LVW using Tapatalk

RikRong said:
I'm not going to argue about it, but it's been discussed in every thread about .15 and there have been many threads about .15.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I think u r same who ruined my post in which I was explaining those .15 can't do anything -_-

livecouk said:
I think u r same who ruined my post in which I was explaining those .15 can't do anything -_-
Click to expand...
Click to collapse
I'm actually the one that let you know you can downgrade since you're unlocked. [emoji6]
Sent from my HTC6525LVW using Tapatalk

rikrong said:
i'm actually the one that let you know you can downgrade since you're unlocked. [emoji6]
sent from my htc6525lvw using tapatalk
Click to expand...
Click to collapse
[deleted] [*apologize]

livecouk said:
Hmm means you are other guy sorry. That guy who ruined by post I hate hm
Click to expand...
Click to collapse
It's me then? Just trying to give some advice, nothing wrong with that, eh?
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]