Related
CF-autoroot does not support Galaxy Tab 4 7'', so here is what I call Inception-Auto-Root for this device (explanation for the name will come later). It works pretty much like CF-AutoRoot work. You end up with supersu installed, and it reinstalls stock recovery when done.
DISCLAIMER
==============
You void your warranty when you flash something to your device
Use at your own risk, I'm not responsible for bricking your device.
XDA:DevDB Information
SM-T230 Inception-Auto-Root , Tool/Utility for the Samsung Galaxy Tab 4
Contributors
tgalal
Source Code: https://github.com/inception-android/inception_base_samsung_degaswifi
Version Information
Status: Testing
Created 2015-06-06
Last Updated 2015-06-06
So you just install this from odin? why not flash twrp if your warrantly goes anyways?
thelous said:
So you just install this from odin? why not flash twrp if your warrantly goes anyways?
Click to expand...
Click to collapse
Maybe someone wants to root their device only, but not install twrp. Plus it's easier/quicker to create an autoroot package than create and maintain a fully functional twrp img
tgalal said:
Maybe someone wants to root their device only, but not install twrp. Plus it's easier/quicker to create an autoroot package than create and maintain a fully functional twrp img
Click to expand...
Click to collapse
But in twrp you can root and flash stock recovery and still gain OTA updates. This one stops them. Anyways some people dont like flashing many things in their devices and rooting with twrp is little bit tricky.
Ok, so will this also work for the SM-T230/NU? I'm assuming it will, but making assumptions when flashing can be a bad idea. Anyone know the answer??
Thanks in advance!!!!
PAinguINx said:
Ok, so will this also work for the SM-T230/NU? I'm assuming it will, but making assumptions when flashing can be a bad idea. Anyone know the answer??
Thanks in advance!!!!
Click to expand...
Click to collapse
I don't know for sure about this one, but this method definitely will work, as will this one too
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is the well known Build of Jiayu Germany Lollipop Release Candidate 5 (latest) for Jiayu S3 (Advance/Basic) with MTK 6752 SoC
There's also a modified version , for the new Jiayu s3 Pro ( with 32GB of internal memory ) also MTK6752
This is being posted here, as this is a full SPFlashTools "Base" ROM, usually used to recover your device
( or if you want to roll back to Lollipop ...)
The "REPACK" Version is simply the same RC5 Rom, but with latest M.A.D. TWRP already included
There's also a modified version for the s3 Pro (32GB)
The Rom should be flashed in "UPGRADE MODE" on SPFlashTools. (Doesn't matter in what ROM / OS you currently are ...)
DO NOT flash any SP Flash Tools Jiayu s3 (old 16gb) roms on the new Jiayu s3Pro (32GB)
--> Preloader, partitions are different, you'll get an hard brick.
Installation Instructions:
BACKUP EVERYTHING, This will ERASE everything from your internal phone memory (pics, videos, data, etc )
Turn OFF the phone
Open MediaTek SPFlashTools
Load mt6752 Scatter
Choose "Upgrade Mode"
Press "Download"
At this moment, plug USB Cable to phone, it'll start flash ...
Some Jiayu S3, require BOTH Volume Keys to be pressed , while you plug USB Cable to enter in "download Mode"
If you wish to upgrade to latest M.A.D. Android Nougat, after you flashed RC5, it's recommended that you let the RC5 boot up, then you can go back to recovery ( Latest M.A.D. Recovery included already)
Place AOSP Nougat Rom on internal memory/ external SDCard
WIPE ALL
Flash AOSP and GAPPS & SuperSu (latest two optional)
Download ROMs from "XDA DevDB Download Section"
Choose the right rom, for your Jiayu S3 variant (s3 advance / basic 16GB) or ( s3 pro 32GB )
Working:
Everything
The Rom Changelogs, and old discussion can be found on this thread :
https://forum.xda-developers.com/jiayu-s3/development/rom-jiayu-s3-5-1-1-t3217241
GPL Compliance:
https://github.com/MediatekAndroidDevelopers
XDA:DevDB Information
[ROM] [REPACK] [ 5.1.1 ] RC5 Lollipop Jiayu S3 & S3 Pro [MT6752], ROM for the JiaYu S3
Contributors
superdragonpt, DerTeufel1980
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: SP Flash Tools
Based On: MediaTek AOSP
Version Information
Status: Stable
Created 2017-01-25
Last Updated 2017-01-25
Reserved
,,,,,,,,,,,,,,
Please include boot from AICP 10 (with fixed wi-fi hotspot).
superdragonpt said:
ROMs will take a while to be uploaded ...
slow speed...
Click to expand...
Click to collapse
thanks man.....
waiting for the s3 pro version....
My net provider is having issues, I currently have no home connection, hopefully they'll fix this today, for me to upload
Bb
ROMs being uploaded
superdragonpt said:
ROMs being uploaded
Click to expand...
Click to collapse
thank you so much...
hope flashing rc5 and then stable 7 fix my low signal connection on s3 pro
All done ...
Can you also upload the SPFT flash tool so that people would use a similar version and reduce variables and become easier to debug when a problem arises?
I'm sorry for the stupid question but are de download links?
Have searched in the download section but keeps sending me back to this post!
Enviado do meu Redmi Note 3 através de Tapatalk
Found it, sorry for double post!
Enviado do meu Redmi Note 3 através de Tapatalk
Upgrade successfull!
Thank you. This has helped me gretly with my quest to upgrade 4.4 -> 5.x -> 7.x.
I had a problem with uploading through SP Flash Tool that it wouldn't start to download to phone, but after many tries i finally changed USB port, and then it worked like a charm.
I have a question though. Should i stay on this ROM or upgrade to 6.0.1 or what? The problem is that Xposed framework does not work yet with 7.x, so untill it does, i will stay on system that does support it.
AgiZ10 said:
Thank you. This has helped me gretly with my quest to upgrade 4.4 -> 5.x -> 7.x.
I had a problem with uploading through SP Flash Tool that it wouldn't start to download to phone, but after many tries i finally changed USB port, and then it worked like a charm.
I have a question though. Should i stay on this ROM or upgrade to 6.0.1 or what? The problem is that Xposed framework does not work yet with 7.x, so untill it does, i will stay on system that does support it.
Click to expand...
Click to collapse
Then go with AICP11 MM its the best MM rom for the phone with xposed (mm) available ...
superdragonpt said:
Then go with AICP11 MM its the best MM rom for the phone with xposed (mm) available ...
Click to expand...
Click to collapse
Thanks, done.
Will continue replying there if something comes bugs me
A huge thank you for the s3pro version. I have just bought a second S3 32gb without knowing that it was different to my old S3 32gb, and bricked it trying to install the old rc5 that is on my old phone. This version rescued the phone from death!!
Can I use TWRP to install SuperSU and root it? I'm guessing there's zero chance of flashing 7.1.1 on the s3pro.
StoneTheKiwis said:
A huge thank you for the s3pro version. I have just bought a second S3 32gb without knowing that it was different to my old S3 32gb, and bricked it trying to install the old rc5 that is on my old phone. This version rescued the phone from death!!
Can I use TWRP to install SuperSU and root it? I'm guessing there's zero chance of flashing 7.1.1 on the s3pro.
Click to expand...
Click to collapse
I've just found that the recovery is the chinese one, not twrp. Reflashing just recovery does not change this. The build number is 20160302-190806. Any ideas on what might have happened here?
I made this thread mainly for the newer s3 33GB variant...
Since I also got the 32gb variant, after my old s3 died
You just need to follow instructions on the first post
Download full rc5 repack for the 32GB variant
And flash in "upgrade mode"
You,ll get the newer MAD twrp, that is also Nougat compatible.
After flash, just boot to recovery , full wipes (including data, and flash newer Nougat release)
Cheers
superdragonpt said:
I made this thread mainly for the newer s3 33GB variant...
Since I also got the 32gb variant, after my old s3 died
You just need to follow instructions on the first post
Download full rc5 repack for the 32GB variant
And flash in "upgrade mode"
You,ll get the newer MAD twrp, that is also Nougat compatible.
After flash, just boot to recovery , full wipes (including data, and flash newer Nougat release)
Cheers
Click to expand...
Click to collapse
Thanks for your reply. I've just done it all again - downloaded the PRO pkg afresh and flashed as 'upgrade', but again booting to recovery shows a chinese menu. I also flashed in 'format all' mode, but the same result. I'm downloading the pkg from the 'downloads' section of this forum, and it unpacks to show recovery as 'S3_h560_TWRP_3.0.2-0' at 13,074kb. The recovery from the old rc5 pkg is a different size - I suppose that can't be used without rewriting the scatter file? Or does the scatter file reference the recovery that's recommended for your latest 7.1.1 rom? I could just get that separately and copy it in.
Apart from blaming the pixies, I really don't understand what is going wrong here.
Stranger and stranger. I replaced the recovery with the one hosted on mediafire for 7.1.1 (though that has a space in the filename which had to be removed for the scatter txt to recognise it) and after flashing the phone was bricked. Then replaced recovery with the one from rc5 and again it was bricked. Then unpacked afresh the pro pkg and flashed with that in 'format all' mode - this time it booted to chinese recovery but refused to boot normally. Then reflashed in 'upgrade' mode and now it boots normally but refuses to boot to recovery. Perhaps the hardware has been changed even further, or perhaps the gods are just laughing at me, but I've run out of options now. The problem is that supersu won't install without updating itself (though it's 2.79) and it fails to update under the 'normal' update option and doesn't have a twrp recovery to update through. Hence the phone can't be rooted.
Sorry for this question, please how can I revert to this ROM I'm already on 7,1.2, what does repack means or how should I repack it ,any possible way to use spflashtool for this ROM, your answer is highly needed urgently please to whom ever knew
This is a ROM that I put together because Verizon Galaxy S5 locked boot-loader phone has very little support, and we cant experience the stock Android Experience.
Any developer could customize this ROM and post their own version.
Whats included in this ROM:
-Google Apps instead of Samsung apps.
-Gravity Box
-Xposed
-Build.prop performance X tweaks
-Pixel Launcher
-Pixel Boot Animation
-Removed Verizon Bloatware
AOSP/Goodlock System UI - Customizable
Bugs:
Fingerprint to unlock- please disable fingerprint lock -++ if u want to use fingerprint install C locker pro and disable lockscreen++
Instructions:
Move to SD card, install - pretty much
to have system UI mods xposed; gravity box is recommended
Unlocked Phones.
Remove boot.img in the Flashable zip. and place any other kernel
XDA:DevDB Information
AOSP-Touchwiz , ROM for the Verizon Samsung Galaxy S5
Contributors
emeka1999
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: Touchwiz
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2018-11-12
Last Updated 2019-01-16
Download Link
https://mega.nz/#!VMBQwSQB!ARlWmnzOyDsHIAJZuL_6RUYFGrLVb4R1tIRMkuBaODI
Thanks for the work. I'm probably going to give this a shot tomorrow and will let you know what I think.
The title says "Unlock/Locked Bootloader"—is this to say I could flash this on my unlocked bootloader G900V without any trouble? I'd like to test ride this for a friend whose S5 whose bootloader may not be unlockable.
any way to root or install magisk in this rom_??
zihar said:
any way to root or install magisk in this rom_??
Click to expand...
Click to collapse
Depends. If you're using a bootloader locked S5, then no. If you have the unlockable bootloader S5, then yes.
Edit: Apologies, it just occurred to me that this only applies if the ROM doesn't mess with the bootloader status, which it very well might, given @zihar's troubles.
J-Lindo said:
Depends. If you're using a bootloader locked S5, then no. If you have the unlockable bootloader S5, then yes.
Click to expand...
Click to collapse
As in flashing a Magisk-vXX.X.zip in TWRP, correct?
chaos_jockey said:
As in flashing a Magisk-vXX.X.zip in TWRP, correct?
Click to expand...
Click to collapse
i have unlocked bootloader... but after flashing magisk the rom stuck at samsung Galaxy s5 logo but no past to the second splash and have the boot led on (blue blinking)....
chaos_jockey said:
As in flashing a Magisk-vXX.X.zip in TWRP, correct?
Click to expand...
Click to collapse
Correct.
zihar said:
i have unlocked bootloader... but after flashing magisk the rom stuck at samsung Galaxy s5 logo but no past to the second splash and have the boot led on (blue blinking)....
Click to expand...
Click to collapse
Now that's strange. My first thought would be maybe a corrupted Magisk .zip? Try flashing the Magisk uninstaller, see if it boots normally, then try again with a fresh downloaded .zip.
On the other hand, since the OP hasn't answered my question yet, it could be that the ROM re-locked your bootloader. Flashing Magisk in that case, which messes with the boot.img, would definitely mess with your system. In that case, I would hope flashing the uninstaller would solve the problem. I think you'll have to go through the process of unlocking the bootloader all over again too.
J-Lindo said:
Correct.
Now that's strange. My first thought would be maybe a corrupted Magisk .zip? Try flashing the Magisk uninstaller, see if it boots normally, then try again with a fresh downloaded .zip.
On the other hand, since the OP hasn't answered my question yet, it could be that the ROM re-locked your bootloader. Flashing Magisk in that case, which messes with the boot.img, would definitely mess with your system. In that case, I would hope flashing the uninstaller would solve the problem. I think you'll have to go through the process of unlocking the bootloader all over again too.
Click to expand...
Click to collapse
after some try i cant get root in this rom :c its look graet but i cant live without root
zihar said:
after some try i cant get root in this rom :c its look graet but i cant live without root
Click to expand...
Click to collapse
I''ve got the emmc 15. I got magisk 17.1 to 'work'.
This is what I've tried; after flashing the rom extract the boot.img from the aosp-touchwiz zip, install magisk manager and patch the boot.img, reboot to twrp and install, install image and select the patched_boot.img, swipe and pray. Had mine lock up at boot, flashed magisk uninstaller, installed the image again and it worked. Although, magisk states it's in core mode only, I tried to have it do its thing to run normally by unchecking the box but it wound up locking up the rom, so rinse and repeat. So, it's root but not through and through? Because I can't seem to move an app to system/priv-app when I do it fails to find the package, I've tried root explorer, es file manager, link2sd, lucky patcher, and TWRP (mounting system); either locks the rom, kills the app, or somehow removes root entirely.
I just want a rom with magisksu and that won't throw a fit when I move an app to system.
---------- Post added at 02:42 AM ---------- Previous post was at 02:31 AM ----------
J-Lindo said:
I think you'll have to go through the process of unlocking the bootloader all over again too.
Click to expand...
Click to collapse
Personally I've only gone through the process of unlocking the bootloader once on my emmc 15, TWRP is also installed as recovery.
My emmc 11 on the other hand is touchy and if you're not careful it'll lock up and you'll have to start over. The emmc 11 (locked bootloader) is touchy in general when dinking around with root/safestrap but the guides here are thorough, a bit more than the emmc 15 threads it seems.
Does installing a ROM like this one, in which bloatware was removed, result in more useable space from the phone's internal storage? Specifically, does it result in more storage for installing apps?
this thread needs to be deleted
After installing from rooted lollipop via safestrap its just stuck on the colored dots loading
Hey there, so I have attempted to root my Samsung S7 edge through TWRP, only to get to the stage where i flash my files, Magisk and no verity, and get an error. I searched around and found out I needed to flash a stock boot.img, so I found on, flashed it and got stuck on the startup screen. After this, I found a new, S7 Oreo one and used that, now i can hear the volume buttons when I press them but have a red screen. All i can do on my phone is access TWRP, the downloading screen and the red screen, any ideas would be amazing. By the way im not very good with this kind of stuff (As you can probably tell).
TheAquarius said:
Hey there, so I have attempted to root my Samsung S7 edge through TWRP, only to get to the stage where i flash my files, Magisk and no verity, and get an error. I searched around and found out I needed to flash a stock boot.img, so I found on, flashed it and got stuck on the startup screen. After this, I found a new, S7 Oreo one and used that, now i can hear the volume buttons when I press them but have a red screen. All i can do on my phone is access TWRP, the downloading screen and the red screen, any ideas would be amazing. By the way im not very good with this kind of stuff (As you can probably tell).
Click to expand...
Click to collapse
Why in the actual hell did you flash some random stuff without asking.You never flash a boot img without confirming the version and the type of boot.img it is.For example you can't flash AOSP boot.img or kernel on Samsung.Or flash Samsung on AOSP.Similarly you don't flash Nougat on Oreo or Oreo on Nougat.You should have made a backup before messing things up.More Importantly you should've converted to Lineage OS immediately after TWRP for easiness.And Most Importantly magisk is only stable for Lineage and Does kinky stuff with Samsung's Version of Android.Your best bet is to get the current running OS with exact same build no date and all specification and extract the boot img and flash it.Or you can ask in S7 forum to provide one with same build and name.Along with OS version
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
Why in the actual hell did you flash some random stuff without asking.You never flash a boot img without confirming the version and the type of boot.img it is.For example you can't flash AOSP boot.img or kernel on Samsung.Or flash Samsung on AOSP.Similarly you don't flash Nougat on Oreo or Oreo on Nougat.You should have made a backup before messing things up.More Importantly you should've converted to Lineage OS immediately after TWRP for easiness.And Most Importantly magisk is only stable for Lineage and Does kinky stuff with Samsung's Version of Android.Your best bet is to get the current running OS with exact same build no date and all specification and extract the boot img and flash it.Or you can ask in S7 forum to provide one with same build and name.Along with OS version
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Alright mate thanks ill have a look.
TheAquarius said:
Alright mate thanks ill have a look.
Click to expand...
Click to collapse
Can I just watch a video on how to flash my phones original firmware through twrp?
Hello,
I have a Samsung Galaxy S10e, and recently I've decided to flash a custom ROM on it.
I upgraded from Android 10 Stock Samsung to Android 11 LineageOS 18.1 following this and this guide.
All successful.
However, after some minutes, I wanted to try out a different ROM, so I installed Pixel Experience (which was based on Android 10 -- big mistake). This ended up resulting in a soft brick, throwing me an 'REV Check Fail Device 9 Binary 8' error everytime I turned on the device. I couldn't get into recovery mode - only download mode.
I managed to fix this by waiting for the Samsung's Stock Firmware (based on Android 11) to come out (did after some hours, I was so lucky I didn't have to wait that long) so I could flash it and go back to stock using Odin. All good, the phone boots, everything works as expected -- no problems what so ever.
I should've made a backup in TWRP, in case something went wrong before flashing Pixel Experience (?), but I didn't. I also should've known that I couldn't downgrade. Anyway...
When I enter download mode, the following important info is displayed:
PRODUCT NAME: SM-G970F
KG STATE: Checking
FRP LOCK: OFF
OEM LOCK: OFF (U)
Secure Download: Enabled
WARRANTY VOID: 1 (0x0e03)
I believe my bootloader is unlocked, since it's enabled and grayed out in developer otions. I also believe that I have no custom recovery (since I flashed Samsung's Stock Firmware), because when I press the recovery button combination, it doesn't boot into TWRP.
My questions:
1. Should I repeat the process in here when flashing TWRP again since I literally flashed the samsung stock firmware? I'm guess I'm comming from "stock" even though I already have some steps complete? Should I flash the " multidisabler-samsung-2.* " too? I already did once, do I need to do it again since I flashed the Stock Samsung firmware?
2. Is there anything you'd recommend me doing to prevent stupid actions like I had above?
3. As long as I have the Stock Samsung Firmware and the phone boots into download mode, I'm good right?
4. Is TWRP 3.5.0 compatible with the S10e Android 11? Or does android versions not matter with recoveries?
5. Which ROM would you recommend to have a good Pixel-Like Stock Android experience? I'm debating wether I should use the PixelExperience again (I used it on my nexus 5x and was happy with it) or if I should try out something else. I also believe it's not yet available unofficially, so I'd have to wait.
6. Would you recommend me installing a GSI?
Thanks!
Questions updated
bump!
Too bad you didn't get an answer... Did you find anysolution ?
Having issues installing TWRP with odin on a s10e..