Related
Hi,
Im using "fastboot boot [name].img" to test the kernels before flashing.
It successfully transfer it and boots, but its stuck at the Google logo.
Code:
C:\android-sdk\platform-tools>fastboot boot gnex_uv.img
downloading 'boot.img'...
OKAY [ 0.439s]
booting...
OKAY [ 0.283s]
finished. total time: 0.722s
Am I doing something wrong, or is it a bug?
That isn't enough. You have to set some paths like where is system partition as well as init and what's the type(format) of system partition.
Sent from my IDEOS S7 Slim using XDA App
Jon2555 said:
That isn't enough. You have to set some paths like where is system partition as well as init and what's the type(format) of system partition.
Sent from my IDEOS S7 Slim using XDA App
Click to expand...
Click to collapse
Thanks, but how about when I try to flash via recovery or ROM Manager? Still the same thing.
i am pretty sur you gotta get
C:\android-sdk\platform-tools>fastboot FLASH boot gnex_uv.img
freebordjunky said:
i am pretty sur you gotta get
C:\android-sdk\platform-tools>fastboot FLASH boot gnex_uv.img
Click to expand...
Click to collapse
But the "boot" command lets me test out the kernel before flashing, or am I completely wrong?
no thats right you didnt say that you just wanted to test them first
forget that you did lol sorry
Hemulen said:
Hi,
Im using "fastboot boot [name].img" to test the kernels before flashing.
It successfully transfer it and boots, but its stuck at the Google logo.
Code:
C:\android-sdk\platform-tools>fastboot boot gnex_uv.img
downloading 'boot.img'...
OKAY [ 0.439s]
booting...
OKAY [ 0.283s]
finished. total time: 0.722s
Am I doing something wrong, or is it a bug?
Click to expand...
Click to collapse
Be aware of the android version of your rom and the kernel you are trying to boot. For instance, Franco's kernel will not boot below android 4.0.3.
flakz0r said:
Be aware of the android version of your rom and the kernel you are trying to boot. For instance, Franco's kernel will not boot below android 4.0.3.
Click to expand...
Click to collapse
I'm aware of that, but this is happening for all kernels.
Franco's, Matr1x and the 1.4GHz overclock + Undervolting kernel.
What ROM are you using? Is it an IML74K (4.0.3) one?
white lie said:
What ROM are you using? Is it an IML74K (4.0.3) one?
Click to expand...
Click to collapse
No, Im using a 4.0.2 ROM (Android Revolution 2.1.1)
I know some of the kernels are 4.0.3 compatible only, but all of them
Anything built from the 4.0.3 kernel source will require a 4.0.3 ROM.
DON'T INSTALL THIS (MANUALLY OR FLASHING)!! Stickman got a bootloop after manual write of the recovery
I just builded a test version with the CWM builder, here is the download link: http://jenkins.cyanogenmod.com/job/recovery/35056/
Personally, i would try the inputrecovery.img cause it has the same size as the original recovery
Good luck
Stickman89 said:
I've built CWM from CM sources. Haven't tried it as of yet though.
Flash at your OWN risk. I will not take responsibility for any actions taken by the user in combination with the provided file... By downloading this image your accepting full liability for any issues that should arise as a result of undergoing ANY flashing/modding on YOUR device.
Click to expand...
Click to collapse
All the credits go to Stickman89 | Thank you for the port
Thank him here: http://forum.xda-developers.com/showthread.php?p=44545580
HOW TO FLASH
-Connect your device in MTP mode
-Enable USB Debuggin
-Open a terminal and navigate to recovery.img's location
-adb reboot-bootloader
-fastboot flash recovery recovery.img
-fastboot reboot
-Done!
To boot into recovery: adb reboot-recovery
This recovery haven't been tested, we don't know acurately if it work (or if the bootloader is fully unlocked), flashing this can BRICK your phone
FYI...
Code:
adb reboot recovery
This will allow you to boot into the stock recovery before you've even flashed a thing. The bootloader is the screen with the static Huawei Logo, therefore I'm pretty certain that this is going to have a very little outcome of disaster since we could still get back into bootloader and/or boot into the ROM.
In any case we perform the below to create a backup recovery.img before doing anything like so:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/BackupRecovery.img
Before beginning first we need to obtain the dumped "BackupRecovery.img" located on your sdcard as can be seen from the above command.
Copy it onto your machine where your fastboot binaries coincide. Then should you need to restore, you'd need to perform the below:
Code:
adb reboot bootloader
Code:
fastboot flash recovery BackupRecovery.img
Code:
fastboot reboot
If I try just to boot it:
Code:
$ sudo fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.310s]
booting...
FAILED (remote: invalid command)
finished. total time: 0.311s
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recove
y recovery.img
target reported max download size of 838860800 bytes
sending 'recovery' (6816 KB)...
OKAY [ 0.194s]
writing 'recovery'...
[B]FAILED (remote: flash failure, ErrNo:2)[/B]
finished. total time: 0.200s
Yeah our bootloader sucks, I tried... No harm caused whatsoever.
Best Regards,
s89
I'm going to try flashing it through stock recovery as an update.zip.
Try a flash all, flash origial B107 boot, efi, modem and after that, recovery. When i get my laptop, i'll explain it better
Sent from my HUAWEI P6-U06 using xda app-developers app
Stickman89 said:
I'm going to try flashing it through stock recovery as an update.zip.
Click to expand...
Click to collapse
How's work? . We are nervous and excited. Thank champion.
Stickman and me are searching an alternative method to get the recovery in a secondary partition, keep reading this forum for more info
Sent from my HUAWEI P6-U06 using xda app-developers app
For now I urge all people to not flash the provided recovery.img for the time being whilst we are investigating a safer alternative for implementing CWM for our device. Please be patient in the meantime, thankyou.
Added a version builded with CWM, inputrecovery.img have the same size of the original recovery so it should work, as usual, flash etc etc at our own risk
Haven't seen any updates on this, does it work?
It won't work until huawei release a tool to sign the UPDATE.APP.
I'm sorry
Sent from my HUAWEI P6-U06 using xda app-developers app
S34Qu4K3 said:
It won't work until huawei release a tool to sign the UPDATE.APP.
I'm sorry
Sent from my HUAWEI P6-U06 using xda app-developers app
Click to expand...
Click to collapse
Understandable, thanks for the reply. Makes me want to see this and just get device that's fully unlocked with 3rd party ROM support. =(
S34Qu4K3 said:
flashing this can BRICK your phone
Click to expand...
Click to collapse
so why u putting it here u mento ..
Yeah, if it's not working don't upload it here. When you make something that's working, upload, everyone who is developing here must upload only working 100 % stuff, not unstable stuff that can brick people's phones.
HUAWEIAscendP6 said:
Yeah, if it's not working don't upload it here. When you make something that's working, upload, everyone who is developing here must upload only working 100 % stuff, not unstable stuff that can brick people's phones.
Click to expand...
Click to collapse
You're wrong, we need those devs, who contribute.
With our Phone we have the Problem, that we only can flash unsigned things on B118CN.
So we can only start real developing with this Firmware.
Or at least a other firmware without signing-check.
Users must read before they flash something. Everything with isn't functioning correctly (at this point) shows visible that it can brick our device.
Without testing-builds there will be no working builds!
raolleel said:
You're wrong, we need those devs, who contribute.
With our Phone we have the Problem, that we only can flash unsigned things on B118CN.
So we can only start real developing with this Firmware.
Or at least a other firmware without signing-check.
Users must read before they flash something. Everything with isn't functioning correctly (at this point) shows visible that it can brick our device.
Without testing-builds there will be no working builds!
Click to expand...
Click to collapse
Maybe devs should do tests on their own phones.
HUAWEIAscendP6 said:
Maybe devs should do test on their own phones.
Click to expand...
Click to collapse
I don't know why you are so mean, and you don't understand testing builds.
Even if a build doesn't work, even if there are bugs we should contribute our builds.
The community can help to erase the bugs, everyone can contribute to those projects.
Keep in mind building Roms, Kernels, Mods isn't easy, it needs very much time and concentration.
We don't get any money, we all do this to contribute to the community.
Devs help each other, to erase bugs.
Not everyone can test the builds, maybe they don't have the phone, maybe their phone is in rapair or something.
People like you are those, who should think before they post.
You get our stuff for fee. So say thank you, and don't comment on them, cause there are not bugfree.
HUAWEIAscendP6 said:
Maybe devs should do test on their own phones.
Click to expand...
Click to collapse
We do Test things prior to uploading and sharing, BUT we can't control what the user (the rest of the community) will do with what we share. If you utilize wrong commands to flash a kernel, recovery or whatever then it will not be Developer's fault. That's the reason for the big bold warning at the beginning of each development thread.
And last for not least, The developer is not FORCING you to test something that can brick your phone, it is up to you and it'll be your responsability if the phone bricks.
I've seen your posts, and most of the time you keep complaining about the phone, about a ROM, a recovery etc... If you don't like it sell it and if this or that doesn't work for you don't use it.
Just my 2 cents...
jimbo77 said:
We do Test things prior to uploading and sharing, BUT we can't control what the user (the rest of the community) will do with what we share. If you utilize wrong commands to flash a kernel, recovery or whatever then it will not be Developer's fault. That's the reason for the big bold warning at the beginning of each development thread.
And last for not least, The developer is not FORCING you to test something that can brick your phone, it is up to you and it'll be your responsability if the phone bricks.
I've seen your posts, and most of the time you keep complaining about the phone, about a ROM, a recovery etc... If you don't like it sell it and if this or that doesn't work for you don't use it.
Just my 2 cents...
Click to expand...
Click to collapse
I don't know what posts you saw, but show me one post in which I complain about the phone.
Unlocked my bootloader with ease dont this many times in the past. Problem i have now is after i install ClockWorkMod and try get into recovery it just freezes.
Sticks on htc screen saying entering recovery.
Any help appreciated.
If it helps im still on stock rom Android version 5.0.2
Nevermind i have managed to fix it.
Hi Junior, What do you do to fix it. because I'm with the same problem.
After upload the "twrp3.0.0.1.img" I select the Recovery, but nothing happen the Phone does not restart in TWRP graphic mode.
phone: HTC M8 - Unlocked
C:\>fastboot devices
FA56JYS01352 fastboot
C:\>fastboot erase cache
erasing 'cache'...
OKAY 0.023s
finished. total time: 0.023s
C:\>fastboot flash recovery twrp-3.0.0-1-m8.img
sending 'recovery' (20022 KB)...
OKAY 2.068s
writing 'recovery'...
OKAY 0.586s
finished. total time: 2.655
kruivo said:
After upload the "twrp3.0.0.1.img" I select the Recovery, but nothing happen the Phone does not restart in TWRP graphic mode.
Click to expand...
Click to collapse
Try to wipe cache again, and install TWRP 3.0.0.0. The version 3.0.0.1 is really new, so maybe there are some issues.
I believe it is another issue...
redpoint73 said:
Try to wipe cache again, and install TWRP 3.0.0.0. The version 3.0.0.1 is really new, so maybe there are some issues.
Click to expand...
Click to collapse
I've tried with all the images below:
twrp-2.7.0.1-m8
twrp-2.7.0.2-m8
twrp-2.8.5.0-m8
and the problem is the same... after upload the recover image, I select RECOVERY in my phone but nothing happen
You might want to give HTC-fastboot.exe a try. I've had troubles flashing the recovery as well with the standard ADB toolset.
You should be ablo to find the HTC fastboot utility somewhere around here
kruivo said:
I've tried with all the images below:
twrp-2.7.0.1-m8
twrp-2.7.0.2-m8
twrp-2.8.5.0-m8
and the problem is the same... after upload the recover image, I select RECOVERY in my phone but nothing happen
Click to expand...
Click to collapse
Pretty sure TWRMP version 2.7 are known to cause problems with Android 5 or later; and not booting into recovery is the known result. TWRP 2.8.5 might be okay, but I'm not sure. I'd try 2.8.7 or (as I already mentioned) 3.0.0.0.
redpoint73 said:
Pretty sure TWRMP version 2.7 are known to cause problems with Android 5 or later; and not booting into recovery is the known result. TWRP 2.8.5 might be okay, but I'm not sure. I'd try 2.8.7 or (as I already mentioned) 3.0.0.0.
Click to expand...
Click to collapse
I tried almost everything, now I will try via Linux.
because via adb I did not get hit "device not found" (tried all drives and nothing happened) only via fastboot I got connection. I believe I first need to remove the S-ON.
kruivo said:
I tried almost everything, now
Click to expand...
Click to collapse
But did you try what I told you to? Meaning TWRP 2.8.7 or 3.0.0?
"I tried everything" doesn't tell us what you actually did or did not do.
kruivo said:
because via adb I did not get hit "device not found" (tried all drives and nothing happened) only via fastboot I got connection.
Click to expand...
Click to collapse
Doesn't matter, since fastboot is what you need for installing TWRP.
kruivo said:
I believe I first need to remove the S-ON.
Click to expand...
Click to collapse
Why do you think that? Folks always jump to the conclusion that s-off is the magical answer to all their problems. S-off doesn't have any bearing on the ability to install custom recovery, or whether you can connect to adb or not.
Waste $25 is you want (as sunshine is the only working s-off method), but it won't solve your problem.
redpoint73 said:
But did you try what I told you to? Meaning TWRP 2.8.7 or 3.0.0?
"I tried everything" doesn't tell us what you actually did or did not do.
Doesn't matter, since fastboot is what you need for installing TWRP.
Why do you think that? Folks always jump to the conclusion that s-off is the magical answer to all their problems. S-off doesn't have any bearing on the ability to install custom recovery, or whether you can connect to adb or not.
Waste $25 is you want (as sunshine is the only working s-off method), but it won't solve your problem.
Click to expand...
Click to collapse
Yes, I tryed 2.8.7 and 3.0.0, but dosen't work. After select RECOVEY , the phone vibrates and nothing happens, forcing a physical reboot it gets stuck on the HTC home screen.
Do fastboot getvar all, and post the output (delete IMEI and serial number before posting) so we can see more info about the device.
Something else is going on here.
Here is a bugless version of TWRP by @Zormax
Full tutorial to unlock bootloader and install TWRPDownload ADB/Fastboot tool and extract it. Make sure you have installed ADB/FASTBOOT drivers on your PC (Google it for this)
Press Shift button and right click in extracted ADB tool's folder
Open command window there
Enable Developer option by clicking 5-6 times on build no.
go to the Developer Option and enale USB debugging and OEM unlock
connect your device to PC
then type these commands:
Code:
adb reboot bootloader
fastboot oem unlock
fastboot reboot
Now your bootloder is unlocked
For flash TWRP:
Code:
adb reboot bootloader
fastboot flash recovery recoveryE4plus.img
fastboot flash boot boot_NMA26.42-97.img
fastboot reboot
Done
then flash phh's superuser to root your phone
TWRP: Click Here
Boot: Click Here
Source
Credits: Zormax
Continues with stock recovery here, XT1773.
I want to root my e4 plus to use Substratum themes but I'm tensed what if I get boot loop there is no stock rom to recover device, Can anybody upload back up of Stock rom from TWRP, So if there is anything wrong I can use back my device is XT1770.
So many Stock rom requests already still there is no availability
SHadYreBOrN said:
So many Stock rom requests already still there is no availability
Click to expand...
Click to collapse
http://www.mediafire.com/file/zbjpsoi6wlfyorm/MOTOROLA_EPLUS_NMA26.42-75_ROW.7z
here is a stock rom
you can flash through sp tool as well
akash_eric said:
http://www.mediafire.com/file/zbjpsoi6wlfyorm/MOTOROLA_EPLUS_NMA26.42-75_ROW.7z
here is a stock rom
you can flash through sp tool as well
Click to expand...
Click to collapse
Can I flash it on E4 plus XT1770 model ??
sandeep chauhan 2722 said:
Can I flash it on E4 plus XT1770 model ??
Click to expand...
Click to collapse
ye u can
its for moto e4 plus - mt6737
sandeep chauhan 2722 said:
Can I flash it on E4 plus XT1770 model ??
Click to expand...
Click to collapse
follow this ! https://forum.xda-developers.com/moto-e4/how-to/how-to-backup-stock-rom-moto-e4-variants-t3654976 applies to both moto e4 and plus.
the boot.img just bricked my phone.... be careful
---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------
log says failed to load kernel also have no recovery twrp that is
neilc300 said:
the boot.img just bricked my phone.... be careful
---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------
log says failed to load kernel also have no recovery twrp that is
Click to expand...
Click to collapse
it is because of dm-verity
Is this for the Snapdragon/Qualcomm version?
Specifically model xt1775
soaringowl2145 said:
Is this for the Snapdragon/Qualcomm version?
Specifically model xt1775
Click to expand...
Click to collapse
nope.
its for mediatek (menitioned in OP)
Francesco Franz said:
nope.
its for mediatek (menitioned in OP)
Click to expand...
Click to collapse
Do you know what it will take to get twrp on the device I mentioned then?
soaringowl2145 said:
Do you know what it will take to get twrp on the device I mentioned then?
Click to expand...
Click to collapse
upload your device recovery and boot image here. i will make twrp for your device.
Didnt work for me, my screen stays black when i try to boot on recovery. xt1773. Then i have to keep pressing power button for 10+ seconds to reboot.
Any help ?
downloadkct said:
Didnt work for me, my screen stays black when i try to boot on recovery. xt1773. Then i have to keep pressing power button for 10+ seconds to reboot.
Any help ?
Click to expand...
Click to collapse
Try this fastboot erase recovery (erase stock recovery)
than flash new recovery
fastboot flash recovery twrp.img
Francesco Franz said:
Try this fastboot erase recovery (erase stock recovery)
than flash new recovery
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Thanks for your answer but ill wait for a better method. This made my phone hardbrick, i was lucky to recovery it using SP
downloadkct said:
Didnt work for me, my screen stays black when i try to boot on recovery. xt1773. Then i have to keep pressing power button for 10+ seconds to reboot.
Any help ?
Click to expand...
Click to collapse
*black screen*
may be twrp recovery doesn't support your device.
Francesco Franz said:
may be twrp recovery doesn't support your device.
Click to expand...
Click to collapse
Most likely, im not the only one saying it didnt work on xt1773
@Francesco Franz mate, after flashing the TWRP on my XT1770 I get also just a black screen when I try to boot into the recovery mode. Could it be, that the .img file is just sligtly too big? I get an output:
Code:
# fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (13426 KB)...
OKAY [ 0.559s]
writing 'recovery'...
OKAY [ 0.315s]
finished. total time: 0.874s
(my ubuntu PC)# fastboot reboot
rebooting...
finished. total time: 0.053s
I can normally reboot the phone into its Android OS
I am a noob in flashing recoveries and ROMs. yesterday, I rooted my Note 5 pro .
Here's what I did:
1) Unlocked Bootloader
2) booted to TWRP through adb
3) Flashed TWRP to Recovery
4) Installed Magisk
now, the phone was correctly rooted and working perfectly.
what I did wrong, is that I installed Xposed framework through magisk and chose the wrong API. The phone was stuck at boot sequence. I tried pressing the poweer button repeatedly, Sideloading Xposed Disabler, Even uninstalled magisk through TWRP. still the device won't boot up!
so I downloaded the Stock ROM and extracted the boot.img, and flashed it to boot through TWRP. The phone booted up fine,but I ended up losing TWRP, Magisk, and now, I am unable to boot TWRP through ADB. it gives this error message:
downloading 'boot.img'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I think I flashed the locked boot file. but my rom thinks that the bootloader is unlocked.
any idea what's going on?
Update 1:
Arslanahmad556 gave link to a video : https://youtu.be/em4SdLK6PBo according to which I should download the fastboot ROM for my device and use "flash_all_lock.bat" to flash stock ROM through fastboot and lock my bootloader again. Please tell me,
1) Can this cause my deice to brick because of any error like "downloading 'boot.img'... FAILED (command write failed (Invalid argument))" error or some other error?
2) Can I unlock the bootloader and root the phone again if I use this method?
3) How safe is this method? or how much a chance of failure is there?
Update 2:
I flashed fastboot rom for my device with XiaoMiFlash, then repeated the entire root process and now my device is rooted and working in all it's glory.
thank you @Nitin890 , @Arslanahmad556 and @ashok99511 for helping out!
Did your device booting into fastboot mode? If yes then i can suggest you one video that helps me too so tell me
Yes it is booting in fastboot mode.
brmediawks said:
I am a noob in flashing recoveries and ROMs. yesterday, I rooted my Note 5 pro .
Here's what I did:
1) Unlocked Bootloader
2) booted to TWRP through adb
3) Flashed TWRP to Recovery
4) Installed Magisk
now, the phone was correctly rooted and working perfectly.
what I did wrong, is that I installed Xposed framework through magisk and chose the wrong API. The phone was stuck at boot sequence. I tried pressing the poweer button repeatedly, Sideloading Xposed Disabler, Even uninstalled magisk through TWRP. still the device won't boot up!
so I downloaded the Stock ROM and extracted the boot.img, and flashed it to boot through TWRP. The phone booted up fine,but I ended up losing TWRP, Magisk, and now, I am unable to boot TWRP through ADB. it gives this error message:
downloading 'boot.img'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I think I flashed the locked boot file. but my rom thinks that the bootloader is unlocked.
any idea what's going on?
Click to expand...
Click to collapse
Bro you did wrong...
Even if you can't boot you have a solution...
Okay right now you have to install again twrp & magisk...
Before that you have to wipe dalvik cache, cache,data,system data,vendor data this 5 are most imp
ashok99511 said:
Bro you did wrong...
Even if you can't boot you have a solution...
Okay right now you have to install again twrp & magisk...
Before that you have to wipe dalvik cache, cache,data,system data,vendor data this 5 are most imp
Click to expand...
Click to collapse
Thank you so much for your reply. but as I mentioned, I am an absolute noob in this. So would you please explain how can I do all this? I know it's kind of pain in A$$ but I really need it!
Also, are you sure it will solve the problem? Coz I'm trying not to brick it again! ?
I am using a Redmi Note 5 pro (whyred) on Oreo 8.1
If u don't want to get deep just flash stock rom through fastboot and then all will work
https://youtu.be/em4SdLK6PBo
Watch this video its in hindi language , but you can flash stock rom via fastboot good luck
Arslanahmad556 said:
https://youtu.be/em4SdLK6PBo
Watch this video its in hindi language , but you can flash stock rom via fastboot good luck
Click to expand...
Click to collapse
thank you bro. but are you sure it won't brick my device because of the "downloading 'boot.img'... FAILED (command write failed (Invalid argument))" error?
When my device got soft bricked it worked for me even that time my phone touch is not working so im pretty sure it will work , other then that wait for any other expert ,
Just a li'l more help...
Nitin890 said:
If u don't want to get deep just flash stock rom through fastboot and then all will work
Click to expand...
Click to collapse
thanks for replying bro!
Arslanahmad556 gave link to a video : https://youtu.be/em4SdLK6PBo according to which I should download the fastboot ROM for my device and use "flash_all_lock.bat" or "flash_all.bat" to flash stock ROM through fastboot and lock my bootloader again. Please tell me,
1)Which one should I use: flash_all_lock or flash_all or flash_all_lock_crc?
2) Can this cause my deice to brick because of any error like "downloading 'boot.img'... FAILED (command write failed (Invalid argument))" error or some other error?
3) Can I unlock the bootloader and root the phone again if I use this method?
4) How safe is this method? or how much a chance of failure is there?
brmediawks said:
thanks for replying bro!
Arslanahmad556 gave link to a video : https://youtu.be/em4SdLK6PBo according to which I should download the fastboot ROM for my device and use "flash_all_lock.bat" or "flash_all.bat" to flash stock ROM through fastboot and lock my bootloader again. Please tell me,
1)Which one should I use: flash_all_lock or flash_all or flash_all_lock_crc?
2) Can this cause my deice to brick because of any error like "downloading 'boot.img'... FAILED (command write failed (Invalid argument))" error or some other error?
3) Can I unlock the bootloader and root the phone again if I use this method?
4) How safe is this method? or how much a chance of failure is there?
Click to expand...
Click to collapse
There are somethings that you should keep in mind while flashing on ARB active device like whyred
1. Always flash latest beta or stable fastboot rom.
2.If you want to lock your bootloader then select Flash_all_lock
If you want to stay unlocked and at the same time want to clean flash Rom then select
Flash_all
If you want save data but want to flash fastboot rom then click on save data option(Not recommended).
3.always Use mi flash software to flash. Never ever try to experiment own commands on CMD.
4.if you follow above steps then this method is safe.
Nitin890 said:
There are somethings that you should keep in mind while flashing on ARB active device like whyred
1. Always flash latest beta or stable fastboot rom.
2.If you want to lock your bootloader then select Flash_all_lock
If you want to stay unlocked and at the same time want to clean flash Rom then select
Flash_all
If you want save data but want to flash fastboot rom then click on save data option(Not recommended).
3.always Use mi flash software to flash. Never ever try to experiment own commands on CMD.
4.if you follow above steps then this method is safe.
Click to expand...
Click to collapse
Bro I have encountered another problem. I have lost connectivity to my Idea Sim network on my device. It is working in other phones. Other network Sim cards are working in this device
Do you, by any means, happen to know if it is caused by rooting my note 5 pro?
Also, I have an OTA update pending. When I reboot for updating, it boots into TWRP and update fails. Any solution?
brmediawks said:
Bro I have encountered another problem. I have lost connectivity to my Idea Sim network on my device. It is working in other phones. Other network Sim cards are working in this device
Do you, by any means, happen to know if it is caused by rooting my note 5 pro?
Also, I have an OTA update pending. When I reboot for updating, it boots into TWRP and update fails. Any solution?
Click to expand...
Click to collapse
The sim network problem is software one and nothing to do with rooting if it is through magisk.
Also,You Can't update official Miui through twrp so if you want to update it then go back to official Miui recovery by flashing recovery. img through twrp.
I hope this is True and work.