So, i want to root my nokia 6 running 7.1.1. And i want to do the following way-->
1) Flash twrp with minimal adb and fastboot from here --> https://forum.xda-developers.com/nokia-6/development/recovery-twrp-3-2-1-0-nokia-6-t3762890
2)Flash magisk through twrp from here --> https://github.com/topjohnwu/Magisk/releases
Will this procedure root my nokia 6 Ta-1021 correctly?
Yes, but first you must unlock bootloader.
Wysłane z mojego TA-1033 przy użyciu Tapatalka
gorbatschoff said:
Yes, but first you must unlock bootloader.
Wysłane z mojego TA-1033 przy użyciu Tapatalka
Click to expand...
Click to collapse
oh! i was thinking of rooting without unlocking bootloader. But seems it is not possible. Thank you for making me aware of that.
https://hikaricalyx.com/product/hmd-nokia-bootloader-unlock/
Wysłane z mojego TA-1033 przy użyciu Tapatalka
Related
I try to fix that on smart switch, after i insert the model and s/n. He show me "does not support initializing"
what should i need to do? Tnx!
It depends on what caused the problem...
In most situations its enough to flash correct firmware in Odin (you won't lose any personal data). If this doesn't solve your problem, then you should make factory reset in recovery mode.
Wysłane z mojego SM-N910C przy użyciu Tapatalka
Shreqg2 said:
It depends on what caused the problem...
In most situations its enough to flash correct firmware in Odin (you won't lose any personal data). If this doesn't solve your problem, then you should make factory reset in recovery mode.
Wysłane z mojego SM-N910C przy użyciu Tapatalka
Click to expand...
Click to collapse
ok.
how i know what is me correct firmware that i nedded?
tnx alot!
First of all you have to know your device model and CSC.
Model should be something like SM-N910C/F/H etc. It is written in download mode or under battery.
CSC you can find in recovery mode. It will be written on the bottom of the screen (for example: XEO/XEH/...).
Then go to www.sammobile.com and under FIRMWARE section put that informations. Choose the newest software from the list and flash it with Odin.
Wysłane z mojego SM-N910C przy użyciu Tapatalka
Shreqg2 said:
First of all you have to know your device model and CSC.
Model should be something like SM-N910C/F/H etc. It is written in download mode or under battery.
CSC you can find in recovery mode. It will be written on the bottom of the screen (for example: XEO/XEH/...).
Then go to and under FIRMWARE section put that informations. Choose the newest software from the list and flash it with Odin.
Wysłane z mojego SM-N910C przy użyciu Tapatalka
Click to expand...
Click to collapse
ok. so in recovery mode in the bottom of the screen he write to me:" dm-verity verification failed..."
tnx again :good:
Ok, so this is a problem with system on the phone. Good to know.
Tell me what model it is and from which country. Is it from any mobile operator or you bought it in store?
Wysłane z mojego SM-N910C przy użyciu Tapatalka
Shreqg2 said:
Ok, so this is a problem with system on the phone. Good to know.
Tell me what model it is and from which country. Is it from any mobile operator or you bought it in store?
Wysłane z mojego SM-N910C przy użyciu Tapatalka
Click to expand...
Click to collapse
ssn:n910cgsmh.
SM-N910C.
USA.
bought it in store.
THANK YOU VERY MUCH ON HELPING WITH THAT!
No problem.
It is hard for me to say which exactly CSC code you have, so what can I suggest is to install this XEO 5.0.1 firmware - http://www.sammobile.com/firmwares/download/47802/N910CXXU1BOE3_N910COXA1BOE3_XEO/ .
Probably it isn't your country code and it will couse some "force close" errors after boot. If so, go to recovery mode again and check correct CSC code. You will not see "dm-verity verification failed" error anymore as soon as you won't try to root or something like that. After checking correct CSC you can finally get correct firmware file and bring your device back to normal life.
Wysłane z mojego SM-N910C przy użyciu Tapatalka
Shreqg2 said:
No problem.
It is hard for me to say which exactly CSC code you have, so what can I suggest is to install this XEO 5.0.1 firmware - http://www.sammobile.com/firmwares/download/47802/N910CXXU1BOE3_N910COXA1BOE3_XEO/ .
Probably it isn't your country code and it will couse some "force close" errors after boot. If so, go to recovery mode again and check correct CSC code. You will not see "dm-verity verification failed" error anymore as soon as you won't try to root or something like that. After checking correct CSC you can finally get correct firmware file and bring your device back to normal life.
Wysłane z mojego SM-N910C przy użyciu Tapatalka
Click to expand...
Click to collapse
OK SO NOW I GET CSC CODE: SER.
I search on the website that you give me, but i cannot find that.
while you are at it, mid telling me where or what coutry my note 4 is
In recovery mode it says LRx22C.N910FXXU1BOC5
and csc is PAN..
I just got my phone, on the box it says mytelenor, and it has some apps, now i dont know, if its hungary, sweeded, norwey, bc it's some kind of language like theirs.. and if there is like any debloated unbranded firmware i can flash, like german one? that will get the 5.1.1. sooner?..
Thanks a lot if you help me, thanks even if you dont
Edit, oh ok, figured the csc out.. simple.. now just the question, if i can flash unbranded let's say german one, or the poland, if it has 5.1.1.?cheers
hag911 said:
OK SO NOW I GET CSC CODE: SER.
I search on the website that you give me, but i cannot find that.
Click to expand...
Click to collapse
It seems that your phone has Russian product code (SER).
Here is the newest firmware for this CSC:
http://www.sammobile.com/firmwares/download/49812/N910CXXU1BOE1_N910COXE1BOF1_SER/
Wysłane z mojego SM-N910C przy użyciu Tapatalka
---------- Post added at 07:27 AM ---------- Previous post was at 07:19 AM ----------
thejunkie said:
Edit, oh ok, figured the csc out.. simple.. now just the question, if i can flash unbranded let's say german one, or the poland, if it has 5.1.1.?cheers
Click to expand...
Click to collapse
Sure you can. But you have to chose correct firmware for your model. There is no XEO variant of N910F so you can only flash German one when 5.1.1 (or any other) is out. In most situations it will work fine without wipe, but if you want to get DBT OTA's in the future, you have to do factory reset.
Wysłane z mojego SM-N910C przy użyciu Tapatalka
Shreqg2 said:
It seems that your phone has Russian product code (SER).
Here is the newest firmware for this CSC:
http://www.sammobile.com/firmwares/download/49812/N910CXXU1BOE1_N910COXE1BOF1_SER/
Wysłane z mojego SM-N910C przy użyciu Tapatalka
---------- Post added at 07:27 AM ---------- Previous post was at 07:19 AM ----------
Sure you can. But you have to chose correct firmware for your model. There is no XEO variant of N910F so you can only flash German one when 5.1.1 (or any other) is out. In most situations it will work fine without wipe, but if you want to get DBT OTA's in the future, you have to do factory reset.
Wysłane z mojego SM-N910C przy użyciu Tapatalka
Click to expand...
Click to collapse
sorry noobo here, how do i know which firmware is the correct one :/
Check it here:
http://www.sammobile.com/firmwares/database/SM-N910F/DBT/
When Samsung release 5.1.1 ".tar" file, it will be shown on the top of the list. Then you can download it and flash to your phone. It is firmware for SM-N910F N4 DBT (Germany).
You can also flash 5.0.1 file and factory reset your phone. When 5.1.1 is available you will get OTA update.
Wysłane z mojego SM-N910C przy użyciu Tapatalka
shreqg2 said:
it seems that your phone has russian product code (ser).
Here is the newest firmware for this csc:
http://www.sammobile.com/firmwares/download/49812/n910cxxu1boe1_n910coxe1bof1_ser/
Click to expand...
Click to collapse
i do the flash boot from odin.and succeed! After that i do a wipe/factory rest.
But, its still stuck om the logo and make a restart :/
Problem , yes I am experienced and no it is not.
Now Huawei Mate 7
root , Yes
unlock, yes
Android version 6.0 B513 works but no Wi-Fi and Bluetooth
B331 version works fine
Update B513 works but no Wi-Fi and Bluetooth
Now B513 works but can not return to B331 .
because I want to have wifi
It is …. But yeah
can someone tell me to go back to the default / basic
have now tried everything, succeeds b513 , no Wi-Fi .
TWRP restore does not work , not even the hard reset method 3 buttons. So now I hate or just say ........
how do I go back to square all the way ....
so just , I screwed up , now back to start again .
I really can not find anywhere .
dead to alive .
help please
I back to stock b331 from b513. Tomorrow I write you how do it. You'll must have unlck code to bootloader. If dont have I can't help you
Why twrp not work???
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
here you have the guide how back to b331 stock ---> http://forum.xda-developers.com/showpost.php?p=65371195&postcount=207
Does not work for me, I tried everything.
This http://forum.xda-developers.com/mate-7/general/tried-to-roll-b511-to-b326-fail-try-t3302479 and this http://forum.xda-developers.com/showpost.php?p=65371195&postcount=207 . but still no luck.
am with TWRP returned to B513
B511 works also.
I can in the fastboot
I can in the TWRP
when I try now I get FAILED <remote: command not allowed>
Now I do not know what to do.
B513 works fine, but I have no WIFI, Blutooth and GPS
You have locked bootloader but you see your bootloader it's unlock
Unlock bootloader with you code
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
This works thanks Unlock bootloader with you code
chudy_85 said:
You have locked bootloader but you see your bootloader it's unlock
Unlock bootloader with you code
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
Click to expand...
Click to collapse
fastboot reboot
jpmaas said:
fastboot reboot
Click to expand...
Click to collapse
what you meen ???
chudy_85 said:
what you meen ???
Click to expand...
Click to collapse
Nothig I made a clerical error and accidental post quick repley
chudy_85 said:
here you have the guide how back to b331 stock ---> http://forum.xda-developers.com/showpost.php?p=65371195&postcount=207
Click to expand...
Click to collapse
it worked but had to unlock several times bootloader.
this was the main problem why it has not worked.
Thanks chudy_85
Yes I now and this process is to long but only one for now. Good work
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
Quite weird to hear, that Wifi, BT and GPS don't work, since I have B513 and everything works just fine, Wifi is fast, BT works with calls and other audio and GPS is accurate too. Only thing that keeps messing around since upgradeing it to B513, is Google Play, which gives me error "can't retrieve information from server" Is it just ROM-s fault or is it something about settings?
If your gp not work go to setting/aplication and find google framework services and clean data and cache then reboot fone.
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
Dear all,
My phone can boot on but reboot after 1 or 2 mins due to lost imei and baseband. It had worked till I updated to 6.0.1 (with firmware download from Sammobile) and run CF autoroot and many things more, sorry I cant remember whole process. My fault is not make EFS backup before doing anything.
It can boot into recovery (TWRP3.0.2) and download mode also. I know my imei, any chance for me to recover it back and make the phone work?
At least, any advice how to prevent it to reboot?
Many thanks,
Anyone using a g9280 phone could give me a working efs backup?? Thought it can help.
Try reflash new soft with odin 3 files
Wysłane z mojego SM-G928F przy użyciu Tapatalka
adiif1 said:
Try reflash new soft with odin 3 files
Wysłane z mojego SM-G928F przy użyciu Tapatalka
Click to expand...
Click to collapse
Flashed full stock rom (5 files) but not solved. Any advices? Thanks!
hi surisumi .... its not gona work like that....u need professional hand....u cant fix it only with computer.....search google there are many people providing these services....or visit any local shop....thnx
delete plx
OK I so I tried rooting my device with odin I have a galaxy s7 edge SM-G935T and everything went great it said passed, I used root.bat, everything It installed supersu for me and everything but when I went to root checker this showed up (look at screen shot) I have another picture also of my device saying my phone is rooted (look at picture)
So is my device rooted or not I can't use any of the rooted apps or anything.
Soooo noo ;d use cf autoroot - best solution and disable rom encryption
Wysłane z mojego SM-G935F przy użyciu Tapatalka
sebusmen69 said:
Soooo noo ;d use cf autoroot - best solution and disable rom encryption
Wysłane z mojego SM-G935F przy użyciu Tapatalka
Click to expand...
Click to collapse
I tried using cf autoroot but it just says fail
Hi!
I'm currently on Xiaomi EU beta, MIUI 11, android 10. I'm going to sell this phone and want to go back to stock global and then locked bootloader. I need some help. Tried downloading xiaomi flash tool, but I get an error message when trying to install drivers. Can I just flash the fastboot image of MIUI 10 global stable? Or will there be any rollback problems? Can I flash the .zip in the chinese TWRP?
Hoping for some answers. thanks
joakimbo said:
Hi!
I need some help. Tried downloading xiaomi flash tool, but I get an error message when trying to install drivers.
Click to expand...
Click to collapse
Try to execute as administrator this tool.
joakimbo said:
Can I just flash the fastboot image of MIUI 10 global stable? Or will there be any rollback problems? Can I flash the .zip in the chinese TWRP?
Click to expand...
Click to collapse
You can try to flash "Recovery" ROM image and flash it via TWRP yes.
Micdu70 said:
Try to execute as administrator this tool.
You can try to flash "Recovery" ROM image and flash it via TWRP yes.
Click to expand...
Click to collapse
I tried to run it as administrator. Still the same error. It wouldn't be a problem downgrading from miui 11 to miui 10 just by flashing zip?
joakimbo said:
I tried to run it as administrator. Still the same error. It wouldn't be a problem downgrading from miui 11 to miui 10 just by flashing zip?
Click to expand...
Click to collapse
I can't tell you if it will work without issue... I think the best solution is using "Fastboot" method.
Be careful not to trigger Anti RollBack protection (ARB) when downgrading, this could brick your smartphone.
valentind.44 said:
Be careful not to trigger Anti RollBack protection (ARB) when downgrading, this could brick your smartphone.
Click to expand...
Click to collapse
Ye, that's what I'm afraid of.. But what if I use the xiaomi tool and flash the fastboot image?
joakimbo said:
Ye, that's what I'm afraid of.. But what if I use the xiaomi tool and flash the fastboot image?
Click to expand...
Click to collapse
Ah yes it seems that if you flash through xiaomi tool or fastboot there is a check before flashing the ROM that can be rejected if the RollBack index is incompatible. Just avoid flashing an older miui version from TWRP, or check the RollBack index before. https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/
valentind.44 said:
Be careful not to trigger Anti RollBack protection (ARB) when downgrading, this could brick your smartphone.
Click to expand...
Click to collapse
Wtf? MIUI 10 and 11 have the same ARB version. What "brick" are you writing about?
Wysłane z mojego Redmi K20 przy użyciu Tapatalka
Antyhaker said:
Wtf? MIUI 10 and 11 have the same ARB version. What "brick" are you writing about?
Wysłane z mojego Redmi K20 przy użyciu Tapatalka
Click to expand...
Click to collapse
I didn't know they had the same ARB version, but I just wanted to warn, you have to be very careful when performing a downgrade. If I had to downgrade, I would check the ARB index just to be safe. There have been devices bricked before because of ARB on Xiaomi devices according to this article https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/ and others. Better safe than sorry.
valentind.44 said:
I didn't know they had the same ARB version, but I just wanted to warn, you have to be very careful when performing a downgrade. If I had to downgrade, I would check the ARB index just to be safe. There have been devices bricked before because of ARB on Xiaomi devices according to this article https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/ and others. Better safe than sorry.
Click to expand...
Click to collapse
You didn't know, but you are the first to give advice
Wysłane z mojego Redmi K20 przy użyciu Tapatalka
Antyhaker said:
You didn't know, but you are the first to give advice
Wysłane z mojego Redmi K20 przy użyciu Tapatalka
Click to expand...
Click to collapse
I never pretended to know whether the ARB index was different or not, I just said it would be a good idea to check. Thanks for bringing your huge knowledge in and giving us more information!
valentind.44 said:
I never pretended to know whether the ARB index was different or not, I just said it would be a good idea to check. Thanks for bringing your huge knowledge in and giving us more information!
Click to expand...
Click to collapse
Np
Wysłane z mojego Redmi K20 przy użyciu Tapatalka
i want to revert to davinciin_in_global_images_V11.0.3.0.QFJINXM_20200 406.0000.00_10
Antyhaker said:
Np
Wysłane z mojego Redmi K20 przy użyciu Tapatalka
Click to expand...
Click to collapse
currently, I am on miui mix and my ARB index is "1" whereas the fastboot rom I have has ARB of "0". Is it safe to flash fastboot rom ?