Related
Hello guys,
At the moment I have a problem with my Huawei. So let me tell you how it all began.
Two weeks ago I was still on Android 5.xx and wanted to update my phone and there I already did something stupid. My Phone was rooted with the old "chinese" method and I started an OTA Update. Which failed and TWRP was randomly gone after that I was in a bootloop. So I restored my phone with a B330 Firmware which was placed on my SD Card. It worked after that and I could install the further updates (B380 atm). Now I wanted to root my phone again and install a custom rom because my 16gb Phone can only use 3.5 GB which are already 80% full.
My Problem now is that neither Hisuite or fastboot can detect the device when it is in fastboot mode. I also tried it on a second pc and my honor never gets recognized and therefore I can neither root my phone or install twrp. What I now tried is to install B330 again and see what happens if I enter fastboot from there, but the Recovery "App" seems to be stuck at 5% of the update process. At the moment I try to install the B130, but it also seems to be stuck at 5%.
Do you guys know something that I can do?
try to use the rollback file (B300) before you try to use other rom versions like B380 /B190 etc!
-> http://www.hihonor.com/de/support/software-list/index.html
BTW: I think, you will have a problem because you have not rooted your system "systemless"!
Your system partition was changed during rooting. The update check the system checksum and this procedure seems to fail at your device.
Maybe the multitool could be a help.
The Rollback is also stuck at 5%.
I mean I got it to recover the phone with the recovery mode. Just now after the OTA Updates it seems like it isn't possible.
I can try the multitool it is just super slow with all it's updating.
Edit: Also If I try to use the normal eRecovery i get "Getting package info failed" . Got it now several times
Edit2: No Idea how the Tool should help. It always requires fastboot. Seems like I ****ed up big time.
Edit3: My honor is recognized as Fastboot 2.0 is that correct?
Maxx2332 said:
The Rollback is also stuck at 5%.
I mean I got it to recover the phone with the recovery mode. Just now after the OTA Updates it seems like it isn't possible.
I can try the multitool it is just super slow with all it's updating.
Edit: Also If I try to use the normal eRecovery i get "Getting package info failed" . Got it now several times
Edit2: No Idea how the Tool should help. It always requires fastboot. Seems like I ****ed up big time.
Edit3: My honor is recognized as Fastboot 2.0 is that correct?
Click to expand...
Click to collapse
Do you have ADB and fastboot set up in a PC? You should have rooted your phone systemlessly in the first place.
Sent from my Galaxy Tab 3 using XDA Labs
adriansticoid said:
Do you have ADB and fastboot set up in a PC? You should have rooted your phone systemlessly in the first place.
Sent from my Galaxy Tab 3 using XDA Labs
Click to expand...
Click to collapse
http://forum.xda-developers.com/honor-7/general/how-to-root-honor-7-t3170735
This is what I used. So it' just TWRP and SuperSU from a chinese guy. What do you guys mean with systemlessly?
And yeah I have fastboot and ADB installed. I still use the same PC and the second PC also has it installed.
Maxx2332 said:
http://forum.xda-developers.com/honor-7/general/how-to-root-honor-7-t3170735
This is what I used. So it' just TWRP and SuperSU from a chinese guy. What do you guys mean with systemlessly?
And yeah I have fastboot and ADB installed. I still use the same PC and the second PC also has it installed.
Click to expand...
Click to collapse
The other guy said your syatem was modified. So I thought your root access was not syatemless. Sytemless root is a tyoe of root method that doesn't modify the system partition so you will still receive OTA updates. If you really can't do OTA, just download your desired version of firmware amd flash it it fastboot. Use Huawei Update Extract Tool to get the images. system.img, boot.img and recovery.img.
Sent from my Galaxy Tab 3 using XDA Labs
adriansticoid said:
The other guy said your syatem was modified. So I thought your root access was not syatemless. Sytemless root is a tyoe of root method that doesn't modify the system partition so you will still receive OTA updates. If you really can't do OTA, just download your desired version of firmware amd flash it it fastboot. Use Huawei Update Extract Tool to get the images. system.img, boot.img and recovery.img.
Sent from my Galaxy Tab 3 using XDA Labs
Click to expand...
Click to collapse
And like I said: Both PC can't access my phone through fastboot. I will try it out with Linux soon. If I could use the fastboot commands it would be pretty easy.
Maxx2332 said:
And like I said: Both PC can access my phone through fastboot. I will try it out with Linux soon. If I could use the fastboot commands it would be pretty easy.
Click to expand...
Click to collapse
Goodluck man.
Sent from my Galaxy Tab 3 using XDA Labs
My p9000 is currently on 20160810 and I'm unable to do the OTA update to 20170112, every time it downloads and starts to install it just stays on "rebooting" but does nothing.
On top of that I've tried to connect it up to a PC to flash it instead (was looking to try Nougart), I've managed to succesfully install the drivers but whatever PC I plug it into when powered off the PC recognises it for a few seconds and then disconnect again. So I have no device in device manager to try to play with the drivers, although as I mentioned I have already installed them sucessfully.
Should also mention I can't hard reset it with the power and voulume+ option either, as unable to enter recovery.
I've tried with Windows 7/8.1/10 all with the same result. The only difference is on the windows 7 machine it recognises it as the mtx65preloader device for a split second.
But to confuse things now more, on my windows 8.1 device the elephone is no longer recognised as a storage device, it shows as a connected device but there is no access to the drive.
The only way to go to the newer 2017 versions of the stock roms (nougat or marshmallow) is to use spflashtools. It is because elephone broke the recovery in 2016810. So when you try to update it will fail because the stock recovery is broken.
Have you disabled the driver signature in windows 10/ 8/ 7 before installing the mtk drivers? Else the installation will fail and you won't have the drivers installed at all.
I used this tutorial and it works for me on windows 10.
https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
Hexyl said:
The only way to go to the newer 2017 versions of the stock roms (nougat or marshmallow) is to use spflashtools. It is because elephone broke the recovery in 2016810. So when you try to update it will fail because the stock recovery is broken.
Have you disabled the driver signature in windows 10/ 8/ 7 before installing the mtk drivers? Else the installation will fail and you won't have the drivers installed at all.
I used this tutorial and it works for me on windows 10.
https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
Click to expand...
Click to collapse
Drivers were all installed fine, but the strangness continued today but for the good. On the Windows 7 machine I managed to flash the Nougart rom and now all is working great. So after days of nothing working it just suddenly decide to co-operate.
with a "broken" recovery, isn't dangerous to do any update operations? if something get corrupted how can you resolve?
Hexyl said:
The only way to go to the newer 2017 versions of the stock roms (nougat or marshmallow) is to use spflashtools. It is because elephone broke the recovery in 2016810. So when you try to update it will fail because the stock recovery is broken.
Have you disabled the driver signature in windows 10/ 8/ 7 before installing the mtk drivers? Else the installation will fail and you won't have the drivers installed at all.
I used this tutorial and it works for me on windows 10.
https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
Click to expand...
Click to collapse
Fabioamd87 said:
with a "broken" recovery, isn't dangerous to do any update operations? if something get corrupted how can you resolve?
Click to expand...
Click to collapse
You simply can't do an ota update if the phone has a broken recovery. It won't install because it fails booting in the recovery. So nothing goes corrupted.
no I mean if the flash fails how you can recover without a working recovery mode?
Well mines been working without a problem for the past week, quite impressed with it.
Fabioamd87 said:
no I mean if the flash fails how you can recover without a working recovery mode?
Click to expand...
Click to collapse
Then try to Flash again. As far as I know the stock recovery can't restore backups. It is for installing ota updates and etc, I think. If you want to backup your ROM then flash a custom recovery with sp flashtools.
Can I flash again if the first flash fails? from where I do it , there is some kind of "download mode/fastboot"? Do I need to root the phone to flash a custom recovery?
thanks
Fabioamd87 said:
Can I flash again if the first flash fails? from where I do it , there is some kind of "download mode/fastboot"? Do I need to root the phone to flash a custom recovery?
thanks
Click to expand...
Click to collapse
I assume you have never installed a ROM/recovery before on your phone (with a mediatek soc). In that case, you flash your phone with a PC. You flash the phone with a program called "sp flashtools".
So the very first time you want to install a CUSTOM ROM/recovery. ---> use sp flashtools.
If you already have a custom recovery installed ----> boot the phone up in recovery (holding power button and volume +. If elephone logo appears, release power button but keep pressing volume +) and install custom ROM from there.
If you want to flash a STOCK rom ( nougat or marshmallow) -----> use sp flashtools.
You do not need a rooted phone for flashing a custom recovery.
For sp flashtools tutorials etc, look it up on XDA or just Google some spflashtool tutorials. The steps are the same for most mtk phones.
Would anyone help me get root on doogee bl 12000? This is a version without a pro so this is a different topic than this one.
No kingoroot or framaroot programs work.
I have flashtoola and rom for this phone. I tried using adb to upload files with the 12000 pro doodge but there was always some error.
I also tried to upload files via flashtoola and recovery. However, without success.
Root Doogee BL12000
Hallo there. I'm trying to root my Bl12000. I've got a TWRP from twrp builder. It works, but whatever zip file I'm trying to install I always get "failed to mount data", invalid argument. The twrp also tells me, that there's bo OS installed, but there is. Phone is working fine after reboot. SuperSu can't be installed. Full wipe is not possible, also "failed to mount" and so on.
any help ?
Tia, Chris
I think it's the encryption. Any ideas how to remove it?
Installed twrp via fastboot and sp flash tool, but I can't boot phone into it. Searched dozens of sites, no success. Flashed the twrp again with sp flash tool and according to sp it was successful. I tried several ways to boot the phone into it afterwards, no luck
My goal is to root this phone only. I'm not very experienced so if anyone could please give me a hand here and tell me where or what I'm doing wrong, that'd would be great and much appreciated. Thanks.
Ok. If I flash the twrp with Sp flash tool and type "fastboot reboot" on the adb console, sending the command while I hold vol+ and power-, the phone boots into the twrp. Next time it will be gone, so I have to flash it again. Noticed that, done.
But all this is taking me nowhere, because the encryption still prevents me from installing any zip file or format a partition. Yuck ?
Root Bl12000
Since the SuperSu method took me nowhere I decided to try Magisk. And.......HURRAY !!!!!!.......it worked.....for a moment. Booted the patched boot.img and got superuser. But with the first reboot I got stuck in bootloop. Tried again, in case I missed something, but same ****.
IT WORKS !!!!! My mistake was to assume, that Magisk works the same way as rooting with SuperSu does. So after rooting with Magisk I tried to install root apps as I was used to, but Magisk does not work that way.
Well, it'll take me awhile to figure this out ?
Why does an app keep coming back on my phone after I have done factory reset?
Christian1968.Bolz said:
Hallo there. I'm trying to root my Bl12000. I've got a TWRP from twrp builder. It works, but whatever zip file I'm trying to install I always get "failed to mount data", invalid argument. The twrp also tells me, that there's bo OS installed, but there is. Phone is working fine after reboot. SuperSu can't be installed. Full wipe is not possible, also "failed to mount" and so on.
any help ?
Tia, Chris
I think it's the encryption. Any ideas how to remove it?
Installed twrp via fastboot and sp flash tool, but I can't boot phone into it. Searched dozens of sites, no success. Flashed the twrp again with sp flash tool and according to sp it was successful. I tried several ways to boot the phone into it afterwards, no luck
My goal is to root this phone only. I'm not very experienced so if anyone could please give me a hand here and tell me where or what I'm doing wrong, that'd would be great and much appreciated. Thanks.
Lucky Patcher 9Apps VidMate
Ok. If I flash the twrp with Sp flash tool and type "fastboot reboot" on the adb console, sending the command while I hold vol+ and power-, the phone boots into the twrp. Next time it will be gone, so I have to flash it again. Noticed that, done.
But all this is taking me nowhere, because the encryption still prevents me from installing any zip file or format a partition. Yuck
Click to expand...
Click to collapse
This Recovery is only supported for Doogee BL12000
You should have either PC or Laptop.
Make sure to charge your phone for at least 50%.
Download and install latest Doogee USB Drivers on your PC/Laptop [All Android USB Drivers]
Download the SP Flash Tool Software
VCOM driver: Download – Instal the VCOM Driver on your computer (still compatible with MT67xx phones)
Before flashing a custom recovery, you need to unlock the bootloader on Doogee BL12000
Take a full backup just in case if you need it later
TWRP+root bl 12000
joachim97 said:
Would anyone help me get root on doogee bl 12000? This is a version without a pro so this is a different topic than this one.
No kingoroot or framaroot programs work.
I have flashtoola and rom for this phone. I tried using adb to upload files with the 12000 pro doodge but there was always some error.
I also tried to upload files via flashtoola and recovery. However, without success.
Click to expand...
Click to collapse
On the forum 4pda can be found for bl 12000
TWRP+ROOT
when you install twrp formatting you can not do it, but immediately install magisk and reboot ...
I just bought a Nuu R1 Rugged Phone. It has Oreo 8.1.0 on it.
It is an "unlocked" phone. But I don't know if unlocked refers to the phone carrier or to the boot loader. (I'm thinking phone carrier.)
The last I rooted my tablets was Android 5, which required using a custom script that a dev here wrote that temporarily ran CW via fast boot.
I would like to root my R1. I hear now that Magisk is the way to go. (Instead of SU.)
Most every Guide says that I have to have TWRP installed before installing Magisk. But there's no TWRP for the R1. And I am incapable of compiling my own.
I learned, from Nuu Tech Support, that I can get into the phone's Recovery mode with some hidden button pushes. Here's a screen shot:
My first question is, could I simply install Magisk by selecting "Update from SD card"?
If it's not that easy, then, second: I can also get to a fastboot screen. (Not shown here.) Could I install Magisk from ADB on my computer?
I suppose a third question: Is there a version of TWRP that's compatible with this phone? And if so, how do I find it? It would be nice to have a Nandroid backup.
I am willing to show various screens that come up from various button pushes if that would help a dev here.
More data for TWRP'ing
So, I see that one needs an image of the OEM ROM to compile TWRP. I found two sites on the web that claim to have the ROM. (Before the R1 was officially released.) Sounds sketchy. Will try to get an image from Tech Support.
In the meantime, I found that the bootloader can be unlocked (or allowed to be unlocked) via a setting under Developer Options.
I contacted Nuu Mobile Support and they were kind to send me the MediaTek USB drivers for the R1.
It was a two step process to get the driver installed for ADB. But now I have access to the R1 via ADB.
I read here on the forums that I can boot TWRP via fastboot, and not risk ruining/corrupting the R1's Recovery Partition.
Anyone know of a TWRP model version that's close enough to work on the R1? (I presume a TWRP for another MediaTek device might work?)
I would hate to try KingRoot to get root.
I found a website called unofficialtwrp.com. It has a TWRP for the MediaTek 6739, running Oreo 8.1, with 16/2 GB. That's exactly what the Nuu Mobile R1 has.
So, hopeful that this would allow me to root my R1, I tried it. (Short version: Didn't work.)
I already had ADB installed and could talk to my R1 via ADB.
But once the R1 had booted into fastboot mode via ADB, I got a message from fastbood devices that it was "waiting."
I learned that that message means that I didn't have drivers for fastboot.
I ended up installing a fresh version of Win8.1 and using the Windows' updater to find the needed drivers. I had to have the R1 plugged in to the USB in fastboot mode for this to work. After that, I could talk to the device via the fastboot command.
So I unlocked the boot loader (which wiped my data - not every Guide warns you about that) and I did "fastboot boot recovery.img."
I got the message that the recovery file had transferred. After abotu 15 seconds, the phone rebooted. But no TWRP.
Rats.
I didn't want to try the fastboot flash command in case this unoffiical twrp from an unofficial site bricked my phone. If I understand things correctly, booting in fastboot to the recovery.img should give me a temporary instance of TWRP.
Presumably, after copying Magisk into memory, I would be able to get root that way.
PMikeP said:
I found a website called unofficialtwrp.com. It has a TWRP
Click to expand...
Click to collapse
Whoa you have been busy you must've heard XDA helps those who help themselves.. :highfive:
I just dropped by to say, 1st rule of modding is taking a pristine stock backup..
For MTK devices, there is a tool called SP Flash Tools, a quick search will help you take a full backup using this tool.
Afterward, you can even try using SP Flash Tools to flash a Magisk patched boot image to your device for ROOT!
Hope this helps!
Thanks. I did see SP Flash Tools mentioned and I did take a look at it. While I've rooted before, I'm trying to get my head around a Scatter File.
Everything I've read so far - well, almost everything - says that I need TWRP to get Magisk installed. But if you think it can be done via SP Flash Tools, I'll start playing with it.
Root nuu r1
Did u ever manage to figure out how to do this & get TWRP to install? :fingers-crossed:
No, I haven't had time to play with rooting lately. I still would like to root it tho.
Anyone know how to root the nuu phones?
someone has the boot.img i need the image
I will port TWRP for you in case you have stock recovery.img
jjgvv said:
I will port TWRP for you in case you have stock recovery.img
Click to expand...
Click to collapse
plis
do you have stock rom?
Doing this quick update because today, when trying to root my phone, bricked it several times and lost all app info
If you are using android 7.11, this guide works fine: https://forum.xda-developers.com/zenfone-3-zoom/how-to/how-to-root-zenfone-3-zoom-ze553kl-t3622256
If on android 8, SuperSU will brick your phone. Use Magisk instead:
- enable usb debug mode on your phone
- unlock bootloader
- plug phone into your computer
on your pc
- Download fastboot and adb:
* Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
* macos: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
* linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
- download the latest Magisk unlock script from https://github.com/topjohnwu/Magisk/releases and copy it to a MicroSD or USB that you can attach to your phone. Look for Magisk, not Magisk Manager
- download twrp v 3.1.0-0-Z01H-20170408: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w?E81jQTCD (this is from https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w, as described in the old root guide using twrp + supersu. It is supposed to be safe)
- `adb reboot bootloader`
- `fastboot flash recovery <path to twrp image downloaded>`
- `fastboot reboot`
Right now, you should probably backup your phone.
back on your phone:
- before booting, press volume up on the bootloader, there, select Recovery. Using fastboot to reboot into recovery might cause the stock recovery image to reflash
- if prompted to enable system modifications, allow it.
- If prompted to decrypt your data in TWRP, use the PIN you setup. If it doesn't work, I can't guarantee you won't brick our phone. Feeling brave enough? In case of brick keep reading, it is easy to restore your phone to stock Android 8 using official firmware.
- press install, choose the device attached to your phone that has Magisk-xxx.zip and select it
- flash the image and it should be OK
In case of brick or unsuccessful flash from SuperSU and without backup:
- Don't panic, like I did today
- download the latest firmware from Asus: https://www.asus.com/us/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_BIOS/
- follow this guide: https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
- when the phone reboots, boot into recovery
- enable ADB sideload
- on your pc: `adb sideload <path to newest firmare>`
- now follow the root guide above before starting your phone
- ???
- profit
Note: commands using adb and fastboot assume you have put the contents from the downloaded platform tools in your PATH, else execute them from the directory in which they were extracted, for instance, on linux:
- `cd /home/$USER/Downloads`
- `unzip platform-tools-latest-linux.zip`
- `cd platform-tools`
- `./adb devices`
Bricked my phone.
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
gchamon said:
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
Click to expand...
Click to collapse
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
This is strange. Magisk is supposed to patch the boot image and install its app (by the way, if you update magisk using the app, phone enters bootloop)
Anyway, I have encountered myself many problems when installing, but nothing like this. Bootloops and corruption message on bootloader yes, but I can't seem to recall anything about partitions not being mounted. If installing stock recovery image, boot image and system doesn't do the trick, in my experience it is either bad partitioning, although unlikely, because those procedures doesn't repartition anything, or bad internal storage.
But just to be sure, you should reflash stock 7.1 image (recovery, boot and system) with fastboot, enter stock recovery and wipe cache/factory reset. If your phone is physically healthy, this should work
anonymousbsb said:
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
Click to expand...
Click to collapse
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Enrico06 said:
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Click to expand...
Click to collapse
Cool, if this fixes the issue I will update the guide with this info
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
kingairtel08 said:
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
Click to expand...
Click to collapse
Downgrade to 7.1.1 and try it again.
Already tried on 7.1.1 lot of times same error shows.
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
normal. please wait 15min max
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
I can't really help you there. This guide is supposed to work for those who are able to unlock bootloader using official asus tools. Never heard of unofficial unlock methods. It is possible that you have a hardware problem if you use those tools and they just don't work.
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
Have you used the latest official unlocking tool? I see there's a July 2019 version available.
If you are on an older version of Android (not Oreo) are you presently still getting OTA update prompts?
I tried this tool but no result.
is it possible to root ZE553KL without loosing user application's data? I have unrooted device, wanted to migrate telegram secret chats to new phone. it is doable but with rooted smartphone only. if rooting process is destructive I cannot migrate. if rooting is doable with preserving installed applications along with their data then there is a hope for successful migration.
does this method look promising or it is just fake method?
Asus Zenfone 3 Zoom ZE553KL root using Magisk [No need TWRP Recovery
How to root Asus Zenfone 3 Zoom ZE553KL with Magisk [no need TWRP recovery, easy method to rood your Android device.
www.mobilewithdrivers.com