Please Help i am stucked - T-Mobile, Samsung Galaxy SIII

I flashed T999_UVDMD5_firmware_v4.zip from this http://forum.xda-developers.com/showthread.php?t=2282603 and now i am unable to boot into recovery, my phone is dead i can't even go in downlaod mode.
thanks

samipsth said:
I flashed T999_UVDMD5_firmware_v4.zip from this http://forum.xda-developers.com/showthread.php?t=2282603 and now i am unable to boot into recovery, my phone is dead i can't even go in downlaod mode.
thanks
Click to expand...
Click to collapse
If the MD5 of the downloaded file matches the MD5 given in the thread, then you do not have a T999, and you bricked your phone. I would guess that you have the intl version. If that's the case, you are in the incorrect forum.

What can i do ?
Aerowinder said:
If the MD5 of the downloaded file matches the MD5 given in the thread, then you do not have a T999, and you bricked your phone. I would guess that you have the intl version. If that's the case, you are in the incorrect forum.
Click to expand...
Click to collapse
My phone model is SGH-T999 written in back. Is there any way to return back my phone.
thanks

samipsth said:
My phone model is SGH-T999 written in back. Is there any way to return back my phone.
thanks
Click to expand...
Click to collapse
That file is designed to not flash unless the checksums match the ones stored in the update script. I'm a little hesitant to link this thread without knowing what went wrong, but here: http://forum.xda-developers.com/showthread.php?t=2439367.

Aerowinder said:
That file is designed to not flash unless the checksums match the ones stored in the update script. I'm a little hesitant to link this thread without knowing what went wrong, but here: http://forum.xda-developers.com/showthread.php?t=2439367.
Click to expand...
Click to collapse
Actually i was trying to install cm10.1 and it was giving error. i couldn't flash stock firmware too it was giving sbl2 error so i went through this flashing in order to unlock bootloader but my fate....
If you have solution thanks...

samipsth said:
Actually i was trying to install cm10.1 and it was giving error. i couldn't flash stock firmware too it was giving sbl2 error so i went through this flashing in order to unlock bootloader but my fate....
If you have solution thanks...
Click to expand...
Click to collapse
Everything you have said so far leads me to believe you don't have a T999, but an I930x. In which case, you are in the wrong forum.

Aerowinder said:
Everything you have said so far leads me to believe you don't have a T999, but an I930x. In which case, you are in the wrong forum.
Click to expand...
Click to collapse
on the back its written sgh-t999
when it was on on about section it's model was sgh-i747. phone had no imie, no baseband so i went through this process

I agree with aerowinder, your posts all suggest it's not a T999, as that's what happens when you flash that firmware to a different model. Are you absolutely certain it does not say SGH-T999L?
If it says it's a T999, then your only chance is the thread he linked to a few posts back.
Our bootloader has never been locked btw....
Where did you get this phone?
Sent from my SGH-T999L using Tapatalk 4

Image of my phone
DocHoliday77 said:
I agree with aerowinder, your posts all suggest it's not a T999, as that's what happens when you flash that firmware to a different model. Are you absolutely certain it does not say SGH-T999L?
If it says it's a T999, then your only chance is the thread he linked to a few posts back.
Our bootloader has never been locked btw....
Where did you get this phone?
Sent from my SGH-T999L using Tapatalk 4
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is it see the picture
thanks

I had an issue with flashing back to stock after cm10.1 as well. Kept saying error but don't remember what it was specifically. But I finally got the backup to work after data format. Of course my backup was on sd card. Hope this hepl.
Sent from my SGH-T999 using XDA Premium 4 mobile app

Are you still unable to get into Recovery (Home + Volume Up + Power) or Download (Home + Volume Down + Power)?
If not, might have to be Jig'd

DJ_SpaRky said:
Are you still unable to get into Recovery (Home + Volume Up + Power) or Download (Home + Volume Down + Power)?
If not, might have to be Jig'd
Click to expand...
Click to collapse
I am still stucked any help will be appreciated.
thanks

samipsth said:
I am still stucked any help will be appreciated.
thanks
Click to expand...
Click to collapse
So, is that a Yes or a No to my question?
Also, what happens when you plug it into a computer via USB?

DJ_SpaRky said:
So, is that a Yes or a No to my question?
Also, what happens when you plug it into a computer via USB?
Click to expand...
Click to collapse
no i can't go into recovery or download mode
there is no response when i press power button
it shows connected as QHSUSB_DLOAD

Aerowinder said:
That file is designed to not flash unless the checksums match the ones stored in the update script. I'm a little hesitant to link this thread without knowing what went wrong, but here: http://forum.xda-developers.com/showthread.php?t=2439367.
Click to expand...
Click to collapse
samipsth said:
no i can't go into recovery or download mode
there is no response when i press power button
it shows connected as QHSUSB_DLOAD
Click to expand...
Click to collapse
Please read the thread that @Aerowinder mentioned.

DJ_SpaRky said:
Please read the thread that @Aerowinder mentioned.
Click to expand...
Click to collapse
I did as the link but my bad luck nothing happened
please any other help

samipsth said:
I did as the link but my bad luck nothing happened
please any other help
Click to expand...
Click to collapse
Try this video first listen carefully, http://www.youtube.com/watch?v=dU5H8NJ7vTM... do not download his debricked img file. Download one from this page http://forum.xda-developers.com/showthread.php?t=2345860. Your phones hardware may be a i747. I had the same problem , behind my battery says it's a I9300 and when I rooted for I9300 didn't work after 2 tries. Then I noticed when I plugged my phone in the usb it was looking for T999 drivers. So I just assumed it was t999 ... well, I ended up bricking the phone and I found that youtube video and presto, fixed. I use the img file for T999. If you think you have an I747 here is the download link http://d-h.st/iEy...do at you own risk. I don't think it matters anyway if your phone is already bricked. I just sayin it worked for me, it may also work for you. Good luck!

samipsth said:
I did as the link but my bad luck nothing happened
please any other help
Click to expand...
Click to collapse
Then there really is not anything else that we can do from here, you will need your phone Jig'd or some other Hard Brick fix.

Related

How to check if bootloader is locked or not?

Is there any code to type in to check?
I need to make sure I relocked it so I can give it back to where i bought it and buy the nexus 4
Thank you everyone who actually read it and maybe is gonna post.
Sorry for the stupid question.
Paulo
when you boot the phone up, do you see a lock that looks slightly opened?
or you can boot into fastboot mode and it will tell you if its locked or unlocked.
As above. You can also boot to bootloader (vol key in + power) it will indicate locked, or unlocked there as well.
Zepius said:
when you boot the phone up, do you see a lock that looks slightly opened?
or you can boot into fastboot mode and it will tell you if its locked or unlocked.
Click to expand...
Click to collapse
Lock doesnt show up.
Where do i check it in the fast boot ?
Lock state: locked
Is that it?
paulo111 said:
Lock doesnt show up.
Where do i check it in the fast boot ?
Lock state: locked
Is that it?
Click to expand...
Click to collapse
That's it.
The other poster was referring to this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
paulo111 said:
Lock doesnt show up.
Where do i check it in the fast boot ?
Lock state: locked
Is that it?
Click to expand...
Click to collapse
yes. you have a locked bootloader.
Also how can i change back to the original boot animation? I once changed it using a program that i removed.. will it get removed when i unroot the phone and factory resset it?
paulo111 said:
Also how can i change back to the original boot animation? I once changed it using a program that i removed.. will it get removed when i unroot the phone and factory resset it?
Click to expand...
Click to collapse
Factory reset will do exactly what it says. Might want to format the internal sd 3-7 times depending on how paranoid you are (NSA standard is being zeroed out 7 times).
063_XOBX said:
Factory reset will do exactly what it says. Might want to format the internal sd 3-7 times depending on how paranoid you are (NSA standard is being zeroed out 7 times).
Click to expand...
Click to collapse
How to you format internal sd card after unrooting and factory resseting?
Also you guys advice me to return this gnexus for 360€ and buy the lg nexus 4 for like 350€ online? it will have universal warranty so the warranty is no problem.
The same way you would format any media device.
Just do what you want. Asking other people for their advice won't get you what you want.
063_XOBX said:
The same way you would format any media device.
Just do what you want. Asking other people for their advice won't get you what you want.
Click to expand...
Click to collapse
May get tips on what is best to do no?
Do I have to unlock bootloader in order to unroot?
Do you know how to follow directions? I'm not trying to be rude but there is a sticky at the very top of the development section for your device that tells you everything you need to know.
063_XOBX said:
Do you know how to follow directions? I'm not trying to be rude but there is a sticky at the very top of the development section for your device that tells you everything you need to know.
Click to expand...
Click to collapse
Alright man sorry for that, i already unrooted the phone and locked bootloader. Also did factory resset, but the boot image is still not the default one, how can i change it to the normal one? Already did factory resset ..
lol, and still goes on.
paulo111 said:
Alright man sorry for that, i already unrooted the phone and locked bootloader. Also did factory resset, but the boot image is still not the default one, how can i change it to the normal one? Already did factory resset ..
Click to expand...
Click to collapse
Refer to this sticky, and you're done.
http://forum.xda-developers.com/showthread.php?t=1626895

[Q] N7100 Emergency Calls Only

Okay my phone has been working fine till now.
My IMEI is intact still displays *#06# the correct no. It has been unlocked. I have rooted installed a custom ROM all was working okay till yesterday. When I turn the phone on emergency calls only is displayed. When I try to make a call it pops up with not registered on network. My data works okay though so I know am not blacklisted. Has anybody got a fix. Been searching but can seem to find a solution. Please help.
you have a backup of your efs folder?
Try a data clear.
Make sure you already have a backup of efs.
Sent from my GT-N7100 using xda premium
UtkarshGupta said:
Try a data clear.
Make sure you already have a backup of efs.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I have tried it already. It's seems like my phine has locked itself in emergency mode and doesnt want to come out of it
Sent from my GT-I9305 using xda app-developers app
MrCeez said:
I have tried it already. It's seems like my phine has locked itself in emergency mode and doesnt want to come out of it
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Gonna have to bump this, since I have the same issue.
Phone was working fine until I tried this rom. Now every rom I try, including flashing stock using odin, leaves the phone as "emergency calls only". I've tried different modems etc, nothing.
Current baseband N71000NEDLK1.
Even flashing the proper UK 3 network stock rom, nothing.
Have you tried with another sim card? Maybe you have a damage sim.
zabumba said:
Have you tried with another sim card? Maybe you have a damage sim.
Click to expand...
Click to collapse
Ive tried my mrs' o2 card, same issue there.
It feels like a rom has changed everything, my modem even. I've tried to flash one recommended for Three UK, but it didn't seem to stick in recovery.
X82X said:
Ive tried my mrs' o2 card, same issue there.
It feels like a rom has changed everything, my modem even. I've tried to flash one recommended for Three UK, but it didn't seem to stick in recovery.
Click to expand...
Click to collapse
Try to restore the stock Firmware or a different custom rom
aukhan said:
Try to restore the stock Firmware or a different custom rom
Click to expand...
Click to collapse
I fear for the worst. I've read a few entries from people saying when this happened to them (some never rooted or on any custom rom) they had a paperweight.
I've tried about 6 different stock roms, many custom. Many modems. Nothing will get it working.
The phone has full signal, can scan for networks, but will not allow calls or connect to data.
I've tried the sim elsewhere and it's fine.
Since this is my only means of communication, I'm extra worried.
Any help on this matter, is greatly appreciated!
X82X said:
I fear for the worst. I've read a few entries from people saying when this happened to them (some never rooted or on any custom rom) they had a paperweight.
I've tried about 6 different stock roms, many custom. Many modems. Nothing will get it working.
The phone has full signal, can scan for networks, but will not allow calls or connect to data.
I've tried the sim elsewhere and it's fine.
Since this is my only means of communication, I'm extra worried.
Any help on this matter, is greatly appreciated!
Click to expand...
Click to collapse
Is your IMEI number intact as shown on the box ?
Which device is this i mean model ?
N7100 or N7105 or some other is this a Carrier specific device ?.
aukhan said:
Is your IMEI number intact as shown on the box ?
Which device is this i mean model ?
N7100 or N7105 or some other is this a Carrier specific device ?.
Click to expand...
Click to collapse
The IMEI is 004XXX010640000 / 01
Model N7100.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
X82X said:
The IMEI is 004XXX010640000 / 01
Model N7100.
Click to expand...
Click to collapse
Is IMEI matching on the box ?
aukhan said:
Is IMEI matching on the box ?
Click to expand...
Click to collapse
Sorry, I never had a box. My dad has been using it great for 6 months, I have it a day, stick a rom on it and boom. But I'm smelling something with the kernel. I changed the kernel and now there is no signal at all. I need to find the right one for this UK model.
I've got the same exact problem as well, my N7100 bought it from china ( not copy) and after install Hong Kong version of stock rom via Odin,I have the same exact problem.
1. I can search for all the available network.
2. Under settings-about-status, it shows my phone number, my carrier, HSDPA mode...all looks normal except "emergency call"
3. I tried calling the sim that was in the N7100 and text message, the line works,text message shows as delivered, but nothing turns up on the N7100.
I've tried custom,stock,per-rooted from many versions of the world but the problem is still there.
X82X said:
Sorry, I never had a box. My dad has been using it great for 6 months, I have it a day, stick a rom on it and boom. But I'm smelling something with the kernel. I changed the kernel and now there is no signal at all. I need to find the right one for this UK model.
Click to expand...
Click to collapse
i think your the victim of IMEI corrupt or EFS Folder corrupted
as the IMEI 004XXX010640000 / 01 this is what you posted it looks suspcious to me
pull the battery there is sticker match the IMEI showing on the sticker and from phone see it they matches if they dont they your in deep trouble where you may have to get it serviced
---------- Post added at 02:37 PM ---------- Previous post was at 02:36 PM ----------
pixellized said:
I've got the same exact problem as well, my N7100 bought it from china ( not copy) and after install Hong Kong version of stock rom via Odin,I have the same exact problem.
1. I can search for all the available network.
2. Under settings-about-status, it shows my phone number, my carrier, HSDPA mode...all looks normal except "emergency call"
3. I tried calling the sim that was in the N7100 and text message, the line works,text message shows as delivered, but nothing turns up on the N7100.
I've tried custom,stock,per-rooted from many versions of the world but the problem is still there.
Click to expand...
Click to collapse
suggest you to try this and check #15
aukhan said:
i think your the victim of IMEI corrupt or EFS Folder corrupted
as the IMEI 004XXX010640000 / 01 this is what you posted it looks suspcious to me
pull the battery there is sticker match the IMEI showing on the sticker and from phone see it they matches if they dont they your in deep trouble where you may have to get it serviced
Click to expand...
Click to collapse
Correct. The IMEI is totally different. But as I said, I am not going to fix it. I'll just sell it on cheap for someone else to. It's a shame and annoying that something like this can go wrong and potentially brick a phone. I know theres risks to all rooting/custom roms, which I accept, but it still doesn't stop it stinging when it does go wrong, which to my knowledge, wasn't my fault.
X82X said:
Correct. The IMEI is totally different. But as I said, I am not going to fix it. I'll just sell it on cheap for someone else to. It's a shame and annoying that something like this can go wrong and potentially brick a phone. I know theres risks to all rooting/custom roms, which I accept, but it still doesn't stop it stinging when it does go wrong, which to my knowledge, wasn't my fault.
Click to expand...
Click to collapse
always remember option number when rooting device always make a backup of Efs folder or backup you rom
aukhan said:
always remember option number when rooting device always make a backup of Efs folder or backup you rom
Click to expand...
Click to collapse
But, for me, the IMEI number is still the same as my original number,from the back of the phone sticker & also the box, could my phone's problem be any different?
pixellized said:
But, for me, the IMEI number is still the same as my original number,from the back of the phone sticker & also the box, could my phone's problem be any different?
Click to expand...
Click to collapse
First thing before you try anything else make a backup of EFS folder search for the thread you will find specific to Note 2.
then try to make a ROM backup
then Flash the stock Firmware see if this works.
X82X said:
Correct. The IMEI is totally different. But as I said, I am not going to fix it. I'll just sell it on cheap for someone else to. It's a shame and annoying that something like this can go wrong and potentially brick a phone. I know theres risks to all rooting/custom roms, which I accept, but it still doesn't stop it stinging when it does go wrong, which to my knowledge, wasn't my fault.
Click to expand...
Click to collapse
Don't be paniced mate. The problem is easy to solve. With a root explorer find the folder efs_Backup, location of the folder varies from rom to rom. If you are in a custom stock rom, you'll find it under sd card. It also may locate on root/media. Every time you flash a new rom the efs backed up automatically in zip. After finding the folder, open it, you'll find many zip files mentioned dates. Extract the one you remember when your phone was fine. Then copy the whole content of the extracted folder and paste to the root/efs.
Before pasting, erase the existing contents of the efs folder.
DONE!
Sent from my GT-N7100 using xda premium

EXE RUU VZW M7 4.4.3 S-on users

Here is a tested working EXE version of the last RUU for the the verizon m7 (4.4.3). This is NOT rooted but will restore a softbricked phone (even s-on/locked!!)
Download the following.
- https://www.androidfilehost.com/?fid=95784891001602579
Extract to folder. Double click ARUwizard.exe. Follow prompts. When complete phone will reboot.
If you aren't on the latest hboot or get an error try this..
flash the following zip in ruu mode...
- https://www.androidfilehost.com/?fid=95784891001602985
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_WL_K443_SENSE60_VZW_MR_VERIZON_WWE_Sign ed_Hboot.zip
fastboot reboot-bootloader
then try your RUU via the app
Before anyone asks yes i know it says M8. I am too lazy to change screen shots here.
Thanks @gerry8 for testing for me
Thanks @Sneakyghost for the fuu files
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dottat said:
Here is a tested working EXE version of the last RUU for the the verizon m7 (4.4.3). This is NOT rooted but will restore a softbricked phone (even s-on/locked!!)
Download the following.
https://www.androidfilehost.com/?fid=95784891001602579
Extract to folder. Double click ARUwizard.exe. Follow prompts. When complete phone will reboot.
Before anyone asks yes i know it says M8. I am too lazy to change screen shots here.
Thanks @gerry8 for testing for me
Click to expand...
Click to collapse
Yes ladies and gentelman this works flawless. @dottat made it possible. I was dead in the water since feb and he did not give up. Now i have my m7 back in service. Root is next
@tflogic did you give it a try?
I'll give it a try in the morning and let you know how it goes. Been out and about all day.
Crossing my fingers!
tflogic said:
I'll give it a try in the morning and let you know how it goes. Been out and about all day.
Crossing my fingers!
Click to expand...
Click to collapse
Gerry had been on a custom Rom too..this tool simply doesn't care ?
@jman036 have you tried this yet?
pmterp said:
@jman036 have you tried this yet?
Click to expand...
Click to collapse
I'm downloading it now and I will see how it works! Thank you.
pmterp said:
@jman036 have you tried this yet?
Click to expand...
Click to collapse
Thanks...was trying to remember everyone who was locked out. For Gerry8....I've been talking to him since the beginning of the year so he was easy to remember.
The img show M8. but this is the M7 thread.
synisterwolf said:
The img show M8. but this is the M7 thread.
Click to expand...
Click to collapse
If i could draw a line to the op from your post I would.
Or were you just being funny? ?
I do get sarcasm...lol
dottat said:
If i could draw a line to the op from your post I would.
Or were you just being funny? ?
I do get sarcasm...lol
Click to expand...
Click to collapse
Tiny phone screen. my bad. ignore my post.
synisterwolf said:
Tiny phone screen. my bad. ignore my post.
Click to expand...
Click to collapse
Looks good on my t6
dottat said:
@tflogic did you give it a try?
Click to expand...
Click to collapse
Just got home and had the chance to run this. Everything worked out good! No tampered flag and running the stock Verizon ROM. Thanks again for all of your help dottat!
tflogic said:
Just got home and had the chance to run this. Everything worked out good! No tampered flag and running the stock Verizon ROM. Thanks again for all of your help dottat!
Click to expand...
Click to collapse
Schweet.
pmterp said:
@jman036 have you tried this yet?
Click to expand...
Click to collapse
I tried but it stayed at 3% saying checking header. Been that way for about 2 hours so I stopped it.
jman036 said:
I tried but it stayed at 3% saying checking header. Been that way for about 2 hours so I stopped it.
Click to expand...
Click to collapse
Did you try it on a fresh reboot of your pc? It doesn't take that long.
jman036 said:
I tried but it stayed at 3% saying checking header. Been that way for about 2 hours so I stopped it.
Click to expand...
Click to collapse
Actually....what firmware were you on? If older..
flash the following zip in ruu mode...
https://www.androidfilehost.com/?fid=95784891001602985
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_WL_K443_SENSE60_VZW_MR_VERIZON_WWE_Signed_Hboot.zip
fastboot reboot-bootloader
then try your RUU via the app
Dottat ,U have just solved the age old problem I've been facing of how imma get back 2 stock if I decide to ota for 5.0 ... I'm currently s off unlocked bootloader, and 2 many mods to remember,but thank u seriously for everything you've done for the m7 community
I'm a little confused.. I haven't messed with this stuff in almost a year so I've forgotten a lot....
My phone was just s-off, rooted, nusense rom. I restored my old backup in twrp to remove nusense. Will this finish returning my phone to stock? Or is this just a fix for the guys who got stuck in the middle of the process? (linked here from the other s-on thread in general discussion)
clarification: phone is still s-off and rooted with twrp recovery. I only removed nusense so far.
RitzCracker said:
I'm a little confused.. I haven't messed with this stuff in almost a year so I've forgotten a lot....
My phone was just s-off, rooted, nusense rom. I restored my old backup in twrp to remove nusense. Will this finish returning my phone to stock? Or is this just a fix for the guys who got stuck in the middle of the process? (linked here from the other s-on thread in general discussion)
Click to expand...
Click to collapse
This will leave you 100% stock. Recovery included. If you are s on and want to go stock and root you will need to flash this...then fastboot flash the recovery of your choosing and then flash supersu zip of choosing in your custom recovery.

Phone SIM card issue after Firmware change.

I am having problems with my phone recognizing my SIM.
To give some background, I soft bricked my phone flashing a different firmware, trying to go to GPE. I got the phone back to stock with RUU, re-unlocked bootloader and I am also S-Off. I flashed the MIUI Rom and it could not recognize my SIM, so I flashed Tasks ROM and the same problem. I then flashed this radio “1.16.21331931.LA11G_20.31A.4145.02L http://d-h.st/NUa | Thanks cruzin_cruzing!” found here: http://forum.xda-developers.com/showthread.php?t=2736921. That did not fix the issue.
When I type *#06# to see my IMEI nothing shows up, but when I look up my IMEI in fastboot using “fastboot oem readimei” it shows the correct IMEI. Does this have something to do with the issue?
Any help on this would be great, I have hit a wall doing everything I know to do.
JON123123 said:
I am having problems with my phone recognizing my SIM.
To give some background, I soft bricked my phone flashing a different firmware, trying to go to GPE. I got the phone back to stock with RUU, re-unlocked bootloader and I am also S-Off. I flashed the MIUI Rom and it could not recognize my SIM, so I flashed Tasks ROM and the same problem. I then flashed this radio “1.16.21331931.LA11G_20.31A.4145.02L http://d-h.st/NUa | Thanks cruzin_cruzing!” found here: http://forum.xda-developers.com/showthread.php?t=2736921. That did not fix the issue.
When I type *#06# to see my IMEI nothing shows up, but when I look up my IMEI in fastboot using “fastboot oem readimei” it shows the correct IMEI. Does this have something to do with the issue?
Any help on this would be great, I have hit a wall doing everything I know to do.
Click to expand...
Click to collapse
I had kind of the same problem. I went to Settings -> Data -> Network -> Choose network automaticly.
After the phone was registred on the network againg, the problem was gone.
jkolner said:
I had kind of the same problem. I went to Settings -> Data -> Network -> Choose network automaticly.
After the phone was registred on the network againg, the problem was gone.
Click to expand...
Click to collapse
This did not work, it was not able to find a network. Also, I forgot to say that my phone will not let me add new APNs.
JON123123 said:
I am having problems with my phone recognizing my SIM.
To give some background, I soft bricked my phone flashing a different firmware, trying to go to GPE. I got the phone back to stock with RUU, re-unlocked bootloader and I am also S-Off. I flashed the MIUI Rom and it could not recognize my SIM, so I flashed Tasks ROM and the same problem. I then flashed this radio “1.16.21331931.LA11G_20.31A.4145.02L http://d-h.st/NUa | Thanks cruzin_cruzing!” found here: http://forum.xda-developers.com/showthread.php?t=2736921. That did not fix the issue.
When I type *#06# to see my IMEI nothing shows up, but when I look up my IMEI in fastboot using “fastboot oem readimei” it shows the correct IMEI. Does this have something to do with the issue?
Any help on this would be great, I have hit a wall doing everything I know to do.
Click to expand...
Click to collapse
Try a factory reset from recovery.
Sorry to say this but why do you open a new thread for your troubles when you dont even get back to the old one and continue there !
http://forum.xda-developers.com/showthread.php?t=2948577
Not very nice of you......and you could have used that thread to continue with your issues.
People put time and effort in your issue it would be nice to get back to them when you get it solved.
Ultimately your goal is to have a working device now right.
Grab the stock ruu and get it back to stock ,from there maybe just use it for texting,messaging,Facebook, etc.
Mr Hofs said:
Sorry to say this but why do you open a new thread for your troubles when you dont even get back to the old one and continue there !
http://forum.xda-developers.com/showthread.php?t=2948577
Not very nice of you......and you could have used that thread to continue with your issues.
People put time and effort in your issue it would be nice to get back to them when you get it solved.
Click to expand...
Click to collapse
Sorry if I should have kept it in one thread, the solution presented in that thread worked. The problems here are unrelated and started after I tried to flash the firmware through RUU. Thanks everyone for the time put into helping myself and everyone on xda.
XSL-FO said:
Try a factory reset from recovery.
Click to expand...
Click to collapse
Unfortunately this did not work the first time I tried it, I will try again and let you know if it does.
jball said:
Ultimately your goal is to have a working device now right.
Grab the stock ruu and get it back to stock ,from there maybe just use it for texting,messaging,Facebook, etc.
Click to expand...
Click to collapse
I went back to stock with no luck. From there I was able to flash a different ROM, and still no luck. I will try going back to stock again.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
JON123123 said:
I went back to stock with no luck. From there I was able to flash a different ROM, and still no luck. I will try going back to stock again.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
Do you have another device with a nano Sim you could pop in your device.maybe you have a bad Sim
jball said:
Do you have another device with a nano Sim you could pop in your device.maybe you have a bad Sim
Click to expand...
Click to collapse
I am using the SIM right now in another phone, so its not bad. I think the problem has something to do with the IMEI. The phone shows no IMEI when I type *#06#, it is just blank. But, in fastboot, it shows the correct IMEI when I type "fastboot oem readimei"
What would make the phone not recognize the IMEI when it shows it correctly in fastboot?
JON123123 said:
I am using the SIM right now in another phone, so its not bad. I think the problem has something to do with the IMEI. The phone shows no IMEI when I type *#06#, it is just blank. But, in fastboot, it shows the correct IMEI when I type "fastboot oem readimei"
What would make the phone not recognize the IMEI when it shows it correctly in fastboot?
Click to expand...
Click to collapse
Found this in my search engine
http://m.youtube.com/watch?v=aCBKVCx3pGU
Give it a try and be careful. Watch the whole video
---------- Post added at 06:36 PM ---------- Previous post was at 06:31 PM ----------
List please what model HTC one m8
at&t
Verizon?
Sprint?
T-Mobile?
Other?
Are you flashing Roms for that specific device?
jball said:
Found this in my search engine
http://m.youtube.com/watch?v=aCBKVCx3pGU
Give it a try and be careful. Watch the whole video
---------- Post added at 06:36 PM ---------- Previous post was at 06:31 PM ----------
List please what model HTC one m8
at&t
Verizon?
Sprint?
T-Mobile?
Other?
Are you flashing Roms for that specific device?
Click to expand...
Click to collapse
I tried this with no luck. The phone's IMEI shows correctly with the command "fastboot oem readimei" but I did give the command "fastboot oem writeimei" with the correct IMEI to make sure. This is an at&t phone, and I have tried Roms specific to this phone
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Does the phone work
jball said:
Does the phone work
Click to expand...
Click to collapse
The phone does turn on and everything is functional except that I cannot connect to the network, so I have no signal. I have checked the apns, there are no apns listed, but my phone will not let me add any. I believe that is due to the IMEI issues.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
I had a similar problem when I converted to GPE, what I did is find a radio that works with my version of the device, flashed it and solved the problem. There is a thread collection of radios on the forum.
Sent from my HTC One_M8 using Tapatalk
MersauX said:
I had a similar problem when I converted to GPE, what I did is find a radio that works with my version of the device, flashed it and solved the problem. There is a thread collection of radios on the forum.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
One of the first things I tried.
JON123123 said:
I then flashed this radio “1.16.21331931.LA11G_20.31A.4145.02L http://d-h.st/NUa | Thanks cruzin_cruzing!” found here: http://forum.xda-developers.com/showthread.php?t=2736921. That did not fix the issue.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
JON123123 said:
I tried this with no luck. The phone's IMEI shows correctly with the command "fastboot oem readimei" but I did give the command "fastboot oem writeimei" with the correct IMEI to make sure. This is an at&t phone, and I have tried Roms specific to this phone
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
Are you using your at&t phone with a different service provider
jball said:
Are you using your at&t phone with a different service provider
Click to expand...
Click to collapse
Nope, att phone with att.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
I did some work over the holidays on my phone to try and get it working again with no luck. I upgraded the firmware downgraded the firmware, installed several ROMs, went back to stock and I still have the same issue. The phone can't seem to read the IMEI number, which is causing it to not be able to connect to ATTs network, but I can see the correct IMEI in fastboot. Below are a couple of screenshots I took while working on it. If anyone can help come up with new ideas on how to fix this, that would be helpful.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Help my Pixel XL,got bootloop,bootloader still locked

Please help my pixel xl
Condition now is bootloop with lock bootloader
Only can enter fastboot,cannot enter into recovery mode
Just try to flash with adb n fastboot but no luck 'cos bootloader still locked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
andixxx81 said:
Please help my pixel xl
Condition now is bootloop with lock bootloader
Only can enter fastboot,cannot enter into recovery mode
Just try to flash with adb n fastboot but no luck 'cos bootloader still locked
Click to expand...
Click to collapse
That's a brick. Call Google with that one. They should replace that. Anytime I've seen the n/a for bootloader and baseband it's toast.
How did you brick with bootloader locked? Best bet is to RMA it for a replacement it's done unless there is a tool to save it but I doubt it
andixxx81 said:
Please help my pixel xl
Condition now is bootloop with lock bootloader
Only can enter fastboot,cannot enter into recovery mode
Just try to flash with adb n fastboot but no luck 'cos bootloader still locked
View attachment 4287902
Click to expand...
Click to collapse
Have you tried a newer RUU version from Google, or was it already on the newest?
toknitup420 said:
That's a brick. Call Google with that one. They should replace that. Anytime I've seen the n/a for bootloader and baseband it's toast.
Click to expand...
Click to collapse
Theres no other way to make this back normal?
liam_davenport said:
How did you brick with bootloader locked? Best bet is to RMA it for a replacement it's done unless there is a tool to save it but I doubt it
Click to expand...
Click to collapse
I just take picture and video,after that suddenly restarted and boot into this,i try to choose start,recovery mode,no luck..
Yes,i did twit google and they said must go to google store
michaelbsheldon said:
Have you tried a newer RUU version from Google, or was it already on the newest?
Click to expand...
Click to collapse
I dont know whats RUU version,i'm nubie about this sir:silly:
andixxx81 said:
I just take picture and video,after that suddenly restarted and boot into this,i try to choose start,recovery mode,no luck..
Yes,i did twit google and they said must go to google store
Click to expand...
Click to collapse
andixxx81 said:
I dont know whats RUU version,i'm nubie about this sir:silly:
Click to expand...
Click to collapse
Yeah RMA it then probably some hardware issue. He means Factory Image from here But I doubt you'll be able to flash one since locked and no fastboot
liam_davenport said:
Yeah RMA it then probably some hardware issue. He means Factory Image from here But I doubt you'll be able to flash one since locked and no fastboot
Click to expand...
Click to collapse
His only option is RMA. Locked bl so he can't do anything on his end. But this is clearly a hardware or software failure that is not his fault. Google will replace it.
Are there any News on this issue?
Got my Pixel Bootlooping with locked Bootloader, disabled OEM-Unlock Option.
Do i have any options other than RMA?
I had this problem too, except I could get into the recovery after many tries. I tried sideloading the ota with adb to fix it. But it didn't help. Any way to get replacement after this many years?
andixxx81 said:
Please help my pixel xl
cannot enter into recovery mode
Click to expand...
Click to collapse
You can get into recovery mode , by (in my case): leave the phone in Power Off mode for an hour or more - Start with power + volume down - recovery... and sometimes it works. But no, it does not help. I sideloaded the OTA multiple times, still no luck
ferydaboss said:
You can get into recovery mode , by (in my case): leave the phone in Power Off mode for an hour or more - Start with power + volume down - recovery... and sometimes it works. But no, it does not help. I sideloaded the OTA multiple times, still no luck
Click to expand...
Click to collapse
I confirm to that as I have the exact problem. I did manage to boot into system a few times after it started bootlooping but it always froze and restarted before I enabled oem unlocking.
iloveoreos said:
I confirm to that as I have the exact problem. I did manage to boot into system a few times after it started bootlooping but it always froze and restarted before I enabled oem unlocking.
Click to expand...
Click to collapse
exactly the same here i just talked to google support, hey redirected me to the UK google support, but i am from Romania, don't really know if they will RMA it or not.. but anyways i will have to pay shipping cost via DHL or something like that. maybe it's not worth it.
ferydaboss said:
exactly the same here i just talked to google support, hey redirected me to the UK google support, but i am from Romania, don't really know if they will RMA it or not.. but anyways i will have to pay shipping cost via DHL or something like that. maybe it's not worth it.
Click to expand...
Click to collapse
I read that replacing the battery sometimes fixes it. I might try that, but it sounds sketchy.
iloveoreos said:
I read that replacing the battery sometimes fixes it. I might try that, but it sounds sketchy.
Click to expand...
Click to collapse
I went to a local repair shop, they said the the "EEMC memory" is bad... meaning that i would have to replace the whole motherboard + there are no spare pieces in my country. Luckily i managed to talk to Google Support, and they will RMA it, i just need to clarify the details of shipping, packaging etc. we'll see HOw it works out. Also i just bought a used pixel 2 XL, so i'm good for the moment. Will sell the pixel XL they send me.
ferydaboss said:
I went to a local repair shop, they said the the "EEMC memory" is bad... meaning that i would have to replace the whole motherboard + there are no spare pieces in my country. Luckily i managed to talk to Google Support, and they will RMA it, i just need to clarify the details of shipping, packaging etc. we'll see HOw it works out. Also i just bought a used pixel 2 XL, so i'm good for the moment. Will sell the pixel XL they send me.
Click to expand...
Click to collapse
Was yours still on warranty?
iloveoreos said:
Was yours still on warranty?
Click to expand...
Click to collapse
It seems so, yes. I bought it last year, from someone, in my country who said it was bought from the UK. I contacted google for fun, and they said that based on the IMEI it is under warranty.
ferydaboss said:
It seems so, yes. I bought it last year, from someone, in my country who said it was bought from the UK. I contacted google for fun, and they said that based on the IMEI it is under warranty.
Click to expand...
Click to collapse
Ok, so I replaced the battery and it booted! Except I broke the screen taking it apart so I couldn't go on it.

Categories

Resources