Database Develop

No sound then baseband on GT-I9305 - tried everything

My Galaxy S3 GT-I9305 LTE was running Liquid Smooth 2.37. I bought the phone second hand, it arrived loaded with a stock ROM for Australia's Optus network.
I promptly rooted and flashed the phone to Liquid Smooth and the phone ran fine for months on the 2 Degrees Network in New Zealand.
Recently, (not sure how) I lost notification and phone ring sounds, I first tried restoring my cwm backup on an external sd card - it failed.
Then, after numerous reinstalls, trying various LS and other roms, I lost baseband and have no cell signal - but after flashing to a stock 4.3 rom I have sound back.
In the phone's 'about' section the baseband field is empty.
I've read tons of help posts but nothing works, maybe I need a more methodical approach, but every entry point seems to have a roadblock.
Here's a few of the things I've tried with results in brackets,
Firstly, I thought I'd re-flash back to the phone's original stock ROM using Kies, but the weird thing is Kies doesn't restore, it upgrades to the latest 4.3 ROM, which fails to restore baseband.
I wanted to send the phone back to the 4.1.2 it came with or was it an earlier ROM? I can't remember as I didn't note it down.
Anyway, I must have tried reflashing a dozen stock roms I've found online using Odin. Some of them partially work, I get sound back, (it seems only the 4.3 ones work, with the german I9305XXUEMKC I9305VD2EMK2 reliably loading - it even gives me a NZ english install option) but none restore the baseband.
And all the ones I've found for Optus, which should work, including earlier Android stocks, are rejected. I get the 'unsupported device' or status 7 error in Odin.
I've tried 'fixing permissions' in cwm then reinstalling but I get the same 'status 7' error.
So I decided to install I9305XXUEMKC, install cwm, root the phone and try installing different baseband kernals and/or custom roms to fix the (probably corrupt) efs.
But I'm going round in circles trying to root the phone. Using CWM, supersu shows as successfully installed, but when I boot into the OS, root checker shows my phone is not rooted. Knox seems to obstruct every attempt I make to disable it as well. I keep getting these 'knox stopped etc...from working messages'.
I'm at my wits end. I can't revert back to an older rom, I can't root and modify any existing 4.3 roms.
I want to try everything before I have to ship the phone off to a repairer who may charge me hundreds of dollars to fix the phone.

[Q] S5 Stuck at Boot Animation With Blue LED After Stock Flash

I searched and found nothing exactly like what I was experiencing and nothing I hadn't already tried. Hopefully someone has seen this before. I HAD a nice rooted stock SM-G900A 4.4.4 and now I have a flashy gold brick (soft). I rooted by downgrading the kernel to use towelroot then flashed stock kernel back. Everything worked fine for about a week or so. I'm not sure at what point I started having issues exactly so I'm not sure if an app or mild mod could have caused my issues. The only thing I had done was use SuperSU to block Knox and change the terrible TW stock sounds to standard ogg clicks and what not. The trouble started with the camera. I opened my camera and the screen would flash green then I would have red ghost images in a pattern on the screen. The pictures I took had the same effect when viewed in the gallery. If I switched modes the problem would go away with the camera until I closed then opened the camera app again so I assumed it was a software rather than hardware problem. I couldn't find any info on a fix so I did a factory reset. The problem persisted. I decided finally to flash back to stock. That's when it really got bad. After flashing to stock the phone will boot to the Samsung animation with the swoosh, freeze there for a few seconds without completing the boot animation then the screen shuts off and the phone becomes unresponsive. The only signs of life is the blue LED is constant lit. I have to do a battery pull to start over. I have flashed just the PDA and I have flashed the whole shootin match (except for BL) and I get the same results. I have tried stock tar files from a couple different sources. It will go into download mode as well as stock recovery where I tried a factory reset after flashing. PLEASE HELP!

So I flashed OA1 stock kernel and got it to boot. Of course now I get the Update interrupted message when I try for the OTA to anything newer than the 4.4.2 it's running. And after 8 hours of messing with this gem the camera issue persists.

Acer904 said:
So I flashed OA1 stock kernel and got it to boot. Of course now I get the Update interrupted message when I try for the OTA to anything newer than the 4.4.2 it's running. And after 8 hours of messing with this gem the camera issue persists.
Click to expand...
Click to collapse
Go here and flash back to NCE. Then take the OTAs.
http://forum.xda-developers.com/showthread.php?p=60012961
Sent from my SAMSUNG-SM-G900A

That is what I ended up doing just an hour before your reply and all is well again. I suppose my first attempt to go back to NCE didn't work because I didn't use the downgrade flash, just a regular 4.4.2 stock. There must be a difference between the two. The OTAs still wouldn't work so I ended up installing the updates from external sd. The lollipop OTA is downloading fine though. Thanks for confirming I FINALLY went the right route. This root screw up wasn't as bad as my last (efs S3 debacle) but it still took too many hours to fix.

Acer904 said:
That is what I ended up doing just an hour before your reply and all is well again. I suppose my first attempt to go back to NCE didn't work because I didn't use the downgrade flash, just a regular 4.4.2 stock. There must be a difference between the two. The OTAs still wouldn't work so I ended up installing the updates from external sd. The lollipop OTA is downloading fine though. Thanks for confirming I FINALLY went the right route. This root screw up wasn't as bad as my last (efs S3 debacle) but it still took too many hours to fix.
Click to expand...
Click to collapse
If you take the 5.0 ota you won't be able to root. Just FYI. There is no root for it yet. There is a pay however in the general section on how to upgrade to 5.0 and keep root.

SM-G870A stuck at logo

I'm currently stuck at the s5 active logo screen and then it boots into recovery. I've tried flashing the full odin.rar (yes I extracted it) and it fails everytime. I get the message "Sw REV CHeck Fail: [aboot]Fused 2> Binary 1. I've already tried wiping the data from the recovery menu. Nothing is working.

We need more info. What were you attempting to do and from what ROM. Are you sure you are using the proper ROM 900 or 870?

I was attempting to downgrade back to stock from 5.0 and hit the stock kernel instead of the firmware accidently when in odin. And yes I am absolutely sure i'm using the 870 rom.
Edit: What if I use a stock img and a PIT file for the phone? OR is it because I need a 5.0 lollipop firmware to flash through odin?
Edit number 2: okay I'm stupid, im on G870AUCU2BOF3. I'm going to have to reflash the of3 zip aren't I?

Okay so I found the OF3 cfg on another thread and was able to load it and flash it and get my phone working! Now, the next question is can I root in my situation or downgrade or am I just stuck?
Edit: Going to wait for a possible root! Mod can close this thread.

if you loaded the 2400258.cfg you probably loaded the OF3 bootloader as well and now you can't go back. No root at this time and it doesn't look good for the future.

Cloudsdabomb said:
Okay so I found the OF3 cfg on another thread and was able to load it and flash it and get my phone working! Now, the next question is can I root in my situation or downgrade or am I just stuck?
Edit: Going to wait for a possible root! Mod can close this thread.
Click to expand...
Click to collapse
At command prompt type without the qoutes.
"getprop ro.bootloader"
Then paste output.
Sent from my SAMSUNG-SM-G870A using Tapatalk

If you took the of3 ota or are otherwise on the of3 bootloader your stuck there....no downgrade or root as of this time.

Me too
I am in a similar situation. Saturday I was on a rooted 4.4.2, flashed a stock unrooted 4.4.2 with Odin (G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5), let AT&T update me to 4.4.4, installed the old kernel with Odin (G870A_NE4_Stock_Kernel.tar.md5), rooted with towelroot, installed the new kernel with Odin (G870A_OA1_Stock_Kernel.tar.md5), updated to 5.0 with Odin and it retained root. However, certain things such as XPosed didn't work and I really really hated the white notification drawer so I just want to go back. I tried flashing the stock 4.4.2 in Odin again and it said success. It restarts and seems to be working but gets stuck on the AT&T logo. Now if I restart it always sticks on the AT&T logo even when I flash again. I don't know what else to try. A different file? Is there a way to go back to KitKat?
Update: I got into recovery mode (I kept trying vol up, vol down, power but it's actually vol up, home, power). I wiped the cache and did a data reset and restarted the phone. It worked! I'm excited to have a black notification screen again

pgross41 said:
I am in a similar situation. Saturday I was on a rooted 4.4.2, flashed a stock unrooted 4.4.2 with Odin (G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5), let AT&T update me to 4.4.4, installed the old kernel with Odin (G870A_NE4_Stock_Kernel.tar.md5), rooted with towelroot, installed the new kernel with Odin (G870A_OA1_Stock_Kernel.tar.md5), updated to 5.0 with Odin and it retained root. However, certain things such as XPosed didn't work and I really really hated the white notification drawer so I just want to go back. I tried flashing the stock 4.4.2 in Odin again and it said success. It restarts and seems to be working but gets stuck on the AT&T logo. Now if I restart it always sticks on the AT&T logo even when I flash again. I don't know what else to try. A different file? Is there a way to go back to KitKat?
Update: I got into recovery mode (I kept trying vol up, vol down, power but it's actually vol up, home, power). I wiped the cache and did a data reset and restarted the phone. It worked! I'm excited to have a black notification screen again
Click to expand...
Click to collapse
How long did you have to wait for your phone to boot all the way up from the ATT logo? Mine is doing exactly the same thing and I've flashed all kinds of kernels via odin and heimdall with no affect. None of the various fixes I've found have helped, including trying to re-apply the OTA file (system just won't do it). All I wanted was to unroot. Awesome.

The first boot can take a while but if it lasts more than 10 minutes it's probably not going to happen. I've gotten it stuck there twice since my last post and I'm always able to salvage it by going into recovery mode (vol up, home, power while powered off). Wipe the cache and data reset and it should be a fresh start like out of the box new.

Hm. So the only real two options are take it in to AT&T and hope they have the full stock G870AUCU2BOF3 image to flash over (since Samsung locked down their bootloader so hard, so downgrading is impossible :good: ) or hope they release G870AUCU2BOF3 on SamMobile/Kies/Smart Switch. This is like the new hard brick... potentially it's salvageable but the company (I'm guessing AT&T here since this is an AT&T exclusive phone) is just screwing us. Guess I'll try the walk of shame to AT&T. Or maybe putting in a claim like that one person did, get a whole new phone because of a mysterious cut on the rear panel seal...

Alright, took it in to AT&T and sure enough they had the full 5.0 image available so after signing a no-return data waiver (didn't even confirm my AT&T account or ask for any ID) the tech took my phone in the back and flashed it back to stock. First boot still showed the "custom" with unlocked padlock on the boot screen but after I rebooted it, I guess it updated the bootloader because it was back to normal.
No more root and he confirmed there's no way to go back to 4.4 once you go up to 5.0, so if you want root, I'd suggest staying away from 5.0. At least now I can use my phone again. Just thought I'd post this up in case anyone wasn't sure if AT&T would actually be able to reflash stock 5.0 and at the very least get your phone working again... enough to put on ebay and get a Moto or some other brand that doesn't lock down the bootloader so hard.
Edit: note the first boot will take a few minutes but I knew it worked when there was a quick vibe and the notification light went from pulsing blue to off. Maybe 4-5 minutes.

retro486 said:
Alright, took it in to AT&T and sure enough they had the full 5.0 image available so after signing a no-return data waiver (didn't even confirm my AT&T account or ask for any ID) the tech took my phone in the back and flashed it back to stock. First boot still showed the "custom" with unlocked padlock on the boot screen but after I rebooted it, I guess it updated the bootloader because it was back to normal.
No more root and he confirmed there's no way to go back to 4.4 once you go up to 5.0, so if you want root, I'd suggest staying away from 5.0. At least now I can use my phone again. Just thought I'd post this up in case anyone wasn't sure if AT&T would actually be able to reflash stock 5.0 and at the very least get your phone working again... enough to put on ebay and get a Moto or some other brand that doesn't lock down the bootloader so hard.
Edit: note the first boot will take a few minutes but I knew it worked when there was a quick vibe and the notification light went from pulsing blue to off. Maybe 4-5 minutes.
Click to expand...
Click to collapse
It's not Samsung that locks down the bootloader, it's AT&T. the T-Mobile Version doesn't have a locked bootloader and is easily rooted . Just have to SIM unlock it and you can use T-Mobile phone on AT&T network.

Delete

ROM Flash not working - multiple attempts, different ROMs

I soft bricked my Sprint HTC One M7 and can't get a new ROM working. I'll start by saying I am probably in over my head and never should have done this to begin with. On the bright side, this is a backup device essentially being used as a toy. I have spent hours trying different things and searching the forums without finding any threads with the same issue. My apologies in advance if there is a thread I could have read but I could not find one. So, on to what I have done and the current issues I am having.
I'm not sure all of this background is necessary but it can't hurt. I successfully unlocked the phone, loaded TWRP, and I thought, rooted the phone, all using the guide on htconeroot.com. I attempted to run a program that requires root access and it said "no root access". I then used fastboot to load SuperSU 2.46 and it all went south. After I loaded SuperSU 2.46, the phone hung on the HTC One load screen.
At this point, I decided I would just Flash a new ROM to the phone. After spending hours trying to get adb to recognize the phone (a whole different story), I finally managed to get adb sideload to work and flashed the most recent version of Android Revolution. I went through the entire install process and got a message saying the install was successful. However, when the phone rebooted, as it was loading it switched to say recovery at the top and loaded into TWRP. I noticed the message icon at the bottom, center of the screen and tapped it. It switched to a gray screen which said "updating partition details..." at the bottom. It just hangs on that screen. I wiped cache with no luck and had same result when I re-flashed.
I tried Viper ROM 8.0 and had the exact same issue as Revolution.
I attempted Bad Boyz 1.4 which got a little further but still wouldn't load. I tried Bad Boyz 1.2 to see if their ROM with Sense 5.0 would work. That version said install successful and rebooted. I got really excited when it showed updating Android and started counting through app updates. It got to the unlock screen with the time and HTC default background picture. When I pull up the lock to unlock the phone, I get error messages that messages stopped unexpectedly and HTC Sense stopped unexpectedly. It then sits on a white screen with the green HTC logo for ~10 seconds and then reboots. If I let it go without trying to unlock it, it still reboots after 20-30 seconds, caught in an unending boot loop.
I am at a loss at this point. Do I try a few other ROMs until I find one that works? Am I doing something wrong? I should add that the guide I used said nothing about a Nandroid backup so I don't have one ?, and I really don't want to go back to stock anyway.
Thanks in advance for any help.

Bucknut816 said:
I soft bricked my Sprint HTC One M7 and can't get a new ROM working. I'll start by saying I am probably in over my head and never should have done this to begin with. On the bright side, this is a backup device essentially being used as a toy. I have spent hours trying different things and searching the forums without finding any threads with the same issue. My apologies in advance if there is a thread I could have read but I could not find one. So, on to what I have done and the current issues I am having.
I'm not sure all of this background is necessary but it can't hurt. I successfully unlocked the phone, loaded TWRP, and I thought, rooted the phone, all using the guide on htconeroot.com. I attempted to run a program that requires root access and it said "no root access". I then used fastboot to load SuperSU 2.46 and it all went south. After I loaded SuperSU 2.46, the phone hung on the HTC One load screen.
At this point, I decided I would just Flash a new ROM to the phone. After spending hours trying to get adb to recognize the phone (a whole different story), I finally managed to get adb sideload to work and flashed the most recent version of Android Revolution. I went through the entire install process and got a message saying the install was successful. However, when the phone rebooted, as it was loading it switched to say recovery at the top and loaded into TWRP. I noticed the message icon at the bottom, center of the screen and tapped it. It switched to a gray screen which said "updating partition details..." at the bottom. It just hangs on that screen. I wiped cache with no luck and had same result when I re-flashed.
I tried Viper ROM 8.0 and had the exact same issue as Revolution.
I attempted Bad Boyz 1.4 which got a little further but still wouldn't load. I tried Bad Boyz 1.2 to see if their ROM with Sense 5.0 would work. That version said install successful and rebooted. I got really excited when it showed updating Android and started counting through app updates. It got to the unlock screen with the time and HTC default background picture. When I pull up the lock to unlock the phone, I get error messages that messages stopped unexpectedly and HTC Sense stopped unexpectedly. It then sits on a white screen with the green HTC logo for ~10 seconds and then reboots. If I let it go without trying to unlock it, it still reboots after 20-30 seconds, caught in an unending boot loop.
I am at a loss at this point. Do I try a few other ROMs until I find one that works? Am I doing something wrong? I should add that the guide I used said nothing about a Nandroid backup so I don't have one ?, and I really don't want to go back to stock anyway.
Thanks in advance for any help.
Click to expand...
Click to collapse
You have a CDMA Sprint htc one (M7WLS variant) ARHD is a rom for GSM htc one (M7_UL or M7_U variants). You can only flash custom recovery, custom roms, kernels ect that are made for the Sprint HTC One (M7WLS).
So you can flash twrp for sprint, then flash a sprint custom rom
or
return to your stock rom using a sprint RUU.
You can find the sprint roms in the "Sprint HTC One" section of xda. TWRP recovery for sprint can be found on their website, the filename should ends with "wls.img"
If your phone was running on android lollipop then using a lower version than supersu2.46 is what caused the bootloop. Thats why you shouldn't follow outdated guides from 2013 like the one at htconeroot.com
We can help you flashing the custom recovery/rom or the RUU, its up to you.

Thanks for the quick reply. I probably should have realized the CDMA vs GSM issue. I used to sell Sprint phones 20 years ago.
I would rather go with a custom ROM on the phone without all of the bloatware/sprint garbage.
I understand the issue with ARHD but what about Bad Boyz? I am using their Sprint ROM v 1.2 from the Sprint M7 section with no luck. It loads Android all the way to the lock screen with the time, status bar, and sense skyscraper wallpaper but then crashes. I tried 1.4 first and it got to the unlock screen but no status bar or sense background (skyscraper wallpaper).
You mention TWRP for Sprint. Is there a specific Sprint version and if I used a different version would it have gotten that far? Should I install a different version of TWRP and try flashing Bad Boyz again?

Bucknut816 said:
Thanks for the quick reply. I probably should have realized the CDMA vs GSM issue. I used to sell Sprint phones 20 years ago.
I would rather go with a custom ROM on the phone without all of the bloatware/sprint garbage.
I understand the issue with ARHD but what about Bad Boyz? I am using their Sprint ROM v 1.2 from the Sprint M7 section with no luck. It loads Android all the way to the lock screen with the time, status bar, and sense skyscraper wallpaper but then crashes. I tried 1.4 first and it got to the unlock screen but no status bar or sense background (skyscraper wallpaper).
You mention TWRP for Sprint. Is there a specific Sprint version and if I used a different version would it have gotten that far? Should I install a different version of TWRP and try flashing Bad Boyz again?
Click to expand...
Click to collapse
If there is a specific version of twrp mentioned in bad boyz thread, use that one. Otherwise any recent version should work but yes it must absolutely be a sprint twrp recovery.
Here are all the sprint version: https://dl.twrp.me/m7wls/
The M7_UL have different partition layout than the Sprint version (see both links below). The kernel (/boot partition), the OS (/system partition) and the radio (/radio) are not located at the same place on the memory. If flashing a M7_UL rom a Sprint phone you'll end up with the OS flashed on the Kernel partition, the Kernel flashed on the radio partition etc... This should be easily fixed by re-flashing a custom rom (if the rom does include its own kernel and radio to overwirte the bad flash). In the worst case, you'll have to flash a RUU to fix everything and then relfash sprint twrp and a sprint custom rom
http://forum.xda-developers.com/showthread.php?t=2317621
http://forum.xda-developers.com/showthread.php?t=2236254

Thanks for all the help. I was able to work on it again last night. I updated TWRP and was able to get viper ROM loaded and working...mostly. I had to delete HTCSetupwiz.apk to get out of the hands-free activation loop. The only problem is, the home key does not work. I get the haptic response from it but it doesn't do anything.
I tried Viper 8.0 and 9.0 and had same issue. I tried to switch to Bad Boyz and adb was hanging at ~7%. I am feeling much more comfortable with all of this and I think I can fix the loading issue with Bad Boyz. I just tired of fiddling with it last night. Before I do that, any idea how to get the home key working with Viper?
Would it be best to flash the ruu and start over just to make sure there are no lingering problems from screwing up the partitions?
Thanks again for all the help.

alray said:
If there is a specific version of twrp mentioned in bad boyz thread, use that one. Otherwise any recent version should work but yes it must absolutely be a sprint twrp recovery.
Here are all the sprint version: https://dl.twrp.me/m7wls/
Click to expand...
Click to collapse
Sorry to bug in... yeah I know, no need to tell me, people have been telling me plenty enough of their kind thoughts..., but the universal builds http://android.cmphys.com/twrp-m7/
should work on M7_U, M7_UL, M7_WLS, M7_WLV
they use "by-name" partitions, etc
maybe even the official builds, as mdmower is the maintainer, but unsure, since I haven't checked.
Obviously, still doesn't allow you flash a ROM not meant for your particular device, especially that many installer-scripts still use hardcoded mmcbkls, which would seriously break things
hmm, that reminds me.... have to check on something else too

Note 4 problems after marshmallow and tmobile update, am trying to root/problems

My note 4 was bought used, no warranty. When I bought it, it was rooted, but no custom rom, worked great. Once lollipop came out, I wiped and returned to non-root and was able to get the update through tmobile. Didn't bother rerooting as things were ok. Marshmallow udpate came, and I noticed a lot of screen lag. Less than a week ago, tmobile did some sort of update and now, the phone shuts off and restarts on it's own, has very slow screen response (nothing, and then tries to do the same function 10 times in a row, messaging is very slow, types the same words several times over). I did a factory re-set twice. Once, I reloaded all my favorite apps, etc. still bad, so then I did factory reset but did not add anything or bring in my contacts, etc. I am planning on buying the note 7 in a 3-4 months, but in the meantime, would like to continue to use my note 4. I tried doing the rooting method using odin, it appeared to work ok (got the successful notice), triggered the knox thing, but..when I use a root checker, it says phone is not rooted. I am hoping that by rooting and putting a new rom on there I can fix this thing in the interim. So..suggestions on what to do next? Let me know what additional information you need. Could it be the phone itself and not the software? Suggestions on a cheap interim phone? links to relevant threads also appreciated. Is there a better way to wipe everything and start new that I am did not do? I did a factory reset. I have two batteries, which I changed out intermittently to see if it as a bad battery. Android version 6.0.1, security patch level july 1, 2016 Kernel 3.10.40-7804088
Knox version 2.6

You need to give more information on what you did to root. What version is your phone, what files did you odin, and did you flash SuperSU?

more info
goosa23 said:
You need to give more information on what you did to root. What version is your phone, what files did you odin, and did you flash SuperSU?
Click to expand...
Click to collapse
No to supersu? it's sm N910t, I think what finally worked what odin 3.9 version and flashed the stock that is meant to go with this particular phone to downgrade it down to lollipop. The first few times, I got fail with Odin, but realized that I had marked the option on the phone to keep it from being wiped/flashed if someone found it, once I got that off, I got a successful message. I used the following link and did all of the things mentioned on a link that I am too newbie to be allowed to post, apparently.
but it goes with 3.7 odin, flash the stock firmware from the phone model, and get to the reset button, if successul and then supersu appears.
I got as far as step 8, with odin showing the green 'reset'. But when I went back to the phone, I did not have supersu.
I've tried to do it again, but I get 'fail'

Try out the toolkit that is in the forum. https://tapatalk.com/shareLink?url=...share_tid=2997946&share_fid=3793&share_type=t
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - GALAXY NOTE 4 - Drivers, Root, Recovery + MORE
Sent from my SM-N910T3 using XDA-Developers mobile app

The link takes me to a 404 page not found, is part of it missing?

send me the link by private message so i can see what you are doing?