Related
Hi XDA,
Can anyone help?
I upgrade my Android 4.1.2 to 4.4.2 on n8010 using a firmware i find on the samsung updates website.
I flash it with mobile odin pro.
The firmware got installed correctly the only problem is my wifi button is not working.When trying to put it "on" state, it goes back to "off" state
Things that i already tried but failed to activate my wifi:
(Btw those are the solutions proposed on several websites)
1.Factory reset
2.Playing with the wifi button several time
3.Whack the n8010 at the back
4.Playing with wifi .conf file on my android using Total Commander
5.Turn it off for several minutes
6.Turning off everything including my router
I am considering of flashing a rom so that i get my wifi back.
But before i do that can someone help me find a solution to the wifi problem because i dont want to flash a rom??
But in case that the only option can anyone recommed me what roms is best to flash on n8010.
OR Maybe i should sell it since without wifi its useless.
Thanks in advance
righen said:
Hi XDA,
Can anyone help?
I upgrade my Android 4.1.2 to 4.4.2 on n8010 using a firmware i find on the samsung updates website.
I flash it with mobile odin pro.
The firmware got installed correctly the only problem is my wifi button is not working.When trying to put it "on" state, it goes back to "off" state
Things that i already tried but failed to activate my wifi:
(Btw those are the solutions proposed on several websites)
1.Factory reset
2.Playing with the wifi button several time
3.Whack the n8010 at the back
4.Playing with wifi .conf file on my android using Total Commander
5.Turn it off for several minutes
6.Turning off everything including my router
I am considering of flashing a rom so that i get my wifi back.
But before i do that can someone help me find a solution to the wifi problem because i dont want to flash a rom??
But in case that the only option can anyone recommed me what roms is best to flash on n8010.
OR Maybe i should sell it since without wifi its useless.
Thanks in advance
Click to expand...
Click to collapse
You Can instan only by ODIN and PC.
You need the new bootloader in order to have a fully working 4.4.2 version by sammy, and mobile odin doesn't flash it, and like HUNited said you need to use the pc version of odin.
jika23 said:
You need the new bootloader in order to have a fully working 4.4.2 version by sammy, and mobile odin doesn't flash it, and like HUNited said you need to use the pc version of odin.
Click to expand...
Click to collapse
Hi, how do we get new bootloader and how do we replace it?
In my case bootloader is blocked on N8010ZCCMH1, this is china version and makes upgrade over pc odin impossible beside 4.1.2 and when I do the update to 4.4.2 over the mobile odin the WiFi is stuck.I have the exact same issue..
As far I understand, the bootloader is the key.But I was not be able to change it to any european version, any help regarding this issue will be highy helpful.
Thank you.
algebra77 said:
Hi, how do we get new bootloader and how do we replace it?
In my case bootloader is blocked on N8010ZCCMH1, this is china version and makes upgrade over pc odin impossible beside 4.1.2 and when I do the update to 4.4.2 over the mobile odin the WiFi is stuck.I have the exact same issue..
As far I understand, the bootloader is the key.But I was not be able to change it to any european version, any help regarding this issue will be highy helpful.
Thank you.
Click to expand...
Click to collapse
Have you tried the fix within the Gnabo Thread? Maybe it helps ...
Markus.
Sukram2014 said:
Have you tried the fix within the Gnabo Thread? Maybe it helps ...
Markus.
Click to expand...
Click to collapse
I'll give it a try.I see that lot of those who tried 4.4.2 are getting back on 4.1.2.
Is 4.4.2 really so bad?
Hi friends, well basically the problem is I got a friends y GT-I9500 and it bootloops over and over with any ROM other than South Africa Rom 4.2.2 and has invalid baseband. It's a cell from a friend of mine I never new which rom was installed on this phone and as soon as I got it I installed the official stock rom from my country which was KIT KAT rom 4.4.2 tried unbranded ARO version first through ODIN, everything went fine, but it got stuck on bootloop.
These were the things I tried.
- stock recovery (I9500UBUGNG1_I9500UUBGNG1_ARO) --> wiping factory data/reset , ---> wiped cache = Same thing bootlooping
Installed another Stock rom KIT KAT from corresponding Carrier (I9500UBUFNC1_I9500TFGFNC1_UFN) , did :
- stock recovery --> wiping factory data/reset , ---> wiped cache = Same thing bootlooping
Downloaded previous builds of stock rom going back to 4.2.2 , installed stock version of 4.2.2 ARO unbranded (I9500UBUBMG1_I9500TFGBMG1_UFN)
- stock recovery --> wiping factory data/reset , ---> wiped cache = Same thing bootlooping
I also tried installed some custom roms , having flashed Philz recovery and installed from there onwards, no luck as well.
So I came across some threads which said the only possible way of downgrading if I had installed 4.4.2 kit kat , was using a South African ROM 4.2.2. So I tried it and to my surprise the phone booted fine without any problems. Honestly I don't remember if I did flash it with the PIT file and re-partition. But I did work . The only problem once inside the OS itself it showed invalid baseband. I suppose this was due to the EFS partition being changed intially by KIT KAT.
So I'm hoping someone might help me out as to know what else to try, because honestly I'm out of all ideas.
Thanks !
When you went into download mode, what was the product name the phone reported?
Strephon Alkhalikoi said:
When you went into download mode, what was the product name the phone reported?
Click to expand...
Click to collapse
mmm I have to check, what do yo uwant me to see what string? I can put it on downlaod mode again.. and get you a screenshot
Screenshot is fine as it will give me what I need to know.
Strephon Alkhalikoi said:
When you went into download mode, what was the product name the phone reported?
Click to expand...
Click to collapse
screenshot attached , please check
Thanks. I just wanted to be sure you didn't get a Frankenstein phone, as there have been a run of these phones appearing in the last few months. Resellers will take SGH-I337 phones (US AT&T Galaxy S4), slap an I9500 or I9505 IMEI on them, and proceed to add firmware for the I9500/I9505 onto them. When the purchaser gets the device and attempts to update it or customize it, they find they can't, as the AT&T S4 bootloader is locked.
Now that I've gotten the explanation out of the way, you need to do the following. 1) Install Wanam's EFS Backup tool to the S4, run it, and backup the hidden partitions on the device. 2) You're going to again install the latest ROM for your region through Odin, but this time you're also going to add an I9500 PIT file to it. The PIT file should be available for download in the S4 forums here and will tell Odin the correct partition layout of the device. Odin will then install the ROM using that partition layout. With luck, it should correct the issues you've been having.
Should you have an issue with no IMEI or no signal after flashing, flash the modem file, which should also be available on the forums, and don't use the PIT file. If that doesn't work, install EFS Backup again and restore the partitions.
Strephon Alkhalikoi said:
Thanks. I just wanted to be sure you didn't get a Frankenstein phone, as there have been a run of these phones appearing in the last few months. Resellers will take SGH-I337 phones (US AT&T Galaxy S4), slap an I9500 or I9505 IMEI on them, and proceed to add firmware for the I9500/I9505 onto them. When the purchaser gets the device and attempts to update it or customize it, they find they can't, as the AT&T S4 bootloader is locked.
Now that I've gotten the explanation out of the way, you need to do the following. 1) Install Wanam's EFS Backup tool to the S4, run it, and backup the hidden partitions on the device. 2) You're going to again install the latest ROM for your region through Odin, but this time you're also going to add an I9500 PIT file to it. The PIT file should be available for download in the S4 forums here and will tell Odin the correct partition layout of the device. Odin will then install the ROM using that partition layout. With luck, it should correct the issues you've been having.
Should you have an issue with no IMEI or no signal after flashing, flash the modem file, which should also be available on the forums, and don't use the PIT file. If that doesn't work, install EFS Backup again and restore the partitions.
Click to expand...
Click to collapse
Ok , thanks for such a complete explanation. It's always nice when someone with knowledge takes the time to go detail by detail explaining everything. This is the way things have to be done, and explained. Ok so let me get things straight
- Wanams Efs backup , I need to install within a working ROM right? It's not through Philz recovery, What should I backup with EFS backup only EFS?. Something I forgot to tell you was I did change some permissions to see if the invalid baseband got fixed, I changed some owner permissions on the EFS folder, you should know about this.
-Then you want me to install latest ROM should that be KIT KAT right?. Unbranded for my region. Yes I know about the PIT file to repartition, I've already done this and still bootlooped with all the rom variants I tried. The only possible way the phone boots and succeeds is with South African ROM 4.2.2 I've tried all previous roms even choosin the apropiate PIT and still bootlooped.
-The only thing I'm left thinking is all these bootloops have something to do with the modem file, which the South African rom 4.2.2 might have a different modem. Which modem should I install I've read the G versions onwards modified the EFS partition.
- Last, how would EFS backup fix the EFS partition if it's only backing it up, Cause i'm thinking as I've initially when I received the phone installed KIT KAT. IT changed the whole partition scheme of efs.
So now that I've gone through every point, can you clear again the steps sorry if I'm so tedious on reviewing again but I needed to clarify bit by bit.
I must have misunderstood you regarding the IMEI. If it's invalid EFS Backup won't help. Also, if you've already ran the PIT file and still get bootloops, you may have to take the device in for servicing. A service center should be able to fix this without too much trouble. Unfortunately, I can't fathom why only one ROM installs, unless the carrier locked down the device so much that upgrades are impossible.
Perhaps one of the other advanced users or developers have a clue?
Strephon Alkhalikoi said:
I must have misunderstood you regarding the IMEI. If it's invalid EFS Backup won't help. Also, if you've already ran the PIT file and still get bootloops, you may have to take the device in for servicing. A service center should be able to fix this without too much trouble. Unfortunately, I can't fathom why only one ROM installs, unless the carrier locked down the device so much that upgrades are impossible.
Perhaps one of the other advanced users or developers have a clue?
Click to expand...
Click to collapse
Hey so many thanks, honestly I don't know what have been wrong with the device. I'm suspeting this has to do with the modem. Could the modem version on the South africa rom be causing the ROM to install fine. But think of this me first installing KIT KAT and have screwed up the efs and as a consequence the IMEI. My only way would be to install kit kat succesfully as the EFS might have changed. Any advices on this?
The modem isn't likely to cause a bootloop. At worst, it's likely to render the cellular and WiFi services unusable until it's flashed again. Screwing the EFS up is where I believe your problems lie. The EFS partition may well be corrupted, which could cause your bootloop. I really think the only way you'll resolve this is by having someone at Samsung take a look at it. You've repeatedly installed ROMs and have had no luck, so installing a ROM again isn't going to help you here.
Hi,
I flashed the new TWRP2.8.6.0 on my N8000 (before I had 2.8.5.x).
Accidently I flashed the "p4noterf" instead of "n8000" version (with Odin 3.09).
When my SIM-card was not detected, I recognized the error.
Then I flashed TWRP 2.86.0 "n8000"-Version, but SIM was still not recognized.
After that I restored different ROMS (OMNI 5.1; CM12..) from which I had backups, including EFS/IMEI and all other stuff.
Also I wiped (factory, cache, dalvik, system, data) and restored the ROMS again (including EFS...).
But whatever I do: SIM is gone / not detected.
I would be grateful for any help/advice :laugh:!
Me too. I was fiddling with my old 10.1 and decided to give it a run on Lollipop 5.1. I updated the CWM to TWRP and sim recognition was lost. IMEI is blank and mobile network is non existent.
Could any kind soul please advise?
Update: Going back to 4.4.2 stock does show the mobile network signal but there is a notification for SIM card to be inserted. IMEI is back but SIM is still not recognised.
3ftguru said:
Update: Going back to 4.4.2 stock does show the mobile network signal but there is a notification for SIM card to be inserted. IMEI is back but SIM is still not recognised.
Click to expand...
Click to collapse
Perhaps yous can try to restore EFS now (once again) - now that you are back to stock.
There is a thread in a German forum that in 1. step going back to stock saved IMEI. Then, as second step to restore EFS brought SIM back again... Hopefully this helps
Best wishes:good:
Tried using EFS Pro to backup and restore again but it didn't work. Interesting enough, my ROM version stated by EFS Pro is pnote and not N8000. So now downloading and flashing a confirmed N8000 stock rom to see if it works.
Update: Another rom still show p4note which means somewhere in EFS the n8000 is replaced with p4note. Anyone got any idea how to edit back?
3ftguru said:
Update: Another rom still show p4note which means somewhere in EFS the n8000 is replaced with p4note. Anyone got any idea how to edit back?
Click to expand...
Click to collapse
Interesting, indeed.
There's a thread on XDA named "Recover your IMEI in 9 steps". I think it's a description of the problem we are faced with or something very close to, at least.
Unfortunately I am not allowed to post links here :crying: If you PM me I can send it to you.
The logic is the same I found in the German thread: go back to Stock and then change/manipulate EFS.
The crucial file in EFS folder seems to be nv_data.bin perhaps the needed information is in there. There is also a ".bak" and ".md5" of this file.
On my working S3 nv_data.bin changes constantly, date of the file is always "new", not older than a few hours. On the non working N8000 the file date is constant and from early April.
I hope to have some time to explore and test something this weekend .
A further idea might be to (also) go back to n8000 stock recovery - perhaps twrp messed something there.
Again, I can not post the link, just seaarch for the term in www.
Back again!
Hi,
finally SIM is back again :good:
1. Flashed n8000 Stock recovery (probably unnecessary, is inculded in stock rom)
2. Flashed Stock ROM; rather old version (4.1.2) from sammobile: N8000XXCMI2_N8000OXACMI2
2a: Got endless boot loop
3. Booted to stock-recovery --> factory reset (or factory wipe?)
4. Booted to sys and SIM was there :laugh:
Ev. it matters which ROM is chosen, probably older ones (close to production date) are the better choice.
@3ftguru: Hope this will work for you too!
UPDATE: DO NOT USE AUTOMATIC UPDATE (OTA by Samsung) after flashing!
This broke my n8000 again, got an endless "Samsung N8000" Start logo after that.
I could not get into recovery, could not shut it down, only bootload was accessible.
Then I flashed same ROM again with odin - nothing changed.
Finally flashed 4.4.2 - and it's back again - SIM o.k., can get into recovery ... ufffffff!
This is the file I used form sammobile: N8000XXUDNE4_N8000OXADNE4
My device type is listed as p4note and not N8000 anymore even after flashing an old 4.1.2 Samsung ROM. Scratching my head on this one.
Anyone knows how to convert back to n8000 for device type?
Same problem. It brokes after installing TWRP.
---------- Post added at 05:47 PM ---------- Previous post was at 05:46 PM ----------
xd_surfer_g said:
Hi,
finally SIM is back again :good:
1. Flashed n8000 Stock recovery (probably unnecessary, is inculded in stock rom)
2. Flashed Stock ROM; rather old version (4.1.2) from sammobile: N8000XXCMI2_N8000OXACMI2
2a: Got endless boot loop
3. Booted to stock-recovery --> factory reset (or factory wipe?)
4. Booted to sys and SIM was there :laugh:
Ev. it matters which ROM is chosen, probably older ones (close to production date) are the better choice.
@3ftguru: Hope this will work for you too!
UPDATE: DO NOT USE AUTOMATIC UPDATE (OTA by Samsung) after flashing!
This broke my n8000 again, got an endless "Samsung N8000" Start logo after that.
I could not get into recovery, could not shut it down, only bootload was accessible.
Then I flashed same ROM again with odin - nothing changed.
Finally flashed 4.4.2 - and it's back again - SIM o.k., can get into recovery ... ufffffff!
This is the file I used form sammobile: N8000XXUDNE4_N8000OXADNE4
Click to expand...
Click to collapse
So do you use TWRP at old ROM?
Have found solution:
1. Install stock ROM (older) - sim will be working
2. Install TWRP 2.6.3.1
3. Flash something - and sim will be working, too
CyanoFresh said:
Have found solution:
1. Install stock ROM (older) - sim will be working
2. Install TWRP 2.6.3.1
3. Flash something - and sim will be working, too
Click to expand...
Click to collapse
doesnt work for me whether i got use pit to repartition or just a 4.0.4 stock rom to flash. The SIM just doesnt get recognised.
Guess I just have to use it as a N8010 instead.
3ftguru said:
doesnt work for me whether i got use pit to repartition or just a 4.0.4 stock rom to flash. The SIM just doesnt get recognised.
Guess I just have to use it as a N8010 instead.
Click to expand...
Click to collapse
Try this 4.4.2 rom:
Thread (Ukrainian language) - http://www.ex.ua/91621823
direct download - http://www.ex.ua/load/171252309
torrent - http://www.ex.ua/torrent/171252309
Flash N8000XXUDNH2_N8000OXEDNH1_N8000XXUDNH2_HOME.tar.md5 by Odin. Try to factory reset. it should work
Thank you so much for this thread an especially for this posting!!!
I had the same problem, maybe flashed a wrong recovery/firmware/rom or whatever but I lost access to the SIM card in my N8000. After I follow your steps below now I'm back in stock rom with SIM-access and can reconfigure my tablet.
xd_surfer_g said:
Hi,
finally SIM is back again :good:
1. Flashed n8000 Stock recovery (probably unnecessary, is inculded in stock rom)
2. Flashed Stock ROM; rather old version (4.1.2) from sammobile: N8000XXCMI2_N8000OXACMI2
2a: Got endless boot loop
3. Booted to stock-recovery --> factory reset (or factory wipe?)
4. Booted to sys and SIM was there :laugh:
Ev. it matters which ROM is chosen, probably older ones (close to production date) are the better choice.
@3ftguru: Hope this will work for you too!
UPDATE: DO NOT USE AUTOMATIC UPDATE (OTA by Samsung) after flashing!
This broke my n8000 again, got an endless "Samsung N8000" Start logo after that.
I could not get into recovery, could not shut it down, only bootload was accessible.
Then I flashed same ROM again with odin - nothing changed.
Finally flashed 4.4.2 - and it's back again - SIM o.k., can get into recovery ... ufffffff!
This is the file I used form sammobile: N8000XXUDNE4_N8000OXADNE4
Click to expand...
Click to collapse
Tried the Ukrainian ROM but still didn't work.
Now I suspect is that I have accidentally made some changes to the EFS or had damaged the SIM port physically. Otherwise I should have been able to achieve the ROM recognizing the sim card.
Sent from my SM-N910G using Tapatalk
Not working
Sim card comeback after i was reinstall rom 4.4.2, but sim card not working when I install cm12.1 .:crying:
Recovery phone
I thing sim card will working if you recovery phone, file recovery boot with odin:
https:// drive.google.com/file/d/0B_SHfdpTGxm6cHhweGRCR05jYlE/view
After reinstall cm 12.1, 13 for Note 10.1 - N8000.
Good luck.
xd_surfer_g said:
Hi,
finally SIM is back again :good:
1. Flashed n8000 Stock recovery (probably unnecessary, is inculded in stock rom)
2. Flashed Stock ROM; rather old version (4.1.2) from sammobile: N8000XXCMI2_N8000OXACMI2
2a: Got endless boot loop
3. Booted to stock-recovery --> factory reset (or factory wipe?)
4. Booted to sys and SIM was there :laugh:
Ev. it matters which ROM is chosen, probably older ones (close to production date) are the better choice.
@3ftguru: Hope this will work for you too!
UPDATE: DO NOT USE AUTOMATIC UPDATE (OTA by Samsung) after flashing!
This broke my n8000 again, got an endless "Samsung N8000" Start logo after that.
I could not get into recovery, could not shut it down, only bootload was accessible.
Then I flashed same ROM again with odin - nothing changed.
Finally flashed 4.4.2 - and it's back again - SIM o.k., can get into recovery ... ufffffff!
This is the file I used form sammobile: N8000XXUDNE4_N8000OXADNE4
Click to expand...
Click to collapse
Hi there, i had flashed cm12.1 for N8000 and didnt backup efs. So even after returning to stock rom, i couldn't find my SIM. My IMEI was lost, and baseband version was showing unknown. So, can I use your method to restore my IMEI and SIM problem? Please reply fast as I need it within a few days. Thank you.
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.
hey all
I did a basic root on my samsung galaxy s6 a few days ago. just installed superSu and gave me root access. after that I installed TWRP which I then used to try and install the xposed framework. From then on my phone is stuck on the samsung screen saying kernel is not seandroid enforcing. I downloaded the stock rom for my phone (sm-g920F on 6.01) and attempted to flash it via odin 3.07 but it always failed after the sboot.
i have searched to try and find a solution but nothing I can find will work. can anyone help?
so i got my s6 working after flashing a full stock firmware i found via a link on this forum (i forget which one...sorry)
it gave me BL_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
AP_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
CP_G920FXXU3DPB6_CL7086820_QB8569466_REV02_user_low_ship.tar.md5
CSC_BTU_G920FBTU3DPB1_CL7140831_QB8460122_REV02_user_low_ship.tar.md5
it also recommended that I flash the pit file ZEROFLTE_EUR_OPEN.pit.
this was all done via the latest version of odin. initially, the flashing failed at cm.bin so I reflashed omitting the bootloader and all seemed to be well.
My phone set up fine and then I realised that it will not recognise my sim...or any sim for that matter. in settings under sim card status...every entry is listed as unavailable. IMEI is unknown as is baseband version.
i realise that I have obviously messed up big time with the initial flashing (uhuh....backup...backup....backup) but I would really like some help to get my phone back up and running as a ...well...phone.
any help or suggestions would be most appreciated.
thanks in advance x
vickstew2000 said:
so i got my s6 working after flashing a full stock firmware i found via a link on this forum (i forget which one...sorry)
it gave me BL_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
AP_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
CP_G920FXXU3DPB6_CL7086820_QB8569466_REV02_user_low_ship.tar.md5
CSC_BTU_G920FBTU3DPB1_CL7140831_QB8460122_REV02_user_low_ship.tar.md5
it also recommended that I flash the pit file ZEROFLTE_EUR_OPEN.pit.
this was all done via the latest version of odin. initially, the flashing failed at cm.bin so I reflashed omitting the bootloader and all seemed to be well.
My phone set up fine and then I realised that it will not recognise my sim...or any sim for that matter. in settings under sim card status...every entry is listed as unavailable. IMEI is unknown as is baseband version.
i realise that I have obviously messed up big time with the initial flashing (uhuh....backup...backup....backup) but I would really like some help to get my phone back up and running as a ...well...phone.
any help or suggestions would be most appreciated.
thanks in advance x
Click to expand...
Click to collapse
Try smart switch. Not sure if it could restore the imei but it could bring the phone back to original csc when you bought it.
Sent from my SM-G925F
Rosli59564 said:
Try smart switch. Not sure if it could restore the imei but it could bring the phone back to original csc when you bought it.
Sent from my SM-G925F
Click to expand...
Click to collapse
i had tried several times to connect to smart switch but it would not recognise my phone. after a lot of faffing about I finally managed to get it to do an emergency recovery and all seems well so far. it even restored my imei number so thanks for that suggestion Rosli. much appreciated xx
When u install xposed did u ude the special wanam version of the framework
Would say whipe cashe and wait a little while for stock roms like 40 minutes after first time install