Related
Last night, I tried to flash gapps using goomanager. I must have used the wrong gapp files. Now, I have a problem. When I turn on tablet, an endless loop of mesages including "Unfortunately Setup Wizard has stopped working". Now I cannot access anything; no notifications, no access to settings, etc. Anyone have an idea where I can start to troubleshoot this?
That seems like a lot of work compared to just dirty-flashing the same ROM you were using before the gapps flash.
If you have a Nandroid backup using TWRP, you could just selectively restore the system partition.
OR, just start over by doing a factory reset in the custom recovery and then re-installing a ROM from scratch. (You didn't say whether saving data was of any concern to you.)
bftb0 said:
That seems like a lot of work compared to just dirty-flashing the same ROM you were using before the gapps flash.
If you have a Nandroid backup using TWRP, you could just selectively restore the system partition.
OR, just start over by doing a factory reset in the custom recovery and then re-installing a ROM from scratch. (You didn't say whether saving data was of any concern to you.)
Click to expand...
Click to collapse
Saving data is not important. I should have a backup of the Nandroid. I made one after rooting the tablet. The part that confuses me is how to get to those options? I can get into fastboot mode on the tablet. However, from the methods I've tried, they all say I do not have abd. I cannot access usb debugging. How would I reset to factory settings?
captainNT said:
Saving data is not important. I should have a backup of the Nandroid. I made one after rooting the tablet. The part that confuses me is how to get to those options? I can get into fastboot mode on the tablet. However, from the methods I've tried, they all say I do not have abd. I cannot access usb debugging. How would I reset to factory settings?
Click to expand...
Click to collapse
What custom recovery is on the tablet?
I would think that no matter what installer you used (I'm not familiar with "goo manager"), the ROM file that you downloaded would still be present on your device's /sdcard.
If that is the case, you boot your custom recovery (get the tablet into fastboot mode, and press the vol-down or vol-up button to until "start recovery" shows up, and then press the Power button).
From there perform a factory reset and then flash the ROM on your /sdcard from the custom recovery menu.
Long term you really need to straighten out your driver issues. You can see why, right? Alternatively, the TWRP recovery can mount USB flash drives in order to get files to a blank tablet that still has a working custom recovery - you just need the USB key drive and a working OTG cable.
bftb0 said:
What custom recovery is on the tablet?
I would think that no matter what installer you used (I'm not familiar with "goo manager"), the ROM file that you downloaded would still be present on your device's /sdcard.
If that is the case, you boot your custom recovery (get the tablet into fastboot mode, and press the vol-down or vol-up button to until "start recovery" shows up, and then press the Power button).
From there perform a factory reset and then flash the ROM on your /sdcard from the custom recovery menu.
Long term you really need to straighten out your driver issues. You can see why, right? Alternatively, the TWRP recovery can mount USB flash drives in order to get files to a blank tablet that still has a working custom recovery - you just need the USB key drive and a working OTG cable.
Click to expand...
Click to collapse
New problem now. I think I have no custom recovery installed. When I go into recovery from fastboot mode, it shows the droid with a red exclamation mark. Trying to diagnose that now but I can't access the tablet settings.
captainNT said:
New problem now. I think I have no custom recovery installed. When I go into recovery from fastboot mode, it shows the droid with a red exclamation mark. Trying to diagnose that now but I can't access the tablet settings.
Click to expand...
Click to collapse
That is the stock recovery.
Which means you need to get fastboot working from a PC; you really have no choice any longer. Have a look at the fastboot / unroot sticky thread.
Used a toolkit to get back to stock settings. Good to go. Thank you.
Hello,
my Nexus 4 dropped on the floor and now the touchscreen in the bottom right corner is not working anymore. This is a very unfortunate position since I am not able to press the "OK" button to unlock the lockscreen. I now want to at least save my data. USB Debugging is not enabled, so adb commands are not working :/
I googled a bit and found this thread witch the pretty much same situation:
http://forum.xda-developers.com/nexus-4/help/nexus-4-to-copy-data-broken-touch-input-t2415195
The steps to take are described as the following:
Read this guide http://forum.xda-developers.com/show....php?t=2266654 . only follow the parts to unlock the boot loader and flash clockworkmod custom recovery. Make sure that you flash the recovery right after unlocking (without rebooting in between) otherwise data will get wiped. )
After that boot into your newly flashed recovery and use "adb pull /data/media/" . this should copy everything on the internal sdcard of the phone.
Click to expand...
Click to collapse
So i did unlock the bootloader and flashed a clockwork custom recovery (6.0.4.7). I also managed to not reboot the phone between these two steps.
I was not sure what to do now as i did not know what was meant by boot into your newly flashed recovery . So i found another thread and followed these instructions
http://forum.xda-developers.com/showpost.php?p=41291371&postcount=28
After wiping the cache in step 4 i was in a boot loop (at least it took time like an eternity) and shut down the phone manually (by pressing the Power On button a few seconds). The new bootet phone is now in a state where I have to set the language for the new clockwork custom recovery. I tried to do some adb commands (because USB Debugging should not be the problem anymore) but it did not work. I am also scared that because of my manually shutting down caused a full wipe as i read the following sentence in the latest thread:
This no longer seems to be working if your phone is on official 4.3 (meaning you have the 4.3 bootloader). It will only give you a bootloop and then you will end up having to do a full wipe, resulting in losing your data. Only do this is you are on 4.2.
Click to expand...
Click to collapse
My question is now: Is all my data lost now? And if not, how can I save it / where did I go wrong?
Thank you for your help, I appreciate it!
frucade
Unlocking the bootloader wipes your device. So, yea, your data is gone. Without a custom recovery and a locked bootloader you were doomed from the beginning.
Sent from my Nexus 9 using XDA Free mobile app
Hi everyone,
tonight I was trying to install the Stagefright OTA using this guide: http://forum.xda-developers.com/moto-x/general/xt1053-222-27-5-stagefright-ota-update-t3210786
The only thing I got was an android with a red triangle on it. So I went back, did a total phone reset, reinstalled the TWRP (fastboot flash twrp.img) and restored my backup. Sadly, the phone keeps rebooting to the TWRP as if there's nothing on it except the TWRP.
I've got the eu model and I can't find any factory image (or image in general) to flash on the device.
EDIT:
I manage to get something to work by simply boot via the "BT Tools" fastboot menu voice.
I don't exactly know why, but this way I manage to boot on a clean Android install and then restore my TWRP backup.
There's just a little problem: if I boot normally the system goes straight to the TWRP and won't boot.
I always need to go in the fastboot menu and select "BT Tools".
i was going through a similar reboot process last night. I realized that my issue was that I had xposed installed and had to uninstall it. however, I realized that after I wiped internal storage.
thus, my solution was to wipe everything (cache, dalvik, data, & internal storage), then mfastboot the stock ROM, then flash TWRP, then restore nandroid.
however, make sure to copy your nandroid to your computer first - you can transfer it back to the phone after flashing TWRP. you may have to perform a small nandroid via TWRP just to setup the right folder names, but you can still transfer the nandroid folder to your phone while the phone is in recovery.
hope this helps.
jco23 said:
i was going through a similar reboot process last night. I realized that my issue was that I had xposed installed and had to uninstall it. however, I realized that after I wiped internal storage.
thus, my solution was to wipe everything (cache, dalvik, data, & internal storage), then mfastboot the stock ROM, then flash TWRP, then restore nandroid.
however, make sure to copy your nandroid to your computer first - you can transfer it back to the phone after flashing TWRP. you may have to perform a small nandroid via TWRP just to setup the right folder names, but you can still transfer the nandroid folder to your phone while the phone is in recovery.
hope this helps.
Click to expand...
Click to collapse
First of all, thanks for your reply.
I manage to get something to work by simply boot via the "BT Tools" fastboot menu voice.
I don't exactly know why, but this way I manage to boot on a clean Android install and then restore my TWRP backup.
There's just a little problem: if I boot normally the system goes straight to the TWRP and won't boot.
I always need to go in the fastboot menu and select "BT Tools".
Any hint on why this is happening?
edmael said:
First of all, thanks for your reply.
I manage to get something to work by simply boot via the "BT Tools" fastboot menu voice.
I don't exactly know why, but this way I manage to boot on a clean Android install and then restore my TWRP backup.
There's just a little problem: if I boot normally the system goes straight to the TWRP and won't boot.
I always need to go in the fastboot menu and select "BT Tools".
Any hint on why this is happening?
Click to expand...
Click to collapse
you could be missing this line: mfastboot getvar max-download-size
I used the guide here: http://forum.xda-developers.com/moto-x/general/xt1060-lollipop-5-1-ota-fxz-thread-t3139519
granted, you appear to have a different model than mine, but the process should be the same.
jco23 said:
you could be missing this line: mfastboot getvar max-download-size
I used the guide here: http://forum.xda-developers.com/moto-x/general/xt1060-lollipop-5-1-ota-fxz-thread-t3139519
granted, you appear to have a different model than mine, but the process should be the same.
Click to expand...
Click to collapse
Yes, I skipped that line and removed it from the .xml of the images I flashed because I found some guides that suggested it.
Now I'm really tempted to re-flash everything using that command first.
edmael said:
Yes, I skipped that line and removed it from the .xml of the images I flashed because I found some guides that suggested it.
Now I'm really tempted to re-flash everything using that command first.
Click to expand...
Click to collapse
All removing that line does is prevent the system partition from error-ing out during the flashing process, which is why it's suggested to remove the line if you are using RSD-Lite to flash an image
mastarifla said:
All removing that line does is prevent the system partition from error-ing out during the flashing process, which is why it's suggested to remove the line if you are using RSD-Lite to flash an image
Click to expand...
Click to collapse
I flashed it using the -P option so I guess it's just the same as using that line, right?
Also: the removal of that line was not only in your guide so I immediatly deleted it
edmael said:
I flashed it using the -P option so I guess it's just the same as using that line, right?
Also: the removal of that line was not only in your guide so I immediatly deleted it
Click to expand...
Click to collapse
Flashing with mfastboot with the -P option is the same, you can verify the option exists by just typing in mfastboot in the command line, it will show you all the commands and what they do
I didn't want to have people dependent on using RSD-Lite (or any particular program) to flash the System Image, as it then makes a Windows machine the only thing possible to flash this image plus it uses Internal Moto Only software (legal issues), so I tried to find a better way to make mfastboot work properly for all types of computers
another thing I have noticed is that my phone kept getting stuck on the boot image screen (failed to proceed to the boot animation screen). to resolve this, I made sure to flash SU via TWRP after flashing my ROM via TWRP (or restoring a nandroid).
mastarifla said:
Flashing with mfastboot with the -P option is the same, you can verify the option exists by just typing in mfastboot in the command line, it will show you all the commands and what they do
I didn't want to have people dependent on using RSD-Lite (or any particular program) to flash the System Image, as it then makes a Windows machine the only thing possible to flash this image plus it uses Internal Moto Only software (legal issues), so I tried to find a better way to make mfastboot work properly for all types of computers
Click to expand...
Click to collapse
I really appreciated that (proud Linux User here), I tried mfastboot on Linux and even RSD-Lite on my Windows machine, but both of them failed to get my phone working with the files you provided in the other thread.
Now I'm stuck with this problem: every boot I need to select BT Tools and wait some minutes for my phone to boot.
I still don't get why it only boot in TWRP and I still don't get how to fix this
edmael said:
I really appreciated that (proud Linux User here), I tried mfastboot on Linux and even RSD-Lite on my Windows machine, but both of them failed to get my phone working with the files you provided in the other thread.
Now I'm stuck with this problem: every boot I need to select BT Tools and wait some minutes for my phone to boot.
I still don't get why it only boot in TWRP and I still don't get how to fix this
Click to expand...
Click to collapse
you may need to wipe internal storage and mfastboot everything from scratch...
jco23 said:
you may need to wipe internal storage and mfastboot everything from scratch...
Click to expand...
Click to collapse
Already did that (the first time I didn't even tried booting with BT Tools, but the effects were the same), but nothing new happened.
edmael said:
I really appreciated that (proud Linux User here), I tried mfastboot on Linux and even RSD-Lite on my Windows machine, but both of them failed to get my phone working with the files you provided in the other thread.
Now I'm stuck with this problem: every boot I need to select BT Tools and wait some minutes for my phone to boot.
I still don't get why it only boot in TWRP and I still don't get how to fix this
Click to expand...
Click to collapse
Have you tried flashing the TWRP System Backup that I provided? It may fix the issue that you are seeing currently
mastarifla said:
Have you tried flashing the TWRP System Backup that I provided? It may fix the issue that you are seeing currently
Click to expand...
Click to collapse
Yes, tried, but nothing happens (except that it boots when I go into BT Tools).
I think there's something wrong with my partition scheme because it always go straight to TWRP.
If I were on a GNU/Linux distro I'd check the grub config because it seems it boot from the wrong partition, but on Android I don't know if/how that's possible.
does it boot up when you flash the stock recovery? perhaps you may need to let it boot up first before installing TWRP?
did you happend to type "mfastboot flash boot twrp.img"? that could be the issue, as the command should be "mfastboot flash recovery twrp.img, right?
sorry I can't be more helpful, as I'm sure this is frustrating for you. just trying to grasp at straws here....
jco23 said:
does it boot up when you flash the stock recovery? perhaps you may need to let it boot up first before installing TWRP?
sorry I can't be more helpful, as I'm sure this is frustrating for you. just trying to grasp at straws here....
Click to expand...
Click to collapse
Don't be sorry, you're helping me!
Also: I'm not much frustrated since I have a working phone right now, I just need do avoid rebooting it
I tried to flash the stock recovery (found here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628, used this: XT1052_GHOST_RETEU_5.1_LPA23.12-15_cid7_CFC.xml.zip) but if I'm not wrong (did that yesterday in the late night) it just booted to the Android with the red triangle on it (so, no booting for me).
EDIT:
No, I don't think I did that. But let's suppose I did, how can I revert it?
Also: is there a way to see my partition scheme so I'm sure everything's fine?
edmael said:
Don't be sorry, you're helping me!
EDIT:
No, I don't think I did that. But let's suppose I did, how can I revert it?
Also: is there a way to see my partition scheme so I'm sure everything's fine?
Click to expand...
Click to collapse
You can revert it by taking the boot.img from the 5.1 zip and flashing that using the command...
mfastboot flash boot boot.img
The partitioning you are mentioning is probably the gpt.bin, but that is typically done near the very beginning of the flashing process
here's what I would do:
boot into recovery
connect phone to PC, copy your nandroid and any other files from the SDcard to your PC
within recovery, wipe cache/dalvik/data/internal storage
reboot to bootloader
run the mfastboot commands as shown (but use the getvar-download....) in place of editing the xml zip file
after running the mfastboot commands, let the phone boot up to stock and establish itself
reboot to bootloader and flash TWRP
again, just a suggestion on what I would do - seems like @mastarifla is a great resource and is more knowledgeable than me, so maybe you'll get some confirmation.
good luck!
Ok, I still haven't solved this issue.
I tried with re-flashing everything, but I still get the problem.
I think it's a problem with the partition scheme because even by flashing just partition gpt.bin and motoboot.img when I launch reboot-bootloader it reboot the phone into TWRP.
I think the TWRP is in the wrong partition and/or I've got a wrong partition scheme, but I don't know how to check it or how to fix it.
edmael said:
Ok, I still haven't solved this issue.
I tried with re-flashing everything, but I still get the problem.
I think it's a problem with the partition scheme because even by flashing just partition gpt.bin and motoboot.img when I launch reboot-bootloader it reboot the phone into TWRP.
I think the TWRP is in the wrong partition and/or I've got a wrong partition scheme, but I don't know how to check it or how to fix it.
Click to expand...
Click to collapse
So your phone thinks that the bootloader is your recovery?
That is actually pretty strange, you could take a look at the Linux kernel on Motorola's GitHub and see if it has any info on the partitioning structure or what happens when a reboot-bootloader command is sent to the phone
It sounds as if the recovery and the bootloader swapped places, as the fastboot menu is considered a part of the bootloader, and if you are not seeing that on the hardware key bootup, then there is something definitely wrong, if you do reboot-recovery does it take you to the bootloader/fastboot menu?
Hi everybody, i would like to remove the devices encription under Security-Encryption
Under Encrypt device i've got Encrypted.
I've tried to restore to factory default, from recovery, from fastboot using format userdata, but, no way.
How i can remove the encryption?
My device is ZE552KL
Thanks
swet90 said:
Hi everybody, i would like to remove the devices encription under Security-Encryption
Under Encrypt device i've got Encrypted.
I've tried to restore to factory default, from recovery, from fastboot using format userdata, but, no way.
How i can remove the encryption?
My device is ZE552KL
Thanks
Click to expand...
Click to collapse
I had a same issue with this device, but I had some experiment.
If your device is unlocked, you can flash TWRP, boot to recovery, wipe, format data.
Backup your data first! It will erase all of your data (Very noob answer)
Totally careful, don't do this if you didn't want a unexpected things. Or something...
The ASUS Zenfone 3 comes shipped encrypted by default. This is required by Google's Play Services agreement for phone OEMs. You cannot remove decryption on the Zenfone 3 without using a custom ROM.
sensi277 said:
The ASUS Zenfone 3 comes shipped encrypted by default. This is required by Google's Play Services agreement for phone OEMs. You cannot remove decryption on the Zenfone 3 without using a custom ROM.
Click to expand...
Click to collapse
Thanks!
TWRP isn't allowing me to Mount my Storage because it's asking for a password I don't know.
ZeldaLinkAaron said:
TWRP isn't allowing me to Mount my Storage because it's asking for a password I don't know.
Click to expand...
Click to collapse
I'm having the same issue. I just got my daughter this phone (the 552KL?), downloaded the official Asus bootloader unlocker APK and ran it, then rebooted to the bootloader to flash TWRP.
TWRP installed, but wants a password to unlock it. Before the bootloader unlock, I did put her Google account on the phone, but the tool said it would completely wipe the phone. Either way, I tried her google account password, but it just says wrong password. Same thing when I tried to boot to system.
Any tips?
@Flapjack
Format through twrp
wang1chung said:
@Flapjack
Format through twrp
Click to expand...
Click to collapse
That's what I ended up doing. I got some help on another thread. The problem I'm having now is that I can't format /cache. It's really weird. If I do a full wipe on the phone, it says it can't format it. I even tried formatting it through fastboot ("fastboot erase cache" then "fastboot format cache"), which says "OKAY finished", but doesn't fix the issue when trying to wipe cache inside of TWRP.
This phone is flat out weird compared to other phones. I don't get the bootloader unlock screen. It doesn't seem to want to boot system... it just keeps going to TWRP. On the few times I have gotten to boot into system (after flashing Carbon 6.1 unofficial), it ends up hanging on a blank screen. Windows makes a sound that a new device is connected, so I'm guessing it's connecting in EDL mode or something (no devices show with a "fastboot devices" or a "adb devices").
I really don't know where to go from here. I'm used to working with Axons, Motorolas, and OnePlus phones. They just work.
@Flapjack
The cache issue is a glitch with the build of twrp, it's not a big deal. There's a workaround posted somewhere, can't remember. Just use the file browser and delete the files on it. I think there's only one file that isn't 0 bytes.
Have you flashed magisk?
Sometimes a full wipe (system/data) and then flashing the raw firmware helps. Try magisk first.
wang1chung said:
@Flapjack
The cache issue is a glitch with the build of twrp, it's not a big deal. There's a workaround posted somewhere, can't remember. Just use the file browser and delete the files on it. I think there's only one file that isn't 0 bytes.
Click to expand...
Click to collapse
So you're saying it doesn't need to be actually wiped, I just need to go into cache and delete all the files in there? How about getting it to boot to system? It just keeps booting to recovery. Not sure when it started that, as after the first time I flashed the ROM, I was able to get it to boot to system by pressing the power button when the "bootloader unlocked" screen came up. That isn't working now.
Have you flashed magisk?
Sometimes a full wipe (system/data) and then flashing the raw firmware helps. Try magisk first.
Click to expand...
Click to collapse
For my first non-stock ROM flash, I flashed the Oreo modem, Carbon 6.1 unofficial ROM, ARM64 Gapps nano, and Magisk 16.0... all at once. I tried booting and it looked like it was setting up... but as I mentioned, it just went to a blank screen. After trying a full wipe and seeing the "couldn't wipe cache" message, I figured that was why.
How will flashing Magisk help me with wiping the cache partition or getting the thing to boot right? Sorry for my ignorance.
Flapjack said:
So you're saying it doesn't need to be actually wiped, I just need to go into cache and delete all the files in there?
Click to expand...
Click to collapse
wiping/formatting cache is the same as deleting all the files. Wiping is easier but as I said, doesn't work at the moment.
Flapjack said:
How will flashing Magisk help me with wiping the cache partition or getting the thing to boot right? Sorry for my ignorance.
Click to expand...
Click to collapse
magisk won't help with cache, but it will remove the verity flag that is tripped from having twrp. From my experience, if I don't flash magisk, it'll bootloop.
Yeah.... absolutely nothing I do will get it to boot to system now. I've flashed the ROM and Magisk, but no matter what, it keeps booting to recovery.
There were two folders under /cache... "Lost&Found" and "recovery". I deleted both, but that didn't help.
---------- Post added 5th July 2018 at 12:40 AM ---------- Previous post was 4th July 2018 at 11:44 PM ----------
wang1chung said:
wiping/formatting cache is the same as deleting all the files. Wiping is easier but as I said, doesn't work at the moment.
Click to expand...
Click to collapse
So I take it I did it right? I would say it's "pretty much" the same. Formatting a partition is different than deleting files/folders in an existing partition. Still, if deleting the files/folders is good enough, then that rules out why the system wouldn't boot after the first ROM install attempt. It would also explain why "fastboot erase cache" seems to work, but TWRP still throws an error. Fastboot erase is probably working just fine.
magisk won't help with cache, but it will remove the verity flag that is tripped from having twrp. From my experience, if I don't flash magisk, it'll bootloop.
Click to expand...
Click to collapse
Is there a custom version of Magisk for this phone? I'm just installing the usual magisk 16.0 zip file you can get on their site, but it doesn't seem to be helping with the phone continuously booting into recovery. Is there a way to remove that verity flag via adb?
@Flapjack
Magisk modifies one of the partitions to get around the flag (I believe), not doable through adb.
Standard magisk off their site is fine
Try this:
Format system/data
Flash custom Rom
Flash magisk
"Wipe" cache and davlik
Reboot
OR
Flash the raw firmware
Flash twrp
Flash whichever custom Rom & gapps where needed
Flash magisk
Factory reset and "Wipe" cache and dalvik
Reboot
wang1chung said:
@Flapjack
Magisk modifies one of the partitions to get around the flag (I believe), not doable through adb.
Standard magisk off their site is fine
Try this:
Format system/data
Flash custom Rom
Flash magisk
"Wipe" cache and davlik
Reboot
Click to expand...
Click to collapse
No go. Still just boots into recovery. Here's what the boot screen looks like (then the Asus logo pops up, then recovery loads)
Code:
< More information :
Dm-Verity in EIO mode
Your device software can't be
checked for corruption. Please
lock the bootloader.
Visit this link on another device:
g.co/ABHg.co/placeholder
Your device will shutdown in 10 seconds
I can press the power button to boot immediately, or wait the 10 seconds... which just boots anyway (doesn't shut down). If I press the volume buttons, I get the following options menu:
Power off
Restart
Recovery
Fastboot
Back to previous page
Flash the raw firmware
Flash twrp
Flash whichever custom Rom & gapps where needed
Flash magisk
Factory reset and "Wipe" cache and dalvik
Reboot
Click to expand...
Click to collapse
I haven't tried this yet. Would this be the best guide to follow?
HOW-TO: Go back to Stock Rom on ZE552KL/ZE520KL
https://forum.xda-developers.com/zenfone-3/how-to/how-to-to-stock-rom-recovery-zenfone-3-t3666223
@Flapjack
That is the correct screen for an unlocked bootloader.
Try this guide for the raw firmware instead, and verify it boots to the OS. Then flash twrp and the rom again.
wang1chung said:
@Flapjack
That is the correct screen for an unlocked bootloader.
Try this guide for the raw firmware instead, and verify it boots to the OS. Then flash twrp and the rom again.
Click to expand...
Click to collapse
Grrr... no matter what I do, it won't flash. The guide says to put it in fastboot mode, but the flash tool won't detect it (even though "fastboot devices" shows it just fine). If I boot it to recovery, it'll show up in the tool, but never actually flashes (see screenshot).
Flapjack said:
Grrr... no matter what I do, it won't flash. The guide says to put it in fastboot mode, but the flash tool won't detect it (even though "fastboot devices" shows it just fine). If I boot it to recovery, it'll show up in the tool, but never actually flashes (see screenshot).
Click to expand...
Click to collapse
This is why I stopped using Windows. Maybe try disabling "driver signature verification"? Swap USB ports? My computer has some high power and low power USB ports, certain devices won't work properly in the low power ones. A couple of guides mentioned unplugging and re-plugging the USB.
wang1chung said:
This is why I stopped using Windows. Maybe try disabling "driver signature verification"? Swap USB ports? My computer has some high power and low power USB ports, certain devices won't work properly in the low power ones. A couple of guides mentioned unplugging and re-plugging the USB.
Click to expand...
Click to collapse
That's a good idea. I'm going through a powered hub right now, but who knows...
I'll try that as soon as I get home.
Ok, different computer. This is my laptop I normally use to flash.
This time, I can get it it to start to flash, but with a second or two, it throws an error (see attached).
Flapjack said:
Ok, different computer. This is my laptop I normally use to flash.
This time, I can get it it to start to flash, but with a second or two, it throws an error (see attached).
Click to expand...
Click to collapse
are you running ASUS flash tool with admin privileges?
Red Magic 5G Bootloader Unlock Guide: OR get ROOT & TWRP without unlocking the BL!!!
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
WARNING: ANY BOOTLOADER UNLOCK METHOD INVOLVES THE RISK OF BRICKING YOUR DEVICE PERMANENTLY. WHILE THERE IS USUALLY A WAY TO RECOVER, DO NOT ATTEMPT THIS PROCEDURE IF YOU DO NOT KNOW WHAT YOU ARE DOING. BAD THINGS CAN HAPPEN. YOU HAVE BEEN WARNED!!! YOU MAY BE LEFT WITH A USELESS BRICK!!! READ ALL FURTHER WARNINGS EXPERIMENTAL METHOD IN ORIGINAL DOWNLOAD FILE WORKS, I'M USING IT
If you want a NOOB guide look at this post: https://forum.xda-developers.com/nu...beginner-tutorial-unlock-bootloader-t4131585/
Also note a user has managed to fix the FP sensor post BL unlock, see this post here: https://forum.xda-developers.com/nu.../guide-calibration-finger-print-loss-t4132961
Still, I suggest root bypass it's better.
MegaNZ Link for Root without unlocking the Bootloader, and without breaking the FP, also includes instructions for installing BlackMagic5G (explanation below), adding HD VOLTE, how to restore from a brick, and some other cool tricks: https://mega.nz/file/igphSCTD#OybJo9t1zwvJ0bdbAcN2BCqxWXAfHdhk3JFB4_5xkVc
I suggest you flash my BlackMagic5G and don't unlock your bootloader at all - just root. It's CN 2.52 ROM based. You'll get VOLTE, , GApps installed, Rooted with Magisk, TWRP, debloated, YouTube Vanced, AdAway, SmartPack Kernel Manager, etc. - looks like the Global / NA variant of the ROM. Almost perfect except still uses Messages and Phone from Nubia. Plus you will enable Face Unlock not available in the Global or NA versions of the ROM, and FP will still work! Click on the Google Search bar widget and the mic icon takes you to the Google Assistant, the left icon is Google Feed, type in the middle bar for a Google Search. Has 1Weather Free weather widget that looks great, and Google Calendar widget for your whole month of activities. Translate, Lens, Chrome, all the Google Apps are there. And the Chinese Nubia apps are nearly all GONE!
MegaNZ Link for BlackMagic5G Beta - IT'S ONLY THE DATA PARTITION + ROOTED KERNEL + NA SPLASH SCREEN, you NEED to 1) install the Red Magic 2.52 ROM below FIRST 2) Root using the first link posted above 3) Flash restore this from TWRP: https://mega.nz/file/r9hF2BwS#RrAXiFWSBNX8dLqfrH8nNHo_uigPC8uYXonwhALhGbo
MegaNZ Link for the Red Magic 5G CN 2.52 ROM: https://mega.nz/file/aoxBFAqY#EDt2OZBGTME4ZGKnERKpK_t-aJT_rWgD0aqBFkilRcY
*** NOW THE BOOTLOADER UNLOCK INSTRUCTIONS ***
Go to Settings / About phone / Build Number (NX659_J_ENCommon_V3.08 on North American Variant), click 7 times, Now you are a developer message appears, go back a menu to Settings / Other system settings / Developer options.
Enable:
OEM unlocking "Allow the bootloader to be unlocked"
USB debugging "Debug mode when USB is connected"
Install Minimal ADB and Fastboot (Windows 10 in this example): https://www.androidfilehost.com/?fid=746010030569952951
Default install path is:
C:\Program Files (x86)\Minimal ADB and Fastboot\
Go to the Search button on the bottom on Windows 10, type cmd, Command Prompt will appear in the menu. Right click it and Run as Administrator. All commands to be typed will be run in this Command Prompt window (referred to as terminal) unless otherwise stated to run on the phone.
Now Terminal window appears (it says Administrator: Command Prompt in the heading):
Text displayed is:
Microsoft Windows
(c) 2020 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>
Typed in terminal:
cd "c:\Program Files (x86)\Minimal ADB and Fastboot"
I now connected the phone to a USB port on the PC.
On the phone, a Window appeared:
"Allow USB debugging?"
The computer's RSA key fingerprint is:
[36 digit code] Example:
C8:A17:E2:01:F6:A1
:368:10:E8:33:20:FB:
93:7D
Always allow from this computer (it's my computer so I clicked it since I trust the computer)
CANCEL / ALLOW (I clicked ALLOW)
Typed in terminal:
adb reboot bootloader
The phone reboots. Once the phone screen boots, in the center it says: Now you are in fastboot mode.
From the terminal I typed:
fastboot oem nubia_unlock NUBIA_NX659J
The terminal now displayed:
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) START set state to 1 ok!!!
In the terminal I typed:
fastboot flashing unlock *** DO NOT TYPE THIS IF YOU WANT TO KEEP A WORKING FP!!! READ TOP OF POST!!! AVOID THIS WITH THE EXPERIMENTAL METHOD OF ROOT WITH NO BL UNLOCK ***
Now a screen appeared on the phone with a big <!> red icon in the left corner. The rest in white text is a warning message. "By unlocking the bootloader, you will be able to install custom operating system on this phone. A custom OS is not subject to the same level of testing as the original OS, and can cause your phone and installed applications to stop working properly-
Software integrity cannot be guaranteed with a custom OS, so any data stored on the phone while the bootloader is unlocked may be at risk.
To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data on your phone.
Press the Volume keys to select whether to unlock the bootloader, then the Power Button to continue."
I selected UNLOCK BOOTLOADER and my device was completely erased. The factory OS loaded then. This process takes some time to complete.
Now the device rebooted with a warning message, and a big <!> yellow icon in the left corner.
"The boot loader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.
Visit this link on another device:
g.co/ABH"
Now the device reloads the firmware apparently and wipes all user data. Upon setting up the phone, the fingerprint display registration comes up and asked to place my finger on the back of the phone. There is no fingerprint sensor on the back of the Redmagic 5G! It is under the screen! So this step must be skipped. The ROM setup is corrupt or incomplete, a beta possibly. I setup the phone then went into Settings / Security to try to add a fingerprint. The button to add fingerprint then appears. Once I click the button, I get this error:
Loss of fingerprint calibration data
Loss of fingerprint calibration data was detected.
Currently unable to complete fingerprint entry,
please contact Nuia after-sales service via
4007006600
See the XDA post for recalibrating the FP: https://forum.xda-developers.com/nu.../guide-calibration-finger-print-loss-t4132961
ROOT FOR ALL DEVICES:
(These files are included in the tools download zip, Magisk 20.4 and MagiskManager-v7.5.1.apk, but this is the official source as updates post): Go to XDA and Download Magisk Manager and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power, release the power button once the screen shows it loading, hold the volume up down until you see TWRP pop up). Flash Magisk from TWRP Install / Zip / sdcard / Magisk.zip reboot and you'll have root.
BL unlock first method was tested on North American variant and it works. But it breaks your FP sensor and gives you an annoying boot prompt.
If at any time you want to remove the OEM Bootloader unlock, you plug into the PC, go to the terminal for Minimal ADB and Fastboot, type:
adb reboot fastboot
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing lock (screen will prompt to relock BL, choose to Relock)
The phone should reboot and install the original software. BUT...
If it says you are corrupted well, you have more issues.
You'll have to reflash the stock recovery.img, reboot to stock recovery, wipe data, wipe cache, and flash the CN update.zip rom to a flash drive FORMATTED TO FAT32 (annoying as hell) But you NEED a USB-C to OTG Adapter to attach a Flash Drive / SDCARD this way). If you don't have one, you better reflash TWRP using the prior instructions and flash the update.zip from there. Install, select the update.zip, flash. Wipe Data, Cache, ART/Dalvik. Reboot.
Now it should WIPE the entire phone and be back to normal Android 10 setup non rooted, no unlocked bootloader. Always beware of data loss doing root functions!!! Always be prepared to setup your phone entirely over again. Google Backup is very good to turn on before you do any of this stuff if you have already installed apps.
*** WARNING - THIS BYPASS METHOD COULD GO AWAY AT ANYTIME. IT SHOULD EVENTUALLY BE FIXED BY NUBIA ***
mslezak said:
{Mod edit}
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
Settings / About phone / Build # click 7 times, now your a dev message appears, good back a menu, go to Additional Settings / Developer Options
Enable:
ADB debugging, + OEM unlock
Connect phone to PC, approve device on phone RSA key for USB debugging
From Minimal ADB and Fastboot:
adb reboot bootlader
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing unlock
(approve on phone with volume keys to unlock and hit the power button, now you'll get an annoyng mesage on boot as insecure unlocked BL) *ALL YOUR DATA WILL BE WIPED*
Next:
fastboot flash recovery recovery-TWRP-3.4.1B-0324-NUBIA_REDMAGIC_5G-CN-wzsx150.img
fastboot reboot recovery
Enter TWRP, set to not be removed by updates if prompted.
Boot up the device, setup as a new device. You're on stock ROM / kernel now unlocked.
Once you get up and running you'll want APK Mirror app to install stuff on the China Variant it's in the Nubia Playstore. Gboard download as well and set as default it's a lot easier than the Chinese keyboard that swaps between Chinese and English. Set size extra tall for this huge phone (I prefer anyhow). Chrome go download it from APK Mirror app as well. Then go to XDA and Download Magisk Manager and download it and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power). Flash Magisk from TWRP reboot and you'll have root.
Note on my testing the fingerprint did not work after unlocking the bootloader. It says to contact Nubia support at some odd number. Hopefully they fix this.
Click to expand...
Click to collapse
You were able to actually install TWRP? Not just boot it? I thought A10 devices cant have twrp permanently installed?
That is a very good question my friend. I had to reflash it several times while rooting so it appears you are correct.
Now a window when I FIRST installed popped up and said make Recovery read only so a system update. can't overwrite it, to this I didn't even pay attention. So assuming that question does lock down recovery, it should stick.
mslezak said:
That is a very good question my friend. I had to reflash it several times while rooting so it appears you are correct.
Now a window when I FIRST installed popped up and said make Recovery read only so a system update. can't overwrite it, to this I didn't even pay attention. So assuming that question does lock down recovery, it should stick.
Click to expand...
Click to collapse
So its not permanent? Thats what I thought.
Well it could be permanent...
VZTech said:
So its not permanent? Thats what I thought.
Click to expand...
Click to collapse
What I was trying to say is that I've never had a phone where I had to select "prevent recovery from being overwritten" so I just clicked off the message. Had I selected "keep TWRP from being overwritten" then possibly it sticks. It's just a matter of making the recovery partition READ ONLY.
mslezak said:
What I was trying to say is that I've never had a phone where I had to select "prevent recovery from being overwritten" so I just clicked off the message. Had I selected "keep TWRP from being overwritten" then possibly it sticks. It's just a matter of making the recovery partition READ ONLY.
Click to expand...
Click to collapse
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe
Can anyone send me backup of the super partition?
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)
Future updates...
VZTech said:
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe
Click to expand...
Click to collapse
Yes what I've been told by prior Redmagic Users 3 and 3S is the ROM is released, as long as your boot.img is not patched with Magisk, it can be installed through the menus in Settings / About Phone / Update or someplace like that. You just download the ROM to the appropriate folder on the phone.
So far I have 1 link to a China ROM update here: https://ui.nubia.cn/rom/detail/65
Now on how to install the ROM, I use the Chrome browser set to autotranslate webpages. Most of the Chinese will be translated from here: https://bbs.nubia.com//thread-1136030-1-1.html
Basically it's going to wipe your device clean, and you can use a Nubia backup tool which will save all your items to a folder. Which then you should copy to your PC before installing the new ROM. Then it gives you instructions to get that data back onto your updated device.
apersomany said:
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)
Click to expand...
Click to collapse
Your probably screwed. I had this issue on a rm3s. You will need an unbrick tool. It was released for the rm3s about 4 mos after release. NUBIA should have true fastboot images available for download, but they dont.
VZTech said:
Your probably screwed. I had this issue on a rm3s. You will need an unbrick tool. It was released for the rm3s about 4 mos after release. NUBIA should have true fastboot images available for download, but they dont.
Click to expand...
Click to collapse
That's because of the super (dynamic) partition, see from the latest (and only) ROM:
Excerpt of the ROM installation script where it delineates the dynamic vs non dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm, The other files (boot.img, dtbo.img, splash.img, etc. and other various files) should be flashable with fastboot.
# Update dynamic partition metadata
assert(update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")));
unmap_partition("product");
block_image_update(map_partition("product"), package_extract_file("product.transfer.list"), "product.new.dat.br", "product.patch.dat");
unmap_partition("vendor");
block_image_update(map_partition("vendor"), package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat");
unmap_partition("system");
block_image_update(map_partition("system"), package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
unmap_partition("odm");
block_image_update(map_partition("odm"), package_extract_file("odm.transfer.list"), "odm.new.dat.br", "odm.patch.dat");
# --- End patching dynamic partitions ---
apersomany said:
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)
Click to expand...
Click to collapse
You should be able to flash the latest ROM via EDL mode if you've ever used EDL mode before, it usually requires shorting pins together in the device, although some recoveries will let you just boot into EDL mode if the phone still boots. It will be detected. Although on this device with the dynamic partition, I don't know how you would flash these in EDL mode... dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm that do not look like fastboot flashable parts. Possibly the unbrick tool for Redmagic 3/3S could be modified to do this for you.
mslezak said:
That's because of the super (dynamic) partition, see from the latest (and only) ROM:
Excerpt of the ROM installation script where it delineates the dynamic vs non dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm, The other files (boot.img, dtbo.img, splash.img, etc. and other various files) should be flashable with fastboot.
# Update dynamic partition metadata
assert(update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")));
unmap_partition("product");
block_image_update(map_partition("product"), package_extract_file("product.transfer.list"), "product.new.dat.br", "product.patch.dat");
unmap_partition("vendor");
block_image_update(map_partition("vendor"), package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat");
unmap_partition("system");
block_image_update(map_partition("system"), package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
unmap_partition("odm");
block_image_update(map_partition("odm"), package_extract_file("odm.transfer.list"), "odm.new.dat.br", "odm.patch.dat");
# --- End patching dynamic partitions ---
Click to expand...
Click to collapse
Yes those .img files can easily be fastboot flashed. Unfortunately it wont solve his problem. He needs the nubia unbrick tool, which is tough to get. I dont understand why Nubia makes things difficult. They should provide proper Fastboot files.
I already tried edl (not to flash, but to recover my backup of the super partition) but it seems like it needed a firehose binary. I still can use bootloader, fastbootd, recovery. It's just that the recovery fails at assert dynamic partition update thing with a error 7 (probably because my super partition turned into a normal partiton). I tried to flash a super empty image made with lpmake and try flashing the ota but that didn't work. I think if someone gives me a backup of the super partition I could flash that and that could work. I also had an idea of flashing a super partition of another devices factory image to make my super partition a dynamic partition, but I couldn't find any online.
apersomany said:
I already tried edl (not to flash, but to recover my backup of the super partition) but it seems like it needed a firehose binary. I still can use bootloader, fastbootd, recovery. It's just that the recovery fails at assert dynamic partition update thing with a error 7 (probably because my super partition turned into a normal partiton). I tried to flash a super empty image made with lpmake and try flashing the ota but that didn't work. I think if someone gives me a backup of the super partition I could flash that and that could work. I also had an idea of flashing a super partition of another devices factory image to make my super partition a dynamic partition, but I couldn't find any online.
Click to expand...
Click to collapse
I get a Global Device on Monday. I'll try to use Qualcomm tools to make a brick restore image of Global. If I get one made I'll post all the tools to restore the device on Mega.nz. Because of the super partition it has to be done this way. Not via TWRP as you know. I'm working on Dev tools for this device as fast as possible.
mslezak said:
I get a Global Device on Monday. I'll try to use Qualcomm tools to make a brick restore image of Global. If I get one made I'll post all the tools to restore the device on Mega.nz. Because of the super partition it has to be done this way. Not via TWRP as you know. I'm working on Dev tools for this device as fast as possible.
Click to expand...
Click to collapse
Thank you so much!
Okay I can't add anything special but daaamn this community is amazing. So much help I love you all
To relock BL repeat the instructions with 1 different command
Just replace
fastboot flashing unlock
with
fastboot flashing lock
Again you approve to lock on the phone prompt with the volume keys and your phone will be wiped and all will be back to normal, you'll be locked. And back to phone setup.
I'd edit the original post but the moderators took away my rights!!! Because I posted a Telegram link WHY - how do you expect development to get better???
BTW anyone with a NEW phone arriving that can record the FP failures and all errors please contact me so I can send to Nubia. They are waiting for me to reproduce the error but I already setup my new phone... Thinking I wouldn't be the ONLY ONE to contact [email protected] ... Guys you want developer support on this phone or not. Contribute please.
mslezak said:
{Mod edit}
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
Settings / About phone / Build # click 7 times, now your a dev message appears, good back a menu, go to Additional Settings / Developer Options
Enable:
ADB debugging, + OEM unlock
Connect phone to PC, approve device on phone RSA key for USB debugging
From Minimal ADB and Fastboot:
adb reboot bootlader
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing unlock
(approve on phone with volume keys to unlock and hit the power button, now you'll get an annoyng mesage on boot as insecure unlocked BL) *ALL YOUR DATA WILL BE WIPED*
Next:
fastboot flash recovery recovery-TWRP-3.4.1B-0324-NUBIA_REDMAGIC_5G-CN-wzsx150.img
fastboot reboot recovery
Enter TWRP, set to not be removed by updates if prompted.
Boot up the device, setup as a new device. You're on stock ROM / kernel now unlocked.
Once you get up and running you'll want APK Mirror app to install stuff on the China Variant it's in the Nubia Playstore. Gboard download as well and set as default it's a lot easier than the Chinese keyboard that swaps between Chinese and English. Set size extra tall for this huge phone (I prefer anyhow). Chrome go download it from APK Mirror app as well. Then go to XDA and Download Magisk Manager and download it and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power). Flash Magisk from TWRP reboot and you'll have root.
Note on my testing the fingerprint did not work after unlocking the bootloader. It says to contact Nubia support at some odd number. Hopefully they fix this.
Click to expand...
Click to collapse
Just in case if somebody need a Chinese version of official ROM v2.46 for RedMagic 5G.
Code:
https://mega.nz/file/vc0DiabR#npahTop-JXZ9Mwv-lA7G6DxTG2qqOOAf6AwW8NdEEKw
mslezak said:
Just replace
fastboot flashing unlock
with
fastboot flashing lock
Again you approve to lock on the phone prompt with the volume keys and your phone will be wiped and all will be back to normal, you'll be locked. And back to phone setup.
I'd edit the original post but the moderators took away my rights!!! Because I posted a Telegram link WHY - how do you expect development to get better???
BTW anyone with a NEW phone arriving that can record the FP failures and all errors please contact me so I can send to Nubia. They are waiting for me to reproduce the error but I already setup my new phone... Thinking I wouldn't be the ONLY ONE to contact [email protected] ... Guys you want developer support on this phone or not. Contribute please.
Click to expand...
Click to collapse
we found out that using the cn rom it all works without even unlocking the bootloader, even while oem unlock was disabled in dev options but there is some kind of vbmeta img required. a full guide is incoming.
VZTech said:
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe
Click to expand...
Click to collapse
You can flash their NX659J-update.zip files directly from TWRP that's how we restored our bricked devices already. So OTA updates no, but you can download them anyway and flash from TWRP directly. Yes we have to figure out a concrete restore method which isn't 100% working yet. I.e. all your data is lost this way apparently AT THIS MOMENT... MORE TO COME.