Database Info

Phone radio dead?

So about 30 minutes ago my phone stopped being connected to any kind of cellular service. I've got the triangle with red crossed circle and both debug menu via the dialer and system settings show that there's no received signal period. Tried reflashing the ROM I had loaded to no avail. Was rooted and unlocked so I may be out of my warranty unless I can relock it/unroot it.
Anyone ever seen this before or could point me in the right direction to something I may have missed?
Thanks in advance,
CMNDR

You said "tried reflashing the ROM I had loaded" - what about flashing stock, or even using RSD to flash completely stock?
If you are officially unlocked, I'm sure your serial number is in moto's database - so even if you relocked/unrooted it, the device's warranty (manufacturer, mind you) is still voided...
Note I said manufacturer. Not sure what Sprint would do......

arrrghhh said:
You said "tried reflashing the ROM I had loaded" - what about flashing stock, or even using RSD to flash completely stock?
If you are officially unlocked, I'm sure your serial number is in moto's database - so even if you relocked/unrooted it, the device's warranty (manufacturer, mind you) is still voided...
Note I said manufacturer. Not sure what Sprint would do......
Click to expand...
Click to collapse
I just finished the slowest download of my life (~30KB/s) for the stock zip to flash from RSD Lite, going to do that in the next few minutes. If I remember correctly I might have the device listed under a BestBuy Mobile protection plan, though I haven't looked into what that has for fine print.

CMNDR said:
I just finished the slowest download of my life (~30KB/s) for the stock zip to flash from RSD Lite, going to do that in the next few minutes. If I remember correctly I might have the device listed under a BestBuy Mobile protection plan, though I haven't looked into what that has for fine print.
Click to expand...
Click to collapse
So flashing back stock with RSD seemed to do the trick as I have data and cell connection again.
I found this post http://forum.xda-developers.com/showthread.php?t=2202291 to be most helpful in locating the files to use in RSD.
Will wait a bit before rerooting and adding custom recovery just to make sure it wasn't a hardware issue. Still no idea how my modem file got corrupted though, as the phone was inactive at the time of the loss.

[Q] Activation Problem - Boot Loop

So I sold an unopened, sealed Nexus 5 to someone last night and he's having a problem activating the device.
Here is his description of what happened:
"I popped in the SIM card, the loading proceeded as normally. It said it was activating and then a box popped up saying that "android is upgrading system files" or something like that. It restarted and went back to the language selection screen. I pressed English, next and then it went to the connect to wifi screen, froze and then restarted before I could even connect. Now it just loads on the boot"
I had him boot into recovery and do a factory reset, but the result is the same. I had him do a 2nd factory reset just be sure, but again, same result.
My thought is the system upgrade didn't happen correctly and not is corrupted.
What's the best course of action? Can I use the WugFresh toolkit to flash stock and unroot, or would I have to do it through ADB since the phone can't boot into the system?
I don't want to leave the buyer hanging, he seems like a nice guy, but I'm just not sure how to proceed?

Use ADB and flash the factory image for him.

Synyster06Gates said:
Use ADB and flash the factory image for him.
Click to expand...
Click to collapse
That's what I figured. I'm not super familiar with ADB but can figure it out I'm sure.

SeanPlunk said:
That's what I figured. I'm not super familiar with ADB but can figure it out I'm sure.
Click to expand...
Click to collapse
Easy walkthrough:
1) Install ADB drivers (You can do it with WUG Toolkit).
2) Reboot your device in Fastboot mode (Hold up/down volume and power)
3) Download the latest HAMMERHEAD image from google website.
4) Download the Google SDK (not needed, but you will need Fastboot.exe, so I would recommend downloading the whole thing)
5) Unzip the image (.tar or .tgz I think) to the location where Fastboot.exe is (all the files should be in the same directory, usually platform-tools)
6) Double-click on the flash-all.bat file from the unzipped .tar or .tgz folder, should install stock image on your phone (note that you might need the latest version of Java installed on your computer)
And you're done.
Hope it helped!

switchfo0t said:
Easy walkthrough:
1) Install ADB drivers (You can do it with WUG Toolkit).
2) Reboot your device in Fastboot mode (Hold up/down volume and power)
3) Download the latest HAMMERHEAD image from google website.
4) Download the Google SDK (not needed, but you will need Fastboot.exe, so I would recommend downloading the whole thing)
5) Unzip the image (.tar or .tgz I think) to the location where Fastboot.exe is (all the files should be in the same directory, usually platform-tools)
6) Double-click on the flash-all.bat file from the unzipped .tar or .tgz folder, should install stock image on your phone (note that you might need the latest version of Java installed on your computer)
And you're done.
Hope it helped!
Click to expand...
Click to collapse
Hello, I am the buyer of this Nexus device. I was able to successfully do these steps above, and reload the stock image for the Nexus 5. However, I am still running into issues.
WITH SIM:
I was able to get to the home screen after the initial setup, sent a few test text messages to my Google Voice number successfully, and browse on Chrome for a little bit before the device froze and restarted. After it restarted, I let it load up again, tried setting up my Google account on the device, then it froze again. All of the freezing happens within 3-5 minutes of using the phone.
So I decided to go into the bootloader, and do a factory wipe/cache wipe, and proceed without having the sim card in. I was able to get to the wifi selection screen, select my router, but as soon as the keyboard was suppose to pop up, the device froze and restarted. I am now just stuck on the welcome screen.
Any ideas now?
---------- Post added 29th November 2013 at 12:45 AM ---------- Previous post was 28th November 2013 at 11:56 PM ----------
Update: So I'm not sure what happened, but I ended up locking the device through Wug's Nexus Toolkit, inserted my sim card, and proceeded to set up the phone normally. So far everything has been working perfectly fine. I can receive/send texts, make and receive calls, and do normal functions with the phone without it locking up and restarting. Fingers crossed it'll stay like this.
Any idea on why this would've happened in the first place with the device?
---------- Post added at 01:38 AM ---------- Previous post was at 12:45 AM ----------
Update 2: Well, I noticed that it will randomly reboot every half hour or so it seems. It's kind of random, but I'm not sure what else could be causing these random reboots. The phone itself is working fine, but I just started experiencing random restarts.

Are you still on the stock rom or custom?

neomorphix said:
Are you still on the stock rom or custom?
Click to expand...
Click to collapse
Stock. I did the steps above and flashed the stock rom that I downloaded from Google's website.
---------- Post added at 01:49 AM ---------- Previous post was at 01:48 AM ----------
Jaybot said:
Stock. I did the steps above and flashed the stock rom that I downloaded from Google's website.
Click to expand...
Click to collapse
It was working fine earlier. I put it on the charger and got it to about 50%, used it for a little bit, then bam. It froze, and restarted all over again. I can use the phone maybe 5 - 10 minutes before it starts to recharge. Sometimes It'll automatically reboot after even unlocking the device.

I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.

neomorphix said:
I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.
Click to expand...
Click to collapse
I will try factory and cache wipe again, and see if that does anything with no apps or anything else installed, and go from there.

Jaybot said:
I will try factory and cache wipe again, and see if that does anything with no apps or anything else installed, and go from there.
Click to expand...
Click to collapse
Sorry its happening. With everything stock and no third party apps or mods there to cause it at least to me things start looking like something bigger might be wrong here.

neomorphix said:
Sorry its happening. With everything stock and no third party apps or mods there to cause it at least to me things start looking like something bigger might be wrong here.
Click to expand...
Click to collapse
I think so too. No go after another factory wipe/cache wipe. It reboots automatically after awhile. I haven't had this kind of issue before, so I'm not sure what is causing it.

Jaybot said:
I think so too. No go after another factory wipe/cache wipe. It reboots automatically after awhile. I haven't had this kind of issue before, so I'm not sure what is causing it.
Click to expand...
Click to collapse
Yeah im kindof at a loss here as well. I have had those issues before but they have always been due to something I have added thats messing things up. I am interested to see if anyone else has any ideas.

neomorphix said:
Yeah im kindof at a loss here as well. I have had those issues before but they have always been due to something I have added thats messing things up. I am interested to see if anyone else has any ideas.
Click to expand...
Click to collapse
I figured it would be a sim card issue since it was working for awhile without the sim, but I did the factory/cache thing without the sim card, signed on via wifi, but it still doesn't work. So I am seeing what my options are from here. Thanks for all the tips everyone.

Jaybot said:
I figured it would be a sim card issue since it was working for awhile without the sim, but I did the factory/cache thing without the sim card, signed on via wifi, but it still doesn't work. So I am seeing what my options are from here. Thanks for all the tips everyone.
Click to expand...
Click to collapse
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.

neomorphix said:
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.
Click to expand...
Click to collapse
I was going to try and do that earlier. I will try and do that now, but I can't even get past the bootscreen animation at this point. The 4 dots will do the animation, freeze, and just reboot.
I'll keep trying. But, I really think this is just a defective one. I had a white Nexus 5 a few weeks ago and didn't have any of these issues :crying:
Edit: My last restart the phone kept vibrating like crazy before restarting.

Jaybot said:
I was going to try and do that earlier. I will try and do that now, but I can't even get past the bootscreen animation at this point. The 4 dots will do the animation, freeze, and just reboot.
I'll keep trying. But, I really think this is just a defective one. I had a white Nexus 5 a few weeks ago and didn't have any of these issues :crying:
Edit: My last restart the phone kept vibrating like crazy before restarting.
Click to expand...
Click to collapse
Ok. This just sucks. But as with any mass produced product there is bound to be the ocasional issue.

neomorphix said:
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.
Click to expand...
Click to collapse
Honestly it sounds like it's hardware related and time for RMA. OP If you do have ADB set up grab the last_kmsg right after the reboot.
Code:
adb pull /proc/last_kmsg
I doubt it will show any kernel panic but it's worth a shot.

theesotericone said:
Honestly it sounds like it's hardware related and time for RMA. OP If you do have ADB set up grab the last_kmsg right after the reboot.
Code:
adb pull /proc/last_kmsg
I doubt it will show any kernel panic but it's worth a shot.
Click to expand...
Click to collapse
From the sound of it he is now not even getting far enough to be able to pull it. I also think RMA is the best option here.

Jaybot said:
Edit: My last restart the phone kept vibrating like crazy before restarting.
Click to expand...
Click to collapse
neomorphix said:
From the sound of it he is now not even getting far enough to be able to pull it. I also think RMA is the best option here.
Click to expand...
Click to collapse
Just saw that. OP by your earlier symptoms I rules out a stuck power button. With the new info I'd look into it further. If the phone is just looping over and over it could be a stuck power button, Mash the power button repeatedly for a minute. Then try and reboot. A few other people have had this on the N5 already and it's a notorious issue on some Samsung phones.

neomorphix said:
I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.
Click to expand...
Click to collapse
If it comes to that, how do I go about transferring the warranty over?
I feel really bad, I just don't get it. I bought two of them, the other buyer hasn't had any problems. Both brand new, sealed, in the box. Go figure.

What rom should I flash to get extra Languages?

I've got the Canadian Virgin Mobile Moto G, and I recently unlocked the carrier. I am going to unlock to bootloader to flash a rom with more languages, specifically Portuguese.. What rom should I use, I'm looking for the original Moto G software.

Zehmistah said:
I've got the Canadian Virgin Mobile Moto G, and I recently unlocked the carrier. I am going to unlock to bootloader to flash a rom with more languages, specifically Portuguese.. What rom should I use, I'm looking for the original Moto G software.
Click to expand...
Click to collapse
I'm running CM11 and a quick look the phone tells me that it have Portuguese for brazil and portugal, alternatively try any latin american stock rom: http://sbf.droid-developers.org/phone.php?device=14

Z-WolF said:
I'm running CM11 and a quick look the phone tells me that it have Portuguese for brazil and portugal, alternatively try any latin american stock rom: http://sbf.droid-developers.org/phone.php?device=14
Click to expand...
Click to collapse
Oh man, thank you for the link, I just might use that. Just a refresher, to flash It I would first unlock the bootloader, flash a new recovery, wipe, and then flash the new rom?

Zehmistah said:
Oh man, thank you for the link, I just might use that. Just a refresher, to flash It I would first unlock the bootloader, flash a new recovery, wipe, and then flash the new rom?
Click to expand...
Click to collapse
yep, but you don't need to flash a custom recovery for a Stock ROM.

Z-WolF said:
yep, but you don't need to flash a custom recovery for a Stock ROM.
Click to expand...
Click to collapse
Thank you!!! and one more question, the new rom should still be capable of getting OTA updates from whatever carrier's rom I flashed, correct?

Zehmistah said:
Thank you!!! and one more question, the new rom should still be capable of getting OTA updates from whatever carrier's rom I flashed, correct?
Click to expand...
Click to collapse
****. I think I ****ed up. http://forum.xda-developers.com/showthread.php?t=2727965

Zehmistah said:
****. I think I ****ed up. http://forum.xda-developers.com/showthread.php?t=2727965
Click to expand...
Click to collapse
Zehmistah said:
Okay so I unlocked my bootloader for my Moto G, and when It rebooted it said android was updating apps and then all the processes stopped working. It booted into the android startup but I couldn't get any processes running so it wouldnt work. I tried to reboot and now android doesn't even boot up. Should I flash a custom recovery right now and then wipe??? I haven't done anything to the phone other than carrier unlock and bootloader unlock. please help
Should I try this? http://forum.xda-developers.com/showthread.php?t=2542219 , or is it too risky right now? I'm planning to restore it to another stock firmware anyways.
Click to expand...
Click to collapse
First, don't panic.
Second, explain how do you unlock the bootloader, did you use this?
Third, what does the bootloader screen (Power+VolDown) says in the second to last line before the first break (LOCKED/UNLOCKED).
Fourth, if it says UNLOCKED, try to flash the ROM using this, otherwise try to unlock the bootloader again with the link i posted in the second point.
And don't worry as long as you can enter fastboot mode (bootloader) you can fix everything, and nothing of the things you are doing affects fastboot mode.

They all want money.
Sent from my GT-N7105 using xda app-developers app

Perry2547 said:
They all want money.
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Can you elaborate?

You can add more languages without a custom ROM using MoreLocale 2.

Z-WolF said:
First, don't panic.
Second, explain how do you unlock the bootloader, did you use this?
Third, what does the bootloader screen (Power+VolDown) says in the second to last line before the first break (LOCKED/UNLOCKED).
Fourth, if it says UNLOCKED, try to flash the ROM using this, otherwise try to unlock the bootloader again with the link i posted in the second point.
And don't worry as long as you can enter fastboot mode (bootloader) you can fix everything, and nothing of the things you are doing affects fastboot mode.
Click to expand...
Click to collapse
I used that webstie to unlock the bootloader, and when I went to fastboot it did say UNLOCKED status code: 3.
I left it plugged into my PC last night because It wouldn't turn off, and I think it wasn't charging because now it's off and won't turn on. I'm going to plug it into a wall charger and wait a few to check if it's on.
After that, I'll try the method you said.
EDIT: Seems like charging doesn't work either, weird... because it said it was connecting to my PC last night in Fastboot

Zehmistah said:
I used that webstie to unlock the bootloader, and when I went to fastboot it did say UNLOCKED status code: 3.
I left it plugged into my PC last night because It wouldn't turn off, and I think it wasn't charging because now it's off and won't turn on. I'm going to plug it into a wall charger and wait a few to check if it's on.
After that, I'll try the method you said.
EDIT: Seems like charging doesn't work either, weird... because it said it was connecting to my PC last night in Fastboot
Click to expand...
Click to collapse
That's weird, doing the steps in that page don't make changes big enough in the phone to make something like that happen.
What does it says in the line below UNLOCKED, USB CONNECTED or CONNECT USB DATA CABLE while you had it connected to your pc/wall?
Why don't you try to use another cable?

Z-WolF said:
That's weird, doing the steps in that page don't make changes big enough in the phone to make something like that happen.
What does it says in the line below UNLOCKED, USB CONNECTED or CONNECT USB DATA CABLE while you had it connected to your pc/wall?
Why don't you try to use another cable?
Click to expand...
Click to collapse
I don't remember what it said.
I've tried a few different wall chargers and cables. They seem to charge my other phones but not this one. I'm going to wait an hour and then maybe put it in the freezer for a few minutes

Zehmistah said:
I don't remember what it said.
I've tried a few different wall chargers and cables. They seem to charge my other phones but not this one. I'm going to wait an hour and then maybe put it in the freezer for a few minutes
Click to expand...
Click to collapse
That's a... unorthodox approach, but reading around it just might work.
I can only recommend you to put it in a sealed container and having a rice bag at hand afterwards, just in case.
Now if you can get it to fastboot mode, try to restore a backup (if you did one) or flash a ROM, im assuming that if you can connect a cable and send commands to fastboot it is charging the phone. BTW at this point if you can send commands and are tired trying to fix it, you can execute
Code:
fastboot oem lock
and you can claim the warranty, that behaviour is not normal, maybe something in the hardware side broke but until we test it more we can't be sure.
Now while we wait in for the phone to become a popsicle, can you detail how you unlocked it?

Z-WolF said:
That's a... unorthodox approach, but reading around it just might work.
I can only recommend you to put it in a sealed container and having a rice bag at hand afterwards, just in case.
Now if you can get it to fastboot mode, try to restore a backup (if you did one) or flash a ROM, im assuming that if you can connect a cable and send commands to fastboot it is charging the phone. BTW at this point if you can send commands and are tired trying to fix it, you can execute
Code:
fastboot oem lock
and you can claim the warranty, that behaviour is not normal, maybe something in the hardware side broke but until we test it more we can't be sure.
Now while we wait in for the phone to become a popsicle, can you detail how you unlocked it?
Click to expand...
Click to collapse
Ok, so I bought the phone and got it carrier unlocked, then yesterday I decided to flash a new rom to get the languages so I went to https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Unlocked the bootloader and when the phone was about to restart from cmd it said "FAILED" but rebooted anyways. It went into fastboot again and ti said it was Unlocked, when I selected Normal Reboot, it started up with the bootloader logo and continued on normally. It was then that it displayed the android startup page (Where you select language, sign into google, connect to wifi etc.) like I haven't used the phone before. Shortly after a popup came and said " Android is updating # of apps out of 137", once that was over every single process on the phone crashed.
Now I'm where I am now.
One more thing, I booted it into recovery before I unlocked the bootloader, accidently. Do you think it maybe could've wiped the original OS on the device?

Zehmistah said:
Ok, so I bought the phone and got it carrier unlocked, then yesterday I decided to flash a new rom to get the languages so I went to https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Unlocked the bootloader and when the phone was about to restart from cmd it said "FAILED" but rebooted anyways. It went into fastboot again and ti said it was Unlocked, when I selected Normal Reboot, it started up with the bootloader logo and continued on normally. It was then that it displayed the android startup page (Where you select language, sign into google, connect to wifi etc.) like I haven't used the phone before. Shortly after a popup came and said " Android is updating # of apps out of 137", once that was over every single process on the phone crashed.
Now I'm where I am now.
One more thing, I booted it into recovery before I unlocked the bootloader, accidently. Do you think it maybe could've wiped the original OS on the device?
Click to expand...
Click to collapse
As far as i know, you can't wipe the system with a stock recovery and with a "blank" OS your phone still connects to PC.
i forgotted this existed, at this point you can't lose anything in trying it. i dont recomend the bootloader bricker part for your case.

Z-WolF said:
As far as i know, you can't wipe the system with a stock recovery and with a "blank" OS your phone still connects to PC.
i forgotted this existed, at this point you can't lose anything in trying it. i dont recomend the bootloader bricker part for your case.
Click to expand...
Click to collapse
The phone isnt't being detected when I plug it in.
I've read that leaving the phone 24 hours untouched could also help the battery. I'm going to try that\
EDIT: GOT IT TO TURN ON!!!

Ok, so I got it working. The thread you told me first helped!! It works fine now with the Brazilian software. Thank you very much, you're a life saver.
Now... I've got another moto G to do the same to

Zehmistah said:
Ok, so I got it working. The thread you told me first helped!! It works fine now with the Brazilian software. Thank you very much, you're a life saver.
Now... I've got another moto G to do the same to
Click to expand...
Click to collapse
You had me worried there, i though it was a goner. in the end everything turned out okay.
Happy to be of service.

[Q] Did my M8 self-destruct?

Yesterday afternoon at work, I rebooted by m8 (Verizon) and didn't realize there was a problem because I put it back in my pocket before it was fully booted. Next time I looked at it, I had no signal and digging deeper, I saw that the baseband is "Unknown" in settings and the IMEI is "U nkn own". I've tried the RUUs for 4.4.3 and 4.4.4 and can't get the phone to see the IMEI and baseband while booted but both show up fine in hboot/fastboot as shown in the attached pics in the next post. I was running the Viper rom when this happened.

Settings and command prompt pics showing problem

bb1981 said:
Yesterday afternoon at work, I rebooted by m8 (Verizon) and didn't realize there was a problem because I put it back in my pocket before it was fully booted. Next time I looked at it, I had no signal and digging deeper, I saw that the baseband is "Unknown" in settings and the IMEI is "U nkn own". I've tried the RUUs for 4.4.3 and 4.4.4 and can't get the phone to see the IMEI and baseband while booted but both show up fine in hboot/fastboot as shown in the attached pics in the next post. I was running the Viper rom when this happened.
Click to expand...
Click to collapse
bb1981 said:
Settings and command prompt pics showing problem
Click to expand...
Click to collapse
Do you always run it in airplane mode?
?

I didn't even realize that when I took the pics but without putting it into airplane mode, it would sit at the htc logo indefinitely until a few minutes pass and it reboots only to get stuck in that cycle unless I jump in and power off. I did forget to mention the reboots after a few minutes in the OP also in case that changes what the issue could be. This was coming off the 4.4.3 RUU and I had the same issue with 4.4.4 and also Sinless 3.5.5(?). It worked great before and I'm just hoping it isn't hardware failure.

bb1981 said:
I didn't even realize that when I took the pics but without putting it into airplane mode, it would sit at the htc logo indefinitely until a few minutes pass and it reboots only to get stuck in that cycle unless I jump in and power off. I did forget to mention the reboots after a few minutes in the OP also in case that changes what the issue could be. This was coming off the 4.4.3 RUU and I had the same issue with 4.4.4 and also Sinless 3.5.5(?). It worked great before and I'm just hoping it isn't hardware failure.
Click to expand...
Click to collapse
Which method did you use for the RUU? Exe or sd?

Initially, I used the exe version but when it have the version number it was going to upgrade to, it was unreadable. Going back to 4.4.3, I flashed the firmware through fastboot then ran the ruu off the sd card. That's also why the sd card is ejected in the first pic so I could get past hboot to make sure it completely powers off.

bb1981 said:
Initially, I used the exe version but when it have the version number it was going to upgrade to, it was unreadable. Going back to 4.4.3, I flashed the firmware through fastboot then ran the ruu off the sd card. That's also why the sd card is ejected in the first pic so I could get past hboot to make sure it completely powers off.
Click to expand...
Click to collapse
Did you try a factory reset from stock recovery/hboot yet?

I'll try that next. I just tried it but it seems like I don't have a recovery installed. Instead of saying recovery booting, it just bootloops.

just tried flashing stock recovery and got stuck in a bootloop again. Running the exe again to try 4.4.4 and still get the same unreadable upgrade version. The version that it's coming from has been right all the time, but the version it's going to I'm guessing should be 3.xxxxx instead of like the screenshot attached.

bb1981 said:
just tried flashing stock recovery and got stuck in a bootloop again. Running the exe again to try 4.4.4 and still get the same unreadable upgrade version. The version that it's coming from has been right all the time, but the version it's going to I'm guessing should be 3.xxxxx instead of like the screenshot attached.
Click to expand...
Click to collapse
That's fine man. It's not an encrypted rom so it doesn't read the plain text file correctly. It will flash what it's supposed to.

dottat said:
That's fine man. It's not an encrypted rom so it doesn't read the plain text file correctly. It will flash what it's supposed to.
Click to expand...
Click to collapse
That's a relief to see that. After I ran it I wasn't sure because it gets stuck on the setup splash screen (thinking it was something not reading correctly on my end and even tried running a second time right away) and I can't get past it at all without airplane mode. I'll have to keep working on it later and see what happens. Thank you for the replies and help, especially with the RUU files and hopefully I can get it figured out. :fingers-crossed::highfive:

bb1981 said:
That's a relief to see that. After I ran it I wasn't sure because it gets stuck on the setup splash screen (thinking it was something not reading correctly on my end and even tried running a second time right away) and I can't get past it at all without airplane mode. I'll have to keep working on it later and see what happens. Thank you for the replies and help, especially with the RUU files and hopefully I can get it figured out. :fingers-crossed::highfive:
Click to expand...
Click to collapse
Did you try flashing the newest twrp 2.8.0.3 recovery ?

Fyi 4.4.4 roms can take up to 20 mins to get to the initial set up screen you might want to hang in there.

Roefastford said:
Did you try flashing the newest twrp 2.8.0.3 recovery ?
Click to expand...
Click to collapse
Twrp does work although I haven't tried it this time just to see if I could try a factory reset to maybe get back my lost baseband and IMEI.
smeejaytee said:
Fyi 4.4.4 roms can take up to 20 mins to get to the initial set up screen you might want to hang in there.
Click to expand...
Click to collapse
I wish I could. The phone once booted will reboot itself after a few minutes.

Oh ok sorry that didn't help.

smeejaytee said:
Oh ok sorry that didn't help.
Click to expand...
Click to collapse
I apologize if the last reply was short and possibly coming across snippy...I was at work and didn't have longer to reply...I think I may have made some very sight progress but the phone still knows nothing about itself once booted. I flashed twrp then wiped system, data, cache and dalvik then proceeded to flash unsense 6 and the 4.4.4 insecure kernel which is recommended by the developer for this rom. It booted fine and on the just a sec screen (right after the language selection on aosp/gpe), I did the four corner tap to bypass setup, enabled dev options, then had it connected to my laptop collecting a logcat for when it rebooted to see if it could show someone who knows far more about android than I do what could be causing trouble. The only problem this time is it never did. Almost like taking a car into the mechanic and somehow it knows and doesn't misbehave.... In fact, I feel asleep for a short time and when I woke up again, the command prompt never changed indicating that it ran the whole time without a reboot. At that time, I powered off and called it a night. Is it possible for a partition to become corrupted causing this?

bb1981 said:
I apologize if the last reply was short and possibly coming across snippy...I was at work and didn't have longer to reply...I think I may have made some very sight progress but the phone still knows nothing about itself once booted. I flashed twrp then wiped system, data, cache and dalvik then proceeded to flash unsense 6 and the 4.4.4 insecure kernel which is recommended by the developer for this rom. It booted fine and on the just a sec screen (right after the language selection on aosp/gpe), I did the four corner tap to bypass setup, enabled dev options, then had it connected to my laptop collecting a logcat for when it rebooted to see if it could show someone who knows far more about android than I do what could be causing trouble. The only problem this time is it never did. Almost like taking a car into the mechanic and somehow it knows and doesn't misbehave.... In fact, I feel asleep for a short time and when I woke up again, the command prompt never changed indicating that it ran the whole time without a reboot. At that time, I powered off and called it a night. Is it possible for a partition to become corrupted causing this?
Click to expand...
Click to collapse
Partitions can get corrupted but as far as I'm aware the only way to fix it is with soff I'm not positive because there is an option in twrp to repair partitions also you may be able to use that without soff.

_)(_(45466_!!$$%[¥|[]®]«¥°]<<° xda app...why do I not have permission to post? [/rant]
I picked up a replacement gunmetal gray m8 on swappa and am considering putting the red one up on the boneyard there to give someone a chance to poke around with it. I was wondering if a partition that twrp doesn't have in the repair section like the one for radio/modem for instance could get damaged. The RUU should take care off any problems like that though so I'm officially stumped and haven't really had any extra time to do any troubleshooting.

bb1981 said:
_)(_(45466_!!$$%[¥|[]®]«¥°]
Weird quotes too...the app doesn't like you lol. If you are replacing it can you send me the broken one so I can better try to support this device?
Edit...I know you probably will get pm requests for that too. I'm all about unbricking HTC phones and I'm sure there's enough people around here to back that up between my ruu support and all.
Click to expand...
Click to collapse

dottat said:
bb1981 said:
_)(_(45466_!!$$%[¥|[]®]«¥°]
Weird quotes too...the app doesn't like you lol. If you are replacing it can you send me the broken one so I can better try to support this device?
Edit...I know you probably will get pm requests for that too. I'm all about unbricking HTC phones and I'm sure there's enough people around here to back that up between my ruu support and all.
Click to expand...
Click to collapse
I finally got wise and did a copy and paste after something like 5 times saying I didn't have permission lol....that sounds like a great idea. More (and better) support and understanding is always good.
Click to expand...
Click to collapse

SM-G955U1. XAA version. Bootloop problem, any help?

MY BAD, PLEASE MOVE THIS TO THE CORRECT SECTION. I'M REALLY SORRY.
Hello!, my mother bought this phone for her in the US and from day 0 it has been having problems. She couldn't use wifi or bluetooth for example, and sometimes it just kept restarting till it worked again, but without any connectivity functions, except mobile data.
I tried to fix this updating the phone using Samsung Smart Switch to the last build (AQL1) but now the phone is stuck on the boot screen no matter what I do.
Tried flashing with Odin, it worked, but the phone is still on boot loop. I read somewhere in this forum that you can install an older version of the bootloader to take the phone out of this hell and I did it, using the build AQK2 bootloader but no luck, same problem.
Also, the phone doesn't have USB debugging enable nor OEM unlock either. I can access both recovery and download mode though.
At this point I'm out of ideas, can someone help me with this one?
Thanks in advanced.
fefin

fefin said:
MY BAD, PLEASE MOVE THIS TO THE CORRECT SECTION. I'M REALLY SORRY.
Hello!, my mother bought this phone for her in the US and from day 0 it has been having problems. She couldn't use wifi or bluetooth for example, and sometimes it just kept restarting till it worked again, but without any connectivity functions, except mobile data.
I tried to fix this updating the phone using Samsung Smart Switch to the last build (AQL1) but now the phone is stuck on the boot screen no matter what I do.
Tried flashing with Odin, it worked, but the phone is still on boot loop. I read somewhere in this forum that you can install an older version of the bootloader to take the phone out of this hell and I did it, using the build AQK2 bootloader but no luck, same problem.
Also, the phone doesn't have USB debugging enable nor OEM unlock either. I can access both recovery and download mode though.
At this point I'm out of ideas, can someone help me with this one?
Thanks in advanced.
fefin
Click to expand...
Click to collapse
Have you reached out to Samsung yet?

Mr. Orange 645 said:
Have you reached out to Samsung yet?
Click to expand...
Click to collapse
Thanks for answering. Where I live there is not a single Samsung Service, only at like 1800km from here, that's why I'm trying to solve this by myself but seems that this is a hard one... I hope someone can help me to deal with this as it was a big investment :/
Thanks again!, if someone knows a way to help please tell me.
fefin

fefin said:
Thanks for answering. Where I live there is not a single Samsung Service, only at like 1800km from here, that's why I'm trying to solve this by myself but seems that this is a hard one... I hope someone can help me to deal with this as it was a big investment :/
Thanks again!, if someone knows a way to help please tell me.
fefin
Click to expand...
Click to collapse
I mean have you called or emailed Samsung?

Mr. Orange 645 said:
I mean have you called or emailed Samsung?
Click to expand...
Click to collapse
No I haven't, I will give a try soon through web chat.
I mean, this shouldn't be happening, it's a brand new phone, all over the internet are people with the same problems as me and looks like so far there is no solution.
Maybe it's a faulty phone/hardware? My knowledge is not enough in this matter.
See you!,
Federico.

I need a couple things from you
1. What model does it say on the back of the phone i understand you posted it in the header but please for safety sake .
2. Go into download mode for me so i can see what carrier it lists
3. Try wiping data cache in recovery
Sent from my SM-G955U1 using XDA-Developers Legacy app

allenjthomsen said:
I need a couple things from you
1. What model does it say on the back of the phone i understand you posted it in the header but please for safety sake .
2. Go into download mode for me so i can see what carrier it lists
3. Try wiping data cache in recovery
Sent from my SM-G955U1 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for answering!, here it goes:
1. It says SM-G955U1
2. Carrier: XAA
3. Done, still the same.
An update from my last post:
After a few bootloops the FRP screen showed up, as the phone can't use wifi yet I managed to access using mobile data and enabled the USB debugging, but after trying to enable wifi the phone froze and went on bootloop again, so still the same but with the USB debugging enabled. I'm currently on the build AQK2.
Thanks again, and I hope we can fix this.
Update 2:
I cleared the cache, after a few bootloops the phone actually boots (gets to the lock screen), and it restarts again while the message "Android is starting" is loading, so now it's a different type of bootloop I guess. It does the same even in safe mode.
I will turn it off for now.

fefin said:
Thanks for answering!, here it goes:
1. It says SM-G955U1
2. Carrier: XAA
3. Done, still the same.
An update from my last post:
After a few bootloops the FRP screen showed up, as the phone can't use wifi yet I managed to access using mobile data and enabled the USB debugging, but after trying to enable wifi the phone froze and went on bootloop again, so still the same but with the USB debugging enabled. I'm currently on the build AQK2.
Thanks again, and I hope we can fix this.
Update 2:
I cleared the cache, after a few bootloops the phone actually boots (gets to the lock screen), and it restarts again while the message "Android is starting" is loading, so now it's a different type of bootloop I guess. It does the same even in safe mode.
I will turn it off for now.
Click to expand...
Click to collapse
Ok i want you to do a couple things for me
1.Download this file http://updato.com/firmware-archive-select-model?record=F837B5F2EC0611E7A5F9FA163EE8F90B this is the latest update for the G955U1
2. extract the zip file using 7zip so you have 5 .tar.md5 files
3. go to the CSC_OYM_G955U1OYM2AQL1_CL12513005_QB15986651_REV00_user_low_ship_MULTI_CERT.tar.md5 and right click on the file and goto 7-zip and then click open archive
4. you will see a file called DREAM2QLTE_USA_SINGLE.pit i want you to extract it to the folder you have Odin in if not quick search forums for it
5. Open odin and go to the the pit tab it will do a pop up just click ok and ignore
6. click the pit button and find the pit file that you extracted and select it
7. now go to options tab
8.check to make sure you have auto reboot, re-partition, and f reset timer checked
9.Load BL,AP,CP,CSC in respective slots on right side
10. click start and let the phone flash, as soon as it is done hold volume up bixby and power button wait for recovery to load and wipe data and factory reset.
11. reboot and let it boot if you are still in a bootloop after these steps pm me and i will help you the last way i know how to fix these phones.

allenjthomsen said:
Ok i want you to do a couple things for me
1.Download this file http://updato.com/firmware-archive-select-model?record=F837B5F2EC0611E7A5F9FA163EE8F90B this is the latest update for the G955U1
2. extract the zip file using 7zip so you have 5 .tar.md5 files
3. go to the CSC_OYM_G955U1OYM2AQL1_CL12513005_QB15986651_REV00_user_low_ship_MULTI_CERT.tar.md5 and right click on the file and goto 7-zip and then click open archive
4. you will see a file called DREAM2QLTE_USA_SINGLE.pit i want you to extract it to the folder you have Odin in if not quick search forums for it
5. Open odin and go to the the pit tab it will do a pop up just click ok and ignore
6. click the pit button and find the pit file that you extracted and select it
7. now go to options tab
8.check to make sure you have auto reboot, re-partition, and f reset timer checked
9.Load BL,AP,CP,CSC in respective slots on right side
10. click start and let the phone flash, as soon as it is done hold volume up bixby and power button wait for recovery to load and wipe data and factory reset.
11. reboot and let it boot if you are still in a bootloop after these steps pm me and i will help you the last way i know how to fix these phones.
Click to expand...
Click to collapse
Sadly it didn't work. The phone is still loading till "android is starting" sign and then restarting again.
I will write you so you can help me through pm, could this be a faulty hardware?

I'd like to know the other solution too.

I will tell you all what todo as a last resort.
IF YOU CHOOSE TO DO THIS I TAKE NO RESPONSIBILITY IF YOUR DEVICE STOPS WORKING OR DOES NOT TURN ON!!!
Follow all previously said steps i outlined but when you go into the options tab select nand erase all also then flash device.
Sent from my SM-G955U1 using XDA-Developers Legacy app

try installing PartCyborgRom

@fefin -Sorry to hear that you're having issues - But I'd like to clear one thing up - Your comment that this is an issue "all over the internet" sim isn't true... I don't know how many Millions of S8 / S8+ have been sold - But your post is the first that I've ever heard of anything like this... I concur with the recommendation that you call or Chat with Samsung Technical Support - Preferably before you find the phone completely unable to Boot into Download Mode - Get Samsung to help you - or you may risk voiding the warranty if Samsung determines that you are ultimately responsible for the state of the phone ??
Sent from my SM-G955W ??

allenjthomsen said:
I will tell you all what todo as a last resort.
IF YOU CHOOSE TO DO THIS I TAKE NO RESPONSIBILITY IF YOUR DEVICE STOPS WORKING OR DOES NOT TURN ON!!!
Follow all previously said steps i outlined but when you go into the options tab select nand erase all also then flash device.
Sent from my SM-G955U1 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for your help! Much appreciated.
DR25 said:
try installing PartCyborgRom
Click to expand...
Click to collapse
Thanks for your suggestion, I will look into it.
shaggyskunk said:
@fefin -Sorry to hear that you're having issues - But I'd like to clear one thing up - Your comment that this is an issue "all over the internet" sim isn't true... I don't know how many Millions of S8 / S8+ have been sold - But your post is the first that I've ever heard of anything like this... I concur with the recommendation that you call or Chat with Samsung Technical Support - Preferably before you find the phone completely unable to Boot into Download Mode - Get Samsung to help you - or you may risk voiding the warranty if Samsung determines that you are ultimately responsible for the state of the phone
Sent from my SM-G955W
Click to expand...
Click to collapse
Thanks for answering!, sorry for my late response.
Well, if you check samsung's official forum there are a few threads with 15+ pages of people complaining about wifi issues (https://us.community.samsung.com/t5/forums/v3_1/forumtopicpage/board-id/GS8QA/thread-id/862/page/1 and https://us.community.samsung.com/t5/forums/v3_1/forumtopicpage/board-id/GS8QA/thread-id/30601/page/1) about bootloop problems, (https://us.community.samsung.com/t5...id/GS8QA/thread-id/3920/highlight/true/page/1) also there is a post on another webpage talking about bootloops on this model and how to fix them (https://thedroidguy.com/2017/12/sol...p-issue-s8-turns-screen-remains-black-1079013).
I know it's not representative, as you said, millions of phones has been sold, but what I meant when I said "all over the internet" is that you can easily find people with this same problem. This shouldn't be happening, not on any phone even less on such an expensive phone.
I think the phone is officially dead, I took it to a well known local technician and even him couldn't fix it. My nearest official samsung service is 1600km away. On the other hand, my aunty got for herself an S8 and it's working perfect, so it's just bad luck for my mom I guess.
The phone had issues since she bought it (wifi and bluetooth didn't worked at all, but she is not really a tech person so she thought it was fine), the phone was working with some bootloops from time to time and after a while it fell from and got a little crack on the top but it didn't change the behavior of the phone, it was still ****ed up. That's the thing, because of the crack I'm pretty sure they won't take it back or even try to fix it (for free at least), they will say the problem is because of the fall. I'd been reading a lot about this and seems that I'm pretty screwed D:
I will sell the phone for parts. At least I will recover 60% of the initial investment.

fefin said:
That's the thing, because of the crack I'm pretty sure they won't take it back or even try to fix it (for free at least), they will say the problem is because of the fall. I'd been reading a lot about this and seems that I'm pretty screwed D:
I will sell the phone for parts. At least I will recover 60% of the initial investment.
Click to expand...
Click to collapse
If you have some 'proof' the problem existed, before the crack, and can prove when the crack occurred, or reasonable determinate approximation, small claims court will vindicate you, and Samsung will have to pay.
Sad to say would take a little time of yours to get them there, but it is an easy process, and with reasonable ability to determine/evidence those two things, a sure win.
But still a PITA.