Database Users

IMEI CM9 lost issue

Well over in the t mobile side of the gs3 we are thinking of different theories...
We think it has to do with the way recovery was installed
If you installed CM9 and lost IMEI did you flash using a cwm recovery installed via Odin or via Adb or terminal emulator
Same question applies to the people who didn't loose IMEI
State your recovery version and also the way you installed and if you lost IMEI or not. Let's get this started!
Sent from my SGH-T999 using Tapatalk 2

I have my imei. I think we should also include date of device release or maybe even serial numbers.
I have a release day blue 16 GB tmo, no problems. I installed cwm via Odin at first, then flashed the newest non-touch cwm using rom manager. Flashed cm10, no problems. Nandroid back, flashed kernels, etc..

Yea your right we should include date
I got mine you can say a week or so after release day, i did flash aokp and didn't loose IMEI, do you think it would be safe to flash cm9 since I didn't loose IMEI when I flashed aokp?
Sent from my SGH-T999 using Tapatalk 2

Just curious does the imei problem only apply to t-mobile and at&t sgs3's?

Odd.. wonder why my last post didn't appear..
Anyway, isn't the hardware revision number listed on a stamp under the battery, along with the imei and whatnot? Would be useful to track hardware batches along with software.

DarkManX4lf said:
Just curious does the imei problem only apply to t-mobile and at&t sgs3's?
Click to expand...
Click to collapse
I really wouldn't know
Sent from my SGH-T999 using Tapatalk 2

I started a thread here, didn't limit it to CM9 and tried to organize via hardware/recovery, and ROM.
http://forum.xda-developers.com/showthread.php?t=1783990
Post if you see fit...

Markdental said:
I started a thread here, didn't limit it to CM9 and tried to organize via hardware/recovery, and ROM.
http://forum.xda-developers.com/showthread.php?t=1783990
Post if you see fit...
Click to expand...
Click to collapse
Thanks glad to see if got something started! Love this community
Sent from my SGH-T999 using Tapatalk 2

IMEI fine here
I flashed cwm using ODIN, then installed Rom Manager and got latest cwm, flashed Sonic Team FreeGS3 Release 1.5, then installed touch recovery from Rom Manager, flashed FreeGS3 release 3, flashed Adama 003 kernel, did a Nandroid backup, flashed CM9, then restored back to FreeGS3 release 3. Of course, not all of this was done immediately after one another. I wiped data/factory reset, wiped cache & dalvik cache 3 times each in between each flash just to be safe. I also did all flashing from recovery and none from Rom Manager. I have a 16GB Tmo Pebble Blue that I picked up from Walmart on release day.
Hopefully we can get to the bottom of this soon, so I can start flashing again worry free!

You guys didnt see this http://forum.xda-developers.com/showthread.php?p=28883417
This thread has been going on for way over a week
Sent from my SAMSUNG-SGH-I747

sTyLeSz said:
Well over in the t mobile side of the gs3 we are thinking of different theories...
We think it has to do with the way recovery was installed
If you installed CM9 and lost IMEI did you flash using a cwm recovery installed via Odin or via Adb or terminal emulator
Same question applies to the people who didn't loose IMEI
State your recovery version and also the way you installed and if you lost IMEI or not. Let's get this started!
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Installed recovery with the QCOM Toolkit with the allinone package root, insecure boot, Busybox...
rebooted to make sure all was good, flashed FireFox release 3.
Installed Touch CWM 5.8.4.5 VIA Terminal rebooted
nandroid
wiped factory reset/cache/system
flashed AOKP then GAPPS and booted
no IMEI or any issues at all... waiting on CM10 to be more stable too flash.

Have you tried to flash cm9 using cwm touch v5.8.4.5 installed via terminal emulator or adb?
Sent from my SGH-T999 using Tapatalk 2

[Q] Stuck in boot after flashing PA

I just flashed Paranoid Android on my N7 running 4.1.2, and it's stuck in the boot animation. I've been on this for about 10 minutes now. What should I do?

Go back to recovery, factory reset, wipe caches and reflash
Sent from my Nexus 7 using xda app-developers app

Try long pressing the power button to turn it off and try booting again. Sometimes it hangs on boot after flashing. Especially with certain kernels.

Wow, I'm in the same spot here after flashing PA. Can't get to recovery, PC isn't seeing it either. Been searching all day. Can anyone point us in the right direction? It will be much appreciated.

SpazticWonder said:
I just flashed Paranoid Android on my N7 running 4.1.2, and it's stuck in the boot animation. I've been on this for about 10 minutes now. What should I do?
Click to expand...
Click to collapse
chivo559 said:
Wow, I'm in the same spot here after flashing PA. Can't get to recovery, PC isn't seeing it either. Been searching all day. Can anyone point us in the right direction? It will be much appreciated.
Click to expand...
Click to collapse
Did you guys update the bootloader?
Sent from my SAMSUNG-SGH-I747 using xda premium

Apocalypse487 said:
Did you guys update the bootloader?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Nope! I'm slapping myself as with one hand as I type with the other. Is there any method of salvation? *Please note: I rely on toolkits most of the time. Any help is appreciated, as always.
***Got it! I forgot to carry the one!

chivo559 said:
Nope! I'm slapping myself as with one hand as I type with the other. Is there any method of salvation? *Please note: I rely on toolkits most of the time. Any help is appreciated, as always.
***Got it! I forgot to carry the one!
Click to expand...
Click to collapse
So you fixed it? I updated the bootloader before updating PA to any newer versions. I haven't had bootloops. I followed the DROIDMODDERX video on YouTube when I was on 4.1.1. In the tool kit thread it tells you how to update.
Sent from my SAMSUNG-SGH-I747 using xda premium

Reboot error related to paths?
I flashed my N7 a few weeks back (using goomanager) with 4.2 JB which worked fine. I then put on gapps and got an endless loop of error messages about trying to configure them. At this point I rebooted to recovery and put back on rooted stock 4.1.1.
I thought I would try PA again this week and the ROM flashes OK, but when I reboot the N7 "hangs" at the boot screen and goes no further. The same thing happens if I try SmoothROM. I can go back to rooted stock OK though.
I notice the paths have been updated as per 4.2 but otherwise things appear the same as before.
Any idea why PA now won't boot?
Thanks
mik

4.3 cm-10.2

Has anyone tried the 4.3 cm10.2 ROMs found over here (http://androidhosting.org/Devs/Dhacker29/cm-10.2/)? I was going to give it a go last night but for some reason my device got stuck on the "warning your boot loader is unlocked" screen and had to use Matt's utility to give it life... I may give it a try tonight when I'm not expecting any calls...
Sent from my XT907 using xda app-developers app

Yeah, I'm running the latest version of it now. I had the same problem. What worked for me was the following:
1. Wipe everything - system, data and both types of cache.
2. Install CM 10.2 and NOTHING else. Boot the ROM. It should go through now.
3. Once you get to the main screen, reboot into recovery.
4. Install the 4.3 GAPPS version. Reboot, get to the main screen and reboot into recovery.
5. Now flash the 4.3 version of Supersu for CM 10.2
6. Boot one last time into CM 10.2
All the links for everything you need can be found with a Google search. Later I may edit this post to include those links.
Sent from my XT907 using Tapatalk 4

Thank you kindly for the reply... I got it booting finally but couldn't get su permission on TiB and what not... I didn't know about needing the 4.3 su ...I'll flash that now... again thank you kindly
Sent from my XT907 using xda app-developers app

TWRP isn't supported either from what I understand. You need to run CWM.

Any time I install 4.3, it won't reboot. It starts up initially, but I can't get it to get past the Motorola logo upon second boot.
I have tried the normal install method and this method.
Then recovery doesn't see the /data folder so something is wrong with the 4.3 install I presume.
Does it change the location of data?

Yeah I Tried It But It Had No Sound So I Changed Over To 4.2.2 AOKP.

grtechguy said:
TWRP isn't supported either from what I understand. You need to run CWM.
Click to expand...
Click to collapse
I was using CWM on my first attempt... this time around I switched to TWRP...
Sent from my XT907 using xda app-developers app

grtechguy said:
TWRP isn't supported either from what I understand. You need to run CWM.
Click to expand...
Click to collapse
I use TWRP, works ok. Got sound, data, everything working fine. Battery life sucks, but no surprise there.

My 2c
I'm running it right now. I must have missed the part about flashing SuperSu, because I can't do anything as root. I had trouble the first time I flashed with the phone bootlooping, but I flashed again and that fixed it. Battery life is somewhat poor, but I just found the performance page today (Icon was different, silly me!) so we'll see how it goes with a different governor. I've been having issues with Navigation and Bluetooth audio on anything except stock. Bluetooth audio locks the phone and I have to soft-reset it. Navigation crashes if you try to multi-task while using it.

HOW TO Install CM 10.2 (Android 4.3) for Razr M (xt907)

I am running CM 10.2 by Skrilax - http://skrilax.droid-developers.org/cm10.2nightly/razrqcom/index.php?device=xt907 (Might be fine with the DHacker version also, but this is what I used.
Pretty much everything seems to work including GPS. I do not have Bluetooth anything so I can't speak to that. Some (maybe most) people seem to have difficulty getting it installed, but it can be done. There are a few tricks to it. Here's what worked for me:
I highly recommend using TWRP 2.6.0 as that's what I use and I know it works. Not sure whether other recoveries will function the same or not.
What you need:
1. The most recent version of CM 10.2 from the link above.
2. Gapps Core 4.3 - http://goo.im/devs/BaNkS/GApps 4.3
3. Root for 4.3 - http://download.chainfire.eu/342/SuperSU/UPDATE-SuperSU-v1.43.zip
1. Erase everything except the external sdcard. Do it three times. (Don't ask, just do it.)
2. Also Format Data - what the heck, do that 3 times too.
3. Install the CM 10.2 ROM, wipe dalvik and cache again and reboot into the system. DO NOT install anything else at this time for best results.
4. Let the OS boot all the way to the desktop.
5. Unlock the developer options by going into Settings\About Phone and tapping 8 times on Build number. (Only needs done one time, updates do not hide it again.)
6. In Developer options, change Root Access to "Apps and ADB". (Go ahead and set up whatever else you want in Settings.Do not install any apps or updates at this time.)
7. Reboot into Recovery. Install Gapps Core 4.3
8. Clear dalvik and cache and reboot into System. If it hangs on the Motorola logo, get back into Recovery and format data again. (This is why I said don't install apps or updates yet.)
9. Once the phone boots all the way, reboot into Recovery again and install Root using Supersu 1.43.
10. Clear dalvik and cache and reboot into System. If it hangs on the Motorola logo, get back into Recovery and format data again. (This is why I said don't install apps or updates yet.)
11. Once System has booted, you can update SuperSu in the Google Play Store. The first time you open it, it will want to update the binary. It's very important that you choose the option to do it from Recovery. Your phone will reboot into Recovery, update the binary and then boot back into System.
12. Once all this is done, so are you. Restore your apps, allow Google Play to do any updates, and customize the layout to your tastes.
Note: Once you get a successfully installed 10.2 setup, you can dirty flash the nightlies. Always clear dalvik and cache. And always backup your apps before flashing anything if you want to make your life easier.
ENJOY!!!

Going to give it a go with CWM I'll let you know how it goes.

Well I got the rom to work but I could not get it to boot after loading gapps. I tried wiping data but no joy!

Hey, Thanks for the very clear update instructions - I'm now on CM 10.2!
I am not able to successfully root though. SuperSU complains:
"There is no SU binary installed and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manualyl re-root - consult the relevant forums for your device!"
I have tried to reflash the SuperSU zip posted here multiple times to no avail...
Thoughts?
EDIT: Solved with http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip

Flashed TWRP and I was able to get it up and running having the same issue with root going to try the file above and I'll update again.
edit
*** the supersu 1.51 file worked for me as well. ***
---------- Post added at 04:43 PM ---------- Previous post was at 03:47 PM ----------
I'm still having issues. I got the root to work but everytime I reboot the device I have wipe data or it hangs on the boot logo.
---------- Post added at 05:02 PM ---------- Previous post was at 04:43 PM ----------
Restored back to carbon rom 1.8. I may try again after a few more dailies are out. As this is my primary device I can not have the issues I saw. Admittedly it may be something that I did wrong and not the rom.
Sent from my XT907 using xda premium

Got this up and running last night and no issues so far for me. I'm wondering though if any custom kernels work with 10.2? I was curious about the vanquishpuppiesn12 kernel.

kensdavid said:
Hey, Thanks for the very clear update instructions - I'm now on CM 10.2!
I am not able to successfully root though. SuperSU complains:
"There is no SU binary installed and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manualyl re-root - consult the relevant forums for your device!"
I have tried to reflash the SuperSU zip posted here multiple times to no avail...
Thoughts?
EDIT: Solved with http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
Click to expand...
Click to collapse
You must not have followed every step exactly. The process I outlined works flawlessly if it is followed exactly. I'm glad you were able to resolve it though. You ended up with the same result and that's what matters!
Sent from my XT907 using Tapatalk 4

Thanks for sharing , make a mark

netizenmt said:
You must not have followed every step exactly. The process I outlined works flawlessly if it is followed exactly. I'm glad you were able to resolve it though. You ended up with the same result and that's what matters!
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
can you confirm if rear mic is working when taking videos? this has been the only hangup for me on the 4.2.2 ROMs...
I doubt it, since that functionality is probably kernel related, but still just curious...
thanks!

Ok I noticed that I had somehow installed the wrong TWRP I installed 2.6.0 today and I have so far had good luck phone is up and running and seems to be stable. At first I had some issues with a few apps throwing errors during the mass install when I sync'ed with Google but a manual download after and they installed just fine. Also the new camera app called focal has some issues for me it opened and took pics but images in gallery are blank. However the stock camera app seems to working fine at least for stills I have not tried video yet.

I've got this all working too, including root. But I've been noticing about a second delay when pressing power to unlock the phone. Sometimes it delays so long that I press power again. So when the phone does wake up, the screen goes off again from my double press of impatience. I'm running the 0907 nighlty
Sent from my XT907 using XDA Premium 4 mobile app

FWIW, never needed to wipe data multiple times and I flashed everything at once. That said, still a good procedure to follow
Also, @georgeascott, that's a known bug. It tends to SOD on occasion... Not much to do to fix except maybe overclocking
Sent from my XT907 using Tapatalk 4

Any plans for safe strap support? My bootloader is apparently permanently locked. Stock isn't terrible.. You can disable and hide bloatware.. But it would be really nice to have pie instead of soft buttons and restart and screen shot on the power menu
Sent from my XT907 using xda app-developers app

zombolt said:
Any plans for safe strap support? My bootloader is apparently permanently locked. Stock isn't terrible.. You can disable and hide bloatware.. But it would be really nice to have pie instead of soft buttons and restart and screen shot on the power menu
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Probably not, but you can get some of that functionality with root alone if you know how to mod systemui and stuff like that. Probably not the answer you're looking for but that's probably what it is...
Can always hope someone will Dev for it though
Sent from my XT907 using Tapatalk 4

sloosecannon said:
Probably not, but you can get some of that functionality with root alone if you know how to mod systemui and stuff like that. Probably not the answer you're looking for but that's probably what it is...
Can always hope someone will Dev for it though
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
I have no clue how to do those things. I got really spoiled on the dinc. So many people spoon feeding contributions to a fabulous device. It sure is a shame it's impossible to unlock my boot loader
Sent from my XT907 using xda app-developers app

everything I've run into *works*
but it all doesn't work so smoothly
Scrolling and everything is kind of choppy, I mean it is definitely livable, but still choppy.

netizenmt,
Thx a lot for your help. I`m now on cm10.2, too.
But there seemed to be some bugs.
1.I cannot install any apps from Google Play Store, or it hangs on the MOTO logo after reboot.
2.I can take calls, but cannot reach the 3G network.
P.S.When I try to use QPST to configure the phone, the QPST tells Serious error encountered, write to phone aborted.

I've installed CM10.2 two weeks ago and everything is working great! The first time I flashed it I got stuck at the CM boot animation... After ten minutes spent watching it I forced it to reboot: stuck again. At this point I booted back to recovery, followed thoroughly netizenmt instructions (wipe three times, really!!!), installed CM10.2, Installed gapps, installed supersu v1.43 and so on (follow all the steps netizenmt told us!)... Everithing worked fine then. At this point I changed build.props to make the phone works in GSM mode.

fargles said:
everything I've run into *works*
but it all doesn't work so smoothly
Scrolling and everything is kind of choppy, I mean it is definitely livable, but still choppy.
Click to expand...
Click to collapse
If you go to settings/developer options and scroll down to HW overlays. Check the box to disable HW overlays. That should help with the tearing/chopping.

Also, maps FC all over the place as soon as you're using GPS.
Sent from my XT907 using xda app-developers app

Stuck at google logo (bootloop) on 4.3-4.4 stock/ROMs

I searched all the internet and can't find any soliution to this.
Here are some examples (didn't find any of N4, but these are the same):
Some additional information:
It happens only on 4.3 or later (including 4.4 port) ROMs or stock OS.
It started when 4.3 came, i updated it officialy (my phone wasn't rooted/unlocked yet)
There were some times on 4.3 stock when it booted after half an hour, but I couldn't boot it again after next shutdown.
I can get to the recovery mode.
I tried to wipe everything, bring it back to factory state, but this thing still, happens. The only way I can use my phone is to have 4.2.2 ROMs/stock (I use cyanogenmod).
Any ideas on how to fix it?
EDIT: Solved by:
1. Flashing stock 4.2.2
2. Trying to officially update
3. Phone doesn't install the update, but goes to recovery instead?!?
4. Flashing official 4.3 with flash-all.bat

Man, you are lucky I saw this. This just happened to me today too and I freaked out. You need to download the radio from 4.2.2. Then manually fastboot install. Once you've done that everything works again and no more bootloop. I guess I accidentally wiped the firmware when installing 4.4. Anyways look for that and I promise you'll find it. I'll look for the post I found and post the link. I promise that's the issue.

I would recommend to download the toolkit and flash stock image. Make sure to backup all your files; it will wipe out everything.
Sent from my Nexus 4 using Tapatalk

nikeman513 said:
Man, you are lucky I saw this. This just happened to me today too and I freaked out. You need to download the radio from 4.2.2. Then manually fastboot install. Once you've done that everything works again and no more bootloop. I guess I accidentally wiped the firmware when installing 4.4. Anyways look for that and I promise you'll find it. I'll look for the post I found and post the link. I promise that's the issue.
Click to expand...
Click to collapse
Nope, doesn't work

badboy47 said:
I would recommend to download the toolkit and flash stock image. Make sure to backup all your files; it will wipe out everything.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
This one doesn't work too

00Justas said:
This one doesn't work too
Click to expand...
Click to collapse
Does your baseband show "Unknown" in the phone settings?
I had the same problem some weeks ago. Fixed it by flashing the stock 4.3 image again and again. The 3rd time it worked.

Here is a photo of my Fastboot screen :crying:
https://www.dropbox.com/s/p5xdyftiv9ua0c3/IMG_20131103_223244.jpg
abaaaabbbb63 said:
Does your baseband show "Unknown" in the phone settings?
I had the same problem some weeks ago. Fixed it by flashing the stock 4.3 image again and again. The 3rd time it worked.
Click to expand...
Click to collapse
Hello,
thahts My first post/replay but i hope it will be fine.
I have the same problem for 2 day's now.
My baseband is: M9615A-CEFWMAZM-2.0.1700.84
I've flashed the stock 4.2.2 and 4.3 with Wug's toolkit http://forum.xda-developers.com/showthread.php?t=2015469&page=94 sevral time's and it did't work
Now i'm stuck on the X logo after Google boot...
Any idea's how to get Nexus back to work ???

!!!!!! I DID IT !!!!!! :victory::victory::victory:
I just got to work My Nexus after following this steps: http://forum.xda-developers.com/showthread.php?t=2010312
IMPORTENT - please follow the instructions writen in RED color as a NOTE after flashing stock. It starts like that: "Note that some users indicate that they can't get past the X on boot...."
PS
Now back to customizing My Nexus
barteekn said:
Here is a photo of my Fastboot screen :crying:
https://www.dropbox.com/s/p5xdyftiv9ua0c3/IMG_20131103_223244.jpg
Hello,
thahts My first post/replay but i hope it will be fine.
I have the same problem for 2 day's now.
My baseband is: M9615A-CEFWMAZM-2.0.1700.84
I've flashed the stock 4.2.2 and 4.3 with Wug's toolkit http://forum.xda-developers.com/showthread.php?t=2015469&page=94 sevral time's and it did't work
Now i'm stuck on the X logo after Google boot...
Any idea's how to get Nexus back to work ???
Click to expand...
Click to collapse

use the guide "ubrick your nexus 4 as long you can get in the bootloader" it reformats everything in download mode or something like dat.

abaaaabbbb63 said:
Does your baseband show "Unknown" in the phone settings?
I had the same problem some weeks ago. Fixed it by flashing the stock 4.3 image again and again. The 3rd time it worked.
Click to expand...
Click to collapse
No, it shows the one I flash. Did you flash using flash-all.bat or in recovery or using adb, and which one jwr666y or jwr66v?

00Justas said:
Did you flash using flash-all.bat or in recovery or using adb?
Click to expand...
Click to collapse
Flash-all.bat. The other way is through Fastboot. You can't install images through adb or recovery directly.

opssemnik said:
use the guide "ubrick your nexus 4 as long you can get in the bootloader" it reformats everything in download mode or something like dat.
Click to expand...
Click to collapse
If you are talking about this, tried, didn't work.

abaaaabbbb63 said:
Flash-all.bat. The other way is through Fastboot. You can't install images through adb or recovery directly.
Click to expand...
Click to collapse
After many re-installs still not working...
EDIT: Working