Database Users

Rooting difficult s7 - How I did it.

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.

GioNEE e7 16gb soft-brick

Hey everyone, let me first of all say, that I am a noob when it comes to android (I'm using iphone) but my father got a gionee e7 recently and didn't liked how it looked and stuff. To the point, I tried putting a custom ROM on it but everytime I try, CWM gives Section 7 error. I read that if u remove the asserts from the script file it fixes it, but there weren't any asserts lines in any of the files. I tried at least 4 different ROMs, even tried stock rom with QCOM tools but nothing works. Currently, the phone is stuck at the Elife logo and that's it. Before I could access CWM from there but now i can't even do that. Any help is appreciated, if you need any info, just post a reply.
Thanks a bunch, and once again ,sorry, a big noob on android here.
Edit: I forgot to mention, CWM was in chinese so i messed around with it a bit. i went to advanced then clicked recovery or something, the phone turned off and i haven't been able to get to CWM since.

Still no solution, anyone?

backup not working

my last backup and my original backup (like in the thread) niether are working , so now i dont have anything , i do have twrp , but how do i get a factory reset ? through fastboot ? how do i know what image to take? theres about ten images in the google site?i will follow the directions of either with or without storage doesnt matter right now, just need to know what image to take , you should i just get one of the 6.0's or one of the 6.1' s ? or does it matter

or is there a factory .zip that i can try n flash , im not sure if i can do that anyway

im trying to re install the factory image , ive gotten back to the lil android , but it wont get me back to "factory reset"

it helps if you slant correctly ? \ instead of / and not drink whiskey while your having fun!

for those of you who bought a NEXUS phone and you are just using it like a standard carrier thingy , put it back up for sale on ebay or craigslist and let some one who wants to learn have fun!! Trust me if your stock , havent done a thing , get with the program people , take a risk and have some fun, youll find out that the XDA devs are smart as hell , they know what they are doing and they will help you , but you have to want to try it , you have to give in , yes it a risk , but hell , think about how much you will learn , read ,READ, READ , ask questions ! Trust me , it is fun , and if it isnt , your not a geek anyway , get a crApple and be like everyone else!

My guide might be helpful for you:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

LeEco Le 1 pro X 800 _US Colour Mod Fix

I Got a Flashable Zip From LeTV Forums & I think Its Ported From LETV Chinese Firmware ,
Installed & tested , its Working Good , You Need Rooted Phone Or TWRP To Install The Same ,
After Getting This Settings , Screen is More Nice to the Eyes ,
Activated Colour Mode
1. LeEco
2.Vivid
3.Natural
4.Soft
Soft is More or Like Night Mode ,
Zip Is From : drive.google.com/file/d/0ByEOR9M5bXAtX1NRZ0dTbUN4Y3M/view
I Dont Know Who Is The Maker , But As Per Letv Forums Big Thanks to " CheduSietesiete "
Regards
Abhilash

Thank you, I'll try it.

Yes it works, waiting for the fix of the Gyroscope (X).
Thanks again.

Is it possible to get the phone rooted without TWRP?
Edit: I asked this question because whenever i install twrp my fone gets the recovery brick. But here's how i used this thing to fix the colour method.
First I installed twrp and installed this zip. Since my phone was stuck in recovery loop so I installed the stock recovery which fixed the recovery loop and went to settings to see if it worked. and It worked. I kinda hated the screen for the colours. i can finally enjoy the phone at its Most

TheDamnedRey said:
Is it possible to get the phone rooted without TWRP?
Edit: I asked this question because whenever i install twrp my fone gets the recovery brick. But here's how i used this thing to fix the colour method.
First I installed twrp and installed this zip. Since my phone was stuck in recovery loop so I installed the stock recovery which fixed the recovery loop and went to settings to see if it worked. and It worked. I kinda hated the screen for the colours. i can finally enjoy the phone at its Most
Click to expand...
Click to collapse
Glad to Know Yours Also Worked ,
You can Root the Phone without Install Custom recovery , Just Google it the same for answers , I think a lot of XDA threads Also Discussing the same ,
comparing to Custom recovery rooting This Rooting is not an easy process ,
Any Help , replay back , I Will Post a replay with step by Step , You can Go through that process ,
Regards & Good Day
Abhilash

I've tried installing TWRP. Its better, for obvious reasons. but I tried installing it on my phone but it always gets stuck in recovery loop. I've tried different versions of TWRP recovery but same problem.. Dont know how to fix it, im not too good with phones, just know the basic stuff :3
thanks again for sharing the colour fix <3

TheDamnedRey said:
I've tried installing TWRP. Its better, for obvious reasons. but I tried installing it on my phone but it always gets stuck in recovery loop. I've tried different versions of TWRP recovery but same problem.. Dont know how to fix it, im not too good with phones, just know the basic stuff :3
thanks again for sharing the colour fix <3
Click to expand...
Click to collapse
I Dont Know Why you are facing Recovery loops Also assuming that you are not tried this recovery
I am Using This Recovery & Working Cool
I Will Give you Quick Guide To TWRP Installation ,
Use Link androidfilehost.com/?w=files&flid=65930
Download Tools 2.7 , Which Is basically For Cuoco Firmware But Sufficient For Our needs , Extract Files & Put It in a folder , and run batch Files ,
As per Your Prevision Post , Assuming that You Unlocked Boot Loader , if not Unlock Boot loader First , You can see Batch Files for Everything , Lastly Run Flashrecovery.exe , Which Will flash Custom Recovery to your Phone
Then report back to me ,
Regards & Good Day
Abhilash

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.