hi folks,
i recently installed KitSlim and had a DualRecovery everything was working fine,
but today i installed BusyBox and now my DualRecovery seems gone.
I'm not able to get into the Recovery at boot anymore.
did i miss something important?
is there a way to get the DualRecovery back without flashing back to stock and redo all the stuff?
schnitzelpete said:
hi folks,
i recently installed KitSlim and had a DualRecovery everything was working fine,
but today i installed BusyBox and now my DualRecovery seems gone.
I'm not able to get into the Recovery at boot anymore.
did i miss something important?
is there a way to get the DualRecovery back without flashing back to stock and redo all the stuff?
Click to expand...
Click to collapse
If you try and flash recovery on top of KitSlim it will go into a bootloop. Have you checked that you still have root? possibly re-installing root might make a difference, but I doubt it.
I suspect that you will have to start again with a stock rom, but at least there is easyroot to help now.
You installed an unsupported busybox version. See known issues: http://forum.xda-developers.com/showpost.php?p=43698321&postcount=2
Related
Hello, I'm having trouble trying to install a custom rom into this device. The thing is that I had the stock 4.4.2 rom, then I managed to root it, and then I also installed TWPR so I could install the custom rom afterwards, well it turns out that I ran into trouble when I realized that after flashing the custom rom I couldn't get it to boot, and then I thought that it might be related to the bootloader. Isn't this tablet's bootloader locked? I know the bootloader gets updated when I update the stock rom, and I suppose it was and I'm on kk bootloader since I'm on 4.4.2 stock. Well it could be that the bootloader is locked and needs to be unlocked? I remember this was true for an HTC I used to have and for my current LG. But I don't know what to do, I mananaged to revert it back to stock after flashing the custom rom since I couldn't get it to work, I'm using odin for everything and following the instructions to the letter, being very careful and all, always wiping data partition and cache before. When following instructions didn't help I decided to try a few things on my own. I first flashed the root, then TWPR then the custom rom, then I tried TWPR, custom rom and then root, then root and custom rom. I've tried like all possible combinations to no avail it gets stuck on Samsung Galaxy Note 10.1 2014 edition logo and the custom rom doesn't boot. I'm so desperate since this is the first android device I haven't been able to install a custom rom on. Now I'm back to stock and lost everything, have to start from scratch now since I didn't back up, I had nothing important on my tablet, but still... I really need someone to help me out. My tablet is working fine now but with stock, no luck with custom rom (Hyperdrive) I don't wanna try other rom because I'm still thinking it has to do with the bootloader, but I don't know if it's locked or what.
sure, boot was ended ? If I remenber well, you need to be patient for first boot of hyperdrive rom, about ten minutes.
if you have have trouble with flashing, may I suggest you to update your tab step by step.
1) reinstall stock rom (seems you have already done that)
2) flash twrp 2.6.X (reboot, and keep time to manage a backup, use your tab, ...)
3) flash a custom rom with twrp (you will be able to restore some data from your backup if needed)
a good way is also to use your stock rooted rom with xposed modules. So you will be able to customize your tab like a custom rom do.
Xcoders said:
Hello, I'm having trouble trying to install a custom rom into this device. The thing is that I had the stock 4.4.2 rom, then I managed to root it, and then I also installed TWPR so I could install the custom rom afterwards, well it turns out that I ran into trouble when I realized that after flashing the custom rom I couldn't get it to boot, and then I thought that it might be related to the bootloader. Isn't this tablet's bootloader locked? I know the bootloader gets updated when I update the stock rom, and I suppose it was and I'm on kk bootloader since I'm on 4.4.2 stock. Well it could be that the bootloader is locked and needs to be unlocked? I remember this was true for an HTC I used to have and for my current LG. But I don't know what to do, I mananaged to revert it back to stock after flashing the custom rom since I couldn't get it to work, I'm using odin for everything and following the instructions to the letter, being very careful and all, always wiping data partition and cache before. When following instructions didn't help I decided to try a few things on my own. I first flashed the root, then TWPR then the custom rom, then I tried TWPR, custom rom and then root, then root and custom rom. I've tried like all possible combinations to no avail it gets stuck on Samsung Galaxy Note 10.1 2014 edition logo and the custom rom doesn't boot. I'm so desperate since this is the first android device I haven't been able to install a custom rom on. Now I'm back to stock and lost everything, have to start from scratch now since I didn't back up, I had nothing important on my tablet, but still... I really need someone to help me out. My tablet is working fine now but with stock, no luck with custom rom (Hyperdrive) I don't wanna try other rom because I'm still thinking it has to do with the bootloader, but I don't know if it's locked or what.
Click to expand...
Click to collapse
Are you on P605 or P600? The Hyperdrive rom is not for all variants.
11737
lightman33 said:
sure, boot was ended ? If I remenber well, you need to be patient for first boot of hyperdrive rom, about ten minutes.
if you have have trouble with flashing, may I suggest you to update your tab step by step.
1) reinstall stock rom (seems you have already done that)
2) flash twrp 2.6.X (reboot, and keep time to manage a backup, use your tab, ...)
3) flash a custom rom with twrp (you will be able to restore some data from your backup if needed)
a good way is also to use your stock rooted rom with xposed modules. So you will be able to customize your tab like a custom rom do.
Click to expand...
Click to collapse
Thank you, I've done all those steps, I've reinstalled the stock rom several times and, then I've flashed twpr 2.6.X and I've also tried with 2.7.X just in case, and I've had to root before or after installing the stock rom because if I don't I can't boot from stock either Ohh yes, I was very patiend the fist time it booted, I waited 15 minutes
shayind4 said:
Are you on P605 or P600? The Hyperdrive rom is not for all variants.
Click to expand...
Click to collapse
I'm on P600 and the Hyperdrive version I picked was made for P600 too, I'm sure of that
Hi guys,
I am getting DESPERATE here. Because of a mistake, I had to reflash stock LG ROM 50020d 4.4.2. From there, I rooted using geohot's towelroot and used Flashify to flash this TWRP 2.8.0.0 After 128754E10th attempt, it worked. I experienced all kinds of recovery loops when I used files for 4.2.2 base (because someone mentioned it's needed to prevent brightness issue) but it caused my recovery to go into some strange loop. So I reflashed the recovery.
Now I can enter TWRP 2.8.0.0 but I cannot, cannot, cannot flash yesterday's CM11 nightly for my device. When I try, log says:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error executing updater binary in zip '/sdcard/cm-11-20141101-NIGHTLY-v500.zip'
Error flashing zip /sdcard/cm-11-20141101-NIGHTLY-v500.zip
Updating partition details
I am truly desperate. I even fixed the name of my device in build.prop to v500 (before it was 'awifi' for some reason) but still no dice.
Please, is there someone to give me some clear instructions? Thanks a lot guys.
TF666 said:
Hi guys,
I am getting DESPERATE here. Because of a mistake, I had to reflash stock LG ROM 50020d 4.4.2. From there, I rooted using geohot's towelroot and used Flashify to flash this TWRP 2.8.0.0 After 128754E10th attempt, it worked. I experienced all kinds of recovery loops when I used files for 4.2.2 base (because someone mentioned it's needed to prevent brightness issue) but it caused my recovery to go into some strange loop. So I reflashed the recovery.
Now I can enter TWRP 2.8.0.0 but I cannot, cannot, cannot flash yesterday's CM11 nightly for my device. When I try, log says:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error executing updater binary in zip '/sdcard/cm-11-20141101-NIGHTLY-v500.zip'
Error flashing zip /sdcard/cm-11-20141101-NIGHTLY-v500.zip
Updating partition details
I am truly desperate. I even fixed the name of my device in build.prop to v500 (before it was 'awifi' for some reason) but still no dice.
Please, is there someone to give me some clear instructions? Thanks a lot guys.
Click to expand...
Click to collapse
Have you tried with another build of CM11? Perhaps the latest milestone? Have you wipe:d all the data and cache and stuff? Can you tell me how you got the TWRP on there? Did it work the first time you flashed the 4.4.2 version? Where you on the latest version of android before rooting?
Thanks for your effor, djmiek.
I managed to fix it yesterday. Nothing was out of ordinary - TWRP 2.8.0.0 (specifically for v500) was flashed using Flashify. Phone was rooted (see my original post) and I wiped everything properly before flashing CM11. However, for some reason there was no way to install nightly from 11/1. Everytime I tried to install, I got aforementioned error message.
So I got fed up with all that and just went and restored my whole tablet to a backup from april (50010b) which I very wisely did just after rooting the brand new device. This reverted TWRP to 2.6.3.2 and as soon as I booted recovery I could install that nightly without any hassle. No incompatible data, no bull like that - everything went smoothly. I don't know if there's a problem with TWRP 2.8.0.0 and current CM11 nightly combo but I sure as hell will stay away from it.
So, the moral of the story - BACKUP any working installation folks! Do not underestimate the power of word "restore". It feels goooood
TF666 said:
Thanks for your effor, djmiek.
I managed to fix it yesterday. Nothing was out of ordinary - TWRP 2.8.0.0 (specifically for v500) was flashed using Flashify. Phone was rooted (see my original post) and I wiped everything properly before flashing CM11. However, for some reason there was no way to install nightly from 11/1. Everytime I tried to install, I got aforementioned error message.
So I got fed up with all that and just went and restored my whole tablet to a backup from april (50010b) which I very wisely did just after rooting the brand new device. This reverted TWRP to 2.6.3.2 and as soon as I booted recovery I could install that nightly without any hassle. No incompatible data, no bull like that - everything went smoothly. I don't know if there's a problem with TWRP 2.8.0.0 and current CM11 nightly combo but I sure as hell will stay away from it.
So, the moral of the story - BACKUP any working installation folks! Do not underestimate the power of word "restore". It feels goooood
Click to expand...
Click to collapse
Is 50010b also 4.4.2 or is it earlier? Did you just flash TWRP with flashify then after rooting?
I think it was 4.4.2.
My initial root after purchase was done according to http://www.youtube.com/watch?v=05T3mYVnYYE
Everything went smoothly then, but I think you'd achieve the same outcome using Flashify.
So i was trying to flash hacker kernel
It bootlooped.
So i reflashed renegade and tried reflashing.
it rebooted
now everytime i try and flash anything it reboots
super su is missing.
I installed super su from play store
when i go to flash binaries it reboots.
I updated TWRP
still same thing.
If i flash anything it just boots back to recovery.
Any thoughts?
Flashed back to stock and rerooted.
Did the trick.
Would you consider editing the topic to add the word "solved" please? The might help give others direction.
So when you started out from stock, you used Odin to install TWRP, but then thought you could get rooted by installing SuperSu from the Play store, which did not work.
Proper steps are to install TWRP using Odin with SuperSU on your phone. After TWRP is installed, instead or rebooting completely, reboot to Recovery and flash SuperSU that way.
Is that about right, @phelony?
koop1955 said:
Would you consider editing the topic to add the word "solved" please? The might help give others direction.
So when you started out from stock, you used Odin to install TWRP, but then thought you could get rooted by installing SuperSu from the Play store, which did not work.
Proper steps are to install TWRP using Odin with SuperSU on your phone. After TWRP is installed, instead or rebooting completely, reboot to Recovery and flash SuperSU that way.
Is that about right, @phelony?
Click to expand...
Click to collapse
No I had previously been rooted fine and dandy. for some reason TWRP started just rebooting on any flash.
so is it not going into bootloop mode anymore? because i've been having this problem for the last 6 months. i thought i'd try again and still doing the same, it'll get to the setup at the beginning and then reboot back to twrp????
I have been trying to root my J6 SM-J600FN for a while, and I thought I was getting close to rooting it when I installed TWRP. But then, my phone was stuck in a boot-loop. I was able to fix it by installing current firmware, and I decided to attempt it a second time. I got the same result. Is there anything I can use to install TWRP that doesn't result in a boot-loop? I just want my phone rooted and be done with it.
As far as i know, trying to root stock rom isn't easy. I could be wrong but idk. You can try by:
1. Flashing stock
2. Flashing TWRP
3. Format data
4. Flash DM-Verity and Disable Force-Encrypt then flash magisk.
And i think you can't flash kernels on stock. I could be wrong but idk.
Hey, how did you even install TWRP?
Before I tried installing it my model number was "SM-J600 FN/DS" and now after the install, when I plug it into my pc it says that it's "FN-600G." Whenever I try to boot it in system mode it's stuck in a loop.
I haven't tried flashing the newest firmware yet because I can't even download it for my country.
Sorry, I am a total newbie and can't seem to fix it.
Al-Ameen Adewunmi said:
I have been trying to root my J6 SM-J600FN for a while, and I thought I was getting close to rooting it when I installed TWRP. But then, my phone was stuck in a boot-loop. I was able to fix it by installing current firmware, and I decided to attempt it a second time. I got the same result. Is there anything I can use to install TWRP that doesn't result in a boot-loop? I just want my phone rooted and be done with it.
Click to expand...
Click to collapse
Hi Guys,
Did you manage to do this? I was experiencing the same bootloop issue and I think it is the version of Twrp (I was using 3.3.1-0).
I used Odin to flash a lower version 3.2.3 found here after which I flashed this DM Verity + Magisk.
Root Success!
Hi there,
I tried to install TWRP as described in this thread https://forum.xda-developers.com/mi-a2-lite/development/official-twrp-daisy-t3855396
However now that its finished it wont boot anymore in my normal system, instead always trwp shows up :/
Before I had installed stock rom and was rooted
I installed TWRP with version twrp-installer-daisy-3.2.3-0
Any advice how I fix that (without loosing data) ?
Im very thankful for any hint.
wsjoke said:
Hi there,
I tried to install TWRP as described in this thread https://forum.xda-developers.com/mi-a2-lite/development/official-twrp-daisy-t3855396
However now that its finished it wont boot anymore in my normal system, instead always trwp shows up :/
Before I had installed stock rom and was rooted
I installed TWRP with version twrp-installer-daisy-3.2.3-0
Any advice how I fix that (without loosing data) ?
Im very thankful for any hint.
Click to expand...
Click to collapse
you can try flash vanilla boot.img again it worked for me, but u will lost magisk and/or twrp previously installed
then reinstall them
Antho02 said:
you can try flash vanilla boot.img again it worked for me, but u will lost magisk and/or twrp previously installed
then reinstall them
Click to expand...
Click to collapse
Thank you so much :fingers-crossed:
The vanilla boot.img havent worked (it did however boot not to twrp anymore) but I was able to pull magisk latest boot.img backup and after flashing that it worked :good: