Related
I am noob on android.
I rooted this phone with 4.1.1 and ever that I change something I have to uso param file for the mobile reboot.
I have some problems, I can't wipe the mobile with odyin, because when the mobile reboot it stuck on samsung galaxy words and then I have to use the param for it works, but nothing is deleted.
I have know 4.1.2 and I can't wipe too, even in phone settings, never can't reboot...
I have also this problem, the process android.process.acore has stopped. I have deleted all matched with contact data and keep appear...
Really I don't know how can I solve this, I only want reset to factory but I cant enter in recovery mode... never.
The buttons combination dont work, quickboot not... all reboot stuck on samsung words...
Have solution?
If you rooted it, open Google Play and download an app called Quick Boot. From there you should be able to reboot into recovery.
Benzonat0r said:
If you rooted it, open Google Play and download an app called Quick Boot. From there you should be able to reboot into recovery.
Click to expand...
Click to collapse
it doesn't work too :S. The device only reboot when is used param file...
Hmm, very weird. Can't think of anything that'll help you at the moment, but if I do I'll post it here immediately.
Benzonat0r said:
Hmm, very weird. Can't think of anything that'll help you at the moment, but if I do I'll post it here immediately.
Click to expand...
Click to collapse
Thank you very much
Enviado desde mi Samsung Galaxy Note II
Dahnark said:
I have some problems, I can't wipe the mobile with odyin, because when the mobile reboot it stuck on samsung galaxy words and then I have to use the param for it works, but nothing is deleted.
Have solution?
Click to expand...
Click to collapse
For factory reset, use this WIPE_I8190 in Odin. Flash as pda.
Good luck.
tys0n said:
For factory reset, use this WIPE_I8190 in Odin. Flash as pda.
Good luck.
Click to expand...
Click to collapse
Not work. All reboot without paran file not work. Stuck and boot and things is not deleted
Enviado desde mi Samsung Galaxy Note II
Have you tried to wipe and reinstall stock firmware without root again?
---------- Post added at 10:52 AM ---------- Previous post was at 10:43 AM ----------
Another question: Are you sure it's a I8190? Not a i8190L or i8190N?
tys0n said:
Have you tried to wipe and reinstall stock firmware without root again?
Click to expand...
Click to collapse
All roms not works without param file. I tried to wipe:
Stock rom without root with paran file for that can boot (but not reboot in recovery mode)
Stock rom without root wiuthout param file, same error
Stock rom with root, same error.
4.1.2 rom without and with root, same error...
All flash never deleted my apps...
tys0n said:
Have you tried to wipe and reinstall stock firmware without root again?
---------- Post added at 10:52 AM ---------- Previous post was at 10:43 AM ----------
Another question: Are you sure it's a I8190? Not a i8190L or i8190N?
Click to expand...
Click to collapse
In settings only appear i8190. How can I know if it is L or N
Dahnark said:
All roms not works without param file. I tried to wipe:
Stock rom without root with paran file for that can boot (but not reboot in recovery mode)
Stock rom without root wiuthout param file, same error
Stock rom with root, same error.
4.1.2 rom without and with root, same error...
All flash never deleted my apps...
Click to expand...
Click to collapse
Not being able to boot to recovery is a well known problem. Some devices just can't. I can't either.
It probably depend on bootloader version.
To get to recovery we have to use adb, or terminal emulator as root.
Flashing new rom won't do any different.
tys0n said:
Not being able to boot to recovery is a well known problem. Some devices just can't. I can't either.
It probably depend on bootloader version.
To get to recovery we have to use adb, or terminal emulator as root.
Flashing new rom won't do any different.
Click to expand...
Click to collapse
what is adb or terminal emulator (this is a app on google play no?)
Dahnark said:
what is adb or terminal emulator (this is a app on google play no?)
Click to expand...
Click to collapse
If you are rooted just download Android terminal emulator from play.
Open it and type su and push enter.
You'll get a promt from su-app to grant or deny su.
Grant, and you will get a # in terminal window wich means you got su privliges.
Type reboot recovery & push enter.
Phone will now reboot to recovery.
You'll probably need busybox installed also, if you havn't installed it yet.
ADB..well thats another thing. Try to search XDA. Theres plenty of guides on how to set it up.
tys0n said:
If you are rooted just download Android terminal emulator from play.
Open it and type su and push enter.
You'll get a promt from su-app to grant or deny su.
Grant, and you will get a # in terminal window wich means you got su privliges.
Type reboot recovery & push enter.
Phone will now reboot to recovery.
You'll probably need busybox installed also, if you havn't installed it yet.
ADB..well thats another thing. Try to search XDA. Theres plenty of guides on how to set it up.
Click to expand...
Click to collapse
Terminal emulator not work, and I don't know how config adb, I have install it but I don't know how change the directory in cmd or things so...
I read this tutorial: http://forum.xda-developers.com/showthread.php?t=1474956
when I enter this: adb shell reboot, say the same that terminal emulator, operation not permitted. I exe it with administration privileges...
tys0n said:
If you are rooted just download Android terminal emulator from play.
Open it and type su and push enter.
You'll get a promt from su-app to grant or deny su.
Grant, and you will get a # in terminal window wich means you got su privliges.
Type reboot recovery & push enter.
Phone will now reboot to recovery.
You'll probably need busybox installed also, if you havn't installed it yet.
ADB..well thats another thing. Try to search XDA. Theres plenty of guides on how to set it up.
Click to expand...
Click to collapse
Ah I forgot write #, but it work and when I use the comando recovery, the device reboot and Stuck again in Samsung Galaxy...
Enviado desde mi Samsung Galaxy Note II
Launch adb command prompt, and type in adb reboot recovery
Sv: Can't wipe/factory SIII mini
In terminal it should look like picture.
Then just push enter once more.
Sent thru time and space from my s3mini.
Benzonat0r said:
Launch adb command prompt, and type in adb reboot recovery
Click to expand...
Click to collapse
I dont find adb command prompt in folder Android sdk... I am noob in this.
tys0n said:
In terminal it should look like picture.
Then just push enter once more.
Yes but it not reboot, same problem that quick boot, Block on Samsung Galaxy...
Sent thru time and space from my s3mini.
Click to expand...
Click to collapse
Enviado desde mi Samsung Galaxy Note II
What root method did you use?
Any link to that?
Maybe you should ask the one who came up with that method/rom.
Sounds like your partitions is screwed up or you got a bad recovery or something.
tys0n said:
What root method did you use?
Any link to that?
Maybe you should ask the one who came up with that method/rom.
Sounds like your partitions is screwed up or you got a bad recovery or something.
Click to expand...
Click to collapse
I used the method of this forum. But I had battery problem and cause this I tried to go back to factory...
How can I fix partitions?
Enviado desde mi Samsung Galaxy Note II
Hi guys!
I reckon many people knows this, but I'm starting this thread for ignorant people.
I'm not responsible for any error. Don't forget this: You must be careful, otherwise you can brick your device
Starting...
If you want to install custom recovery, you should unlock bootloader but to do this you must be rooted
HOW TO ROOT?
Download framaroot here for the root device. This app can root many device. --->> http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
Download and install it to your phone. Then click open. You should select "Install SuperSU" from above section then click "Gandalf". Other sections don't work on our devices. After click it, you should see this message "Succes SuperSU installed. Reboot!" if you see this message please restart your phone. Now you are ready for unlocking bootloader.
HOW TO UNLOCK BOOTLOADER?
If your device is E610, download E610.zip from attachment and extract E610.bin. If your device is E612, download from attachement E612.zip and extract E612.bin to your internal storage's root directory.
(/mnt/sdcard/ directory). Then, download "Terminal Emulator" from Google Play Store and open it. Type this commands. Please be careful! If you type wrong, you can brick your device!
FOR E610
Code:
su
dd if=/sdcard/E610.bin of=/dev/block/mmcblk0p5
FOR E612
Code:
su
dd if=/sdcard/E612.bin of=/dev/block/mmcblk0p5
SUCCES! You've unlocked your bootloader! Now we can install custom recovery.
HOW TO INSTALL CUSTOM RECOVERY?
Download custom recovery from atachement. What do you want. Then copy it to internal storage's root directory. (/mnt/sdcard/ directory)
Then type this commands: (This is same in both.)
FOR CWM RECOVERY
Code:
su
dd if=/sdcard/cwm-6.0.5.0.img of=/dev/block/mmcblk0p17
FOR TWRP RECOVERY
Code:
su
dd if=/sdcard/twrp-2.8.0.0.img of=/dev/block/mmcblk0p17
FOR PHILZ TOUCH RECOVERY
Code:
su
dd if=/sdcard/philz_6.58.7.img of=/dev/block/mmcblk0p17
AND SUCCES! YOU CAN INSTALL ROM-APP-ANYTHING-ZIP FILE IN YOUR CUSTOM RECOVERY!
GOOD LUCK!
Credits goes to:
PecanCM
aidasaidas75
Very good thread,nice!!!
TEAM-OPTIMA-XDA!!!
-CALIBAN666- said:
Very good thread,nice!!!
TEAM-OPTIMA-XDA!!!
Click to expand...
Click to collapse
txh this is my first guide and I'm very happied :fingers-crossed:
:d
Nice work!
Thankssssssssss!
Thanks alot man! Worked like charm. Was just finding a way to do all the stuff without adb thing, and eureka! got it Keep up man!~ :good::good::good:
Hi, I have tried to install CWM in many different ways already (see this post), but when I try to enter recovery mode, only the two back/menu buttons briefly light up, and the phone goes dark again.
I have downloaded your e610.zip, and it contains the same files I already tried (found also in other .zips and .rars). Should this work for a phone that was already updated to 4.1.2 (stock ROM so far)?
HanSolo77 said:
Hi, I have tried to install CWM in many different ways already (see this post), but when I try to enter recovery mode, only the two back/menu buttons briefly light up, and the phone goes dark again.
I have downloaded your e610.zip, and it contains the same files I already tried (found also in other .zips and .rars). Should this work for a phone that was already updated to 4.1.2 (stock ROM so far)?
Click to expand...
Click to collapse
I'm not sure, I've never worked for L5. This is just a guide for how-to. You may ask to the other ones or open a thread at Optimus L3, L5, L7 Q&A, Help & Troubleshooting if you still haven't and wait for replys.
Good luck.
My E612 has some software problem. Somehow device remembered apps installed, settings, messages everything used once and now stuck on to it. Factory reset dosen't works. Everthing remains the same even after factory reseting. No root, bootloader locked. Complete stock. Any help is appreciated.
Sent from my A0001 using XDA-Developers mobile app
rachit011 said:
My E612 has some software problem. Somehow device remembered apps installed, settings, messages everything used once and now stuck on to it. Factory reset dosen't works. Everthing remains the same even after factory reseting. No root, bootloader locked. Complete stock. Any help is appreciated.
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
Flashing stock system over the current on your device might help you. You can search "firmware updating optimus l5"
Hello,
I have a LG L5 E612g and I followed this guide to unlock the bootloader (only that) and the result was that the phone boots like always, but after a while it reboots randomly. According to what I have read that is common when you use the wrong .bin. The thing is that there is not much information available about the differences between E612 and E612g (apparently it is a variant, maybe to South-America), and as a result I didn't know whether I should flash the e610.bin or the e612.bin. I tried the latter... and it failed.
What do you guys think? How can I revert to normal, do I have to flash the stock rom again? Should I try the e610.bin instead?
xXLosstarotXx said:
Hello,
I have a LG L5 E612g and I followed this guide to unlock the bootloader (only that) and the result was that the phone boots like always, but after a while it reboots randomly. According to what I have read that is common when you use the wrong .bin. The thing is that there is not much information available about the differences between E612 and E612g (apparently it is a variant, maybe to South-America), and as a result I didn't know whether I should flash the e610.bin or the e612.bin. I tried the latter... and it failed.
What do you guys think? How can I revert to normal, do I have to flash the stock rom again? Should I try the e610.bin instead?
Click to expand...
Click to collapse
Which baseband you're on? I had same thing when I flashed baseband which doesn't match with my device model. Make you sure you're on v20 baseband. I'm hoping it occurs cause of this fault.
Please help root.
LG-E612 v20f-ESA-XX
many thanks
So, after searching and asking to no avail, I decided to test it myself, and it works!
After you unlocks your android one device, your warranty bit is set to no, even if you lock it again afterwards.
This may or may not affects your real warranty service. But better safe than sorry.
This will also locks your bootloader once again.
Download
http://goo.gl/CPTQOf
How to use
1. Download file seccfg.img above
2. Download TWRP or CWM or PhilZ, if you don't already have it
3. Enter fastboot mode
4. Boot custom recovery
Code:
fastboot boot <path/to/custom/recovery/file.img>
5. After entering custom recovery, push my seccfg.img to internal memory:
Code:
adb push seccfg.img /sdcard/
6. (Optional) Do a backup to your original seccfg before overwriting it:
Code:
adb shell dd if=/dev/block/platform/mtk-msdc.0/by-name/seccfg of=/sdcard/seccfg_original.img
7. Overwrite the seccfg:
Code:
adb shell dd if=/sdcard/seccfg.img of=/dev/block/platform/mtk-msdc.0/by-name/seccfg
8. And you are done.
To check wether your warranty bit is back or not, back to fastboot and type this command:
Code:
fastboot getvar all
Alternative method using fastboot
After downloading, enter fastboot mode, and flash the file from there by using:
Code:
fastboot flash seccfg <path/to/seccfg.img>
and you're done.
Yet another alternative method using custom recovery
Just flash attached flashable zip via custom recovery, and you are done.
awaaas said:
So, after searching and asking to no avail, I decided to test it myself, and it works!
After you unlocks your android one device, your warranty bit is set to no, even if you lock it again afterwards.
This may or may not affects your real warranty service. But better safe than sorry.
Download
http://goo.gl/CPTQOf
How to use
1. Download file seccfg.img above
2. Download TWRP or CWM or PhilZ, if you don't already have it
3. Enter fastboot mode
4. Boot custom recovery
Code:
fastboot boot <path/to/custom/recovery/file.img>
5. After entering custom recovery, push my seccfg.img to internal memory:
Code:
adb push seccfg.img /sdcard/
6. (Optional) Do a backup to your original seccfg before overwriting it:
Code:
adb shell dd if=/dev/block/platform/mtk-msdc.0/by-name/seccfg of=/sdcard/seccfg_original.img
7. Overwrite the seccfg:
Code:
adb shell dd if=/sdcard/seccfg.img of=/dev/block/platform/mtk-msdc.0/by-name/seccfg
8. And you are done.
To check wether your warranty bit is back or not, back to fastboot and type this command:
Code:
fastboot getvar all
Click to expand...
Click to collapse
Yea It Works!
help
can any one help me how to do this process..icant understand how to proceed
rahuldasari12 said:
can any one help me how to do this process..icant understand how to proceed
Click to expand...
Click to collapse
I thiink its not that important to get the warranty back (at least on Indian variants) as flashing the stock ROM via SP flash tools of fastboot does the job. Interesting procedure by the way.......
rahuldasari12 said:
can any one help me how to do this process..icant understand how to proceed
Click to expand...
Click to collapse
I think it is pretty straightforward
Saurabh K said:
I thiink its not that important to get the warranty back (at least on Indian variants) as flashing the stock ROM via SP flash tools of fastboot does the job. Interesting procedure by the way.......
Click to expand...
Click to collapse
There's currently no checking either here in Indonesia, but better safe than sorry
Again, why would you want your warranty, there is a solution of any problem on XDA ....
Sent from my Sparkle V
Saurabh K said:
Again, why would you want your warranty, there is a solution of any problem on XDA ....
Sent from my Sparkle V
Click to expand...
Click to collapse
Some problems are simply not resolvable by us, for example, in this video, the phone's light sensor is broken, can you repair it by yourself? No, and reflashing the phone doesn't help. You still needs the warranty service for something that outside your reach/knowledge.
Any manufacturing defect is always the responsibility of the company and any hardware damage done intentionally is not covered under warranty if I'm right. I appreciate your work and of course I'm not arguing.
Sent from my Sparkle V
Will it work for 8 gb devices too ?
DarkHeart Z said:
Will it work for 8 gb devices too ?
Click to expand...
Click to collapse
Yes, I personally tested this on 8 GB device.
awaaas said:
Yes, I personally tested this on 8 GB device.
Click to expand...
Click to collapse
Thanks a lot lot much more bro you guys have made our day easier than ever
awaaas said:
Yes, I personally tested this on 8 GB device.
Click to expand...
Click to collapse
And one last thing I need to know . I booted into twrp but adb is not working can I know why ?
DarkHeart Z said:
And one last thing I need to know . I booted into twrp but adb is not working can I know why ?
Click to expand...
Click to collapse
Check your device manager, maybe your device isn't yet installed properly. Install the driver manually if that actually the case.
awaaas said:
Check your device manager, maybe your device isn't yet installed properly. Install the driver manually if that actually the case.
Click to expand...
Click to collapse
Checked . No missing driver showed . same thing happened with sp flash tool too . but later after 1st unlocking bootloader driver got recognized . I am wondering if it is the cause .
DarkHeart Z said:
Checked . No missing driver showed . same thing happened with sp flash tool too . but later after 1st unlocking bootloader driver got recognized . I am wondering if it is the cause .
Click to expand...
Click to collapse
I have updated the original post with flashable zip, just flash it via your custom recovery, and you should be done.
awaaas said:
I have updated the original post with flashable zip, just flash it via your custom recovery, and you should be done.
Click to expand...
Click to collapse
Thanks bro . Will you create a flashable zip for backing up orginal seccfg ? please . since I cannot access adb from recovery so it will be really helpful for all of us
Edit : Latest twrp has this kickass feature called terminal command . this fixed my problem . I backed up my original seccfg with it .
Edit : Bro the the person who modified the recovery actually broked the adb and many other features too . I used @1cefire 's recovery and everything is perfect there . just like mini android os in recovery .
Thank you very much for this, I made my own seccfg backup after reading this thread, and I'm glad I did. I managed to restore it as well. No need to worry anymore about warranty
Please help me
Download the latest Superuser Zip and flash it using TWRP Recovery (Unlocked bootloader is required for rooting)
[email protected] said:
Download the latest Superuser Zip and flash it using TWRP Recovery (Unlocked bootloader is required for rooting)
Click to expand...
Click to collapse
Is there any way to flash it via flashtool?
My bootloader is unlocked.
Holydao said:
Is there any way to flash it via flashtool?
My bootloader is unlocked.
Click to expand...
Click to collapse
I dont know the other way.
If you already unlocked the bootloader, flash TWRP Recovery using Fast Boot Command and then flash SU Zip using TWRP.
[email protected] said:
I dont know the other way.
If you already unlocked the bootloader, flash TWRP Recovery using Fast Boot Command and then flash SU Zip using TWRP.
Click to expand...
Click to collapse
Thank you very much, I''ll try asap.
[email protected] said:
I dont know the other way.
If you already unlocked the bootloader, flash TWRP Recovery using Fast Boot Command and then flash SU Zip using TWRP.
Click to expand...
Click to collapse
Which version of TWRP should I use for Z3+ (E6553) on nougat (32.3.A.0.372_R3D_Customized RU_1295-0592)?
Holydao said:
Which version of TWRP should I use for Z3+ (E6553) on nougat (32.3.A.0.372_R3D_Customized RU_1295-0592)?
Click to expand...
Click to collapse
Check this step by step guide: https://forum.xda-developers.com/xperia-z4/general/guide-safe-bootloader-unlock-restore-t3386915
[email protected] said:
Check this step by step guide: https://forum.xda-developers.com/xperia-z4/general/guide-safe-bootloader-unlock-restore-t3386915
Click to expand...
Click to collapse
I don't know why but I just couldn't make it, I got soft brick everytime and I flashed to "32.3.A.0.372_R3D_Customized RU" for hundred times. I quit trying that.
Now I'm trying to root my E6553 (on 32.2.A.0.224), stiil couldn't make it either. It stucks on SONY logo or endless boot loop. I just want to root it for once, not to flash twrp but to boot on twrp and flash SU. Isn't that what we call "root"? Am I wrong?
My device bootloader is unlocked, on stock MM rom "32.2.A.0.224". I just want to boot it on TWRP and flash SU, that's all. Isn't that enough for rooting? After that I want to use some apps that only works on rooted devices.
Anyway, thank you for your help, I really apreciate that but I still need help more than ever, each post that I followed to root my device ended in a bad way.
I have essential drivers, my bootloader is unlocked. What is wrong with my device? I tried lots of boot.img's, recovery.img and twrp1.img's but nothing changed...
Holydao said:
I don't know why but I just couldn't make it, I got soft brick everytime and I flashed to "32.3.A.0.372_R3D_Customized RU" for hundred times. I quit trying that.
Now I'm trying to root my E6553 (on 32.2.A.0.224), stiil couldn't make it either. It stucks on SONY logo or endless boot loop. I just want to root it for once, not to flash twrp but to boot on twrp and flash SU. Isn't that what we call "root"? Am I wrong?
My device bootloader is unlocked, on stock MM rom "32.2.A.0.224". I just want to boot it on TWRP and flash SU, that's all. Isn't that enough for rooting? After that I want to use some apps that only works on rooted devices.
Anyway, thank you for your help, I really apreciate that but I still need help more than ever, each post that I followed to root my device ended in a bad way.
I have essential drivers, my bootloader is unlocked. What is wrong with my device? I tried lots of boot.img's, recovery.img and twrp1.img's but nothing changed...
Click to expand...
Click to collapse
Sorry bro, forgot to tell you that you also need a patched stock kernel (with DM Variety & Sony RIC disabled and DRM fixed). After that only you can flash SU Zip. Else it will be boot looped. Check guide link for making patched kernel of you choice of version with one little tool. You can also flash custom Kernel like Zach Kernel, Andro Plus Kernel... etc instead of patched stock kernel to avoid bootloop after SU flash.
AND MY XPERIA OPTION TO BE TURNED OFF else also will in boot loop.
Now the steps are as follows:
Flash Stock ROM
Flash patched kernel
Flash TWRP Recovery
Flash SU Zip
That's it
More info Patched Kernel and DM Variety & Sony RIC disabled and DRM fixed: LINK
I did it at last
One of the kernels didn't create a bootloop after I tried aprox. 128 times and after that SU was flashed. Now I have substratum on MM, thanks again
E6553 cihazımdan Tapatalk kullanılarak gönderildi
Holydao said:
I did it at last
One of the kernels didn't create a bootloop after I tried aprox. 128 times and after that SU was flashed. Now I have substratum on MM, thanks again
E6553 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
Ohhhhh... Great...
But tried 128 times??? OMG... You have to spend some time on reading all TECH and FAQ posts before attempting the 3rd atleast bro.... :laugh::good:
I spent my whole time after work and slept at 3 am for 4 days, spent aprox 30 hours... I read every discussion about root 5 times on forum. ?
Why is it so hard to find a proper kernel to root?
E6553 cihazımdan Tapatalk kullanılarak gönderildi
Hello!
Where can I find the stock recovery .img for my VIE-L29C636? I wish to update my P9 Plus to version B632 but since my phone is rooted and I use the TWRP custom recovery, I'm not able to do so.
Cheers
mechasnyper
mechasnyper said:
Hello!
Where can I find the stock recovery .img for my VIE-L29C636? I wish to update my P9 Plus to version B632 but since my phone is rooted and I use the TWRP custom recovery, I'm not able to do so.
Cheers
mechasnyper
Click to expand...
Click to collapse
Use HuaweiUpdateExtractor and download a firmware and extract the recovery.img
Sent from my HUAWEI LON-L29 using XDA Labs
Mostar088 said:
Use HuaweiUpdateExtractor and download a firmware and extract the recovery.img
Sent from my HUAWEI LON-L29 using XDA Labs
Click to expand...
Click to collapse
Thank you very much! Worked for me!
mechasnyper said:
Thank you very much! Worked for me!
Click to expand...
Click to collapse
Can you explain how you got it? I'm on VIE-L09C432B360 and I receive an update to B370 but when the download finishes, the phone restarts and when TWRP tries to install the update I got an error (which I can't read). My guess, the update fails because of TWRP. So I want to reinstall the stock recovery. Can you explain the steps you followed? Thanks in advance.
alfesc said:
Can you explain how you got it? I'm on VIE-L09C432B360 and I receive an update to B370 but when the download finishes, the phone restarts and when TWRP tries to install the update I got an error (which I can't read). My guess, the update fails because of TWRP. So I want to reinstall the stock recovery. Can you explain the steps you followed? Thanks in advance.
Click to expand...
Click to collapse
No problem! Haha, lucky timing, I was about to head to bed.
Anyways, you will need Android-SDK platform tools, Huawei Update Extractor, which you can download here, and the CURRENT firmware file of your device, which you can download using Huawei Firmware Finder here. Here's how you do it...
1. Find and download your firmware using Huawei Firmware Finder. Go to the common base tab and enter your CURRENT build number in the textbox labeled "Model for find". Under the "type" list, find the one that says "FullOTA" and click the link under the "Filelist". This opens a new window with a list of links. Open the link that ends with "update.zip". That will download your firmware.
2. Open the zip file and extract the file called "UPDATE.APP"
3. Open the Huawei Update Extractor, and drag and drop the "UPDATE.APP" on the window. You will see a list of files. Select and right click "RECOVERY.img", and click on "Extract Selected" and set your file destination. This is the recovery software.
4. Once it has finished extracting, simply flash it as you would with TWRP.
Hope this helps! Don't be afraid to ask if you need more help.
mechasnyper said:
No problem! Haha, lucky timing, I was about to head to bed.
Anyways, you will need Android-SDK platform tools, Huawei Update Extractor, which you can download here, and the CURRENT firmware file of your device, which you can download using Huawei Firmware Finder here. Here's how you do it...
1. Find and download your firmware using Huawei Firmware Finder. Go to the common base tab and enter your CURRENT build number in the textbox labeled "Model for find". Under the "type" list, find the one that says "FullOTA" and click the link under the "Filelist". This opens a new window with a list of links. Open the link that ends with "update.zip". That will download your firmware.
2. Open the zip file and extract the file called "UPDATE.APP"
3. Open the Huawei Update Extractor, and drag and drop the "UPDATE.APP" on the window. You will see a list of files. Select and right click "RECOVERY.img", and click on "Extract Selected" and set your file destination. This is the recovery software.
4. Once it has finished extracting, simply flash it as you would with TWRP.
Hope this helps! Don't be afraid to ask if you need more help.
Click to expand...
Click to collapse
On step 4 you mean type "fastboot flash recovery recovery.img" from fastboot mode?
Thanks. I'm gonna try today.
Enviado desde mi VIE-L09 mediante Tapatalk
alfesc said:
On step 4 you mean type "fastboot flash recovery recovery.img" from fastboot mode?
Thanks. I'm gonna try today.
Enviado desde mi VIE-L09 mediante Tapatalk
Click to expand...
Click to collapse
Yep! That's how you flash the recovery.
Thanks. I hope you had a nice sleep.
Anyway I did it via flashify, but what I get is eRecovery and I think it's not the same as stock recovery.
Sorry to bother you again, but options are not the same than stock recovery. In eRecovery you haven't options to wipe, only download new versions and reboot/shutdown. As I don't know if stock recovery has been properly installed, I don't dare to install the B370 update.
Enviado desde mi VIE-L09 mediante Tapatalk
alfesc said:
Thanks. I hope you had a nice sleep.
Anyway I did it via flashify, but what I get is eRecovery and I think it's not the same as stock recovery.
Sorry to bother you again, but options are not the same than stock recovery. In eRecovery you haven't options to wipe, only download new versions and reboot/shutdown. As I don't know if stock recovery has been properly installed, I don't dare to install the B370 update.
Enviado desde mi VIE-L09 mediante Tapatalk
Click to expand...
Click to collapse
Hmm, obviously that's not right... Have you tried using ADB to reboot into your recovery? Try opening a command window and try typing in "adb reboot recovery". That's usually how you get into your recovery other than turning on your phone by holding both your volume up and power button until you see the recovery screen. If that doesn't work try flashing again using adb instead of Flashify.
mechasnyper said:
Hmm, obviously that's not right... Have you tried using ADB to reboot into your recovery? Try opening a command window and try typing in "adb reboot recovery". That's usually how you get into your recovery other than turning on your phone by holding both your volume up and power button until you see the recovery screen. If that doesn't work try flashing again using adb instead of Flashify.
Click to expand...
Click to collapse
I thought it wasn't ok. Today I haven't got a computer near. I'll try tomorrow and let you know. I really appreciate your help.?
Enviado desde mi VIE-L09 mediante Tapatalk
mechasnyper said:
Hmm, obviously that's not right... Have you tried using ADB to reboot into your recovery? Try opening a command window and try typing in "adb reboot recovery". That's usually how you get into your recovery other than turning on your phone by holding both your volume up and power button until you see the recovery screen. If that doesn't work try flashing again using adb instead of Flashify.
Click to expand...
Click to collapse
Cool! "flashboot flash recovery recovery.img" worked. Stock Recovery is working know. I'm going to try to install update know. Thanks again.
alfesc said:
Cool! "flashboot flash recovery recovery.img" worked. Stock Recovery is working know. I'm going to try to install update know. Thanks again.
Click to expand...
Click to collapse
Great! Let me know how it turns out!
mechasnyper said:
Great! Let me know how it turns out!
Click to expand...
Click to collapse
Everything working fine. I'm now on b370 and I have reinstalled TWRP. My next step, reRoot. Thanks again. I've learned a lot and practiced my rusty English.
Enviado desde mi VIE-L09 mediante Tapatalk
Hi @mechasnyper
I'm on stock B360, rooted and twrp installed. I got an update of B380 and as described by others I was unable to update through twrp. I tried your method, downloaded B360 firmware through FIRMWARE FINDER, when I opened "UPDATE. APP" in update extractor, I got two images of recovery "RECOVERY.IMG" & "RECOVERY2.IMG". I extracted "RECOVERY.IMG" and flashed. Everything went fine recovery flashed successfully.
After that I started OTA update. It started flashing but it is giving me error when reaches at 5%. Kindly tell me what is wrong?
My variant is: VIE-L29C185
faakher said:
Hi @mechasnyper
I'm on stock B360, rooted and twrp installed. I got an update of B380 and as described by others I was unable to update through twrp. I tried your method, downloaded B360 firmware through FIRMWARE FINDER, when I opened "UPDATE. APP" in update extractor, I got two images of recovery "RECOVERY.IMG" & "RECOVERY2.IMG". I extracted "RECOVERY.IMG" and flashed. Everything went fine recovery flashed successfully.
After that I started OTA update. It started flashing but it is giving me error when reaches at 5%. Kindly tell me what is wrong?
My variant is: VIE-L29C185
Click to expand...
Click to collapse
What error does it give you?
Hey all, I'm in a similar situation in that I'm trying to restore stock recovery in order to receive the new B386 OTA update.
Problem is, I'm on B385 firmware and the last version available for download is B384. Does anyone know if it would be possible to extract the B384 recovery and flash that, or is that just a really bad idea?
I'd really rather not do a factory reset all for the sake of a Google security patch
After giving up last year I came back to try again and everything worked smoothly. Don't know why I had trouble the first time!
To anyone with a rooted device who wants to go back to receiving OTA updates, just follow mechasnyper's instructions and download the full firmware zip for your current OS version in Firmware Finder, extract and flash recovery.img, and hey presto.
Now to just sit and wait for the L29 Oreo update to arrive