Develop Bugs

[Recovery][Titan] TWRP 2.8.0.1 for Moto G 2014

TWRP 2.8.0.1​
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel
Click to expand...
Click to collapse
Download:
TWRP_2.8.0.1_Titan_v2.img
Instalation:
Unlock your Bootloader, click here
Go into bootloader mode (power off and hold power+vol down and release)
Connect the phone to your PC
Install Adb and Fastboot into your PC (if don't install yet) (Windows, Mac)
From CMD or Terminal go into your the download folder and execute:
fastboot flash recovery TWRP_2.8.0.1_Titan_v2.img
Click to expand...
Click to collapse
Credits:
Team Win Recovery Project
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Reserved

when i try to flash this recovery i get a "mismatch partition size." when i reboot to recovery it just boots the phone back up. did i do something wrong?

marcviado said:
when i try to flash this recovery i get a "mismatch partition size." when i reboot to recovery it just boots the phone back up. did i do something wrong?
Click to expand...
Click to collapse
connect your phone to your PC, open CMD in your adb folder and write adb reboot recovery, then press enter
It worked for me, I had the same problem

Try using this recovery by @suhas.holla TWRP v 2.8 but it has some issues while taking backup and clearing cache partition.
Thread Link : http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245/
Else use TWRP v2.7 by @suhas.holla Working perfectly fine only bug is you cant backup to internal sdcard, backup to external sd is possible.
Link : https://drive.google.com/folderview?id=0B0AbMwIJ-N7xM25CdjlQOUl2Qlk

marcviado said:
when i try to flash this recovery i get a "mismatch partition size." when i reboot to recovery it just boots the phone back up. did i do something wrong?
Click to expand...
Click to collapse
"mismatch partition size" is normal, all non official image show this message. To access you have to select recovery from bootloader and press volume up button.

sharkymyn said:
Try using this recovery by @suhas.holla TWRP v 2.8 but it has some issues while taking backup and clearing cache partition.
Thread Link : http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245/
Else use TWRP v2.7 by @suhas.holla Working perfectly fine only bug is you cant backup to internal sdcard, backup to external sd is possible.
Link : https://drive.google.com/folderview?id=0B0AbMwIJ-N7xM25CdjlQOUl2Qlk
Click to expand...
Click to collapse
My 2.8 don't have the backup bug, is fully working. The 2.7 flash fine and backup to external sdcard, but it have a problem with install that use data partition, every install that use data partition execute but don't record the data, essentially falling.

adrianom said:
My 2.8 don't have the backup bug, is fully working. The 2.7 flash fine and backup to external sdcard, but it have a problem with install that use data partition, every install that use data partition execute but don't record the data, essentially falling.
Click to expand...
Click to collapse
For me the TWRP v2.8, while taking backup of system partition the phone reboots. I am waiting for CWM recovery for our device. :fingers-crossed:

sharkymyn said:
For me the TWRP v2.8, while taking backup of system partition the phone reboots. I am waiting for CWM recovery for our device. :fingers-crossed:
Click to expand...
Click to collapse
You test my 2.8? Because this is working fine for me. The 2.8 from suhas have this problem, but this don't.
The CWM at http://forum.xda-developers.com/mot...covery-cwm-philz-touch-6-moto-g-2014-t2896586

adrianom said:
TWRP 2.8.0.1​
Download:
TWRP_2.8.0.1_Titan.img
Click to expand...
Click to collapse
Can you please share source code as well?

jheller said:
Can you please share source code as well?
Click to expand...
Click to collapse
Is a ported version, so the source is the same as official, only changed the config files in image.

adrianom said:
Is a ported version, so the source is the same as official, only changed the config files in image.
Click to expand...
Click to collapse
Ok, thanks. Still open, can you please share the config files in that case? Github would be nice , but just attaching to this post would work as well of course.

I installed this recovery ..but when i try to create a backup it gives an error saying that cannot crete a backup folder

I can take a twrp backup only in sd card... Cant take backup in internal memory.... Please help

Would you mind telling me what you changed?
I'm trying to get a tree for the phone.
Also, could someone with a stock phone boot into the stock recovery, reboot back to the os and give me the /cache/recovery/last_log file.

Please delete, I'm stupid

prateek.khurana31 said:
I installed this recovery ..but when i try to create a backup it gives an error saying that cannot crete a backup folder
Click to expand...
Click to collapse
prateek.khurana31 said:
I can take a twrp backup only in sd card... Cant take backup in internal memory.... Please help
Click to expand...
Click to collapse
You don't are using the recovery from this thread, the first version don't have sdcard support, so you probably are using the version from suhas.holla. Flash the recovery from this thread that you are be able to backup to internal memory.

Somcom3X said:
Would you mind telling me what you changed?
I'm trying to get a tree for the phone.
Also, could someone with a stock phone boot into the stock recovery, reboot back to the os and give me the /cache/recovery/last_log file.
Click to expand...
Click to collapse
I ported from Moto G v1 recovery, and I basically change the fstab and the property string, is essentially the same phone. A tree for this phone can probably be be a copy from Moto G v1 with small changes, the problem is that the kernel source don't was release yet.

New Version:
Changelog:
* Add support to external sdcard
Download:
TWRP_2.8.0.1_Titan_v2.img

adrianom said:
New Version:
Changelog:
* Add support to external sdcard
Download:
TWRP_2.8.0.1_Titan_v2.img
Click to expand...
Click to collapse
OK i will install this recovery and report !...
---------- Post added at 01:54 PM ---------- Previous post was at 01:46 PM ----------
prateek.khurana31 said:
OK i will install this recovery and report !...
Click to expand...
Click to collapse
Ok i flashed this recovery using the flash v1.2 tool and its working.... I can take backup in internal storage as well...
1 more question can someone port roms from moto g1 to moto g2?

Twrp bootloop

Hello,
i just unlocked bootloader and installed twrp and it all went fine..
until i wanted to fully wipe my device, i did this via twrp.
after 20Minuts, nothing happend, the bar was still white and gray (not even a little bit blue)
and it kept stuck on ''twrp formatting data using make_ext4fs function''.
i knew this wasn't a good idea, but i decided to turn off my phone,
and now, everytime when i turn it on on the normal way it just redirrects me to TeamWin in a bootloop.
even if i want to go to recovery mode i keep stuck in that bootloop, so there is nothing i can do right now, i only can stick at Fastboot Mode but nothing else,
Is there any way to fix this problem?
Using ASUS ZENFONE 2 551ML

I hope you did a backup of your system before? Otherwise just download the latest full image:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.174-user.zip
place it on your internal sdcard (via adb push) and then flash it normally with TWRP. Please note that the procedure can take up to 30 minutes, where the formatting is the procedure taking the longest time...

TheSSJ said:
I hope you did a backup of your system before? Otherwise just download the latest full image:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.174-user.zip
place it on your internal sdcard (via adb push) and then flash it normally with TWRP. Please note that the procedure can take up to 30 minutes, where the formatting is the procedure taking the longest time...
Click to expand...
Click to collapse
How to he flash stock rom by twrp?

Download and flash this via twrp http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526
Make sure you flash Supersu before you flash the rom.

mr_gourav2000 said:
How to he flash stock rom by twrp?
Click to expand...
Click to collapse
It's all written there...adb push on the phone, flash the zip normally via twrp, wait and done

TheSSJ said:
It's all written there...adb push on the phone, flash the zip normally via twrp, wait and done
Click to expand...
Click to collapse
but i cant use twrp on my phone because its stuck in bootloop, or what do you mean? (english not my main language)
please give me some proper step by step instructions, i would really apreciate that!
thanks anyway your awesome!

Man, I misread your post, sorry...I thought you could boot only into twrp
If you still have fastboot, why not flashing twrp 2.8.x.x?
Code:
Fastboot flash recovery nameofrecovery.img
Fastboot reboot recovery
Otherwise you could flash stock system with this guide: http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
It's a lot to read

wow, that is something really helpfull, there is still hope to revive my phone
i'll let you know how it turnt out xd
thanks alot!!

i fixed recovery mode, so thats already one step further. Oefff @TheSSJ thanks for the help.
But now i get some other problems, when i try to wipe my phone i get the error like ''unable to mount /data'' and ''unable to wipe dalvik''
and all other kinds of these errors, i get the same problem when i was installing rom. isn't there anything or a way to fully wipe all this **** so i can install a fresh rom.

i flashed custom rom and this is error log i get. its all full written down.
E: could not mount /data and unable to find crypto footer.
E: unable to mount /data
E: unable to recreate /data/media folder.
updating partition details...
E: unable to mount /data
... done
E: unable to mount storage.
E: unable to mount /data/media during GUI startup
Full SELinux support is present.
E: unable to mount /data/media/twrp. twrps when trying to read settings file.
E:unable to mount /data
MTP enabled
E: unable to mount /data
E: unable to mount /data
E: unable to mount /data
Installing external_sd/UL-Z00A-WW-2.20.40.174-user.zip ...
Checking for MD5 file...
Skipping MD5 check: no MD5 File found
Device image SKU:
OTA image SKU: WW
assert failed: getprop ("ro.build.asus.sku") == ''WW''
E: Error executing updater binary in zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Error flashing zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Updating Partition Details...
E:unable to mount /data
... done
E: unable to mount storage.
Failed

Seems you don't have a WW image installed, do you have a CN Software? Then you need another Software of course

what do you mean with ww & cn software?
sorry but im new in this.. but im really interested so can you please explain a little bit?
how can i get this other software! thanks!!!

Where did you buy your Phone? what does the packaging state? WW, CN, TW, etc? These 2 letters must be written in uppercase somewhere, then we will know which software to flash, there is a check where your phone's software is compared to the zip you are trying to flash:
assert failed: getprop ("ro.build.asus.sku") == ''WW''
Which TWRP did you flash?

ohhh yes, i do have CN software Probably, as it is buyed from china.
Where can i find this other type software?
thanks!

colldor200 said:
ohhh yes, i do have CN software Probably, as it is buyed from china.
Where can i find this other type software?
thanks!
Click to expand...
Click to collapse
There you go: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-CN-2.20.40.159-user.zip
I think flashing will still fail though...but pls try first,maybe it'll work

i tryed it, i get the same error :/

Update: i changed from CN to WW.
Because of this i reflashed to twrp 3.0 and it works properly and now wiping shows no problem anymore.
I also got the WW ota zip but dont know how to install that.
Anyway, i tryed to install xaosp rom (even if my ota is still CN)
And it showed no problems at all!
BUT when i tryed to startup my phone it sticks with the asus logo and wont go any further, not a bootloop, it just sticks at the asus logo.
We are Always getting more and more steps further into fixing my phone, thanks for that @TheSSJ were almost there ?

colldor200 said:
Update: i changed from CN to WW.
Because of this i reflashed to twrp 3.0 and it works properly and now wiping shows no problem anymore.
I also got the WW ota zip but dont know how to install that.
Anyway, i tryed to install xaosp rom (even if my ota is still CN)
And it showed no problems at all!
BUT when i tryed to startup my phone it sticks with the asus logo and wont go any further, not a bootloop, it just sticks at the asus logo.
We are Always getting more and more steps further into fixing my phone, thanks for that @TheSSJ were almost there
Click to expand...
Click to collapse
You could try flashing cm13 first and then xosp:
First wipe data/cache
Then flash cm13
Boot up and hope that it works
Reboot to recovery
Wipe data/cache
Flash xosp and maybe a kernel that fits (FlareM?)
Boot to system again

You could try flashing cm13 first and then xosp:
First wipe data/cache
Then flash cm13
Boot up and hope that it works
Reboot to recovery
Wipe data/cache
Flash xosp and maybe a kernel that fits (FlareM?)
Boot to system again
Click to expand...
Click to collapse
sorry for the kinda late answer, but yes i followed your instructions, and it works completely, after cm13 i also immediately installed gapps.
i skipped xaosp im fine with cm13
Thanks alot @TheSSJ for all the help my phone is fully fixed now and even working faster then before its like super fast.
thanks again your great!

Blu Advance 4.0 L2 (A030U) - Custom Recovery TWRP and root

Hi all,
First of all be carefull, Nobody will be responsible for bricking your device but yourself.
I compiled twrp 3.0 for blu advance 4.0 l2 (A030U) https://drive.google.com/open?id=0Bw48RaTkRMm_eTRXVk84aWJTUjA here the sources https://github.com/contrerasojuanc/device_blu_advance_l2_A030U, thanks to @Dees_Troy and its guide on https://forum.xda-developers.com/showthread.php?t=1943625. So, in order to install it on this device, we will need to unlock bootloader (Factory reset needed), and flash TWRP recovery on recovery partition.
Settings -> About device -> Compilation number click multiple times to get new developer options menu.
Enable Unlock OEM.
On terminal:
Code:
adb reboot bootloader
On terminal:
Code:
fastboot oem unlock
On terminal:
Code:
fastboot flash recovery twrp_a030u.img
On terminal:
Code:
fastboot reboot
(Immediately press and hold Volumen + on device until custome recovery shows up.)
In order to achieve root on this device, we need to install from TWRP a Supersu system-mode, available thanks to @mauam, it can be get at https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120 (I used SR3-SuperSU-v2.79-SYSTEMMODE.zip).
Note that maybe /system need to be mounted as writeable, so first mount System and then, on TRWP's terminal:
Code:
/system/bin/mount -o remount,rw /system
Hope, it can be useful somehow. Any questions, please let me know.

I did everything right but I can not get root

Could you give more detail on how you installed supersu in system mode? I used the command mount -o remount,rw /system (replacing /system with the actual system folder path I found using the mount command in twrp temrinal) BUT discovered system remained read-only and everywhere I searched says you need to have root access to mount it as re-writeable.
I installed the zip you used anyways but am now stuck at the BLU logo screen. What should I do now?

talesgs said:
I did everything right but I can not get root
Click to expand...
Click to collapse
Please give me more details of what was done, in order to try to help

4mand said:
Could you give more detail on how you installed supersu in system mode? I used the command mount -o remount,rw /system (replacing /system with the actual system folder path I found using the mount command in twrp temrinal) BUT discovered system remained read-only and everywhere I searched says you need to have root access to mount it as re-writeable.
I installed the zip you used anyways but am now stuck at the BLU logo screen. What should I do now?
Click to expand...
Click to collapse
The command I used for get writable /system was
Code:
/system/bin/mount -o remount,rw /system
exactly that one, remember that if you are in TWRP you have root access in recovery partition, so /system can be set as writeable from there. Probably you need to flash recovery and system partition again. I have those partitions from my stock device, let me know if want to give it a try.

Did you type any commands before that? I get the error "sh: /system/bin/mount: not found".
It would be great if you could link the stock partitions.

4mand said:
Did you type any commands before that? I get the error "sh: /system/bin/mount: not found".
It would be great if you could link the stock partitions.
Click to expand...
Click to collapse
No command before, this is what I did:
1. In TWRP tap Mount menu, then check "Mount system partition read-only" then check "System", then middle bottom button (Home). (So now we have /system partition mount but as RO)
2. Tap Advance menu, Terminal and type
Code:
/system/bin/mount -o remount,rw /system
3. Now if all goes alright, we should have /system writeable.
4. With /system writeable, tap on Install menu, select the Supersu file (Only this worked for me SR3-SuperSU-v2.79-SYSTEMMODE.zip).
5. Deviced rooted.
Ok, I'll try to upload the partitions tonight, while you could search the rom in web.

contrerasojuanc said:
No command before, this is what I did:
1. In TWRP tap Mount menu, then check "Mount system partition read-only" then check "System", then middle bottom button (Home). (So now we have /system partition mount but as RO)
2. Tap Advance menu, Terminal and type
Code:
/system/bin/mount -o remount,rw /system
3. Now if all goes alright, we should have /system writeable.
4. With /system writeable, tap on Install menu, select the Supersu file (Only this worked for me SR3-SuperSU-v2.79-SYSTEMMODE.zip).
5. Deviced rooted.
Ok, I'll try to upload the partitions tonight, while you could search the rom in web.
Click to expand...
Click to collapse
Yes, what you describe is exactly what I did on a previously stock device, but with the same issue on terminal I posted before. After ignoring that, and sideloading the supersu .zip you used, the device gets stuck on the second BLU logo screen on boot, no hope getting back to system. Hopefully it works the second time around with stock partitions...

4mand said:
Yes, what you describe is exactly what I did on a previously stock device, but with the same issue on terminal I posted before. After ignoring that, and sideloading the supersu .zip you used, the device gets stuck on the second BLU logo screen on boot, no hope getting back to system. Hopefully it works the second time around with stock partitions...
Click to expand...
Click to collapse
Also here
;-;

Blu Advance 4.0 L2 (A030U) rom partitions
Blu Advance 4.0 L2 (A030U) stock rom partitions
HTML:
https://ufile.io/j6925
Inside there is a scatter file to use with flashtools

contrerasojuanc said:
Blu Advance 4.0 L2 (A030U) rom partitions
HTML:
https://ufile.io/j6925
Inside there is a scatter file to use with flashtools
Click to expand...
Click to collapse
rooted? or stock?

talesgs said:
rooted? or stock?
Click to expand...
Click to collapse
Stock

I have a Blu Advance 4.0 L2 (A030L) device, I know it is different, but I dared, now I have a bricking device with this twrp 3.0. Anybody knows somethings about reverse it or if it is possible??

I already gave up doing root does not work

doni.zeti said:
I have a Blu Advance 4.0 L2 (A030L) device, I know it is different, but I dared, now I have a bricking device with this twrp 3.0. Anybody knows somethings about reverse it or if it is possible??
Click to expand...
Click to collapse
Hi, the only way I know would be to flash stock partitions of that device. If you manage to find them in the web, I could tell you how to flash it.

contrerasojuanc said:
Hi, the only way I know would be to flash stock partitions of that device. If you manage to find them in the web, I could tell you how to flash it.
Click to expand...
Click to collapse
thank you for your attention, I'm already trying your recommend, but no success yet. I have the stock, sp-flash and drivers (for win). I think it is any problem with drivers or sp-flash (v5.1712)...

Not working
Hi, I have a BLU Advance 4.0 L2 (A030U) and the TWRP doesn't work in my phone, it boots but the touchscreen isn't working, any suggestion?
UPDATE: I was booting twrp from fastboot because I wasn't able to flash it like is explained here, I think that is why my touchscreen wasn't working, anyways I managed to flash it through SP Flash Tools and It worked but now the root doesn't work, it softbrick the phone everytime I try, I'm able to mount system and all that stuff, everything is successfull but the phone does not boot.

Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.

i have a030u v12 rom. v5generic not work, after install result crash bootlogo loop same make option format... recovery not work! same press up button! after all process not enter in twrp. i test magisk not work customize boot.img flash to sp flash result crash boot! mtk droid not detect my phone too please help me.... very hard root this device!
TianNian said:
Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.
Click to expand...
Click to collapse
[/COLOR]
TianNian said:
Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.
Click to expand...
Click to collapse
---------- Post added at 07:13 AM ---------- Previous post was at 07:13 AM ----------
[/COLOR]
TianNian said:
Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.
Click to expand...
Click to collapse

Hi, in order to know what can be happening, first let's try to flash recovery partition, for that, please follow these steps:
Settings -> About device -> Compilation number click multiple times to get new developer options menu.
Enable Unlock OEM.
On terminal:
Code:
adb reboot bootloader
On terminal:
Code:
fastboot oem unlock
On terminal:
Code:
fastboot flash recovery twrp_a030u.img
On terminal: After write the next command, press enter on your computer and immediately press and hold Volumen + on device until custom recovery shows up.
Code:
fastboot reboot

Nexus 7 2013 ERROR: 7

Hi, I'm new here. I did some searching and couldn't find any answers regarding my problem exactly. I'm using TWRP to update my Nexus 7 2013 (flo). I have been successful in the past - as recently as yesterday. Something happened along the way and now I only get an error when attempting to flash ROMs.
I have been trying Lineage 16 and 17.1. I did do the repartition, but I get the same error on both ROMs:
Installing zip file '/sdcard/Download/lineage-17.1-20200803-UNOFFICIAL-flo.zip'
Checking fir Digest file...
Warning: No file_contexts
Target: google/razor/flo:6.0.1/MOB30X/3036618:user/release-keys
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Error installing zip file /sdcard/Download/lineage-17.1-20200803-UNOFFICIAL-flo.zip'
Updating partition details...
...done
I have tried to edit the text to eliminate the "asserts" - no help. I downgraded TWRP one version, no help. What else can I do. I'm pretty much a noob when it comes to this, and I'm willing to "hold hands" to get a solution if there is one. Thanks!

ericdudeus said:
....I have tried to edit the text to eliminate the "asserts" - no help. I downgraded TWRP one version, no help. What else can I do. I'm pretty much a noob when it comes to this, and I'm willing to "hold hands" to get a solution if there is one. Thanks!
Click to expand...
Click to collapse
In TWRP go Advanced Wipe and wipe system/data/cache/dalvik before installing the ROM.
If it still does not work and you wish to investigate it, please 'install' this zip in twrp, find 'logs.tgz' in the root of internal storage and post it here.
If you just want this ROM installed ASAP then do:
RESTOCK (select repartition to original factory layout)
CROSS
:fingers-crossed:

Thank you! I actually started over - completely wiped the tablet, repartitioned it, flashed the ROM, and Gapps, and it's fully functioning again. It just didn't like something in the process before, I guess.
k23m said:
In TWRP go Advanced Wipe and wipe system/data/cache/dalvik before installing the ROM.
If it still does not work and you wish to investigate it, please 'install' this zip in twrp, find 'logs.tgz' in the root of internal storage and post it here.
If you just want this ROM installed ASAP then do:
RESTOCK (select repartition to original factory layout)
CROSS
:fingers-crossed:
Click to expand...
Click to collapse

Hi,
i have too this problem.
I wipe everything, flashed the repartitioning zip and still havoc 3.3 cannot be flashed. What i have to do? thanks

The solution for me was to just completely wipe the storage - everything, and start over. Once wiped, I repartitioned, flashed the ROM (I used Resurrection Remix), and then GApps. The tablet seems to be fully functional at this point, but it's showing its age.
Good luck!

ericdudeus said:
The solution for me was to just completely wipe the storage - everything, and start over. Once wiped, I repartitioned, flashed the ROM (I used Resurrection Remix), and then GApps. The tablet seems to be fully functional at this point, but it's showing its age.
Good luck!
Click to expand...
Click to collapse
It's tell me E: eroor creating fstab

k23m said:
In TWRP go Advanced Wipe and wipe system/data/cache/dalvik before installing the ROM.
If it still does not work and you wish to investigate it, please 'install' this zip in twrp, find 'logs.tgz' in the root of internal storage and post it here.
If you just want this ROM installed ASAP then do:
RESTOCK (select repartition to original factory layout)
CROSS
:fingers-crossed:
Click to expand...
Click to collapse
I ran the logging zip. My log.tgz is here: https://abar.duckdns.org/s/aywJagDNJDxfiyL

thrilway said:
I ran the logging zip. My log.tgz is here: https://abar.duckdns.org/s/aywJagDNJDxfiyL
Click to expand...
Click to collapse
OK, the relevant error is...
Code:
erasing 18342 blocks
BLKDISCARD ioctl failed: Invalid argument
failed to execute command [erase 4,223772,228864,229950,243200]
new data receiver is still available after executing all commands.
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7
It seems your eMMC hardware version is <4.4
But RESTOCK should work.

Thanks, but I'm running a linux desktop, so I can't really run RESTOCK. Is there a guide somewhere to run the commands in RESTOCK manually?

EDIT
I've reviewed your logs. For the custom ROM to work you need repartition. Install sysrepart-max.zip then reboot and now install the ROM. If gapps are needed, use pico.

It worked! Thanks

k23m said:
In TWRP go Advanced Wipe and wipe system/data/cache/dalvik before installing the ROM.
If it still does not work and you wish to investigate it, please 'install' this zip in twrp, find 'logs.tgz' in the root of internal storage and post it here.
If you just want this ROM installed ASAP then do:
RESTOCK (select repartition to original factory layout)
CROSS
:fingers-crossed:
Click to expand...
Click to collapse
Thank you so much! It worked perfectly. In the beginning it didn't work, I just reboot the device after wiping system/data/cache/dalvik, then tried again to install the ROM, Now my device has the new ROM working without problem.

Getting error 70 in twrp when installing Opengapps (pico) even BitGapps

Hi, I have the Error 7 Problem with my Nexus 10 Using newest TWRP Recovery and trying to install Lineage 17.1 unoffical. Generated the logs.tgz file - which you will find encllosed. Hope anyone could help.
Thanks a lot in advance!

BlackVoltage said:
Hi, I have the Error 7 Problem with my Nexus 10 Using newest TWRP Recovery and trying to install Lineage 17.1 unoffical. Generated the logs.tgz file - which you will find encllosed. Hope anyone could help.
Thanks a lot in advance!
Click to expand...
Click to collapse
This is a Nexus 7 forum, not Error 7 forum, lol.
The error indicates a too small 'system' partition and you need to enlarge it. You will find a solution on Nexus 10 'manta' forum.

Ok thanks - I did not see that at first. My fault. Do you know a special Error 7 Nexus 10 Forum? Or am I just right here?
[ROM][LineageOS][17.1][UNOFFICIAL][Nexus10]
LineageOS lineage-17.1-20230404-UNOFFICIAL-manta.zip Known issues: - Pls disable "Adaptive brightness" in display settings -> sensor service problems. - GPS is not working and has been disabled completely - NFC is not working and has been...
forum.xda-developers.com

Question Bricked. Stuck in TWRP (wrong Wipe)

Hello guys.
I have encountered very big problem and I need your guys help. I wipe something wrong (the problem is I forgot what I wipe, I do have some experiences with Orangefox but no to TWRP) in the TWRP and now it says
Failed to mount ´/system_ext` (Invalid argument)
Failed to mount `/product` (Invalid argument)
I tried to copy file from the computer to do recovery, not possible.
I tried to do ADB Sideload, not detected.
I tried to do Fastboot, also not detected.
Right now when I tried to go to reboot to system, it goes back to the TWRP again and again.
Maybe anyone encountered this? Or has already a solution? Can you please assist me?
Any answers or helps will be very appreciated from me. Thanks.

Renatoskie said:
Hello guys.
I have encountered very big problem and I need your guys help. I wipe something wrong (the problem is I forgot what I wipe, I do have some experiences with Orangefox but no to TWRP) in the TWRP and now it says
Failed to mount ´/system_ext` (Invalid argument)
Failed to mount `/product` (Invalid argument)
I tried to copy file from the computer to do recovery, not possible.
I tried to do ADB Sideload, not detected.
I tried to do Fastboot, also not detected.
Right now when I tried to go to reboot to system, it goes back to the TWRP again and again.
Maybe anyone encountered this? Or has already a solution? Can you please assist me?
Any answers or helps will be very appreciated from me. Thanks.
Click to expand...
Click to collapse
Are you using TWRP by Vasishoth? Those "Failed to mount" errors are related to his TWRP, no user error. Nebrassy's TWRP doesn't have those errors.
Are you using a Custom ROM or Stock ROM?
You may have accidentally wiped "/metadata". That partitions is crucial and contains the encryption key for /data, and without the encryption key /data cannot be accessed, and therefore the system can't boot.
If that's the case, you might have bad luck and need to format data, in order to boot the system again.

dreamytom said:
Are you using TWRP by Vasishoth? Those "Failed to mount" errors are related to his TWRP, no user error. Nebrassy's TWRP doesn't have those errors.
Are you using a Custom ROM or Stock ROM?
You may have accidentally wiped "/metadata". That partitions is crucial and contains the encryption key for /data, and without the encryption key /data cannot be accessed, and therefore the system can't boot.
If that's the case, you might have bad luck and need to format data, in order to boot the system again.
Click to expand...
Click to collapse
Oh I see. I think it his, it was twrp-aliothin, the unofficial one. I using a stock ROM and decided to move to Pixel Experience through TWRP and I stuck there. Where to format the data? Is it in the TWRP? And what do I do after that, sir?

Renatoskie said:
Oh I see. I think it his, it was twrp-aliothin, the unofficial one. I using a stock ROM and decided to move to Pixel Experience through TWRP and I stuck there. Where to format the data? Is it in the TWRP? And what do I do after that, sir?
Click to expand...
Click to collapse
Yup that's Asishoth's TWRP. Both Nebrassy's and Asishoth's are unofficial tho. No official TWRP yet available for Poco F3.
Did Pixel Experience boot properly once, tho? Or has it never booted?
Yup I meant Format Data inside TWRP. It's in "Wipe". That may fix your problem, but I'm not sure...

Renatoskie said:
Hello guys.
I have encountered very big problem and I need your guys help. I wipe something wrong (the problem is I forgot what I wipe, I do have some experiences with Orangefox but no to TWRP) in the TWRP and now it says
Failed to mount ´/system_ext` (Invalid argument)
Failed to mount `/product` (Invalid argument)
I tried to copy file from the computer to do recovery, not possible.
I tried to do ADB Sideload, not detected.
I tried to do Fastboot, also not detected.
Right now when I tried to go to reboot to system, it goes back to the TWRP again and again.
Maybe anyone encountered this? Or has already a solution? Can you please assist me?
Any answers or helps will be very appreciated from me. Thanks.
Click to expand...
Click to collapse
Can you start it in fastboot?
Does your pc recognize it in fastboot?
If the answer is yes, try switching back to the stock you previously had using miflash.
Remember to select "clean all" instead of "clean all and block" otherwise the brick is insured...
You can also read this guide which contains a lot of information that may be useful to you.
How to flash ROM and TWRP on POCO F3 / k40 / mi11x. And an explanation. A very important guide
Mandatory instructions for beginners (and not only beginners) to install ROM and other on poco f3 Prerequisite, unlocking the bootloader For questions, if something is not clear, please write to "Conversations", I will try to correct it in a post...
forum.xda-developers.com

dreamytom said:
Yup that's Asishoth's TWRP. Both Nebrassy's and Asishoth's are unofficial tho. No official TWRP yet available for Poco F3.
Did Pixel Experience boot properly once, tho? Or has it never booted?
Yup I meant Format Data inside TWRP. It's in "Wipe". That may fix your problem, but I'm not sure...
Click to expand...
Click to collapse
I tried this and still not working honestly. It's still in the process of loading the Pixel Experience ROM. My bad actually, Pixel Experience ROM also provides a Recovery but it seem sketchy so I decided to use the TWRP one.

RollDload said:
Can you start it in fastboot?
Does your pc recognize it in fastboot?
If the answer is yes, try switching back to the stock you previously had using miflash.
Remember to select "clean all" instead of "clean all and block" otherwise the brick is insured...
You can also read this guide which contains a lot of information that may be useful to you.
How to flash ROM and TWRP on POCO F3 / k40 / mi11x. And an explanation. A very important guide
Mandatory instructions for beginners (and not only beginners) to install ROM and other on poco f3 Prerequisite, unlocking the bootloader For questions, if something is not clear, please write to "Conversations", I will try to correct it in a post...
forum.xda-developers.com
Click to expand...
Click to collapse
Oh yes thank you. Finally it worked. At first I didn't find the menu for Bootloader Fastboot, instead the Fastboot that the TWRP provided, which makes the device undetected with Mi Flash, CMD Fastboot Devices, Xiaomi Szaki Tools, but after I found the right menu which lead me ro Bootloader Fastboot, it can detect my device again, so I properly did what you told and voila, all worked again. Many thanks, Sir!

Renatoskie said:
Oh yes thank you. Finally it worked. At first I didn't find the menu for Bootloader Fastboot, instead the Fastboot that the TWRP provided, which makes the device undetected with Mi Flash, CMD Fastboot Devices, Xiaomi Szaki Tools, but after I found the right menu which lead me ro Bootloader Fastboot, it can detect my device again, so I properly did what you told and voila, all worked again. Many thanks, Sir!
Click to expand...
Click to collapse
I'm glad it worked.
however, if you want to enter fastboot mode easily do this:
1) turn off the phone;
2) hold down the "volume - and power" keys until the word fastboot appears.