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
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
I rooted my N7 (NE370T) a few months ago but can't remember how I did it. I would now like to flash a stock 4.3 ROM to it, and was looking for the safest way of doing it while retaining root. I have CWM 6.0.1.9 installed - would it be easiest to install a flashable stock rooted ROM zip from CWM? (e.g. http://forum.xda-developers.com/showthread.php?t=2376881)
I'm currently on v4.2.1 (JOP40D)
itm said:
I rooted my N7 (NE370T) a few months ago but can't remember how I did it. I would now like to flash a stock 4.3 ROM to it, and was looking for the safest way of doing it while retaining root. I have CWM 6.0.1.9 installed - would it be easiest to install a flashable stock rooted ROM zip from CWM? (e.g. http://forum.xda-developers.com/showthread.php?t=2376881)
I'm currently on v4.2.1 (JOP40D)
Click to expand...
Click to collapse
Yes it would be easiest to flash a 4.3 ROM actually. I went the way of Clean ROM 4.0 and faux kernel and I don't regret it. It came pre rooted and optimized. Though as always you should make a nandroid before you flash anything.
Also, make sure your bootloader is up to date if you have problems flashing a 4. 3 ROM
Sent from my Nexus 7 using Tapatalk 4 Beta
TheLastSidekick said:
Yes it would be easiest to flash a 4.3 ROM actually. I went the way of Clean ROM 4.0 and faux kernel and I don't regret it. It came pre rooted and optimized. Though as always you should make a nandroid before you flash anything.
Also, make sure your bootloader is up to date if you have problems flashing a 4. 3 ROM
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Sorry for the dumb question, but how do I check and update my bootloader version??
Check the dev section for the latest bootloader. As for checking, you'd have to use commands in fastboot and I'm sorry I don't know them. Basically what I would do is just do as I said in the previous post. If things don't work, then it's obvious you'd need to either update Cwm or your bootloader or both.
Sent from my SGH-T999 using Tapatalk 4 Beta
You might want to have a look at my blog, there I described a very easy way for updating to 4.3
Boot loader version comes up in the bootloader screen ( vol down + vol up + power while tab is off ) .. And to flash the bootloader
Code:
fastboot flash bootloader bootloader.img
4.23 is the latest version for bootloader.
Sent from my Nexus 7
Thanks for all the help. I managed to successfully flash a pre-rooted 4.3 stock ROM from a zip using CWM recovery. I suspect that my bootloader may not be the latest but everything seems to be working OK so I guess it's OK to leave it.
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
Hi Guys,
So I tried the new stock Kitkat firmware for my d802. Flashed the KDZ through support tool. I lost root as expected.
Then I started to miss root and control over my phone, so I wanted to go back to Jellybean.
After some difficulties I got the support tool working in offline mode. Flashed Jellybean stock KDZ.
Rooted the phone again and installed recovery.
Converted the stock KitKat rom to a flashable zip, and copied it to SD card.
I flashed the zip and all went fine.
Anyhow, when I wanted to return to recovery it did a factory reset instead, and now I can start all over.
Do we have a solution to this problem?
Thanks.
A
szaboagoston said:
Hi Guys,
So I tried the new stock Kitkat firmware for my d802. Flashed the KDZ through support tool. I lost root as expected.
Then I started to miss root and control over my phone, so I wanted to go back to Jellybean.
After some difficulties I got the support tool working in offline mode. Flashed Jellybean stock KDZ.
Rooted the phone again and installed recovery.
Converted the stock KitKat rom to a flashable zip, and copied it to SD card.
I flashed the zip and all went fine.
Anyhow, when I wanted to return to recovery it did a factory reset instead, and now I can start all over.
Do we have a solution to this problem?
Thanks.
A
Click to expand...
Click to collapse
We are waiting for LG to release KitKat kernel sources for D802 before a solution can be made, but it does require you to go back to JB again and then flash a KitKat rom with the modified kernel in order to keep your custom recovery
GizmoKaca said:
We are waiting for LG to release KitKat kernel sources for D802 before a solution can be made, but it does require you to go back to JB again and then flash a KitKat rom with the modified kernel in order to keep your custom recovery
Click to expand...
Click to collapse
Thanks. I thought that if it was a flashable zip, I could always return to custom recovery, but of course it is the content of the file that needs to be modified. I'll wait.
GizmoKaca said:
We are waiting for LG to release KitKat kernel sources for D802 before a solution can be made, but it does require you to go back to JB again and then flash a KitKat rom with the modified kernel in order to keep your custom recovery
Click to expand...
Click to collapse
it would not be just a modified kernel it would be an entirely modified zip with parts from 4.2.2 and 4.4.2 so that it can support custom recovery like in jb but be able to boot into kk in fact the only reason we need the kernel source is because we have to add some lines so it can allow jb and kk partiotions to work together
---------- Post added at 11:30 AM ---------- Previous post was at 10:33 AM ----------
D802 kit Kat kernel source just came out a few hours ago so soon you guys should see a stock kk Rom with root and recovery support
Sent from my LG-D800 running kitkat using XDA Premium 4 mobile app
Can't wait to see that. Is there any downsides to this method or is all working well with this work around?
Sent from my LG-D802 using Tapatalk
ephumuris said:
Can't wait to see that. Is there any downsides to this method or is all working well with this work around?
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I have been using it but for att and have not experienced any troubles and I also know of a few people who have already flashed roms whitput trouble also it seems like the g pro 2 rom might be the first to seeing custom recovery on d802 since someone there already made a patch but has not tested it yet and thus has not released it yet
Hey guys, I'll keep it short. I was rooted, installed TWRP, running Simple Rom and was just feeling to flash erobot. Flashed it doing full wipes and then rebooted, cool. Got to the samsung logo and within a second back to the note 4 screen. Okay I said, maybe the file I downloaded was corrupted or I installed it wrong. Did it over again, this time trying a few variations in the aroma installer (not installing xposed) thought maybe that was the problem. Bam same issue.
No worries I still had the old simple rom on the sd card. Went back with the same install and what do you know, that rom is now in a bootloop as well. Tried flashing through odin but I always get a nand write failed to start or something like that. Tried 3 different usb ports and same issue.
Am I missing something? Any advice would be greatly appreciated.
So you are using the Exynos model? Last I checked there is this OJ5 bootloader which can't be downgraded from!
ithehappy said:
So you are using the Exynos model? Last I checked there is this OJ5 bootloader which can't be downgraded from!
Click to expand...
Click to collapse
Yes I'm on the exynos model. So what did I do wrong, I went from lollipop to a lollipop rom. I didn't go back to KK or anything. What do I have to do?
guys help me im having bootloop because i was trying to install the su suser .in my note 4 Note 4 N910C lolipop in tw recovery still boot loop? because i want to root it .send me a maasage thank you
Anyone?
Did you flash a kernel for your variant after flashing the ROM?
No but that is my next move today, had a feeling it might be the problem, I'll try it and report back.
Oj5 bl doesn't let the flash of older rom even lp 5.1.1 older then oj5 but erobot 12 and 13.4 are newest then oj5 so it must be something else like the supersu v2.65 have issues with some costum kernels try to flash v 2.45
radium56ad said:
Oj5 bl doesn't let the flash of older rom even lp 5.1.1 older then oj5 but erobot 12 and 13.4 are newest then oj5 so it must be something else like the supersu v2.65 have issues with some costum kernels try to flash v 2.45
Click to expand...
Click to collapse
Will try that, thanks. On a side note, flashed custom kernel after flashing the ROM and nothing same bootloop.
try this! http://forum.xda-developers.com/note-4/help/n910c-to-stock-rom-cm13-t3321132
migsguerra said:
guys help me im having bootloop because i was trying to install the su suser .in my note 4 Note 4 N910C lolipop in tw recovery still boot loop? because i want to root it .send me a maasage thank you
Click to expand...
Click to collapse
Had the same problem, solved it by flashing cf auto root using ODIN.
can't you just flash the previous rom again??
Enter your recovery and flash your "old" rom