Hello,
So all along I thought I had a Tab PRO 10.1 and attempted to install TWRP for it. I ended up messing up my whole OS and just I started messing around with the OS and recovery. Long story short, I now have no OS and the only Recovery I can access is ODIN.
Can someone please help me reinstall a stable custom or OEM ROM, Kernel, Recovery?
Thanks!
Stock Firmware is at sammobile
Related
Hello everyone,
So I stupidly wiped my OS in TWRP and now I am having a difficult time flashing any ROMs as they keep "failing" when I try to install them. Please help.
Thank you
Try flashing a stock rom for your phone model, you can get the files from here. You'll be able to flash the rom through Odin via 'Download Mode', rather than using TWRP. Hope that helps, good luck!
Hi all,
I am new here and I am having trouble with my Galaxy 3 SGH-I747 from at&t
I rooted the phone using KingoRoot and everything was fine.
I used the phone for about a week and decided to update from kitkat 4.4.2 to lolipop 5.0.
I have a micromax phone that is rooted and I didnt have any trouble updating it while it was rooted, so i figured it wouldnt be a problem but when I updated the s3 it said update failed at 94% and started rebooting and got stuck in an update loop.
I searched and searched and tried finding recovery options using odin but I cant find a 4.4.2 stock firmware, and cant find much information on recovering my device.
I am unable to boot in to recovery. I cant find a link for the SGH-I747 to philz recovery, the links all seem to be dead.
I can boot in to download mode.
I want to install a custom recovery via ODIN but i cant find one for my phone.
After I install the custom recovery, how will i know which stock OS my phone is currently at
I appreciate any advice you can give me, thanks.
Use TWRP for custom recovery. CWM and Philz haven't been updated in quite a while. You can get odin flashable tars from here.
Flashing TWRP should get you to working recovery, and you can find the rom zips you need to get back up and running in the development section here.
Unrooted stock will overwrite TWRP with stock recovery upon boot. Depending on how far your phone is getting into the booting process that might happen if you let odin auto-reboot. Your best bet is to uncheck auto-reboot in odin, so it won't restart on you automatically. Upon success remove the USB cable and pull battery. Replace battery and boot straight to recovery by holding home+vol up+power until you see tiny blue text in the upper left corner then releasing.
Thankyou! i was able to install the recovery by TWRP.
I just need to figure out what firmware to install and where I can get it... I was on kitkat, I tried to update to lollipop but it didnt work. My phone is bricked so I dont know how i would see the firmware version on it.
I really just want any kind of stable firmware that is rooted. Any ideas where I could find one? I'm trying to sift through the forums
Lots of ROMs are available here: http://forum.xda-developers.com/galaxy-s3-att/development
audit13 said:
Lots of ROMs are available here: http://forum.xda-developers.com/galaxy-s3-att/development
Click to expand...
Click to collapse
I appreciate all the help - It seemed really hard because I was finding roms and flashing with ODIN but it always failed TWRP is giving me results. I flashed slimkat and got my phone working again! the only problem is my sound is a bit junky, idk why.
I plan on trying out Octos - M, because I heard marshmallow OS has a lot better battery life among other things
If i upgrade to a custom marshmallow OS, is there any coming back to a former custom OS like 4.4.2? or is it a permanent upgrade?
Do you guys recommend any custom OS? I need something stable, that uses the resources efficiently.
Before flashing additional ROMs, make sure the phone is running the latest bootloader and modem.
To verify the installed bootloader and modem, install the Samsung Phone Info app from the Play store.
With a custom ROM, you can flash from one to another, usually without any issues as long as you perform a complete wipe (system, data, cache) before flashing a new ROM. If you are upgrading an existing custom ROM with a newer custom ROM (e.g. CM12.1 2016-01-01 nightly to CM12.1 2016-01-02 nightly), you can just flash the updated ROM over the existing ROM.
I am trying to re-install STOCK ROM on SM-T705. I was previously running Lineage OS 14 with TWRP Recovery.
Downloaded the Stock ROM and used ODIN to reinstall the ROM. On reboot, it first showed the android Logo restoring OS and then on reboot, is stuck on Samsung logo. The tablet vibrates periodically, but nothing happens. Have waited for couple of hours.
I encountered similar problem last time when installing Lineage OS. At that time, I got around this by flashing TWRP via ODIN. But I do want to go to Stock Recovery.
I can get the tablet back into ODIN mode.
Any help is most appreciated. My overall experience in installing ROM and Rooting, etc is very limited.
praveenvj said:
I am trying to re-install STOCK ROM on SM-T705. I was previously running Lineage OS 14 with TWRP Recovery.
Downloaded the Stock ROM and used ODIN to reinstall the ROM. On reboot, it first showed the android Logo restoring OS and then on reboot, is stuck on Samsung logo. The tablet vibrates periodically, but nothing happens. Have waited for couple of hours.
I encountered similar problem last time when installing Lineage OS. At that time, I got around this by flashing TWRP via ODIN. But I do want to go to Stock Recovery.
I can get the tablet back into ODIN mode.
Any help is most appreciated. My overall experience in installing ROM and Rooting, etc is very limited.
Click to expand...
Click to collapse
My SM-T700 was in same situation but i was able to fix it by re-flashing twrp then doing full data format, then after that format the cache partitions, then odin flash the factory firmware.
After doing that booted to the factory setup wizard. Hope this helps you out of your situation
Issue resolved. Please close the thread
I managed to fix the issue. I tried flashing another ROM from Sammobile and lower version of ODIN and did the patching and it started working. I guess had a bad ROM downloaded from SAMMOBILE.
This thread can be closed.
Hi
So I want to return to the stock rom now with magistrates and fix some of the Samsung bloat. But I haven’t got access to a computer and can only use twrp. Can I flash it and not brick my phone? Please help if you know anything. Thanks a lot.:fingers-crossed:
Note: I’m using a custom rom and when I installed twrp I went straight to a custom rom Andy never tried magus to fix Samsung skin.
Up
Hi all,
While I have successfully installed Lineage 14.1 and the GApps 7.1 on my Tab Pro 12.2, I can't get it to install Lineage 17.1. I had issues getting 14.1 onto it until I loaded a new bootloader file through Odin (BL_T900XARBOJ1), but I can't seem to find a bootloader that will let me install Lineage 17.1. Does anyone have any suggestions?
Similar problem
-- sorry, wrong device, please disregard. I can't seem to find a delete button. Newby passing through.--
I have not previously installed custom ROMs on my devices. Now I am also trying to install Lineage 17.1 on my Galaxy Tab Pro 12.2 and thus far have been unable. Maybe your experience is similar to mine:
I used ODIN to flash the latest TWRP to the boot loader and booted to recovery (so Samsung system boot would not replace TWRP with stock recovery) and TWRP recovery is stable. In TWRP, I installed SuperSU from a zip file on the extSD. After booting into the stock system, I was prompted to finish rooting, which I did using TWRP. Once I was able to reliably boot into recovery or normally (stock system), I booted to recovery and made a backup of my stock image. I have reliably flashed Samsung stock image, which boots to the initial setup process, and restored by backed up image, which boots to the previously configured state.
At this point I downloaded the Lineage 17.1 image zip file onto the extSD card and tried flashing it from recovery. While unzipping the image, the recovery screen shows a couple of error messages, along the lines of image is 'for device v1awifi but this device is .' and flashing fails. I believe at this point rebooting hangs with the Samsung logo animation, but I have been able to boot recovery and restore my previous rooted Samsung stock state. Custom ROM Manager confirms my device Codename is v1awifi.
Is this what you experienced? If not, how is your experience different? Can you describe your approach, what steps you've taken, and where the process does not go as expected?
ScrooLoose said:
Hi all,
While I have successfully installed Lineage 14.1 and the GApps 7.1 on my Tab Pro 12.2, I can't get it to install Lineage 17.1. I had issues getting 14.1 onto it until I loaded a new bootloader file through Odin (BL_T900XARBOJ1), but I can't seem to find a bootloader that will let me install Lineage 17.1. Does anyone have any suggestions?
Click to expand...
Click to collapse
where did you find 17.1 for tab pro 12.2?
ScrooLoose said:
Hi all,
While I have successfully installed Lineage 14.1 and the GApps 7.1 on my Tab Pro 12.2, I can't get it to install Lineage 17.1. I had issues getting 14.1 onto it until I loaded a new bootloader file through Odin (BL_T900XARBOJ1), but I can't seem to find a bootloader that will let me install Lineage 17.1. Does anyone have any suggestions?
Click to expand...
Click to collapse
So you are on TWRP 3.4.0-0?
Although I own a P900 I had problems flashing 17.1 before updating to 3.4.0-0.
And for 17.1 I used BiTGapps instead of opengapps for the last didn't like it.
Does anyone know how to modify this note 12.2 LOS 17 zip so it can be flashed on tab 12.2? https://forum.xda-developers.com/t/...l-lineage-17-1-android-10-q-20201221.4152395/
I was able to get it installed on my Tab pro 12.2 T900. It gets stuck on the bootup lineage logo screen. I guess android 10 on this device is too good to be true.
Dusterrr said:
I was able to get it installed on my Tab pro 12.2 T900. It gets stuck on the bootup lineage logo screen. I guess android 10 on this device is too good to be true.
Click to expand...
Click to collapse
I had the same issue. You need to flash 17.1 over 14.1.
rojorojorojo said:
I had the same issue. You need to flash 17.1 over 14.1.
Click to expand...
Click to collapse
I tried this and it isn't working. Any suggestions? Can you help me out? Nevermind, its working this time! I tried many times, but the final time I didn't clear cache and it worked .
NVM not working again...
I clean flashed lollipop with odin, then twrp, then lineageos14.1, configure it, and dirty flashed 17.1, and at the moment it's working. No root installed.