Develop Bugs

[Q] Repair platform.xml?

Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Any suggestions on how I can get access back to my device so I can repair/replace the platform.xml file and restore functionality to my phone?
Thank you very much!

Deozaan said:
Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Click to expand...
Click to collapse
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery

enryea123 said:
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
Click to expand...
Click to collapse
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).

Deozaan said:
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Click to expand...
Click to collapse
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.

enryea123 said:
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
Click to expand...
Click to collapse
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.

Deozaan said:
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Click to expand...
Click to collapse
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
having a backup of the sdcard is always a good idea :good:, i have 2 backups of mysdcard on 2 different hard drives of my computer and the pictures i take with the camera are automatically uploaded on my dropbox .

enryea123 said:
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
Click to expand...
Click to collapse
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.

Deozaan said:
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Click to expand...
Click to collapse
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip

enryea123 said:
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip
Click to expand...
Click to collapse
I was in CWM Recovery. I was using the zip file that I extracted from the link you gave me for Google's stock ROMs (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!

enryea123 said:
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
Click to expand...
Click to collapse
Try this one
Deozaan said:
I was in CWM Recovery. I was using the zip file that I extracted from here the link you gave me (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
Click to expand...
Click to collapse
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.

enryea123 said:
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
Click to expand...
Click to collapse
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.

I got it working again. The ROM you gave me failed signature verification in CWM Recovery, but I told it to install anyway and it worked. Thank you.
The problem I was having with Gmail not syncing was that I used Titanium Backup to restore my data, but because all the data from my "SD card" got erased, Titanium Backup itself lots its settings, so my Device ID was different. I guess Gmail relies on the device ID for syncing.
Thank you so much for your help! I learned a lot from the experience.

Glad i helped you. well this is one of the reasons why i don't restore data with titanium (especially system data).
and by the way:
Deozaan said:
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
Click to expand...
Click to collapse
To fully reset and install a clean rom using fastboot you have to extract the bootloader-blabla.img and radio-blabla.img files from the tar.gz archive and then extract the 4 .img files inside the zip (that is inside the tar.gz) and flash this 6 .img files connetting your phone in bootloader mode to your computer and using fastboot in terminal (in fact this procedure reinstall the recovery too).

Recovery Bootloop Help!!

Flashed Philz touch CWM. Flashed BAM ROM. IT ran fine for a day and a half. Flashed the custom kernel, and immediately started getting recovery bootloops. Instead of the boot message saying "Secure Booting Error Causeevice Unlock, So boot Success." It said, " Secure Booting Error Cause:Certification Verify" then I rebooted, and it just went to recovery. I reflashed everything minus the custom kernel, and it gave me the regular message, but it won't actually boot. Someone PLEASE help!!!

Might have to go back to stock.. I guess I was pointing everyone to the wrong recovery when I said look in Madmack's CM thread for his TWRP.
Use this one: https://db.tt/bQeSgkEJ
It says E986 but works perfectly.
Sent from my SlimKat LG-E980

Neroga said:
Might have to go back to stock.. I guess I was pointing everyone to the wrong recovery when I said look in Madmack's CM thread for his TWRP.
Use this one: https://db.tt/bQeSgkEJ
It says E986 but works perfectly.
Sent from my SlimKat LG-E980
Click to expand...
Click to collapse
Perfectly for some CM based ROMS but not for 4.1.2+
Sent from my LG-E980 using Tapatalk

Neroga said:
Might have to go back to stock.. I guess I was pointing everyone to the wrong recovery when I said look in Madmack's CM thread for his TWRP.
Use this one: https://db.tt/bQeSgkEJ
It says E986 but works perfectly.
Sent from my SlimKat LG-E980
Click to expand...
Click to collapse
Do I have to use the FlashTools? Cuz this won't end. I've wiped everything multiple times, reflashed multiple times, I even factory reset it through hardware keys. Does anyone have an idea before i return to complete stock? It's greatly appreciated

Nigglenuts said:
Do I have to use the FlashTools? Cuz this won't end. I've wiped everything multiple times, reflashed multiple times, I even factory reset it through hardware keys. Does anyone have an idea before i return to complete stock? It's greatly appreciated
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=50242586&postcount=83

So do I need the LG drivers? Because I can't find them anywhere... I'm unsure how to install aroma file manager.

i cant even get my computer to see my sdcard. I got the drivers installed, have the aromafm.zip on my desktop. when i go into device manager, it doesnt show my phones storage. i am so confused... i need expert help

Does PhilzTouch have adb? If so, you could just push that to your device through your PC.
adb push filename /sdcard/filename
Sent from my SlimKat LG-E980

Neroga said:
Does PhilzTouch have adb? If so, you could just push that to your device through your PC.
adb push filename /sdcard/filename
Sent from my SlimKat LG-E980
Click to expand...
Click to collapse
I cant find it. But now my cpu wont recognize my phone. it says that the drivers weren't installed even though ive installed them multiple times. Ill put the phone in download mode, itll see the phone, then i boot back to recovery, and it no longer recognizes

Solutions...
Nigglenuts said:
So do I need the LG drivers? Because I can't find them anywhere... I'm unsure how to install aroma file manager.
Click to expand...
Click to collapse
Here are the solutions:
1. Download the aroma file manager here
2. Rename the file to aromafm.zip
3. Put the aromafm.zip in "clockworkmod/aromafm/" in any of the storage volumes
4. In Philz touch recovery, tap the Aroma File Manager (it will open the aroma file manager automatically if you put it into the correct folder as stated above)
5. Open the terminal in the aroma file manager
6. Type this:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 count=1088
7. Reboot system
DONE!

mysteryinc said:
Here are the solutions:
1. Download the aroma file manager here
2. Rename the file to aromafm.zip
3. Put the aromafm.zip in "clockworkmod/aromafm/" in any of the storage volumes
4. In Philz touch recovery, tap the Aroma File Manager (it will open the aroma file manager automatically if you put it into the correct folder as stated above)
5. Open the terminal in the aroma file manager
6. Type this:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 count=1088
7. Reboot system
DONE!
Click to expand...
Click to collapse
How do I get my computer to see my phones storage? I got the drivers installed, it claims that they installed properly, but once I take it out of download mode, the device goes to unspecified in the "Devices & Printers." I know how to mount storage in recovery, but when i get to recovery, the computer no longer recognizes it....

Nigglenuts said:
How do I get my computer to see my phones storage? I got the drivers installed, it claims that they installed properly, but once I take it out of download mode, the device goes to unspecified in the "Devices & Printers." I know how to mount storage in recovery, but when i get to recovery, the computer no longer recognizes it....
Click to expand...
Click to collapse
no need for the computer to see the phone storage. you can put the aroma file manager either in your sdcard or usb storage, both should be readable when you use CWM to open aroma.

mysteryinc said:
Here are the solutions:
1. Download the aroma file manager here
2. Rename the file to aromafm.zip
3. Put the aromafm.zip in "clockworkmod/aromafm/" in any of the storage volumes
4. In Philz touch recovery, tap the Aroma File Manager (it will open the aroma file manager automatically if you put it into the correct folder as stated above)
5. Open the terminal in the aroma file manager
6. Type this:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 count=1088
7. Reboot system
DONE!
Click to expand...
Click to collapse
But how do i get my computer to actually recognize my phone? And get it to see my phones storage?

mysteryinc said:
no need for the computer to see the phone storage. you can put the aroma file manager either in your sdcard or usb storage, both should be readable when you use CWM to open aroma.
Click to expand...
Click to collapse
How do i do that???? I get 3 USB options, USB Modem, USB Composite Device, and USB Serial Port

Nigglenuts said:
But how do i get my computer to actually recognize my phone? And get it to see my phones storage?
Click to expand...
Click to collapse
why should your computer need to recognize your phone?
you can take out your microsd card & insert it into the memory card reader & transfer the aroma file thru the reader by using your PC or put the aroma file manager thru your usb / pendrive & then use usb otg & CWM will automatically mount the usb storage.

mysteryinc said:
why should your computer need to recognize your phone?
you can take out your microsd card & insert it into the memory card reader & transfer the aroma file thru the reader by using your PC or put the aroma file manager thru your usb / pendrive & then use usb otg & CWM will automatically mount the usb storage.
Click to expand...
Click to collapse
If a microSD was present, I would've done that, unfortunately, one is not. So how do i put the aromafm.zip through the USB? i was up til like 3:00 AM last night trying to set up ADB. But nothing seems to work. Thanx for the help man.

Nigglenuts said:
If a microSD was present, I would've done that, unfortunately, one is not. So how do i put the aromafm.zip through the USB? i was up til like 3:00 AM last night trying to set up ADB. But nothing seems to work. Thanx for the help man.
Click to expand...
Click to collapse
just plug in your usb to your pc & then transfer the file into it. after that plug in USB OTG cable (if you have one) to your phone & connect the pendrive, make sure you are in recovery mode.

mysteryinc said:
just plug in your usb to your pc & then transfer the file into it. after that plug in USB OTG cable (if you have one) to your phone & connect the pendrive, make sure you are in recovery mode.
Click to expand...
Click to collapse
i got a microSD. No otg cable though..... My grandma needs to get a card reader lol

Thank you guys so much for all your help. I got the beast fixed... I ended up using the ADB 15 Second Tool and it worked!
Sent from my ( Working Again) Optimus G Pro using xda app-developers app

Nigglenuts said:
Flashed Philz touch CWM. Flashed BAM ROM. IT ran fine for a day and a half. Flashed the custom kernel, and immediately started getting recovery bootloops. Instead of the boot message saying "Secure Booting Error Causeevice Unlock, So boot Success." It said, " Secure Booting Error Cause:Certification Verify" then I rebooted, and it just went to recovery. I reflashed everything minus the custom kernel, and it gave me the regular message, but it won't actually boot. Someone PLEASE help!!!
Click to expand...
Click to collapse
I posted a solution that requires the use of a microsd card....but you could've just gone and bought a cheap card reader to be able to use this method......but anyway this guide won't work if you don't have a microsd card.....I made this a while back to help someone else
http://forum.xda-developers.com/showthread.php?t=2619403
Sent from my LG-E980 using Tapatalk

[Q] Stuck in boot, need help

Hello,
I'm looking for help as I have exhausted all of my search on google and xda developers and the answer doesn't seem to be there. I'm afraid I might be unable to get out of this one.
I have a huawei ascend P6-U06 I bought it and it came with the international firmware, I had rooted it and flashed miui v5 into my phone, everything was fine but one thing, I was unable to use themer, so about 3 days ago I finally decided to flash omni rom.
I downloaded omni rom and installed CWM recovery and once into the system I selected the zip from my sd card and flashed it, only to find that the phone would not go pass the first screen (stuck in boot and could not be shutdown or anything)
Since I did not do a TWRP recovery (and I don't know how, I'm just a beginner) I was unable to do anything other than the "3 button method" so I looked and found that I could put the UPDATE.APP file on the dload folder and it should work, so I tried it and the UPDATE.APP firmware version is the B125, all good I think this was the Chinese version but it had English and other languages as well, but Chinese seemed to be the main one.
Anyways I had the phone back and it did an update, after the update everything was working fine, I deleted the dload file from the sd card, also I saw that the "system" or the phone itself created a dload file on the internal storage but then once I had themer on the phone I saw myself that I hated the emotion ui and in the first place that was the reason I had put miui into my phone, I still wanted to try omni rom and persistently I tried a second time.
Now this time since I already new that I could just do the dload thingy I thought (what could happen) so I tried again with CWM to flash the omni rom (the latest version) but it gave me an error saying something like the installation was aborted or something like that.
So I went back to having the phone stuck in boot, I put the B125 UPDATE.APP and created a dload folder on the sd card, but when doing the "3 button method" the system gave me an error, I tried downloading the B122 and the B132 and also the B510 but although I have put the UPDATE.APP on the dload folder it just doesn't do it's magic like it previously did.
Now I don't really have money to buy another phone, if I did I would just buy another one (I like the p7) but I don't so I need to fix this issue otherwise I don't have a phone.
Please help me, I'd appreciate if you can do your best explaining as I'm dumb in this matter, (just a beginner as said before) Also I'm attaching a picture of the error message being received when entering the system recovery through the "3 button method"
Thanks for all of your time, I DO appreciate your help and if you have any questions please just ask! I really need to fix this!

DanRioja said:
Hello,
I'm looking for help as I have exhausted all of my search on google and xda developers and the answer doesn't seem to be there. I'm afraid I might be unable to get out of this one.
I have a huawei ascend P6-U06 I bought it and it came with the international firmware, I had rooted it and flashed miui v5 into my phone, everything was fine but one thing, I was unable to use themer, so about 3 days ago I finally decided to flash omni rom.
I downloaded omni rom and installed CWM recovery and once into the system I selected the zip from my sd card and flashed it, only to find that the phone would not go pass the first screen (stuck in boot and could not be shutdown or anything)
Since I did not do a TWRP recovery (and I don't know how, I'm just a beginner) I was unable to do anything other than the "3 button method" so I looked and found that I could put the UPDATE.APP file on the dload folder and it should work, so I tried it and the UPDATE.APP firmware version is the B125, all good I think this was the Chinese version but it had English and other languages as well, but Chinese seemed to be the main one.
Anyways I had the phone back and it did an update, after the update everything was working fine, I deleted the dload file from the sd card, also I saw that the "system" or the phone itself created a dload file on the internal storage but then once I had themer on the phone I saw myself that I hated the emotion ui and in the first place that was the reason I had put miui into my phone, I still wanted to try omni rom and persistently I tried a second time.
Now this time since I already new that I could just do the dload thingy I thought (what could happen) so I tried again with CWM to flash the omni rom (the latest version) but it gave me an error saying something like the installation was aborted or something like that.
So I went back to having the phone stuck in boot, I put the B125 UPDATE.APP and created a dload folder on the sd card, but when doing the "3 button method" the system gave me an error, I tried downloading the B122 and the B132 and also the B510 but although I have put the UPDATE.APP on the dload folder it just doesn't do it's magic like it previously did.
Now I don't really have money to buy another phone, if I did I would just buy another one (I like the p7) but I don't so I need to fix this issue otherwise I don't have a phone.
Please help me, I'd appreciate if you can do your best explaining as I'm dumb in this matter, (just a beginner as said before) Also I'm attaching a picture of the error message being received when entering the system recovery through the "3 button method"
Thanks for all of your time, I DO appreciate your help and if you have any questions please just ask! I really need to fix this!
Click to expand...
Click to collapse
So first of all DON'T ever use CWM on our phone because its not really good to use! Always use TWRP.
Than second when you want to install a KK ROM like OMNI you have to update first via update.app to a KK firmware, then install TWRP and so on. This is all described in the first post in the OMNI thread.
Third and this is your problem now you have an modified build.prop in your ROM so the recovery will not update you have to push an stock unmodified build.prop via fastboot, that's the only method I think. How to push that with fastboot there you will find something on google.
Good luck

try this
DanRioja said:
Hello,
I'm looking for help as I have exhausted all of my search on google and xda developers and the answer doesn't seem to be there. I'm afraid I might be unable to get out of this one.
I have a huawei ascend P6-U06 I bought it and it came with the international firmware, I had rooted it and flashed miui v5 into my phone, everything was fine but one thing, I was unable to use themer, so about 3 days ago I finally decided to flash omni rom.
I downloaded omni rom and installed CWM recovery and once into the system I selected the zip from my sd card and flashed it, only to find that the phone would not go pass the first screen (stuck in boot and could not be shutdown or anything)
Since I did not do a TWRP recovery (and I don't know how, I'm just a beginner) I was unable to do anything other than the "3 button method" so I looked and found that I could put the UPDATE.APP file on the dload folder and it should work, so I tried it and the UPDATE.APP firmware version is the B125, all good I think this was the Chinese version but it had English and other languages as well, but Chinese seemed to be the main one.
Anyways I had the phone back and it did an update, after the update everything was working fine, I deleted the dload file from the sd card, also I saw that the "system" or the phone itself created a dload file on the internal storage but then once I had themer on the phone I saw myself that I hated the emotion ui and in the first place that was the reason I had put miui into my phone, I still wanted to try omni rom and persistently I tried a second time.
Now this time since I already new that I could just do the dload thingy I thought (what could happen) so I tried again with CWM to flash the omni rom (the latest version) but it gave me an error saying something like the installation was aborted or something like that.
So I went back to having the phone stuck in boot, I put the B125 UPDATE.APP and created a dload folder on the sd card, but when doing the "3 button method" the system gave me an error, I tried downloading the B122 and the B132 and also the B510 but although I have put the UPDATE.APP on the dload folder it just doesn't do it's magic like it previously did.
Now I don't really have money to buy another phone, if I did I would just buy another one (I like the p7) but I don't so I need to fix this issue otherwise I don't have a phone.
Please help me, I'd appreciate if you can do your best explaining as I'm dumb in this matter, (just a beginner as said before) Also I'm attaching a picture of the error message being received when entering the system recovery through the "3 button method"
Thanks for all of your time, I DO appreciate your help and if you have any questions please just ask! I really need to fix this!
Click to expand...
Click to collapse
hi there. try to boot with adb shell in fastboot mode.
if you have b111,125,132,118 etc you need twrp for jelly bean.
after that install twrp recovery and wipe system, data, cache, dalvik.
then reinstall stock recovery also via fastboot and then you can install update.app from dload.
if you want omni you have to update to official b510 because it repartitions your device, then flash omni via twrp.
don't use cwm again

adipaval said:
hi there. try to boot with adb shell in fastboot mode.
if you have b111,125,132,118 etc you need twrp for jelly bean.
after that install twrp recovery and wipe system, data, cache, dalvik.
then reinstall stock recovery also via fastboot and then you can install update.app from dload.
if you want omni you have to update to official b510 because it repartitions your device, then flash omni via twrp.
don't use cwm again
Click to expand...
Click to collapse
Hey thank you for the quick response, could you send me a link with the steps? as I said before I'm really just a beginner so I don't understand much, I mean I don't know what adb shell is, and how to enter the fastboot mode. I'd appreciate if you could help me with that!
Thanks

try this
sorry for the late response, i've been very busy.
you must have hisuite installed because you need the drivers.
so first you have to put your phone in download mode. you do this by starting your phone with vol down pressed. (it will remain on the ascend logo) and in windows you should see a quick removable device.
you need twrp recovery for jelly bean from here (the twrp2.6.x.x. IMG file ) http://forum.xda-developers.com/showthread.php?t=2534420
put the downloaded twrp2.6.3.3.img file in the folder which you'll extract from the attached zip of this post
in the fastboot folder shif+right click - start command windows here
type adb reboot bootloader - it will start the service then display error device not founde
type fastboot flash recovery "and the nameof the recovery ex. twrp2.6.3.3.img" - it should sai ok
safely remove device from windows and reboot your phone.
then you should be able to boot in twrp and clear system, data, cache, dalvik cache. this will let your phone without an operating system so either you install a custom jelly bean or put via twrp the stock recovery back (you cand find on the same page linked above) and then install stock jelly bean via dload folder.
P.S. from what I see in your screenshot, did you put an update.zip in hwouc folder on sdcard? hwouc is the folder where phone saves updates downloaded via ota then installs them from recovery.
are you sure you put update.APP in dload folder?
hope I helped

adipaval said:
sorry for the late response, i've been very busy.
you must have hisuite installed because you need the drivers.
so first you have to put your phone in download mode. you do this by starting your phone with vol down pressed. (it will remain on the ascend logo) and in windows you should see a quick removable device.
you need twrp recovery for jelly bean from here (the twrp2.6.x.x. IMG file ) http://forum.xda-developers.com/showthread.php?t=2534420
put the downloaded twrp2.6.3.3.img file in the folder which you'll extract from the attached zip of this post
in the fastboot folder shif+right click - start command windows here
type adb reboot bootloader - it will start the service then display error device not founde
type fastboot flash recovery "and the nameof the recovery ex. twrp2.6.3.3.img" - it should sai ok
safely remove device from windows and reboot your phone.
then you should be able to boot in twrp and clear system, data, cache, dalvik cache. this will let your phone without an operating system so either you install a custom jelly bean or put via twrp the stock recovery back (you cand find on the same page linked above) and then install stock jelly bean via dload folder.
P.S. from what I see in your screenshot, did you put an update.zip in hwouc folder on sdcard? hwouc is the folder where phone saves updates downloaded via ota then installs them from recovery.
are you sure you put update.APP in dload folder?
hope I helped
Click to expand...
Click to collapse
Hey, I was trying to follow the instructions, but somehow this is not working, I mean the hisuite is stock searching the drivers and once I type adb reboot bootloader it just says not found. but doesn't do anything.
As for the screenshot I found it online, it's the closest thing to the error presented, but I did put the UPDATE.APP on the dload folder
The error I get first it gives me some sort of error which disappears once the Android system recovery menu comes up. then the only thing I'm able to see says:
Checking Module MD5RSA.. OK
Checking Module CRC.... OK
Checking Module CURVER.... OK
Checking Module VERLIST....
Huawei SD card update fail.....
cust copying files...
copy cust files successed!
===================
FAIL
===================
EDIT: I'm updating the actual picture of the error received.

Not found as in command not found or what? Post print screen please
Sent from my HUAWEI P6-U06 using XDA Free mobile app

adipaval said:
Not found as in command not found or what? Post print screen please
Sent from my HUAWEI P6-U06 using XDA Free mobile app
Click to expand...
Click to collapse
Here's the screenshot!

Did you see that you wrote abd instead of adb?
Sent from my HUAWEI P6-U06 using XDA Free mobile app

adipaval said:
Did you see that you wrote abd instead of adb?
Sent from my HUAWEI P6-U06 using XDA Free mobile app
Click to expand...
Click to collapse
My bad, although with adb is still not working lol.

mine is working
DanRioja said:
My bad, although with adb is still not working lol.
Click to expand...
Click to collapse
i downloaded zip from before to be sure.
i see in my console that it runs as administrator, i think that's the reason why yours is not working.

adipaval said:
i downloaded zip from before to be sure.
i see in my console that it runs as administrator, i think that's the reason why yours is not working.
Click to expand...
Click to collapse
I have a question, could it have something to do with the drivers not being installed? I mean I installed the hi-suite but it never installed the drivers, so I'm wondering if that could be the reason, or could it be due to the phone not booting and not having TWRP?

DanRioja said:
I have a question, could it have something to do with the drivers not being installed? I mean I installed the hi-suite but it never installed the drivers, so I'm wondering if that could be the reason, or could it be due to the phone not booting and not having TWRP?
Click to expand...
Click to collapse
EDIT: I'm uploading the picture, I tried with administrator, still not working.

If it says device not found it means adb started but cannot find device.
It is ok because in download mode you cannot enable usb debugging so that adb sees it but if you type to flash the twrp.img it should work. At least on mine it did
Be sure you started phone in download mode by powering it on with vol down pressed. Press it longer just to be sure
Sent from my HUAWEI P6-U06 using XDA Free mobile app

adipaval said:
If it says device not found it means adb started but cannot find device.
It is ok because in download mode you cannot enable usb debugging so that adb sees it but if you type to flash the twrp.img it should work. At least on mine it did
Be sure you started phone in download mode by powering it on with vol down pressed. Press it longer just to be sure
Sent from my HUAWEI P6-U06 using XDA Free mobile app
Click to expand...
Click to collapse
Hmm it's weird, I tried to skip the first step " adb reboot bootloader" and went to the second step, this is what I got (check the picture)

.img
DanRioja said:
Hmm it's weird, I tried to skip the first step " adb reboot bootloader" and went to the second step, this is what I got (check the picture)
Click to expand...
Click to collapse
that's because you did not write .img
fastboot flash recovery twrp_2_6_3_3_recovery.img

DanRioja said:
Hmm it's weird, I tried to skip the first step " adb reboot bootloader" and went to the second step, this is what I got (check the picture)
Click to expand...
Click to collapse
Hello !
Please follow this steps from here !
Because adb not working, you can put your device in bootloader mode manually : press and keep at the same time for about 10~15 sec. power button and volume down , now your device are in bootloader mode and you can use "fastboot" command to flash stock/twrp recovery !
If your device was on Android JB you must use stock/twrp forAndroid JB, else if your device was on Android KitKat you must use stock/twrp for Android KitKat .
The next time when you want to flash something in your device please do your research more - because here on XDA you have almost all the answers to every question - sure, you need to spend some time to read - and not ultimately you can ask , if you are not 100% sure what to do
Good luck !

surdu_petru said:
Hello !
Please follow this steps from here !
Because adb not working, you can put your device in bootloader mode manually : press and keep at the same time for about 10~15 sec. power button and volume down , now your device are in bootloader mode and you can use "fastboot" command to flash stock/twrp recovery !
If your device was on Android JB you must use stock/twrp forAndroid JB, else if your device was on Android KitKat you must use stock/twrp for Android KitKat .
The next time when you want to flash something in your device please do your research more - because here on XDA you have almost all the answers to every question - sure, you need to spend some time to read - and not ultimately you can ask , if you are not 100% sure what to do
Good luck !
Click to expand...
Click to collapse
I'm going to give it a try. thanks!

[How to] Properly install TWRP with Flashify

So like myself, many of you have rooted, but still don't have a recovery, or one didn't install properly.
Well, I'm here to help!
For those that don't know, Flashify is a program from the Play Store that rooted users can use to install a custom recovery. In this case, it's TWRP.
The problem: At the time of this post, Flashify does not see any current recovery files for our device.
The solution: We make it see the recovery!
So, on to the goodies...
What you need:
Rooted LG G3 (D851 for these instructions)
Flashify from the Play Store
TWRP image file
Click to expand...
Click to collapse
Now that you have the required items and are ready to go, the hard part is done... Now let's get that recovery installed for you.
Instructions:
1. Plug your phone into your PC.
Once this is done, find the TWRP IMG file you downloaded and move it to your phone's internal storage.
2. On your phone, open Flashify and make sure to allow it SuperUser access when prompted.
3. Select "Recovery Image" and then select "Choose a File." Navigate to where you saved the IMG file on your device and select it.
4. Finally, Flashify will prompt you if you are sure you want to do this. Select "Yup!", let it do it's thing, and that's it.
Click to expand...
Click to collapse
You should now have a working TWRP recovery installed on your device.

Worked like a champ. Thanks. I don't have a computer right now so this was definitely helpful.

TWRP 2.8.0.1
BINGO:good:

Shouldn't you be able to move the files from a file manager?

Mnorton1228 said:
Shouldn't you be able to move the files from a file manager?
Click to expand...
Click to collapse
Yes, if you downloaded directly to your device. Personally, I like to download on the PC, then move it that way, but everyone has their own preferences.

I understand and that would probably be my preferred method as well. I just wanted to clarify so there were more options available!

bryceowen said:
Quick question, does this latest release include the 'view online album' fix mentioned in this post?
Click to expand...
Click to collapse
Hey man. Didn't you used to make Bootsplashes for the Inspire 4G?

Can't install anything in TWRP

i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?

Citroon said:
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Click to expand...
Click to collapse
It looks so simply but did you take a look to your rom zip? open with a zip explorer like winzip in /META-INF/com/google/android and here you must find this file

SubwayChamp said:
It looks so simply but did you take a look to your rom zip? open with a zip explorer like winzip in /META-INF/com/google/android and here you must find this file
Click to expand...
Click to collapse
it's not only with the roms, it's with everything
i've tried to flash new firmware, gapps and nothing works :/

well, what version of twrp do you use? try first with oficcial 3.0.2.0, bootloader unlocked? check usb debbugging and allow oem unlock in developer options, sometimes neccessary mount system or enable MTP in recovery

SubwayChamp said:
well, what version of twrp do you use? try first with oficcial 3.0.2.0, bootloader unlocked? check usb debbugging and allow oem unlock in developer options, sometimes neccessary mount system or enable MTP in recovery
Click to expand...
Click to collapse
im using the official 3.0.2.0, i currenly have no RoM installed so i can't boot into anything

Citroon said:
im using the official 3.0.2.0, i currenly have no RoM installed so i can't boot into anything
Click to expand...
Click to collapse
try first formatting data, wipe everything except where placed your rom zip (int or extSD), mount system and flash again

SubwayChamp said:
try first formatting data, wipe everything except where placed your rom zip (int or extSD), mount system and flash again
Click to expand...
Click to collapse
Tried that, still having the error:crying:

Citroon said:
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Click to expand...
Click to collapse
ok, go to format the data and then write YES, but u will lose your data, so, backup your files, and then restore them. should be working !!

StonebridgeGr said:
ok, go to format the data and then write YES, but u will lose your data, so, backup your files, and then restore them. should be working !!
Click to expand...
Click to collapse
Doesn't work either, this is really weird to me, i've been flashing for a few years now, and never encountered this issue before.
-also note that i'm not amazing at this

Citroon said:
Doesn't work either, this is really weird to me, i've been flashing for a few years now, and never encountered this issue before.
-also note that i'm not amazing at this
Click to expand...
Click to collapse
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )

StonebridgeGr said:
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
Click to expand...
Click to collapse
i've tried about every RoM available.
I also want to note that i have flashed with this version of TWRP before (3.0.2.0)

StonebridgeGr said:
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
Click to expand...
Click to collapse
tried about every rom available, and other things just to see what would work and what wouldn't (nothing can flash)
im currently running 3.0.2.0 and have flashed with this version of TWRP before, but suddenly it stopped working

Citroon said:
Tried that, still having the error:crying:
Click to expand...
Click to collapse
Probably a bad flashing and you are needing repari partitions, for that I recommend start from beginning again:
- flash miui rom for fastboot (unpack zip rom in your adb folder for better performance, connect device to pc into mode fastboot, be sure device be recogniced typing; fastboot devices then right click mouse and execute like admin over "flash all".
- then to install rom you can flash again twrp via fastboot typing any place adb folder and placing file recovery.img this folder; fastboot flash recovery recovery.img
- then go to recovery with hardware keys and flash supersu v.2.79

SubwayChamp said:
Probably a bad flashing and you are needing repari partitions, for that I recommend start from beginning again:
- flash miui rom for fastboot (unpack zip rom in your adb folder for better performance, connect device to pc into mode fastboot, be sure device be recogniced typing; fastboot devices then right click mouse and execute like admin over "flash all".
- then to install rom you can flash again twrp via fastboot typing any place adb folder and placing file recovery.img this folder; fastboot flash recovery recovery.img
- then go to recovery with hardware keys and flash supersu v.2.79
Click to expand...
Click to collapse
oh boy, i guess im screwed for now then.
i only have access to a macbook for the next few days, tried installing fastboot on it but that's a complete nightmare

Citroon said:
oh boy, i guess im screwed for now then.
i only have access to a macbook for the next few days, tried installing fastboot on it but that's a complete nightmare
Click to expand...
Click to collapse
two things; I assume that trying to flash from extSD, if yes with file explorer of recovery copy to internal memory, maybe an issue to reading extSD, also you can to install a newer version of recovery 3.0.3.2 works sometimes for me and last here you have a reading page about install fastboot on mac (nightmare) http://www.stechguide.com/setup-adb-and-fastboot-on-mac-easy-step-by-step-guide/

SubwayChamp said:
two things; I assume that trying to flash from extSD, if yes with file explorer of recovery copy to internal memory, maybe an issue to reading extSD, also you can to install a newer version of recovery 3.0.3.2 works sometimes for me and last here you have a reading page about install fastboot on mac (nightmare) http://www.stechguide.com/setup-adb-and-fastboot-on-mac-easy-step-by-step-guide/
Click to expand...
Click to collapse
I finally got it working
I was so stubborn that I decided to install Windows Bootcamp on my mac
it was as simple as reinstalling TWRP and do a clean wipe, now i can install roms and all the other things as i please again.
-Thank you for your help!