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
Related
I have tried installing through ADB and used the one provided by KingOfMezi. Have also tried the automated installation of CATUVA21. It always brings me to the Huawei eRecovery. I have unlocked bootloader, USB Debugging is on too.
First indicate which version are you in, Noughat or Oreo ??? I say so bcoz there are separate recoveries for
the 2 versions of Android available here @ XDA
Also indicate what happens when you try to flash the TWRP after fastboot command, does it say
FAILED or any error or it installs properly ? Send screenshot of your fastboot command and its result
themagicalmage22 said:
I have tried installing through ADB and used the one provided by KingOfMezi. Have also tried the automated installation of CATUVA21. It always brings me to the Huawei eRecovery. I have unlocked bootloader, USB Debugging is on too.
Click to expand...
Click to collapse
If i were you dont install twrp now. On huawei nova 2i because the device is new. Developers of twrp have some issue to backup all of the system data. So it is useless and remember you cant update OTA. I rooted and install twrp now i regret. Because stock roms and software update are hard to find. And you cant flash it so easy. Im just giving you an idea.
Mate 10. So, I tried to install the latest EMUI version using HuRUpdater - bad idea. Now, my phone will not boot. I can enter EMUI Recovery Mode but when I try to receive download package, it says it can't be retrieved. I can also enter Fastboot Mode but the problem with that is that under Device Manager, it only gets recognized as, "Android Bootloader Interface."
Please, any help would be greatly appreciated.
edit: So, fastboot DOES work. What files from what version do I flash to return to stock recovery? I don't even know if Pie was actually written to the device or not before the device rebooted and wouldn't boot.
edit again: I have just successfully installed TWRP via fastboot but it hangs at startup screen - is this because it's not compatible with Pi?
So I've tried flashing ramdisk_recovery.img, kernel.img and system.img from the Pi version but I still can't factory reset the phone. It boots back to the white screen with the android dude and says, "Please update system again."
Any help would be appreciated...
Using Multi-Tool, it detects my device in Fastboot mode as still 8.0.0.143. So, I'm trying to flash System, Ramdisk, Cust, Recovery_Ramdisk and Userdata......all succeed, except one - Ramdisk.img. When I manually try to flash Ramdisk.img in command prompt, it also fails, "FAILED (remote: partition length get error)". In Multi-tool, the error is, "the size or path does not match the file system markup."
Please, does anyone have any other suggestions? I've been at this for nearly 12 hours straight.
I assume u have unlocked bootloader and frb unlocked too if both yes u can search in xda for zip file beta downy 0.4
It will help you to downgrade emui 9 to. Emui 8
If u have unlocked bootloader only I guess u need funky huawei to restore ur devise
I hope I did helped u
Thanks for the reply.
My bootloader is unlocked but how do I know if I have unlocked FRP?
And downy tool requires ADB but I can only access Fastboot.
edit: I just checked and my FRP is also unlocked. What now?
Tried Funky Huawei just now, no go. Still get package can't be received error in ERecovery after following all of the instructions. Have emailed them as that's what they suggest doing if it didn't work.
Not sure what else to try to be honest. How the hell does updating my phone from 8.0.0.143 to 9.0.0.159 with HuRUpdate brick my phone? Ffs.
essen212 said:
Tried Funky Huawei just now, no go. Still get package can't be received error in ERecovery after following all of the instructions. Have emailed them as that's what they suggest doing if it didn't work.
Not sure what else to try to be honest. How the hell does updating my phone from 8.0.0.143 to 9.0.0.159 with HuRUpdate brick my phone? Ffs.
Click to expand...
Click to collapse
Well, it happened because HuRUpdater it's not supported on EMUI 9.0.
Ramdisk fails to flash because even if in fastboot your device is showing as 8.0.0.143, it has EMUI 9's partition layout, so no more ramdisk partition.
Try flashing a firmware with the DLOAD method (search on androidhost.ru for a firmware designed for your device/cust).
Pretoriano80 said:
Well, it happened because HuRUpdater it's not supported on EMUI 9.0.
Ramdisk fails to flash because even if in fastboot your device is showing as 8.0.0.143, it has EMUI 9's partition layout, so no more ramdisk partition.
Try flashing a firmware with the DLOAD method (search on androidhost.ru for a firmware designed for your device/cust).
Click to expand...
Click to collapse
Damn. Well, that makes perfect sense. A question - do I flash the 9.0.0 version or 8.0.0.143 version?
essen212 said:
Damn. Well, that makes perfect sense. A question - do I flash the 9.0.0 version or 8.0.0.143 version?
Click to expand...
Click to collapse
Try with EMUI 9 first, then, if it fails, try Oreo. The most important part is finding a DLOAD firmware for your cust/region.
I've fixed it!
Funky emailed me back and I ended up using a different method on their site which worked like a charm. I couldn't recommend them enough.
Hi, good to hear you got it sorted! Would you mind sharing the details on what you had to do differently with FHC? I'm in the same boat here with a mate 10 pro that died on emui9 and I'm not sure if I should go the FHC way or not...
Thx - David
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?
When attempting to flash TWRP through Odin I get a message on the screen that says, “Only official released binaries are allowed to be flashed(RECOVERY)”, after I hold the volume up, Bixby, and power buttons. Does anyone know why??
1. I have OEM Unlock on, but it somehow bypassed 7 days when I flashed from 8.0 to 9.0 Pie. It was not there until I flashed.
2. Download page says, “OEM LOCK: OFF”.
3. I have flashed back to stock 9.0 Pie firmware each time it failed and OEM Lock was still on the whole time.
4. I have even tried to trick to set the date back a month from latest security check date.
Not sure what I am doing wrong... Even though it says OEM is unlocked, do I still have to wait 7 days?
Thanks in advance.
JTM206 said:
When attempting to flash TWRP through Odin I get a message on the screen that says, “Only official released binaries are allowed to be flashed(RECOVERY)”, after I hold the volume up, Bixby, and power buttons. Does anyone know why??
1. I have OEM Unlock on, but it somehow bypassed 7 days when I flashed from 8.0 to 9.0 Pie. It was not there until I flashed.
2. Download page says, “OEM LOCK: OFF”.
3. I have flashed back to stock 9.0 Pie firmware each time it failed and OEM Lock was still on the whole time.
4. I have even tried to trick to set the date back a month from latest security check date.
Not sure what I am doing wrong... Even though it says OEM is unlocked, do I still have to wait 7 days?
Thanks in advance.
Click to expand...
Click to collapse
I wanted to know if you are only rooting the device or installing update ROMs or not.
If you are installing ROMs then you don't need to root your device there is another way too.
Sent from my P5 mini using premium XDA app
PrashannaGP said:
I wanted to know if you are only rooting the device or installing update ROMs or not.
If you are installing ROMs then you don't need to root your device there is another way too.
Sent from my P5 mini using premium XDA app
Click to expand...
Click to collapse
I am trying to run Magisk to hide the app to play PokémonGO with a joystick. Want to root it because it seems like the safest way.
JTM206 said:
I am trying to run Magisk to hide the app to play PokémonGO with a joystick. Want to root it because it seems like the safest way.
Click to expand...
Click to collapse
then you have to download stock rom for your device and also TWRP and replace the recovery file with twrp recovery and flash the recovery.img (downloaded recovery.img) for your device not stock rom with sp flash tool and flash the SuperSU.zip from twrp and again install magisk and its module. Done:good::good:
You are not supposed to allow it to boot with full stock firmware, ever. You should have intercepted the reboot and immediately flashed, twrp, magisk and the kernel patch.
pauaxe said:
You are not supposed to allow it to boot with full stock firmware, ever. You should have intercepted the reboot and immediately flashed, twrp, magisk and the kernel patch.
Click to expand...
Click to collapse
Yes but we can only do one thing. That is to unlock bootloader and then flash twrp from fastboot using
fastboot flash recovery ---------.img
fastboot reboot
adb devices
adb reboot recovery
press on INSTALL
select MAgisk.zip
reboot.
Done
Sent from my [device_name] using XDA-Developers Legacy app
PrashannaGP said:
Yes but we can only do one thing. That is to unlock bootloader and then flash twrp from fastboot using
fastboot flash recovery ---------.img
fastboot reboot
adb devices
adb reboot recovery
press on INSTALL
select MAgisk.zip
reboot.
Done
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Well if he is getting "Only official released binaries are allowed to be flashed(RECOVERY)" then he'll probably have to wait it out for 7 days anyway. That's why I said he shouldn't have let it boot, to avoid waiting 7 days.
Also there is no fastboot for Samsung phones.
pauaxe said:
Well if he is getting "Only official released binaries are allowed to be flashed(RECOVERY)" then he'll probably have to wait it out for 7 days anyway. That's why I said he shouldn't have let it boot, to avoid waiting 7 days.
Also there is no fastboot for Samsung phones.
Click to expand...
Click to collapse
Yes. That's right . Patience is important
Sent from my [device_name] using XDA-Developers Legacy app
In August, I bought this tablet, Lenovo TAB M10 (TB-X505F), to read and study for University. I rooted the device with Magisk. I also bought a 64 GB SD Card, which I installed and configured to expand the internal memory. About a month later, an OTA update failed to install; I removed the SD card, the OTA installed and the tablet went back to factory defaults; not pleasant, but not terrible. I reconfigured it, and kept using it.
Last couple of weeks, a new OTA was released. it tried to install a few times, and failed; just rebooted the OS with a generic failure message. One morning, it tried to update during the night, and I found it on the Recovery menu; a generic error message said it couldn't update. The OTA tried to update some more times, rebooting to the OS or going to the Recovery screen.
Yesterday, I removed the SD card and tried to install the OTA update; it failed, and sent the tablet again to factory defaults. Something happened, I can't tell what it was, and now the tablet is screwed. It won't boot; it won't go to recovery. I have no ADB, but I have Fastboot.
I worked with tablets and phones many times before: recovering, rooting, flashing, upgrading, downgrading, unlocking, unbricking, etc. I have the original ROM, and also the latest. I have the original boot.img, and the modified by Magisk. I tried to fastboot flash boot, recovery, and TWRP; it flashes "OK", but nothing happens: it won't boot to recovery. I tried to fastboot flash system, but it didn't do anything. This is a "system_1.img", "system_2.img", "system_n.img", not a ".sparsechunk"; I never had to deal with this one, I might be doing something wrong. I tried to fastboot flashall; nothing seems to work, although it looks like it is flashing ok. I don't know what to do or try anymore. Any help will be greatly appreciated. NB: I'm in Linux; I'll prepare a Windows box, in case it is needed.
Thank you very much. Best regards.
I suggest you to re-flash tablet's Stock ROM to bring tablet back to its original state.
FYI: Installing official updates from your manufacturer or carrier is not supported by TWRP.
jwoegerbauer said:
I suggest you to re-flash tablet's Stock ROM to bring tablet back to its original state.
FYI: Installing official updates from your manufacturer or carrier is not supported by TWRP.
Click to expand...
Click to collapse
Yes, thank you for your suggestion. Any ideas on how? I got the stock ROMs, but when I re-flash each partition, it says "flash OK", except with the System partition, which fastboot seems to not being able to handle this "system_1.img", "system_2.img", "system_n.img" format... Besides, the recovery partition flashed OK, but I'm not able to boot to recovery mode. The flashall didn't work either, with or without the -w argument. I'm on a Linux machine.
farotta said:
Yes, thank you for your suggestion. Any ideas on how? I got the stock ROMs, but when I re-flash each partition, it says "flash OK", except with the System partition, which fastboot seems to not being able to handle this "system_1.img", "system_2.img", "system_n.img" format... Besides, the recovery partition flashed OK, but I'm not able to boot to recovery mode. The flashall didn't work either, with or without the -w argument. I'm on a Linux machine.
Click to expand...
Click to collapse
There is a Lenovo smart assistant PC program
That can reflash firmware for some devices try the flash rescue option.
There is a link to download in my LMSA thread.
My thread is written for Motorola devices and I haven't used any Lenovo devices.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ocean using XDA Labs
sd_shadow said:
There is a Lenovo smart assistant PC program
That can reflash firmware for some devices try the flash rescue option.
There is a link to download in my LMSA thread.
My thread is written for Motorola devices and I haven't used any Lenovo devices.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
Thank you very much for your response. I'm assuming is a Windows tool... I'm finishing setting up a Windows box to test; I'll take a look at it as soon as I have it; I'll test it and post the results.
farotta said:
Yes, thank you for your suggestion. Any ideas on how? I got the stock ROMs, but when I re-flash each partition, it says "flash OK", except with the System partition, which fastboot seems to not being able to handle this "system_1.img", "system_2.img", "system_n.img" format... Besides, the recovery partition flashed OK, but I'm not able to boot to recovery mode. The flashall didn't work either, with or without the -w argument. I'm on a Linux machine.
Click to expand...
Click to collapse
Why not re-flash the Stock ROM by means of "adb sideload" instead of "fastboot ..."?
jwoegerbauer said:
Why not re-flash the Stock ROM by means of "adb sideload" instead of "fastboot ..."?
Click to expand...
Click to collapse
Because I didn't have adb, only fastboot.
sd_shadow said:
There is a Lenovo smart assistant PC program
That can reflash firmware for some devices try the flash rescue option.
There is a link to download in my LMSA thread.
My thread is written for Motorola devices and I haven't used any Lenovo devices.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
THIS THING WORKED LIKE MAGIC! THANK YOU VERY MUCH!
It was more difficult to set up the Windows box to make it work, than the rescuing of the tablet with this tool. A few clicks, wait for the image to download, follow some easy and clear instructions, and my device is alive, again. I feel I can't thank you enough.