Develop Bugs

Cant't flash any roms

First day I got the phone I rooted and installed clockwork mod. I downloaded and installed cm9 but now I can't flash any other roms. Every time I try and flash a new one it boots to log screen then stays on a blank black screen. Any help would be appreciated as i would like to try something else out. Also I followed the flashing instructions of each rom and even tried formatting system with no luck.

just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.

scott0 said:
just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.
Click to expand...
Click to collapse
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.

lendmeyoureers said:
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.
Click to expand...
Click to collapse
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?

drumist said:
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?
Click to expand...
Click to collapse
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.

lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.

scott0 said:
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.
Click to expand...
Click to collapse
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download

lendmeyoureers said:
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download
Click to expand...
Click to collapse
i didn't say your's was bricked, i said i bricked mine doing what you did.
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
i'm not sure what post 29 is, but i've done machz's unbricking 2x succesfully, it's the 1st post in his thread.
either way, i know how frustrating it can be, i hope you get it all sorted out.

lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
scott0 said:
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
Click to expand...
Click to collapse
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).

drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
this is good advices. but i never was able to sort out how to use terminal emulator, ugh. i kept trying to run commands from within the phone that were ....hekk can't recall exactly. it was frustrating.
but the best advice i think is the nandroid b/u of the original ROM. although nothing necc. wrong with doing a debrick, only takes <30 minutes, as long as the debricking Gods are all in a good mood at that particular moment.

If you get hono's GB rom, then flash HONO's GB kernel, you should be able to boot into GB no problem

drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.

lendmeyoureers said:
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.
Click to expand...
Click to collapse
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)

drumist said:
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)
Click to expand...
Click to collapse
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...

hah, yeah, that command reminded me of what i was doing wrong, i was mistakenly trying to run shell commands from the emulator.

lendmeyoureers said:
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...
Click to expand...
Click to collapse
Awesome. Now make a Nandroid backup BEFORE you install another ROM, so you have an easier way to revert to your current boot image. That way you can install CM9 again later if you want without worrying about going through this again if you want to install something else.

B512 or B513

Hey as the title shows I want to know which firmware is the better one, to know I have TWRP installed so actually the better option would be the B513 repack for TWRP because otherwise I must install stock recovery and so on right? Is there a big difference between these two version? And which would you recommend?
Thanks in advance.

Which rom do you have installed currently?

digijedi007 said:
Which rom do you have installed currently?
Click to expand...
Click to collapse
Paranoid Android 4.45 the newest build.

Well in my opinion the actual stock software is better in this case than the custom ones, since in the b5x roms there are little to none bugs, I have used b510 now since it came out and i don't see the need to update again,everything works as it should (except the gps but then the gps in the p6 is horrible)so i'd say if you already have one of them use it, I actually prefer the stock based rom's because if something were to go seriously wrong I would still be able to send it in for repairs, and in my expierience the stock huawei roms work better than repacks, so my advice go for 132>B5x whatever you want they are all mostly the same except for very minor tweaks, easiest is b510, if you want some quick pointer's and a few must have mods try http://forum.xda-developers.com/showpost.php?p=54717666&postcount=8

Okay thanks man

Hey have you changed your rom yet? I would recommend you try this http://forum.xda-developers.com/ascend-p6/development/diy-rom-b510-based-add-want-t2843511, you can replace b510 with b511,b512,b513 if you wanted to

No not yet I am backing up my data right now, my plan was now to directly install B512 since its a full update.app and not a OTA like in the other firmwares. So now I install stock B510 recovery and boot.img and go straight to B512 and not install B132 before that should theoreticly work, or?

As far as i know you have to install b132 first otherwise it won't work(i think the b132 contains files that the b510,b512,b513 roms need(they are probly ota update files even if they look like normal firmware files) [note] did you download a repackged one? they might work like that.
---------- Post added at 12:15 PM ---------- Previous post was at 12:13 PM ----------
also fiy you could use titanium backup to make the process much much easier(hint of warning though don't restore alarms,bluetooth,wifi stuff between different android versions it will seriously mess up your phone)for call logs and messages use call logs backup & restore and for sms use sms backup and restore

http://www.huaweiblog.de/huawei/huawei-ascend-p6-firmwareupdate-b512-offiziell/ Here when you use google translator and scroll down they have the full firmware which can be flashed over all versions. For me that worked everytime with B506 and B507 which was kinda the same procedure. So I will try and report back if he doesn't update I will install B132 and so on

ok let me know what happens, i did see them mentioning the b132 firmware there near the bottom so maybe it's the same as the one's one the forum

So okay it worked without Problems I just installed boot.img and recovery.img from B510 and made a force update. Worked perfectly. Maybe you can add this to your thread.

so you extracted the boot .igm file and the recovery.img from the b510 and copied the 510's update.app file to the interal memory> flashed boot and rec > then flashed b510 > Is that how you did it? Keep in mind I need to keep the steps reasonably simple so that newbs to android(flashing etc) can also do it.

Okay
1. Starting with Paranoid Android, OMNI or any other AOSP-based ROM.
2. Backing up all data with Titanium backup and copy everything you need from your internal storage. ATTENTION: The internal storage will be wiped while flashing, so the backup MUST be on your SD-Card.
3. Copy dload folder to SD-Card or internal storage. (there should be no differnce)
4. Boot to TWRP and make a backup if something goes wrong.
5. In TWRP wipe everything except internal and external storage.
6. In TWRP choose reboot to bootloader. Confirm that no OS is installed and don't install SuperSU.
7. Plug your phone in your PC and open a CMD.
8. Download B510 recovery.img and boot.img from this thread http://forum.xda-developers.com/showthread.php?p=51718316 .
9. Follow the instructions by @surdu_petru. IMPORTANT: When the installation is finished and the phone reboots hold all three buttons and unplug the USB cable. (I needed more than one time to get it because the first time it was frozen in recovery. Just hold all three buttons till it reboots again.
10. You are finished!! The first boots takes some time no need to panic.
Additional:
Reinstall TWRP and flash SuperSU for Root. Than you can restore your backup you made in the second step.
Here you go. you can copy this in your post if you want.

Just one issue in your guide in step 9 you linked to his profile not the post

Oh yeah can you search for the right link I don't have time right now.
Edit: edited my first post.

Did you saw my correction?

Empty phone storage for HTC One M8

Hi all, first of all...sorry if I did not provide enough information...I am first time doing this whole flashing thing on my own...
My phone's CID number: HTC_044
Version main: EMPTY <<< is this normal?
Version bootloader: 3.19.0.0000
Using stock ROM i suppose...didn't flash any other third party's ROM before
My phone was rooted for sometime and lately I want to upgrade my phone to Lollipop...I thought I need to unroot first and therefore I found solution online...everything went fine and I was able to upgrade to Lollipop using the official way (update through phone).
However, later on I was trying to root it back...tried to download SU from Google Play and it just can't install properly...I then thought have to re-do everything again (restore back to basic OS version).
Then this second time I do, I wiped the data, cache, and dalvik cache (I did not do this for the first attempt). Then things start to go haywire...my Android files are not going into the internal storage...instead...it is being installed in my external SD card.
I then tried numerous time flasing back to basic OS version (Kit Kat 4.4.2) and update to Lollipop again...still no luck...
Until yesterday I thought everything worked out fine...and I tried installing Facebook...it says cannot install...
Can anyone help me on this? I also not quite sure what went wrong...hope you guys can enlighten me...will try to provide as much information as possible.

jkidz91 said:
However, later on I was trying to root it back...tried to download SU from Google Play and it just can't install properly...I then thought have to re-do everything again (restore back to basic OS version).
Click to expand...
Click to collapse
That is not the proper way to root. Installing SU from the store does not root the phone. It just install the app, not the SU binary.
To root, unlock the bootloader, install TWRP and flash the proper version SuperSU zip in TWRP.
---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------
jkidz91 said:
Then this second time I do, I wiped the data, cache, and dalvik cache (I did not do this for the first attempt). Then things start to go haywire...my Android files are not going into the internal storage...instead...it is being installed in my external SD card.
I then tried numerous time flasing back to basic OS version (Kit Kat 4.4.2) and update to Lollipop again...still no luck...
Until yesterday I thought everything worked out fine...and I tried installing Facebook...it says cannot install...
Click to expand...
Click to collapse
Its not clear to me what you did, but it might be best to RUU to full stock using the link I provided in the other thread you posted to.

redpoint73 said:
That is not the proper way to root. Installing SU from the store does not root the phone. It just install the app, not the SU binary.
To root, unlock the bootloader, install TWRP and flash the proper version SuperSU zip in TWRP.
---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------
Its not clear to me what you did, but it might be best to RUU to full stock using the link I provided in the other thread you posted to.
Click to expand...
Click to collapse
Noted bro! You r really helpful!

[RECOVERY][3.1.1-0] TWRP for hi6250 Devices [METICULUS]

No more development from me.
XDA:DevDB Information
TWRP for the Hauwei P10 Lite, Tool/Utility for the Huawei P10 Lite
Contributors
Meticulus
Source Code: http://github.com/Meticulus
Version Information
Status: Testing
Created 2017-12-05
Last Updated 2018-01-18

Good work!!

You guys ready for custom ROMs?
This is my WAS-LX3 Running my Pure AOSP for HI6250 Devices! Installation is a bit tricky but I'll fix that up soon!

Great work!
Just tested it on my P10 lite(was-lx1c432), and it works.

Thanks for your work. I haven't tried it yet. I'm waiting for your custom Rom.
With Devcheck system info (search in playstore) I saw that my device is compatible.

Hi, I flashed it on my WAS-LX1C432 but it freezes at the screen where it asks about allowing modifications to the system partition. The build from the other thread works though, apart from decryption.

Cannot wait to get aosp good work!!

Ra2rd said:
Cannot wait to get aosp good work!!
Click to expand...
Click to collapse
Stock decryption not working here either
I have not found any easy way to get back to stock...

When i tried to flash the zip with the other TWRP build, i got error 7 : This build is for Washington, not for Warsaw.
So, i flashed the img with fastboot and it works.
Also after allowing modifications at first boot of TWRP, i don't get that msg anymore.
With the other build i had to allow it everytime i booted TWRP.
I have WAS-LX1AC432

waaagh313ph4n7 said:
Hi, I flashed it on my WAS-LX1C432 but it freezes at the screen where it asks about allowing modifications to the system partition. The build from the other thread works though, apart from decryption.
Click to expand...
Click to collapse
Touch unresponssive happened to also. I've just rebooted into recovery again. Solved.
This build works like a charm
Encryption of data will be always a problem on kirin devices ...

[email protected]@[email protected] said:
When i tried to flash the zip with the other TWRP build, i got error 7 : This build is for Washington, not for Warsaw.
So, i flashed the img with fastboot and it works.
Also after allowing modifications at first boot of TWRP, i don't get that msg anymore.
With the other build i had to allow it everytime i booted TWRP.
I have WAS-LX1AC432
Click to expand...
Click to collapse
Washington? Which device is Washington?... Other twrp is port from Washington?

WAS-TL10C01B220 cmcc/cn is work.
Tnx

Meticulus said:
Washington? Which device is Washington?... Other twrp is port from Washington?
Click to expand...
Click to collapse
I forgot to make a pic. That's what i remember. Maybe I saw or did something wrong.
Edit :
Found this with Google
https://www.frequencycheck.com/models/Az88E/huawei-p10-lite-dual-sim-lte-was-lx3-huawei-washington

[email protected]@[email protected] said:
I forgot to make a pic. That's what i remember. Maybe I saw or did something wrong.
Edit :
Found this with Google
https://www.frequencycheck.com/models/Az88E/huawei-p10-lite-dual-sim-lte-was-lx3-huawei-washington
Click to expand...
Click to collapse
Oh geez I didn't know about Washington. I thought all P10 Lite was Warsaw...:silly:

Meticulus said:
Oh geez I didn't know about Washington. I thought all P10 Lite was Warsaw...:silly:
Click to expand...
Click to collapse
Me too.
With your twrp build I tried to flash the recovery again. The zip file. And this time I didn't get any errors.
How's the progress on your rom?
I would be happy to test it.

[email protected]@[email protected] said:
Me too.
With your twrp build I tried to flash the recovery again. The zip file. And this time I didn't get any errors.
How's the progress on your rom?
I would be happy to test it.
Click to expand...
Click to collapse
The ROM is pretty good. I'm just concerned about ppl being able to go back to stock. Because the ROM is not a daily driver yet..,
Rear cam video capture not working.
Little laggies happen during ui animation.
Edit: If you are confident you can get back to stock if you need to pm me.

Any Other Testers?
If there is anyone else who is confident they can get back to stock via the 'dload' method and would like to test AOSP for the P10 Lite, pm me.

Worked for me. I needed to do a full wipe in TWRP first. ( i wiped data too, dunno if it was needed)
Flashed open gapps 7.1 pico.
There is no browser or file manager included in the rom.
So after setting up playstore, download a file manager if you need to access your ext sdcard.
Flashed supersu in twrp and have root too.
---------- Post added at 06:42 PM ---------- Previous post was at 06:15 PM ----------
Restored my apps and data with titanium Backup.
Working fine.
Maybe create a new topic for this ROM?

I made a TWRP backup. Selected everything except /cache.
With 3 button dload method i was able to go back to stock rom.
Unlocked bootloader again, flashed TWRP and then tried to restore the backup.
Got a 255 error. So i did a full wipe and formatted /data.
After this succesfully restored the backup and phone booted normally with everything intact.
So, internal storage is not encrypted in TWRP.
Rom is pretty smooth. Didn't encouter any issues. Except the known bugs.
Finger print is working, GPS too.
Didn't test NFC or dual sim.
Will use this rom and see how it goes.
edit :
Made a "tap and pay" payment in the supermarket. So NFC is working.

[email protected]@[email protected] said:
Worked for me. I needed to do a full wipe in TWRP first. ( i wiped data too, dunno if it was needed)
Flashed open gapps 7.1 pico.
There is no browser or file manager included in the rom.
So after setting up playstore, download a file manager if you need to access your ext sdcard.
Flashed supersu in twrp and have root too.
---------- Post added at 06:42 PM ---------- Previous post was at 06:15 PM ----------
Restored my apps and data with titanium Backup.
Working fine.
Maybe create a new topic for this ROM?
Click to expand...
Click to collapse
I'll create new topic for this 2morrow...:highfive:

How to install march update with unlocked bootloader and rooted phone?

Hey guys,
I'm still trying to install the march update.
I disabled magisk and tryed to install the march update as usual.
I followed this guide and this worked for the february update.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
WIth the march update i get an error during the update.
After that my phone stucked at the bootloader and i couldn't boot anymore.
Luckily i fixed this with patching the old boot.img.
So is there any work around to get the new update while keeping my data and root?

Install magisk again and backup all your apps with titanium backup. Make sure you save those backups to an external spot.
Flash factory image with miflash - make sure you uncheck clean and lock! and update to current then install magisk and restore data with titanium.
It really is less frustrating that way.
I did this recently and gave me a chance to try paranoid Android. That was about aweek ago and have been using it since. Very few issues, and for my use I think it's better than stock.
---------- Post added at 09:08 PM ]
As long as you keep your bootloader unlocked, you can recover from anything