Develop Bugs

[Q] Samsung Note 2 N7100 Soft-Bricked (Solutions not working)

My Samsung note 2 won't move from the boot screen. It does boot into recovery when I press the buttons but it won't mount any files. Sideloading works through ADB but then that's just about it as it gives me errors. Tried to use Odin to unbrick it but it keeps giving me errors. What do I do? How do I unbrick my phone? I have posted a screenshot of the errors I am getting. Can someone please advise on what I should do?

boshez said:
My Samsung note 2 won't move from the boot screen. It does boot into recovery when I press the buttons but it won't mount any files. Sideloading works through ADB but then that's just about it as it gives me errors. Tried to use Odin to unbrick it but it keeps giving me errors. What do I do? How do I unbrick my phone? I have posted a screenshot of the errors I am getting. Can someone please advise on what I should do?
Click to expand...
Click to collapse
I have almost a same situation here with my brothers phone. I don't know why, but every time he manages to brick it like that. When booting into recovery from rom (power menu), it crashes the phone and it gets in a bootloop trying to get into the recovery.
What I did:
- Reflash recovery through odin (odin succes, phone fail)
- Reflash recovery through odin and erase nand (same...)
The only fix I found was to flash the stock rom and nand erase through odin, then flash the recovery (twrp 2.8.6.0), erase almost everything (sys, data, cache) and flash custom rom.
Looking at your pic, after nand write it fails, it could be that your nand chip is dead, and if it is like that, move to an other phone, it isn't worth to get a new mobo for your phone, those things cost more than 100 euro and a great new phone would get about 250 from you (like that asus zenfone, I think that is the one you should aim for if you want mid class to high class phones)

boshez said:
My Samsung note 2 won't move from the boot screen. It does boot into recovery when I press the buttons but it won't mount any files. Sideloading works through ADB but then that's just about it as it gives me errors. Tried to use Odin to unbrick it but it keeps giving me errors. What do I do? How do I unbrick my phone? I have posted a screenshot of the errors I am getting. Can someone please advise on what I should do?
Click to expand...
Click to collapse
The firmware you trying to flash xxalj3 (saw at screenshot) is very old 4.1.1 with sds bug also. Probably your phone has newer bootloader and 4 this you can't flash it, download latest firmware from Sammy and try again.
Sent from my GT-N7100

So I found out that my phone went through SDS. Had to get a new eMMC chip. the imei number got screwed up as well.

boshez said:
So I found out that my phone went through SDS. Had to get a new eMMC chip. the imei number got screwed up as well.
Click to expand...
Click to collapse
Sorry to hear this.
Sent from my GT-N7100

vagsvag said:
Sorry to hear this.
Sent from my GT-N7100
Click to expand...
Click to collapse
Got my phone to start working again after I installed a new eMMC. However when I updated it to a 4.4.2 Stock ROM, it won't register on to the network.

boshez said:
Got my phone to start working again after I installed a new eMMC. However when I updated it to a 4.4.2 Stock ROM, it won't register on to the network.
Click to expand...
Click to collapse
Your imei is normal or something 0004....? Corrupted general imei
Sent from my GT-N7100

vagsvag said:
Your imei is normal or something 0004....? Corrupted general imei
Sent from my GT-N7100
Click to expand...
Click to collapse
IMEI is the same as the one on the phone. I believe I must have installed the wrong ROM. I installed the N7100XXUFNL1 one which said Pakistan but then now that I checked it again, I found out it was for Nigeria, UAE, etc (which share the same CSC). Now I am downloading the N7100XXUFND4 one. Hope it makes a difference. I did backup my IMEI etc incase there is an issue.

boshez said:
IMEI is the same as the one on the phone. I believe I must have installed the wrong ROM. I installed the N7100XXUFNL1 one which said Pakistan but then now that I checked it again, I found out it was for Nigeria, UAE, etc (which share the same CSC). Now I am downloading the N7100XXUFND4 one. Hope it makes a difference. I did backup my IMEI etc incase there is an issue.
Click to expand...
Click to collapse
Samsung had made efs partition update when released 4.3 if I remember well. This update was making by the kernel when was flashing the fw was updating the efs too. If you haven't flash original firmware via odin 4.3 or later probably your efs is not updated. Try to flash original fw via odin, I think it will work.
Sent from my GT-N7100

Losing IMEI everytime!

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?

Bootloop after flahsing Magisk & no-verity zips

Hi,
I just tried to root my Mi Max 3 but got bootloop, what can I do?
I unlocked the device.
Then I flashed TWRP 3.2.0. nitrogen, devcie was encrypted then.
I flashed Magisk 18.1., rebooted, but bootloop.
I rebooted into TWRP again and flashed no-verity-opt-encrypt-6.0.zip and again Magisk 18.1 and rebooted, but bootloop only.
I did factory reset but bootloop only.
What am I suposed to do? Any help from you guys?
Thanks you very much !

download and install the latest twrp from nijel8. Make a wipe and install only a clean rom and magisk. Nothing more. It must work.

Tried magisk 18.0?
I use magisk 18.0 and official twrp 3.2.3.0.

Hi,
it didnt help unfortunately.
I think I first need to flash a stock firmware completely right? Then try another round with the suggested versions by you guys.
I downloaded stock ROM from Xiao Mi Website here: http://en.miui.com/a-234.html
It is named: nitrogen_global_images_V10.2.1.0.OEDMIFK_20181218.0000.00_8.1_global
But when I try to flash it via fastboot mode and the help of Xiao Mi Flash Tool I get an error like this (attachment)
Any help?
Update: I just flashed official full rom named: miui_MIMAX3Global_V10.2.1.0.OEDMIFK_885d8903d6_8.1.zip via TWRP and it didnt show any errors (but TWRP still installed, I expected stock revoery actually?!). I wiped cache and rebooted but still bootloop.
I am really not sure what to do now.
Update 2: I now was able to flash stock rom (nitrogen_global_images_V10.2.1.0.OEDMIFK_20181218.0000.00_8.1_global) via fastboot mode (error like on screenshot didnt appear anymore, dont really know why) now phone is only booting into stock MIUI recovery and shows a red noteification: "This MIUI Version cant be installed on this device" -> Can anybode give me help please?
Update 3: Tried to unlock again but it fails due to my device is not bound to my MI Account, but how to add it to account as I cant boot it up anymore and go to the settings in android. Or do I need another FULL Rom? I read smth that this error (Rom cant be installed on this device) appears if one is trying to flash Global Rom instead of China ROM? Where to get this one? Dont know the difference actually But my phone had google services preinstalled
I now even downloaded the chinese full rom: Mi Max 3 China Stable ROM 10.0.6.0 – V10.0.6.0.OEDCNFH / MIUI 9 / fastboot / Android Oreo because I think maybe this was originally i nstalled (purchased phone in Indonesia which is black market)
but once I try to flash it, the mix flash tool tells me now erase is not allowed in locked mode. I need to unlock first? but how? Unlock bootloader is not possible due to device is not bound with my mi-account.

I am really lost know
current situation:
not able to flash china full rom because locked
not able to unlock because device not bound to mi-account
I amonly able to bootup into mi-stock reciovery and stock bootloader.
what can I do?

tobyffm said:
I am really lost know
current situation:
not able to flash china full rom because locked
not able to unlock because device not bound to mi-account
I amonly able to bootup into mi-stock reciovery and stock bootloader.
what can I do?
Click to expand...
Click to collapse
What base it has, china or global when you get it?

tobyffm said:
I am really lost know
current situation:
not able to flash china full rom because locked
not able to unlock because device not bound to mi-account
I amonly able to bootup into mi-stock reciovery and stock bootloader.
what can I do?
Click to expand...
Click to collapse
Can't you flash from stock recovery? Download recovery rom matching your stock recovery(china or global), save in microsd. Enter recovery and flash rom.
Edit: sorry, just checked. Not possible to select file from stock mi recovery.

Lecterr said:
What base it has, china or global when you get it?
Click to expand...
Click to collapse
I dont really know. AT least all google services were available. does this mean it has been the global base? I bought this phone in Indonesia were it is not available officially, only through some black market sellers in the malls. Maybe they also have used the chinese versions, unlocked and reflashed the global versions and then they sell it. So maybe it has been the chinese base originally but is sold out with the global version? On the devices backside is a sticker with IMEi, IMEI2, MEID and SN, does this say anything about the version?
bobo9900 said:
Can't you flash from stock recovery? Download recovery rom matching your stock recovery(china or global), save in microsd. Enter recovery and flash rom.
Click to expand...
Click to collapse
I think not, in Stock Recovery which is now installed on the phone I only have Reboot, Wipe Data and Connect MIAssistant

How about this?
https://forum.xda-developers.com/redmi-note-5-pro/how-to/tut-flashing-official-recovery-rom-t3798165
Same chipset as mi max3..

bobo9900 said:
How about this?
https://forum.xda-developers.com/redmi-note-5-pro/how-to/tut-flashing-official-recovery-rom-t3798165
Same chipset as mi max3..
Click to expand...
Click to collapse
thanks a lot for this tip, bro. I am not sure because in this guide they say it will help you to flash a recovery? I am having stock recovery already installed. I need to reflash the correct Rom. Anyway, I will try it asap. Atm it fails due to bad internet connection in my hotel right now.
I will download following ROM: Chinese Stable: MIUI 10 V10.2.1.0.OEDCNXM as a .zip archive and will try to load it into the Mi Assistant tool and try to start flashing from there. OK? Will let you know about the result then.

tobyffm said:
thanks a lot for this tip, bro. I am not sure because in this guide they say it will help you to flash a recovery? I am having stock recovery already installed. I need to reflash the correct Rom. Anyway, I will try it asap. Atm it fails due to bad internet connection in my hotel right now.
I will download following ROM: Chinese Stable: MIUI 10 V10.2.1.0.OEDCNXM as a .zip archive and will try to load it into the Mi Assistant tool and try to start flashing from there. OK? Will let you know about the result then.
Click to expand...
Click to collapse
Its for flashing rom. Use the recovery rom, not fastboot rom. What it means is that your recovery should match the rom. (MiRecovery china, recovery rom china. MiRecovery global, recovery rom global)
I dont know which recovery version you successfully flashed to phone, but i guess its china. Won't able too boot if device is locked and recovery is not original to phone aka china recovery.
Edit:from that thread,someone successfully flashed miui10. If you failed to do so, DO NOT try to flash miui9. Different ARB, will permanently brick device.

bobo9900 said:
Its for flashing rom. Use the recovery rom, not fastboot rom. What it means is that your recovery should match the rom. (MiRecovery china, recovery rom china. MiRecovery global, recovery rom global)
I dont know which recovery version you successfully flashed to phone, but i guess its china. Won't able too boot if device is locked and recovery is not original to phone aka china recovery.
Edit:from that thread,someone successfully flashed miui10. If you failed to do so, DO NOT try to flash miui9. Different ARB, will permanently brick device.
Click to expand...
Click to collapse
bobo9900 said:
Its for flashing rom. Use the recovery rom, not fastboot rom. What it means is that your recovery should match the rom. (MiRecovery china, recovery rom china. MiRecovery global, recovery rom global)
I dont know which recovery version you successfully flashed to phone, but i guess its china. Won't able too boot if device is locked and recovery is not original to phone aka cina recovery.
Click to expand...
Click to collapse
My recovery is at least in english language, does this help?
I just tried to flash the CN rom package mentioned in my last post with this MiAssistant Beta 3.0, but package verification failed:
Does this mean it is the wrong rom package and I simply need to download the other versions and test it with other ones and once erfification works fine I will know this must be the correct one? Or is this just another error i am know running into?
Any idea?
Many tanks!
PS: Many thanks for your update: I only tried to load miui_MIMAX3_V10.2.1.0.OEDCNXM_4f84ff82ea_8.1.zip into that Mi Assistant but verification failed, didnt do anything else so far.

tobyffm said:
My recovery is at least in english language, does this help?
I just tried to flash the CN rom package mentioned in my last post with this MiAssistant Beta 3.0, but package verification failed:
Does this mean it is the wrong rom package and I simply need to download the other versions and test it with other ones and once erfification works fine I will know this must be the correct one? Or is this just another error i am know running into?
Any idea?
Many tanks!
PS: Many thanks for your update: I only tried to load miui_MIMAX3_V10.2.1.0.OEDCNXM_4f84ff82ea_8.1.zip into that Mi Assistant but verification failed, didnt do anything else so far.
Click to expand...
Click to collapse
I guess verification failed means not matching. You can try global rom. Btw, have you try wipe data. Maybe rom already flashed properly but data bug causes bootloop. Try wipe then reboot.

bobo9900 said:
I guess verification failed means not matching. You can try global rom. Btw, have you try wipe data. Maybe rom already flashed properly but data bug causes bootloop. Try wipe then reboot.
Click to expand...
Click to collapse
Yes, I also used this wipe feature in this Mi Assistant but unfortunately it did not help. After rebooting again bootup screen appears a bit longer and I can hear a short beep sound which let me think it will boot up properly but unfortunately it then restarts into recovery mode only.
well installed is this one: nitrogen_global_images_V10.2.1.0.OEDMIFK_20181218.0000.00_8.1_global, which I flashed earlier today via mi flash tool.
Now I tried to flash miui_MIMAX3Global_V10.2.1.0.OEDMIFK_885d8903d6_8.1.zip which should be the same, but verification failed, too.
Does it make sense?!
In this thread, there are many Stock Roms available:
https://forum.xda-developers.com/mi-max-3/how-to/rom-official-recovery-fastboot-roms-mi-t3827503
Shall I download all MIUI 10 Stable (Global and China) and try?

tobyffm said:
Yes, I also used this wipe feature in this Mi Assistant but unfortunately it did not help. After rebooting again bootup screen appears a bit longer and I can hear a short beep sound which let me think it will boot up properly but unfortunately it then restarts into recovery mode only.
well installed is this one: nitrogen_global_images_V10.2.1.0.OEDMIFK_20181218.0000.00_8.1_global, which I flashed earlier today via mi flash tool.
Now I tried to flash miui_MIMAX3Global_V10.2.1.0.OEDMIFK_885d8903d6_8.1.zip which should be the same, but verification failed, too.
Does it make sense?!
In this thread, there are many Stock Roms available:
https://forum.xda-developers.com/mi-max-3/how-to/rom-official-recovery-fastboot-roms-mi-t3827503
Shall I download all MIUI 10 Stable (Global and China) and try?
Click to expand...
Click to collapse
Global and china rom have their own signature. But different version always have same signature. If verification failed, I thought signature didn't match.
Now you have tried both global and china and still failed. I'm confused. I don't have any idea anymore..

bobo9900 said:
Global and china rom have their own signature. But different version always have same signature. If verification failed, I thought signature didn't match.
Now you have tried both global and china and still failed. I'm confused. I don't have any idea anymore..
Click to expand...
Click to collapse
Thanks anyway bobo9900 for assisting me. And I should not try to flash a MIUI 9 rom, yeah?
Argh, I really don't understand it. I just got this phone yesterday, unlocked and installed twrp and magisk by using a how.to especially for Mi Max 3 and ran into this issue, FU**. Why does this happen to me, I only did these simple steps. Phone for trash after 1 day already?
Anybody else there who can help me?

tobyffm said:
Thanks anyway bobo9900 for assisting me.
Argh, I really don't understand it. I just got this phone yesterday, unlocked and installed twrp and magisk by using a how.to especially for Mi Max 3 and ran into this issue, FU**. Why does this happen to me, I only did these simple steps. Phone for trash after 1 day already?
Anybody else there who can help me?
Click to expand...
Click to collapse
Confirm your version global or china, so other might able to help. Mine come locked with screen protector sticker in English without Chinese words. Box had 'global version' written in red sticker.
Semoga sukses bro..

bobo9900 said:
Confirm your version global or china, so other might able to help. Mine come locked with screen protector sticker in English without Chinese words. Box had 'global version' written in red sticker.
Semoga sukses bro..
Click to expand...
Click to collapse
well, now there is nitrogen_global_images_V10.2.1.0.OEDMIFK_20181218. 0000.00_8.1_global installed on the phone.
Also the Mi Assistant tool recgnizes V10.2.1.0.OEDMIFK as currently installed. My box has pon backside some chinese signs, no teaser "Global version". I think it has been chinese but black market sellers flashed global roms already to fit the indonesian market.
But I just noticed that in this Mi Assistant tool I have the options "Flash" and "Quick FLash" (erase all data) and there they mention it will work with Miui 8 and 9. Seems this Assistant tool is not MIUI 10-ready?! And I couldnt find a newer version of this.
Maybe this is the reason why verification with MIUI 10 packages fails?

tobyffm said:
well, now there is nitrogen_global_images_V10.2.1.0.OEDMIFK_20181218. 0000.00_8.1_global installed on the phone.
Also the Mi Assistant tool recgnizes V10.2.1.0.OEDMIFK as currently installed. My box has pon backside some chinese signs, no teaser "Global version". I think it has been chinese but black market sellers flashed global roms already to fit the indonesian market.
But I just noticed that in this Mi Assistant tool I have the options "Flash" and "Quick FLash" (erase all data) and there they mention it will work with Miui 8 and 9. Seems this Assistant tool is not MIUI 10-ready?! And I couldnt find a newer version of this.
Maybe this is the reason why verification with MIUI 10 packages fails?
Click to expand...
Click to collapse
Read the last page, someone manage to re flash 10.0.2.0.
If you wanna flash old version, check ARB level first.

bobo9900 said:
Read the last page, someone manage to re flash 10.0.2.0.
If you wanna flash old version, check ARB level first.
Click to expand...
Click to collapse
OK checked. Through fastboot check of ARB I get:
fastboot getvar anti
getvar:anti FAILED (remote: GetVar Variable Not found)
finished. total time: 0.016s
Wondering again why again an error lol
TRhrough opening flash_all.bat file I see:
CURRENT_ANTI_VER=4
fastboot %
which means I cant downgrade, ya?

I F*cked up! Help me please?

Long story short bought a G5 Cedric running latest official firmware oreo 8.1, didn't like it cuz it's too heavy, unlocked the bootloader, flashed twrp then flashed lineage 17 but can't pass safetynet,(clean) flashed resurrection remix after same problem, then i flashed omni rom and suddenly my IMEI was gone and can't install gapps, what to do now? I just want a good custom rom that passes safetynet, don't care if it's pie or Q.

Flash a rom where imei works
Backup efs partition using 64bit twrp
You can then restore efs partition if you loose imei
With regards to safetynet none of the custom roms will pass without you doing some work
You need to flash magisk
Flash Busybox magisk module
Flash props config module and follow all the instructions on how to change device fingerprint eg to a pixel 4 https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/
Hide magisk manager with a random package name from magisk settings
Hide app that detects root with magisk hide from its settings
You can also try the universal safetynet patcher magisk module if the above doesn't work but some report it causes bootloops on some devices/roms

Thank you for the quick response, i have a few questions regarding what you said:
1- how will i know which rom to flash where the IMEI works before flashing the actual rom itself?
2- how do i know if my current twrp is 64bit or not? it's the one from the Lineage 17 thread.
3- when im succesfull in executing those steps and i have to back up efs, where can i find it to restore it if i flash another rom again? because last time before flahsing i wiped system,dalvik & Cache & data but not the storage and yet my back-up was gone?
TheFixItMan said:
Flash a rom where imei works
Backup efs partition using 64bit twrp
You can then restore efs partition if you loose imei
With regards to safetynet none of the custom roms will pass without you doing some work
You need to flash magisk
Flash Busybox magisk module
Flash props config module and follow all the instructions on how to change device fingerprint eg to a pixel 4 https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/
Hide magisk manager with a random package name from magisk settings
Hide app that detects root with magisk hide from its settings
You can also try the universal safetynet patcher magisk module if the above doesn't work but some report it causes bootloops on some devices/roms
Click to expand...
Click to collapse

maserati2011 said:
Thank you for the quick response, i have a few questions regarding what you said:
1- how will i know which rom to flash where the IMEI works before flashing the actual rom itself?
2- how do i know if my current twrp is 64bit or not? it's the one from the Lineage 17 thread.
3- when im succesfull in executing those steps and i have to back up efs, where can i find it to restore it if i flash another rom again? because last time before flahsing i wiped system,dalvik & Cache & data but not the storage and yet my back-up was gone?
Click to expand...
Click to collapse
1 - You will have to try roms yourself to find out
2 - All custom roms from oero onwards are 64bit - you wouldn't be able to flash them without a 64bit twrp so you already have one
3 - data/media/twrp/backups or storage/emulated/0/twrp/backups
I recommend changing the storage location to your sdcard so they don't get deleted when you wipe data or transferring to a pc
Formatting data is effectively formatting internal storage as the device is encrypted

TheFixItMan said:
1 - You will have to try roms yourself to find out
2 - All custom roms from oero onwards are 64bit - you wouldn't be able to flash them without a 64bit twrp so you already have one
3 - data/media/twrp/backups or storage/emulated/0/twrp/backups
I recommend changing the storage location to your sdcard so they don't get deleted when you wipe data or transferring to a pc
Formatting data is effectively formatting internal storage as the device is encrypted
Click to expand...
Click to collapse
I'm currently sticking with m_vaisakh's AOSP-10 as it shows both my IMEI numbers, its also the most stable and reliable out of the Android 10 roms for the G5 CEDRIC, i do have a problem though: i tried 2 simcards in the dual sim function and they both worked but no 4G, just 3G/HSPA+ both SIM-1 & SIM-2, how can i fix this issue?

maserati2011 said:
I'm currently sticking with m_vaisakh's AOSP-10 as it shows both my IMEI numbers, its also the most stable and reliable out of the Android 10 roms for the G5 CEDRIC, i do have a problem though: i tried 2 simcards in the dual sim function and they both worked but no 4G, just 3G/HSPA+ both SIM-1 & SIM-2, how can i fix this issue?
Click to expand...
Click to collapse
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
If rebuilding the efs doesn't work I do not know
Backup efs first incase it fails to rebuild and imei is 0 again - use a twrp 64 bit to back it up and obviously save to sdcard & pc incase you need to re-flash rom as wiping data will erase your backup on internal storage

TheFixItMan said:
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
If rebuilding the efs doesn't work I do not know
Backup efs first incase it fails to rebuild and imei is 0 again - use a twrp 64 bit to back it up and obviously save to sdcard & pc incase you need to re-flash rom as wiping data will erase your backup on internal storage
Click to expand...
Click to collapse
it didn't work as my IMEI was 0 on both sims, thankfully i backed up EFS before erasing, so I managed to restore the IMEI again.
Is there really no other way to get 4G back?

Hello friend, did you get my reply regarding 4G ?

maserati2011 said:
Hello friend, did you get my reply regarding 4G ?
Click to expand...
Click to collapse
As stated before - I do not know the answer
I don't own this device

maserati2011 said:
Hello friend, did you get my reply regarding 4G ?
Click to expand...
Click to collapse
Which ROM are you using and didn't you got your IMEI?

riyan65 said:
Which ROM are you using and didn't you got your IMEI?
Click to expand...
Click to collapse
I was using m_vaisakh's AOSP_10 where i retrieved my IMEI (after losing it on different roms) i tried both sims and had only 3G no 4G.
Now i have switched to OfficerJimLahey's CarbonROM_7 Android_9 both my IMEI numbers show but i haven't tested 4G with simcards yet.

maserati2011 said:
I was using m_vaisakh's AOSP_10 where i retrieved my IMEI (after losing it on different roms) i tried both sims and had only 3G no 4G.
Now i have switched to OfficerJimLahey's CarbonROM_7 Android_9 both my IMEI numbers show but i haven't tested 4G with simcards yet.
Click to expand...
Click to collapse
If it doesn't work in rom then move back to stock Oreo and once you got the 4g take backup of efs and persist and move to custom ROM. If the 4g is available then no need to restore backup, if not restore the backup and enjoy 4g.

riyan65 said:
If it doesn't work in rom then move back to stock Oreo and once you got the 4g take backup of efs and persist and move to custom ROM. If the 4g is available then no need to restore backup, if not restore the backup and enjoy 4g.
Click to expand...
Click to collapse
How do i do that? using the Lenovo Moto Smart Assistant?

maserati2011 said:
How do i do that? using the Lenovo Moto Smart Assistant?
Click to expand...
Click to collapse
Flash stock rom firmware via fastboot
Stock rom firmware is available via
https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you don't know what one to choose I suggest latest retail
If you don't know how to flash stock firmware via fastboot Google is your friend

TheFixItMan said:
Flash stock rom firmware via fastboot
Stock rom firmware is available via
https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you don't know what one to choose I suggest latest retail
If you don't know how to flash stock firmware via fastboot Google is your friend
Click to expand...
Click to collapse
i have flashed stock rom using Lenovo Moto Smart Assistant, IMEI is there, 4G works, how can i relock the bootloader from here? cuz i wanna sell the device.

maserati2011 said:
i have flashed stock rom using Lenovo Moto Smart Assistant, IMEI is there, 4G works, how can i relock the bootloader from here? cuz i wanna sell the device.
Click to expand...
Click to collapse
I wouldn't re-lock it for several reasons
1- you need the unlock code to unlock it again & Motorola will say its already been unlocked
2 - Even if you re-lock it it will still display its been unlocked previously
3 - if you ever need to flash stock firmware via fastboot again it may fail with permission denied as the firmware may not be fully signed & you can't flash unsigned firmware with a locked bootloader
4 - if you ota update & it it fails & you hardbrick then again same as point 3
If you really want to Google how to & you need fully signed firmware else it will not lock

TheFixItMan said:
I wouldn't re-lock it for several reasons
1- you need the unlock code to unlock it again & Motorola will say its already been unlocked
2 - Even if you re-lock it it will still display its been unlocked previously
3 - if you ever need to flash stock firmware via fastboot again it may fail with permission denied as the firmware may not be fully signed & you can't flash unsigned firmware with a locked bootloader
4 - if you ota update & it it fails & you hardbrick then again same as point 3
If you really want to Google how to & you need fully signed firmware else it will not lock
Click to expand...
Click to collapse
I'm going to respond to each point you mentioned:
1- I still have the email from Lenovo containing the unlock code, do i need the same code to relock the bootloader?
2-are you sure it will still say it's been unlocked before?
3-what does fully signed mean? i searched through the link you sent me earlier and i found the same one that i flashed through LMSA, that is XT1676_CEDRIC_RETEU_DS_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip is the one I flashed through LMSA not fully signed?
4-there's no updates anymore after the version i mentioned in point 3.
side question: does this method you mentioned still applies to relock the bootloader without the aforementioned issues?
PS: it still says ID: bad key on the bootloader unlocked warning, even though i retrieved my IMEI number, shouldn't it display my IMEI number instead of bad key?

maserati2011 said:
I'm going to respond to each point you mentioned:
1- I still have the email from Lenovo containing the unlock code, do i need the same code to relock the bootloader?
2-are you sure it will still say it's been unlocked before?
3-what does fully signed mean? i searched through the link you sent me earlier and i found the same one that i flashed through LMSA, that is XT1676_CEDRIC_RETEU_DS_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip is the one I flashed through LMSA not fully signed?
4-there's no updates anymore after the version i mentioned in point 3.
side question: does this method you mentioned still applies to relock the bootloader without the aforementioned issues?
PS: it still says ID: bad key on the bootloader unlocked warning, even though i retrieved my IMEI number, shouldn't it display my IMEI number instead of bad key?
Click to expand...
Click to collapse
You don't need code to lock bootloader - just to unlock it
Yes the bootloader will display its locked but will also give a status code that states its been previously unlocked
Fully signed means each part of the firmware has been signed by Motorola - sometimes the boot.img isn't
You will always get bad key or n/a with an unlocked bootloader - this is normal - you can flash a modded logo.bin to replace this
Those are the steps to re-lock the boot-loader - obviously oreo firmware has more sparsechunk so add the extra parts

TheFixItMan said:
You don't need code to lock bootloader - just to unlock it
Yes the bootloader will display its locked but will also give a status code that states its been previously unlocked
Fully signed means each part of the firmware has been signed by Motorola - sometimes the boot.img isn't
You will always get bad key or n/a with an unlocked bootloader - this is normal - you can flash a modded logo.bin to replace this
Those are the steps to re-lock the boot-loader - obviously oreo firmware has more sparsechunk so add the extra parts
Click to expand...
Click to collapse
So basically i should leave it unlocked it's better this way yes? and if i want to flash a modded logo.bin do i need to flash TWRP again?

maserati2011 said:
So basically i should leave it unlocked it's better this way yes? and if i want to flash a modded logo.bin do i need to flash TWRP again?
Click to expand...
Click to collapse
No you can do it via fastboot
fastboot flash logo logo.bin

Question Going back to CN Rom from Global

hey guys, successfully flashed the global rom over my redmagic 6 pro CN version but decided to go back to the CN rom, but when I try to install it via local update it results in a recovery boot loop and the only option is to do a factory reset, but when I do a factory reset, for some reason it goes back to the Global Rom. Any tips on what I need to do? thanks

auerick said:
hey guys, successfully flashed the global rom over my redmagic 6 pro CN version but decided to go back to the CN rom, but when I try to install it via local update it results in a recovery boot loop and the only option is to do a factory reset, but when I do a factory reset, for some reason it goes back to the Global Rom. Any tips on what I need to do? thanks
Click to expand...
Click to collapse
Personally what I would do is extract the boot image from the CN rom zip and fastboot flash it after you flash the CN rom via local update. You will have to be bootloader unlocked of course. You can always relock after you've got the CN rom up and running.

bob24260 said:
Personally what I would do is extract the boot image from the CN rom zip and fastboot flash it after you flash the CN rom via local update. You will have to be bootloader unlocked of course. You can always relock after you've got the CN rom up and running.
Click to expand...
Click to collapse
I actually tried that but then it get's stuck on the Nubia logo, so something must have gone wrong somewhere, and one odd thing is if I try installing the latest V2.63 CN rom via local update it tells me that the package is not compatible with the phone. At least the Redmagic 5G had the local update option on its recovery. Nothing at all on the Redmagic 6 Pro. Isn't recovery.img included in the payload.bin? doesn't seem to be there when I dumped the payload

auerick said:
hey guys, successfully flashed the global rom over my redmagic 6 pro CN version but decided to go back to the CN rom, but when I try to install it via local update it results in a recovery boot loop and the only option is to do a factory reset, but when I do a factory reset, for some reason it goes back to the Global Rom. Any tips on what I need to do? thanks
Click to expand...
Click to collapse
Hi there, can you describe the whole steps to flash your RM6 pro from CN to global?
Which rom did you use? EU or non-EU?
Thanks for the reply.

cannon3025 said:
Hi there, can you describe the whole steps to flash your RM6 pro from CN to global?
Which rom did you use? EU or non-EU?
Thanks for the reply.
Click to expand...
Click to collapse
I installed both just to see if I cam go back to CN rom once I'm on either Rom
Basically just downloaded the Global ROM file from the Nubia website, put it on my phones root folder, then did a local update, using the system update local update setting

auerick said:
I actually tried that but then it get's stuck on the Nubia logo, so something must have gone wrong somewhere, and one odd thing is if I try installing the latest V2.63 CN rom via local update it tells me that the package is not compatible with the phone. At least the Redmagic 5G had the local update option on its recovery. Nothing at all on the Redmagic 6 Pro. Isn't recovery.img included in the payload.bin? doesn't seem to be there when I dumped the payload
Click to expand...
Click to collapse
I believe the recovery is part of the boot image now. I've dumped the payload too and I'll have a quick look and see if it's present. I have all the files for the US, global version. It's 4.1.2 I believe. I'll be happy to help any way I can. I just had a bad experience today... I've had my 6 Pro a week and already the cord has quit working. Not a good sign. I'm starting to regret my purchase.

auerick said:
I actually tried that but then it get's stuck on the Nubia logo, so something must have gone wrong somewhere, and one odd thing is if I try installing the latest V2.63 CN rom via local update it tells me that the package is not compatible with the phone. At least the Redmagic 5G had the local update option on its recovery. Nothing at all on the Redmagic 6 Pro. Isn't recovery.img included in the payload.bin? doesn't seem to be there when I dumped the payload
Click to expand...
Click to collapse
I checked and sure enough no recovery image. Pretty sure it's baked into the boot image. Perhaps try the 4.1.2 boot image? That may boot it. Seems like you've rebranded it global version by flashing the global rom. That's a possibility anyways

bob24260 said:
I checked and sure enough no recovery image. Pretty sure it's baked into the boot image. Perhaps try the 4.1.2 boot image? That may boot it. Seems like you've rebranded it global version by flashing the global rom. That's a possibility anyways
Click to expand...
Click to collapse
ok I'll try to play around with it, won't flashing the 4.1.2 boot.img cause a brick?

auerick said:
ok I'll try to play around with it, won't flashing the 4.1.2 boot.img cause a brick?
Click to expand...
Click to collapse
Shouldn't cause a brick. If you've already flashed global before there shouldn't be any problem. But to be sure instead of flashing just fastboot boot the image.
Fastboot boot boot.img
This will allow you the luxury of trying it without actually flashing it. If it hangs up simply reboot by holding power.

bob24260 said:
Shouldn't cause a brick. If you've already flashed global before there shouldn't be any problem. But to be sure instead of flashing just fastboot boot the image.
Fastboot boot boot.img
This will allow you the luxury of trying it without actually flashing it. If it hangs up simply reboot by holding power.
Click to expand...
Click to collapse
cool didn't know I could do that, thanks for the tip

bob24260 said:
Personally what I would do is extract the boot image from the CN rom zip and fastboot flash it after you flash the CN rom via local update. You will have to be bootloader unlocked of course. You can always relock after you've got the CN rom up and running.
Click to expand...
Click to collapse
i tried this and it work but i forgot to wipe ..now i cant save images, files etc. but it doesnt matter.. anyway can you plese tell me how to relock my bootloader? some commands i think? im not familiar with relocking ..only unlocking xD this is my first time relocking bootloader

kittyshik said:
i tried this and it work but i forgot to wipe ..now i cant save images, files etc. but it doesnt matter.. anyway can you plese tell me how to relock my bootloader? some commands i think? im not familiar with relocking ..only unlocking xD this is my first time relocking bootloader
Click to expand...
Click to collapse
fastboot flashing lock
though this will prompt another factory reset

auerick said:
fastboot flashing lock
though this will prompt another factory reset
Click to expand...
Click to collapse
thanks man appreciated!

where did you get the CN rom? can you share here?

here bro https://ui.nubia.cn/rom/detail/68

kittyshik said:
here bro https://ui.nubia.cn/rom/detail/68
Click to expand...
Click to collapse
thanks

Hello what are the steps and commands to go back to the CN rom? I cannot get it from all your comments here :'(

bob24260 said:
Personally what I would do is extract the boot image from the CN rom zip and fastboot flash it after you flash the CN rom via local update. You will have to be bootloader unlocked of course. You can always relock after you've got the CN rom up and running.
Click to expand...
Click to collapse
hmm i tried this method, it seems like my phone just went back to global rom even after cn boot image flashed

China rom is faster than global