Hey guys!
I have been using the new 4.4 roms as my daily drivers, but strangely some of them start rebooting as soon as I can enter my sim digits to unlock the phone.
For example, SlimKat works, as does CRDroid4.4. Others, like PURITY bootloop.
I have updated my bootloader. Not the modem driver (which seems unnecessary to me with this problem).
I am using TWRP, the newest November release.
Unnecessary? Says who?
When u update to KitKat make sure to update everything. I know twrp works great but I recommend sticking with cwm recovery if possible. KitKat custom Roms are in early stage. Give it sometime. I am using stock KitKat; so far everything is working for me.
Sent from my Nexus 4 using Tapatalk
Related
hi to all. is anyone having issus with latest DLL7?
what i mean is that i made a clean install of LL7. after rooting with autoroot i installed TWRP 2.3.2.3 cause latest gave me only black screen.
but if i want to update from 2.3.2.3 to 2.3.3.1 it does never boot to recovery bur instead it gives broken Samsung n7100 screen.
it is the same if installing any CWM recovery. so Sammy has made some really weird changes with this update.
any other info. maybe bootloader downgrade just as in S3 thread. Advices
This is a little bit like my problems but I have random reboots instead. They occur almost immediately on a clean XLL7 install flashed from Odin without any root or apps installed.
Everything works perfectly in 4.1.1.
sorry to hear that. but this is nothing like that. to me this looks pretty serious. it seems like plus in security from Sammy.
as for you you can try re-install the stock rom for your phone using Kies.
all you have to do is open kies go to tools- and sellect the 2 or 3 option with your phone not connected.
write GT-N7100 and right after the serial number from your phone, follow instructins on screen.
bear in mind. this will wipe your phone.
mariosraptor said:
sorry to hear that. but this is nothing like that. to me this looks pretty serious. it seems like plus in security from Sammy.
as for you you can try re-install the stock rom for your phone using Kies.
all you have to do is open kies go to tools- and sellect the 2 or 3 option with your phone not connected.
write GT-N7100 and right after the serial number from your phone, follow instructins on screen.
bear in mind. this will wipe your phone.
Click to expand...
Click to collapse
I will try that and see what will happen.
Do not flash any recovery !!!!!!!!
They updated the bootloader so it is very dangers to flash untested mods and stuff.
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
Do not flash any recovery !!!!!!!!
They updated the bootloader so it is very dangers to flash untested mods and stuff.
Click to expand...
Click to collapse
I've flash the last ARHD rom 8.o which have last dll7 firmware and after note2core kernel 2.21 and all works fine. Now I won't install anything else until it's proved working on dll7.
JCVD_ said:
I've flash the last ARHD rom 8.o which have last dll7 firmware and after note2core kernel 2.21 and all works fine. Now I won't install anything else until it's proved working on dll7.
Click to expand...
Click to collapse
do not worry. he means with stock rom.
in ARHD and other custom roms bootloader is left ou of flash.
anyway. i think that sammy has changed the some partitions. twrp works but only 2.3.2.3
No the roms who are based on dll7 are safe.
The recovery imao needs to be updated.
Sent from my GT-N7100 using xda app-developers app
Do you mean that it is dangerous to flash the CWM recovery to the device when it runs XXDLL7?
I flashed the root and CWM package after flashing XXDLL7 and it seems to work (my random reboot problem is unrelated I guess since it happened even with just stock recovery in place).
Now, I have the new bootloader and radio and flashed BatteryPlus 0.2 from CWM without any problems. I flashed the CWM-root-package through Odin after flashing XXDLL7, also from Odin.
So the question is: is there a problem with CWM and other custom recoveries and the XXDLL7?
Or are we talking about flashing mods?
No it can be an issue. It's not recommended at this stage.
Sent from my GT-N7100 using xda app-developers app
If there is a problem with CWM and XXDLL7, that could perhaps explain my reboot problem in that case.
If so, I will hold off for a while and stay on my current configuration.
I have the new bootloader and radio already.
i have noticed that 4.1.2 isnt so friendly with custom recovery. I had cwm recovery and going into it, took a lot of time with 4.1.2 firmware. Maybe samsung is trying to make some higher security in 4.1.2 against custom recoveries and etc.
If they wanted they could have made it absolutely protected. No I don't think they actually wanted to increase security.
I just think the new bootloader isn't friendly with the old recovery.
Sent from my GT-N7100 using xda app-developers app
Hello, I have a new note 3 n900tmobile. I love it but, i cant live with touchwiz, i am rooted with twrp... i tried to flash cwm.tar through the lovely odin. But with the 4.4 bootloader i have learned that changes are permanent and cwm just throws me through a bootloop. I also get a bootloop through twrp flashing cm11 plz help! I also cant flash to 4.3 due to the bootloader? i think thats why.
I also flashed phillz cwm and tried flashing same issue I thought it might change due to not flashing on twrp with some devices namely the optimus , I'm gonna see if the latest nightly will flash correctly. If not the release candidate.
Sent from my SM-N900T using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2614461
This is what you need to know. For now wait and flash the latest nightlies and it will be fixed I have faith in cyanogenmod.
PS. I should have looked done some more research before starting a new thread thanks.
Sent from my SM-N900T using Tapatalk
Hi,
I just got a new phones so I decided it'd be cool to root my old RAZR M. I got the root and unlocked bootloader, and then I went in to try and install a custom rom. It ended failing and it gets stuck on the "WARNING BOOTLOADER UNLOCKED" screen. I'm able to go into fastboot and recovery.
I did some looking around, and I found that you can use RSD to get stock ROMs back. I tried downloading the 4.4.2 ROM from here, but it for some reason ends up going down to 0b/s and then says network error, so I tried the 4.1.2. It downloaded, and i went in using RSD to flash it, but it says that gpt_main0.bin failed and it stops. Since I did that, whenever I go into recovery it just freezes and I can't do anything.
Anyone have any idea what I can do to either get the 4.1.2 one working and root that or get the 4.4.2 one downloaded and try that?
Thanks
EDIT: Got 4.4.2 loaded back and did research and got CM11 loaded. Thanks anyways!
Please tell us what stock version you're on and what recovery and ROM you installed. It sounds like you've combined a JB BL ROM with a KK BL phone or vice versa.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
I'm on 4.4.2 stock, the recovery I have is TWRP. I tried to install CarbonRom. I guess i should have done more research for ROMs.
Also, I've been able to keep a download of stock 4.4.2 rom going and it's ~85% done so I'm hoping it's able to finish this time.
EDIT: Got 4.4.2 downloaded and installed using RSD. Going to get it all rooted again. Does CyanogenMod 11 work with version 183.46.10.XT907.Verizon.en.us?
Thanks
wholocked10 said:
EDIT: Got 4.4.2 downloaded and installed using RSD. Going to get it all rooted again. Does CyanogenMod 11 work with version 183.46.10.XT907.Verizon.en.us?
Thanks
Click to expand...
Click to collapse
Yes it does, however CM11 for KK BL (moto_msm8960) still has these nasty WiFi and GPS bugs. If you want a bug-free CM11, you'll have to follow the guide in General section to downgrade to JB (98.30.1) and then flash CM11 for JB BL (moto_msm8960_jbbl). Don't worry, if you've unlocked your BL, then nothing would relock it, not even downgrading.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Hi guys,
I'm a newbie in this rooting world. So please bear with me. I know this forum will help me solve my problems and answer my questions so here goes.
The problem is I can't flash any rom. I'm having this error
"E:Error executing updater binary in zip '/sdcard/Download/CM12/CM-12-20150802-NIGHTLY-D802.zip"
What I did was
-Rooted my phone
-Install AutoRec to install TWRP Recovery
-Install quickboot
-Reboot into recovery
_Update my TWRP recovery to 2.8.7.1 bumped
-Backed up my everything
-Wipe everything (except Internal Storage)
-Install CM12 alongside with GAPPS
Now everytime I flash a rom I end up with that error.
My device is
LG G2 D802 Rooted Running on 5.0.2 Stock ROM.
Can somebody help me please? It will be much appreciated.
Thanks XDA Members.
Can you also suggest some good ROMS compatible with my device?
Thank you.
I got exactly the same message on my d802.
Unfortunately, I wiped my system and it rebooted with a "security error" message. I had to restore a stock LP ROM using LG's Mobile Support Tool program.
@audit13 and @markl098 official cm12 might be still using the old loki method of installing so it will need the jellybean bootloader. Most of the times if you get that error you are using a rom which is using loki on a kitkat bootloader. I suggest to use nevax bootloader changer and flash the rom. You might also need another modem for it. Search it on the forum which modem you need for the official cm12, you probably need kitkat aosp modem from dr87.
I also suggest to look for the newer roms in the forum here in xda as most of them are all using new caf sourcecode and running on lollipop bootstack with bump. (Ofcourse kitkat bootloader)
Audit13 the security error probably happend because you wiped the system but the boot.img remained and loki isn't signing the boot.img with an lg key so it will result on kitkat bootloader in an security error. With bump that problem is fixed as the kernels are getting signed with an lg key. I hope you guys can flash now happy further with no probs
Verstuurd vanaf mijn LG-D802 met Tapatalk
I guess it not be a good idea to change mine then.
Verizon LG G2
- sent from LG G2 (doronize.com)
Thank you so much for your answer. I can't find much info on that regard. Things becoming more clear now. Can I ask one more question?
I was on stock, decide to try SlimSaber, which is quite nice by the way. So, I rooted my D800 and got TWRP. Then flashed Loki's lollipop bootstack (bootstack-d800-LP_30d-loki-signed.zip) recommended by OP and ROM and GAPPS. Everything works perfect. Now if I want go for 4.4.2 based stock ROM for example I should flash K.K bootstack before? I found this file - bootstack-d800-KK_20y-v1.1-blastagator-signed.zip. So is this mandatory always flash bootstack before upgrading downgrading, right? I can't find any detailed info on this in XDA unfortunately.
Thank you for your time.
Greetings.
wulsic said:
@audit13 and @markl098 official cm12 might be still using the old loki method of installing so it will need the jellybean bootloader. Most of the times if you get that error you are using a rom which is using loki on a kitkat bootloader. I suggest to use nevax bootloader changer and flash the rom. You might also need another modem for it. Search it on the forum which modem you need for the official cm12, you probably need kitkat aosp modem from dr87.
I also suggest to look for the newer roms in the forum here in xda as most of them are all using new caf sourcecode and running on lollipop bootstack with bump. (Ofcourse kitkat bootloader)
Audit13 the security error probably happend because you wiped the system but the boot.img remained and loki isn't signing the boot.img with an lg key so it will result on kitkat bootloader in an security error. With bump that problem is fixed as the kernels are getting signed with an lg key. I hope you guys can flash now happy further with no probs
Verstuurd vanaf mijn LG-D802 met Tapatalk
Click to expand...
Click to collapse
@wulsic, your suggestion worked perfectly. I am now running a custom LP ROM
Thank you, thank you, thank you.
Sorry my phone is in my pocket I didnt knew I posted something. Peace!
shrisha said:
Thank you so much for your answer. I can't find much info on that regard. Things becoming more clear now. Can I ask one more question?
I was on stock, decide to try SlimSaber, which is quite nice by the way. So, I rooted my D800 and got TWRP. Then flashed Loki's lollipop bootstack (bootstack-d800-LP_30d-loki-signed.zip) recommended by OP and ROM and GAPPS. Everything works perfect. Now if I want go for 4.4.2 based stock ROM for example I should flash K.K bootstack before? I found this file - bootstack-d800-KK_20y-v1.1-blastagator-signed.zip. So is this mandatory always flash bootstack before upgrading downgrading, right? I can't find any detailed info on this in XDA unfortunately.
Thank you for your time.
Greetings.
Click to expand...
Click to collapse
Ehhm. You can try it. The reason why is because the use of bootstacks became more since lollipop. You can try it. Perhaps it works else you could always autorec and then folllow the guide on how to flash. I can test it perhaps also for you later. Ofc with my d802 version but I am still underway from heading back so I can test jt only from wednesday
@audit13 no problem. :good: enjoy
Verstuurd vanaf mijn LG-D802 met Tapatalk
@audit13
Can you tell me how did you do it ? I'm really new to this.
Edit:
NVM, I figured it out. I just used the nevax's bootloader changer. Changed to JB Bootloader and now I can flash custom roms with no errors. Thank you @wulsic
Hey guys, just pulled my nexus 7 out. I want to update it to the latest, but it's been so long since I've used it, I don't know where to begin. Right now here's what it's running:
Android 4.3
Model ME370T
Build CleanROM 4.0.0
Kernel 3.1.10 leankernel grouper 43-2-0-+
Whatever I do, I don't want to lose root etc. I would like to update it to either the latest kitkat if available or Lollipop. Have all the bugs been worked out for the most part with the lollipop roms on this tablet? I've only briefed the threads so far.
Should I just use Wug's Nexus Rootkit to do everything? I just don't want to lose root. I know with my ATT s4 you can lock the bootloader with the later updates and just dont wanna make a mistake.
Trying to keep the tablet as close to stock look as possible, but some cosmetic changes aren't too big a deal to me. Cleanrom was pretty good, but I'll have to research some of the new ones now.
Thanks!
danman132x said:
Hey guys, just pulled my nexus 7 out. I want to update it to the latest, but it's been so long since I've used it, I don't know where to begin. Right now here's what it's running:
Android 4.3
Model ME370T
Build CleanROM 4.0.0
Kernel 3.1.10 leankernel grouper 43-2-0-+
Whatever I do, I don't want to lose root etc. I would like to update it to either the latest kitkat if available or Lollipop. Have all the bugs been worked out for the most part with the lollipop roms on this tablet? I've only briefed the threads so far.
Should I just use Wug's Nexus Rootkit to do everything? I just don't want to lose root. I know with my ATT s4 you can lock the bootloader with the later updates and just dont wanna make a mistake.
Trying to keep the tablet as close to stock look as possible, but some cosmetic changes aren't too big a deal to me. Cleanrom was pretty good, but I'll have to research some of the new ones now.
Thanks!
Click to expand...
Click to collapse
At your state you can't keep root without updating. Best way to upgrade is to get the latest factory image (Lollipop LMY47V) and flash that. After that flash latest trwp and flash supersu zip or flash a rom
GtrCraft said:
At your state you can't keep root without updating. Best way to upgrade is to get the latest factory image (Lollipop LMY47V) and flash that. After that flash latest trwp and flash supersu zip or flash a rom
Click to expand...
Click to collapse
Sounds good, thanks for the guidance. I'll follow that path then