Root [TWRP] [MS323, D320n, D325] Team Win Recovery Pro 3.0

[spenzozozo123]

It doesn't help, the screen is still purple bro.

 

[Paul pinckston]

I don't know then mate, I had the same issue; dbi error fatal, etc. Correct aboot.bin fixed it for me. Maybe check you downloaded the correct file and it wasn't corrupted, and try to reflash. Otherwise hopefully someone else may have an idea.

 

[spenzozozo123]

I don't know then mate, I had the same issue; dbi error fatal, etc. Correct aboot.bin fixed it for me. Maybe check you downloaded the correct file and it wasn't corrupted, and try to reflash. Otherwise hopefully someone else may have an idea.

Do you want to tell me step by step what to do right now, please?

 

[Paul pinckston]

Also make sure you renamed the file to aboot.bin and check for any mistakes when entering the dd command; a space where there shouldn't be one, or any capital letters where they should be lower case, etc.

 

[spenzozozo123]

Also make sure you renamed the file to aboot.bin and check for any mistakes when entering the dd command; a space where there shouldn't be one, or any capital letters where they should be lower case, etc.

I copied what you wrote on the thread, bro.

 

[Paul pinckston]

Did you manage to download the aboot dump? I just tried on my phone but no file was listed on media fire,just an empty folder. If you have got the zip file you need to follow the instructions on the page I linked you to, basically unzip the aboot dump, identify the file that corresponds to your handset, and rename that file to aboot.bin. Then flash using the dd if command detailed in the post. The aboot file should be copied to your internal sdcard before flashing, otherwise the command won't work.

 

[spenzozozo123]

Did you manage to download the aboot dump? I just tried on my phone but no file was listed on media fire,just an empty folder. If you have got the zip file you need to follow the instructions on the page I linked you to, basically unzip the aboot dump, identify the file that corresponds to your handset, and rename that file to aboot.bin. Then flash using the dd if command detailed in the post. The aboot file should be copied to your internal sdcard before flashing, otherwise the command won't work.

I have downloaded the D320 .bin aboot file, yes.

EDIT: I did adb reboot recovery, and it's purple again...??
EDIT2: I found out I need D320F8, and I did it again, but it's still purple bro.

 

[Paul pinckston]

Did you delete the d320n aboot from the internal sd? You may have inadvertently flashed the same file again. Otherwise all I can say is to keep trying, it took me a couple of days off and on to fully root, unlock bootloader and flash recovery! Just read as much as you can first and try to understand exactly what is needed for your specific handset. I've a D320n so there may be subtle differences.

 

[spenzozozo123]

Did you delete the d320n aboot from the internal sd? You may have inadvertently flashed the same file again. Otherwise all I can say is to keep trying, it took me a couple of days off and on to fully root, unlock bootloader and flash recovery! Just read as much as you can first and try to understand exactly what is needed for your specific handset. I've a D320n so there may be subtle differences.

When I try to enter the recovery mode manually, it doesn't work. It just boots up and the cellphone turns off. Maybe my TWRP doesn't support L70 or something? I don't get this shit.

EDIT:
This is what I have when I do 'adb reboot recovery'

EDIT2: I found a good aboot and I got it fixed!!

 

[Paul pinckston]

Sorry, went to bed last night. Glad you got it sorted mate.

 

[spenzozozo123]

Sorry, went to bed last night. Glad you got it sorted mate.

Now my home button doesn't work.
http://forum.xda-developers.com/general/xda-assist/twrp-recovery-problem-t3275226#post64417950

 

[Paul pinckston]

Have you flashed cm13? There's a bug with the latest nightly I think, try the previous versions. I'm still on 5.1 tesla rom, waiting for the bugs to be ironed out of cm13.

 

[spenzozozo123]

Have you flashed cm13? There's a bug with the latest nightly I think, try the previous versions. I'm still on 5.1 tesla rom, waiting for the bugs to be ironed out of cm13.

What do you mean, flashed cm13? I have placed it on my sdcard and installed it through twrp.

 

[Paul pinckston]

That's the meaning of "flashed", if you read the cm13 thread you will find these bugs before you install.

 

[spenzozozo123]

That's the meaning of "flashed", if you read the cm13 thread you will find these bugs before you install.

What bugs man? My home button doesn't work. CM13 somehow disabled my home button.

 

[Paul pinckston]

Almost all custom roms have bugs of some sort, this home button issue is a bug that has been reported numerous times on the relevant thread. It will most likely be fixed in the next nightly release. You need to read the WHOLE THREAD before you install a rom, otherwise you run the risk of encountering issues such as this. I knew you had installed cm13 simply because of the home button issue you reported, because I have read and kept up with the thread.

 

[Markaos]

Hello,
I can't get into recovery using key combo anymore (I know it worked in the past, as I rooted my phone by flashing modified kernel using the stock recovery). It still works with adb reboot recovery and Rebooter, but I want to be able to restore my backups if the OS will not start.
Question: What key combo do you use to get to recovery? (LG D320n)
Alternative: Is there any way to reboot to recovery from fastboot?

 

[Miguel__]

i cant install this recovery. can someone help me please?

this is the 2nd time i get pink screen.

im on stock D32510d_00.kdz. copy the twrp.img to the sdcard. input this commands on cmd :
adb shell
su
dd if=/storage/external_SD/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

then i reboot the phone and i get the signature problem.
but i have firmware upgrade with key combo so i dont have a brick atm.
now i have restored the phone to 10d stock version, no issues with drivers and that kind of things.

im using windows 7 64 bits. and my phone is lg l70 d325 dual sim. (i have a full backup of this rom)
im also flashing the aboot.bin from sammyz (that one worked for me when i installed cm12 but now its not working)

EDIT AND FIXED!
first push the aboot.bin (douglas's aboot worked for me)
then replace the recovery.
then magic.

 

[vm03]

On http://vasy.ru/TWRP/ new TWRP with adopted storage support.

 

[crutchcorn]

On http://vasy.ru/TWRP/ new TWRP with adopted storage support.

Added to OP

 

[vladimirs77]

Flash in recovery zip

 

[crutchcorn]

On http://vasy.ru/TWRP/ new TWRP with adopted storage support.

Just checking, I have adapted storage enabled. If I flash the newest TWRP, can I flash the latest CM nightly without running into issues? I mean, I don't see why I would run into issues, but I am just checking just in case

 

[crutchcorn]

@vm03, the newest build of TWRP does not load on my device (MS323). It only loads a black screen

 

[vm03]

@vm03, the newest build of TWRP does not load on my device (MS323). It only loads a black screen

Some else have problem, but in my test on my devices work good include OTA from adopted SD. Try reformat SD... Or wait news from twrp team... Adopted storage support in progress.

 

[crutchcorn]

Some else have problem, but in my test on my devices work good include OTA from adopted SD. Try reformat SD... Or wait news from twrp team... Adopted storage support in progress.

I will wait. Thanks for the info!