I have a SM-N900W8 canadian note 3. I just installed new DOC4 lollipop rom via odin. I did clean install by wiping data. I root with CF-Root and flash latest TWRP. Everything seems to work perfectly until i try to made some small mod to add datamobile button in quicksettings using this thread. : http://forum.xda-developers.com/showthread.php?t=2342370
After it boots up to a black screen and a pop up shows up for nearly all of my apps that says they are not responding so all I get is that and a black screen. I reflash the rom via odin without wiping my data, re-root and everything went back fine and my mod works. ???!! I now have my datamobile button.
Later, i made a nandroid backup with TWRP. After reboot i got the same errors.... So i Reflash-rom, re-root, everything back to normal.
TO make a short story, everytime i access recovery or flash something in recovery or modify my system partition i got this errors....
I suspect having partition mismatched ... i don't know...
Any idea ???
Any help appreciated...
Which version of TWRP did you use? As far as I know, the latest only supports up to kitkat (4.4)
Maybe this is what causes your problems?
That's what i thought, I'm using the latest one (2.8.6.0). I ask other users in another thread and they said this version is working flawlessly with lollipop...
I have the same phone, and I flashed lollipop DOC4 using Odin yesterday, with CF-auto-root and TWRP 2.8.6.0.
I just tried (litterally minutes ago) adding the data toggle, and it worked, but I could not reproduce your problem.
Which version of TWRP did you use? The hltecan one or the hltexx?
Tornade69 said:
I have a SM-N900W8 canadian note 3. I just installed new DOC4 lollipop rom via odin. I did clean install by wiping data. I root with CF-Root and flash latest TWRP. Everything seems to work perfectly until i try to made some small mod to add datamobile button in quicksettings using this thread. : http://forum.xda-developers.com/showthread.php?t=2342370
After it boots up to a black screen and a pop up shows up for nearly all of my apps that says they are not responding so all I get is that and a black screen. I reflash the rom via odin without wiping my data, re-root and everything went back fine and my mod works. ???!! I now have my datamobile button.
Later, i made a nandroid backup with TWRP. After reboot i got the same errors.... So i Reflash-rom, re-root, everything back to normal.
TO make a short story, everytime i access recovery or flash something in recovery or modify my system partition i got this errors....
I suspect having partition mismatched ... i don't know...
Any idea ???
Any help appreciated...
Click to expand...
Click to collapse
1. Are you sure you installed correct TWRP? The correct one for your device: HERE.
2. Seems that mod for datamobile button doesn't work for your device. Reflash rom, re-root and don't install that mod. Try that update firmware for some days and tell me how it works :highfive:
I used HLTECAN 2.8.6.0. When i was on 4.4.2 NB7, i was using the same file and i had not problems at all. If you re-read my first post, i said my data toggle is working fine now but i needed to re-flash the entire rom without wiping data to get rid of the many apps errors. I guess i need to reflash everything from scratch... Will use another USB wire and another USB port. Maybe it'll help... Or maybe i should try another root method ??? I used CF-Root for SM-n900w8...
I suggest trying with hltexx, since it is the version I used, and I encountered no problem at all so far.
Let's check for any other difference between devices. I got :
Baseband N900W8VLUBMJ4
Bootloader N900W8UBUCNA2
PDA Version N900W8VLU2DOC4
CSC Version N900W8OYADOC4
Stock Kernel
how do you root n900w8 lollipop rom ?
phberb said:
I have the same phone, and I flashed lollipop DOC4 using Odin yesterday, with CF-auto-root and TWRP 2.8.6.0.
I just tried (litterally minutes ago) adding the data toggle, and it worked, but I could not reproduce your problem.
Which version of TWRP did you use? The hltecan one or the hltexx?
Click to expand...
Click to collapse
I want to root my n900w8 too ...tell me intrusions before tell is it safe .
phberb said:
I suggest trying with hltexx, since it is the version I used, and I encountered no problem at all so far.
Let's check for any other difference between devices. I got :
Baseband N900W8VLUBMJ4
Bootloader N900W8UBUCNA2
PDA Version N900W8VLU2DOC4
CSC Version N900W8OYADOC4
Stock Kernel
Click to expand...
Click to collapse
Hi, can I root N900W8 running N900W8UBU2DOG2 firmware from region TTT with twrp? If not is there any other method I can use to root my device ?
Related
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
There is a script in official firmware that checks for official recovery and if it finds a custom one it tries to overwrite with official one. If i remember correct it's called install-recovery. sh
PhilZ recovery handles it automatically.
It's impossibe to flash anything other than the leaked 4.4.2 stock because you flashed your bootloader to kitkat, no you MUST stay on sammy 4.4.2 till the devs found a solution for this. Thats why you have to read carefully be4 you flash.
silentvisitor said:
There is a script in official firmware that checks for official recovery and if it finds a custom one it tries to overwrite with official one. If i remember correct it's called install-recovery. sh
PhilZ recovery handles it automatically.
Click to expand...
Click to collapse
No luck!
I tried PhilZ recovery from the below link.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltexx
What are my other options?
sid8907 said:
No luck!
I tried PhilZ recovery from the below link.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltexx
What are my other options?
Click to expand...
Click to collapse
This one seems to be the only one working with 4.4.2 right now.
Possible solution
The way I can suggest is to create a little update.zip file with little updater-script to remove install-recovery.sh file from device (just one line needed).
Ok, I found a zip which I am attaching below. You(or anyone) may review the script before flashing.
Place this on your external (or internal) sdcard.
In ODIN don't check Auto reboot
Flash Recovery. Remove phone when it says PASS.
Remove battery. Start in Recovery mode by pressing buttons.
You should now be in new Recovery.
Flash that zip file.
Reboot.
You should be good.
The Auto Reboot for some reason is faded out. Tried different versions of Odin and also tried to open it with the phone connected/disconnected.
I am out of ideas.
I would suggest you to wait for someone to come up with working solution. Being too adventurous with ODIN could brick your device.
sid8907 said:
The Auto Reboot for some reason is faded out. Tried different versions of Odin and also tried to open it with the phone connected/disconnected.
Click to expand...
Click to collapse
Clear out all your ODIN caches etc, delete all files and keep 1.85.
Flash this (only working recovery on 4.4.2) via PDA in ODIN, If it doesn't reboot auto after saying PASS or RESET.. just turn phone off, reboot into recovery and it'll be fine.
EDIT: Just re-read, Re flash your Stock 4.4.2 (Use XEO not the leaked one!) and then start again
Thanks!
Maybe a little off topic, but is there a way to install CM11 on Stock 4.4.2 on the Note 3?
I've been reading Samsung is out with a new bootloader so there is no way round this?
radicalisto said:
Clear out all your ODIN caches etc, delete all files and keep 1.85.
Flash this (only working recovery on 4.4.2) via PDA in ODIN, If it doesn't reboot auto after saying PASS or RESET.. just turn phone off, reboot into recovery and it'll be fine.
EDIT: Just re-read, Re flash your Stock 4.4.2 (Use XEO not the leaked one!) and then start again
Click to expand...
Click to collapse
Thanks!!
sid8907 said:
Thanks!
Maybe a little off topic, but is there a way to install CM11 on Stock 4.4.2 on the Note 3?
I've been reading Samsung is out with a new bootloader so there is no way round this?
Click to expand...
Click to collapse
You may have to do a little reading but I believe CM11 is now working on the KK bootloader...
sid8907 said:
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
Click to expand...
Click to collapse
here's the link for twrp for ya'll http://forum.xda-developers.com/showpost.php?p=50333147&postcount=398
sid8907 said:
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
Click to expand...
Click to collapse
jp.26 said:
here's the link for twrp for ya'll http://forum.xda-developers.com/showpost.php?p=50333147&postcount=398
Click to expand...
Click to collapse
so.... yeah i just updated my bootloader to 4.4.2 and this drove me literally insane. ive been working on it for 4 hours now. i encountered so many problems with installing the bootloader. exact same problem as SID8907. i gotta tell you tho.... you worked some magic my friend. i tried almost everything. then i came across your link. i was like why not? so i flashed the img in odin..... anddddd :drumroll pleaseeeeee:: IT WORKED. ahhh....... so much frustration and the problem is solved!!! thank you so much JP.26 :good::laugh:
is there any word on how to fix this been looking for hours tmobile note beast dont want to put any roots down on my phone before i find a way to flash cm or a non bloated note rom would be nice.
I'll that I've managed is to root and flash twrp I found a way to turn cwm recovery into a tar file and flash through odin. But i just get into a boot loop with cwm due to the boot loader I presume but tarp works fine I just can't flash cm11. I get boot loop every time
Sent from my SM-N900T using XDA Premium 4 mobile app
im sorry but im confused here... does this all simply mean that there is not yet a working cwm for 4.4.2 yet? and that while we can root, there is no working recovery for this version?
I'm not sure myself tarp works but I can't flash cm11
Sent from my SM-N900T using Tapatalk
Phillz cwm Dev edition I think that's the name works its a themed touch cwm. This works great but still can't flash cm so gayyyy
Sent from my SM-N900T using Tapatalk
I was wondering what happened to the cmw too.
The modded cmw by Chenglu is the only one working that I know of.
Link to thread: http://forum.xda-developers.com/showthread.php?t=2454079
I will try to explain me clearly
My phone is working normally and I can restore nandroid without issues
I'm actually with my V29 KK TW and work without issues
BUT If i flash aosp or cm rom, just afeter enter pin code, the screen becomes black like problem with proximity sensor
I can put my hand in front, it doesn't change, If I push the buttons, sometimes the screen appears and disappears immediately
and the more strange is I have this problem with the RR 5.3.9 I had flashed before without issue and can restore a nandroid I have done with it...
I have done a clean flash of my KK TW V29 without issue....
first I have made a FULL wipe include internal storage and flash stock NI4 rom but without any changes
someone got an idea???
thank's
I have flashed successfully 2 QS L differents versions but can't with CM roms (euphoria, tema, RR...)
is there a reason to that
This is x-files troubles, personally I reflash stock LP with Odin and all is good now
I have try back with RR 5.3.9 and got same problem but if I restore nandroid from 5.3.9 it's working without issues...WTF!!!!!!!!!!!!
i try to flash L stock rom with odin root, complete wipe (except ext sdcard)
I run masik script wipe and ael cleaner, format boot, system data
It seem's it begin when I flash arter kernel or the UKM (universal kernel manager) to run civ kernel..
so i try to uninstall ukm but allways without succes
I flashed 4.4 c-rom without issues, so I flashed back KK rom with odin and back to my V29 kk rom
look my signature to have details on my config
thank's for the help..
So...first question:
Did you ever take the official lollipop update from samsung?
Second Question:
What country are you in, and carrier do you use?
Please message me the following details from the sticker inside the device under the battery, so I can grab the Service files from samsung for you!
I've flashed OB1 with odin and flash back after 2 weeks NI4 and the last I try was this N9005XXUFNG2_N9005OXXFNG3_XEF (Open France) (No-wipe)
the flash goes well but doesn't change my BL and modem, before that I was with NI4 BL and NI3 modem and now still with that
I use sosh carrier (orange) in france
will send you the details from sticker
@rayman95 This is what i have found out!!! From my understanding, You took the Lollipop bootloader when you installed the OC1 Package. if you want to completely restore to "Earlier Version", WHICH this may not be possible due to a SAMSUNG new coding issue, You would need to have the complete 4 Files software to repair your device.... As well as using all the following checkboxes in ODIN:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase ALL
Phone Bootloader Update
I Attempted to download your files for the device, but Kies will Not "Initialize" for download, and it will give you an Error if you plug the device into Kies3 i believe because you device is ROMMed.
IF you want to try Kies to restore AND it begins "DOWNLOADING", You can copy the Tmp****.tmp.zip that is created when the progress indicator hits 85% in Kies.
The File location on Win7 is "C:\Users\*Your Screen Name HERE*\AppData\Local\Temp"
If you Have the 4 Part file for NI2, try flashing in ODIN wioth the Above Checkboxes selected!!
Kies don t let me dl any files and gave me some error but don't remember exactly what... but not important because you give me good files.....after that I hope flashing again cm12.1.....
Thank so again chief....
Hi,
I have rooted and installed TWRP on my 910F Note4 as I was fed up waiting on the lollipop update rolling out. I am currently on 4.4.4 and have made a full backup using TWRP of the stock rom.
My intention was flashing the Cyanogen ROM and using that, but i now see on sammobile there is a stock 5.01 rom available. I have a few questions about this.
1. If I flash to Cyanogen can I still revert back to the stock rom 4.4.4 I have made a backup with? I read somewhere there might be problems as I was on KitKat then moved to lollipop(Cyanogen).
2. Can I flash the stock lollipop rom from within TWRP? Or do you have to do this via ODIN?
3. If I flash the Lollipop stock ROM with Odin I assume I will lose root and TWRP? So this would have to done again?
Guess I am asking what is the best way to proceed?
Thanks again
Paul
pmlfrew said:
Hi,
I have rooted and installed TWRP on my 910F Note4 as I was fed up waiting on the lollipop update rolling out. I am currently on 4.4.4 and have made a full backup using TWRP of the stock rom.
My intention was flashing the Cyanogen ROM and using that, but i now see on sammobile there is a stock 5.01 rom available. I have a few questions about this.
1. If I flash to Cyanogen can I still revert back to the stock rom 4.4.4 I have made a backup with? I read somewhere there might be problems as I was on KitKat then moved to lollipop(Cyanogen).
2. Can I flash the stock lollipop rom from within TWRP? Or do you have to do this via ODIN?
3. If I flash the Lollipop stock ROM with Odin I assume I will lose root and TWRP? So this would have to done again?
Guess I am asking what is the best way to proceed?
Thanks again
Paul
Click to expand...
Click to collapse
hi Paul,
1. i beleve to flash CM from kitkat you will need to install the lollipop bootloader first.
2. You have to flash the stock rom via Odin, you will keep all apps settings and files but you will lose root (you u can re root in 3 minutes)
Best thing you could do is flash the stock rom first with odin, see how that feels (IMO its good been using it for months now) and then root it and back it up and flash CM12 (you dont have to flash any boatloader at this point)
grtz
Luc
Racinghart91 said:
hi Paul,
1. i beleve to flash CM from kitkat you will need to install the lollipop bootloader first.
2. You have to flash the stock rom via Odin, you will keep all apps settings and files but you will lose root (you u can re root in 3 minutes)
Best thing you could do is flash the stock rom first with odin, see how that feels (IMO its good been using it for months now) and then root it and back it up and flash CM12 (you dont have to flash any boatloader at this point)
grtz
Luc
Click to expand...
Click to collapse
Thanks will flash to lollipop today then....
pmlfrew said:
Thanks will flash to lollipop today then....
Click to expand...
Click to collapse
Ok tried to flash Stock O2 UK lollipop ROM via ODIN and got error message on screen. MD5 too big or something. Had to pull battery on phone. Had to then reflash TWRP. Got back into TWRP and tried to do a recovery of the backup I took but phone is stuck at Galaxy note 4 screen. It then shuts down and restarts and gets to the same screen again.
Do I try a different ROM? What can I do?
Thanks
Paul
pmlfrew said:
Ok tried to flash Stock O2 UK lollipop ROM via ODIN and got error message on screen. MD5 too big or something. Had to pull battery on phone. Had to then reflash TWRP. Got back into TWRP and tried to do a recovery of the backup I took but phone is stuck at Galaxy note 4 screen. It then shuts down and restarts and gets to the same screen again.
Do I try a different ROM? What can I do?
Thanks
Paul
Click to expand...
Click to collapse
I got it working by flashing the German non branded ROM... Got the error message again but then used a "All samsung recovery.tar" as stated on another post in here and it booted fine eventually... Now on Lollipop. Now time to flash with TWRP.... Again!!!
Please, i need help !
I need help, urgently !
My Note 4 SM-N910C does not work. I can enter the Recovery and the Download Mode. When attempting to install a Custom ROM gives me an error that says I have no data. In the internal memory I have 0mb.
I tried using odin, but I can not .. Salta error.
Someone who can make a backup of your phone (which is factory), leave me a link to download it? So I install the TWRP. Please.
They have another solution?
Thank you.:good:
Hi,
I tried to downgrade my Note 3 with CSC VIA to Kitkat VIA. Downloaded and flashed firmware from Sammobile. Didn't work. failed in ODIN though it finished.
I tried it again and now i can flash Kitkat with ODIN "passed" but I'm stuck in bootloop. Full wipe and cache clean in recovery won't work. Tried it a last time with Kitkat DBT version (debranded) and added a PIT file by Darklord for 1DBT. ODIN says passed but the bootloop still is there. Download mode is still available so i see some real chance to get it done.
Is it possilbe to debrand to DBT that easily or shall I stay on VIA? I never tried the PIT file for DBT with VIA firmware. Anyone has a clue what I might try to get it working again? Ah btw. Recovery and Download seems to be perfectly fine and Knox isn't triggered.
Your input is highly appreciated, thanks in advance!
peety25 said:
Hi,
I tried to downgrade my Note 3 with CSC VIA to Kitkat VIA. Downloaded and flashed firmware from Sammobile. Didn't work. failed in ODIN though it finished.
I tried it again and now i can flash Kitkat with ODIN "passed" but I'm stuck in bootloop. Full wipe and cache clean in recovery won't work. Tried it a last time with Kitkat DBT version (debranded) and added a PIT file by Darklord for 1DBT. ODIN says passed but the bootloop still is there. Download mode is still available so i see some real chance to get it done.
Is it possilbe to debrand to DBT that easily or shall I stay on VIA? I never tried the PIT file for DBT with VIA firmware. Anyone has a clue what I might try to get it working again? Ah btw. Recovery and Download seems to be perfectly fine and Knox isn't triggered.
Your input is highly appreciated, thanks in advance!
Click to expand...
Click to collapse
Try this:
1. Full wipe first (system, data, cache and dalvik)
2. Flash the VIA Kit Kat firmware via ODIN unticking "Autoreboot".
3. Take out the battery and pull in it again when the flashing process finish.
4. Boot in Recovery and make full wipe again.
5. Reboot your device and it should boot normally.
6. Tell me if it worked for ya
Hi,
thanks for you input. I tried it - still the bootloop. So I made a try with the current version (installed before). This works - most likely because I'm unable to clean Dalvik with the standard recovery.
Anyhow in the end I'm not happy with the outcome because of the bluetooth issues of the new version. Anybody has a suggestion how to downgrade sucessfully - I'd happily install a CM12.1 as well but a nightly without installation advice seems to be a bit too much for me.
try flashing MODEM with NON-HLOS, I think you have corrupted the EFS.
peety25 said:
Hi,
thanks for you input. I tried it - still the bootloop. So I made a try with the current version (installed before). This works - most likely because I'm unable to clean Dalvik with the standard recovery.
Anyhow in the end I'm not happy with the outcome because of the bluetooth issues of the new version. Anybody has a suggestion how to downgrade sucessfully - I'd happily install a CM12.1 as well but a nightly without installation advice seems to be a bit too much for me.
Click to expand...
Click to collapse
You can flash TWRP recovery if you don't care about KNOX and follow my steps above :highfive:
So.. hello.
Normally I don't come to forums to get help... but yeah. This is kinda bad.
I've got a little situation here.
I got my new Samsung Galaxy Note 4 (SM-N910F).
It was delivered with Stock 5.1.1.
First try:
I booted to the Downloader, fired up Odin, let it download the Autoroot.
Then I've got a bootloop.
Second try:
Booted into the Downloader, fired up Odin, let it install the 5.0.1 Stock ROM (Ending with 'BOB4')
It booted normally , then two things pop up constantly:
Something like "phone.xxxxxxxx.xxx Service crashed".
and "NFC crashed."
So I can't even unlock that phone.
Third try:
Booted into the Downloader, fired up Odin, let it install "N910FXXU1COI3_DevBase_alexndr".
Ended up in a Bootloop.
Then I tried to install the Bootloader aswell as the Modem and the Kernel, which are also in alexndr's Thread.
Ended up in the same Situation as the second try.
I don't no what to do anymore.
I'd really love to hear some help from you guys.
Greetings,
R3dRacoon
// Edit:
// It is a German Device from Telekom.
// If that helps or makes a little difference.
______________
UTC+1 (If I don't answer instantly)
And yeah, I've used search. And that for like the whole day.
Try Samsung care
R3dRacoon said:
So.. hello.
Normally I don't come to forums to get help... but yeah. This is kinda bad.
I've got a little situation here.
I got my new Samsung Galaxy Note 4 (SM-N910F).
It was delivered with Stock 5.1.1.
First try:
I booted to the Downloader, fired up Odin, let it download the Autoroot.
Then I've got a bootloop.
Second try:
Booted into the Downloader, fired up Odin, let it install the 5.0.1 Stock ROM (Ending with 'BOB4')
It booted normally , then two things pop up constantly:
Something like "phone.xxxxxxxx.xxx Service crashed".
and "NFC crashed."
So I can't even unlock that phone.
Third try:
Booted into the Downloader, fired up Odin, let it install "N910FXXU1COI3_DevBase_alexndr".
Ended up in a Bootloop.
Then I tried to install the Bootloader aswell as the Modem and the Kernel, which are also in alexndr's Thread.
Ended up in the same Situation as the second try.
I don't no what to do anymore.
I'd really love to hear some help from you guys.
Greetings,
R3dRacoon
______________
UTC+1 (If I don't answer instantly)
And yeah, I've used search. And that for like the whole day.
Click to expand...
Click to collapse
The third attempt was incorrect, that file is to be flashed from a custom recovery.
The second try might be because you did a dirty flash (Need to wipe data)
The first attempt boot-looped because in order to root in 5.1.1 you need a rootable kernel and the latest SuperSU (Not CF-Auto root)(Kernel is found in the Android Development thread)
Battlehero said:
The third attempt was incorrect, that file is to be flashed from a custom recovery.
The second try might be because you did a dirty flash (Need to wipe data)
The first attempt boot-looped because in order to root in 5.1.1 you need a rootable kernel and the latest SuperSU (Not CF-Auto root)(Kernel is found in the Android Development thread)
Click to expand...
Click to collapse
Thanks for the response.
What can I do to get a correct working System back? (Theoretically, I got time and bandwidth.)
Since flashing the Stock ROM did not quiet work.
medo sator said:
Try Samsung care
Click to expand...
Click to collapse
KNOX Flag is already 0x1. Means varranty is void, isn't it?
So I don't think they will help me.
R3dRacoon said:
KNOX Flag is already 0x1. Means varranty is void, isn't it?
So I don't think they will help me.
Click to expand...
Click to collapse
ok first flash twrp via odin then flash your 5.0.1 bootloader and modem then boot to recovery and wipe all systems and data then bootinto download mod and flash any custom 5.0.1 rom
medo sator said:
ok first flash twrp via odin then flash your 5.0.1 bootloader and modem then boot to recovery and wipe all systems and data then bootinto download mod and flash any custom 5.0.1 rom
Click to expand...
Click to collapse
I've already tried to flash TWRP via Odin, but I've never seen it.
Flashed recovery was for trltexx.
Getting to Recovery should be the same as getting to Download Mode, or?
Anyways. Will try it with tbltetmo and report back.
// Just installed the tbltetmo.
// Can't see how to get into the recovery.
// Am I missing something?
Update:
Just signed up at sammobile and downloaded the BOB6 (4.4 i think) for T-Mobile.
Flashed via Odin.
Seems like it does work again.
Currently its installing like 260 Apps.
Let's see.
// Edit: Nah. It got even worse.
// But I got a Recovery. So that's something.
IT ****ING WORKS NOW
Went into the recovery and cleared cache and data. (Kinda stupid I did not do it inb4)
Do a clean install in Odin. Since it came with stock android 5.1.1, then flash the 5.1.1 stock firmware in Odin. If you have a locked device of a specific carrier it will be even better to use the firmware made for that carrier only. And check the "Nand erase all" option in odin before hitting the start button to flash. That will erase all the data from ur phone and will do a clean install. Your phone must then boot normally. Also note that android 5.0 root file may not work for 5.1. Also check the model number before flashing.