Database Users

[Recovery]CWM 6.0.4.5[UPDATED WITH INSTRUCTIONS][25/12/2013]

Well here is cwm 6.0.4.5 for our beloved a500. You will need this to flash KitKat ROMs like the new kitkat rom that was recently relased for our tablet. It is recommended that you flash this in secboot as I am not very sure what works and what does not. It pays to have a working recovery in your recovery partition.
To flash this rom in your secboot, you must have skrilax bootloader installed from http://forum.xda-developers.com/showthread.php?t=1619913
Download link of recovery: http://www.mediafire.com/view/?myy59371lsrs6u4
Instructions:
1. Use this awesome tool from http://forum.xda-developers.com/showthread.php?t=2588979 to install adb and fastboot on your windows pc easily. (Remember to run the downloaded exe as administrator)
2. Install Acer A500 usb drivers from http://us.acer.com/ac/en/US/content/drivers (Just search for A500 in the search by product model search box.)
3. Make sure you have Skrilax_CZ's bootloader installed on your A500.
4. Turn off your A500 and turn it on again, this time holding the volume up button.
5. When the bootloader screen appears, scroll with the volume buttons and select Fastboot with the power button.
6. Now, copy the recovery.img which you downloaded from the download link above to the root of your C:/ drive.
7. Press start and open cmd.
8. In cmd, type cd C:/
9. Now, connect your A500 to the PC via usb and wait for a while before typing
Code:
fastboot flash secboot recovery.img
in cmd.
10. After the process is done, type
Code:
fastboot reboot
into cmd.
11. When the tablet boots, hold volume up and when the bootloader screen shows, scroll to Boot Secondary Kernel Image with the volume keys and select it with the power button. CWM should load and have fun!!!
Thanks to @pjsports for his 4.3 device source and vendor blobs

nelsontky said:
Well here is cwm 6.0.4.5 for our beloved a500. You will need this to flash KitKat ROMs in the future. It is recommended that you flash this in seboot as I am not very sure what works and what does not. It pays to have a working recovery in your recovery partition.
Download link: http://www.mediafire.com/view/?myy59371lsrs6u4
Installation:
fastboot flash secboot recovery.img (recommended)
Or
fastboot flash recovery recovery.img
Thanks to @pjsports for his 4.3 device source and vendor blobs
Click to expand...
Click to collapse
ok this is what i get when i try to flash this or any recovery
C:\sdk-tools>fastboot flash recovery recovery.img
sending 'recovery' (5132 KB)... OKAY [ 1.278s]
writing 'recovery'... FAILED (remote: (00030003))
finished. total time: 1.675s
C:\sdk-tools>
any ideas?
ok I got a recovery on there but now it is not seeing any files within my folders- this is so strange

I tried flashing this recovery but i get this error
also i tried flashing the img recovery with this app but i don't work either
https://play.google.com/store/apps/details?id=com.cgollner.flashify

nsciucco said:
ok this is what i get when i try to flash this or any recovery
C:\sdk-tools>fastboot flash recovery recovery.img
sending 'recovery' (5132 KB)... OKAY [ 1.278s]
writing 'recovery'... FAILED (remote: (00030003))
finished. total time: 1.675s
C:\sdk-tools>
any ideas?
ok I got a recovery on there but now it is not seeing any files within my folders- this is so strange
Click to expand...
Click to collapse
Erm what ROM are u using. And yea do you have like zip files in your folders cos I think the recovery only see zip files

tire_007 said:
I tried flashing this recovery but i get this error
also i tried flashing the img recovery with this app but i don't work either
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Click to expand...
Click to collapse
Dun use the app (idk those apps never worked for me, well except for the Acer recovery installer) and when using fastboot, make sure the recovery.IMG is in the same directory as fastboot

I was on cm10.2. My tablet froze so I held the power button down to hard reset. Then it never booted up. I tried to go into recovery to install a new rom and I'm not even able to get into downloads. If I click sd or sd-ext there is no folders anything. It's like my device is wiped. I'm stuck. Only thing I can do is get into bootloader or apx mode. I've downloaded roms that I can supposedly flash in apx mode with that blackthunder tool. But I can't figure it out. I'm not an idiot either. I've rooted well over 200 phones . I do it for extra cash...and never had a issue like this
Sent from my SM-N900P using xda app-developers app

nsciucco said:
I was on cm10.2. My tablet froze so I held the power button down to hard reset. Then it never booted up. I tried to go into recovery to install a new rom and I'm not even able to get into downloads. If I click sd or sd-ext there is no folders anything. It's like my device is wiped. I'm stuck. Only thing I can do is get into bootloader or apx mode. I've downloaded roms that I can supposedly flash in apx mode with that blackthunder tool. But I can't figure it out. I'm not an idiot either. I've rooted well over 200 phones . I do it for extra cash...and never had a issue like this
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Hmmm download a working recovery and flash into your recovery partition. Then flash this into secboot

Flash what?
Sent from my SM-N900P using xda app-developers app

nsciucco said:
Flash what?
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Well you can download twrp from http://teamw.in/project/twrp2/88 and flash it to your secboot partition with "fastboot flash secboot [name of recovery].img" Then go to your boot menu (hold volume up when booting) and choose the akb partition (second partition) This should get you booted into twrp where your files should be there. If there are still no files, you have to use an external sdcard good luck

any chance you can build this: http://forum.xda-developers.com/showthread.php?t=2201860
against our device + CWM version 6.0.4.8?
I'd do it, but I have no idea where to start. I love PhilZ touch recovery, it's very customizable and also very useful.

kronflux said:
any chance you can build this: http://forum.xda-developers.com/showthread.php?t=2201860
against our device + CWM version 6.0.4.8?
I'd do it, but I have no idea where to start. I love PhilZ touch recovery, it's very customizable and also very useful.
Click to expand...
Click to collapse
Well i can try but no promises

thanks! apparently it's easy.
Once you can build stock CWM, just replace your bootable/recovery folder with this one and lunch for your device
Click to expand...
Click to collapse
I just don't have the sources, or the knowhow to compile this myself.

nelsontky said:
Well i can try but no promises
Click to expand...
Click to collapse
had a chance to try yet? not to bug or nag, just curious for an update

Now updated with instructions
Now this is updated with instructions!

thanks man.
good work

nelsontky said:
Now this is updated with instructions!
Click to expand...
Click to collapse
can you provide building instructions? I tried using the sources you used, but I get errors using his repos. He's got some repos from "loosethisskin" which don't allow building. I can't remember the exact errors, but I'm wondering what you did to avoid this(if you encountered this at all)
By simply not replacing those repos(ie: removing them from the manifest before syncing) I get a resulting recovery.img that fails to fastboot flash.
I've even tried using acer recovery flasher, and a couple other tools, but it doesn't boot.
I'd like to try building 6.0.5.0 as well as PhilZ Recovery, but again, I can't get it to build.

@nelsontky
Thanks for your job.
I want to make a backup before to install the new Bootloader ( Skrilax_CZ's), but to that I cannot do it with stock recovery (the stock recovery didn't have the option to backup/restore).
Is there some problem/incompatibility that avoid to load your recovery (6.0.4.5) before to load Skrilax_CZ's bootloader?
Or in another way the function of your recovery are based on Skrilax_CZ's bootloader?
Could you update your recovery with new file from CWM Github (recovery version is now 6.0.5.0)?
Could you post the configuration file (Board parameters) that you use to compile the recovery.
I downloaded the source of CWM and I want to test it myself.
If you update your CWM repository via GitHub pull command just recompile the recovery.
Proposal to download the file: could be better to distribute the recovery as zip (like A500_CWM_recovery_vx.x.x.x.x.zip - it's self explantory) with inside the recovery.img file. It's always better to avoid to download native recovery image to avoid partial download or corrupted file.
Thanks.

bovirus said:
@nelsontky
Thanks for your job.
I want to make a backup before to install the new Bootloader ( Skrilax_CZ's), but to that I cannot do it with stock recovery (the stock recovery didn't have the option to backup/restore).
Is there some problem/incompatibility that avoid to load your recovery (6.0.4.5) before to load Skrilax_CZ's bootloader?
Or in another way the function of your recovery are based on Skrilax_CZ's bootloader?
Could you update your recovery with new file from CWM Github (recovery version is now 6.0.5.0)?
Could you post the configuration file (Board parameters) that you use to compile the recovery.
I downloaded the source of CWM and I want to test it myself.
If you update your CWM repository via GitHub pull command just recompile the recovery.
Proposal to download the file: could be better to distribute the recovery as zip (like A500_CWM_recovery_vx.x.x.x.x.zip - it's self explantory) with inside the recovery.img file. It's always better to avoid to download native recovery image to avoid partial download or corrupted file.
Thanks.
Click to expand...
Click to collapse
The Skrilax_CZ bootloader is absolutely necessary, because it allows flashing and booting from the secboot. The recovery is too large to fit in the recovery partition. That having been said, I may be able to shrink it to fit, if I could get it to compile and boot.
I've had to do the same thing to the recovery for the HTC ChaCha,
He's not using a straight up CWM repo, he would be using the repos for CM10.2, which automatically compiles CWM along with it(or if you give it the arguments, it can compile just recovery)
The bootloader can only be flashed using nvflash, and for a backup, you'll need an older copy of CWM and flash that via fastboot. I personally recommend the tegraowners recovery(I don't like the tegraowners team, but their recovery really is best out of the older ones) you can find it here

Apparently windows 8 hates my tablet. so I tried it on a windows 7 machine, the result was a working recovery. although oddly, it build 6.0.4.6, not 6.0.5.0. weird. maybe I'll poke at it later and try to update just the cwm repo. whatever the case, this gives me a working setup to try PhilZ Touch Recovery

I believe that the main scope should be to have a recovery that use no more space than the partition size.
It's due to avoid not use unofficial bootloader and to avoid overwiting importan partition like NVRAM (IMEI).

[RECOVERY][YotaPhone2][Lollipop][ROOT]Modified YotaPhone 2 Stock Recovery for ROOT

YotaPhone 2 ROOT with modified stock recovery​
NOTE:
Check out the more functional TWRP recovery for YotaPhone 2.
Since not much dev work is happening on the YotaPhone 2, I though I'd kick off by publishing a recovery image that will hopefully allow you to root your YotaPhone 2 device with lollipop, and e.g. make partition backups.
First off: Disclaimer!
I am not responsible for damaged or bricked devices. If you follow instructions in this post, then YOU are making the choice to tinker with your device, and you are likely to void your warranty by doing so. You might even damage or brick your device, so ask yourself if the benefits outweigh the risks, because after proceeding you are pretty much on your own.
What is it?
It's a slightly modified stock recovery that allows to install packages signed with testkeys, plus adb root access and busybox for e.g. shell. That's it.
What can you do with it?
- adb root & shell access (e.g. to manually backup partitions or modify system files)
- install update zips signed with testkeys (e.g. SuperSU) in addition to original Yota Devices software
- root your device
What can it NOT do?
- probably can NOT install unsigned zips (must be signed by YD (like fota update zips), OR signed with standard testkeys)
- no fancy features, just boring AOSP stock recovery as included in stock firmware
- installing of apks/zips only through adb sideload, not from (emulated) SD card
What do you need?
- YotaPhone 2 (YD201) with Lollipop 5.0, I used firmware 1.39 YMMV with other versions
- Some technical confidence
- USB cable with a PC or laptop on one end
Steps overview:
1) First read the whole post to understand what's going to happen
2) backup (sync stuff, copy photos off, use a backup app etc, use search if unsure how to)
3) Unlock the bootloader
4) Install adb and fastboot if not yet installed. (For Windows look e.g. here, for linux the fastest is probably to install Android SDK with platform tools, see here If this is not enough info to get you started, please use xda search!)
5) Download recovery image: yd201_reco_139_testkeys_v01.img
6) boot the recovery image
7) root the device by sideloading SuperSU,
Unlocking bootloader:
Warning 1: It is currently not known how to re-lock the bootloader. (fastboot oem lock just hangs). This means you cannot completely undo the next step as of yet. This might have consequences for sending the device in for repairs, if they check for this, and deem it a (warranty) problem.
Warning 2: on some devices unlocking the bootloader wipes the device clean to factory defaults. I didn't see this happening on my YD201, but be warned, backup first!
On Linux:
Code:
sdk/platform-tools$ sudo ./fastboot oem unlock
...
OKAY [ 0.002s]
finished. total time: 0.002s
On Windows:
Code:
C:\android-sdk-windows\platform-tools>fastboot oem unlock
...
OKAY [ 0.002s]
finished. total time: 0.002s
Maybe Windows will install some extra drivers in the process.
BOOT the recovery image:
a) First: put the device in fastboot/download mode:
method 1: Power off with USB cable disconnected, then hold volume down key while inserting USB cable (which should already be in your PC on the other end).
method 2: do a
Code:
adb reboot bootloader
You should see a black screen with a tiny white: downloading...
b) boot the recovery image:
On linux:
Code:
sdk/platform-tools$ sudo ./fastboot devices
Should show a connected device in fastboot mode, then proceed:
Code:
sdk/platform-tools$ sudo ./fastboot boot <path>/<to>/yd201_reco_139_testkeys_v01.img
Where <path>/<to>/yd201_reco_139_testkeys_v01.img is the path you downloaded the image file to (e.g. ~/Download/yd201_reco_139_testkeys_v01.img)
On Windows:
copy the yd201_reco_139_testkeys_v01.img file to the folder with fastboot.exe (here assuming C:\android-sdk-windows\platform-tools, and D:\downloads as download location for the img)
* snippet below is fabricated, but you get the idea
Code:
D:\>C:
C:\>cd C:\android-sdk-windows\platform-tools
C:\android-sdk-windows\platform-tools>fastboot.exe devices
Should show a connected device in fastboot mode, then proceed:
Code:
C:\android-sdk-windows\platform-tools>copy D:\downloads\yd201_reco_139_testkeys_v01.img . [i]note the dot at the end[/i
C:\android-sdk-windows\platform-tools>fastboot.exe boot yd201_reco_139_testkeys_v01.img
Hopefully you see the screen go completely black after a few seconds, and recovery menu will appear. Like stock recovery, it will show an error (E:Cannot load volume /misc) but you can ignore that, along with the 'error' triangle icon that goes with it.
If booting fails with a signature error, the bootloader is probably not properly unlocked, try again.
Note that this recovery image could be flashed too (I haven't actually tried to flash yet), but if you're cautious (as we are in this post) you can just boot it every time you need it.
SuperSU flashing:
1) download Chainfire's SuperSU flashable zip from this page, filename is:UPDATE-SuperSU-v2.46.zip
2) Assuming you're still in custom recovery, otherwise boot into custom recovery again as outlined above
3) choose "apply update from ADB" from the menu (choose with volume up/down keys, confirm with power key). Recovery now waits for a file.
4) on the connected PC:
on Linux:
Code:
sdk/platform-tools$ adb sideload <path>/<to>/UPDATE-SuperSU-v2.46.zip
on Windows:
Code:
D:\>C:
C:\>cd C:\android-sdk-windows\platform-tools
C:\android-sdk-windows\platform-tools>copy D:\downloads\UPDATE-SuperSU-v2.46.zip .
C:\android-sdk-windows\platform-tools>adb.exe sideload UPDATE-SuperSU-v2.46.zip
5) on the phone you should see SuperSU installing.
6) reboot when done
7) if SuperSU app is not visible in launcher, download & install SuperSU from playstore.
To verify if rooting worked, start SuperSU. If that looks OK, start an app that requires root (like e.g. betterbatterystats) or use a simple checkroot app from the store. Reboot and check again if it persisted.
NOTE: you could also FLASH this image, replacing the stock recovery on the recovery partition permanently (until you flash again). Above we're just BOOTing it once, next time entering recovery in the standard way will just load the stock recovery from the recovery partition). You would use fastboot flash instead of fastboot boot above. Flashing is UNTESTED.
Problems & FAQ
Q: It doesn't work!!1!
A: Please provide plenty of detail about error messages, which step, what versions etc. Without providing any detail you'll look silly.
Q: I don't know how to <backup/adb/download/reboot/flash>
A: Please use the search button, xda forums have lots of info
Q: How can I tell if I'm in stock recovery or modded stock recovery? They look the same!
A: The Droid error icon with the triangle in the centre of the modded recovery screen has some white text (yd201_cr0.1), the stock one doesn't.
Future development
I hope that there are some devs out there willing to work on the YotaPhone 2 in the near future. I'll try to tinker a bit every now and then, but I cannot promise anything as I'm no expert. To enable proper development of custom ROMs and better recoveries (e.g. TWRP) it would be great if Yota Devices released their Kernel sourcecode for the kernel they use in their YotaPhone 2 ROMs. I know they have been asked to release sources before (and they should in order to comply with the GPL license), but so far without response.
Good news is that You Can Help! Please stimulate Yota to publish Kernel sourcecode for YotaPhone 2 through their support page (hint: choose 'sales' as category, otherwise you'll have to enter lots of details. Be polite!).
Info::
Mod by: SteadyQuad
Version: 0.1 based on YD stock recovery 5.0 1.39 EU
Thanks to: Yota Devices for a great device, Jeopardy for testing and suggestions, Chainfire for SuperSU
Created: 2015-06-10
Last Updated: 2015-06-20 (added warning about current inability to re-lock bootloader)

As SteadyQuad already mentioned, I can confirm that this method works.
Bye bye Google Newsstand! Goodbye Google Books!
(When uninstalling system apps Lollipop handles a bit differently from Kitkat, and I had to always restart the device after deleting.)
Thank you very much for your effort SteadyQuad.

Allelujah!
Thanks SteadyQuad for this great job! It works like a charm!
:good:
Anybody tried to install xposed module on rooted Yotaphone2? (alpha 4 modules)?
I think it little bit risky that's why I'm asking...
Or maybe somebody know how to make a full backup Yotaphone (like in CWM)?
Thanks in advance again for a really great job!

zencooler said:
Allelujah!
Thanks SteadyQuad for this great job! It works like a charm!
:good:
Anybody tried to install xposed module on rooted Yotaphone2? (alpha 4 modules)?
I think it little bit risky that's why I'm asking...
Or maybe somebody know how to make a full backup Yotaphone (like in CWM)?
Thanks in advance again for a really great job!
Click to expand...
Click to collapse
I haven't tried testing xposed yet, but am planning to sooner or later.
Running that custom recovery we do have root level access to everything, so it should be possible to create a backup from there with the help of a computer. Have to look into this.

the recovery download doesn't work.
EDIT : it worked on laptop
How about somebody can compile a TWRP recovery because Yotaphone has posted there SDK ?
So we can make Nandroid backup.

a question : if you can modify stock recovery,
can't you compile from TWRP source and yotaphone SDK a TWRP recovery for the yotaphone 2 users ?
just my 2 cents, i evenly willing to pay for it

Gojira-r32 said:
a question : if you can modify stock recovery,
can't you compile from TWRP source and yotaphone SDK a TWRP recovery for the yotaphone 2 users ?
just my 2 cents, i evenly willing to pay for it
Click to expand...
Click to collapse
I think if we all contribute to twrp and request them they might make us one
Sent from my YD201 using Tapatalk

Can the bootloader be re locked And can the root be removed for warranty purposes
Sent from my YD201 using Tapatalk

Yes
Fastboot oem lock

Gojira-r32 said:
Yes
Fastboot oem lock
Click to expand...
Click to collapse
If the recovery image is modified don't we flash back to stock before oem lock
Sent from my YD201 using Tapatalk

Good work. A pity Xposed framework isn't compatible yet.
Sent from my YD201 using XDA Free mobile app

dai75 said:
Good work. A pity Xposed framework isn't compatible yet.
Sent from my YD201 using XDA Free mobile app
Click to expand...
Click to collapse
Xposed framework isn't FULLY compatible, but many features already work. See SteadyQuad's thread here

adamo86 said:
Can the bootloader be re locked And can the root be removed for warranty purposes
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
I haven't been able to re-lock it when I last tried (fastboot oem lock just hung). If anyone did succeed to lock, let us know! (Gojira-r32: did you actually execute the fastboot oem lock?)

I also failed to lock it back . I wanted to install the new update 1.44 that arrive in France but it failed at the recovery stage. E:Error in cache/update/yota....zip (status 7)
I did a wipe cache partition but not a wipe data as I don't want to lose all my settings. Anyone achieved to install the new Yota update version? And then root?

I just updated to latest update in UK. But I tried Kingo no success still.
Sent from my YD201 using Tapatalk

and the first post with flashing S%U tru modified recovery ?
is this firmware somewhere to download?
still not yet on yota FTP

Has anyone the stock recovery image? Maybe I'll achieve to get the OTA update after unrooting my YD201 with the original stock recovery firmware.

i am doing that right now, unroot, flash stock recovery, i have the OTA 1.1.44 pulled out of phone after download and will try to flash it

stock recovery, boot, sustem img, unrooted, everything tried
also got other build, fixed that.
now yotaphone is completly stock and get :
error in update zip "status 7"
so i think this update is no good, some faults in it, that's why we can't flash it yet, also chaged some things in OTA and resigned it etc... no good

Gojira-r32 said:
stock recovery, boot, sustem img, unrooted, everything tried
also got other build, fixed that.
now yotaphone is completly stock and get :
error in update zip "status 7"
so i think this update is no good, some faults in it, that's why we can't flash it yet, also chaged some things in OTA and resigned it etc... no good
Click to expand...
Click to collapse
Did you try to flash the OTA update via adb sideload in the modified recovery? I'm having the same problem.
Edit: I just tried to flash the update via adb sideload - no joy. I got the following error:
Package expects build fingerprint of YotaPhone/yotaphone2/yotaphone2:5.0/LRX21M/5.0.0-EU1.1.39:user/release-keys or Yotaphone/yotaphone2/yotaphone2:5.0/LRX21M/5.0.0-EU1.1.44:user/release-keys; this device has Yotaphone/yotaphone2/yotaphone:5.0/LRX21M/5.0
E:Error in /sideload/package.zip
(Status 7)
I also tried resigning the package with testkeys, but that didn't work either. Same error. So something has changed in the rooting process, because some people in the forum have managed to update normally, presumably on their nonrooted devices.

[TUTORIAL] Unbricking VNS-L21/VNS-L31

Hello everyone! I know there are a lot of threads and comments about unbricking your device but in order to get you on track quicker then anything else and point you to the right direction i`m writing this tutorial which i find is quite successfull. This tutorial was made basically on my personal experience and with the help of some advices and suggestions.
First of all there are some questions that you must ask and answer yourself in order to do everything correct:
1. Do i have unlocked bootloader and frp? If yes, continue reading. If no, read Important note 2!
1.1. Do i have access to stock/custom recovery? If yes then continue to read.
1.2 Do i have problems mounting partitions with Revolution Recovery? If yes, read Important note 1!
3. Do i have installed SDK Platform Tools (ABD and FASTBOOT)? If no then download from here (Always use the latest version!!!)
4. Do i have installed HiSuite? If no then download it from here.
Okey mate if all your answers are Yes then follow Guide 1!
5. If you think your device don`t have access to these then read and follow Guide 2!
For those of you with locked FRP you can check this website and see if it helps!
How to get into fastboot?
Variant 1
Hold down (VOL-) + POWER when connected to PC!
Variant 2
1.Start HiSuite.
Step 2 (Click for image preview)
Step 3 (Click for image preview)
Turn off your phone and then by holding down (VOL-) + POWER connect usb to the pc!
! Important note 1 !
If you can`t mount partitions then the thing you must do is go to Revolution Recovery then do as i say:
Wipe -> Advanced Wipe -> Select partitions one at a time! -> Repair or change file system -> Change file system -> F2FS -> Then go back -> Select EXT4 -> And voila u`re done!
! Important note 2 !
Okay easy way to find out is if you see warning screen about unlocked bootloader then it is unlocked so it is frp. If you go to fastboot and you see Bootloader: unlocked/frp: unlocked but you don`t see the warning screen then my friend u`re not unlocked! Quickly open up the console window connect to fastboot and type:
Code:
fastboot oem unlock <your unlock code here>
Easy, a?
GUIDE 1
First of all download these files in order to continue. (Place them somewhere easy to find! )
Recovery - Revolution Recovery NOUGAT
(I can guarantee you that this version works that`s why i used her in this tutorial! METICULUS was not working for me it doesn`t even started at first place.)
Stock OEM info - Download
Stock ROM - L21C432B130
1. Open up fastboot then flash Revolution Recovery from the zip.
Code:
fastboot flash recovery recovery_twrp.img
2. Start up Revolution Recovery by connecting your device to the PC and holding down (VOL +) + (VOL -) + POWER
3. Flash Stock OEM info from the zip via Revolution Recovery. Make sure when installing it the result was Successfull!!!
4. Remove usb cable from PC and Shutdown the device via Recovery and don`t plug the cable or start the phone!
4. Get your SD Card ready and plugged to the PC then Create a New Folder named "dload" in the root directory of the SD Card and paste update.app file in there!
How it should look in the Micro SD Card: dload -> update.app
5.Place the SD Card in the phone
6. Start the phone!
7. Okay logo is there showing up wait about 1 - 2 minutes and phone will be automatically starting to update from SD Card. When it is done it will restart the phone. Make sure at the moment when it does and screen goes black, hold down VOL UP!
8. Format data and cache!!! If you skip this part there will be a bootloop!
9. Voila. You got your device unbricked and aliveeeeeeee :highfive::highfive::highfive:
That was the easy part! If u`re unlucky enough for Guide 2 well my friend get some coffee and play some calming music list!
GUIDE 2 (When no one can help you but you :silly
First of all you should know that every case is different from one another but everything comes to one mission. Access to fastboot or access to custom recovery in order to unbrick. I will give you steps which I did when I bricked my device and I had no fastboot access, no access to stock or custom recovery, no erecovery access and no wi-fi upgrade.
So what I experienced?
You see logo but only that. Warning screen saying bootloader is unlocked. When you see warning screen u`ve got a choice what to do – Press to enter recovery, press to continue booting etc. None of that. When I was connecting the usb cable to the PC no detection at all. No working key combinations.
1. DRAIN BATTERY! REALLY. IT`S THAT SIMPLE. Leave the device on and put it in a shelf or something like that so you can`t see it and can`t touch it. 2-3-4-5 days. (I left mine for 2 weeks! :laugh The battery must be that empty that when you try to power it up only power icon shows up or nothing shows up at all.
2. When u`ve done with Step 1 get a laptop or a PC with freshly installed Windows or Linux.
3. Install SDK Platform Tools (ABD and FASTBOOT) the newest version from their website!
4. Install HiSuite from their respective website!
5. So now when you`re all done with installing the requisites get your phone in your hands plug the usb cable in the phone and then hold down (VOL -) + POWER when plugging it to the PC or laptop.
6. Believe me. It should get into fastboot. I`m 99% sure. If all the steps I wrote are done correct!
Why should battery be drained at ZERO?
I will tell you the truth – I don`t know. Really. But all I know is that it`s kind of a switch. When something goes wrong draining the battery will clear something that it shouldn’t be there.
If this tutorial helped you then click Thank you so i can count how many good things i`ve done in my life he he! If i didn`t helped you then don`t stop reading until you find the solution! Good luck!
How did you unbricked your device? Tell us here and help others do the same!

Is there a special reason why we should use a Nougat Recovery? I'm on C432B160 and have tried the change filesystem thing with METICULUS Recovery and well... it didn't work

Thank you!
Created an account just to say thanks for this! I've have spent hours and hours trying to unbrick my phone..

goretsov said:
Hello everyone! I know there are lot`s of threads and comments about unbricking your device but in order to get you on track quicker then anything else and point you to the right direction i`m writing this tutorial which i find is quite successfull.
First of all these are the questions that you must ask and answer yourself in order to do everything correct:
1. Do i have unlocked bootloader and frp? If yes, continue reading. If no, read Important note 2!
1.1. Do i have access to stock/custom recovery? If yes then continue!
1.2 Do i have problems mounting partitions with Revolution Recovery? If yes, read Important note 1!
Okey mate if all your answers are Yes then follow Guide 1!
2. If you think your device don`t have access to these then read and follow Guide 2!
! Important note 1 !
If you can`t mount partitions then the thing you must do is go to Revolution Recovery then do as i say:
Wipe -> Advanced Wipe -> Select partitions one at a time! -> Repair or change file system -> Change file system -> F2FS -> Then go back -> Select EXT4 -> And voila u`re done!
! Important note 2 !
Okay easy way to find out is if you see warning screen about unlocked bootloader then it is unlocked so it is frp. If you go to fastboot and you see Bootloader: unlocked/frp: unlocked but you don`t see the warning screen then my friend u`re not unlocked! Quickly open up the console window connect to fastboot and type:
Code:
fastboot oem unlock <your unlock code here>
Easy, a?
GUIDE 1
First of all download these files in order to continue. (Place them somewhere easy to find! )
Recovery - Revolution Recovery NOUGAT
Stock OEM info - Download
Stock ROM - L21C432B130
1. Open up fastboot then flash Revolution Recovery from the zip.
2. Start up Revolution Recovery by connecting your device to the PC and holding down (VOL +) + (VOL -) + POWER
3. Flash Stock OEM info from the zip via Revolution Recovery. Make sure when installing it the result was Successfull!!!
4. Remove usb cable from PC and Shutdown the device via Recovery and don`t plug the cable or start the phone!
4. Get your SD Card ready and plugged to the PC then Create a New Folder named "dload" in the root directory of the SD Card and paste Update.app file in there!
How it should look in the SD: SD CARD -> dload -> update.app
5.Place the SD Card in the phone
6. Start the phone!
7. Okay logo is there showing up wait about 1 - 2 minutes and phone will be automatically starting to update from SD Card. When it is done it will restart the phone. Make sure at the moment when it does and screen goes black, hold down VOL UP!
8. Wipe cache!!!
9. Format data!!!
10. Voila. You got your device unbricked and aliveeeeeeee :highfive::highfive::highfive:
That was the easy part! If u`re unlucky enough for Guide 2 well my friend get some coffee!
Guide 2 will come soon because my time is limited!
Click to expand...
Click to collapse
waiting for guide 2... :fingers-crossed:

I have installed LineageOS 14.1 on my device (VNS-L21C432) and I want stock android back, I don't have a dump backup, just a normal one.. Can I use your method to get stock? I have installed TWRP by Meticulous and bootloader unlocked. I really want to came back to stock!!
I appreciate any advice, please help!

Yes i believe so
wimsjohn said:
Is there a special reason why we should use a Nougat Recovery? I'm on C432B160 and have tried the change filesystem thing with METICULUS Recovery and well... it didn't work
Click to expand...
Click to collapse
Good question! The reason i told everyone to use there version and this custom recovery is because METICULUS is not working at least didn`t for me! It didn`t even started at first place! Nougat is preferable because a lot of people get in trouble when they upgrade to Nougat and then try to downgrade that`s one of the reasons too. So my advice is try Nougat custom recovery for your case! Good Luck and best wishes

dezzie81 said:
Created an account just to say thanks for this! I've have spent hours and hours trying to unbrick my phone..
Click to expand...
Click to collapse
You are welcome my friend! I know how tough it is to find a solution out there in this wild world!

MrSagace said:
I have installed LineageOS 14.1 on my device (VNS-L21C432) and I want stock android back, I don't have a dump backup, just a normal one.. Can I use your method to get stock? I have installed TWRP by Meticulous and bootloader unlocked. I really want to came back to stock!!
I appreciate any advice, please help!
Click to expand...
Click to collapse
Yes of course there will be no trouble at all but instead of METICULUS recovery use the one i posted here! You have access to fastboot and unlocked bootloader so just follow the steps from number 4! If this doesn`t work you can try to flash http://consumer.huawei.com/bg/support/products/downloads/detail/huawei-p9lite-bk.htm?id=93797 this rollback package and via the method with SD Card and then flash stock rom from the link above! :highfive:
Good luck and i`m waiting for the result! :highfive:

arleybarros said:
waiting for guide 2... :fingers-crossed:
Click to expand...
Click to collapse
Tomorrow i`m going to post it here so wait for update! I just have to put my ideas in some kind of order to be easy to understand! :highfive:

goretsov said:
Tomorrow i`m going to post it here so wait for update! I just have to put my ideas in some kind of order to be easy to understand! :highfive:
Click to expand...
Click to collapse
i think my micro sd was bad when i tried to update my phone and now i'm stuck in a boot loop with a data partition problem (it fails when i try to wipe data) and locked bootloader.

arleybarros said:
i think my micro sd was bad when i tried to update my phone and now i'm stuck in a boot loop with a data partition problem (it fails when i try to wipe data) and locked bootloader.
Click to expand...
Click to collapse
Okay. First of all buy a decent Micro SD Card at least 6gb of storage! This is one of the most important things i forgot to tell here. Decent means famous brand like Kingston or Philips or something like that because other then this will fail! After that do you have access to fastboot? If you have fastboot then type "fastboot oem unlock <your unlock code>" If you don`t know it i can help you with that! After that flash the recovery i posted and try to fix the partition by the way i explained above. Then follow the last steps for preparing the SD and flashing the ROM. Good Luck my friend:highfive:

goretsov said:
Okay. First of all buy a decent Micro SD Card at least 6gb of storage! This is one of the most important things i forgot to tell here. Decent means famous brand like Kingston or Philips or something like that because other then this will fail! After that do you have access to fastboot? If you have fastboot then type "fastboot oem unlock <your unlock code>" If you don`t know it i can help you with that! After that flash the recovery i posted and try to fix the partition by the way i explained above. Then follow the last steps for preparing the SD and flashing the ROM. Good Luck my friend:highfive:
Click to expand...
Click to collapse
I appreciate the help, but the phone is locked. Phone Locked and FRP lock. I already imagine that at this point I only have a nice paper weight.

arleybarros said:
I appreciate the help, but the phone is locked. Phone Locked and FRP lock. I already imagine that at this point I only have a nice paper weight.
Click to expand...
Click to collapse
No there is a way to unlock FRP. I will look and tell you more. Don`t worry :highfive:

goretsov said:
No there is a way to unlock FRP. I will look and tell you more. Don`t worry :highfive:
Click to expand...
Click to collapse
If you are talking about DC Unlocker, i tried and after the phone reboot i get that "reset failed" error...

arleybarros said:
If you are talking about DC Unlocker, i tried and after the phone reboot i get that "reset failed" error...
Click to expand...
Click to collapse
No this one is free. TODO Give it a try and tell what happened. It might detect you an virus or something like that which is normal i tried it myself a time ago. Tell later what happened

goretsov said:
No this one is free. TODO Give it a try and tell what happened. It might detect you an virus or something like that which is normal i tried it myself a time ago. Tell later what happened
Click to expand...
Click to collapse
HTML:
>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (35528 KB)...
OKAY [ 0.753s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.760s
fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (27434 KB)...
OKAY [ 0.581s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.587s

arleybarros said:
HTML:
>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (35528 KB)...
OKAY [ 0.753s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.760s
fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (27434 KB)...
OKAY [ 0.581s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.587s
Click to expand...
Click to collapse
Did you try TODO for the FRP?

goretsov said:
Did you try TODO for the FRP?
Click to expand...
Click to collapse
i think you sent the wrong link...

Check again i correct it

I´m facing the same poblem. Bootloop with Bootloader locked, FRP locked, battery empty. I can get into fastboot mode but no chance of flashing anything. USB debugging seems to be deactivated. I cant charge the battery because as soon as I connect the phone to a powersource its starts the bootloop. Force flashing via sd card (volume up and down plus power) doesn´t seem to work either (guess due to the low battery).
Any suggestions are much appreciated.
regards

Safe to reboot? axon7toolkit boot.img remote: unknown command

Hey everyone,
I am in the process of rooting my axon7 (B10) and need some quick advice
I unlocked the bootloader using this method: https://forum.xda-developers.com/axon-7/how-to/guide-unlock-bootloader-easily-t3704595
Then went on to install twrp using the axon7toolkit. steps 1 and 2 reported to be working correctly but during the twrp install this came up. (see attached)
okay so recovery flashed successfully, but something went wrong with reboot? why, how, there is no indication that the tool wrote anything to boot.img so I should be fine? Can I just boot to recovery manually and continue normally? Or should I be worried that something went wrong?
the phone is currently still in fastboot mode and responding. however I am super cautious and don't want to brick the phone because I didn't ask so I am keeping it in this state for now.
any help is much appreciated
Checking ADB\Fastboot Connectivity...
ADB device connected!
Rebooting to bootloader...
Checking Fastboot Connectivity...
Fastboot device connected!
Flashing TWRP...
target reported max download size of 536870912 bytes
sending 'recovery' (14452 KB)...
OKAY [ 0.484s]
writing 'recovery'...
OKAY [ 0.113s]
finished. total time: 0.601s
Booting TWRP...
downloading 'boot.img'...
OKAY [ 0.475s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.497s
Tap 'Keep read-only'" on startup!
Checking ADB Recovery Connectivity...
Checking ADB Recovery Connectivity...
Click to expand...
Click to collapse

fleity said:
Hey everyone,
I am in the process of rooting my axon7 (B10) and need some quick advice
I unlocked the bootloader using this method: https://forum.xda-developers.com/axon-7/how-to/guide-unlock-bootloader-easily-t3704595
Then went on to install twrp using the axon7toolkit. steps 1 and 2 reported to be working correctly but during the twrp install this came up. (see attached)
okay so recovery flashed successfully, but something went wrong with reboot? why, how, there is no indication that the tool wrote anything to boot.img so I should be fine? Can I just boot to recovery manually and continue normally? Or should I be worried that something went wrong?
the phone is currently still in fastboot mode and responding. however I am super cautious and don't want to brick the phone because I didn't ask so I am keeping it in this state for now.
any help is much appreciated
Click to expand...
Click to collapse
Why do you even use axon7toolkit? Use "fastboot flash recovery recovery.img" and you'll be able to avoid using the toolkit. It's finicky as hell.
Otherwise at least use EDL Tool...
Your boot image is untouched. Seemingly axon7toolkit does "fastboot boot recovery.img" which basically sends the recovery to RAM or something and makes the phone boot into that file instead of the actual boot.img.
If you are on Fastboot select "Recovery" from it and hit power. It will enter the recovery directly. This is important because if the phone boots, it will reinstall the stock one.
After you get into TWRP, FLASH MAGISK. This will let you retain TWRP.

Choose an username... said:
Why do you even use axon7toolkit? Use "fastboot flash recovery recovery.img" and you'll be able to avoid using the toolkit. It's finicky as hell.
Otherwise at least use EDL Tool...
Your boot image is untouched. Seemingly axon7toolkit does "fastboot boot recovery.img" which basically sends the recovery to RAM or something and makes the phone boot into that file instead of the actual boot.img.
If you are on Fastboot select "Recovery" from it and hit power. It will enter the recovery directly. This is important because if the phone boots, it will reinstall the stock one.
After you get into TWRP, FLASH MAGISK. This will let you retain TWRP.
Click to expand...
Click to collapse
yeah I don't know why it seemed like a good idea, it's a sticky post in the rom section... It's how I started and then wanted to stick to it somehow.
indeed booting into recovery works like a charm which is already pretty reassuring.
flashed magisk, twrp is not up to date (3.1.1.0), but system boots. thanks a bunch
I guess I'll update / flash the most current version of twrp via fastboot and then go on to flash lineage
again, thank you very much

fleity said:
yeah I don't know why it seemed like a good idea, it's a sticky post in the rom section... It's how I started and then wanted to stick to it somehow.
indeed booting into recovery works like a charm which is already pretty reassuring.
flashed magisk, twrp is not up to date (3.1.1.0), but system boots. thanks a bunch
I guess I'll update / flash the most current version of twrp via fastboot and then go on to flash lineage
again, thank you very much
Click to expand...
Click to collapse
Is your twrp installed as "Keep Read Only" or did you select "Swipe to Allow Modifications"?
After giving flash in the Magisk you gave wipe?
Thanks if you can respond.
Enviado de meu ZTE A2017 usando o Tapatalk

EwertonR19 said:
Is your twrp installed as "Keep Read Only" or did you select "Swipe to Allow Modifications"?
After giving flash in the Magisk you gave wipe?
Thanks if you can respond.
Enviado de meu ZTE A2017 usando o Tapatalk
Click to expand...
Click to collapse
If you're asking because you want to know:
-swipe to allow modifications is okay
-If you want to get rid of encryption, you have to FORMAT data (not wipe). You'll lose the internal storage. After that, flash magisk.
You can just flash it without formatting , but your storage will be encrypted, and you'll lose the internal storage if you ever change ROMs.

I swiped to allow modifications
I backed up everything I needed from the phone. I actually planned for removing everything to get a fresh setup.

Choose an username... said:
If you're asking because you want to know:
-swipe to allow modifications is okay
-If you want to get rid of encryption, you have to FORMAT data (not wipe). You'll lose the internal storage. After that, flash magisk.
You can just flash it without formatting , but your storage will be encrypted, and you'll lose the internal storage if you ever change ROMs.
Click to expand...
Click to collapse
So after installing twrp I format the Data partition and give flash in Magisk, correct?
I am afraid to enter bootloop because I have already done several procedures and in all the same thing happened. I hope everything will work out this time.

EwertonR19 said:
So after installing twrp I format the Data partition and give flash in Magisk, correct?
I am afraid to enter bootloop because I have already done several procedures and in all the same thing happened. I hope everything will work out this time.
Click to expand...
Click to collapse
yes

[H918] Back to Stock Everything

Saw a post in the roms section (for different variant) of a flashable to turn back to stock.
I flashed/rooted a while ago, I did a factory reset and now it boots into TWRP.
Looking to get it back to stock.
Thanks!

Reboot into twrp that's installed on recovery. Flash
this to get download mode back. Use it and LG UP in upgrade mode to flash a kdz to restore literally everything to stock.

Phoenix591 said:
Reboot into twrp that's installed on recovery. Flash
this to get download mode back. Use it and LG UP in upgrade mode to flash a kdz to restore literally everything to stock.
Click to expand...
Click to collapse
Does aboot check laf version?

Alibaba0101 said:
Does aboot check laf version?
Click to expand...
Click to collapse
Yes, but that is laf for the H918 -- so you are good.
-- Brian

Every TWRP I try to flash says:
target reported max download size of 536870912 bytes
sending 'recovery' (22616 KB)...
OKAY [ 1.505s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.528s
It already has TWRP previously flashed in some way, but I cannot get into it. I see the logo flash up from time to time.
Tried Uppercut's LG UP and it will actually connect and give me the chance to flash a KDZ, but the phone will just do a quick restart and f*k everything.
OTA updates fail and say the software isn't verified. Also get the warning screen at bootup that the device has loaded a different operating system.
Any ideas? I just want it back to stock.

runningnak3d said:
Yes, but that is laf for the H918 -- so you are good.
-- Brian
Click to expand...
Click to collapse
How do I boot into TWRP? Feels like a silly question...
"adb reboot recovery" just boots to what looks like regular recovery. However, when I try to update or flash a .KDZ through LG UP, it will restart and flash up the twrp logo and say twrp 3.2.1-3. So I know the fcker is in there somewhere. I want it gone... all of it.
HALP!! Please.

Cookster128 said:
Every TWRP I try to flash says:
target reported max download size of 536870912 bytes
sending 'recovery' (22616 KB)...
OKAY [ 1.505s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.528s
It already has TWRP previously flashed in some way, but I cannot get into it. I see the logo flash up from time to time.
Tried Uppercut's LG UP and it will actually connect and give me the chance to flash a KDZ, but the phone will just do a quick restart and f*k everything.
OTA updates fail and say the software isn't verified. Also get the warning screen at bootup that the device has loaded a different operating system.
Any ideas? I just want it back to stock.
Click to expand...
Click to collapse
OTA updates and unmodified official stock files won't flash via TWRP.
Try flashing a copy of your stock recovery, then try installing the OTA update via stock recovery.
By the way, is that Charlotte NC? I ask because I live in Rockingham.
Sent from my LGL84VL using Tapatalk

Droidriven said:
OTA updates and unmodified official stock files won't flash via TWRP.
Try flashing a copy of your stock recovery, then try installing the OTA update via stock recovery.
By the way, is that Charlotte NC? I ask because I live in Rockingham.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Eh... Charlotte is about two hours from me. I'm at the bottom of the mountain, but I've been to Rockingham a few times. Dad graduated as a RCHS Cougar in '78.
Also, if you didn't already know, I'm the same fool from the noob thread. Glad you found me here. So, when I say it has download mode, I mean when I hit volume up and plug in, it flashes up and says it, then shows the twrp logo, then boots as normal. Calling 'adb reboot download mode' just reboots. You think the bootloader needs to be re-locked?

Cookster128 said:
Eh... Charlotte is about two hours from me. I'm at the bottom of the mountain, but I've been to Rockingham a few times. Dad graduated as a RCHS Cougar in '78.
Also, if you didn't already know, I'm the same fool from the noob thread. Glad you found me here. So, when I say it has download mode, I mean when I hit volume up and plug in, it flashes up and says it, then shows the twrp logo, then boots as normal. Calling 'adb reboot download mode' just reboots. You think the bootloader needs to be re-locked?
Click to expand...
Click to collapse
Yeah, I saw you in the noob thread, I came here looking for the issue you were having.
I'm not certain about the bootloader, I own LG devices, but none of them have fastboot or download mode so I don't have experience troubleshooting flashing issues on LG devices.
Have you tried removing root and any changes you've made to system via the file manager or terminal emulator that is built into TWRP then flashing a copy of stock recovery via TWRP then reboot recovery to allow stock recovery to boot then boot to fastboot and try locking the bootloader then try flashing firmware.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Yeah, I saw you in the noob thread, I came here looking for the issue you were having.
I'm not certain about the bootloader, I own LG devices, but none of them have fastboot or download mode so I don't have experience troubleshooting flashing issues on LG devices.
Have you tried removing root and any changes you've made to system via the file manager or terminal emulator that is built into TWRP then flashing a copy of stock recovery via TWRP then reboot recovery to allow stock recovery to boot then boot to fastboot and try locking the bootloader then try flashing firmware.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I may have got it! Maybe... don't pop the champagne yet. I couldn't get into TWRP at all. It would flash up then just boot regularly. Finally I tried to enter DL mode again but this time I kept holding down the volume up button and pressed every other button like I was entering a secret code on Mortal Kombat. It actually entered TWRP!
Luckily I had already put a laf.zip and H91820f.zip on the SD card. Flashed the ROM first... did nothing except put Magisk on it... don't want. Reboot, flashed laf.zip with my secret MK code, then I had access to the real DL mode! LG UP found it and flash the real ROM. Still working on it to make sure it's all good.
---------- Post added at 07:20 PM ---------- Previous post was at 06:38 PM ----------
Yep, it's good now. Even updated itself to H91820h with no verification snags.
I shall now sell it on eBay for one billion dollars! Muahahaha!