Database Users

Failed to boot 4

Hi guys after having upgraded my AT & T Motorola Atrix gingerbread to version 1.83 I get this error: failed to boot 4.
how do I reset the phone? thanks

Flas sbf. Look in development for flashing sbfs. Tons of information. Also wrong section this should be under questions and answers section.
Sent from my MB860 using Tapatalk

Flash either full 4.1.26 or 4.1.57 sbf, then update OTA to 4.1.83.
And what do you mean Gingerbread?
Unless you flashed to 2.3.4 HKTW you don't have Gingerbread.

CaelanT said:
And what do you mean Gingerbread?
Unless you flashed to 2.3.4 HKTW you don't have Gingerbread.
Click to expand...
Click to collapse
commonsense suggests that, that's what he means.
Sent from rooted Atrix on 2.3.4 with unlocked bootloader using xda premium app.

alexrita said:
Hi guys after having upgraded my AT & T Motorola Atrix gingerbread to version 1.83 I get this error: failed to boot 4.
how do I reset the phone? thanks
Click to expand...
Click to collapse
Failed to boot 4
me too,help!!!

help!!!
help!!!
help!!!

veafin said:
Failed to boot 4
me too,help!!!
Click to expand...
Click to collapse
What did you flash, and how? Is your phone unlocked?
I suspect "Failed to boot 4" is when a filesystem is missing a signature. (And "2" is when the signed hash doesn't match the data)
If you are using RSD and a Motorola .sbf, shouldn't be a problem. Please explain in detail what you have done. If you want a quick fix, after flashing 4.1.83 SBF, if you still have this problem, go back and flash The2d's PUDDING (unlocked BL.)
(This fix will only work if you have unlocked your phone.. but the only way you could get this error is if you are trying to use fastboot without first unlocking your phone, or you are manually editing boot/recovery, or making .sbf files yourself...)
Please provide clear, concise details of what you've done.

eval is right, I got both failed to boot 4 and 2 in the past
if you have an att atrix you just need to flash 1.2.6 sbf then the 1.8.3 over it, unclok your bootloader then flashboot will go.

My cell phone is Hong Kong release, flashed Chinese simplified ROM,"掘墓者ME860国行官方ROM_OLYGC_U4_1.21.0.DearTanker"
when the tip is：
SVF:105:1:2
Failed to boot 0x1000
can't get the "RSD" and "fast boot"mode.
What can I do?

Same here...got "Failed to boot 4" error...
I had leaked 2.3.4 HKTW installed
I was trying to move back to 2.2...Keep getting errors when flashing to 1.2.6 as well...failing at the step where it says "Switching the device to BP mode"....Please help....

Hi,
I got that error when I had an sbf flashed and then I flashed a system.img from another firmware. Such a mismatch would also occur if an sbf was interrupted.
Cheers!

veafin said:
My cell phone is Hong Kong release, flashed Chinese simplified ROM,"掘墓者ME860国行官方ROM_OLYGC_U4_1.21.0.DearTanker"
when the tip is：
SVF:105:1:2
Failed to boot 0x1000
can't get the "RSD" and "fast boot"mode.
What can I do?
Click to expand...
Click to collapse
You cannot boot into RSD by holding volume-up on start?
We are lucky, when our phones fail signature/hash check, we are dropped directly into RSD mode. This seems not to be the case for you. Also, this message "Failed to boot 0x1000" is new to me, and so far seems only to have happened to ME860 users. I suspect fastboot gets the kernel (or something else?) loaded into memory at 0x1000, see:
Code:
000D173C .Unrecoverable bootloader error (
000D1760 [Fastboot]: Fastboot Entry
000D1784 Point ..Failed to boot 0x1000..LOG.
in bootloader CG from an extracted SBF. But... fails to boot kernel/microBoot? Hard to understand how a signed CG, which passed the check for your Boot ROM (same encryption keys) can have a kernel/? that does not boot on your hardware. Unless Moto has used similar keys with some hardware changes that means that .sbfs from international ROMs are not purely interchangeable? =(
And this is strange, since fastboot gives this error, so it is alive and in memory, should take some input: hopefully booting power-on + volume-down would be enough to get the menu of options, which includes RSD, same for booting power-on+volume-up key ? The inability to get into any fastboot / RSD menu looks like it could be a serious Moto bug... I hope whoever posted that SBF puts a huge WARNING for users of your model of phone...

I forgot to ask the 0x1000 people...
During any point during boot, does the device show up in usb? Command "watch -n .2 lsusb" in linux would do..

Thank bro…. I’ve try this way “As the devices is booting hold the volume up button”
But it is no use … the device is continue booting … again and again…
If it is work … at the top of the screen will show “strating RSD protocol ….”
But now my atrix didn’t show anything ..
And the screen won’t show any MOTO’s logo….
Does anyone can help me to save my atrix ?? > <
Please …
Look here,Please:http://forum.xda-developers.com/showthread.php?p=14673911

Again, do you ever see it appear on usb? In linux
# watch -n .1 lsusb
and keep your eyes open for Motorola PCS
That is your only hope... if we cannot even communicate with the phone via usb, well, it is pretty much a hard-brick.
Who made this [email protected]! Others are OK with it??
veafin said:
Thank bro…. I’ve try this way “As the devices is booting hold the volume up button”
But it is no use … the device is continue booting … again and again…
If it is work … at the top of the screen will show “strating RSD protocol ….”
But now my atrix didn’t show anything ..
And the screen won’t show any MOTO’s logo….
Does anyone can help me to save my atrix ?? > <
Please …
Look here,Please:http://forum.xda-developers.com/showthread.php?p=14673911
Click to expand...
Click to collapse

[SOLVED] how to rescue? "boot verified failed" "recovery verified failed"

[SOLVED] how to rescue? "boot verified failed" "recovery verified failed"
Edit: Solved - searched through bazillions of threads -- just about all of them referenced Timmy Dean threads
1) http://forum.xda-developers.com/showpost.php?p=20654298&postcount=129
2) http://forum.xda-developers.com/showthread.php?t=1307539
Attempts to run PBJ20upgrade.exe after getting into APX mode were failing me with invalid CPUID.
Of course when you can't boot, or get to recovery, there's basically NO WAY to get your CPUID. The number provided by using usbdview is NOT the CPUID; it's the serial number aka the same serial number on the sdcard cover.
Thankfully, some months ago I saved the CPUID / UID in a notepad doc on another machine. Grabbed that number, popped it in when PBJ20upgrade.exe prompted and the device is now recovered.
Will look into ICS upgrades again after the teeth heal up... need rest now.
--------------------------------------------------------------
Context: had my wisdom teeth pulled so I'm a bit medicated; not sure what I did in trying to do an ICS upgrade, but I seem to have hosed my tablet for sure. Didn't realize a tablet counts as heavy machinery. ;-)
Power on shows "boot verified failed" in red; attempting to boot recovery with the vol- shows "recovery verified failed" in red.
-I cannot boot straight nor can I get into recovery.
+The tablet supposedly IS able to get into APX mode, though.
+I have my UID and SBK saved on my desktop in a text file for use as needed.
I have tried using BlackThund3r's APX Flash tool with the EUUs_SBK_Acer_A500_1.016.05_COM_GEN1.a500apx package to no avail (the flash tool recognizes the tablet as an APX device once in APX mode, but each of the writes seems to fail).
What else can I try?
The few search results for anyone that has experienced both errors were for people that were within warranty that sent it back to Acer... well, I'm out of warranty.

so did any of our info in your other thread help?

chismay said:
so did any of our info in your other thread help?
Click to expand...
Click to collapse
huh?

vprasad1 said:
huh?
Click to expand...
Click to collapse
oh damn srry matey mutli-window posting wrecked me earlier :S

Bricked A500

So, my A500 seemingly died - it is stuck on Acer logo screen, none of the tools seem to work - I made it all the way from soft reset to babsector which pops out with write error. I assume it means that my motherboard is fried. Any advice on the best way to procure a replacement? Is it even worth it? Perhaps I am better off just dumping it and replacing it with something more modern?

tornadolf said:
So, my A500 seemingly died - it is stuck on Acer logo screen, none of the tools seem to work - I made it all the way from soft reset to babsector which pops out with write error. I assume it means that my motherboard is fried. Any advice on the best way to procure a replacement? Is it even worth it? Perhaps I am better off just dumping it and replacing it with something more modern?
Click to expand...
Click to collapse
Difficult to advise you
Please post:
1. the write error you got
2. what ROM and boot loader u were on.
3. What tools 'didn't work'?
Sent from my GT-I9300 using Tapatalk 4 Beta

dibb_nz said:
Difficult to advise you
Please post:
1. the write error you got
2. what ROM and boot loader u were on.
3. What tools 'didn't work'?
Click to expand...
Click to collapse
Thanks
1. I've got Acer logo screen
2. I was on rooted stock 4.0.3 and I assume it means ICS bootloader
3. Here's what I tried: both resets -> update.zip metod -> extract CPUID/get SBK -> Timmy's tool (gets stuck at 10%) -> APX flashtool (gets stuck at stage two) -> babsector (reports an error - command 12 iirc)

[Q] Iconia500 shows white power light but no screen or vibrate

My old charger for the Iconia 500 broke and I got a replacement charger (not acer). When it came the iconia was already completely drained. I plugged it in, charged it, and since then the only thing that happens is this:
- I push power and after about 3s it turns white. Nothing happens on the screen, no vibration, nothing.
- I can turn the power back off by holding the button for 5s.
> I have tried holding the button longer but no difference.
> From what I have read I suspect it might somehow have gotten into APX mode?
> I have tried to read through the numerous posts on this forum but cannot quite find this same problem/am overwhelmed by the lingo.
> I have tried to connect the tablet to my PC with a microSD cable, and it lists it as APX, category unknown, APX doesn't have a driver
- Can anyone confirm/suggest what might be wrong with my tablet?
- Is this something that can be fixed at a repair shop?
- Is this something I could fix? (I have no ID's or codes for the tablet, have never played with APX mode before)
Thank you for any advice!
- Chris

CKM80 said:
My old charger for the Iconia 500 broke and I got a replacement charger (not acer). When it came the iconia was already completely drained. I plugged it in, charged it, and since then the only thing that happens is this:
- I push power and after about 3s it turns white. Nothing happens on the screen, no vibration, nothing.
- I can turn the power back off by holding the button for 5s.
> I have tried holding the button longer but no difference.
> From what I have read I suspect it might somehow have gotten into APX mode?
> I have tried to read through the numerous posts on this forum but cannot quite find this same problem/am overwhelmed by the lingo.
> I have tried to connect the tablet to my PC with a microSD cable, and it lists it as APX, category unknown, APX doesn't have a driver
- Can anyone confirm/suggest what might be wrong with my tablet?
- Is this something that can be fixed at a repair shop?
- Is this something I could fix? (I have no ID's or codes for the tablet, have never played with APX mode before)
Thank you for any advice!
- Chris
Click to expand...
Click to collapse
Hi chris, yes you are stuck in apx mode.
To fix this you must have your tabs CPUID.
The easiest way is from an old nandroid backup, thats if you have one. If you do, look in the cwm backup folder under cpuid.txt
If you dont have a backup, your only chance is thru ubuntu. There is a guide by "srbeen" stickied in the General forum.
If you can retrieve yr cpuid, post back here and we can help u get fixed. YoU will need anutha file to do this tho'. Its called babsector.rar and you can download it in post 2 in the root guide in my sig.
You will also need a rom to flash - only ICS or JB.
To summarise,
1. Retrieve the cpuid/sbk
2. Once you have that then
3. Download babsector and a rom.
4. Come back here for unbricking help.
Good luck with the cpuid/sbk, without it you can do nothing.
dibb

Thanks for your reply and your advice! It is nice to have the confirmation about what the problem is, and a step by step guide to start tackling it. I feel a bit less lost now I'm going to try to follow your steps and will let you know if I get stuck anywhere.
- Chris

next steps?
Ok, so somehow (a miracle I guess) I managed to do your steps:
- installed ubuntu
- followed srbeen's steps upto the point where I got my CPUID
- got my SBK
- downloaded babsector.rar (luckily chrome offered to translate the russian site I found it at)
- unrarred it
- downloaded a ROM from http://forum.xda-developers.com/showthread.php?t=1935582 (is this an appropriate ROM?)
- unzipped the ROM and copied it to the external micro SD card
Can you point me in the right directions for the next steps?
Thanks,
Chris
dibb_nz said:
Hi chris, yes you are stuck in apx mode.
To fix this you must have your tabs CPUID.
The easiest way is from an old nandroid backup, thats if you have one. If you do, look in the cwm backup folder under cpuid.txt
If you dont have a backup, your only chance is thru ubuntu. There is a guide by "srbeen" stickied in the General forum.
If you can retrieve yr cpuid, post back here and we can help u get fixed. YoU will need anutha file to do this tho'. Its called babsector.rar and you can download it in post 2 in the root guide in my sig.
You will also need a rom to flash - only ICS or JB.
To summarise,
1. Retrieve the cpuid/sbk
2. Once you have that then
3. Download babsector and a rom.
4. Come back here for unbricking help.
Good luck with the cpuid/sbk, without it you can do nothing.
dibb
Click to expand...
Click to collapse

Next steps?
Hi dibb_nz (and others)
I am still stuck. I have been trying several things, but none worked so far.
- I think the drivers are installed properly. When I go to device manager it lists APX under unspecified device - with Acer USB Boot recovery Driver installed under the hardware tab. It also says Model: APX, Category: Unknown
- I tried to run babsector, and it gives me an error. Before giving me the error it does get my tablet to show the text "Entering Acer Download Mode" in the topleft corner. Then I get the error "failed executing command 16 NvError 0x120002, command failure: create failed (bad data)" in the attached image.
- I also tried to follow the steps in Timmy Dean's V4 post, since I hoped maybe that would help, but that also gave me an error. (Red letters saying it failed, and to follow the steps again and try again).
I feel once more defeated, and hope you know what to do next.
- Chris
dibb_nz said:
Hi chris, yes you are stuck in apx mode.
To fix this you must have your tabs CPUID.
The easiest way is from an old nandroid backup, thats if you have one. If you do, look in the cwm backup folder under cpuid.txt
If you dont have a backup, your only chance is thru ubuntu. There is a guide by "srbeen" stickied in the General forum.
If you can retrieve yr cpuid, post back here and we can help u get fixed. YoU will need anutha file to do this tho'. Its called babsector.rar and you can download it in post 2 in the root guide in my sig.
You will also need a rom to flash - only ICS or JB.
To summarise,
1. Retrieve the cpuid/sbk
2. Once you have that then
3. Download babsector and a rom.
4. Come back here for unbricking help.
Good luck with the cpuid/sbk, without it you can do nothing.
dibb
Click to expand...
Click to collapse

CKM80 said:
Hi dibb_nz (and others)
I am still stuck. I have been trying several things, but none worked so far.
- I think the drivers are installed properly. When I go to device manager it lists APX under unspecified device - with Acer USB Boot recovery Driver installed under the hardware tab. It also says Model: APX, Category: Unknown
- I tried to run babsector, and it gives me an error. Before giving me the error it does get my tablet to show the text "Entering Acer Download Mode" in the topleft corner. Then I get the error "failed executing command 16 NvError 0x120002, command failure: create failed (bad data)" in the attached image.
- I also tried to follow the steps in Timmy Dean's V4 post, since I hoped maybe that would help, but that also gave me an error. (Red letters saying it failed, and to follow the steps again and try again).
I feel once more defeated, and hope you know what to do next.
- Chris
Click to expand...
Click to collapse
OK< there is a slim chance u may be able to recover your tab.
There is a bct error - usually only one tool can repair this.
Download the apxflash tool.
Power your tab off.
Enter apx mode via the buttons - DO NOT use the tool to do this -
Connect your usb cable.
Run the tool - choose to go to the bundle market and download bundle 17.
If the apx driver has loaded and is showing in device manager then continue with the apx flash tool -
You will eventually see a window asking whether to dump and save yr bct, choose yes.
Hopefully the tool will carry on with the flash, once thats done, boot straight to recovery, complete the wipes and formats and then flash your rom.

I have done the steps below.
Just to make sure, when you are talking about the APX drivers being loaded, do you mean the one I see when I go to devices, right click on APX, choose hardware, where it says "ACER USB Boot-recovery driver" under device functions?
So when I tried to dump my own it gave me the following error (attached as image):
Unhandled exception, could not find file bct.dec.
It gave me the option to try to continue anyway, which I tried, but now it has been hanging in the screen "staging and backing up BCT, Using default BCT" for a long time...
so, does this mean it really is dead? And if so, what part of the tablet is dead? And if not (*hope*), then what else can I try?
Thanks,
Chris
ps. my tablet was never rooted, so I don't know if that complicates the matter... it does say that it needs to have been rooted to choose the dump option. Moreover, I never was able to turn USB debugging on, because I don't have access to the tablet. It does nothing besides black screen and occasionally the "Enter download mode" (but not with these steps)
dibb_nz said:
OK< there is a slim chance u may be able to recover your tab.
There is a bct error - usually only one tool can repair this.
Download the apxflash tool.
Power your tab off.
Enter apx mode via the buttons - DO NOT use the tool to do this -
Connect your usb cable.
Run the tool - choose to go to the bundle market and download bundle 17.
If the apx driver has loaded and is showing in device manager then continue with the apx flash tool -
You will eventually see a window asking whether to dump and save yr bct, choose yes.
Hopefully the tool will carry on with the flash, once thats done, boot straight to recovery, complete the wipes and formats and then flash your rom.
Click to expand...
Click to collapse

CKM80 said:
I have done the steps below.
Just to make sure, when you are talking about the APX drivers being loaded, do you mean the one I see when I go to devices, right click on APX, choose hardware, where it says "ACER USB Boot-recovery driver" under device functions?
Click to expand...
Click to collapse
yep thats correct
So when I tried to dump my own it gave me the following error (attached as image):
Unhandled exception, could not find file bct.dec.
It gave me the option to try to continue anyway, which I tried, but now it has been hanging in the screen "staging and backing up BCT, Using default BCT" for a long time...
Click to expand...
Click to collapse
Do you have the latest version of the apxflash tool....as far as I know, this is the ONLY way to fix a bct error....
So if you try and save yr tabs bct but you get the error and if u try to continue it just hangs???
The only thing I can suggest now is to power off both devices and then power on. When u get to the bct option try the default option first if it still hangs, power everything down again and this time try saving the bct again. Not much help I'm afraid, sometimes the tools do get stuck, and its best to power down and try again.
so, does this mean it really is dead? And if so, what part of the tablet is dead? And if not (*hope*), then what else can I try?
Click to expand...
Click to collapse
I hope not!! If the tool insists on hanging, you can TRY the babsector file, post an error if you get one. Its in the root guide in my sig, along with instructions for use
good luck
dibb
EDIT: Added attachment apxFlash Tool v1.1.1 @CKM80

Well, I am trying to again with the default option, but it has been saying "Flashing bootloader (EBT) stage two - uploading image" for 45 minutes now, while another nvflash.exe window that popped up says "nvflash started, [resume mode]"
The tablet says "Acer Iconia APX mode" in the topleft.
I am not sure if it is doing something still (after 45 min) or that it is hanging.
I will let it sit a while longer, and if it doesn't work I will try all options again.
Will keep you posted.
Chris
dibb_nz said:
yep thats correct
Do you have the latest version of the apxflash tool....as far as I know, this is the ONLY way to fix a bct error....
So if you try and save yr tabs bct but you get the error and if u try to continue it just hangs???
The only thing I can suggest now is to power off both devices and then power on. When u get to the bct option try the default option first if it still hangs, power everything down again and this time try saving the bct again. Not much help I'm afraid, sometimes the tools do get stuck, and its best to power down and try again.
I hope not!! If the tool insists on hanging, you can TRY the babsector file, post an error if you get one. Its in the root guide in my sig, along with instructions for use
good luck
dibb
EDIT: Added attachment apxFlash Tool v1.1.1 @CKM80
Click to expand...
Click to collapse

CKM80 said:
Well, I am trying to again with the default option, but it has been saying "Flashing bootloader (EBT) stage two - uploading image" for 45 minutes now, while another nvflash.exe window that popped up says "nvflash started, [resume mode]"
The tablet says "Acer Iconia APX mode" in the topleft.
I am not sure if it is doing something still (after 45 min) or that it is hanging.
I will let it sit a while longer, and if it doesn't work I will try all options again.
Will keep you posted.
Chris
Click to expand...
Click to collapse
sorry m8, missed your post...did u try the flash tool version i posted??
Have u tried the babsector file??? I'd be tempted to run that but from what you have said its sounding like a hardware failure....babsector will tell you tho
Hang in there and hopefullly we can have it resolved one way or another!
dibb

Hi Dibb_nz,
I did try... the flashing never worked, always stopped.
Babsector gave the attached error,
Chris
dibb_nz said:
sorry m8, missed your post...did u try the flash tool version i posted??
Have u tried the babsector file??? I'd be tempted to run that but from what you have said its sounding like a hardware failure....babsector will tell you tho
Hang in there and hopefullly we can have it resolved one way or another!
dibb
Click to expand...
Click to collapse

CKM80 said:
Hi Dibb_nz,
I did try... the flashing never worked, always stopped.
Babsector gave the attached error,
Chris
Click to expand...
Click to collapse
oh right. the bct thing...thats a bumma m8, wish I could suggest something for ya, but my bag of tricks is empty
All I can tell u is that 'sometimes' after trying wot seems everything a hundred tries or more, something finally happens and it works...this doesn't mean you do not have a faulty memory chip, as this is just what happens...you could try it next week and it may well work....no consolation I know...
You might wanna try a friends computer (specially if they do not have win8!!) you neva know yr luck!!

Yeah, I think I'll try a couple of times, but I am pretty much ready to give up.
Thanks for all your tips along the way.
- Chris
dibb_nz said:
oh right. the bct thing...thats a bumma m8, wish I could suggest something for ya, but my bag of tricks is empty
All I can tell u is that 'sometimes' after trying wot seems everything a hundred tries or more, something finally happens and it works...this doesn't mean you do not have a faulty memory chip, as this is just what happens...you could try it next week and it may well work....no consolation I know...
You might wanna try a friends computer (specially if they do not have win8!!) you neva know yr luck!!
Click to expand...
Click to collapse

Phone Bricked. PLEASE HELP

I will try to explain everything from the beginning. I was about to install a custom rom install (it was in 7.1.1 stock, unlocked bootloader) so when I was going to do full wipe with lastest TWRP there was an error. Wait for about 15 minutes just in case, but nothing happened so I decided to restart it to try again. But the phone stuck in the ZTE logo and if it tried to enter TWRP was stuck in the logo too, I tried with all versions of TWRP and no one works. Find a post that said I could use TWRP tenfars tool to recover my phone and had to enter the EDL mode. I managed to put the phone in edl mode but now I can not get out of it. I press and hold the power button for a minute and nothing happens (no vibration, no led, no ZTE logo) my pc just does the unplug windows sound. My pc recognizes the phone as QUSB_BULK. When I try to use the tenfars tool I get this message:
C:\Users\Alejandro Saavedra\Downloads\minimal_adb_fastboot_1.4.1_portable>axon7tool -w 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.
Also try using the xiaomi MiFlash tool (even change the drivers from QUSB_BULK to COM COM 5) but something similar happens, also tells me can not recive hello package.
I'm a little new to this so I beg you a little patience
Please work very hard to buy this phone, there has to be some way to unbrick it. :crying:
If you need any additional information just tell me

If you use axon7tool :
check in Devices Manager if is called QLIBSD.
rename recovery.img to recovery.bin.
If you use MiFlash :
get latest version : https://www.androidfilehost.com/?fid=673368273298954241
check in Devices Manager if is called Qualcomm 8004.

CelesteBlue said:
check in Devices Manager if is called QLIBSD.
rename recovery.img to recovery.bin.
Click to expand...
Click to collapse
You need two files, recovery.img and recovery.bin in same folder. (Don't forget to unzip tenfars TWRP and after that rename and make a copy)
Please read: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Best regards
Smedslund

Smedslund said:
You need two files, recovery.img and recovery.bin in same folder. (Don't forget to unzip tenfars TWRP and after that rename and make a copy)
Please read: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Best regards
Smedslund
Click to expand...
Click to collapse
anyway :
https://ab-exclusive.us/fileserver/uploads/twrp_rec_tenfar.zip
404 Not Found...
To flash a recovery file (STOCK or TWRP) with axon7tool, the file has to be called recovery.bin.

CelesteBlue said:
anyway :
https://ab-exclusive.us/fileserver/uploads/twrp_rec_tenfar.zip
404 Not Found...
To flash a recovery file (STOCK or TWRP) with axon7tool, the file has to be called recovery.bin.
Click to expand...
Click to collapse
You will find tenfar 3.0.2-2 TWRP at download center:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Once unzipped, copy it to recovery.bin:
copy twrp_rec_tenfar.img recovery.bin

Thanks to everyone for your answers, I was able to recover my phone using miflash, qualcom usb drivers and this ROM https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip I put my phone in EDL mode and then flash the mentioned rom. It took me like 20-30 tries to finally get it. The last attempt I made was to unplug the device from the computer, I kept the power button for 10 seconds and connect it to the computer without ever releasing the power button. It was seen as always (black screen, not led) but for some reason this time works. I hope everyone can solve this problem. Can pm me if you need help, maybe i can help with something

ale0796 said:
Thanks to everyone for your answers, I was able to recover my phone using miflash, qualcom usb drivers and this ROM https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip I put my phone in EDL mode and then flash the mentioned rom. It took me like 20-30 tries to finally get it. The last attempt I made was to unplug the device from the computer, I kept the power button for 10 seconds and connect it to the computer without ever releasing the power button. It was seen as always (black screen, not led) but for some reason this time works. I hope everyone can solve this problem. Can pm me if you need help, maybe i can help with something
Click to expand...
Click to collapse
That's because you reset the EDL that way. the method is weird but seemed to work...
If you hold the 3 buttons for ~10 secs while the device is in EDL it will reset it

@Choose an username... I am out of context, but I wonder if I can remove the ugly message on each startup telling it can't check if the device is not corrupted... I think this message is caused by the unlocked bootloader. A solution ? Thank you.

CelesteBlue said:
@Choose an username... I am out of context, but I wonder if I can remove the ugly message on each startup telling it can't check if the device is not corrupted... I think this message is caused by the unlocked bootloader. A solution ? Thank you.
Click to expand...
Click to collapse
Actually, it is a nice feature for the few seconds it lasts, but read HERE if you must. Be careful!
Good luck

CelesteBlue said:
@Choose an username... I am out of context, but I wonder if I can remove the ugly message on each startup telling it can't check if the device is not corrupted... I think this message is caused by the unlocked bootloader. A solution ? Thank you.
Click to expand...
Click to collapse
I'd advice against doing it... I had no trouble with it but a bunch of people now have paperweights. But yeah, the link is the one provided by the other guy above me

Thank you so much @Choose an username... and @amphi66 : that worked !
Anyway I am on G B04 (Nougat).
Do you know some cool mods I should do ?
Like debloat, remove the boot message (done), etc...