Database Develop

[Q] Huawei p7 Bootloop

A couple of days ago my Huawei p7 started to shut itself down and after that it keeps rebooting.
It starts itself up and I get into the choose your language screen and then it shuts down.
When i try to get into the system recovery (using volume & power) I get the following screen:
Android system recovery <3e>
Huawei software installed failed.
Please retry!
Shutdown system now
There is no UPDATE.APP
.............................................
FAIL
And even in system recovery it keeps rebooting.
Im kinda helpless at the moment not knowing what to do.
Did this occur to anyone ? Is there a solution for this problem ?
Thanks in advance.

You should download firmware update file from Huawei Official web site. Extract dload folder from downloaded archive and put it on your SD card. After that you should try to trigger firmware update with factory reset (method which is usually called "force update") by holding all three buttons when the phone is turned off.
But maybe your phone have some hardware problem if it restarts even in recovery mode.
UPDATE:
Does phone restarts itself when it's in fastboot mode (you can get into that mode by holding VOLUME DOWN and POWER button while phone is turned off and connected into USB port of computer just before pressing that button combination) ??

wekii said:
You should download firmware update file from Huawei Official web site. Extract dload folder from downloaded archive and put it on your SD card. After that you should try to trigger firmware update with factory reset (method which is usually called "force update") by holding all three buttons when the phone is turned off.
But maybe your phone have some hardware problem if it restarts even in recovery mode.
UPDATE:
Does phone restarts itself when it's in fastboot mode (you can get into that mode by holding VOLUME DOWN and POWER button while phone is turned off and connected into USB port of computer just before pressing that button combination) ??
Click to expand...
Click to collapse
I've downloaded the update file and proceeded with your steps. I continued to trigger the firmware update with the factory reset.
At first it seemed to work, the phone started updating but after a couple of seconds it started to reboot itself again
I got the phone in fastboot mode and at this moment it does not restart itself !
I went on downloading Hisuite and at this moment it keeps searching for drivers on the network.
The searching for drivers is taking quite some time is this normal ?
Thank you very much for your help so far !

OK, maybe these are good news if you say that your phone doesn't restart when it's in fastboot mode.
I would recommend you to try to reflash your phone's stock recovery and boot images with those extracted from firmware that you are trying to install.
Follow these steps:
Download Huawei Extractor tool from here,
Open update.app with Huawei Extractor and extract next two images: RECOVERY and BOOT (you can do that by selecting those two images while holding CTRL button, then right click > Extract Selected),
When extracted, rename those two images into "recovery.img" and "boot.img",
Copy those two images into "platform-tools" folder of Android SDK,
Run command prompt and go to "platform-tools" folder by using "cd" command,
Start your phone into fastboot mode,
Enter following command into command prompt: "fastboot devices" (without quotes), you should get your phone's serial number listed, if that's right, go to the next step,
Enter: "fastboot oem get-bootinfo", it needs to say that your bootloader is unlocked. If it's not you need to enter the next command "fastboot oem unlock 1234567812345678", where "1234567812345678" should be replaced with unlock code that is unique for your device. Instructions which explain how to obtain unlock code for your device can be found here,
Flash your phone's recovery with "fastboot flash recovery recovery.img",
Flash your phone's boot image with: "fastboot flash boot boot.img",
After successful flashing of both images, turn your phone off by holding POWER button for a several seconds,
Prepare SD card on your PC by formatting SD card and copying "dload" folder of phone's firmware onto SD card,
After you insert SD card into phone, start your phone with "forced install" method by holding all three buttons on your phone.
After that your phone should process firmware install successfully if there is no some hardware issues. Good luck and inform us about your progress.

wekii said:
OK, maybe these are good news if you say that your phone doesn't restart when it's in fastboot mode.
I would recommend you to try to reflash your phone's stock recovery and boot images with those extracted from firmware that you are trying to install.
Follow these steps:
Download Huawei Extractor tool from here,
Open update.app with Huawei Extractor and extract next two images: RECOVERY and BOOT (you can do that by selecting those two images while holding CTRL button, then right click > Extract Selected),
When extracted, rename those two images into "recovery.img" and "boot.img",
Copy those two images into "platform-tools" folder of Android SDK,
Run command prompt and go to "platform-tools" folder by using "cd" command,
Start your phone into fastboot mode,
Enter following command into command prompt: "fastboot devices" (without quotes), you should get your phone's serial number listed, if that's right, go to the next step,
Enter: "fastboot oem get-bootinfo", it needs to say that your bootloader is unlocked, if it's not read this,
Flash your phone's recovery with "fastboot flash recovery recovery.img",
Flash your phone's boot image with: "fastboot flash boot boot.img",
After successful flashing of both images, turn your phone off by holding POWER button for a several seconds,
Prepare SD card on your PC by formatting SD card and copying "dload" folder of phone's firmware onto SD card,
After you insert SD card into phone, start your phone with "forced install" method by holding all three buttons on your phone.
After that your phone should process firmware install successfully if there is no some hardware issues. Good luck and inform us about your progress.
Click to expand...
Click to collapse
Hi,
I've got the same issue.
When I start to "force install" method, my phone doesn't boot.
It just stay in a state of "charging" but nothing append.
I flashed boot and recovery with Fastboot.
But now, when I start the phone in Fastboot&Rescue Mode, the device doesn't appear in the liste when I run adb devices.
But when I start in the "force install" mode, adb devices returns the serial of the phone (but it doesn't respond to fastboot command).
Are there other files to flash on the phone than juste recovery and boot ?
Thank's for those steps, i'll continue to try to flash again.
Edit :
Ok phone is back !
The problem came from my SD Card, I had not only the dload folder, but an other file.
Format SD Card -> dload folder -> "force install" method -> ENJOY !
Thank's a lot !

wekii said:
OK, maybe these are good news if you say that your phone doesn't restart when it's in fastboot mode.
I would recommend you to try to reflash your phone's stock recovery and boot images with those extracted from firmware that you are trying to install.
Follow these steps:
Download Huawei Extractor tool from here,
Open update.app with Huawei Extractor and extract next two images: RECOVERY and BOOT (you can do that by selecting those two images while holding CTRL button, then right click > Extract Selected),
When extracted, rename those two images into "recovery.img" and "boot.img",
Copy those two images into "platform-tools" folder of Android SDK,
Run command prompt and go to "platform-tools" folder by using "cd" command,
Start your phone into fastboot mode,
Enter following command into command prompt: "fastboot devices" (without quotes), you should get your phone's serial number listed, if that's right, go to the next step,
Enter: "fastboot oem get-bootinfo", it needs to say that your bootloader is unlocked, if it's not read this,
Flash your phone's recovery with "fastboot flash recovery recovery.img",
Flash your phone's boot image with: "fastboot flash boot boot.img",
After successful flashing of both images, turn your phone off by holding POWER button for a several seconds,
Prepare SD card on your PC by formatting SD card and copying "dload" folder of phone's firmware onto SD card,
After you insert SD card into phone, start your phone with "forced install" method by holding all three buttons on your phone.
After that your phone should process firmware install successfully if there is no some hardware issues. Good luck and inform us about your progress.
Click to expand...
Click to collapse
I followed all your steps but i get stuck at step 7. When I give the command fastboot devices it doesn't show my phone's serial number. Instead it shows a ? (question mark).
Did I do something wrong or is there a solution for this?
Thanks in advance!

Maybe you should try other version of platform tools. I would recommend you to download adt-bundle-windows-x86_64-20140702.zip (x64) or adt-bundle-windows-x86-20140702.zip (x32) from "Android SDK" official web pages (I assume that your are using Windows OS). After download extract only "platform-tools" directory to the root of Windows C:\ partition and try described procedure again.
However if you are still getting question marks instead of phone's serial number, you should ignore that step and go onto the next one. I had the same problem in the past and flash commands were successful even serial number wasn't been displayed.
Keep us informed about your progress. Good luck zbnd !!

wekii said:
Maybe you should try other version of platform tools. I would recommend you to download adt-bundle-windows-x86_64-20140702.zip (x64) or adt-bundle-windows-x86-20140702.zip (x32) from "Android SDK" official web pages (I assume that your are using Windows OS). After download extract only "platform-tools" directory to the root of Windows C:\ partition and try described procedure again.
However if you are still getting question marks instead of phone's serial number, you should ignore that step and go onto the next one. I had the same problem in the past and flash commands were successful even serial number wasn't been displayed.
Keep us informed about your progress. Good luck zbnd !!
Click to expand...
Click to collapse
Thanks for your response !
So I followed through like you said. Gave the fastboot oem get-bootinfo command and then I got (bootloader) locked. So I followed the bootloader's unlock code (official way), entered my product SN and product IMEI, used the Huawei Product ID generator followed the procedure and all I get is : Please input the correct Product ID
What did I do wrong this time ? I'm not sure if it's even possible to do this wrong. Is there another way around ?

You can unlock with Vroot, like I did. I didn't try to get a serial from Huawei.
For the Fastboot command 'Fastboot device's I had a ? too, but with 'adb devices' command, I got my serial number.
Sent from my HUAWEI P7-L10 using XDA Free mobile app

Pboguet said:
You can unlock with Vroot, like I did. I didn't try to get a serial from Huawei.
For the Fastboot command 'Fastboot device's I had a ? too, but with 'adb devices' command, I got my serial number.
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Click to expand...
Click to collapse
I've downloaded Vroot (english version) but when i connect my phone it says not support mode
I tried to connect while in fastboot&rescue mode, because this is the only way the phone stays on without restarting.
I then tried to connect without fastboot&rescue mode. But my phone keeps rebooting. I did get a message that USB debugging is disabled. However I can't enable usb debugging because my phone won't boot up normally.

@Pboguet
You should read carefully because your answer has no sense for the phone which is in state like zbnd's phone is.
 @zbnd
Maybe you are doing something wrong. You can send me your's phone serial number and IMEI in PM inbox, I will try to generate unlock code for you.

wekii said:
@Pboguet
You should read carefully because your answer has no sense for the phone which is in state like zbnd's phone is.
@zbnd
Maybe you are doing something wrong. You can send me your's phone serial number and IMEI in PM inbox, I will try to generate unlock code for you.
Click to expand...
Click to collapse
Thank you very much for all your help!
Despite following all your steps my phone keeps rebooting

Sorry to hear that. Did you manage to make all steps that I described to you? Can you share more informations about your current efforts please.

wekii said:
Sorry to hear that. Did you manage to make all steps that I described to you? Can you share more informations about your current efforts please.
Click to expand...
Click to collapse
Ik
After unlocking my phone I got the message unlocked in CMD.
I then flashed recovery and boot. Both times it said that the flash was succesfull, this only took a few seconds I don't know if thats normal? I then followed your last steps ( dload folder etc) and put the SD card in my phone.
It start installing but after approximetaly 25 seconds the phone shuts itself down and then reboots.
The procedure then starts again and it starts installing followed by shutting down and rebooting.

I'm sorry to hear that. Seems like it's some hardware issue.
However I still have one more idea that you can try in fastboot mode. I would recommend you to install entire firmware manually with fastboot commands.
By following previously described procedure try to extract with "Huawei Extractor" tool next images also: SYSTEM, USERDATA, CUST and CACHE.
After step number 10, try to use next commands also:
"fastboot flash system system.img"
"fastboot flash cust cust.img"
"fastboot flash userdata userdata.img"
"fastboot flash cache cache.img"
When you are finished with flashing of all images, use "fastboot reboot" command to restart your phone. Steps 11, 12 and 13 should be ignored this time.
Let me know the result

Hey, I'm glad I found this forum, because I have exactly the same problem! Since zbnd did not reply I wanted to let you know that flashing boot.img, recovery.img, cache.img, userdata.img, cust.img and system.img via fastboot did not work
The commandline for each file said "OKAY" and "finished" therefore I assume the process(es) completed succesfully.
Maybe I should tell you some information and the steps I did with my P7:
- my device is a branded german telekom version with firmware P7-L10-V100R001C150B122​- because of crappy pink telekom bootlogo und bloatware I wanted to flash the original huawei firmware so I downloaded the B126 from the official website and updated via force update method​- at the end of the update process i got the messages "huawei cust fail" and "update_post_process fail" but when I rebootet the B126 was installed and showed a message "Defect report reminders - This is an internal test version. Please report defects to Yangyexiao 00143718" - can't be correct, I thought​- after googling a lot and reading through several forums I rooted my device with RootGenius, installed HiSuite and Android-SDK (driver were installed correctly, adb devices showed a device with serial) and deleted the "cust" directory on my phone - at that point everything still worked​- next step: I installed TWRP 2.7.1.0, made an updateable zip file with huawei update extractor (including system.img, userdata.img, cust.img and boot.img) and flashed it via TWRP. The process completed succesfully, but needed only a few seconds. After that I got this bootloop at the language selection​- then I wanted to return to the last functioning state, so I flashed the stock recovery via fastboot and started with force update method. But after a few seconds the device rebooted during the update process which led to another (maybe the same) bootloop. I had to remove the sd card, but the device continued to reboot in recovery mode. So i installed TWRP 2.7.1.0 again​- Then I tried to restore a B133 backup I got from another forum, but it obviously did not work (see attached image)​
Now I just don't know what to do ... I get a bootloop in stock recovery and I get a bootloop in TWRP 2.8.0.0.
Only TWRP 2.7.1.0 does not reboot. What is about the other files inside the UPDATE.APP (modemimage.img, efi.img, etc)? Is it possible that some of these files are needed?
Thanks in advance...

mbert said:
Hey,
Only TWRP 2.7.1.0 does not reboot.
Thanks in advance...
Click to expand...
Click to collapse
If this recovery works than try:
1. Save this Se7en or this HRT or this custom MIUI ROM on SD card
2 .Wipe in TWRP everything (dalvik, system,data,cust, internal) except external (SD card). Internal only if You have a backup or not important data there.
4. Install zipp ROM from external memory. Sometimes try more than one time in fail case. For HRT ROM especially.
Let me know if helped.

Ziółek said:
If this recovery works than try:
1. Save this Se7en or this HRT or this custom MIUI ROM on SD card
2 .Wipe in TWRP everything (dalvik, system,data,cust, internal) except external (SD card). Internal only if You have a backup or not important data there.
4. Install zipp ROM from external memory. Sometimes try more than one time in fail case. For HRT ROM especially.
Let me know if helped.
Click to expand...
Click to collapse
failed
I tried se7en and miui.
I wiped dalvik,system,data,internal,cache and custom, which only lasted about 2 seconds, but said succesful (Is that enough to delete all partitions?).
Installation of both custom roms completed succesfully and lastet several seconds (max 1 min I think).
Se7en: reboot -> huawei logo -> reboot -> language selection (in the style of stock rom?) -> reboot ...
Miui: reboot -> miui logo -> reboot -> language selection (miui style) -> reboot -> wifi selection (I skipped) -> searching for sim card -> reboot

mbert said:
Hey, I'm glad I found this forum, because I have exactly the same problem! Since zbnd did not reply I wanted to let you know that flashing boot.img, recovery.img, cache.img, userdata.img, cust.img and system.img via fastboot did not work
The commandline for each file said "OKAY" and "finished" therefore I assume the process(es) completed succesfully.
Maybe I should tell you some information and the steps I did with my P7:
- my device is a branded german telekom version with firmware P7-L10-V100R001C150B122​- because of crappy pink telekom bootlogo und bloatware I wanted to flash the original huawei firmware so I downloaded the B126 from the official website and updated via force update method​- at the end of the update process i got the messages "huawei cust fail" and "update_post_process fail" but when I rebootet the B126 was installed and showed a message "Defect report reminders - This is an internal test version. Please report defects to Yangyexiao 00143718" - can't be correct, I thought​- after googling a lot and reading through several forums I rooted my device with RootGenius, installed HiSuite and Android-SDK (driver were installed correctly, adb devices showed a device with serial) and deleted the "cust" directory on my phone - at that point everything still worked​- next step: I installed TWRP 2.7.1.0, made an updateable zip file with huawei update extractor (including system.img, userdata.img, cust.img and boot.img) and flashed it via TWRP. The process completed succesfully, but needed only a few seconds. After that I got this bootloop at the language selection​- then I wanted to return to the last functioning state, so I flashed the stock recovery via fastboot and started with force update method. But after a few seconds the device rebooted during the update process which led to another (maybe the same) bootloop. I had to remove the sd card, but the device continued to reboot in recovery mode. So i installed TWRP 2.7.1.0 again​- Then I tried to restore a B133 backup I got from another forum, but it obviously did not work (see attached image)​
Now I just don't know what to do ... I get a bootloop in stock recovery and I get a bootloop in TWRP 2.8.0.0.
Only TWRP 2.7.1.0 does not reboot. What is about the other files inside the UPDATE.APP (modemimage.img, efi.img, etc)? Is it possible that some of these files are needed?
Thanks in advance...
Click to expand...
Click to collapse
To use fastboot you need to unlock bootloader first. And before flash, you need to erase partition first, for a proper job. Please read well about the fastboot procedure is a dangerous procedure

My bootloader is unlocked, but fastboot sais I don't have permission to erase partitions ...
Gesendet von meinem HUAWEI P6-U06 mit Tapatalk

[Tutorial] Unbrick Optimus l3 e400 if you get bootloop after a kdz update

In normal circunstances, kdz update sould be the solution for bricked phones, but some (Very rare) times, it become the trouble itself.
It happened yesterday, i've flashed the kdz file on my l3 as usual, but instead of getting the stock rom, I got a bootloop.
This happened probably because I was using sdmerge before, and after flashing the stock kdz, the /data partition became corrupted in a way that nor stock rom or stock recovery was able to deal with the corrupted data, so the only thing i had access was the emergency mode.
In this case, the obvious solution is use cwm to wipe /data, but to flash cwm I need a working rom, and I didn't had any,
so in this tutorial we will flash cwm with kdz update to wipe /data and ressurect the phone.
the tutorial was originally posted here, but it's for optimus black, well, the process is almost the same here but i'll post it here because when this problem happened the first thing i did was to google "bootloop after kdz update e400", but i didn't found nothing and only founded that post some hours later.
you will need:
The cwm image
The KDZ file
Your prefered tool to flash the kdz
Cheat engine
CWMInject
The kdz file is encripted, so you can't simplely insert the cwm image on kdz, you must have the decrypted image to inject the cwm, well, the kdz is decrypted by the flashing tool before upload and the decrypted image is on the program's memory, so you will use cheatengine to find the memory adress of the stock recovery and use CWMInject to inject the cwm on the memory before the flashing tool reaches this adress, so you need to be fast!
1- open the task manager, the flashing tool, cwminject (don't forget to run it as administrator) and cheatengine.
2- on the flashing tool, prepare everything to the flash but DO NOT start the flashing process.
3- on cwminject, select the flash tool's process and the cwm image
4- on cheat engine, select the flash tool's process, set Value Type for String and scan Type for Search for text, on the text field type "ANDROID!".
5- Start the flashing process and keep the eye on the taskmanager, when the amount of memory used by the flasher grows you know that the kdz was decrypted, click on first scan on cheat engine, it sould find FOUR adresses with the word "ANDROID!", if it don't find the word or if it only find one it means that you have scanned to early and the image was not completely decrypted yet, in this case just click on new scan and then scan again until it find FOUR adresses with the word "ANDROID!", the last one is the adress that you need.
6- Now be fast to put the adress on the cwminject and click on write memory, the stock recovery will be overwritten with cwm.
7- Now just wait the flashing ends, your phone will continue with the bootloop, but now, you should have the cwm installed, so put back the battery and turn the phone on holding vol- and home to start the cwm recovery.
8- now you can wipe the /data partition and bring the phone back to life.
9- (OPTIONAL) flash the stock kdz without modifications, i recomend you to do that because we have used hacking methods do modify the flasher's memory, and we don't know all of the effects of this modification, your phone will not enter in the bootloop anymore because we have fixed the /data partition with cwm and the /data partition is not written when we flash a kdz.

It never happened with me, but thanks anyway!!!!:good::good::good::good::good:

thanks

[GUIDE] Unbrick a Hard Bricked L90 all variants

Warning: Use this at your own risk. I’m not responsible for any damages that may happen due to using this guide.
Problem:
LG L90 stuck at LG Boot Logo;
Cannot enter download mode;
Stuck at factory reset screen (factory reset processing) and cannot enter recovery;
Cannot enter fastboot mode;
Cannot enter qhsusb mode, or Qualcomm 9008 mode;
Attention: All the unbricking process is made WITHOUT the battery in the phone.
If your device is recognized in device manager as qhsusb_bulk or Qualcomm HS-USB QDloader 9008 jump to part 2.
Part 1 – Put the phone in qhsusb mode:
1.1 Disassembly the phone: Vídeo
1.2 Find the Test Point;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Compatible whith the folloing models: D400h, D400hn, D405, D405h, D405n, D405tr, D410, D410h, D410hn, D415, D415rd)
1.3 Connect the usb cable to the device (don’t connect it to pc yet);
1.4 Prepare the Test Point wires;
(I personally use an usb extension)
1.5 Short the phone resistor;
1.6 Connect the usb cable to pc;
1.7 Wait until Windows to recognize the device;
1.8 Disconnect the Test Point;
Now you should have the phone in qhsusb mode (Device Manager shows “QHSUSB_BULK” or “Qualcomm HS-USB QDloader 9008”).
If the phone doesn’t get recognized repeat this steps again.
If you see “Qualcomm HS-USB QDloader 9008” in Device Manager jump to the part 2;
If you see “QHSUSB_BULK” in Device Manager follow the next steps:
1.1.1 Download L90_Drivers.zip; (https://3r0xub.s.cld.pt)
1.1.2 Install the DriverL90;
1.1.3 If Windows can’t install it properly, restart the pc and press F8 repeatedly, a boot menu will appear, select "Disable Driver Signature Enforcement". Then you need to repeat everything from the beginning (Step 1.1);
1.1.4 Even if you can’t install it properly, try to install the AlternativeDriver. Then you need to repeat the whole process from the beginning (Step 1.1);
Part 2 – Restore Phone files:
2.1 Unzip L90_Hardbrick.zip; (https://ntqyw2.s.cld.pt)
2.2 Start boarddiag (b2b.exe);
2.3 Choose “W7 G2MDS (MSM8226)” Chipset;
2.4 Choose Port according to the port you see in the Device Manager;
2.5 Select your “Target Dir”;
2.6 Check “AP check”;
2.7 Check “EMMC”;
2.8 Press “START” button;
2.9 After some time you should see “PASS” in AP and EMMC. Then you just need to check “RESTORE BOOT IMG” and flash the files in this order:
1- aboot;
2- BackupGPT;
3- boot;
4- laf;
5- PrimaryGPT;
6- recovery;
7- rpm;
8- tz;
9- sbl1;
After flashing all the files remove the usb cable, put the phone back together, and turn it on. Now you should have the phone working again.
If you get "device was not found in dload trying flash programmer" error, go to Device Manager, expand the COM ports section, right click on the QDloader 9008 device, select Update Driver Software, follow the steps and point to the DriverL90. Reboot your PC and try the steps again. (Thanks @krusli)
If the phone hangs on LG Boot Logo, do a factory reset.
Factory Reset
1. Turn off the device;
2. Press and hold Volume Down key + Power Key;
3. Release Power key when LG logo appear;
4. Press and hold Power key again;
5. Release all keys when Factory Data Reset menu appears;
After that, you have to offline flash a stock KDZ for your L90 variant
Sources:
4pda (http://4pda.ru/forum/lofiversion/index.php?t575959-4560.html)
Credits to @TreQUS

This is probably the last resort for those that cannot get into any mode or get their phone recognized in PC.
Too bad a complete disassembly is necessary since the test points are in the front of the motherboard.

Hi, help me pls
Hi, i am beginner and i don't know how i can connect 'this point' to GND in first picture and when i should 'disconnect' it. Pls help coz i reallly need it
Anyway thanks for this guide it's my problem coz when i upgrade kitkat 4.4.2 to lollipop on lg l90 it's stop in 2/2 steps (7% and 'blue screen' with some bad parts) and i can't go to recovery,download,s/w mode

justM4gic said:
Hi, i am beginner and i don't know how i can connect 'this point' to GND in first picture and when i should 'disconnect' it. Pls help coz i reallly need it
Anyway thanks for this guide it's my problem coz when i upgrade kitkat 4.4.2 to lollipop on lg l90 it's stop in 2/2 steps (7% and 'blue screen' with some bad parts) and i can't go to recovery,download,s/w mode
Click to expand...
Click to collapse
For me, the easiest way to connect 'this point' to GND is as I show in the third picture, you can also get a piece of wire and connect the GND to the resistor, something like this:
Atention, be carefull to not connect the wire anywhere else than those two points.
To know when you should disconnect the wire, just turn on your computer speakers, when you hear a sound like when you attach a flash drive, it's time to disconnect the wire.

Thanks it's work now all good i can see qualcomm, but It's not my problem coz when i start phone its still the same problem i mean when LG logo dissapear automatically running android update 2/2 part and after several seconds i have error on black screen. I think i need format but i don t know how to do it, i saw yestarday i can go into s/w mode but lg flash tool don t help too with installing new android, on computer i have 4.4.2 and lollipop for lg l90 and i just can see after installing 4.4.2 in s/w mode i have rooted device but nothing more it s still the same problem with update. I think error say something about fonts.
Edit:
I install 4.4.2 drivers in lollipop from this hardbrick.zip and that s why perhaps its not working, i install drivers from lollipop and now i don t see update but just logo and i can t get into recovery, i try install now original KDZ
Drivers i mean it s just what we see in RESTORE BOOT IMG and i changed these file to lollipop

This Works But...
This Works but now in "About Phone" shows V120b-OP1-HQ.
Formerly V20b-SCA-XXX and now the frontal camera doesn't work!
How to Fix this?

Thi_Memoria said:
This Works but now in "About Phone" shows V120b-OP1-HQ.
Formerly V20b-SCA-XXX and now the frontal camera doesn't work!
How to Fix this?
Click to expand...
Click to collapse
I think you used the recovery images from a different model to launch download mode. The hardbrick file is nothing more than the partition tables and partitions images backups until the laf mmcblk0p15 of an unknown L90 variant (probably D410 dual-SIM without NFC). I believe you are able to fix this by rooting, unlocking the bootloader and flashing the whole bootstack from you model. When I say whole, I mean all partitions you'll find inside the KDZ of your model (except for GPT tables of course). A TWRP flashable zip can be easily setup for this task. Many people can face this problem but I think this is the solution, the hardbrick file is a good start so you can launch download mode and after flash the proper images of your exact model.
I'm not sure this will solve your problem, but I believe this is the cause. :good:

Tanks
F. Gacrux said:
I think you used the recovery images from a different model to launch download mode. The hardbrick file is nothing more than the partition tables and partitions images backups until the laf mmcblk0p15 of an unknown L90 variant (probably D410 dual-SIM without NFC). I believe you are able to fix this by rooting, unlocking the bootloader and flashing the whole bootstack from you model. When I say whole, I mean all partitions you'll find inside the KDZ of your model (except for GPT tables of course). A TWRP flashable zip can be easily setup for this task. Many people can face this problem but I think this is the solution, the hardbrick file is a good start so you can launch download mode and after flash the proper images of your exact model.
I'm not sure this will solve your problem, but I believe this is the cause. :good:
Click to expand...
Click to collapse
Ok, I have the KDZ my unpacked device. and it contains these files; aboot abootb BackupGPT boot cust factory laf modem persist PrimaryGPT rct recovery rpm rpmb SBL1 sbl1b sDI system tz TZB all accompanied with a numbering system and divided 17 part example: system_933888 system_1197064 system_1201176 tz_150528 tzb_157696 etc ... What should I do?

Whats your variant and what kdz you are trying to flash (kk or ll)? If your bootloader is unlocked and you have TWRP installed, I can arrange the flashable zip for you, all you'll have to do it's to drag and drop the files into the zip.
The multiple system binaries can be merged in the LG Firmware Extract, there is a button to merge all in a single img file, this one can also be used to flash your system partition.

Tanks again
F. Gacrux said:
I think you used the recovery images from a different model to launch download mode. The hardbrick file is nothing more than the partition tables and partitions images backups until the laf mmcblk0p15 of an unknown L90 variant (probably D410 dual-SIM without NFC). I believe you are able to fix this by rooting, unlocking the bootloader and flashing the whole bootstack from you model. When I say whole, I mean all partitions you'll find inside the KDZ of your model (except for GPT tables of course). A TWRP flashable zip can be easily setup for this task. Many people can face this problem but I think this is the solution, the hardbrick file is a good start so you can launch download mode and after flash the proper images of your exact model.
I'm not sure this will solve your problem, but I believe this is the cause. :good:
Click to expand...
Click to collapse
So... I flash all available partitions KDZ and yet this V20b - OP1 -HQ the only partition that I found in KDZ was the " MISC " would be the problem ? I take this partition and flashing by fastboot ? I have unlocked bootloader and TWRP recovery and fastboot mode too!
I have another D410hn! Maybe i make backup the misc partition and flash on my device!
---------- Post added at 03:59 AM ---------- Previous post was at 03:51 AM ----------
F. Gacrux said:
Whats your variant and what kdz you are trying to flash (kk or ll)? If your bootloader is unlocked and you have TWRP installed, I can arrange the flashable zip for you, all you'll have to do it's to drag and drop the files into the zip.
The multiple system binaries can be merged in the LG Firmware Extract, there is a button to merge all in a single img file, this one can also be used to flash your system partition.
Click to expand...
Click to collapse
So... My variant is D410hn Brazil V20b Lollipop! Here the link to my kdz: csmgdl.lgmobile. com/dn/downloader.dev?fileKey=FW6332R032URAYPC7CBB62W/D410hn20b_00.kdz

Thi_Memoria said:
So... I flash all available partitions KDZ and yet this V20b - OP1 -HQ the only partition that I found in KDZ was the " MISC " would be the problem ? I take this partition and flashing by fastboot ? I have unlocked bootloader and TWRP recovery and fastboot mode too!
I have another D410hn! Maybe i make backup the misc partition and flash on my device!
---------- Post added at 03:59 AM ---------- Previous post was at 03:51 AM ----------
So... My variant is D410hn Brazil V20b Lollipop! Here the link to my kdz: csmgdl.lgmobile. com/dn/downloader.dev?fileKey=FW6332R032URAYPC7CBB62W/D410hn20b_00.kdz
Click to expand...
Click to collapse
Hi @Thi_Memoria sorry , I've been a little busy , and so I've not been able to watch this thread as much as I wanted.
Now that you have the phone working you have to flash (offline) the KDZ suitable for your device.
Here you can see how to flash your kdz: http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479

Thi_Memoria said:
So... I flash all available partitions KDZ and yet this V20b - OP1 -HQ the only partition that I found in KDZ was the " MISC " would be the problem ? I take this partition and flashing by fastboot ? I have unlocked bootloader and TWRP recovery and fastboot mode too!
I have another D410hn! Maybe i make backup the misc partition and flash on my device!
---------- Post added at 03:59 AM ---------- Previous post was at 03:51 AM ----------
So... My variant is D410hn Brazil V20b Lollipop! Here the link to my kdz: csmgdl.lgmobile. com/dn/downloader.dev?fileKey=FW6332R032URAYPC7CBB62W/D410hn20b_00.kdz
Click to expand...
Click to collapse
Mine is also the brazilian variant D410hn.
The files you flashed to get access to download mode are from the Asian CIS D410 (dual-SIM without NFC).
I unlocked the actual D410hn bootloader and made the proper bootstack for our version.
Make sure to be using TWRP 2.8.7.0, I didn't tested in older versions or CWM.
Bootstack - this flashes all D410hn partitions, except system: http://www.mediafire.com/download/mzc4qt5a7r79rcl/Bootstack_D410hn_Lollipop_v20b.zip
If you are willing to return to Lollipop (boot/system). This is the flashable android zip to install system without KDZ: http://www.mediafire.com/download/i2ijgbwa07o2ugf/Flashable_D410hn_Stock_Lollipop_v20b.zip
Before flashing the big lollipop (second zip), wipe data/cache/dalvik/system, since it's a huge file, It takes around 10 minutes to flash. Also, after that flash SuperSU: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip then reboot and check if everything is back to normal.

Solved?!
neverdies said:
Hi @Thi_Memoria sorry , I've been a little busy , and so I've not been able to watch this thread as much as I wanted.
Now that you have the phone working you have to flash (offline) the KDZ suitable for your device.
Here you can see how to flash your kdz: http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Click to expand...
Click to collapse
Ok I know about Flash KDZ Updater and I found out where the problem is! he is in MISC partition and CUST partition, I edited files CUST partition with Root Explorer and now is normal and front camera working now! I edited these files: cust.prop cust_grup_mapping.cfg and cust.prop of open_sca folder. Tanks for All!:good:

The flashable bootstacks I made for D410hn also flash CUST partitions, this would have solved your problem too. In fact flashes all partitions in kdz, except boot and system that are in another different zip. With those two files you can flash everything in TWRP just like lg kdz would do if you have your partition table ok.

Help
F. Gacrux said:
The flashable bootstacks I made for D410hn also flash CUST and MISC partitions, this would have solved your problem too. In fact flashes all partitions in kdz, except boot and system that are in another different zip. With those two files you can flash everything in TWRP just like lg kdz would do if you have your partition table ok.
Click to expand...
Click to collapse
So... I flash this Bootstack_D410hn_Lollipop_v20b and my imei is now "0"
i'm downloading the big zip now

Thi_Memoria said:
So... I flash this Bootstack_D410hn_Lollipop_v20b and my imei is now "0"
i'm downloading the big zip now
Click to expand...
Click to collapse
Weird, because I flashed kk and ll bootstack multiple times between kk, ll, cm11 and cm 12.1 flashes and my imei remains the same. Try to flash system and boot of the big zip.
Edit: Sorry for the wrong info, it doesn't flash misc partition since it do not exist in kdz, I see you modified some files in misc partition, this might be the cause for your lost imei.
For reference, my cust.prop at cust root folder is
# Define cupss root dir from NT Code or BUYER
ro.lge.capp_cupss.rootdir=/cust
# Define CUPSS group in SWOV
ro.lge.cupssgroup=OP1-HQ
# Define Google Client ID
ro.com.google.clientidbase=android-om-lge
ro.com.google.clientidbase.ms=android-om-lge
ro.com.google.clientidbase.am=android-om-lge
ro.com.google.clientidbase.gmm=android-om-lge
ro.com.google.clientidbase.yt=android-om-lge
ro.lge.callduration=1
cust_group_mapping.cfg
ro.lge.cupssgroup=OP1-HQ
cust.prop at open_sca folder:
# Define cupss root dir from NT Code or BUYER
ro.lge.capp_cupss.rootdir=/cust/OPEN_SCA
# Define target operator/country/region
ro.build.target_operator=OPEN
ro.build.target_country=SCA
ro.build.target_region=SCA
# Default language
ro.product.locale.region=BR
ro.product.locale.language=pt
ro.build.default_country=BR
# Define Google Client ID
ro.com.google.clientidbase=android-om-lge
ro.com.google.clientidbase.ms=android-om-lge
ro.com.google.clientidbase.am=android-om-lge
ro.com.google.clientidbase.gmm=android-om-lge
ro.com.google.clientidbase.yt=android-om-lge
# Define SWV from CUPSS : Important for releasing Event Version
# Define swversion property when release official version
ro.lge.swversion=D41020b
ro.lge.swversion_short=V20b
ro.lge.swversion_rev=0
#ro.lge.swversion_svn=0
# Define swv_date property when the version date need to fix as the specific date
#ro.lge.swv_date=DEC-05-2013
ro.lge.opensw=SCA-XXX
# Define CUPSS group in SWOV
ro.lge.cupssgroup=OP1-HQ
# Define call duration feature
ro.lge.callduration=1
# Define handwriting
ime_handwriting_apply=false
ime_trace_apply=false
ime_trace_menu=false
# Define cust language set
ro.lge.custLanguageSet=true
# Cell Broadcast scenario
persist.sys.cust.cbinfo_not_bar=true
# Enable MLT at SetupWizard
persist.sys.mlt_swupdt=1
If nothing works, try to flash the foreign d410 lollipop bootstack: http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632 you flashed another variant unbrick images I believe some "unique" partitions were overwritten by this flash and your phone no longer is a d410hn anymore at software level.

Nothing...
F. Gacrux said:
Weird, because I flashed kk and ll bootstack multiple times between kk, ll, cm11 and cm 12.1 flashes and my imei remains the same. Try to flash system and boot of the big zip.
Edit: Sorry for the wrong info, it doesn't flash misc partition since it do not exist in kdz, I see you modified some files in misc partition, this might be the cause for your lost imei.
For reference, my cust.prop at cust root folder is
# Define cupss root dir from NT Code or BUYER
ro.lge.capp_cupss.rootdir=/cust
# Define CUPSS group in SWOV
ro.lge.cupssgroup=OP1-HQ
# Define Google Client ID
ro.com.google.clientidbase=android-om-lge
ro.com.google.clientidbase.ms=android-om-lge
ro.com.google.clientidbase.am=android-om-lge
ro.com.google.clientidbase.gmm=android-om-lge
ro.com.google.clientidbase.yt=android-om-lge
ro.lge.callduration=1
cust_group_mapping.cfg
ro.lge.cupssgroup=OP1-HQ
cust.prop at open_sca folder:
# Define cupss root dir from NT Code or BUYER
ro.lge.capp_cupss.rootdir=/cust/OPEN_SCA
# Define target operator/country/region
ro.build.target_operator=OPEN
ro.build.target_country=SCA
ro.build.target_region=SCA
# Default language
ro.product.locale.region=BR
ro.product.locale.language=pt
ro.build.default_country=BR
# Define Google Client ID
ro.com.google.clientidbase=android-om-lge
ro.com.google.clientidbase.ms=android-om-lge
ro.com.google.clientidbase.am=android-om-lge
ro.com.google.clientidbase.gmm=android-om-lge
ro.com.google.clientidbase.yt=android-om-lge
# Define SWV from CUPSS : Important for releasing Event Version
# Define swversion property when release official version
ro.lge.swversion=D41020b
ro.lge.swversion_short=V20b
ro.lge.swversion_rev=0
#ro.lge.swversion_svn=0
# Define swv_date property when the version date need to fix as the specific date
#ro.lge.swv_date=DEC-05-2013
ro.lge.opensw=SCA-XXX
# Define CUPSS group in SWOV
ro.lge.cupssgroup=OP1-HQ
# Define call duration feature
ro.lge.callduration=1
# Define handwriting
ime_handwriting_apply=false
ime_trace_apply=false
ime_trace_menu=false
# Define cust language set
ro.lge.custLanguageSet=true
# Cell Broadcast scenario
persist.sys.cust.cbinfo_not_bar=true
# Enable MLT at SetupWizard
persist.sys.mlt_swupdt=1
If nothing works, try to flash the foreign d410 lollipop bootstack: http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632 you flashed another variant unbrick images I believe some "unique" partitions were overwritten by this flash and your phone no longer is a d410hn anymore at software level.
Click to expand...
Click to collapse
Nothing work... imei=0 imeisv=0

Thi_Memoria said:
Nothing work... imei=0 imeisv=0
Click to expand...
Click to collapse
I took a look into the unbrick images you used and I could identify that they came from the D410 (dual sim no nfc) v10d kitkat. I would try this two things:
1 - Flash D410 (dual sim no nfc) kitkat bootstack and CM11 (since it's a smaller file, just to test and see if you have you imei back).
If it don't work:
2 - Return stock lg recovery and flash KDZ via LG Flash Tools in emergency mode.
You can extract the binary from the KDZ (LG Firmware Extract, extrack kdz, then dz and extract the recovery_numbers.bin), name it recovery.bin, put in the root of your microSD and flash in terminal or adb with:
dd if=/storage/external_SD/recovery.bin of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Or use Jrummy ROM Installer.
Then follow this guide: http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
I have 2 L90 with the unlocked bootloader I made, I flashed the bootstacks hundred times to go between almost all custom roms available here in xda and stock and never faced this problem, probably something changed when you got the hard brick and flashed the d410 l90 variant unbrick images so you can never change your bootstack to d410hn again, I never flashed other variant files in my two L90 and they both are ok.
If nothing more works, unfortunately, I believe the only way is to make the test point again and redo the whole process :crying:

OK
F. Gacrux said:
I took a look into the unbrick images you used and I could identify that they came from the D410 (dual sim no nfc) v10d kitkat. I would try this two things:
1 - Flash D410 (dual sim no nfc) kitkat bootstack and CM11 (since it's a smaller file, just to test and see if you have you imei back).
If it don't work:
2 - Return stock lg recovery and flash KDZ via LG Flash Tools in emergency mode.
You can extract the binary from the KDZ (LG Firmware Extract, extrack kdz, then dz and extract the recovery_numbers.bin), name it recovery.bin, put in the root of your microSD and flash in terminal or adb with:
dd if=/storage/external_SD/recovery.bin of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Or use Jrummy ROM Installer.
Then follow this guide: http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
I have 2 L90 with the unlocked bootloader I made, I flashed the bootstacks hundred times to go between almost all custom roms available here in xda and stock and never faced this problem, probably something changed when you got the hard brick and flashed the d410 l90 variant unbrick images so you can never change your bootstack to d410hn again, I never flashed other variant files in my two L90 and they both are ok.
Click to expand...
Click to collapse
OK i am download this now and i have the cm11 installed on my device!

Thi_Memoria said:
OK i am download this now and i have the cm11 installed on my device!
Click to expand...
Click to collapse
Make sure to flash kitkat recovery if you are using kitkat bootstack.

Recovery problem

Hey
My phone is LG L90 410
I was trying to install cm 12.1 -i'm on official lg lolipop rom-
first i tried to install CWM .. i used Flashify
then after try enter the recovery menu it says "secure booting error cause boot certification"
then enter a purple screen asking for something like RAM dump
any help please to fix this ?

KareemWaheed said:
Hey
My phone is LG L90 410
I was trying to install cm 12.1 -i'm on official lg lolipop rom-
first i tried to install CWM .. i used Flashify
then after try enter the recovery menu it says "secure booting error cause boot certification"
then enter a purple screen asking for something like RAM dump
any help please to fix this ?
Click to expand...
Click to collapse
Did you unlock the bootloader before install the recovery?
Can you still boot to android?

same problem here too... device is rooted ... tried to install twrp but when I want to enter into recovery this problem appears
Yes, in my case I can boot into android ... just when pink screen ram dump appears need to hold power button to restart and it boot android like normal

@KareemWaheed @gjurosi
Follow this guide: http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690
This should fix your phones.

neverdies said:
@gjurosi
Follow this guide: http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690
This should fix your phones.
Click to expand...
Click to collapse
tried but nothing,extract aboot.bin to external storage and in terminal when I tried to tipe commands it says unallowed user

gjurosi said:
tried but nothing,extract aboot.bin to external storage and in terminal when I tried to tipe commands it says unallowed user
Click to expand...
Click to collapse
Did you grant root permision, after typing "su" in terminal?

neverdies said:
Did you grant root permision, after typing "su" in terminal?
Click to expand...
Click to collapse
last time I had that option ... now this situation,dont know anymore why I cant ...? I'll make factory reset then everything from the begining ... one question..when I downloaded this aboot.bin with unlock bootloader,I only need to extract it on external storage?
I cant see any (original) aboot.bin in external storage when I enter phone

gjurosi said:
last time I had that option ... now this situation,dont know anymore why I cant ...? I'll make factory reset then everything from the begining ... one question..when I downloaded this aboot.bin with unlock bootloader,I only need to extract it on external storage?
I cant see any (original) aboot.bin in external storage when I enter phone
Click to expand...
Click to collapse
As you can see at that guide, you need to put the patched aboot.bin on your external sd (/storage/external_SD/aboot.bin) then run the following commands on your phone's terminal.
Code:
su
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
After the su command you've to accept the root request.
Be sure to download and flash the right version of aboot for your phone variant, a wrong version of aboot will brick your phone.

@neverdies ....
in terminal I run the following commands ,but it says "cannot open for read:no such file or directory" ... I put aboot.bin on external storage ...dont know anymore wtf ?!? and I cant do factory reset !!!! again its security boot error and pink screen...
dont know why now... really annoying

gjurosi said:
@neverdies ....
in terminal I run the following commands ,but it says "cannot open for read:no such file or directory" ... I put aboot.bin on external storage ...dont know anymore wtf ?!? and I cant do factory reset !!!! again its security boot error and pink screen...
dont know why now... really annoying
Click to expand...
Click to collapse
Are you sure that your aboot.bin file is in /storage/external_SD?
You can put the aboot.bin in your internal memory instead, or anywhere else, just change command according to your aboot.bin file location.
Exemple if you put your aboot.bin file in /storage/internal_SD run the following command:
Code:
su
dd if=[B]/storage/internal_SD/aboot.bin[/B] of=/dev/block/platform/msm_sdcc.1/by-name/aboot

neverdies said:
Are you sure that your aboot.bin file is in /storage/external_SD?
You can put the aboot.bin in your internal memory instead, or anywhere else, just change command according to your aboot.bin file location.
Exemple if you put your aboot.bin file in /storage/internal_SD run the following command:
Code:
su
dd if=[B]/storage/internal_SD/aboot.bin[/B] of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Click to expand...
Click to collapse
finally , it work ... aboot.bin were on external_sd ..but I dont know why the first time it didnt work ... I tryed again and it worked
flashed rom and everything now works ... thnxxx for help me solving the problem :good:

Can't get out of Fastboot.

"Cyanogendmod.Org / Install CM for z3c / Unlock Your Xperia Z3 Compact" <--- That's the URL somehow.
Followed this instruction. Got myself the 12.1 .zip and .img.
I get error installaing the .zip and the .img isn't even an option:
The old rom is infinitly loading in that blue/purple wave line.
I then turn the phone off by holding down the power button until the phone restarts.
My history:
>Pressing up and down on the button rockers.
>Cyanogen Recovery starts.
>I choose "Wipe data/factory reset".
>I choose "Apply update".
(Apply from ADB doesn't work as it seems as ADB has no access for USB debugging. That's why install it from an external SD)
>Install "cm-12.1-20160918-NIGHTLY-z3c.zip" or its copy that I named "update.zip".
Error message:
[CAN'T POST PICTURE BECAUSE XDA HAS VERY FUNNY MEME RULES XDDD]
Private message maybe...? Can I send you guys URL pics via PM?
How can I get out of this loop?

If you want to go back to stock, use flashtool and flash whatever version you want (FTF method), I had an issue with flashing CM too, it said this is for aries but this device is z3c etc. Is this your problem?

marshalpear said:
If you want to go back to stock, use flashtool and flash whatever version you want (FTF method), I had an issue with flashing CM too, it said this is for aries but this device is z3c etc. Is this your problem?
Click to expand...
Click to collapse
I definitly want CyanogenMod 12.1 on my Z3C. Is it still possible?
I hope you can decypher the URL h t t p : / / t i n y u r l . c o m / j 6 4 u 8 u a

Few things you can do:
1- Download the ROM again, might be corrupted download.
2- Flash Lollipop FTF(not necessary), Flash TWRP recovery, boot into recovery, (If it asks, swipe to allow modifications to system), wipe everything (system,cache,dalvik,data), flash the ROM through TWRP recovery.
3- If it gives the error that I talked about in my first message, let me know.

marshalpear said:
Few things you can do:
1- Download the ROM again, might be corrupted download.
2- Flash Lollipop FTF(not necessary), Flash TWRP recovery, boot into recovery, (If it asks, swipe to allow modifications to system), wipe everything (system,cache,dalvik,data), flash the ROM through TWRP recovery.
3- If it gives the error that I talked about in my first message, let me know.
Click to expand...
Click to collapse
I tried #1 but I'm already stuck with the "SONY XPERIA" blackscreen at the very beginning when booting the smartphone. I suppose it's because of the failed installation and the not choosing of "Wipe clean/factory reset".
I hope that still doesn't count as bricking. I let the accumulator run dry and reload the battery and try to get into the Cyanogenmod Recovery again. Right now nothing is possible. =/
I hope that doesn't count as bricking. If so: These special OTG USB thingies fix a lot I heard, should I get myself one?

SYLVER SECOND said:
I tried #1 but I'm already stuck with the "SONY XPERIA" blackscreen at the very beginning when booting the smartphone. I suppose it's because of the failed installation and the not choosing of "Wipe clean/factory reset".
I hope that still doesn't count as bricking. I let the accumulator run dry and reload the battery and try to get into the Cyanogenmod Recovery again. Right now nothing is possible. =/
I hope that doesn't count as bricking. If so: These special OTG USB thingies fix a lot I heard, should I get myself one?
Click to expand...
Click to collapse
If you are on CM recovery, then there is the problem. AFAIK you can't flash anything through that, so you have to push TWRP on your device using fastboot and then flash AOSP/CM rom you want.

SYLVER SECOND said:
I tried #1 but I'm already stuck with the "SONY XPERIA" blackscreen at the very beginning when booting the smartphone. I suppose it's because of the failed installation and the not choosing of "Wipe clean/factory reset".
I hope that still doesn't count as bricking. I let the accumulator run dry and reload the battery and try to get into the Cyanogenmod Recovery again. Right now nothing is possible. =/
I hope that doesn't count as bricking. If so: These special OTG USB thingies fix a lot I heard, should I get myself one?
Click to expand...
Click to collapse
That's called a soft-brick. You should install the ADB drivers for your phone on your PC and then download TWRP for your phone (.img file) and rename the TWRP you downloaded to recovery.img .
You should put the recovery.img into the folder where your ADB drivers are installed, then Shift + RClick on that folder then select Open Command Window Here. Connect your phone in fastboot mode to your PC (Keep Vol. Up button then plug in your device). Type the following commands:
fastboot flash boot recovery.img
fastboot reboot
If you've done it all correctly, your phone should boot into TWRP recovery. From there you should go to wipe-advanced wipe and wipe your Cache,Dalvik Cache, System, Boot. DO NOT REBOOT NOW. You should go back to main menu and choose install, then choose the ROM you want to install. It should flash it if you don't have a corrupted file. After flashing, you can safely reboot your phone, don't forget to flash GApps if you want Google features on your Cyanogen, hope I helped!

More info about my error:
h t t p : / / t i n y u r l . c o m / z b e v y u 2
Each version of step #3 doesn't work. Still trying to figure out how to get TWRP...

marshalpear said:
That's called a soft-brick. You should install the ADB drivers for your phone on your PC and then download TWRP for your phone (.img file) and rename the TWRP you downloaded to recovery.img .
You should put the recovery.img into the folder where your ADB drivers are installed, then Shift + RClick on that folder then select Open Command Window Here. Connect your phone in fastboot mode to your PC (Keep Vol. Up button then plug in your device). Type the following commands:
fastboot flash boot recovery.img
fastboot reboot
If you've done it all correctly, your phone should boot into TWRP recovery. From there you should go to wipe-advanced wipe and wipe your Cache,Dalvik Cache, System, Boot. DO NOT REBOOT NOW. You should go back to main menu and choose install, then choose the ROM you want to install. It should flash it if you don't have a corrupted file. After flashing, you can safely reboot your phone, don't forget to flash GApps if you want Google features on your Cyanogen, hope I helped!
Click to expand...
Click to collapse
K, 90% of this works. I got the TWRP "app" and I cleaned the cache and all that, but I had to reboot. You see:
To transfer new media I need to remove my external SD from the z3c to my old LG. The LG is connected with my PC and is therefore a kind of card-reader. I tried 2 different nightly thingies.
I still get extraction errors, see:
h t t p : / / t i n y u r l . c o m / h j j d 4 o b
I downloaded 2 different nightlies 6 times already. I dunno. Somethings off here.
Also: For what is the recovery.img? Should I install it afterwards?
I have to restart the phone in order to replug the SD card and get recognigzed by the TWRP.
I did everything from this:
http://forum.xda-developers.com/showthread.php?t=2522762
Because of Error 7.
Now I get Error 6.....

SYLVER SECOND said:
K, 90% of this works. I got the TWRP "app" and I cleaned the cache and all that, but I had to reboot. You see:
To transfer new media I need to remove my external SD from the z3c to my old LG. The LG is connected with my PC and is therefore a kind of card-reader. I tried 2 different nightly thingies.
I still get extraction errors, see:
h t t p : / / t i n y u r l . c o m / h j j d 4 o b
I downloaded 2 different nightlies 6 times already. I dunno. Somethings off here.
Also: For what is the recovery.img? Should I install it afterwards?
I have to restart the phone in order to replug the SD card and get recognigzed by the TWRP.
I did everything from this:
http://forum.xda-developers.com/showthread.php?t=2522762
Because of Error 7.
Now I get Error 6.....
Click to expand...
Click to collapse
OK, your problem is that you messed up your system, so wiping it is not gonna solve this issue. You need to download a stock firmware file (an FTF file) and flash it through Flashtool, because your device name seems to be "." which is why you were getting "error 7". As for the recovery.img, you will use it to flash TWRP recovery on your phone. TWRP app doesn't work correctly if you don't flash it to your recovery partition so do as follows:
1- Download Flashtool, install the drivers of your device for Flashtool (you can search it on xda forums), download an FTF file, any of them should do, but as you will install CM 12.1, I recommend a Lollipop FTF.
2- Flash the firmware through Flashtool. This will turn your phone into a stock one. Unlock your bootloader if you haven't already, which I believe you have.
3- Flash the TWRP recovery through fastboot (follow my earlier instructions)
4- After you open TWRP recovery do the wipes, note that you can still connect your phone to your computer for file transfers in TWRP Recovery.
5- Install the CM zip file through recovery
IF YOU GET ERROR 7 SAYING :this package is for device: D5803, D5833, z3c; this device is aries.
7- Open the CM 12.1 zip file on your computer and proceed to META-INF/com/google/android directory.
8- In that folder you should see "updater-script", extract it to somewhere and open it with Notepad.
9- Once you open it press Ctrl + H to change some of the lines.
10- Write "D5833" without the quotation marks in the first space and write "aries" without the quotation marks into the second space and click replace all.
(This will change all "D5833" to "aries" in the file therefore making it usable for your device) Save the file and put it into the directory of where you found it, replace it with the original.
11- Now put the edited .zip file into your phone storage, and flash it through recovery. It should work. :good:

marshalpear said:
3- Flash the TWRP recovery through fastboot (follow my earlier instructions)
Click to expand...
Click to collapse
I think he shouldn't flash TWRP on boot partition, as you wrote. That might cause further issues. I am flashing my recovery through fastboot without problems using next command:
fastboot flash recovery recovery.img

Cirra92 said:
I think he shouldn't flash TWRP on boot partition, as you wrote. That might cause further issues. I am flashing my recovery through fastboot without problems using next command:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
It won't matter. Because when he flashes the CM, it'll flash the CM Recovery along with it.

marshalpear said:
It won't matter. Because when he flashes the CM, it'll flash the CM Recovery along with it.
Click to expand...
Click to collapse
Yea I know, but before that, he needs to have a working TWRP on right partition to be able to even flash any rom.

Cirra92 said:
Yea I know, but before that, he needs to have a working TWRP on right partition to be able to even flash any rom.
Click to expand...
Click to collapse
That's why I wrote those steps for him/her to follow. If you flash TWRP to boot partition, when you boot the phone, it will go straight into TWRP. If you flash it to recovery partition, you'll have to boot it manually.

marshalpear said:
That's why I wrote those steps for him/her to follow. If you flash TWRP to boot partition, when you boot the phone, it will go straight into TWRP. If you flash it to recovery partition, you'll have to boot it manually.
Click to expand...
Click to collapse
Logical step, didn't think about it that way, I assumed OP knew how to enter recovery

"1- Download Flashtool, install the drivers of your device for Flashtool (you can search it on xda forums), download an FTF file, any of them should do, but as you will install CM 12.1, I recommend a Lollipop FTF.
2- Flash the firmware through Flashtool. This will turn your phone into a stock one. Unlock your bootloader if you haven't already, which I believe you have.
3- Flash the TWRP recovery through fastboot (follow my earlier instructions)
4- After you open TWRP recovery do the wipes, note that you can still connect your phone to your computer for file transfers in TWRP Recovery.
5- Install the CM zip file through recovery
IF YOU GET ERROR 7 SAYING :this package is for device: D5803, D5833, z3c; this device is aries.
7- Open the CM 12.1 zip file on your computer and proceed to META-INF/com/google/android directory.
8- In that folder you should see "updater-script", extract it to somewhere and open it with Notepad.
9- Once you open it press Ctrl + H to change some of the lines.
10- Write "D5833" without the quotation marks in the first space and write "aries" without the quotation marks into the second space and click replace all.
(This will change all "D5833" to "aries" in the file therefore making it usable for your device) Save the file and put it into the directory of where you found it, replace it with the original.
11- Now put the edited .zip file into your phone storage, and flash it through recovery. It should work."
K, so I guess I'm finished with #1 and #2. Sorry, had a ****-ton of chores to do. Before I progress, I wanted to send you guys
this pic:
https://img3.picload.org/image/rdricord/unbenannt.png
Is the root access necessary, or can I progress?
That's the sites I've used, if anybody wonders why something is the way it is right now:
http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
http://forum.xda-developers.com/showpost.php?p=66275965&postcount=2029
http://forum.xda-developers.com/showpost.php?p=60001557&postcount=829
Von "Sony Mobile Flasher by Androxyde":
"23/023/2016 22:23:52 - INFO - Root access denied
23/024/2016 22:24:07 - ERROR - Illegal key size or default parameters
23/024/2016 22:24:12 - ERROR - Illegal key size or default parameters
23/024/2016 22:24:13 - WARN - Please check your Phone and 'ALLOW' Superuseraccess!
23/024/2016 22:24:14 - INFO - Root access denied"

FlashTool says the firmware has been flashed so I don't understand what are you trying to do after that? After flashing the FTF file you should flash TWRP through "FASTBOOT". Then follow the instructions.

K, did everything you said. Read everything five-times. Replaced "D5833" to "aries" and all that stuff. Still getting ERROR 7.
The phone is still in TWRP Recovery from FASTBOOT / BOOTLOAD because I "constantly" charge it to stay in recovery. If I had found this Mount option earlier... kinda feel stupid for that. So I still get ERROR 7. I copied the modified .zip to internal storage and SD card to see if I get the same error twice. And yeah.
Exact error message in red letters:
"Updater process ended with ERROR: 7
Error installing zip file ' /external-sd/cm-12.1-20160918-NIGHTLY-z3c.zip'
Updating partition details...
... done"
So I forethought and cleaned the cache and need somewhat new instructions.
Also:
I suppose with "Advanced Wipe" and your instructions you meant this points, right?:
http://tinyurl.com/jc5rv3a

SYLVER SECOND said:
K, did everything you said. Read everything five-times. Replaced "D5833" to "aries" and all that stuff. Still getting ERROR 7.
The phone is still in TWRP Recovery from FASTBOOT / BOOTLOAD because I "constantly" charge it to stay in recovery. If I had found this Mount option earlier... kinda feel stupid for that. So I still get ERROR 7. I copied the modified .zip to internal storage and SD card to see if I get the same error twice. And yeah.
Exact error message in red letters:
"Updater process ended with ERROR: 7
Error installing zip file ' /external-sd/cm-12.1-20160918-NIGHTLY-z3c.zip'
Updating partition details...
... done"
So I forethought and cleaned the cache and need somewhat new instructions.
Also:
I suppose with "Advanced Wipe" and your instructions you meant this points, right?:
http://tinyurl.com/jc5rv3a
Click to expand...
Click to collapse
OK, so try flashing TWRP to recovery partition to get you out of TWRP after you boot by writing these commands in the ADB:,
fastboot flash recovery recovery.img
fastboot reboot recovery
This will flash the TWRP to recovery partition and will boot you into TWRP. As you do this you won't have a go at the recovery again but for this time. You can reach the TWRP by pressing the Vol. Down button when the phone vibrates at the boot. Also if you want to force shutdown your phone you can use Vol. Up + Power Button combination for a few secs.

marshalpear said:
OK, so try flashing TWRP to recovery partition to get you out of TWRP after you boot by writing these commands in the ADB:,
fastboot flash recovery recovery.img
fastboot reboot recovery
This will flash the TWRP to recovery partition and will boot you into TWRP. As you do this you won't have a go at the recovery again but for this time. You can reach the TWRP by pressing the Vol. Down button when the phone vibrates at the boot. Also if you want to force shutdown your phone you can use Vol. Up + Power Button combination for a few secs.
Click to expand...
Click to collapse
K, cool feature. Got it all set up now, but back to the main subject:
Is it even possible to install CyanogenMod 12.1 on Sony Z3C?