hey guys, I had a problem where I tried to flash the android 2.2 for the epic 4g to my samsung mesmerize, I know stupid move, I bricked my phone.
I was able to get the phone back on by using the guides using odin restore files that can be found here, http://forum.xda-developers.com/showthread.php?t=782204
I flashed my phone and turned it into a fascinate however I hated it and I figured I have the backup for my memserize let me see what I can do with it. After I followed ALL the steps in the thread above and I had my phone back on with fascinate software I rooted my phone and installed rom manager onto my phone, installed cwm and rebooted my phone into recovery. Once in recovery I restored my phone with the backup of the stock mesmerize I had made, everything went through and the phone reboot, however when it turned back on it was stuck on the samsung screen.
I couldnt get the phone to get past the samsung screen, so I took out the battery, connected my phone to my computer and put the battery back in and held the volume down button to put the phone in download mode.
I used odin to install the uscc kernel I found online, I dont remember where I got it from but I will post the link for it as soon as it is done uploading to dropbox,once it was done installing the kernel my phone reset and it turned back on with the us cellular splash screen and I was back in business with my mesemrize as a mesmerize. I hope this helps anyone who ends up going down the same path I did or wants to install the fascinate roms on their phone becasue you can always revert to mesmerize. I installed the uscellular mesmerize so what I did was I had a backup of my stock us cellular samsung mesmerize backup that I had made with rom manager
Also I dont havent gotten a chance to try going from my stock mesmerize back to the fascinate firmware, I hope this helps those who are on the fascinate firmware and want to go to the mesmerize or for those who want to play around with their phone but are afraid of bricking it!
Enjoy
uscc i500 kernel-http://db.tt/LDbvo2U
Thanks goes out to all the devs and people who posted on these forums to help me get back to my stock mesmerize, sorry if I didnt give credit for the kernel I just dont remember where I found out, also I cant upload the stock uscc backup image of the mesmerize because the files to big and my internets being extremly slow, however I believe it's floating around xda somewhere.
So do the phones share the same modem.bin then?
It would seem that a fascinate could take this route as well?
we already have a vzw modem.bin for both di01 and dj05. so if you want to make vzw fascinate a mezmerize, I would do a nandroid and flash a mezmerize system partition.
Sent from my SCH-I500 using XDA App
So here's my deal. The other day I was doing fine, and I had a version of CM9 that I got from here. I tried the dev's latest version and it was a little wonky so I tried to restore my ClockworkMod backup if his previous version that worked better. And I bumped the cable while it was in process, and that stopped the flash and got me stuck with a non-booting system.
So then I decided I'd reset the phone, re-root, and then I could restore a backup. The first part went good, and then without thinking I accepted Verizon's update.
I found someone saying that I could flash this non-Verizon SBF to it, and it worked but it's for some "nTelus" carrier that apparently isn't here in Michigan and I can't figure out how to put Verizon on it. I tried *228 and it gave me the "Activating your phone" screen but the robovoice on the phone just told me that I wasn't authorized to do something and then said something in Spanish.
I know I can just put Verizon's new ROM on there and it'll work but I prefer to have CM7 or CM9, and either way I definitely don't want their crapware. ClockworkMod is the only backup I have but it obviously does me no good when the phone isn't rooted so I can install ClockworkMod.
So my question is this: is there a way I can root Verizon's new ROM, or revert to an old ROM, and if not then is there a way to make the nTelus ROM know that it should be using Verizon's network?
You have to flash the non Verizon SBF (version .604) but you cannot use RSD Lite, you just use the Linux method.
Now you need to use RSD Lite to return your phone to stock Verizon .621. This will fix your activation problem.
Then, download 1KDS's .604 Live Linux CD and use it to flash the rootable SBF.
Sent from my DROIDX using Tapatalk 2
Thanks, I'll try that when I get home.
Anyways, something I'm about to try, I'll let you know the results. I've found a small section of text in these files that appears to have the Access Point Names and connection data for the carriers. In the nTelos file there's only one carrier, in the Verizon file there's Verizon, ATT, and others. So I'm going to copy-paste-pray and I'll let you know how it works. If it goes smoothly I'll post the resulting file somewhere.
EDIT: Nope, it didn't work. C'est la vie.
OK so it sorta worked... I guess. But now I have no data connection...
Great.
Hello everyone! I'm brand new to the forums so if I am breaking any rule or regulation, just give me a heads up. So, some basic information about my predicament.
- own a Samsung Galaxy Note 3 from Verizon.
- I use t-mobile network. Works great with no problems.
- phone was successfully rooted via towel root.
I was looking to get cynagenmod on the phone so I started looking up guides and such. Only thing I wasn't aware of was that carrier branded versions can't have their recovery flashed. That said, I used flashify and the clockwork apk. The app did its job, killed the stock recovery, but couldn't load the new one. Now the phone says error, no recovery when trying to access it during boot.
It should be said that the phone still boots and works normally but I really want to get the recovery working so I can at least try again the right way to get cynagenmod working.
My question is, is it possible to get my hands on the stock recovery for my phone and just flash it back to how it was? Basically, how do I fix this problem I put myself in. Of course, I didn't make backups. During the whole process, I figured "if I follow this tutorial word for word, why bother with backups?" look how wrong I was
Any help would be sincerely appreciated. I'm posting this from my replacement phone, not my note 3.
HI many name is Sameer. I bought Samsung S4 from a dealer who sells unlocked and rooted phone.
HE said to me its from outside and its unlocked plus rooted. so i was glad its rooted and unlocked now the problem is i dont see the super su app on the phone but i can use apps that require root access.(weird)
Now when i used to use htc explorer (pico) I never had to install any modems or some baseband thingy so i'm a little confused here.
Goals; I want to install this Rom: JFLTE-GPE
This rom requires latest modem and twrp
Twrp is no biggy i can install it using twrp manager, but i don't know if i can install a modem and i don't even know if i even have to cuz the guy who gave me(mobile) must have installed some modem to make my domestic sim work i live outside US
I want someone to help me on how to install modem and to tell me weither i have to install one or not.
Also i want to know if i install the rom will my device lock and i won't be able to use my domestic sim
I know there are a lot of guides out there, i'm here cuz i couldn't figure them out.
Forgive me for my bad English.
SS of about device for all the info: Screen Shot
I am not absolutely sure about the domestic lock stuff, but when I got my L720, I flashed an entire stock firmware on it, updating the modem, system and everything in the process, yet the phone capability isn't affected in any way. I flashed CM12.1 on it, made a small patch to jump between GSM and CDMA (GPe probably won't need it), and all is well.
Assuming that you don't need to worry about the network problems, you need to learn how to use Odin, and find a latest modem file that's Odin-flashable. Or to save this trouble, you can flash a full latest firmware just like what I did, although this means you'll also have to re-flash your TWRP recovery.
One tip: TWRP is also flashable from Odin, and this is the suggested method.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Hi
really need some help really bad, Im stuck and battery running down.
I have a s7e and I have tried so any times to root it and three times Iv had to take it into have it fixed ie re-flashed
I have recovery installed and can go into that ok.
Iv put suppersu on and no-verity-encrypt-2.2
and thats about as far as iv got cant do any thing more as I dont know what to do.
keeps saying cant mount some thing, did a back up of every thng to sdcard but it said it cant do it.
Its cost me a 150.0 so far getting it re-flashed after I miss it up lol no its not funning
But the other half has saiid she will do some thing really nasty if I have to spend any more on getting it fixed and was told to not do it.
but it got the better of me had another go and now i in a mess again, cant seem to get passed this point.
any help pointers would be great and i will be every so regretful if you can help get this rooted I haveread so much now Im brian dead.
thanks again for any help given.
Hi, I need the ROM for this phone, more specifically, the boot.img file, as the current kernel is for the older, Indian revision of the On5, and my revision, the USA version SM-G550T1, seems not to have any copies of its firmware floating around. I'm running an OS for the SM-G550FY, which has no audio or camera support. Even if the version isn't an exact match, if you bought this phone in the USA, new, in 2016, your boot.img will probably work. I need this kernel guys. Please, if someone has an On5 in the USA, can I please get a copy of your boot.img and possibly system.img? I really care about the boot.img.
Thanks guys
-Subsentient
Firstly, did you try the updated ones at these locations:
http://www.theandroidsoul.com/galaxy-on5-stock-firmware-2-86761/
http://firmwarefile.com/samsung-sm-g550fy
Secondly, why exactly do you need the boot.img, what problem do you think it'll solve? Is there any specific issue with your current ROM that you are trying to solve?
Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.
Subsentient said:
Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.
Click to expand...
Click to collapse
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
prahladyeri said:
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.
Subsentient said:
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.
Click to expand...
Click to collapse
There you are! I just cannot emphasize enough that why don't you guys backup your existing ROMs before flashing a new one? It hardly takes five minutes with CWM/TWRP recovery.
In any case, what happens when you flash the Indian ROM (5.1.1)? I guess that could be your only option.
Otherwise, you can put a request on the CyanogenMod thread for your particular Samsung model.
For future reference, perform device backups and all the research before flashing a custom ROM, not after the fact.
EDIT
If you can contact Samsung support, see if you can manage to get a stock ROM from them that you can flash using ODIN or something.
I contacted them already, they basically told me to go **** myself. The missing ROM is a result of bad parameters I accidentally put in to Heimdall/ODIN flasher. I wanted to back up, but ironically, my first attempt at installing TWRP is what destroyed my ROM.
I've downloaded the kernel source code from Samsung and I'll try compiling it myself. If I create a working boot.img, I'll post it here.
prahladyeri said:
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
boot.img is where the kernel is stored. I know, I decompressed it.
Subsentient said:
boot.img is where the kernel is stored. I know, I decompressed it.
Click to expand...
Click to collapse
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.
prahladyeri said:
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.
Click to expand...
Click to collapse
The kernel on this device does not have loadable module support. It's entirely monolithic. And, I'm having one hell of a time building a kernel this thing is willing to boot.
I really would love just to get a ROM from someone else's SM-G550T or SM-G550T1.
locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know
bandtab said:
locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know
Click to expand...
Click to collapse
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.
Subsentient said:
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.
Click to expand...
Click to collapse
thank you!
however, i can't install twrp to my recovery partition anymore because i got FRP locked, and i can't go into my settings to disable it now. so i think my only option really is via odin. i'll see what i can do with this though, thank you very much. i did have twrp on there before but after i got frp locked i can't go into recovery mode at all.
I've been losing my mind trying to make this work.
I think if I installed the stock recovery.img it may work, but I can't find it in the files you sent. Would you or anyone else be able to make a copy of it for me? I would be eternally indebted to whoever could.
If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.
holydude92 said:
If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.
Click to expand...
Click to collapse
unfortunately smart switch is incompatible with this model phone for the time being.
I got four of these from T-Mobile when we switched from Verizon ($120 for 4 lines). Three of our Verizon phones worked well on T-Mobile (after a few APN tweaks), but my dad's old Galaxy S3 barely worked at all, and when it did, only got Edge for data. So I set one of the On5 phones up for him.
Everything was going great. I put the TWRP recovery on it, rooted it, froze all the bloatware, and backed up/restored his apps from the old S3. However, he wanted me to see if I could restore all his SMS/MMS. I tried restoring that, and the stock Messaging app started FC'ing. I installed Textra, which worked (and saw the old messages), but he never received new texts (even though he could send). So I tried removing Messaging and Textra, as well as the SMS cache (which seemed to be in "Dialer Storage (Phone SMS/MMS). I removed it, but now I'm getting an error every five seconds about "com.android.phone" and can't seem to get rid of it. I tried to restore the dialer storage backup again, but it just seems to sit forever without installing.
I've looked far and wide for a stock ROM... hoping I could just put this mess behind me, but I'm surprised to find it is nowhere to be found.
My other alternative would be to fix the com.android.phone error, but nothing seems to fix it.
Which cynogenmod or any custom os suits for Samsung Galaxy on 5.......please tell me guys.....I am bored with this official os
I was really hoping to come back to this forum and finally see stock ODIN files for this phone. I really, really want to get rid of the MetroPCS ROM I used to fix it.
Has anyone been able to find it?