Related
I was able to flash an EVGA ROM successfully and also Shaky156's CWM recovery. Primary reason was to get rid of Chinese notifications completely. Problem is that I cannot get the 1.1 OTA update to install because of the CWM recovery. I tried to flash stock recovery via fastboot but was not successful. Tried different versions even the BAT_CWM_recovery but it won't accept any except Shaky's version. Also tried the Super Tool but it won't recognize the tablet. I have previously installed the SDK and can get fastboot to run. Will try version 1.5 if it works.
Freeje said:
I was able to flash an EVGA ROM successfully and also Shaky156's CWM recovery. Primary reason was to get rid of Chinese notifications completely. Problem is that I cannot get the 1.1 OTA update to install because of the CWM recovery. I tried to flash stock recovery via fastboot but was not successful. Tried different versions even the BAT_CWM_recovery but it won't accept any except Shaky's version. Also tried the Super Tool but it won't recognize the tablet. I have previously installed the SDK and can get fastboot to run. Will try version 1.5 if it works.
Click to expand...
Click to collapse
Always erase the partition beforehand.
fastboot erase boot
then... as an example
fastboot flash boot boot.img
or
fastboot erase recovery
then... as an example
fastboot flash recovery recovery.img
Make sure you are cautious never to loose fastboot ability. Other words if your bootloader can't be obtained from restarting and hold buttons down, then make sure you don't restart till you get a successful flashing. Always have the system ADB enabled and certified with the computer.
e8hffff said:
Always erase the partition beforehand.
fastboot erase boot
then... as an example
fastboot flash boot boot.img
or
fastboot erase recovery
then... as an example
fastboot flash recovery recovery.img
Make sure you are cautious never to loose fastboot ability. Other words if your bootloader can't be obtained from restarting and hold buttons down, then make sure you don't restart till you get a successful flashing. Always have the system ADB enabled and certified with the computer.
Click to expand...
Click to collapse
Did what you said but still no stock recovery installed. When I reboot after erasing the old recover and flashing the stock instead of going to recovery it just boots up. Looks like the recovery never gets flashed. I did check if the tablet is being recognized by the computer before any flashing. After flashing the stock recovery it says okay so I don't know what's happening.
Freeje said:
Did what you said but still no stock recovery installed. When I reboot after erasing the old recover and flashing the stock instead of going to recovery it just boots up. Looks like the recovery never gets flashed. I did check if the tablet is being recognized by the computer before any flashing. After flashing the stock recovery it says okay so I don't know what's happening.
Click to expand...
Click to collapse
Have you done an OEM unlock?
fastboot oem unlock
e8hffff said:
Have you done an OEM unlock?
fastboot oem unlock
Click to expand...
Click to collapse
Yes, tablet is unlocked. Says so when I boot into the bootloader. I have flashed Shaky's CWM and it installed fine. Don't know why the tablet does not like the stock recovery. Even tried BAT-cwm recovery but also failed to install. I'll just have to wait for someone to come up with a flashable ROM if the Kitkat update comes around.
Freeje said:
Yes, tablet is unlocked. Says so when I boot into the bootloader. I have flashed Shaky's CWM and it installed fine. Don't know why the tablet does not like the stock recovery. Even tried BAT-cwm recovery but also failed to install. I'll just have to wait for someone to come up with a flashable ROM if the Kitkat update comes around.
Click to expand...
Click to collapse
Do your best to get Bat_recovery for the recovery parititon and the 4.3.1 boot.img for the boot partition, shared on my Tegra Note Discoveries thread. Never flash the bootloader partition unless you are really know what you're doing. Then possible flash the system partition with Tom's system.img with;
fastboot erase system
fastboot flash system system.img
Tom's image should patch and is an English styled setup so you get all the Google Apps, etc.
e8hffff said:
Do your best to get Bat_recovery for the recovery parititon and the 4.3.1 boot.img for the boot partition, shared on my Tegra Note Discoveries thread. Never flash the bootloader partition unless you are really know what you're doing. Then possible flash the system partition with Tom's system.img with;
fastboot erase system
fastboot flash system system.img
Tom's image should patch and is an English styled setup so you get all the Google Apps, etc.
Click to expand...
Click to collapse
Here's what I did:
1. Erased the system and flashed the 4.3plus system zip.
2. Erased the boot image and flashed the 4.3plus boot image.
3. Erased the recovery and flashed the bat recovery.
4. Rebooted and got stuck on the Tegra Note screen. (flashing on and off).
Tried to experiment and flashed another boot image and this time got stuck on the Tegra Note screen but this time it was not flashing on and off. Turned it off but nothing happened, Pressed the key combination to boot to the bootloader mode but failed. I thought I bricked it and then tried to go the the apx mode and was successful. This time I pressed the bootloader key combination and thankfully was successful. I thought I bricked the tablet.
Is there a way to flash the 4.2.2 ROM? Read somewhere that someone flashed the old ROM and the stock recovery. Once done he was able to update to 4.3plus. I thought there was a flashable 4.2.2 ROM at rootjunky.com but when I clicked on the link I got an error message saying that the file does not exist. I asked the poster where he got the ROM and recovery but never got a reply.
I'll try to flash the 4.3 ROM back
homecare tegra note 7
Freeje said:
Here's what I did:
1. Erased the system and flashed the 4.3plus system zip.
2. Erased the boot image and flashed the 4.3plus boot image.
3. Erased the recovery and flashed the bat recovery.
4. Rebooted and got stuck on the Tegra Note screen. (flashing on and off).
Tried to experiment and flashed another boot image and this time got stuck on the Tegra Note screen but this time it was not flashing on and off. Turned it off but nothing happened, Pressed the key combination to boot to the bootloader mode but failed. I thought I bricked it and then tried to go the the apx mode and was successful. This time I pressed the bootloader key combination and thankfully was successful. I thought I bricked the tablet.
Is there a way to flash the 4.2.2 ROM? Read somewhere that someone flashed the old ROM and the stock recovery. Once done he was able to update to 4.3plus. I thought there was a flashable 4.2.2 ROM at rootjunky.com but when I clicked on the link I got an error message saying that the file does not exist. I asked the poster where he got the ROM and recovery but never got a reply.
I'll try to flash the 4.3 ROM back
Click to expand...
Click to collapse
have you tried extracting the Rom and nvflash into the same folder and running the "download.bat" to fix this? I haven't found a nvflash that works with tegra note 7
Tha T said:
have you tried extracting the Rom and nvflash into the same folder and running the "download.bat" to fix this? I haven't found a nvflash that works with tegra note 7
Click to expand...
Click to collapse
Don't know how to do that.
I've managed to flash a 4.2.2 ROM (tried the deodex version first) but not the stock recovery. Funny thing is that only Shaky156's version can be flashed. The big problem with the ROM is that there's no wifi and that sucks big time. It means I can't update the the firmware. Will try to flash the odex version and see the wifi works. There's no access to the files too. Good thing the bluetooth works.
REcovry
pls, what recovery works best with the homecare tegra note? prefarably one that allows backup/restore with external sd card
Freeje said:
I've managed to flash a 4.2.2 ROM (tried the deodex version first) but not the stock recovery. Funny thing is that only Shaky156's version can be flashed. The big problem with the ROM is that there's no wifi and that sucks big time. It means I can't update the the firmware. Will try to flash the odex version and see the wifi works. There's no access to the files too. Good thing the bluetooth works.
Click to expand...
Click to collapse
so did the odex$.2.2 work fine or what solution did you use? And where did you get your 4.2 rom ?
Freeje said:
I've managed to flash a 4.2.2 ROM (tried the deodex version first) but not the stock recovery. Funny thing is that only Shaky156's version can be flashed. The big problem with the ROM is that there's no wifi and that sucks big time. It means I can't update the the firmware. Will try to flash the odex version and see the wifi works. There's no access to the files too. Good thing the bluetooth works.
Click to expand...
Click to collapse
The no wifi problem is endemic of a broken/mismatched boot.img to system version. Get an original (eg EVGA version) boot.img not a modified rooted version, since SuperSU sideloaded will give proper root later on top of an original boot.img.
I have boot.img shared on Tegra Note Discovery thread.
Try using rootjunkie supertool and get new kit kat or flash another ROM very easy to use
Sent from my Moto G using XDA Premium 4 mobile app
Tha T said:
pls, what recovery works best with the homecare tegra note? prefarably one that allows backup/restore with external sd card
Click to expand...
Click to collapse
I can only get Shakys156 recovery to work but it does not have backup/restore to ext sdcard.
recovery
Freeje said:
I can only get Shakys156 recovery to work but it does not have backup/restore to ext sdcard.
Click to expand...
Click to collapse
ok, thanks. And have you finally fixed your wifi issue? I'm on 4.3+ deodex and mine doesn't even rotate the screen
e8hffff said:
The no wifi problem is endemic of a broken/mismatched boot.img to system version. Get an original (eg EVGA version) boot.img not a modified rooted version, since SuperSU sideloaded will give proper root later on top of an original boot.img.
I have boot.img shared on Tegra Note Discovery thread.
Click to expand...
Click to collapse
Are these the files that you're referring to?
TegraNote_bootimg_4p4rip.zip
TegraNote_bootimg_4p3p1rip.zip
I tried flashing the deodex version of 4.3+ and then flashed the boot image (from TegraNote_bootimg_4p3p1rip.zip) but I still get no wifi.
Tha T said:
ok, thanks. And have you finally fixed your wifi issue? I'm on 4.3+ deodex and mine doesn't even rotate the screen
Click to expand...
Click to collapse
No luck. I tried what e8hfff suggested but still got no wifi. I used to have a Korean version of the Galaxy S3 and I could flash the modded ROMS made for the international version only if it is converted. Some guy came up with a converter and you flash it after you have flashed the modded ROM. We might have to get something similar if we want to flash EVGA ROMs.
Right now I'm not that concerned with getting the Kitkat update since there's something wrong with it (write to SD card). Once they have come up with an update to correct the bug then I'll give it another try. SO for now, I'll stick to the 4.3 ROM.
Freeje said:
Are these the files that you're referring to?
TegraNote_bootimg_4p4rip.zip
TegraNote_bootimg_4p3p1rip.zip
I tried flashing the deodex version of 4.3+ and then flashed the boot image (from TegraNote_bootimg_4p3p1rip.zip) but I still get no wifi.
Click to expand...
Click to collapse
Yes try, TegraNote_bootimg_4p3p1rip.zip first as I haven't tested the 4.4 boot.img, and only use the boot.img within as there is another directory of the uncompress boot.
wifi
Freeje said:
No luck. I tried what e8hfff suggested but still got no wifi. I used to have a Korean version of the Galaxy S3 and I could flash the modded ROMS made for the international version only if it is converted. Some guy came up with a converter and you flash it after you have flashed the modded ROM. We might have to get something similar if we want to flash EVGA ROMs.
Right now I'm not that concerned with getting the Kitkat update since there's something wrong with it (write to SD card). Once they have come up with an update to correct the bug then I'll give it another try. SO for now, I'll stick to the 4.3 ROM.
Click to expand...
Click to collapse
Does shaky156's version have a working wifi or any rom at all, (even 4.2) that has wifi, my TN7 is next to useless without it
Hey. I had rooted 5.1.1 Moto X Style and did a return to stock 5.1.1. eu version (relocked bootloader). After booted up, I received update to Marshmallow, I installed it. It worked. Later I wanted to root it, so I unlocked bootloader again and also did flash custom recovery - TWRP (twrp-2.8.7.1-clark). Later I restarted device and its was stuck on logo of Motorola. Nothing boots up.
Cant find solution for this. Thanks.
UPDATE:
Solved my issue here.
UPDATE2:
If there is problems upgrading your device to Marshmallow, I would suggest install custom ROM TruPureXMM with custom KERNEL Frankenclark. I am using this combo for long period of time and now I can suggest to others too!
Mine is having a similar issue. Mine took forever to boot at your stage because it formatted itself. Once I flashed SuperSU is where mine refused to boot. I have no idea what's going on either.
I am having the exact same issue. I updated to Marshmallow, installed TWRP (twrp-2.8.7.1-clark), flashed SuperSU and the phone hung on the Motorolla Logo at boot. I was still able to access the boot loader (holidng down the volume and the power button) and attempted to restore using http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905. I was able to restore however now my wifi does not work and therefore I cannot update to Marshmallow OTA.
dgato said:
I am having the exact same issue. I updated to Marshmallow, installed TWRP (twrp-2.8.7.1-clark), flashed SuperSU and the phone hung on the Motorolla Logo at boot. I was still able to access the boot loader (holidng down the volume and the power button) and attempted to restore using http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905. I was able to restore however now my wifi does not work and therefore I cannot update to Marshmallow OTA.
Click to expand...
Click to collapse
You need to reflash the LP radio from the restore all file ( NON-HLOS.bin ). That should do it.
I'm having the exact same issue. I'm so glad you posted. I gave up and used the restore-to-stock tool as well, but my Wi-Fi isn't working either. What is LP radio and how do I flash it? Now that I've restored to stock, I no longer have TWRP, and because I don't have WiFi, I can't update to Marshmallow.
JayShams said:
I'm having the exact same issue. I'm so glad you posted. I gave up and used the restore-to-stock tool as well, but my Wi-Fi isn't working either. What is LP radio and how do I flash it? Now that I've restored to stock, I no longer have TWRP, and because I don't have WiFi, I can't update to Marshmallow.
Click to expand...
Click to collapse
If you want WIFI on stock 5.1.1 you need to flash right modem for you.
You should download .zip file that contains all stock files, unzip it, and find "NON-HLOS.bin", thats modem file that you need.
Now boot into fastboot mode (power+volume down), and from PC use "fastboot flash modem NON-HLOS.bin"
Restart device, you should be okey now.
For XT1572 "STYLE" EU you can download this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTUU4cUVmcUtBTEU/view;
But for XT1575 "PURE" US use this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTl9Wd1JQX0hFejg/view.
If you are using other device, use this thread http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486 to find your device, but this threads links are very slow.
BooBzi said:
If you want WIFI on stock 5.1.1 you need to flash right modem for you.
You should download .zip file that contains all stock files, unzip it, and find "NON-HLOS.bin", thats modem file that you need.
Now boot into fastboot mode (power+volume down), and from PC use "fastboot flash modem NON-HLOS.bin"
Restart device, you should be okey now.
For XT1572 "STYLE" EU you can download this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTUU4cUVmcUtBTEU/view;
But for XT1575 "PURE" US use this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTl9Wd1JQX0hFejg/view.
If you are using other device, use this thread http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486 to find your device, but this threads links are very slow.
Click to expand...
Click to collapse
Terrific! It actually worked! Thank you.
Did you find a solution for it being stuck at Motorola logo? I was also stuck on that after installing TWRP.
ChadMan097 said:
Mine is having a similar issue. Mine took forever to boot at your stage because it formatted itself. Once I flashed SuperSU is where mine refused to boot. I have no idea what's going on either.
Click to expand...
Click to collapse
Looks like you flashed SuperSU but didn't flash the boot_root.img , or you can use the systemless root.
JayShams said:
Terrific! It actually worked! Thank you.
Did you find a solution for it being stuck at Motorola logo? I was also stuck on that after installing TWRP.
Click to expand...
Click to collapse
Nop, could find solution, so I did full wipe, and restored my backup file with 5.1.1. Also flashed stock logo, boot and modem, so it can boot my old 5.1.1. Moto.
Will wait for some kind of european ROM with Marshmallow, or TWRP update. Maybe later will try again to go fully stock and upgrade to Marshmallow, maybe will find something that will work, right now I just need my "phone" back so I can use it as daily driver.
I just finished flashing TruPureXMM. I'm in the middle of restoring all my apps, and I still need to re-fix the WiFi, but otherwise my experience is working well. You might want to check that out.
JayShams said:
I just finished flashing TruPureXMM. I'm in the middle of restoring all my apps, and I still need to re-fix the WiFi, but otherwise my experience is working well. You might want to check that out.
Click to expand...
Click to collapse
For wifi you should flash modem from his thread: https://www.androidfilehost.com/?fid=24269982087017262
Its Pure modem with band 12 fix.
I was using his Rom for some hours and didnt like it, my personal opinion:
Good: easy to install; twrp, supersu, xposed is working.
Bad: modified kernel (had more problems with it, it was draining battery so fast - 4 little cores was always online for ~900-1440MHz, and 1 big core always online for same frequancy as little cores, only one big core was going idle), so I didnt like all this modifications to stock kernel, also I didnt like that mine EU version now is listed as US version XT1575, and last that I noticed after some hours of usage is that on secret menu, mine 3G network was listed as WCDMA, but on EU of mine Style same 3G is using GSM auto method. I suppose that there can be some difficulties in EU countries - after changing settings to 4G, I loosed signal, and only after restart I got it back.
Thats the main reasons why I want european rom, or to modifie stock eu MM with xposed.
patt2k said:
Looks like you flashed SuperSU but didn't flash the boot_root.img , or you can use the systemless root.
Click to expand...
Click to collapse
I think in that case I did flash SuperSU the old way for Stock Moto Marshmallow. I then did a TWRP backup to go back to full stock and tried rooting using systemless, but something isn't right. It's showing up, apps are asking for permission, but its acting odd. The apps can't get permission and Viper for example just crashes and other apps just keep saying something is wrong. My TWRP is messed up to. It was pushed correctly, but it seems very unstable. I can't flash any ROMs and if I plug it into my computer to send a file, when I reboot it no longer shows it in my directory to install. Sometimes if I hit reboot device, it only reboots recovery or just ignores the command entirely. I think I will revert it back to moto standard and try again, but this has been a little weird.
ChadMan097 said:
I think in that case I did flash SuperSU the old way for Stock Moto Marshmallow. I then did a TWRP backup to go back to full stock and tried rooting using systemless, but something isn't right. It's showing up, apps are asking for permission, but its acting odd. The apps can't get permission and Viper for example just crashes and other apps just keep saying something is wrong. My TWRP is messed up to. It was pushed correctly, but it seems very unstable. I can't flash any ROMs and if I plug it into my computer to send a file, when I reboot it no longer shows it in my directory to install. Sometimes if I hit reboot device, it only reboots recovery or just ignores the command entirely. I think I will revert it back to moto standard and try again, but this has been a little weird.
Click to expand...
Click to collapse
Either do systemless or 2.52 had same issue til I flashed 2.52
Sent from my XT1575 using Tapatalk
Solved my issue here.
BooBzi said:
If you want WIFI on stock 5.1.1 you need to flash right modem for you.
You should download .zip file that contains all stock files, unzip it, and find "NON-HLOS.bin", thats modem file that you need.
Now boot into fastboot mode (power+volume down), and from PC use "fastboot flash modem NON-HLOS.bin"
Restart device, you should be okey now.
For XT1572 "STYLE" EU you can download this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTUU4cUVmcUtBTEU/view;
But for XT1575 "PURE" US use this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTl9Wd1JQX0hFejg/view.
If you are using other device, use this thread http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486 to find your device, but this threads links are very slow.
Click to expand...
Click to collapse
fastboot flash modem NON-HLOS.bin
Where and how do I type this? I have everything else done.
Hi,
I followed this instructions and I have two problems:
It only boots using flashboot boot boot.img (in fact I can't do the fastboot reboot-bootloader command because the previous command just boots the phone)
There's no wifi, I tried flashing the modem linked before but I think that's for 5.1.1 so it didn't work
donebrasko said:
fastboot flash modem NON-HLOS.bin
Where and how do I type this? I have everything else done.
Click to expand...
Click to collapse
For this you need adb files on your PC.
You should read this thread, for how to get this files on your PC.
Then:
Basically, open terminal within adb driver folder, connect phone via USB to PC with USB Debugging ON, and you are ready to go - boot your phone into fastboot mode (shut down phone first, and then power+volume down) and now your are ready to use this command: fastboot flash modem NON-HLOS.bin, but remember to put this "NON-HLOS.bin" file into folder where you opened terminal from.
But if you experience problems, I suggest just install TruPureXMM ROM. It whould be much easier!
Good luck!
Kennyeni said:
Hi,
I followed this instructions and I have two problems:
It only boots using flashboot boot boot.img (in fact I can't do the fastboot reboot-bootloader command because the previous command just boots the phone)
There's no wifi, I tried flashing the modem linked before but I think that's for 5.1.1 so it didn't work
Click to expand...
Click to collapse
Hello!
Have you read my other thread?
I have explained all my steps there, my device is Moto X Style (XT1572).
But I can suggest also use TruPureXMM ROM. Right now I am using this rom for about month, you could try it!
Good luck!
No luck with reflashing NON-HLOS.bin
I tried systemless root on my moto x pure marshamallow. Now the wifi is not working at all. I tried reflashing the NON-HLOS.bin but no luck there. Is there any way to solve this issue? Or should i revert back to lollipop seems like it is working just fine for others on lollipop.
[email protected]@lker said:
I tried systemless root on my moto x pure marshamallow. Now the wifi is not working at all. I tried reflashing the NON-HLOS.bin but no luck there. Is there any way to solve this issue? Or should i revert back to lollipop seems like it is working just fine for others on lollipop.
Click to expand...
Click to collapse
Lets start from beginning.
What is your device codename (region)?
Hi guys,
I have a honor 6 plus (PE-TL10), it was running EMUI 4. I flashed TWRP 2.8.7 and then wiped all partitions through it(cust,system,etc) then flashed stock recovery back, now i am trying to install EMUI 4.0.1(Android 6.0) via 3 buttons Huawei update but it stops at 5% and fails. Can you guys provide me with any help, I really need it.
Also now when i am trying to wipe data thru stock recovery i get an weird error message at almost 25% saying "reset balong modem setting fail", which making it more difficult to get back stock rom.
Just last question; the Unbrick option in the "HONOR_6_and_6Plus_Multi-Tool", wil it restore the device to stock rom and fully functional state after that or it will miss some parts of the stock rom ?
Many thanks and regards
demonjo2001 said:
Hi guys,
I have a honor 6 plus (PE-TL10), it was running EMUI 4. I flashed TWRP 2.8.7 and then wiped all partitions through it(cust,system,etc) then flashed stock recovery back, now i am trying to install EMUI 4.0.1(Android 6.0) via 3 buttons Huawei update but it stops at 5% and fails. Can you guys provide me with any help, I really need it.
Also now when i am trying to wipe data thru stock recovery i get an weird error message at almost 25% saying "reset balong modem setting fail", which making it more difficult to get back stock rom.
Just last question; the Unbrick option in the "HONOR_6_and_6Plus_Multi-Tool", wil it restore the device to stock rom and fully functional state after that or it will miss some parts of the stock rom ?
Click to expand...
Click to collapse
For you to restore to stock you need to flash boot, recovery, system and cust.
Make sure you have stock boot and recovery to for forced update (3 buttons).
What happens in most of the cases is boot and recovery files are corrupt.
I would try the unbrick of the Multitool. If it fails, I would flash manually all img files for each partition. But using the same firmware version as the last installed one.
Post your results and I will try to help.
1:Extract the ROM with huawei update extractor
2:download latest minimal adb and fastboot drivers and install them
3ut the extracted system.img,recovery.img,cust.img,boot.img and userdata.img into the fastboot.exe folder
4: boot into the fastboot mode
And finally flash the above mentioned imgs one by one with this command
fastboot flash XXX XXX.img
After flashing files type
Fastboot reboot
and every thing should be fine again
Sent from my H30-U10 using Tapatalk
zinko_pt said:
For you to restore to stock you need to flash boot, recovery, system and cust.
Make sure you have stock boot and recovery to for forced update (3 buttons).
What happens in most of the cases is boot and recovery files are corrupt.
I would try the unbrick of the Multitool. If it fails, I would flash manually all img files for each partition. But using the same firmware version as the last installed one.
Post your results and I will try to help.
Click to expand...
Click to collapse
Thank you for answering, I did used Huawei MultiTool and Unbricked my device. I flashed four img files(SYSTEM,CUST,RECOVERY,BOOT) and now i am back to stock rom and running smoothly.
I tried to use force update feature on my device after that but again i got the same result, it stopped at 5% and failed. I guess i will keep it the way it's now.
Many thanks; you guys are awesome!
hamzio7 said:
1:Extract the ROM with huawei update extractor
2:download latest minimal adb and fastboot drivers and install them
3ut the extracted system.img,recovery.img,cust.img,boot.img and userdata.img into the fastboot.exe folder
4: boot into the fastboot mode
And finally flash the above mentioned imgs one by one with this command
fastboot flash XXX XXX.img
After flashing files type
Fastboot reboot
and every thing should be fine again
Sent from my H30-U10 using Tapatalk
Click to expand...
Click to collapse
Thank you, I did that except for userdata.img file, the Huawei MultiTool only mentioned 4 files(system,recovery,boot,cust). Now my device is running back again on stock rom. Should I flash userdata.img file or is it ok?
Just a question that i keep asking myself; inside the stock update.app file there are 22 img files, what do they do? I only flashed four of them so what purpose do the rest serve as? if the device can operate fully functional with four of them!
Many thanks,
demonjo2001 said:
Thank you, I did that except for userdata.img file, the Huawei MultiTool only mentioned 4 files(system,recovery,boot,cust). Now my device is running back again on stock rom. Should I flash userdata.img file or is it ok?
Just a question that i keep asking myself; inside the stock update.app file there are 22 img files, what do they do? I only flashed four of them so what purpose do the rest serve as? if the device can operate fully functional with four of them!
Many thanks,
Click to expand...
Click to collapse
It's for the other partitions like cust, modem etc.
demonjo2001 said:
Thank you, I did that except for userdata.img file, the Huawei MultiTool only mentioned 4 files(system,recovery,boot,cust). Now my device is running back again on stock rom. Should I flash userdata.img file or is it ok?
Just a question that i keep asking myself; inside the stock update.app file there are 22 img files, what do they do? I only flashed four of them so what purpose do the rest serve as? if the device can operate fully functional with four of them!
Many thanks,
Click to expand...
Click to collapse
Don't use any other img file. And don't flash userdata.
If it works, don't change it. ?
Got similar issue on my honor 6. Can't update via SD card method or 3 button after leaving developer preview. Not even OTA updates install. All fail at 5%. So I'm stuck on B830 for now. Will try for a solution later.
goldfinv said:
Got similar issue on my honor 6. Can't update via SD card method or 3 button after leaving developer preview. Not even OTA updates install. All fail at 5%. So I'm stuck on B830 for now. Will try for a solution later.
Click to expand...
Click to collapse
Fastboot woukd be the only choice.
Sent from my honor 5X using XDA Labs
adriansticoid said:
Fastboot woukd be the only choice.
Click to expand...
Click to collapse
I've installed several versions of 6.0 via fastboot. Same thing. I just get stuck on that version. Can't even reinstall same version.
goldfinv said:
I've installed several versions of 6.0 via fastboot. Same thing. I just get stuck on that version. Can't even reinstall same version.
Click to expand...
Click to collapse
What partitions did you flash?
Sent from my Galaxy Tab 3 using XDA Labs
adriansticoid said:
What partitions did you flash?
Click to expand...
Click to collapse
The usual. Boot. System. Recovery. Cust.
goldfinv said:
The usual. Boot. System. Recovery. Cust.
Click to expand...
Click to collapse
No errors in fastboot?
Sent from my Galaxy Tab 3 using XDA Labs
adriansticoid said:
No errors in fastboot?
Click to expand...
Click to collapse
None. Just errors in software update/upgrade. Right now I'm looking into testing different stock recoveries.
goldfinv said:
None. Just errors in software update/upgrade. Right now I'm looking into testing different stock recoveries.
Click to expand...
Click to collapse
Goodluck with it man. I am sorry I can't help you any further as I am new in hsing fastboot. I got used to Odin in Samsung.
Sent from my Galaxy Tab 3 using XDA Labs
goldfinv said:
None. Just errors in software update/upgrade. Right now I'm looking into testing different stock recoveries.
Click to expand...
Click to collapse
There's no other solution, either stock img files or some sort of transitional package.
zinko_pt said:
There's no other solution, either stock img files or some sort of transitional package.
Click to expand...
Click to collapse
Stock is a no go for me. I'll try transition package next. Maybe only just the recovery. Might work for the OP as well.
goldfinv said:
Stock is a no go for me. I'll try transition package next. Maybe only just the recovery. Might work for the OP as well.
Click to expand...
Click to collapse
Let us know if you fixed it.
Sent from my Galaxy Tab 3 using XDA Labs
Same issue with me as well please help me in this case.
zinko_pt said:
For you to restore to stock you need to flash boot, recovery, system and cust.
Make sure you have stock boot and recovery to for forced update (3 buttons).
What happens in most of the cases is boot and recovery files are corrupt.
I would try the unbrick of the Multitool. If it fails, I would flash manually all img files for each partition. But using the same firmware version as the lasthttps://cdn-cf-3.xda-developers.com/images/smilies/frown.gif installed one.
Post your results and I will try to help.
Click to expand...
Click to collapse
Hello,
today i wanted to update my *rooted* WAS-LX1 to B182, so i downloaded the update.zip and tried to flash it with FlashFire.
Then my phone booted in Error Mode. So i tried to boot in Fastboot mode, and it worked. So i flashed TWRP and now i want to install Stock firmware again, but i don't know which file i should flash. I've got 3 files called update.zip, update_data_full_public.zip and update_full_WASL21A_hw_eu.zip.
I hope you can help me.
Zillinda
Zillinda said:
Hello,
today i wanted to update my *rooted* WAS-LX1 to B182, so i downloaded the update.zip and tried to flash it with FlashFire.
Then my phone booted in Error Mode. So i tried to boot in Fastboot mode, and it worked. So i flashed TWRP and now i want to install Stock firmware again, but i don't know which file i should flash. I've got 3 files called update.zip, update_data_full_public.zip and update_full_WASL21A_hw_eu.zip.
I hope you can help me.
Zillinda
Click to expand...
Click to collapse
To update my rooted phone to B182 I had to download the full package (2.3gb, including update.zip and update_full_WASL21A_hw_eu.zip). I was not successfull in updating via TWRP. I updated via the official system menu so I don't know how exactly it was applied. According to other guides (http://www.stechguide.com/tag/was-lx1c432b182/ for example) it should be update.zip first and update_full_WASL21A_hw_eu.zip second, without a reboot. Let us know how it worked out...
garris_bibop said:
To update my rooted phone to B182 I had to download the full package (2.3gb, including update.zip and update_full_WASL21A_hw_eu.zip). I was not successfull in updating via TWRP. I updated via the official system menu so I don't know how exactly it was applied. According to other guides (http://www.stechguide.com/tag/was-lx1c432b182/ for example) it should be update.zip first and update_full_WASL21A_hw_eu.zip second, without a reboot. Let us know how it worked out...
Click to expand...
Click to collapse
Unfortunately it didn't work. The only thing i can do is boot in the TWRP recovery. Is there a way to flash the stock rom with fastboot?
Zillinda said:
Unfortunately it didn't work. The only thing i can do is boot in the TWRP recovery. Is there a way to flash the stock rom with fastboot?
Click to expand...
Click to collapse
I only tried flashing the update via sideload and recovery and it didn't work (http://rootmygalaxy.net/flash-ota-firmware-updates-using-adb-fastboot-commands/). Maybe you are lucky. Problem is, I'm quite new to this stuff, hopefully someone else can help out.
Can someone please provide us with a link for the stock recovery?
kazzot17 said:
Can someone please provide us with a link for the stock recovery?
Click to expand...
Click to collapse
https://mega.nz/#!V3AwUI6K!mcqlNCwcyE71MroUZuP9w-bNDhgt3MGzz0svgHUY8Ow
By the way, i solved the problem. I downloaded HuaweiUpdateExtractor for extracting the .img files from the update.app and i flashed them with fastboot.
Nice, congrats
I have UB and rooted with magisk 20.1. I rooted the October build by patching the boot image using magisk. I try to flash the new November stock image and it fails. It says
Writing boot
Failed (failed to write to partition Not found)
I think it may be connected to booting into slot a or b. Maybe?
Can anybody help?
You already took the November OTA or are you still on October?
ctfrommn said:
You already took the November OTA or are you still on October?
Click to expand...
Click to collapse
I'm on October trying to flash November
Pretty sure you cant flash the boot image alone. I always flash the stock boot for the build Im currently on then take the OTA. I think there is a new bootloader for November. Not 100% on that though.
I'm just trying to flash the full factory November stock image. I downloaded it, unzip it, plug in the phone in fastboot and double click the run me bat file.
This has always been fine before but I am new to pixel 3a and have only done this once before, on October build. But I came from an original pixel so I've spent 2 years updating that in this way.
I can't work out why the flash is failing.
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
I've tried flashing October factory image and get the exact same result. Not sure what else to try.
ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
Sorry just reread your post. Will try and reflash boot IMG. I do that with fastboot flash boot.img?
Thanks
Yes.... fastboot flash boot boot.img
ctfrommn said:
Yes.... fastboot flash boot boot.img
Click to expand...
Click to collapse
Have tried reflashing boot.img and still won't update ota and same result trying to flash factory image. Any other ideas? And thanks very much for your help
ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
Do I need to flash boot.img to both slots a and b? If so how do I do that?
I only ever flash the one in use.
Just fastboot flash boot boot.img is all you need.
Your can also always just clean flash the OTA. Just download it, factory reset, adb sideload the OTA in recovery.
I've done that a few times now.
ctfrommn said:
I only ever flash the one in use.
Just fastboot flash boot boot.img is all you need.
Your can also always just clean flash the OTA. Just download it, factory reset, adb sideload the OTA in recovery.
I've done that a few times now.
Click to expand...
Click to collapse
Thanks. Will try things tomorrow. It's late here in London. But I can't get a twrp.img to work. It doesn't seem to mount the system and I can't flash anything. Have you got twrp to work? I'll come back to you in about 18hrs if that's ok?
TWRP doesn't work with Q. Just use stock recovery to sideload.
ctfrommn said:
TWRP doesn't work with Q. Just use stock recovery to sideload.
Click to expand...
Click to collapse
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
Yes, OTA and factory images are essentially the same thing just packaged differently.
And the easiest way to reroot is to just download and repatch the new stock image, or flash a custom pre patched kernel.
Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
The OTA zip is packaged differently and does not include a boot.img file that we can use. (I'm sure it must be in there somewhere, but not in a usable form). Therefore you must download the "Factory Image" from Google. Unzip it, open it where you will find another zip file inside. Open that second zip file and you will find the boot.img file there. Move that boot.img file to your phone so that Magisk can access it and to modify it.
https://developers.google.com/android/images
Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
FYI here are the steps I took to update my rooted 3a this morning:
1. in Magisk Manager select Uninstall and select restore images (I did this because I kept getting a 'installation error' on the OTA page)
2. Like an idiot I rebooted my phone, do not reboot! So I had to reinstall magisk
2a. copy the boot.img of Oct to my phone to have it patched by magisk
2b. fastboot flash boot boot_patched.img
3. the OTA downloaded while I was on the stock boot.img so I just followed the magisk instructions to install the OTA in the other partition
Next month I'll just jump from step 1 to 3 and carry on being rooted.
The simplest way to update when youre rooted is to......
Reflash the stock boot from the current build youre on
Take the OTA directly on the phone
Download stock image from new build and move it to phone
Patch with Magisk and move to your PC
Fastboot flash boot boot.img
Ive done this for the last 3 updates and it works perfectly every time......I obviously substitute my kernel for the patched boot but the process is the same. I find this far simpler than messing with Magisk
Thanks for all the suggestions but I still cannot update.
I have tried restoring boot.img
data reset from recovery
relocking bl - ota fails
Unlocking bl again - won't flash using ADB
There is no problem with the phone being recognised on ADB, the flash Just fails as the screen shot in my opening post. I'm thinking it may be connected to needing to flash to the inactive slot.
Anyone got any ideas?