Related
Hi guys, hoping someone can help me here.
My Nexus 7 is stuck on the Google logo after trying to update to Lollipop using the Nexus Root toolkit.
It will boot into fastboot with this underneath:
Product name - grouper
Variant - grouper
MW version - ER3
Bootloader Version - 4.23
Baseband version - N/A
Serial Number -
Signing - not yet defined
Lock state - unlocked
I have tried a few things so far like using the root toolkit to root it, using the flash stock & unroot on soft brick setting, it'll download the package etc but when it comes to install them on the device it keeps coming back as failed on everything.
I also tried using the Minimal ADB & Fastboot from this thread here http://forum.xda-developers.com/showthread.php?t=2317790 to erase boot, cache, recovery, system data & user data all which come back as FAILED.
Is my Nexus beyond repair, or is there any chance I can bring it back from the dead.
Thanks :good:
Bandit1988 said:
Hi guys, hoping someone can help me here.
My Nexus 7 is stuck on the Google logo after trying to update to Lollipop using the Nexus Root toolkit.
It will boot into fastboot with this underneath:
Product name - grouper
Variant - grouper
MW version - ER3
Bootloader Version - 4.23
Baseband version - N/A
Serial Number -
Signing - not yet defined
Lock state - unlocked
I have tried a few things so far like using the root toolkit to root it, using the flash stock & unroot on soft brick setting, it'll download the package etc but when it comes to install them on the device it keeps coming back as failed on everything.
I also tried using the Minimal ADB & Fastboot from this thread here http://forum.xda-developers.com/showthread.php?t=2317790 to erase boot, cache, recovery, system data & user data all which come back as FAILED.
Is my Nexus beyond repair, or is there any chance I can bring it back from the dead.
Thanks :good:
Click to expand...
Click to collapse
Why did you try 'erase' commands on flashboot, instead of trying to flash the system/boot/cache and recovery stock partitions from the factory image? (just wondering). I think the problem you have may be that the toolkit failed to flash the bootloader and so the process stopped and didn't flash any other parition? We can't know for sure I think because the stock images bootloaders for grouper are ****ed hard mostly and all of them from 4.3? onwards have the same version 4.23 wrong labeled (source) :S
NEVER USE TOOLKITS, they can mess up the phone hard.. In your case I think you shouldn't have any problem to flash the system/boot/cache and recovery stock partitions from the stock factory image, or at least I'd try that. But do not touch the bootloader whatever you do!!!
Also for 5.0 and onwards you needed the 1.2 version of Minimal ADB and Fastboot, I think, be sure ur not using another one.
I don't have an unlocked bootloader and i flashed the CWM. Now when i try to enter the recovery mode with buttons, nothing happens just turns the phone on normally. I searched for stock recoveries, but didn't found nothing.
I have GRA-L09, B200, Europe Open
Thanks for help!
To get an unlocked bootloader you must go to settings> about phone> build number
and then press build number 7 times
after you did that exit out of about phone then click on the newly-appeared 'developer settings'
there you should find OEM Unlocking and Enable USB Debugging
You'll get it from there.
I have the Dev Ops, but don't have OEM unlock.
But shouldn't you already have an unlocked bootloader to have DevOps?
Don't know. I don't typed any code in to unlock bootloader.
Are you sure you have DevOps?
---------- Post added at 01:58 PM ---------- Previous post was at 01:55 PM ----------
And also try to do it not with buttons, but with your computer
I don't know the script for how to boot into recovery mode but to fastboot, for example, you'd type in >fastboot
when your phone is connected to your PC via USB.
Y'know, just search up 'How to use Recovery Mode' - maybe you just did it wrong
Didn't tryed it w/ adb yet.
ADB didn't worked. I'm trying a full hard reset..
Hard reset didn't do nothing. HELP PLS!!
adb reboot-bootloader worked, but it has a subtitle: Phone Locked (with red). What is it?
TheGolem said:
adb reboot-bootloader worked, but it has a subtitle: Phone Locked (with red). What is it?
Click to expand...
Click to collapse
That means you have a locked bootloader, so CWM didn't install successfully.
In other words, you need to unlock the bootloader first in order to successfully install CWM.
So, 1st step - visit the Huawei unlocking code request page, taking your time to fill in the form accurately & submit it.
[Btw, if you don't already have a Huawei ID, you can register for one here: http://www-file.huawei.com/en/my-huawei/register
Then use these login details in the above link to request for the unlock code]
2nd step: Once you receive the unlock code from them, use it to unlock the bootloader by issuing the following command in fastboot mode [the asterisks (*) represent your 16-digit unlock code]:
Code:
fastboot oem unlock ****************
Now you can attempt to install CWM. Where are you getting the CWM img file from?
GaT7 said:
That means you have a locked bootloader, so CWM didn't install successfully.
In other words, you need to unlock the bootloader first in order to successfully install CWM.
So, 1st step - visit the Huawei unlocking code request page, taking your time to fill in the form accurately & submit it.
[Btw, if you don't already have a Huawei ID, you can register for one here: http://www-file.huawei.com/en/my-huawei/register
Then use these login details in the above link to request for the unlock code]
2nd step: Once you receive the unlock code from them, use it to unlock the bootloader by issuing the following command in fastboot mode [the asterisks (*) represent your 16-digit unlock code]:
Code:
fastboot oem unlock ****************
Now you can attempt to install CWM. Where are you getting the CWM img file from?
Click to expand...
Click to collapse
Sorry, "Phone Unlocked" with red
TheGolem said:
Sorry, "Phone Unlocked" with red
Click to expand...
Click to collapse
Ok, so it appears you may have corrupted the recovery partition.
Is the phone otherwise booting into the system & functioning normally?
Also, can you tell us what you are wanting to ultimately achieve by installing CWM?
Just to confirm the bootloader is unlocked, run this command in fastboot mode & let us know the result:
Code:
fastboot oem get-bootinfo
Ok, I just read your post in the other thread about wanting to update B200 to B370.
TheGolem said:
I have b200 but can't install it [B370]. Why?
Early flashed the CWM with flashify succesfully, but don't have unlocked bootloader. And if i try to enter recovery mode, nothing happens. Is it possible, that i cant' install it because of this?
Click to expand...
Click to collapse
As the guys already said, you do not need to install anything in order to update an official rom.
So, let's leave out CWM, bootloaders, etc for now, & help you update only from B200.
When you try using TopperBG's method to update, what happens?
What is your current FULL firmware version? It will be in this format: GRA-L09CxxxB200 - if everything else is as I've mentioned, I'm interested in the Cxxx part.
GaT7 said:
Ok, I just read your post in the other thread about wanting to update B200 to B370.
As the guys already said, you do not need to install anything in order to update an official rom.
So, let's leave out CWM, bootloaders, etc for now, & help you update only from B200.
When you try using TopperBG's method to update, what happens?
What is your current FULL firmware version? It will be in this format: GRA-L09CxxxB200 - if everything else is as I've mentioned, I'm interested in the Cxxx part.
Click to expand...
Click to collapse
Update succeed, it wroks fine. The problem is with the recovery mode.
When i'm trying the button method to enter recover, the phone just normally turns on. When still hold the buttons, black screen. It's with the abd too.
TheGolem said:
adb reboot-bootloader worked, but it has a subtitle: Phone Locked (with red). What is it?
Click to expand...
Click to collapse
you don't have a unlocked bootloader so you can't have cwm
I said it wrong:
-Android 5 succeed
-If i try to install Android 6
https://forum.xda-developers.com/huawei-p8/how-to/emui4-0-1-p8-official-marshmallow-6-0-t3417212
or enter recovery mode, then happens the black screen.
TheGolem said:
I said it wrong:
-Android 5 succeed
-If i try to install Android 6
https://forum.xda-developers.com/huawei-p8/how-to/emui4-0-1-p8-official-marshmallow-6-0-t3417212
or enter recovery mode, then happens the black screen.
Click to expand...
Click to collapse
1. You need to install stock recovery for android 5(unlocked bootloader is required).
2. Then you can use the dload method to update.
3. You can flash TWRP after that because no-one uses CWM.
GaT7 said:
Ok, so it appears you may have corrupted the recovery partition.
Is the phone otherwise booting into the system & functioning normally?
Also, can you tell us what you are wanting to ultimately achieve by installing CWM?
Just to confirm the bootloader is unlocked, run this command in fastboot mode & let us know the result:
Code:
fastboot oem get-bootinfo
Click to expand...
Click to collapse
Phone normally booting, no problem with current system.
I typed in the command, and its <waiting for device>.
GaT7 said:
Where are you getting the CWM img file from?
Click to expand...
Click to collapse
http://www.teamandroid.com/2015/06/07/install-huawei-p8-clockworkmod-recovery/2/
Step 5
cwm-p8-nogui.img
This thread will be for the Canadian version of ZE552KL, and will be updated with specific info relevant to Z012DC model found in Canada (Canada Computers, Staples, other retailers). It has WW SKU number.
It took me a while and some searching to figure all steps out. I also modified Asus N and M firmware to remove version checks. Without this step - i was stuck with error 7 in TWRP. The only difference between Z012D and Z012DC seems to be in Fastboot and ADB drivers, TWRP recovery, system images seem to work well so far.
Steps:
1. Download Fastboot and ADB Drivers. For me usb driver on ZE552KL Asus download page didn't work. Select "Only install driver", you do not need to update your drivers via DRP.
Fastboot driver (for Vendor VID_18D1&PID_D00D): http://drivers.drp.su/Telephone/Hua...03.00/Huawei-FORCED-Allx64-2.00.03.00-drp.exe
ADB Driver (for VID_18D1&PID_D002): http://drivers.drp.su/Telephone/Leshcat/WinAll/Leshcat-WinAll-drp.exe
2. Save the following files on your External SD Card:
Modified M image UL-ASUS_Z012D-WW-13.20.10.152-user.zip
Modified N image UL-ASUS_Z012D-WW-14.2015.1701.8-user.zip
SuperSU - latest version from here
no-verity-opt-encrypt-5-1.zip. Give thanks to @kaffeine1 , without him - we would all be stuck with black screens
3. Save ADB and Fastboot files on your computer, and extract; give thanks to @snowwolf725
4. Download newer recovery (TWRP 3.1.0) from here
5. Unlock bootloader via unofficial unlock method; give thanks to @snowwolf725
6. Get into fastboot by turning off the phone, and pressing volume up + power. Install recovery that you downloaded in step #4:
Code:
fastboot flash recovery twrp-3.1.0-0-Z012D.img
7. Follow the steps this guide by @kaffeine1 . Skip the steps of downloading Nougat and Marshmallow firmware from Asus site, as you have already downloaded and saved both firmwares in Step #2 . Also skip the last step - do not reboot into Nougat, but go back to fastboot mode.
8. Root Nougat - follow steps under #2 here:
https://forum.xda-developers.com/zenfone-3/how-to/twrp-recovery-3-0-2-root-zenfone-3-t3569926
How to update to the latest version of OS:
1. Go to Asus Site, download latest WW image UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip
2. Extract UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip\META-INF\com\google\android\updater_script , edit, remove first two lines, and put back into the zip file (e.g. using 7zip)
3. Extract from above zip file boot.img , and flash it via: fastboot flash boot boot.img
4. Flash recovery: fastboot flash recovery twrp-3.1.0-0-Z012D.img
5. Reboot into recovery, and flash:
- Firmware that you modified in #2
- no-verity-opt-encrypt-5.1.zip
- Latest SuperSU
- Rooted.zip (from step #8 above)
6. Reboot mobile, and enjoy new version!
Phone info as purchased:
Model Number: ASUS_Z012DC
Android version: 6.0.1
Baseband version: M3.10.42-Libra_080001
Build number: MMB29P.WW_Phone-13.20.10.152-20161222
Manufacture date (on the box): January 2017
Latest version - UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip
Model Number: ASUS_Z012DC
Android version: 7.0
Baseband version: M3.10.47-Libra_080001
Build number: NRD90M.WW_Phone-14.2020.1703.28-20170410
Special thanks to:
- @jcadduono for TWRP recovery
- @snowwolf725 for guide unlock bootloader
- @kaffeine1 for guide how to upgrade to N from M
Reserved for future use
can i follow this step for ZE520KL ?
I got my self a canadian vertion ZE552KL, but i can´t seem to fully unlock the boot loader, it goes onto fastboot, but it does not allow me to flash anything it gives a permision denied .
when i tried to flash fw from sdcard gives a error: the the sku is "WW_" and mine is ""
have you came across this problem.
how can it be solved?
thanks
lastremnant said:
can i follow this step for ZE520KL ?
Click to expand...
Click to collapse
no, I do not think so. these are different phones.
DilipRB said:
I got my self a canadian vertion ZE552KL, but i can´t seem to fully unlock the boot loader, it goes onto fastboot, but it does not allow me to flash anything it gives a permision denied .
when i tried to flash fw from sdcard gives a error: the the sku is "WW_" and mine is ""
have you came across this problem.
how can it be solved?
thanks
Click to expand...
Click to collapse
try first flashing 6.0.1 firmware from asus site and then modified 7.0 firmware. if the error is when flashing 6.0 fw - try modified 6.0. and do paste specific rrror.
anterus said:
no, I do not think so. these are different phones.
Click to expand...
Click to collapse
nevermind sir, it worked for me
Strange things do happen!!!
anterus said:
try first flashing 6.0.1 firmware from asus site and then modified 7.0 firmware. if the error is when flashing 6.0 fw - try modified 6.0. and do paste specific rrror.
Click to expand...
Click to collapse
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
DilipRB said:
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
Click to expand...
Click to collapse
backup those zips, open with winrar or another app. open meta-inf/android/google/updater-script with notepad++ try deleting from ifelse until ) );
save and let winrar save new update
lastremnant said:
backup those zips, open with winrar or another app. open meta-inf/android/google/updater-script with notepad++ try deleting from ifelse until ) );
save and let winrar save new update
Click to expand...
Click to collapse
Tryed that, and got footer error...
seems that to modifying the script file and then recompresing will change the compretion check algorithem. giving a footer error.
i should try pakaging the apk again...
there was a program to do so but i cant recall which...
thks
DilipRB said:
Tryed that, and got footer error...
seems that to modifying the script file and then recompresing will change the compretion check algorithem. giving a footer error.
i should try pakaging the apk again...
there was a program to do so but i cant recall which...
thks
Click to expand...
Click to collapse
i found it ...
apktool from :
https://forum.xda-developers.com/showthread.php?t=1989533
Sorry this was for apks... but i guess same principle aplies... when i can i shall try and post the outcome
DilipRB said:
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
Click to expand...
Click to collapse
I noticed that in some cases TWRP doesn't "stick", and gets overridden by default bootloader. Specific check is essentially useless - just to prevent flash of improper image. Just remove the check in the new FW, or use modified FW that has the check removed. I think in your case you can just re-flash TWRP since your bootloader is unlocked?
I tryed several TWRP 3.02 and 3.10 if a boot imge ... if entered bootloader with volum key + power it says all ok but booting never happens... if i enter bootloader trough adb it stucks until i disconnect and reconnect usb cable. when trying to flash. fast boot returns error not have permision and side load error secttion 7 on UL modified or else footer w
error after passing check. i shall try modiffying UL 13.20.10 and see what happens
DilipRB said:
I tryed several TWRP 3.02 and 3.10 if a boot imge ... if entered bootloader with volum key + power it says all ok but booting never happens... if i enter bootloader trough adb it stucks until i disconnect and reconnect usb cable. when trying to flash. fast boot returns error not have permision and side load error secttion 7 on UL modified or else footer w
error after passing check. i shall try modiffying UL 13.20.10 and see what happens
Click to expand...
Click to collapse
flash modified images through twrp - with links in OP
Well my wife liked the phone so much, that she "kindly requested" me to gift it to her... now she is the proud owner of a canadian vertion of ZE552KL and i got myself a ZS570KL
thanks a lot for all your help.
P.D. : i think she was not happy with the time i was spending with the device.
I know this is going to sound super dumb, but the unofficial bootloader unlock still triggers the bootup message and voids the warranty, right?
This might be even dumber... But my guess is that the official app to unlock boot loader, does more than unlock,
My guess is that it also register with asus mobile, the fact that for your device has been unlocked...
DilipRB said:
This might be even dumber... But my guess is that the official app to unlock boot loader, does more than unlock,
My guess is that it also register with asus mobile, the fact that for your device has been unlocked...
Click to expand...
Click to collapse
That's what some manufacturers do, like Motorola and HTC. But from back when I unlocked the BL on my Zenfone 2 Laser, I remember that all it did (as far as I could tell) was unlock the bootloader and set a flag in the bootloader that made it say it was unlocked that couldn't be reversed. No need for fancy registration systems when you can just boot up the phone and take a look.
What was modified in your N-image firmware file? There is now a newer version that I'd like to install. Can you provide an updated modified file for version WW-14.2020.1703.28 or give the steps needed to modify it myself?
Jarrick said:
What was modified in your N-image firmware file? There is now a newer version that I'd like to install. Can you provide an updated modified file for version WW-14.2020.1703.28 or give the steps needed to modify it myself?
Click to expand...
Click to collapse
Updated OP with instructions regarding how to upgrade to the latest version of N - just tested steps myself. Should be applicable to all future versions of N posted on Asus site. Enjoy!
Hi!
I need some help rooting my Nokia 6 Mobile phone
The model number is TA- 1033
I have tried all kinds of different sources as a guide, but all failed for me.
I tried several one-click root tools as well. (Kingroot, Kingo Root)
I have tried to unlock the bootloader with Fastboot and ADB for the TWRP recovery flash
I have got developer options and also enabled USB Debugging and OEM unlocking ut the procedure still fail all the time.
I've tied to flash the TWRP without unlocking the bootloader but that ailed as well.
My device is not bricked yet.
Thank you for your help
My attempts to root were successful only on Nougat (Not Oreo, because of bootloader)
Make a backup of all your important files in your phone.
Download OST and with it install this stock rom (https://mega.nz/#!5ccRnb4b!VsgiKQ4CjxFyjbjcxR0esjeKmHZsUTnEz0FA_FMZQbM)
(To install it, you need the phone in bootloader mode.)
If it displays an error the first time, try again until the installation is fully successful.
Once the phone is turned on, the first thing you need to do is turn off automatic software updates. Know that if you want root, you should forget about OTA updates.
Once all written above is done remains to unlock the bootloader and installing TWRP.
For that..
Enter in bootloader mode.
Use Fastboot from your PC and enter this command to allow the partitions to be changed on your phone.
(To get MD5 of your serial number, use this website: http://www.miraclesalad.com/webtools/md5.php)
fastboot oem dm-verity [MD5_of_your_device_serial_number]
(Example: fastboot oem dm-verity 5f47b9a8dc1da1873c12945cf806691e)
After that download this bootloader(http://pc.cd/xUFrtalK) and flash it:
fastboot flash aboot D1C-emmc_appsboot.mbn
(Make sure that downloaded bootloader is located in adb/fastboot folder)[Or you can type full file path of bootloader(Example: "C:\Users\Martin\Downloads\D1C-emmc_appsboot.mbn")]
(This to flash an unlocked bootloader.)
fastboot reboot-bootloader
(This is to reboot for using new unlocked bootloader.)
fastboot oem dm-verity [MD5_of_your_device_serial_number]
(Again to allow installing partitions.)
Download recovery from here: https://mega.nz/#F!K1k0gC5C!xpw3-AQvSQJ5p6VWX19gpA)
Flash it with this command:
fastboot flash recovery nokia-6-ta-1000-8_0-twrp3.2.1-7to-recovery-magisk-root-2018.3.15.img
(Make sure that downloaded recovery is located in adb/fastboot folder)[Or you can type full file path of twrp recovery(Example: "C:\Users\Martin\Downloads\nokia-6-ta-1000-8_0-twrp3.2.1-7to-recovery-magisk-root-2018.3.15.img")]
After that reboot to twrp recovery and flash Magisk ROOT.
All is done.
Magisk is built in recovery. You don't need to download it from internet. Flash magisk which is in recovery.
Warning: After opening magisk manager you can update app but you can't update magisk version (core). Because latest version cause bootloop on ours devices. Use 16.1 version which is in recovery build it.
I hope everything will be fine. Good luck!
Hi! I have some issues.
marto2013 said:
My attempts to root were successful only on Nougat (Not Oreo, because of bootloader)
Make a backup of all your important files in your phone.
Download OST and with it install this stock rom
Click to expand...
Click to collapse
Okay
So when I tried to flash the rom you gave me it failed with a download error. I tried to use OST LA 6.0.4 and 6.1.2 but both failed.
Clicking on the "Edit phone information" didn't work either. Can you help me in this situation? I have tried to reinstall OST LA several times, but it didn't resolve the problem.
VargaTibor1 said:
Okay
So when I tried to flash the rom you gave me it failed with a download error. I tried to use OST LA 6.0.4 and 6.1.2 but both failed.
Clicking on the "Edit phone information" didn't work either. Can you help me in this situation? I have tried to reinstall OST LA several times, but it didn't resolve the problem.
Click to expand...
Click to collapse
On which patch level are you?
ZeroPointMax said:
On which patch level are you?
Click to expand...
Click to collapse
I am on Patch Level: 1 November 2018
Android version 8.1.0
Build number 00WW_5_580_SP08
VargaTibor1 said:
I am on Patch Level: 1 November 2018
Android version 8.1.0
Build number 00WW_5_580_SP08
Click to expand...
Click to collapse
That means you cannot use OST LA or oem-veracity. Nokia changed the algorithm with August patch. You can basically not root your phone anymore using this method.
ZeroPointMax said:
That means you cannot use OST LA or oem-veracity. Nokia changed the algorithm with August patch. You can basically not root your phone anymore using this method.
Click to expand...
Click to collapse
He can downgrade his bootloader using older OTA update.
=====
VargaTibor1 said:
I am on Patch Level: 1 November 2018
Android version 8.1.0
Build number 00WW_5_580_SP08
Click to expand...
Click to collapse
Make backup on anything! You will not have access to anything until you install the rom I gave you in the first post.
Go to recovery and flash this ota update.
https://my.pcloud.com/publink/show?code=XZYg1T7ZzpJwx2DdRo4wbpTUEXABAfnS9PgX
After all go to recovery again.
If it says that the Android version is 7.1, then everything is ready.
If it does not get the first time, flash ota again.
When I did it, I think I flash two times ota update.
If it's okay, try the Instructions from the first post again.
marto2013 said:
He can downgrade his bootloader using older OTA update.
=====
Make backup on anything! You will not have access to anything until you install the rom I gave you in the first post.
Go to recovery and flash this ota update.
https://my.pcloud.com/publink/show?code=XZYg1T7ZzpJwx2DdRo4wbpTUEXABAfnS9PgX
After all go to recovery again.
If it says that the Android version is 7.1, then everything is ready.
If it does not get the first time, flash ota again.
When I did it, I think I flash two times ota update.
If it's okay, try the Instructions from the first post again.
Click to expand...
Click to collapse
I thought this wouldn't work too
I downloaded a rom from androidhost.ru thinking it was an official rom. My aim was downgrading. But it's not an official rom, i guess. And either I can't get back to official rom. Please help. The Huawei technical support told me that the device could be out of guarentee.
Try installing Hi Suite and do a recovery from there
Billabomb75 said:
Try installing Hi Suite and do a recovery from there
Click to expand...
Click to collapse
Thank you. I tried Hi Suite. Hi Suite says the firmware is updated.
There is no huawei identity part and there is no update information, the firmware seems updated.
I downloaded 155 version but i can't update. About phone section --> software number seems 8.0.0.0.46(0JVO).
I can downgrade or upgrade using androidhost.ru files but the other files (app or update.zip) don't work.
Eset Nod32 says the phone is rooted, root checker says the phone is not rooted.
Well try forcing your phone to install the official Rom... Try to boot into a download mode and flash through there
I download full ota zip and L11_hw_eu files from different sites. I turn off the device. I push the volume down and volume up and power button (force) the software installation fails.
Search XDA universal search for hurupdater ..
Get firmware finder from playstore ..download correct stock rom
Follow hurupdater instructions to update in recovery
Firmware finder doesn't find firmware for p smart.
Hurupdater needs unlocked bootloader i guess.
candask said:
Firmware finder doesn't find firmware for p smart.
Hurupdater needs unlocked bootloader i guess.
Click to expand...
Click to collapse
I have a huawei p smart and firmware finder & hurupdater is working ..but yes ..you need an unlocked bootloader ..
In that case
Download stock rom with firmware finder and put on sd
download stock recovery from p smart forum and flash with fastboot ..boot into stock recovery and use stock recovery to restore ...
And on a seperate note , I recommend downloading dc unlocker application and downgrading and unlocking bootloader using dc unlocker ..just search in XDA universal search ....it's a working method ..
Here you can see it :good:
KevMetal said:
I have a huawei p smart and firmware finder & hurupdater is working ..but yes ..you need an unlocked bootloader ..
In that case
Download stock rom with firmware finder and put on sd
download stock recovery from p smart forum and flash with fastboot ..boot into stock recovery and use stock recovery to restore ...
Click to expand...
Click to collapse
thank you but here somebody says:
"Unless your bootloader is unlocked you can't flash ANY .img file ..."
candask said:
thank you but here somebody says:
"Unless your bootloader is unlocked you can't flash ANY .img file ..."
Click to expand...
Click to collapse
No , you can flash only *signed files ...big difference ..you can ALWAYS flash files signed by huawei like stock recovery
https://drive.google.com/file/d/1dFFjCG2xeg9E08SZFA7jC9y21iX1sJgD/view
_there is stock recovery in link
_put in fastboot folder
_rename to recovery.img
_inside settings of phone enable usb debugging ..connect to pc ..in pop-up window allow debug connection (tick always allow )
_open cmd window as admin in fastboot folder
_Run the following commands
adb devices
*should show a serial number
adb reboot bootloader
fastboot devices
*should show a serial number
fastboot flash recovery_ramdisk recovery.img
fastboot reboot
KevMetal said:
No , you can flash only *signed files ...big difference ..you can ALWAYS flash files signed by huawei like stock recovery
https://drive.google.com/file/d/1dFFjCG2xeg9E08SZFA7jC9y21iX1sJgD/view
_there is stock recovery in link
_put in fastboot folder
_rename to recovery.img
_inside settings of phone enable usb debugging ..connect to pc ..in pop-up window allow debug connection (tick always allow )
_open cmd window as admin in fastboot folder
_Run the following commands
adb devices
*should show a serial number
adb reboot bootloader
fastboot devices
*should show a serial number
fastboot flash recovery_ramdisk recovery.img
fastboot reboot
Click to expand...
Click to collapse
thank you. but failed command not allowed?
Does your phone have the OEM UNLOCK option enabled in the developer settings / is the FRP setting disabled. Having an unlocked bootloader simplifies things a lot. I had a similar issue and used the PC version of the huawei firmware finder by TEAM MT and had to use the DNS method (either do via router or set the pc as a hotspot to reflash a lower version of firmware
I took the telephone to a shop for firmware repair. He tried for a couple of days and he also couldn’t get back to official software.
candask said:
Firmware finder doesn't find firmware for p smart.
Hurupdater needs unlocked bootloader i guess.
Click to expand...
Click to collapse
Hi, Candask
I see you are having problems getting back to official software for the Huawei P smart
Knowing that it says System 8.0.0.046 means you are running Huawei Firmware but System 8.0.0.046 usually means the firmware was made for a different model
How this works is the version folder ( partition ) includes information on the device model and if that version folder does not include the files for your region or model, it will display as System 8.0.0.046, not a serious issue but it is fixable
If you could get in contact with me on our Facebook page www.facebook.com/livitechdev
and also provide us with the Huawei P smart model number ( at the bottom of the phone on the back it will say Model: FIG-XXX, mine says FIG-LX1 )
And we will see if we can help you out - Thanks Ryan
8.0.0 is just the software version, what i think you need to match is for example mine is C782
example if you search you had found the following FIG-LX1C09B139 is device/model , and (8.0.0.139) is software version, id reckon aslong as you match the device and get the latest software version it would work
friartuckme said:
8.0.0 is just the software version, what i think you need to match is for example mine is C782
example if you search you had found the following FIG-LX1C09B139 is device/model , and (8.0.0.139) is software version, id reckon aslong as you match the device and get the latest software version it would work
Click to expand...
Click to collapse
@candask - this User is on the right track,
He would be able to get the software version of he already knows his phones model number C782, C472, C106, etc
The only place I believe you can find your model number inside Android is on the build number inside of settings>System>About Phone
8.0.0.137 ( C782 ) is the usual format
8.0.0 being Android version
137 being Huawei's version
( C782 ) being model number of device
the build number Candask has says
System 8.0.0.046( 0VJO )
Which does not give Indication of what model phone he has
Have you tried using E-recovery?
Livi-Tech said:
@candask - this User is on the right track,
He would be able to get the software version of he already knows his phones model number C782, C472, C106, etc
The only place I believe you can find your model number inside Android is on the build number inside of settings>System>About Phone
8.0.0.137 ( C782 ) is the usual format
8.0.0 being Android version
137 being Huawei's version
( C782 ) being model number of device
the build number Candask has says
System 8.0.0.046( 0VJO )
Which does not give Indication of what model phone he has
Have you tried using E-recovery?
Click to expand...
Click to collapse
hi livi-tech
I think what he is experiencing is when he has flashed a custom rom on his phone its changed the rom version name i believe, so even in e-recovery and fastboot it is being read as an unsupported device. il attach a picture to try and show
E-Recovery and attempting to use hisuite will work up until it checks his imei and device / software info then it is unable to proceed
friartuckme said:
hi livi-tech
I think what he is experiencing is when he has flashed a custom rom on his phone its changed the rom version name i believe, so even in e-recovery and fastboot it is being read as an unsupported device. il attach a picture to try and show
E-Recovery and attempting to use hisuite will work up until it checks his imei and device / software info then it is unable to proceed
Click to expand...
Click to collapse
Hello @friartuckme
I haven't had any issues with E-recovery and fastboot in the past no matter what my build number was or what custom ROM was flashed, not sure about HiSuite as I don't have a use for it but I had a look to confirm, even with the build number being different E-recovery still works and fastboot
This is my current setup
Build number: LiviTech (EM Pixel)
EMUI version: 8.0.0
E-recovery picks up: 8.0.0.137(C782) and starts downloading package
This was my setup when looking into compatibility issues a few months ago
Build number: System 8.0.0.046( 0VJO )
EMUI version: 8.0.0
E-recovery picks up: 8.0.0.137(C782) and starts downloading package
Deleting the whole version partition results in
Build number: System 8.0.0.046( OVJO )
EMUI version: 8.0.0
E-recovery picks up: 8.0.0.137(C782) and starts downloading package
( Would not recommend deleting version partition or modifying it unless you want phone to reset or apps to get removed, it's a Huawei issue )
I think I know what the issue his, the firmware he flashed sounds like Huawei firmware ( or a version of it ) but it sounds like the version partition included with that firmware doesn't include the files for his model.