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

Root [D320N] Unlock Bootloader Issue

Mola_2

Mola_2

Lurker
I tried many times to unlock bootloader of my phone using the tutorial in the forum but at the end of part one i notice that there is a memory error like this :

[*] Now going to zero out the laf partition

/dev/block/platform/msm_sdcc.1/by-name/laf: write error: No space left on device.

So now I lost the download mode and the original recovery. How can I unlock the bootloader properly and then flash some recovery and custom ROMs?
Thanks for the help,
Marco
 
That sounds about right. You should get an error similar to that.
It should then say 'Completed in 1.2 seconds'
If you no longer have download mode, you should instead boot into fastboot mode using the download mode key combo.
 
Yes i can go into fastboot, so i tried to flash some recovery but i failed. I'd like to flash twrp to install RRemix unofficial rom. Which version of the twrp recovery i must flash? Are there some extras that i must do before flash the rom on d320n? I rooted my phone but i have not yet updated supersu binaries. Any suggestions?
Thanks for the help.
 
Did you
Code: 
fastboot oem unlock
?
If not you will get a boot error anyways.
You MUST find twrp for YOUR EXACT MODEL or you will just get a pink screen or something to that effect.
The kernels are different between the variants.
If you can find one, the latest version is 2.8.7.0
 
I can boot the stock ROM and the phone works properly, but I get pink screen if I try to boot in recovery. I will try to do that command in fastboot mode and than i will flash the recovery thankyou!
 
I flash the recovery using fastboot. Fastboot says the bootloader is unlocked but if i try to go into twrp recovery i have pink screen. What is wrong?
 
I had a similar issue, also got the pink screen while trying to boot into recovery mode. I went on and installed a custom rom nonetheless and all I got was the purple screen. The problem in my case was related to the aboot file... If it happens to you there is plenty of info in this forum.

Anyway, using fastboot you can also boot an image that is stored in the computer and not the phone
Put the image in the same directory as fastboot (so that you don't have to write the path to the file)
then issue:

fastboot boot TWRP.img or whatever the image file name is. It should boot into TWRP without any problems.
 
Yup, known aboot problem. There's a link in my signature which leads to the thread with solution for that.
 
Thankyou i found the thread but i did not understand so much. If i flash patched aboot.bin on my phone i will lose the possibility to boot the stock ROM? Moreover using the patched aboot.bin can i boot the twrp and make nanadroid backups and flash custom roms (like CM or RRMX)? Sorry for being insistent but i really don't want to brick my phone!
 
Do not worry, many people have bricked their phones so you don't have to! Find the proper aboot and flash via fastboot or dd command.
 
You must log in or register to reply here.
Back
Top Bottom