Related
Hi to all,
I created this thread here is for existing users, potential users, interested users and experienced users or any casual visitors who wants to know more about the rom. Well, SGS users will ask why create a thread just for this, when there is another one over at the development section. The answers are listed as follows:
To reduce the number of posts in the other thread (reduce spamming) thereby not bogging down the developers with issues that can be solved by the users. And they can spend their time to concentrate what they do best, which is improving the MIUI Rom.
To consolidate questions, problems, bug reports, comments in one place. As you can see from the other thread, many a times, some of the posts which benefits the users were consumed by newer posts. While there is a SEARCH function, I can understand it can sometimes be a challenging task just to sieve through the searched posts results. I know we can't eliminate users posting repeated issues, but at least this will attempt to reduce those posts.
To allow new xda members who are on MIUI but unable to post their ideas, comments, etc. This is also an important avenue to allow new xda members to have a voice. While they may be new, they might have tips, tricks and also can help to resolve issues. Issues brought up can be shared by everyone too.
To allow the developers concentrate on improving the MIUI rom. Who doesn't want a better MIUI? Of course the developers doors will always be open, and will help out whenever they can, but wouldn't it be better for us to let them concentrate on what they do best, and what we want best?
So, to make it successful, I need you guys to help one another out, like what I have seen over the other thread.
This thread belongs to all of you, and I am sure that there is active participations in here.
MIUI has a pretty long history. However, for our device, MIUI has just evolved. Likewise, the user base has just started to grow. There will be times when even the most experienced user or developer will get stumped too, and not able to come up with a solution to resolve. We can see from the other thread that there are diverse views regarding battery life, sdcard issue, etc etc. We will not know since the usage pattern of each individual is as good as your fingerprint. No one is alike. Therefore we seek your understanding that issues not solved immediately will be looked into seriously by the team. There will always be limitations for every rom, regardless what base they come from.
All we ask is whether this rom fits your usage or not. And the only way for you is to try it out. Feel it, experience it, and judge for yourself if this rom fits you, can you live with the shortcomings of the rom. If you decide that this rom doesn't fit your daily needs, you can just simply flash to another rom that fit your needs better. And you can at least tell yourself that I have tried but it is not suitable.
Is this thread some form of advertising? Well, again different interpretations for different people. We will not go into that as we believe the QUALITY OF THE ROM WILL SPEAK FOR ITSELF.
One thing that can be said though, credits goes to the cm7 team, the official MIUI developers too. And each day, we can see breakthroughs. I do foresee a bright future for this rom here.
FAQ Section
[Written by Galnet, g00ndu and me]
Before asking for help, please read through post 1 to post 4. Most of the issues have been addressed in this 4 posts. By doing so, you are helping to keep this thread clean.
1. APP RELATED:
1.1 Apps crashing all the time!
Simply enter recovery mode and do a Format on Data, System, Cache
1.2.1 Apps restored from backup not working
I would always flash from clean and redownload all your apps from market. I know you can backup and restore, but to me this causes alot of issues which people bring up all the time. If you want a clean install and avoid any issues in the long run, then 15 - 20 minutes of redownloading isn't as bad as hours of issues!
Also, if you want to try to restores apps using Titanium Backup, restore "APP ONLY," restoring data causes problems.
1.2.2 3rd party apps force closing
Turn off compatibility mode. Settings > Programs Tab > Manage Applications > All Tab > Select app > Turn off OR IF IT STILL FORCE CLOSES Settings > Programs Tab > Manage Applications > All Tab *again* > Select app > Clear Data > Uninstall and then reinstall using Market.
1.3 Apps not installing
Clear market cache and try again.
1.4 Can't See Paid Apps in Market
Download SGS-Tools and select Market Fix and apply then reboot.
1.5 Downloading from Market Not working
Goto Downloads Press Menu Key and switch Settings to WiFi or Mobile network.
1.6 Searching not working
Simply enter search advanced settings and turn off searching within SMS (Mentioned on Original Post)
2. HARDWARE RELATED:
2.1 SD-CARD Not working or other issues with Camera or Sensors
When flashing if you don't see the Cyanogen Logo after the Samsung one when turning the phone on to enter recovery (After flashing cm7-galaxys-initial-kernel.tar) , then STOP flashing process as you have done something wrong or are trying to install coming from a JVK rom. Downgrade to Froyo or if need be JM1 and start the process over.
Also, camera is not working properly (known bug) – poor saturation and multiple lines running through image.
2.2 External SD card not detected
If your external sd card is not detected even when the kernel had corrected the issue, you most likely has the 2.3.3 bootloaders. You may flash the bootloader (definitely not recommended) or you can restart using EZBase rom or follow galnet's guide in his site.
2.3 Auto rotation/accelerometer not working
If your auto rotation/acceleromter is not working (despite having it enabled in Settings > Common Tab > Display Settings > Auto-rotate screen) then hard reboot (completely switch off device, wait 10+ seconds, and then switch device back on)
2.4 High Battery Drain
Known CM7 bug that is not fixed yet.
2.5 Battery only reports ~96% on full charge
This is a function implemented on ALL 2.2.1+ ROMS (including MIUI, which is based off CM7 2.3.3) so that the battery of the devices do not overcharge. Samsung ROMS falsely report 100% charge, but in actual fact, it also charges to ~96% and that if you watch closely, after a few minutes, the battery will rapidly drop back down to ~96% and stablise.
http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
2.5 Battery has stopped charging
Battery is known to stop charging when it gets too hot. This is to protect the battery and phone from exploding.
2.6 Phone turns on when I insert charger
This is a known bug (or function LOLS) which is present in the Nexus S ROMS and because the SGS MIUI ROM is a derived from the MIUI Nexus S ROM, SGS will also have this bug/function.
3. ETC:
3.1 Where do I start?
Have a look at Galnet's MIUI Guide and note that you can start from ANY Froyo ROM (Stock and Custom) as long as your device has a Froyo Bootloader.
3.2 Flashing from JVK to MIUI
You must first downgrade the firmware to Froyo (which MUST include a Froyo Bootloader - check in zip via WinRar for boot.bin and sbl.bin) It has been found that the Gingerbread bootloader has caused major problems. It is recommended that you downgrade to Eclair JM1 then upgrade to JS5 (files are avaliable on Galnet's Website) and then follow Galnet's MIUI guide to flash MIUI.
Note that flashing/using any Gingerbread modems such as JVK will not cause problems, it is only the Gingerbread bootloader that is causing problems.
3.3 IMEI SCREWED!
Flash back to JS5 or another Official Rom and it will be restored!
3.4 FLASH AT OWN RISK
If you don't have a clue what you are doing or ODIN is a strange word, then please go over to Galnet's MIUI guide and read it before flashing, make sure you understand the risks and note that the developers are not always available to answer your questions instantly!
3.5 Applying a downloaded theme:
Move theme file anywhere onto your phone's memory (should have a .mtz file extension) > Open Theme Manager > Press on Capacitive Menu Button > Import Theme > Locate and Select the theme you added onto your phone's memory
Alternatively, you can directly move the theme (.mtz) file to sdcard/MIUI/theme/
3.6 (SOME) Themes not changing lockscreen
Check that the theme supports MIUI Gingerbread 1.4.8, older MIUI FROYO themes will not work.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
COPY AND PASTE:
(Insert FAQ here)
In the future, please refer to the MIUI FAQ Section[/URL ] before posting.
TIPS AND TRICKS
1. Download seems to get stuck forever. Download only works with wifi.
To fix, open up the Download App, click menu, select toggle 3g /wif. This normally will work. If it doesn't work, try for 2 or 3 times. Remember to cancel the download from the app. If it still doesn't work, reboot and try again. The best fix will be to boot into recovery, and do a wipe / factory reset and reboot. Before downloading, go to the download app to activate the 3g / wifi toggle.
2. Speaker phone is too loud (Thanks to Ekin)
Goto DSPManager > Phone Speaker > Enable equalizer
Then drag all the zeros on the graph down to about -3.0 but keep them all roughly the same. This will lower the volume on the loudspeaker for everything, fixing your problem. When you want to watch a movie and want to make it louder, go back here and just swipe it to disable. So its only one swipe to get it on/off. In order to keep the settings, you need to hit the Back button for it to register correctly.
Raising it/enabling bass boost seems to kill the quality a little bit, so I recommend not to do those.
I have a Nokia headset that I use, and its a little quite so I do the same trick (except I raise the "headset" equalizer) and this nifty trick is basically the same as the voodoo sound hack which takes proper use of the high-quality sound card inside the Hummingbird.
3. Choppy / Laggy graphics and interface (Thanks to whitesox311)
In the settings under battery options....it has " power saving mode" on automatically....if you disable this it gets rid of all the issues. Also, if you leave "Hi-res graphics" turned off in the launcher settings it vastly improves smoothness.
4a. How to get Swype to work (Thanks to Prototype159)
Download the swype installer.
Follow the directions all the way til the end.
Hit the finish button. Reboot.
If it didn't work, clear data and uninstall swype and the swype installer. Try again.
If you change the kernel, you will have to redo it again.
4b. How to get Swype to work (Thanks to agha123)
Follow the instructions to the tee on this web page ,
http://www.androidpeek.com/2010/12/get-swype-keyboard-working-on-miui-rom/
5. Screenshot (Thanks to hacksome)
Pressing Menu + Volume DOWN -->> Screenshot!
reserved
Sent from my GT-I9000
Hmm...good timing. I have some questions on my own.
I have been reading the installation procedures for a while. This particular line intrigues me
6: Pull out the USB cable and start (in download mode) with 3-button-combo in recovery mode (waiting until samsung logo appears)
How do I start recovery mode within download mode? I don't want to take any risks but wish to understand fully on what I will be doing before I commit.
Another question: Assuming that later I decided MIUI is too buggy, is there a backtrack procedure? Usually I will just reflash with ODIN to a stock rom(eg: JPY) to rid of all the lagfixes etc then to maybe Doc's rom for example.
Since this is a ASOP sort of ROM in GB. how do I go about it?
Noob questions I know but I rather be noob now then to beg for help around later
i dont have the maps application in my rom. After installation i dont see any maps app.
mystifiyer said:
Hmm...good timing. I have some questions on my own.
I have been reading the installation procedures for a while. This particular line intrigues me
6: Pull out the USB cable and start (in download mode) with 3-button-combo in recovery mode (waiting until samsung logo appears)
How do I start recovery mode within download mode? I don't want to take any risks but wish to understand fully on what I will be doing before I commit.
Another question: Assuming that later I decided MIUI is too buggy, is there a backtrack procedure? Usually I will just reflash with ODIN to a stock rom(eg: JPY) to rid of all the lagfixes etc then to maybe Doc's rom for example.
Since this is a ASOP sort of ROM in GB. how do I go about it?
Noob questions I know but I rather be noob now then to beg for help around later
Click to expand...
Click to collapse
It means exactly that. In download mode hold the 3 buttons (vol up, power & home) and release all keys when the Samsung logo appears. After about 5 seconds you will see recovery mode.
You can easily backtrack. In Odin use a fw that has all three files and tick repartition. I use jpu.
Sent from my GT-I9000 using XDA App
sxi200 said:
It means exactly that. In download mode hold the 3 buttons (vol up, power & home) and release all keys when the Samsung logo appears. After about 5 seconds you will see recovery mode.
You can easily backtrack. In Odin use a fw that has all three files and tick repartition. I use jpu.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
@mystifyer,
this is the same answer i will give. it is correct.
thanks sxi200.
Sent from my GT-I9000
vivekrk44 said:
i dont have the maps application in my rom. After installation i dont see any maps app.
Click to expand...
Click to collapse
maps can be downloaded from market.
Sent from my GT-I9000
This is new! I didn't know we can do that!
Shall give it a try this Friday Thanks for the explanation
Another question:
I understand also that ASOP roms don't have the very good codec support. Fair enough. Some threads I seen has mentioned of Moboplayer. I gave it a try. Works well enough in hardware acceleration mode but software decoding mode looks really slow.
Now my question is: Does software decoding mode works better in ASOP roms than say a generic lagfixed rom?
vivekrk44 said:
i dont have the maps application in my rom. After installation i dont see any maps app.
Click to expand...
Click to collapse
Download from Market.
mystifiyer said:
This is new! I didn't know we can do that!
Shall give it a try this Friday Thanks for the explanation
Another question:
I understand also that ASOP roms don't have the very good codec support. Fair enough. Some threads I seen has mentioned of Moboplayer. I gave it a try. Works well enough in hardware acceleration mode but software decoding mode looks really slow.
Now my question is: Does software decoding mode works better in ASOP roms than say a generic lagfixed rom?
Click to expand...
Click to collapse
wow, this one i dont really know. i am not sure if there were bemchmarks being made on that or not.
not a good comparison, but still say this. i ran quadrant for this two roms, and the framerate for samsung is better in 3D, and not much different on 2D.
dont forget samsung did not release the sourcecode, and cyanogenmod do it from scratch. but nevertheless it is still good in aosp.
Sent from my GT-I9000
Prasad007 said:
Download from Market.
Click to expand...
Click to collapse
tks buddy, glad you are here too.
Sent from my GT-I9000
g00ndu said:
tks buddy, glad you are here too.
Sent from my GT-I9000
Click to expand...
Click to collapse
Likewise.
No problem. I will know it after I try this Friday. I can share it then, provided nothing goes wrong.
Quite a fair bit of adventurous users tend to dive in straight without checking the cons of a ASOP rom, only to regret and then flash back. I don't really want to fall in this category.
Multimedia is big for me as I watch alot of animes. This codec problem might give me abit of a headache with the software decoding and probably missing code support.
I think I asked enough. Shall camp here and explore other users' problems.
Thanks for the feedback. Appreciate it.
Did the galnet's instructions and the result is the same. so tired by the way
dr.bahaeddin said:
Did the galnet's instructions and the result is the same. so tired by the way
Click to expand...
Click to collapse
I've PM'ed you, I advise you do a 3 file install of JP2 via ODIN to make sure all your files on the phone aren't corrupted.
Once you have got Froyo installed then please get back to us. (Boot into Froyo and make sure it's all working correctly)
galnet said:
I've PM'ed you, I advise you do a 3 file install of JP2 via ODIN to make sure all your files on the phone aren't corrupted.
Once you have got Froyo installed then please get back to us. (Boot into Froyo and make sure it's all working correctly)
Click to expand...
Click to collapse
got your message man downloading right now. maybe my internal sd makes files corrupted?
dr.bahaeddin said:
got your message man downloading right now. maybe my internal sd makes files corrupted?
Click to expand...
Click to collapse
Pass mate, but if you have a felling this could be the case then format the internal sd, after installing Froyo and then copy the required MIUI files back across to your internal sd and then try to proceed in flashing MIUI again.
galnet said:
Pass mate, but if you have a felling this could be the case then format the internal sd, after installing Froyo and then copy the required MIUI files back across to your internal sd and then try to proceed in flashing MIUI again.
Click to expand...
Click to collapse
ok now i'm on JP2 everything works fine.
Ok, so I have a Droid X2, and the Droid X and Droid 1 as predecessors. I have never had any major problems, and the few that I couldn't get around I had SBF via RSD for. To my knowledge, there is no form of SBF for the Acer A500 (yet). So heres the issue:
I may have either flashed an update without the proper files to go before it; or I have have forgotton to wipe something. Nonetheless, my A500 wouldn't boot. When I did some research, I went to this site:
{http://forum.ppcgeeks.com/showthread.php?p=2127076#post2127076}
because it seemed in my eyes to have the most pertinent information. I got the update.zip to install and my A500 booted again! However, I could not get to stop two because my insternal SD card was wiped somehow and when I get to the main screen, do the circular unlock, the launcer, and many other programs repeatedly force close, so much so that I cannot do ANYTHING. How would you approach this, and is there a way for me to get into CWM. I have a recent nandroid backup that what 100% functional, and I would hope the MD5 sums would still match....
Any help/advice is greatly appreciated!
you're wrong, this is absolutely normal issue
http://forum.xda-developers.com/showthread.php?t=1159443
follow this link, this will give you yout tablet back fully operational.
in case of any further prob, this links will help you to perform an Hard/Wipe reset
http://forum.xda-developers.com/showthread.php?t=1132760
good luck
xda-dev2k said:
you're wrong, this is absolutely normal issue
http://forum.xda-developers.com/showthread.php?t=1159443
follow this link, this will give you yout tablet back fully operational.
in case of any further prob, this links will help you to perform an Hard/Wipe reset
http://forum.xda-developers.com/showthread.php?t=1132760
good luck
Click to expand...
Click to collapse
The top link provides a way to install via Acer recovery the new 3.1 OS, but to my understanding its unrootable for now, is that still the case?
the update zip is uploadable even without root.
just like the original OTA firmware. Try it, many other users got back their pads with this one, as you can see in internal posts of the thread
xda-dev2k said:
the update zip is uploadable even without root.
just like the original OTA firmware. Try it, many other users got back their pads with this one, as you can see in internal posts of the thread
Click to expand...
Click to collapse
I totally get what you're saying. What I meant is that if I did the update, it completed successfully, that I would then NOT be able to root the device. Obviously that is a better option that a brick! But I'm trying to find out if I can recover to the most updated version that has been rooted.
Maybe I'm wrong and a root program has been made for 3.1?
hey mate, U quite a little lazy readinf threads titles uh...
take a look at this http://forum.xda-developers.com/showthread.php?t=1138228
pick up the 1.3 version. it will root your "definitely final" version of os, this update U have just uploaded IS the last one available, and it's eligible of any further OTA update...
take care
xda-dev2k said:
hey mate, U quite a little lazy readinf threads titles uh...
take a look at this http://forum.xda-developers.com/showthread.php?t=1138228
pick up the 1.3 version. it will root your "definitely final" version of os, this update U have just uploaded IS the last one available, and it's eligible of any further OTA update...
take care
Click to expand...
Click to collapse
I work 70+ hours a week, I'm certainly not lazy. But that is why I ask these questions hoping for someone to give me a little short cut to the answer. Between work and sleep I have 2.75 free hours a day and do NOT want to spend them reading a forum where its a lot of bs banter in between the actual info. I'm sure there are a lot of people out there that just don't read, but I truly don't have the time.
Also, this is one of the biggest forums for Android out there. Theres no way I could ever read the HUNDREDS of threads just on this device alone....
I do appreaciate your help!!!
I'll give a final report when I have a chance to do it!
This method did NOT work. When I boot into recovery, it always goes to the screen with the triangle and the android. I never see a progress bar....does this matter?
I also tried your other suggestion of "wipe device without recovery" and that didnt work as well.
I know its not a lost cause since it boots all the way up. But every app force closes so I have NO access
YOU have to do things in proper steps !!! ( lack of sleep will do that to you ! )
1/ grab the file from that thread
http://forum.xda-developers.com/showthread.php?t=1159443
( remember to unzip it to get update.zip file and placed on your card and flash using normal recovery.... not renaming ! )... assuming you don't have CWM at the moment.
2/ grab the "iconiaroot 1.3" file to root your device ( as CWM and Acer Recovery Installer required root access )
3/ grab the Acer Recovery Installer and proceed to install CWM to your device...
after all those are done... work your way with CWM ( to access CWM ... you need to keep holding the buttons (Power & Volume down) until you see 4 lines of text...and not let go before that !! )
remember to wipe cache & factory reset ( both before and after to ensure 110% cleaned to avoid errors and FC )
good luck !!
UnicornKaz said:
YOU have to do things in proper steps !!! ( lack of sleep will do that to you ! )
1/ grab the file from that thread
http://forum.xda-developers.com/showthread.php?t=1159443
( remember to unzip it to get update.zip file and placed on your card and flash using normal recovery.... not renaming ! )... assuming you don't have CWM at the moment.
2/ grab the "iconiaroot 1.3" file to root your device ( as CWM and Acer Recovery Installer required root access )
3/ grab the Acer Recovery Installer and proceed to install CWM to your device...
after all those are done... work your way with CWM ( to access CWM ... you need to keep holding the buttons (Power & Volume down) until you see 4 lines of text...and not let go before that !! )
remember to wipe cache & factory reset ( both before and after to ensure 110% cleaned to avoid errors and FC )
good luck !!
Click to expand...
Click to collapse
So I responded to this last night, but somehow it disappeared?? Anyways, thank you for your effort to help me resolve this, but if you look at my initial post, there's no way your description and process would work. First of all, the update above I tried (like I mentioned) and it did NOT work. Also from my description I mentioned that when the tablet does boot, it boots to the home screen (stock green) but, all the important applications, the launcer included, force close so rapidly and repeatedly that I can't do ANYTHING. Thus, I would obviously NOT be able to install any programs, let alone root the device.
Thus the name of this thread....
ibrooks123 said:
So I responded to this last night, but somehow it disappeared?? Anyways, thank you for your effort to help me resolve this, but if you look at my initial post, there's no way your description and process would work. First of all, the update above I tried (like I mentioned) and it did NOT work. Also from my description I mentioned that when the tablet does boot, it boots to the home screen (stock green) but, all the important applications, the launcer included, force close so rapidly and repeatedly that I can't do ANYTHING. Thus, I would obviously NOT be able to install any programs, let alone root the device.
Thus the name of this thread....
Click to expand...
Click to collapse
And obviously you are suffering from lack of sleep !!
The update.zip ( after extraction ) from that thread can be flash either normal recovery or CWM recovery.
and here's the added tool to wipe without a recovery:http://forum.xda-developers.com/showthread.php?t=1132760
Therefore... what's stopping you ??
and please re-read my steps above.. after flashing... you will need to root and re-flash CWM using ( Acer Recovery Installer)
maybe you're not clearly looking at the picture...
there are 2 recoveries ( normal Acer stock recovery and CWM recovery )... DO NOT mistake Acer's stock recovery for the program called Acer Recovery Installer.
what Acer recovery Installer does is install CWM recovery for you and also backup/restore your original Acer recovery.
and you cannot use the program until you are rooted ( step #2 above )
FYI ... each recovery boot differently !!
Stock recovery -->> hold Power & volume down ( closest to the power button ) until some text appear 2-3 lines )
CWM recovery invoke differently.... ( hold Power & Volume down until you get 4 lines of text... do not let go anytime earlier then that )
~~~
extract that update.zip file ( my guess is this is where you went wrong... you didn't extract ? )
when you extract... make sure only the update.zip is put on your MicroSD card ( format FAT32 ).... no sub-folder...etc
Then insert into device and use the stock recovery method above.
if all else fail... get a different microSD card !!
then follow steps #2 and #3 from my previous post .
again... what's stopping you ??
I did the steps that E.B. recommended initially (directions followed religiously). Then I did what you posted (twice now,again, religiously - and yes I know how to, and properly extracted the update. !). Furthermore, I also tried a totally different SD card. 8gb pny VS 16gb San disk.
Hi, this is just a recompilation so that people don't have to get confused and scared.
Before your read this, please understand that this happened because of my own stupidity at somehow managing to delete the /boot from recovery 5.5.0.4, and caused a BLUESCREEN. When I tried to go to recovery, it went back to a pink screen. There were also other issues, such as a corrupted internal sd partitioning (warning, please be careful about doing partition, i highly recommend a proper partitioning zip which i'll link later in the post). In the end I was able to revive from the soft brick, and continued on to reinstall CM10.1 (it was version 7 at the time of the crash)
OKAY, let me repeat. Probably at this point you have a phone that has bricked. But if you can access PINK SCREEN, you're in luck (EVEN IF YOU DO NOT HAVE USB connection, its fine, as long as your EXTERNAL SD CARD is still accessible, physically.)
I'll put the stages in below:
WARNING I am not responsible for any loss, damage, or earthquakes or whatever crap that happens. Do this at your risk. Before you proceed, PLEASE OPEN THE BATTERY AND LOOK INTO THE BACK OF THE PHONE AND MAKE SURE IT SAYS MODEL: U8800 NOT U8800H, NOT U8800PRO. THIS IS FOR U8800 (okay, I admit i'm using U8800H but this is just an exception, probably)
PREPARATION:
STAGE 1: Getting the PINK SCREEN and booting into 2.2 Froyo / 2.3 Gingerbread
STAGE 2: Getting the TOUCH RECOVERY / CLOCKWORK RECOVERY, ROOT and SUPERUSER into the phone.
STAGE 3: Flashing the recovery, the partition, and the firmware
STAGE 4: Miscellaneous
PREPARATION
Click to expand...
Click to collapse
There are a few things that you need to prepare before hand.
1. A working computer (in this case i use windows)
2. Huawei USB drivers for windows. http://www.mediafire.com/?5z6i5cv8l6br292
3. Huawei Gingerbread base 528 ROM (this is BOOTLOCKED but don't worry, we can fix it just read up)
http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDEyNTU=
4. BLEFISH's "get back your pinkscreen" zip file (to be used with item 3, listen!) http://forum.xda-developers.com/showthread.php?t=1457490
5. Super One Click http://www.multiupload.com/9AJDSU1Q11
6. Blefish's recovery.img for the CLOCKWORKMOD recovery
7. Forumber's PARTITION.ZIP (the better option thus far) http://forum.xda-developers.com/showthread.php?t=2145187&page=124
8.. A ROM OF YOUR CHOICE (http://forum.xda-developers.com/showthread.php?t=2166353) as for me i'll just wait for Blefish to release his version of JB / CM re-write.
Now we're done, let's proceed
BEFORE YOU BEGIN:
*credits to forumber2*
Forumber2 wrote in one of the responses (not in this thread) that caught my attention. Apparently, if you're using a B158 bootloader, you can still access the STORAGE if you remove the battery and plug in USB for 1 minute.
forumber2 said:
In Blue screen,connect your phone to PC and wait 1 minute. A storage will show if you was in B518 bootloader. If the storage shows,please report here
Click to expand...
Click to collapse
I am not sure what steps to take this (it is a new information for me) but I presume you can immediately restore the TCRW from there. Have to ask forumber2 though.
STAGE 1: Getting the PINK SCREEN and booting into 2.2 Froyo / 2.3 Gingerbread
Here are the steps.
1. Install the HUAWEI drivers for the phone, and also SUPER ONE CLICK for windows.
2. Take out the U8800's EXTERNAL SD CARD, and plug it into computer. (use a card reader if you don't have)
3. open (UNZIP) the downloaded OFFICIAL GINGERBREAD ROM. Inside it should be a manualand a folder called "STEP 1", and inside folder "STEP 1", another folder called "DLOAD".
3a) COPY the "DLOAD" folder (and its content) and place it into the ROOT of your EXTERNAL SD CARD. that means from your computer it should read like this: (when you navigate)
X:/EXTERNAL SD CARD/DLOAD/UPDATE.APP
(X is the name of the drive)
4. Unmount the EXTERNAL SD CARD, and then slot it back into the U8800 phone.
5. Pull out battery.
6. Stick USB into the port, and into computer. (WITHOUT THE BATTERY)
7. PRESS VOL+,VOL- and POWER together (Reboot into pink screen)
FIRMWARE UPDATE PROGRESS. it should be 1/2 then 2/2.
"Do Not turn off the device".
AFTER finishing step 4 (it takes some time)
there will be a "TICK" and it will say "RESTARTING".
QUESTION What if I can't? It doesn't work?
ANSWER There's another trick. Pull out the battery, plug the USB wire in (YES, just plug in without battery) and then boot into recovery. This should work. Assuming it does not, get another USB cable with data capabilities, and USB 2.0 ready port on the computer. This should provide MORE POWER to the phone (the phone has a weird failsafe system where it would not proceed with upgrade if the power is too low)
REASON: HUAWEI wanted the customers to have a simple update process, so they created the entire thing to just be unzip, plug in, and wait. Yeah. I know, you'll feel weird especially when other phones seem to be super sophisticated at this part and Huawei made it so easy. Even the remove the battery part. Yes.
QUESTION: But what if i'm stuck at 1/2? goddamnit?
ANSWER This did not happen to me with the file. Like I said, again, it depends on the firmware. What I've read and understood is that there is a possibility of 1) bad firmware (need to download another firmware) or 2) EXTERNAL SD CARD is badly formatted (please use an Android phone / tablet to format just to be sure) There's a thread with specific discussion about this but it was lost on my notes, but that's the gist about it. What I'll suggest you to do is download the 2.2 Froyo then upgrade back to 2.3 Gingerbread. Some people have made it through this stage by doing everything from 2.2 Froyo itself.
Reason: I'm not so sure what is wrong, but this is one of the irregularities that posters have asked when unbricking the phone.
NOTE:
After the installation part, it should restart itself a few times. Basically, after the big "TICK" and "RESTARTING", it will continue to restart again, and again, and again, and again. Then finally it should boot up properly, and then the HUAWEI logo, then the flying dust animation, then the Huawei lotus flower glowing animation, and then boot up into 2.2 Froyo or 2.3 Gingerbread (depending on your firmware)
QUESTION: Okay, I see the boot looping. However, it just boot loops, and does nothing. At times i see the animation stop. Something must be WRONG!
ANSWER This happened exactly to me. The answer was that for some reason the pinkscreen update DID not format cache and data, as well as dalvik, etc. This is a recovery issue. The way i solved this was, that I re-did the update (making sure that it really did update properly into the official stock rom), then wait for the boot animation loop, (which happened) Then, the next step was like this:
1. TURN off the phone.
2. Plug in battery (or remove it)
3. Plug in USB (yes, again!)
4. Hold POWER button and VOLUME UP button.
If you can somehow boot into a blue colored Android system recovery *3E* screen. This one is the recovery with menu, but it is HUAWEI's recovery.
5. FORMAT CACHE, FORMAT DATA
6. REINSTALL THE official ROM, (YES wait again for the "TICK" and "RESTARTING", then it should restart a few times, then boot up. Have patience and faith!
*note: apparently as noted by aashi02 when the said user was unbricking the u8800, the 3E recovery has a factory data reset which somehow clears up the entire phone and enables the phone to properly work with the stock factory-default firmware (instead of crashing again and again and again in 2nd boot onwards). So I would presume that after first boot, one would have to again boot into recovery and do a factory reset (or do it while in the settings in first boot). Not sure if there are any users to encounter "2nd boot force close syndrome" after this. (if there are, please tell me)
The phone should have booted. If it doesn't, please tell me. I can't help much but I'll try to record as many possible errors and steps to overcome it, if i see responses from others and proven to work.
STAGE 2: Getting the TOUCH RECOVERY / CLOCKWORK RECOVERY, ROOT and SUPERUSER into the phone.
Once you've got into the GINGERBREAD / FROYO, follow this thread
http://forum.xda-developers.com/showthread.php?t=1420728
Or I'll record the instructions here
Thatguy said:
Rooting the U8800 with SuperOneClick v2.3.3
1) Dial: *#*#2846579#*#*
2) Go to projectmenu > background settings > log settings > log switch > set Log on
3) Reboot Phone
4) Switch USB Debugging ON
5) Download SuperOneClick v2.3.3
6) Plug your U8800 into your computer but DO NOT mount SD Card.
7) Run SuperOneClick and press the ROOT Button, and let it do its thing (say yes to install drivers if asked).
8) Your phone should now be Rooted.
9) You can now go back and turn logging off if you want.
Click to expand...
Click to collapse
The next step immediately after this is NOT TO RESTART the phone, but to install the CWM
Thatguy said:
Installing ClockworkMod 5.5.0.4 on your U8800
1) On your U8800 go to Settings > Applications > Untick Fast Boot (if ticked)
2) Download Blefish's ClockworkMod from HERE (ClockworkMod v5.5.0.4)
3) Copy the recovery.img from computer to your SD Card.
4) Using Remount mount the .cust_backup/image folder as RW.
5) Using ES File Explorer or File Expert copy the recovery.img from the SD Card to .cust_backup/image (replacing existing)
6) ClockworkMod v5.5.0.4 will now be Installed on your U8800
7) Turn on your U8800 while holding [VOL+] to load ClockworkMod Recovery (keep holding [Power] + [VOL+] until ClockworkMod Loads)
Note: if you have a Synaptics screen you have to use the [VOL] buttons to navigate and [Power] button to select an option.
Click to expand...
Click to collapse
QUESTION: Okay, somehow somewhere when i boot the phone for the first time, its okay. Second time, everything goes to hell (Force Closure, errors, etc, i can't press anything!) Something must be wrong again! You suck!
ANSWER Well, yes, this happened to me. Again, please read the guide. I said, no reset. Just do everything in one GO. That's how i fixed the problem.
NOTE: by now you should be able to boot into CLOCKWORKMOD recovery.
STAGE 3: Flashing the recovery, the partition, and the firmware
This is where we want to go to, and this is where you want to fix all the problems. I should not need to elaborate here, but if you're reading this part, you can now close this thread and go to the ROM of your choice and install as per THEIR INSTRUCTIONS:
QUESTION: Wait a minute. Something's fishy. THAT EASY? You screwin' with me, noob?
ANSWER Technically it should. There should not be any other problems UNLESS you somehow again delete the /boot. NEVER EVER DELETE /BOOT. If you have installed any firmware higher than 518 (B522 and above) firmware, then you need to do the next step:
NOTE: HOW TO INDENTIFY your firmware base
This is from my own Android "about" screen:
Android version
2.3.5
Baseband version
404020
Kernel version
2.6.35.7-perf
[email protected] #1
Build number
U8800V100R001C00526G001
Click to expand...
Click to collapse
Notice the 526 in there? it means i installed base 526
QUESTION: Wait a minute. You asked me to download that frickin' partition.zip and what do you expect me to do?
ANSWER Read the answer to the next question.
QUESTION: Help! I haz problemz! i cannot install ROM! it haz fail / not enough space on my internal SD! helpz!
ANSWER IF, and I repeat IF, you're reading this, then you're probably installing something way bigger than the original partition's system partition. To help you imagine, think of it as a 10-car train. The basic idea is instead of 1 engine, you now put 2 engine, and sacrifice 1 compartment car (that means from "1engine-9car train" into a "2engine-8car train". This is where you'll find the partition.zip helpful.
BUT BEFORE YOU DEAL WITH PARTITION.ZIP, do install "GET YOUR PINKSCREEN" by Blefish, read it here:
http://forum.xda-developers.com/showthread.php?t=1457490
I quote Blefish:
Blefish said:
In the newer official ROMs, Huawei included a "feature" to lock the bootloader and therefore, get less bricks. But happened the opposite - if your cust partition gets corrupted/deleted, you'll have a high change of bricking your device.
The new bootloader is not actually locked, it's changed to use QPST (Qualcomm Product & Support Tools). As it needs a code, we can't use it.
This method flashes the B518 bootloader straight to your phone, so you will get back USB.
Apply only if you have upgraded your phone to B522 or newer. You may have a custom ROM on top, but the base has to be B522 or newer.
Tested by myself on B522, B526 & B528.
The steps required to get back pink/blue screen USB:
Automatic flashable zip is pretty much fail proof, but I have warned you.
Automatic method (recommended):
Download update-B518-bootloader.zip from MediaFire.
Save it to the root of your SD Card.
Start the phone in recovery mode (recommended recovery is 5.5.0.4)
Select "install zip from sdcard"
Select "chooze zip from sdcard"
Select the zip you downloaded before.
Select yes.
Reboot and enjoy!
Click to expand...
Click to collapse
Now that you've fixed the locked bootloader on 522/526/528, now its time to do the partition. zip
Follow this thread:
http://forum.xda-developers.com/showthread.php?t=2145187&page=124
I quote NERDO
Nerdo said:
RePartition
Note:After this operation;Phone's /data partition will be 1.4 GB,/system will be 360 MB /HWUserData (2GB Internal Memory) will be 1.02 GB and formatted
1.Download partition.zip in the attachments and copy to sdcard
2.Goto recovery
3.advanced > reboot recovery
4.Wipe data factory set
5.mounts and stroage > format system
6.advanced > reboot recovery
7."install from sdcard" and select partition.zip
*Phone will reboot to recovery after install partition.zip
7."install from sdcard" and select partition.zip again
*Phone will reboot to recovery after install partition.zip again
Click to expand...
Click to collapse
The KEY IDEA here is that you need to flash the partition 2 times.
B]QUESTION:[/B] Now what?
ANSWER Install your custom ROM as per your custom ROM's instruction.
B]QUESTION:[/B] No, really. Now what? I want to double make sure, because i don't trust you, noob.
ANSWER Okay, you need to format and clear, not everything. Follow these steps.
ROM Installation:
Use only Forumember partition.zip.
1. Copy package to SD card
2. Boot to recovery
3. Full wipe (data, cache, dalvik,) <--- This one is in main menu
4. Format /system, /data, /cache <--- This one is in ADVANCED MENU. NO NEED TO MOUNT and DISMOUNT, and DO NOT FORMAT BOOT
5. Reboot recovery
6. Install the custom ROM (and gapps if needed.)
7. Reboot. Take a deep breath.
The phone should now boot into your new custom ROM.
As per writing, i booted into CM10.1 v7 by ilyaa299. Still waiting for a better JellyBean ROM though.
Congratulations, enjoy your unbricked phone!
STAGE 4: Miscellaneous
Not all ROMs are created equal. And none stand peer to peer. No matter how many seasons have come and go, please remember the ROM is only alive as long as its developer remains commited to its releases and updates. Please thank them. They will appreciate it.
For most usage, I have no issues, except the piss poor memory of 300++MB. I have not found a way to solve this. There are APPS that claim to create a virtual RAM, but if you don't have class 6, or class 10 External SD card, don't bother, and from what I read it'll shorten your EXTERNAL SD CARD's life A LOT. use it at your own risk.
To help alleviate the situation, i installed "auto memory manager" and also "greenify". This has helped me a lot. Auto memory manager deals with current usage, but "greenify" deals with the apps that are inactive, but greedily and stealthily use RAM and hog it (as if they're some royalty of some sort)
One of the greatest points of this phone is that it has a SUPERIOR camera (even if its only 5.0mp) and it has superior HD viewing (watch movies, youtube, etc, in FULL HD, where other phones, even the MORE expensive ones cannot do)
Try to avoid apps that uses 'download as a process" like mangawatcher, because i somehow managed to fry my EXTERNAL SD card (total death) because i left it overnight to download some manga, and then it froze. Then again it probaby may be a ROM issue (its a custom ROM) but just be careful! I lost a 16GB class 4 SD card.
CREDITS:
Thanks to all that have posted to help me, big thanks to (by alphabetical order)
bdgraue
forumber2
kilroystyx
rqmok
reserved thanks to people named in the process written, especially forumber2 for his help in his post and his partition.zip. Without his post, he would not have triggered my thought process in thinking out of the box to unbrick my phone.
and a big thank you to YOU for reading, and (IF) responding to this thread to help make this thread better.
i made the same mistake, i would guess you formatted the /boot too.
you now have to take an original huawei rom, 2.3.5 will be suitable, and follow some instructions you should find in this forum already.
than u have to root your device again and install the rom you need.
Yes, you need to install the official 2.3.5 firmware again. Download it from Huawei's official website.
http://forum.xda-developers.com/showthread.php?t=1420728
in this thread you find almost every information about rooting the device.
and http://forum.xda-developers.com/showthread.php?p=22682229#post22682229 there are the instructions about installing the original rom
gl&hf
still does not work (pink screen)
Hello everyone, I did my homework by searching, but alas I could not revive my phone. (U8800)
How did it bricked: Installed CM10.1 v7, (ran fine, had to re-flash because i read that one must do /format system, /format cache, somehow probably i deleted something i wasn't supposed to, and now its bricked)
Symptoms:
1. Press power button: Blue Screen. This includes Power button and volume + together. Blue Screen. (NOTE: Huawei logo flashes briefly for less than 1 sec before screen goes blue)
2. Press power button and volume + & - together: Pink Screen.
3. (new#)Cannot access from Windows 8 (I have drivers installed, will not detect. Every time i plug the phone into win8 the phone boots up blue) but can't see internal SD.
What I know:
1. This is a U8800
2. CWM 5.5.0.4 was installed (it was bricked after i clear and format, and cannot re-enter the CWM anymore, it goes into pink screen instead)
3. Internal SD is not read-able. (this was documented when i wrote my issue, another forumer by the name of rqmok says its fine because i updated the partitioned.zip, therefore even if it cannot be read, but if it can be accessed from the android file browsers, it is okay. I believe him)
4. I can boot up the huawei + bluescreen, but no
What I did:
1. Because i was at CM10.1 v7, i renamed the entire thing as update.zip and place into external sd root folder . RESULT = nothing. just pink screen
2. grabbed an update (Gingerbread) from XDAFORUM u8800 wikipedia page (the international version), place as update.zip in external sd root folder. RESULT = nothing. just pink screen.
3# (new) I unplugged battery and the external SD, plugged the phone via USB to computer. Boot up (few seconds of Huawei logo) then bluescreen.
Yes, I understand that others have asked about this and somehow revived. What I've read, and understood was:
1. Blue screen = something about ./boot was deleted, and needs to be reinstalled.
2. Pink screen = still safe, has a chance to revive the phone.
What i do not understand:
1. Put ROM files as update.zip, but pink screen does not flash into any form of recovery.
2. Somebody from somewhere said use something called ubuntu / bt5 to "dive" into the phone's internal SD. (I don't know how to do this, and from what i understand it is risky because it involves partioning the internal SD again.
3. Any other way to rescue my phone?
What I would like to ask is some form of step by step help.
I would be very grateful if anyone can lend me some assistance. This is my first android phone (yes i'm a poor fellow) and its not even a week old. I do have an AcerA500 tablet and i have been able to update that tablet to any custom variations (ever since i owned it roughly 2 years ago), so i'm pretty confident that i am good in following instructions)
EDIT:
Okay, i'm able to update the firmware by doing the following:
1. PUT "DLOAD" folder into EXTERNAL SD, root.
2. Pull out battery.
3. Stick USB into the port, and into computer.
4. PRESS VOL+,VOL- and POWER together (Reboot into pink screen)
FIRMWARE UPDATE PROGRESS. it should be 1/2 then 2/2.
"Do Not turn off the device".
AFTER finishing step 4 (it takes some time)
there will be a "TICK" and it will say "RESTARTING".
And then the HUAWEI FLOWER (no animation).
And it repeats itself....
What do I mean by repeat itself?
1. BLANK
2. HUAWEI WITH FLOWER (NO ANIMATION)
After this, there is a green android picture and says "FORMAT /CACHE" and something like that.
Then it goes blank and huawei flowr (no animation) again, and again, and again.
*NEWv2*
I can enter the the blue colored Android system recovery *3E* screen.
formatted / data reset
it has formatted all (at first cannot format cache, causes many problems, now finally fixed). So somehow I managed to format data and clear cache.
It finally reboots. It starts up. And I thought problem over. It was not.
First time boot up was okay. It asks me to set up android, etc. Second time boot up, it will get stuck in a boot loop. Help!
I'm stuck here. Any help?
Can you access to phone from PC while pink screen?
forumber2 said:
Can you access to phone from PC while pink screen?
Click to expand...
Click to collapse
no, unfortunately no.
When I press the volume + up buttons, i can access the blue native recovery.
I updated my post as above.
Can you help me?
NEW:
again, it boots! But 2nd boot will cause issues like process.android.acore and process.google something something has stopped.
can you guys help me on this last one? (i've recorded what i've done and what happened and how i fixed it in previous post. will edit all posts later to do a proper walkthrough.
badiyee said:
no, unfortunately no.
When I press the volume + up buttons, i can access the blue native recovery.
I updated my post as above.
Can you help me?
Click to expand...
Click to collapse
Can the recovery detect sdcard?
forumber2 said:
Can the recovery detect sdcard?
Click to expand...
Click to collapse
yes, the recovery can detect the EXTERNAL SD.
But Internal SD, no. but when i click wipe data, and wipe cache (i think it does it on internal sd) it has no issues.
Again, first time boot =OKAY!
2nd time boot = F.C, all apps.
list of errors said:
The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly. Please try again)
The process android.process.acore has stopped unexpectedly. Please try again
Click to expand...
Click to collapse
I suspect the errors happen because of the fact that i installed JELLY BEAN CM10.1 v7 before, and flashed the gapps too.
Do i need to reflash gapps to GB version after formating the system? What should I do?
badiyee said:
I suspect the errors happen because of the fact that i installed JELLY BEAN CM10.1 v7 before, and flashed the gapps too.
Do i need to reflash gapps to GB version after formating the system? What should I do?
Click to expand...
Click to collapse
did you flash the original huawei rom first? or do you try to flash some custom rom immediately.
which version of original rom do you flash, when u do so?
bdgraue said:
did you flash the original huawei rom first? or do you try to flash some custom rom immediately.
which version of original rom do you flash, when u do so?
Click to expand...
Click to collapse
I flashed the original Huawei Rom first. I know i cannot flash custom rom because the recovery is *3E* recovery, not the CWM/TCW recovery.
any ideas?
I've recorded the errors.
Should I try to reinstall the original HUAWEI ROM again?
okay tried flashing Gingerbread GAPPS (FAIL SIGNATURE!)
formating data and cache again...
*ADD MORE INFO*
Huawei ROM via phone status says this
Android version
2.3.5
Baseband version
404020
Kernel version
2.6.35.7-perf
[email protected] #1
Build number
U8800V100R001C00526G001
Did I do any mistakes?
badiyee said:
Should I try to reinstall the original HUAWEI ROM again?
Click to expand...
Click to collapse
thats what i would do. first flash the huawei rom. start it, look that it works properly. after that i would root the phone, start again and look that all work as expected. then install rom manager and flash the cwm recovery, start again. boot into recovery, start again, always look if the phone is still working as it should. than take a good rom(aurora or cm10.1 v7) and flash it.
as often as you try it out and test if it all works as expected as early you can find out where errors come from.
only flash gapps if the rest works fine.
(which version of gapps do you try to flash? gapps-jb-20130301-signed.zip worked best for me over here)
Edit: http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDEyNTU=
this ist official 528 which worked very well for me. maybe 526 isnt the best suitable.
bdgraue said:
thats what i would do. first flash the huawei rom. start it, look that it works properly. after that i would root the phone, start again and look that all work as expected. then install rom manager and flash the cwm recovery, start again. boot into recovery, start again, always look if the phone is still working as it should. than take a good rom(aurora or cm10.1 v7) and flash it.
as often as you try it out and test if it all works as expected as early you can find out where errors come from.
only flash gapps if the rest works fine.
(which version of gapps do you try to flash? gapps-jb-20130301-signed.zip worked best for me over here)
Click to expand...
Click to collapse
This is the SAME ERROR i'm facing.
http://forum.xda-developers.com/showthread.php?t=2146478
I tried flashing gapps-20110828 it gave error. I also have the gapps jb20130301 file as well. But when i flash the GB gapps it says failed signature verification
QUESTION: could the partition be a problem because i used custom partition!
THANK YOU!
Thanks to everyone!
I have fixed the problem.
I will now re-write the ENTIRE post to help others that have similar issues as mine so that they would not need to be lost like I was.
Thanks again everyone!
badiyee said:
Thanks to everyone!
I have fixed the problem.
I will now re-write the ENTIRE post to help others that have similar issues as mine so that they would not need to be lost like I was.
Thanks again everyone!
Click to expand...
Click to collapse
I'll suggest you to install the patch from blefish if you are using B522, B526 or B528 as rom base.
You don't know when will be helpful to have a bootloader unlocked.
Find here: http://forum.xda-developers.com/showthread.php?t=1457490
kilroystyx said:
I'll suggest you to install the patch from blefish if you are using B522, B526 or B528 as rom base.
You don't know when will be helpful to have a bootloader unlocked.
Find here: http://forum.xda-developers.com/showthread.php?t=1457490
Click to expand...
Click to collapse
Question, how would I know my base ROM? I have read the thing, but there isn't a way in my status to know that its a B522, B526 or a B528 based ROM.
Answer: Look at the code of the installer:
E.G:
U8800V100R001C00526G001 means I have base 526 installed (LOCKED BOOTLOADER)
badiyee said:
Question, how would I know my base ROM?
Click to expand...
Click to collapse
badiyee said:
Huawei ROM via phone status says this
Android version
2.3.5
Baseband version
404020
Kernel version
2.6.35.7-perf
[email protected] #1
Build number
U8800V100R001C00526G001
Click to expand...
Click to collapse
at least after installing you will find the information in the area yoou mentioned yourselve.
if you use the original rom, the version should be in the filename. (U8800_Android 2.3 V100R001C00B528G001%28通用版%29.zip for me)
Wait, is your current recovery CWM recovery? If yes, try installing Aurora ICS. If no, first try rooting your phone and installing CWM recovery.
badiyee said:
Question, how would I know my base ROM? I have read the thing, but there isn't a way in my status to know that its a B522, B526 or a B528 based ROM.
Answer: Look at the code of the installer:
E.G:
U8800V100R001C00526G001 means I have base 526 installed (LOCKED BOOTLOADER)
Click to expand...
Click to collapse
Official Huawei GB roms have 3 different bootloaders, B517, B518 and B522, the first two are unlocked this mean you easily can reach to eMMC via pink screen. For B522 bootloader that comes into rom B522, B526 and B528 Huawei changed the way how to communicate, so we can’t reach eMMC via pink screen mode. To check if it is unlocked in pink screen mode connect to PC, if you can see the folder “image” your bootloader is unlocked.
Blefish explained in his topic that you have more chances to recover your device from soft-brick if you have a unlock bootloader because you are able to restore your device with a previous full backup done with “dd” command or with a similar program used in windows platform.
Change partition size have a high risk to corrupt them and get a soft-brick.
To have more chances to recover my device I usually follow some steps before start play with roms, see my checklist:
- Install B528
- Root the device
- Imei backup (if I haven’t done previously)
- Install CWM
- Flash Blefish’s patch, alternative I use my patch because I need my phone with SIM unlocked
- Full backup (if I haven’t done previously)
- Ready to play
rqmok said:
Wait, is your current recovery CWM recovery? If yes, try installing Aurora ICS. If no, first try rooting your phone and installing CWM recovery.
Click to expand...
Click to collapse
I think at the time of writing AURORA ICS is the most stable, usage-ready, and most complete ROM as of writing. In the future hopefully the newer ROMs like Jelly Bean, Key Lime Pie and others will be able to fit in, and be a PROPER, USABLE ROM just like how AURORA ICS and the MIUI ICS was for this phone.
kilroystyx said:
Official Huawei GB roms have 3 different bootloaders, B517, B518 and B522, the first two are unlocked this mean you easily can reach to eMMC via pink screen. For B522 bootloader that comes into rom B522, B526 and B528 Huawei changed the way how to communicate, so we can’t reach eMMC via pink screen mode. To check if it is unlocked in pink screen mode connect to PC, if you can see the folder “image” your bootloader is unlocked.
Blefish explained in his topic that you have more chances to recover your device from soft-brick if you have a unlock bootloader because you are able to restore your device with a previous full backup done with “dd” command or with a similar program used in windows platform.
Change partition size have a high risk to corrupt them and get a soft-brick.
To have more chances to recover my device I usually follow some steps before start play with roms, see my checklist:
- Install B528
- Root the device
- Imei backup (if I haven’t done previously)
- Install CWM
- Flash Blefish’s patch, alternative I use my patch because I need my phone with SIM unlocked
- Full backup (if I haven’t done previously)
- Ready to play
Click to expand...
Click to collapse
Ah, i forgot about the IMEI backup. But since mine wasn't an issue (just missing serial number, but can be found at the sticker behind phone (inside) anyways haha.
So, this is my first time trying to mod. Actually, this can be the first time I got an android phone. So I want to ask/confirm things first, since I'm not too sure.
I want to use cyanogenmod 11 ( http://forum.xda-developers.com/showthread.php?t=2519448 )
The phone is
Model: LG L5 E612
Android Version: 4.0.3
Kernel: 3.0.8-perf
Download
BETA 9: https://www.mediafire.com/?v6we6p3h7bn7vop
Gapps (both Art & dalvik) : http://forum.xda-developers.com/show....php?t=2397942
e612 user install latest kernel from here to get deep sleep working in cm-11.0 :
https://www.mediafire.com/?0vo1fzfvilr67dc
Install instructions:
Note : CM-11 is only for jellybean (v20) baseband. If you are on ics (v10) baseband flash v20 baseband from this thread and then make sure you have cwm 6.0.4.8 recovery installed. from beta 4+ you must need cwm 6.0.4.8 to flash. download cwm 6.0.4.8 from here
Wipe data and cache
Flash the CM11 zip
Reboot
boot into recovery mode
Install gapps
Reboot
Click to expand...
Click to collapse
According to Lifehacker, I have to root my phone first, but I don't know how to do it. I found this guide, but it says it doesn't work anymore. Does UnlockRoot works? It doesn't have LG L-series in its list.
Second, I have to go here and download v20 basebands since my Android version is 4.0.3
Then I have to download cwm 6.0.4.8 from here.
The problem is I don't know what to do with those two files. How and when should I install the new kernel?
CMIIW, but do I just put the zip file on phone's memory card?
Factory reset/wipe is next, I think?
The next step is rebooting while pressing volume buttons, into recovery mode, right? then select the mod from the option (Again, do I just put the zip into memory card?).
I'm sure I missed many things, so I hope you can help me.
Thanks before.
I am not responsible for damage to equipment ! If you don't know something or you are not sure ask !
Follow the steps like on website below to install ROM with root and CWM :
http://androidteen.com/lg-optimus-l5-e610612-android-4-1-2-how-to-root-and-install-custom-recovery/
If you have installed ROM from the tutorial above follow the steps below :
1. Download ROM which you want and copy to SD Card ( v10 baseband 4.1 +, v20 4.4 kitkat + )
2. Go to CWM ( Hold Volume down, Home and Power button )
3.Update CWM from link below :
http://forum.xda-developers.com/showthread.php?t=2163698
3. Restart CWM.
4. Do wipe data and cache.
5.Install baseband v10 or v20.
5. Install ROM and the kernel if it has included.
6.Restart phone and wait.
Thanks. But after following several links, I got here. It shows the tutorial for 4.0.3, I believe I should use this one instead? Your link is for 4.1.2. Besides, the root package is smaller (3MB) compared to the one in your link, 360MB. Can use it instead?
The instruction told me to copy recovery.img at CWM step. I have CWM 6.0.4.8 from the cyanogen thread, but the recovery.img size is bigger (7MB vs 5MB), is it the same, or I should be using the 5MB one from rooting tutorial? If they're the same, I prefer using the 7MB one from cyanogen thread.
About Backup, LG PC Suite offer me a backup option, is that enough, or I should use/install another backup application?
THanks again
fathuzzaman said:
Thanks. But after following several links, I got here. It shows the tutorial for 4.0.3, I believe I should use this one instead? Your link is for 4.1.2. Besides, the root package is smaller (3MB) compared to the one in your link, 360MB. Can use it instead?
The instruction told me to copy recovery.img at CWM step. I have CWM 6.0.4.8 from the cyanogen thread, but the recovery.img size is bigger (7MB vs 5MB), is it the same, or I should be using the 5MB one from rooting tutorial? If they're the same, I prefer using the 7MB one from cyanogen thread.
About Backup, LG PC Suite offer me a backup option, is that enough, or I should use/install another backup application?
THanks again
Click to expand...
Click to collapse
I don't know that. I did this from 4.1.2 JellyBean. If you are on 4.0.3 version follow the guide from the link. Or hold on for somebody who did this from 4.0.3 and knows more.
Doing it from 4.0.3 is much harder.
You must install root then unlock bootloader then install CWM (that 7mb file will do the trick) then u must to flash BASEBAND to v20 to be able to use CM11.
Much easier is to flash your phone via KDZ with v20d+root+cwm.kdz (wich have buildin root cwm unlock boot etc) then u have to just update cwm to 6.0.4.8/6.0.4.9 via zip then flash cm11 no need to think about basebands etc.
Just flash your phone with v20d+root+cwm.KDZ and problem away
Alright, I think I got it. I managed to flash CM11, although got a little trouble when unlocking bootloader. I'll remember KDZ if I ever need to redo the process again
Anyway, I can't seem to boot into recovery mode anymore. holding volume+power+home doesn't get me anywhere, while reboot recovery from adb/terminal gives me neverending LG-Logo loading. Did I do something wrong? The rom and everything works perfectly before, only this recovery mode that doesn't work, which means I can't flash anything anymore...
EDIT: I got into recovery mode. I have to 'su' from phone terminal, not from adb or anything else.
But now, after I installed Google Apps, the touchscreen stopped working. I don't know what to do anymore...
Well i dont understand what u did in first sentence.
U installed CM11 and after that u wanted to unlock bootloader? thats wrong.
Let me Tell it again.
Flash your phone with v20d KDZ via KDZ tool. THATS IT no need to unlock bootloaders etc
Put this on your SD Card http://www.mediafire.com/download/0ywu6ri06c94l4z/cwm6.0.4.9.zip
Turn your phone OFF.
VOLUME DOWN + HOME + POWER until vibration then release power to enter recovery.
WIPE DATA/CACHE
Advanced > WIPE DALVIK
Install from ZIP
Now choose secondd option to browse SD Card
Point cwm6.0.4.9.zip and flash it.
Reboot to system
Turn OFF again
Enter CWM flash CM11.
Reboot
No, the first sentence was from before I knew about KDZ. I was still trying to root and unlocked bootoader, but I got a wrong file. e612 is using different bootloader from e610, but e612F is using e610 one instead of e612, hence I got the boot loop. I checked model number in Android setting and on the box, it says e612, but when I wanted to open the battery, there's a model number on the phone, saying it's e612(f).
But everything works perfectly now. I get my CM11 working. The broken touchscreen also works (weirdly, after I put my SIM Card). Except one thing: I've never been able to enter recovery mode from start up using volume+power+home, even until now. I always have to boot into phone, then choose restart into recovery mode.
CM 11, CWM 6.0.4.9.
Anyway, if I ever want to re-flash CM or another room, or have some broken thing that I have to wipe /system, do I have to re-flash v20, or just the rom?
Also the kernel, if I want to flash a kernel, do I just flash it without any need of special order (like wipe cache first, then kernel, the rom, etc.)
Just the ROM.
But if u format /system remember to have anything ready on sd card to flash right away because if u reboot phone with formated system woth out flashing new rom then well..... KDZ
KDZ only if your phone die in a way it will stuck at LG LOGO and even recovery wont work. Then KDZ. In any other situation when recovery work then only rom flashing via CWM nice and easy
So VOL DOWN + HOME + POWER (PREFERABLY IN THAT ORDER) then release POWER after vibration dont work for ya?
Mine phone under battery says e610/e612(f) wich is just clean e610 xD just saying.
struart said:
Just the ROM.
But if u format /system remember to have anything ready on sd card to flash right away because if u reboot phone with formated system woth out flashing new rom then well..... KDZ
KDZ only if your phone die in a way it will stuck at LG LOGO and even recovery wont work. Then KDZ. In any other situation when recovery work then only rom flashing via CWM nice and easy
So VOL DOWN + HOME + POWER (PREFERABLY IN THAT ORDER) then release POWER after vibration dont work for ya?
Mine phone under battery says e610/e612(f) wich is just clean e610 xD just saying.
Click to expand...
Click to collapse
I see. I'll make sure to back up it on the card then
Yeah, it does nothing. The LG Logo disappear, and the Back and Menu buttons are flashing forever (longest try is for about 3 minutes, still no result) until I release Power button, then the Logo reappear and continuing like normal boot. There's no vibration or anything like that.
Ah, mine is like that too. Then what should we choose if we get kernels/option for different types again in the future, e610 or e612? This half-hearted serial number is confusing :laugh:
Pure e610 nothing more. Its simply l5 with NFC and single SIM.
Strange when i press vol down then add home and power buttons flash then phone vibrates and i release power LG logo appear then i stop pushing anything and after 30 SEC 1 min im in cwm.
Wysłane z mojego LG-E610 przy użyciu Tapatalka
Ah, it works!
thanks a lot!
I read somewhere it was "Volume + Power, then hold Home when the light turns on"
There should be no "when the light turn on" =_=
THanks a lot!
I see.. CM11 disable/not tested NFC anyway, so it basically is really a pure 610
Yeah only Android Beam work from NFC module. NFC it self (with nfc tag) dont work since CM10.2.
so, cm11 beta 9.1 is unusable. the battery drain is too high, 10% in 2-4 hours with or without framework fix. my option is to revert back to beta 9 and unable to rec video/sound and unable tp use VoIP, or change to another rom.
do you have any other rom suggestion?
Lperia but on android 4.1.2 ( optima team ) AOKP, SlimKat ( CM11 ), mod of stock 4.1.2 but very very fast., and now i have unofficial CM11 4.4.3
Sent from my LG-E610 using XDA Free mobile app
I dont have such drain on CM11 with patch even without patch its not that high.
Check with some wakelock detector what keep your phone awake.
My top 4 are
google service (Mostly sync),
1013 (what is this? Type system(media), Mostly audiomix. I didnt touch aausio/music things),
Android system (again, audiomix),
and BlackBerry messenger
currently 50% in about 8.5 hours.
Google service shouldnt be even listed there even IF sync is on.
1013 i dont have it at all.
I think u suffer from google services 5.0 bug with cm. Download some proces killer and block SystemUpdateService and it will solve problem till next beta with updated sources from cm with fix.
Wysłane z mojego LG-E610 przy użyciu Tapatalka
i downloaded zapper task killer, but couldn't find the process systemupdateservice. I'll try another app later.
1013 and google service only appear if I check show system process from wakelocker detector settings.
my battery this morning, 96% in ~1hour, with the main culprit being Android, 1013, and bbm. beside bbm, the top 5 seems to be system related.
next update is.. next month, right?
What process from Android system and google services wakelock ur phone?
89% wake lol mine is 2% wake xD
Check with Battery Stats Plus in Wake section wich part of OS and wich process inside is creating problem.
[Q&A] [ROM][5.0.1] [12/14] DarkoBass PSD ROM [AOSPA 5.0] [SM4.8/4.9]{alpha}{dark mat
Q&A for [ROM][5.0.1] [12/14] DarkoBass PSD ROM [AOSPA 5.0] [SM4.8/4.9]{alpha}{dark material}
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.0.1] [12/14] DarkoBass PSD ROM [AOSPA 5.0] [SM4.8/4.9]{alpha}{dark material}. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Tnx for new room
Tomorrow will try.. anyway, nice to see domestic names
its buggy and lags alot, theme is nice and has potential, however, not too much of the ui is themed.
How to make screenshot? Power+volume down dosent work for me.
Hy. I think I found a bug. If it has been mentioned yet, than I am sorry.
So. Sometimes the recent button is going to be silly and stucks as clear all button. Is there a way to change the clear all button's position?
Thanks.
dephsone said:
Hy. I think I found a bug. If it has been mentioned yet, than I am sorry.
So. Sometimes the recent button is going to be silly and stucks as clear all button. Is there a way to change the clear all button's position?
Thanks.
Click to expand...
Click to collapse
yeah i know about this, somehow Inherited from Paranoid Android, hopefully they will fix it soon..
Some recents clear all options comming in next release yes
So I really want to try your Rom out but I'm on d801. I tried booting up other d802 roms with no luck. Even after installing a d801 kernel first still had no luck. I saw another user sayin he installed it on his d800 by installing the render kernel first. Will this work on the d801 by first installing the render kernel?
Rom is good but need help with something.
Hi. I downloaded the rom succesfully. But there is one problem. When i lock the screen, it opens itself when i move or touch it. Any Help?
good works
turkish language support?
Problem
Hello guys, first off ... I'm pretty new at this whole Android custom ROMs, rooting thing. So I screwed up. I tried installing the DarkoBas PSD ROM via ADB. My LG G2 D802 was rooted using StumpRoot app, then I couldn't get to the Recovery Reboot so I used an app, that worked and I wiped data and cache ... Couldn't find the Dalvik cache so I left that out. Next thing I connected it to the PC via USB cable and sent the .zip file through ADB, it took a while but it was transfered ok, the phone started preping itself and then the installation stopped and something like "Unable to unmount /sdcard" and "Unable to unmount /system". I thought "damn it, I'm gonna have to stick with the stock ROM". But it was even worse, after reboot the phone doesn't start up... When I hold down the PWR button the LG logo pops up and after few seconds a text appears under it saying "Security Error". And that's it, I can't get to the Recovery mode or Download mode (not that I could before). It doesn't even get detected by Windows, no 15HDDs or wrong ID in device manager, nothing. The only thing I can do is get to the "Factory data reset" (which doesn't help BTW) by pressing vol. Down and PWR, after the logo pops up I let go and hold vol. Up and Down... Guys it's bad and I'd appreciate any help I can get. Thanks in advance.
dont worry you will be able to recover. just seek help in those kind of threads, because this isnt rom specific. basicaly what u need to do is use the lg flash tool to flash stock again and then start over.
Can we have indibidual ringer/notification volume control?
abc001 said:
Can we have indibidual ringer/notification volume control?
Click to expand...
Click to collapse
yes, uploading right now
can i flash this rom if i have 4.4.2? or do i have to install 5.0.1 first??
i love the black theme!!
I find your work very well. go on like this. can you tell me when the next build comes out for lgg2
there has appeared an error. the display flickers and it was all black and white on the display and then the phone is turned off and turned on again by itself. can you please fix the next build. everything else is great. did great. just please fix this error. thank you man
Hy!
In the Layers app, can I set custom icon packs like Flex?
And if I can, how?
Thanks.
"Power button ends call" seems to be an option within 2 menus, Settings - Remix Settings - Buttons and Soft Keys, as well as Settings - Accessibility. They also don't seem to be synced.
One option remains off while the other remains on.
I appreciate your hard work and time spent on this ROM @darkobas.
May I also add, link ringtone & notification volumes option is not working for me when enabled. Ringtone is on low, option is enabled, yet notifications are coming in at a much higher volume.
Just letting you know, I can live with setting them individually but thought I'd share my experienced bugs so far.
robotic voice
hey that's good ... finally there's someone out there having the same problem as me ...
do you know already what kind of problem it could be ? baseband, build , or kit kat / lollipo problem ?