• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Purple screen after installing roms in D320, using TWRP, any way to avoid going back to stock?

cadash

cadash

Newbie
Hi guys, I followed the guides on the forums to install a new rom into my phone, I installed TWRP and then installed the ROMs but after the phone boot it says boot certificate error and takes me to the purple screen unless I get into fastboot and thenk into TWRP, however, it doesnt matter which version of Android 5.1 The one I used first is Cyanogenmod 12.1, not sure if that makes a difference or not, I am always getting the same error. I have no idea what is causing the problem to start looking into it. Anyone can give me some info? Is there any way to avoid going back to stock?
I always wipe the data first, then install the rom and gap, wipe data and remove so that looks ok.
The error looks like some of problem with the bootloader, can someone confirm?
 
I've seen some posts where you have to get into the adb shell and use the dd command but when I try it, it tells me my device is offline. I can only boot into TWRP with the device in fastmode or get the purple screen. If someone has the link, please let me know, in the meantime I will keep digging
 
Thanks man, I already had made it to your thread for the aboot.img. I also downloaded PhilZ, and installed it using

fastboot flash recovery recovery.img

But after

fastboot reboot

It will take me to the purple screen, so instead I use this:

fastboot boot recovery.img

with TWRP I used to do the same thing, "fastboot boot twrp.imp" then from the same command line I issue: adb devices
I get to see the PhilZ app but no luck in getting ADB to see anything
 
Booted in Linux, saw all the partitions, tried copying aboot.bin to the sdc6 partition that was where aboot was and nothing, tried with aboot.img
One thing I notice is that the only way I can get into fastboot is if I press the volume up and connect the cable afterwards, same combination but with power instead will not work
 
Last edited:
cadash said:
Booted in Linux, saw all the partitions, tried copying aboot.bin to the sdc6 partition that was where aboot was and nothing, tried with aboot.img
One thing I notice is that the only way I can get into fastboot is if I press the volume up and connect the cable afterwards, same combination but with power instead will not work
Click to expand...
get into fastboot and flash philz, you can use adb there to flash aboot. then restore to twrp to flash your rom.
 
First of all, thanks for all the help. ok I am with you till the part I flash PhilZ: "fastboot flash recovery philz.img "
Here is the output:


C:\Users\Alexis\Downloads\LG L70\bootloader\bootloader_unlock_part1>fastboot fla
sh recovery recovery.img
target reported max download size of 301989888 bytes
sending 'recovery' (22528 KB)...
OKAY [ 0.763s]
writing 'recovery'...
OKAY [ 2.696s]
finished. total time: 3.460s
C:\Users\Alexis\Downloads\LG L70\bootloader\bootloader_unlock_part1>

C:\Users\Alexis\Downloads\LG L70\bootloader\bootloader_unlock_part1>fastboot reboot
rebooting...

finished. total time: 0.002s

But I never get into Philz or anything, unless I use the fastboot boot command and reference an IMG file.

This is what I get when I run ADB:

C:\Users\Alexis\Downloads\LG L70\bootloader\bootloader_unlock_part1>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached

C:\Users\Alexis\Downloads\LG L70\bootloader\bootloader_unlock_part1>adb shell
error: device not found

Sorry to be such a pest, I feel stupid and with a bricked phone. Maybe I am getting it all wrong....

I was following your videos and want trhough the first 4 without problems or errors, I think I also came up with the boot error while trying to reboot into recovery with rebooter while I still had the stock rom
 
Last edited:
cadash said:
First of all, thanks for all the help. ok I am with you till the part I flash PhilZ: "fastboot flash recovery philz.img "
Here is the output:


C:\Users\Alexis\Downloads\LG L70\bootloader\bootloader_unlock_part1>fastboot fla
sh recovery recovery.img
target reported max download size of 301989888 bytes
sending 'recovery' (22528 KB)...
OKAY [ 0.763s]
writing 'recovery'...
OKAY [ 2.696s]
finished. total time: 3.460s
C:\Users\Alexis\Downloads\LG L70\bootloader\bootloader_unlock_part1>

C:\Users\Alexis\Downloads\LG L70\bootloader\bootloader_unlock_part1>fastboot reboot
rebooting...

finished. total time: 0.002s

But I never get into Philz or anything, unless I use the fastboot boot command and reference an IMG file.

This is what I get when I run ADB:

C:\Users\Alexis\Downloads\LG L70\bootloader\bootloader_unlock_part1>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached

C:\Users\Alexis\Downloads\LG L70\bootloader\bootloader_unlock_part1>adb shell
error: device not found

Sorry to be such a pest, I feel stupid and with a bricked phone. Maybe I am getting it all wrong....

I was following your videos and want trhough the first 4 without problems or errors, I think I also came up with the boot error while trying to reboot into recovery with rebooter while I still had the stock rom
Click to expand...
do it via fastboot boot recovery.img, that'll boot into recovery. I think in PhilZ theres an option to mount the device, under Mount.
 
I think I am making some kind of progress, one of the drivers wasn't being installed when I boot into PhilZ, I manually chose the LGE Mobile ADB device and it worked, ADB now recognizes and sees the device online.
I had to change the command slightly, where it said sdcard I used external_sd as this was where the aboot.bin file is located.
/external_sd # dd if=/external_sd/aboot.bin of=/dev/block/platform/msm_sdcc.1/by
-name/aboot
dd if=/external_sd/aboot.bin of=/dev/block/platform/msm_sdcc.1/by
-name/aboot
4096+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.928957 seconds, 2.2MB/s
But still I am getting the purple screen. I wonder if I should try with each and every aboot.bin for the 320s available.
 
First of all, thank you all!!! I tried with all the versions of aboot as I wasnt sure which model to use, no luck, looked at the back of the phone and it said 320F8, I gave a try to the second version of the file you had in your dump LitrosNub and it worked!!!!! thank you a lot!!!!

I even started looking at prices for a new phone... thanks guys

One more question, this aboot.bin thing, If I put another rom in the phone, would I have to do the same?
 
cadash said:
First of all, thank you all!!! I tried with all the versions of aboot as I wasnt sure which model to use, no luck, looked at the back of the phone and it said 320F8, I gave a try to the second version of the file you had in your dump LitrosNub and it worked!!!!! thank you a lot!!!!

I even started looking at prices for a new phone... thanks guys

One more question, this aboot.bin thing, If I put another rom in the phone, would I have to do the same?
Click to expand...
Nope!
 
By the way, in case someone else is having problems here are a few pointers.
After you boot into Philz, go to mount, mount USB storage first and you will see your SD card contents, after you copy the aboot.bin to the root mount, exit USB mount, mount sim card and system, I also mounted data and cache just in case.
If you don't mount system you wont be able to use the SU or any other command and if you don't mount the sim you won't be able to copy the abin to the device internal's memory.

The IF part in dd stands for input file if you are not used to linux or dd, so if the phone doesn't find the SD contents, try looking for it under a different directory in root, mine was external_sd

If the system doesn't pickup the drivers correctly. Go to the device manager, you will see W5 with a yellow exclamation mark. Choose to update the drivers manually and choose driver from a list and look for LGE Mobile ADB, I suspect other ADB android drivers might work as well, the one automatically installed by the system after I got android working is now Android Net Sooner Single ADB Interface.

If you are unsure what model you have or if it does have some letters that are not common, just look for over the phone. In my case the model was D320AR and I couldn't find any aboots for it, however somewhere near the battery it said D320F8 and I was able to find that aboot and successfully recover the phone from the Purple screen.
 
You must log in or register to reply here.
Back
Top Bottom