I have a boot loop problem when installing CM10.2, CM11, PAC ROMs on N7100.
I did every possible wipe and yet boot looping in animation.
The recovery is TWRP latest.
Is it a problem with the new bootloader with 4.3? I'm using it with Criskelo ROM and it works well.
Should I downgrade to the old bootloader? How?
Thanks
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,
So I put the custom ROM Cyanogenmod 14.1 based on Nougat and my recovery was not booting. I use TWRP. I tried factory resetting through the CM 14 settings and now my phone won't boot into system or recovery. I only have fastboot and don't know what to do.
PLEASE HELP!!!
Thanks in advance,
Gavin
Get modified TWRP.
http://forum.xda-developers.com/devdb/project/dl/?id=21676
Hey guys,
first what happened.
I was running the latest CM 14.1 nightly on my oneplus 3. Then I saw the new Video from xda on youtube. I installed substratum and a theme. But after rebooting I got a bootloop.
Tried resetting via cm recovery did not work. Then tried resetting via fastboot. Also did not work device won't boot up.
So I tried flashing the original boot.img and system.img. Flashing itself worked great. Phone gets to the OP and Android-Logo then screen goes black and device turnes off. Same with the twrp-recovery I tried to flash. Won't boot into recovery.
What can I do/try?
Please help thx
Premaider
Premaider said:
Hey guys,
first what happened.
I was running the latest CM 14.1 nightly on my oneplus 3. Then I saw the new Video from xda on youtube. I installed substratum and a theme. But after rebooting I got a bootloop.
Tried resetting via cm recovery did not work. Then tried resetting via fastboot. Also did not work device won't boot up.
So I tried flashing the original boot.img and system.img. Flashing itself worked great. Phone gets to the OP and Android-Logo then screen goes black and device turnes off. Same with the twrp-recovery I tried to flash. Won't boot into recovery.
What can I do/try?
Please help thx
Premaider
Click to expand...
Click to collapse
Flashed original cm recovery. That works an boots up. What now?
flash the custom recovery for CM or sideload a official oneplus rom.
Hi everyone,
I followed this forum to change My CN BS3 to global rom (using beta rom), i followed the method, unlocking, flashing twrp and flashing rom. Flashing success (via twrp), but its bootloop. Then i did factory reset. Yeah! Its entering the rom, but its stuck and restarting suddenly. So, i flashed the other cn rom but still same. Any solution? Im newbie here. Thank you.
My BS kle-a0 (joy ui 12.5 android 11) before flashing