TMobile Galaxy S5 G900T Boot Loop Issue after root. - T-Mobile Samsung Galaxy S 5

So I recently had Marshmallow firmware version G900TUVU1GPE1_G900TTMB1GPE1_TMB installed and had gotten tired of the update service running and trying to download a firmware update, I used these directions here to root my phone and then install Titanium backup to turn off OTA updating services and ES file explorer to delete the update.zip file
http://forum.xda-developers.com/tmo...l/root-how-to-root-sm-g900t-firmware-t3358190
I recently started having an issue with the phone whenever I would use it with GPS enabled or off, it would reboot and get back to the unlock screen and then go into a reboot loop, which would only stop if the battery were pulled. This happens in Apps too such as Google Play or Facebook, or Accuweather. I figured I'd try to install the Stock KitKat version of G900TUVU1BNH5_G900TTMB1BNH5_TMB, well the reboot loop issue still exists. Is there anyway of resolving this issue as I am thinking of putting GPE1 back In and Redoing the root just to undo it. I know it is forbidden to check NAND Erase All or other firmware options in ODIN. I downloaded a partition/PIT file just i ncase I need it too. I'm pulling my hair out lol.
Thank you
Upate, After I reinstalled G900TUVU1GPE1_G900TTMB1GPE1_TMB, and did a normal system recovery (no TWRP in at this point) I had enabled WIFI and it went into a reboot loop, took the battery out, then I installed TWRP- went to advanced wipe, did not select System, Only Davlik, Internal, Cache. I have not installed SuperSU. I hope this resolves the issue, otherwise I might need a new phone or motherboard...

Did you pull the battery as soon as it boot looped? Mine always loops once after flashing firmware, but boots normally on the second attempt without pulling the battery.

invisiblewave said:
Did you pull the battery as soon as it boot looped? Mine always loops once after flashing firmware, but boots normally on the second attempt without pulling the battery.
Click to expand...
Click to collapse
I have been pulling the battery, plus another oddity is when the phone goes into a loop and I can't get it to stop until after a bit, I can just plug the charger in and then It stops. Someone said the battery could be at fault. I bought a battery and waiting on it between the 14th and 16th, I will definitely follow up if that resolves my issue too.

invisiblewave said:
Did you pull the battery as soon as it boot looped? Mine always loops once after flashing firmware, but boots normally on the second attempt without pulling the battery.
Click to expand...
Click to collapse
Well I believe the Issue has been Resolved, I got the battery yesterday, charged it up over the night and started using it today, so far no random reboots or bootloops.
Differences
The Battery that came with my phone was Made in China, the one I just bought is made in Vietnam.
I will keep yall posted after a few days to see if it has any issues.

Well the battery Fixed my issue.

I'm on my third battery and still looping... Anyone else have any ideas?

workingmomjd said:
I'm on my third battery and still looping... Anyone else have any ideas?
Click to expand...
Click to collapse
go back to stock 4.4.2 rom is the most I can say at this point

The 5th was the charm (I hope!)! Going on day two and at 78%, so the rapid battery drain that started right before the looping is also cured. It's a good thing this is the last of 4 Samsung s5's so cycle the house, so I had lots of spare batteries on hand Thank you!

workingmomjd said:
The 5th was the charm (I hope!)! Going on day two and at 78%, so the rapid battery drain that started right before the looping is also cured. It's a good thing this is the last of 4 Samsung s5's so cycle the house, so I had lots of spare batteries on hand Thank you!
Click to expand...
Click to collapse
i come to notice the battery that came with my phone stated made in china, the new one I ordered said Made In vietnam. I believe batteries made in china is what caused the Note 7s to go up in flames along with Surefire Flashlights to overheat and catch fire too

Related

SGS2 bootloop! Help!

Hi guys! First off, I know this sounds like a common problem, but I've looked through several times and haven't found a solution yet.
I have a SGS2, came as 2.3.3 stock but upgraded a while back to 2.3.5 through Kies. It was working perfectly for as long as I remember.
About a month ago the battery started acting weird going from 80% to 20% in no time, heating up too, I do remember dropping the phone once during this period, but it was nothing (just thought I should include this, also, I usually leave the phone plugged into the charger overnight as I do not have a power source at work (i work outdoors) i probably need a battery replacement)
The screen brightness would sometimes flicker and then POOF! The phone shuts off...At first this would happen at any activity, nothing specific, BUT, I have noticed that it intensifies with the Facebook app.
Anyways, usually plugging the phone back into the charger and powering it up would bring it back online, but not this time. It would get stuck looping the animation of the 'S' at the beginning and no booting up. I have a valid warranty card which I'm guessing will get the phone either fixed or replaced but I need help to try to salvage whatever info I can get my hands on, preferably everything, but my memos are most important to me.
Thanks for the help!
sherief87 said:
Hi guys! First off, I know this sounds like a common problem, but I've looked through several times and haven't found a solution yet.
I have a SGS2, came as 2.3.3 stock but upgraded a while back to 2.3.5 through Kies. It was working perfectly for as long as I remember.
About a month ago the battery started acting weird going from 80% to 20% in no time, heating up too, I do remember dropping the phone once during this period, but it was nothing (just thought I should include this, also, I usually leave the phone plugged into the charger overnight as I do not have a power source at work (i work outdoors) i probably need a battery replacement)
The screen brightness would sometimes flicker and then POOF! The phone shuts off...At first this would happen at any activity, nothing specific, BUT, I have noticed that it intensifies with the Facebook app.
Anyways, usually plugging the phone back into the charger and powering it up would bring it back online, but not this time. It would get stuck looping the animation of the 'S' at the beginning and no booting up. I have a valid warranty card which I'm guessing will get the phone either fixed or replaced but I need help to try to salvage whatever info I can get my hands on, preferably everything, but my memos are most important to me.
Thanks for the help!
Click to expand...
Click to collapse
are u rooted
try flashing the stock rom again and check if u face the same issue
I'm not rooted. I tried doing that using odin and got the stock firmware from sammobile. same thing happens, stuck at the boot.
a friend suggested i try to flash the stock ICS version, same thing.
sherief87 said:
I'm not rooted. I tried doing that using odin and got the stock firmware from sammobile. same thing happens, stuck at the boot.
a friend suggested i try to flash the stock ICS version, same thing.
Click to expand...
Click to collapse
Weird. It shouldn't boot loop. You sure your version is GT-I9100 and not GT-I9100G? Since I'm in Riyadh, the latest version for GB here (Saudi Arabia) was JPKJ2, but that's for GT-I9100, dunno about the G version.
Sent from my GT-I9100 using Tapatalk 2
okay so with the help of a friend and this awesome forum, i managed to install cwm, from there i could take a nandroid backup, but i cant mount the phone as a drive or anything to copy the files, and i'm guessing i cant use this backup i just took to restore later because it'll just get me stuck at the same place im at now
i read that i can use unyaffs to extract files from the resultant backup image, so my question is, before i do a wipe, is there any other method through which i could get a backup of my stuff? the things i would very much like to get a copy off are my messages/notes/whatsapp history and pretty much anything really
thanks for the help!

Constant reboot not caused by rom

My note started doing this after it went through airport security. It was in a bag and went through the x-ray machine. It randomly reboots very often, probably between 20-60 second intervals. I was on CM10, then I flashed back to stock ICS, and then finally up to the official JB update. None of which has solved this problem.
i posted in here.. this may help.
http://forum.xda-developers.com/showthread.php?t=1854944
Good Luck
Still need help
dweeezy said:
i posted in here.. this may help.
http://forum.xda-developers.com/showthread.php?t=1854944
Good Luck
Click to expand...
Click to collapse
Phone is stuck in a boot loop and this is what I know so far. Phone is on stock ROM, power button is working fine, I can get to recovery and OS and download mode, and while phone was charging I took the battery out and the phone keeps vibrating. I now know it's a hardware problem for me (I think), but I can not pin point where. Any advise would be helpful cause I really love my note and this is just breaking my heart.:crying:

[Q]Bootloop Issue

Ok, so my fiancee's at&t note is stuck in a bootloop. I had it running on Blackstar, and since giving it to her hadn't bothered messing with the setup as it was stable. On her way home from work she apparently left the phone in her truck while making a stop in 92 degree weather(Farenheit). Now it will show both Samsung screens and then bootloop. I did some searching here on the forums and have tried everything I can find/think of. Here's a list of everything I've done:
1. Booted into twrp recovery, wiped data, cache, and sdcard for good measure.
2. Got to lockscreen, bootloop.
3. Used ODIN to push Samsung stock files onto phone, including recovery.
4. Got to AT&T easy setup screen, bootloop.
5. Used stock recovery to do hard reset.
6. Still bootlooping from second Samsung screen.
7. Removed back of phone, cleaned power button.
8. Still bootlooping.
I should note that the phone never booted itself after a battery pull, but I figured cleaning the power button couldn't hurt any.
Is there anything else I can try before going to at&t to have it fixed?
UPDATE: Thanks rangercaptain for that. I had totally forgotten Kies had the Firmware recovery. Unfortunately, it didn't work. And AT&T, well, we all know how they are about out of warranty phones. So I'm seemingly stuck, but I did have a thought. If the battery overheated, and malfunctioned, could it cause this? Would it be worth the 10 bucks to order a replacement OEM battery on Amazon and see if it fixes it?
Kies emergency firmware upgrade. Factory cable. Rear (powered) usb port on pc. Battery fully charged. Serial and model number under battery (all capital letters). Pray.
Don't quote, reply. If you quote, edit.
The battery try might be worth a shot. If not.... Surely mobiletechvideos could fix it. If they can be brought back from the dead, surely they can be brought out of bootloop.
Sent from my SGH-I717 using Tapatalk 2
darthmalgus said:
UPDATE: Thanks rangercaptain for that. I had totally forgotten Kies had the Firmware recovery. Unfortunately, it didn't work. And AT&T, well, we all know how they are about out of warranty phones. So I'm seemingly stuck, but I did have a thought. If the battery overheated, and malfunctioned, could it cause this? Would it be worth the 10 bucks to order a replacement OEM battery on Amazon and see if it fixes it?
Click to expand...
Click to collapse
Definitely try the battery. I had exactly this same problem, and even though the old battery seemed to be taking a charge, it was still screwing everything up (in the same ways you described). A new battery fixed everything*.
* - Ok, it actually it took a couple ROM reinstalls, to fix everything I apparently screwed up while trying to fix the devices before switching out the batteries.
Thanks for the info. I went ahead and ordered a new bateery, it'll be here Monday, so hopefully that works. I have the phone flashed stock with Kies at the moment, so I would hope I don't have to do any more reflashing if the battery is the issue.
Yeah i have the same issue. I was running blackstar. I had some issues occasionally with it crashing, nothing major. decided to install JB once ATT had official out. Wiped, installed, gets to att logo and reboot... please post your fix if it works. I have a second battery. I'll give it a shot but I have been keepeing it plugged in while doing these things and it still doesnt work.
"Wiped, installed, gets to att logo and reboot..."
If you're getting to the att logo, it may not be a battery problem. I'd suggest reinstalling the update after manually wiping everything using CWM.
Matt Bernius said:
"Wiped, installed, gets to att logo and reboot..."
If you're getting to the att logo, it may not be a battery problem. I'd suggest reinstalling the update after manually wiping everything using CWM.
Click to expand...
Click to collapse
Tried a couple flashes, with the debloated and bloated Roms based on Official JB. I can get to the getting started screen sometimes. typically I hit the next button and it goes into bootloop. once or twice i was able to select the next button and get to the next screen before it crashed. I'm thinking it's dead but.... idk.
This fixed my issue...
Replaced battery and yeah. I'm all better. so odd.. shrug. The other wasn't giving any indication that it was actually defective.
Awesome ... final step ... change the title to include solved :victory:

[Q&A] [ROM]【4.4.4】Google Play Edition 【KTU84P】- 09/30/2014

[Q&A] [ROM]【4.4.4】Google Play Edition 【KTU84P】- 09/30/2014
Q&A for [ROM]【4.4.4】Google Play Edition 【KTU84P】- 09/30/2014
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
gpz1100 said:
I gave up trying to calibrate my compass. I have issues with it in any rom including stock TW. Some of these chips are just broken.
Click to expand...
Click to collapse
After trying many of the suggestions on this thread to fix the compass (my GPS lock is fine), I thought I might have messed up the hardware somehow. However, last night I flashed the 7/12 KT GE kernel, and the compass now correctly points in the right direction.
Germany?
Hi Dan (or whoever else reads this). Love the ROM! It's amazing. Do you know if it will work in Germany? I went to Mexico a few months ago, and the latest build at the time would not get reception anywhere. Flashing a TW ROM solved the problem, but I would much rather use yours.
Thanks!
TheSt33v said:
Hi Dan (or whoever else reads this). Love the ROM! It's amazing. Do you know if it will work in Germany? I went to Mexico a few months ago, and the latest build at the time would not get reception anywhere. Flashing a TW ROM solved the problem, but I would much rather use yours.
Thanks!
Click to expand...
Click to collapse
Well in case anyone is curious, this ROM gives me great cell service (full signal on Vodaphone.de) but no data in Munich. I tried airplane mode, disabling/enabling data roaming several times and setting the network mode to GSM preferred, but no luck. Flashing the latest release of Hyperdrive ROM allowed me to use data. Oh well.
flashing google edition on verizon s4 on nc5
I'm a noob and can't figure out if i can use safestrap to flash the dandvh google play edition rom.
verizon galaxy s4 on nc5 build, rooted with towel root and running safestrap 3.75
Viper Audio Working?
Does anyone else use Viper Audio with this rom? I find that the audio driver frequently stops processing when I stop playing music and then come back and play again. It will start processing again if I reboot the phone or even kill the Viper gui process. I've tried installing it as a user or system app but hasn't seemed to matter. Anyway, just curious if anyone else was having the same kind of results.
Hi everyone, hoping you all can help me with a problem I'm having with my phone. First, some specs:
ROM: Danvdh GPE 9/30
I am one of those lucky MDK users, I got the phone in May 2013 and rooted early
I had been running the NC5 modem for a while now with no issue. The problem started after I flashed the NG6 modem (from Surge1223's thread) in TWRP. Just fyi, here are the steps I took to flash the modem. Within TWRP, I flashed the zip file, cleared Dalvik/cache, then rebooted.
Almost immediately I started getting random reboots. It rebooted twice, then seemed to settle down, so I decided to wait a day or so to see what my phone would do. Sadly enough, it started rebooting again, so I gave up last night and reflashed the NC5 modem in TWRP using the same method as before. The phone was fine after that, until this afternoon. About an hour ago, my phone froze, and rebooted, but the screen cut off at the Samsung custom padlock boot screen. It seems to be off at this point, but I can't power on the phone without pulling the battery. After pulling and replacing the battery, the phone powers on by itself, but again cuts off at the Samsung boot screen, about 3-4 seconds into the boot process. I've tried booting into TWRP and download mode, with the screen turning off and the device seemingly freezing after 3-4 seconds. I'm at a loss as to what to do at this point.
I'm at work right now, but when I get home, I will see if Odin3 can make some sort of contact with the phone. Any help in the meantime would be greatly appreciated!
Sounds like you may have a bad dl. Re download. Turn phone off. Then boot into TWRP and reflash the modem zip. Not the non-halos.zip.
Alxoom33 said:
Sounds like you may have a bad dl. Re download. Turn phone off. Then boot into TWRP and reflash the modem zip. Not the non-halos.zip.
Click to expand...
Click to collapse
I would love to, but I can't.
I put a video up on Youtube showing what the phone is doing right now. I don't have 10 posts yet, so I can't post links, but if you go to youtube.com then add "/watch?v=3ey5xD9LodY" at the end of the URL, you can see what the phone is doing.
It is the only thing the phone will do. I've tried doing a hard reset by holding the power button, but nothing happens. All I can do is pull the battery and start this process again. If I hold the correct button combos, I can begin to boot into TWRP or download mode, but the phone cuts off/freezes like clockwork after 3 seconds.
I tried to get Odin3 to recognize the phone, but my desktop doesn't recognize that anything is plugged in when I connect my phone to it, so Odin3 by extension doesn't see anything.
Did you install the Samsung apps on your computer? You need them for the computer to recognize your phone.
To hard boot into recovery you need to hold power button and volume up at the same time, then let go of power button once blue writing appears on upper corner of phone.
Sent from my Xoom Wifi using Tapatalk
I'm sure I have. I've been able to send adb commands to the phone in the past. Now however, my PC doesn't even see that a device has been connected to it (nothing shows up in the device manager, not even an unrecognized device).
The phone will no longer charge when I plug it into an AC adapter either (or at least the LED no longer lights up indicating it's charging).
I have tried booting into recovery several times. Each time, it will begin to boot into TWRP, the blue text, "RECOVERY BOOTING...", will display, then immediately afterwards, the screen will cut off and the phone will freeze, just like in the Youtube video I posted.
I'm afraid the thing is bricked...
So, I was talking to a friend about what's been going on with my phone. During the conversation, I started goofing around and smacking the back of the phone like 4-year-old me would an NES to try and make it work (ah, good times...). Believe it or not (and I did not touch the power button while doing this), the phone powered up and successfully booted!!!
It showed only 2% battery life, so I connected it to the AC adapter, but then a few seconds later the phone died again.
This occurrence leads me to believe there is something wrong with the battery, and leads me to another question. Can the S4 (or any other smartphone) run solely on USB power?
My roommate has a Galaxy SIII, I read the SIII battery can be used in the S4, so I will test the phone out with his battery when he gets back tomorrow, and update you then.
marioluigi64 said:
So, I was talking to a friend about what's been going on with my phone. During the conversation, I started goofing around and smacking the back of the phone like 4-year-old me would an NES to try and make it work (ah, good times...). Believe it or not (and I did not touch the power button while doing this), the phone powered up and successfully booted!!!
It showed only 2% battery life, so I connected it to the AC adapter, but then a few seconds later the phone died again.
This occurrence leads me to believe there is something wrong with the battery, and leads me to another question. Can the S4 (or any other smartphone) run solely on USB power?
My roommate has a Galaxy SIII, I read the SIII battery can be used in the S4, so I will test the phone out with his battery when he gets back tomorrow, and update you then.
Click to expand...
Click to collapse
Have you tried a different USB cable/transformer? It sounds like you might just have a charging issue. Not enough juice to get it started.
Allowing a battery to cool down will give it more usable power, which as it heats back up will deplete again. This sounds like your situation... Power off for a few, restart it has enough to begin booting, then depleted again.
The phone cannot run on USB alone it needs the battery to sustain it's operation.
I have tried 3 USB cables, 2 AC adapters, and 2 PCs.
When this started on Friday, my phone was hooked up to my PC at work and showing about 50% battery, but it's possible something went wrong with the battery and it's stopped delivering any significant amount of power or accepting a charge.
So it turns out it wasn't the rom or new modem that was the problem, my battery has decided to kick the bucket. I tried my roommate's battery in my phone and it booted right up as if nothing was ever wrong! Strange that an OEM battery would just die like that, but I suppose that does happen from time to time. Thanks for the help!
matycakes said:
Does anyone else use Viper Audio with this rom? I find that the audio driver frequently stops processing when I stop playing music and then come back and play again. It will start processing again if I reboot the phone or even kill the Viper gui process. I've tried installing it as a user or system app but hasn't seemed to matter. Anyway, just curious if anyone else was having the same kind of results.
Click to expand...
Click to collapse
I use it, and I've never had any issues with it. I would recommend reinstalling, but you've probably tried that already. Are you using the latest version of the app?
TheSt33v said:
I use it, and I've never had any issues with it. I would recommend reinstalling, but you've probably tried that already. Are you using the latest version of the app?
Click to expand...
Click to collapse
Yeah, I have tried reinstalling it, and I am using the latest version of the app. The fact that you haven't had any issues is encouraging. I'll continue to troubleshoot and see what I can find.
I keep getting this (in CWM touch)
Flashing Google Play Edition
Android 4.4.4
Enjoy!
format() expects 5 args, got 4
E: Error in /storage/sdcard1/danvdh-GE-4.4.4-09-30-2014-VZW.zip
(status 7)
installation aborted
Is it just a bad DL?
EDIT: Tried a new DL, same issue. I want to get this fixed asap
Is cm11 theme manager included in this rom?
brd912 said:
Is cm11 theme manager included in this rom?
Click to expand...
Click to collapse
It is not.

Charging issue after lollipop update

I upgraded to 5.1 the other day using the package offered on Huawei's own site. Had to use the force upgrade method, which I did while the phone was plugged into an outlet using the factory charger. Since then, my battery has crapped out on me. I left it to charge all night and when I woke up it was still stuck at roughly 30%. In the span of two days I have tried multiple chargers and performed a factory reset. Somehow I managed to charge it up to 78%, but now it's stuck at that percentage. Anyone have a clue what could possible be preventing it from fully charging?
I have not seen this or heard it from anyone else. Maybe your hardware has an issue?
kimtyson said:
I have not seen this or heard it from anyone else. Maybe your hardware has an issue?
Click to expand...
Click to collapse
That's what I was thinking. As 322 rewrites pretty much everything coming from 4.3. The batteries are hard to replace. But it is doable. Someone posted about doing it. And there is a video of it being done on YouTube. You could also try reflashing 322 first.
I've read one other report on the Huawei forum of someone having a similar issue, except he is able to recharge only after the phone has been discharged to 9%. My thoughts are maybe there is some kind of power conservation trigger or something? I've never had any problem charging my phone to 100% prior to installing the update. If it is a hardware issue, it chose the perfect time to malfunction...
I'm gonna try to downgrade back to 4.3 and see if the issue persists.
Rb8623 said:
I've read one other report on the Huawei forum of someone having a similar issue, except he is able to recharge only after the phone has been discharged to 9%. My thoughts are maybe there is some kind of power conservation trigger or something? I've never had any problem charging my phone to 100% prior to installing the update. If it is a hardware issue, it chose the perfect time to malfunction...
I'm gonna try to downgrade back to 4.3 and see if the issue persists.
Click to expand...
Click to collapse
That should work to. First i have heard of it on stock ROM. Still may want to try reflashing 322 first. Then4.3. Some ran into issues reverting to 4.3. The file system changes evidently can screw up. Let us know how you resolve it in case someone else runs into the same issue.
Moody66 said:
That should work to. First i have heard of it on stock ROM. Still may want to try reflashing 322 first. Then4.3. Some ran into issues reverting to 4.3. The file system changes evidently can screw up. Let us know how you resolve it in case someone else runs into the same issue.
Click to expand...
Click to collapse
Just curious, I'm completely new to android, but could you possibly point me in the direction of how to proceed with reflashing 322? Gonna try it when I get back home from work this afternoon.
Rb8623 said:
Just curious, I'm completely new to android, but could you possibly point me in the direction of how to proceed with reflashing 322? Gonna try it when I get back home from work this afternoon.
Click to expand...
Click to collapse
http://forum.xda-developers.com/asc...ex-huawei-ascend-mate-2-updated-2015-t3149530
That thread has everything you may need in it. Just download the 322 update to your SD card and boot holding down all three buttons. Volume up and down and power. Let it run. Here is Huawei official page with the download and the instructions.
https://community.gethuawei.com/sup...15/06/30/mate2-android-l-update-now-available
I think you probably already did that, but want to mention it regardless. Have you tried turn off phone completely, the boot up and charge? Also charge it when phone is off? I am saying this because the other days I learned reboot the phone is different from turn off then turn on.
Tried downgrading to 148 yesterday, woke up with a 25% charge, same as it was when I plugged it in last night. I also tried the above recommendations for charging while the phone is off, restarting, etc. I have scoured other forums for this issue and found similar stories with other model phones. I'm now thinking it's a hardware issue with a mechanism that senses the battery's status.
Rb8623 said:
Tried downgrading to 148 yesterday, woke up with a 25% charge, same as it was when I plugged it in last night. I also tried the above recommendations for charging while the phone is off, restarting, etc. I have scoured other forums for this issue and found similar stories with other model phones. I'm now thinking it's a hardware issue with a mechanism that senses the battery's status.
Click to expand...
Click to collapse
Very odd indeed. Have you tried completely draining the battery? Then charge while phone is off.. Is it still under warranty?
I have had luck disconnecting the battery, rebooting on outlet power and reconnecting the battery.(this WILL VOID your warranty) Not gospel thou, could have been luck. Reflash if you didn't already first. There are some screwy things that happen, I for instance have a phone that I cannot get back to JB for anything. When it boots it uses stock android bootanimation from system/bin not /cust folder.
If you replace the battery peel carefully or you'll break the LCD.
I don't think its battery thou.
Yep. Tried all of the above. After downgrading to 148, the phone wouldn't even charge even while plugged in. Fortunately, it is still under warranty so I'm sending it in to be serviced...
Unfortunately for me, the entire reason I bought this phone is because it is unlocked and I am leaving for Germany next friday. I bought it hoping to be able to plug a sim from a local phone co. overseas and just go. Now I'll probably have to get a relative to ship it to me after they finish repairs.
And by the way, I initially installed B322 using the forced method. I didn't think it would make a difference. Guess I was wrong.
Rb8623 said:
Yep. Tried all of the above. After downgrading to 148, the phone wouldn't even charge even while plugged in. Fortunately, it is still under warranty so I'm sending it in to be serviced...
Unfortunately for me, the entire reason I bought this phone is because it is unlocked and I am leaving for Germany next friday. I bought it hoping to be able to plug a sim from a local phone co. overseas and just go. Now I'll probably have to get a relative to ship it to me after they finish repairs.
And by the way, I initially installed B322 using the forced method. I didn't think it would make a difference. Guess I was wrong.
Click to expand...
Click to collapse
Sorry we couldn't help. Was worth a shot. Stay safe on your trip.

Categories

Resources