Database Users

Ideos rom question

I don't know where to post this cause I don't see a section for the huawei m850, but since its basicly a rebranded ideos I thought Idk try here. I tied to flash gingerman v1 to it but when it flashed it changed the version of cwm, now I cant read my backup to flash back. It'll load but its stuck in airplane mode and force closes every 15 secs or so. Is there anyway to flash back to stock, like how Samsung has odin, or to get a copy of the stock rom? Any help anybody can give me would b appreciated, thanks in advance.
Sent from my Huawei Ascend using XDA App

Since huawei m850 is identical to U8120, your best hopes are to copy one of these ROMs on the sd card and flash from recovery mod.
http://forum.xda-developers.com/showthread.php?t=782802
http://forum.xda-developers.com/showthread.php?t=802893
http://forum.xda-developers.com/showthread.php?t=1096075
good luck!

[Q] Incompatible ROMs?

Hi everyone,
For a reason unknown to me some of the newer roms don't work properly on my u8800 smartphone. I can install and run them but the rom doesn't show battery percentage / level. Can somebody tell me what my phone is missing or what's outdated on it?
Also a recommendation for a CWM version would be highly appreciated (there's a lot to chose from).
Kind Regards,
Jasper

Did you install official 2.3.5 before you tried them? If not, there is your reason. Install beta 1 or 2, so your bootloader will stay unlocked. Both recoveries for .35 kernel are good. 5.0.2.7 and 5.5.0.4.

First of all; thank you for your quick response!
Yes I upgraded to the official 2.3.5 (and everything was working just fine); but after doing so (following the guide and installing the newest version of CWM) I got errors trying to install ROMs. I can't remember the specific error; something with incompatibility ~ I couldn't install any custom rom said CWM.
Could you perhaps provide me a few links so I can try it again? :]

Other thing is can think is that you install u8800pro rom. Or you have pro and you installed u8800 rom. Might sound stupid but armeijan cant think anything else. If figure something else, i'll post here.
Sent from my Derp using XDA Herp

[Q] [Defy+] Downgraded To CM7 from CM9 & Battery Shows Question Mark

Last night I rooted my Defy+ with CM7(latest nightlies from defy-cm.net), applied battery and camera fix, everything worked perfectly and I enjoyed it.
I tried little experimenting then installed CM9(usedEpsylon builds) and flashed the kernel mentioned here(http://forum.xda-developers.com/showthread.php?t=1432100&page=3) but then I noticed it had lot of bugs and my phone started having a lot of weird reboots.
So I thought of reverting back to CM7 and then problem of the battery popped up. Battery now shows a question mark and I dont know whether it could charge or not. After reading a lot I thought it would be better to revert to CM9 just incase if the battery isn't charging and I'd have to find a workaround for charging.
Although I love CM9 very much but I can't stick to it because of the camera and a lot of instability.
After studying forums I realised it may be because of the incompatible kernel for CM7. So the only way I could get teh original kernel is by flashing the original SBF. But the problem arises is that I cant find the same build for my device and I am little skeptical about flashing with different SBF. Also I have no nandroid backup as such. Nearest I could find a SBF was with 4.5.1-134_DFP-1321. Also I have gone through all the Walter79 posts and his SBF collection too and it doesnt have the SBF for my DEFY+.
Can somebody guide me with the workaround?
My DEFY+ specifications:
system version - 45.0.891.MB526,AsiaRetail.en.03
model number - mb526
android version - 2.3.4
baseband version - epu93_u_00.60.00
kernel version - 2.6.32.9-gbdd614e [email protected]#1
build number - 4.5.1-134_DFP-891

I am having the same problem, even after resoring to the original the battery keeps giving me a question mark and the phone shuts down.
I can boot it into recovery by plugging it in but whatever rom I flas the battery keeps going to question mark.
I am becoming a little sacred I killed my phone now..

Same problem with me. flashing my stock nandroid backup did not solve the problem..
http://forum.xda-developers.com/showthread.php?t=1569336
I put everything back to stock, because without the mcguyver trick I am not able to charge my battery..
I am sending it RMA this monday

So you say that even if I flash a SBF, the battery problem won't solve?? I thought it was just because of a kernel incompatibility otherwise why would the battery charge while I'm using CM9?
Sent from my MB526 using XDA

Oh!!! It seems there are two threads of the same name!!!! I replied here
You may find a solution
---------- Post added at 01:09 AM ---------- Previous post was at 01:08 AM ----------
Hi,
My Defy+ also came with the same SBF version however I updated it to another one and now service center updated it to another one(which is unrootable!!) So be careful while choosing the SBF(Don't worry I will tell you which one should be safe! ). First:
There are issues with battery charging with CM9. moreover you should have tried Quarx's build CM9 for Defy+. Both CM7 and CM9_Defy+ of quarx are more stable!! however, as per memory serves I remember flashing CM7 for Defy when I had the version of SBF you have, so I believe even CM9 for Defy should work(No need to flash extra kernels if you flash the Defy versions of CM).
Now coming to the SBF part you may go for this SBF(from my dropbox). It is 4.5.1-134_DFP-1321 version SBF. That will update your phone to 2.3.6 and BL6. Thus you won't be able to downgrade to any Froyo kernels and will have to use CM7 and CM9 for Defy+ builds(use Quarx's build this time). However NEVER flash the version with DFP-231!!! It has BL7 and is still not rootable!!! ( Thanks to dumb service center people I am stuck with this!!)

It happened because of some network problem here and I don't see any option to delete the other post.
I'm downloading the SBF right now and wish that the problem gets solved and I can use CM7 again with no battery issue.
Sent from my MB526 using XDA

I did flash Quarks new nightly that was just posted. All worked fine at first and then I rebooted and since then it will no longer boot. If I plug it in I can get into recovery but if I let it try to start up I get a big battery with a question mark in it. I will try this sbf and thank you so much for helping

Also I notice that your sbf file is quite huge compared to the same file by walter79.. Is it just that he zipped it and you didn't?
Sent from my MB526 using XDA

Puckying said:
I did flash Quarks new nightly that was just posted. All worked fine at first and then I rebooted and since then it will no longer boot. If I plug it in I can get into recovery but if I let it try to start up I get a big battery with a question mark in it. I will try this sbf and thank you so much for helping
Click to expand...
Click to collapse
Welcome Make sure you don't drain your battery much. I have seen many users using CM9 with this prob. However there is a battery fix if you want to try. Search it in Q&A also someone posted recently. Sorry don't have time now to search!
meherranjan said:
Also I notice that your sbf file is quite huge compared to the same file by walter79.. Is it just that he zipped it and you didn't?
Sent from my MB526 using XDA
Click to expand...
Click to collapse
Its of big size because:
1.) I didn't zip it.
2.) Its a full SBF not fixed. A fixed SBF has its cmg39 deleted which contains BL version and also all system image! Dis is done to maintain downgradability and thus needs a nandroid backup too!

pranks1989 said:
Welcome Make sure you don't drain your battery much. I have seen many users using CM9 with this prob. However there is a battery fix if you want to try. Search it in Q&A also someone posted recently. Sorry don't have time now to search!
Its of big size because:
1.) I didn't zip it.
2.) Its a full SBF not fixed. A fixed SBF has its cmg39 deleted which contains BL version and also all system image! Dis is done to maintain downgradability and thus needs a nandroid backup too!
Click to expand...
Click to collapse
I added the battery fix as well but then the battery had already drained. It went really fast from 90% to completely dead.
I shall try the McGyver trick today and see if it will respond again after that.

Puckying said:
I added the battery fix as well but then the battery had already drained. It went really fast from 90% to completely dead.
I shall try the McGyver trick today and see if it will respond again after that.
Click to expand...
Click to collapse
Oh okay..!! Ya then try the McGyver trick.. But be careful at it or you may end up frying your battery!!

I am a bit worried about that too so it is still laying there, ready to try but my courage lacks.
My husband is an elctro man and will be home tomorrow so I think I will wait till then.
I wonder after flashing the new sbf it will again recognise the battery..

I reflashed cm 9 and now everything is up and running again. Battery is charging.
I will see how it holds up over time , if all else fails I can still flash the full sbf

Puckying said:
I reflashed cm 9 and now everything is up and running again. Battery is charging.
I will see how it holds up over time , if all else fails I can still flash the full sbf
Click to expand...
Click to collapse
My problems are solved as well I did not want to work on CM9 anymore. To much problems and instability.
http://forum.xda-developers.com/showthread.php?p=24340090#post24340090

fokkeh said:
My problems are solved as well I did not want to work on CM9 anymore. To much problems and instability.
http://forum.xda-developers.com/showthread.php?p=24340090#post24340090
Click to expand...
Click to collapse
Puckying said:
I reflashed cm 9 and now everything is up and running again. Battery is charging.
I will see how it holds up over time , if all else fails I can still flash the full sbf
Click to expand...
Click to collapse
Good to know the problem is solved! Probably you should wait till a stable CM9 (Defy+) comes out

I flashed a full sbf, the one that was posted but now can no longer receive calls or texts.
I can ring out so there is a connection. but nothing comes through. I have saerched all over the place , installed the baseband changer. But no incoming calls...

Puckying said:
I flashed a full sbf, the one that was posted but now can no longer receive calls or texts.
I can ring out so there is a connection. but nothing comes through. I have saerched all over the place , installed the baseband changer. But no incoming calls...
Click to expand...
Click to collapse
The SBF I posted is for India. You should flash an SBF that suits your region. You said you installed baseband switcher but baseband switcher works only after rooting and you need to make correct changes. So, since you are flashing full SBF I suggest flash the one for your region. There should not be any prob then!

Yes I am doing so now Thanks again. Steep learning curve here
And I rooted at once with super one click
---------- Post added at 03:52 PM ---------- Previous post was at 03:03 PM ----------
No difference, still no incoming calls..
Phew! Fixed. No more modding for a bit..well not today anyway

pranks1989 said:
The SBF I posted is for India. You should flash an SBF that suits your region. You said you installed baseband switcher but baseband switcher works only after rooting and you need to make correct changes. So, since you are flashing full SBF I suggest flash the one for your region. There should not be any prob then!
Click to expand...
Click to collapse
No problems here (In the Netherlands) with your ROM (asia version).

Thanks guys for the answers. I'm now running CM9(quartz build) with no kernel flashing. Camera works fine and everything as well. I think I'll stick to this for sometime. Although I see little lag in the homescreen animation and drawers stack animation. But as it is a nightly and still under development, it is quite expected. Also I'll keep using it anyway so that I can help in the development of CM9 by bug and automatic reports submissions.
This was all possible because of the SBF mentioned here..
Sent from my MB526 using XDA

New User - Problem with Update after rooting

I'm sorry for having to post here, I'm a new XDA member and I've just started using my tablet and found out I can't post in the dev section. I'm not sure how else to get help and a previous boyfriend told me the xda-developers community was a great place so I thought I would try here.
I have the Nexus 7 (2013 edition) and I used WUG's method of rooting - everything went perfectly, but now I'm getting a notification that there is an update (an OTA update - I think that's what they are called?) and it doesn't apply. I'm not sure if I should have, but I did the bootloader unlock and installed a new recovery (TWRP - I think that's how it's spelled?. sorry again)...
Anyway.... At this point my tablet is working great, but I constantly see this notification for an update and I'm not sure what to do.. It says "touch to install" and I've done that but it just boots into my new recovery. If anybody has access to WUG in the dev forum, could you please ask him what I should do?
Thanks!!!!!!!!!!!!!!

BarbaraG said:
I'm sorry for having to post here, I'm a new XDA member and I've just started using my tablet and found out I can't post in the dev section. I'm not sure how else to get help and a previous boyfriend told me the xda-developers community was a great place so I thought I would try here.
I have the Nexus 7 (2013 edition) and I used WUG's method of rooting - everything went perfectly, but now I'm getting a notification that there is an update (an OTA update - I think that's what they are called?) and it doesn't apply. I'm not sure if I should have, but I did the bootloader unlock and installed a new recovery (TWRP - I think that's how it's spelled?. sorry again)...
Anyway.... At this point my tablet is working great, but I constantly see this notification for an update and I'm not sure what to do.. It says "touch to install" and I've done that but it just boots into my new recovery. If anybody has access to WUG in the dev forum, could you please ask him what I should do?
Thanks!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Do you have the WiFi only version or the LTE version? Also, under your settings -> about phone, what build number are you currently on? Since you have rooted and installed a custom recovery, OTA updates will not install correctly. You have a couple of options in this regards, and I or someone will go over them once we figure out what version you are running.

railed said:
Do you have the WiFi only version or the LTE version? Also, under your settings -> about phone, what build number are you currently on? Since you have rooted and installed a custom recovery, OTA updates will not install correctly. You have a couple of options in this regards, and I or someone will go over them once we figure out what version you are running.
Click to expand...
Click to collapse
ThankYou so much for the help... It's the WiFi only version. The build number is: JSS15J

http://forum.xda-developers.com/showthread.php?t=2404833

BarbaraG said:
ThankYou so much for the help... It's the WiFi only version. The build number is: JSS15J
Click to expand...
Click to collapse
Thanks for that:
Here's what you can do to install the update.
1) go to this thread and download either the odexed or deodexed version.
2) Reboot to recovery
3) Wipe Cache/Dalvik Cache
4) Flash the .zip file you just downloaded
5) Reboot your updated tablet.
OR
You can read here and try this.

railed said:
Thanks for that:
Here's what you can do to install the update.
1) go to this thread and download either the odexed or deodexed version.
2) Reboot to recovery
3) Wipe Cache/Dalvik Cache
4) Flash the .zip file you just downloaded
5) Reboot your updated tablet.
OR
You can read here and try this.
Click to expand...
Click to collapse
Oh railed, thankyou so much - I was not sure if I would be able to get any more updates. If I do that, will it delete everything on my tablet? It did that when I did the change to an unlocked bootloader, and I had to reload everything.

BarbaraG said:
Oh railed, thankyou so much - I was not sure if I would be able to get any more updates. If I do that, will it delete everything on my tablet? It did that when I did the change to an unlocked bootloader, and I had to reload everything.
Click to expand...
Click to collapse
All your data will be preserved. Only Wipe the Cache/Dalvik Cache, not the Data. Before you install go to Wipe -> Advance -> Check only Cache and Dalvik Cache.
Typically when an update comes out, someone will post a flashable update within a couple of hours so we can install them as well. Hope it helps.
Edit: As always before flashing anything, make a backup, by rebooting into recovery and selecting Backup (i check all the boxes).

BarbaraG said:
Oh railed, thankyou so much - I was not sure if I would be able to get any more updates. If I do that, will it delete everything on my tablet? It did that when I did the change to an unlocked bootloader, and I had to reload everything.
Click to expand...
Click to collapse
Also.... If I just load the latest cyanogenmod on it, will that take care of it. I have the same old phone from my previous boyfriend and it's running cyanogenmod.. It will update the OS whenever a new version comes out and I don't lose the data like I did with the unlock bootloader thing?

BarbaraG said:
Also.... If I just load the latest cyanogenmod on it, will that take care of it. I have the same old phone from my previous boyfriend and it's running cyanogenmod.. It will update the OS whenever a new version comes out and I don't lose the data like I did with the unlock bootloader thing?
Click to expand...
Click to collapse
I believe so, Cyanogenmod usually merges the updates pretty quickly into the code and you won't get any update notifications from Google directly any more. There are only nightly releases so far for this device if you feel like going that route.

railed said:
I believe so, Cyanogenmod usually merges the updates pretty quickly into the code and you won't get any update notifications from Google directly any more. There are only nightly releases so far for this device if you feel like going that route.
Click to expand...
Click to collapse
Thank You! Very Much!!!
Do you think I should go the cyanogenmod route?
I've really liked cyanogenmod on the phone on barnes&noble device they are on, but I've been scared to update this tablet since we've broken up and I don't have anybody that can help.

BarbaraG said:
Thank You! Very Much!!!
Do you think I should go the cyanogenmod route?
I've really liked cyanogenmod on the phone on barnes&noble device they are on, but I've been scared to update this tablet since we've broken up and I don't have anybody that can help.
Click to expand...
Click to collapse
That's completely up to you and what you prefer... I like the stock android experience so far, but there are many options out there for custom ROMs besides CM. Take a look here and here and figure out if a ROM in there has something you want... the great thing about this is if you don't like it, flash something else until you find exactly what you like... that's how I plan to do it, once the ROMs get more stable with the 4.3 updates.

railed said:
Thanks for that:
Here's what you can do to install the update.
1) go to this thread and download either the odexed or deodexed version.
2) Reboot to recovery
3) Wipe Cache/Dalvik Cache
4) Flash the .zip file you just downloaded
5) Reboot your updated tablet.
OR
You can read here and try this.
Click to expand...
Click to collapse
I've been reading through all of the links you sent and some others I've found. Should I go with the odexed or deodexed version?

BarbaraG said:
I've been reading through all of the links you sent and some others I've found. Should I go with the odexed or deodexed version?
Click to expand...
Click to collapse
I use deodexed, as do a lot of people who like to customize. There's not a lot of difference between the two. Here is an article that explains it pretty well: Odexed vs Deodexed

railed said:
I use deodexed, as do a lot of people who like to customize. There's not a lot of difference between the two. Here is an article that explains it pretty well: Odexed vs Deodexed
Click to expand...
Click to collapse
Thank You, I now know the difference between them. I think I'll go with the Deodexed version also.
Thanks again for all of your help!!!!!

OxygenOS 3 Black screen after reboot

Hello!
Ever since trying out the first OO3 Beta (3.0.0) I have gotten a weird bug, flashing the ROM works fine and everything works all the way until I reboot my phone. It loads through the bootanimation and then it just has a black screen and you can see the notification bar flash every 5 seconds or so. This issue also come up on the newest 3.0.1 beta.
I've tried different ways of flashing using the modified recovery and the modified supersu (also without the supersu) but I still get the same issue. I've tried different OO3 ROMs as well like Skydragon and CyanOxy but I get the same bug.
I haven't seen anyone post something about the same issue so I figured I'd ask, sorry if this already has been answered and I missed it.
Thanks in advance.

Same happend to me, always get that black screen, try to reboot once you are in it, works for me.

I've tried rebooting a few times and still got the same result, unfortunately.
Thanks for the advice anyways!

Hi,
I'm facing exactly same issue since new OTA update...
Did you manage to fix it?

Hey Endoloris.
I haven't been able to fix it yet unfortunately. I've really tried almost everything at this point which makes me think there's something odd with the hardware, but I don't really know.
I'll update this thread if I fix it.

Have you uninstalled the Google Search app?? Every time I trie to uninstall the Google app I get the same problem. Now I just let it on my phone.
Edit:
Have you flashed the right firmware for OxygenOS 3??

LordHelmchen89 said:
Have you uninstalled the Google Search app?? Every time I trie to uninstall the Google app I get the same problem. Now I just let it on my phone.
Edit:
Have you flashed the right firmware for OxygenOS 3??
Click to expand...
Click to collapse
Yes, I've tried both those options. I've tried pretty much everything. I even tried restoring the phone to stock 2.2.1 and then updating via OTA and I still got the same issue.

So the weird thing is that I get the same issue on the new Paranoid Android ROM released today.

Adhas said:
So the weird thing is that I get the same issue on the new Paranoid Android ROM released today.
Click to expand...
Click to collapse
Really strange...sorry,but Ican't help you then. Maybe you ask one of the devs with pm.
---------- Post added at 04:07 PM ---------- Previous post was at 04:02 PM ----------
Are you realy sure, that you flashed the right TWRP and firmware?? Or do you use a custom kernel.
Sorry, my last ideas...

I did try different firmwares, it didn't work at all with the old ones for obvious reasons. I tried the twrp 3.0.2 Hybrid, a custom recovery when the first Oxygen 3 beta came out (was orange), and I tried the recovery made by Grarak recently. I also tried using stock recovery and flashing.
No custom kernel, I've tried flashing with the modified Supersu but I was thinking that it might be causing the issue so I tried without root and I still got the same result.

In the same boat here, was running official CM, then this happened.