HI dudes,
it seems i screwed up ...
I was in 4.2.2 and I wanted to go to 4.3 (my tab was rooted and unlock)
I decided to use "back to stock" from the wug software (with the 4.3 file) and now
I've got "booting error"
START: booting failed
RECOVERY : booting failed
bootloader : I've got the android character
what can i do now ?
thanks
You've erased your ROM and recovery before the failed flash. You can describe in more detail on the status of your bootloader?
well ... yes ...
booloader version 4.23
lock state unlocked
fastboo mode
product name tilapia
So your bootloader is fine. You can just reinstall all the stock images with fastboot.
Username invalid said:
So your bootloader is fine. You can just reinstall all the stock images with fastboot.
Click to expand...
Click to collapse
Ouf ...
DO you have a tutorial ?
Can I try with Nexus root kit with "back to stock" 4.2.2 (and what to choose in current status ? normal or soft bricked ?)
thanks anyway.
alucard_xs said:
Ouf ...
DO you have a tutorial ?
Can I try with Nexus root kit with "back to stock" 4.2.2 (and what to choose in current status ? normal or soft bricked ?)
thanks anyway.
Click to expand...
Click to collapse
Download stock package.
Unzip contents to C:\Program Files\WugFresh Development\data.
Open toolkit > Advanced Utilities > Launch CMD > "flash-all.bat" will restore your device to 4.3 stock.
thanks but do I have to use the 4.3 stock or the 4.2.2 stock like I was before the failed flash ?
You can flash any version you want (4.1.2, 4.2.2, 4.3).
Thanks a lot.
last question :
what kind of model should i use in the configuration ?
4.3 or 4.2.2 ? is it important ?
That will flash all the images. You can flash each image individually.
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
---------- Post added at 06:08 AM ---------- Previous post was at 06:07 AM ----------
alucard_xs said:
Thanks a lot.
last question :
what kind of model should i use in the configuration ?
4.3 or 4.2.2 ? is it important ?
Click to expand...
Click to collapse
As I said, it is entirely up to you on which Jelly Bean version you want.
Okay, I did what you tell me and it seems to be okay right now !
What a relief !!
Thanks again for your help !!!!!
That's good.
Flash a original firmware to your tablet
Sent from my LG-P700 using xda app-developers app
Username invalid said:
That's good.
Click to expand...
Click to collapse
im having trouble with the steps you have suggested .. when i try the command "flash-all.bat" it says command not recognized ..
funkme021 said:
im having trouble with the steps you have suggested .. when i try the command "flash-all.bat" it says command not recognized ..
Click to expand...
Click to collapse
{
"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 to extract everything in the stock image package including "flash-all.bat" to your ADB/Fastboot folder.
https://www.youtube.com/watch?v=foLQCNxroHw
Username invalid said:
You need to extract everything in the stock image package including "flash-all.bat" to your ADB/Fastboot folder.
https://www.youtube.com/watch?v=foLQCNxroHw
Click to expand...
Click to collapse
it appears that i need to have an updated bootloader ... i currently have 4.18 and it says the update requires 4.23 ... but when i tried to flash the 4.23 bootloader it says that it sends it to the device just fine but i get the failed message when it tries to write the bootloader ... giving me this message FAILED <remote: invalid Partition Name.> ... <FRUSTRATED> lol ... also i appreciate all your help
UPDATE
ok i finally got it .. i just went and downloaded the factory images for jdq39 (the image that used the bootloader v. 4.18) installed that and then let the tablet update itself... thats what i call a crash course in fastboot lol .. learned the hard way but i think i somewhat understand it now
Related
Dear value members i need some help with my Zenfone 5 AC501CG it stuck on boot
i tried many methods but all of it doesn't work
i can boot in fast boot with no problem but the bootloader is locked
1- i tried sideload via adb for kitkat nad lolipop it fail to complete as E: can't mount data ... recovery etc
2- i tried via xFSTK-Downloader tool and flashed dnx and other files it complete but doesn't accept ant rooms
3- i tried via ASUS Flash Tool and flash raw files a message say " oem partion command failed retval = -1
4- i tried to unlock bootloader to flash TWRP but all files excute some order and when sending dnx and iwfi fail of command and message say unlocked success but in fact the bootloader stil locked and i can't flash TWRP
here some photo
how can i pass this problem i had 4 days searching without any progress
{
"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"
}
have you checked the partition.tbl file? there's some editing as i have red a couple of days ago. it's a known error on some raw firmwares. but honestly i haven't even started using Zenfone yet coz I'm still stuck at boot 😂
and im guessing you're on fake Chinese firmware too is that right? those are firmware versions 2.99 with fake serial. reference was your screenshots uploaded. but correct me if I'm wrong
If u need to unlock bootloader
use auto unlock go to this thread http://forum.xda-developers.com/zenfone-5/general/recovery-twrp-2-8-6-0-asus-zenfone-5-t3136263
gradd said:
have you checked the partition.tbl file? there's some editing as i have red a couple of days ago. it's a known error on some raw firmwares. but honestly i haven't even started using Zenfone yet coz I'm still stuck at boot 😂
and im guessing you're on fake Chinese firmware too is that right? those are firmware versions 2.99 with fake serial. reference was your screenshots uploaded. but correct me if I'm wrong
Click to expand...
Click to collapse
i don't think so
i update the phone many times via OTA and i checked imei via imei info and all correct and last room was kitkat 2.22.40 as i remember
alvinhaw said:
If u need to unlock bootloader
use auto unlock go to this thread http://forum.xda-developers.com/zenfone-5/general/recovery-twrp-2-8-6-0-asus-zenfone-5-t3136263
Click to expand...
Click to collapse
i face this error and unlocking by other ways other error see pictures
The main problem in flashing partion.tpl file
i got this error fron asus flash tool or if i used fastboot flash
somaare said:
i face this error and unlocking by other ways other error see pictures
Click to expand...
Click to collapse
study the thread
this is the easiest method
there is 2 build
i use build 3 successfuly unlocked
i use auto unlock cuz I'm not sure
what model it is...
u can manually fastboot flash it
using Advance User Download
follow the instruction
anyway I'm new to zenfone
never buy zenfone again!
alvinhaw said:
study the thread
this is the easiest method
there is 2 build
i use build 3 successfuly unlocked
i use auto unlock cuz I'm not sure
what model it is...
u can manually fastboot flash it
using Advance User Download
follow the instruction
anyway I'm new to zenfone
never buy zenfone again!
Click to expand...
Click to collapse
none of the 2 build success to unlock the boatloader
the same error when sending dnx and iwfi : command fail invalid angrument
i think u need to check DNX & ifwi
with ur stock rom, cuz u mention
ur device is A501CG
U try to get this 2 file from stock rom
n flash via fastboot see still error not...if not then Google search for related A501CG unlock bootloader
I have good experience with other phones but this is my first time working with ZE550KL.
So I took my uncle's phone and he asked me to update his phone to the latest firmware to get the VoLTE feature.
He is was on ZE550KL_WW_21.40.1220.1708 which is Marshmallow of the ZEN UI.
I have downloaded the latest firmware from the ASUS website but I couldn't update it because the recovery which came with the marshmallow update is broken.
These are the errors I got
{
"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"
}
Here is what I did, and hope this works for everyone.
Hoping that you already went and searched about the problem over the internet.
These are the things you need to download :
ADB and fastboot
https://drive.google.com/file/d/0B0aDjdU4gTwZZW1HUHhqWnEteXM/view
Recovery image file
https://drive.google.com/open?id=0B0aDjdU4gTwZa1MyUmVPN3BhQjQ
Latest firmware:
https://www.asus.com/in/support/Download/39/1/0/22/ZROQURlyupei1ZQz/32/
1. Download the adb and fastboot drivers. Download the latest firmware and copy it onto your internal storage.
2. Boot into the bootloader.
3. Download the recovery image and paste it into the adb folder.
4. Now type the following command.
Code:
fastboot flash recovery recovery.img
5. This step is very important.
Now, all you have to do is hold the power button and the volume down button to boot into the installed recovery.
Remember that if you restart your phone after step 4, your old recovery(which does not work) will still be there.
6. Now select update from sdcard and select the zip file of the latest firmware you downloaded.
7. It will take at least 10 minutes to install, don't panic if you think the screen froze.
I hope this solves the issues many users are facing.
Feel free to ask questions, I will be very happy to answer.
The recovery we installed is the recovery of Android Lollipop version of the Zen UI ROM.
Thanks. It worked. The only difference is that after flashing the old recovery, my SD card was showing blank. So i selected the adb sideload option and flashed the new build.. Thanks for your guide.
Thanks but few doubts remain. The recovery you used is from Lollipop`s 1.17.40.1503 right?
Can we not do this by installing a temporary recovery image (twrp)?
I have also read elsewhere ( https://devs-lab.com/e-unable-to-mount-asdf-recovery-error-solved.html ) that you would need the boot image too. But your instructions are way too easier and easy to follow. Why don't you use boot image?
If we are using the boot image then which version of it should we use?
hellbraker said:
Thanks but few doubts remain. The recovery you used is from Lollipop`s 1.17.40.1503 right?
Can we not do this by installing a temporary recovery image (twrp)?
I have also read elsewhere ( https://devs-lab.com/e-unable-to-mount-asdf-recovery-error-solved.html ) that you would need the boot image too. But your instructions are way too easier and easy to follow. Why don't you use boot image?
If we are using the boot image then which version of it should we use?
Click to expand...
Click to collapse
Before I tried any of this... First thing I did was boot TWRP and install the lastest firmware.
But I couldn't do so because TWRP doesn't let you flash .img files.
And for the best result it is always better for you to use the official recovery to flash an official firmware.
Because ASUS f***ed up, I needed to install the previous version of the recovery to flash the firmware.
And I'm very happy that my guide worked for you.
Don't forget to give thanks. :laugh:
I haven't tried it yet. So you didn't tamper with boot.img at all. Right?
Also as previously asked what's the build number from which you extracted the recovery.img? Is it from .1503?
My current build is .1708 same as what you worked on. And will data get erased during this process?
How can I boot into the bootloader? is it by unlocking it? or is there any other non-invasive way?
Update: I installed as per your instructions. Device shows "Optimizing app 5 of 51".
Thank you.
Thank you
Thank you sir, this helped me a lot.
recovery link is asking need access plzz help
My Asus Zenfone doesn't boot anymore and doesn't even allow me to factory reset it from the bootloader. How to force reset it??
It is the same problem as written here : https://forum.xda-developers.com/p8...awei-p8-lite-2017-pra-lx1-brick-trwp-t3660664
I've followed every steps, but my phone is still bricked.
My build version is (I guess?) PRA-LX1C432B100
I tried several firmware builds to restore on, but when I try to install it (by pushing POWER / VOL - / VOL +) :
- PRA-LX1C530B130 : firmware versions mismatch
- PRA-LX1C33xxxx : can't install, I don't remember error message but surely the same as the above one.
- PRA-LX1C432B128 : "Installing update" at 5% then "Software install failed" with sub message "Get help from http://www.emui.com/emotiondownload?mod=restore"
I followed the rooting method from a french website that was for build PRA-LX1C432B100 but I can't find this firmware anywhere.
Can someone have the link ? Tried with Firmware Finder.. Now i'm downloading from needrom but still don't know if it's for the good build version...
When the phone boots, it displays :
- HW Logo
- Warning about the BL
- HW logo
- blank
- HW logo
- Warning about the BL
- erestore
When trying to download and reboot from erestore, it says "Getting package info failed" and thus, can't download.
----
TWRP
I also tried to flash PRA-LX1C530B130 update.zip, but I get the exact same thing as here : https://forum.xda-developers.com/attachment.php?attachmentid=4008385&d=1484772172
---
Any way to unbrick this d*mn thing ?
I need help, thank you.
Your phone is locked. Try the unlocking by huawei unlockcode.
Thank you for this fast answer,
though, where do I enter the code(s) ?
I went to https://tools.texby.com/unlock-codes/huawei/ to obtain my code, is that correct ?
I entered fastboot, no devices found with "huawei code writer"
Same with recovery mode and eRecovery :
{
"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"
}
Do this command in fastbootmode by adb:
fastboot oem unlock 1234567...... (your unlock code from Huawei.
Oh okay, but i'm already unlocked.
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.004s
Click to expand...
Click to collapse
Ok., then flash the stock recovery again and make a factoryreset.
I can't find the stock recovery on internet nor on Firmware Finder. Do you know where I can find PRA-LX1C432B100 ?
I flashed many times on differents build versions those files :
recovery.img
boot.img
system.img
cust.img
Do I need to only flash the stock recovery (if I can find it..) to make everything else work ?
if I have no stock system nor stock boot, will it boot ?
And by "stock" I mean "stock for my device" because I've tried many stock images that end up in erecovery, even after a factory reset in the stock recovery.
-- EDIT --
With the mobile app, it says that the PRA-LX1C432B100 has been removed from the server.
Flash TWRP and see if it starts there.
ChinHon said:
Flash TWRP and see if it starts there.
Click to expand...
Click to collapse
Flashed TWRP.
Can still not boot on system (it's going on eRecovery) but sure I can boot in TWRP.
You have removed the usb cable during the reboot?
I have bricked my phone, can't install rom from erecovery becouse doesn't retrive update from server. What can I do?
I'm disperate can you help me?
ChinHon said:
You have removed the usb cable during the reboot?
Click to expand...
Click to collapse
Yes I did
Sw0ut said:
Yes I did
Click to expand...
Click to collapse
Ah, but I did it again and it worked.
Go TWRP and I can boot. I can indeed see my build version which is PRA-LX1C432B164.
I can boot, so i'm gonna follow the tutorial again.
Thanks.
Sw0ut said:
Ah, but I did it again and it worked.
Go TWRP and I can boot. I can indeed see my build version which is PRA-LX1C432B164.
I can boot, so i'm gonna follow the tutorial again.
Thanks.
Click to expand...
Click to collapse
:good:
hi, yesterday mi moto g4 xt1621 was working well but today when i switch it on it didn't show me the boot logo and started in fastboot 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"
}
so i tried to went to the recovery and it gave me an error which said: "start up failed:
your device didn't start up successfully.
use the software repair assistant on computer to repair your device.
connect your device to your computer to get the software repair assistant
AP Fastboot Flash mode (secure)
Fastboot reason: failed to initialize partition table
error: no bootimage found. skip to fastboot
boot up failed
i tried a lot of things, when i connected it to my pc recognizes it as Fastboot athene_13mp S
and i didn't get the software repair assistant
and
i don't know what to do if someone could help me, I would be very grateful
have you found the solution
adithya11198 said:
have you found the solution
Click to expand...
Click to collapse
unfortunately i haven't found the solution yet
System lost perhaps?
It seems that the boot image was lost or erased on your phone, at least you still keep the Bootloader right? it's still alive, so there's a way to solve it, yet, this means the procedure may be hard, but you can make it boot again but your files will be erased since flashing a rom by fastboot usually clears all User Data, follow the steps from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but Skip the Blank Flash files, you won't need them (thankfully) I hope this solve your problem
Omega Adrek said:
It seems that the boot image was lost or erased on your phone, at least you still keep the Bootloader right? it's still alive, so there's a way to solve it, yet, this means the procedure may be hard, but you can make it boot again but your files will be erased since flashing a rom by fastboot usually clears all User Data, follow the steps from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but Skip the Blank Flash files, you won't need them (thankfully) I hope this solve your problem
Click to expand...
Click to collapse
Thank you Omega Adrek i will try this :fingers-crossed:
Question: I don't have the boot loader unlocked. Is there a problem with that?
null2025 said:
Thank you Omega Adrek i will try this :fingers-crossed:
Question: I don't have the boot loader unlocked. Is there a problem with that?
Click to expand...
Click to collapse
Since the Link contains the Stock Moto G4/G4 Plus rom, you shouldn't have any problem with the Bootloader being locked or unlocked, so try it out and hopefully it will make Android boot once again
Omega Adrek said:
Since the Link contains the Stock Moto G4/G4 Plus rom, you shouldn't have any problem with the Bootloader being locked or unlocked, so try it out and hopefully it will make Android boot once again
Click to expand...
Click to collapse
Ok thanks adrek, i'm going to try it when my PC recognizes my smartphones again, it's another problem which I have but I don't want to bother you with that
Rom flashing failed . What should I do?
adithya11198 said:
Rom flashing failed . What should I do?
Click to expand...
Click to collapse
As the message says, it can't find a bootlogo. (usually logo.bin). If you've got a locked bootloader, you must have all key partitions, including logo.bin on the same patch level (and as such you may have to flash all partitions).
Which firmware did you try to flash and what flashing commands did you use, and can you show us the outputs of said commands?
This will help You : https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
thank you
Omega Adrek said:
It seems that the boot image was lost or erased on your phone, at least you still keep the Bootloader right? it's still alive, so there's a way to solve it, yet, this means the procedure may be hard, but you can make it boot again but your files will be erased since flashing a rom by fastboot usually clears all User Data, follow the steps from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but Skip the Blank Flash files, you won't need them (thankfully) I hope this solve your problem
Click to expand...
Click to collapse
Thank you really much omega adrek, it worked, my moto g4 owe you its life
Hi,
I've installed an ota update and the device didn't boot... it is stuck in a bootloop....
When i try to flash via fastboot, it appears an error saying that the device is locked ant cennot erase...
via fastboot oem unlock i get the error message: Remote: oem unlock is not allowed
via MiUnlocker the unlock gets to de 50% and gives an error and on its logs it says: Remote: oem unlock is not allowed
I tryed to flash TWRP with command fastboot flash recovery but the error is the same: remote: partition flashing is not allowed
Can anyone help me please??
I'm stuck on the bootloop i can't go to setting - developer - allow oem unlock option!!
Have you tried doing a Factory Reset from stock recovery?
This is a strange behavior, even if an OTA update corrupted the system for some reason, the phone should boot from the original slot.
Have you tried switching slots manually from fastboot ?
Parnas72 said:
This is a strange behavior, even if an OTA update corrupted the system for some reason, the phone should boot from the original slot.
Have you tried switching slots manually from fastboot ?
Click to expand...
Click to collapse
How can i do that?
Hello!
I've faced the exact same problem yesterday.
You need to force the phone to boot in EDL mode by opening the back cover and short circuit 2 pins as shown in THIS video.
After you have the phone in EDL and being detected by your PC (you need the correct drivers, you may get them on THIS thread by @CosmicDan), you may use MiFlash Tool to flash official PIE Rom, access developer options and enable oem unlock to be able to unlock your phone again.
If you wish to revert to Oreo, please use THIS guide.
Cheers!
Tepig said:
Have you tried doing a Factory Reset from stock recovery?
Click to expand...
Click to collapse
No recovery.. i get this:
{
"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"
}
Typhus_ said:
Hello!
I've faced the exact same problem yesterday.
You need to force the phone to boot in EDL mode by opening the back cover and short circuit 2 pins as shown in THIS video.
After you have the phone in EDL and being detected by your PC (you need the correct drivers, you may get them on THIS thread by @CosmicDan), you may use MiFlash Tool to flash official PIE Rom, access developer options and enable oem unlock to be able to unlock your phone again.
If you wish to revert to Oreo, please use THIS guide.
Cheers!
Click to expand...
Click to collapse
Obrigado!
I'll try it now!!
xistolas said:
No recovery.. i get this:
Click to expand...
Click to collapse
Actually you have a recovery. You need to long press the power button and, afterwards (not at the same time), press the volume + button. You'll see that all options will appear.
xistolas said:
How can i do that?
Click to expand...
Click to collapse
fastboot getvar current-slot
to show the current slot,
fastboot --set_active=a or fastboot --set_active=b
to change it.
xistolas said:
Obrigado!
I'll try it now!!
Click to expand...
Click to collapse
get into fastboot mode
hot boot twrp using fastboot command
copy efs backup to twrp backup folder and restore
then go into bootloader mode
flash the firmware using miflash
---------- Post added at 09:27 PM ---------- Previous post was at 09:23 PM ----------
akashavel said:
get into fastboot mode
hot boot twrp using fastboot command
copy efs backup to twrp backup folder and restore
then go into bootloader mode
flash the firmware using miflash
Click to expand...
Click to collapse
follow from step 6 to end in below link
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624