I've updated my Note Edge (italian, 100% stock) to Lollipop few days ago, but i really don't like it, i think it's the worst android version i ever used (i hate, a lot, how the lockscreen works now).
Is there any safe (and maybe easy) way to reinstall Kitkat 4.4.4?
i've found this guide searching with Google:
http://androidsigma.com/how-to-downgrade-samsung-note-edge-from-android-lollipop-to-kitkat/
is it ok?
thanks in advance
Goofy-Goober said:
i've found this guide searching with Google:
http://androidsigma.com/how-to-downgrade-samsung-note-edge-from-android-lollipop-to-kitkat/
is it ok?
thanks in advance
Click to expand...
Click to collapse
I did it just the way the guide says, download your official Rom for you phone from sammobile, then use odin, its pretty straight forward, if you get into a bootloop, just wipe cache and it should boot.
MHeat said:
I did it just the way the guide says, download your official Rom for you phone from sammobile, then use odin, its pretty straight forward, if you get into a bootloop, just wipe cache and it should boot.
Click to expand...
Click to collapse
ok, thanks for the reply.
you did the downgrade starting from an original Lollipop rom?
because my phone is non-rooted and 100% stock now, with the Lollipop rom that i received via KIES update.
Goofy-Goober said:
ok, thanks for the reply.
you did the downgrade starting from an original Lollipop rom?
because my phone is non-rooted and 100% stock now, with the Lollipop rom that i received via KIES update.
Click to expand...
Click to collapse
I have the SM-N915T the version from tmobile, but when i bought it from a third party (brand new and unlocked) it did not come with the tmobile rom, it was the one from trinidad and tobago kitkat 4.4.4)
so i downloaded the lollipop Rom for Tmobile, and it worked fine, but i did not like all the bloatware from Tmobile so i decided to go back to kitkat, so i downloaded the kitkat version i had before, downloaded it from sammobile
checked usb debugging in developers settings, then put the phone in download mode, opened odin, click on PDA and selected the kitkat rom i had downloaded from sammobile, everything went fine, after everything completed, remember to wait for the PASS message fro odin, do not disconnect the phone unless it says PASS, after that the phone just boot looped, samsung logo, then samsung logo. So i booted to recovery and cleared cache, after that the phone booted just fine. So basically that is what i did, no problems at all, just make sure you download the Rom for yous specific Edge Model.
i've succesfully downgraded my phone
after the flash with Odin the phone was bootlooping, but with a full wipe (data and cache) everything was ok
now i've disabled automatic firware updates and i'll stick to KK 4.4.4 till Google new updates to Lollipop and the awful head-ups notification system.
thank you very much!
Goofy-Goober said:
i've succesfully downgraded my phone
after the flash with Odin the phone was bootlooping, but with a full wipe (data and cache) everything was ok
now i've disabled automatic firware updates and i'll stick to KK 4.4.4 till Google new updates to Lollipop and the awful head-ups notification system.
thank you very much!
Click to expand...
Click to collapse
Cool man, glad everything went fine.
Hi,
I am having bootloop issue even after I clear with cache and dalvik from the recovery. I flashed with ODIN(N915GXXU1ANK4_N915GOLB1ANK4_MM1.zip) from Lollipop 5.0.1 as mine is Singapore unit. Anyone care to share their experience on how to recover from this.....
yltan said:
Hi,
I am having bootloop issue even after I clear with cache and dalvik from the recovery. I flashed with ODIN(N915GXXU1ANK4_N915GOLB1ANK4_MM1.zip) from Lollipop 5.0.1 as mine is Singapore unit. Anyone care to share their experience on how to recover from this.....
Click to expand...
Click to collapse
This is how i did from lollipop rollback to kitkat CWM > wipe data/factory reset > wipe cache partition > advance > wipe dalvik cache > turn off phone go to download mode > odin start to flash kitkat (SM-N915G Singapore)
The way I recovered this is factory reset instead of clearing the cache. Now running Kit Kat and very much happier...
yltan said:
The way I recovered this is factory reset instead of clearing the cache. Now running Kit Kat and very much happier...
Click to expand...
Click to collapse
Thanks for the suggestion. It worked as I went from Lollipop to Kit Kat. Much happier, especially considering the camera button on the edge panel for both selfie and normal mode. makes life a whole lot easier
I have a Verizon edge but everytime I try to flash back to kitkat with odin, it says it fails. I've tried 2 different files but neither seem to work. Are there any other methods or any other place to get the file from other than sammobile? Lollipop has killed my love for this phone. Maybe I'm doing something wrong. Who knows.
blayzejlm said:
I have a Verizon edge but everytime I try to flash back to kitkat with odin, it says it fails. I've tried 2 different files but neither seem to work. Are there any other methods or any other place to get the file from other than sammobile? Lollipop has killed my love for this phone. Maybe I'm doing something wrong. Who knows.
Click to expand...
Click to collapse
If you know the baseband number of the verizon 4.4.4 Stock ROM, my T Mobile one is N915TUVU1ANK3, you can search for it on https://www.androidfilehost.com/
Downloads much faster with none of that stupid gimmicky pricing.
This phone really shines on Kit Kat. if only Samsung put just a little more effort in maintaining the features of Kit Kat on Lollipop. I really do like the face lift of Lollipop but I'll take the ergonomic Kit Kat that takes full advantage of the Edge any day.
hi guys, im using note edge, sprint N915P, with 5.1.1 but my fingerprint have problem. I would like to downgrade to 4.4.4, is that ok or any suggestion i need to pay attention? I heard that the phone will be null, lost imei if we try to downgrade, is that real? Thanks all
phognle said:
hi guys, im using note edge, sprint N915P, with 5.1.1 but my fingerprint have problem. I would like to downgrade to 4.4.4, is that ok or any suggestion i need to pay attention? I heard that the phone will be null, lost imei if we try to downgrade, is that real? Thanks all
Click to expand...
Click to collapse
Never heard the IMEI thing before. Doesn't even make sense to me. Just download the stock 4.4.4 ROM for sprint via Odin.
Read the above directions In the thread.
edo101 said:
Never heard the IMEI thing before. Doesn't even make sense to me. Just download the stock 4.4.4 ROM for sprint via Odin.
Read the above directions In the thread.
Click to expand...
Click to collapse
Thanks, im dowloading the 4.4.4 Rom and wait for the good result, this is my first time, so nervous.
phognle said:
Thanks, im dowloading the 4.4.4 Rom and wait for the good result, this is my first time, so nervous.
Click to expand...
Click to collapse
i tried but it said fail, my baseband is N915PVPU4COG1, and i downloaded the firmware "N915PVPU1ANK1_N915PSPT1ANK1_XAS" from sammobile. Did i download the correct firmware? Please support. Thanks a lot.
What was the fail message? was it aboot.mbn????
Thanx
Yes thats the failed message I got. I tried the file from 2 different sites.
blayzejlm said:
Yes thats the failed message I got. I tried the file from 2 different sites.
Click to expand...
Click to collapse
Yeah I got the same error message attempting to move from the firmware for SM-N915P (5.1.1.) to SM-N915FY(5.0.1.) though I've seen a few people talk about the fact that you can't go backwards now.
Related
I've noticed there was an update on kies this week (P3113UEBLH1), I'm not sure what it was thought.
I've tried upgrading in kies, it was stuck at 0% downloading then connection timed out.
The OTA update didn't find any updates available.
Then next morning, kies said no update available too.
So, Anyone got the update to work, and if so what changes did you notice?
The update is available for flashing with odin on samsung-updates.com , this is the 2nd 4.0.4 update. (I'm still running the old 4.0.4 (P3113UEBLG5))
I don't have it, but I can look into it...
Bibicp said:
I've noticed there was an update on kies this week (P3113UEBLH1), I'm not sure what it was thought.
I've tried upgrading in kies, it was stuck at 0% downloading then connection timed out.
The OTA update didn't find any updates available.
Then next morning, kies said no update available too.
So, Anyone got the update to work, and if so what changes did you notice?
The update is available for flashing with odin on samsung-updates.com , this is the 2nd 4.0.4 update. (I'm still running the old 4.0.4 (P3113UEBLG5))
Click to expand...
Click to collapse
My device is rooted, and the only backup I made with CWM was after I rooted, if I go to update (if my device can find it) will I:
1) Brick out and be screwed?
2) Have to flash my backup (which is rooted, so would that mean I can't update again?)
3) Be ok and keep my rooting?
4) Be ok, and lose my rooting, and have to re-root?
I realize I am kind of answering your question with a question, but I would be happy to see if I can track it down and see what changes there are, if it's safe to install.
FlynnErik said:
My device is rooted, and the only backup I made with CWM was after I rooted, if I go to update (if my device can find it) will I:
1) Brick out and be screwed?
2) Have to flash my backup (which is rooted, so would that mean I can't update again?)
3) Be ok and keep my rooting?
4) Be ok, and lose my rooting, and have to re-root?
I realize I am kind of answering your question with a question, but I would be happy to see if I can track it down and see what changes there are, if it's safe to install.
Click to expand...
Click to collapse
Try backing up your system using clockworkmod recovery first, then go to download mode, flash your firmware version (download from samfirmware or samsung-updates) and flash it with odin.
This way you're unrooted, running stock rom and stock recovery and then you can install the update.
I didn't try to install an update while rooted, but it's not recommended so don't try.
I did a back up after I rooted with CWM
Bibicp said:
Try backing up your system using clockworkmod recovery first, then go to download mode, flash your firmware version (download from samfirmware or samsung-updates) and flash it with odin.
This way you're unrooted, running stock rom and stock recovery and then you can install the update.
I didn't try to install an update while rooted, but it's not recommended so don't try.
Click to expand...
Click to collapse
So is my backup going to be rooted? Or will it be the stock? I am currently rooted stock 4.0.4.
Btw, I have found no information about the update anywhere on the net. Maybe they accidently did a push to us, and pulled it back?
Should I wipe cache, dalvik and FDR before I flash the firmware from those sites or use the backup I made already? (which I am unsure if I should even use since idk if it will be rooted or not lol)
I wasn't going to update till it was time to get JB, but this update that vanished is intriguing enough I might lol
As i know yes when you restore backup with cwm the result will be rooted also as the cwm takes image of the system when doing backup and as you when doing backup was rooted so when restore this backup you will be still rooted if you flash via odin no need to wipe cash and dalvik cash i never read anyone doing this
Even if you do this wipe no harm at all
Sent from my GT-I9100 using xda app-developers app
As mohamed selim said, but wipe your data and do a factory reset in clockworkmod (after backup)
and why will samsung pull back the update?
There's several reasons why this may happen
Bibicp said:
As mohamed selim said, but wipe your data and do a factory reset in clockworkmod (after backup)
and why will samsung pull back the update?
Click to expand...
Click to collapse
They pushed it out to the wrong devices
They pushed it out to early
They found a last minute bug and had to pull back
They are testing it, and not everyone should have gotten the option to get it.
Ok so to get things straight. If/when we go to JB I will need to download a firmware stock from one of the sites listed above, download it.
Do a backup (just to be safe of what I have now)
FDR/Wipe everything
Install the firmware using Odin
If everything looks good, re-flash CWM
Do another backup so I have a clean stock to revert back to down the road if needed.
That sum it up correctly? This way I can bookmark this thread so I don't forget lol.
**EDIT** When I use Odin to restore stock will I lose CWM? If so, what happens if something goes wrong in the Odin restore and I have a boot loop, or etc, what would be my next move since I won't have CWM to restore previous, would I be able to install it like I would if things were going ok?
Sorry for sounding like a n00b, I am still learning all about this, but I think I am getting closer to learning enough to not be a n00b lol. I only have 10 tabs open with this forum instead of 20!
FlynnErik said:
They pushed it out to the wrong devices
They pushed it out to early
They found a last minute bug and had to pull back
They are testing it, and not everyone should have gotten the option to get it.
Ok so to get things straight. If/when we go to JB I will need to download a firmware stock from one of the sites listed above, download it.
Do a backup (just to be safe of what I have now)
FDR/Wipe everything
Install the firmware using Odin
If everything looks good, re-flash CWM
Do another backup so I have a clean stock to revert back to down the road if needed.
That sum it up correctly? This way I can bookmark this thread so I don't forget lol.
**EDIT** When I use Odin to restore stock will I lose CWM? If so, what happens if something goes wrong in the Odin restore and I have a boot loop, or etc, what would be my next move since I won't have CWM to restore previous, would I be able to install it like I would if things were going ok?
Sorry for sounding like a n00b, I am still learning all about this, but I think I am getting closer to learning enough to not be a n00b lol. I only have 10 tabs open with this forum instead of 20!
Click to expand...
Click to collapse
It's not for the wrong device since it's saying P3113, and it's not jelly bean. as I've seen on samsung firmware.com it's 4.0.4.
Well, on my homescreen I put a shortcut for the software update, it still has a circle saying 'N" on it (which probably stands for new), but going in kies I don't find it, It only says it downloaded it but the firmware is up to date.
So probably either they really pulled it back, or it's a bug and they're fixing it. (I really can't wait for jelly bean)
Second, yes it will erase the CWM recovery and go back to stock recovery.
The common mistake people make to get a bootlop is not wiping data/doing a factory reset before flashing a new ROM, so you should go to recovery and do a factory reset, then go to download mode and flash the firmware with odin. If you ever get stuck in a bootloop, try pressing volume down + power key to get to download mode and re flash the ROM. if it's still stuck, try re-downloading the ROM files you downloaded, it could be corrupted.
Awesome!
Bibicp said:
It's not for the wrong device since it's saying P3113, and it's not jelly bean. as I've seen on samsung firmware.com it's 4.0.4.
Well, on my homescreen I put a shortcut for the software update, it still has a circle saying 'N" on it (which probably stands for new), but going in kies I don't find it, It only says it downloaded it but the firmware is up to date.
So probably either they really pulled it back, or it's a bug and they're fixing it. (I really can't wait for jelly bean)
Second, yes it will erase the CWM recovery and go back to stock recovery.
The common mistake people make to get a bootlop is not wiping data/doing a factory reset before flashing a new ROM, so you should go to recovery and do a factory reset, then go to download mode and flash the firmware with odin. If you ever get stuck in a bootloop, try pressing volume down + power key to get to download mode and re flash the ROM. if it's still stuck, try re-downloading the ROM files you downloaded, it could be corrupted.
Click to expand...
Click to collapse
So the one on the site even though its XAR is us? Can I ask why we have that tag? Not something like US or etc? I mean I don't care, just kinda curious since that would make it more simple to know which region gets what, at least for me it would lol.
Thank you so much for the help and the knowledge, I figured I would end up with stock recovery, which is why I wanted to make sure about what if something goes wrong.
As a side thought, where does the backup that CWM makes located? Can I copy and paste that on to my PC so I always have a back up handy? (I would sync it into the cloud). Can I flash that with odin down the road? Or is that only a CWM usable file?
Any more info on the firmware release?....Trying to download it now!
Firmware Version: P3113UEBLH1
OS: Ice Cream Sandwich
OS Version: v4.0.4
Release Date: 08-10-2012
Build Date: 08-10-2012
Changelist: 999349
Gizmo said:
Any more info on the firmware release?....Trying to download it now!
Firmware Version: P3113UEBLH1
OS: Ice Cream Sandwich
OS Version: v4.0.4
Release Date: 08-10-2012
Build Date: 08-10-2012
Changelist: 999349
Click to expand...
Click to collapse
That's all I know about it, where are you downloading it? samsung updates.com? or kies/OTA update?
Bibicp said:
That's all I know about it, where are you downloading it? samsung updates.com? or kies/OTA update?
Click to expand...
Click to collapse
I found it on some foreign site....samsung-updates.com won't let you download the P3113UEBLH1 firmware, Just the Kernel, I don't use Kies! Uploading it right now!
Gizmo said:
I found it on some foreign site....samsung-updates.com won't let you download the P3113UEBLH1 firmware, Just the Kernel, I don't use Kies! Uploading it right now!
Click to expand...
Click to collapse
Alright, tell me if you notice anything different.
Nice
good!
Im downloading it now. Ill post it when its rooted and deodexed
Bibicp said:
I've noticed there was an update on kies this week (P3113UEBLH1), I'm not sure what it was thought.
I've tried upgrading in kies, it was stuck at 0% downloading then connection timed out.
The OTA update didn't find any updates available.
Then next morning, kies said no update available too.
So, Anyone got the update to work, and if so what changes did you notice?
The update is available for flashing with odin on samsung-updates.com , this is the 2nd 4.0.4 update. (I'm still running the old 4.0.4 (P3113UEBLG5))
Click to expand...
Click to collapse
I tried updating it once with KIES and it got to a point and froze on the screen. I had to force the tablet to shut down and rebooted and the tablet was OK. Being a glutton for punishment I tried again with KIES and the LH1 update successfully updated my GT2 7 and the About screen confirms it. Directly after installing and rebooting I started getting error messages about Chrome crashing. I uninstalled Chrome browser and reinstalled it and all is well. No other problems. Do NOT really notice ANY difference at all.
The only problem I have is that NOW I have decided that I would like to root my GT2 7 and I am NOT sure the methods I see out there will work with the P3113UEBLH1 update.
Does anyone know if my GT2 7 - P3113UEBLH1 can be rooted safely??
grobin
I dont think IT is better than CM9
RomsWell said:
Im downloading it now. Ill post it when its rooted and deodexed
Click to expand...
Click to collapse
Can you please tell me what's different than the older UEBLG5 version? and btw can you upload the stock rom itself without root so I can test it? because I couldn't download :s
EDIT: I downloaded it via samsung-updates.com and flashed it with odin.
It's pretty much the same as UEBLG5 I didn't notice anything different, but I downgraded to UEBLG5 as samsung appears to have pushed back this update (UEBLH1), because when I connect the device to kies, it doesn't recognize it.
Bibicp said:
Can you please tell me what's different than the older UEBLG5 version? and btw can you upload the stock rom itself without root so I can test it? because I couldn't download :s
EDIT: I downloaded it via samsung-updates.com and flashed it with odin.
It's pretty much the same as UEBLG5 I didn't notice anything different, but I downgraded to UEBLG5 as samsung appears to have pushed back this update (UEBLH1), because when I connect the device to kies, it doesn't recognize it.
Click to expand...
Click to collapse
I think it broke wifi. Not sure what the change log says about it. If the Cam is fixed i think im just going to add it to the G5 update. And not bother posting this untill its confrimed OTA
RomsWell said:
I think it broke wifi. Not sure what the change log says about it. If the Cam is fixed i think im just going to add it to the G5 update. And not bother posting this untill its confrimed OTA
Click to expand...
Click to collapse
Sorry for the question, but what do you mean comfirmed OTA? Once kies told me about the UEBLG5 update, I couldn't install it with kies as it was lagging.
Next day I found it on the OTA update.
This one showed on kies for a day, then next day neither kies or the OTA udpates showed there was an update so it probably got pulled back?
Hey guys,
I just got my phone and it updated to 4.4 pretty much out of the box. I still wanted to root so I used a method I found on here (will find if necessary) which is supposed to not trip the KNOX by putting the phone into "Custom Mode." Everything went fine until I tried to use ROM Manager to install CM.
When I boot I get the message "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." I've tried reflashing using Odin, clearing the cache and factory resets, but I get the same error every time.
I'm currently downloading another stock ROM which might work, but I wanted to see if anyone else has had this problem?
Thank you!
mortified21 said:
Hey guys,
I just got my phone and it updated to 4.4 pretty much out of the box. I still wanted to root so I used a method I found on here (will find if necessary) which is supposed to not trip the KNOX by putting the phone into "Custom Mode." Everything went fine until I tried to use ROM Manager to install CM.
When I boot I get the message "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." I've tried reflashing using Odin, clearing the cache and factory resets, but I get the same error every time.
I'm currently downloading another stock ROM which might work, but I wanted to see if anyone else has had this problem?
Thank you!
Click to expand...
Click to collapse
You are permanently stuck on the TW 4.3 OTA because the bootloader is signed with special keys that prevents:
-installing a custom recovery
-flashing custom roms/kernels
-downgrading your software below 4.3
If you can boot into download mode, do this 4.3 soft brick method.
With TW 4.3 OTA, all you can do is root using a tool called: Saferoot.
If you have 4.3 stock firmware you can root and that's it, no custom recovery, no custom rom, kernel, nothing, and just a heads up there are like 10 threads where people don't read and have done what you have, you need to flash the Odin 4.3 image for you phone to work again, never take an ota, enjoy your locked down device now
Sent from my SCH-I535 using XDA Premium 4 mobile app
SlimSnoopOS said:
You are permanently stuck on the TW 4.3 OTA because the bootloader is signed with special keys that prevents:
-installing a custom recovery
-flashing custom roms/kernels
-downgrading your software below 4.3
If you can boot into download mode, do this 4.3 soft brick method.
With TW 4.3 OTA, all you can do is root using a tool called: Saferoot.
Click to expand...
Click to collapse
Worked perfectly! Thank you so much!
mortified21 said:
Worked perfectly! Thank you so much!
Click to expand...
Click to collapse
My pleasure but all the thanks is owed to ThePagel, make sure to post your success in his thread. The more people that report their success with that method, then the less fear someone else may have in using that should they suffer the same experiences. :victory::good::good:
If you need any updates on the state of TW 4.3 then keep this discussion thread bookmarked.
I did the same thing today. The 4.3 update installed by itself!!! So i rooted it using Saferoot,
i installed rom manager, clicked the Install rom from sd card and i got that message. it will repeat that message and it wont boot. So i went into Odin mode and hit the volume down button to restart it. And after that it booted normally.
So basically i am stuck with 4.3? and is there 4.4 out for our phones yet?
also forgot to mention, it says my OS is custom when i first realized it updated.
AURMEND said:
I did the same thing today. The 4.3 update installed by itself!!! So i rooted it using Saferoot,
i installed rom manager, clicked the Install rom from sd card and i got that message. it will repeat that message and it wont boot. So i went into Odin mode and hit the volume down button to restart it. And after that it booted normally.
So basically i am stuck with 4.3? and is there 4.4 out for our phones yet?
also forgot to mention, it says my OS is custom when i first realized it updated.
Click to expand...
Click to collapse
Once you successfully updated with 4.3, you stuck with 4.3, there is no going back or flash anything and 4.3 is the latest factory rom for now. There's no 4.4 yet for our phone. There is custom 4.4 but only for people who didn't take the 4.3 update. Since they still have unlocked bootloader so they could load any custom rom.
buhohitr said:
Once you successfully updated with 4.3, you stuck with 4.3, there is no going back or flash anything and 4.3 is the latest factory rom for now. There's no 4.4 yet for our phone. There is custom 4.4 but only for people who didn't take the 4.3 update. Since they still have unlocked bootloader so they could load any custom rom.
Click to expand...
Click to collapse
Dang this sucks. I have no idea how it installed automatically then. I was listening to music the whole time. And I was trying to get a custom 4.4 after the update...
AURMEND said:
Dang this sucks. I have no idea how it installed automatically then. I was listening to music the whole time. And I was trying to get a custom 4.4 after the update...
Click to expand...
Click to collapse
Yep! sucks big time!!
Is there someone managed to do it. I already read a lot of post regarding downgrading to 4.4.4, some says theres no chance to downgrade if you upgraded OTA but some managed to downgrade. So can really downgrade back to 4.4.4?? I'm really confused right now. Lollipop on my device has a lot of issues. Battery drains much faster even on idle mode it sucks up my battery. Game run much lagger than before. Already did factory wipe and clear cache 3x. I never experienced this when i was on Kitkat 4.4.4 and i really want to downgrade.. many of the user who tried to downgrade (Note Edge) have their phone soft bricked due to bootloader or something..
So is there a possibility that i can downgrade back to 4.4.4?? Thanks!
I was able to do it on my T Mobile Edge. I downgraded by following these instructions http://androidsigma.com/how-to-downgrade-samsung-note-edge-from-android-lollipop-to-kitkat/
I didn't use Sammobile though because they want me to pay to be able to download stock ROMs that should be free so I googled the PDA of the stock T Mobile ROM and downloaded it from https://www.androidfilehost.com
I got a boot loop but I fixed it by booting into Samsung recovery mode (stock normal one) and doing a cache wipe and a hard reset.
Hi! Thanks for your reply.. Actually i already read that sites(Downgrade guide) but the comments on that link prevent me from doing the downgrade because almost all who commented on that site had their edge bricked..
Bought mine at Singapore.. can i also used that T mobile ROM?? thats a stock ROM right?
You can stop the soft brick by doing a hardware reset which you need to do anyway after every OTA update. You can do the reset off of the stock Samsung recovery
And yes that is Stock T Mobile ROM. What model is your Note Edge? T Moble ROMs normally work on most versions
Mine is SM-N915G..
I already downloaded the stock FW here: http://www.sammobile.com/firmwares/confirm/38097/N915GXXU1ANJ5_N915GOLB1ANJ3_XSP/
inside the zip folder contain N915GXXU1ANJ5_N915GOLB1ANJ3_N915GXXU1ANJ3_HOME.tar.md5 file.... thats all i need right??
In the Odin.. did u enable the Auto Reboot and F. Reset Time??
Hard Reset means factory reset right?
Thanks.. you're my only hope now hahaha...
Will downgrade today. Wish me luck!
It'll work . Just make sure to do a recovery factory reset.
Thanks for your assistance! Managed to downgrade my unit back to kitkat 4.4.4... is there a way to disbble OTA witthout root.. its kinda irritating! It just stays at the in the notfication bar...
Btw, my games run my smoother now!!! Games especially emulator for NDS, PSX, Nintendo GC arent optimized on lolliopop.. But on Kitkat, it runs very smooth
I think you can do that through software updates settings on about phone section. Glad to see it worked. Told you it would. Sometimes you just gotta take risk. It was scary for me too but I just had this confidence I'd tweak my way out of it if I bricked my phone.
A while back i managed to root my Canadian s6 (g920w8) using ping pong root? An app I downloaded from google playstore.. I used root checker and it looks good.. I am rooted.
Do now I'd like to put custom firmware on to get rid of all the crap that comes with this phone.. it is so damn slow its driving me crazy!
Any help is greatly appreciated. Thanks.
1roddy said:
A while back i managed to root my Canadian s6 (g920w8) using ping pong root? An app I downloaded from google playstore.. I used root checker and it looks good.. I am rooted.
Do now I'd like to put custom firmware on to get rid of all the crap that comes with this phone.. it is so damn slow its driving me crazy!
Any help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
Anyone?
There is a few things u can do. Custom ROM and Kernel and recovery. Which I prefer to do. If you just want to remove the bloat download titanium backup
What are you looking for in a Rom? Better ?? Better ?? More memory and performance?
Sent from my SM-G920F using Tapatalk
Well its taken me awhile but ive got time to do some time finally.. i put alliance rom on the phone but when i tried to make a phone call the was no sound on either end of the conversation.. is this a kernal issue?
think this is the best rom arround here alexis rom best battery ad performans
https://forum.xda-developers.com/galaxy-s6/development/alexis-rom-1-0-feel-game-sound-01-04-t3349944
Just tried the Alexis Rom and same thing.. stuck on boot. I reinstalled Alliance hoping for diffrent results.. can text message but no audio during a calls.. ugh! Back to stock again lol..
Provider - Telus
S6 920w8
Stock Android version - 5.0.2
Stock Kernal 3.10.61-4808800
I am using TWRP v2.8.6.0 and am wondering if the version or kernal may have anything to do with getting stuck on boot with almost every ROM i've tried to install..
My procedure when installing a custom ROM is to do a factory reset from TWRP (i dont do data or format because there is no sd card slot to store my rom or backup image), install ROM, clear cache/divik, reboot to system.
Any Ideas??
1roddy said:
Just tried the Alexis Rom and same thing.. stuck on boot. I reinstalled Alliance hoping for diffrent results.. can text message but no audio during a calls.. ugh! Back to stock again lol..
Provider - Telus
S6 920w8
Stock Android version - 5.0.2
Stock Kernal 3.10.61-4808800
I am using TWRP v2.8.6.0 and am wondering if the version or kernal may have anything to do with getting stuck on boot with almost every ROM i've tried to install..
My procedure when installing a custom ROM is to do a factory reset from TWRP (i dont do data or format because there is no sd card slot to store my rom or backup image), install ROM, clear cache/divik, reboot to system.
Any Ideas??
Click to expand...
Click to collapse
Reflash any ROM giving you sound issues and then flash either hacker kernel or arter kernel as they are the only two compatible as far as I know. Once you have flashed arter kernel and then rebooted your phone. Reboot your phone back into recovery once more and then flash this https://drive.google.com/file/d/0B4Gyz91x5k7gc2NBS2N5TFQwY0k/view?usp=drivesdk it is the call audio fix for our devices (925T / 925W8)
(920T / 920W8)
Just make sure you DO NOT FLASH THIS BEFORE DEVICE REBOOT AFTER FLASHING CUSTOM KERNEL. Or you will get into a bootloop and say this doesn't work. (Your system needs to build with kernel settings first)
Here's a step by step I hope helps.
1. Flash custom ROM
2. Flash custom kernel
3. REBOOT
4. Set up ROM.
5. Reboot into recovery.
6. Flash call fix.
7. REBOOT
8. Profit.
Hope it helps you and welcome to making your phone truly yours.
---------- Post added at 01:46 PM ---------- Previous post was at 01:39 PM ----------
Another reason why you are not booting is because you are on 5.0.1
You will have to update the bootloader to MM 6.0 first in order to use 6.0 custom ROMs this can be achieved by flashing any of our latest Canadian firmwares. (Does not matter what company if you are changing FW after.)
ALSO you can use the advanced wipe settings on TWRP to wipe everything but 'internal storage' that is where the ROM is downloaded.
I had alot of issues installing custom ROM's.. so i decided to upgrade and install OEM marshmallow 6.0.1 then re-root my phone. It worked.. I'm running Griffin ROM atm but will play around with other roms now that i have a good idea of where i went wrong.
1roddy said:
I had alot of issues installing custom ROM's.. so i decided to upgrade and install OEM marshmallow 6.0.1 then re-root my phone. It worked.. I'm running Griffin ROM atm but will play around with other roms now that i have a good idea of where i went wrong.
Click to expand...
Click to collapse
Griffin is great, I'm also using the latest version.
christopherrrg said:
Griffin is great, I'm also using the latest version.
Click to expand...
Click to collapse
Do you have any trouble sending MMS? Mine seem to hang until they fail..
1roddy said:
Do you have any trouble sending MMS? Mine seem to hang until they fail..
Click to expand...
Click to collapse
I do not. However I always have mobile data running, maybe toggle yours and see if it sends. Some of the new ROMS have incorporated a tweak that auto toggles data to recieve pictures and send them. Griffin AFAIK does not have this tweak yet so when sending MMS you need to manually turn mobile data on and off.
christopherrrg said:
I do not. However I always have mobile data running, maybe toggle yours and see if it sends. Some of the new ROMS have incorporated a tweak that auto toggles data to recieve pictures and send them. Griffin AFAIK does not have this tweak yet so when sending MMS you need to manually turn mobile data on and off.
Click to expand...
Click to collapse
I did another wipe and clean install.. it took care of the problem.. looking for a new kernal now so i can get private mode working.
1roddy said:
I did another wipe and clean install.. it took care of the problem.. looking for a new kernal now so i can get private mode working.
Click to expand...
Click to collapse
Private mode?
Like in the browser? Or in the actual software?
I've never used it before so I've never hunted it down.
(Asking because I shall)
christopherrrg said:
Private mode?
Like in the browser? Or in the actual software?
I've never used it before so I've never hunted it down.
(Asking because I shall)
Click to expand...
Click to collapse
Private mode in setings---> privacy---> private mode. I read somewhere a kernal will fix it.. i'll play around with that later!
Hi guys,
for some reason after I did update to KangVIP I can't get rid off it. Besides I got no wifi and bt and I was going to start over with b023 as suggested but at this point I wont bother anymore.
I did wipe the system, I did advanced wipe using twrp but no matter what I do none of the stock firmwares are going through however the Kanga one always goes through.(KangaVIP goes through only in TWRP)
twrp 2.8.7.0
wipe
advanced wipe
I select all the partitions
mkdosfs process ended with error=1
unable to wipe /usb
unknown mtp message type: 1
unable to wipe /usb
I go back, restart to fastboot, (device is saying there is no OS installed), I restore the recovery, create dload folder on my sdcard, put there 028 (actually I tried all of them already), volume+ volume - power and I get error.
What am I missing ?
Anyone can help ?
Thanks in advance.
Eric
First you did a OTA from B029 to B209?
If so you are now on a Android 6 ROM you cant go back to Android 5 without a Rollback from Huawei.
Hirs_E_Fruit said:
First you did a OTA from B029 to B209?
If so you are now on a Android 6 ROM you cant go back to Android 5 without a Rollback from Huawei.
Click to expand...
Click to collapse
Yes I did then I wiped everything and started with b028 again.
Same thing, wifi didn't work same with BT.
Wipe again and this time I did local update and since the local update I can't go back not even b029.
77Eric77 said:
Yes I did then I wiped everything and started with b028 again.
Same thing, wifi didn't work same with BT.
Wipe again and this time I did local update and since the local update I can't go back not even b029.
Click to expand...
Click to collapse
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Hirs_E_Fruit said:
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Click to expand...
Click to collapse
I'm stuck on 6.0
I know I can do force update on 5.0 I said it above I just can't do it with 6.0 -> b029, only with your rom.
Anyone else is having this issue ?
The Kanga rom got a quite few problems no wifi and not BT, Google play services crashing (this can be fixed with gapps) my co worker just tried it with his own methods and same issue. After I went through the whole Kanga thread 60% of the posters got problems most of them are ignored.
I don't have any problems but I think the people with problems are people who have a DAV 701L.
Hirs_E_Fruit said:
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Click to expand...
Click to collapse
Hirs_E_Fruit said:
I don't have any problems but I think the people with problems are people who have a DAV 701L.
Click to expand...
Click to collapse
I got DAV-703L, just simple question, why is the wifi and bt not working ?
When I get into Kanga I can remove the root or deny access to it is there a way to ditch it ?
Yeah I know it's working for you and it's not working for 10 other people including 703L owners. There is something wrong with the rom no doubt about it.
77Eric77 said:
I got DAV-703L, just simple question, why is the wifi and bt not working ?
When I get into Kanga I can remove the root or deny access to it is there a way to ditch it ?
Yeah I know it's working for you and it's not working for 10 other people including 703L owners. There is something wrong with the rom no doubt about it.
Click to expand...
Click to collapse
I think there was an error while flashing and without a full clean Rom flash i can't see a solution.
Before I got it to work I flashed it more than 3 times and everytime everything worked so I think don't think the ROM is that bugged.
Hirs_E_Fruit said:
I think there was an error while flashing and without a full clean Rom flash i can't see a solution.
Before I got it to work I flashed it more than 3 times and everytime everything worked so I think don't think the ROM is that bugged.
Click to expand...
Click to collapse
The first rom you introduced is working "fine" I get the wifi and bt no problem but once I switch into the latest build it's gone.
Any idea where can I get full clean Rom ?
This one is a no go http://www.needrom.com/download/p8max-dav-703l/
I managed to rollback to 5.1.1 but when I try to force flash it, it says it's not compatible.
If you don't update properly to B209, when you flash any B209 rom you are going to run into issues such as the wireless Bluetooth and sim card switching for some. If you properly updated the dload method should have completed successfully. Look at the kernel and radio version of B209 in About phone and compare it to others and see if they match.
ajsmsg78 said:
If you don't update properly to B209, when you flash any B209 rom you are going to run into issues such as the wireless Bluetooth and sim card switching for some. If you properly updated the dload method should have completed successfully. Look at the kernel and radio version of B209 in About phone and compare it to others and see if they match.
Click to expand...
Click to collapse
I don't want to use your rom even if you removed the Chinese it's still inside the system. Boot load times take much longer. Unexpected crashes. I did try it on 4 phones with OTA and local updates 2 are working but the Kang does crash twice a day minimum.
All what I'm asking is how to restore it to it's original settings, this was my worst mistake ever.
What I'm trying to say if I do something I do it properly just look at your thread 85% failure ratio that doesn't look like it was done properly does it ?
77Eric77 said:
I don't want to use your rom even if you removed the Chinese it's still inside the system. Boot load times take much longer. Unexpected crashes. I did try it on 4 phones with OTA and local updates 2 are working but the Kang does crash twice a day minimum.
All what I'm asking is how to restore it to it's original settings, this was my worst mistake ever.
What I'm trying to say if I do something I do it properly just look at your thread 85% failure ratio that doesn't look like it was done properly does it ?
Click to expand...
Click to collapse
Really dude?? No worries, it will be the last time I do anything for the P8Max. Maybe you should just sell the phone since you're having all sorts of issues with it....or maybe you should have left it totally stock then. Or maybe read through the Mediapad X2 forums because the two phones are very similar.