Is this real ? i really cant access boot loader , just the recovery with the no command screen
can you confirm ??
if so then what i think that this device is already dead
It has a fasboot mode, for now I can only access it via adb (adb reboot bootloader). It shows a black screen with fastboot mode at the bottom.
It also has a stock recovery mode, shows 'no command' but can be activated by pressing power button.
After you've activated it:
Vol+ to select
Vol- navigate down
Power to go back
Adb No devices found , idk why my Laptop doesn't detect my desire 820s
wil try now just installed htc sync manager
okay it worked and i went to fastboot mode , when i give a cmd order it says waiting for device
eg..... fastboot oem info
Same here
fastboot oem unlock
FAILED (remote: unknown command)
fastboot oem get_identifier_token
FAILED (remote: unknown command)
any idea ?
Nc.netcat said:
Same here
fastboot oem unlock
FAILED (remote: unknown command)
fastboot oem get_identifier_token
FAILED (remote: unknown command)
any idea ?
Click to expand...
Click to collapse
Mediatek Htc devices do not need bootloader unlocking, you can flash anything from fastboot mode
---------- Post added at 04:16 PM ---------- Previous post was at 04:10 PM ----------
Mohamed Yaser said:
Is this real ? i really cant access boot loader , just the recovery with the no command screen
can you confirm ??
if so then what i think that this device is already dead
Click to expand...
Click to collapse
You are right, Mediatek HTC devices dont have bootloader. Infact mediatek htc phones can be flashed with SP Flash tool just like micromax phones. I know this is true for htc 816g.
sziraqui said:
Mediatek Htc devices do not need bootloader unlocking, you can flash anything from fastboot mode
.
Click to expand...
Click to collapse
hhmm
fastboot flash recovery recovery.img => partition 'recovery' not support flash
but flashing recovery with SP flash tool will work for sure.
1. Put your custom recovery in the firmware folder,
2. del stock recovery.img,
3. rename your custom recovery as recovery.img,
4. load scatter file,
5. uncheck everything except recovery
6. click download and then connect your powered off phone to pc while holding vol down
someone Please confirm if this works with 820s, without worrying about bootloader
sziraqui said:
but flashing recovery with SP flash tool will work for sure.
1. Put your custom recovery in the firmware folder,
2. del stock recovery.img,
3. rename your custom recovery as recovery.img,
4. load scatter file,
5. uncheck everything except recovery
6. click download and then connect your powered off phone to pc while holding vol down
someone Please confirm if this works with 820s, without worrying about bootloader
Click to expand...
Click to collapse
It works. How about flashing a RUU?
Gibz97 said:
It works. How about flashing a RUU?
Click to expand...
Click to collapse
Can mention on which device you have checked it, does it has locked bootloder (if exists)?
RUU in mediatek? i dont think mediatek phones have RUU, (try "fastboot oem rebootRUU" to check)
But if it does, you can extract rom.zip from the RUU THEN EXTRACT system.img, boot.img and recovery.img
Then keep copy this to your firmware folder (containg scatter file)
load scatter file
Uncheck everything except system,boot and recovery in sp flash tool
Click download and connect your powered off device to pc holding vol down
sziraqui said:
Can mention on which device you have checked it, does it has locked bootloder (if exists)?
RUU in mediatek? i dont think mediatek phones have RUU, (try "fastboot oem rebootRUU" to check)
But if it does, you can extract rom.zip from the RUU THEN EXTRACT system.img, boot.img and recovery.img
Then keep copy this to your firmware folder (containg scatter file)
load scatter file
Uncheck everything except system,boot and recovery in sp flash tool
Click download and connect your powered off device to pc holding vol down
Click to expand...
Click to collapse
I've done that but the phone usually cannot boot into the system.
BTW I am on Kitkat 4.4.4 without Sense and I want to flash Lollipop 5.0.2 Sense 7.
The RUU is from a Taiwanese variant 820ys which runs Lollipop 5.0.2 and Sense 7 out of the box, same models(htc_a50ml_dtul)
The problem is that the Kitkat Firmware has smaller partitions compared to the lollipop one. An example is the Kitkat system partition which is about 1.4Gbs while Lollipop has about 4.9Gbs, so I cannot flash with the same scatter file.
So I edit the scatter file to inflate the partitions in order to accommodate the big Lollipop files (sytem.img,recovery.img and boot.img) and perform firmware upgrade.
What could be stopping it from booting? Is it due the fact that the Lollipop boot and recovery are verified? Thanks in advance
Screenshots for Kitkat and Lollipop firmware files below
Gibz97 said:
I've done that but the phone usually cannot boot into the system.
BTW I am on Kitkat 4.4.4 without Sense and I want to flash Lollipop 5.0.2 Sense 7.
The RUU is from a Taiwanese variant 820ys which runs Lollipop 5.0.2 and Sense 7 out of the box, same models(htc_a50ml_dtul)
The problem is that the Kitkat Firmware has smaller partitions compared to the lollipop one. An example is the Kitkat system partition which is about 1.4Gbs while Lollipop has about 4.9Gbs, so I cannot flash with the same scatter file.
So I edit the scatter file to inflate the partitions in order to accommodate the big Lollipop files (sytem.img,recovery.img and boot.img) and perform firmware upgrade.
What could be stopping it from booting? Is it due the fact that the Lollipop boot and recovery are verified? Thanks in advance
Screenshots for Kitkat and Lollipop firmware files below
Click to expand...
Click to collapse
well this question will take the thread off topic. I would request you to create a new thread regarding this issue under "q&a,help and troubleshooting". Chances of your problem getting solved are higher if you do so. I will post my views regarding your issue in that thread. And i apologize to OP, because i only started answering questions irrelevant to his thread.
i totally accept off topics if they are helpful
sziraqui said:
but flashing recovery with SP flash tool will work for sure.
1. Put your custom recovery in the firmware folder,
2. del stock recovery.img,
3. rename your custom recovery as recovery.img,
4. load scatter file,
5. uncheck everything except recovery
6. click download and then connect your powered off phone to pc while holding vol down
someone Please confirm if this works with 820s, without worrying about bootloader
Click to expand...
Click to collapse
Hi.
It worked, but pressing Vol UP, not down. Anyway i've installed Recovery but when i try to access it from bootloader the device stopped me tellig that is for Android developers. I think that is because at the top of bootloader screen it tell "LOCKED". Any solution?
htc desire 820 softbrick not connecting with fastboot
Related
I can't well english. sorry. I have been using a translator.
My Tablet : Lenovo yoga 2 10 Android, only WiFi version (1050F) and Lollipop version
I accidentally flashing -> delete recovery!! :crying:
but, I was rooting.
Fortunately, I have been using Android, without problems.
I know this :
(Install TWRP Recovery, but only Kitkat.. or waiting)
http://forum.xda-developers.com/android/development/twrp-t3103296?goto=newpost
(Lollipop -> Kitkat, but It is difficult and risk)
http://forum.xda-developers.com/thinkpad-tablet/general/guide-root-yoga-tablet-2-pro-8-10-13-3-t2930428/post60490907#post60490907
Is there any other way?
what do you want?
to root in lollipop?
to return to stock kitkat?
ionioni said:
what do you want?
to root in lollipop?
to return to stock kitkat?
Click to expand...
Click to collapse
Forgive me for being late.
I using lollipop(root), Android(OS) is operating normally And unlocked bootloader
I want to install Recovery
neverapple88 said:
Forgive me for being late.
I using lollipop(root), Android(OS) is operating normally And unlocked bootloader
I want to install Recovery
Click to expand...
Click to collapse
you want to install back the stock recovery? or do you want a custom one?
if stock it's easy, if you want a custom one first you will need an unlocked bootloader then the custom recovery itself (compatible with your tab)
you have an unlocked bootloader??? what? how?
also try translating with google translate it's much better at asian languages (you koreean huh?)
ionioni said:
you want to install back the stock recovery? or do you want a custom one?
if stock it's easy, if you want a custom one first you will need an unlocked bootloader then the custom recovery itself (compatible with your tab)
you have an unlocked bootloader??? what? how?
also try translating with google translate it's much better at asian languages (you koreean huh?)
Click to expand...
Click to collapse
I now, using debian noroot, Android in trying -> text delete...
I don't know (how to unlocked bootloader)
but, I use googling -> find link : http://unlock-bootloader.info/mp3-0/lenovo-yoga-tablet-2-10-1-6731.html This(Link -> Files) is malware!
I think unlocked bootloader because...
http://forum.xda-developers.com/showpost.php?p=57543871&postcount=1
here post : WARNING : This Temporary CWM / TWRP Recovery Session is for some Intel Devices with locked boot loaders.
It is not intended for installing custom roms as if the devices has a locked bootloader the device will fail to boot the unsigned images
I succeeded(rooting), therefore i think unlocked
Sorry my english.
I using korean
and i now go to word understand
neverapple88 said:
I now, using debian noroot (= therefore can't using translating), Android in trying -> text delete...
I don't know (how to unlocked bootloader)
but, I use googling -> find link : http://unlock-bootloader.info/mp3-0/lenovo-yoga-tablet-2-10-1-6731.html
I think unlocked bootloader because...
http://forum.xda-developers.com/showpost.php?p=57543871&postcount=1
here post : WARNING : This Temporary CWM / TWRP Recovery Session is for some Intel Devices with locked boot loaders.
It is not intended for installing custom roms as if the devices has a locked bootloader the device will fail to boot the unsigned images
I clear!(rooting), therefore i think unlocked
Sorry my english.
I using korean
and i now go to word understand
Click to expand...
Click to collapse
그래서 , 이 순간에 당신은 당신의 장치 에 Lollipop 가 있습니까? 그리고 당신은 root 을 갖고 싶어 ?
또는 KitKat 로 다운 그레이드 싶어?
ionioni said:
그래서 , 이 순간에 당신은 당신의 장치 에 Lollipop 가 있습니까? 그리고 당신은 root 을 갖고 싶어 ?
또는 KitKat 로 다운 그레이드 싶어?
Click to expand...
Click to collapse
Yes, I have Lollpop. (rooted)
I no want KitKat.
I want custom recovery, but can this 'only' kitkat version. (sry english)
Therefore, I want stock recovery.
and english <-> korean translate(computer) is bed
I go to translate(understand) = very better
1. for stock recovery:
boot tablet in droidboot mode (PowerOff then PowerOn+VolDown)
on your PC issue the command: fastboot flash recovery recovery.img using the recovery.img from the stock rom
(i am assuming your droidboot is functional as you were asking for recovery)
2. if you cannot boot into droidboot mode you will need to restore the droidboot: extract on your PC from the OTA Lollipop package, the files bootx64.efi (it can be found in the esp.zip in \EFI\BOOT directory) and the droidboot.img file, then boot into dnx mode (PowerOff then PowerOn+VolUp+VolDown, screen should say "starting fastboot..."), at this moment issue in order these commands:
fastboot flash osloader bootx64.efi
fastboot boot droidboot.img and after it boots in droidboot mode enter:
fastboot flash fastboot droidboot.img
the bootx64.efi and droidboot.img are both from the OTA Lollipop package (you can find the OTA over the net, YT2-1050F_USR_S100017_1505261558_WW52_CN_otafull) or you can ask someone with Lollipop installed to give them from their system (bootx64.efi is on the ESP partition and droidboot.img can be dumped with a dd from the fastboot partition)
ps. there is no custom recovery at this moment (lollipop or kitkat) as there is no unlocked bootloader (one can flash whatever wants on the boot/fastboot/recovery partition but the images will be rejected at boot for not being signed)
ionioni said:
1. for stock recovery:
boot tablet in droidboot mode (PowerOff then PowerOn+VolDown)
on your PC issue the command: fastboot flash recovery recovery.img using the recovery.img from the stock rom
(i am assuming your droidboot is functional as you were asking for recovery)
2. if you cannot boot into droidboot mode you will need to restore the droidboot: extract on your PC from the OTA Lollipop package, the files bootx64.efi (it can be found in the esp.zip in \EFI\BOOT directory) and the droidboot.img file, then boot into dnx mode (PowerOff then PowerOn+VolUp+VolDown, screen should say "starting fastboot..."), at this moment issue in order these commands:
fastboot flash osloader bootx64.efi
fastboot boot droidboot.img and after it boots in droidboot mode enter:
fastboot flash fastboot droidboot.img
the bootx64.efi and droidboot.img are both from the OTA Lollipop package (you can find the OTA over the net, YT2-1050F_USR_S100017_1505261558_WW52_CN_otafull) or you can ask someone with Lollipop installed to give them from their system (bootx64.efi is on the ESP partition and droidboot.img can be dumped with a dd from the fastboot partition)
ps. there is no custom recovery at this moment (lollipop or kitkat) as there is no unlocked bootloader (one can flash whatever wants on the boot/fastboot/recovery partition but the images will be rejected at boot for not being signed)
Click to expand...
Click to collapse
Sorry, I find stock rom -> fail
I search YT2-1050F_USR_S100017_1505261558_WW52_CN_otafull, stock rom, other..
but, download -> ???.apk or close server or other.. nowhere rom
Where is stock rom?
1. do you need the recovery.img from the stock rom? if you have a valid droidboot(fastboot), ie if you get the droidboot menu when you start with (Pwr+VolDown) then the recovery.img can be found in the stock rom, check the all in one thread for 1050F stock rom (the recovery.img is the KitKat one, the OTA doesn't update that)
2. if you need bootx64.efi and droidboot.img meaning you cannot boot in droidboot(fastboot) mode (you are sure you cannot flash with fastboot) then the two files can be found in the OTA, search baidu for YT2-1050F_USR_S100017_1505261558_WW52_CN_otafull.zip, actually this is OTA for chinese package but i think it's safe to get/flash the bootx64.efi /droidboot.img from there (and only that)
Update: find all the needed files (from stock 1050F Lollipop ROM) here https://anonfiles.com/file/1025d77353f4395d090b07c88bcf156d
1. for stock recovery reflashing: boot tablet in droidboot mode (PowerOff then PowerOn+VolDown)
on your PC issue the command: fastboot flash recovery recovery.img
2. if you cannot boot into droidboot mode you will need to restore the droidboot first: boot into dnx mode (PowerOff then PowerOn+VolUp+VolDown, screen should say "starting fastboot..."), at this moment issue in order these commands:
fastboot flash osloader bootx64.efi
fastboot boot droidboot.img and after it finishes booting in droidboot mode (screen should display "waiting commands" in the bottom) enter:
fastboot flash fastboot droidboot.img
ionioni said:
1. do you need the recovery.img from the stock rom? if you have a valid droidboot(fastboot), ie if you get the droidboot menu when you start with (Pwr+VolDown) then the recovery.img can be found in the stock rom, check the all in one thread for 1050F stock rom (the recovery.img is the KitKat one, the OTA doesn't update that)
2. if you need bootx64.efi and droidboot.img meaning you cannot boot in droidboot(fastboot) mode (you are sure you cannot flash with fastboot) then the two files can be found in the OTA, search baidu for YT2-1050F_USR_S100017_1505261558_WW52_CN_otafull.zip, actually this is OTA for chinese package but i think it's safe to get/flash the bootx64.efi /droidboot.img from there (and only that)
Update: find all the needed files (from stock 1050F Lollipop ROM) here https://anonfiles.com/file/1025d77353f4395d090b07c88bcf156d
1. for stock recovery reflashing: boot tablet in droidboot mode (PowerOff then PowerOn+VolDown)
on your PC issue the command: fastboot flash recovery recovery.img
2. if you cannot boot into droidboot mode you will need to restore the droidboot first: boot into dnx mode (PowerOff then PowerOn+VolUp+VolDown, screen should say "starting fastboot..."), at this moment issue in order these commands:
fastboot flash osloader bootx64.efi
fastboot boot droidboot.img and after it finishes booting in droidboot mode (screen should display "waiting commands" in the bottom) enter:
fastboot flash fastboot droidboot.img
Click to expand...
Click to collapse
(1, 2) Succeeded!
It has been a great help.
I will be diligent backups from today.
Thank you for your sincere answer to the question.
neverapple88 said:
but, I use googling -> find link : http://unlock-bootloader.info/mp3-0/lenovo-yoga-tablet-2-10-1-6731.html
Click to expand...
Click to collapse
nope... the only thing you will get from there is malware
ionioni said:
nope... the only thing you will get from there is malware
Click to expand...
Click to collapse
OMG,,,
Fortunately, I did not run it.
Found a way to reboot to edl mode from fastboot
All credits to @emuzychenko
1) Download modified fastboot file
2) Reboot your phone to fastboot
3) Double click on edl.cmd
4) You are on 9008/edl mode
5) Flash any fastboot image from Mi flash
You successfully unbricked your device
Hi
Try with that method also. It seams to work .
Next time I brick it again (trust me, it will happen) I will give those a try.
This is the solution www(dot)htcmania.com(/)showthread(dot)php?t=1163463
Cheked by me, the brick was to try to unlock the bootloader without the Xiaomi message.
Sorry for my english, bu ti hope to be helpful.
To restore the default Bootloader copy paste the emmc_appsboot.mbn from Fastboot Rom to the Adb foldee
and type command on cmd
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot reboot
For those who have failed and stuck on "HS USB 900E" and the bootloader stick locked here is the solution :
1. Enter fastboot by holding vol down + power
2. Plug your RN3Pro to PC
2. Flash original bootloader from official fastboot firmware
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
3. Type again :
fastboot reboot
and quickly hold volume up untuk it enter "sideload" mode
4. Install Mi PC Suite from this link en.miui.com/thread-225600-1-1.html
5. Let the Mi PC Suite download the latest chinese firmware, just sit and wait until it done
6. Lets Brick the beast again
parfetto said:
Hi
Try with that method also. It seams to work .
Click to expand...
Click to collapse
this method only works for few very people, everyone cant access adb through recovery.
apixbuanget said:
For those who have failed and stuck on "HS USB 900E" and the bootloader stick locked here is the solution :
1. Enter fastboot by holding vol down + power
2. Plug your RN3Pro to PC
2. Flash original bootloader from official fastboot firmware
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
3. Type again :
fastboot reboot
and quickly hold volume up untuk it enter "sideload" mode
4. Install Mi PC Suite from this link en.miui.com/thread-225600-1-1.html
5. Let the Mi PC Suite download the latest chinese firmware, just sit and wait until it done
6. Lets Brick the beast again
Click to expand...
Click to collapse
Have you tested this method yourself? I think this is for people who bricked the device but had stock recovery inside, what about people who has twrp and bricked the device? Also I dont think you can flash anything through fastboot in locked bootloader
IT WORKS
apixbuanget said:
For those who have failed and stuck on "HS USB 900E" and the bootloader stick locked here is the solution :
1. Enter fastboot by holding vol down + power
2. Plug your RN3Pro to PC
2. Flash original bootloader from official fastboot firmware
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
3. Type again :
fastboot reboot
and quickly hold volume up untuk it enter "sideload" mode
4. Install Mi PC Suite from this link en.miui.com/thread-225600-1-1.html
5. Let the Mi PC Suite download the latest chinese firmware, just sit and wait until it done
6. Lets Brick the beast again
Click to expand...
Click to collapse
Worked like a magic. I can confirm for sure. Was stuck at HS USB 900E with locked bootloader.
Rajdip said:
Have you tested this method yourself? I think this is for people who bricked the device but had stock recovery inside, what about people who has twrp and bricked the device? Also I dont think you can flash anything through fastboot in locked bootloader
Click to expand...
Click to collapse
Yeah i bricked mine with twrp .. and i cannot enter into recovery mode now.. only fastboot works and i cannot flash stock recovery too because the bootloader is locked :/ stupid Mi :/
Dharani_V said:
Yeah i bricked mine with twrp .. and i cannot enter into recovery mode now.. only fastboot works and i cannot flash stock recovery too because the bootloader is locked :/ stupid Mi :/
Click to expand...
Click to collapse
So, did you try above mentioned method?
amsmu said:
So, did you try above mentioned method?
Click to expand...
Click to collapse
Yes i did .. and its not allowing me to flash anything .. Getting Error Device is locked :/
failed bro, getting error device is locked using QFIL.:crying:
Guys, please mention the reason behind your device getting bricked too when you are reporting what worked and what didn't. Like whether during unlock bootloader process(without xiaomi's permission) or flashing custom ROM(most probably MIUI official updates) via twrp.
Dharani_V said:
Yes i did .. and its not allowing me to flash anything .. Getting Error Device is locked :/
Click to expand...
Click to collapse
What were you doing when it bricked?
Go to service center. They will repair it
mine happened same..... hard bricked my mobile after restoring original bootloader.......
QFIL cannot do a thing ..... all the eror i get is unable to go to EDl mode......
nothing for me except download mode and fastboot......
so toook to service centre and got it repaired for free in 2hrs
puli where do u live[emoji14]
Sent from my Redmi Note 3 using XDA-Developers mobile app
Rajdip said:
Have you tested this method yourself? I think this is for people who bricked the device but had stock recovery inside, what about people who has twrp and bricked the device? Also I dont think you can flash anything through fastboot in locked bootloader
Click to expand...
Click to collapse
i've tried this myself. In HS USB 900E you can flash aboot through fastboot whether you stock recovery or twrp before bricked.
Rajdip said:
I have found few ways by which people may unbrick from HS USB 900E state without test point, but those guides are for other devices, needs thorough testing for Redmi note 3.
Tools needed:-
1) QPST http://www.androidbrick.com/downloa...qcn-for-lollipop-android-5-0-6-0-marshmallow/
2)Nubia tool studio https://drive.google.com/folderview?id=0BwtoIMKf470SRUxfdHA5cU14ZTQ#
Now follow these guides for reference,
1)http://www.androidbrick.com/ultimat...ide-snapdragons-are-unbrickable-qhsusb_dload/
2)http://www.androidbrick.com/unbrick...-you-have-the-right-kind-of-rom-qhsusb_dload/
Only people with hardbrick(900E) and locked bootloader can this test methods, Please try and leave your feedback, maybe we will find a way to unbrick without opening the phone and voiding warranty. Good Luck
Click to expand...
Click to collapse
Does anyone success ? Please share a guide !
apixbuanget said:
i've tried this myself. In HS USB 900E you can flash aboot through fastboot whether you stock recovery or twrp before bricked.
Click to expand...
Click to collapse
wow!!! thats great, but before you flashed aboot through fastboot did you check whether your bootloader was locked or not?
Hi, my problem is with the L31,
I've trying to downgrade from Nougat to MM. I saw on the thread this steps and i followed:
"Fastboot flash boot boot.img
Fastboot flash system system.img
Fastboot flash cust cust.img (This one is in the second zip from badwolf nougat download)
Then I flashed badwolfs recovery b2 as that one lets me transfer files from pc to phone and followed instructions from htcmania from here".
The problem is that i didn't reach to downgrade and when i try to reinstall Nougat by TWRP i get this error messages:
" E: Unknow comand (errno) update_huawei-pkg_from_ota_zip: update package from zip failed"
"Updater process ended with error: 7
Error installing zip file '/external_sd/DLoad/Update.zip'
Updating partition details...
...done"
Now my phone stays freeze on the huawei logo and the flashtool doesn't even recognize my device.
Can someone help me with this matter, please?
try to flash stock recovery and do a factory reset
simo255 said:
try to flash stock recovery and do a factory reset
Click to expand...
Click to collapse
Problem solved.:good:
aalmeida1972 said:
Problem solved.:good:
Click to expand...
Click to collapse
how did you flash a stock recovery please ???
darth_us37 said:
how did you flash a stock recovery please ???
Click to expand...
Click to collapse
I followed the steps that someone advice me. Like above.
"I had to first extract the nougat firmware with huawei firmare extractor and flash everything by fastboot
Fastboot flash boot boot.img
Fastboot flash system system.img
Fastboot flash cust cust.img (This one is in the second zip from badwolf nougat download)
Booth files you can find it in this page.
http://forum.xda-developers.com/huawei-p9lite/development/android-nougat-dev-build-huawei-t3488360/page33"
To flash img. i used the file that i attached.
Good luck
so now i restored twrp , i put the update app in sd card and it doesn't want to flash , i'm still trapped in bootloop but i have access to twrp now what to do now ?
I found the old twrp is okey for downgrade,
Just put b161 update.app into sdcard/dload and press volume down + power key.
but flash badwolf's twrp will get stuck in fastboot, though It's not really bricked.
hi, maybe you also have a solution for my problem.
i installed a wrong update via sd card (dload etc.), now my phone is just black no signal nothing. and it seems like a fastboot loop always when i plug into the pc im in fastboot without doing anything
when i try to unlock the bootloader i get "failed command not allowed")
and also when i try to flash the extracted files from update.zip i get the same error ("failed command not allowed")
by the way i didnt active usb debuggin or oem unlocking
please help thank you
Hi,
is it possible to relock the bootloader to original factory mode.
fastboot oem lock (will erase userdata)
Also you should restore the fbop partition: /dev/block/bootdevice/by-name/fbop
For more reference see:
https://forum.xda-developers.com/axon-7/help/lock-unlocked-bootloader-t3444044
https://forum.xda-developers.com/showpost.php?p=68738854&postcount=100
Also please don't open a thread to a question that has already been answered several times.
After i unlocked bootloader my phone now is recognized as A2017U. When i relock it will it then recognized as original A2017G ?
I am interested in a tutorial about going back to stock for G model
The procedure for the g model is no different than the U model except you have to revert the bootloader (fbop partition) because the european model is quite restricted.
For making a tutorial I would need to know exactly what you modified.
There are already good step by step guides in this forum. All I could offer you are my backup files for the recovery and bootloader for the 2017G with update B08.
Bomberus said:
The procedure for the g model is no different than the U model except you have to revert the bootloader (fbop partition) because the european model is quite restricted.
For making a tutorial I would need to know exactly what you modified.
There are already good step by step guides in this forum. All I could offer you are my backup files for the recovery and bootloader for the 2017G with update B08.
Click to expand...
Click to collapse
At the moment i am on B09 rooted but I installed it via TWRP using DrakenFx's tutorial from here : https://forum.xda-developers.com/showpost.php?p=68873485&postcount=3
Futhermore when I unlocked the bootloader I was on B03 and I saved the aboot.img and fbop_lock.img .
Now I would like to go back to fully stock to prepare for the android N update.
I would highly appreciate it if you could offer me some directions for this matter.
Never tried this method (so I take no responsibility) but in order to receive ota you need an unmodified system with locked bootloader.
To lock your bootloader:
First backup all your apps, data and internal sdcard !
Connect your phone to a PC and start adb:
Type: "adb reboot bootloader"
Phone will restart: (if you are on linux, run fastboot with root permission)
Type: "fastboot oem device-info" (just to check things)
"fastboot oem lock" (will lock your bootloader)
According to DrakenFX you should have the stock recovery already installed. So you can flash a sd card upgrade from ZTE "http://www.ztedevice.com/support/detail?id=98CEB24F9FFD433EA99EC424163149A6" (to bring you back to stock)
If you still have TWRP use DrakenFX files to flash your system back to stock, but this time do not flash supersu.
You should be good to go and just have to wait for ZTE to release the update and apply it via the updater UI.
BTW this is my fastboot oem device-info output:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.059s]
finished. total time: 0.059s
Click to expand...
Click to collapse
dodo34 said:
Hi,
is it possible to relock the bootloader to original factory mode.
Click to expand...
Click to collapse
You mind my asking the reason WHY you want to Relock?
If is cuz the N update , I'll rather keep it unlock base on @lokissmile thread and I'm 100% sure I'll be releasing N TWRP Flashable Zips for all variants when N is available.
i have G model and flashed the aboot of the U modell.
How to flash back now the aboot of the G modell back ?
Any help for the G modell ?
dodo34 said:
Any help for the G modell ?
Click to expand...
Click to collapse
as far my understanding the G model have factory images right? just download the one you were using and flash it using custom recovery.
LifeSupportZ said:
as far my understanding the G model have factory images right? just download the one you were using and flash it using custom recovery.
Click to expand...
Click to collapse
@dodo34
This is correct, the full image should be the one that contains both the emmc_appsboot.mbn (this is your aboot or bootloader partition) and the fastboot.img (the fbop or fastboot command partition) as well as recovery.img. This will set everything back to stock in one swoop. Otherwise you have to reflash the signed (tenfars) TWRP to flash back the fastboot image and then falsh back stock, since regular TWRP will either not be there anymore or will not run since BL is locked now
P.S, you can leave the fastboot alone for the purposes of OTA, no update so far hes checked on it and i am not sure if there is a G package with it since it has not changed from release, so as long as the image you flash has the bootloader and recover you should be good for N
P.S.2 Actually I see a little catch 22 here. If you lock the BL first, then you will not be able to run TWRP or boot into system if it was modified. You would need to flash the "signed" version of TWRP or flash stock recovery before locking the BL. Stock would be preferable since it can flash the factory package withouht modifications. If using TWRP i think you have to change updater-script to remove a .... and i just found another catch 22. The updater-script will look for product name P996A04 and if yours shows as 2017U the it will report back P996A01 so you will have to have a signed TWRP on there no matter what. Either to flash the backed up aboot fbop and recovery and then flash the full factory package through stock recovery or mod the updater-script and remove the assert line and flash the whole thing with TWRP. What do you get in TWRP shel when you run this "getprop ro.product.model"
peramikic said:
@dodo34
This is correct, the full image should be the one that contains both the emmc_appsboot.mbn (this is your aboot or bootloader partition) and the fastboot.img (the fbop or fastboot command partition) as well as recovery.img. This will set everything back to stock in one swoop. Otherwise you have to reflash the signed (tenfars) TWRP to flash back the fastboot image and then falsh back stock, since regular TWRP will either not be there anymore or will not run since BL is locked now
P.S, you can leave the fastboot alone for the purposes of OTA, no update so far hes checked on it and i am not sure if there is a G package with it since it has not changed from release, so as long as the image you flash has the bootloader and recover you should be good for N
P.S.2 Actually I see a little catch 22 here. If you lock the BL first, then you will not be able to run TWRP or boot into system if it was modified. You would need to flash the "signed" version of TWRP or flash stock recovery before locking the BL. Stock would be preferable since it can flash the factory package withouht modifications. If using TWRP i think you have to change updater-script to remove a .... and i just found another catch 22. The updater-script will look for product name P996A04 and if yours shows as 2017U the it will report back P996A01 so you will have to have a signed TWRP on there no matter what. Either to flash the backed up aboot fbop and recovery and then flash the full factory package through stock recovery or mod the updater-script and remove the assert line and flash the whole thing with TWRP. What do you get in TWRP shel when you run this "getprop ro.product.model"
Click to expand...
Click to collapse
if he mod the updater_script from official zte update to make it flash friendly, this is what i'll do,
* Mod updater script and remove aboot and recovery for now
* flash new zip without file mention above
* boot to bootloader while having custom recovery
* lock back the bootloader
* boot to custom recovery and perform " format data "
* create a flashable zip with stock aboot and recovery
* flash new zip with aboot and recovery
* reboot to recovery and check if boot to stock recovery and while in there perform a factory reset
i know is a lot of steps but, seems like is the way to go to get everything back in place without zte noticing anything.
Now i am on B06.
I put update.zip B08 and select update. But it boots to TWRP recovery and update fails.
@dodo34 If you are trying to restore from the OS system update you need to reflash your stock recovery for it to work properly. Wait for someone to confirm what I just said, but that's how it worked for me.
how can i flash my original recovery. what is the command for cmd ?
Please help restoring back original recovery.
dodo34 said:
Please help restoring back original recovery.
Click to expand...
Click to collapse
rczrider said:
Putting Your Axon 7 Back to Stock
If you want to revert back to stock and re-lock your bootloader (eg. sending the phone in for warranty work or are selling it), you should be able to do that using the steps below. It worked for me, anyway, exactly as written below.
Copy everything off your internal storage that you don't want to lose. If you're not rooted (so already stock, but with unlocked bootloader), skip to step 6 below. Otherwise, continue.
Grab the "StockSystem" zip for your variant from this thread and place on your microSD card: http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Reboot into TWRP and wipe system, data, dalvik, and cache
Flash the StockSystem zip and power off (doing so will restore stock boot but does not appear to restore recovery)
Boot into EDL mode and flash stock recovery only: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Power off the phone, plug from computer, and then boot into stock recovery (hold Vol+ and press Pwr, continue holding Vol+ until recovery comes up)
Select "Wipe data / factory reset" and then "Yes"
After that finishes, select "Reboot to bootloader"
Plug in your phone into your computer and do: fastboot oem lock (see second post if this doesn't work and says <waiting for device>)
Your phone will reboot and should have been totally wiped (including internal storage) by doing the above
This should leave you with a stock, locked, and unrooted phone that can take OTAs. Note: it's possible (in fact, likely) that an OTA could break the ability to unlock your bootloader and gain root again, so be careful about going back to stock if you think you'll want to unlock/root later on!
If you need any stock files for B20 or B27 (stock recovery for re-locking, for example), you can get them here: http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
Click to expand...
Click to collapse
Try this guide from newbie unlock thread.
I get this error.
C:\Users\Intel\Downloads\Axon7\ADB>axon7tool -r
Usage:
axon7tool -r <boot|recovery|gpt> ...
axon7tool -w <boot|recovery>
C:\Users\Intel\Downloads\Axon7\ADB>axon7tool -r recovery
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
what i did.
Flashed Draken TWRP System Image B06
Flashed Draken TWRP Stcok Recovery B06
Flashed full update.zip B08
Now my phone is recognized as A2017G on the PC
But when i reboot the phone i get a message that the phone is unlocked and not trusted ?
why ?
Hello, good day. I just wanted to ask, (Im using custom rom now and my old backup is nowhere to be found) If I am going to flash my device to official stock rom, like if I flashed the older version (lets say the MM) can I still update my device today (up to nougat) through OTA update?
i think huawei cloud is the site where we download OTA updates from but I think is already dead.
(sorry if my poiint is confusing, I just really don't know how to explain it clearly)
emmanueldlauron said:
Hello, good day. I just wanted to ask, (Im using custom rom now and my old backup is nowhere to be found) If I am going to flash my device to official stock rom, like if I flashed the older version (lets say the MM) can I still update my device today (up to nougat) through OTA update?
i think huawei cloud is the site where we download OTA updates from but I think is already dead.
(sorry if my poiint is confusing, I just really don't know how to explain it clearly)
Click to expand...
Click to collapse
Hi,
in fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
and post results.
thanks for resonding
(bootloader) :Elite ROM v7.7
(bootloader) HUAWEI VNS-L31
vendorcountry: hw/spcseas
FAILED (remote: 'invalid command')
emmanueldlauron said:
thanks for resonding
(bootloader) :Elite ROM v7.7
(bootloader) HUAWEI VNS-L31
vendorcountry: hw/spcseas
FAILED (remote: 'invalid command')
Click to expand...
Click to collapse
Okay, last question - single SIM or dual SIM?
Dual Sim
emmanueldlauron said:
flash my device to official stock rom
Click to expand...
Click to collapse
So if I not mistaken, your build number is VNS-L31C185 EMUI 5 (correct me if I'm wrong).
Firmware finder and Huawei old server are down, so download service ROM.
IMO now you have two possibilities:
A) flash Service ROM using dload method, guide can be found in ReleaseDoc folder. The process will erase all your data and lock the BL again!
B)
- from downloaded ROM extract BOOT.img
RECOVERY.img
SYSTEM.img
CUST.img via 'Huawei update extractor' , follow Guide
(Note: CUST.img on Nougat can be found in the second archive)
- In fastboot mode flash extracted partitions using commands
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
- fastboot reboot
- Factory reset in stock recovery
-Alf- said:
So if I not mistaken, your build number is VNS-L31C185 EMUI 5 (correct me if I'm wrong).
Firmware finder and Huawei old server are down, so download Service ROM
IMO now you have two possibilities:
A) flash Service ROM using dload method, guide can be found in ReleaseDoc folder. The process will erase all your data and lock the BL again!
B)
- from downloaded ROM extract BOOT.img
RECOVERY.img
SYSTEM.img
CUST.img via 'Huawei update extractor' , follow Guide
(Note: CUST.img on Nougat can be found in the second archive)
- In fastboot mode flash extracted partitions using commands
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
- fastboot reboot
- Factory reset in stock recovery
Click to expand...
Click to collapse
I don't have sd card on me right now. is there any way I can flash service rom without sd card?
Edit: and also this device is C636xxx.
neverming the first paragraph I said. I'm confused with CUST.img thing, I donwloaded the C635 update but there's no second archive on what I had downloaded
emmanueldlauron said:
flash service rom without sd card?
Click to expand...
Click to collapse
Nope.
emmanueldlauron said:
this device is C636xxx.
Click to expand...
Click to collapse
Okay, then download C636
-Alf- said:
Nope.
Okay, then download C636
Click to expand...
Click to collapse
Thanks for the tips and ideas, I somehow understand something new today.
emmanueldlauron said:
there's no second archive on what I had downloaded
Click to expand...
Click to collapse
VNS-L31_hw_xxxxx
-Alf- said:
VNS-L31_hw_meafnaf
Click to expand...
Click to collapse
Oh yeah. I just figured it out but had to rename that to update.app so update extractor can accept the file. Thanks by the way.
for now SYSTEM and CUST takes time to finish extracting.
-Alf- said:
So if I not mistaken, your build number is VNS-L31C185 EMUI 5 (correct me if I'm wrong).
Firmware finder and Huawei old server are down, so download service ROM.
IMO now you have two possibilities:
A) flash Service ROM using dload method, guide can be found in ReleaseDoc folder. The process will erase all your data and lock the BL again!
B)
- from downloaded ROM extract BOOT.img
RECOVERY.img
SYSTEM.img
CUST.img via 'Huawei update extractor' , follow Guide
(Note: CUST.img on Nougat can be found in the second archive)
- In fastboot mode flash extracted partitions using commands
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
- fastboot reboot
- Factory reset in stock recovery
Click to expand...
Click to collapse
UPDATE: I did the B. they're all finished without any errors, but I ended with bootloop, like I can't go to recovery and when I tried to it vibrates twice and show nothing but just the huawei logo with "powered by android" texts.
emmanueldlauron said:
UPDATE: I did the B. they're all finished without any errors, but I ended with bootloop, like I can't go to recovery and when I tried to it vibrates twice and show nothing but just the huawei logo with "powered by android" texts.
Click to expand...
Click to collapse
Try command
fastboot erase userdata
and reboot.
Check your current build number etc.
https://forum.xda-developers.com/t/stock-rom-to-update-in-2021.4320501/post-85489493
-Alf- said:
Try command
fastboot erase userdata
and reboot.
Check your current build number etc.
https://forum.xda-developers.com/t/stock-rom-to-update-in-2021.4320501/post-85489493
Click to expand...
Click to collapse
emmanueldlauron said:
(bootloader) :Elite ROM v7.7
(bootloader) HUAWEI VNS-L31
vendorcountry: hw/spcseas
FAILED (remote: 'invalid command')
Click to expand...
Click to collapse
still the same with these
emmanueldlauron said:
still the same with these
Click to expand...
Click to collapse
Bro try this way out...
Download and install TWRP (if possible) and let me know
Upd.: nevermind, I forgot you don't have an sd card,.
Upd.2.: without SD you can try to flash Service ROM (or B361 firmware) using TWRP and sideload method. Unfortunately, sideload is Greek to me , so google it.
-Alf- said:
Bro try this way out...
Download and install TWRP (if possible) and let me know
Upd.: nevermind, I forgot you don't have an sd card,.
Upd.2.: without SD you can try to flash Service ROM (or B361 firmware) using TWRP and sideload method. Unfortunately, sideload is Greek to me , so google it.
B361 firmware is a fullOTA-MF-PV version, download and instructions here
Click to expand...
Click to collapse
I can still go fastboot mode and install everything without any errors but I don't why, it confuses me that let say I just flashed recovery (custom or stock) but when I'm going to access it (volume up + power button) phone just vibrates twice but nothing will happen.
emmanueldlauron said:
I can still go fastboot mode and install everything without any errors but I don't why, it confuses me that let say I just flashed recovery (custom or stock) but when I'm going to access it (volume up + power button) phone just vibrates twice but nothing will happen.
Click to expand...
Click to collapse
Flash TWRP over eRecovery, run command
fastboot flash recovery2 twrp.img
fastboot reboot
when a yellow warning appears on the screen, pres and hold Vol Up for 3 sec.
Edit: maybe your data partition is formatted with f2fs (after installing Elite ROM) , it should be ext4. I'm out of ideas bro, sorry.
-Alf- said:
Flash TWRP over eRecovery, run command
fastboot flash recovery2 twrp.img
fastboot reboot
when a yellow warning appears on the screen, pres and hold Vol Up for 3 sec.
Edit: maybe your data partition is formatted with f2fs (after installing Elite ROM) , it should be ext4. I'm out of ideas bro, sorry.
Click to expand...
Click to collapse
No problem. I think I hard bricked my phone, I just got boot logo and fastboot but I can't find any fix or solution or anything to do with this.
Flashing recovery or recovery2 finished w/o any errors but I can't boot to recovery.
Thanks for your help by the way. I appreciate it! Kudos and have a nice day. Keep safe.
emmanueldlauron said:
I think I hard bricked my phone,
Click to expand...
Click to collapse
IMO you only need an SD card and flash the Service ROM.