Hi,
i love this verizon version sumsung s3 so far. Yesturday i flashed my phone to cm9. I followed the steps on ROOTZWIKI
but data is not working. Do any one have same issue. I tried re-flashing it with the same steps but no luck.
Thanks
/bin/ said:
Hi,
i love this verizon version sumsung s3 so far. Yesturday i flashed my phone to cm9. I followed the steps on ROOTZWIKI
but data is not working. Do any one have same issue. I tried re-flashing it with the same steps but no luck.
Thanks
Click to expand...
Click to collapse
Check your IMEI... You may need a replacement or need to get it fixed at a Verizon store.
did you backup your imei prior to flashing?
droidstyle said:
did you backup your imei prior to flashing?
Click to expand...
Click to collapse
No.
Can i go back to stock root? will that help?
Do you need to back it up before flashing any rom?
Sent from my SCH-I535 using xda app-developers app
matt0715 said:
Do you need to back it up before flashing any rom?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
you should back it up before doing any flashing at all!
Ouch! That's gonna hurt. Backup backup backup...repeat.
ouch 600 dollar mistakes suck. thanks for leading a lesson for me...
bigmook said:
ouch 600 dollar mistakes suck. thanks for leading a lesson for me...
Click to expand...
Click to collapse
Check "About phone" -> "Status" -> "IMEI" if that is 0 then more than likely your screwed. Return it to complete stock and take it to Verizon and play dumb. I got a new phone when this happened to me.
vader699 said:
Check "About phone" -> "Status" -> "IMEI" if that is 0 then more than likely your screwed. Return it to complete stock and take it to Verizon and play dumb. I got a new phone when this happened to me.
Click to expand...
Click to collapse
Thus why verizon encrypted the bootloader in the first ****ing place!
I'll point the finger at you, at this point but I'll also add that if the **** was unlocked, they wouldn't get so many phones back from people who ****ed them up in the first place as it would be easier to fix.
Both a-d'em things is lame.
ancashion said:
Thus why verizon encrypted the bootloader in the first ****ing place!
I'll point the finger at you, at this point but I'll also add that if the **** was unlocked, they wouldn't get so many phones back from people who ****ed them up in the first place as it would be easier to fix.
Both a-d'em things is lame.
Click to expand...
Click to collapse
The same thing happens on ATT, Tmobile, Rogers, etc.. all which are unlocked bootloaders. Read and understand the risk before you flash. I'm on phone #2 after hosing my IMEI.
ancashion said:
Thus why verizon encrypted the bootloader in the first ****ing place!
I'll point the finger at you, at this point but I'll also add that if the **** was unlocked, they wouldn't get so many phones back from people who ****ed them up in the first place as it would be easier to fix.
Both a-d'em things is lame.
Click to expand...
Click to collapse
this problem has nothing to do with locked bootloaders...do some research and quit spewing out repeated internet hearsay! The lost imei is happening to ALL US variant gs3's, as already mentioned.
droidstyle said:
this problem has nothing to do with locked bootloaders...do some research and quit spewing out repeated internet hearsay! The lost imei is happening to ALL US variant gs3's, as already mentioned.
Click to expand...
Click to collapse
The IMEI # gets lost with absolutely zero interaction? No swapping Roms? No "hacking?" It just.. disappears? Reboot the phone and poof- it's gone? Wake up one morning and no IMEI. Dead phone - completely random? Could happen to me on my way to the grocery store kinda thing?
Cause.. it kinda sounds like a tripwire to me.
My apologies if I am wrong.
Related
hi, i had a rooted and unlocked nexus s, and i tried to unroot it to stock. but when i was doing this, i somehow erased my IMEI number,
am i screwed or is there anyway to get this back? help pleeease
LightsCameraAction said:
hi, i had a rooted and unlocked nexus s, and i tried to unroot it to stock. but when i was doing this, i somehow erased my IMEI number,
am i screwed or is there anyway to get this back? help pleeease
Click to expand...
Click to collapse
First of all: Wrong section
Second: Yes you are screwed, your best bet would be to send it in for repair.
This is why you back up your efs folder before doing anything potentially dangerous.
Your IMEI is on your box.
Wrong section....fail
Return to stock....fail.
You are on a roll!
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
Wrong section....fail
Return to stock....fail.
You are on a roll!
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
seriously very wrong, but I cant help but giggle.
I understand the guy posting here though, he's freaking out and the Q&A section is a veritable graveyard of knowledgeable people lol. Just a bunch of us screaming help with no answers from above, sort of like Dante's Hell.
tevil said:
seriously very wrong, but I cant help but giggle.
I understand the guy posting here though, he's freaking out and the Q&A section is a veritable graveyard of knowledgeable people lol. Just a bunch of us screaming help with no answers from above, sort of like Dante's Hell.
Click to expand...
Click to collapse
He still got his answer though
Wrong section! But yes, this is strange. Somehow my phone has same weakness. Few times I went back to rooted stock, and every time I've tried to root it, my EFS folder got wiped. I was trying to figure out which ROM did that, but it was never ROM, it was root process somehow :S...
but why do you keep rooting? All you need to do is install loader and then use pre rooted roms.
Because I wanted to try that option, to wipe completely and flash all stock rooted. I did that two times with no luck... Every time my EFS folder got wiped and rebuild :S...
Tenhi said:
Because I wanted to try that option, to wipe completely and flash all stock rooted. I did that two times with no luck... Every time my EFS folder got wiped and rebuild :S...
Click to expand...
Click to collapse
That's not very good. Good to know though. Whose root app are you using?
Sent from my Nexus S using xda premium
LightsCameraAction said:
hi, i had a rooted and unlocked nexus s, and i tried to unroot it to stock. but when i was doing this, i somehow erased my IMEI number,
am i screwed or is there anyway to get this back? help pleeease
Click to expand...
Click to collapse
if you can find from anyone an efs backup zip with his/her imei number. and search with an hex editor or something like that. and replace your imei number into the file and flash it from recovery back.
it's just a supposition.
MYPaT said:
if you can find from anyone an efs backup zip with his/her imei number. and search with an hex editor or something like that. and replace your imei number into the file and flash it from recovery back.
it's just a supposition.
Click to expand...
Click to collapse
You can't just replace IMEI, because that file is encrypted. Already tried that ...
Hey guys,
So I have the Galaxy S2 Skyrocket with AT&T and I have it rooted etc. Today I tried flashing the MIUI rom, but was unsuccessful due to a message saying "Installation aborted". So I did as I read to do and wiped cache, Delvik or w/e, and then I reformatted the SDcard to redownload the ROM, however when I rebooted the next time it did not boot back up. Now I have the phone completely dead it would seem, I have tried the button combinations, etc to no avail.
What happened and is there anything I can do?
How can my phone be bricked if I never got to install a new ROM? I can't be without it for too long so any answers would be appreciated
Thanks,
Smernst
When you say button combinations are you saying you tried to get into download mode?
Sent from my SAMSUNG-SGH-I727
Sheolrock said:
When you say button combinations are you saying you tried to get into download mode?
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Yes, exactly that
Smernst said:
Yes, exactly that
Click to expand...
Click to collapse
Sometimes download mode can work even if the screen isn't turning on. You should follow the instructions for download mode and see if Odin recognizes the phone.
Sent from my SAMSUNG-SGH-I727
Well there are symptoms of Brick See below and find ur category!!!!
appdroid said:
Brick → When used in reference to consumer electronics, "brick" describes a device that cannot function in any capacity (such as a device with damaged firmware). This usage derives from the fact that some electronic devices (and their detachable power supplies) are vaguely brick-shaped, and so those which do not function are useful only as actual bricks. The term can also be used as a verb. For example, "I bricked my phone when I tried to modify its firmware.
Hard Brick → When your phone does not turn on at all. When you can’t get in to CWR/CWM Or Stock recovery. You are basically screwed. If its hard brick Here is thread that will help you!!!
Soft Brick → When your phone bootloops. When you can get into CWR/CWM. When You can use jigtag to get into download mode.
Click to expand...
Click to collapse
Smernst said:
Yes, exactly that
Click to expand...
Click to collapse
appdroid said:
Well there are symptoms of Brick See below and find ur category!!!!
Click to expand...
Click to collapse
UPDATE:
I just went in to the AT&T store and they are sending me a new phone tonight and it should be here tomorrow!
Now, does anyone have a guide to recommend for getting, say, MIUI onto the Samsung Galaxy S2 Skyrocket? I don't know enough about the versions, mp5, etc to do it alone, and a safe guide would really help me
Thanks
MIUI rite now is not daily driver has lots of bugs and Here is link scroll down it will give you step by step instructions.
Smernst said:
UPDATE:
I just went in to the AT&T store and they are sending me a new phone tonight and it should be here tomorrow!
Now, does anyone have a guide to recommend for getting, say, MIUI onto the Samsung Galaxy S2 Skyrocket? I don't know enough about the versions, mp5, etc to do it alone, and a safe guide would really help me
Thanks
Click to expand...
Click to collapse
Got it, thanks
Also, if my phone is truly hard-bricked the AT&T guys that I return it to will not be able to tell that it is rooted will they?
Thanks
No att ppl are dumb and they can't even turn on the phone so they won't be able to say that it was rooted. When they ask you anything about rooting just pretend like you don't know what they are talking about.
Smernst said:
Got it, thanks
Also, if my phone is truly hard-bricked the AT&T guys that I return it to will not be able to tell that it is rooted will they?
Thanks
Click to expand...
Click to collapse
appdroid said:
No att ppl are dumb and they can't even turn on the phone so they won't be able to say that it was rooted. When they ask you anything about rooting just pretend like you don't know what they are talking about.
Click to expand...
Click to collapse
Okay sweet thank you for all the help!
See you around
Smernst
Hope next phone doesn't give you any grief.
Sent from my SAMSUNG-SGH-I727 using xda premium
Hey guys.....
I tried flashing IceColdJelly on my HTC One X ATT and i was rushing and i just remembered a notice before i rebooted the phone that it says there was no OS something something to this rom and i clicked OK and it attempted to reboot. Now its not turning on at all. Cannot get into download mode or ANYTHING. Don't tell me to try pressing any more buttons because i've been doing that for the past 3 hours. I know my way around phones and this is my biggest problem i've ever faced. I put in the phone to the computer and it recognizes it but has 3 beeps after basically cannot do anything to the phone. I have TWRP recovery on it btw. Basically, its a paperweight. Cannot turn on a single freaking thing. Please help. I cannot thank you guys enough if you can help in any way....
Thanks.
Andrew10567 said:
Hey guys.....
I tried flashing IceColdJelly on my HTC One X ATT and i was rushing and i just remembered a notice before i rebooted the phone that it says there was no OS something something to this rom and i clicked OK and it attempted to reboot. Now its not turning on at all. Cannot get into download mode or ANYTHING. Don't tell me to try pressing any more buttons because i've been doing that for the past 3 hours. I know my way around phones and this is my biggest problem i've ever faced. I put in the phone to the computer and it recognizes it but has 3 beeps after basically cannot do anything to the phone. I have TWRP recovery on it btw. Basically, its a paperweight. Cannot turn on a single freaking thing. Please help. I cannot thank you guys enough if you can help in any way....
Thanks.
Click to expand...
Click to collapse
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck
tactical kitten said:
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck
Click to expand...
Click to collapse
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Andrew10567 said:
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Don't panic.right now there is no solution.There will be one soon.
GOOD LUCK
Wrong section ...... And not to be a **** the but hahaha people really need to Stop and read
Sent from my Nexus 7 using Tapatalk 2
Andrew10567 said:
Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Taking the time to research before flashing a ROM that is not even meant for your phone would have saved a lot of heartache:
http://forum.xda-developers.com/showthread.php?t=1974101
I thought the ICJ Bricking Crew was no more. I guess those clowns are trying to make a comeback.
tactical kitten said:
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck
Click to expand...
Click to collapse
I have downgraded using JET from 1.14 to 2.20. Process includes bricking your phone to get into special recovery mode that give RW access to hboot, but you do need TWRP at some point I think (not sure though) to get in bricked, before you start downgrade, so you might not be able to downgrade.
However, I don't think you are SOL. Look into manual steps of downgrading here: http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107
OP gives you there way to verify that device is connected and part of the steps is listing partitions. If you can get partitions listed on your PC, then I think you can just dd system image and it should come back to life... also have you tried 2.20 RUU? I had a corrupted system partition (bad sector causing reboot when I would try to access system - including booting phone or into twrp recovery). I ended up using RUU (which also failed from the same bug, but It actually reformatted my system partition giving me access to twrp and then I was able to restore).
http://www.youtube.com/watch?v=wwleOote5M0&feature=youtube_gdata_player
Sent from my HTC One XL using Tapatalk 2
Andrew10567 said:
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Lol. wow kid.
Sent from my HTC One XL
rpomponio said:
http://www.youtube.com/watch?v=wwleOote5M0&feature=youtube_gdata_player
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
It hurts to laugh so hard.
igagnidz said:
However, I don't think you are SOL. Look into manual steps of downgrading here: http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107
Click to expand...
Click to collapse
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.
iElvis said:
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.
Click to expand...
Click to collapse
If there is no ROM loaded onto the phone, as in doing a full /system wipe, the asserts will not work.
The assert that's being flashed looks at the build.prop that's already loaded onto the phone.
Sent from my One X using xda premium
Myrder said:
If there is no ROM loaded onto the phone, as in doing a full /system wipe, the asserts will not work.
The assert that's being flashed looks at the build.prop that's already loaded onto the phone.
Click to expand...
Click to collapse
And of course, it's good practice to wipe /system when changing roms. I didn't think of that. That's obviously why people are still getting in trouble.
iElvis said:
And of course, it's good practice to wipe /system when changing roms. I didn't think of that. That's obviously why people are still getting in trouble.
Click to expand...
Click to collapse
I don't ever wipe /system when flashing ROMs. It gets wiped when you flash anyway. I always wipe user data (factor reset), Dalvik and cache. But that's it.
iElvis said:
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.
Click to expand...
Click to collapse
Yep, if you format /system, the build.prop is gone, and the assert looks to the build.prop.. why it flashes, I don't know.
The way its set up seems like it would only flash if "ro.device=endeavoru" or whatever the line is, is present. I guess there is no fail safe to stop the process if the build.prop isn't present
Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.
Andrew10567 said:
Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.
Click to expand...
Click to collapse
They do and you're not the first to ask. I think they just swap up the motherboard.
Andrew10567 said:
Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.
Click to expand...
Click to collapse
They can fix any software corruption they have the tools too they know their phones front to back and can rewrite anything to them...just tell them what happened and they'll tell you the cost( maybe they'll feel bad and give a nice price) honesty can get you in good places sometimes
Thanks. Will send everyone who replied a thank button. Regardless of what type of comment...... I'll need to check the cost. Hopefully its below 100....
okay i upgraded to 4.3 OTA and tried to revert back and soft bricked my phone. I still have access to download mode and the stock recovery. I know now that i can not revert but is there any way of getting it back to 4.3 so i can have a phone again?
thanks for the future help.
This is similar what happened to me. I have never done anything with my phone as far as rooting and I tried reverting to stock 4.1.2. In Odin I kept getting the "Nand Start! Fail (Auth)" because of the locked bootloader I guess. I flashed some other firmware that was unofficial with the locked bootloader and now I get the "unauthorized software detected" and I cant do anything but enter Odin download mode. What should I do?
that is exactly what is happing to me. same error and all.
Once you took the OTA 4.3 you got locked in. No way of going back.
Sent from my SCH-I535 using Tapatalk
I dont want to go back just get rid of the soft brick so i can use it
im having the same problem and need to get it fixed please help anyone???!!!! im leaving for florida in two days and have nothing else. HELP!!!!
If you took the OTA and tried to flash 4.1.2 Odin or unlock bootloader you are Hard bricked , no method or recovering it yet.
If you have stock recovery and download mode , only hope is wait for 4.3 .tar file
Theres no custom recovery I can flash and flash some other software or something?
Elemt said:
Theres no custom recovery I can flash and flash some other software or something?
Click to expand...
Click to collapse
Nope , once you take 4.3 OTA you done , no flashing anything. And once you try to flash recovery or revert to older software you are bricked.
Sorry to be the bear of bad news.
There is a full thread of why and how so many devices have been bricked
http://forum.xda-developers.com/showthread.php?t=2575661
jlyle said:
Nope , once you take 4.3 OTA you done , no flashing anything. And once you try to flash recovery or revert to older software you are bricked.
Sorry to be the bear of bad news.
There is a full thread of why and how so many devices have been bricked
http://forum.xda-developers.com/showthread.php?t=2575661
Click to expand...
Click to collapse
Do you know if anyone is working on a fix? or a .tar file of 4.3?
dvdavid2 said:
Do you know if anyone is working on a fix? or a .tar file of 4.3?
Click to expand...
Click to collapse
Thanks for the info. hopefully a fix will be done soon. And do you know how i should keep to see when the work around is finished .
thanks in advanced guys.
This might give you a chance to unbrick.... possibly
http://forum.xda-developers.com/showthread.php?t=2581166
I got the "unauthorised software detected" on my phone like 3 days ago from messing up on a recovery and all I did was go into the Verizon store and said idk what happened and they called technical support and they asked me if I flashed software on my phone and I just said "no, I just plugged it into my laptop and it did this" so they said they will just send me a new sgs3 and I just got it today.
Pretty simple.
And I don't have insurance .
Hit thanks if I helped
Sent from my SCH-I535 using xda app-developers app
ScubaSteev said:
I got the "unauthorised software detected" on my phone like 3 days ago from messing up on a recovery and all I did was go into the Verizon store and said idk what happened and they called technical support and they asked me if I flashed software on my phone and I just said "no, I just plugged it into my laptop and it did this" so they said they will just send me a new sgs3 and I just got it today.
Pretty simple.
And I don't have insurance .
Hit thanks if I helped
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app
jlyle said:
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Any break throughs????
dvdavid2 said:
Any break throughs????
Click to expand...
Click to collapse
None that I have seen
Sent from my SCH-I535 using xda app-developers app
jlyle said:
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Not to mention it is basically fraud, and is the main reason Verizon decided to start locking down phones in the first place.
I understand everyone is taking risks when flashing custom, and flashes can go wrong even when you do everything right, but there is VERY little chance of bricking your phone if you take your time and do a bit of research before you hit any buttons. And if you do manage to brick your phone, man up and pay for a new phone or pay for it to be fixed. Otherwise stop treating your $600 piece of technology like a toy.
BattsNotIncld said:
Not to mention it is basically fraud, and is the main reason Verizon decided to start locking down phones in the first place.
I understand everyone is taking risks when flashing custom, and flashes can go wrong even when you do everything right, but there is VERY little chance of bricking your phone if you take your time and do a bit of research before you hit any buttons. And if you do manage to brick your phone, man up and pay for a new phone or pay for it to be fixed. Otherwise stop treating your $600 piece of technology like a toy.
Click to expand...
Click to collapse
The first time I ever rooted, I was worried about bricking. So i read everything I could find relevant.
Why in the world anyone would flash without reading is beyond me. Every single thread in Verizon Galaxy S3 at least mentions, if not totally devoted, to how bad 4.3 is and if you flash something on it you will brick.
I just don't get it.
Sent from my Last Ever Samsung Device.
If you do a battery pull and start back up in download mode (might take a couple of times to get it to work) then use the Verizon software upgrade assistant it should fix it but you will be stuck with 4.3. Worked for me
So i bought me a new used nexus 5 on craigslist from some old chinese guy. He said it wasn't connecting to a network no matter what or whose sim cards he used and how many times he rooted it. the phone is on stock unrooted 4.4.2. I got it on the cheap and was hoping ot fix it up and use it. Any idea what might be wrong with it?
butthurtlocker said:
So i bought me a new used nexus 5 on craigslist from some old chinese guy. He said it wasn't connecting to a network no matter what or whose sim cards he used and how many times he rooted it. the phone is on stock unrooted 4.4.2. I got it on the cheap and was hoping ot fix it up and use it. Any idea what might be wrong with it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2601997
Sounds like the old Chinese guy knew what he was doing.
You don't mention that YOU returned it to stock, you just said it was stock and unrooted. If it is exactly the way he gave it to you I would fastboot flash the stock 4.4.2 images from google and see what that does for you. You could simply have a corrupted file somewhere.
thionylx said:
You don't mention that YOU returned it to stock, you just said it was stock and unrooted. If it is exactly the way he gave it to you I would fastboot flash the stock 4.4.2 images from google and see what that does for you. You could simply have a corrupted file somewhere.
Click to expand...
Click to collapse
Yes when he sold it to me it was stock. I haven't returned it to stock, ive rooted it and tried diff rom/basebad combos and still nothing. Theres also a weird persistent notification that i cant swipe away that says Nework (ROGERS) Unvailable....even when i reset and try a Telus sim! Is there an easier way to flash stock besides fastboot? I am pretty new to this gig and am not too comfortable with fastboot
butthurtlocker said:
Yes when he sold it to me it was stock. I haven't returned it to stock, ive rooted it and tried diff rom/basebad combos and still nothing. Theres also a weird persistent notification that i cant swipe away that says Nework (ROGERS) Unvailable....even when i reset and try a Telus sim! Is there an easier way to flash stock besides fastboot? I am pretty new to this gig and am not too comfortable with fastboot
Click to expand...
Click to collapse
This being a Nexus you have little or no risk of doing damage by playing around. My original Droid X was always threatening to self destruct if you messed up the tiniest little step. Spending a couple hours learning about and installing Fastboot and ADB will be the best investment you can make. Once you learn to use them the fear of messing something up is gone. You can flash roms at will without worry as you can always return to stock and start over.
Flash a Google stock image
Sent from my Nexus 5 using Tapatalk
---------- Post added at 08:15 PM ---------- Previous post was at 08:14 PM ----------
All nexus 5 regardless of carrier should be unlocked
Sent from my Nexus 5 using Tapatalk
butthurtlocker said:
Yes when he sold it to me it was stock. I haven't returned it to stock, ive rooted it and tried diff rom/basebad combos and still nothing. Theres also a weird persistent notification that i cant swipe away that says Nework (ROGERS) Unvailable....even when i reset and try a Telus sim! Is there an easier way to flash stock besides fastboot? I am pretty new to this gig and am not too comfortable with fastboot
Click to expand...
Click to collapse
Just follow method one of this. It's easy http://forum.xda-developers.com/showthread.php?p=47156064
PS, why did you buy a device thinking you could fix it of you don't know fastboot commands
thionylx said:
This being a Nexus you have little or no risk of doing damage by playing around. My original Droid X was always threatening to self destruct if you messed up the tiniest little step. Spending a couple hours learning about and installing Fastboot and ADB will be the best investment you can make. Once you learn to use them the fear of messing something up is gone. You can flash roms at will without worry as you can always return to stock and start over.
Click to expand...
Click to collapse
Thanks man thats a good point!
jd1639 said:
Just follow method one of this. It's easy http://forum.xda-developers.com/showthread.php?p=47156064
PS, why did you buy a device thinking you could fix it of you don't know fastboot commands
Click to expand...
Click to collapse
Oh thats perfect bro thanks, nice and straightforward. Will see how this goes after school. I just htought it was maybe a radio issue or rom issue so i thought i could flash around and fix it. Also it was only 70 bucks and in mint condition aside from this problem so I didn't think it was a bad deal
Sounds like the ESN/IMEI is bad.
Hard to fix ATM.
Sent from my Nexus 5 using Tapatalk
Dragn4rce said:
Sounds like the ESN/IMEI is bad.
Hard to fix ATM.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oh really?how does that happen!? The imei isn't blacklisted or anything and shows up as a registered imei. I tried flashing stock image and still no dice! Looks like I'm doomed. Any other suggestions?
That usually happens when the following steps occur.
The original owner unlocked bootloader.
They put twrp on it and did a full backup including ESN
The device developed a fault so they RMA'd it.
They restored the backup from the faulty device into the new one.
The ESN is device specific and by restoring it onto a different device you end up with not being able to connect to a network.
You can check by going into the about phone menu in the settings. If it displays your imei then I don't think this is your problem.
Have you tried popping the back cover off and checking the antennae contacts
Sent from my Nexus 4 using xda app-developers app
The good news is the parts are worth more than the $70 you paid for it. Find someone with a busted screen and sell it.
jd1639 said:
The good news is the parts are worth more than the $70 you paid for it. Find someone with a busted screen and sell it.
Click to expand...
Click to collapse
That's a good idea.
Thanks for the advice. Ended up selling it this morning as is to an eager repair junkie. Btw my imei was showing up and the antennas were all in place so still a mystery what was up with it!
Sent from my LG-G2 using xda app-developers app