[Patched_Boot.img]
https://1drv.ms/u/s!AqlJY73bUA7rholGl4AULW_tHKaCrg
https://mega.nz/#!NUBmnawT!Pgrorx3HWBjPjv_DjeQZVN76VnwzqT1cn0u1U0MzgSA
[TWRP Backup Boot.img]
https://1drv.ms/u/s!AqlJY73bUA7rholRaoTR_Nvxq7v6kw
https://mega.nz/#!0EZkXSDB!WYcB8wt1Eu92GZvVTExeaWRN9y1zQBLOjULCuKRHvR8
[Boot.img]
https://1drv.ms/u/s!AqlJY73bUA7rholJT3zo4rEY9oO0lQ
https://mega.nz/#!URYmHIxZ!i77uZQZ2V0aWBRNewxLY1UJPPhuhg2wicowDQMVETo4
Be careful as Always, only use this img for booting so you can install magisk direct.
To restore your boot image with trwp:
Unzip twrp and add to root of the sdcard,
fastboot boot twrp daisy zero(sdcard fixed version) and restore trwp backup, don't touch anything else, and reboot by holding power button.
Fastboot boot patched_boot.img to boot phone for direct install of magisk. ALWAYS RECOMENDED.
thanks a lot, can you provide also an unmodified 10.30.0 boot image?
Yep, a non patched would be also useful. Which Magisk version did you use to patch the image?
Still bootlooping after flashing it.
fastboot boot patched_boot.img
fastboot reboot
pippozio said:
thanks a lot, can you provide also an unmodified 10.30.0 boot image?
Click to expand...
Click to collapse
I can provide an unmodified trwp made boot.img from my phone, thats why i said not to flash the patched boot image, and to only boot from it, twrp backups are .wim, i just changed the .wim extension to .img and patched it. As far as im aware its a normal packed boot.img but renamed .wim for trwp to flash it, ill provide it but use at own risk. https://1drv.ms/u/s!AqlJY73bUA7rholIeKoHAB8o6s94gA .Rename boot.img if your going to flash it.
anzhaki said:
Yep, a non patched would be also useful. Which Magisk version did you use to patch the image?
Still bootlooping after flashing it.
fastboot boot patched_boot.img
fastboot reboot
Click to expand...
Click to collapse
I used magisk v18 latest. Unmodified boot.img is in one of the posts. Ive used it so it should be fine, but still its done at your own risk. Im not sure how you will stop it bootlooping, sounds like magisk messed up the install when re applying after OTA.
anzhaki said:
Yep, a non patched would be also useful. Which Magisk version did you use to patch the image?
Still bootlooping after flashing it.
fastboot boot patched_boot.img
fastboot reboot
Click to expand...
Click to collapse
Dont fastboot reboot, just boot from it, if your rebooting then your wiping the temp boot.
boe323 said:
I used magisk v18 latest. Unmodified boot.img is in one of the posts. Ive used it so it should be fine, but still its done at your own risk. Im not sure how you will stop it bootlooping, sounds like magisk messed up the install when re applying after OTA.
Click to expand...
Click to collapse
The same thing happened when I updated from oreo to pie using the method to maintain root. If I remember well I solved the problem by flashing stock boot.img with
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
then it should normally boot and after that it should be ok to manually patch the boot image.
Maybe it's better to wait an image extracted from OTA
Thanks anyway
---------- Post added at 12:54 AM ---------- Previous post was at 12:51 AM ----------
boe323 said:
Dont fastboot reboot, just boot from it, if your rebooting then your wiping the temp boot.
Click to expand...
Click to collapse
Unfortunately still bootloops D:
anzhaki said:
The same thing happened when I updated from oreo to pie using the method to maintain root. If I remember well I solved the problem by flashing stock boot.img with
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
then it should normally boot and after that it should be ok to manually patch the boot image.
Maybe it's better to wait an image extracted from OTA
Thanks anyway
---------- Post added at 12:54 AM ---------- Previous post was at 12:51 AM ----------
Unfortunately still bootloops D:
Click to expand...
Click to collapse
Try anzhaki's method, he said it works but i cant confirm it as ive never run into problems (touch wood). Dont go making things worse by flashing custom stuff, try using his method and factory reset.
anzhaki said:
The same thing happened when I updated from oreo to pie using the method to maintain root. If I remember well I solved the problem by flashing stock boot.img with
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
then it should normally boot and after that it should be ok to manually patch the boot image.
Maybe it's better to wait an image extracted from OTA
Thanks anyway
---------- Post added at 12:54 AM ---------- Previous post was at 12:51 AM ----------
Unfortunately still bootloops D:
Click to expand...
Click to collapse
boe323 said:
Try anzhaki's method, he said it works but i cant confirm it as ive never run into problems (touch wood). Dont go making things worse by flashing custom stuff, try using his method and factory reset.
Click to expand...
Click to collapse
I m in bootloop. Anyone help me the pie fastboot image link? Thanks.
There isn't one for v10.0.30.0 at present .
boe323 said:
There isn't one for v10.0.30.0 at present .
Click to expand...
Click to collapse
your unmodified boot.img shows 64 mb, it should be 26-27 mb. no?
and can you upload it another server plz?
---------- Post added at 09:22 AM ---------- Previous post was at 09:09 AM ----------
Flashed your unmodified boot.img. no luck, still in bootloop.
Is there any inprovements with this ypdate
boe323 said:
[Patched_Boot.img]
https://1drv.ms/u/s!AqlJY73bUA7rholGl4AULW_tHKaCrg
[TWRP Backup Boot.img]
https://1drv.ms/u/s!AqlJY73bUA7rholRaoTR_Nvxq7v6kw
[Boot.img]
https://1drv.ms/u/s!AqlJY73bUA7rholJT3zo4rEY9oO0lQ
Be careful as Always, only use this img for booting so you can install magisk direct.
To restore your boot image with trwp:
Unzip twrp and add to root of the sdcard,
fastboot boot twrp daisy zero(sdcard fixed version) and restore trwp backup, don't touch anything else, and reboot by holding power button.
Fastboot boot patched_boot.img to boot phone for direct install of magisk. ALWAYS RECOMENDED.
Click to expand...
Click to collapse
thanks, this boot image solved my bootloop problem
pippozio said:
thanks, this boot image solved my bootloop problem
Click to expand...
Click to collapse
Hi, which one did you flash and with what command?
Nvm, I used the last one.
What is the procedure to update ota with magisk? Restore image with magisk, reboot, update ota and then flash modified boot.img?
Thx in advance.
Me tio want to update and when i see that people are having troubles. What is the correct procedure for this?
Please help me, im rooted at v10.0.2.0 but when i unsintall/revert my boot.img in magisk it say's "store backup does not exist" . i factory reset my phone when i got a problem in substratum . didn't know that it will be remove by doing that, what should i do next? i want to OTA update my Phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mms047 said:
your unmodified boot.img shows 64 mb, it should be 26-27 mb. no?
and can you upload it another server plz?
---------- Post added at 09:22 AM ---------- Previous post was at 09:09 AM ----------
Flashed your unmodified boot.img. no luck, still in bootloop.
Click to expand...
Click to collapse
No , original is bigger, only when you patch it ,it goes smaller, from other ppl who know about this stuff it's just padding
iniro said:
What is the procedure to update ota with magisk? Restore image with magisk, reboot, update ota and then flash modified boot.img?
Thx in advance.
Click to expand...
Click to collapse
I wouldnt try magisk ota method, theres reports of bootloops after OTA, best is to return everything to stock, disabale modules and reboot, uninstall modules and reboot, then uninstall magisk and reboot, any modded hosts need to be stock, audio/soundfx need to be stock, basically anything to do with system should be stock. If you get into any install issues with ota, then download the 10.0.20.0 rom from Mi's website and use flash all except storage, this will keep data and give you a fresh system image.
barumbads said:
Please help me, im rooted at v10.0.2.0 but when i unsintall/revert my boot.img in magisk it say's "store backup does not exist" . i factory reset my phone when i got a problem in substratum . didn't know that it will be remove by doing that, what should i do next? i want to OTA update my Phone.
Click to expand...
Click to collapse
Redo your system image with the rom on Mi's website, use flash all except storage.
Related
Welcome To Negalite HW TWRP Recovery!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features
lz4 Compression Algorithm - boot speed
f2fs Support
logging enabled(logcat)
fb2png - take screenshots within recovery
compiled using Uber Toolchains
compiled using Negalite HW kernel
many features enabled
Custom Theme
Downloads
Recovery Flashable! Flash From Within Your Current Custom Recovery
negalite-HW-TWRP-3.0.3-v1.5.zip - 1/09/17
Fastboot Flashable! Flash From Within Bootloader Using Fastboot
negalite-HW-TWRP-3.0.3-v1.5.img - 1/09/17
Device Source
https://github.com/Negamann303/omni_twrp_device
Reserved...
Nice. Thanks for your work man! I'll try this out and report back if I notice any issues. If you don't hear from me then it's all good!
Is f2fs only for cache, data, and internal storage? Or can it be used on system as well?
[update] I used the flash method and it's running good. Switched cache, data, and internal storage to f2fs and all is running well.
imucarmen said:
Nice. Thanks for your work man! I'll try this out and report back if I notice any issues. If you don't hear from me then it's all good!
Is f2fs only for cache, data, and internal storage? Or can it be used on system as well?
[update] I used the flash method and it's running good. Switched cache, data, and internal storage to f2fs and all is running well.
Click to expand...
Click to collapse
Good I set it up for system to do it as well, even though technically it would be pointless since system doesn't write files(unless you manually add to it or flash something to it) . I haven't tested it though
Sent from my SM-G935P using Tapatalk
Updated Recovery To The Latest 3.0.2-1!
I guess the restore bug may not be present in this watch's system due to no efs partition. I'm wondering if it does affect it at all since it does affect quite a few devices.
shag_on_e said:
I guess the restore bug may not be present in this watch's system due to no efs partition. I'm wondering if it does affect it at all since it does affect quite a few devices.
Click to expand...
Click to collapse
We are one commit past that issue, it was already fixed
Sent from my SM-G935P using Tapatalk
i get a red exclamation when i flash this recovery and then try to reboot into recovery. i am not sure what i am doing wrong. I flashed 2-3 times now with the same result. here is the command i am using
adb reboot bootloader
fastboot flash recovery negalite-HW-TWRP-3.0.2-v1.4.img
fastboot reboot
samjoandco said:
i get a red exclamation when i flash this recovery and then try to reboot into recovery. i am not sure what i am doing wrong. I flashed 2-3 times now with the same result. here is the command i am using
adb reboot bootloader
fastboot flash recovery negalite-HW-TWRP-3.0.2-v1.4.img
fastboot reboot
Click to expand...
Click to collapse
After you flash the recovery, boot to the normal watch running before you boot back to recovery, i *think* that is how I solved it, but it has been some time ago.
Pkt_Lnt said:
After you flash the recovery, boot to the normal watch running before you boot back to recovery, i *think* that is how I solved it, but it has been some time ago.
Click to expand...
Click to collapse
i tried this multiple times without success
samjoandco said:
i tried this multiple times without success
Click to expand...
Click to collapse
I had to do it about 8 times with the same problem.
Try flashing recovery then back to bootloader with
Code:
fastboot reboot-bootloader
Then manually reboot from the bootloader to recovery.
Sorry, I just don't remember how I solved it
while in bootloader mode, is fastboot boot negalite-HW-TWRP-3.0.2-v1.4.img working?
samjoandco said:
i get a red exclamation when i flash this recovery and then try to reboot into recovery. i am not sure what i am doing wrong. I flashed 2-3 times now with the same result. here is the command i am using
adb reboot bootloader
fastboot flash recovery negalite-HW-TWRP-3.0.2-v1.4.img
fastboot reboot
Click to expand...
Click to collapse
Your bootloader is unlocked?
gwolfu said:
while in bootloader mode, is fastboot boot negalite-HW-TWRP-3.0.2-v1.4.img working?
Click to expand...
Click to collapse
Success Finally
this command worked. i didnt even have to reboot; in am in TEAMWIN blue screen and everything works now
Thanks for helping me .
---------- Post added at 06:45 PM ---------- Previous post was at 06:31 PM ----------
samjoandco said:
Success Finally
this command worked. i didnt even have to reboot; in am in TEAMWIN blue screen and everything works now
Thanks for helping me .
Click to expand...
Click to collapse
back to the same red exclaimation mark after rebooting! and boot to recovery.
my bootloader is unlocked
samjoandco said:
Success Finally
this command worked. i didnt even have to reboot; in am in TEAMWIN blue screen and everything works now
Thanks for helping me .
---------- Post added at 06:45 PM ---------- Previous post was at 06:31 PM ----------
back to the same red exclaimation mark after rebooting! and boot to recovery.
my bootloader is unlocked
Click to expand...
Click to collapse
Fastboot boot temporarily loads the recovery.img. Try doing that then flashing the recovery zip within recovery. Quick workaround for you
Sent from my SM-G935P using Tapatalk
samjoandco said:
Success Finally
this command worked. i didnt even have to reboot; in am in TEAMWIN blue screen and everything works now
Thanks for helping me .
---------- Post added at 06:45 PM ---------- Previous post was at 06:31 PM ----------
back to the same red exclaimation mark after rebooting! and boot to recovery.
my bootloader is unlocked
Click to expand...
Click to collapse
download the recovery img boot in to bootloader fastboot flash recovery img.whit the hardver button navigate to reboot recovery tourn long and you will booted in twrp recovery
negamann303 said:
Fastboot boot temporarily loads the recovery.img. Try doing that then flashing the recovery zip within recovery. Quick workaround for you
Sent from my SM-G935P using Tapatalk
Click to expand...
Click to collapse
thanks this worked!
after trying for almost 24 hours, this worked fine. now i can go into recovery from ADB as well as from the reboot prompts within the watch. this is solved for good
negamann303 said:
Fastboot boot temporarily loads the recovery.img. Try doing that then flashing the recovery zip within recovery. Quick workaround for you
Sent from my SM-G935P using Tapatalk
Click to expand...
Click to collapse
yeas was about to suggest just that
well my idea was to boot in TWRP temporary to validate that the recovery image works and then flash it again from recovery
but heck negamann303 was faster then me on this
glad you made it work
Hey guys
Just got mine YEEEES
Is it possible to dualboot 1.5 & 2.0 via multiROM, dual-boot-scripts or magisk?
Thank you soo much
Cheers
Blade
Also, can I take backups of the current state, to revert to it later?
BIade said:
Hey guys
Just got mine YEEEES
Is it possible to dualboot 1.5 & 2.0 via multiROM, dual-boot-scripts or magisk?
Thank you soo much
Cheers
Blade
Also, can I take backups of the current state, to revert to it later?
Click to expand...
Click to collapse
No multirom for us yet. But you can do backup and restore!
BTW, luv Koln my last visit
Hello XDA, I am trying to figure out all the steps to get mainly Twrp, Magisk, Viper and, Substratum working correctly without any hiccups. I have been reading the forums all day and trying to get all the files necessary to get all that working and the files to revert to stock if it doesn't work. I know after the Bootloader is unlocked I won't be able to relock it due to no Moto signed boot images. I just don't want to brick it and be here with other problems later.
So far I have done the following
1. Installed ADB and Fastboot + Drivers
2. Done everything to get the code to unlock bootloader
3. Downloaded the files to flash twrp from (https://forum.xda-developers.com/z2-force/development/twrp-3-1-1-0-moto-z2-force-nash-t3687421)
4. Downloaded the latest stock NCX26.122-59-8 to extract the boot img and patch it with Magisk manager from (https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859)
I think I have everything I need to get it rooted. Here's where I get kinda confused. My phone (XT1789-03 Sprint) is on NCXS26.122-59-8-11 November patch (I think the S is for sprint lol). Would It be okay to flash the Magisk patched boot img from the one I downloaded after I unlock the bootloader? Is Twrp necessary? Is there anything else I need to know about? Thanks in advance.
This forum just died? What the hell noone helps anymore???
Sent from my XT1650 using Tapatalk
TWRP is official now. Download the bootable image from https://twrp.me/motorola/motorolamotoz2force.html and the corresponding zip. Boot to twrp and flash the zip. Flash Magisk and install what you want that needs root. Hint: I'd advise the Viper4Android from Magisk modules in the magisk app.
Uzephi said:
Boot to twrp and flash the zip.
Click to expand...
Click to collapse
What do you mean by this? Fastboot flash TWRP, but then flash what zip?
breakerfall said:
What do you mean by this? Fastboot flash TWRP, but then flash what zip?
Click to expand...
Click to collapse
Do NOT flash the twrp img. "Fastboot boot imagename.img" then flash the twrp zip if you wish to have it as your recovery. You can find both on twrp.me.
This hard.. even with instructions u don't know what to flash where and what it will achieve lol. I just want unlock and root. What's the easiest way to do that on sprint z2 force?
So far I understand u need to install twrp to root with magisk, then use twrp to flash magisk Img, then boot up install magisk apk and u should be rooted. Hope I've got that all right.
But do any of the images on this site also unlock gsm on sprint or TMobile?
Sent from my Moto Z (2) using Tapatalk
Uzephi said:
Do NOT flash the twrp img. "Fastboot boot imagename.img" then flash the twrp zip if you wish to have it as your recovery. You can find both on twrp.me.
Click to expand...
Click to collapse
Not trying to be a **** here, but what exactly do you mean by imagename.img? .. the twrp.img file? and if I don't want TWRP as recovery, then are you saying that it will remain stock if I don't flash the twrp.zip file?
I recently did this on an Essential phone, and the process was: fastboot flash TWRP.img, reboot to TWRP (recovery), flash stock boot.img, then flash magisk.zip.
The last phone I rooted/rommed before that was a Nexus 6, and **** was different then.
breakerfall said:
Not trying to be a **** here, but what exactly do you mean by imagename.img? .. the twrp.img file? and if I don't want TWRP as recovery, then are you saying that it will remain stock if I don't flash the twrp.zip file?
I recently did this on an Essential phone, and the process was: fastboot flash TWRP.img, reboot to TWRP (recovery), flash stock boot.img, then flash magisk.zip.
The last phone I rooted/rommed before that was a Nexus 6, and **** was different then.
Click to expand...
Click to collapse
Yes, just boot it. If you flash, your phone will boot to recovery. Don't flash the TWRP image!!
---------- Post added at 07:25 PM ---------- Previous post was at 07:24 PM ----------
jmagi said:
So far I understand u need to install twrp to root with magisk, then use twrp to flash magisk Img, then boot up install magisk apk and u should be rooted. Hope I've got that all right.
Click to expand...
Click to collapse
You don't flash the TWRP.img file!!! You fastboot boot it. It will temp boot to twrp
Uzephi said:
Yes, just boot it. If you flash, your phone will boot to recovery. Don't flash the TWRP image!
Click to expand...
Click to collapse
Ahhhh!
Fastboot boot TWRP.img, then just flash the magisk.zip in TWRP, right?
Thank you!
Also, @jmagi -- you shouldn't have to manually install the magisk apk. Flashing the magisk.zip in TWRP should result in a Magisk app in your "all apps" next time you boot.
Uzephi said:
Yes, just boot it. If you flash, your phone will boot to recovery. Don't flash the TWRP image!!
---------- Post added at 07:25 PM ---------- Previous post was at 07:24 PM ----------
You don't flash the TWRP.img file!!! You fastboot boot it. It will temp boot to twrp
Click to expand...
Click to collapse
Ohhh thats how it works. So i dont have to install twrp from playstore?
Sent from my Moto Z (2) using Tapatalk
jmagi said:
Ohhh thats how it works. So i dont have to install twrp from playstore?
Click to expand...
Click to collapse
No, you don't
Uzephi said:
No, you don't
Click to expand...
Click to collapse
Ok got it thank you. So fastboot boot twrp, and from twrp flash magisk.img then run magisk after bootup.
I too havent rooted a phone since droid4 which was just doubleclick a bat file lol. All this twrp stuff is new to me. Hope i got it right. Love this phone. Might get another one soon and the qwerty keyboard mod is expected on amazon within a couple months. Only reason i upgraded.
Sent from my Moto Z (2) using Tapatalk
jmagi said:
Ok got it thank you. So fastboot boot twrp, and from twrp flash magisk.img then run magisk after bootup.
I too havent rooted a phone since droid4 which was just doubleclick a bat file lol. All this twrp stuff is new to me. Hope i got it right. Love this phone. Might get another one soon and the qwerty keyboard mod is expected on amazon within a couple months. Only reason i upgraded.
Click to expand...
Click to collapse
Some people had issues and needed to wipe user data after flashing magisk
Hey now TWRP is officially available for Nokia 8 NB1
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip.You will need to have fastboot binaries and the correct drivers installed.
You can grab latest platform-tools (fastboot binaries) from [here]https://developer.android.com/studio/releases/platform-tools
Now go in the directory where your adb/fastboot binaries exists.Connect the device to your PC.Enable USB debugging in developer options & then open a command window and run the following command from the proper location:
adb reboot bootloader
Your device should now be in the bootloader.
Then again from command window run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. Use adb to push the zip onto your device:
adb push path/to/twrp.zip /
Even MTP is working you can also directly copy zip from your pc and paste to your device.
Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Thanks to @dg28gadhavi he is the maintainer for NB1
https://eu.dl.twrp.me/NB1/#
Flash instruction see dev post #4
Powered by View 10
Great news.... Thanks for sharing!!!
---------- Post added at 08:06 PM ---------- Previous post was at 08:02 PM ----------
But to my understanding, i learnt twrp is embedded into tha boot.img (kernel)..... Is it same with tha official twrp or differs?
Thanks.
Yes thats right.
Atm seems workig fine i make nandroid backup
Well will see what i can do with th System.img
Gonna make a proper thread Have fun ! BTW don't flash it to boot partitions instead use ramdisk injector zip provided by me or TWRP team site!
For Now wait! ( Am not able to send Link in message as I freshly rejoined )
Quick steps :
1) adb reboot bootloader
2) fastboot boot twrp-3.2.3-0-NB1.img
3 ) Flash permanent making zip once booted in twrp
4) Go in reboot menu of twrp and reboot to recovery once permanent making zip is flashed
5 ) Now flash Magisk zip. ( Latest beta 16.7 not stable 16.0 )
2WildFirE said:
Yes thats right. You have to flash boot recovery is in kernel image
Atm seems workig fine i make nandroid backup
Well will see what i can do with th System.img
Click to expand...
Click to collapse
I did backup with tha final verison provided here too https://forum.xda-developers.com/showpost.php?p=77307135&postcount=74 and it works fine... Buh i had a problem, i replaced my SystemUI.apk dat i modded n fix permission but stuck on Android is starting screen and i reboot to recovery n restore tha system backup cos but after restoration, still didnt load homescreen, just blank screen. Dnt know why!!!!
Also recovery didn't recognised SD Card.... Same thing is tha final version posted above!!!
Does this have the bug that brick the phone likes bidhata version?
climhz said:
Does this have the bug that brick the phone likes bidhata version?
Click to expand...
Click to collapse
Nope and bidhata posted a working version weeks back!!!
whalesplaho said:
Nope and bidhata posted a working version weeks back!!!
Click to expand...
Click to collapse
That version had the slot change brick problem. Thats what hes asking whether if this build does the same
ironman38102 said:
That version had the slot change brick problem. Thats what hes asking whether if this build does the same
Click to expand...
Click to collapse
The official version have no slot change problem. I did it Serval times works fine here.
Gesendet von meinem TA-1012 mit Tapatalk
2WildFirE said:
The official version have no slot change problem. I did it Serval times works fine here.
Gesendet von meinem TA-1012 mit Tapatalk
Click to expand...
Click to collapse
Thats good to know! Hopefully this leads to Custom ROMs
Sent from my Nokia 8 using Tapatalk
As you can see [emoji6] not bricked View attachment 4578359
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gesendet von meinem TA-1012 mit Tapatalk
ironman38102 said:
That version had the slot change brick problem. Thats what hes asking whether if this build does the same
Click to expand...
Click to collapse
I understand now... My bad!
---------- Post added at 10:59 PM ---------- Previous post was at 10:57 PM ----------
My current slot is B also but avnt tried tha feature in TWRP..... I just hope dey make tha sd card readable also!!!
Holy crap!
This is some serious good news for Nokia 8 users!
Will this work on my TA-1004?
---------- Post added at 11:39 AM ---------- Previous post was at 11:31 AM ----------
And am I going to lose official updates from Nokia?
---------- Post added at 11:42 AM ---------- Previous post was at 11:39 AM ----------
Also what's that slot A and slot B thing?
Can someone please explain?
OneWayGamer said:
Holy crap!
This is some serious good news for Nokia 8 users!
Will this work on my TA-1004?
---------- Post added at 11:39 AM ---------- Previous post was at 11:31 AM ----------
And am I going to lose official updates from Nokia?
---------- Post added at 11:42 AM ---------- Previous post was at 11:39 AM ----------
Also what's that slot A and slot B thing?
Can someone please explain?
Click to expand...
Click to collapse
1. It will work on yur model version... Just fastboot to boot_a and boot_b.
2. Better to turn off official updates cos heard from August patch, bootloader wont be able to be unlocked n unlocked ones will be locked through tha updates.
3. Slot A/B re tha partitions for storage....
whalesplaho said:
1. It will work on yur model version... Just fastboot to boot_a and boot_b.
2. Better to turn off official updates cos heard from August patch, bootloader wont be able to be unlocked n unlocked ones will be locked through tha updates.
3. Slot A/B re tha partitions for storage....
Click to expand...
Click to collapse
Wait so I have to flash it on both slots?
And umm my phone is already unlocked and I have installed August security patch
And I'm guessing Slot A is for internal storage and slot B is for external storage? I'm not sure
OneWayGamer said:
Wait so I have to flash it on both slots?
And umm my phone is already unlocked and I have installed August security patch
And I'm guessing Slot A is for internal storage and slot B is for external storage? I'm not sure
Click to expand...
Click to collapse
Nope. Slot A n B are for system. Its just tha new way partitions are set so incase when yhu have issues with a slot den yhu can switch to tha other slot to boot up tha phone... But tha news o read was dat after updating to August patch, it ll block bootloader n wont be able to unlocked. Im still on May patch 488B!
I flashed on both slots and working fine!!!!
OneWayGamer said:
Wait so I have to flash it on both slots?
And umm my phone is already unlocked and I have installed August security patch
And I'm guessing Slot A is for internal storage and slot B is for external storage? I'm not sure
Click to expand...
Click to collapse
https://www.xda-developers.com...ect-custom-development-on-xda/
This should help you understand
Sent from my Nokia 8 using Tapatalk
ironman38102 said:
https://www.xda-developers.com...ect-custom-development-on-xda/
This should help you understand
Click to expand...
Click to collapse
Thanks for helping me out!
One last question!
Will my device brick if I update my device with twrp installed?
OneWayGamer said:
Thanks for helping me out!
One last question!
Will my device brick if I update my device with twrp installed?
Click to expand...
Click to collapse
The Updater itself wont let you update because it'll detect that you're having a different boot image and will say "Installation Problem". I suggest you somehow backup the boot image and then install TWRP so that if you wanna install patches you could just revert it.
Edit: Noticed I didnt link the article properly
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
Sent from my Nokia 8 using Tapatalk
ironman38102 said:
The Updater itself wont let you update because it'll detect that you're having a different boot image and will say "Installation Problem". I suggest you somehow backup the boot image and then install TWRP so that if you wanna install patches you could just revert it.
Edit: Noticed I didnt link the article properly
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
Click to expand...
Click to collapse
That's interesting. Hmm... Can I install stock rom using twrp? (This one https://forum.xda-developers.com/nokia-8/development/nokia-8-nb1-june-firmware-via-ota-t3798056 ) or do I have to use the OST LA thingy?
All Praise And All Thanks To God
Note: Please take full twrp backup of your phone before you proceed with the below steps
Steps for Magisk root:
1. Unlock bootloader if not done yet.
see this guide to unlock:
https://forum.xda-developers.com/realme-3/how-to/guide-bootloader-unlock-guide-realme-3-t3999463
2. Install TWRP in your phone
Follow this guide on installing TWRP on your phone:
https://forum.xda-developers.com/realme-3/development/screen-doesnt-twrp-realme-3-t3944022
3. Boot your phone to TWRP.
4. Install magisk-release.zip using TWRP
5. Reboot, Done
6. Refer this for Magisk lagging Fix:
https://forum.xda-developers.com/android/general/magisk-lagging-issue-fix-t4012863/
Links:
Magisk: https://github.com/topjohnwu/Magisk/releases
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
------------------------------------------------------------------------------------------------------------------------------------------------------
OLD Method, Only root shell access, Please follow the above method for rooting , this method is only for reference to help get root access shell for new Realme and oppo phones launched in market
Steps to get Root Shell access in Realme 3, I have tested it on my phone, it works:
Part 1:
1. Unlock bootloader if not done yet.
see this guide to unlock:
https://forum.xda-developers.com/realme-3/how-to/bootloader-unlock-realme-3guide-t3920394
2. Commands to Execute:
adb reboot bootloader
fastboot erase system
fastboot -w (this will erase all the userdata)
fastboot flash system system_adbroot.img
fastboot reboot
3. let the system reboot and do the following command (Also Enable USB Debugging if not enabled):
adb shell
4. Now you have shell root access
System image with root shell access:
https://www.androidfilehost.com/?fid=1395089523397966779
Stock System image:
https://www.androidfilehost.com/?fid=1395089523397966778
Note: If you want to unroot the shell access, just flash back the Stock system image.
--------------------------------------------------------------------------------------------------------------------------------------
Credits:
1. Bjoern Kerler
For reverse engineering the ozip keys
Link to Bjoern Kerler's Github repo: https://github.com/bkerler/oppo_ozip_decrypt
Link to his awesome ozip reverse engineering guide:
https://bkerler.github.io/reversing/2019/04/24/the-game-begins/
2. @topjohnwu
For Magisk and adding full system as root support in it
3. @haditriw
For Testing all other realme 3 stuff without fear of getting hard brick and helping in the development of Realme 3, when no one is ready to help.
For real??
Keep up the good work mate
after fastboot flash boot magisk_patched.img,then fastboot reboot,now my realme 3 got bootloop,any advice?
myeganz said:
after fastboot flash boot magisk_patched.img,then fastboot reboot,now my realme 3 got bootloop,any advice?
Click to expand...
Click to collapse
I have been advised that this phone should rebooted ONLY with power switch and never from fastboot instruction...
May be I am wrong...?
Anyway you have to flash OZIP rom (may be only update) in order to reset the phone.
Hope that work.
If this is correct, OP will add BIG advice in opening post.
EDIT:
I see the stock boot link in first post op, did you try to flash it back?
myeganz said:
after fastboot flash boot magisk_patched.img,then fastboot reboot,now my realme 3 got bootloop,any advice?
Click to expand...
Click to collapse
I am not sure, currently don't have phone to test on,
see this guide:
https://forum.xda-developers.com/realme-3/how-to/realme-3-recover-soft-brick-boot-loop-t3920401
After you get the phone working properly, Instead of fastboot flash boot magisk_patched.img , try fastboot boot magisk_patched.img and follow the next steps written in instructions
Fastboot boot magisk_patched.img command doesn't work. My Realme 3 still boots normally and have no root access for Magisk Manager to install Magisk as direct install.
ReveHavan said:
Fastboot boot magisk_patched.img command doesn't work. My Realme 3 still boots normally and have no root access for Magisk Manager to install Magisk as direct install.
Click to expand...
Click to collapse
I have updated the guide
fawazahmed0 said:
I have updated the guide
Click to expand...
Click to collapse
I feel afraid to flash my boot.img with the patched img. I don't quite understand how it boots differently between fastboot reboot and by pressing manual power button. Has anyone tried flashing the Realme 3 stock boot.img when having bootloop? Is the stock boot.img for Realme 3 3/32 and 4/64 the same?
Does this work on 3/64 variant?
ReveHavan said:
I feel afraid to flash my boot.img with the patched img. I don't quite understand how it boots differently between fastboot reboot and by pressing manual power button. Has anyone tried flashing the Realme 3 stock boot.img when having bootloop? Is the stock boot.img for Realme 3 3/32 and 4/64 the same?
Click to expand...
Click to collapse
The boot image is extracted from ozip file for Realme 3, There is only one ozip for both 3gb and 4gb variant , So it should work
yametekudasai said:
Does this work on 3/64 variant?
Click to expand...
Click to collapse
Yes, it should work
fawazahmed0 said:
Yes, it should work
Click to expand...
Click to collapse
Ok thank you maybe ill root after few months just to be sure.
ReveHavan said:
. I don't quite understand how it boots differently between fastboot reboot and by pressing manual power button. ?
Click to expand...
Click to collapse
Even I don't know, but in Realme U1 doing 'fastboot reboot' will cause bootloop, so same applies here.
See this: https://forum.xda-developers.com/android/help/method-rooting-realme-u1-t3916683/
fawazahmed0 said:
Even I don't know, but in Realme U1 doing 'fastboot reboot' will cause bootloop, so same applies here.
See this: https://forum.xda-developers.com/android/help/method-rooting-realme-u1-t3916683/
Click to expand...
Click to collapse
Ah I see. I guess I'll try it then. I'll report back the result.
Edit: It bootlooped . My phone displayed the white REALME logo over and over but never went to the animated yellow logo. Thankfully the stock boot.img works. Now my phone boots normally again and it keeps all the apps and data. Still no access to root.
ReveHavan said:
Ah I see. I guess I'll try it then. I'll report back the result.
Edit: It bootlooped . My phone displayed the white REALME logo over and over but never went to the animated yellow logo. Thankfully the stock boot.img works. Now my phone boots normally again and it keeps all the apps and data. Still no access to root.
Click to expand...
Click to collapse
Currently I don't have my phone to test, I got it hardbricked, while trying to build twrp for the phone, I will see into this, when I get my phone back. Thanks for trying and letting me know the recovery steps
ReveHavan said:
Ah I see. I guess I'll try it then. I'll report back the result.
Edit: It bootlooped . My phone displayed the white REALME logo over and over but never went to the animated yellow logo. Thankfully the stock boot.img works. Now my phone boots normally again and it keeps all the apps and data. Still no access to root.
Click to expand...
Click to collapse
Can you try one more time, I have updated the patched boot image , it is patched using magisk beta channel
fawazahmed0 said:
Can you try one more time, I have updated the patched boot image , it is patched using magisk beta channel
Click to expand...
Click to collapse
I did it and the result was exactly the same as before.
ReveHavan said:
I did it and the result was exactly the same as before.
Click to expand...
Click to collapse
Thanks for trying, I think Magisk does not support our phone yet, I will file an issue at Github for bootloop problem, I will wait for my phone, before filing the issue, as it requires logs to submit.
waiting for magisk or twrp too.. i have build smali patcher, but still waiting twrp or magisk patch for install it,,
So i was running Android 10 Nov update rooted WITHOUT TWRP
And i wanted to update to Dec update
So i DLed DEC update factory image took out the -w booted my phone into the bootloader flash-all
It does its thing phone boots up obvi now i dont have root.
I put the bootloader.img onto my phone go into Magisk manager and modify the bootloader then bring it back to the computer.
Boot the phone into bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
phone gets stuck in the G logo with the loading bar
any hints????
after doing some researched i tried it again but this time flashing the patched boot.img to both a and b slots. Still same result
krolla03 said:
So i was running Android 10 Nov update rooted WITHOUT TWRP
And i wanted to update to Dec update
So i DLed DEC update factory image took out the -w booted my phone into the bootloader flash-all
It does its thing phone boots up obvi now i dont have root.
I put the bootloader.img onto my phone go into Magisk manager and modify the bootloader then bring it back to the computer.
Boot the phone into bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
phone gets stuck in the G logo with the loading bar
any hints????
Click to expand...
Click to collapse
krolla03 said:
after doing some researched i tried it again but this time flashing the patched boot.img to both a and b slots. Still same result
Click to expand...
Click to collapse
You stated that you patched the bootloader.img, is that correct?? You need to patch the boot.img, or, was that just a typo on your part?
Did you disable all your magisk modules before you fastbooted the factory image?? If not, then it's very likely that one, or maybe more modules, isn't compatible with the December update. I'll wait for your reply before trying to help solve the problem.
I previously dealt with similar symptoms. You can read about it here -- https://forum.xda-developers.com/showpost.php?p=81102855&postcount=33
Badger50 said:
You stated that you patched the bootloader.img, is that correct?? You need to patch the boot.img, or, was that just a typo on your part?
Did you disable all your magisk modules before you fastbooted the factory image?? If not, then it's very likely that one, or maybe more modules, isn't compatible with the December update. I'll wait for your reply before trying to help solve the problem.
Click to expand...
Click to collapse
OK so stupid me yes i was patching and flashing the bootloader.img not the boot.img.
I just tried flashing the indeed patched boot.img and now im getting the same issue as rustnails. Where it gets stuck at the G logo for a few secs and reboots.
I did not uninstall or disable any of the magisk modulus
how do i do that now that i dont have root?
krolla03 said:
OK so stupid me yes i was patching and flashing the bootloader.img not the boot.img.
I just tried flashing the indeed patched boot.img and now im getting the same issue as rustnails. Where it gets stuck at the G logo for a few secs and reboots.
I did not uninstall or disable any of the magisk modulus
how do i do that now that i dont have root?
Click to expand...
Click to collapse
Fastboot into twrp. Go to advanced, select file manager, go to /data/adb/modules then delete each one of them. Reboot, then go back and fastboot your patched boot.img to regain root :good:
Badger50 said:
Fastboot into twrp. Go to advanced, select file manager, go to /data/adb/modules then delete each one of them. Reboot, then go back and fastboot your patched boot.img to regain root :good:
Click to expand...
Click to collapse
Ok. Before i try that let me just ask this.
Can i just temp boot TWRP to do that
I dont want to install TWRP permanently because ive had mostly trouble with TWRP in the last few android versions.
krolla03 said:
Ok. Before i try that let me just ask this.
Can i just temp boot TWRP to do that
I dont want to install TWRP permanently because ive had mostly trouble with TWRP in the last few android versions.
Click to expand...
Click to collapse
Yep. It'll just be temporary :good:
Badger50 said:
Yep. It'll just be temporary :good:
Click to expand...
Click to collapse
Thanks man. I got it all working again!!!
Hi badger, @Badger50 (Mod Edit: added mention tag)
i have an issue with rooting my device
when I write fastboot flash boot magisk_patched.img I get a message says < waiting for device >
can you please help me to find a solution to my problem?
dark_heroo said:
Hi badger, @Badger50 (Mod Edit: added mention tag)
i have an issue with rooting my device
when I write fastboot flash boot magisk_patched.img I get a message says < waiting for device >
can you please help me to find a solution to my problem?
Click to expand...
Click to collapse
Not sure what your starting point is but:
After installing you fastboot factory image
you can either temporarily or permanently install TWRP (temp TWRP= fastboot twrp.img, install magisk, reboot OR perm TWRP = fastboot twrp.img, install TWRP.zip from witin TWRP)
then you just flash/install magisk in TWRP
In my sig is a link to a detailed step by step guide for all this.
Good luck!