Hello everyone and happy new year to all of you.
I am creating this thread because i want to share with you my horror experience when i was rooting/adding twrp on the sm-t700 and how i soft bricked the tablet. Thankfully @HobbitCy was able to help and we got the device back. In this thread if you read everything you will also be able to understand the do's and dont's and if u follow them you can do it too
I AM NOT RESPONSIBLE FOR ANY DAMAGE YOU DO ON YOUR TABLET. PROCEED ON YOUR OWN. THIS IS AN EDUCATIONAL AND SELF SHARING EXPERIENCE I HAD AND THE STEPS I FOLLOWED TO SAVE MY TABLET.
ROOT
So to root the tablet i used this video on youtube https://www.youtube.com/watch?v=m8n8YWZedXU which is pretty clear and easy to follow. If you follow the steps fully u won't mess anything. Trust me, is super easy.
After rooting the tablet for a week i was finally confident to flash twrp aswell.
TWRP
After i downloaded the twrp manager from Google play store and tried to follow their original guide the manager kept crashing without doing anything. So i decided to restart the tablet ( maybe twrp wasnt going to crash after a fresh restart) but guess what, it was stuck on the samsung sm-t700 animation and kept looping. So again back to odin to re-flash the device with a fresh twrp. Went ahead and flashed 2.8.3.0 but guess what, device was giving me a new notification now instead of the samsung logo booting thingy which was this . So went ahead and downloaded the kies software from samsung only to find out it wasn't recognizing the device. Even the laptop was not recognizing the device. At the point i thought, my tablet is ruined. Went again into download mode then to odin and reflash flashed 2.8.3.0 only to again find out the flashing was failing at hidden.img . Decided to try a lower version of twrp after many failed attempts on that version. So went ahead with 2.7.1.0 and the tablet was loading into twrp ( YEEY my heart beat came back to normal levels ). Flash a new rom/kernel and gapps and the tablet was working again.
Although i was thinking why isnt the latest version working? So i went ahead and flashed every version of twrp from : 2.7.1.0 up to 2.8.3.0 ( 6 versions total ). All versions are working expect the last one ( at least for me and for my tablet. So i flash the 2.8.2.0 and let it still. Flashed 2-3 Roms to make sure everything was fine and voila i was in again with a fully functional tablet. Took me 3hours to figure out it was a problem with the twrp version.
Guide on Root/Twrp:
As i said earlier this is how you should root your precious tablet : Use this video on youtube https://www.youtube.com/watch?v=m8n8YWZedXU which is pretty clear and easy to follow. If you follow the steps fully u won't mess anything. Trust me, is super easy.
To flash twrp on your tablet : You will need to download odin v3.09 ( at least this is what i used for it ) and one working version of twrp ( i am using 2.8.2.0 ). Connect your tablet with the pc, wait for odin to recognize it in the ID:COM section, make sure auto reboot is ticked and F. Reset Time is ticked. Click onthe AP Button on the right side, find the twrp version you downloaded and press start, it will take approximately 2.30 minutes and then you will see a "PASS" GREEN NOTIFICATION ON THE TOP LEFT in odin. Voila you now have TWRP on your device.
I hope i helped/guided you. All of this experience was a lesson to read carefully next time you mess around your stuff! Thanks again @HobbitCy for helping me out !
I AM NOT RESPONSIBLE FOR ANY DAMAGE YOU DO ON YOUR TABLET. PROCEED ON YOUR OWN. THIS IS AN EDUCATIONAL AND SELF SHARING EXPERIENCE I HAD AND THE STEPS I FOLLOWED TO SAVE MY TABLET.
It was quite an experience for sure.
Couple hours of trying different things, always keep your cool, and as long as you have access to the device all hope is not lost.
People need to read about the problems with twrp 2.8.3.0 before flashing. It was in the twrp thread near the end about twrp 2.8.3.0. Always read before you flash.
Related
I have Cyanogenmod 10.1 (stable) installed; the other day it crashed while I was on Instagram, rebooted itself, and wouldn't go past the spinning circle screen. Tried rebooting it, now it won't go past the screen before that, with the blue Cyanogenmod man and the Samsung logo.
I have TWRP 2.5.0.0 installed with it, which I don't know how is possible being that the file systems are incompatible, so unless I used Odin to install CM10.1, I don't know how I did it without installing Clockworkmod Recovery over TWRP.
I've been trying to fix it for a couple days now (I'm kicking myself for not getting around to posting here sooner). When I go into TWRP it asks me for a password (which I've never set, I assume it's asking me because that's all it knows to do when the file system is incompatible), which I click cancel at every time, and when I try to do just about anything (including installing new ROMs or recoveries from within TWRP) it gets errors when trying to mount any partitions on the device, so I can't change anything on the phone at all.
I've tried re-installing TWRP AND Clockworkmod Recovery with Odin, and they succeed, but when the phone tries to reboot, the screen just turns off and nothing happens, and I have to take the battery out to do anything else.
So right now I'm totally screwed unless I can fix this thing. I'd like to not have to drop 200 on a Nexus 4 after only a year or having this phone I bought brand new, especially with the Nexus 5 already coming out later this year...can somebody help me???
EDIT: I should clarify that I can access recovery and download mode
If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.
FoxTrotz said:
If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.
Click to expand...
Click to collapse
I should've clarified that I've tried this with a bunch of roms, and it just shows SBA2 in the status box forever. I left it for a full hour before and it never changed.
According to this page http://www.alliance-rom.com/community/wiki/bricked-android/ reformating your external sd card may help. It also links to something I personally have never heard of but apparently this: http://forum.xda-developers.com/showthread.php?p=15330252 can help unbrick any samsung phone that's flashable with odin.
Hi Everyone,
I am a new owner of a soft-bricked SM-T700. I am feeling very down and need some advice. I will be as thorough as I possibly can and I would truly, truly appreciate some help and advice from you kind folks. This is the first time I have had a bricked device out of my many Android devices.
My PLAN:
-Root
-Custom Recovery
-Nandroid Backup
-Backup EFS
-Flash stock western country firmware
What HAPPENED
Today I bought a wifi T700. I bought it in my hometown, which is China. Whenever I buy a new Android device in China my first action is to ensure it doesn't have any hardware/warranty issues. I then go about reflashing a western firmware so I can use Google services.
1) First I rooted using CF-Auto Root. That worked fine. I confirmed that I had root using an app called root checker.
2) I then attempted to flash TWRP recovery by following the instructions here: http://teamw.in/project/twrp2/238
- First I tried flashing the .tar file using Odin. As soon as I hit 'Start' Odin froze and I got the Windows error saying "Odin Downloader Has Stopped Working", asking to close the program. I close the program. I tried this several times then rebooted. It seemed as though the phone booted fine.
- I then tried using their own software, TWRP manager, here: http://jmzsoftware.com/twrp-manager-4. This app just crashed every time I booted it. I submitted an error log.
- I then tried using 'Flashify' as suggested by someone here on XDA. Once I did that it said flashed successfully and would I like to reboot. I said yes. This is when my troubles started.
3) Upon reboot it immediately booted into a sparse looking 'Download Mode' screen, all in English (the normal one on mine has some Chinese too) without the volume button options to reboot or continue. It just went straight into this screen.
After trying to reboot the phone using several power button holds and key combinations, it appears I am stuck in this screen, so I thought I had no chance of doing a NADROID backup as originally planned, so I decided to try my luck and flash the western firmware.
I tried to flash the version of the firmware provided here: http://forum.xda-developers.com/showthread.php?t=2798835
http://www.androidfilehost.com/?fid=23501681358556680
It got all the way through the install until it hit the hidden.img and then failed. I've attached a screen capture.
A few notes;
I have tried using two different USB cables (the one that came with it, and the one that came with my HTC One). I have tried several USB plugs, including the one in the back of my PC. I allowed Odin to do it's MD5 check and it said the file checks out.
I have tried using the Kies emergency Firmware recovery. Pffft! As it that was going to work. Damn Kies.
I sound like I've still got my sense of humor, but actually I am really cut up about this. It is so much money for a tablet and now it is useless unless I can get s firmware that will flash.
I don't have my stock Chinese firmware. That is T700ZCU1ANF4/T700CHN1ANF4/T700ZCU1ANF4/T700ZCU1ANF4 (CHN).
Questions:
Does anyone know where I could find the stock Chinese firmware to try flashing back to that?
Does anyone have the .PIT file and instructions on how to flash that, because I have read in other threads that it solves the hidden.img problem.
Does anyone know why this may have happened and have any alternative suggestions?
Could it have been the TWRP that actually caused this? The thread here indicates others aren't having trouble. Why would it have frozen for me?
I will try anything at this point. I am desperate.
Thanks so much in advance. Please come through XDA! Please come through Galaxy Tab S owners!!!!!!
-------------------------------------------
CLOSURE EDIT: I managed to flash Australian firmware, after reinstalling Kies, uninstalling and reinstalled the device drivers. I also made sure all Kies processes were killed before flashing with Odin.
For people in a similar situation I would urge them to have patience and keep trying to flash stock firmware.
Private Message UpInTheAir and see what he thinks.
Well let me start out by saying i have done some truely horrible things to my tablet in the proceas of porting CM 11. Bad kernels, messing up the partitions, you name it ive probably done it at this point.
I would try using heimdall. Flash one of the recoveries.. and try formatting your partitions.
The program crashing is when you should back off from trying to flash. Reassess what you did and what happened and if it's failing at a point flash the stock back before rebooting.
Continuing blindly was the problem. On something as expensive as a tablet never continue past a point where something goes wrong without reflashing back to stock and starting again.
As eousphoros said Use heimdall and flash a recovery.
Good luck.
eousphoros said:
Well let me start out by saying i have done some truely horrible things to my tablet in the proceas of porting CM 11. Bad kernels, messing up the partitions, you name it ive probably done it at this point.
I would try using heimdall. Flash one of the recoveries.. and try formatting your partitions.
Click to expand...
Click to collapse
Hi All,
Thanks for taking the time to reply.
You are certainly right that it is my fault and I should have stopped at some point and reassessed what was happening.
Can you please give me some more information about the steps you have offered? I am researching heimdall now, but if you could give some steps or advice that would be much appreciated.
It's probably going to be difficult because I assume we are in different timezones. I will persevere and try to get this worked out.
I have downloaded Heimdall and understand that it is an alternative to using Odin.
I currently have three questions about Heimdall.
1. Do I need to do the install drivers step if I have already installed the drivers for my device? Is this some step that actually replaces the current drivers with ones that are required for Heimdall to operate? I ask them because when I list USB devices, my tab is not shown up as Samsung Composite Device. It is actually shown as two separate entries, looking like generic USB entries.
2. Do I need to have a valid PIT file in order to run a custom Heimdall flash?
3. Which partition should I select if/when I run the Heimdall flash?
I'm dying a little inside every time I look at my tablet
Install heimdall
Download a recovery, I am going to pimp mine. http://forum.xda-developers.com/galaxy-tab-s/general/cwm-recovery-6-0-5-0-galaxy-tab-s-8-4-t2824099.
Run sudo ~/git/Heimdall/heimdall/heimdall flash --RECOVERY cwm6.0.5.0-2.img. Wait for it to complete, your tablet will reboot and will probably fail like it has been.
Hold down Power + Vol Down + Home button... wait for the "Press vol up to continue, press vol down to cancel"
Press vol down to cancel, then immediately hold down Power + Vol Up + Home button till you see the recovery screen pop up.
If you get the recovery screen your tablet can probably still be saved. Woo!
So then download http://forum.xda-developers.com/showthread.php?t=2798835 (Which i think you already have)
Unzip it, there will be a tar file. tar xvf T700....something.tar.md5 -C some_directory
You will get a bunch of img files. From those you should be able to finish the recovery and hopefully return full function to your device. (Which unless something is physically broken you will most likely be able to do.) Good Luck! And again this is all done at your own risk, please dont sue me.
eousphoros said:
Install heimdall
Download a recovery, I am going to pimp mine. http://forum.xda-developers.com/galaxy-tab-s/general/cwm-recovery-6-0-5-0-galaxy-tab-s-8-4-t2824099.
Run sudo ~/git/Heimdall/heimdall/heimdall flash --RECOVERY cwm6.0.5.0-2.img. Wait for it to complete, your tablet will reboot and will probably fail like it has been.
Hold down Power + Vol Down + Home button... wait for the "Press vol up to continue, press vol down to cancel"
Press vol down to cancel, then immediately hold down Power + Vol Up + Home button till you see the recovery screen pop up.
If you get the recovery screen your tablet can probably still be saved. Woo!
So then download http://forum.xda-developers.com/showthread.php?t=2798835 (Which i think you already have)
Unzip it, there will be a tar file. tar xvf T700....something.tar.md5 -C some_directory
You will get a bunch of img files. From those you should be able to finish the recovery and hopefully return full function to your device. (Which unless something is physically broken you will most likely be able to do.) Good Luck! And again this is all done at your own risk, please dont sue me.
Click to expand...
Click to collapse
First of all, let me just say that OH MY F#@$ING GOD I THINK THE NIGHTMARE IS OVER!!!! I managed to flash the Australian Firmware successfully. It has now booted fine, I have factory reset and I am in the process of setting up the device afresh.
Having said that, when I do come to reroot and install a custom recovery, I will definitely take a look at yours. Was this here 12 hours ago? I looked and couldn't find anything about CWM except for a short thread and an unofficial port. I have never tried TWRP before and I will avoid it like the plague in the future. I have NEVER had trouble with CWM.
When (if ever) I get the nerve up to give this another go, I will try your CWM.
Thanks again.
I am so relieved right now.....
And make a Nandroid first this time
Hey,
I had the exact same issue with my Galaxy Note 8, every time I tried to install European or custom Rom.
The only way to get the tab back was to flash with the Chinese firmware. You may find it easily on Baidu.
Since it happened also with a note 2 and note 3, I stopped buying Android device in China... Unless you can make sure that you buy a model coming from HK.
Hi everybody.
In order not to create another Thread I would like to leave a request for help in here while searching the answer myself.
I've messed up with SM-T700 and it is suffering a "near brick expirience" now. D:
I wanted to install the TWRP in order to backup the stock ROM before proceeding to anything else. So I put it in download mode. In Odin. 3.09 I put the TWRP under the AP section, the auto-reboot and f-reset were checked. (later I understood that I look at a different chrome tab and followed the instuction for auto-root flashing in via Odin instead of TWRP's. Stupid me) THen I proceeded with flashing and it was succesfull. After that I rebooted to recovery but it was not TWRP but stock. So I went to Download mode again and decided to repeat the procedure. Hower this time, and each time after that Odin stuck with the SetupConnection... The tab itself is stuck in Downloading Do not tur off target!! and does not react to any combinations of buttons.
Looking for a piece of advice here.
At least Odin is detecting the tab is a good sign right?
Attaching the photo and screenshot just in case.
ky3bmu4 said:
Hi everybody.
In order not to create another Thread I would like to leave a request for help in here while searching the answer myself.
I've messed up with SM-T700 and it is suffering a "near brick expirience" now. D:
I wanted to install the TWRP in order to backup the stock ROM before proceeding to anything else. So I put it in download mode. In Odin. 3.09 I put the TWRP under the AP section, the auto-reboot and f-reset were checked. (later I understood that I look at a different chrome tab and followed the instuction for auto-root flashing in via Odin instead of TWRP's. Stupid me) THen I proceeded with flashing and it was succesfull. After that I rebooted to recovery but it was not TWRP but stock. So I went to Download mode again and decided to repeat the procedure. Hower this time, and each time after that Odin stuck with the SetupConnection... The tab itself is stuck in Downloading Do not tur off target!! and does not react to any combinations of buttons.
Looking for a piece of advice here.
At least Odin is detecting the tab is a good sign right?
Attaching the photo and screenshot just in case.
Click to expand...
Click to collapse
Replying to myself: The tab began to respond to buttons so now I succesfully rebooted it and will continue with Rooting then recovery
Added: Rooted successful but the same problem as described above occured when I tryied to flash TWRP in Odin under PDA tab unchecked the auto-reboot
ky3bmu4 said:
Replying to myself: The tab began to respond to buttons so now I succesfully rebooted it and will continue with Rooting then recovery
Added: Rooted successful but the same problem as described above occured when I tryied to flash TWRP in Odin under PDA tab unchecked the auto-reboot
Click to expand...
Click to collapse
Yeah I've had a really bad experience with TWRP on this device. Try flashing a firmware from sammobile.com or elsewhere to at least get it up and running again. Try to do that as quickly as possible too, so you don't have to leave the device in download mode all night. I think that is what caused the battery swelling in my first device that I had to return.
I'm going to stick with CWM when I work up the courage to try again....
pierrotee said:
Yeah I've had a really bad experience with TWRP on this device. Try flashing a firmware from sammobile.com or elsewhere to at least get it up and running again. Try to do that as quickly as possible too, so you don't have to leave the device in download mode all night. I think that is what caused the battery swelling in my first device that I had to return.
I'm going to stick with CWM when I work up the courage to try again....
Click to expand...
Click to collapse
Hi thx for reply. Actually it managed to unstuck from Download mode in 10-15 minutes. It happened twice to me.
ky3bmu4 said:
Hi thx for reply. Actually it managed to unstuck from Download mode in 10-15 minutes. It happened twice to me.
Click to expand...
Click to collapse
Cool! So do you now have root and custom recovery?
pierrotee said:
Cool! So do you now have root and custom recovery?
Click to expand...
Click to collapse
Yeah))
TWRP installs OK via TWRP Manager
I installed TWRP Manager, selected 'klimtwifi' as the device, and it successfully installed TWRP 2.7.1.1 without a hitch.
From TWRP I then immediately performed a nandroid backup of everything but the caches to my microSD card and encountered no problems.
The last step was to enable writing to my microSD card by installing NextApp SDFix.
My SM-T700 is bricked as well and I tried to flash a custom recovery with Heimdall on Mac but it gave me the Error "Claiming Interface failed". Seems like you really need the pit.
I screwed up my SPH-D710 big time (see details here ...). I am starting a new question thread here as this doesn't have anything to do with the device constantly booting anymore.
I have now manged to get the device into a state, that it doesn't boot anymore, neither regular nor into recovery, but hangs in the black boots screen that says "Samsung Galaxy S II" in white letters.
I can still boot into Odin mode though - and I hope that's a good thing.
Last thing I put onto the device (also mentioned in the other thread) was Garwynn's SXTP+Agat Recovery kernel v0.3.0 from Rwilco12's repository.
Can I still save the device and how.
I really want some expert advice before I do the next step ...
Thanks in advance!
OK, so my device is officially bricked. I think I can still get into Odin mode (if I find a charged battery, as mine drained / didn't charge any more in the mean time).
In case I find a charged battery and can still get into ODIN mode, I want to try a [rooted] stock ROM - does it matter which one?
Eventually I want to load CM11.
Thanks.
Please follow these directions to return to stock latest rooted.
Download these files and place them onto your desktop named EpicStockRooted.
Choose between whether you want Data wiped, or not.
GB27 Rooted Data Wipe
GB27 No Data Wipe
Samsung Drivers
Make sure Samsung Kies, or other versions of Samsung Drivers are uninstalled first. Then install the Samsung Drivers.
Once you're finished start the executable GB27 file as administrator mode and wait for it to load. Once you're done, proceed to put the device into download mode. Hold Volume Down + Power button until you're on a Android Firmware dialogue with the green android, press volume up to proceed to the next screen.
Now plug in the device to the computer ( USB 2.0, original samsung usb to micro plug ) and let the device be recognized. you'll see a [COM:##] show up within the first white box, doesn't matter about the ##, as long as it's reading [COM:]
Proceed to click START! and wait for it to be finished, appx ~15 minutes to do so.
Once done the device should auto-reboot. Let it load up.
Setup your device and proceed to the home screen of the launcher, SuperSU will force close on you, don't worry about that, press YES and setup your Google Account for Play Store.
Update SuperSU via playstore, then install as /system app in SuperSU, you're done setting up now.
You're issue was installing a custom kernel for the wrong type of Android version for your ROM.
The latest Custom Kernel for Jellybean GB27 is Agat's Source version 1.4.2f. Use Odin 3.07, within PDA slot to flash the custom kernel. But make sure you're fully loaded on stock first.
If you happen to think about loading CM11, Please feel free to see this post HERE
Thank you very much Spark!
That's pretty much what I did after some heavy research here on this - very helpful - forum.
I downloaded and installed a rooted one-click GB27 and am back up and running - learned a lot from that experience.
Thanks also for explaining what I did wrong.
I am now in the process of downloading the necessary stuff for going to CM11.
I installed Mobile Odin (Lite) and am putting EL26 CWM recovery (StockCWM-EL26.tar.md5), an ICS modem (FL24.zip), gapps and CM11 (I will start with the stable milestone version from here, and then maybe try the latest nightly, if success ...) on my sdcard.
I read (and read again ...) this post on the "one Stop FAQ for Noobs" thread and hope that I won't run into any issues.
Thanks again!
You're welcome, it's all about trial and errors here, People can read and read but most posts around here do get confusing on what you should do and it is A LOT of reading. But once you get used to it, you'll be up to speed on what to do from there on.
I managed to get the device to CM11 and everything is working.
I followed the instructions in the "One Stop ... for Noobs" thread and the OP in the CM one. The only hickup that I had was that the EL26 recovery kernel only has CWM5 and one obviously needs CWM6 (probably in order to flash a KitKat ROM ... (?)), so I had to find a CMW6 recovery that I could flash with CWM5.
Hi XDA, many threads here have helped me in the past so time to ask another (probably stupid) question. It's a bit of a long story so I apologise in advance.
I've been running CM (one of the nightly builds from about 3 weeks back, don't have the file so I can't say which) on my phone for a while with no issues until a couple of nights ago when it was overheating (charging while playing a game, stupid I know) so I decided to turn it off so it could cool down without taking it off charge.
The following morning I turn it back on to find that it's getting to the blue android head logo of CM and getting stuck there. First thing I do is reboot into TWRP and flash my backup from right after I installed CM. Reboot and... same result. Okay, no biggie right? Time to reinstall CM (the latest nightly build from yesterday) and Google Apps (nano package) via TWRP and reboot again. Still stuck at the blue android head logo. The reinstall was handled after using the Wipe-Factory Reset function of TWRP, as the guide here explains.
At this point I decide to do a bit of research and learn that it's called a softbrick or bootloop and apparently flashing the stock rom can fix it. The LG software suite won't even recognise the device but a friend of mine found this guide so I attempted to run through it. All goes well until it comes time for the software to connect to the phone - I pop it in download mode while putting the USB cable in, the program says waiting for connection, runs for 14 seconds and says it's trying to put the phone into download mode, at this point it fails saying the phone can't be put into download mode.
Some of the comments beneath the article offer fixes like using USB 2.0 instead of 3.0, putting the program into compatability mode for Win7 and running in administrator mode. To be thorough I tried every USB port on my machine (both 2.0 and 3.0) and run the program in compatability mode (with and without admin mode) for several versions of windows. Same result every time.
Another friend then suggests that somehow permissions got borked and it might be worth reflashing SuperSU to the system but at this point I'm at a loss for how to do that. I have the one click root script that I got from god knows where (not this one because that didn't work for me) that has a SuperSU zip in it, presumably it flashes that to the phone when it runs (found this out the hard way because I've been a moron in the past and tried installing SuperSU through TWRP and broke the boot previously, fixed by re-running the one click root script - this was ages ago before even installing CM.)
So right now I can put the phone into download mode manually, get into TWRP and use all its functions as well as connect to my PC and use ADB functions while the phone's in TWRP but can't boot into CM or flash a stock rom. Any help would be appreciated, I've spent a whole day reading guides, asking friends and clumsily trying to fix this only to get nowhere.
Have u tried installing the stock via TWRP? Via zip ... Wipe cache delvik also..
jinderation said:
Have u tried installing the stock via TWRP? Via zip ... Wipe cache delvik also..
Click to expand...
Click to collapse
I haven't tried that, I didn't even know it was possible. Could you give me some more detailed pointers on how to do this? I noticed that the stock ROM I have cames as a .TOT file but CM is several files and folders in the zip. Will it install fine from that zipped up TOT file?
Thank you so much for your time.
When the rom is uploaded by the dev its also uploaded in .zip file place it ur system rom just go into twrp recovery flash the the zip file before flashing wipe cache n delvik too its easy as 1,2,3 search here on xda for ur compatible model
jinderation said:
When the rom is uploaded by the dev its also uploaded in .zip file place it ur system rom just go into twrp recovery flash the the zip file before flashing wipe cache n delvik too its easy as 1,2,3 search here on xda for ur compatible model
Click to expand...
Click to collapse
Thank you so much. I got it sorted. I really appreciate you taking the time to help me out with my stupidity.
I need to install Lineage OS on this phone.
After multiple tries several months apart, I am still not in success.
Followed all internet tutorials and sites.
I don't want to install any G apps or any special root-things like magdisk..
I only want pure Lineage OS without any extra applications.
Way I tried and probably ended up like before:
Get newest official samsung ROM installed, update, enable usb debigging and oem, go download mode and go factory reset, get back in, sign in to wifi again, again enable develop. settings and usb debugging, go into download mode, take odin and install through the AP option the TWRP now that the phone is in download mode a 3rd time, supposed to be possible now with OEM unlock.
Most of the names on the way I don't understand, just follow tutorials.
I need to get to TWRP to then finally, as used to always, install Lineage from zip.
But I never get rebooted into TWRP recovery, just forver the samsung one, even when firmware is no longer there - after flashing in ap option the twrp tar again it never boots into TWRP afterwards.
Is there something else i must do? is not getting into oem unlock and flashing TWRP enough to get there?
And after, will the zip install finaly get me to have lineage installed?
Did you try the official guide?
https://wiki.lineageos.org/devices/beyond0lte/
I hope I picked the right phones, otherwise check devices overview.
Alternatively, perhaps this helps:
https://forum.xda-developers.com/t/...-a-graphical-installer-for-lineageos.4509995/
PS: Usually LOS doesn't do TWRP anymore but comes with its own recovery (a/b)
Why they don't do TWRP now?
I saw TWRP tuorial fot s10 on tutorials and it worked
Do I have to give up on TWRP way and od it with the adb commands from PC
frustrateduser118 said:
Why
Click to expand...
Click to collapse
It's because of this new double recovery scheme:
https://forum.xda-developers.com/t/help-understanding-a-b-partitions.3748003/post-75545902
https://source.android.com/docs/core/ota/ab
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
EOD: It's safer, updating happens in the background, then just a quick reboot et voila.
frustrateduser118 said:
I saw TWRP tuorial
Click to expand...
Click to collapse
Yes, it's still there but perhaps you post a link to your guide (or ask there). To me it seems you had TWRP just in your RAM but not your phone?
As for me, I finally gave up on TWRP and use the "crappy" LOS recovery Have way more important things to waste my time on...
PS: Sorry to bring such "bad" news, wasn't too happy with that change myself
Great, I finaly made it work.
I followed the site with turotial on installation and did not try TWRP
First I had to install samsung ROM again
It turned out to still stay unlocked so went straight to download mode and this time flashed Lineage recovery sucesfuly with heimdall
Then it booted up and a half samsung sreen made it seem like there is trouble
but Lineage recovery launched
The adb load from PC did not work so i chose to instal zip from SD even there
Now Lineage is installed
Still don't know how much is randomness, luck and so on
But it's done and hopefuly repeatable
frustrateduser118 said:
hopefuly repeatable
Click to expand...
Click to collapse
I am afraid it is
Well, most of times: Far too often I forget some little prerequisite, too... so started a little text file with steps/reminders.
anyway glad for support sigmund
you re my friend now