Related
Let me apologize for being a newbie as I come from 5 years of using Windows Mobile and just got my first Tab/Android 2 weeks ago. This is all new to me.
After messing up with some system files and factory applications (like I removed stk.apk and other things) I decided to do a full hardware reset. This is something I did many times in Windows Mobile... whats bad get overwriten in ROM and whats missing gets back where it was. But is seems on this Tab this is not the case.
After the full resetthings only got dramatically worse. All the missing system apps are still missing (I thought they be "restored") and nothing works, just crashes one after the next, cant use anything. I also tried with the system off the method of pressing and holding the “Volume Up” and “Power” buttons at the same time, then after recovery screen appears navigate and select “wipe data / Factory reset” and pressing the “Home” button, but after that and the system re-starts, same thing! All bad.
Can someone please explain to me how to do a full rstore where all system files, all and everythign gets back as it was in the Tab as it was shipped? What a flippin' nightmare... Windows Mobile, I love you!
Thanks in advance.
settings/privacy/factory reset.
natious said:
settings/privacy/factory reset.
Click to expand...
Click to collapse
No no, that doesnt restore anything! All missing files dont get restored. I need a full stock ROM image and restore EVERYTHING. Thats what I dont know where to get and how to do...
VeEuzUKY said:
No no, that doesnt restore anything! All missing files dont get restored. I need a full stock ROM image and restore EVERYTHING. Thats what I dont know where to get and how to do...
Click to expand...
Click to collapse
Yeh i realized that after reading your post properly sorry man, i guess you can just flash one of roms found here, like rotos or modaco's JMI, that would atlest give you a work tab till you can find a stock samsung rom
If you dont have cwm installed you can flash with odin or heidmill (sp)
natious said:
Yeh i realized that after reading your post properly sorry man, i guess you can just flash one of roms found here, like rotos or modaco's JMI, that would atlest give you a work tab till you can find a stock samsung rom
If you dont have cwm installed you can flash with odin or heidmill (sp)
Click to expand...
Click to collapse
Yeah, I enever flashed the Tab. Can U advise me on a stable "OK" ROM? Where can i find odin or heidmill and some sort of a guide to help me step-by-step? I have positively no clue what I am doing... sorry for my ignorance... I feel thoroughly stupid...
I got lucky and found this site. Hope yours is a Verizon Tab
I'm not allowed to post links. But go to google type in "galaxy tab system restore" and click on the "[How TO] Restore VZW Galaxy Tab to stock DJ11" link
It's in the droidforums. net
VeEuzUKY said:
Yeah, I enever flashed the Tab. Can U advise me on a stable "OK" ROM? Where can i find odin or heidmill and some sort of a guide to help me step-by-step? I have positively no clue what I am doing... sorry for my ignorance... I feel thoroughly stupid...
Click to expand...
Click to collapse
First of all, you need to post what "type" of Tab you have, which is generally going to be determined by your country and/or carrier.
Flashing a new Android ROM isn't a particularly complicated process, but it can seem daunting if you've not done it before - this is especially true when using Odin or Heimdall over a "recovery" based flash.
FWIW, the reason your "factory reset" didn't work is because all is essentially does it reformat the /data partition (a generalisation, but close enough for these purposes). On a stock Tab, you cannot mount /system as read/write, so you are unable to change the contents of that partition. This means that on a stock Tab, /system should never change.
However, when you root the device you give yourself the ability to remount /system as read/write and thus make changes which are not going to affected by a factory reset.
Take a look at this thread - lots of useful information there!
Regards,
Dave
foxmeister said:
First of all, you need to post what "type" of Tab you have, which is generally going to be determined by your country and/or carrier.
Flashing a new Android ROM isn't a particularly complicated process, but it can seem daunting if you've not done it before - this is especially true when using Odin or Heimdall over a "recovery" based flash.
FWIW, the reason your "factory reset" didn't work is because all is essentially does it reformat the /data partition (a generalisation, but close enough for these purposes). On a stock Tab, you cannot mount /system as read/write, so you are unable to change the contents of that partition. This means that on a stock Tab, /system should never change.
However, when you root the device you give yourself the ability to remount /system as read/write and thus make changes which are not going to affected by a factory reset.
Take a look at this thread - lots of useful information there!
Regards,
Dave
Click to expand...
Click to collapse
Thanks for the link... yes Ive seen that master thread... I just keep reading from link to link and thread to thread and all gets more complicated, I keep downloading more files and installing more stuff but in the end Im more confused and positively going no where. There is not one simple, from start to finish guideline on how to do the process of wiping all data and installing a new ROM. Ive done this endless times on many phones under WinMo, and with more or less difficulty never had any problems getting this done. But here, the more I read the more utterly chaotically confused I am.
I am yet to have anyone explain what type of Tab I have. Its GSM, I think its Euro, bought in Hong Kong. I have found out all bootloaders and stuff seem to be cleaer and I should be able to flash anything. Its a GT-P1000 and Baseband P1000ZHJJ1. This is all I know.
VeEuzUKY said:
Thanks for the link... yes Ive seen that master thread... I just keep reading from link to link and thread to thread and all gets more complicated, I keep downloading more files and installing more stuff but in the end Im more confused and positively going no where. There is not one simple, from start to finish guideline on how to do the process of wiping all data and installing a new ROM. Ive done this endless times on many phones under WinMo, and with more or less difficulty never had any problems getting this done. But here, the more I read the more utterly chaotically confused I am.
I am yet to have anyone explain what type of Tab I have. Its GSM, I think its Euro, bought in Hong Kong. I have found out all bootloaders and stuff seem to be cleaer and I should be able to flash anything. Its a GT-P1000 and Baseband P1000ZHJJ1. This is all I know.
Click to expand...
Click to collapse
Its pretty much the same as mine then, so i recommend you use modacos kernel and rom and installing cwm
cwm - http://forum.xda-developers.com/showthread.php?t=870690
Kernel - http://forum.xda-developers.com/showthread.php?t=925760
Rom - http://forum.xda-developers.com/showthread.php?t=941423
If you have and external sd card (one that you put into the side of the tab)
You can flash the ext4 kernel via odin, its pretty simple, there will be instructions in the threads.
Are you still able to go on the market? If so download the cwm app and use that so you get the awesome recovery menu and features, you can then use it to flash a new rom and make backups that are really really easy to restore. Seeing it looks like you like to mess around with stuff i suggest it the best way to go.
Hope this helps
Ok thanks for the tips. I have finally managed to get the Tab working again and flashed it with Roto JMI Pre-Rooted Firmware v2. All seems OK at this point. Ill check the links you sent me and follow-up. Flashing Roto JMI Pre-Rooted Firmware v2 with Odin3 1.7 is easy so I hope modacos kernel and rom and installing cwm are easy as well.
A little off topic:
I just got my SGT on Friday and want to root&/flash custom ROM. Gonna definitely root soon...But thinking of holding off on the custom ROM until CM7 is stable or a nice clean Honeycomb ROM is cooked
Does ClockWorkMod require root? I know Titanium Backup does. Can't really do any "fun" things with the tab until it's rooted it seems.
Excuse the long thread title lol..
I've been gently lowering myself into all this tampering with my phone as I've always been a bit of a tinkerer with everything i've ever owned.
So back in march my phone, an unbranded handset on o2 uk was on 2.2.1. My first foray into modifying my handset was to flash the jvk gb firmware. I then rooted it using cf root. All very simple. I then flashed it using cwm with Simply honey 3.2 and then the latest 3.5. No issue.
So this afternoon, I flashed it with the "unspoken ones" kernel just cos I could lol. Something didnt seem right though. There was a bit of lag and I got one or two forced closures so I decided to restore one of the cwm backups I had. Thing is, it hung upon reboot at the i9000 screen, for about 10 minutes so I pulled the battery. Now I couldnt get it restarted. Panic set in. This was my first proper issue and I just wished I was back in march on 2.2.1 again.
As said, couldnt get it started so went hunting some advice. Install a base stock rom with 3 files and a 512 pit. I struggled. Could I find 3 files ? Nope. Not on samfirmware. Every file I downloaded was one file. JP1 JPU JPY. All 1 file. So. As JPY was the firmware I was on originally, I chose the 1 file version, put the phone in download mode and flashed it via odin. It worked !!! And then I plugged it into kies and up popped the box, I have an firmware update ! JPO GB! So i installed that. I'm quite surprised that I got the update because you always see lots of threads regarding people being unable to update by kies once they have modified their phones. Why did mine work? Because the handset in unbranded perhaps ?
Anyway, I wanted to get back to the Simply Honey rom because it ran really well and the battery life is fantastic but Simone hasnt done a version based on JVO yet as far as I could tell so I thought, I know, I'll root with cf root, again and try that backup again using cwm. And it worked, and here I am back where I was earlier today ! Ace ! lol
Sorry about the essay but I'm sure that there are some questions in there worth answering.. ?...and also to serve as a bit of help to those that find themselves in a dodgy situation. Just calm down, search for the advice, it is out there and do as it says and everything will be cool
Posted from my restored and working handset...
the files you download from samfirmware are rar files (have a .rar extention). This means you need to decompress them into a folder and the "three files" will be in there. You need a rar extractor app. You can use 7-zip which is free.
You need odin (or ezodin or heimdal) to flash the stock rom but I am sure you know that already. There are a few guides around for all tools.
There is a lot of information here, especially in the "sticky" posts. If you feel like learning what you are doing rather than copy instructions (as I think you do), it may be a good idea to go through them.
Anyway you got your phone working in the end so that's good!
simple solution when an install hangs is only to reflash the kernel in odin: that restarts the phone.
cwm is not invincible and the restored rom is there but the phone hangs on the boot because of the kernel hiccup. Reflashing the kernel to the one you now want will allow the phone to boot and access the rom that matches -- you do have to ensure the recovery version rom and the kernel you are flashing are in sync.
Persist. You only really panic the first time this happens -- after that you know it is a possibility and how to fix it.
Worst case scenario: pull the battery, reinsert, go to download mode and reflash the kernel and base rom of your choice. At least now you have a clean phone!
Two things are important to remember: (1) always do a backup before installing a new rom or kernel and (2) use titanium backup for all applications -- easy to restore everything.
Also I find it easier to use google calender and my internet email as bases for dates, appointments and contacts -- that way if I loose everything on the phone I can quickly reload my data by sync with online accounts once I have the phone "rebuilt".
I want say thanks to all they great people on this forums out who help us in our times of needs.
Here is my story:
In preparation to the upcoming gingerbread update for my i9000m I decided to disable my lagfix and revert back to an RFS filesystem. I had installed a new kernel. I had replaced my stock kernel with a Kernel switcher app because I did not want to use Odin. Having an i9000m that was plagued with a failed motherboard back in December, I did not want to have another brick in my hand.
So Friday night, I went in the recovery boot. Disabled Ext4 in favour of RFS. Rebooted to convert the filesystem. Went I went from RFS to EXT4 the whole thing took approximately 20 minutes. After an hour of converting, it was stuck on one file for about 45 minutes that is when I should I ask instead of act. I pulled the battery and hoped for the best. It restarted. The filesystem seemed to have been converted and it booted into android without an itch. I decided then to revert back to the stock kernel which is when I brick my phone. It did not reboot. After the animation screen it never loaded into Android. After wiping out and trying for format my SD card, I got over my fear of Odin and decided to flash the custom kernel once again, however, instead of flashing it through PDA, I flashed it through CSC. My bad… At this point I was able to see the Galaxy S I9000m screen but never loaded the animation. I thought I was screwed badly. I tried to find over the forum the darn CSC tar file for the KC1 update but couldn’t find it all by it self. After reading a few post I registered myself over at samfirmware, downloaded the whole update, flash it through Odin again because at least I was able to load into download mode. Now, I was able to see the animation screen once more but nothing after that. I loaded into recovery mode; saw the notice that it cannot mount the E:something, which I suspect was there all along. I search over the forum for the solution. Found it, applied the missing file through Odin. Phone booted into android perfectly.
I made every the mistakes that I should not have done, primarily not searching for a solution first before acting. I acted before reading and I screw up my phone and lost all my data because of that. If I had read the error that my phone was giving me and applied the patch, I would still have all of my information and all my apps, but this is the price I accept to pay for my mistakes. I have learned my lesson but also have learned that Odin is very easy to use.
Thanks again to all the people who keep this forum alive with solutions and great apps, ROMs and kernel.
*I flashed a CM12.1 nightly on top of one that was a couple days old, and the new one had all kinds of force closes. This was through CM's internal update function, which sets a recovery script and reboots into recovery to install it (which BTW failed).
So I went into TWRP and flashed the backup I made not a couple hours earlier. But now I have kind of a bootloop. Most of the time, the LG logo shows up, then it just reboots back into recovery. One time it got stuck on the logo, and I was able to see it with ADB but it told me init.sh was missing when I tried to adb shell into it.
I have three backups I tried restoring, which had /boot, /recovery, /system and /data, plus I wiped the Dalvik cache and /cache, but nothing I've tried will kick this thing loose. I've even tried formatting it back to EXT4 from F2FS, and erasing and recreating the partitions in fastboot. It seems like there's a flag somewhere telling it to reboot into recovery, but I can't find anything pertinent online. I'm really at a loss as to how to fix it, and out of ideas now.
Have you tried using the lg support tool to bring the phone back to stock?
audit13 said:
Have you tried using the lg support tool to bring the phone back to stock?
Click to expand...
Click to collapse
Yeah, I was going to edit the OP to say I've also now tried to flash back to stock, using the 20a KDZ and the LG Flash Tool 2014. When it gets to the point where it's actually about to flash, it says "USB is not connected". I have all the latest drivers, and have tried different cords, to no avail. It has been transferring files while connected in TWRP, so I'm not sure what that's about.
What about using the lg support tool to flash stock?
LG Mobile Support Tool is what LG Flash Tool calls to actually flash the ROM (otherwise you have to depend on what LGMST decides to download). It saw the phone the last time I used it, but wouldn't show LP 5.0.2 as being an available update, even though it had been released.
This thread has the instructions I've been working off of, which was posted around the time the ROM was released. It "should" work, it just doesn't. If I'm not mistaken, there may be another tool you can use, but I haven't been able to find it.
There's one other way I suppose I could go about this, but it would be delicate. I could push all the individual IMG files from a ZIP archive I have of the KDZ, but I don't know what all the partition names are, and there are like 10 of them, including laf, aboot, etc. For example, the /data partition is actually named "userdata" when you use fastboot flash.
I didn't know about the difference between the LGMST and Flash Tool.
All I know is that the LGMST was able to download the correct LP ROM for my phone, install it, and get me back to stock after I screwed things up when trying to get root.
i have same problems , here is my solutions
- use SKR tool -> 4 .fix utility -> 5.unbrick ,
if u want go back to stock, try use TOT file to go back JB
cant use kdz way
Dễ.Thương said:
i have same problems , here is my solutions
- use SKR tool -> 4 .fix utility -> 5.unbrick ,
if u want go back to stock, try use TOT file to go back JB
cant use kdz way
Click to expand...
Click to collapse
+Thanks, I have never even heard of that. But I'll give it a try. By any chance were you using F2FS?
Though I am not sure, but I'm leaning towards some kind of hardware failure -- this is a refurbished phone, so there's no telling what it's been through inside. T-Mobile sent another one overnight, which I should have in a few hours, but I still need to clean up this one if it has to go back.
audit13 said:
I didn't know about the difference between the LGMST and Flash Tool.
All I know is that the LGMST was able to download the correct LP ROM for my phone, install it, and get me back to stock after I screwed things up when trying to get root.
Click to expand...
Click to collapse
Mine told me I had the latest version, which is peculiar. Was your phone rooted at the time? Because I could understand it refusing in that case: I ran into a soft-brick on a D800 because of an OTA once. Otherwise, I'm not sure why one would work, and the other wouldn't.
voxluna said:
+Thanks, I have never even heard of that. But I'll give it a try. By any chance were you using F2FS?
Though I am not sure, but I'm leaning towards some kind of hardware failure -- this is a refurbished phone, so there's no telling what it's been through inside. T-Mobile sent another one overnight, which I should have in a few hours, but I still need to clean up this one if it has to go back.
Click to expand...
Click to collapse
i dont use f2fs , just use SKR tool with luck but i think u need flash a stock rom first
Dễ.Thương said:
i dont use f2fs , just use SKR tool with luck but i think u need flash a stock rom first
Click to expand...
Click to collapse
The reason I ask is that I had a debate in another thread about using F2FS instead of EXT4 for the filesystem. Most people suggested it's buggy and causes problems, so I wondered if that's what happened here.
When I used lgmst, my phone was giving me boot certification errors. I played around some more with it and then it would only go to download mode.
I connect the phone in download mode and the program downloaded and installed the latest LP rom for my 802 from UAE.
audit13 said:
When I used lgmst, my phone was giving me boot certification errors. I played around some more with it and then it would only go to download mode.
I connect the phone in download mode and the program downloaded and installed the latest LP rom for my 802 from UAE.
Click to expand...
Click to collapse
If u can boot your phone ,try to use Tot file , lg flash tool doesnt work anymore
LGMST fixed my 802 so there was no need for a tot file.
audit13 said:
When I used lgmst, my phone was giving me boot certification errors. I played around some more with it and then it would only go to download mode.
I connect the phone in download mode and the program downloaded and installed the latest LP rom for my 802 from UAE.
Click to expand...
Click to collapse
I wish I had a D802 -- it's ubiquitous, and thus has more support on XDA, I think. I'm not sure why T-Mobile chose to have a customized model. Same goes for AT&T, since they both use the same frequencies... and I don't know what the hell Verizon was thinking with those hideous buttons. The only differences I see between most of them is the SAR.
I am not sure that all g2 phones support the same frequencies. My 802 will not connect to LTE in Canada.
audit13 said:
I am not sure that all g2 phones support the same frequencies. My 802 will not connect to LTE in Canada.
Click to expand...
Click to collapse
Well, they don't, especially Verizon and Sprint being entirely incompatible because of CDMA. I looked it up just now, and while there are several variations of your phone, it actually looks like it has a lot less frequencies than the T-Mobile device. I was under the impression it was the other way around, but I dunno exactly -- yours is supposed to be a D803 up there. It depends on the carrier/region, and which LTE bands they're using. It may be that you get LTE somewhere else eventually.
I don't know why the hell they don't just make the phone with all the bands you expect to encounter on a continent, but I'm sure it has to do with lock-in. Because the SoC should already have that stuff baked in.
I actually have an 802 (International version, unlocked) that I bought off a guy on Kijiji. It was an incredibly cheap price because it had some scratches on the screen which are not very noticeable. Once I applied a tempered glass screen protector, you could only see the scratches from an oblique angle. The guy even included an official LG flip case which wakes and sleeps the phone This phone even has a stock LP ROM.
I love the glass protectors! That gel adhesive just melts on the screen and leaves not a single bubble. And yeah, it gets into scratches and improves them, too. I'll never use film ones again. I've personally never broken a screen, but Gorilla Glass can be scratched under the right conditions. Hey, as long as it's working for you, cheap is always good. HSPA+ isn't anything to sneeze about either -- I've had some amazing speeds on T-Mobile with it, for years now. It's a great fallback for LTE.
Okay, I managed to recover the original phone!
Something in my previous build was triggering the boot loop into recovery. This happened when the CyanogenMod updater tried to flash a new nightly, so there's a possibility it set a flag that kept it looping. But it's also possible Xposed went haywire somehow, and/or a module did. I'm not really sure why it decided to fail like this, when I had been using it without issue.
All my backups did the same thing, yet those builds ran okay when I backed them up. And I don't know why I could see the COM41 port, but not use it -- the drivers were perfect, I went to a lot of trouble to uninstall and replace them. That meant no LGFlashTool, and manual restoration (ye olde commande line).
So, what I did was use fastboot to flash every partition I could get my hands on, not just the ones you can format in TWRP. I used the 20c files from here. You basically do:
fastboot erase aboot
fastboot flash aboot.img
fastboot erase laf
fastboot flash laf.img...etc. Then you format the /system partition, and flash a Cyanogenmod nightly into there. I also flashed the /data partition, but left /data/media alone, which saves the internal storage. Then I erased and flashed /recovery just for good measure.
This is a somewhat specific fix, but maybe if someone else comes across it, it can help.
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?