Hi,
I recently acquired a Note Edge N915G and was going through the rigmarole of finding a rom to suit my eyes and my requirements from the phone. in doing that I rooted the device and flashed micky387 MM rom 1.0 on the device and then tried the noble rom and RR rom too. I wasnt too excited about them so thought of downgrading to lollipop and trying some custom roms on lollipop base. I did that and found the alliance rom and having used their roms on my note 2 and note 3 I was happy to find one for note edge and flashed it after flashing a stock lollipop rom through odin it was N915GXXU1BOBC_N915GODD1BOC1_INS but it did not let alliance rom boot past the startup logo.
After trying different options i thought ill go back to MM as it was a stable rom and flashed stock N915GXXU1DPE1_N915GODD1DPE1_N915GDDU1DPB6_HOME.tar rom and decided to boot it up and see what it is like. I found it okay and installed twrp recovery from odin and then added su through recovery along with sony walkman, dolby atmos and viperfx.
the thing which got me here is that i received notifications of system updates available to me and on accepting them last night got 3-4 updates starting at 350 mb or so and upto 700 mb (Not exact) . My knox was already tripped and showed 4 before this but i got the ota updates and they installed without any issues.
I was always under the impression that rooting takes away the option of ota updates as the device becomes unofficial. I am unable to understand how i could get those updates after i had rooted and tried different roms and then loaded a stock rom through odin. I am also unable to get alliance past the initial boot logo and would appreciate suggestions. i installed stock N915GXXU1BOBC_N915GODD1BOC1_INU before flashing twrp and then Alliance through recovery. it wasnt booting past the first screen and i tried adding the permissive kernel which got it to conme to the alliance logo and it is animated but doesnt go any further.
thanks in advance for all the help and my thanks to xda and the great develo[pers who have given us more than the manufacturers ever could in making our devices as unique as each one of you.
Related
Hi all,
I recently rooted and installed a custom recovery per Jay Dogg's guide in the Galaxy S Relay. Development forum. I kept my stock ROM by choice and recently ready up on the recent Jelly Bean OTA update (MC5). I'd like to update but the official OTA update states you can't be rooted. I downloaded the update via Settings/About phone/update. Upon choosing to update, the phone rebooted to my custom recovery. It stated the certificate on the package was invalid so I backed off and just rebooted. I'm guessing my options are :
- Revert to an unrooted stock ROM, update to 4.2 (MC5) and re-root.
- Attempt to apply the official OTA update via custom recovery despite its complaints of certificate issues.
- Apply a non-stock or ripped ROM (not preferred at this point)
Can someone help me? I would like to avoid the hassle of unrooting, but that's probably my best option as far as I can tell. Any feedback is appreciated. I'm happy with the stock ROM's stability for now and don't really want to deal with the bluetooth / camera issues present builds of custom ROMs have.
Spent the last few weeks trying to get a rom with black backgrounds on my I9505 that still has full camera functionality. Installed slimkat which was fine but the camera barely worked at all so decided to go back to stock 4.4.2 which is where my problems started. Upon doing this I got a message saying I might loose root and did I want to fix it, I said yes and from that time on I have never been able to instal another 4.4.2 system. I am however able to instal stock lollipop.
I suspect this is a knox issue and I have tripped the counter but I have no idea what I could try next as the graviton rom (4.4.2) seems to be my best option for a black background rom still with touchwiz camera stuff. I also find every custom recovery I instal gets over ridden back to the stock recovery and Im constantly reinstalling them.
This is truly driving me around the bend, Could someone point me in the right direction on what the problem is please?
Hi, thank you for using XDA Assist. The Samsung devices usually have qfuses which get "blown" when updating to the latest firmware. This prevents you from downgrading the firmware to earlier versions. I would suggest you follow this to flash the stock firmware in Odin and start over. http://forum.xda-developers.com/showthread.php?p=41072377 You'll have to reinstall your custom recovery, however, you should still be able to flash 4.4.2 custom roms.
Sent from my Nexus 9 using XDA Free mobile app
Thread closed.
I got this s6 back in march or april and it was on 5.0.2 and well now that iv've updated to the OTAS 5.1.1 OFE i was curious about root and i continued with a thread about rooting it and etc
( i kinda regret that now, i shouldve stayed on 5.0.2)
but the main reason i rooted was to recover files and welli did but i installed dr fone on my computer it asked for my phones root permissions so i went ahead and rooted it but after a bit i noticed it started to freeze my phone and after a bit it just stopped working.
i turn it on and restart it i see a blue led cycling and i see the sprint spark screen but it does nothing from there.
and so i stupidly went to to stock recovery, wiped cache, and factory resetting it and now idk what to do
there isnt an OFE stock tar yet so i cant fix this on my own, im just thinking if i flash twrp right now and then flash a custom rom will that work?? for my OFE build
am i able to or should i just download the stock tar 5.0.2 to reflash it or will that just basically brick me completely??
also i did have insurance for this and i thnink i just blew that one too :/
ive noticed mine said this
G920PVPU2BOFE
and not G920PVPU2BOF7
so does that mean im able to use the stock firmware from the website and reflash it or like what do i do...
SO what i did countless of researching
i ended up having the
custom binary blocked by FRP lock, by forgetting to unlock oem before updating the Twisted Projects SuperSu or User since it asked me to updated i ovbiously just went ahead of myself and that happened thus into this Boot Loop Soft
and im flashing with ODIN the stock 5.1.1 OF7 tar its surprisingly working. ( i was originally on the OFE OTA tho.)
unlike the Twisted Project custom roms, kernel and or twrp setup, i couldnt boot into the twrp or even past the android screen, and well the only option i had was just Download Mode.
And this basically saved me.
Very Informative
Ok,,,,here is my plight...
about 6 months ago my s5 became unusable due to the fact that concrete and GS5's dont play well together...becoming more and more frustrated having to use an older phone (HTC ONE M7) i went ahead and threw caution to the wind and bought a new LCD digitizer for my GS5 and hoped for the best...
replaced my digitizer and VIOLA !! my phone booted and was exactly the same as it was the day before concrete and LCD collided..
after booting it up went in to check everything and all seems well....root was still good,,,just had to upgrade everything and move on..
my problem is that since it has been a while there have been so many changes as far as updates,,ROMs,,and other techniques i need to find out the steps to take and what would be my best plan of attack..
i am on MOAR v2.2 NE5 and when i installed that back when i first got the phone tripped KNOX,,but i dont think that is too much of a concern at this point...or is it ??
i have read alot of things about going to Lollipop but am not sure if i need to do anything except find a Firmware and flash it with Kies or if ODIN is a better way to go....it would be great if i were able to just jump right to MM but i know the chances of that happening are <0....
any help would be appreciated
thank you in advance
Well the latest version for this phone currently is Marshmallow, and there is a great mm n5 rom that is still a work in progress, but i reccomend downloading the full marshmallow restore tar file and using odin to update, then flash recovery, and then a rom of your choosing (currently the n5 rom or a version of cm13). But to flash a lollipop rom download the OK4 lollipop restore file (last version of lollipop 5.0) and do the same process.
hadn't heard much so i went ahead and downloaded an OK4 firmware and flashed with ODIN....works flawlessly setting up now
surprisingly enough,,,it kept all of my settings from MOAR.....hafta say that i am shocked.....gotta love Android
So first off I would say I am average in the world of modifications, I know the basics. I used to run a stock Nougat rom with Magisk.
Being the clumsy fool that I am, I dropped my phone and the screen broke. I went to a Samsung service center and deposited my phone there for screen replacement and they decided to update my phone for no reason...
As my phone was rooted, after forcing an update on my phone a soft brick happened and they had to flash a new firmware which meant that I lost everything. Now I am running latest stock Oreo 8.0.
I tried these things to root my phone again:
(The first thing I did was flashing twrp through odin)
#1: Downloaded Magisk and a decryptor for getting past the locked bootloader... flashed them both using recovery (twrp works 100%), and my phone got stuck on the Samsung S7 - powered by android after a reboot from recovery. Waited for a long time. Tried a lot of alternatives on this method but got stuck..
#2 After I gave up on rooting the firmware I was given, I decided to go back on my old Nougat firmware which used to work flawlessly... so I had the nougat firmware on my computer but this time Odin gave me an error along with some red text on top right in download mode. I looked up the error and it basically meant that I cannot revert back to Nougat anymore (which is surprising as I could easily swap between Nougat and Marshmallow but I can't do the same with Oreo and Nougat)
Quote from a person on the internet: ''SW REV CK FAIL usually means that you are not flashing the most current released firmware version. Most Samsung devices will not let you downgrade. You have to flash what was previously installed or higher Android version.''
#3 I was frustrated. I tried using a last resort.. downloaded a custom rom which has root included called ''Galaxy Project''... Flashed it using twrp and got a bootloop for 2 hours. To get past the bootloop I had to download Oreo stock rom and flashed it using Odin. That worked.. I'm back on stock Oreo again... back to square one.
Please help out a stumped Android enthusiast... I have spent 2 days on this... but no solution works. My phone is not in danger of a hard brick as I can always revert to stock Oreo using Odin but having root would be nice.
I am having average experience, I know just the basics... please help me out and tell me what to do in a step by step manner.. I will try everything and report the findings till I finally come across a method which works.
EDIT: My phone model is G930FD
Devansh_Droidgeek! said:
So first off I would say I am average in the world of modifications, I know the basics. I used to run a stock Nougat rom with Magisk.
Being the clumsy fool that I am, I dropped my phone and the screen broke. I went to a Samsung service center and deposited my phone there for screen replacement and they decided to update my phone for no reason...
As my phone was rooted, after forcing an update on my phone a soft brick happened and they had to flash a new firmware which meant that I lost everything. Now I am running latest stock Oreo 8.0.
I tried these things to root my phone again:
(The first thing I did was flashing twrp through odin)
#1: Downloaded Magisk and a decryptor for getting past the locked bootloader... flashed them both using recovery (twrp works 100%), and my phone got stuck on the Samsung S7 - powered by android after a reboot from recovery. Waited for a long time. Tried a lot of alternatives on this method but got stuck..
#2 After I gave up on rooting the firmware I was given, I decided to go back on my old Nougat firmware which used to work flawlessly... so I had the nougat firmware on my computer but this time Odin gave me an error along with some red text on top right in download mode. I looked up the error and it basically meant that I cannot revert back to Nougat anymore (which is surprising as I could easily swap between Nougat and Marshmallow but I can't do the same with Oreo and Nougat)
Quote from a person on the internet: ''SW REV CK FAIL usually means that you are not flashing the most current released firmware version. Most Samsung devices will not let you downgrade. You have to flash what was previously installed or higher Android version.''
#3 I was frustrated. I tried using a last resort.. downloaded a custom rom which has root included called ''Galaxy Project''... Flashed it using twrp and got a bootloop for 2 hours. To get past the bootloop I had to download Oreo stock rom and flashed it using Odin. That worked.. I'm back on stock Oreo again... back to square one.
Please help out a stumped Android enthusiast... I have spent 2 days on this... but no solution works. My phone is not in danger of a hard brick as I can always revert to stock Oreo using Odin but having root would be nice.
I am having average experience, I know just the basics... please help me out and tell me what to do in a step by step manner.. I will try everything and report the findings till I finally come across a method which works.
EDIT: My phone model is G930FD
Click to expand...
Click to collapse
OEM unlocked???
cooltt said:
OEM unlocked???
Click to expand...
Click to collapse
through developer settings? yes
Devansh_Droidgeek! said:
through developer settings? yes
Click to expand...
Click to collapse
follow this guide here