Hi guys I just wannted to share my expierence with my Galaxy Tab 3. From 4.1.2 to 4.4.2 I encoutered many problems and created solutions to fix them. And here are some.
The first thing that I had a problem with was when I unrooted and left busybox installed. When I did a factory data reset, the device became so laggy and almost unusable. I I could not root my device for some reason. To fix this, just simply reflash the stock room using odin. After I fixed this, I upgraded to Kit-kat and looked for a custom recovery to install. I went for clockwormod and found my self getting stuck in a cwm bootloop. To fix this, download the latest version of TWRP and install via odin. I strongly recomend to use TWRP as it does not go into a recovery bootloop unlike CWM. Now for Xposed I noticed that the boot up is way slower then before. A simple install of the module boot manager can help.
That's it. I hope I can help some new users with problems on the galaxt tab 3. If you have any other problems, just let me know and I'll do my best to help.
Sent from my SM-T210 using XDA Free mobile app
I flashed TWRP and got a recovery boot loop.
hen I flashed Clockwork, which didn't loop.
So, use most recent one which resets the switch for booting into recovery! Doesn't matter for this problem which one, as long as it is the lastest loader.
Related
Hi folks, I seek the advice of any one who could help me with issue. To give you a bit of background information, I have a D802 version which is rooted with CloudyStock 1.1, android 4.4.2 KK.
Yesterday I tried to update the version of Philz recovery that I had which has never been a problem before. I downloaded the latest version from the dedicated page here and went into the recovery to install the zip.
Whilst the zip was extracted without issue there was an error regarding "lokifying" the boot loader. I turned the phone off and tried to get in the recovery again but this time I had the error "secure booting: boot certification verify".
I never had any problem before, I don't know why the latest version of the recovery would create more problem that the old one.
The thing is that the phone works fine, it boots and runs without issue, I just can't get into recovery mode. Also the download mode works.
I'm sure they must be a way to get the recovery back. I tried to flash CMW with Rom Manager without success.
If anyone knows, I would appreciate the help greatly.
Cheers
considering kitkat has no root yet, getting a recovery on it is going to be difficult.
you will need a via zip flashable distro of kitkat. Which if you search you can make yourself. It was on xda portal some time ago.
That way I think root\recovery is maintained.
send from the jungle
bachera said:
considering kitkat has no root yet, getting a recovery on it is going to be difficult.
you will need a via zip flashable distro of kitkat. Which if you search you can make yourself. It was on xda portal some time ago.
That way I think root\recovery is maintained.
send from the jungle
Click to expand...
Click to collapse
Thank you for your answer Bachera. I am not sure I understand what you mean by "via zip flashable distro of kitkat."
Plus my kitkat version of android is rooted, why would you think kitkat has no root yet?
Light_Addict said:
Hi folks, I seek the advice of any one who could help me with issue. To give you a bit of background information, I have a D802 version which is rooted with CloudyStock 1.1, android 4.4.2 KK.
Yesterday I tried to update the version of Philz recovery that I had which has never been a problem before. I downloaded the latest version from the dedicated page here and went into the recovery to install the zip.
Whilst the zip was extracted without issue there was an error regarding "lokifying" the boot loader. I turned the phone off and tried to get in the recovery again but this time I had the error "secure booting: boot certification verify".
I never had any problem before, I don't know why the latest version of the recovery would create more problem that the old one.
The thing is that the phone works fine, it boots and runs without issue, I just can't get into recovery mode. Also the download mode works.
I'm sure they must be a way to get the recovery back. I tried to flash CMW with Rom Manager without success.
If anyone knows, I would appreciate the help greatly.
Cheers
Click to expand...
Click to collapse
I encountered something similar on my phone. However, i was on 4.2.2 but this worked for me. Give it a shot, it might work for you too
http://forum.xda-developers.com/showthread.php?t=2500441
Good luck
Try Flashify from the Play store to flash a working recovery for your phone. I had the same issue with philz latest version. I had to use an older version of philz to get it to work on my phone.
Sent from my LG-D803 using xda app-developers app
Yeah I misread, I thought you went to a official kitkat. Only way to get root on kitkat is if lucky its maintained with a ota update. or a special made kitkat, thats what I mean with special distribution (distro) one via recovery flashable.
kitkat rooting directly at the moment of writing is not possible due to lg bootloader.
send from the jungle
Thank you all for the help and suggestions. I tried flashify and I did not work.
However freegee worked very well and managed to go back to CMW.
All functional now!
Thanks
Sadly, I installed the Kitkat ota, through a misclick. I am on the Verizon LgG2. So the problem isn't that I'm stuck on the logo after the ota, it is that after successfully rooting, flashing twrp recovery and creating a backup with which I can get out of this loop easily, I cannot get a rom to work. Every time, and of four roms I have tried I am stuck in a bootloop. I am not new to doing this sort of thing and have done it perfectly without troubles before the ota, but now I can get no roms to boot correctly, and I am thus stuck on the logo. I have tried AutoRec, but to no avail, maybe because I had applied twrp before using AutoRec. Nevertheless, is anyone else having this issue or has anyone corrected the problem when they had it? I'd love to get a rom going!!
Hi all,
I am hoping someone can help! I have the s4 gt i9505: jftlte with twrp recovery, AOKP rom and the premium version of chain fires superSU. I've come to update my ROM tonight with the latest version of AOKP as I have not done this for a while firstly my phone won't boot into recovery. I get the traditional 3 lines at the tip of the screen then the phone just hangs and will not open up in recovery. Secondly I have no icon for superSu.
Is there anything I can do to get my phone to boot on recovery or should I flash a new recovery mod?
I have checked the twrp app it states I have version 2.7 installed trued to update this but it doesn't seem to have the download file available for the latest twrp.
Any help is much welcome.
Regards
Just be patient. Reboot into the ROM, then try rebooting into recovery. Every once in a great while I get this issue, and rebooting resolves the problem.
Hi, first of all, I'm new to all this so I'm not sure what I'm doing and I don't know much about technical terms.
All I wanted to do was to install CM12.1 ROM on my Note 3 Exynos. I was on stock Lollipop 5.0., rooted.
To start I had installed TWRP Recovery Manager from Google Play Store according to the instruction on the first page of the CM12.1 ROM thread. Then opening the app it asks me to install BusyBox (which I hit OK but nothing seems to be happening). Then on the very first screen I selected my phone model, then below I hit Install Recovery, which it did and report it was successful. Then it asks if I wanted to boot into recovery and I hit yes, and since then I have been stuck in a bootloop.
So I'm sure that I messed something up, but I'm not sure how to get out. I have searched through the forums and see multiple ways but I'm afraid to do anything in fear that I might damage the device any further. I am aware that one of the best solution is to flash the device back to stock ROM, however I have some data on this device that I want to keep, if that is possible.
Thank you very much for you help.
You recovery corrupted. Flash twrp with odin. If it doesn't work flash official firmware. You should not lost you data. Never use rom manger after this. It caused many cases of bootloop.
Sent from my GT-N7000
Rosli59564 said:
You recovery corrupted. Flash twrp with odin. If it doesn't work flash official firmware. You should not lost you data. Never use rom manger after this. It caused many cases of bootloop.
Sent from my GT-N7000
Click to expand...
Click to collapse
thank you very much. Flashing TWRP with Odin didn't work but as you said, flashing back to stock ROM still keeps my data. So thank you.
Try Philz Recovery .
problem solved. thanks guys. admin please delete thread.
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.