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
I'm on the latest TWRP (2.8.7.0) and after flashing a custom rom, no matter what it is (Bliss, DN4, CyanideL), it always boots up to recovery (TWRP or stock. Haven't tried CWM). The only way I found to fix it on Bliss is to use CF-Auto Root via Odin and it boots up normally for some reason. But if I try to update that ROM, it has the issue again. DN4 doesn't boot at all no matter what I try.
Any idea how to fix this? I'm on I317M
jokkir said:
I'm on the latest TWRP (2.8.7.0) and after flashing a custom rom, no matter what it is (Bliss, DN4, CyanideL), it always boots up to recovery (TWRP or stock. Haven't tried CWM). The only way I found to fix it on Bliss is to use CF-Auto Root via Odin and it boots up normally for some reason. But if I try to update that ROM, it has the issue again. DN4 doesn't boot at all no matter what I try.
Any idea how to fix this? I'm on I317M
Click to expand...
Click to collapse
Didn't see you try to downgrade the recovery to the last one? Might help fix your problem...
Or you can try using Odin back to stock. And start over with everything fresh.
Now Dn4 not booting, only means you need to flash Agni kernel afterwards. Get it here>Agni kernel downloads.
Good luck.
I had the same problem. TWRP 2.8.5 is the last version that doesn't have this problem on the i317m.
Just wanted to say thanks to @phzi . Same problem, downgraded to TWRP 2.8.5 fixed issue.
Hello, a friend of mine installed a custom rom at my lg g3 android phone. The rom is ressurrection remix. I accidently dirty flashed an older version of the same rom, I had 5.1.1 r6 and I flashed 5.0.3, and now neither adb works nor download mode due to killswitch. The only thing it does is show the old rr boot image. It's on a bootloop and since it doesn't open I don't know how to fix it. Can someone tell me what should I do?
Can you use the button combo to boot into TWRP? If you can get into TWRP then just flash the ROM you want and be sure to follow the rom threads instructions before flashing of course.
Hi.
I had an issue with my phone and I flashed a stock LG KDZ to go back to stock before sending my phone to LG.
Now, after having re-rooted my phone, via the 1-Click Root tool for LL, I can only install stock based ROMs such as Fulmics 5.1, but if I try to install an AOSP ROM such as Exodus/Candy6/RR/etc, I get a soft boot loop after rebooting from TWRP..
Using latest 3.0.2-0 TWRP recovery.
Anyone got any ideas?
Note, I was running AOSP based ROMs for the last year without issue..
I am having this same issue. For CM13 and Dirty Unicorns. Can someone help?
Hello all,
Having a weird issue. I flashed a stock-based Nougat ROM today and everything went fine, flashed new bootloader/radio first and new vendor img after ROM. Set up the ROM without issues, everything running smooth. I just went to flash a custom kernel and found out that I can't seem to get into TWRP. When I reboot to bootloader and then select "Recovery mode" it brings up the TWRP splash screen but the recovery never loads, it just hangs there for several minutes. I've tried rebooting several times.
Anyone else having this issue? Afraid I might need to reflash the recovery but I'd like to avoid that if possible.
Thanks.
The_mamba said:
Hello all,
Having a weird issue. I flashed a stock-based Nougat ROM today and everything went fine, flashed new bootloader/radio first and new vendor img after ROM. Set up the ROM without issues, everything running smooth. I just went to flash a custom kernel and found out that I can't seem to get into TWRP. When I reboot to bootloader and then select "Recovery mode" it brings up the TWRP splash screen but the recovery never loads, it just hangs there for several minutes. I've tried rebooting several times.
Anyone else having this issue? Afraid I might need to reflash the recovery but I'd like to avoid that if possible.
Thanks.
Click to expand...
Click to collapse
You need to reflash recovery because you are on 3.0.2.0 and you need at least 2.1 or 2.2. Just fastboot that img and it'll boot
Stevica Smederevac said:
You need to reflash recovery because you are on 3.0.2.0 and you need at least 2.1 or 2.2. Just fastboot that img and it'll boot
Click to expand...
Click to collapse
Okay, thanks. Any idea if I will need to revert recoveries if I go back to 6.0 or are they backwards compatible?
The_mamba said:
Okay, thanks. Any idea if I will need to revert recoveries if I go back to 6.0 or are they backwards compatible?
Click to expand...
Click to collapse
No need, newest will work with MM