Related
Hello All,
I think I may have possibly bricked my m8.
I was using cyanogen 11, when I decided to try and flash the GPE rom that is available.
However I did not flash the latest firmware. I am not able to get into fast boot. When I press Power + Volume Down, it takes me too bootloader but no options are available other then press power to reboot.
When it reboots I do get into the rom however, wifi, and service are unavailable for obvious reasons. My Stupidity may have costed me this phone :/ I wasn't able to get s-off with my t mobile variant. It is unlocked, and had TWRP installed.
Any help would be greatly appreciated!
Bricked? But you can get into ROM? Do you even know what a "brick" means?
Just restore your device to Stock and do an OTA to get latest firmware in order to have a working custom ROM on latest firmware. You are T-Mobile, US? Do an RUU, or head over to the Collection thread in General section and download a nandroid backup for your device and restore it from within TWRP(Instructions is also available in the first 2 posts of the Collection Thread).
If you can get it into bootloader/fastboot it ain't "bricked", it's recoverable.
BerndM14 said:
Bricked? But you can get into ROM? Do you even know what a "brick" means?
Just restore your device to Stock and do an OTA to get latest firmware in order to have a working custom ROM on latest firmware. You are T-Mobile, US? Do an RUU, or head over to the Collection thread in General section and download a nandroid backup for your device and restore it from within TWRP(Instructions is also available in the first 2 posts of the Collection Thread).
If you can get it into bootloader/fastboot it ain't "bricked", it's recoverable.
Click to expand...
Click to collapse
Okay maybe not bricked but I messed it up quite badly, Im not able to get it into the recovery or have it be detected via fastboot. I did try and do a ruu to have it be put back to stock but Im not sure how to go about doing that since ruu cannot see it since it isnt in fastboot... :/
Did you Make sure you update you SDK. Only the latest fastboot and adb will work with lollipop
subarudroid said:
Did you Make sure you update you SDK. Only the latest fastboot and adb will work with lollipop
Click to expand...
Click to collapse
I did get the latest one from the official site, I was able to use it perfectly fine last night. Now however when I try adb shows the device offline, even if I kill and start the server, and disable and renable the debugging, try different ports etc. I can get it to show the device name, but it says offline next to it, I get no prompt on the device. I was reading the gpe doesnt use fastboot, ( I may be wrong) But that would explain why I dont see anything at the bootloader screen, other then press power to reboot the device.
Good news everyone! I was able to fix it in the most impractical way ever.
So why nothing else worked, I did still have access to the rom which of course had no wifi or service. So what I did was install the terminal emulator via browsers onto my phone, from there I was able to type reboot recovery and restore my backup that I had! and wala, whatya know, now it works, and I dont have a useless phone anymore
Hello, it's been a long time since I messed with this but I'm smart. I'm also in a rush (unfortunately) to find a TW-based firmware that I can flash to from CM11.
The end goal is to use the unlock code I just purchased, but that won't work because I'm on CM11, I assume.
I'm knee deep in information, half of which I understand, half of which I think I barely understand.
What information do you need to help me?
From what I understand, being on a 4.4.4 CM 11 I must have a firmware that is at least android 4.3 or higher, is that correct?
If so, what other specs do I need to ensure I don't brick the phone from having the wrong bootloader, modem, ect from being incompatible?
Effectively, I'm tyring to find firmware to get back to any TW-based firmware from CM11 android 4.4.4. (Also somewhat unsure if it needs to be just TW based or 100% stock)
politelyowned said:
Hello, it's been a long time since I messed with this but I'm smart. I'm also in a rush (unfortunately) to find a TW-based firmware that I can flash to from CM11.
The end goal is to use the unlock code I just purchased, but that won't work because I'm on CM11, I assume.
I'm knee deep in information, half of which I understand, half of which I think I barely understand.
What information do you need to help me?
From what I understand, being on a 4.4.4 CM 11 I must have a firmware that is at least android 4.3 or higher, is that correct?
If so, what other specs do I need to ensure I don't brick the phone from having the wrong bootloader, modem, ect from being incompatible?
Effectively, I'm tyring to find firmware to get back to any TW-based firmware from CM11 android 4.4.4. (Also somewhat unsure if it needs to be just TW based or 100% stock)
Click to expand...
Click to collapse
The first thing I would recommend is to verify your bootloader and modem version. There is a playstore app, Phone Info *Samsung*, by vndnguyen that will do this. Or you can use the terminal emulator that is in CM roms and find out with these two commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
All I have seen indicates you will need to be on a stock rom with a stock dialer to use the code. You may even need to unroot before using (I am not sure about root/unroot.) Before recommending any stock rom source, are you using an i747 or an i747M?
dawgdoc said:
The first thing I would recommend is to verify your bootloader and modem version. There is a playstore app, Phone Info *Samsung*, by vndnguyen that will do this. Or you can use the terminal emulator that is in CM roms and find out with these two commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
All I have seen indicates you will need to be on a stock rom with a stock dialer to use the code. You may even need to unroot before using (I am not sure about root/unroot.) Before recommending any stock rom source, are you using an i747 or an i747M?
Click to expand...
Click to collapse
I know that it is an I747. I will comment again when I have the info for bootloader and modem.
So lets assume we find a rom that is; i747 gs3 stock rom and stock dialer; meets android version requirements (which I would love to have confirmed, based on the OP); compatible bootloader and modem; and is rooted, and the unlock code doesn't work. If we assume the unlock failed because it is rooted, is there a way to unroot the phone that doesn't require flashing a different, unrooted, to spec, rom? That is something that I truly don't understand what is happening.
Is there a wiki, or a list, or somewhere I can go to learn more about bootloaders and modems? I don't understand how they play into the overall configuration; such as how they may be X or Y when I'm running CM11, instead of being mandatory for a given configuration. I guess that question is, what prerequisites determine the bootloader and modem options that one may be and can be running or that one can flash successfully.
politelyowned said:
I know that it is an I747. I will comment again when I have the info for bootloader and modem.
So lets assume we find a rom that is; i747 gs3 stock rom and stock dialer; meets android version requirements (which I would love to have confirmed, based on the OP); compatible bootloader and modem; and is rooted, and the unlock code doesn't work. If we assume the unlock failed because it is rooted, is there a way to unroot the phone that doesn't require flashing a different, unrooted, to spec, rom? That is something that I truly don't understand what is happening.
Is there a wiki, or a list, or somewhere I can go to learn more about bootloaders and modems? I don't understand how they play into the overall configuration; such as how they may be X or Y when I'm running CM11, instead of being mandatory for a given configuration. I guess that question is, what prerequisites determine the bootloader and modem options that one may be and can be running or that one can flash successfully.
Click to expand...
Click to collapse
Some of the stock ROMs will remove root, that would be one way to resolve the issue. If you flash a stock image that is rooted, and it is rooted with SuperSu you can use the options in the SuperSu app to either temporarily unroot or to completely remove root.
I don't recall seeing a specific source for info about what bootloader / modem is needed in each situation. Most is accumulated knowledge from reading many posts and threads.
There are variations on what is correct, it all depends on the specifics of a device's status. For example, CM 11 would run on 4.3 bootloaders and modems up until about September of a year ago (or was that two years ago), since then you need to be on 4.4.2 bootloaders and modems. I think the same held true for AOSP based roms. I don't recall seeing where any of the 5.x.x roms have run on 4.3 bootloaders and modems. (Well, I think the devices run but have signal and data issues - both 4.4.x and 5.x.x roms.)
Generally you will see it said that the 4.4.2 Touchwiz based custom roms must be on 4.4.2 bootloaders and modems. In truth there were a number of such roms that would run with the 4.3 bootloader and modem IF one of a few specific kernels were flashed just after the rom was flashed.
Guys need some advice from you Remix OS experts:
I just bought the new Ugoos AM1 android box which has specs almost similar to Unuiga S905 (listed in Jide.com). I have flashed ROMs in phones which would require a recovery that supports it.
I am not sure of the process with these android boxes. How will I go about it? In regards to his I have two questions:
1. Please point me to a thread that can help me step by step to flash the Remix OS, what is the recovery procedure etc., Fortunately this box comes with an option to root if required.
2. Secondly, say I want to go back to the ROM how it shipped with? how do we do this? The official ROM is available from their website just like any other android boxes.
3. For example, the remix ROMs available in the supported devices section at Jide.com - how will the user flash these, (this could cover my question above about recovery etc.,) in that case how do they get back to the official one that came with the device (this is again a repetition of my second question) but in simple terms when you flash back the OEM ROM is there a process that skips flashing via recovery and flash directly via SD card?
4. Or we just simply download the rom and flash using the option under settings to update ROM - we have options to do OTA flash (online update) or download the ROM and update manually. But this is for the OEM ROM. These options come with the box. Will this work if we flash a different ROM? and how do we flash it back to OEM in that case, I guess this is where recovery might come in!?
thanks and looking forward for your help as I can test it on my device.
S
All,
my sgh-i747 WiFi doesn't appear to work. under settings> WiFi slider (OFF)> slide to on (remains off)
next goto WiFi setup screen: no devices listed, buttons at bottom of screen dim/greyed out.
history:
phone was bricked by a forced ATT update. I finally did a rom update/reinstall to push a working stock kernel kitkat 4.4.2
thx
Rob
ALSO i need working links to Lollipop for sgh-1747 using oden
PS: I do ROM , hardware and software updates on data storage systems with petabytes of storage. BUT THIS PHONE MAKES ME FEEL STUPID....
My Hats Off to All Of You Who Hack, Play, or Make Mods for the Phones.
Boot image not matching firmware on your phone can cause wifi to not work. The kernel doesn't have the what it needs to work with the radio you have installed. It is a fairly typical stock rom problem. Custom roms typically have broader support instead of being targeted at a specific firmware.
First step is to figure out what exactly you have on your phone now. Need to know bootloader, modem, and boot image versions since this phone is finicky. Hard bricks are possible, so don't do anything hasty. There's an app in the Play store called phone info samsung by vndnguyen that helps with that. Install it and see what it says you have for bootloader and modem/baseband. Also check in Settings -> About and see what kernel version you have (the app might tell you that too, it has been a long time). Report that all back here and it will help with how to fix it.
Alternately if you don't want to mess with the app enter this in a terminal app or adb shell:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
You won't find an Odin package for lollipop. Samsung never updated this device past kitkat. Anything lollipop or newer would be a custom rom, and those are all custom recovery flashable zips, not Odin.
jason2678 said:
Boot image not matching firmware on your phone can cause wifi to not work. The kernel doesn't have the what it needs to work with the radio you have installed. It is a fairly typical stock rom problem. Custom roms typically have broader support instead of being targeted at a specific firmware.
First step is to figure out what exactly you have on your phone now. Need to know bootloader, modem, and boot image versions since this phone is finicky. Hard bricks are possible, so don't do anything hasty. There's an app in the Play store called phone info samsung by vndnguyen that helps with that. Install it and see what it says you have for bootloader and modem/baseband. Also check in Settings -> About and see what kernel version you have (the app might tell you that too, it has been a long time). Report that all back here and it will help with how to fix it.
Alternately if you don't want to mess with the app enter this in a terminal app or adb shell:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
You won't find an Odin package for lollipop. Samsung never updated this device past kitkat. Anything lollipop or newer would be a custom rom, and those are all custom recovery flashable zips, not Odin.
Click to expand...
Click to collapse
Thank You
jason2678 what you said makes perfect sense to me. like needing a VIN # for a 2002 Toyota to figure out what water pump or alternator because they used 6 different versions of each, LOL
so i would like to use 5.1 lollipop which is a custom ROM i believe, if you can suggest one i will defer to your judgement
but as a fallback suggest a kitkat ROM as well
bootloader I747UCUFNJ1
BASEBAND I747UCUFNJ1
KERNEL VERSION:
3.4.0-1514807
[email protected] #1
32-bit
modem msm8960
please and thank you
respectfully
123RobH
At NJ1 you're not on the latest bootloader and modem, but you're close enough. And your bootloader and modem match. I wouldn't mess with it. You'll be able to run all the latest custom ROMs on that, no problem.
If you want lollipop, look around the development section here. I'm not sure if you'll be able to track down a lollipop rom download linked to XDA. You might have to poke around old uploads for d2att on androidfilehost.com for 5.1.1 roms. I'm pretty partial to slimkat stable 9 on this phone, and it runs fine on NJ1 firmware too.
Oct-Os is probably the most actively supported rom currently. They've moved on to nougat these days. You'll be able to run it on NJ1 too. You might want to give it a shot.
Track down a rom and matching gapps. Then full wipe and flash them with TWRP recovery. If you run into any trouble or have any questions, just ask. I'm pretty certain once you get a custom rom on your phone your wifi problems will go away. Stick to lollipop, marshmallow, or nougat and you'll be fine. Even newer KitKat ROMs will be OK on NJ1.
So as I've looked into it, it appears that nothing has changed here in the 2-3 years since I last explored this issue. I'm talking about the fact that you can't successfully update PRL and profile on CDMA carriers in LOS and AOSP ROMS. The usual behavior if you even have the option in the UX is that you get a force close. I'd love to understand why this hasn't been addressed.. It's a huge reason someone would stay on stock over AOSP/LOS. I saw someone suggesting a Nexus 5 dev had some success using a couple of APKs including OmaDmclient.apk, and a few threads here and on Reddit talking about how it must've been broken by an AOSP contributor, but in any event it still doesn't work. Isn't this something that the LOS team could fix if they wanted to?
The issue with CDMA is that most of the stuff isn't open source. This is why the aosp source code is targeted to GSM. So I sought this will get fixed any time soon.
Same problem... I think
My neighborhood has excellent Sprint 4G LTE coverage and it's much faster than T-Mobile. I happen to use Ting (which allows you to choose between T-Mobile GSM and Sprint CDMA, although to switch from one to the other costs $20). GSM isn't really an option for me.
Anyway, I used to have this problem with my LG Volt LS740. I could work around it by forcing a PRL and profile update on stock and then flashing to Cyanogenmod.
That phone finally bit the dust. I have now inherited my wife's Moto G 2015 (osprey) XT1548. Really nice phone.... but the issue is, the latest stock I can find is Android 6.0. I can activate the phone and get great 4G LTE on stock, but to flash to Lineage OS 14.1 (or AOSP) I have to wipe the device. I simply can't get it to pick up the 4G LTE service on the custom ROM's (tried both). This is a real problem.
As I understand it (admittedly from reading Wikipedia), the PRL contains an "acquisition table" that prescribes the frequencies/modes that the device will communicate on... so I think that's probably my issue. After doing the prescribed wipes in the ROM installation documentation, flashing the ROM, and booting the device, I think I've lost the PRL somewhere in that process.
Is there some way to retrieve the PRL while the device is on stock and put it back when flashing custom? If the PRL is indeed stored on the R-UIM, should I just remove the R-UIM during the first boot? Maybe I'm wrong and the problem isn't really the PRL.
Any thoughts? Please don't tell me to switch to GSM. The GSM coverage here is just plain bad from both carriers who offer it in my neck of the woods.
I have this same exact question. Ting, N910P note 4 that was originally Sprint, and days-old Lineage 16 / Andorid 9.0 . The latest stock rom is 6.0.1, and works fine. Lineage 16 works 99% fine and I'd really rather use that. But LTE doesn't work. If I force it to use 3G only, it actually all works. data, voice, text, bluetooth, gps… and being Lineage, I don't have to try to surgically remove all the spyware and other crapware without breaking it. It's just not in there in the first place. I'd really rather use that.
I would be fine having to extract things from the stock rom and edit files or whatever if it were at least just known what needed to be done. I'm fine with the fact that Lineage nor anyone else can actually include and redistribute any carrier proprietary stuff.
it should be possible
Has anyone figured this out?
I too have devices on ting, fantastically built devices that run amazingly thanks to a solid construction, the support of many many developers who are craft some of the best ROMs for any device I've ever seen, considering the limited specs of the XT1031s. Fortunately/adequately enough though, they only run on 3G Sprint, Boost originally, moved to Ting for their great rates for FreedomPop customers when they bought them out.
Anyway, currently to get a device on ting, I have to flash the latest 5.1 official stock Boost Mobile Rom with the latest radio baseband and firmware and such. A process thats pretty involved. I'm hoping that I can backup the stock image using TWRP, as when I went through the process of reloading the official image through the individual files via mfastboot, I skipped the logo and recovery files, and since I was able to retain my custom logos for boot and bootloaderunlocked screens, and the recovery, I'm hoping to be able to make an image of the stock ROM, which if at all possible, I'm going to do my best to make as bare bones as possible. May start with flashing the bloatware removed version of stock thats available, then going through and removing basically every app on the phone with the exception of settings and anything to do with phone, phone/carrier services, sim toolkit, etc, so I can have the smallest image possible that could maybe be restored everytime/anytime that I want to update the PRL or Profile. Which it looks like theres a new version of each released at a minimum every 3 months, as I just activated another device this way and there was only an incremental update of the last digit. If this works, great. If it doesn't then I hope that theres an answer to the question in the initial post of this thread;
Is there a way to update the CDMA PRL and Profile on a device that is running a custom ROM? If so, is it something the ROM needs to specifically support or is it something that is possible to do with a bundle of apks? Like sim toolkit and the like?
If its ROM related, are there, or would it be possible to take the necessary components from the stock files and install them in Xposed or Magisk? Or perhaps the buttons in the settings panel of the stock rom simply executes a series of commands that can be executed within a terminal CLI on the custom ROM? I assume that since the custom ROM clearly has access to the 3G radio since I can make and recieve calls, I have data, and text messaging (haven't tried MMS, but I assume it works) so why couldn't it do one more thing and initiate the PRL update?
I assume that even the stock rom doesn't ever touch the PRL or Profile, seeing as they remain even after a user data wipe, and are available for the radio to continue to use with custom roms, which means that the radio chip has to be the one storing the PRL Profile, so I bet that the radio also directly downloads those files from the carrier when asked to do so, and the stock rom must only come into play for the base logicstics of it all such as radio-"is this prl/profile a newer version than the one that i have now?" and phone-"yes, download new, purge old, flash new, tell me when done and leave me alone" Since the radio doesn't have its own processor for those sorts of things perhaps? If thats the case, then that should imply that theres nothing particularly proprietary or licensed, etc, that a rom would explicitly need to have in order to initiate these updates since it would never directly need to touch/see the files, just know that they were updated and what version number they are. What also lends me to believe this is the case is the fact that you can't select to downgrade the prl/profile, rollback, or load one manually, at least not that I can see.
So basically I'm saying that I hope it should be something simple to do. And if it is simple to do, you would think that custom roms would be able to read the carrier correctly too? Right now my new device reads "Boost" still. My previous one when I got it on ting I wanna say actually read ting afterwards. But when I loaded ressurrection remix, I had no cell/data/voice nothing, It just kept asking me for a sim card, which this phone doesnt have at all. When I loaded Lineage, everything cell related work. But can't update prl/profile, and carrier reads as "3G Roming Indicator Off" Which idk why thats the case.
Perhaps I'm missing something
Perhaps custom roms are missing a few somethings.
The only sure thing is that carriers need to just not be so greedy/dumb/uselessly difficult, and make giving them money for service easier, preferably without questions. Or at the very least actually provide some security so all this nonsense is at least worth something in the end to the end user, instead of being done so that they can try to spy on your unencrytped texts and calls to sell to advertisers, and selling access to the higest bidders such as the government and bounty hunters, whilst preventing you from restricting that information.