Flashing android 6 over android 7 - brick - Droid Turbo 2 Q&A, Help & Troubleshooting

Hello,
I`ve been reading forums for 8 hrs now but can`t find any help.
I`ve flashed 6.0 firmware on 7.0 device without bootloader unlocked. Device can`t see any WiFi. When I try to flash via fastboot it`s always the same.
I wanted to enable oem unlock to unlock bootloader to instal TWRP to flash new firmware from SD card, but cant acces settings - no wifi - can`t go over setup wizzard.
Can enter fastboot, recovery mode. Win10 here RSD(odin like software) can`t see my device.
Do you have any suggestions what do do to instal any firmware that will work on my xt1580 Moto X Force?
Looking forward for help.

Cin3k33 said:
Hello, I`ve been reading forums for 8 hrs now but can`t find any help. I`ve flashed 6.0 firmware on 7.0 device without bootloader unlocked. Device can`t see any WiFi. When I try to flash via fastboot it`s always the same...
Click to expand...
Click to collapse
I don't have this device but, the XT1580 is actually a Motorola Droid Turbo 2 and your best bet is to post this question within the following thread.
https://forum.xda-developers.com/showthread.php?t=3387653
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Related

I can't seem to unlock the bootloader of the Axon 7

I wanted to try LinageOS but I can't get the bootloader to unlock. I followed the information in the link http://www.cyanogenmods.org/forums/topic/unlock-bootloader-android-phone-using-fastboot/...
When connected to my PC and the phone booted I do adb devices and it shows my phone ... I do adb reboot bootloader and my phone reboots to the boot loader.. I type fastboot devices and it shows my phone ... i type fastboot oem unlock and it says Failed (command not found) I type in fastboot -i 0x19d2 oem unlock and it says "waiting for device" and never comes out of it.
Don't think you can unlock the ZTE Axon 7 in the way described.. does anyone know a way to do this? I have tried googling it but no one seems to have an answer and everyone says to do the same thing but it doesn't work
You may skip the other parts if all you want to do is unlock your bootloader. Or better, if you're on A2017U, you can use this bootloader unlock guide, too: https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
---------- Post added at 02:52 PM ---------- Previous post was at 02:50 PM ----------
Have you tried this guide?
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
It is more comprehensive than the one on the site you visited. Also pay attention to the "Allow OEM unlock" section. I'm sure that's where your problem might be from.
The problem I have is ... you seem to need TWRP installed .. the one post you listed removed the link for TWRP and the other has a link that the only download is a spammer/downloader exe crap .. the "real" download link doesn't work. So ... the method may work but I can't try it .. and both these seem to be for the older stuff .. hope it doesn't brick a phone with Nougat update installed already. ... I guess you need a certain TWRP because some will break the phone if you try to do a restore ... I just want to unlock my bootloader so I can try different ROMS .. but .. it seems like it's a very dangerous and "iffy" thing .. I can't afford another phone if I kill this one.
Seems I need the fastboot_unlock.img installed before I can use the oem unlock command and that may be different in the Nougat update??? maybe that is why they "put on hold" unlocking ... I would wait for them but it seems like they aren't going to enable unlocking again or it should have been available with the new update.
an additional note ... I can't even get the axon7tool to work .. got the QUSB_BULK driver installed .. and if i try to run axon7tool -r boot to back up my boot partition i get the following:
C:\adb>axon7tool -r boot
Connecting to device...
Sending programmer...
S: failed to read command
S: Failed to read request
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.
Alright, try the axon7root tool, then. Many people have had success with that also.
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
unfortunately this is the same ... all the links posted in the above link just link to nasty horrible pages .. don't click on the links on a Windows PC without major protection .. even trying them in a Linux VM i couldn't get the files to download.
So none of the files are available that I need .. and I guess I hope someone will have tried this with the new B15 Nougat
I was able to get axon7tool-1.5-win64.exe which doesn't work at least to back up so I didn't want to try flashing anything.
I also have TWRP_UnlockBootloaderPackage_by_DrakenFX.zip but you need TWRP installed to use it and again not sure if it works with B15 Nougat.
I have the twrp-3.0.3-1-ailsa_ii.img but don't know if this is one of those versions that deletes some number when you try to restore and breaks things... or if this version would work for the B15 Nougat setup.
I was unable to download the "tools" which I guess include axon7root.exe so I can't try that to flash TWRP-3.0.3-1-ailsa_ii.img
Oh and sorry .. this is a A2017U with the latest update B15 Nougat
I will personally upload the necessary files, along with a signed version of TWRP(3.0.2-2) and send you a link
Ok thanks ... I'm worried about having the Nougat update already.... not sure any of the unlocking stuff has been tested with the Nougat update ... I hope it doesn't break something
Hey, has anyone found out whether any of this works on Nougat yet? I can't seem to get past any of the steps with nougat
KwesiJnr showed me this link https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514 Which has some newer B15 files ... But I am unable to get through the first step using the MiFlash to flash the EDL package. Maybe you would have better luck .. it seems to be a computer thing ... it didn't work at all at first but after reinstalling drivers I got some reaction out of the program but still cant make it through

OK, this is a loooong story. Can someone save my xperiac4?PLS...........

I have a xperia c4 e5303, is a awesome device and 5-6 days ago i wanted to use xposed firmware to enable a fake gyroscope.
AND THE HELL STARTED.
I had the device rooted with custom recovery twrp when i was in lollipop 5.1, i installed the firmware for xposed and the phone was stucked in "android optimization", for hours. I restarded it sometimes but nothing, so i formatted my device and when i rebooted it, i was stucked in "sony" logo screen, some minutes ago i founded that my phone was totally empty.
c: *internal screaming*
I waited the next day, i downloaded the ftf of original marshmallow 6.0 firmware for sony xperia c4 and i installed it on my device, then everything worked perfectly luckely.
Easy peasy lemon squeezy, or not?
Some hours after i founded that i couldn't use the recovery mode!
I searched and searched and i founded that the problem could be the bootloader,so i used a sony official guide to unlock that.
I couldn't finished that guide becouse with any connection, on any computer, android sdk can't install his components(such as google usb driver, that are required for that method), and the program just install everytime the same package in loop. I tried aaaallll the method in the universe for that, i tried also to install once per once the zip files of the downloaded package but it was totally useless.
So i founded another method after some days of searching (with flashtool) and now my bootloader is fully unlocked, if i use flashtool to unlock the bootloader, it says that is unlocked and ask me if i want to relock it so i think now the bootloader unlock is done. FINALLY.
Then, i turned off the phone and started it by pressing the volume down+power botton, and all the device did was reboot himself repitetly until i release hard keys and when i do it the phone start automatically.
I think my device now reboot himself instead of going in recovery mode.
What can i do i am totally frustrated about this and i really don't want to buy a new device becouse i don't have a gyroscope. I love my xperia c4, i just don't know why i can't get the recovery mode back to install twrp, for rooting the device, for retry to get xposed virtual sensor and then finally enjoy my vr experience...
In the end, i have a Xperia C4 5303 with original Marshmallow 6.0 firmware installed, that can't go in recovery mode in any ways.
Pls someone help me..
no one?..
No one here know hot to save my smartphone?
update: now i can use fasboot and adb commands becouse i installed the drivers properly.
but i still can't flash a custom recovery to get the root..
asnachan said:
update: now i can use fasboot and adb commands becouse i installed the drivers properly.
but i still can't flash a custom recovery to get the root..
Click to expand...
Click to collapse
Digging through XDA (next time use the website's search bar, tee hee hee) I found this thread:
https://forum.xda-developers.com/xp.../bootloader-unlocked-custom-recovery-t3285521
Edit: I know it says C5 Ultra whatever but the thread says it also works with your model (C4 E5303 no?)
Before trying anything, I'd seriously recommend reading all eleven pages so you don't miss anything and end killing your phone (or back at square 1).
I'm not an expert on Android or anything (I personally have only owned 1 device — a first gen Moto G), but the method presented in the thread is very odd. Are all Xperia phones this weird?
Read carefully — some steps might be unnecessary (after all, you already unlocked your bootloader [maybe?])
P.S. you lost the recovery because by installing the original firmware it basically got erased (original firmware didn't have TWRP after all!)
P.S.S. you should create a backup once you get TWRP up and running, just in case.
I can't help you more than this because I do not own the device, so I cannot share ~personal wisdom~ with you (beyond recommending the Moto G series).
Good luck!
( And search the forums and threads before posting — that's an XDA rule! )
Sent from my Motorola Moto G using XDA Labs
thx
Bludwurst said:
Digging through XDA (next time use the website's search bar, tee hee hee) I found this thread:
https://forum.xda-developers.com/xp.../bootloader-unlocked-custom-recovery-t3285521
Edit: I know it says C5 Ultra whatever but the thread says it also works with your model (C4 E5303 no?)
Before trying anything, I'd seriously recommend reading all eleven pages so you don't miss anything and end killing your phone (or back at square 1).
I'm not an expert on Android or anything (I personally have only owned 1 device — a first gen Moto G), but the method presented in the thread is very odd. Are all Xperia phones this weird?
Read carefully — some steps might be unnecessary (after all, you already unlocked your bootloader [maybe?])
P.S. you lost the recovery because by installing the original firmware it basically got erased (original firmware didn't have TWRP after all!)
P.S.S. you should create a backup once you get TWRP up and running, just in case.
I can't help you more than this because I do not own the device, so I cannot share ~personal wisdom~ with you (beyond recommending the Moto G series).
Good luck!
( And search the forums and threads before posting — that's an XDA rule! )
Sent from my Motorola Moto G using XDA Labs
Click to expand...
Click to collapse
Thanks a lot for your time, but i am using that thread to root this, and i am stucked at the last point becouse i don't know what he means with:
"THIS IS IMPORTANT
The rom has
Code:
recovery.from.boot.p"
I did all the steps except for that, and i get no errors but when i try to boot in recovery the phone just stay on the logo and then after some minutes reboot himself and starts normally.
i already ask what the last point is in that thread
p.s.: i know i will not have twrp if i reinstall stock fw, but the point is that i don't have also the normal recovery, i can't access to that via adb or via hard keys..
asnachan said:
Thanks a lot for your time, but i am using that thread to root this, and i am stucked at the last point becouse i don't know what he means with:
"THIS IS IMPORTANT
The rom has
Code:
recovery.from.boot.p"
I did all the steps except for that, and i get no errors but when i try to boot in recovery the phone just stay on the logo and then after some minutes reboot himself and starts normally.
i already ask what the last point is in that thread
p.s.: i know i will not have twrp if i reinstall stock fw, but the point is that i don't have also the normal recovery, i can't access to that via adb or via hard keys..
Click to expand...
Click to collapse
Ah. You should've mentioned it (i.e. linked to the guide). Sorry sorry!
Read further down. The "recovery.from.boot.p" is this thing that overwrites TWRP with the stock recovery. Following the «THIS IS IMPORTANT» indication are instructions to get rid of the thing, and so being able to keep TWRP permanently.
You need that last step to succeed.
Sent from my Motorola Moto G using XDA Labs
in the other thread they said to me to roll back to 5.1 i am doing it now
nvm i got hard brick, the phone is dead and i can't enter in download mode....
asnachan said:
nvm i got hard brick, the phone is dead and i can't enter in download mode....
Click to expand...
Click to collapse
I'm very sorry to hear that ?
Sent from my Motorola Moto G using XDA Labs
Is fine, i had to buy another phone that is why is tarted to root the xperia.
just..i'm out from the world of rooting i think. i broke 2 devices 1 by flashing a original rom with sony original flashtool and 1 by installing a root with kigroot, and now on that i can't read the sim.
i wait until the world of rooting will be more stable and with more official custom roms...
RIP

[ASK] Oppo A37f (neo9) problem

Hi, im new here with no knowledge about android system.
my phone is oppo a37f running coloros 5.1.1 and 1 week ago i was downgraded it bcs i want to get root access. but i think something is crashed everytime. my screen freeze or hang and then restarted everything like rebooted.
now i want to unlock bootloader and try TWRP recovery so i can try custom rom for my phone.
i've tried many ways to unlock bootloader (with/without pc) and i still cant get into it
edit: because i think my phone cant load fastboot or even dont have fastboot mode. only recovery mode exist. tried with adb reboot-bootloader or adb reboot bootloader and nothing changed, normally startup, then if i type fastboot devices and nothing shown in my powershell, and if fastboot device without 's' then show waiting for device and stuck. tried also to fix this under devmgmt.msc because i think its a driver problem but still nothing.
yesterday i was tried for using oppotools but bootunlocker is not working for no reason, clicked unlock and tamper but nothing happened. and yesterday i accidentally deleted my stock recovery but everything is back now.
i have tried many ways until download QFIL but still not working. please help :crying:
sorry for my english
vlentzz said:
Hi, im new here with no knowledge about android system...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3631737
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Ibuprophen said:
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3631737
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
I've seen that thread also but still nothing happened with my phone
because i've seen many tutorial from xda about my phone thats why i make this thread. tired of googling and even search on youtube. :crying:
ok sorry, will do it later. thankyou bro.

brick axon 7 A2017G (android 7.1.1.)

Good evening owner of the axon 7 I decided to finally get into the unlocking of my phone in order to root. I followed the first step. Install the twrp on the phone. I had the Nexus 4 and the LG G3 I managed to do it without problem.
There I am the steps I had problems with drivers that I had to reinstall. When then I made the invitation to order I had trouble to have the "QUSB__BULK".
When I managed it with XDA's Axon7_EDL_Tool software (compatible with my French axon in 7.1.1) I managed to install twrp except that ... behind bootloop I get stuck on the zte logo !!! I press volume up the twrp is displayed. I decided to use my update on my SD. I realize that my phone reference US (A2017U) !!! I do not understand how I did to find myself with that !!! However, I used the tutorial link [GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM. Is it because of Axon EDL tool? Yet I read and read it is compatible with the euro version A2017G! I do not understand and I panic !!! So I tried to use my backup Update (the last update of ZTE performed in August) and I find myself without the twrp! And I still have the bootloop ... How to remove this brick please ???? Thank you very much for your help !!!:crying::crying::crying:
angelmika91 said:
Good evening owner of the axon 7 I decided to finally get into the unlocking of my phone in order to root. I followed the first step. Install the twrp on the phone. I had the Nexus 4 and the LG G3 I managed to do it without problem.
There I am the steps I had problems with drivers that I had to reinstall. When then I made the invitation to order I had trouble to have the "QUSB__BULK".
When I managed it with XDA's Axon7_EDL_Tool software (compatible with my French axon in 7.1.1) I managed to install twrp except that ... behind bootloop I get stuck on the zte logo !!! I press volume up the twrp is displayed. I decided to use my update on my SD. I realize that my phone reference US (A2017U) !!! I do not understand how I did to find myself with that !!! However, I used the tutorial link [GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM. Is it because of Axon EDL tool? Yet I read and read it is compatible with the euro version A2017G! I do not understand and I panic !!! So I tried to use my backup Update (the last update of ZTE performed in August) and I find myself without the twrp! And I still have the bootloop ... How to remove this brick please ???? Thank you very much for your help !!!:crying::crying::crying:
Click to expand...
Click to collapse
that is not very understandable to be honest. Just know that any misstep can put you into a hard brick.
If your phone is an A2017G then you have to install A2017G stuff, NO MATTER WHAT. The name will change to A2017U after installing a ROM, but that's normal since most ROMs are based in U firmware. Your phone is still a G.
You cannot install an official SD card update from zte if you are on TWRP, it will fail. Those can only be installed through the stock recovery
To unbrick your phone, first enter EDL mode (vol+ vol- and insert the cable). Tell me what driver appears on the Device manager (QUSB_BULK, Qualcomm HS-USB, ZTE diagnostics)
If it is Qualcomm HS-USB QDLoader 9008, you'll need a stock EDL file (download one FOR THE A2017G, from the EDL Tool thread). Then install it using EDL Tool
Reading your post I didn't see you unlock the bootloader first?
That can cause major problems.
The best app to use to reinstall your firmware is the Miflash app.
Ive used the Edl tool and the Axon 7 toolkit and both are good for certain flashing and unlocking.
If you have a A2017G make sure all software is related to that device to be sure.
Syberclone said:
Reading your post I didn't see you unlock the bootloader first?
That can cause major problems.
The best app to use to reinstall your firmware is the Miflash app.
Ive used the Edl tool and the Axon 7 toolkit and both are good for certain flashing and unlocking.
If you have a A2017G make sure all software is related to that device to be sure.
Click to expand...
Click to collapse
don't mislead. if you're using Controllerboy's guide you have to install a signed TWRP prior to unlocking the bootloader.
Choose an username... said:
don't mislead. if you're using Controllerboy's guide you have to install a signed TWRP prior to unlocking the bootloader.
Click to expand...
Click to collapse
I'm not using anyone's guide, (I always read several guides not just one BTW)
Show me where Twrp is installed on a locked bootloader, I think that info is misleading.
The twrp site instructions require an unlocked bootloader.
Cyanogen Mod also states and unlocked bootloader is required.
Syberclone said:
I'm not using anyone's guide, (I always read several guides not just one BTW)
Show me where Twrp is installed on a locked bootloader, I think that info is misleading.
The twrp site instructions require an unlocked bootloader.
Cyanogen Mod also states and unlocked bootloader is required.
Click to expand...
Click to collapse
The twrp site has nothing to do with specific per-device unlocking. The point of signed TWRP is being able to install it on a locked phone without wreaking havoc.
I don't have to show you. He said which guide he used, go check it up. But don't mess it up more than it is.
Choose an username... said:
The twrp site has nothing to do with specific per-device unlocking. The point of signed TWRP is being able to install it on a locked phone without wreaking havoc.
I don't have to show you. He said which guide he used, go check it up. But don't mess it up more than it is.
Click to expand...
Click to collapse
I do know the difference between "signed" and "unsigned" software.
I'll let you help this guy out if you think my info is misleading, good luck
Hello,
We can close the subject, I managed to do it again my phone thanks to the update file (the last update ZTE) I still had in the micro SD card.
The latter by putting it in my samsung tablet I saw that my content was not finally erased. So I put the sd in my tel and suddenly the content was finally visible in the part apply update from sdcard. I could make a flash with the update and everything is fine it works! ouffff
Anyway all my apologies I had misread the tutorial.
I did not see that it was compatible only with Marshmallow and not Nougat. I was in 7.1.1 ... I focused too much on the models (A2017x) and the updates of ZTE (B4 / B5 / B6 ...). Then my english is bad. I had to use google translation but no apology is my fault. I should have been careful. I am a bit rusty since Nexus 4 (or it was super easy and there was a huge community) and even the LG G3. I find the ZTE Axon 7 more boring to root, to unlock ...
In short again thank you and sorry for this post !!!
Syberclone said:
Reading your post I didn't see you unlock the bootloader first?
That can cause major problems.
The best app to use to reinstall your firmware is the Miflash app.
Ive used the Edl tool and the Axon 7 toolkit and both are good for certain flashing and unlocking.
If you have a A2017G make sure all software is related to that device to be sure.
Click to expand...
Click to collapse
for information I also based on a second site in French where it was explained that it was necessary to first put the TWRP and after and only after unlocked the bootloader. In short, I lacked vigilance and concentration. Even on the French tutorial it was marked in red that it was incompatible Nougat. I read diagonally and made a mix with the other XDA tutorial. That's it I did not care. Do not fight lol The phone works is essential. Now I would like to know why I have a driver problem on my PC it seems to me but that's another subject! Thank you all anyway !!!
angelmika91 said:
for information I also based on a second site in French where it was explained that it was necessary to first put the TWRP and after and only after unlocked the bootloader. In short, I lacked vigilance and concentration. Even on the French tutorial it was marked in red that it was incompatible Nougat. I read diagonally and made a mix with the other XDA tutorial. That's it I did not care. Do not fight lol The phone works is essential. Now I would like to know why I have a driver problem on my PC it seems to me but that's another subject! Thank you all anyway !!!
Click to expand...
Click to collapse
Glad you got your phone running again
angelmika91 said:
for information I also based on a second site in French where it was explained that it was necessary to first put the TWRP and after and only after unlocked the bootloader. In short, I lacked vigilance and concentration. Even on the French tutorial it was marked in red that it was incompatible Nougat. I read diagonally and made a mix with the other XDA tutorial. That's it I did not care. Do not fight lol The phone works is essential. Now I would like to know why I have a driver problem on my PC it seems to me but that's another subject! Thank you all anyway !!!
Click to expand...
Click to collapse
what kind of driver problem? EDL or mtp?
Honestly MTP works when it wants to work, so I can't help you if your PC doesn't recognize it. EDL is another matter though, pretty easy.

Sooo... I screwed up BIG TIME...

First of all, hello there community, all of you have already helped me so much and I really appreciate the effort that you put into this site to help guys like me out
Now onwards to my Problem:
I've had the P Smart for a couple of month when I considered using a Treble custom Rom (just to try it out and have some fun with it).
Since I didn't know how to flash GSI's I googled it and took the first step by step tutorial and followed it.
The Rom I flashed was the PixelExperience_arm64_a-8.1.0-20181015-0009-OFFICIAL.img.
Basically I flashed the rom via fastboot.
When I then realized that it wasn't quite what I expected I wanted to try out other roms.
So I went do dev-options and turned on ADB and OEM-Unlock but then... The OEM-Unlock option was greyed out.
f.
Since I came from stock I have had not yet installed TWRP.
I have searched the internet for hours and hours, day after day but I could not find a single option that could help me with my particular problem.
My current state:
- I have a rom that I do not longer want installed
- I do not have TWRP or any other custom-recovery installed
- In fastboot it says
"bootloader unlocked"
"FRP locked"
(My model is FIG-LX1 btw)
So, here I am and asking you guys for help.
Is there ANY possibility (aside from replacing the mainboard) to fix my phones current state?
Your help is really appeciated,
love y'all
kthxbye
the_darkest_knight said:
First of all, hello there community, all of you have already helped me so much and I really appreciate the effort that you put into this site to help guys like me out
Now onwards to my Problem:
I've had the P Smart for a couple of month when I considered using a Treble custom Rom (just to try it out and have some fun with it).
Since I didn't know how to flash GSI's I googled it and took the first step by step tutorial and followed it.
The Rom I flashed was the PixelExperience_arm64_a-8.1.0-20181015-0009-OFFICIAL.img.
Basically I flashed the rom via fastboot.
When I then realized that it wasn't quite what I expected I wanted to try out other roms.
So I went do dev-options and turned on ADB and OEM-Unlock but then... The OEM-Unlock option was greyed out.
f.
Since I came from stock I have had not yet installed TWRP.
I have searched the internet for hours and hours, day after day but I could not find a single option that could help me with my particular problem.
My current state:
- I have a rom that I do not longer want installed
- I do not have TWRP or any other custom-recovery installed
- In fastboot it says
"bootloader unlocked"
"FRP locked"
(My model is FIG-LX1 btw)
So, here I am and asking you guys for help.
Is there ANY possibility (aside from replacing the mainboard) to fix my phones current state?
Your help is really appeciated,
love y'all
kthxbye
Click to expand...
Click to collapse
You must sign in google account
leap_ahead said:
You must sign in google account
Click to expand...
Click to collapse
Did that already...
Erecovery, connects to wifi, reads the lastest rom from a server, installs it, wipes it all to stock
Hopefully that works
https://www.hardreset.info/devices/huawei/huawei-p-smart/recovery-mode/
redultra82 said:
Erecovery, connects to wifi, reads the lastest rom from a server, installs it, wipes it all to stock
Hopefully that works
https://www.hardreset.info/devices/huawei/huawei-p-smart/recovery-mode/
Click to expand...
Click to collapse
Tried that already, it can't connect to the update server. ("Getting package info failed").
Also I tried the dload method, but none of the update files that I tried seemed to work, it either goes to 5% or says "software install failed" (or both).
..
the_darkest_knight said:
Tried that already, it can't connect to the update server. ("Getting package info failed").
Also I tried the dload method, but none of the update files that I tried seemed to work, it either goes to 5% or says "software install failed" (or both).
Click to expand...
Click to collapse
I thought that was the be all of recovery, its never let me now
Hey dude i had ur same problem . All u need to do is use eRecovery and firmware finder through d's its easy
U this will guide you
https://www.google.tn/amp/s/forum.x...y-huawei-erecovery-solution-100-t3620165/amp/
let me know if you need further help
redultra82 said:
I thought that was the be all of recovery, its never let me now
Click to expand...
Click to collapse
I don't know why it doesn't work...
ilyes9999 said:
Hey dude i had ur same problem . All u need to do is use eRecovery and firmware finder through d's its easy
U this will guide you
https://www.google.tn/amp/s/forum.x...y-huawei-erecovery-solution-100-t3620165/amp/
let me know if you need further help
Click to expand...
Click to collapse
So I tried that out, but firstly I couldn't find a proper OEMINFO, and secondly I don't think I could flash it, since my OEM bootloader is still locked...
As I understood HWOTA doesn't support the P Smart (yet?), and it also needs the OEM to be unlocked
And without the OEMINFO it does not seem to work
the_darkest_knight said:
I don't know why it doesn't work...
So I tried that out, but firstly I couldn't find a proper OEMINFO, and secondly I don't think I could flash it, since my OEM bootloader is still locked...
As I understood HWOTA doesn't support the P Smart (yet?), and it also needs the OEM to be unlocked
And without the OEMINFO it does not seem to work
Click to expand...
Click to collapse
I don't know what you mean . All i know by my experience if you can access the eRecovery you can fix it even with locked bootloader
---------- Post added at 03:27 PM ---------- Previous post was at 03:25 PM ----------
And by the way when looking for a firmware for your device . You should use older versions and it should be the full ota update

Categories

Resources