Related
To all devs out there ,im been trying to root the hero for a week now ,ive tried every guide going also the gold card with 10 different sd cards with no luck.the rom what ive got is the release 2.73.405.66 rom.it has the new nboot is thats why i cant flash.is there any way i can wipe all date and software so i will have nothing on the phone and then install an earlier rom, its just an idea as im starting to lose it with this fone.i hope someone can help me or do i have to wait for the official update from htc
with this rom version you need to create a goldcard and downgrade your rom before you can install a custom rom. if you have problems with the goldcard you should be more specific.
waiting for the update doesn't seem like the best idea, because it might take some until a security flaw is found that allows to root the rom when already installed on the phone. if you have the custom recovery image you will be able to install the (pre-rooted) update short time after it was released.
You should be able to use fastboot for this issue.
Search around the forums, (also http://hero.modaco.com) and read about it.
All you need is the fasboot tool, a usb cable and the "debugging mode" switched on at ur phone...
everytime i create the gold card and try to downgrade the rom it states boot error 140.i follow the guides very indepth i get the serial number from the sdcard than i reverse the string and then replace the first two numbers or letters with 2 zeros how can you tell when the goldcard is on the sdcard.when i replace the sdcard back in sdcard reader it states that the folder is empty.im quite clued up on winmo but android is giving me a headache
wouldn't the fastboot give you the "remote: not allowed" error?
anyway, you can try:
start your phone by holding back and pushing power, you should see three skating androids. put recovery image in the folder where your fastboot.exe is, open terminal and go to that folder and type:
Code:
fastboot boot recovery-RA-hero-v1.5.3.1.img
if that works report back.
for the goldcard i can't help, never did it.
at last im rooted thanks for for the help .the way i did
(with the phone in normal mode)
1) Connect your Hero via usb to your pc/mac/...
2) Open Command Prompt ->
Put in the following text ->
C:\Users\Username> cd\
C:\>cd android\tools\
C:\>android\tools>adb push recovery-RA-Hero-v1.5.3.1.img /sdcard/recovery-RA-Hero-v1.5.3.1.img
C:\>android\tools>adb shell flash_image recovery /sdcard/recovery-RA-Hero-v1.5.3.1.img
3) JOB DONE!
rednose30 said:
at last im rooted thanks for for the help .the way i did
(with the phone in normal mode)
1) Connect your Hero via usb to your pc/mac/...
2) Open Command Prompt ->
Put in the following text ->
C:\Users\Username> cd\
C:\>cd android\tools\
C:\>android\tools>adb push recovery-RA-Hero-v1.5.3.1.img /sdcard/recovery-RA-Hero-v1.5.3.1.img
C:\>android\tools>adb shell flash_image recovery /sdcard/recovery-RA-Hero-v1.5.3.1.img
3) JOB DONE!
Click to expand...
Click to collapse
I guys, I seem to be having the same issue as the OP. Having tried the above it tells me that there is an error writing recovery: Permission denied. Any idea how to solve this?
Thanks!
mjames_84 said:
I guys, I seem to be having the same issue as the OP. Having tried the above it tells me that there is an error writing recovery: Permission denied. Any idea how to solve this?
Thanks!
Click to expand...
Click to collapse
Getting exactly the same. Tried the goldcard method numerous times using 3 different cards and always get the bootloader 140 error. Tried the above with same errors... very frustrating!
Mine is a UK T-Mobile G2 with build number 2.73.110.26, any suggestions gratefully tried!
Edit: Finally managed to sort it. I was using "RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe" - this didnt work. Once I found and tried RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe it all clicked into place!
Thanks for all the info provided on these forums, cheers!
TastyBurger said:
Getting exactly the same. Tried the goldcard method numerous times using 3 different cards and always get the bootloader 140 error. Tried the above with same errors... very frustrating!
Mine is a UK T-Mobile G2 with build number 2.73.110.26, any suggestions gratefully tried!
Edit: Finally managed to sort it. I was using "RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe" - this didnt work. Once I found and tried RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe it all clicked into place!
Thanks for all the info provided on these forums, cheers!
Click to expand...
Click to collapse
Hi
I have tried making a goldcard, and installed via. the RUU shown here.. 405.5 .. but then I tried using Flashrec to get another recovery image, it failed making the first step...
So is my phone rooted or did something go wrong ?
the phone is still unfortunately not rooted. I would've tried the fastboot method
Sent from my HTC Hero using the XDA mobile application powered by Tapatalk
just curious but did anyone just try to flash the older version without bothering with the goldcard...i dun know what i did to my htc hero orange but when i was researching i was told i needed to downgrade to root. I tried to take a long shot and used htc sync and old orange ruu..and somehow it just downgraded itself.... i know it might not help but its a long shot!
nicknyhk said:
just curious but did anyone just try to flash the older version without bothering with the goldcard...i dun know what i did to my htc hero orange but when i was researching i was told i needed to downgrade to root. I tried to take a long shot and used htc sync and old orange ruu..and somehow it just downgraded itself.... i know it might not help but its a long shot!
Click to expand...
Click to collapse
Very similar story. I did make a goldcard but hadn't got as far as finding out how to extract the update.zip out of the RUU exe, in order to use it. I tried running the RUU to see what would happen & my Hero downgraded.
hi, i have a problem with my N6P. it was unlocked, twrp flashed and running newest version of this ROM http://forum.xda-developers.com/nexus-6p/development/rom-debloated-prerooted-deoxeded-t3372600.
then, out of the blue, phone refused to work. when i'm trying to restart it, only option is boot to bootloader. i was trying to flash newest radio, bootloader, vendor and recovery - all failed with message "(remote: flash write failure)"
when i'm in bootloader mode, Andy Android is lying on his back, with no red exclamation point.
also there is written below Andy:
BL: K
Baseband: (empty)
Product/Variant: Angler-VN2
Serialn Number: (is present, but i think there is no need to write it)
CPU: MSM8994 0x20001
eMMC: 32GB Samsung
DRAM: 3072MB HYNIX LPDDR4
Console: NULL
Battery OK
Device is LOCKED
Qfuse Status: ENABLED
Off-Mode-charge: ENABLED
Download Mode: DISABLED
Connect USB Data Cable
strange thing is, that there is written "Device is LOCKED", because when wrote command "fastboot flashing unlock", there was a message:
...
(bootloader) Device already unlocked!
FAILED (remote failure)
I was able to fastboot boot boot.img, but it hanged on "Google" screen.
device is not visible after writing "adb devices", but is visible after writing "fastboot devices".
any ideas?
Might be a dumb question, but have you tried going back to stock Android N using Googles Factory Image in fastboot just to determine if your phone will still boot into os?
i'm downloading GFI, but 3 more hours left to finish download (unless there is a mirror server to download them). i'll probably try to do it, but i would like to avoid it because my backup is 2 months old :/
Fe Mike said:
Might be a dumb question, but have you tried going back to stock Android N using Googles Factory Image in fastboot just to determine if your phone will still boot into os?
Click to expand...
Click to collapse
tried this, no luck - still "remote flash write failure" message.
strange thing is, that i'm able to relock the bootloader (at least command "fastboot flashing lock" gave me possibility to do this {(YES/NO) message}, i didn't relocked it.
i've read, that this is probably fried emmc, but would it be possible to relock bootloader though?
miguelm75 said:
tried this, no luck - still "remote flash write failure" message.
strange thing is, that i'm able to relock the bootloader (at least command "fastboot flashing lock" gave me possibility to do this {(YES/NO) message}, i didn't relocked it.
i've read, that this is probably fried emmc, but would it be possible to relock bootloader though?
Click to expand...
Click to collapse
You might be right about fried emmc, have you tried placing a twrp.img in fastboot folder and run command fastboot boot twrp-x-x-x.img (not flash)? If it is fried can you rma?
Edit: I found this thread, second post has a link that may help. It is kinda advanced. The process can at least tell you if in fact emmc is bad and if it's not bad there may be a way of fixing it.
Fe Mike said:
You might be right about fried emmc, have you tried placing a twrp.img in fastboot folder and run command fastboot boot twrp-x-x-x.img (not flash)? If it is fried can you rma?
Edit: I found this thread, second post has a link that may help. It is kinda advanced. The process can at least tell you if in fact emmc is bad and if it's not bad there may be a way of fixing it.
Click to expand...
Click to collapse
1. i tried to flash recovery - no luck.
2. there will be problem with RMA, because i won this phone in a giveaway at AndroidAuthority.com and it has US warranty, so it would be rather expensive to send it to USA from Poland. but i will try to contact Huawei support in my country.
3. did you forgot to insert link to this thread?
miguelm75 said:
1. i tried to flash recovery - no luck.
2. there will be problem with RMA, because i won this phone in a giveaway at AndroidAuthority.com and it has US warranty, so it would be rather expensive to send it to USA from Poland. but i will try to contact Huawei support in my country.
3. did you forgot to insert link to this thread?
Click to expand...
Click to collapse
Yes I did, my bad.
https://www.google.com/amp/s/amp.re...here_a_way_to_check/?client=ms-android-google
Fe Mike said:
Yes I did, my bad.
https://www.google.com/amp/s/amp.re...here_a_way_to_check/?client=ms-android-google
Click to expand...
Click to collapse
thank you. unfortunatelly this is for LG devices. i can't find anything similiar for Huawei devices. i did tried Nexzus Root Toolki by Wug Fresh and i got the same error - "remote flash write failure"
so i think i will try to contact Huawei and local phone service to see, if they are able to fix it. thank you for your help.
Did you try to format data partition then flash the google image?
Iceburn1 said:
Did you try to format data partition then flash the google image?
Click to expand...
Click to collapse
i just did and received (remote: failed to erase partition) error.
miguelm75 said:
thank you. unfortunatelly this is for LG devices. i can't find anything similiar for Huawei devices. i did tried Nexzus Root Toolki by Wug Fresh and i got the same error - "remote flash write failure"
so i think i will try to contact Huawei and local phone service to see, if they are able to fix it. thank you for your help.
Click to expand...
Click to collapse
The op has an LG device but in second post there is a link (the one I'm posting now) for Qualcomm chipsets.
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
miguelm75 said:
tried this, no luck - still "remote flash write failure" message.
strange thing is, that i'm able to relock the bootloader (at least command "fastboot flashing lock" gave me possibility to do this {(YES/NO) message}, i didn't relocked it.
i've read, that this is probably fried emmc, but would it be possible to relock bootloader though?
Click to expand...
Click to collapse
Same thing just happened to me except I was just using my phone then it crashed and never came back tried for days to recover was able to re-lock bootloader but no other commands took. Had to RMA it back to Huawei took 3 weeks but it was covered by 12 month warranty so that's a plus
did you switch on find my phone in administer options before unlocking and flashing errors ?
rowihel2012 said:
did you switch on find my phone in administer options before unlocking and flashing errors ?
Click to expand...
Click to collapse
no, i didn't touch it.
Happened to me too while using it. I am still trying to save my data, but no luck for now.
Hi all,
Thinking about this phone, what is bootloader like, unlockable? Can fastboot be accessed?
Looked all over for info, most Chinese forums are bashing the phone, but the reason is not clear to me (seems mostly joking that it is just a knock off of the Nexus they produced). Chinese is not my first language, that is probably most of the problem.
I am interested in getting some development going on here, but I need to know if it is worth the trouble even trying. Huawei does release source, but it is really not easy to find. Also, source for this phone seems to not be released yet. If you google "huawei open source" you get some sources, but not for this device. If anyone can point me in a better direction I would appreciate it.
I followed step 1 of this guide: http://forum.xda-developers.com/showthread.php?p=68280798 to get my bootloader unlock code.
I haven't been able to find a version of TWRP for this phone yet and KingoRoot hasn't been able to achieve root either ?
Sent from my HUAWEI MLA-L03 using Tapatalk
You might try this for root: http://www.huaweishuaji.com/112.html
Supports many other Huawei devices, but I cannot guarantee as I have never used it, so use at your own risk. There are also some Chinese guides for unbricking out there. It involves putting the stock image onto the external SD card and running a flash from the phone. Seems it would be fairly easy to build TWRP for the the device if there was a little more info about it, such as partitions. Unfortunately, I do not have the device and need to upgrade my PC before I can start building anything again.
Bored today, so been digging. Seems it would be fairly easy to port the zenfone 3 twrp over, as the specs are similar.
I can't try to build as I need to upgrade, and don't have the phone to test anyway.
Here is the git, looks like only a few changes to make: https://github.com/shakalaca/android_device_asus_ze520kl
Here is a link with how to flash the zenfone: http://www.asus-zenfone.com/2016/10/how-to-root-asus-zenfone-3-ze520kl-and.html
If it was me I would give it a go booting the z017d one, but make sure you "fastboot boot filename.img" and not flash. I would take the risk, but not saying anyone else should.
Not going to have anything to build with until around Christmas, so hopefully someone can give it a go building for the phone. I might get the phone around Christmas too, lets see how development goes.
can anyone try to load the twrp from p9 lite? The hardware specs are just as much the same
"fastboot boot recovery recovery_twrp.img"
maybe it works...
It's a no go booting either of those recoveries. Each flash while successful, ends in a boot loop.
I also don't have the time right now to dedicate to build TWRP from source.
Sent from my HUAWEI MLA-L03 using Tapatalk
thisizM1 said:
I followed step 1 of this guide: http://forum.xda-developers.com/showthread.php?p=68280798 to get my bootloader unlock code.
I haven't been able to find a version of TWRP for this phone yet and KingoRoot hasn't been able to achieve root either
Sent from my HUAWEI MLA-L03 using Tapatalk
Click to expand...
Click to collapse
Mine was bricked after trying the KingoRoot. Any chance I can unbrick it somehow?
P/S: Yes I am an idjit because I didn't make any kind of backup. :crying::crying:
Seems the Huawei unlock code generator is down. I entered my phones data, but the unlock code never appears. I only get an error message when I enter wrong data (i.e., CAN-L11 instead of HUAWEI CAN-L11), so seems the data is validated. When did you create your code, @wangdaning?
Regards,
sebastian
Don't have the phone, I think an earlier poster did get an unlock. I was speculating about what might be possible.
wangdaning said:
Don't have the phone, I think an earlier poster did get an unlock. I was speculating about what might be possible.
Click to expand...
Click to collapse
Sorry, my fault. thisisMZ1 was the lucky guy with the unlock code.
@thisisMZ1: did you try to boot the image without flashing it first? Don´t know if that makes a difference, but one never knows.
For the unlock code, I got an unhelpful reply from the support team ("please use the form provided on..."). My replies on this haven´t been answered yet, so I´m waiting... Will keep you updated.
Regards,
Sebastian
Hi again,
I managed to unlock the bootloader: I created the Huawei ID on the wron (Asian) website. I created a new ID via the German website and was able to use the website for unlocking code with the new ID.
Regards,
Sebastian
sebixvi said:
Sorry, my fault. thisisMZ1 was the lucky guy with the unlock code.
@thisisMZ1: did you try to boot the image without flashing it first? Don´t know if that makes a difference, but one never knows.
For the unlock code, I got an unhelpful reply from the support team ("please use the form provided on..."). My replies on this haven´t been answered yet, so I´m waiting... Will keep you updated.
Regards,
Sebastian
Click to expand...
Click to collapse
I tried both, booting and flashing, neither worked.
Sent from my Nexus 6P using Tapatalk
sebixvi said:
Hi again,
I managed to unlock the bootloader: I created the Huawei ID on the wron (Asian) website. I created a new ID via the German website and was able to use the website for unlocking code with the new ID.
Regards,
Sebastian
Click to expand...
Click to collapse
Hi,
could you leave us the links to the websites you used? Thank.
TWRP has been released in Chinese http://www.netded.com/a/jingpinshouji/2016/1108/32373.html
m00h said:
Hi,
could you leave us the links to the websites you used? Thank.
Click to expand...
Click to collapse
https://uniportal.huawei.com/accounts/register.do?method=toRegister®siterMethod=byPhone ist the page I used to create my ID.
Regards,
Sebastian
wangdaning said:
TWRP has been released in Chinese http://www.netded.com/a/jingpinshouji/2016/1108/32373.html
Click to expand...
Click to collapse
i installed this on my Nova Plus and then changed the language to english
works, however when trying to backup the files it says invalid argument. no matter what it tries to mount
soliditalstud said:
i installed this on my Nova Plus and then changed the language to english
works, however when trying to backup the files it says invalid argument. no matter what it tries to mount
Click to expand...
Click to collapse
Wonder if it is only for the nova and not the nova plus. I did not make it and have neither phone to test, just passing it along. Unfortunately, they seem to have not used github.
Does anyone have a link to the factory recovery.img?
I flashed the Recovery to the Nova (not the plus) and I got exactly the same error. If I try to flash the superSU, I got a error that it couldnt Mount data and after a Reboot the root doesnt work.
I guess their could be several variants of the phone, which does not bod well for hopes of development.
Something new?
The chinese recovery boots but has problems to mount the partitions.... Its for the CAN-L01 and on my CAN-L11 is a different fstab. I have not the skills to compile a working one.
I have successfully booted the rr 7.1.2 rom from 4pda on my device every thing seems very well except in performance its much slower than the stuck firmware , also i have check the antutu score and it get lower by 10k points , i have check the gpu with another app and the working percent was stuck at 0%
So if any one could help fixing the hwc , kernel , hw coding and decoding,, it will make the device fly again
fir1996 said:
I have successfully booted the rr 7.1.2 rom from 4pda on my device every thing seems very well except in performance its much slower than the stuck firmware , also i have check the antutu score and it get lower by 10k points , i have check the gpu with another app and the working percent was stuck at 0%
So if any one could help fixing the hwc , kernel , hw coding and decoding,, it will make the device fly again
Click to expand...
Click to collapse
I have been trying to get this room to work but failed everytime, because of the encryption.
Everytime I get decryption successful but something went wrong. As far as I understand the encryption should be disabled on this ROM completely, but I can't get it done. I tried reformatting data to ext4 but that didn't work.
Edit: The problem was that I was using Magisk as root solution. I tried with the provided SuperSU and it all worked.
My device runs well with rr. I only notice the performance issue on startup, right after but the phone is very slow.
I noticed that there is no swap memory use in this ROM, while in stock there was a deal memory partition.
I'll try to figure out if we can enable it in this ROM. That might improve performance.
JudgeDread11 said:
I have been trying to get this room to work but failed everytime, because of the encryption.
Everytime I get decryption successful but something went wrong. As far as I understand the encryption should be disabled on this ROM completely, but I can't get it done. I tried reformatting data to ext4 but that didn't work.
Edit: The problem was that I was using Magisk as root solution. I tried with the provided SuperSU and it all worked.
My device runs well with rr. I only notice the performance issue on startup, right after but the phone is very slow.
I noticed that there is no swap memory use in this ROM, while in stock there was a deal memory partition.
I'll try to figure out if we can enable it in this ROM. That might improve performance.
Click to expand...
Click to collapse
Don't mean to hijack this thread but im desperate. Im trying to root mt MYA L22 but can't seem to find the right instructions. Posted here two times but no one is replying. Could you tell me how you unlocked bootloader on your phone? I already have the code from Huawei website. I am stuck at the cmd prompt when i type "list adb devices" from a cmd prompt opened through the adb and fastboot folder that ive downloaded. It says adb devices attached but shows nothing after that, basically an empty list. Any advice would be greatly appreciated!
Dylan2232 said:
Don't mean to hijack this thread but im desperate. Im trying to root mt MYA L22 but can't seem to find the right instructions. Posted here two times but no one is replying. Could you tell me how you unlocked bootloader on your phone? I already have the code from Huawei website. I am stuck at the cmd prompt when i type "list adb devices" from a cmd prompt opened through the adb and fastboot folder that ive downloaded. It says adb devices attached but shows nothing after that, basically an empty list. Any advice would be greatly appreciated!
Click to expand...
Click to collapse
It was a long time ago since I setup fastboot and ADB. I used this thread
https://forum.xda-developers.com/showthread.php?t=2277112&page=53
JudgeDread11 said:
It was a long time ago since I setup fastboot and ADB. I used this thread
https://forum.xda-developers.com/showthread.php?t=2277112&page=53
Click to expand...
Click to collapse
I went through that thread. I understand you rooted it but then started having problems? Like you couldn't download? Where you able to solve those problems? Now I am worried to root it.
Dylan2232 said:
I went through that thread. I understand you rooted it but then started having problems? Like you couldn't download? Where you able to solve those problems? Now I am worried to root it.
Click to expand...
Click to collapse
I'm not sure which post you saw, but I think my post on there were with an other device and yes, I have never bricked a device unrecoverable (yet).
That said, you will always be taking a risk when rooting or trying custom ROMS.
Then again if you never take risks you won't get anywhere. The question is how much are you willing to risk. In this case are you willing to risk your phone for the extra possibilities you might get when rooting it
First think you need to do before modifying anything is learning how to backup and restore.
JudgeDread11 said:
I'm not sure which post you saw, but I think my post on there were with an other device and yes, I have never bricked a device unrecoverable (yet).
That said, you will always be taking a risk when rooting or trying custom ROMS.
Then again if you never take risks you won't get anywhere. The question is how much are you willing to risk. In this case are you willing to risk your phone for the extra possibilities you might get when rooting it
First think you need to do before modifying any freething is learning how to backup and restore.
Click to expand...
Click to collapse
Thanks JudgeDread. Yes, I've rooted several phones in my life time. I understand the risk, but I tend to research about that particular rooting method with my phone before going ahead and doing it. I feel like the rooting method for my phone is particularly more risky, not because of what I read but rather from what info I am NOT able to find. Did you have a Huwaei Y5 2017 MYA l22 that you rooted successfully without issues? Can you point me to the instructions? That thread is a bit confusing.
Dylan2232 said:
Thanks JudgeDread. Yes, I've rooted several phones in my life time. I understand the risk, but I tend to research about that particular rooting method with my phone before going ahead and doing it. I feel like the rooting method for my phone is particularly more risky, not because of what I read but rather from what info I am NOT able to find. Did you have a Huwaei Y5 2017 MYA l22 that you rooted successfully without issues? Can you point me to the instructions? That thread is a bit confusing.
Click to expand...
Click to collapse
Yes exact same model, rooted and after several tries custom ROM.
I unlocked using the official method and then flashed TWRP in the recovery partition.
The difficulty was to get back into TWRP after rebooting. So I would advice to immediately install a root solution. I used Magisk. While root works without problem Magisk modules will only work if you use the f2fs workaround.
I am now running Resurrection remix (Android 7.1.2) without many issues. Only every now and then a forced close of the system UI.
It took some time to get it running. Because I used a different root solution the provided on the same page as the ROM. So on install use the provided SuperSU. After install you can change of you want.
Also the patches are needed. I still have bad videos on YouTube but haven't looked into the issue much yet.
hi , good news for Huawei y5 2017(MYA-L22) users.
Download latest lineage14.
visit to my blog.
cheers
https://p55novo.blogspot.com/2018/07...e-141-for.html
JudgeDread11 said:
Yes exact same model, rooted and after several tries custom ROM.
I unlocked using the official method and then flashed TWRP in the recovery partition.
The difficulty was to get back into TWRP after rebooting. So I would advice to immediately install a root solution. I used Magisk. While root works without problem Magisk modules will only work if you use the f2fs workaround.
I am now running Resurrection remix (Android 7.1.2) without many issues. Only every now and then a forced close of the system UI.
It took some time to get it running. Because I used a different root solution the provided on the same page as the ROM. So on install use the provided SuperSU. After install you can change of you want.
Also the patches are needed. I still have bad videos on YouTube but haven't looked into the issue much yet.
Click to expand...
Click to collapse
Thanks again for replying. Unfortunately though, 80 percent of what you just said flew over my head
I am not an expert but I can follow instructions! Any step by step guide on how to root it? So far I've gotten the unlock code from Huawei. I downloaded the ADB and fast boot folder and launched from that folder the cmd prompt. I type in "list of ADB deviced" and below comes an empty list. Please share what you did.
Dylan2232 said:
Thanks again for replying. Unfortunately though, 80 percent of what you just said flew over my head
I am not an expert but I can follow instructions! Any step by step guide on how to root it? So far I've gotten the unlock code from Huawei. I downloaded the ADB and fast boot folder and launched from that folder the cmd prompt. I type in "list of ADB deviced" and below comes an empty list. Please share what you did.
Click to expand...
Click to collapse
For rooting you need unlocked bootloader ( if you don't do ir then below won't work).
1)download the 4pda app from google play store and register an account .
2) download the TWRP.img file from 4pda website here is the link
https://4pda.ru/forum/index.php?showtopic=823938&view=findpost&p=74424572
3) enable developer mode in your phone by going to setting about phone , tap 6 times on the build number.
4)go to developer mode and enable usb debugging and oem factory unlock .
5) go to your pc install adb here link https://forum.xda-developers.com/showthread.php?t=2588979
6) now conect the phone to the pc and run cmd , type adb reboot bootloader . (Your device ahould restart and enter bootloader mode (white screen)).
7) now take the TWRP.img (must be copyied to desktop ) and type in cmd cd desktop.
8) type fastboot flash recovery TWRP.img (change the file name to TWRP ).
9) type fastboot reboot.
Now you have successfully install TWRP on your device.
Continue... If replied
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