My Honor 7x BND-L21 is quite broken, need help - Honor 7X Questions & Answers

Hello, sorry for the generic title, but i'm quite the noob about android modding and stuff.
Anyway I wanted to root my phone, just to stream some music to my stereo system. How naive I was...
So I unlocked the bootloader, installed twrp with adb and SuperSU with twrp. Everything was fine and phone was rooted but my past naive me thought "well let's try a custom rom, why not". So I went forth and downloaded some stuff from getdroidtips and what I understood is that all I needed to do was to do a wipe, then install the zip file via twrp. I did that and didn't work. After that I realized I made a crucial mistake: I didn't backup my phone from twrp, so I was there with no OS, quite panicked and frustrated. So I tried some other roms, finally I got one that worked, this: https://forum.xda-developers.com/honor-7x/development/openkirin-aosp-8-0-honor-7x-t3746257
It works but it's barebones and on boot it shows a message: "There's an internal problem with your device. Contact your manifacturer for details.". So, I tried recovering from HiSuite, recovery mode etc but nothing worked, I reinstalled SuperSU in the new OS via twrp to see if that would help somehow, but no. in the end I had the even more naive thought that maybe unrooting would allow me to repair via hi suite or something, so I mindlessly selected "complete unroot" on the SuperSU app, and this was the second big mistake, the process somehow ****ed up the twrp install and it no longer works. Instead, if I try to enter twrp with power button + volume up button, it shows the regular "your phone has been unlocked" screen and then comes up for a split second a black screen with, on the bottom half of the screen the "no command" logo, under it some lines of code that I can't read. It suddenly disappears and sometimes enters in a bootloop showing this screen and powering off every time.
If I keep power button pressed bootloop ends and the phone boots "regularly" in the openkirin OS.
I tried reinstalling twrp the same way I did the first time. No error on adb but same no command behaviour
So what I got now is:
kind of bootlooping no command window
openkirin OS with internal problem message
fastboot and rescue mode
it seems to work on adb (everything is fine if I type adb devices)
not working HiSuite recovery
not working Huawei eRecovery
not working download mode (I guess? the power+volume up+volume down combination)
Maybe I should mention I also did a data wipe (?? the option on the right next to "advanced wipe" in the Wipe screen, if I remember correctly) in twrp before installing openkirin, it was suggested on a yt video about how to install openkirin. And that, at a stage I tried using MultiTool but it gives me an error: "exception during a web client request. Error#9", while at the bottom left it says "downloading AdbWinUsbApi.dll..."
Sorry for the general noobishness and the bad english that might be there.
So, any tips for bringing back the phone to normal? Or at least repair twrp??
Please help, I hate needing to throw this phone away just because I wanted to stream some music and because of a couple of stupid errors

Sorry for not answering earlier. It seems, between TWRP and stock recovery, you have messed up I think. When there is no proper recovery it become difficult to bring back the phone. You should try to put it in fastboot mode first, by powering off, pressing the volume lower button and connecting it to computer. Try installing TWRP and flash a custom rom other than openkirin from there if possible. Fastboot is the choice to go if recovery is messed up.

sdivk said:
Sorry for not answering earlier. It seems, between TWRP and stock recovery, you have messed up I think. When there is no proper recovery it become difficult to bring back the phone. You should try to put it in fastboot mode first, by powering off, pressing the volume lower button and connecting it to computer. Try installing TWRP and flash a custom rom other than openkirin from there if possible. Fastboot is the choice to go if recovery is messed up.
Click to expand...
Click to collapse
No worries, I managed to fix it anyway. Some things might be obvious but I'll share what I did nevertheless, in case some other newbie finds himself in a similar situation.
So there was seemingly no way of reinstalling twrp nor the stock recovery. But luck came my way and by almost random clicking I found out that, even if multitool closed as soon as I clicked the ok button in the error message, if I simply ignored the error, the program worked just fine (as I write this I installed another version and it gave no error message). So I played with it a bit and found out that it can flash twrp and it does not need a file from you, it already has a twrp version ready to install. I did that and it worked. It looks like the first twrp file I used didn't work anymore or was someway corrupted by the countless things I tried. So, with twrp working again I was able to backup the sloppy openkiring OS and try the unbrick tool. So I browsed the internet for a guide. Guides always mention as the first step for unbricking using the VENDOR.img file located inside a full stock rom. Problem is, 99% of the times they provide a rom without the needed file. So after some tries I found a good complete stock rom with the VENDOR.img here: drive.google.com/file/d/1tjHefytEWbpuV1f4YjX8AaSMzT6jr8TQ/view but I can't remember which forum/site I found it in.
I followed the guide which involves:
-extracting the UPDATE.APP file contained in the provided zip with huawei extractor tool into an X folder on your pc
-copying the VENDOR.img file contained in the X folder, on the root folder of the sd card
-backing up OS (if there's any) via twrp (I had something like 50 partitions, I guess that was messing things up a bit, but for safety I backed them all up)
-doing an advanced wipe from twrp selecting ALL checkboxes BESIDES the SDcard of course
-flashing the vendor.img file via twrp selecting the "Vendor" partition when prompted
-downloading the update_full_[your model]_hw_[your region].zip file, in my case update_full_BND-L21C_hw_eu.zip
-extracting the UPDATE.APP file contained in update_full_BND-L21C_hw_eu.zip with Huawei extractor tool in some other folder Y
-looking for a file named cust.img/CUST.img/version.img/other_name.img (I don't know which other names it can have, I was lucky and had a VERSION.img file in it)
-rename the cust.img/CUST.img/version.img/other_name.img to CUST.img and copy it from the Y folder to the X folder
-boot your phone into fastboot mode
-connect phone to multitool via usb and select the "unbrick" tab
-there, Multitool asks for a folder, give it the X folder. There are some checkmarks on the Multitool "unbrick" page. 4/5 of them should become checked after the folder input. In my case the first 4
-then, simply press the unbrick button
-wait and pray (it can look like it freezes while it's copying the system.img file but wait, it'll be fine)
So I did that and it worked flawlessly, the phone booted slowly but surely into EMUI 5.1 with Android 7.0 I think and everything was fine.
At that point I had a working OS and a working twrp but wanted to go back to the OS I was used to, Android 8.something so, I tried connecting the thing to HiSuite and it automatically asked if I wanted to update, not to 8.something but to 9.1. I thought "SURE I DO!" and updated flawlessly (I thought 9.1 hadn't even been released here in Italy).
When it booted I found out the new OS was working like an antivirusless xp pc: it didn't recognise the SIM, it would crash every 20 seconds, app downloads got stuck at 99%, if it felt like it, it rebooted, pc connection was not stable. Besides, the update being "official" and installed from "trusted" sources (HiSuite), it completely wiped twrp.
And that was the "OH ****, here we go again" moment: no twrp and worse-than-ever-working OS.
So because of the new EMUI version, I guess, Multitool kept recognizing the phone but stopped offering its own recovery, eRecovery, twrp files available for flashing. I was completely frustrated with all of this and decided to give up, but I made the last effort: I tried the relock function in multitool. So I provided the key, pressed relock, waited, prayed, and finally cheered. It worked like a charm. Phone runs now on EMUI 9.1 with locked bootloader without problems. Finally
So I guess in the end I payed 4 euros for a nice update, a painful and frustrating trip into android modding and a lesson : never do android modding!
no, just kidding, don't do it just if you are a newbie AND you don't want to risk to throw the phone in the grabage.
In all other cases consider it carefully
Oh, and also, God bless the MT Team and Russia altogether!! thanks

Quite an experience. All the best. ?

Lol sounds fun. I've bricked my Huawei Mate SE/Honor 7x more times than I can count. I'm just awaiting my 9.1. I want my GPU Turbo! Is it as good as it's supposed to be?

Related

[Q] phone crashed last night, now says it needs to be activated, wont activate

Hoping someone here can give me some help. Sometime last night my phone crashed - had an error message on the screen asking me if i wanted to restart - basically the android version of a blue screen.
I rebooted and when it started up it tried to activate but failed. Tried it a few times, never activated. I called sprint and they had me type in 2 different codes:
##72786# which didn't get an error but didn't help anything
They had me try a 2nd 6 digit number, which I'm not sure if it's unique to my phone or not so I wont post it here but that did nothing at all - typed in the ##______# and nothing happened. They claimed it was because the phone is rooted, but the phone is ONLY rooted. I haven't installed a new OS it's the stock rom as far as i can tell.
Anyone have any ideas whats going wrong here or how to fix it?
thanks
edit: and apparently now I wiped the OS from the phone since it wont go past the LG logo. Is there some way for me to either copy a rom onto the phone from TWRP or copy a backup onto the phone? I've got a couple of TWRP backups saved on my pc, but since the phone wont start up I don't have any way of copying them onto the phone - damn non-user removable sd cards.
merkk said:
Hoping someone here can give me some help. Sometime last night my phone crashed - had an error message on the screen asking me if i wanted to restart - basically the android version of a blue screen.
I rebooted and when it started up it tried to activate but failed. Tried it a few times, never activated. I called sprint and they had me type in 2 different codes:
##72786# which didn't get an error but didn't help anything
They had me try a 2nd 6 digit number, which I'm not sure if it's unique to my phone or not so I wont post it here but that did nothing at all - typed in the ##______# and nothing happened. They claimed it was because the phone is rooted, but the phone is ONLY rooted. I haven't installed a new OS it's the stock rom as far as i can tell.
Anyone have any ideas whats going wrong here or how to fix it?
thanks
edit: and apparently now I wiped the OS from the phone since it wont go past the LG logo. Is there some way for me to either copy a rom onto the phone from TWRP or copy a backup onto the phone? I've got a couple of TWRP backups saved on my pc, but since the phone wont start up I don't have any way of copying them onto the phone - damn non-user removable sd cards.
Click to expand...
Click to collapse
Can you boot to recovery?
If you can, then flash a newer TWRP build, they have MTP support, you can mount it while connected to your PC, copy a ROM zip over (there is a stock on in these threads somewhere), flash it from recovery, wipe everything first. Then you should be able to boot into a working device.
Yes I can boot into twrp, but I'm not sure how to copy files that way. I tried using adb but it couldnt find the phone. Can you give me some tips on how to copy a new ROM or twrp backup to the phone?
Thanks
merkk said:
Yes I can boot into twrp, but I'm not sure how to copy files that way. I tried using adb but it couldnt find the phone. Can you give me some tips on how to copy a new ROM or twrp backup to the phone?
Thanks
Click to expand...
Click to collapse
Yes, first thing is to flash this.
http://cubegamemc.de/kevinjoa/lollipop/recovery-geehrc/twrp/
You can flash it through fastboot.
follow these steps:
1. Download and place the file on your PC.
2. Reboot your device into Fastboot Mode. To do that, simply hold down the Volume DOWN+Power buttons together.
3. Once inside the Fastboot mode, connect your device to your PC via USB cable.
4. Launch a Command Prompt Window in the folder you saved the recovery image to. You can do that by holding down the Shift button on your keyboard and right-click on any blank area on the screen, then select Open command window here.
4. Enter the following command into the Command Prompt Window. You need to replace recoveryfilename.img with the actual name of the Recovery Image you downloaded.
Code:
fastboot flash recovery recoveryfilename.img
5. Once it is done, reboot your device
Code:
adb reboot recovery
should do it. If not, just hold down the power button, and get back to recovery.
at that point you should have the newest recovery. This recovery has MTP enabled so you can transfer files just like you can if you had a running device.
Once it shows up on you PC you can transfer a ROM zip or a backup to the internal SD. From there you I am sure you know how to flash a zip or restore a backup. It is the same as an older version. MTP should be under the "MOUNT" section of TWRP. I don't remember because I have a different device now.
Good luck!
If this doesn't work, follow the thread here: You would need the super big full bin file if you do though because you do not have a working ROM or zip currently on your internal SD card and this contains a very old recovery, but it does work.
http://forum.xda-developers.com/showthread.php?t=2230106
edit: I altered the directions from the source here for the att version. Don't worry, I changed them to suit your current need.
http://theunlockr.com/2013/03/26/how-to-install-twrp-recovery-on-the-lg-optimus-g-att/
My phone seems to behave a little differently than what you describe. Holding down the volume down and power button just turns it on. Holding vol up and power puts me into a screen with the android bot on it with the option to restart bootloader, go into recovery, or power off. and at the bottom there's some text indicating fastboot mode is on.
I was able to use the fastboot command to load the newer recovery. But for some reason, none of the adb commands work on my phone.
I'm copying a twrp backup to the phone now and i'll restore that. Hopefully that'll fix the issue of the phone not booting and if i am really lucky, fix the issue of the phone not being activated, but I'm not too hopeful about that.
Thanks again for all your help
hey - just wanted to say thank. Got my phone to boot back up again. Unfortunately the backup restore doesnt seem to have fixed my initial problem. Phone is back to saying it needs to be activated. Any ideas about that? It's also showing zero bars - not sure if that's what it's supposed to show when it's not activated.
Thanks again for your help
merkk said:
hey - just wanted to say thank. Got my phone to boot back up again. Unfortunately the backup restore doesnt seem to have fixed my initial problem. Phone is back to saying it needs to be activated. Any ideas about that? It's also showing zero bars - not sure if that's what it's supposed to show when it's not activated.
Thanks again for your help
Click to expand...
Click to collapse
EDIT:: TRY THIS FIRST<
Do a full wipe of the system and data, not internal. GO to recovery, select wipe, then factory reset. Then boot your phone. You will have to setup everything again but it might help. If it does not, you can always restore your backup again.
^^^^^^^^^^^^^^^^^^^^^^^
Interesting that your phone was the opposite for the buttons. Maybe I had it backwards, or maybe my source did. Either way I am glad you have a device that boots now.
Check this...
Go to the about section and see if your imei and other information are blank or have 0's. I am almost certain that there are 0000's.
If that's the case then you lost your EFS some how. and there is a way to recover that as long as you have a backup somewhere. You should have one somewhere if you used freegee to unlock your phone in the beginning. If not, perhaps an earlier backup you had of your device. A lot of the recoveries for this device make a backup of the EFS.
well i just dropped the phone off at a sprint repair store to see if they could do anything with it now that it actually boots. If they can't fix it, I'll try what you suggested. Although i already tried a factory reset and that didn't help.
well you are right about the esn/meid/IMEI - they are all zeros
I did a restore and then used freegee to restore the efs. Will free tell you if there is no backup of the EFS? Because i restored it, it finished pretty much instantly, and then i restarted the phone just be safe. Unfortunately it didn't fix it.
Phone still says searching for service, and now there's a little red x over the bars. Before the bars were blank but there was no red x. Not sure if that makes any difference.
Also, something else weird is going on now. I just tried copying a newer backup to the phone to try and restore the newer one. I don't seem to be able to copy files now. When i drag the folder windows , it says the device has stopped responding. If i try and copy each individual file in the backup folder, it starts to copy, and then just sits there like it froze, or like it's copying so slowly it might as well be frozen. I had to reflash twrp to the newer version and then I'm able to copy files.
Reloaded the efs backup again but still can't activate/have all zeros.

Looking to replace stock rom

Just purchased the P8000 with the stock UI and all those little apps they install that no one ever actually wants.
Is there a rom I can install that will basically put this back to being what I think is a standard UK phone. It versions are presently as follows.
Android V 5.1
BaseBand V: MOLY.LR9.W1444.MD.LWTGLMP.V16.P10
Kernel: 3.10.65
Build No: ALPS.L1.MP3.V2.NB6753.65U.L1_P22
Custom Build Version: Elephone_P9000_20151014
thanks in advance
You should try Eragon rom, this is much better than stock although it is based on stock it has been improved greatly. This is the only fully working rom at present.
http://forum.xda-developers.com/elephone-p8000/development/rom-06-9-eragon-1-0-android-5-1-t3195007
Sorry thats not true, there is a vibe and flyme rom but they either have Chinese apps or lots of features we can use.
Thats the one I think I am going to look at this evening when I get home, thanks. Cant understand why they have some great and cheap phones coming out of Asia but insist on filling them up with bloatware...
Personally I dont think the p8000 has much bloat especially compared to samsung phones. I am sure you will enjoy Eragon.
I lost my phone (lenovo) in Dubai, was not handed in at the airport, no surprises there, so this is a cheap alternative.
Anyway, followed the instructions, and my screen looks nothing like the one on the Elephone instructions page.
I can see the recovery function, but when I select it, the Elephone logo appears for a few seconds, then I have a dead Android icon, with red triangle and exclamation mark, so I cant even root the thing yet, even following their instructions
Try using philz recovery, this is what I use. Its a scatter file just like elephones clockworkmod version. Just to confirm, are you holding volume up button and power at the same time which brings up the bootloader. Then select what you want with volume up and confirm with volume down?
http://forum.xda-developers.com/ele...covery-philz-touch-6-59-0-port-p8000-t3224478
ok Im going to have another go at this, as I am not sure I did anything right.
Looking at the Phillz Link, it takes me to the flash info at Elephones site.
Followed the instructions and selected scatter file, flashtool download took about 4 seconds, max.
Came up with the big green tick in the window
Now is where I am lost, because it says the rom download is now completed, but nothing on the phone has changed, and there appear to be no more instructions?
What exactly have I just done, because its not entirely clear.
I am assuming I just downloaded a backup copy of the rom I have presently installed, the stock P8000 rom, but the instructions are not exactly clear on this
ok, this time on holding power and vol down I got a different display, but sadly the 4 available options were in chinese so I have no idea which one to select, and I suspect the next page, should I guess right, will also be in Chinese, so I guess I cant do this,
Right, making some, little, progress.
Now get into bootloader (instructions are not quite right for me, have to do Pwr + Vol Down, then select recovery, then hold power and vol up to get into bootloader
Anyway, select eragon from folders, and it starts then says failed with an error aborted.
Back to try again, with new fresh download
ok following the instructions from Eragon, I get to the select the zip and it starts and fails, however, I place the zip fileon what I know is the external microSD I put in the phone, but I get the feeling that during the start process it un-mounts this drive and thus fails immediately.
So, I am now able to do as follows.
Put ZIP onto external SD
Boot into Bootloader
factory reset phone
Select ZIP
Start install
fail with following information
E:cannot mount custom path
E:you must first setup a valid folder
/storage/sdcard1: Checking
/storage/sdcard1: mounted
Calculating MD5sum....
I then select YES - INSTALL Eragon_P8000_V_5.5.0.zip
Installing:/storage/sdcard1/Eragon_P8000_V_5.5.0.zip
Finding update package...
Opening update package...
E:/Cant Open storage/sdcard1/Eragon_P8000_V_5.5.0.zip
(bad)
E:Installation aborted
Press any key to continue
lovely, looks like its bricked.
Get logo nothing else
Can get to the android menu where it says recovery, something I cant read and normal, but recovery does nothing
Which revovery do you use?
Use thePhillz Touch recovery, cwm have problems with external sd.
Best way to install it is for you via SPFlash tool.
If you done with that, you can boot into bootloader and choose there recovery.
Than you should be able to install the marvelous Eragon ROM.
hth
Cheers
sorry Im not following you.
I have the flash tool software
I appear to no longer be able to get into the bootloader.
can I upgrade the firmware to Eragon using the flashtool?
I have to say, I am a very technical person but this is a baffling process.
I am well versed in rom updates on MB, Tablets etc, all of which should be similar.
after trying both the Eragon and Phillz instructions, nether worked for me
Then I found the phone sat at the logo and I was unable to do anything
Now, for unknown reasons it let me into the bootloader again
I am now able to factory reset
I am not going to try Eragon because it simply will not let me do it
Are you all sure you have the same phone, or that there are not perhaps some versions of the same phone where these instructions are not right?
What seems simple to do is proving impossible to do
Why else able to enter the recovery
111
spottedhaggis said:
I have to say, I am a very technical person but this is a baffling process.
I am well versed in rom updates on MB, Tablets etc, all of which should be similar.
after trying both the Eragon and Phillz instructions, nether worked for me
Then I found the phone sat at the logo and I was unable to do anything
Now, for unknown reasons it let me into the bootloader again
I am now able to factory reset
I am not going to try Eragon because it simply will not let me do it
Are you all sure you have the same phone, or that there are not perhaps some versions of the same phone where these instructions are not right?
What seems simple to do is proving impossible to do
Click to expand...
Click to collapse
I had trouble getting Philz recovery to load to phone but finally got it to work using the latest version of SP flash tool from Android MTK. Google to find it. Load the scatter.txt from unzipped Philz recovery, click download, attach powered off phone to PC. Only took a few minutes to load for me.
spottedhaggis said:
ok following the instructions from Eragon, I get to the select the zip and it starts and fails, however, I place the zip fileon what I know is the external microSD I put in the phone, but I get the feeling that during the start process it un-mounts this drive and thus fails immediately.
So, I am now able to do as follows.
Put ZIP onto external SD
Boot into Bootloader
factory reset phone
Select ZIP
Start install
fail with following information
E:cannot mount custom path
E:you must first setup a valid folder
/storage/sdcard1: Checking
/storage/sdcard1: mounted
Calculating MD5sum....
I then select YES - INSTALL Eragon_P8000_V_5.5.0.zip
Installing:/storage/sdcard1/Eragon_P8000_V_5.5.0.zip
Finding update package...
Opening update package...
E:/Cant Open storage/sdcard1/Eragon_P8000_V_5.5.0.zip
(bad)
E:Installation aborted
Press any key to continue
Click to expand...
Click to collapse
you still have the problem? if yes send me a pm . i can help

I think I bricked my ZE551ML_Z00A

Hi everyone, I think I bricked my ZE551ML by being very very dumb, how did I come in such troubles? Well I'll explain you the whole story.
Usually I'm quite good with IT but I'm new to Android and I wanted to install Lineageos because I don't like Asus's ROM, so I searched tutorials and I found the lineage website tutorial at first it didn't seem like a hard task for me, so I started following the tutorial and I got stopped first with trying to get twrp-3.1.1-0-Z00A on the device but didn't seem to work so I tried an older version witch didn't worked too, so I came to xda to get the twrp_z00a_v24_repack and it worked (so well that I erased the system without saving anything just in case but I saved myself by getting the Asus ROM and pushing it to /sdcard/ ) so I attempted to install Lineage (that time with a save) but it gave me the "error executing updater binary in zip" so I searched on the Internet and it seemed that I had to root the phone so I downloaded addonsu-14.1-x86-signed from the Lineageos website and ran it on twrp and it told me that it worked so I wiped the system (I still got the backup) and tried to install Lineage but the same error showed up so I was thinking "Hmm maybe due to TWRP being an old version it might not work if it's not updated" so I rebooted to fastboot and then did fastboot flash recovery twrp-3.1.1-0-Z00A and tried to go in recovery, the phone rebooted, the splashscreen showed and it got to a screen similar to the splashscreen and did nothing (just heard the plug-in device sound in Windows), when I try to shut down and push the power + "+" Button it just starts as normal and the fastboot mode doesn't show.
So that's where I am, if someone could do a dumbproof step by step tutorial on how to unbrick that thing and then install Lineageos that would be so great.
Thank so much to the person (or people) that will help me
PS: I tried to search how to get out of this mess but I didn't understood all of it so I didn't wanted to get in more troubles.
Yuno17 said:
Hi everyone, I think I bricked my ZE551ML by being very very dumb, how did I come in such troubles? Well I'll explain you the whole story.
Usually I'm quite good with IT but I'm new to Android and I wanted to install Lineageos because I don't like Asus's ROM, so I searched tutorials and I found the lineage website tutorial at first it didn't seem like a hard task for me, so I started following the tutorial and I got stopped first with trying to get twrp-3.1.1-0-Z00A on the device but didn't seem to work so I tried an older version witch didn't worked too, so I came to xda to get the twrp_z00a_v24_repack and it worked (so well that I erased the system without saving anything just in case but I saved myself by getting the Asus ROM and pushing it to /sdcard/ ) so I attempted to install Lineage (that time with a save) but it gave me the "error executing updater binary in zip" so I searched on the Internet and it seemed that I had to root the phone so I downloaded addonsu-14.1-x86-signed from the Lineageos website and ran it on twrp and it told me that it worked so I wiped the system (I still got the backup) and tried to install Lineage but the same error showed up so I was thinking "Hmm maybe due to TWRP being an old version it might not work if it's not updated" so I rebooted to fastboot and then did fastboot flash recovery twrp-3.1.1-0-Z00A and tried to go in recovery, the phone rebooted, the splashscreen showed and it got to a screen similar to the splashscreen and did nothing (just heard the plug-in device sound in Windows), when I try to shut down and push the power + "+" Button it just starts as normal and the fastboot mode doesn't show.
So that's where I am, if someone could do a dumbproof step by step tutorial on how to unbrick that thing and then install Lineageos that would be so great.
Thank so much to the person (or people) that will help me
PS: I tried to search how to get out of this mess but I didn't understood all of it so I didn't wanted to get in more troubles.
Click to expand...
Click to collapse
if you are able to access recovery then dd fastboot there. if no recovery, no fastboot, no system there isonly option left. go to below thread and do step by step as suggested.. after you get fastboot mode back, do not use asus flash tool use commands to flash raw firmware see section flash firmware without AFT
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
if you are able to access recovery then dd fastboot there. if no recovery, no fastboot, no system there isonly option left. go to below thread and do step by step as suggested.. after you get fastboot mode back, do not use asus flash tool use commands to flash raw firmware see section flash firmware without AFT
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Hi, thanks for the reply, I don't know if I have to post it here or on the guide but xFSTK-downloader just won't run (Windows 10 1151) and it doesn't show up in task manager (even when the antivirus is disabled).
Have you got an idea on why it doesn't work?
Yuno17 said:
Hi, thanks for the reply, I don't know if I have to post it here or on the guide but xFSTK-downloader just won't run (Windows 10 1151) and it doesn't show up in task manager (even when the antivirus is disabled).
Have you got an idea on why it doesn't work?
Click to expand...
Click to collapse
very first of all uninstall everything especially i soc drivers and xFSTK. then disable driver signature enforcement. and go to thread above posted and do step by step.
how to disable signature enforcement and install driver on win 10 see in thread above

Lenovo P2 (P2a42) stuck mostly on blue logo screen

Hello --
I found this very nice looking phone thrown away in a bin and I guess this problem was the reason.
It would be great to get it going maybe even worth paying to get it running.
But I would appreciate any suggestions on how to do it myself.
I am not familiar with a lot of the in-depth hacks people do with phones. Words like "flash" and "ROM" are foreign to me.
But I like to try to fix things.
I have tried a few simple actions to get the phone going but it still does only three main things:
1. Shows the "Lenovo powered by Android" screen of course.
2. Volume down + Power: shows Fastboot screen with just three options: Start, Barcodes, Power off
3. Occasionally, some buttons I push get to Teamwin Recovery Project. But I do not exactly know how it happens and it is hard to repeat. It seems to come up after trying everything and then putting the phone down.
From TWRP I have selected these options:
-- Factory reset
-- Restore (I think) -- I selected just a single item displayed available for restore
-- Wiped Delvik cache and format cache
-- Reboot
I also downloaded ADB and installed it. Instructions I read said to run an .exe file but all I could find was .bat so I clicked on it and saw the RUN screen open briefly then close.
Thank you.
NickSergeant said:
Hello --
I found this very nice looking phone thrown away in a bin and I guess this problem was the reason.
It would be great to get it going maybe even worth paying to get it running.
But I would appreciate any suggestions on how to do it myself.
I am not familiar with a lot of the in-depth hacks people do with phones. Words like "flash" and "ROM" are foreign to me.
But I like to try to fix things.
I have tried a few simple actions to get the phone going but it still does only three main things:
1. Shows the "Lenovo powered by Android" screen of course.
2. Volume down + Power: shows Fastboot screen with just three options: Start, Barcodes, Power off
3. Occasionally, some buttons I push get to Teamwin Recovery Project. But I do not exactly know how it happens and it is hard to repeat. It seems to come up after trying everything and then putting the phone down.
From TWRP I have selected these options:
-- Factory reset
-- Restore (I think) -- I selected just a single item displayed available for restore
-- Wiped Delvik cache and format cache
-- Reboot
I also downloaded ADB and installed it. Instructions I read said to run an .exe file but all I could find was .bat so I clicked on it and saw the RUN screen open briefly then close.
Thank you.
Click to expand...
Click to collapse
YOU CAN CHECK IN MY SIGNATURE FOR ALL BASIC TERMS USED IN FLASHING.
Look here if you want to return to offical stock Rom
https://forum.xda-developers.com/lenovo-p2/development/fastboot-files-stock-firmware-t3649914/amp/
If you have TWRP installed , you can update TWRP and then flash a custom rom. You can hold both volume up and down and power key to boot into TWRP when phone is switched off.
Remember new custom roms need newer version of TWRP.
What you'll need to do is download a custom rom like say Havoc OS Android 10 (just search it in the forum), you will need to upgrade your TWRP.
Once this is done, you will download Havoc OS Rom and put it in your phone or sd card
You just do a factory reset and then format only system . Don't format other partitions in TWRP.
Install that room and then you will also need to install gapps. (Google open gapps , chose Android 10 version and architect as 64bit and choose nano or pico gapps)
So in your sd card, you must have rom and gapps.
Once you install rom first and then gapps, restart. If it comes with an error, it means your TWRP needs update.
To update you will choose to download TWRP (zip format will install directly while IMG format can be flashed as well by choosing install IMG while you select install in your TWRP.
Restore is only available if you already made a backup with your TWRP .
I will suggest to make a full backup (except system and data ) in TWRP before you do the above.
I will also suggest you to Google if you are not sure. Make sure to follow instructions only from XDA as they are most reliable than other sources.
Watching YouTube videos may help you as well
In short:
Update TWRP
Download Havoc Rom and Gapps pico
Put them in your sd card
Install them in this order rom and then gapps.
Restart.
If you still feel you need help, please quote me for an answer
All the best .
Hnk1 said:
Look here if you want to return to offical stock Rom
https://forum.xda-developers.com/lenovo-p2/development/fastboot-files-stock-firmware-t3649914/amp/
Click to expand...
Click to collapse
Thank you for this advice -- it worked! Finally the phone gets past the logon and is operating.
Now I have a further problem and please let me know if you think this should be a new thread for this.
I cannot sign in to Google because of anti-theft feature -- instead I get this.
“This device was reset. To continue, sign in with a Google Account that was previously synced on this device”
I see a few solutions online but not exactly for Lenovo. What would you recommend?
I'm on the same boat as Nick. Do we have to wait 15 days to unlock the bootloader? Just coz it'll be hard to be 15 days without a phone and everything wiped out. I wanna try Syberia 2.9 as the last LineageOS is not ready yet. Thank you very much.

LineageOS 17.1 device shuts down after some time from booting on SM-T295

note: everything that I've flashed was from my SD card; I had the files on /sdcard1/Download
note 2: since my device's bootloader is unlocked, I have to press the power button after turning on the device, so that the "bootloader unlocked" warning goes away
I've managed to install TWRP (I followed this guide, "How to Install twrp Recovery on Samsung SM-T295" part, I modified a bit the steps, i had to go into download mode again after flashing TWRP_3.4.0.1+vbmeta_T295.tar and flash aboot_vk_T295XXS3ATB4.tar) and then LineageOS 17.1 (from a GSI I found on this post, to flash I followed this guide) on a Samsung Galaxy Tab A 8.0 (2019) (SM-T295). Then I rooted it after installing LOS (from this guide, "How to Root Samsung SM-T295" part, I didn't make a backup due to errors, and multidisabler-samsung-2.6.zip failed to flash). Magisk had to update after, so I did that. Until then, no errors, until I downloaded BitGApps (I followed this guide, I downloaded the ARM64 version for Android 10 directly from my device). My TWRP had some problems flashing, because I couldn't access the Internal Storage from there (for some reason, /sdcard directory shows only folders on Install (and files, in the file manager) with random numbers and letters names like MAKVjaaw24Ajg35waD (not an actual folder or file, just an example), and I couldn't find the files to flash, which is why i had to flash everything from my SD card), so I rebooted to system from TWRP, and tried to copy the BitGApps file to my SD card so I could flash. I think I was about to copy the file (or I had just selected the copy option but hadn't found the directory to copy the file to, which was /sdcard1/Download), and suddenly, my device just powered off. I thought "oh it's just a bug, I'll power it on again and it'll be fine", but something strange happened when I powered it on; Now, every time I turn it on with the power button, I have to hold it less time for it to boot for some reason. That's weird. When android started and I could use the device, I tried to copy BitGApps to my SD card again, but my tablet powered off again and the same happens every time now. When i boot into safe mode, this doesn't happen, so I suspect it happens because of an app I installed, and now that I think about it while writing, I think it's probably Magisk Manager (I made it so that Magisk allows any superuser request, which is why I think Magisk has to do). I have the apps Phone Guardian (I always install it because I love it), Magisk Manager and the Official TWRP app.
Also something weird I noticed; Ever since the first time it bugged for me, whenever I boot into TWRP and then power off from the reboot menu, next boot is TWRP even if I don't do the button combo to boot into recovery (for my SM-T295 it's hold power + hold volume up at the same time when the device is off, then when it powers on, release all the keys and press power when promted to make the "bootloader unlocked" warning go away if necessary).
Does anyone have any ideas on why this is happening? Am I right on my guess that Magisk is faulty? Do I need to uninstall it and unroot if that's the case? Thank you all in advance.
Update: it was Magisk, but not the option I said, maybe a module?
Update: I got it now.
Jaqueek said:
Update: it was Magisk, but not the option I said, maybe a module?
Click to expand...
Click to collapse
No, I was wrong. I figured it out. It bugs after I update to Magisk 21.3 from 20.4. The manager is not a problem. Also,...
Jaqueek said:
Now, every time I turn it on with the power button, I have to hold it less time for it to boot for some reason. That's weird.
Click to expand...
Click to collapse
... It is weird indeed, but not important, it's not annoying and useful if I'm in a hurry or smth so I can't complain. Also, after I uninstalled Magisk that didn't dissapear. Anyways, I just don't care about that anymore.
Also, I managed to flash GApps pico, it was a little hard.
One last thing, when I said that my TWRP saw gibberish when trying to access /sdcard1,
it appeared to not be only TWRP. Stock File Manager saw those weird names too, after I wiped the Internal Storage partition. I just fixed content in TWRP and wiped Int. Storage again, it's fine now. I still haven't checked TWRP though. (just checked, yeah it looks the same still but any file manager is fine)
So, what is causing my device to turn off when I update to Magisk 21.3?
Edit: It also happens when I uninstall the original and install the new one.
How did you get the Treble GSI working on this device?
Mine just bootloops on the bootloader, even after doing your steps...

Categories

Resources