Hi,
I have been given an old Huawei P9 from a friend who tried to install a custom ROM on it, which apparently didn't go so well. The phone doesn't seem to boot past the bootloader unlocked message. He asked me to try to recover it so he could use it temporarily as his current phone died.
It appears to have TWRP 3.1.1.0 installed, but from what I can tell TWRP can't mount the /data folder, I haven't really looked into that issue much as I was hoping to just reinstall the stock recovery and take it back to stock, but struggling to find/understand instructions. Hope there is someone that can still help, any help would be appreciated.
It is an Australian (carrier: Optus) model EVA-L09, and that's about all I can tell as fastboot doesn't seem to be able to get much else
Code:
fastboot.exe oem get-bootinfo
(bootloader) unlocked
OKAY [ 0.006s]
Finished. Total time: 0.009s
fastboot.exe oem get-product-model
(bootloader)
OKAY [ 0.006s]
Finished. Total time: 0.069s
fastboot.exe getvar vendorcountry
vendorcountry: optus/au
Finished. Total time: 0.007s
fastboot.exe oem get-build-number
(bootloader) :
OKAY [ 0.004s]
Finished. Total time: 0.007s
fastboot.exe oem oeminforead-System_Version
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
greyjoy said:
I have been given an old Huawei P9 from a friend who tried to install a custom ROM on it, which apparently didn't go so well. The phone doesn't seem to boot past the bootloader unlocked message. He asked me to try to recover it so he could use it temporarily as his current phone died.
It appears to have TWRP 3.1.1.0 installed, but from what I can tell TWRP can't mount the /data folder, I haven't really looked into that issue much as I was hoping to just reinstall the stock recovery and take it back to stock, but struggling to find/understand instructions. Hope there is someone that can still help, any help would be appreciated.
It is an Australian (carrier: Optus) model EVA-L09, and that's about all I can tell as fastboot doesn't seem to be able to get much else
Click to expand...
Click to collapse
Are there really no answers (even no "Failed") to some commands - try to execute again and attach also screenshot from PC
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
PAUSE
REM fastboot getvar rescue_enter_recovery
zgfg said:
Are there really no answers (even no "Failed") to some commands - try to execute again and attach also screenshot from PC
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
PAUSE
REM fastboot getvar rescue_enter_recovery
Click to expand...
Click to collapse
No other errors that I can see when I run the oem commands at least, see screenshot
{
"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"
}
greyjoy said:
No other errors that I can see when I run the oem commands at least, see screenshot
Click to expand...
Click to collapse
This is all very strange. Even after custom ROM and/or brick it should know to answer on get-product-model or get-build-number.
Maybe only if some ... deleted all partitions by TWRP or so?!
Just one suggestion. Forget Platform tools and install to the PC very simple and small (only few MB) "Minimal ADB and Fastboot" package and execute from there (you don't need to type "fastboot.exe", just "fastboot" is enough)
Do you know at least, was it Android 6, 7 or 8. Almost certainly not 8, it would be CN, not AU. 6 only if stock was not updated from the beginning
From the TWRP version I would guess it was Nougat, i.e. EMUI 5.
In that case you can install generic/no-check version of Nougat stock recovery:
https://mega.nz/file/09k1wIST#IyMKcRwPq7llKEmnflOAQJSl2B4v8pmz6Myj_ZawxQs
You should also know was it L09 Single SIM or L19 Dual SIM
Searching for custs, Australia might be c636 or c183 but seems that c34 was Australia Optus
Find on FirmwareFinder or from:
https://pro-teammt.ru/firmware-database/?firmware_model=EVA-L09c34
"FullOTA-MF-PV" (only PV are suitable for DLOAD) firmware for e.g. EVA-L09c34, like EVA-L09c34b380 (pkg #93280 from 2017.08.15) and try simple DLOAD method
But if really all partitions were deleted, DLOAD would likely fail. You could try (with your c34, not c432 as in the guide) something like this:
https://forum.xda-developers.com/showpost.php?p=74169408&postcount=7
Related
{
"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"
}
1. Download this zip file and extract it.
2. Hold Shift and then Right click inside the extracted folder and then click on
"Open Command Window here"
3. Connect your device to PC (Make sure that usb debugging is enabled).
4. In command window type
"adb reboot bootloader" //This will boot your phone into fastboot mode.
5. Then type
"fastboot boot twrp.img" //This will boot the device into TWRP recovery temporarily.
6. In recovery click mount -> check system.
7. Now type
"adb pull /system/build.prop" //This will copy the build.prop in the fastboot folder.
8. Open the build.prop using notepad++ (simple notepad may corrupt the file)
9. Find "ro.build.type=user" and change it to " ro.build.type=userdebug"
Then save it.
10. Now type
"adb push build.prop /system/" //this will push the edited build.prop.
11. Now type
"adb shell"(press enter)
"cd system"(press enter)
"chmod 644 build.prop"(press enter)
"exit" (press enter)
12. Type "adb reboot" //to reboot your device
13. Now go in Developer options in setting and enable Multi-window mode
14. enjoy:laugh:
HIT THANKS IS YOU LIKE THIS GUIDE
Error: Device offline
It shows me this error. What should I do?
error: device offline
check adb driver in device manager windows,up date
[email protected] said:
It shows me this error. What should I do?
error: device offline
Click to expand...
Click to collapse
Help!!!!!
bro i have extreated the fastboot file i didnt see the build prop file..................................so what can i do now................please help
Do I need an unlocked bootloader for this?
C:\Users\Elias\Desktop\Fastboot\Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.312s]
booting...
FAILED (remote failure)
finished. total time: 0.315s
C:\Users\Elias\Desktop\Fastboot\Fastboot>
Nera2600 said:
Do I need an unlocked bootloader for this?
C:\Users\Elias\Desktop\Fastboot\Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.312s]
booting...
FAILED (remote failure)
finished. total time: 0.315s
C:\Users\Elias\Desktop\Fastboot\Fastboot>
Click to expand...
Click to collapse
failed for me too
ArvinLam said:
failed for me too
Click to expand...
Click to collapse
9. Find "ro.build.type=user" and change it to " ro.build.type=userdebug"
Then save it.
Change these lines in system build.prop then reboot goto developer options nd enable it
dsbhai said:
9. Find "ro.build.type=user" and change it to " ro.build.type=userdebug"
Then save it.
Change these lines in system build.prop then reboot goto developer options nd enable it
Click to expand...
Click to collapse
thanks
me too..
you find any solution?
question
working fine in android one thanks....Does it work only on android one or any rooted phone?
error
device not found!!!
fail
C:\Users\William\Desktop\Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.277s]
booting...
FAILED (remote failure)
finished. total time: 0.294s
what to do?
Device ASUS ZENFONE 4_T00I
Last working firmware was Jellybean 4.2.2 (never upgraded)
Problem started: Consistent FC msgs of almost all msgs.
1. Droidboot State
Droidboot Version: 6.6.3.0
Product : WW_ZENFON
Not Rooted. No Custom Recovery
Bootloader : Could never unlock. Tried the app but never success.
2. Device Status: Was on Stock Jelly bean and was contineously giving com.android.phone failure and other FC closure consistently , hence needed to try flasing a new rom or same version.
3. Read the forums and collected following data:
Stock Firmwares:
UL-ASUS_T00I-WW-6.6.3.0_user.zip
UL-ASUS_T00I-WW-7.4.4.0-user.zip
UL-ASUS_T00I-WW-9.9.9.0-user
Raw Firmware:
Zenfone4V4.3.10.raw
4. All the Tools required to flash the firmwares and study of methods to do so. I used WIN-XP and tools installed on the same. All Drivers installed successfully device recognizing and able to use fastboot and adb.
5.Current device status: To flash UL-ASUS_T00I-WW-6.6.3.0_user.zip
I tried following methods :
FW placed on SD Flashing started but failed everytime
Tried Fastboot flash update FW.zip method by cleaning all partitions- Failed "Problem in creating otp update file-error)
Now left with no system, no userdata or no data partitions on device.
Now trying AFT method to flash .raw firmware which I have downloaded.
AFT not at all listing up my device in Droidbot mode.
Final Status: No System on / No firmware on device at all. Can use Droidboot thats all.
Now please help me to give life to the device...
Thank you in advance.
C:\Zenfone>fastboot flash boot boot.img
sending 'boot' (8661 KB)...
OKAY [ 1.375s]
writing 'boot'...
OKAY [ 1.859s]
finished. total time: 3.234s
C:\Zenfone>fastboot flash fastboot droidboot.img
sending 'fastboot' (11253 KB)...
OKAY [ 1.578s]
writing 'fastboot'...
OKAY [ 2.156s]
finished. total time: 3.734s
C:\Zenfone>fastboot flash update UL-ASUS_T00I-WW-9.9.9.0-user.zip
sending 'update' (825100 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.016s
==================================================
C:\Zenfone>fastboot flash update UL-ASUS_T00I-WW-7.4.4.0-user.zip
sending 'update' (837024 KB)...
OKAY [ 37.469s]
writing 'update'...
FAILED (remote: problem with creating ota update file!)
finished. total time: 37.578s
==================================================
AFT not detecting device and showing this error everytime I connect or disconnect device (in droidboot mode)
{
"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"
}
Maybe you can search this files on google :
1. 6.5.35 system.img.gz file
2. 6.5.35 boot.img file
3. 6.5.35 fastboot img file
Should be the same version, then flash it..
Ok, I will try that.
Although I wanted to know whats d fault and where did I go wrong on procedures? I could not unlock bootloader so will fastboot allow me to flash the mentioned firmware images?
Why AFT dint worked for me and. Lot of questions around.. I AINT NOOB FOR ANDROID but. Dis device does not hv anything similar to axnormal android.
Sorry for behaving noob.
Thnkyou for help
Help me please
the AFT i installed on my pc doesnt detect the raw file i have
i've spend two weeks to solve this still no luck
please give me some advice how do i fixed my zenfone 4 its stuck on ASUS LOGO
Fix it already but got a new problem
Flash image failure(FAILED (remote: ERROR: Image-SKU: 'TW_Zenfone' Device-SKU: 'WW_Zenfone'))
u guys can use this method
http://forum.xda-developers.com/zenfone-4/general/guide-how-to-flash-stock-rom-relock-t3302917
Hi !
I have a problem with my Moto 2gen 2014 LTE (THEA). Firstly I unlock my bootloader using command : #fastboot oem unlock 'code' and install TWRP and custom ROM Lineage OS 14.1. In this ROM my SIM card was not detected and I'm going to lock my bootloader (Command: # fastboot oem lock 'code) and install stock ROM. Now when I turn the phone immediately enter into fastboot mode, and shows me :
Device is LOCKED. Status Code: 2
failed to validate system image
Fastboot Reason: Fall-throught from normal boot mode USB connected.
{
"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"
}
I try several times to boot the new system, but every time is the same
When i try unlock my bootloader cmd shows me :
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.030s
whether it is still somehow saved? Please, help me.
(Sorry for my bad english)
Have you fix it yet? I have the same problem....
b4toons said:
Hi !
I have a problem with my Moto 2gen 2014 LTE (THEA). Firstly I unlock my bootloader using command : #fastboot oem unlock 'code' and install TWRP and custom ROM Lineage OS 14.1. In this ROM my SIM card was not detected and I'm going to lock my bootloader (Command: # fastboot oem lock 'code) and install stock ROM. Now when I turn the phone immediately enter into fastboot mode, and shows me :
Device is LOCKED. Status Code: 2
failed to validate system image
Fastboot Reason: Fall-throught from normal boot mode USB connected.
I try several times to boot the new system, but every time is the same
When i try unlock my bootloader cmd shows me :
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.030s
whether it is still somehow saved? Please, help me.
(Sorry for my bad english)
Click to expand...
Click to collapse
select option 4 ,format device and reflash rom
Hay !!
After you lock your bootloader then flash the Entire ROM and make sure after flashing use those two command
$ fastboot erase userdata
$ fastboot erase cache
then reboot
$ fastboot reboot
Hi, sorry for necroposting. Did you fix it?
I had rooted Nokia 8 TA-1004(Android 9 ), but decided to switch back on 8.1
First step in instruction was to lock the bootloader to make a critical unlock
I used "fastboot oem lock" command and after that i got this notification:
"Your device is corrupt. It can't be truster and will not boot. Your device will shutdown in 30 seconds." And it's actually shutting down all the time without system load! =(
I can enter Download mode only. Platform tools also see my device (latest platform-tools_r28.0.1-windows). I couldn't access recovery mode. When i hold vol.+ and plug in USB, that warning shows again
What i've already tried:
fastboot flash unlock unlock.key (FAILED (remote: Fail to verify)
fastboot flash boot_a boot.img (Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot flash boot_b boot.img (Writing 'boot_b' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot flash system_a system.img (Invalid sparse file format at header magic)
fastboot -i 0x2e04 flash unlock unlock.bin (FAILED (remote: Fail to verify)
fastboot -i 0x2e04 oem unlock-go (FAILED (remote: Flashing Unlock is not allowed)
fastboot set_active a (FAILED (remote: 'Slot Change is not allowed in Lock State)
fastboot set_active b (FAILED (remote: 'Slot Change is not allowed in Lock State)
adb sideload (
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found)
Help me please. IDK what to do. I do have my old unlock.key, but couldn't install it to open the bootloader....Any ideas, please :crying:
First of all why the hell would u even lock your bootloader if you wish to flash anything ? There's nothing that should justify relocking your device perhaps apart from giving out your phone for repairs on warranty.
Can you access your recovery menu mode ?
KonikoO said:
First of all why the hell would u even lock your bootloader if you wish to flash anything ? There's nothing that should justify relocking your device perhaps apart from giving out your phone for repairs on warranty.
Can you access your recovery menu mode ?
Click to expand...
Click to collapse
I needed to make a critical unlock, and according to instruction 1st step was to lock the bootloader.
I can access download mode only
well this is completely messed up situation here. Maybe going to service center is the only option left. Btw, you repaired your phone yet or it is still like that??
This actually happened because you were on modified system when you locked the bootloader. You need to be completely stock while locking the bootloader.
sumitinhome said:
well this is completely messed up situation here. Maybe going to service center is the only option left. Btw, you repaired your phone yet or it is still like that??
This actually happened because you were on modified system when you locked the bootloader. You need to be completely stock while locking the bootloader.
Click to expand...
Click to collapse
Everything is fine. Ntool helped me to install stock 8.1
Mihalsch said:
Everything is fine. Ntool helped me to install stock 8.1
Click to expand...
Click to collapse
Process please.
sumitinhome said:
Process please.
Click to expand...
Click to collapse
Bought Ntool credits, download stock 8.1, flash it from Ntool..that's all.
pls help bro im having the same probelm of urs for 1 month
Mihalsch said:
Bought Ntool credits, download stock 8.1, flash it from Ntool..that's all.
Click to expand...
Click to collapse
which version of ntools did you use and where can i download stock 8.1 im new to this pls help :crying:
gogeta blue said:
which version of ntools did you use and where can i download stock 8.1 im new to this pls help :crying:
Click to expand...
Click to collapse
0.036 version
Here is 8.1. Pass (techmesto.com)
https://drive.google.com/file/d/1g4rsUE2sohL9EISb0Uu5FPRlNs0D73Xl/view
Mihalsch said:
0.036 version
Here is 8.1. Pass
Click to expand...
Click to collapse
0.036 version is not found any where i can only find 0.1 pls help
gogeta blue said:
0.036 version is not found any where i can only find 0.1 pls help
Click to expand...
Click to collapse
Try this
https://fex.net/635965328106
Mihalsch said:
Try this
Click to expand...
Click to collapse
Error while flashing
RUNNING NTool 0.036
PHONE "NB1GAD1791302820" CONNECTED
ProjectCode : NB11
model : NB1
sub_model : none
software version : NB1-488K-0-00WW-B01
SW model : 00WW
build number : B01
hardware version : 3.1
RF band id : G_850_900_1800_1900^W_1_2_4_5_8^L_1_2_3_4_5_7_8_
secure : yes
Bootloader type : commercial
Download size : 00000512 mB
Elapsed: 40 secs.
SELECT FIRMWARE PACKAGE
Will flash : NB1-488B-0-00WW-B04.mlf
PLEASE CONNECT POWERED OFF PHONE
PHONE "NB1GAD1791302820" CONNECTED
ProjectCode : NB11
model : NB1
sub_model : none
software version : NB1-488K-0-00WW-B01
SW model : 00WW
build number : B01
hardware version : 3.1
RF band id : G_850_900_1800_1900^W_1_2_4_5_8^L_1_2_3_4_5_7_8_
secure : yes
Bootloader type : commercial
Download size : 00000512 mB
Security version : 0004
Challenge : 9AEEE713ECEF3D6448B2E0842D1C8B34EA5D12BF
Waiting for calculation process ...
recv error [10054]
FATAL ERROR: server error: No server found.
Elapsed: 0 secs.
Mihalsch said:
I had rooted Nokia 8 TA-1004(Android 9 ), but decided to switch back on 8.1
First step in instruction was to lock the bootloader to make a critical unlock
I used "fastboot oem lock" command and after that i got this notification:
"Your device is corrupt. It can't be truster and will not boot. Your device will shutdown in 30 seconds." And it's actually shutting down all the time without system load! =(
I can enter Download mode only. Platform tools also see my device (latest platform-tools_r28.0.1-windows). I couldn't access recovery mode. When i hold vol.+ and plug in USB, that warning shows again
What i've already tried:
fastboot flash unlock unlock.key (FAILED (remote: Fail to verify)
fastboot flash boot_a boot.img (Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot flash boot_b boot.img (Writing 'boot_b' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot flash system_a system.img (Invalid sparse file format at header magic)
fastboot -i 0x2e04 flash unlock unlock.bin (FAILED (remote: Fail to verify)
fastboot -i 0x2e04 oem unlock-go (FAILED (remote: Flashing Unlock is not allowed)
fastboot set_active a (FAILED (remote: 'Slot Change is not allowed in Lock State)
fastboot set_active b (FAILED (remote: 'Slot Change is not allowed in Lock State)
adb sideload (
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found)
Help me please. IDK what to do. I do have my old unlock.key, but couldn't install it to open the bootloader....Any ideas, please :crying:
Click to expand...
Click to collapse
I meet the same thing,but my phone is nokia3.1plus(ta1104),I flash by ntool, every thing passed,but it still show that,the phone shutdown itself。please help me
same problem with my nokia 8 ta-1004
dugu1248 said:
I meet the same thing,but my phone is nokia3.1plus(ta1104),I flash by ntool, every thing passed,but it still show that,the phone shutdown itself。please help me
Click to expand...
Click to collapse
you must change your battery ,thats battery problem
Mihalsch said:
I had rooted Nokia 8 TA-1004(Android 9 ), but decided to switch back on 8.1
First step in instruction was to lock the bootloader to make a critical unlock
I used "fastboot oem lock" command and after that i got this notification:
"Your device is corrupt. It can't be truster and will not boot. Your device will shutdown in 30 seconds." And it's actually shutting down all the time without system load! =(
I can enter Download mode only. Platform tools also see my device (latest platform-tools_r28.0.1-windows). I couldn't access recovery mode. When i hold vol.+ and plug in USB, that warning shows again
What i've already tried:
fastboot flash unlock unlock.key (FAILED (remote: Fail to verify)
fastboot flash boot_a boot.img (Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot flash boot_b boot.img (Writing 'boot_b' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot flash system_a system.img (Invalid sparse file format at header magic)
fastboot -i 0x2e04 flash unlock unlock.bin (FAILED (remote: Fail to verify)
fastboot -i 0x2e04 oem unlock-go (FAILED (remote: Flashing Unlock is not allowed)
fastboot set_active a (FAILED (remote: 'Slot Change is not allowed in Lock State)
fastboot set_active b (FAILED (remote: 'Slot Change is not allowed in Lock State)
adb sideload (
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found)
Help me please. IDK what to do. I do have my old unlock.key, but couldn't install it to open the bootloader....Any ideas, please :crying:
Click to expand...
Click to collapse
same device, same problem
{
"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"
}
Hello,
I have a Moto G 7 Plus (a XT1965-3 EU), which I softbricked when aborting an Android update by mistake (power button hold in bag while updating....)
I'm stuck on Android recovery with the message
Code:
Can't load Android system. Your data may be corrupt
. I have two options, Try again or Factory data reset (not an acceptable option).
What I tried so far:
- I tried this tutorial, but Motorola doesn't release the images, and sideloading this image (LAKE_RETAIL_9.0_PPWS29.98-111-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml), gives me this message :
Code:
footer is wrong
Signature verification failed
error: 21
- I tried to call the Motorola support, but they won't give me the OTA image, nor help me in a useful way.
- I wanted to install a custom recovery, but unlocking the oem would wipe everything, so no thanks.
I would rather get all the data than repairing the phone (I got it for free thanks to an Amazon Prime trial...), I have several priceless souvenirs in it, and of course I lost my backup drive when I moved away.
Thank you in advance for your help
NicolasBFR said:
Hello,
I have a Moto G 7 Plus (a XT1965-3 EU), which I softbricked when aborting an Android update by mistake (power button hold in bag while updating....)
I'm stuck on Android recovery with the message
Code:
Can't load Android system. Your data may be corrupt
. I have two options, Try again or Factory data reset (not an acceptable option).
What I tried so far:
- I tried this tutorial, but Motorola doesn't release the images, and
Click to expand...
Click to collapse
I don't know if these still work.
Update Tools
[TOOL][WIN] OTA Updates (Motorola)
[TOOL] Motorola OTA Link Generator Tool
NicolasBFR said:
sideloading this image (LAKE_RETAIL_9.0_PPWS29.98-111-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml), gives me this message :
Code:
footer is wrong
Signature verification failed
error: 21
Click to expand...
Click to collapse
That image is not an OTA, it's the full firmware and is not coded for installing with recovery, it's meant for fastboot mode.
You can try flashing with fastboot.exe
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
I don't know if these still work.
Update Tools
[TOOL][WIN] OTA Updates (Motorola)
[TOOL] Motorola OTA Link Generator Tool
Click to expand...
Click to collapse
Unfortunatly, both require ro.build.version.full to get the appropriate OTA image, and my device won't give it to me with fastboot getvar all . Any idea how I could find it ?
As for Fastboot flash, I would loose the data, which is not an option.
NicolasBFR said:
As for Fastboot flash, I would loose the data, which is not an option.
Click to expand...
Click to collapse
No, only if you use fastboot erase userdata
sd_shadow said:
No, only if you use fastboot erase userdata
Click to expand...
Click to collapse
So, I just have to do fastboot flash with all the .img and sparsechunk files (even though my bootloader is not unlocked and the device not rooted) ?
Why do all internet tutorials erase both cache and userdata ?
And what is the worse that could happen ?
I attached a screen of the archive content:
{
"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"
}
NicolasBFR said:
So, I just have to do fastboot flash with all the .img and sparsechunk files (even though my bootloader is not unlocked and the device not rooted) ?
Why do all internet tutorials erase both cache and userdata ?
And what is the worse that could happen ?
I attached a screen of the archive content:
View attachment 5421721
Click to expand...
Click to collapse
Flashing with a locked bootloader is tricky.
Your best option is using RSD Lite with an old Windows 7 or XP Machine
The servicefile.xml and the flashfile.xml contain the flash commands
the servicefile shouldn't have the userdata line, the flashfile does.
Use Notepad++ to remove the userdata line and save, then flash with RSD Lite.
If that is not an option you can try fastboot.exe
Use the servicefile.xml and the Online FlashFile Converter
run the commands one at a time, if you get an error stop.
and see my Troubleshooting
sd_shadow said:
If that is not an option you can try fastboot.exe
Use the servicefile.xml and the Online FlashFile Converter
run the commands one at a time, if you get an error stop.
and see my Troubleshooting
Click to expand...
Click to collapse
I had USB 3.0 ports so I had the "(bootloader) is-logical:partiti : not found" error.
if you want to know my script (from Online Flashfile converter), is
Bash:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
# fastboot erase carrier
# fastboot erase ddr
fastboot oem fb_mode_clear
echo English - Process concluded!
pause
fastboot reboot
exit
I have a second computer from 2005 with 2.0 USB, I am going to try again in few hours.
Also, all my computers are on Arch Linux (Manjaro) and I download fastboot with pacman,
fastboot --version returns me
Bash:
fastboot version 31.0.2-android-tools
Installed as /usr/bin/fastboot
.
Is my fastboot version ok ?
I am so stupid, I ran the commands above using my old computer, the same fastboot version and with a USB 2.0 port, but with once in a shell script. I don't even have the logs, and now the "Can't load android system" doesn't even appear anymore ! It's just a bootloop.
What should I do ?
Okay @sd_shadow , I used the linux mfastboot recommended by your guides, and this time it managed to flash everything... but I'm back to the bootloader error menu "Can't load Android system"...
Maybe I could flash TWRP recovery (or even just fastboot boot ?), then use it to retrieve userdata and then factory reset ?
EDIT: I tried fastboot boot TWRP.img but I got "permission denied". Maybe there is a custom ROM out there that don't need the userdata ?