"set warranty bit recovery" sm-t350 - Samsung Galaxy Tab A series Questions & Answers

Just got this tablet today 2nd hand. Installed twrp, wiped tablet, got it set up. I went into twrp to back everything up and now when i reboot into system i get this message:
"set warranty bit recovery "
and it boots back into twrp.
Is tried powering the device down and and then restarting but it keeps going into twrp.
It looks like i can flash the stock firmware in odin to fix this, but does anyone know can i just flash the custom kernel (in odin) that's available for the T350? Would that be enough.
Thanks
Sent from my Nexus 6 using XDA-Developers mobile app

So flashing the kernel found on this site for the 350 works if anyone comes across this error. I flashed it in odin (as opposed to twrp)
Sent from my Nexus 6 using XDA-Developers mobile app

rrrrrrredbelly said:
Just got this tablet today 2nd hand. Installed twrp, wiped tablet, got it set up. I went into twrp to back everything up and now when i reboot into system i get this message:
"set warranty bit recovery "
and it boots back into twrp.
Is tried powering the device down and and then restarting but it keeps going into twrp.
It looks like i can flash the stock firmware in odin to fix this, but does anyone know can i just flash the custom kernel (in odin) that's available for the T350? Would that be enough.
Thanks
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
If you installed the CF-Autoroot for your SM-T350 (I have this device) then it will softbrick your device, I do not know the cause, but I tried it. Also if you install TWRP for SM-T350, install the Lollipop version! The Marshmallow version is not compatible with 3rd party apps yet but the Lollipop version does. If you want to install SuperSU, then install from here: https://download.chainfire.eu/1012/SuperSU/SR3-SuperSU-v2.78-SR3-20161103171345.zip
YOU HAVE TO FLASH IT IN TWRP! INSTALL LOLLIPOP VERSION TWRP BEFORE YOU FLASH!!! ALSO, IF TWRP ASKS YOU TO INSTALL ROOT, DON'T LET IT!
Happy Flashing and Hope I helped.

Related

Unable to update to 4.4.3 due to custom recovery

Hello,
I run rooted Nexus 4, Stock ROM running Franco Kernel #207 with TeamWin recovery.
My device is promoting me to install the new update but when I run the installation and automatically restarts the device it goes straight to recovery and nothing happens afterwards. So, I end up loading my device normally with nothing installed. I have been sitting on this update for 2 days so far with no solution found. Are there any way to bypass the recovery so that installation can go normally?
I really would like to just install the update without a fresh installation for now, if I started to face some issues after the installation I guess I will have no other choice but to do a fresh installation.
Thank you.
You may be able to flash update if you install stock recovery
Sent from my Nexus 4 using Tapatalk
Zetsubou. said:
Hello,
I run rooted Nexus 4, Stock ROM running Franco Kernel #207 with TeamWin recovery.
My device is promoting me to install the new update but when I run the installation and automatically restarts the device it goes straight to recovery and nothing happens afterwards. So, I end up loading my device normally with nothing installed. I have been sitting on this update for 2 days so far with no solution found. Are there any way to bypass the recovery so that installation can go normally?
I really would like to just install the update without a fresh installation for now, if I started to face some issues after the installation I guess I will have no other choice but to do a fresh installation.
Thank you.
Click to expand...
Click to collapse
You have a bunch of stuff which is not allowing you to take the ota. You should try this, it'll work in your situation http://forum.xda-developers.com/showthread.php?p=53176897
Sent from my Nexus 5 using XDA Free mobile app
Zehlek said:
You may be able to flash update if you install stock recovery
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
it will fail cause he's using custom kernel
What if I restored the stock kernel and stock recovery and tried to install the update?
Zetsubou. said:
What if I restored the stock kernel and stock recovery and tried to install the update?
Click to expand...
Click to collapse
You have to be on stock system, kernel and recovery. You'll also lose root
Sent from my Nexus 5 using XDA Free mobile app

Nvidia SHIELD Portable Root

Hi everyone!
This morning I woke up to find my SHIELD with the so waited notification of Lollipop update. I'm really happy to finally have lollipop running on my device, but sadly I found a problem after the update. I was trying to re-root my device, but neither the SHIELD RAM tool or Root Genius could do the trick. But I didn't gave up, I searched in Google any way to root my SHIELD with the still fresh update, and found that the Kinguser app can root it without trouble.
You just need to download the apk, install it on your SHIELD and open it.
Btw, the old recovery isn't working anymore, you can flash it with the RAM tool, but the device will reflash the stock recovery.
Downloaded and it's says shield portable android 5.1 not supported...
Sent from my SM-N910P using Tapatalk
kenmacker said:
Downloaded and it's says shield portable android 5.1 not supported...
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
You need to turn on USB Debugging, and then run the app.
USB debugging is now turned on but it says root access is unavailable
Sent from my SM-N910P using Tapatalk
work great
thanks
Old recovery is working for me - it's CWM 6.0.4.4.
I had to flash it twice, first time it was reflashed to stock.
PS: TWRP 2.8.5.0 (unofficial) is working too.
kenmacker said:
USB debugging is now turned on but it says root access is unavailable
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Look if you have your SHILD's bootloader unlocked, that may be causing the problem.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
I wanted a full restore/clean version of the ROM without waiting for the factory image to be updated.
I flashed the 101 Factory Image from here. I notice that 103 is there now so just skip this step and flash that now.
I noticed that after flashing the latest SuperSU the device would never boot.
So I had to use KingRoot but for me the apk method never worked so I went with the desktop version.
To get Root I went to KingRoot's XDA page and downloaded the Desktop version.
When running the program it is all in Chinese but is thankfully idiot proof with its one big button on it. Just make sure that USB Debugging is turned on and wait for it to finish, it will reboot during the process.
KingRoot installs its own version of a Super User advisor so it will prompt when something needs root access and for most people that would be enough but I prefer SuperSU, Thankfully KingRoot has a set of instructions, follow these to the letter and it will guide you through removing KingRoot and installing SuperSU. During that process you will get a lot of errors saying that files are no longer there, just ignore them, that means the initial uninstall got the files.
Once I was able to ensure that SuperSU and Root where staying after a reboot I re-installed TWRP (for some reason I couldn't get CWM to stick after a reboot but oh well I like TWRP more >_>) and made a backup of my stock rooted device.
I then went to this page and grabbed the Unofficial Xposed 5.1 .zip and went to this page and grabbed the Xposed Installer.
Rebooted and waited for the App Cache to re-build as the Xposed framework nukes it then installed my mods as normal.
Took a little bit longer than normal to update but oh well, Everything is working smoothly and I'm happy with it.
Rooted my Shield two times wth CWM without problems.
astuermer said:
Old recovery is working for me - it's CWM 6.0.4.4.
I had to flash it twice, first time it was reflashed to stock.
PS: TWRP 2.8.5.0 (unofficial) is working too.
Click to expand...
Click to collapse
Which cmw did you use and where did you get it? I tried using flashify with twrp and it says boot failed when booting into recover.
astuermer said:
Rooted my Shield two times wth CWM without problems.
Click to expand...
Click to collapse
Give me a few mins. I will upload my Recovery package...
Here we go. I've flashed and rooted my SHIELD successfully after OTA upgrade - and today again after flashing the clean 103 factory Image.
SHIELD-Portable-Recoveries.zip
Update: I've attached a ZIP file with 4 different recoveries. Simply execute the Batch file I've included (if you're on Windows) and select 1-4.
stock KitKat recovery (from update 101)
stock Lollipop recovery (from update 103)
ClockworkMod recovery (CWM) 6.0.4.4 (somewhere from XDA, but couldn't find the link)
TWRP recovery 2.8.5.0 (from here)
From @Steel01 The TWRP located here may give people problems and we should be using the one in the MultiROM TWRP located here.
Source here.
EDIT: I will test tonight and see what happens when you image with the factory image and just install MultiROM's TWRP and then try SuperSU's latest BETA.
I was trying to use the other TWRP before and could never boot which is why I did the KingRoot method.
If you wanted to change Kinguser to SuperSU all you have to do is download any "Control Rotation App" and set it as Portrait Mode (if it didn't work make sure that the Nvidia Shield Portable is in a sitting position and flip it , It should work , If not try installing other apps), Install "Super-Sume" , Then touch the big blue button , After that wait until the process is done , You should see SuperSU, In the other hand Kinguser has already vanished (I'm not sure if SuperSU will open automatically or not), Install the binary, Reboot, Done.
Have a nice day

Root & recovery for LG G Pad 8.3 v500 on Lollipop (5.x.x) in 5 minutes with no PC

Hey XDA!
I updated my LG G Pad 8.3 to the korean stock 5.0.2 a while back, and now I wanted the AOSP Marshmallow rom on it - but I had no root or recovery!
Turn out (after three hours of infinite searches and no progress) that the solution is really easy - and can be done on the tablet with no PC!
Just enable USB debugging, download the KingRoot app (http://www.kingroot.net/) and let it root the device for you - it loads pretty slow but works great.
Then follow this link to install TWRP (https://twrp.me/devices/lggpad83.html) by following their link to the Play Store. Install the TWRP app, select your device (v500) and the latest recovery image, then confirm the recovery location and let it install the recovery image for you. Mine gave an error but booted right into TWRP afterwards despite saying failed.
And that is it!
Hey dude, after almost a year, someone finnally discovered how to do it! .But I have one problem, I can install the 2.8.7.0 twrp version, but I can't boot into recovery. It just stays in the LG logo, with the (normal) error text on the top left. How did you make it?
Interesting... k
Perrotti said:
Hey dude, after almost a year, someone finnally discovered how to do it! .But I have one problem, I can install the 2.8.7.0 twrp version, but I can't boot into recovery. It just stays in the LG logo, with the (normal) error text on the top left. How did you make it?
Click to expand...
Click to collapse
Have you tryied installing something like quickboot?
I'm really interested in root not to change ROM but to remove bloatware, install a serious ad blocker and perform nandroid backups.
FandangoL said:
Have you tryied installing something like quickboot?
I'm really interested in root not to change ROM but to remove bloatware, install a serious ad blocker and perform nandroid backups.
Click to expand...
Click to collapse
I have the same issue.
root ok
twrp 2.8.7 ok
reboot to recovery stay on the boot logo with "boot certification verify problem" error.
Tried quick boot same issue ...
I tried KingRoot a few months ago and had similar problems. It was kind of like a partial root that worked of a fashion but not completely.
The only way I know of to go from Lollipop to a custom ROM is to download a KitKat kdz and flash it through the Mobile Tool and then root that. Quite a hassle - and one I'm just about to start now.
I've been off the V500 forum for a little while, so maybe there is a better solution out there.
I only rooted because I'm scared of bootloop since in this thread still no answer on how to boot to recovery.
Actually I installed and used successfully an ad blocker and titanium but SuperSU can't be installed because of the missing twrp.
I hope that the thread creator will answer on how to go to recovery.
Sent from my LG-D855 using XDA Free mobile app
kingroot is still dodgy?
Do you mean?
Sent from my LG-D855 using XDA Free mobile app
it still sends alot of data to china servers?
Ok now it's clear. I will check using a firewall on the Wifi router.
Do you know where to get more information on this?
Anyway I used information from this site:
http://zidroid.com/how-to-get-ride-and-replace-kinguser-with-supersu-app/#comment-8930
to remove kingroot and install SuperSU
Sent from my LG-D855 using XDA Free mobile app
@FandangoL
Thanks you for the tip, it works great.
Anyone had luck with this?
I get the Boot Error message when I try to boot with twrp.
I avoided to install twrp because another guy wrote that seems not working.
Root is enough for what I need
Sent from my LG-D855 using XDA Free mobile app
Thank you very much!!!!!!!!!!!!!!!!
Had to install - uninstall KingRoot 2-3 times before SuperSU would work. Lost root access the two first times I replaced KingRoot with SuperSU, but suddenly it worked
When installing recovery image with twrp I get a message that installation failed, but anyway twrp reports that recovery image is installed. (Same thing happened with KingRoot, but then recovery image was not installed)
When I try to boot in to recovery I get the annoying boot error message
Just flashed my G pad V500 20f with Hongkong v50030b. Applied root using this tutorial here. It works. Thank you.
Then, replaced Kinguser with Supersu from the link provided by @FandangoL. Success. Thank you. Pad works great now. As happy as a clam...
UPDATE : is it me ? or with Hongkong v500 30b, it doesn't allow stock recovery mode. Screen just stayed on android lying down exclamation mark. Tried all button combo hold power then tap vol up etc etc .. but none worked.
Read in Google+ Lg G Pad 8.3 forum :
Hi guys, I need your help. I just flashed the Hong Kong version of 5.0.2 to my gpad using LG Flash Tool 2014 and everything went well. Now I found out that there is a 5.1 update in the net for gpad and I even manage to download it. But the problem is that the update file is in zip format which means that I cannot use the Flash tool and it seems that LG disable recovery mode to allow sideloading of update zip files. I really don't want to install custom recovery so if anyone of you have any idea of what I can do to flash this update, please help.
Finally got TWRP to work
Next step is to install cm-13.0
Followed this post to get TWRP working. Had some problems regarding location of *.img files. But if you read the thread I have explained what I had to do.
http://forum.xda-developers.com/lg-g-pad-83/help/v500-how-to-install-twrp-stock-lp-t3165846
xurena said:
.
Now I found out that there is a 5.1 update in the net for gpad and I even manage to download it. But the problem is that the update file is in zip format which means that I cannot use the Flash tool and it seems that LG disable recovery mode to allow sideloading of update zip files. I really don't want to install custom recovery so if anyone of you have any idea of what I can do to flash this update, please help.
Click to expand...
Click to collapse
Do you mean exist a stock update with 5.1 in zip format?
Sent from my LG-D855 using XDA Free mobile app

[RECOVERY][ROOT] N910T/T3 6.0.1 PE3 - How to Root (Systemless & System Mode) / TWRP

[RECOVERY][ROOT] N910T/T3 6.0.1 PE3 - How to Root (Systemless & System Mode) / TWRP
This is really simple but I'm guessing people are still wondering.
Download TWRP
Download SuperSU 2.76 Systemless (for Stock Kernels) or Download SuperSU 2.76 SystemMode (Permissive Kernel Required)
*Optional* Download a Permissive Kernel like BeastMode (only needed for System Mode SuperSu)
Download Odin
Put the SuperSU on your SD Card / Internal Storage
*Optional* Put Custom Kernel on SD Card (Optional, Only required if using SuperSu SystemMode)
Reboot into Download Mode
Flash TWRP in Odin
Boot into TWRP
Flash SuperSU
Enjoy!
For details on how to flash with Odin, flash with TWRP please see other threads or use Google.
Additional Downloads:
-N910T PE3 Stock Recovery
Additional Info:
NetFlix:
Some users have reported that NetFlix would not connect after rooting. There is no need to do this if you do not have any problems with NetFlix.
-Delete /system/vendor/lib/liboemcrypto.so and reboot.
------------------------------------------------------
Thanks of course to Chainfire & Teamwin
Also Thanks to freeza.
Cool. Thanks. it's same for all other mm roms too.
Is this Systemless root?
So if we already have a rooted device with TWRP installed, and assuming we already were able to flash 6.0.1 to the device, then the only step required is:
Download SuperSU
Flash SuperSU via TWRP
Is that right?
Sent from my SM-N910T3 using XDA-Developers mobile app
f4phantomii said:
So if we already have a rooted device with TWRP installed, and assuming we already were able to flash 6.0.1 to the device, then the only step required is:
Download SuperSU
Flash SuperSU via TWRP
Is that right?
Sent from my SM-N910T3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Your prior rooted device needs to be rerooted. Download SuperSu to phone. Download TWRP to computer. Odin TWRP. Once TWRP is flashed, boot to TWRP and install Supersu [at least that's what I did.]
But since I already have TWRP installed as recovery, do I need to re-install it via Odin?
Unless flashing 6.0.1 overwrites the recovery?
Otherwise just flashing SuperSU should re-root.
Sent from my SM-N910T3 using XDA-Developers mobile app
f4phantomii said:
But since I already have TWRP installed as recovery, do I need to re-install it via Odin?
Unless flashing 6.0.1 overwrites the recovery?
Otherwise just flashing SuperSU should re-root.
Click to expand...
Click to collapse
Odin flashing MM will overwrite your recovery.
Got it. Thanks fo clarifying that.
Sent from my SM-N910T3 using XDA-Developers mobile app
Question, have rooted and jail broke many but not this 910T yet. I am on non-root 5.1.1, should I take the OTA 6.0.1 and then follow the above instructions or download 6.0.1 from samsung and install via Odin and then start following these instructions? Would perfer to take over the air so I dont have to reset up everything.
Thanks in advance and I cant fn wait to start using Adfree again!
I downloaded via Kies. Didn't have to setup a thing after.
Sent from my SM-N910T using XDA-Developers mobile app
I'm impressed we got this being 1.90 generations old. I usually feel forgotten and abandoned by now. Thanks T-Mo. Now please don't F us on the Note 6/7 bootloader!
Bubba Fett said:
I'm impressed we got this being 1.90 generations old. I usually feel forgotten and abandoned by now. Thanks T-Mo. Now please don't F us on the Note 6/7 bootloader!
Click to expand...
Click to collapse
Agreed.
Anybody know if editing the platform.xml still works for SD card writing? And with the update I am getting the stupid -504 error in google play store trying to install Titanium backup......I might have to reflash ugh.
Edit*****
I fixed my issue
Bubba Fett said:
I'm impressed we got this being 1.90 generations old. I usually feel forgotten and abandoned by now. Thanks T-Mo. Now please don't F us on the Note 6/7 bootloader!
Click to expand...
Click to collapse
They will.
Man I hope not. We did a lot of *****in! Looks like HTC is gonna do the next nexus and should be on par with the N7 but I really don't want to do that. There is no way any phone can compare with the same phone rooted and custom. We will see.
Any ideas, stock non rooted 5.1 updated via OTA to 6.0.1, flashed latest TWRP 3.2.0 successfully (USB Deb enabled, R/L disabled) and still boots into stock recovery? What am I doing wrong?
SM-N910T
---------- Post added at 02:39 AM ---------- Previous post was at 01:41 AM ----------
Found a work around from another post:
'm trying to install TWRP, but it keeps getting overwritten. After installing, I can initially boot into TWRP, but after doing a system reboot, it goes back to stock recovery. What am I doing wrong?
Here's the steps I take:
Open Odin, check AP and load twrp image (3.0.0)
Connect phone and wait for Added!
Uncheck Auto Reboot
Click Start and wait to finish.
I then have to take out the battery to turn the phone off (I had to do it this way because leaving Auto Reboot checked would cause the same issue as below). I then boot directly into recovery and TWRP loads as expected. Everything looks fine, and I can do a recovery reboot back to TWRP. However, if I do a system reboot and let Android load, then shutdown and boot into recovery again, I'm back to stock.
Sprint SM-N910P
Android 5.1.1
http://androidforums.com/threads/twrp-keeps-getting-overwritten.1003988/
richard75013 said:
Any ideas, stock non rooted 5.1 updated via OTA to 6.0.1, flashed latest TWRP 3.2.0 successfully (USB Deb enabled, R/L disabled) and still boots into stock recovery? What am I doing wrong?
SM-N910T
---------- Post added at 02:39 AM ---------- Previous post was at 01:41 AM ----------
Found a work around from another post:
'm trying to install TWRP, but it keeps getting overwritten. After installing, I can initially boot into TWRP, but after doing a system reboot, it goes back to stock recovery. What am I doing wrong?
Here's the steps I take:
Open Odin, check AP and load twrp image (3.0.0)
Connect phone and wait for Added!
Uncheck Auto Reboot
Click Start and wait to finish.
I then have to take out the battery to turn the phone off (I had to do it this way because leaving Auto Reboot checked would cause the same issue as below). I then boot directly into recovery and TWRP loads as expected. Everything looks fine, and I can do a recovery reboot back to TWRP. However, if I do a system reboot and let Android load, then shutdown and boot into recovery again, I'm back to stock.
Sprint SM-N910P
Android 5.1.1
http://androidforums.com/threads/twrp-keeps-getting-overwritten.1003988/
Click to expand...
Click to collapse
I'm having the same issue however I can't get into TWRP period... I pushed MM and TWRP 3.0.2 from ODIN 3.07. During reboot it rw's the MM recovery
Has anyone flashed the new 6.0 MM BL and CP vs Flashfire?
The G.O.A.T. said:
I'm having the same issue however I can't get into TWRP period... I pushed MM and TWRP 3.0.2 from ODIN 3.07. During reboot it rw's the MM recovery
Click to expand...
Click to collapse
richard75013 said:
Any ideas, stock non rooted 5.1 updated via OTA to 6.0.1, flashed latest TWRP 3.2.0 successfully (USB Deb enabled, R/L disabled) and still boots into stock recovery? What am I doing wrong?
SM-N910T
---------- Post added at 02:39 AM ---------- Previous post was at 01:41 AM ----------
Found a work around from another post:
'm trying to install TWRP, but it keeps getting overwritten. After installing, I can initially boot into TWRP, but after doing a system reboot, it goes back to stock recovery. What am I doing wrong?
Here's the steps I take:
Open Odin, check AP and load twrp image (3.0.0)
Connect phone and wait for Added!
Uncheck Auto Reboot
Click Start and wait to finish.
I then have to take out the battery to turn the phone off (I had to do it this way because leaving Auto Reboot checked would cause the same issue as below). I then boot directly into recovery and TWRP loads as expected. Everything looks fine, and I can do a recovery reboot back to TWRP. However, if I do a system reboot and let Android load, then shutdown and boot into recovery again, I'm back to stock.
Sprint SM-N910P
Android 5.1.1
http://androidforums.com/threads/twrp-keeps-getting-overwritten.1003988/
Click to expand...
Click to collapse
Perhaps try wiping everything...
System, Data, Internal Storage.
Then flash the Odin MM tar.
Then start the process in the thread.
I personally did the process after a SmartSwitch update and it worked from just doing what I listed in the OP.
DeeXii said:
Perhaps try wiping everything...
System, Data, Internal Storage.
Then flash the Odin MM tar.
Then start the process in the thread.
I personally did the process after a SmartSwitch update and it worked from just doing what I listed in the OP.
Click to expand...
Click to collapse
Yeah idk... It just worked this time. IF I was to say what I did different I booted into recovery first it started with applying update or something then crashed because no update was there, then showed stock MM recovery I then. Shutdown and went into download mode and did the OP.
It work!!!
Doing a new backup now

LG G3 [D855] Custom Recovery And Rom Flashing

I have went through many tutorials but none of them were able to help me with flashing custom recovery(TWRP). My LG G3 D855 was rooted with towelroot(I think long time ago). I do not know how can I unlock my bootloader or I don't know if it is already unlocked(Picked it off craiglist long time ago). Phone is stuck in fastboot mode. I have tried to fix but I could not. There is no 'download mode'.
Could you please explain each and every step in detail? I really want to reboot my device with a custom ROM.
Phone is running Androind 4.4.2.
So guys? Any help? Just tell me how can I remove that fastboot mode that appears when I restart my device for recovery.
AtaliaKetch said:
So guys? Any help? Just tell me how can I remove that fastboot mode that appears when I restart my device for recovery.
Click to expand...
Click to collapse
Have you flashed TWRP already?
I have a an D855, I don't think you have to worry about a locked bootloader Mate,
but it was a long time since I got rid of the LG crap, because it was the first thing I did after buying new!
You're on 4.4.2 with towel root so it should very simple to download and flash TWRP using the official TWRP app in Playstore or using an app like Flashify etc.
I basically lost my S7 Edge a week ago so I'm back using my old LG G3 now running Resurrection Remix 5.8(Nougat 7.1.2. AOSP based)
If you wanna run anything using Aroma installer then don't go later than TWRP 3.0.0. for now, because the newer versions don't work.
Either download the Quickboot app to boot to recovery or search on Youtube on how to boot to recovery from off..
andi54 said:
Have you flashed TWRP already?
I have a an D855, I don't think you have to worry about a locked bootloader Mate,
but it was a long time since I got rid of the LG crap, because it was the first thing I did after buying new!
You're on 4.4.2 with towel root so it should very simple to download and flash TWRP using the official TWRP app in Playstore or using an app like Flashify etc.
I basically lost my S7 Edge a week ago so I'm back using my old LG G3 now running Resurrection Remix 5.8(Nougat 7.1.2. AOSP based)
If you wanna run anything using Aroma installer then don't go later than TWRP 3.0.0. for now, because the newer versions don't work.
Either download the Quickboot app to boot to recovery or search on Youtube on how to boot to recovery from off..
Click to expand...
Click to collapse
The problem is, there is no recovery. Even though flashing TWRP via flashify resulted in nothing but an error showing "Fastboot mode started" when I tapped on option named "Reboot to recovery". This is the main problem I am facing. I can flash, upgrade/downgrade and etc but this fastboot mode thing is something beyond what I can fix with my current knowledge.
AtaliaKetch said:
The problem is, there is no recovery. Even though flashing TWRP via flashify resulted in nothing but an error showing "Fastboot mode started" when I tapped on option named "Reboot to recovery". This is the main problem I am facing. I can flash, upgrade/downgrade and etc but this fastboot mode thing is something beyond what I can fix with my current knowledge.
Click to expand...
Click to collapse
Maybe first flash back stock, update to the latest firmware and start fresh from there?
There are some good guides in the forums here for that.
Cheers
Sent from my Google Pixel using XDA Labs
If you've to go back to firmware, don't install the newest. Rooting needs an older version. Also described in root-threads here.

Categories

Resources