Related
salve a tutti
ho fatto un bel casino!!!
inanzi tutto vi mostro cosa ho per le mani:
fastboot getvar all
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.12.901.3
version-misc: PVT SHIP S-ON
serialno: SH354W90****
imei: 3544360561****
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: TIM__401
battery-status: good
battery-voltage: 4302mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
brand TIM
I have tried in various ways but I can not flash any rom
I unlocked
I can flash the recovery
I tried downloading several recovery, both stock that mod.
the stock do not see the memory cell, the mods do not complete the flash
from fastboot I tried to flash the> RUU (those with X.XX.401.X imagine are right) but I do not go cheap fine.Metto in flasboot, step screen black HTC but me error !!
if some kind soul help me ....
by dint of attempts I managed to ruin the original system without backup !!!
Now I can start only in FlashBoot or recovery
are in s-on and I know that it is not possible for now switch to s-off
thank you
ho provato in vari modi ma non riesco a flashare nessuna rom
l'ho sbloccato
posso flashare le recovery
ho provato a caricare diverse recovery ,sia stock che mod.
le stock non vedono la memoria del cell, le mod non completano il flash
da fastboot ho provato a flashare le >RUU(quelle con X.XX.401.X immagino siano giuste) ma non vado a buon fine.Metto in flasboot,passo a schermo nero HTC ma mi da errore!!
se qualche anima pia mi aiuta....
a forza di tentativi sono riuscito a rovinare il sistema originale senza backup!!!
ora posso avviare solo in flashboot o recovery
sono in s-on e so che non è possibile per ora passare a s-off
grazie
Che recovery hai?
this belongs to qa and troubleshooting thread..
ne ho tante scaricate da vari siti piu quelle mod tipo philz_touch... ecc. tutte si avviano,ma non mi permettono di flashare la ruu!!!
quale puo essermi piu utile per salvare il cell???
scresan said:
ne ho tante scaricate da vari siti piu quelle mod tipo philz_touch... ecc. tutte si avviano,ma non mi permettono di flashare la ruu!!!
quale puo essermi piu utile per salvare il cell???
Click to expand...
Click to collapse
Please follow forum rules and use English, use an online translator if needed. Would like to help you but I can't understand what you are saying because you are mixing English and Italian. From what I understand (and I'm not sure I get it) you are stuck without a working ROM and you can't flash a recovery...
Unlock your bootloader using HTCdev.com
flash TWRP recovery 2.6.3.3
Push a rom to your phone using either adb push, adb sideload or a USB OTG cable and a USB drive
Flash the rom with TWRP.
And you can't use a x.xx.401.x RUU on your phone. Yours is a x.xx.901.x so you'll need to achieve S-OFF, change CID/MID before you can use any RUU (there is no RUU for your version). Hence why you must flash a custom rom, not a RUU.
sorry I do not speak English, use google translator.
I thank you for your attention
as I tried to explain I planted !!!!
I have my htc one m7 that can unlock and relock
I can install any recovery
I can copy files to the internal memory
I can use adb, fastboot, sideload ...
I leave all the recovery that I install ...
I read and re-read various posts.
having the bootloader 1.57.0000 I can not change the cidnum TIM___401
I think my problem.
I can only fash firmware X.XX.901.XX think
the problem is that they are not RUU X.XX.901.XX !!!!
thank you
scresan said:
sorry I do not speak English, use google translator.
I thank you for your attention
as I tried to explain I planted !!!!
I have my htc one m7 that can unlock and relock
I can install any recovery
I can copy files to the internal memory
I can use adb, fastboot, sideload ...
I leave all the recovery that I install ...
I read and re-read various posts.
having the bootloader 1.57.0000 I can not change the cidnum TIM___401
I think my problem.
I can only fash firmware X.XX.901.XX think
the problem is that they are not RUU X.XX.901.XX !!!!
thank you
Click to expand...
Click to collapse
Since there is no RUU for your phone you should download ARHD 84.0 or MaximusHD. If your bootloader is "Unlocked" then try following these steps:
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone any ways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didn't install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse
with the information, I was able to retrieve the phone !!!!!
for what I know with s-on and hboot 1.57.0000 with cidnum: TIM__401, you can not install RUU, because there are no signed X.XX.901.X (signature TIM Italy)
* I managed to recover the cell due to a backup of a cell with the same firmware and my 2 recovery found on a forum Italian.
I do not know if I can post the link, but for me it was important and I think it can be useful to oth
xxx.androidiani.com/forum/modding-htc-one/405113-ritorno-stock-tim.hxxl
from here I recovered the sense of backupBackup TIM 6 with Android 4.4.2
and 1 recovery: Recovery Philz touch 6.07.9
more a CWM / TWRP Recovery that can not remember ....
however, the method is simple:
unlock htc m7 through the site htc
install the recovery Philz touch
connect the cell to pc with active recovery that shows the cell and allows you to copy the backup downloaded in the right directory
install CWM recovery / TWRP (I forget which one !!!)
boot from recovery and do a restore by removing the security check MD5
so I retrieved my htc one m7.
Q&A for [Windows Tool] Moto G 2015 XT1072 Restore to to Stock Android 5.0.2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Windows Tool] Moto G 2015 XT1072 Restore to to Stock Android 5.0.2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
ah, waiting for your roms :good:
Will this also revert back to stock recovery? All I have to do after this is to lock relock bootloader (if I want to)?
skippieb0y said:
Will this also revert back to stock recovery? All I have to do after this is to lock relock bootloader (if I want to)?
Click to expand...
Click to collapse
When you perform this operation manually, you have your stock recovery restored. I did not try this automatic tool, but I think the result is the same.
i have adb installed but when i run this script i get and error saying mfastboot.exe is not a recognized internal or external command. any ideas?
djisgod said:
i have adb installed but when i run this script i get and error saying mfastboot.exe is not a recognized internal or external command. any ideas?
Click to expand...
Click to collapse
Tried a few times myself and get the same error message. As above, anyone any ideas?
fs1023 said:
Tried a few times myself and get the same error message. As above, anyone any ideas?
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=2427667 download that file and extract it into the folder where you have already placed all the files. it should then work fine. it is the mfastboot file that is missing. took a lot of trial and error to figure out how to get it working lol i found it by doing this whole process manually by following a guide on here.
djisgod said:
http://forum.xda-developers.com/attachment.php?attachmentid=2427667 download that file and extract it into the folder where you have already placed all the files. it should then work fine. it is the mfastboot file that is missing. took a lot of trial and error to figure out how to get it working lol i found it by doing this whole process manually by following a guide on here.
Click to expand...
Click to collapse
Good stuff djisgod. Have yo tried this recovery to stock method yourself?
fs1023 said:
Good stuff djisgod. Have yo tried this recovery to stock method yourself?
Click to expand...
Click to collapse
yeah i flashed back to stock using this method . relocked the bootloader. then unlocked it again and flashed cm12.1
this will bring back stock update notification? or I will have to do something more manually?
djisgod said:
yeah i flashed back to stock using this method . relocked the bootloader. then unlocked it again and flashed cm12.1
Click to expand...
Click to collapse
once again thanks djisgod. one more question if you don't mind. how do you relock the bootloader?
fs1023 said:
once again thanks djisgod. one more question if you don't mind. how do you relock the bootloader?
Click to expand...
Click to collapse
use the command :
fastboot oem lock
in ADB
Restore to Stock Android 5.0.2 for Motorola Moto G 2015 (XT1072)
"adb" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
< waiting for device >
The part in spanish says " "adb" isn't recognized as an intern or extern command, program or file executable" or something like that.
help? thank you in advance
edit: I don't know if it helps, but I was using CM 12.1 without problems. Then the phone froze and I restarted it. BAM! bootloop. I can't enter recovery.
CanallaManiaco said:
Restore to Stock Android 5.0.2 for Motorola Moto G 2015 (XT1072)
"adb" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
< waiting for device >
The part in spanish says " "adb" isn't recognized as an intern or extern command, program or file executable" or something like that.
help? thank you in advance
edit: I don't know if it helps, but I was using CM 12.1 without problems. Then the phone froze and I restarted it. BAM! bootloop. I can't enter recovery.
Click to expand...
Click to collapse
use the this http://forum.xda-developers.com/attachment.php?attachmentid=2427667. extract the files into the folder where you put the tool then it will work ok.
Everything works fine, just like the guys above said - you need to put the files in /platform-tools directory and rename fastboot.exe to mfastboot.exe.
I guess it saved my device from bootloop.
NOT WORKING: Image is too large
I have a problem when using this tool, I'm quite desperate to fix it because I don't have a recovery due to installing the wrong TWRP version (I installed Titan) at first, here is the problem:
When I start the script I get multiple 'Image file is too large' errors on my phone, this is in my cmd when the errors happen.
target max-sparse-size: 256MB
sending 'system' (256969 KB)...
OKAY [ 8.479s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.588s
target max-sparse-size: 256MB
sending 'system' (259819 KB)...
OKAY [ 8.578s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.643s
Click to expand...
Click to collapse
Clearly the 'Target max-sparse-size (256MB) is smaller than the file it's trying to write (for example 259819 KB > 256 MB), I wonder if there is a way to expand the target max-sparse-size, or if there is any other solution. These errors now result in an infinite ' bootloader unlocked screen'
I am 100% sure that I have a XT1072 .
I will donate if you help me fix this
Don't know what to do?
Hi.
I download the file through the link and i don't know what to do next, can you walk me trough what should i do next. Pls
can anoyone reupload the file , i had a moto g 2015 with bootloop problem
milanmore said:
I have a problem when using this tool, I'm quite desperate to fix it because I don't have a recovery due to installing the wrong TWRP version (I installed Titan) at first, here is the problem:
When I start the script I get multiple 'Image file is too large' errors on my phone, this is in my cmd when the errors happen.
Clearly the 'Target max-sparse-size (256MB) is smaller than the file it's trying to write (for example 259819 KB > 256 MB), I wonder if there is a way to expand the target max-sparse-size, or if there is any other solution. These errors now result in an infinite ' bootloader unlocked screen'
I am 100% sure that I have a XT1072 .
I will donate if you help me fix this
Click to expand...
Click to collapse
Take a look here: http://forum.xda-developers.com/moto-g-lte/help/moto-g-4g-lte-xt1072-bricked-t3091863 and here: http://forum.xda-developers.com/mot...ng-rom-stock-via-twrp-2-t3208614#post63312449
It seems to be an open issue that no one has solved so far. I have exactly the same problem.
Will this remove root and allow me to install OTA updates with no hassle?
Please help me in figuring out how to fix the unknown baseband error with null imei for Moto E4 plus Xt1770 Indian version.
What i have done so far!!!
I flashed twrp recovery after unlocking the boot loader, flashed Lineage OS 14.1 custom ROM and rooted using Phh superuser. But as I was not satisfied with it, I reverted back to the stock ROM using SP flash tool " Format all + Download ". But ever since I have unknown baseband error. I cant go back to the custom rom. So Please help me in fixing this problem by staying on the stock rom. I am desperately welcome to all suggestions.
AthulPrasad said:
Please help me in figuring out how to fix the unknown baseband error with null imei for Moto E4 plus Xt1770 Indian version.
What i have done so far!!!
I flashed twrp recovery after unlocking the boot loader, flashed Lineage OS 14.1 custom ROM and rooted using Phh superuser. But as I was not satisfied with it, I reverted back to the stock ROM using SP flash tool " Format all + Download ". But ever since I have unknown baseband error. I cant go back to the custom rom. So Please help me in fixing this problem by staying on the stock rom. I am desperately welcome to all suggestions.
Click to expand...
Click to collapse
Do you get the null imei in the bootloader only? Or is there an imei when you dial *#06#?
Also provide pictures like this from cpuz
https://ibb.co/i2mVH6
https://ibb.co/gh7sVR
https://ibb.co/ddTMPm
sp flash tools + stock rom @google.
solves the problem
ROGGGER3G said:
sp flash tools + stock rom @google.
solves the problem
Click to expand...
Click to collapse
It does not solve, I already did it in mine, and the problem continued.
[EDIT]
I CANT ATTACH THE FILE IN THE REPLY. I HAVE POSTED IT IN DISCUSSION FORUM OG MOTO E4 PLUS.
This is the solution for unknown baseband and null imei error for mt6737 device Moto E4 Plus.
This is fix for Moto E4 Plus Xt1770 Indian Version.
(Note: You must have adb folder in Local disk C of your computer. To make things easier if you paste the firmware folder of Xt1770 within the adb folder , things will run more smoothly. To know how to have adb folder in Local Disk C, just Google it.)
Fixing On Moto E4 Plus XT1770
1.First download stock firmware and flash it (Format all+ download).
2. Then run the phone once. You will be having unknown baseband error.
3. Nothing to worry. Here is the fix.
4. Again Open Sp flash Tool and Click On Scatter Loading.
5.Here Select Scatter from LK Folder (Already In Firmware Folder)
6.Click On Download. Switch off the phone and holding volume up and volume down button connect it to PC.
7.After Flash Switch On The device
Device Will be on Special Bootloader Mode.
8.Again Connect Device to PC
9.Open Firmware Folder
7.Run "hwflash" Bat.It is present in firmware folder.(IMPORTANT)
8. Next Download XT1770. (I have attached the file)
Copy That Bat File in Firmware Folder and run it.
AFTER THE BAT Runs,Type "1"press Enter.
( Note: If it just runs without you getting a chance to press 1 , that means adb is not there in Local Disk C. You can confirm by running the command "adb devices" from cmd. )
9.If things go correctly, you will get Press any key to exit command.
10. Now disconnect your phone.
11. Again open Sp flash tool and select the default 6737 scatter file( NOT the one in lk folder).
12. Now deselect all except preloader and lk. Click download. Your phone is still in special Bootloader mode. Power off and holding volume up and volume down connect your device to the PC again.
13. Once flashing is complete. Switch on the phone again.
14. You will now have baseband. If you still have null imei, fix it using Maui Meta tool from hovatek forum.
15. All this info was collected from GsmHosting.
Thanks .
hwflash bat file not opening showing error internet securiety setting prevented one or more files from beging opend solutio
nikhiljalaja said:
hwflash bat file not opening showing error internet securiety setting prevented one or more files from beging opend solutio
Click to expand...
Click to collapse
I think that is because you have a highly secured antivirus installed. Try disabling the antivirus. Also in Windows 10 , ensure real-time protection from Windows Update is turned off. And even after doing all this if nothing works, like I already said, check if "adb devices" command detect your device. If the command does not recognize your device install minimal adb and fastboot and copy the files to a folder created to a folder named "adb" in Local Disk C. For assuring 100% success you can paste the firmware files also in adb. Hope this helps.
AthulPrasad said:
Please help me in figuring out how to fix the unknown baseband error with null imei for Moto E4 plus Xt1770 Indian version.
Click to expand...
Click to collapse
Null imei or no baseband. your device nvram which contain radio functionality of device(imei, bluetooth, wifi etc etc) somehow got corrupted or formatted.
AthulPrasad said:
But as I was not satisfied with it, I reverted back to the stock ROM using SP flash tool " Format all + Download ". But ever since I have unknown baseband error.
Click to expand...
Click to collapse
*Format all* option erases data from all partitions. probably you lose your device nvram.
AthulPrasad said:
Please help me in figuring out how to fix the unknown baseband error with null imei
Click to expand...
Click to collapse
You can fix this by following method :
anyone in this forum willing to provide you their device nvram data can fix your device or you can fix this by using imei injector tool.
Backup your device nvram manually :
dd if=/dev/block/platform/.../.../by-name/nvram of=/sdcard/nvram.img
dd if=/dev/block/platform/.../.../by-name/nvdata of=/sdcard/nvdata.img
Install using this method :
fastboot flash nvram nvram.img
fastboot flash nvdata nvdata.img
My device no nvram
Francesco Franz said:
Null imei or no baseband. your device nvram which contain radio functionality of device(imei, bluetooth, wifi etc etc) somehow got corrupted or formatted.
*Format all* option erases data from all partitions. probably you lose your device nvram.
You can fix this by following method :
anyone in this forum willing to provide you their device nvram data can fix your device or you can fix this by using imei injector tool.
Backup your device nvram manually :
dd if=/dev/block/platform/.../.../by-name/nvram of=/sdcard/nvram.img
dd if=/dev/block/platform/.../.../by-name/nvdata of=/sdcard/nvdata.img
Install using this method :
fastboot flash nvram nvram.img
fastboot flash nvdata nvdata.img
Click to expand...
Click to collapse
Oi o meu lenovo esta sem IMEI moto e4 xt1763 Mediatek .
estou enfrentando problemas aqui com isso após flashar uma rom.
IMEI, WIFI, GPS com problemas, wifi funciona mas fica um erro na rede ERRO = 0x10 como se fosse uma rede wifi (rede ficticia, criou essa rede) apenas nas redes de verdade.
Emfim gostaria de uma solução para esse problema de IMEI, ja tentei varias ferramentas e nada, inclusive o miracle box versão PC não conecta no aparelho não sei porque mesmo com todos drivers.
Qualquer ajuda que alguém possa me dar sera bem vinda. OBRIGADO.
RobinssonCL said:
Oi o meu lenovo esta sem IMEI moto e4 xt1763 Mediatek .
estou enfrentando problemas aqui com isso após flashar uma rom.
IMEI, WIFI, GPS com problemas, wifi funciona mas fica um erro na rede ERRO = 0x10 como se fosse uma rede wifi (rede ficticia, criou essa rede) apenas nas redes de verdade.
Emfim gostaria de uma solução para esse problema de IMEI, ja tentei varias ferramentas e nada, inclusive o miracle box versão PC não conecta no aparelho não sei porque mesmo com todos drivers.
Qualquer ajuda que alguém possa me dar sera bem vinda. OBRIGADO.
Click to expand...
Click to collapse
Translation :
Hi, my lenovo is without IMEI moto e4 xt1763 Mediatek.
I'm having trouble here with this after flashing a rom.
IMEI, WIFI, GPS with problems, wifi works but there is an error in the network ERROR = 0x10 as if it were a wifi network (fictitious network, created this network) only in real networks.
Finally I would like a solution to this problem of IMEI, already tried several tools and nothing, including the miracle box PC version does not connect in the device do not know why even with all drivers.
Any help someone can give me will be welcome. THANK YOU.
I have NO imei/baseband on a XT1771 - Did you fix it???
http://forum.gsmdevelopers.com/moto...d-moto-mtk-mobile-database-file-download.html
http://forum.gsmdevelopers.com/moto...moto-e4-plus-xt1770-firmware-gd_mekail92.html
try these
Thank You so much. Fixed k8 plus through your instructins
AthulPrasad said:
[EDIT]
I CANT ATTACH THE FILE IN THE REPLY. I HAVE POSTED IT IN DISCUSSION FORUM OG MOTO E4 PLUS.
This is the solution for unknown baseband and null imei error for mt6737 device Moto E4 Plus.
This is fix for Moto E4 Plus Xt1770 Indian Version.
(Note: You must have adb folder in Local disk C of your computer. To make things easier if you paste the firmware folder of Xt1770 within the adb folder , things will run more smoothly. To know how to have adb folder in Local Disk C, just Google it.)
Fixing On Moto E4 Plus XT1770
1.First download stock firmware and flash it (Format all+ download).
2. Then run the phone once. You will be having unknown baseband error.
3. Nothing to worry. Here is the fix.
4. Again Open Sp flash Tool and Click On Scatter Loading.
5.Here Select Scatter from LK Folder (Already In Firmware Folder)
6.Click On Download. Switch off the phone and holding volume up and volume down button connect it to PC.
7.After Flash Switch On The device
Device Will be on Special Bootloader Mode.
8.Again Connect Device to PC
9.Open Firmware Folder
7.Run "hwflash" Bat.It is present in firmware folder.(IMPORTANT)
8. Next Download XT1770. (I have attached the file)
Copy That Bat File in Firmware Folder and run it.
AFTER THE BAT Runs,Type "1"press Enter.
( Note: If it just runs without you getting a chance to press 1 , that means adb is not there in Local Disk C. You can confirm by running the command "adb devices" from cmd. )
9.If things go correctly, you will get Press any key to exit command.
10. Now disconnect your phone.
11. Again open Sp flash tool and select the default 6737 scatter file( NOT the one in lk folder).
12. Now deselect all except preloader and lk. Click download. Your phone is still in special Bootloader mode. Power off and holding volume up and volume down connect your device to the PC again.
13. Once flashing is complete. Switch on the phone again.
14. You will now have baseband. If you still have null imei, fix it using Maui Meta tool from hovatek forum.
15. All this info was collected from GsmHosting.
Thanks .
Click to expand...
Click to collapse
Made an account on xda solely to thank you. I was searching for a fix for 7 hrs and i finally found it.
Try this like https://forum.xda-developers.com/moto-e4-plus/how-to/fixed-moto-e4-plus-xt1771-unknown-t3831831 with your stock rom and proper bat file according to your model.
Quite a simple question huh.....
we see lots of threads mentioning TWRP for emui 5
so
Is there ... or not ... a fully working TWRP for our beloved :silly: Oreo modded P10
Hello, the TWRP coded by @Blackball for P10 plus works ok on our P10 Oreo (emui 8.0).
Here is the link
i have found it only two bugs:
1) ADB doesn't work over this TWRP
2) Data backup doesn't work (that's because there isn't a proper TWRP decryption for our emmc/ufs system)
Everything else works as expected.
thanks for reply....
ADB and /data,arent they the most important to work ?
Being root with custom kernel,i guess ill wait for a fully working one...
Adb is working fine. I can take some pics if you don't believe me. I tried on two different windows (win 7 and 10) and on Linux mint.
There is no nougat or oreo twrp that decrypt huawei internal storage. You can format your storage and do small modifications on vendor.
Then you can backup your data too.
Gesendet von meinem BKL-L04 mit Tapatalk
i cannot install,give me this error
FAILED (remote: partition length get error)
Flash with fastboot
fastboot flash recovery_ramdisk nameoftwrp
Gesendet von meinem BKL-L04 mit Tapatalk
Thanks Blackball
when i was using my nova plus before it died,to use /data properly i had to format it,,,i had to type YES the after that,all twrp was working.
Is it about the same with your kernel ?
you re talking about Vendor...what are the mods and what does they do ?
I need Help please
x1988 said:
i cannot install,give me this error
FAILED (remote: partition length get error)
Click to expand...
Click to collapse
My error is the same remote partition length get error I need help please I have huawei p20lite. I have
Phone unlocked
FRP Unlock and I entry in Fastboot mode
I have to install the twrp for download the xposer please answer me please
atteindre TWRP ???
Bonjour,
J'ai un P10 emui 8 android 8
J'ai suivi le TUTO à la lettre( je crois) et je suis bloqué au message( partition lenght get error ) .J'ai vu que beaucoup on eu cette erreur, y-a t'il une solution svp.
Mon téléphone fonctionne normalement mon seul problème et que je ne peux accéder au TWRP quand je ( vol+ + power) donc impossible de passer en L-29....
Merci d'avance!
You should delete pin
eddyping said:
Bonjour,
J'ai un P10 emui 8 android 8
J'ai suivi le TUTO à la lettre( je crois) et je suis bloqué au message( partition lenght get error ) .J'ai vu que beaucoup on eu cette erreur, y-a t'il une solution svp.
Mon téléphone fonctionne normalement mon seul problème et que je ne peux accéder au TWRP quand je ( vol+ + power) donc impossible de passer en L-29....
Merci d'avance!
Click to expand...
Click to collapse
First you must have drives adb (minimal Fastboot) of you mobile
Second the mobile should be root
Third the comand is "fastboot flash recovery_ramdisk nameimage.img"(twrp of your mobile )
Then delete pin o password of mobile (facial unlocking,fingerprints)
@eddyping
Please, only post in English.
x1988 said:
i cannot install,give me this error
FAILED (remote: partition length get error)
Click to expand...
Click to collapse
jesusKD said:
My error is the same remote partition length get error I need help please I have huawei p20lite. I have
Phone unlocked
FRP Unlock and I entry in Fastboot mode
I have to install the twrp for download the xposer please answer me please
Click to expand...
Click to collapse
Sorry if I am late to reply but this is the solution. Go to the folder where ADB executable file is installed, mouse right click on a blank space anywhere inside the folder and choose "open command window here as administrator". And from there proceed as normal. If you don't see the option google how to activate it.
x1988 said:
i cannot install,give me this error
FAILED (remote: partition length get error)
Click to expand...
Click to collapse
If anyone else also getting this error, please make sure you know the right name of recovery partition.
I was doing
Code:
fastboot flash recovery nameoftwrp
But in reality i was required to flash
Code:
fastboot flash recovery_ramdisk nameoftwrp
First you have to download and install 'Minimal ADB and Fasboot' (https://forum.xda-developers.com/showthread.php?t=2317790)
Now you have to download the latest firmware available here https://mirrors.lolinet.com/firmware/moto/montana_retcn/official/RETCN/
Extract it to the folder you installed Minimal ADB
Press Shift + Right click in the folder, select "open command window"
Put your phone in fastboot mode
Select and copy all the codes below then right click in the CMD window opened.
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
All working, tested by myself.
Wont brick because commands related to bootloader were removed.
For Brazilians:
Primeiramente você vai precisar instalar o 'Minimal ADB and Fastboot'(https://forum.xda-developers.com/showthread.php?t=2317790)
Baixe o ultimo firmware disponivel neste site: https://mirrors.lolinet.com/firmware/moto/montana_retcn/official/RETCN/
Extraia ele para a mesma pasta que você instalou o Minimal ADB
Agora nessa pasta, pressione Shift + Clique direito, selecione "Abrir janela de comando aqui"
Coloque seu aparelho em modo fastboot
Copie os códigos acima e clique com o botão direito na janela do CMD
Tudo já foi testado, não tem risco de brick pois comandos relacionados ao bootloader foram removidos.
From the only Firmware folder none of command will execute, You need to download
minimal adb fastboot Tools and extract anywhere in PC.
Than
You need to extract downloaded firmware zip file to fastboot Tools folder, and
Than
just copy attached file in the same folder,
Rename file from FlashRomZui.txt to FlashRomZui.bat
It will become Batch file...
In case by renaming it wont become batch file than open in notepad and save as FlashRomZui.bat in same folder it will become batch file for sure.
Now connect your phone to PC in bootloader mode
And just double click FlashRomZui.bat
Wait to end process... it will take 5 to 7 Minutes
Copy past commands one by one can make it complicated for beginners...
Cheers
Sorry if stupid question , but does the bootloader get locked after the operation ? And also , is it necessary to overwrite the recovery too ? Cause i saw the line. And if so , can i put TWRP back with no problem ?
bogdanwp said:
Sorry if stupid question , but does the bootloader get locked after the operation ? And also , is it necessary to overwrite the recovery too ? Cause i saw the line. And if so , can i put TWRP back with no problem ?
Click to expand...
Click to collapse
No, the bootloader remains unlocked.
The Stock recovery is needed just for first boot, after that u can flash and use TWRP normally
zahidm said:
From the only Firmware folder none of command will execute, You need to download
minimal adb fastboot Tools and extract anywhere in PC.
Than
You need to extract downloaded firmware zip file to fastboot Tools folder, and
Than
just copy attached file in the same folder
Click to expand...
Click to collapse
Well said my friend, I'll edit my thread.
VulgarusBR said:
No, the bootloader remains unlocked.
The Stock recovery is needed just for first boot, after that u can flash and use TWRP normally
Click to expand...
Click to collapse
Thank you ! I went ahead and found out on my own. Confirmed working without problems for me.
---
L.E. : good rom , fast , to much bloatware , to much chinese. Went back to lineage 14 and no more fingerprint sensor. Any help please ?
bogdanwp said:
Thank you ! I went ahead and found out on my own. Confirmed working without problems for me.
---
L.E. : good rom , fast , to much bloatware , to much chinese. Went back to lineage 14 and no more fingerprint sensor. Any help please ?
Click to expand...
Click to collapse
You flashed nougat and no more fingerprint? When you back to LOS 14 nougat?
zahidm said:
You flashed nougat and no more fingerprint? When you back to LOS 14 nougat?
Click to expand...
Click to collapse
I fastbooted zui and no more fingerprint when back to LOS 14 yes. Also after i restored my original image that i always keep , still no fingerprint
bogdanwp said:
I fastbooted zui and no more fingerprint when back to LOS 14 yes. Also after i restored my original image that i always keep , still no fingerprint
Click to expand...
Click to collapse
1: Download below file from link.
https://mega.nz/#!Az5EBYxC!_fqx-2iHD9KiddRwTgd3yharQ61jINDOcYjNLJnE-d4
2: Extract anywhere in PC
3: connect Mobile in Bootloader mode
4: Go to folder
5: Duble click file flash downgrade.bat
Wait and reboot
If still Won't get fingerprint, than please tell.
zahidm said:
1: Download below file from link.
https://mega.nz/#!Az5EBYxC!_fqx-2iHD9KiddRwTgd3yharQ61jINDOcYjNLJnE-d4
2: Extract anywhere in PC
3: connect Mobile in Bootloader mode
4: Go to folder
5: Duble click file flash downgrade.bat
Wait and reboot
If still Won't get fingerprint, than please tell.
Click to expand...
Click to collapse
Ayyyy , it's working ! Thank you mate. You're a lifesaver.
bogdanwp said:
Ayyyy , it's working ! Thank you mate. You're a lifesaver.
Click to expand...
Click to collapse
Welcome. Cheers
Is there easy way to uninstall zui?
Lmaocetong said:
Is there easy way to uninstall zui?
Click to expand...
Click to collapse
Yes flash stock
What exactly is this? Any screenshots???