Error after rooting - Galaxy Tab 3 Q&A, Help & Troubleshooting

Hi,
Sorry for creating a new thread. I asked the question in other ones but got no answer.
I tried to root my p5200 on 4.4.2 (details in screen shot)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I followed the thread over here : http://forum.xda-developers.com/showthread.php?t=2531784
But no matter which recovery i use, i get a error regarding binaries not installed. (Reflashing didnt work)
So this is what i did.
I installed the twrp recovery with "auto reboot" unchecked. After the procees i pressed volume up and power button together while still in download mode.
Got in to recovery, for some reason it was extremely laggy, but i manged to install the root file stored in the internal sd card.
Successfully flashed, but when i goto the superuser app i get this message
" Error: The su binary is necessary to update! Click to install
Error during in the installation...Please send the error report to the developers!"
I reflashed, wiped dalvik and cache but nothing worked.
I odin installed philz recovery and flashed another root file but still the same
"There is no su binary installed and superuser cannot install them. This is a problem"
Lastly, i odin flashed cf auto root. Flashing was successful, but the tab gets stuck in the boot logo.
Where am i going wrong?
Thanks

Umn.... What do you mean by root files? Superuser flashable zip? If flashing superuser zip didn't work, then try flashing SuperSU

utsha.saha.58 said:
Umn.... What do you mean by root files? Superuser flashable zip? If flashing superuser zip didn't work, then try flashing SuperSU
Click to expand...
Click to collapse
Yeah, it was superuser flashable zip files. I tried both but didnt work.

Related

Can't root or install TWRP/CWM

So, I'm trying to root my T-Mobile T999 S3 using this guide:
http://forum.xda-developers.com/showthread.php?t=2563955&highlight=failed
I'm on the "Flash (install) the Knox Remover zip" in the recovery menu step, and I keep getting the "supersu failed to verify whole-file signature" error. I also get that error when I try to install SuperSU.
I figured that I needed to use CWM or TWRP but I can't get them to install. Odin says PASS but when I press Home + Volume Up + Power, I still get to the old, stock recovery menu.
What do I do?
EDIT: I downloaded the root66_TMO_T999UVUENC2.7z ROM from this page: http://forum.xda-developers.com/showthread.php?t=1771687 and it has rooted my phone.
Should I keep it, is it the same?
Thanks.
Keep what? Your phone is rooted, isn't that what you wanted? If you want to use the Knox remover zip download and install flashify from the playstore and you can install twrp from there, after that boot into recovery and flash the zip
Sent from my SGH-M919 using Tapatalk
serio22 said:
Keep what? Your phone is rooted, isn't that what you wanted? If you want to use the Knox remover zip download and install flashify from the playstore and you can install twrp from there, after that boot into recovery and flash the zip
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
But that thread is from 2012. How is it that I downloaded a 2 year-old ROM and it kept my 4.3 and simply rooted it?
It feels like I just did a random thing and got the exact result I waned..
That's because the thread was updated recently to add the newer firmwares.
Notice the following.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
13th July 2012, 10:34 PM
(Last edited by mrRobinson; 4th April 2014 at 04:07 PM.)

Installing TWRP Problem

I have uncloked bootloader and I Flashed TWRP Recovery via ADB and when I send comand "adb reboot recovery" I have the Android guy (SS) I drop SS with Adb comand prompt too
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Domolâ„¢ said:
I have uncloked bootloader and I Flashed TWRP Recovery via ADB and when I send comand "adb reboot recovery" I have the Android guy[/IMG]
Click to expand...
Click to collapse
Hey I had this exact same problem just a few moments ago. I didn't necessarily fix it but I found a different way of installing TWRP:
Basically what I did was temporarily boot into the recovery image I had (instead of properly flashing it) and then flashed a zip version of the recovery which works permanently.
To do that, go into the bootloader as normal (adb reboot bootloader) and then use [fastboot boot {filename}.img] (so replace filename with whatever file you have) to boot into the recovery temporarily, then flash the recovery zip.
Here's the link to the zip I used: https://www.androidfilehost.com/?fid=24407100847292484
UPDATE: OK turns out after a few reboots the recovery went back to not working, but I did try another method which definitely works. Temporarily boot into the recovery image as above, but this type install a Supersu zip. This will root the phone. Then boot into the phone as normal, install Flashify from the Play Store and use that to install the recovery image (which you should move onto the phone).
Here are some links:
Supersu zip I used: http://download.chainfire.eu/supersu-stable
Flashify: https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en_GB

[Q] Stuck on Boot Animation after flashing SuperSU on ResurrectionRemix ROM

ROM: ResurrectionRemix-M-v5.7.1-20160715-t0lte
SuperSU: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip?retrieve_file=1
Recovery: ClockWorkMod
So, I probably did something dumb and I'm stuck on the boot animation which loops forever. I can get into Recovery and Bootloader. I previously had a working install of the ROM listed above but I thought I needed to regain root (apparently it is already rooted but that was turned off or something) so I downloaded the SuperSU file to the device and rebooted into Recovery. I installed the SuperSU and rebooted but now I have the problem. Please advice. This is my first time ever using a custom ROM and I had it working fine before I did this to myself...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I suggest flashing TWRP as CWM has not been updated for a long time. Once TWRP is on the phone, perform a full system wipe and re-install a custom ROM.
audit13 said:
I suggest flashing TWRP as CWM has not been updated for a long time. Once TWRP is on the phone, perform a full system wipe and re-install a custom ROM.
Click to expand...
Click to collapse
Thank you for your reply!
I was unaware that CWM was so out of date; it did work well before I tried to root an already rooted ROM. But I will try TWRP in any case. Still, I was hoping to solve this issue without wiping/reinstalling everything as I have data I want to preserve. If there is no way out of this mess except that, I will use ADB to get what data I can, then reinstall.

Question FAILED (remote: '(recovery_a) No such partition')

Hello, I've always installed custom rom, and recovey in well f3, overnight, I'm having problems, whenever there's an updated miui I install it through my flash to test, when installing a recovery, it started to give this error in the partition, being A or B, when changing partitions and being able to install a recovey, the ROM simply disappears, as if it had nothing, anyone already had the problem?, I remember that when installing a recovery or ROM it never gave this partition error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've had a similar problem. Try installing any rom through sideloading it. Boot to system then flash recovery again and your good to go.
Hi,
I'm using mi 11t Pro
Getting same error
unable to reboot in system or recovery
always booting on fastboot
showing current slot-A
I flashed twrp as steps stated in your picture
but I'm unable to boot into recovery
please help....
IgorCunhaBr said:
Hello, I've always installed custom rom, and recovey in well f3, overnight, I'm having problems, whenever there's an updated miui I install it through my flash to test, when installing a recovery, it started to give this error in the partition, being A or B, when changing partitions and being able to install a recovey, the ROM simply disappears, as if it had nothing, anyone already had the problem?, I remember that when installing a recovery or ROM it never gave this partition error.
View attachment 5502819
Click to expand...
Click to collapse
Hey...!
I'm using mi 11t pro...
got stuck on fastboot mode.
While flashing recovery i got same error of "no such partition" like yours.
Now I flashed twrp as per your above picture.
But I'm unable to boot into my twrp.
Please help

Question SOLVED Faulty root access on Xiaomi Eu rom

I cleanly installed Xiaomi Eu rom, then got root access by flashing Magisk 24.3. The installation went smoothly. According to the Root Checker app, I have root access on my device. But when I try to modify a file in the system folder with the Root Explorer app, it won't let me do it and gives me an error message.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know if I've missed something or I'm uninformed, but is it not possible anymore (or never was) to modify system files in Miui based roms?
Hmm... Try using FX File Manager
I highly recommend this File Manager!
Did you flash magisk directly using twrp? If so, that might be the problem.
See this post:
Gapps error 70, resize System Partition.
Hello. After I received my new Poco f3, the first I've done was unlocking the bootloader. 7 days later, everything was done and I flashed lineageos. >Fastboot boot twrp.img>advanced>flash current twrp. After that I've wiped and format data...
forum.xda-developers.com
user0u said:
Did you flash magisk directly using twrp? If so, that might be the problem.
See this post:
Gapps error 70, resize System Partition.
Hello. After I received my new Poco f3, the first I've done was unlocking the bootloader. 7 days later, everything was done and I flashed lineageos. >Fastboot boot twrp.img>advanced>flash current twrp. After that I've wiped and format data...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes I have flashed it using twrp and also from fastboot mode.
Never mind, I fixed it flashing (using TWRP) the MAKERW-STABLE-4.1.11.zip file from this thread https://forum.xda-developers.com/t/...-script-to-install-all-roms-via-twrp.4405061/

Categories

Resources