Got it!
{
"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"
}
Sent from my Pixel 4 XL using Tapatalk
Magisk works? (I want to try but need to wait after work....)
lssong99 said:
Magisk works? (I want to try but need to wait after work....)
Click to expand...
Click to collapse
im trying now and it says magisk image detected .. patching then i reboot and nada...
Yeah, cant get magisk working. Even full flash-all, set up with magisk, manually create patched image
Any time you boot from the patched img, it just boots to a black screen. unrooted works fine
Updated the app and set to canary
I didn't have any issue with the vanilla magisk, Installed update via full image with wipe removed and then patched the boot with magisk and flashed it to both boots.
No issues here with June update being rooted.
Might want to flash both stock..img then right after flash patched.img
No issues here either. Updated with full factory image with "wipe" removed, patched the boot image then flashed those on both slots. Everything works fine.
I didn't get june update. Why???
yes it work
and soli work
Haxxan7 said:
I didn't get june update. Why???
Click to expand...
Click to collapse
I downloaded it and that may apply to some or all of the other posters here; it can take days or even a week or more before you get it over the air on their rollout schedule. Some report not getting it when rooted; cant speak to that as I always download the full image and dirty flash it as soon as it's available.
So I flashed and magisk patched like I always do and I get a blackscreen with with power controls when I push power button and adb support, but nothing else. I reboot and reflash stock boot and it loads but my wallpaper is gone. Ideas?
Brakiss said:
So I flashed and magisk patched like I always do and I get a blackscreen with with power controls when I push power button and adb support, but nothing else. I reboot and reflash stock boot and it loads but my wallpaper is gone. Ideas?
Click to expand...
Click to collapse
Just a few things....maybe
When you patched your boot.img, did you first disable, or remove all magisk modules??
Did you disable/remove all magisk modules before you fastbooted the .img??
Are your platform-tools up to date?
Did you flash the patched.img to both slots?
Possible USB cable issues??
Badger50 said:
Just a few things....maybe
When you patched your boot.img, did you first disable, or remove all magisk modules??
Did you disable/remove all magisk modules before you fastbooted the .img??
Are your platform-tools up to date?
Did you flash the patched.img to both slots?
Possible USB cable issues??
Click to expand...
Click to collapse
I followed the same pattern I have with the same cable that I have used for the last 6 updates with no issues. update installs fine and runs, I do magisk patched and hang, reboot into adb and flash stock. Flashed on both slots, removed magisk completely and tried flashing patched, nothing.
Brakiss said:
I followed the same pattern I have with the same cable that I have used for the last 6 updates with no issues. update installs fine and runs, I do magisk patched and hang, reboot into adb and flash stock. Flashed on both slots, removed magisk completely and tried flashing patched, nothing.
Click to expand...
Click to collapse
Again, platform-tools up to date? 30.01 is current.
Then I'd try fastbooting the factory image to your inactive slot and start over again.
That's the version of platform tools I have, and I did that. I ran the flash_all script and verified it ran on both slots
Try erasing both boots and both systems and reboot the bootloader:
fastboot erase system_a
fastboot erase system_b
fastboot erase boot_a
fastboot erase boot_b
fastboot reboot-bootloader
I responded in a little more detail over on your other post but as it sounds like you have a clue I can save you the click and tell you it's mostly what Badger covered. Do be sure and get a fresh copy of image and do not use the factory cable, you want an A to C. Also try using something like 7zip if you're using windows built in utility to decompress. Occasionally that can hang you up. Again, don't use the factory cable, it can flash some things but very often wont work with the factory images. People often think that's BS so they skip that one but it's not BS, it's a real thing.
Brakiss said:
So I flashed and magisk patched like I always do and I get a blackscreen with with power controls when I push power button and adb support, but nothing else. I reboot and reflash stock boot and it loads but my wallpaper is gone. Ideas?
Click to expand...
Click to collapse
This is due to an unsupported magisk module.
Use the boot img from this thread https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557 to boot (dont flash, boot the phone with the image i.e. fastboot boot <img>) into the phone with magisk core only mode.
Then after the phone boots up open magisk and disable/remove all the modules.
Now boot into bootloader and then flash the magisk patched boot image and reboot.
This time the phone should boot up normally and you should have root.
Now go and delete .disable_magisk file from /cache before any of your modules will work.
After this you can apply your modules one by one to see which one is failing.
I had the center clock magisk module fail for me.
Ok i will try that but both your threads you linked are dead. I do have center clock so that could be the issue.
EDIT I believe I found the thread you were trying to link me to.
EDIT #2 It worked, thank you I am loaded. It was the center clock mod.
---------- Post added at 06:09 AM ---------- Previous post was at 06:08 AM ----------
prgopala said:
This is due to an unsupported magisk module.
Use the boot img (Boot Image core-only uploaded 6-2-20
https://www.androidfilehost.com/?fid...26312261824020) from this thread https://forum.xda-developers.com/pix...agisk-t3990557 to boot (dont flash, boot the phone with the image i.e. fastboot boot <img>) into the phone with magisk core only mode.
Then after the phone boots up open magisk and disable/remove all the modules.
Now boot into bootloader and then flash the magisk patched boot image and reboot.
This time the phone should boot up normally and you should have root.
Now go and delete .disable_magisk file from /cache before any of your modules will work.
After this you can apply your modules one by one to see which one is failing.
I had the center clock magisk module fail for me.
Click to expand...
Click to collapse
Brakiss said:
Ok i will try that but both your threads you linked are dead. I do have center clock so that could be the issue.
EDIT I believe I found the thread you were trying to link me to.
EDIT #2 It worked, thank you I am loaded. It was the center clock mod.
---------- Post added at 06:09 AM ---------- Previous post was at 06:08 AM ----------
Click to expand...
Click to collapse
No worries. I have updated my post with the correct link now.
Related
If someone wants to make mirrors or a flashable zip, feel free to contact me and I will update thread
I've got my new OP3 today and what I've noticed that it runs with Oxygen OS 3.2.5. So I have looked around and saw that nobody backed up their 3.2.5 und uploaded it so I decided to do it.
Here is the download link: https://mega.nz/#!PJhzRDyL!wX12zmq9ptiu8gNbtfQfypB2Q6wGdu3IfNFFwi9acQk
The only requirement is an unlocked bootloader as fastboot doesn't allow to flash on locked devices
How to install:
via twrp:
- boot into twrp recovery
- press "install"
- press "install image" on the bottom right
- select the image and confirm on which partition it should flash
(not recommended) via fastboot:
- boot into fastboot
- use these commands to flash it:
ignore the little warning message and pe patient because it can take a while till you get a response from cmd because fastboot splits the image into 6 parts
Code:
fastboot flash boot boot.img
fastboot flash system system.img
Note: if your phone isn't booting, flash supersu and it should boot.
screenshots:
{
"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"
}
Fastboot flashing is not working.
Can you comment on the LTE reception and performance? It was the only issue i had with 3.2.4
Anyone tried looks tempting
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
TWRP is working, fastboot not.
Im on 3.2.5 now so yes its working, but only with TWRP
*Extracted fine with newest winrar*
Error on my end, sorry, thank you!
Chronzy said:
@hellcat50 zip is corrupt, "unexpected end of archive" when I tried to extract the img's. Downloaded it twice. Don't recommend wiping and trying to install at this time.
Would love to have this though, would you mind repacking?
---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------
you were able to extract the imgs? I downloaded it twice and got corrupt zip both times.
Click to expand...
Click to collapse
It did extract without any issues on my end.
I downloaded and extracted the file on my PC with the latest winrar.
EDIT:
Worked as described in the first post.
I flashed both files, followed by the latest SuperSU 2.78 and Xposed,
then did a reboot.
All works well!
So, I will not lose my data, right?
No, but you should still do a backup in TWRP.
AcmE85 said:
No, but you should still do a backup in TWRP.
Click to expand...
Click to collapse
Sorry, but I haven't installed TWRP. I'm completely on stock (system and recovery)
Andrea224 said:
Sorry, but I haven't installed TWRP. I'm completely on stock (system and recovery)
Click to expand...
Click to collapse
Then there is probably no way to install this to your device, as a user already said that using fastboot does not work.
I also think that your bootloader should be unlocked for this to work.
AcmE85 said:
Then there is probably no way to install this to your device, as a user already said that using fastboot does not work.
I also think that your bootloader should be unlocked for this to work.
Click to expand...
Click to collapse
Mmh...ok, thanks anyway.
So basically you should have unlocked bootloader, supersued, and TWRP'ed
Reconfigured said:
So basically you should have unlocked bootloader, supersued, and TWRP'ed
Click to expand...
Click to collapse
SuperSU is not needed, why should it be? With this you overwrite the whole System partition, thus removing all mods including SuperSU and Xposed.
waiting for someone to confirm the LTE issue resolution.. if it's resolved, I'll flash this ASAP..
AcmE85 said:
EDIT:
Worked as described in the first post.
I flashed both files, followed by the latest SuperSU 2.78 and Xposed,
then did a reboot.
All works well!
Click to expand...
Click to collapse
Pick your brain for a moment if you don't mind...
Still having issues with both methods... in TWRP, at the install image screen i'm only getting boot and recovery partition options, supposed to have system too right?
Fastboot it hangs for a moment at an error of something about invalid sparsing but continues to flash, apparently successfully, but when i reboot system it just boots back to recovery.
Chronzy said:
Pick your brain for a moment if you don't mind...
Click to expand...
Click to collapse
I am using this recovery
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
After switching to image install, I simply picked the system.img and was able to pick between system, boot and recovery.
Repeated for boot.img as boot...
AcmE85 said:
I am using this recovery
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
After switching to image install, I simply picked the system.img and was able to pick between system, boot and recovery.
Repeated for boot.img as boot...
Click to expand...
Click to collapse
Can we directly flash it over 3.2.4 in twrp ?
Any differences with the previous version guys?3.2.4....Tnx!!
AcmE85 said:
I am using this recovery
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
After switching to image install, I simply picked the system.img and was able to pick between system, boot and recovery.
Repeated for boot.img as boot...
Click to expand...
Click to collapse
I was on an older recovery, should have known... that did it, Thanks! :good:
Unofficial release -TWRP recovery for the Galaxy SM-J530F, Exynos7870
{
"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"
}
this version just tested in J5 pro 2017 (android 7).
use latest kernel source from opensource.samsung.com
device tree : github
mtp not work in linux.
Instructions:
Flash with ODIN 3.10.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
http://www.mediafire.com/file/qpxypf08usashe4/twrp_v3.1.1_SM-J530F.tar
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/app...2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
http://www.mediafire.com/file/ln38z3q9c6iz3ny/patched-boot.tar
just putting my 2 cents in, this TWRP does not work with J530Y, it installs and boots to system after being installed but trying to reboot when you enter causes a boot loop incase any 1 comes across this and has the same model as me, my only complaint is the, debug? text in the terminal, but thats just a small gripe of mine
work in j530f duos 2GB RAM? no pro version?
twrp working fine.But when i rebooted i lost root.Super su not found installed .Should i reflash super su and boot image
---------- Post added at 10:36 AM ---------- Previous post was at 10:35 AM ----------
akaluptos21 said:
work in j530f duos 2GB RAM? no pro version?
Click to expand...
Click to collapse
i installed on pro version.2017 sm530f/fd version
work fine thks
and now?
any custom rom for j530f?
akaluptos21 said:
and now?
any custom rom for j530f?
Click to expand...
Click to collapse
Recovery came out yesterday and you already expect a rom to be ready ?? lol
what would happen if I flashed this on a frp locked SM-J530F? I assume that the OEM Unlocking is disabled, is it worth a shot or is it just a waste of time?
Can't moun data on SM-J530F (J5 2017) (non Pro)
Dont forget Point 2.(Format Data)
Now boot.img is taking a long time to flash. Trying to flash it in AP slot of Odin.
There is not an option in TWRP to install image.
Adlbert said:
There is not an option in TWRP to install image.
Click to expand...
Click to collapse
I dont understand, TWRP dont see boot patch file. In odin i cannot do anything
davidescion said:
what would happen if I flashed this on a frp locked SM-J530F? I assume that the OEM Unlocking is disabled, is it worth a shot or is it just a waste of time?
Click to expand...
Click to collapse
Waste of time
CeloxX said:
I dont understand, TWRP dont see boot patch file. In odin i cannot do anything
Click to expand...
Click to collapse
Mine could not see it as well. Maybe you should convert .tar to .img? After some research i found out TWRP can't flash .tar.
Although, recovery works fine without patching boot.
i did the same but end up well.Its working !!.Mine was both OEM and FRP locked .i did clean install of stock rom and disabled oem lock and installed twrp and rooted aswell.
---------- Post added at 05:30 AM ---------- Previous post was at 05:29 AM ----------
davidescion said:
what would happen if I flashed this on a frp locked SM-J530F? I assume that the OEM Unlocking is disabled, is it worth a shot or is it just a waste of time?
Click to expand...
Click to collapse
Adlbert said:
Mine could not see it as well. Maybe you should convert .tar to .img? After some research i found out TWRP can't flash .tar.
Although, recovery works fine without patching boot.
Click to expand...
Click to collapse
if u unzip that patch u would get .img and use that in twrp .
served in j5 Pro Sm-J530G?
FerXray13 said:
served in j5 Pro Sm-J530G?
Click to expand...
Click to collapse
check the model of the device according to the year
I root mine J530F yesterday and install twrp afterwords. It's working, but no 2/3/4G network anymore after flashing one of both.
Not possible to install boot image from twrp app. Also sound problems and brightness troubles.
I am going back to stock rom and wait for a while for a better later version.
Great news! :good:
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
bockywocky said:
I root mine J530F yesterday and install twrp afterwords. It's working, but no 2/3/4G network anymore after flashing one of both.
Not possible to install boot image from twrp app. Also sound problems and brightness troubles.
I am going back to stock rom and wait for a while for a better later version.
Click to expand...
Click to collapse
I think you have to do the inverse process. Flash twrp and after supersu
Oke I start from scratch again...
Flashed the stok ROM first.
Enable OEM and USB debugging
Flashed TWRP twrp_v3.1.1_SM-J530F with Odin3 v3.12.7 and disable Auto Reboot option.
Important: Reboot my phone holding Vol down, Home button, Power button AND when vibrate, Imminently pushed Vol up, Home button, Power button to go directly into TWRP.
Install Magisk-v14.0 (it fails, but just do it instead of installing SuperSU)
Boot my phone and restore al my apps from the play store include root checker. It has already root acces now
Install MagiskManager-v5.3.0.apk and dowload inside this app Magisk-v14.0.zip and choose Update (recommended)
With MagiskManager you are now able to disable root checking apps like SnapChat from root access. So my Snapchat is still working now
Hope this will help you.
If so than let me know with :good:
Bocky Wocky
bockywocky said:
Oke I start from scratch again...
Flashed the stok ROM first.
Enable OEM and USB debugging
Flashed TWRP twrp_v3.1.1_SM-J530F with Odin3 v3.12.7 and disable Auto Reboot option.
Important: Reboot my phone holding Vol down, Home button, Power button AND when vibrate, Imminently pushed Vol up, Home button, Power button to go directly into TWRP.
Install Magisk-v14.0 (it fails, but just do it instead of installing SuperSU)
Boot my phone and restore al my apps from the play store include root checker. It has already root acces now
Install MagiskManager-v5.3.0.apk and dowload inside this app Magisk-v14.0.zip and choose Update (recommended)
With MagiskManager you are now able to disable root checking apps like SnapChat from root access. So my Snapchat is still working now
Hope this will help you.
If so than let me know with :good:
Bocky Wocky
Click to expand...
Click to collapse
Hey
Do you Wipe Data before u Flash The Stock rom
Do I have to install on J5 2017 (no PRO)?
Hello,
I have this phone (infinix note 4 x572) running oreo 8.1 , build number :X572-H5312CE-O-180531V117
I wish to root it but after a while of searching i'm overly confused and frustrated..
can you please guide me through rooting it?
thanks alot
btw, does local update help in any way ?
{
"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"
}
All the info and installation instructions you need can be found in the release thread:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
And if you encounter problems along the way, take a look at the troubleshooting guide.
https://www.didgeridoohan.com/magisk/Magisk
If you have further questions after that, make sure to be specific about what you need help with. "Guide me through it" is a bit too general and is already covered in the links above.
Didgeridoohan said:
All the info and installation instructions you need can be found in the release thread:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
And if you encounter problems along the way, take a look at the troubleshooting guide.
https://www.didgeridoohan.com/magisk/Magisk
If you have further questions after that, make sure to be specific about what you need help with. "Guide me through it" is a bit too general and is already covered in the links above.
Click to expand...
Click to collapse
thanks, the first prerequisite is the stock boot.img,, i tried backing it up using miracle box but encountered the 'unstable port' problem, what other possible ways i could extract the boot.img from my phone ?
and btw, i remember asking a guy somewhere and he told me that magisk won't root my device, is that true considering it's a less-known manufacturer ?
yazansayed said:
thanks, the first prerequisite is the stock boot.img,, i tried backing it up using miracle box but encountered the 'unstable port' problem, what other possible ways i could extract the boot.img from my phone ?
Click to expand...
Click to collapse
I'd try the TWRP route instead. I found this thread after about 2 minutes of searching on XDA (search words "infinix note 4 x572"):
https://forum.xda-developers.com/android/general/infinix-one-support-root-twrp-firmware-t3695803
It's a really good idea to use the XDA search, because it often works quite good.
If you want to keep the stock recovery on your device, you can actually just boot the TWRP image instead of flashing it. In that case, the command used in that thread:
Code:
fastboot flash recovery recovery.img
should be changed to:
Code:
fastboot boot recovery recovery.img
If that doesn't work, you can actually make quite easily make a backup of your boot image in TWRP and then patch that file in the Manager, to see if that works better.
If things don't work out in TWRP, make sure to provide the recovery log.
---------- Post added at 20:35 ---------- Previous post was at 20:32 ----------
yazansayed said:
and btw, i remember asking a guy somewhere and he told me that magisk won't root my device, is that true considering it's a less-known manufacturer ?
Click to expand...
Click to collapse
It's very possible... It depends on how stock the Manufacturer has kept Android on your device, what chipset the device has, and so on...
Didgeridoohan said:
I'd try the TWRP route instead. I found this thread after about 2 minutes of searching on XDA (search words "infinix note 4 x572"):
https://forum.xda-developers.com/android/general/infinix-one-support-root-twrp-firmware-t3695803
It's a really good idea to use the XDA search, because it often works quite good.
If you want to keep the stock recovery on your device, you can actually just boot the TWRP image instead of flashing it. In that case, the command used in that thread:
Code:
fastboot flash recovery recovery.img
should be changed to:
Code:
fastboot boot recovery recovery.img
If that doesn't work, you can actually make quite easily make a backup of your boot image in TWRP and then patch that file in the Manager, to see if that works better.
If things don't work out in TWRP, make sure to provide the recovery log.
---------- Post added at 20:35 ---------- Previous post was at 20:32 ----------
It's very possible... It depends on how stock the Manufacturer has kept Android on your device, what chipset the device has, and so on...
Click to expand...
Click to collapse
thanks alot for the quick responses, i will try it and reply as fast as possible
okay, i downloaded the twrp recovery image for Note 4, flashed it using Fastboot method successfully,
the problem is when i try to boot into the twrp recovery mode, i tried holding the power menu+ vol.down buttons, it sends me into a black screen with "factory mode" upwards in yellow, no button is working.
i then tried
Code:
adb reboot recovery
the phone reboots and says "No command" under a red triangle.
i then tried to flash the twrp img using sp flash tools, and flashed it successfully but the same errors occur, i can't seem to be able to boot into recovery mode.
i looked up for a solution for the "no command" problem, here's one:
I faced the same problem with nexus 6p. It works when you root immediately after flashing the TWRP. Keep the superSU file in the storage. Get into bootloader. Flash TWRP via fastboot. Without restarting anything, just press volume up/down buttons while in the bootloader to select recovery. TWRP will open. Flash the SuperSU.zip. Then restart the system. Next time, if you open recovery, you won't get the "no command". If you don't flash SuperSU and you try to open recovery later, you will get the "No command".
Click to expand...
Click to collapse
what i understood is that i shouldn't reboot my device using "fastboot reboot" , he says i should get into recovery mode directly without restarting, idk how to do that since there are no option for it on the screen, i just have
Code:
=> FASTBOOT mode...
on the screen !
Didgeridoohan said:
It's very possible... It depends on how stock the Manufacturer has kept Android on your device, what chipset the device has, and so on...
Click to expand...
Click to collapse
unfortunately i never used the sp flash tool before, so i tried flashing a stock rom but the device is now dead with "dram failed" error, i'll try fixing this first
It's tricky trying to help with a device you don't have...
Did you manage to boot to recovery? Usually you use the volume buttons to select the options and then the power button to confirm. You could also just use the fastboot boot option command I wrote earlier. It'll boot straight into TWRP.
There are a few threads for your device around, so if you need help specific to your device, that's the place to go...
everything is fine now,, fixed the device by flashing a rom named (X572-H5312CE-O-180203V55) then used magisk app to patch the included boot.img, flashed the patched boot.img using sp flash tool,, and everything is working fine now,,,
thanks alot
the twrp from the post you provided is for an older firmware, this is why i couldn't get into recovery after i flashed the provided twrp img,, there is no available twrp for the oreo version of the firmware, but i requested one from twrp builder project,, thanks alot, i've learnt alot in the last 24 hours
yazansayed said:
everything is fine now,, fixed the device by flashing a rom named (X572-H5312CE-O-180203V55) then used magisk app to patch the included boot.img, flashed the patched boot.img using sp flash tool,, and everything is working fine now,,,
thanks alot
Click to expand...
Click to collapse
could you upload the boot.img pls (the stock and the patched if possible )
{
"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"
}
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
hello guys in last few daysME/Mr. Dhruv worked so hard to finally got Twrp ready to use so far we built Twrp for nokia 6.1 2018 and nokia 7 plus
Notice1:
both phones they share same kernel and tree and both have A/B partitions, this twrp based on nokia7+
to prevent issues its better to flash it in both slot, because I/We can not know on which partition you are
Notice2:
take a backup for your data and your important files or folders before you start your Warrenty will be lost
Notice3
to reboot recovery from buttons follow this steps:
first of all you have to plug your phone to pc or charger and switch off your phone totally then press and hold volume up and power at the same time untill the bootloader`s unlock message disappear after that release power button and keep holding volume up
there you are
Notice4
to boot to fastboot switch off your phone plug it to charger or pc wait till the screen charging become black now press and hold volume down and power buttons you`ll get fastboot page there you are
Notice5:
so far no issues but if you find any please let us know
and Dhruv working on complete Twrp fully funactions he will release it soon
Notice6:
If you have different model you can contact with me on Telegram link
https://t.me/Maherabed
Twrp Nokia 7 plus TA-1046
thanks to Nick he keep testing till we boot it up
https://drive.google.com/file/d/1k2G3ERyxBFJ3bTmGtKjCpF5i7vk9prbf/view?usp=sharing
Twrp Nokia 7 plus TA-1046 P DP4
https://drive.google.com/file/d/1jA7XRIXfm9zGb_YMWZq0UBZOWXOF1Iah/view?usp=sharing
Twrp Nokia 7 plus TA-1062 P DP4
https://drive.google.com/file/d/11SIAYHTto6A5qgsq_8W-gTZHkn3Zim0f/view?usp=sharing
INSTALLATION
required :
1- unlocked bootloader
2- ADB and fastboot
3- enable usb debugging in developer settings.
4- use those codes
Code:
adb shell
Code:
reboot bootloader
now we flash it in slot a
Code:
fastboot flash boot_a <image`s name>.img
after that we flash it also in slot b
Code:
fastboot flash boot_b <image`s name>.img
then
Code:
fastboot reboot
it will boot to system dirctly so reboot to recovery
Code:
adb reboot recovery
5- install magisk.zip v16.7 download it with latest apk from here (( thanks for Magisk developers )
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
6- if you like our work hit like and if you want to share cup of cappuccino with me
paypal.me/MaherAbdulghani
Nokia globle group on Telegram go here
https://t.me/joinchat/EDAqGkPkzNQG5b7q28b1yw
Nokia 7 plus globle group on Telegram go here
https://t.me/joinchat/ItSJYkcNkKEXqcUCAaWlyg
Special thanks to
Team Win Recovery Project developers
big thanks to my mate Dhruv for hard work on this twrp
Reserved
#Reserved
N7+ TA-1062, stuck on "Nokia" boot screen after flashing this. Any help getting back to a functioning system?
Nokia 7+ global group on Telegram
https://t.me/joinchat/ItSJYkcNkKEXqcUCAaWlyg
How to unlock bootloader
---------- Post added at 04:11 AM ---------- Previous post was at 04:10 AM ----------
Is there picturs of the recovery
And please make video about how to do that
---------- Post added at 04:12 AM ---------- Previous post was at 04:11 AM ----------
And when i do that can i receive update from nokia
OK. It asked for password to decrypt the data. Pressed cancel and rebooted. Now, it goes into Download Mode every time
whoknowshimself said:
OK. It asked for password to decrypt the data. Pressed cancel and rebooted. Now, it goes into Download Mode every time
Click to expand...
Click to collapse
password should be the same that you use to unlock the phone when it's up and running. for me it's a pin. at least this is how it worked on my nexus 5x
Great. Now I am stuck in download mode. Does not boot into system anymore.
donjamal said:
password should be the same that you use to unlock the phone when it's up and running. for me it's a pin. at least this is how it worked on my nexus 5x
Click to expand...
Click to collapse
whoknowshimself said:
Great. Now I am stuck in download mode. Does not boot into system anymore.
Click to expand...
Click to collapse
After rebooting when I didn't have magisk installed after installing PixelExperience img, I am now also stuck in download mode whenever I try to reboot.
EDIT: After switching which partition to boot from a couple of times in reboot menu, I finally got back into a rom. I would suggest that "Whoknowshimself" try to do similar.
Sorry guys you all stuck on Download mode because of the command was written wrong
It was falsh but it's should be flash now all is okay
In case you got download mode loop try to active slot a for june release
Slot b for July
Fastboot --set_active=a
Fastboot --set_active=b
if i'm not mistaken, android version doesn't matter, does it? can i use this on P DP4?
I flashed everything correctly and was able to get into several ROM setups; PixelExperience, RR.
On every ROM though, SIM cards do not work in any slot.
I am in the process of getting back to stock and then I will make a rooted backup of the system with no user setup yet and I will upload the backup somewhere so that others can benefit from my experiments today.
EDIT: It will take me a while to get the backup uploaded etc... so don't hold your breath anybody
EDIT 2: It will be quicker and easier for people to just do the backup themselves before messing around flashing stuff. I can still upload it at some point if someone is in need, but just MAKE SURE YOU TAKE A BACKUP BEFORE ANYTHING ELSE.
Too late for me. I tried switching the active slot but to no avail. I had a backup but it is corrupted
I cannot even flash the ROM through OST. It says ROM does not match.
Doktaphex said:
I flashed everything correctly and was able to get into several ROM setups; PixelExperience, RR.
On every ROM though, SIM cards do not work in any slot.
I am in the process of getting back to stock and then I will make a rooted backup of the system with no user setup yet and I will upload the backup somewhere so that others can benefit from my experiments today.
EDIT: It will take me a while to get the backup uploaded etc... so don't hold your breath anybody
EDIT 2: It will be quicker and easier for people to just do the backup themselves before messing around flashing stuff. I can still upload it at some point if someone is in need, but just MAKE SURE YOU TAKE A BACKUP BEFORE ANYTHING ELSE.
Click to expand...
Click to collapse
whoknowshimself said:
Too late for me. I tried switching the active slot but to no avail. I had a backup but it is corrupted
I cannot even flash the ROM through OST. It says ROM does not match.
Click to expand...
Click to collapse
Everything working perfectly for me
Can you please tell me what model you guys have
Mine is TA-1046 JULY RELEASE
donjamal said:
if i'm not mistaken, android version doesn't matter, does it? can i use this on P DP4?
Click to expand...
Click to collapse
Better not I'll manage to edit to make it work on P DP4
TA-1062 May. Cannot boot anymore. Cannot flash using OST
Maherabed1986 said:
Everything working perfectly for me
Can you please tell me what model you guys have
Mine is TA-1046 JULY RELEASE
Click to expand...
Click to collapse
whoknowshimself said:
TA-1062 May. Cannot boot anymore. Cannot flash using OST
Click to expand...
Click to collapse
The way I fixed mine was to flash the patched July boot.img from the root your a/b partitions to both boot a and boot b.
I then downloaded all the zips to downgrade to Oreo from the official firmware and ota thread.
I used the latest rollback from that thread and then the 3 ota patches.
I side-loaded each one and booted the phone between each zip flash.
I am now at stock 8.1 fully rooted with magisk 16.7 with safety net passing completely.
Doktaphex said:
The way I fixed mine was to flash the patched July boot.img from the root your a/b partitions to both boot a and boot b.
I then downloaded all the zips to downgrade to Oreo from the official firmware and ota thread.
I used the latest rollback from that thread and then the 3 ota patches.
I side-loaded each one and booted the phone between each zip flash.
I am now at stock 8.1 fully rooted with magisk 16.7 with safety net passing completely.
Click to expand...
Click to collapse
Magisk v16.7 caused random power off after 5 minutes so i prefer using 16.6
Help me guys so i have my phone rooted via patched boot.img provided by Magisk but then decided to grab my stock boot.img to patch it again so i can update to v22.0 then i restart my device to access for fastboot and everything went blackscreen(i can't even see anything literally) luckily for me i memorize the key command to access fastboot so i flashed my stock boot.img , recovery.img and vendor.img but now my phone won't start
This thing shows up
https://imgur.com/a/fVDp06e
yes it's provably stupid to flash stock boot.img , recovery.img and vendor.img but i panic everything went all black even the BLU logo is black (no backlight phone)
What phone do you have? I think one way to try is to flash the boot.img, then boot into recovery from adb and try instaling full android from there. I haven't tried this yet but in a few hours I just might
Oliie23 said:
What phone do you have? I think one way to try is to flash the boot.img, then boot into recovery from adb and try instaling full android from there. I haven't tried this yet but in a few hours I just might
Click to expand...
Click to collapse
well that escalated quickly i just want fully update Magisk now i need to install full stock rom
ineedroot69 said:
well that escalated quickly i just want fully update Magisk now i need to install full stock rom
Click to expand...
Click to collapse
If I'm thinking correctly you won't lose data. Just dirtyflash it and it should work fine
Update ::
I flashed my stock system.img via fastboot and it fuking fix the issue
and would you look at that good as new
i thought Magisk is systemless but somehow my system.img got corrupted
{
"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"
}
ineedroot69 said:
Update ::
I flashed my stock system.img via fastboot and it fuking fix the issue
and would you look at that good as new
i thought Magisk is systemless but somehow my system.img got corrupted
Click to expand...
Click to collapse
Great news. So how did you obtain the system.img? Did you flash just that and it booted? Do you have a custom recovery?
Oliie23 said:
Great news. So how did you obtain the system.img? Did you flash just that and it booted? Do you have a custom recovery?
Click to expand...
Click to collapse
no i don't have custom recovery like TWRP the development for my device is quite dead
also i use this thread https://forum.xda-developers.com/t/amazing-temp-root-for-mediatek-armv8-2020-08-24.3922213/ to dump all my device partition just in case something like this happen
ahh it fixed now my mother won't kill me
ineedroot69 said:
no i don't have custom recovery like TWRP the development for my device is quite dead
also i use this thread https://forum.xda-developers.com/t/amazing-temp-root-for-mediatek-armv8-2020-08-24.3922213/ to dump all my device partition just in case something like this happen
Click to expand...
Click to collapse
Did you lose data? And have you dumped the files before and that's how you've had the system.img?
Oliie23 said:
Did you lose data? And have you dumped the files before and that's how you've had the system.img?
Click to expand...
Click to collapse
look like completely factory default the bloatware are back
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Sebi673 said:
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Click to expand...
Click to collapse
ahaha this Magisk update v22.0 is bonker
Sebi673 said:
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Click to expand...
Click to collapse
Let me know how it goes, please
ineedroot69 said:
look like completely factory default the bloatware are back
Click to expand...
Click to collapse
Are your apps all gone? It's basically like clean flash, right?
Oliie23 said:
Let me know how it goes, please
Click to expand...
Click to collapse
dirty flash worked, reinstalled prev magisk v. magisk hide got stuck and did not complete with custom name, yet after a restart it asked to dl something something and worked - banking app does not see magisk. will stick to the prev magisk v
Sebi673 said:
dirty flash worked, reinstalled prev magisk v. magisk hide got stuck and did not complete with custom name, yet after a restart it asked to dl something something and worked - banking app does not see magisk. will stick to the prev magisk v
Click to expand...
Click to collapse
Wonderful news. So in your case it would stay in Fastboot and wouldn't launch? What did you do then?
Oliie23 said:
Wonderful news. So in your case it would stay in Fastboot and wouldn't launch? What did you do then?
Click to expand...
Click to collapse
tried flashing the new version via twrp but i was met by an error right after unpacking. At that point i couldn't save the logs sadly.
followed by device corruption warn on boot w/ the usual bootloop.
twrp, fastboot and flashmode were ok but simply flashing the boot img didn't work - had to do a full sys flash and then magisk.
[updatee] screens attached
Sebi673 said:
tried flashing the new version via twrp but i was met by an error right after unpacking. At that point i couldn't save the logs sadly.
followed by device corruption warn on boot w/ the usual bootloop.
twrp, fastboot and flashmode were ok but simply flashing the boot img didn't work - had to do a full sys flash and then magisk.
Click to expand...
Click to collapse
Mine won't go into TWRP from the Fastboot unfortunately. It just stays there. I've managed to get TWRP to launch from ADB but I'm not sure if I should just flash the ROM that way. Should I?
[duplicate]