Related
Dear all,
Well I dont know where to start. But here is what happened with my N7100 Note 2.
I was on the latest 4.4.2, the phone restarted suddenly one day and it just dont boot stuck at samsung logo,
flashed the 4.4.2 stock from sammobile. and it worked fine everything was perfect for a week, till it happened again
flashed the same rom. and here is where the trouble begins.
The IMEI changed to generic 00499XXX.., Serial No: 000000
i managed to downgrade to 4.1.2 with mobile odin, flashed a lot of stocks and customs as well. And after a very hard work for a week i manage to get back my IMEI and serial number back, now I backed up my EFS learned my lesson
Now i flashed the stock rom 4.1.1, phone is unlocked. cant make calls, or sms or data internet.
Now I have service: out of service, Bluetooth address: unavailable (while its in the efs folder the mac is in the file), Device status modified, And when I connect it to USB it wont recognize the phone until I have to dial *#7284# and change USB from modem to PDA, then save and reset. (EVERYTIME) I need a permanent fix as well for that.
Please I need help with those as i cant make my phone work.
Thanks and regards,
Mohamed Selim.
First and most important:
If you ever were on stock 4.4.x you can't downgrade to 4.1.x because of knoxed bootloader.
What you did with mobile odin was no real downgrade cause your bootloader wasn't touched.
Don't try to flash firmware beyond your current bootloader version.
Install Samsung Phone Info app from play store and look for actual bootloader version.
Androidwizzard said:
First and most important:
If you ever were on stock 4.4.x you can't downgrade to 4.1.x because of knoxed bootloader.
What you did with mobile odin was no real downgrade cause your bootloader wasn't touched.
Don't try to flash firmware beyond your current bootloader version.
Install Samsung Phone Info app from play store and look for actual bootloader version.
Click to expand...
Click to collapse
Well It actually did downgrade to 4.1.2 with Mobile odin and I checked the version and Baseband and everything it was the 4.1.2
Now I am on 4.1.1 stock. rooted and trying to figure out what to do now
onix17_5 said:
Well It actually did downgrade to 4.1.2 with Mobile odin and I checked the version and Baseband and everything it was the 4.1.2
Now I am on 4.1.1 stock. rooted and trying to figure out what to do now
Click to expand...
Click to collapse
As I said before: YOU DID NOT DOWNGRADE firmware to 4.1.2 with Mobile Odin, check with Info app from Samsung:
You will find bootloader between *ND3 and *NI1 and all are 4.4.2 KitKat
So, whatever firmware you try to flash under 4.4.2 is supposed to fail.
Androidwizzard said:
As I said before: YOU DID NOT DOWNGRADE firmware to 4.1.2 with Mobile Odin, check with Info app from Samsung:
You will find bootloader between *ND3 and *NI1 and all are 4.4.2 KitKat
So, whatever firmware you try to flash under 4.4.2 is supposed to fail.
Click to expand...
Click to collapse
I am not trying to argue here, And yes I do agree with you, it failed with i tried to downgrade with windows odin all the time, but acutally never failed with mobile-odin pro latest version. you dont have to believe me, I wont lie to you. I just need a solution for the problem im having now.
Thanks.
onix17_5 said:
I am not trying to argue here, And yes I do agree with you, it failed with i tried to downgrade with windows odin all the time, but acutally never failed with mobile-odin pro latest version. you dont have to believe me, I wont lie to you. I just need a solution for the problem im having now.
Thanks.
Click to expand...
Click to collapse
Mobile Odin does everything but doesn't flash bootloader so it is like flashing a custom rom which also doesn't contain bootloader.
PC Odin flashes complete firmware, so this is the only way to really up- or downgrade. Hope you understand the difference.
The only solution I see for you is to concentrate on 4.4.2 equal or up your actual bootloader version.
Androidwizzard said:
Mobile Odin does everything but doesn't flash bootloader so it is like flashing a custom rom which also doesn't contain bootloader.
PC Odin flashes complete firmware, so this is the only way to really up- or downgrade. Hope you understand the difference.
The only solution I see for you is to concentrate on 4.4.2 equal or up your actual bootloader version.
Click to expand...
Click to collapse
I do Understand the difference, and thanks for explaining more.
But I attached About my device
But any way beside all this points, I need to fix all the problems I am having either im on 4.1.1 or 4.4.2
Thanks.
onix17_5 said:
I do Understand the difference, and thanks for explaining more.
But I attached About my device
But any way beside all this points, I need to fix all the problems I am having either im on 4.1.1 or 4.4.2
Thanks.
Click to expand...
Click to collapse
I really want to help you out and I assure you that I know what I am talking about (take a look into my signature with stock roms and bootloaders).
There is indeed no solution on 4.1.1 and the screenshot doesn't show bootloader version. To believe what I say try to find out what BL version you are on. If it shows XXUFND3 up to XXUFNI1 you have the proof.
Androidwizzard said:
I really want to help you out and I assure you that I know what I am talking about (take a look into my signature with stock roms and bootloaders).
There is indeed no solution on 4.1.1 and the screenshot doesn't show bootloader version. To believe what I say try to find out what BL version you are on. If it shows XXUFND3 up to XXUFNI1 you have the proof.
Click to expand...
Click to collapse
kay my Bootloader is: N7100XXUFND4. Android Version: 4.1.1, you are right, I kinda understand what you were talking about now.
So now im all ears, Please help me solve my problems.
onix17_5 said:
Okay my Bootloader is: N7100XXUFND4. Android Version: 4.1.1
Well now how can I solve my problems, All ears
Click to expand...
Click to collapse
XXUFND3 was the first KitKat firmware for N7100 and yours was the second.
Three options:
1) Flash firmware using PC Odin at least ND4, maybe better NE1 or up
2) Flash through recovery any stock KitKat custom rom provided by wesamothman, cosmyndemeter or me
3) Flash through recovery any KitKat custom rom you like from development section here
4.3 custom roms may work also, but not 100% sure.
Beyond 4.3 I wouldn't recommend.
Androidwizzard said:
XXUFND3 was the first KitKat firmware for N7100 and yours was the second.
Three options:
1) Flash firmware using PC Odin at least ND4, maybe better NE1 or up
2) Flash through recovery any stock KitKat custom rom provided by wesamothman, cosmyndemeter or me
3) Flash through recovery any KitKat custom rom you like from development section here
4.3 custom roms may work also, but not 100% sure.
Beyond 4.3 I wouldn't recommend.
Click to expand...
Click to collapse
Okay, I will flash a stock Kitkat custom rom provided by you, Can you please require one for me. And I will flash it through recovery now.
onix17_5 said:
Okay, I will flash a stock Kitkat custom rom provided by you, Can you please require one for me. And I will flash it through recovery now.
Click to expand...
Click to collapse
Best and fastest one is XXUFNI1, NH2 and NG3 aren't bad either.
Do a clean installation (factory reset) and after setup device go back into recovery to flash SuperSu.zip.:highfive:
Androidwizzard said:
Best and fastest one is XXUFNI1, NH2 and NG3 aren't bad either.
Do a clean installation (factory reset) and after setup device go back into recovery to flash SuperSu.zip.:highfive:
Click to expand...
Click to collapse
Okay I staterd the download for XDA_XXUFNI1.zip and the BL NH2.
I think I got it, no BL just the XDA_XXUFNI1.zip and clean install it
Okay will be back when im done
onix17_5 said:
Okay I staterd the download for XDA_XXUFNI1.zip and the BL NH2.
should I flash the NH2 with odin after the rom? , or just the Rom without the NH2?
Click to expand...
Click to collapse
No need to flash BL cause you already have KitKat BL
Androidwizzard said:
XXUFND3 was the first KitKat firmware for N7100 and yours was the second.
Three options:
1) Flash firmware using PC Odin at least ND4, maybe better NE1 or up
2) Flash through recovery any stock KitKat custom rom provided by wesamothman, cosmyndemeter or me
3) Flash through recovery any KitKat custom rom you like from development section here
4.3 custom roms may work also, but not 100% sure.
Beyond 4.3 I wouldn't recommend.
Click to expand...
Click to collapse
Okay im done with this part flashed and step up, and installed superU.
So what next
onix17_5 said:
Okay im done with this part flashed and step up, and installed superU.
So what next
Click to expand...
Click to collapse
After reboot everything should be fine: Stable, rooted, fast, right?
Androidwizzard said:
After reboot everything should be fine: Stable, rooted, fast, right?
Click to expand...
Click to collapse
Yes rooted fast everything is stable, but all the problems I said in the first post still there
onix17_5 said:
Yes rooted fast everything is stable, but all the problems I said in the first post still there
Click to expand...
Click to collapse
You mean really everything
out of service,
Bluetooth address: unavailable
Device status modified -> that's ok
USB doesn't recognize the phone
Androidwizzard said:
You mean really everything
out of service,
Bluetooth address: unavailable
Device status modified -> that's ok
USB doesn't recognize the phone
Click to expand...
Click to collapse
Yes still out of service
Bluetooth address: unavaliable
USB doesnt recognize the phone until i have to do *#7284# and change USB to PDA, this its okay but once i restarted the phone I have to do it again save and reset.
onix17_5 said:
Yes still out of service
Bluetooth address: unavaliable
USB doesnt recognize the phone until i have to do *#7284# and change USB to PDA, this its okay but once i restarted the phone I have to do it again save and reset.
Click to expand...
Click to collapse
Ok, last one is driver related to your PC (Mac or Windows?), are you running Kies?
For BT I found this APP
For the first issue I think about IMEI lost, pls check
Hi,
I am running CYanogenMod 13.0-20360525 UNOFFICIAL tritevzw
Baseband N910VVRU2CPJ2
Build Number: ANdroid 6.0.1 MOB30JN910VVRU2BPA1
Whenever I go into settings and click on "Security" I get a popup box that says"
"Unfortunately Settings has stopped"
To try to fix this I have gone into recovery and wiped dalvik and caches.
Thanks for any help!
plainbum said:
Hi,
I am running CYanogenMod 13.0-20360525 UNOFFICIAL tritevzw
Baseband N910VVRU2CPJ2
Build Number: ANdroid 6.0.1 MOB30JN910VVRU2BPA1
Whenever I go into settings and click on "Security" I get a popup box that says"
"Unfortunately Settings has stopped"
To try to fix this I have gone into recovery and wiped dalvik and caches.
Thanks for any help!
Click to expand...
Click to collapse
What build of CM13 did you flash? Your build number says BPA1, but it should be saying CPF3.
quinciebee said:
What build of CM13 did you flash? Your build number says BPA1, but it should be saying CPF3.
Click to expand...
Click to collapse
Hi quinciebee, thanks fo ryour reply.
I was on ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 and firmware BPA1
Then I wanted to try out Hsbadr's new 7.1.1 Nougat Rom and it required new CPJ2 firmware so I odin'd it in.
I TWRP backed up my ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 build I have been running for months.
Then flashed his newest "EmotionOS" But could not get 4G LTE to work so I restored my 6.0 backup since I cant function on 3G only and no one in these forums was able to help me.
Hope that wasn't too confusing
Oh by the way, I am doing this on a Developer Edition Note 4 on Verizon
When I flashed CPJ2 firmware I used a partial build as explained here:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
He quotes:
Quote:
"If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:
N910VVRU2CPJ2_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2."
plainbum said:
Hi quinciebee, thanks fo ryour reply.
I was on ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 and firmware BPA1
Then I wanted to try out Hsbadr's new 7.1.1 Nougat Rom and it required new CPJ2 firmware so I odin'd it in.
I TWRP backed up my ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 build I have been running for months.
Then flashed his newest "EmotionOS" But could not get 4G LTE to work so I restored my 6.0 backup since I cant function on 3G only and no one in these forums was able to help me.
Hope that wasn't too confusing
Oh by the way, I am doing this on a Developer Edition Note 4 on Verizon
When I flashed CPJ2 firmware I used a partial build as explained here:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
He quotes:
Quote:
"If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:
N910VVRU2CPJ2_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2."
Click to expand...
Click to collapse
How did you flash CM13, and did you flash the 09/19 build?
quinciebee said:
How did you flash CM13, and did you flash the 09/19 build?
Click to expand...
Click to collapse
The build date is May 25 2016
Here is a list of roms of that ilk
https://forum.xda-developers.com/devdb/project/?id=12650#downloads
plainbum said:
The build date is May 25 2016
Here is a list of roms of that ilk
https://forum.xda-developers.com/devdb/project/?id=12650#downloads
Click to expand...
Click to collapse
Then I think that's the problem, you'll have to clean flash the 09/19 build.
Delete
quinciebee said:
Then I think that's the problem, you'll have to clean flash the 09/19 build.
Click to expand...
Click to collapse
I flashed to 09/19 build the phone would not boot. I kept getting a rapid glow behind the Blue android mascot.
I then tried to odin the BOG5 firmware and I got errors . rebooted the phone and it wouldnt boot.
Now just bootloops to the samsung screen,
It's borked.
I think I lost Dev Edition and the best I can do is start from scratch?
Not sure where to go now.
plainbum said:
I flashed to 09/19 build the phone would not boot. I kept getting a rapid glow behind the Blue android mascot.
I then tried to odin the BOG5 firmware and I got errors . rebooted the phone and it wouldnt boot.
Now just bootloops to the samsung screen,
It's borked.
I think I lost Dev Edition and the best I can do is start from scratch?
Not sure where to go now.
Click to expand...
Click to collapse
Is the BOG5 firmware stock? If so, you shouldn't have flashed it. If you still have TWRP and root, take these steps to clean flash to CM13.
1. Boot to TWRP, wipe all but your External Storage (SD Card)
2. Flash CM13 09/19 zip
3. Flash the boot image from CM13 07/24
(Click on install image, select the boot.img file, you will then see two choices: boot and recovery, select boot only, then swipe to flash.)
4. Flash gapps and SuperSU zip
5. Reboot
The rapid blinking was happening because you need the boot image from 07/24 in order for the rom to load properly. I'd post the boot image for you, but it exceeds the file size limit. To get the boot image, download the CM13 07/24 build, unzip the file, and extract the boot.img file to your SD card, along with everything else that you want to flash. Let me know if you need me to provide more details on any of the steps.
I can't even get into twrp.
All I can do is get into "Download mode"
I have started a new thread looking for help here:
https://forum.xda-developers.com/no...p-screwed-vzw-dev-ed-software-update-t3530282
plainbum said:
I can't even get into twrp.
All I can do is get into "Download mode"
I have started a new thread looking for help here:
https://forum.xda-developers.com/no...p-screwed-vzw-dev-ed-software-update-t3530282
Click to expand...
Click to collapse
What do you see when you try to boot into recovery?
Hi quinciebee,
I posted this before I borked my phone, before you started helping me.
How I got here was I was trying to upgrade the firmware so I could them flash The ne 7.1.1 "EmotionOS"
I was following the instruction here:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
Specifically where is says:
"If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:
N910VVRU2CPJ2_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2."
It flashed fine and then I installed the EmotionOS and all went well but I could NOT get 4G LTE to work, only 3G.
So I abandoned it and reflashed a backup of the CM 13 I was running since May 25.
I was good on cm13 but I got errors when I was in settings and tried to go into "Security"
Im all god now and I will be trying to get back to 6.0 and then 7.1.1 after my house guests leave.
The phone is running fine in 5.1.1.
THanks again!
Hello guys!
I have a problem with my wife's Note II (should be 7100).
Starting from a stock 4.4.2 I tried installing MIUI 8 through PhilzTouch. Everything went fine, I also installed Open Gapps but I had lost the IMEI. The phone didn't recognize the sim at all (INSERT SIM).
So I tried to restore the working EFS partition (of the 4.4.2) but still the IMEI was corrupted.
I had to restore the whole ROM backup to get the phone working again.
Then i tried with RR 7.1 but I had the same problem.
Basically it seems that everything i flash make me lose the IMEI :|
Any suggestions? Thanks!
The phone was running the latest bootloader and modem before flashing a custom ROM? I also recommend using TWRP to flash, not CWM or Philz.
audit13 said:
The phone was running the latest bootloader and modem before flashing a custom ROM? I also recommend using TWRP to flash, not CWM or Philz.
Click to expand...
Click to collapse
Thanks for the reply!
I'm not sure that the Samsung firmware the phone was running was the latest. Didn't think it could make any difference :/
Can you pinpoint me to the correct files?
Oh and will try with TWRP as you told
The latest n7100 firmware is here: https://www.sammobile.com/firmwares/database/GT-N7100/
To find out about the phone's bootloader and modem, you can install the Samsung Phone Info app from the Play Store.
audit13 said:
The latest n7100 firmware is here: https://www.sammobile.com/firmwares/database/GT-N7100/
To find out about the phone's bootloader and modem, you can install the Samsung Phone Info app from the Play Store.
Click to expand...
Click to collapse
Thanks, downloading now.
It's terribly slow, is there any other mirror?
Try this: http://samsung-updates.com/
audit13 said:
Try this: http://samsung-updates.com/
Click to expand...
Click to collapse
Even worse
Update:
Installed the latest n7100 firmware then flashed MIUI 8 through TWRP... Still unknown baseband and no IMEI
Tried to restore EFS and MODEM but no luck.
Same for RR 7.1.1
I'm trying Eclipse now sigh
UPDATE 2:
Eclipse working good at least!
Maybe it's just a bug in MIUI? I'm not sure as I don't have a note 2 to test.
audit13 said:
Maybe it's just a bug in MIUI? I'm not sure as I don't have a note 2 to test.
Click to expand...
Click to collapse
I don't think so, cause I'm having the same problem on RR 7.1 :/
Maybe you need to flash a different kernel? Anyone else in the RR thread mention this issue?
I am currently running stock 7.1.1 with august updates NPNS26.118-22-1
I am facing some serious issues with it and thinking about downgrading to NPNS25.137-24-1-9 ( nougat 7.0) via fastboot.
I have heard that downgrading can result in a bricked phone. Is it so?
kkube said:
I am currently running stock 7.1.1 with august updates NPNS26.118-22-1
I am facing some serious issues with it and thinking about downgrading to NPNS25.137-24-1-9 ( nougat 7.0) via fastboot.
I have heard that downgrading can result in a bricked phone. Is it so?
Click to expand...
Click to collapse
Yes you'll end up bricking your phone, the best thing you can do is reflashing stock 7.1.1 either by adb or a zip or try a custom ROM but don't downgrade for your phone's sake.
nosiobadx said:
Yes you'll end up bricking your phone, the best thing you can do is reflashing stock 7.1.1 either by adb or a zip or try a custom ROM but don't downgrade for your phone's sake.
Click to expand...
Click to collapse
I have doubt, when I had the original Moto G 2013 it was possible to downgrade via fastboot flashing boot, recovery and system, avoiding gpt and bootloader (it was even possible to flash the modem without ending with a brick) do you know if it's possible to do the same kind of downgrade with this phone?
ddiuit said:
I have doubt, when I had the original Moto G 2013 it was possible to downgrade via fastboot flashing boot, recovery and system, avoiding gpt and bootloader (it was even possible to flash the modem without ending with a brick) do you know if it's possible to do the same kind of downgrade with this phone?
Click to expand...
Click to collapse
What are the issues you're facing??
It can be done, but to be sure you can reflash 7.1.1 and if the issues persists then yes you can try the steps you wrote above.
I tried to flash for the first time a custom rom for this phone, tried with Pixel OS and Pixel experience, after the phone restart, i notice that the SIM card 1 and SIM card 2 wasn't working i placed my sim on 2 different phones and worked perfecly fine, is there any method to solve this problem? Or i should go back to stock rom.
Uriel970219 said:
I tried to flash for the first time a custom rom for this phone, tried with Pixel OS and Pixel experience, after the phone restart, i notice that the SIM card 1 and SIM card 2 wasn't working i placed my sim on 2 different phones and worked perfecly fine, is there any method to solve this problem? Or i should go back to stock rom.
Click to expand...
Click to collapse
flash firmware for your region
REDOTHELLO said:
flash firmware for your region
Click to expand...
Click to collapse
I just flashed the last global firmware, but even using stock rom, I'm not able to use any of my SIM slots now, MIUI says that SIM is not inserted.
Uriel970219 said:
I just flashed the last global firmware, but even using stock rom, I'm not able to use any of my SIM slots now, MIUI says that SIM is not inserted.
Click to expand...
Click to collapse
check IMEI if it''s still there, otherwise nvdata might've gone haywire.
Flashing fastboot version of the stock ROM should fix any partition being messed up, right?
Mthw said:
Flashing fastboot version of the stock ROM should fix any partition being messed up, right?
Click to expand...
Click to collapse
It should, but talking about NVdata, it is actually specific for every device and even Stock ROMS doesn't ship with NVdata partition otherwise all of us explorers would have the same NVdata(SN, IMEI, MAC Address) if we flash it. But I'm pretty confident that if the guy's IMEI is still intact to the phone, then it must be a hardware issue.
GN-z11 said:
check IMEI if it''s still there, otherwise nvdata might've gone haywire.
Click to expand...
Click to collapse
Yep, im able to see both IMEI numbers under settings however, miui says that there's no SIM inserted, i've tried to flash the last rom via fastboot, 13.0.5.0 the problem persist, tried with 13.0.2.0 same, my last attempt was flashing 13.0.2.0 but closing the bootloader at the end, and i got the same result, any thoughts?
Uriel970219 said:
Yep, im able to see both IMEI numbers under settings however, miui says that there's no SIM inserted, i've tried to flash the last rom via fastboot, 13.0.5.0 the problem persist, tried with 13.0.2.0 same, my last attempt was flashing 13.0.2.0 but closing the bootloader at the end, and i got the same result, any thoughts?
Click to expand...
Click to collapse
Quick update, i flashed MIUI 12.5 rom and now the device is recognizing both SIM slots, however i don't have signal yet. I'm gonna flash 13.0.2 to see if problem gets solved.
Uriel970219 said:
Quick update, i flashed MIUI 12.5 rom and now the device is recognizing both SIM slots, however i don't have signal yet. I'm gonna flash 13.0.2 to see if problem gets solved.
Click to expand...
Click to collapse
Do you have a backup efs partition. If you happen to have it, do a restore and solve the problem
akins0405 said:
Do you have a backup efs partition. If you happen to have it, do a restore and solve the problem
Click to expand...
Click to collapse
Tnx for reply, no, i don't have a backup of efs partition, si there any other way to fix the problem? I tried yo flash stock rom via edl, but i need an authorized developer acct. Any ideas.?
Uriel970219 said:
Tnx for reply, no, i don't have a backup of efs partition, si there any other way to fix the problem? I tried yo flash stock rom via edl, but i need an authorized developer acct. Any ideas.?
Click to expand...
Click to collapse
No firehose for Xiaomi 11 Lite 5G NE: Not available yet, so I don't know how to install in edl. >try to install stock rom with stock recovery, maybe it will help.
Is there a guide to do it? I already flashed stock rom via fastboot, but the problem persist.
akins0405 said:
No firehose for Xiaomi 11 Lite 5G NE: Not available yet, so I don't know how to install in edl. >try to install stock rom with stock recovery, maybe it will help.
Click to expand...
Click to collapse