Rooting difficult s7 - How I did it. - Ideos S7 General

Ok so this is my first post, apologizes for posting here but I cant post it in development because I am a noobe lol
First let me explain some history . . .for the last 2 months I have been trying to Root and install a custom recovery on the IDEOS s7 (Telstra/Australian), running Indo 2.2 . . .
Following ALL the suggestions found in the forum and elsewhere only resulted in set back after set back . . .my s7 refused to Root (although I extend my gratitude to everyone here for there solutions and work-arounds) . . .
Gingerbrake . . Fail
Super one click . . Fail
(Modified) Super one click . . Failed
And out of frustration Revoked, scripts, terminal, dos, etc, etc . . LOL
The closest we got to rooting was with an un-modified Super one click.
Installed (and un-installed) every driver I could find for the s7 under windows7 but Super one click would not see the s7 at all.
However after a forced un-install of the drivers and reinstall of the drivers from the Ideos_S7_Froyo_1.3_Upgrade_tools package the xauBeta_CWR_0.1/CWM-Install-Script would see it untill the s7 would reboot into Bootloader (then nothing).
From there I found after some experimentation Super one click would "see" the s7 and start Rooting it until failing (at step 4) if you re-installed the drivers (again) and run xauBeta_CWR_0.1/CWM-Install-Script stopping it just before it reboots the s7 into bootloader.
If you then exit bootloader on the s7 and re-press root in Super one click as the s7 is booting normally it would complete steps 1 through 6 (maybe 7) until failing when the s7 finishes booting . . .
So thinking it may work if I could slow down the boot up on the s7 I closed everything -
1. Re-installed the drivers from the Ideos_S7_Froyo_1.3_Upgrade_tools package into windows7 (swearing included).
2. Started the xauBeta_CWR_0.1/CWM-Install-Script until it found the s7 but did not continue further into re-booting the s7 in bootloader mode (keep it running).
3. Opened Super one click and pressed "Root" and waited until it said it was "Waiting for the device"
4. Then did a "normal" reboot of the s7 and kept pressing the Down Volume key in the hopes of "slowing" the boot time.
I don't know enough to know if pressing the down key would do anything but it did appear to slow down the boot time and allow time for Super one click to complete all the steps un-hindered and root the s7 (finally).
So if anyone is experiencing the same trouble as me rooting the s7 you could try this(but I give no guarantees).
I seem to have a particularly troublesome s7 and have found getting a recovery on as well very difficult . . . I will post soon the only way I could get one on mine later.
I hope this is useful to someone out there (like me) . . oh and yes if some of the things I have mentioned are obvious (or well known) to others please forgive me I am a Noobe and could not get any of the work-arounds I found to work as best as I understood them.
Regards,
Andrew.

good thanks.

Related

Putting a custom Recovery on diffacult s7 - How I did it.

So this is my second post, again my apologizes for posting here but I still cant post it in development because I am a noobe lol
First let me explain some history . . .for the last 2 months I have been trying to Root and install a custom recovery on the IDEOS s7 (Telstra/Australian), running Indo 2.2 . . .
After finally getting my s7 rooted (see my other post) I found myself again having a "battle of wills" with my s7 trying to get a custom recovery on.
After trying all the suggestions I could find here and elsewhere (again thank you to everyone) the s7 still refused to co-operate.
After trying batch install scripts under windows, terminal emulators, Clockwork Mod and all sorts of voodoo magic nothing seemed to work.
it flat refused to install a recovery from windows7 or SD card
lol - I certainly can pick a fussy one . .
After 2 days . . . and faced with the daunting task of trying to force it to do it through terminal under Linux (I am a Linux Noobe too) I came across this apk - (opps I cant post links to . . 329772-app-recovery-manager-v036-beta)
I think it is made for specifically for ZTE devices but after installing it on the s7 . . selecting the CWM 2.5.1.8 by goodoane on the SD card and executing . . . (wow)
Without even rebooting the s7 . . .no bootloader, no complaints, no freezing . . the CWM 2.5.1.8 by goodoane is on and working
I have re-booted into recovery 3 times now just to convince myself I am not dreaming . . lol
After flashing the Apk (on the s7) does not see the recovery but the recovery is flashed and working.
Again I hope this is useful to someone out there because I can attest to how frustrating it can be reading everyone else's and being left arguing with my s7 lol
Just because I am a glutton for punishment I think I will now go install the FroyoFusion-R2 (Hybrid) . . . . maybe the s7 will "talk" to me now
Regards,
Andrew.
Ideos_S7_Froyo-v1.3-EXT4-SA.zip On and working like a dream so far
I hope my experience getting the s7 rooted and customized is help to someone else
Regards,
Andrew.
Joenilan's latest ROM is awesome
Can someone please pass on my thanks to him because I still cant post in Development.

Helppp plzzz!!!!

I was unable to get root access for my Galaxy S for about 1 week, and today I finally could do it. Unfortunately, I rushed to try all of the apps I downloaded before that need root access, one of which was supposed to change the battery icon's (that in the upper tray) appearance. When I clicked on that, the mobile rebooted and kept giving again and again the (Samsung GT-I9000 Galaxy S) screen without proceeding to operation. What made it worse, as I think, is that because I was afraid and very concerned, I tried to do anything and so I entered into recovery mode and kept pressing on things I don't remember exactly but what I do is that I think I unmounted the SD. It's urgent; any1 plz try to help me as soon as possible.
Romino0 said:
I was unable to get root access for my Galaxy S for about 1 week, and today I finally could do it. Unfortunately, I rushed to try all of the apps I downloaded before that need root access, one of which was supposed to change the battery icon's (that in the upper tray) appearance. When I clicked on that, the mobile rebooted and kept giving again and again the (Samsung GT-I9000 Galaxy S) screen without proceeding to operation. What made it worse, as I think, is that because I was afraid and very concerned, I tried to do anything and so I entered into recovery mode and kept pressing on things I don't remember exactly but what I do is that I think I unmounted the SD. It's urgent; any1 plz try to help me as soon as possible.
Click to expand...
Click to collapse
Simply put the phone in download mode and flash the same firmware. The app you used probably caused the bootloop, likely because it wasn't made for your phone/firmware.
Next time, read and learn about it before you do it. And also, just some advice, before you do ANYTHING that will potentially cause your phone to bootloop or no longer work, ALWAYS ALWAYS ALWAYS do a nandroid backup (which can be done in recovery mode). That way, if it messes up your phone, you can simply restore the backup and be right back where you left off.
Good luck!
Thnx for ur concern and advices. I already did that the day after I posted; I discovered another thread on the forum and followed the instructions, and yeah sure I won't rush in these things again .
This kind of this happens all the time when we began in the flash world ajajaj
Don't worry this is the way everyone learns.

S7 edge (Canada) WILL NOT boot to twrp

HI all!! Glad to be here! Thank you in advance for the opportunity to receive much needed help.
ADMIN : Please put this in the proper topic forum if needed. Thank you!
Samsung Galaxy S7 SW-G935W8
I've never rooted an android and want to to customize the gui (to something really hi res and sharp looking and cool like 3D lazer razors!:cyclops: ) and remove bloatware.
I've done a bit of research prior too, just to familiarize myself with rooting and what's involved. Today, I found myself with an extra hour worth of time and figured, "meh, cant take that long!" Wow was I wrong! I have been working at this for 4 hours already.
I started by watching a tutorial AND reading thru the tutorial and DLing all necessary files to my computer that the tutorial said to. It was twrp ver 3.0.2-4 and ODIN, SU, and the samsung drivers. I quickly read through some troubleshooting posts here in case I got into some trouble I'd know what I'm dealing with.
step one(I'm doing this from memory)
copy SU onto phone (i put in in root directory and onto the sim *just in case)(had to look up where the "root" folder was located:silly: )
Step 2: turn off phone.
Step 3: turn phone on into Download mode
Step 4: press volume up to enter download mode
Step 5: open odin on pc
Step 6: put twrp*.*.*.*.img in the space for AP
Step 7: UNCHECK auto reboot
Step 8: hit start in ODIN
Step 9: PASS!!! right?!?!? WRONG!!!
SO THIS IS WHERE I MANUALLY REBOOT (oops caps) (vol dn+home button + power button) as soon as screen turns off (from DL screen) press and hold vol up whilst holding home + power.
Sometimes it just boots normally, sometimes it boots to a red screen, I have tried several different versions of the twrp and ODIN without success.
At this point I give up unless you can help me. I'm just glad I haven't bricked my phone *|YET|*
I have also tried leaving autoreboot enabled in ODIN. and then quickly holding vol dn+vol up+ home + power(also just vol dn+home+power and then switching to vol up+home+power) without success.
Any suggestions? Again thank you in advance!!
So I ended up using chain fire to auto root it. I must've been using the wrong img file. So anyway I've rooted my phone now. I checked with a root checker.
This is the weird thing. I haven't lost any of my data on my phone. All my contacts, texts, and even chrome bookmarks are still there. Is this normal?
Also I was wondering if CM Launcher was any good? It has ads which I don't like and a bunch of crap ended up on my home screen and all the folders are now mixed up! I installed the "Next tech" theme which seems pretty good except for all the apps are disorganized.
I installed G DATA Internet Security as well. Again I've read a few reviews and it's saying it's not all that great. Anyone have any experience with G DATA?
I humbly ask for your insight and although you people are probably a lot younger than me, your expertise will go a long way to help me. If you have any tips to make my phone more enjoyable please pass them along!
Thank you!
Ok so now I have a new problem! I disabled developer options. Then restarted my phone. Don't ask me why! Now the OEM unlock is off too. So when I restarted I guess it says custom binary blocked by FAP lock"
What do i do now? please I have been messing around with this all day and am tired! I didn't get anything else done i was supposed to get done! I'm so fkn fat and lazy!
fat35yo said:
Ok so now I have a new problem! I disabled developer options. Then restarted my phone. Don't ask me why! Now the OEM unlock is off too. So when I restarted I guess it says custom binary blocked by FAP lock"
What do i do now? please I have been messing around with this all day and am tired! I didn't get anything else done i was supposed to get done! I'm so fkn fat and lazy!
Click to expand...
Click to collapse
Blocked by FRP lock...
You'll need to reflash stock firmware with Odin, go to SamMobile and you'll find what u need there.
---------- Post added at 07:03 AM ---------- Previous post was at 07:00 AM ----------
fat35yo said:
So I ended up using chain fire to auto root it. I must've been using the wrong img file. So anyway I've rooted my phone now. I checked with a root checker.
This is the weird thing. I haven't lost any of my data on my phone. All my contacts, texts, and even chrome bookmarks are still there. Is this normal?
Click to expand...
Click to collapse
Samsung devices when you root it you don't actually have to unlock the bootloader (Uh, maybe turning on OEM unlocking in Dev options...) So it doesn't wipe.
PalmCentro said:
You'll need to reflash stock firmware with Odin, go to SamMobile and you'll find what u need there.
Click to expand...
Click to collapse
Thank you so much for your fast and courteous reply!
There are 4 options i see for "Canada" "Rogers" G935W8
I clicked the newest one and its a 2gb download, does that seem right? is there THAT much bloatware?
Am I going to lose all my data now? Should I remove my sd card?
Thanks again!
There are 4 options i see for "Canada" "Rogers" G935W8
I clicked the newest one and its a 2gb download, does that seem right? is there THAT much bloatware?
Am I going to lose all my data now? Should I remove my sd card?
Thanks again!
Click to expand...
Click to collapse
ok so i guess they uploaded another Stock firmware lastnightn before getting an answer here so i Downloaded the newest on. I used ODIN (Thanks SAMMOBILE for making it easy to figure out which file goes where!)
I reset phone with ODIN and everyhting seems to work EXCEPT it won't let me sign in using my Gmail account. it keeps saying "please sign in using one of the owners accounts for this device'"
so now I stuck again!
It's stupid because it sends this phone prompts to verify thru SMS, It even let me reset my Gmail password through a sms verification through my phone. After a bit of reading though, I found out that you shouldn't reset your password for 72 hours or something! I dunno! I'm just skimming articles to try and fix this phone!
I tried signing into Google from my tablet. I verified that the s7 trying to access my account was in fact me. I then tried signing into the s7 to no avail. I'll keep posting my updated. Oh and administrator....I'm not just trying to get my 10 posts!
PalmCentro said:
Blocked by FRP lock...
.
Click to expand...
Click to collapse
Yea I realize that now...just thought it was a developer with a sick (but awesome) sense of humour??!!
Ok I'm pretty sure I found the info I needed here: https://productforums.google.com/fo...c;context-place=topicsearchin/gmail/icyseraph
I guess all it took was a little gugling

Need support on 7.1.2 for Y5 2017 mya-l22

I have successfully booted the rr 7.1.2 rom from 4pda on my device every thing seems very well except in performance its much slower than the stuck firmware , also i have check the antutu score and it get lower by 10k points , i have check the gpu with another app and the working percent was stuck at 0%
So if any one could help fixing the hwc , kernel , hw coding and decoding,, it will make the device fly again
fir1996 said:
I have successfully booted the rr 7.1.2 rom from 4pda on my device every thing seems very well except in performance its much slower than the stuck firmware , also i have check the antutu score and it get lower by 10k points , i have check the gpu with another app and the working percent was stuck at 0%
So if any one could help fixing the hwc , kernel , hw coding and decoding,, it will make the device fly again
Click to expand...
Click to collapse
I have been trying to get this room to work but failed everytime, because of the encryption.
Everytime I get decryption successful but something went wrong. As far as I understand the encryption should be disabled on this ROM completely, but I can't get it done. I tried reformatting data to ext4 but that didn't work.
Edit: The problem was that I was using Magisk as root solution. I tried with the provided SuperSU and it all worked.
My device runs well with rr. I only notice the performance issue on startup, right after but the phone is very slow.
I noticed that there is no swap memory use in this ROM, while in stock there was a deal memory partition.
I'll try to figure out if we can enable it in this ROM. That might improve performance.
JudgeDread11 said:
I have been trying to get this room to work but failed everytime, because of the encryption.
Everytime I get decryption successful but something went wrong. As far as I understand the encryption should be disabled on this ROM completely, but I can't get it done. I tried reformatting data to ext4 but that didn't work.
Edit: The problem was that I was using Magisk as root solution. I tried with the provided SuperSU and it all worked.
My device runs well with rr. I only notice the performance issue on startup, right after but the phone is very slow.
I noticed that there is no swap memory use in this ROM, while in stock there was a deal memory partition.
I'll try to figure out if we can enable it in this ROM. That might improve performance.
Click to expand...
Click to collapse
Don't mean to hijack this thread but im desperate. Im trying to root mt MYA L22 but can't seem to find the right instructions. Posted here two times but no one is replying. Could you tell me how you unlocked bootloader on your phone? I already have the code from Huawei website. I am stuck at the cmd prompt when i type "list adb devices" from a cmd prompt opened through the adb and fastboot folder that ive downloaded. It says adb devices attached but shows nothing after that, basically an empty list. Any advice would be greatly appreciated!
Dylan2232 said:
Don't mean to hijack this thread but im desperate. Im trying to root mt MYA L22 but can't seem to find the right instructions. Posted here two times but no one is replying. Could you tell me how you unlocked bootloader on your phone? I already have the code from Huawei website. I am stuck at the cmd prompt when i type "list adb devices" from a cmd prompt opened through the adb and fastboot folder that ive downloaded. It says adb devices attached but shows nothing after that, basically an empty list. Any advice would be greatly appreciated!
Click to expand...
Click to collapse
It was a long time ago since I setup fastboot and ADB. I used this thread
https://forum.xda-developers.com/showthread.php?t=2277112&page=53
JudgeDread11 said:
It was a long time ago since I setup fastboot and ADB. I used this thread
https://forum.xda-developers.com/showthread.php?t=2277112&page=53
Click to expand...
Click to collapse
I went through that thread. I understand you rooted it but then started having problems? Like you couldn't download? Where you able to solve those problems? Now I am worried to root it.
Dylan2232 said:
I went through that thread. I understand you rooted it but then started having problems? Like you couldn't download? Where you able to solve those problems? Now I am worried to root it.
Click to expand...
Click to collapse
I'm not sure which post you saw, but I think my post on there were with an other device and yes, I have never bricked a device unrecoverable (yet).
That said, you will always be taking a risk when rooting or trying custom ROMS.
Then again if you never take risks you won't get anywhere. The question is how much are you willing to risk. In this case are you willing to risk your phone for the extra possibilities you might get when rooting it
First think you need to do before modifying anything is learning how to backup and restore.
JudgeDread11 said:
I'm not sure which post you saw, but I think my post on there were with an other device and yes, I have never bricked a device unrecoverable (yet).
That said, you will always be taking a risk when rooting or trying custom ROMS.
Then again if you never take risks you won't get anywhere. The question is how much are you willing to risk. In this case are you willing to risk your phone for the extra possibilities you might get when rooting it
First think you need to do before modifying any freething is learning how to backup and restore.
Click to expand...
Click to collapse
Thanks JudgeDread. Yes, I've rooted several phones in my life time. I understand the risk, but I tend to research about that particular rooting method with my phone before going ahead and doing it. I feel like the rooting method for my phone is particularly more risky, not because of what I read but rather from what info I am NOT able to find. Did you have a Huwaei Y5 2017 MYA l22 that you rooted successfully without issues? Can you point me to the instructions? That thread is a bit confusing.
Dylan2232 said:
Thanks JudgeDread. Yes, I've rooted several phones in my life time. I understand the risk, but I tend to research about that particular rooting method with my phone before going ahead and doing it. I feel like the rooting method for my phone is particularly more risky, not because of what I read but rather from what info I am NOT able to find. Did you have a Huwaei Y5 2017 MYA l22 that you rooted successfully without issues? Can you point me to the instructions? That thread is a bit confusing.
Click to expand...
Click to collapse
Yes exact same model, rooted and after several tries custom ROM.
I unlocked using the official method and then flashed TWRP in the recovery partition.
The difficulty was to get back into TWRP after rebooting. So I would advice to immediately install a root solution. I used Magisk. While root works without problem Magisk modules will only work if you use the f2fs workaround.
I am now running Resurrection remix (Android 7.1.2) without many issues. Only every now and then a forced close of the system UI.
It took some time to get it running. Because I used a different root solution the provided on the same page as the ROM. So on install use the provided SuperSU. After install you can change of you want.
Also the patches are needed. I still have bad videos on YouTube but haven't looked into the issue much yet.
hi , good news for Huawei y5 2017(MYA-L22) users.
Download latest lineage14.
visit to my blog.
cheers
https://p55novo.blogspot.com/2018/07...e-141-for.html
JudgeDread11 said:
Yes exact same model, rooted and after several tries custom ROM.
I unlocked using the official method and then flashed TWRP in the recovery partition.
The difficulty was to get back into TWRP after rebooting. So I would advice to immediately install a root solution. I used Magisk. While root works without problem Magisk modules will only work if you use the f2fs workaround.
I am now running Resurrection remix (Android 7.1.2) without many issues. Only every now and then a forced close of the system UI.
It took some time to get it running. Because I used a different root solution the provided on the same page as the ROM. So on install use the provided SuperSU. After install you can change of you want.
Also the patches are needed. I still have bad videos on YouTube but haven't looked into the issue much yet.
Click to expand...
Click to collapse
Thanks again for replying. Unfortunately though, 80 percent of what you just said flew over my head
I am not an expert but I can follow instructions! Any step by step guide on how to root it? So far I've gotten the unlock code from Huawei. I downloaded the ADB and fast boot folder and launched from that folder the cmd prompt. I type in "list of ADB deviced" and below comes an empty list. Please share what you did.
Dylan2232 said:
Thanks again for replying. Unfortunately though, 80 percent of what you just said flew over my head
I am not an expert but I can follow instructions! Any step by step guide on how to root it? So far I've gotten the unlock code from Huawei. I downloaded the ADB and fast boot folder and launched from that folder the cmd prompt. I type in "list of ADB deviced" and below comes an empty list. Please share what you did.
Click to expand...
Click to collapse
For rooting you need unlocked bootloader ( if you don't do ir then below won't work).
1)download the 4pda app from google play store and register an account .
2) download the TWRP.img file from 4pda website here is the link
https://4pda.ru/forum/index.php?showtopic=823938&view=findpost&p=74424572
3) enable developer mode in your phone by going to setting about phone , tap 6 times on the build number.
4)go to developer mode and enable usb debugging and oem factory unlock .
5) go to your pc install adb here link https://forum.xda-developers.com/showthread.php?t=2588979
6) now conect the phone to the pc and run cmd , type adb reboot bootloader . (Your device ahould restart and enter bootloader mode (white screen)).
7) now take the TWRP.img (must be copyied to desktop ) and type in cmd cd desktop.
8) type fastboot flash recovery TWRP.img (change the file name to TWRP ).
9) type fastboot reboot.
Now you have successfully install TWRP on your device.
Continue... If replied

Trying to install TWRP and Lineage . . . vbmeta is in the way

I've been trying for the last few days to root and install Lineage on a brand new S6 lite tablet. I've downloaded Lineage, Odin, stock rom, ADB/platform tools, Ls4 tool, the 7 whatever it is extraction tool. I've unlocked the bootloader (I can recite every option under developer options). I've installed Magisk hoping that it might help if I rooted the dumb thing (spoiler alert: it rooted, it didn't help). I've tried to install it using ADB (before reading that Samsungs don't play nice with it ). I tried to side load it with an SD card; tablet liked the card, poo poo'd the files on it. I've used ODIN in every way shape and form, it always says "Yay! You Pass!" then my tablet reboots saying "Boo! You Lose!". I then reinstall the stock ROM, try something else, reinstall stock ROM, try this solution, reinstall stock ROM. The latest and greatest hurdle: when trying to install TWRP I get the error message VBMETA Error verifying image, not signed (3), verification disabled bit is set. I found info on that here, downloaded vbmeta from my stock ROM, tried to use a blank vbmeta, even went overboard and did something with the PIT function in Odin (saw it in the internet, it HAS to be correct, right?). Nothing nothing nothing.
I've rooted and installed custom ROM on Samsung tablets in the past, but this is ridiculous. It would take me a LONG time to give all the details of everything I've tried, if needed I can. At this point it's the principal of the matter . . . I am going to make this happen one way or another, and any advice someone might have would be appreciated.
About me!
Samsung Galaxy Tab S6 tablet LITE, SM-P610, running Android 11, UI 3.1, WIFI only.
vstarjewel said:
I've been trying for the last few days to root and install Lineage on a brand new S6 lite tablet. I've downloaded Lineage, Odin, stock rom, ADB/platform tools, Ls4 tool, the 7 whatever it is extraction tool. I've unlocked the bootloader (I can recite every option under developer options). I've installed Magisk hoping that it might help if I rooted the dumb thing (spoiler alert: it rooted, it didn't help). I've tried to install it using ADB (before reading that Samsungs don't play nice with it ). I tried to side load it with an SD card; tablet liked the card, poo poo'd the files on it. I've used ODIN in every way shape and form, it always says "Yay! You Pass!" then my tablet reboots saying "Boo! You Lose!". I then reinstall the stock ROM, try something else, reinstall stock ROM, try this solution, reinstall stock ROM. The latest and greatest hurdle: when trying to install TWRP I get the error message VBMETA Error verifying image, not signed (3), verification disabled bit is set. I found info on that here, downloaded vbmeta from my stock ROM, tried to use a blank vbmeta, even went overboard and did something with the PIT function in Odin (saw it in the internet, it HAS to be correct, right?). Nothing nothing nothing.
I've rooted and installed custom ROM on Samsung tablets in the past, but this is ridiculous. It would take me a LONG time to give all the details of everything I've tried, if needed I can. At this point it's the principal of the matter . . . I am going to make this happen one way or another, and any advice someone might have would be appreciated.
About me!
Samsung Galaxy Tab S6 tablet LITE, SM-P610, running Android 11, UI 3.1, WIFI only.
Click to expand...
Click to collapse
Stumbled upon the answer to get Lineage OS and recovery installed . . . AND IT FREAKIN WORKED! Happy Dance!!!!!
vstarjewel said:
Stumbled upon the answer to get Lineage OS and recovery installed . . . AND IT FREAKIN WORKED! Happy Dance!!!!!
Click to expand...
Click to collapse
How did you fix? Just for a reader's curiosity sake.
Real_fakename said:
How did you fix? Just for a reader's curiosity sake.
Click to expand...
Click to collapse
I believe he used LineageOS Recovery instead of TWRP (since the latter has been abandoned by the developer due to too many problems getting it working properly).
MJPollard said:
I believe he used LineageOS Recovery instead of TWRP (since the latter has been abandoned by the developer due to too many problems getting it working properly).
Click to expand...
Click to collapse
What he said . . . still my hero!!!! Not sure if it matters or not, but I ended up using Heimdall/ADB to install Lineage. More key strokes but it worked the first time I tried it. Thumbs up for it
I'm hanging installing the recovery, see: https://forum.xda-developers.com/t/...s-on-galaxy-tab-s6-lite.4417629/post-86603873
How to reboot into recovery after flashing? I always land into Stock ROM
I mistakenly thought that Heimdell could get you right into recovery mode, but upon reading the instructions I sent you it says you need to boot into recovery manually . . . I apologize for the wrong info. I can say that I found that if you don't move them fingers FAST from the reboot mode to recovery mode buttons, you will keep getting plopped back to the stock ROM. Like the SECOND the screen goes dark you switch over to the power and volume up buttons, AND DO NOT LET GO! I do remember having a bit of a pause when booting into the Lineage recovery, and I thought I would have to start over when the recovery screen came up. I did a triple take, couldn't believe I got it to work.
vstarjewel said:
I mistakenly thought that Heimdell could get you right into recovery mode, but upon reading the instructions I sent you it says you need to boot into recovery manually . . . I apologize for the wrong info. I can say that I found that if you don't move them fingers FAST from the reboot mode to recovery mode buttons, you will keep getting plopped back to the stock ROM. Like the SECOND the screen goes dark you switch over to the power and volume up buttons, AND DO NOT LET GO! I do remember having a bit of a pause when booting into the Lineage recovery, and I thought I would have to start over when the recovery screen came up. I did a triple take, couldn't believe I got it to work.
Click to expand...
Click to collapse
Did your S6 happen to show "KG STATE: Checking" constantly? After 2 hours, even though the console shows that there was success, the device itself appears to constantly be downloading, as per the instructions. But even after 2 hours, there is no notification on the tablet that shows the download is complete.

Categories

Resources