Develop Bugs

I've bricked my flatmate's Desire? [FIXED, thanks]

NOTE: THIS ISSUE HAS BEEN FIXED, See this post #97 by "teppic74" for how I fixed the phone
My flatmate recently got a Desire from Vodafone, it's got their latest ROM on it with all their bloatware.
I told him I could debrand it, but the goldcard method didn't work because he had bootloader 0.83.
So I followed a thread to this site on how to downgrade the bootloader:
http://www.tolxdorff.net/tutorials/?step=2
So I did step 4... and then the screen went blank. I left it for a while, I thought it may be installing...
After a long time, I pulled the battery out and rebooted the phone ... I'm pretty nervous by this point LOL
Anyway, the phone reboots and I can hear the annoying HTC chime, which never happened on the Voda rom...
But I can't see anything. It appears that the phone is booting up, but the screen is not working.
Anyone got any advice on what I might do to fix this or am I toast? Grateful for any advice.

Have you try it again or download a original rom (maybe on vodafone...on my o2site it give a original rom and also here on xda)...or have you tried unrevoked...what say the h boot now..?????
with kind regards...Alex

Unforunately that's the problem... the phone is working and booting up, but the screen is blank... so I can't see anything.
I'll try to find and flash the voda rom, that's a good idea

mmm_ok said:
Unforunately that's the problem... the phone is working and booting up, but the screen is blank... so I can't see anything.
I'll try to find and flash the voda rom, that's a good idea
Click to expand...
Click to collapse
so you cant even get into recovery?

mmm_ok said:
Unforunately that's the problem... the phone is working and booting up, but the screen is blank... so I can't see anything.
I'll try to find and flash the voda rom, that's a good idea
Click to expand...
Click to collapse
you have no acsess to bootloader or recovery.....??
try vol down (hold it) and phone on (power)...

Well... I think I can get into recovery... it's just I can't tell because the screen is not showing anything...
if I was to make a noob guess at what's wrong, and this is unsubstantiated, it's that it's a new desire with SLCD screen and that it's get the driver for the AMOLED screen installed when I downgraded...

Two more people over at modaco at reporting the same issue, I think:
http://android.modaco.com/content/h...o-com/315329/ive-bricked-my-flatmates-desire/
http://android.modaco.com/content/htc-desire-desire-modaco-com/315332/borked-recovery-image/

Test your theory.
Pull out the battery and put it back in.
Press and hold volume down and birefly press power on.
Keep volume down pressed for 5 seconds, then release it.
Count 20 seconds, then press the power key briefly once more.
You should now be in fastboot.
Connect your phone to the USB port and it should list it self when you execute fastboot devices.
If see it listed, you can restore the original ROM via the vodafone RUU file.

mmm_ok said:
Well... I think I can get into recovery... it's just I can't tell because the screen is not showing anything...
if I was to make a noob guess at what's wrong, and this is unsubstantiated, it's that it's a new desire with SLCD screen and that it's get the driver for the AMOLED screen installed when I downgraded...
Click to expand...
Click to collapse
have you try phone on...wait 3-5 min and flash the original rom....or maybe a original ota with h boot 092...maybe windows recognizes the phone

georgemv said:
Test your theory.
Pull out the battery and put it back in.
Press and hold volume down and birefly press power on.
Keep volume down pressed for 5 seconds, then release it.
Count 20 seconds, then press the power key briefly once more.
You should now be in fastboot.
Connect your phone to the USB port and it should list it self when you execute fastboot devices.
If see it listed, you can restore the original ROM via the vodafone RUU file.
Click to expand...
Click to collapse
not bad...that is what i think too
edit: but better explained

mmm_ok said:
Two more people over at modaco at reporting the same issue, I think:
Click to expand...
Click to collapse
Correct that's me.
I tried a normal boot, unrevoked found the phone but got stuck waiting for boot loader.

I did follow the test you mentioned regarding fastboot.
Windows did make a bleep bleep sound when i plugged it in, but when I ran adb devices (is that what you meant when you asked "is it listed"?), there were no devices listed.
The phone does make the annoying htc sound on normal boot... just no screen

mmm_ok said:
I did follow the test you mentioned regarding fastboot.
Windows did make a bleep bleep sound when i plugged it in, but when I ran adb devices (is that what you meant when you asked "is it listed"?), there were no devices listed.
The phone does make the annoying htc sound on normal boot... just no screen
Click to expand...
Click to collapse
nothing in the list also not unknown...?

Alex-V said:
have you try phone on...wait 3-5 min and flash the original rom....or maybe a original ota with h boot 092...maybe windows recognizes the phone
Click to expand...
Click to collapse
Thanks I did try to flash an original ROM... but I get the same problem I had before when running the RUU (error 140)
If I find a .92 ROM, i'm not sure I can install it without seeing what's on the screen though...

Alex-V said:
nothing in the list also not unknown...?
Click to expand...
Click to collapse
Nah, it just says "List of devices attached" and then nothing

mmm_ok said:
I did follow the test you mentioned regarding fastboot.
Windows did make a bleep bleep sound when i plugged it in, but when I ran adb devices (is that what you meant when you asked "is it listed"?), there were no devices listed.
The phone does make the annoying htc sound on normal boot... just no screen
Click to expand...
Click to collapse
ADB will not find your phone in fastboot. You need to download fastboot binary and run fastboot devices to list devices in fastboot mode. If you use windows, you also need to install the fastboot windows driver. (I think you can find that in the android SDK)

I no longer even get the startup beep. Think I am totally screwed?

georgemv said:
ADB will not find your phone in fastboot. You need to download fastboot binary and run fastboot devices to list devices in fastboot mode. If you use windows, you also need to install the fastboot windows driver. (I think you can find that in the android SDK)
Click to expand...
Click to collapse
Thanks for your help. I'm working on it. Get back to ya soon.

SavageCore said:
I no longer even get the startup beep. Think I am totally screwed?
Click to expand...
Click to collapse
I'm getting the bleep bleep cause I tried to install the generic rom... you're probably not getting it because you only tried to root the existing rom, is that correct?

yeah i used this driver...open attached htm file (if you have download unrevoke...its also in) adb

[Q] Desire (stock, not root) can't boot !

Hi,
I need help with my HTC Desire 2.2 stock (not rooted).
I don't know why but it can't boot (freeze on HTC white screen).
I tried vol down + power button to enter in bootloader then tried to clear storage and other items but I still can't boot in normal mode.
Anybody can help me please ?

How long have you left it before turning it off?

About 1 minute. How long should I wait ?
Since I cleared storage it vibrates 7 times quickly and doesn't boot.

bysus said:
About 1 minute. How long should I wait ?
Since I cleared storage it vibrates 7 times quickly and doesn't boot.
Click to expand...
Click to collapse
Any resolve to the above problem anyone? I have the same situation, also bootloader loads intermittently, when it does, mostly gets stuck after a few seconds. Any suggestions appreciated

mndgz said:
Any resolve to the above problem anyone? I have the same situation, also bootloader loads intermittently, when it does, mostly gets stuck after a few seconds. Any suggestions appreciated
Click to expand...
Click to collapse
Probably a hardware failure. But you can also try to download a stock rom. Then remove your sim and sd card. Go into the bootloader, select fastboot and then run the ruu on your pc.
If you still have the same problem you have a hardware failure.

cant enter boot loader as well
I have almost the same prob here. my phone is dead and after going to boot loader and want to flash a stock rom,the phone does not recover after RUU wanting it to reload bootloader

Lennyz1988 said:
Probably a hardware failure. But you can also try to download a stock rom. Then remove your sim and sd card. Go into the bootloader, select fastboot and then run the ruu on your pc.
If you still have the same problem you have a hardware failure.
Click to expand...
Click to collapse
I get the feeling that it's to do with hardware as well...
I extracted rom.zip from a stock ROM and tried flashing via SD card, but it either comes up as invalid CID or freezes altogether after 'Parsing PB99IMG.zip'

mndgz said:
I get the feeling that it's to do with hardware as well...
I extracted rom.zip from a stock ROM and tried flashing via SD card, but it either comes up as invalid CID or freezes altogether after 'Parsing PB99IMG.zip'
Click to expand...
Click to collapse
Exactly same error at my end to... cid error both with rom.zip n Rom.exe please help us... pleasre
Sent from my HTC Desire using XDA App

If you have a cid error, then you have the wrong rom. Cid means that if you are branded, you can only flash branded roms. For example, if your carrier is vodafone, you should flash a vodafone stock rom. Otherwise you will get that error.

Accidently flashed a tablet rom on my GNEX

Since then I get no service.
Now it's the AKOP B20 Rom.
Latest Franco kernel.
HELP????

Flash a radio maybe ?

I think I got xxkk6 radio :S

reflash the radio anyway

Didnt work

Try the stock google image try nexus root kit.

Iv'e tried that.
Not working.
I don't think there's anything I didnt try.

Have you flashed a different rom

wayneb02 said:
Have you flashed a different rom
Click to expand...
Click to collapse
Yes, It's on the stock rom of google.
Nothing has changed.

It seems like the phone "turned" into a tablet.
Everything works fine besides the mobile network.
Iv'e tried different sim cards, different rom and I flashed the radio again.
STILL DEAD.

Nandroid backup?

Use the fastboot images from Google to return to stock. Then if things still don't work, relock the bootloader and look into your warranty.
http://code.google.com/android/nexus/images.html

Jaredsk74 said:
Use the fastboot images from Google to return to stock. Then if things still don't work, relock the bootloader and look into your warranty.
http://code.google.com/android/nexus/images.html
Click to expand...
Click to collapse
Done that.
I guess warranty is the my only option right now.

turgi said:
Done that.
I guess warranty is the my only option right now.
Click to expand...
Click to collapse
Have you tried going into the service menu and cycling/checking that the preferred network is set correctly and the radio is on: *#*#4636#*#* /phone information/
Set preferred network type default should be gsm/cdma auto (prl) and radio should of course be on.

rgbc said:
Have you tried going into the service menu and cycling/checking that the preferred network is set correctly and the radio is on: *#*#4636#*#* /phone information/
Set preferred network type default should be gsm/cdma auto (prl) and radio should of course be on.
Click to expand...
Click to collapse
The device is not searching for a network.
It gives me an error if I'm trying to do it manually.

Iv'e tried to fix it with ODIN and now its ever worst.
The phone won't start. I get a black screen with a draw of a phone and a monitor. Between them there is a line and in the middle a yellow triangle with exclamation mark.
I think the phone is absolutely dead.

what happens if u plug it into your computer?

wayneb02 said:
what happens if u plug it into your computer?
Click to expand...
Click to collapse
Nothing. Dead.

Press the Volume up+down buttons on the screen with the android guy. Anything happen?

Ryands991 said:
Press the Volume up+down buttons on the screen with the android guy. Anything happen?
Click to expand...
Click to collapse
There's no such screen.
Just a black screen with a monitor and a phone.
No respond to any of the buttons.

[Q] What have I done to my Desire to prevent it from working on Rogers??

Long time reader/self-resolver. First time poster.
I have a Telus HTC Desire that I rooted years ago and successfully put Oxygen on. I've now switched to Rogers and wish to use the phone on the new network.
I've purchased and entered an unlock code from Telus. Every time I put in a Rogers sim card (I've tried five different Rogers sim cards) the phone tells me there is no sim card present. It also asks me to enter an unlock code every time I boot up. I enter it again and the phone tells me unlock was successful. This happens every time I put a Rogers card in but then I get the symbol in the menubar that there is no sim card present.
I've gone to a local store that unlocks phones and they gave me a T-Mobile card to try out. While the phone showed that there was no network (an inactive simcard), the phone did NOT give me a message that there was no sim card present - just like when my no-longer-active Telus card is put in. This tells me that the phone is, in fact, unlocked. It does not ask me for an unlock code with either a Telus or T-mobile card inserted. Just ANY Rogers card.
I've since put two more ROMS on there - MildWild and 4.2.2 ROM I can't recall the name of anymore (shows a multicolored X on the splash screen). No dice.
I've updated the radio to 5.17.05.23 and still no recognition of any Rogers simcard.
I've read up on the Rogers APN settings and tried many times to enter them, but the phone won't save them - perhaps because it doesn't see a simcard?
Might I have done something irreversable to the radio when I rooted the phone way back when? Can I undo what I did?
I've noticed that the chip is smaller on the Rogers simcards than the chip on the Telus cards. Should this matter? The phone is supposed to be able to work on the Rogers network.
I'm slightly exasperated and am finally asking for help.
Please let me know if there is any other information I can offer.
Much obliged....

Give the sim unlock tool in the desire general section a try.
I used it on my telus desire when I had to switch to rogers and it worked perfectly.
Sent using xda-developers app

Chromium_ said:
Give the sim unlock tool in the desire general section a try.
I used it on my telus desire when I had to switch to rogers and it worked perfectly.
Sent using xda-developers app
Click to expand...
Click to collapse
Yh i used it too, couple weeks ago when i got new motherboard for my desire and it worked perfect first time and very fast

jmcclue said:
Yh i used it too, couple weeks ago when i got new motherboard for my desire and it worked perfect first time and very fast
Click to expand...
Click to collapse
Thanks for the prompt reply gentlemen. Did you guys use Windows 7 when running the unlocker?
I keeping getting a hang on 'Waiting for HBOOT' and an "Error13a: AdbReadEndpointSync returned error 31 hboot usb plug"
I've read that the unlocker doesn't work in Windows 7. I've also tried the 0.9.4 version and it hangs as well.
My phone reboots into HBOOT but then says "HBOOT USB PLUG" and nothing else happens.
FYI, I'm doing all of this with the old Telus simcard in because my Rogers simcard is in my wife's phone right now - if that matters.

CCNutritionist said:
Thanks for the prompt reply gentlemen. Did you guys use Windows 7 when running the unlocker?
I keeping getting a hang on 'Waiting for HBOOT' and an "Error13a: AdbReadEndpointSync returned error 31 hboot usb plug"
I've read that the unlocker doesn't work in Windows 7. I've also tried the 0.9.4 version and it hangs as well.
My phone reboots into HBOOT but then says "HBOOT USB PLUG" and nothing else happens.
FYI, I'm doing all of this with the old Telus simcard in because my Rogers simcard is in my wife's phone right now - if that matters.
Click to expand...
Click to collapse
Yea i did it with Win 7. Try taking the sim out of the phone while doing it.
Also read my post here (more info on what exactly to do)

Chromium_ said:
Yea i did it with Win 7. Try taking the sim out of the phone while doing it.
Also read my post here (more info on what exactly to do)
Click to expand...
Click to collapse
Thanks Chromium.
I've updated the drivers as per your instructions so far as I can tell (in fact I'd updated them earlier following a different thread) and I'm running everything the same (HBOOT, Touch Panel, etc.) as you were at the time of the post you linked to except that I've gone back to Mildwild so I'm running Gingerbread instead of ICS.
If I run the unlocker from the bootloader then it tells me there is no phone found and to enable ADB. It doesn't see that I'm already in HBOOT.
If I let the unlocker reboot into bootloader for me after a normal full boot it seems to get stuck on the second reboot, again not able to see that I'm already in HBOOT and it waits to infinity for a phone to appear.
Debugging is on, so I'm not sure what's up here.
The status in my bootloader is HBOOT USB PLUG. Should it just be showing HBOOT?

CCNutritionist said:
Thanks Chromium.
I've updated the drivers as per your instructions so far as I can tell (in fact I'd updated them earlier following a different thread) and I'm running everything the same (HBOOT, Touch Panel, etc.) as you were at the time of the post you linked to except that I've gone back to Mildwild so I'm running Gingerbread instead of ICS.
If I run the unlocker from the bootloader then it tells me there is no phone found and to enable ADB. It doesn't see that I'm already in HBOOT.
If I let the unlocker reboot into bootloader for me after a normal full boot it seems to get stuck on the second reboot, again not able to see that I'm already in HBOOT and it waits to infinity for a phone to appear.
Debugging is on, so I'm not sure what's up here.
The status in my bootloader is HBOOT USB PLUG. Should it just be showing HBOOT?
Click to expand...
Click to collapse
USB PLUG is normal (just means that your phone is plugged in while in hboot). Looks like its not detecting your phone. Download and extract this zip. Then go into the platform-tools folder, shift + right click in an empty space, Open command window, and enter "fastboot devices". Does your phone show up?

Chromium_ said:
USB PLUG is normal (just means that your phone is plugged in while in hboot). Looks like its not detecting your phone. Download and extract Then go into the platform-tools folder, shift + right click in an empty space, Open command window, and enter "fastboot devices". Does your phone show up?
Click to expand...
Click to collapse
No, nothing appears to show up. This is with the phone in bootloader.

CCNutritionist said:
No, nothing appears to show up. This is with the phone in bootloader.
Click to expand...
Click to collapse
Got it to work.
After several days of not being able to get the computer to see the phone no matter how many threads I followed I took a few days away, returned and tried the .iso method and that worked.
My Desire is now fully functional on the Rogers network.
Thank you for your help!

[Q] Bootloop, can't access Recovery Mode

Hi All!
I've checked all similar threads but I haven't found any solution to my problem, hence this post.
I was trying to root Samsung Note 2 and install Cyanogenmod but rooting failed
The current problem:
1. Samsung Note 2 has ended up in a bootloop after failed rooting
2. I can't boot the phone in the Recovery Mode
3. The USB Debugging Mode was not activated
4. I can't turn on the phone
Description:
I was trying to root my friend's Samsung Note 2 using the following method from this website http://forum.xda-developers.com/showthread.php?t=2291827
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
Click to expand...
Click to collapse
The problem is that by mistake I used a wrong CF-Auto-Root... file and instead of this file CF-Auto-Root-t03g-t03gxx-gtn7100.zip which was designed for Samsung Note 2 I used a file which I was using before for my own phone (Samsung Galaxy S4) CF-Auto-Root-jflte-jfltexx-gti9505.zip
Result 1: The rooting process got frozen and I had to disconnect the USB cable connecting the phone with the computer.
Result 2: Black screen, I couldn't boot the phone.
Next, I used the same rooting method but with the correct CF-Auto-Root... file.
Result 3: Bootloop. The phone boots up when I press the power button but when I see the first screen with a white "Samsung Note 2" on a black background, the phone reboots again and the process repeats itself for ever.
Result 4: I can't boot the phone in recovery mode. When I press the Volume Up+Power+Home buttons, the phone reboots and keeps rebooting instead of going into recovery mode.
Result 5: The USB Debugging Mode was not activated before rooting. Since I can't turn on the phone I can't activate the mode now. All solutions to my problem that I've seen require having USB Debugging Mode activated.
Could anyone help me and suggest what to do, please?
I don't know much about how mobile phone works but I can follow instructions if I know what to do.
I rooted my own mobile phone and installed Cyanogenmod successfully. I wanted to do the same with my friend's phone who was fed up with bloated and slow manufacturer's firmware.
I hope you can help me. Thank you.

I really don't know why so many users try to root before flashing a custom rom -> it is simply useless and as shown in this example dangerous, when a false root method or file is chosen.
You need:
1. Custom recovery, flash through ODIN, I think latest TWRP will do the job
2. Flash your desired custom rom through above recovery, (if needed: GApps also)
3. Flash SuperSu if needed (read in OP of that rom) done
If number 1 won't work, you got to flash firmware from sammobile first using ODIN
and then take steps 1, 2, 3

Androidwizzard said:
I really don't know why so many users try to root before flashing a custom rom -> it is simply useless and as shown in this example dangerous, when a false root method or file is chosen.
You need:
1. Custom recovery, flash through ODIN, I think latest TWRP will do the job
2. Flash your desired custom rom through above recovery, (if needed: GApps also)
3. Flash SuperSu if needed (read in OP of that rom) done
If number 1 won't work, you got to flash firmware from sammobile first using ODIN
and then take steps 1, 2, 3
Click to expand...
Click to collapse
Hi AndroidWizzard!
Thank you very much for your quick reply.
I've done everything as you advised me to and... it worked!
Firstly, I installed TWRP, I wiped all files on the phone, downloaded Cyanogenmod to external SD card, installed Cyanogenmod through TWRP and all done! I also installed the minimum version of Gapps and it's all I need.
Thank you SO much for your help. twdeim which
All the best!

britanix said:
Hi AndroidWizzard!
Thank you very much for your quick reply.
I've done everything as you advised me to and... it worked!
Firstly, I installed TWRP, I wiped all files on the phone, downloaded Cyanogenmod to external SD card, installed Cyanogenmod through TWRP and all done! I also installed the minimum version of Gapps and it's all I need.
Thank you SO much for your help.
All the best!
Click to expand...
Click to collapse
Never praise a ford till you get over.
Click to expand...
Click to collapse
As I said, everything I mentioned before went fine but there is one problem. The system doesn't detect the network as if the SIM card wasn't inserted. I double checked everything and I have no idea what that is.
I installed CyanogenMod version 11-20140715-NIGHTLY-n7100 with android version4.4.4.
I would be very grateful for any suggestions.
Many thanks!

Access Recovery Tool
RecoveryFix for Access data recovery software expediently recover inaccessible Access file. It recovers user data from damage Access files.

udansikka said:
RecoveryFix for Access data recovery software expediently recover inaccessible Access file. It recovers user data from damage Access files.
Click to expand...
Click to collapse
I am sorry but I don't understand how RecoveryFix relates to my problem. Could you write a bit more, please?
Thank you.

britanix said:
I am sorry but I don't understand how RecoveryFix relates to my problem. Could you write a bit more, please?
Thank you.
Click to expand...
Click to collapse
Hi All,
I've solved the problem. Thank you!

britanix said:
Hi All,
I've solved the problem. Thank you!
Click to expand...
Click to collapse
can you tell me how to solved your problem because i have something like your problem

suirs said:
can you tell me how to solved your problem because i have something like your problem
Click to expand...
Click to collapse
The problem originated from the fact that my IMEI got lost somewhere during failed rooting/flashing. I've flashed with the stock firmware which retrieved my IMEI and the phone connected to the network as usual. After the phone was brought back to the fully operational state, I used CyanogenMod installer for Mac and I successfully installed CM, and it works like a dream.
I hope it will help. Good luck!

britanix said:
The problem originated from the fact that my IMEI got lost somewhere during failed rooting/flashing. I've flashed with the stock firmware which retrieved my IMEI and the phone connected to the network as usual. After the phone was brought back to the fully operational state, I used CyanogenMod installer for Mac and I successfully installed CM, and it works like a dream.
I hope it will help. Good luck!
Click to expand...
Click to collapse
there is have a version worked on windows 7 ??

suirs said:
there is have a version worked on windows 7 ??
Click to expand...
Click to collapse
I understand that you are asking if there is a CyanogenMod installer for Windows. Yes, there is, particularly for Windows http://beta.download.cyanogenmod.org/install

Just copy of my posts in another thread as this one is more relevant to my problem I think:
Good afternoon gents and girls, I have a bit strange problem wonder if anyone can get a bit of light on it. My Mrs's GT-7100 one day was stuck on boot up screen. I thought is was corrupt tried to do factory reset. Didn't work out read about is decided to flash it with a different official ROM for that installed twrp-3.0.2-0-t03g.img.tar and was trying to do a lot of different things within TWRP mode. As I'm not familiar with flashing process I guess didn't do it properly BUT! While doing it all over sudden I realised that the phone is actually working while connected to external power it shows charge and goes upto 100% but as as soon as it disconnected from main power source it starts to reboot constantly again stuck at the same boot screen again, till reconnected to power source again, then goes in to fool boot and functions properly making and receiving phone calls. The charge shown on the battery drops from 100% to 4-7% in a matter of the boot up time which is say 5-10 seconds.
Tested by multimeter battery shows 4.32V. I can't test battery under load, but will endeavor to do so by a test light. I have a bit strange problem wonder if anyone can get a bit of light on it.
So any thoughts?
I suspect the battery is not the issue. I have 2 external banks which are holding the charge to keep running Galaxy 3 8.0 up to 2-3 hours in use. Both of them are 5.2V 1A and having GT-7100 connected to them doesn't help to boot up the phone. Olso 5V 0,5A charger of Bluebery either, only Samsung 2A charger gets the GT-7100 back to fanctioning mode. When phone is booted up it shows
The ROM Version it is N7100XXUFND3,
Kernel version 3.0.31-152758,
Build number
KOT49H.N7100XXSFQA1
SE for Android status
enforcing
SEPF_GT-7100_4.4.2_0016