Related
So, first,
Thanks all in advance.. You are amazing.. I, and so many others have learnt so much from you and your support.
Now,
I have a Canadian n900w8
http://www.mrcrab.net/viewstockrom/10688-sm-n900w8.html
I was so happy at that ROM,and was playing around.. Learning.. And ran into problems..
I made a stupid mistake, really.. Now I don't know how to get out..
I installed a 4.4.4 boot loader.. And flashed with Phil's, back to my 4.4.2 fine, was testing.. So ten I tried a 4.4.4 ROM, and the boot loader.. Worked.. And then some how I lost my recovery, now no matter what I do I can't get a recovery to load.. I have the ROM working, except the modem does work.. Its rooted.. And I can flash a little with flashify, or Odin.. But there are only att2 recoveries.. For 4.4.4 and any TLS recoveries are for 4.4.2..
Any help would be appreciated.. Thanks all in advance..
I already know I'm a noon, no sence reminding me, that's why I'm here..
as far as i know i can still odin back to my normal firmware,
is that correct?
it's been 3 days, i've been trying to download the right one, but most of the mirrors are brokens..
I'm currently Downloading at 35k from one.. so if it's just that simple,
I'll post back so people know..
There seems to be allot of confusion about bootloaders...
as far as i understand though, the one i flashed witih wasn't locked, so..
I think I can still odin to stock..
GhostCyber said:
as far as i know i can still odin back to my normal firmware,
is that correct?
it's been 3 days, i've been trying to download the right one, but most of the mirrors are brokens..
I'm currently Downloading at 35k from one.. so if it's just that simple,
I'll post back so people know..
There seems to be allot of confusion about bootloaders...
as far as i understand though, the one i flashed witih wasn't locked, so..
I think I can still odin to stock..
Click to expand...
Click to collapse
1. Download and unzip the latest firmware for your device: HERE.
2. Remember untick autoreboot in ODIN. Wait till the flash finish. Reboot your device in Recovery Mode and Wipe data/Factory reset your device. Reboot now normally.
3. Install this APPhttps://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en and take a look the part that tells "BOOTLOADER" for clarify things then.
Thanks.
Joku1981 said:
1. Download and unzip the latest firmware for your device: HERE.
2. Remember untick autoreboot in ODIN. Wait till the flash finish. Reboot your device in Recovery Mode and Wipe data/Factory reset your device. Reboot now normally.
3. Install this APPhttps://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en and take a look the part that tells "BOOTLOADER" for clarify things then.
Click to expand...
Click to collapse
Thanks,
Like I said I have been trying to do that, but i apreciate you conferming it will work..
unfortunately, samMobile has just broken links to the rom...
I'm on my forth attempt, downloading froma source with 45k...
Why sammobiles got broken dl's I don't know, but it really has made this experience draw out.
Thanks Again,
Peace.
thanks man. everything worked out, thanks for the reassurances, bricked stuff is scary...
for everyone else with a telus note...
i spent 3 days trackingn the stock firmware, so i'm uploading it to a site, and will post it here sometime soon..
Okay, I've searched the forum for several hours but there's just too much here to make sense of.
My phone is a SM-G900W8 brought home June 19 this year.
Stock Lollipop 5.0 pre-installed.
Code:
Baseband version: G900W8VLU1BOC1
Kernel version: 3.4.0-4100894
Build number: LRX21T.G900W8VLU1BOC1
SE for Android status: Enforcing, SEPF_SM-G900W8_5.0_0002
KNOX version: 2.3
Rooted using CF-Auto-Root (this file), Custom recovery is Philz Touch 6.57.8 klte.
Both of these were in place early on and haven't caused any problems.
Everything was working perfectly fine until last night, when I tried this trick (in first post), rebooted, and now I'm stuck at the splash screen.
Nothing gets me out except a battery pull.
I've tried:
Button combo volup - home - power to go to recovery; this does nothing from the splash screen (actually even pressing and holding down power does nothing), and after a battery pull it won't boot into recovery either.
Booting into download mode (success! yay!) and using Odin to re-flash Philz recovery. Reboot doesn't go into recovery, as stated above.
Just waiting, at various points in the process (while in splash screen, while turned off) to give a chance for things to happen if they just needed time.
So now I'm able to get into download mode and use Odin but from there I don't know what to do next. Flash the bootloader? Okay, but there are so many links...which one do I use? Of all the specs I've gathered, why didn't I find that out?
Can somebody help me please?
[EDIT: Solution and links, for SM-G900W8 users who might be looking for help]
I finally managed to boot into recovery by leaving the USB cable connected to the computer while pressing volup+home+power, a last-ditch trick found in deanr1977's very helpful thread "Read before flashing a Rom (Tips for new & old)"
Links to the firmware for this specific model can be found here, or if you just need a piece:
G900W8_OC1_Stock_Partitions.tar.md5
G900W8_OC1_100%_Stock_Rooted_ROM.zip
Stock_G900W8_VLU1BOC1_Kernel.zip
G900W8-LP-VLU1BOC1-MODEM.tar.md5
PushyPhoenix said:
Okay, I've searched the forum for several hours but there's just too much here to make sense of.
My phone is a SM-G900W8 brought home June 19 this year.
Stock Lollipop 5.0 pre-installed.
Code:
Baseband version: G900W8VLU1BOC1
Kernel version: 3.4.0-4100894
Build number: LRX21T.G900W8VLU1BOC1
SE for Android status: Enforcing, SEPF_SM-G900W8_5.0_0002
KNOX version: 2.3
Rooted using CF-Auto-Root (this file), Custom recovery is Philz Touch 6.57.8 klte.
Both of these were in place early on and haven't caused any problems.
Everything was working perfectly fine until last night, when I tried this trick (in first post), rebooted, and now I'm stuck at the splash screen.
Nothing gets me out except a battery pull.
I've tried:
Button combo volup - home - power to go to recovery; this does nothing from the splash screen (actually even pressing and holding down power does nothing), and after a battery pull it won't boot into recovery either.
Booting into download mode (success! yay!) and using Odin to re-flash Philz recovery. Reboot doesn't go into recovery, as stated above.
Just waiting, at various points in the process (while in splash screen, while turned off) to give a chance for things to happen if they just needed time.
So now I'm able to get into download mode and use Odin but from there I don't know what to do next. Flash the bootloader? Okay, but there are so many links...which one do I use? Of all the specs I've gathered, why didn't I find that out?
Can somebody help me please?
Click to expand...
Click to collapse
factory reset. Then flash stock rom. if you cant boot into recovery try the latest twrp. It works if its still not working then flash stock firmware from SAMMOBILE with odin. it will work then
Thanks for the reply. The problem I'm having is knowing where to download the files I need to flash - because there are so many threads here for so many different models of this phone. Believe me, I've looked, and keep turning up everything BUT W8
I'm tired and frustrated and need my phone functional - can you point me to a post or a thread with the latest version of TWRP that I can flash with Odin?
[edit] Sorry about that - I found the thread. I'll give that a shot and see what happens.
PushyPhoenix said:
Thanks for the reply. The problem I'm having is knowing where to download the files I need to flash - because there are so many threads here for so many different models of this phone. Believe me, I've looked, and keep turning up everything BUT W8
I'm tired and frustrated and need my phone functional - can you point me to a post or a thread with the latest version of TWRP that I can flash with Odin?
Click to expand...
Click to collapse
EDIT: THESE TOOLS ARE FOR 900F MODEL
Latest twrp from https://twrp.me/
Philz recovery from https://mega.co.nz/#!oVNz0T6C!VII47M...MpQIN2b-PEUYN8
Best Stock firmware 5.0 BTU from http://www.sammobile.com/firmwares/download/44413/G900FXXU1BOC7_G900FOXA1BOC7_BTU/
Enter download mode and Flash either one of the recoveries and Clear dalvik cache, clear cache, format system, format data and then factory reset. After that boot into odin mode directly and flash the Stock Firmware.
note: in Odin uncheck "auto reebot option" and after flashing recovery when the odin shows its done wait 1 minute disconnect usb and pull out battery then turn it on if your phone says "Recovery is seandroid enforcing" wait for 3-4 seconds it will go away and recovery will boot up.
dork997 said:
Best Stock firmware 5.0 BTU from http://www.sammobile.com/firmwares/download/44413/G900FXXU1BOC7_G900FOXA1BOC7_BTU/
Click to expand...
Click to collapse
Now, I just want to check: this is for the G900F; will it make a huge difference to my phone? Can I restore my data directly from the backup? I thought what I needed is the exact stock rom that was installed on this phone when I got it so I've been looking everywhere for the G900W8 firmware. I do intend to play with tweaked ROMs in future, but today's not that day.
Finally managed to boot into recovery after flashing TWRP - read a tip somewhere about doing the keypresses while connected to PC via USB. Currently running a nandroid backup before moving on to all the wiping/formatting steps - at least then if something else goes wrong I've got the latest data. :victory:
PushyPhoenix said:
Now, I just want to check: this is for the G900F; will it make a huge difference to my phone? Can I restore my data directly from the backup? I thought what I needed is the exact stock rom that was installed on this phone when I got it so I've been looking everywhere for the G900W8 firmware. I do intend to play with tweaked ROMs in future, but today's not that day.
Finally managed to boot into recovery after flashing TWRP - read a tip somewhere about doing the keypresses while connected to PC via USB. Currently running a nandroid backup before moving on to all the wiping/formatting steps - at least then if something else goes wrong I've got the latest data. :victory:
Click to expand...
Click to collapse
i am sorry the tools i mentioned are for 900f model. Here http://www.sammobile.com/firmwares/database/SM-G900W8/ you can find firmware for G900W8. Just factory reset format dalvik cache, cache , data and system and flash your stock firmware in recovery. There are many different firmwares available with the exact bootloader and modem but they are carrier specific. I don't know which carrier you are on (if any) so just go through the list and download the firmware you were on, flash it. I will highly recommend you to backup your EFS and modem folder aswell just incase anything goes wrong and u flash the wrong firmware.
Oh! Oh! I found it! The stock ROM, as well as the kernel and the modem! So, next question - should I flash all three or just the ROM?
(God I feel like an amateur right now...Thanks so much for helping me out here dork997. :highfive: )
PushyPhoenix said:
Oh! Oh! I found it! The stock ROM, as well as the kernel and the modem! So, next question - should I flash all three or just the ROM?
(God I feel like an amateur right now...Thanks so much for helping me out here dork997. :highfive: )
Click to expand...
Click to collapse
no prb, Okay if you download the rom from sammobile it should be in a .zip format extract it once and it will give you a .tar.md5 file which you have to flash in odin (this file has bootloader+firmware+modem) if you have 7zip or other such programs it will give you option to re-extract the .tar.md5 file but you dont need to do that just extract the downloaded zip once. and flash it in odin (make sure you factory reset and do the formating steps before flashing it....flashing rom over an old rom has caused some issues for me in the past so i always factory reset before but people also flash without factory reset or formating, choice is urs.
And I believe you've just answered my question. I'll hold off on flashing kernel and modem but I did back up everything, just in case. Wiping/formatting now; crossing fingers that things will go fine from here.
(My carrier is in my userinfo under my name, btw. )
Edit 'cause we keep posting at the same time: Hells yeah, I know how to flash, I've done it tons of times, just never run into this problem or had a device with so many variants so I'm just not used to asking so many questions, is all. I sincerely appreciate you guiding me through, and hope this will help others with this device in the future.
PushyPhoenix said:
And I believe you've just answered my question. I'll hold off on flashing kernel and modem but I did back up everything, just in case. Wiping/formatting now; crossing fingers that things will go fine from here.
(My carrier is in my userinfo under my name, btw. )
Edit 'cause we keep posting at the same time: Hells yeah, I know how to flash, I've done it tons of times, just never run into this problem or had a device with so many variants so I'm just not used to asking so many questions, is all. I sincerely appreciate you guiding me through, and hope this will help others with this device in the future.
Click to expand...
Click to collapse
cheers, if it does help you just try to give it back to the community.....i ve had similar issues and people here on xda helped me out. So i am doing the same.
FYI - It worked like a charm and now Lexie (I name my phones ) is up and running again almost like nothing happened. Thank goodness!
In case anyone else winds up needing them, I'm adding links to the stock firmware I downloaded.
Good day everyone.
Got a strange problem trying to upgrade my Note 4 (910C) to eRobot 11 (11.1) based on the latest COJ5 base.
After flashing device just does not start up - the black screen with "Galaxy Note 4" hangs and nothing goin on. Bootloops sometimes
I tried eRobot and another custom ROM based on COJ5 - the same result.
COI4 based ROM works fine.
Being flashed via ODIN the COJ5 based ROM works fine.
I have latest TWRP recovery, COJ5 bootloader and already have tried flashing service 4-file ROM.
If anyone got any information that can help - please welcome!
Thanks!
kurkovda said:
Good day everyone.
Got a strange problem trying to upgrade my Note 4 (910C) to eRobot 11 (11.1) based on the latest COJ5 base.
After flashing device just does not start up - the black screen with "Galaxy Note 4" hangs and nothing goin on. Bootloops sometimes
I tried eRobot and another custom ROM based on COJ5 - the same result.
COI4 based ROM works fine.
Being flashed via ODIN the COJ5 based ROM works fine.
I have latest TWRP recovery, COJ5 bootloader and already have tried flashing service 4-file ROM.
If anyone got any information that can help - please welcome!
Thanks!
Click to expand...
Click to collapse
Try flashing a kernel after flashing COJ5 ROM. Clear cache/davlik cache also
http://forum.xda-developers.com/note-4/development/n910c-spacex-kernel-v0-1-auto-root-t3192875
http://forum.xda-developers.com/note-4/development/kernel-suemax-kernel-lite-v1-0-t3221865
dicksteele said:
Try flashing a kernel after flashing COJ5 ROM. Clear cache/davlik cache also
Click to expand...
Click to collapse
Done.
I even tried flashing bootloader via ODIN after flashing ROM.
Got bootloop on Sixperience v5 and erobot 11.1.
kurkovda said:
Done.
I even tried flashing bootloader via ODIN after flashing ROM.
Got bootloop on Sixperience v5 and erobot 11.1.
Click to expand...
Click to collapse
ODIN Flash this
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
It should boot up fine. Blow past all the setup.
Boot into Download Mode, ODIN flash TWRP.
https://dl.twrp.me/treltexx/twrp-2.8.7.0-treltexx.img.tar
Boot into recovery then try flashing Six or e-Robot
I have the same phone and I've done this more time that I can count (TODAY !!)
dicksteele said:
ODIN Flash this
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
It should boot up fine. Blow past all the setup.
Boot into Download Mode, ODIN flash TWRP.
https://dl.twrp.me/treltexx/twrp-2.8.7.0-treltexx.img.tar
Boot into recovery then try flashing Six or e-Robot
I have the same phone and I've done this more time that I can count (TODAY !!)
Click to expand...
Click to collapse
Done already.
As I've rote - being flashed via ODIN the COJ5 based rom works fine
After flashing this ROM via ODIN I've tried flashing recovery, then geting root by installing prerooted krernel, then flashing custom ROM.
You've missed the point with flashing prerooted kernel, does this matter?
kurkovda said:
Done already.
As I've rote - being flashed via ODIN the COJ5 based rom works fine
After flashing this ROM via ODIN I've tried flashing recovery, then geting root by installing prerooted krernel, then flashing custom ROM.
You've missed the point with flashing prerooted kernel, does this matter?
Click to expand...
Click to collapse
Depends which ROM, and if it has a kernel in install. Looking through most of them, it is included.
How long are you waiting for it to boot? At the Samsung Logo depending on kernel it could take up to 5-10 minutes.
If it's stuck at first Galaxy Note 4 screen, usually that's kernel. My experience anyways. And I've flashed every 5.1.1 ROM here. Multiple times for many of them.
dicksteele said:
Depends which ROM, and if it has a kernel in install. Looking through most of them, it is included.
How long are you waiting for it to boot? At the Samsung Logo depending on kernel it could take up to 5-10 minutes.
If it's stuck at first Galaxy Note 4 screen, usually that's kernel. My experience anyways. And I've flashed every 5.1.1 ROM here. Multiple times for many of them.
Click to expand...
Click to collapse
It stucks on Galaxy Note 4 screen and bootloops sometimes.
ROMs eRobot and sixperience I've flashed has kernels inside, eRobot even has four via Arome, and I've tried each of them
Well, will try your method, thanks a lot for help, will write down about the results!
kurkovda said:
It stucks on Galaxy Note 4 screen and bootloops sometimes.
ROMs eRobot and sixperience I've flashed has kernels inside, eRobot even has four via Arome, and I've tried each of them
Well, will try your method, thanks a lot for help, will write down about the results!
Click to expand...
Click to collapse
Switch off the phone and remove the battery.Wait 2 minutes then re-insert the battery.Then flash the boot loader via odin.
kakkooran said:
Switch off the phone and remove the battery.Wait 2 minutes then re-insert the battery.Then flash the boot loader via odin.
Click to expand...
Click to collapse
Will be able to try this out later this evening, thanks!
kurkovda said:
Will be able to try this out later this evening, thanks!
Click to expand...
Click to collapse
I'm not sure what that will accomplish. The bootloader gets flashed during the stock ROM install I posted.
That's the sboot.bin file that gets flashed in ODIN not the boot.img that is the kernel with TWRP. Big difference.
Try to enter download mode by shutting off mobile (remove battery if it wont work) and enter downloade mode with 3 finger combo.
I had observed sometimes that flashing with odin by entering downloadmode from software will cause problems....
Maybe this will help...
Greetings
HalloSpencer said:
Try to enter download mode by shutting off mobile (remove battery if it wont work) and enter downloade mode with 3 finger combo.
I had observed sometimes that flashing with odin by entering downloadmode from software will cause problems....
Maybe this will help...
Greetings
Click to expand...
Click to collapse
I'm not sure you are speaking about MY problem
Flashing by ODIN causes no problem, they start after flashing ane custom COJ5 ROM via TWRP.
And I use "hardware" method every time I need to get to ODIN mode
Just wanted to make clear that you flashed COJ5 bootloader using "hardware method".... I actualy cant remeber were I read that flashing otherwise can cause problems (without odin failure)....
And yes I was speaking about your problem
dicksteele said:
ODIN Flash this
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
It should boot up fine. Blow past all the setup.
Boot into Download Mode, ODIN flash TWRP.
https://dl.twrp.me/treltexx/twrp-2.8.7.0-treltexx.img.tar
Boot into recovery then try flashing Six or e-Robot
I have the same phone and I've done this more time that I can count (TODAY !!)
Click to expand...
Click to collapse
As for me this is wiered but that worked obviously 0_o
The phone is booting up now.
But could you please explain what was wrong with this ROMs, or with my phone, or with me?) And - will I need to repeat all this shaman dances to flash any other ROM?
Anyway, I owe you, thanks a lot!
Does anyone knows what makes N910C COJ5 refuses the downgrade? In theory, the downloading mode that ODIN uses should be controlled by the bootloader, correct? The code in the downloading mode is the one responsible for not allowing downgrades. Why can't we just flash a different bootloader that allows us to downgrade or did samsung created some mechanism to protect the current some parts from COJ5 bootloader from being replaced (I noticed I can flash different bootloaders, but the issue with downgrading persists). If we could completely replace the booloader, this would provide answers for this thread and at least 5 other threads diving in the same issue.
amidsal said:
Does anyone knows what makes N910C COJ5 refuses the downgrade? In theory, the downloading mode that ODIN uses should be controlled by the bootloader, correct? The code in the downloading mode is the one responsible for not allowing downgrades. Why can't we just flash a different bootloader that allows us to downgrade or did samsung created some mechanism to protect the current some parts from COJ5 bootloader from being replaced (I noticed I can flash different bootloaders, but the issue with downgrading persists). If we could completely replace the booloader, this would provide answers for this thread and at least 5 other threads diving in the same issue.
Click to expand...
Click to collapse
They did
amidsal said:
Does anyone knows what makes N910C COJ5 refuses the downgrade? In theory, the downloading mode that ODIN uses should be controlled by the bootloader, correct? The code in the downloading mode is the one responsible for not allowing downgrades. Why can't we just flash a different bootloader that allows us to downgrade or did samsung created some mechanism to protect the current some parts from COJ5 bootloader from being replaced (I noticed I can flash different bootloaders, but the issue with downgrading persists). If we could completely replace the booloader, this would provide answers for this thread and at least 5 other threads diving in the same issue.
Click to expand...
Click to collapse
The bootloader was not the issue in this thread. It was flashing ROMs.
Samsung obviously realized we had way to much freedom our phones and has tightened down the sboot.bin (COJ5 bootloader file)
You will notice in your ODIN flashes when trying to downgrade, that's the file it barfs on.
Which surprises me, that why I bought the 910C to get away from the locked down crap from ATT.
---------- Post added at 01:27 PM ---------- Previous post was at 01:21 PM ----------
kurkovda said:
As for me this is wiered but that worked obviously 0_o
The phone is booting up now.
But could you please explain what was wrong with this ROMs, or with my phone, or with me?) And - will I need to repeat all this shaman dances to flash any other ROM?
Anyway, I owe you, thanks a lot!
Click to expand...
Click to collapse
Good deal. Booting up on a Custom ROM?
I usually flash back to stock every now and then. Never hurts.
I'm running SIMPLROM5c. Running pretty good. I've tried them all. I usually run them a couple of days and see how I like it.
All of the ROMs have their own personality. Just find one that fits yours. I'm finding a stock one like SIMPLROM will probably be my daily one, but I have backups of the others to change whenever my mood changes.
The N5 and S6 features are cool, but I bought a Note 4 because it's a Note 4. If I wanted a Note5 or S6 I would have gotten one.
Now the S7 MAY make me change my mind. we'll see.
kurkovda said:
They did
Click to expand...
Click to collapse
And even if we have the device rooted, we can't overwrite the bootloader because of it is not possible interfere with the environment external to hypervisor (like the bootloader, kernel, etc.) unless someone finds a loophole, right? In this situation, wouldn't it be possible to overwrite the booloader completely if we could access the internal sd card and mounting it in a regular linux environment (similarly to the way people used to extract the xbox 360 using a probe). Could it be possible?
dicksteele said:
Good deal. Booting up on a Custom ROM?
I usually flash back to stock every now and then. Never hurts.
I'm running SIMPLROM5c. Running pretty good. I've tried them all. I usually run them a couple of days and see how I like it.
All of the ROMs have their own personality. Just find one that fits yours. I'm finding a stock one like SIMPLROM will probably be my daily one, but I have backups of the others to change whenever my mood changes.
The N5 and S6 features are cool, but I bought a Note 4 because it's a Note 4. If I wanted a Note5 or S6 I would have gotten one.
Now the S7 MAY make me change my mind. we'll see.
Click to expand...
Click to collapse
Yep, the ROM has booted up and works
I'm a kind of newbe for Note4 and now just want to find out who is who But I've stucked being unable to flash the new base ROM, and unfortunately on my native forum there are just a very few rommakers, and no one could give me some info about this issue.
Now I'll test sixperience, and if it's not as good as I hope will try something else
kurkovda said:
Yep, the ROM has booted up and works
I'm a kind of newbe for Note4 and now just want to find out who is who But I've stucked being unable to flash the new base ROM, and unfortunately on my native forum there are just a very few rommakers, and no one could give me some info about this issue.
Now I'll test sixperience, and if it's not as good as I hope will try something else
Click to expand...
Click to collapse
All the ROMs work great, and there's great support. It all depends on what you looking for in a ROM.
I think there's a little too much expectation from people that think jamming (porting) features from other phones (N5 and S6) is supposed to work perfectly on a Note 4.
A lot of work goes into trying to make it work. But if they want the features that are on that phone to work perfectly, buy that phone.
---------- Post added at 02:00 PM ---------- Previous post was at 01:56 PM ----------
amidsal said:
And even if we have the device rooted, we can't overwrite the bootloader because of it is not possible interfere with the environment external to hypervisor (like the bootloader, kernel, etc.) unless someone finds a loophole, right? In this situation, wouldn't it be possible to overwrite the booloader completely if we could access the internal sd card and mounting it in a regular linux environment (similarly to the way people used to extract the xbox 360 using a probe). Could it be possible?
Click to expand...
Click to collapse
I have read someone suggesting doing a NAND ERASE ALL in ODIN during the firmware flash. That should wipe the hell out of everything.
I'm waiting to hear back if he's done that on the OJ5 bootloader.
I've had my phone from a month, I'm not willing to take that chance yet.
Hello, merry Christmas and happy new year as I'm so proud to bring to you all a way to downgrade to 5.0.1 even if you have updated to the new pk firmware. I'm sorry to say that this obviously only works on the 910T model. I could go into a long story about how I've been rooting and roming since the g1 but i wont, instead ill get right into the good stuff. To downgrade flash odin 5.1.1,( im not sure if you even have to do this part but it doesn't hurt) boot up, set up, root it by flashing recovery (TWRP), make sure you unselect auto reboot from odin. after the flash is complete pull the battery, place back in after 30 sec and hold up on the volume, home button, and power. In odin (before you do the following make sure to wipe everything 3x times in recovery and reboot back into recovery then reboot to download mode) flash the following, in BL slot flash the COD6 kernel, and in the CP slot flash COD6 modem. All will pass. Now I didn't boot up, i pulled the battery again and booted to recovery which will still be TWRP, now i did a factory reset and then flashed DaRTHSTALKER v2 and rebooted not expecting it to boot but to my surprise it did and for the last 1hour its been running perfect
I will have some snap shots that I'll be uploading in the next few minutes.
Here are the links for COD6
http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2902574
Picture added
Pic 1
5.1.1 is better than 5.0.1 in battery and performance. You should have jumped to 4.4.4. ?
I did. I used the OG2 from Sam mobile which was the rent a center note 4 and after a few days the camera failed. Then I flashed dynamic kat and while in a call I used action memo and the system ui FC even after a reset. 5.1.1 battery on all the roms I used (which was all ) still had bleeding battery. Just for the record, you can use DaRTHSTALKER v1 on 4.4.4, but not v2. V2 has the best battery on any Rom I've used to date that's why I chose to go back to 5.0.1, but your milage may very. So far my phone is sipping battery. Besides, you may be right but I did this for the option of choice, more roms to flash is always a good thing.
Hangoverr said:
5.1.1 is better than 5.0.1 in battery and performance. You should have jumped to 4.4.4.
Click to expand...
Click to collapse
g1-and-only said:
Hello, merry Christmas and happy new year as I'm so proud to bring to you all a way to downgrade to 5.0.1 even if you have updated to the new pk firmware. I'm sorry to say that this obviously only works on the 910T model. I could go into a long story about how I've been rooting and roming since the g1 but i wont, instead ill get right into the good stuff. To downgrade flash odin 5.1.1,( im not sure if you even have to do this part but it doesn't hurt) boot up, set up, root it by flashing recovery (TWRP), make sure you unselect auto reboot from odin. after the flash is complete pull the battery, place back in after 30 sec and hold up on the volume, home button, and power. In odin (before you do the following make sure to wipe everything 3x times in recovery and reboot back into recovery then reboot to download mode) flash the following, in BL slot flash the COD6 kernel, and in the CP slot flash COD6 modem. All will pass. Now I didn't boot up, i pulled the battery again and booted to recovery which will still be TWRP, now i did a factory reset and then flashed DaRTHSTALKER v2 and rebooted not expecting it to boot but to my surprise it did and for the last 1hour its been running perfect
I will have some snap shots that I'll be uploading in the next few minutes.
Here are the links for COD6
http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2902574
Click to expand...
Click to collapse
1 tip for you.
Not just 5.0.1 You can flash kitkat 4.4.4 also with 5.1.1 bootloader/baseband
Flash any kitkat rom along with nadia kernel 4.4.4 and it will work flawlessly
https://mega.nz/#!accnkb6B!f_wdM79WXZ2UYy2El87DXYctihB40MBjV4imBKlhoDo
I didn't know that.
Would it be stock tmobile 4.4.4 or the rent a center one? After trying so many I was curious to see about going to 5.0.1 without any alt kernels, close to stock because of the battery drain that's plagued our N4 after the 6.0 updates. I know darthstalker uses a stock tmo kernel he just changed enforcing to permissive. Only on v2 does it work on 5.0.1 but v1 could be used on 4.4.4, but there was more done on the second version so that's why I've now flashed v2 of dstalker.
Trex888 said:
1 tip for you.
Not just 5.0.1 You can flash kitkat 4.4.4 also with 5.1.1 bootloader/baseband
Flash any kitkat rom along with nadia kernel 4.4.4 and it will work flawlessly
https://mega.nz/#!accnkb6B!f_wdM79WXZ2UYy2El87DXYctihB40MBjV4imBKlhoDo
Click to expand...
Click to collapse
Also works on 6.0.1 ?
But you can't use darthstalker on 6.0.1:victory:
noob4598 said:
Also works on 6.0.1
Click to expand...
Click to collapse
Still nothing for the t3?
I've been running 601, several note 7 ports and the battery has been very respectable. Why go back?
Sent from my Samsung Note 6
Araltd said:
I've been running 601, several note 7 ports and the battery has been very respectable. Why go back?
Sent from my Samsung Note 6
Click to expand...
Click to collapse
Because many users like me had issues with battery shutdown at 20% & random reboots with marshmallow .while on lollipop or kitkat doesn't happen.marshmallow is good and very well optimized but not good for note 4.
I was also on 6.0.1 and I followed your instructions. I flashed both the modem and kernel successfully. Darthstalker is installed, but my question is can I flash a stock tw rom with out issue. I want to sim unlock my phone but my octoplus box requires stock 5.1.1.
Yes, you can flash stock 5.1.1 though Odin.
gwest04 said:
I was also on 6.0.1 and I followed your instructions. I flashed both the modem and kernel successfully. Darthstalker is installed, but my question is can I flash a stock tw rom with out issue. I want to sim unlock my phone but my octoplus box requires stock 5.1.1.
Click to expand...
Click to collapse
This worked great on my n910t.
---------- Post added at 06:44 PM ---------- Previous post was at 06:43 PM ----------
g1-and-only said:
Yes, you can flash stock 5.1.1 though Odin.
Click to expand...
Click to collapse
Well it worked. Ty for your work on this.
Araltd said:
I've been running 601, several note 7 ports and the battery has been very respectable. Why go back?
Click to expand...
Click to collapse
Besides the random shutdowns, LP's multitasking was better. I don't recall exactly what now, but I remember being disappointed in the MM implementation of it. Can anyone comment on what LP multitasking had?
Flashing the 910T all the way back to ANIH (KitKat) has always been possible with Odin, as far as I know. I haven't experimented fully but I have jumped back and forth a couple of times from firmwares noted as "no way back" without problems. It's only if you insist on using .zips via recovery that problems arise.
It's the 910T3 that has problems even with Odin.
Quick question ... if im on qe2 6.0.1 will this work as well ? im rooted stock, unlocked for metro pcs it would be nice to load 4.4.4 on this i got just the rom for it lol
The Development section is for people to post their own original development work in compliance with the sticky titled "Rules for Posting in Development." Please do no share links to other people's work in that section.
THREAD MOVED
g1-and-only said:
Hello, merry Christmas and happy new year as I'm so proud to bring to you all a way to downgrade to 5.0.1 even if you have updated to the new pk firmware. I'm sorry to say that this obviously only works on the 910T model. I could go into a long story about how I've been rooting and roming since the g1 but i wont, instead ill get right into the good stuff. To downgrade flash odin 5.1.1,( im not sure if you even have to do this part but it doesn't hurt) boot up, set up, root it by flashing recovery (TWRP), make sure you unselect auto reboot from odin. after the flash is complete pull the battery, place back in after 30 sec and hold up on the volume, home button, and power. In odin (before you do the following make sure to wipe everything 3x times in recovery and reboot back into recovery then reboot to download mode) flash the following, in BL slot flash the COD6 kernel, and in the CP slot flash COD6 modem. All will pass. Now I didn't boot up, i pulled the battery again and booted to recovery which will still be TWRP, now i did a factory reset and then flashed DaRTHSTALKER v2 and rebooted not expecting it to boot but to my surprise it did and for the last 1hour its been running perfect
I will have some snap shots that I'll be uploading in the next few minutes.
Here are the links for COD6
http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2902574
Click to expand...
Click to collapse
Ok so, as it turns out, my device is apparently an ACTUAL 910T3. DOK2 T3 ROM still fails, but this time it gave the normal "fused 3>binary 1" error that youre supposed to get if you try to downgrade BL's. Progress. Now, lets see if i can get a T3 DOK2/DOG1 kernel/modem to crack this baby open. Anyone know where i can find TWRP flashable kernel/modem of that sort?
Edit: Use the COD kernel for the BL slot. Download the DOK2 T3 ROM from https://forum.xda-developers.com/no...y-steps-n910t3-dofc-dog1-how-to-root-t3177225 Open the md5 file in winrar. Extract the modem.bin to a folder. Flash modem.bin in TWRP (I used 3.09). Make sure "auto reboot" is unchecked. Wait 10-15 seconds after TWRP says "reset." Pull battery. Flash a 5.1.1 T3 compatible ROM (I used a backup of TEKxodus with the rage 1.8 ZL kernel, ymmv) then flash a DOK2 kernel like https://forum.xda-developers.com/no...t/kernel-beastmode-stock-1-0b-n910t3-t3238775
Looks like data will work with this setup, but wifi does not. Cant get wifi to work on any ROM at all besides MM ones. If you can live without wifi, it looks like T3 users will be just fine. If you cant ... well youre stuck with MM for now. Cause Wifi wont work if your BL and modem versions dont match (and MM modem apparently doesnt like LP which isnt surprising). I found a DOK2 T3 kernel, and it did nothing to crack this thing open. Odin failed to flash it. Looks like simple solutions are out. Unless i missed something etremely obvious.
Araltd said:
I've been running 601, several note 7 ports and the battery has been very respectable. Why go back?
Sent from my Samsung Note 6
Click to expand...
Click to collapse
Im getting great battery life on Max overdrive edge 7 port on 6.0.1
My friend got an old phone from his dad, who had an old custom ROM installed on it, and asked me to return it to the original software.
I used ODIN 3.09 and installed the appropriate ROM which I downloaded from Sammobile.
The phone went into a bootloop, so I wiped the cache and when that didn't work, I wiped all data. After that the phone booted into the Welcome screen and my friend started to configure it. In the middle of the process, the phone rebooted, and now it loads into the Welcome screen, but reboots after a few seconds.
After that I've tried reflashing the software and doing multiple resets, to no avail. Any ideas?
Please let me know of any Ideas. I am very ashamed of damaging my friend's phone.
PS: I should say, I put a bootloader into ODIN the first time I flashed the software because some tutorial recommended it and I haven't seen that requierement in any other tutorial since. Might this be the cause? How could I test that?
What model what firmware what bootloader ??
JJEgan said:
What model what firmware what bootloader ??
Click to expand...
Click to collapse
The phone is a Note 3 N900 UB, the firmware I installed was N900UBSEBQB5, and to be honest, I can't quite tell what the bootloader is, the file I downloaded is just called "bootloader".
the file I downloaded is just called "bootloader
My guess is that's the fault as bootloaders are named same as firmwares
Example >>> BL_N9005ZSUGPJ2
Could be a bootloader for anything .because some tutorial recommended
Have you taken a chance to reflashing the official firmware with ordin , that would be helpful all the time.
After that you should make sure your phone work fine on the official rom .
Then update your Recovery to a third party Rec,like CWM or TWRP .
Next step,flashing an original rom.
larrycn said:
Have you taken a chance to reflashing the official firmware with ordin , that would be helpful all the time.
After that you should make sure your phone work fine on the official rom .
Then update your Recovery to a third party Rec,like CWM or TWRP .
Next step,flashing an original rom.
Click to expand...
Click to collapse
Thats wrong .