Hello everyone, so today I tried installing lineageos on my g play mini, and while I was factory reseting using twrp, it actually deleted my OS, even though I'm fairly sure I didn't check internal memory... Anyway, my phone got completely wiped out, but I can access twrp recovery, and fastboot mode. Is there a way to get back to the stock ROM? I've been trying for hours, but I can't find a solution. There are no custom mods for this phone, even the twrp version I'm using is for the honor 4c. Any help would be appreciated
kikowastaken said:
Hello everyone, so today I tried installing lineageos on my g play mini, and while I was factory reseting using twrp, it actually deleted my OS, even though I'm fairly sure I didn't check internal memory... Anyway, my phone got completely wiped out, but I can access twrp recovery, and fastboot mode. Is there a way to get back to the stock ROM? I've been trying for hours, but I can't find a solution. There are no custom mods for this phone, even the twrp version I'm using is for the honor 4c. Any help would be appreciated
Click to expand...
Click to collapse
That's sad..
Download stock firmware flash stock recovery and then flash stock firmware via dload method..
hassanjavaid8181 said:
That's sad..
Download stock firmware flash stock recovery and then flash stock firmware via dload method..
Click to expand...
Click to collapse
I tried that, it updates normally but it stops right before the end and it gets stuck
I also tried extracting the Recovery, Boot and Cust files from the UPDATE.app file, and flashing them, but it doesn't do anything.
When I try to install it via zip file from the original recovery menu, it fails instantly with the message "cust link file fail. please check if vendor/country is valid. Software install failed!"
:crying: I've been trying to solve this for the past three days straight.
kikowastaken said:
I tried that, it updates normally but it stops right before the end and it gets stuck
Click to expand...
Click to collapse
Did you download right firmware number..coz you cannot flash lower number of firmware if you were on higher number...
What firmware version you were on before issue??
hassanjavaid8181 said:
Did you download right firmware number..coz you cannot flash lower number of firmware if you were on higher number...
What firmware version you were on before issue??
Click to expand...
Click to collapse
I still had the one that came originally with it. Which is Android Kit Kat (4.4) if I'm not mistaken. I never changed it while my phone was alive. I tried flashing the 4.4 rom available in Huawei's official site, as well as a lollipop one, and a 6.0 one. None worked, unfortunately.
kikowastaken said:
I still had the one that came originally with it. Which is Android Kit Kat (4.4) if I'm not mistaken. I never changed it while my phone was alive. I tried flashing the 4.4 rom available in Huawei's official site, as well as a lollipop one, and a 6.0 one. None worked, unfortunately.
Click to expand...
Click to collapse
You need to find rollback pkg for you device according to you model number..after flashing that you can flash any firmware number
Give me you phone details..
Model number
Build number
If I find I will post it here..
hassanjavaid8181 said:
You need to find rollback pkg for you device according to you model number..after flashing that you can flash any firmware number
Give me you phone details..
Model number
Build number
If I find I will post it here..
Click to expand...
Click to collapse
I've been trying to find it but how can I know that, now that I have no OS installed? Is there a way?
I'm so pissed, I used those details 5 days ago to unlock bootloader, but I didn't save them anywhere
kikowastaken said:
I've been trying to find it but how can I know that, now that I have no OS installed? Is there a way?
I'm so pissed, I used those details 5 days ago to unlock bootloader, but I didn't save them anywhere
Click to expand...
Click to collapse
Do you have its box??it must be written on that..
hassanjavaid8181 said:
Do you have its box??it must be written on that..
Click to expand...
Click to collapse
I can only find the model, which is HUAWEI chc-u01, and the IMEI number...
kikowastaken said:
I can only find the model, which is HUAWEI chc-u01, and the IMEI number...
Click to expand...
Click to collapse
and then there's a few more numbers but I don't know what they are
there's also a few numbers but I'm not sure what they are. One is next to the bar code and the other one says S/N: and then the number
kikowastaken said:
there's also a few numbers but I'm not sure what they are. One is next to the bar code and the other one says S/N: and then the number
Click to expand...
Click to collapse
There is no build number written??
hassanjavaid8181 said:
There is no build number written??
Click to expand...
Click to collapse
I can't find it anywhere
I finally fixed it
kikowastaken said:
I finally fixed it
Click to expand...
Click to collapse
Glad that you fixed it...
How did you fixed it??
I'm not 100% sure, but here's what I did:
Downloaded an oeminfo zipped file, and flashed it through twrp. It was supposed to be for my model, but after flashing it successfully, I noticed my phone showed the "honor" logo, instead of the usual huawei one.
So after that, I downloaded the Kit Kat rom for Honor 4c, and extracted the following files from the UPDATE.app: boot, cache, cust, system, recovery.
Flashed them independently, and then I tried to turn on the phone, and it was working again, running Android Kit Kat. After that I've been able to update it to 6.0, EMUI4.0, through dload, local update method
this **** was scary but I pulled it off somehow. I have no knowledge whatsoever, this was pure trial and error for 5 days straight.
I should be able to install LineageOS now, don't you think?
kikowastaken said:
I'm not 100% sure, but here's what I did:
Downloaded an oeminfo zipped file, and flashed it through twrp. It was supposed to be for my model, but after flashing it successfully, I noticed my phone showed the "honor" logo, instead of the usual huawei one.
So after that, I downloaded the Kit Kat rom for Honor 4c, and extracted the following files from the UPDATE.app: boot, cache, cust, system, recovery.
Flashed them independently, and then I tried to turn on the phone, and it was working again, running Android Kit Kat. After that I've been able to update it to 6.0, EMUI4.0, through dload, local update method
this **** was scary but I pulled it off somehow. I have no knowledge whatsoever, this was pure trial and error for 5 days straight.
I should be able to install LineageOS now, don't you think?
Click to expand...
Click to collapse
That's great man..
Yes you will be able to install any ROM..make sure you make all partitions backup and keep it safe in PC..:good:
did you solve it? I have the same trouble ):
mau1361317 said:
did you solve it? I have the same trouble ):
Click to expand...
Click to collapse
If you had Android version higher than Android 5 and TWRP, you can download stock firmware with firmwarefinder (if it still exist, search in forums for it) and flash it in TWRP like any rom.
Related
OK, twice now this has happened.
The first time was after I updated some apps. The second was when I had installed a new app.
Initially several apps then fail to work, they open and close straight away.
I reboot and phone hangs on first M screen - before the swirly white bits.
Into recovery from there shows dead Android with open chest and Explanation mark (I think)
Factory reset from recovery fail doesn't seem to do anything
Only solution is to flash official ROM using RSD
Phone is totally UK Orange Stock - not unlocked or rooted.
Eserim said:
OK, twice now this has happened.
The first time was after I updated some apps. The second was when I had installed a new app.
Initially several apps then fail to work, they open and close straight away.
I reboot and phone hangs on first M screen - before the swirly white bits.
Into recovery from there shows dead Android with open chest and Explanation mark (I think)
Factory reset from recovery fail doesn't seem to do anything
Only solution is to flash official ROM using RSD
Phone is totally UK Orange Stock - not unlocked or rooted.
Click to expand...
Click to collapse
To access recovery in the Android with open chest and Explanation mark : press Volume up AND down some times to get in recovery
and in recovery try factory reset.
ManoBros said:
To access recovery in the Android with open chest and Explanation mark : press Volume up AND down some times to get in recovery
and in recovery try factory reset.
Click to expand...
Click to collapse
Thanks for that, it may be useful in future, but any ideas what may have caused this?
Eserim said:
Only solution is to flash official ROM using RSD
Click to expand...
Click to collapse
I have the same issue right now, what do I have to do? Where can I get an official ROM and can I just flash the ROM on an locked and unrooted phone? I have O2 DE phone. Thanks.
lukassek said:
I have the same issue right now, what do I have to do? Where can I get an official ROM and can I just flash the ROM on an locked and unrooted phone? I have O2 DE phone. Thanks.
Click to expand...
Click to collapse
See http://forum.xda-developers.com/razr-i/general/index-razr-t2832722 - should answer all your questions - but yes, you can use RSD on any phone, without unlocking or rooting - it is the official Motorola tool. The O2 De ROMs are on the linked page http://forum.xda-developers.com/showthread.php?t=2028814
Eserim said:
See http://forum.xda-developers.com/razr-i/general/index-razr-t2832722 - should answer all your questions
Click to expand...
Click to collapse
Well, it didn't, I'm still getting this: 'Please check input file. Either XML format is wrong or image files associated is missing' after exctacting through RSD Lite. And I can't get further.
lukassek said:
Well, it didn't, I'm still getting this: 'Please check input file. Either XML format is wrong or image files associated is missing' after exctacting through RSD Lite. And I can't get further.
Click to expand...
Click to collapse
By looking at your other post you are using this zip file in RSD-lite: http://forum.xda-developers.com/showthread.php?t=2028814
As the Titel of the thread says, they are 'OTA' updates. So only usable through recovery and when going from a working 4.0.4 stock rom to 4.1.2.
That's why u are getting that error. The zip is not intended to be used through RSD-Lite.
U will need to get your hands on a JB RSD-Lite firmware zip file. This site: http://motofirmware.com/files/category/24-smi/
Has some firmwares, not all.
Hazou said:
U will need to get your hands on a JB RSD-Lite firmware zip file. This site: http://motofirmware.com/files/category/24-smi/
Has some firmwares, not all.
Click to expand...
Click to collapse
Thanks I followed Eserims advise. I also found this site: http://forum.xda-developers.com/showthread.php?t=2239706 before, but only working link was Retail UK/British and I wasn't sure if I can use it since i have O2DE.
But on the site you showed me I found this: CFC_9.8.2I-50_SMI-26_S7_USASMIJBO2DE.xml.zip. I don't know what CFC means, but I'm going to try it, thank you.
Update:
It's working... Couple of days reading threads, searching the internet and nothing, than Hazou came and it's done, thaks again.
lukassek said:
Thanks I followed Eserims advise. I also found this site: http://forum.xda-developers.com/showthread.php?t=2239706 before, but only working link was Retail UK/British and I wasn't sure if I can use it since i have O2DE.
But on the site you showed me I found this: CFC_9.8.2I-50_SMI-26_S7_USASMIJBO2DE.xml.zip. I don't know what CFC means, but I'm going to try it, thank you.
Update:
It's working... Couple of days reading threads, searching the internet and nothing, than Hazou came and it's done, thaks again.
Click to expand...
Click to collapse
No problem, I am pleased it worked out for you!
Hello
After trying to do an OTA update which failed my phone won't boot normally. If I just turn it on it boots into stock recovery and if I reboot it from there it just boots back into recovery.
I have tried to do a factory reset but it won't work, it seems like the system partition has been messed up.
I keep reading that I just need to "run the RUU" but I have no idea where I can find a RUU for my phone, it's a EU 64Bit version with no carrier. The htcdev site just lists kernel sources for my device.
Any idea how I can fix this and get back to a stock system?
henning_ said:
Hello
After trying to do an OTA update which failed my phone won't boot normally. If I just turn it on it boots into stock recovery and if I reboot it from there it just boots back into recovery.
I have tried to do a factory reset but it won't work, it seems like the system partition has been messed up.
I keep reading that I just need to "run the RUU" but I have no idea where I can find a RUU for my phone, it's a EU 64Bit version with no carrier. The htcdev site just lists kernel sources for my device.
Any idea how I can fix this and get back to a stock system?
Click to expand...
Click to collapse
Download this...
http://dl4.htc.com/RomCode/Source_and_Binaries/a11ul-3.10.28-g930be6d.zip
Thanks for the reply but the link just takes me to the general download page, could you tell me what filter you used to find the correct download?
henning_ said:
Thanks for the reply but the link just takes me to the general download page, could you tell me what filter you used to find the correct download?
Click to expand...
Click to collapse
Just enter the desire 510 skip the carrier and version just EU in the region and download the first one.
MrMike2182 said:
Just enter the desire 510 skip the carrier and version just EU in the region and download the first one.
Click to expand...
Click to collapse
Ok, but those are all just kernel sources, that's the problem, I can't use any of those to restore my device.
henning_ said:
Ok, but those are all just kernel sources, that's the problem, I can't use any of those to restore my device.
Click to expand...
Click to collapse
Well the only way I think you're gonna be able to fix it now is to follow the thread that shows you how to root the phone and install a recovery called philz touch recovery for 64 bit and then you'll be able to install the back up recovery that other users have posted.
MrMike2182 said:
Well the only way I think you're gonna be able to fix it now is to follow the thread that shows you how to root the phone and install a recovery called philz touch recovery for 64 bit and then you'll be able to install the back up recovery that other users have posted.
Click to expand...
Click to collapse
Thanks, I just did this, but I installed an old backup I had made before rooting the phone earlier this year. Now I'm back!
henning_ said:
Thanks, I just did this, but I installed an old backup I had made before rooting the phone earlier this year. Now I'm back!
Click to expand...
Click to collapse
Glad you got it fixed because I couldn't find anything for you about the RUU for 64 bit... So I was pretty sure you could fix it by rooting it!
Hey community,
i googled a lot and searched a lot here, didnt help.
Basically i wiped everything using TWRP by accident... Now i dont have any OS on my P10... I can still go to fastboot mode, erecovery and normal recovery...
any ideas what to do? i already tried dloading the correct firmware, it didnt work.
BaumFX said:
Hey community,
i googled a lot and searched a lot here, didnt help.
Basically i wiped everything using TWRP by accident... Now i dont have any OS on my P10... I can still go to fastboot mode, erecovery and normal recovery...
any ideas what to do? i already tried dloading the correct firmware, it didnt work.
Click to expand...
Click to collapse
https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286
Did it help, what @glehel posted?
I want to know, because I want to provide this guide also for fixing problems like you have ... or had.
Use dload forced method with first before using scripts.
Just download the correct firmware for your device, if you know the firmware-version you had, use the exact one, because it was approved for installation:
http://pro-teammt.ru/firmware-database/?firmware_model
Extract the the update.zip and put the update.app into a folder called dload on your sdcard.
Start you phone while holding all 3 buttons, this will launch th dload process.
This way you maybe safe some time.
LwannaCM said:
Just download the correct firmware for your device, if you know the firmware-version you had,
Click to expand...
Click to collapse
Is there a way to retrieve the exact name of the installed stock firmware? For my VTR-L09C432 there are multiple versions listed (like 360, 365, etc). Also I am wondering what's the difference between FullOTA-MF / OTA-MF / FullOTA-MF-PF, etc.
tadeussenf said:
Is there a way to retrieve the exact name of the installed stock firmware? For my VTR-L09C432 there are multiple versions listed (like 360, 365, etc). Also I am wondering what's the difference between FullOTA-MF / OTA-MF / FullOTA-MF-PF, etc.
Click to expand...
Click to collapse
No, you can´t check your version, but if you choose an older firmware, you should be fine. Afterwards you can update to a newer version.
The only problem might be, if you already had oreo installed, then you should use it again for restore, because the partitionlayout changed from nougat to oreo.
All version named B1XX are Nougatfirmwares
All version named B3XX are Oreofirmwares.
Choose a FULLOTA for updates, the others are just incremental and won´t help you in your case.
To be exact you should use a FullOTA-MF-PV. The PV stands for public version and all other firmwares are just internal builds from huawei.
LwannaCM said:
Lot's of great information
Click to expand...
Click to collapse
Thanks alot, this was exactly the information I was looking for!
BaumFX said:
Hey community,
i googled a lot and searched a lot here, didnt help.
Basically i wiped everything using TWRP by accident... Now i dont have any OS on my P10... I can still go to fastboot mode, erecovery and normal recovery...
any ideas what to do? i already tried dloading the correct firmware, it didnt work.
Click to expand...
Click to collapse
If you don't want to go back to stock firmware, you also have the option of custom roms such as Lineage OS or one of the others in this forum.
If you go with stock firmware, I suggest you make a Nandroid back-up before you flash TWRP. You can easily do this by booting into twrp instead of flashing (eg: fastboot boot twrp.img). After creating and copying the back-up to your PC, you can proceed with flashing twrp and never have to worry about the softbricking again =).
BaumFX said:
Hey community,
i googled a lot and searched a lot here, didnt help.
Basically i wiped everything using TWRP by accident... Now i dont have any OS on my P10... I can still go to fastboot mode, erecovery and normal recovery...
any ideas what to do? i already tried dloading the correct firmware, it didnt work.
Click to expand...
Click to collapse
Good evening, try this: https://forum.xda-developers.com/mate-9/how-to/funky-huawei-erecovery-solution-100-t3620165, it really works, I rescue my P10 from a hard brick
Full ODIN stock ATT files.
Download one file and unzip to md5 format. Put in ODIN and flash.
I take no responsibility if anything goes wrong. You don't need to be on certain baseband to flash this, you can flash this directly from any baseband version to this.
AP_G920AUCS7ERC1_CL12991177_QB17238575_REV02_user_low_ship_meta.tar.md5
BL_G920AUCS7ERC1_CL12991177_QB17238575_REV02_user_low_ship.tar.md5
CP_G920AUCS7ERC1_CP9116334_CL12991177_QB17238575_REV02_user_low_ship.tar.md5
CSC_ATT_G920AATT7ERC1_CL12991177_QB17238575_REV02_user_low_ship.tar.md5
What's changing: Android device security updates
Android version: 7.0.1
Security patch level (SPL): March 1, 2018
Baseband version: G920AUCS7ERC1
Build number: NRD90M.G920AUCS7ERC1
Download link: https://drive.google.com/uc?id=1g6XVKD-hsDOOXnLbBfbGKgPz7NFoLpxR&export=download
Download link for Odin3_v3.12.3: https://odindownload.com/download/Odin3_v3.12.3.zip
If i helped you don't forget to hit thanks button.
I just got a Samsung S6 from AT&T and I am trying to root it. Nothing I've found has worked at all other than these files. I constantly get write errors in Odin and TWRP doesn't install nor does SuperSU. These four files however loaded on without any problems and completely restored the phone back to how I got it. Still no root though. Any ideas/suggestions? Thanks in advance.
stek-kravari said:
Full ODIN stock ATT files.
Download one file and unzip to md5 format. Put in ODIN and flash.
I take no responsibility if anything goes wrong. You don't need to be on certain baseband to flash this, you can flash this directly from any baseband version to this.
AP_G920AUCS7ERC1_CL12991177_QB17238575_REV02_user_low_ship_meta.tar.md5
BL_G920AUCS7ERC1_CL12991177_QB17238575_REV02_user_low_ship.tar.md5
CP_G920AUCS7ERC1_CP9116334_CL12991177_QB17238575_REV02_user_low_ship.tar.md5
CSC_ATT_G920AATT7ERC1_CL12991177_QB17238575_REV02_user_low_ship.tar.md5
What's changing: Android device security updates
Android version: 7.0.1
Security patch level (SPL): March 1, 2018
Baseband version: G920AUCS7ERC1
Build number: NRD90M.G920AUCS7ERC1
Download link:
If i helped you don't forget to hit thanks button.
Click to expand...
Click to collapse
brokenmaschine said:
I just got a Samsung S6 from AT&T and I am trying to root it. Nothing I've found has worked at all other than these files. I constantly get write errors in Odin and TWRP doesn't install nor does SuperSU. These four files however loaded on without any problems and completely restored the phone back to how I got it. Still no root though. Any ideas/suggestions? Thanks in advance.
Click to expand...
Click to collapse
You cannot install TWRP or root it via flashing SuperSU because the bootloader is locked on at&t model.
stek-kravari said:
You cannot install TWRP or root it via flashing SuperSU because the bootloader is locked on at&t model.
Click to expand...
Click to collapse
I had a feeling that was happening because all steps mention something about OEM unlocking and I wasn't able to do that.
Is this version rootable or am I stuck with this?
brokenmaschine said:
I had a feeling that was happening because all steps mention something about OEM unlocking and I wasn't able to do that.
Is this version rootable or am I stuck with this?
Click to expand...
Click to collapse
From what I'm reading it appears that AT&T's 7.x isn't rootable...
The baseband version I got is G920AUCS7ERC1. Can I downgrade the phone to Android v 6.x and then root or am I totally locked out of this phone and should look to get something different?
brokenmaschine said:
From what I'm reading it appears that AT&T's 7.x isn't rootable...
The baseband version I got is G920AUCS7ERC1. Can I downgrade the phone to Android v 6.x and then root or am I totally locked out of this phone and should look to get something different?
Click to expand...
Click to collapse
You cannot downgrade to previous version. If you want to root phones and install custom roms always buy the internation model (european) with exynos chipset
stek-kravari said:
You cannot downgrade to previous version. If you want to root phones and install custom roms always buy the internation model (european) with exynos chipset
Click to expand...
Click to collapse
Thank's for clearing this up for me. I didn't buy this phone, rather I got it as a replacement when I filed an insurance claim, meaning I had no control over what they sent me. What is the main thing I should look for when I get another replacement?
How do I do this? Is there written step by step instructions?
chrisb20 said:
How do I do this? Is there written step by step instructions?
Click to expand...
Click to collapse
Click on the 'BL' button, then choose the file that starts with "BL" inside your extracted firmware folder. Next, click on the 'AP' button and choose the AP file inside your extracted firmware folder. Click on the 'CP' button, choose the CP file inside your extracted firmware and finally click on the 'CSC' button, choose CSC file inside your extracted firmware and click START
Actually you can downgrade to 6.0.1 and any Revision aka BIT 5 firmware. The reason for this is that the Rev 7 or 7.0 Firmware has the same bootloader firmware as 6.0.1 as long as its BIT 5 aka Rev 5 Firmware you are flashin. Also use Odin 3.13.3 SHAE 256 Fix_ATT_Verizon. PrinceComsy Odin may work as well. But I have done several of these downgrades on G920A with no issues-
dave357 said:
Actually you can downgrade to 6.0.1 and any Revision aka BIT 5 firmware. The reason for this is that the Rev 7 or 7.0 Firmware has the same bootloader firmware as 6.0.1 as long as its BIT 5 aka Rev 5 Firmware you are flashin. Also use Odin 3.13.3 SHAE 256 Fix_ATT_Verizon. PrinceComsy Odin may work as well. But I have done several of these downgrades on G920A with no issues-
Click to expand...
Click to collapse
I didn't know that, thanks for the info
dave357 said:
Actually you can downgrade to 6.0.1 and any Revision aka BIT 5 firmware. The reason for this is that the Rev 7 or 7.0 Firmware has the same bootloader firmware as 6.0.1 as long as its BIT 5 aka Rev 5 Firmware you are flashin. Also use Odin 3.13.3 SHAE 256 Fix_ATT_Verizon. PrinceComsy Odin may work as well. But I have done several of these downgrades on G920A with no issues-
Click to expand...
Click to collapse
Sir I want to downgrade my G925A running Official 7.0 , I tried downgrading it to 6.0.1 but it didn't flash it fails and gives an error
"sw rev check fail device 5 binary 4" please help me i want to downgrade it..
_shaddy_ said:
Sir I want to downgrade my G925A running Official 7.0 , I tried downgrading it to 6.0.1 but it didn't flash it fails and gives an error
"sw rev check fail device 5 binary 4" please help me i want to downgrade it..
Click to expand...
Click to collapse
Need help too
I flashed my sm g920a via this files and odin. it worked well. my phone opened and wanted me my samsung account .Ididn remember my samsung account at all.
I went to recovery menu and I did wipe data (aka. factory reset.). it was successfull. and I select reboot system now. It closed and opened. and stuck at at&t screnn with blue att logo.
I push power+volume down and is starts re-opening. when it was opening I pushed home+power+vol. up, for going to recovery mode. I've tryed factory reset, and reboot, it got freezed at att logo. I've tryed wipe cache partition with factory reset and reboot, it stuck at att logo. I've tryed run graphics got error, it delete something, and update again. and I've tryed to reboot. it opened.
but again it locked via samsung account.
I went to recovery menu and againg factory reset and reboot. it stuck again. I've tryed same things it isnt fixed.
I dont know waht to do.
can you help me pls.
Saidish said:
I flashed my sm g920a via this files and odin. it worked well. my phone opened and wanted me my samsung account .Ididn remember my samsung account at all.
I went to recovery menu and I did wipe data (aka. factory reset.). it was successfull. and I select reboot system now. It closed and opened. and stuck at at&t screnn with blue att logo.
I push power+volume down and is starts re-opening. when it was opening I pushed home+power+vol. up, for going to recovery mode. I've tryed factory reset, and reboot, it got freezed at att logo. I've tryed wipe cache partition with factory reset and reboot, it stuck at att logo. I've tryed run graphics got error, it delete something, and update again. and I've tryed to reboot. it opened.
but again it locked via samsung account.
I went to recovery menu and againg factory reset and reboot. it stuck again. I've tryed same things it isnt fixed.
I dont know waht to do.
can you help me pls.
Click to expand...
Click to collapse
Before you flashed the firmware you needed to disable samsung reactivation lock, I don't know how to fix this, maybe
try searching on youtube
Right Now phone cant go furter than att logo from start.
Samsung account is problem yes but there is another problem. Should I re-flash my phone?
Saidish said:
Right Now phone cant go furter than att logo from start.
Samsung account is problem yes but there is another problem. Should I re-flash my phone?
Click to expand...
Click to collapse
Try to reflash the firmware but you'll still need to enter your samsung account i think
stek-kravari said:
Try to reflash the firmware but you'll still need to enter your samsung account i think
Click to expand...
Click to collapse
Should I reflash via same files or any other files from xda?
By the way, thank You for answerin.g
Saidish said:
Should I reflash via same files or any other files from xda?
By the way, thank You for answerin.g
Click to expand...
Click to collapse
Flash this combination file in the AP section in Odin https://drive.google.com/uc?export=download&id=1ZHcN_h2mzFjZpnkea5hbJycofIezoeW5
After that the phone should boot up, go to settings and do a factory reset from there.
And now flash this firmware again (G920AUCS7ERC1) and the protection should be removed completely
stek-kravari said:
Flash this combination file https://drive.google.com/uc?export=download&id=1ZHcN_h2mzFjZpnkea5hbJycofIezoeW5
After that the phone should boot up, go to settings and do a factory reset from there.
And now flash this firmware again (G920AUCS7ERC1) and the protection should be removed completely
Click to expand...
Click to collapse
Okay, I will do. Thank you for everything.
Hi all!
First a warning: I tell you how what I done, applying this on different model is possible but require some knowledge... don't try if you are not enough experienced.
My BTV-DL09 had a C100B303 firmware (unlocked, rooted with SuperSu 2.82) and I wanted to upgrade to last version, B310, downloaded with Firmware Finder for Huawei.
But this formware is not yet approved for my device! So i searched a way to update the firmware and found HuRUpdater.
Here the step-by-step tutorial:
1) download version B310
2) rename files (required by HuRUpdater):
- update_data_full_public.zip -> update_data_public.zip
- update_full_BTV-DL09_hw_eu.zip -> update_all_hw.zip
3) download HuRUpdater, I used version 0.3 if a new is available read what's changed.
4) (optional) download custom recovery (in this case the Greatslon TWRP for EMUI 5) and rename it "recovery.img"
5) copy all files to SD, in a subfolder (don't use "dload")
6) install, if not already present, the custom recovery
7) boot to the recovery and install "HuRUpdater_0.3.zip"
8) follow on-screen instructions than reboot!
At this point the Mediapad was working BUT
A) without root
B) with a "half" lock: the bootloader says it's unlocked but refused to flash or boot a custom recovery.
Problem B: I had to re-unlock the booloader with command
fastboot oem unlock 12345678901234567980
I accepted that my data will be erased (I have a backup, you too???) and the Mediapad rebooted.
I was lucky because the data was not erased and the bootloader now was fully unlocked. I'm not sure if this works for all of you so backup your data before. (***)
Problem A: not the custom recovery is booting so I flashed Magisk 15.3 (I had this version on other devices and don't wanted to do more testing for that day). It installed correctly, rebooted and
that's all folks!
(***) Here the enlightenment: https://forum.xda-developers.com/showpost.php?p=78194270&postcount=1029 from @zxz0O0
In short: flash also the custom recovery!
I have a M3 that can only boot up to twrp. I am trying to fix this tablet, since the previous owner accidentally erased the system partition, and it will not load. I did a search using the firmware finder, but wasn't sure I did it right, alot of versions came up. I do not know what software version was on it, before it got messed up. All I know is that it was bought less than two months ago. I was hoping someone could post a direct link to the firmware that I could use to get this tablet up and running again. the original owner lives in the US, as do I. Any help will be greatly appreciated. Thanks in advance
thew-tab said:
I have a M3 that can only boot up to twrp. I am trying to fix this tablet, since the previous owner accidentally erased the system partition, and it will not load. I did a search using the firmware finder, but wasn't sure I did it right, alot of versions came up. I do not know what software version was on it, before it got messed up. All I know is that it was bought less than two months ago. I was hoping someone could post a direct link to the firmware that I could use to get this tablet up and running again. the original owner lives in the US, as do I. Any help will be greatly appreciated. Thanks in advance
Click to expand...
Click to collapse
First you need to know the exact model. One method can be this:
0) insert an SD card
1) boot the TWRP
2) open the terminal
3) execute the command:
Code:
dd if=/dev/block/bootdevice/by-name/oeminfo of=/external_sd/oeminfo.img
this will copy the OEMINFO partition to the SD card.
4) open the oeminfo.img file with a hex editor and search for "BTV", do not stop to the first occurrence: there are some and you will find the exact firmware code that was installed.
5) search a FULL firmware with FW finder than flash it!
Nicola
nicolap8 said:
First you need to know the exact model. One method can be this:
0) insert an SD card
1) boot the TWRP
2) open the terminal
3) execute the command:
Code:
dd if=/dev/block/bootdevice/by-name/oeminfo of=/external_sd/oeminfo.img
this will copy the OEMINFO partition to the SD card.
4) open the oeminfo.img file with a hex editor and search for "BTV", do not stop to the first occurrence: there are some and you will find the exact firmware code that was installed.
5) search a FULL firmware with FW finder than flash it!
Nicola
Click to expand...
Click to collapse
Hello. I messed up my M3 trying to update and now Bluetooth does not work.
My firmware shows in Settings as "testkeys", so I don't really now what firmware is, probably B302 since security patch is from November 2017.
I am trying to flash full firmware again and do a full wipe. I tried to do it via TWRP and eRecovery too, but both methods fail.
I also tried the method the OP mentioned with no luck either (maybe because mine is the WiFi-only European version).
What should I do? How do I go back to stock? I don't care if I lose my data or if I have to relock bootloader again, I just want my M3 to work properly again!
sergio_sant said:
Hello. I messed up my M3 trying to update
Click to expand...
Click to collapse
Exact model?
Exact firmware that you have?
nicolap8 said:
Exact model?
Exact firmware that you have?
Click to expand...
Click to collapse
Model is BTV-W09C100B006 according to oeminfo.img, so I guess firmware must be B006?
In Settings it shows up like the screenshot attached:
sergio_sant said:
Model is BTV-W09C100B006 according to oeminfo.img, so I guess firmware must be B006?
In Settings it shows up like the screenshot attached:
Click to expand...
Click to collapse
Ahi, ahi... you are unable to discriminate what is the device model (BTV-W09) from the firmware version (BTV-W09C100B006). So you are not enough experienced nor skilled... Search someone that can help you offline!
nicolap8 said:
Ahi, ahi... you are unable to discriminate what is the device model (BTV-W09) from the firmware version (BTV-W09C100B006). So you are not enough experienced nor skilled... Search someone that can help you offline!
Click to expand...
Click to collapse
I may be not enough experienced nor skilled but I've been unlocking, rooting and changing roms to my phones since Android 2.1 era, that was many years ago as you know.
I know that the model is BTV-W09, I just said that OEMINFO says BTV-W09C100B006 when searching "btv" with an hex-editor following YOUR instructions from your earlier post.
Anyway, thanks for nothing, I finally found a solution by myself writing the required images one by one trough ADB.
Have a nice day.
I had to have messed up something quite well, I ran the updater, everything seemed to go fine, but when I rebooted, it wont go off the Huawei MediaPad android screen, and I can not get it back into TWRP , or get it to do anything else, any help would be greatly appreciated.
nicolap8 said:
First you need to know the exact model. One method can be this:
0) insert an SD card
1) boot the TWRP
2) open the terminal
3) execute the command:
Code:
dd if=/dev/block/bootdevice/by-name/oeminfo of=/external_sd/oeminfo.img
this will copy the OEMINFO partition to the SD card.
4) open the oeminfo.img file with a hex editor and search for "BTV", do not stop to the first occurrence: there are some and you will find the exact firmware code that was installed.
5) search a FULL firmware with FW finder than flash it!
Nicola
Click to expand...
Click to collapse
thew-tab said:
I had to have messed up something quite well, I ran the updater, everything seemed to go fine, but when I rebooted, it wont go off the Huawei MediaPad android screen,
Click to expand...
Click to collapse
Explain better, which screen?
and I can not get it back into TWRP , or get it to do anything else, any help would be greatly appreciated.
Click to expand...
Click to collapse
Reread first post.
It is the initial boot screen
nicolap8 said:
Explain better, which screen?
Reread first post.
Click to expand...
Click to collapse
Model?
Firmware previously on tablet?
Firmware that you installed?
Which files you used?
The update procedure was successfully or there was some message?
Model number is BTV-W09
Do not know the original firmware, but I apparently read the model number wrong when I looked it up. I used BTV-DL09. TWRP said install was a success ( I used the HuRUupdater thru TWRP) The files used was the full OTA , the update_full_BTV-DL09_dialcu_cn.zip, as well as the update_data_full_public.zip. I changed the file name to the names that were needed to run HuRUpdater. So my question is does anyone know how to fix my mistake?
I was able to get it into fastboot mode, but it said the phone was locked, and was not picked up by my computer.
nicolap8 said:
Model?
Firmware previously on tablet?
Firmware that you installed?
Which files you used?
The update procedure was successfully or there was some message?
Click to expand...
Click to collapse
thew-tab said:
Model number is BTV-W09
I used BTV-DL09. TWRP said install was a success
Click to expand...
Click to collapse
NEVER install the software for one model on a different hardware. NEVER!
What TWRP says it's not important: it only wrote some files on a disk but it's not of interest what is inside these files.
You have to flash an appropriate firmware, no other options.
how can I flash the the firmware, if I no longer have TWRP, or when I can get into flashboot mode, the computer does not recognize the tablet? . Here is a probably stupid question: do I look for BTV-W09, which is the model of MY tablet?
nicolap8 said:
NEVER install the software for one model on a different hardware. NEVER!
What TWRP says it's not important: it only wrote some files on a disk but it's not of interest what is inside these files.
You have to flash an appropriate firmware, no other options.
Click to expand...
Click to collapse
thew-tab said:
how can I flash the the firmware, if I no longer have TWRP, or when I can get into flashboot mode. Here is a probably stupid question: do I look for BTV-W09, which is the model of MY tablet?
Click to expand...
Click to collapse
You have to unpack the firmware and flash the partition images with flashboot.
Search the forum for "Huawei Update Extractor".
which of these are the partition images? Second stupid question, I tried to get in to fastboot, but the computer would not recognize the tablet
nicolap8 said:
You have to unpack the firmware and flash the partition images with flashboot.
Search the forum for "Huawei Update Extractor".
Click to expand...
Click to collapse
thew-tab said:
which of these are the partition images? Second stupid question, I tried to get in to fastboot, but the computer would not recognize the tablet
Click to expand...
Click to collapse
All of this are partition images!
The problem is that you have to write all relevant partitions that was written from bad firmware!
Often boot.img is enough to have TWRP working.
What about if I can't get the computer to recognize the tablet in fastboot mode?
nicolap8 said:
All of this are partition images!
The problem is that you have to write all relevant partitions that was written from bad firmware!
Often boot.img is enough to have TWRP working.
Click to expand...
Click to collapse
This is the screen I see when I am in flashboot mode
thew-tab said:
What about if I can't get the computer to recognize the tablet in fastboot mode?
Click to expand...
Click to collapse