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.
Related
DELETED!
Don't want to risk anyone getting bricked, because of me giving you the wrong info.
Thanks for this topic, but I've a few questions:
- If I unlock the bootloader, can I still use TrackID or is it completly over?
- Which other Sony apps are effected (except WisePilot)?
- Can I re-lock the bootloader with FlashTool as written in the forums here to use TrackID again?
- Can I flash a new bootloader with FlashTool, too? I didn't read anything about it and I don't want to use any sony page.
- Currently I'm using Xperia CWM (from Google Play) with a stock kernel and different ROMs. It works so far. Is CWM included with every kernel?
1) Download TrackID from the market. That's a better and newer version than the one supplied with the ROM, plus it works even with an unlocked bootloader.
2) FB Like won't work if you've got the bootloader unlocked. But I hardly think that's a deal breaker.
3) Yes, you can relock the bootloader but the original TrackID still wouldn't work as you would have erased the DRM keys. (The newer version still works).
4) You can't flash a bootloader. You can flash kernels and ROMs.
5) Most custom kernels have CWM recovery within.
Cheers! Hope that answered your questions.
Swyped from my SE Xperia arc (LT15i) using Tapatalk 2
xtacy! said:
4) You can't flash a bootloader. You can flash kernels and ROMs.
Click to expand...
Click to collapse
This was a typo...
Did I mention that I'll flash a new kernel soon? I'll try it with FlashTool.
1. Can I unlock & root after official ICS update?
2. Can I install custom ROM using this(http://wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Arc:_Full_Update_Guide) method?
Just to be sure: I can only unlock the bootloader of my Arc S with the Sony-method? Is there another free way to do it?
In FlashTool I've to select "Flash" -> "Fastboot Mode" -> "Reboot into fastboot mode (via ADB)" -> "Select kernel to Flash" and flash the kernel file?
edit: All my questions were answered in the last hours.
hi, can i root my arc s with ICS with DoomLor method?
Hi,
I did steps 1& 2 (unlocking & rooting) but nothing seems to have happened. How can I tell if it worked? I followed everything to the T and got no errors.
Ive just checked and my bootloader is unlocked butthe pphone does not appear to have been rooted (I checked using a root checker app). Can you think of any reason for this? Should I just try again or could that cause me problems?
Thanks
edit:
Do I need to do step 3 & 4 before it is fully rooted? I assumed I could stop after step 2...
anybody? please help. im not sure if i should try to flash the rom if it isn't rooted yet, or is that what i need to do to complete the process?
soooo confused
twelveways said:
anybody? please help. im not sure if i should try to flash the rom if it isn't rooted yet, or is that what i need to do to complete the process?
soooo confused
Click to expand...
Click to collapse
The root method posted doesn't work with the latest ICS (431) update.
I'm running Android 2.3.4 and the build number is 4.0.2.A.0.62.
thanks for that
i have arc s and when i tried the way you say
it says already unlocked
is that normal ??
or there is a problem ??
This has only been tested on Arc S with 4.0.3 firmware.
THIS WILL NOT WORK ON THE LATEST FIRMWARE (4.0.4)
Sorry for not answering guys, thought my thread was dead.
Will bookmark.
Oscar-Mark said:
THIS WILL NOT WORK ON THE LATEST FIRMWARE (4.0.4)
Click to expand...
Click to collapse
Worked for me.
Update: Thread edited a bit.
If anyone has got this working on the latest (4.0.4) firmware please tell, (reply, no PM)
please can you reup the part of kernel flashing? i thought this thread is still existing, i deleted the hole system to prepare it for new rom and kernel flashing and no its deleted?! please help me my phone doen't boot i need a tutorial to flash the kernel, this tut herer was extreme good and noob friendly, please reuppload it :C
Google fetishist said:
please can you reup the part of kernel flashing? i thought this thread is still existing, i deleted the hole system to prepare it for new rom and kernel flashing and no its deleted?! please help me my phone doen't boot i need a tutorial to flash the kernel, this tut herer was extreme good and noob friendly, please reuppload it :C
Click to expand...
Click to collapse
To flash a kernel:
This will wipe all your data
Turn off your device, make sure you have atleast one ROM on your SD card in case anything goes wrong.
Put the kernel boot.img in /fastboot/fastboot_with_Android_USB_file/fastboot folder.
Press and hold SHIFT button while right clicking at an empty space in the /fastboot/fastboot_with_Android_USB_file/fastboot folder, and select "open command window here". (you can now release the SHIFT button )
Now plug your phone's USB cable to your computer.
Press and hold the MENU button on your phone, while connecting the MicroUSB connector to your phone.
When the LED turns blue you can release the button, your phone is now in fastboot mode.
Open the command window and insert the text you got in the Kernel thread, most certainly fastboot flash boot FILENAME.img, and press ENTER.
When the Command Window is finished close it and unplug your phone.
Turn on the phone, and when the button backlights turn on quickly press any button. Your phone will now boot into CWM Recovery.
RECOMMENDED: do a full wipe and flash your ROM.
If you want to keep your ROM and data just wipe cache and dalvik.
(If you're coming from a kernel with WiFi modules (ArcNight, DoomKernel) DO NOT do this, it will only mess up your phone.)
Hello,
I have a problem when trying to root my wifes U8800Pro. The SuperOneClick gets always stuck at step #7. I have done everything as instucted (enabled logging and usb debug, disabled fast boot, etc).
Before you say that I should search, this has been discussed before. Yes I know, I have searched and found couple threads, but they didn't help.
I'm guessing that the problem is that I have too new stock firmware? I had this in the phone originally:
u8800pv100r001c00b535
custnorc306d002
But now I downgraded (?) or upgraded to:
U8800Pro V100R001C00B512G001
And the SuperOneClick still isn't working. I don't know what to do. I can't find any older stock 2.3.5 firmwares and don't know if it would even help me if I could downgrade to some older version.
Could someone please help me how to root this phone. I have done Galaxy S before, but it wasn't this complex
BTW, the SD card stopped mounting when I flashed V100R001C00B512G001. I have to take it out and re-insert it to make it work every time.
I'll answer to my self. I don't know if all this is correct, but anyone can correct me if they want.
The stock roms can be rooted in various different ways. Most used options might be SuperOneClick and "pink screen" boot.img change.
SuperOneClick doesn't seem to work with at least newer versions of 2.3.5 at all. It's only usable in older stock roms.
Another option is using the "pink screen" method, with boot.img and it goes like this:
1. Power off, and then Power on with Vol + & - pressed to get to the Pink Screen.
2. Connect the phone to your computer with USB cable.
3. Browse the phone contents with your computer. You should only see one folder called "image". Go inside the folder.
4. Backup the boot.img file to your computer. You will deed it if you want to unroot / return to stock later.
5. Replace the boot.img with a rooted one. You have to find a boot.img specific to your firmware version. I haven't found one for 2.3.5. I'm not sure if they are different between U8800 and U8800Pro, but I guess they are.
6. Once done, detach the usb cable from the phone and restart it by taking the battery out and reinserting it.
You should have now rooted your stock firmware phone and you should see a Super User app in your app drawer.
But if you are going to load a custom firmware to your phone, there is no need to root the stock firmware. In this case you should use Clockwork Mod Recovery to load the custom firmware into your phone, because custom firmwares are already rooted.
It goes like this:
1. Power off, and then Power on with Vol + & - pressed to get to the Pink Screen.
2. Connect the phone to your computer with USB cable.
3. Browse the phone contents with your computer. You should only see one folder called "image". Go inside the folder.
4. Backup the recovery.img file to your computer. You will deed it if you want to return to stock later.
5. Replace the recovery.img with the CWM Recovery file. You need to make sure that you have the correct version for the rom that you are going to load. The needed version is usually mentioned in the rom description. I think the latest one is this: [Recovery] Unofficial CWM Recovery 5.0.2.7[u8800pro&u8800] (?)
6. Once done, detach the usb cable from the phone and restart it by taking the battery out and reinserting it.
7. You can now install custom roms with CWM Recovery by holding volume + and power to boot up your phone. Look at the install instructions of the rom you are going to install.
Be sure to backup your phone with CWM Recovery as soon as you have installed it in case anything goes wrong.
See how to create nandroid backups with CWM Recovery here.
http://forum.xda-developers.com/showpost.php?p=23565074&postcount=7
Experiences said:
http://forum.xda-developers.com/showpost.php?p=23565074&postcount=7
Click to expand...
Click to collapse
This is for regular u8800 not pro.
Sent from my U8800 using Tapatalk 2
I'm going to reply to this thread as this is kind of on topic... could someone more experienced answer at least some of the questions below, thanks.
Does anyone know where I could find stock firmwares for U8800Pro? I'm having hard time to find any even from Huawei's site. I only found this there and that says it's only usable in Russia.
I had this in the phone originally when I purchased it:
u8800pv100r001c00b535
custnorc306d002
Was that the newest stock firmware? Where can I find the newest one?
Is there a "rooted" boot.img for the latest stock firmware? Is the boot.img different for every firmware version? Is it different between U8800 and U8800Pro?
Is this the latest CWM Recovery and should I use that? I'm going to put some ICS rom in to the phone after I've tested the official demo version which is coming "soon" I hear.
I'll answer to my self once again..
Here's some stock firmwares for U8800Pro:
http://madmodder.co.uk/huawei/u8800-pro/huawei-u8800pro-firmware-list.htm
I guess the newest stock version is V100R001C00B572G001.
For the "rooted" boot.img I have no clue where to find one, or are they firmware specific or different between U8800 and U8800Pro.
As to the CWM, here's the official releases. There's no releases for U8800Pro, I don't know if it has different recovery.img as the U8800 has. I guess the one which I linked to is the latest "unofficial" version. Reading the comments seems to point that it works for some and some have problems. I guess that should be used still if you want to go for ICS rom.
Anyone care to comment on any of this?
I have the same problem i did every thing perfectly and i couldn't get to root my u8800 pro ... i tried super one click, z4root , easy root, unlock root , changing boot.img, ... i have my drivers installed correctly.. checked usb debugging.. disable fast boot....switched to logged on ( project menu ) and i still got stuck on step 7 on super one click.. another program mentioned.. ( adb server out of date.. ) and ( failed to copy superuser.apk due to system read only..) ... so I'm stuck now for 2 month..can any one help ???
Sent from my U8800Pro
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.
Hello, I am facing a major issue here, I had CM13 nightly 20151214 and I applied a theme, I even can't remember its name then the mobile rebooted then it stuck in a boot loop since then.
I have tried so many times and I can't get into the recovery!! Don't know why! I was on TWRP 2.8.7.3 bumped and everything was working perfect until that restart.
I still can access the download mode but I don't want to flash the stock rom now as I have so important files on the phone and I want to back it up first; and since I can't access the recovery to copy the files or flash another rom I am out of options!!
Your help is much appreciated here.
Phone: LG G2 D802 International version
I think that Android M created a smaller /system partition and in turn caused problems when you wrote to it and did not have space left. The only thing I can suggest is keep trying to boot to recovery...
shaneel1491 said:
I think that Android M created a smaller /system partition and in turn caused problems when you wrote to it and did not have space left. The only thing I can suggest is keep trying to boot to recovery...
Click to expand...
Click to collapse
For some reason the buttons combination for opening the recovery are not working anymore!
Pr0fess0rX said:
For some reason the buttons combination for opening the recovery are not working anymore!
Click to expand...
Click to collapse
Try either the vol down plus power, and I know there is another but I can't remember it, just do some regarding the different bootloaders..
Try vol- plus power when see lg logo release and press volume+ and vouleme-
I couldn't access the recovery (despite the fact that I know the combination very well) and also wasn't able to flash a stock rom.
After many tried and so much help in the following thread, I was successfully able to install a stock rom and here is the link: http://forum.xda-developers.com/showpost.php?p=64331109&postcount=11256
Hi all, new to Android and Samsung, so sorry for the noob question.. and sorry if its been answered before, Ive done a HEAP of reading and Im still confused...
I recently bought an S4 GT-I9505, thinking that getting into Android and maybe tweaking it a bit would be fun..
This phone was a Warranty replacement for a Telstra "POST Paid" service and has been sitting in a cupboard for a few years, It is NOT network locked. The phone had never been used before I bought it but has since ran out of warranty,,
I can't remember what ver of Android was on the phone when I got it but Its now updated to 5.0.1 and ofcourse has KNOX.. I obviously dont care about KNOX Warranty tripping to 0x1 as its ran out anyway...
My question is though....
Every guide or thread I read about installing custom ROMs and such says "phone must have an UNLOCKED bootloader" ... So how do I "UNLOCK" the bootloader or is this something that happens when flashing a custom ROM? ... What am I missing here guys?
Thanks in advance
kingsdene
Only few devices have a locked bootloader.
Verizon and AT&T devices have a locked bootloaders.
If you're device is none of the above then you're good to go.
GDReaper said:
Only few devices have a locked bootloader.
Verizon and AT&T devices have a locked bootloaders.
If you're device is none of the above then you're good to go.
Click to expand...
Click to collapse
Hi thanks for your reply,,
That clrears things up a bit,,
I read somewhere that the international versions weren't locked.. and in another thread I read they said the I9505 is international but on that same thread someone else said that it wasn't international, only the i9500 was,, so that confused me a little...
but on wikipedia the I9505 and I9506 are listed as international.... so if thats the case I definitely should be right hey???
Also because Im from AUS and not much is listed in terms of Australian Service providers.. would it be worth me trying to contact Telstra because its a Telstra "POST Paid" phone and asking if there would be any restrictions on it???
kingsdene said:
Hi thanks for your reply,,
That clrears things up a bit,,
I read somewhere that the international versions weren't locked.. and in another thread I read they said the I9505 is international but on that same thread someone else said that it wasn't international, only the i9500 was,, so that confused me a little...
but on wikipedia the I9505 and I9506 are listed as international.... so if thats the case I definitely should be right hey???
Also because Im from AUS and not much is listed in terms of Australian Service providers.. would it be worth me trying to contact Telstra because its a Telstra "POST Paid" phone and asking if there would be any restrictions on it???
Click to expand...
Click to collapse
It might at worst have a network/carrier lock on it, but that would be it, no other locks.
See here for info/fees: https://whirlpool.net.au/wiki/phone_unlocking
I believe post paid phones are unlocked from the word go, but you may want to check...easiest way is to grab a sim from a family member/friend on another carrier and put it in and see if it registers on the network...prolly quicker than waiting on the phone to telstra...only to be told its not locked .
Here you go, more info:
http://www.acma.gov.au/theACMA/engage-blogs/engage-blogs/Telco/The-key-to-unlocking-your-mobile
Me im in Aus too, i bought my S5 i9505, a former Telstra S4, a few days back knowing it was unlocked fortunately....took it home and rooted it, debloated it and living happily on the stock 5.01 TouchWiz ROM with TWRP Recovery and Xposed , ill prolly chuck a custom one on at some point....
stylemessiah said:
It might at worst have a network/carrier lock on it, but that would be it, no other locks.
I believe post paid phones are unlocked from the word go, but you may want to check...easiest way is to grab a sim from a family member/friend on another carrier and put it in and see if it registers on the network...prolly quicker than waiting on the phone to telstra...only to be told its not locked .
Me im in Aus too, i bought my S5 i9505, a former Telstra S4, a few days back knowing it was unlocked fortunately....took it home and rooted it, debloated it and living happily on the stock 5.01 TouchWiz ROM with TWRP Recovery and Xposed , ill prolly chuck a custom one on at some point....
Click to expand...
Click to collapse
Hi mate, Thanks very much for the reply/info
Thats really good to know.. Looks like Im all set then,, I knew it wasn't networked locked, I tested with an Optus sim..
Would you mind sharing your process on how you rooted it and installed TWRP? Did you use apps or flash from Odin/Heimdal etc,, I know theres heaps of guides and different ways of doing so.... Im just curious on different peoples experiences
Oh and just thaught id let you know I noticed in your sig you've listed you device as S4 I9095
kingsdene said:
Hi mate, Thanks very much for the reply/info
Thats really good to know.. Looks like Im all set then,, I knew it wasn't networked locked, I tested with an Optus sim..
Would you mind sharing your process on how you rooted it and installed TWRP? Did you use apps or flash from Odin/Heimdal etc,, I know theres heaps of guides and different ways of doing so.... Im just curious on different peoples experiences
Oh and just thaught id let you know I noticed in your sig you've listed you device as S4 I9095
Click to expand...
Click to collapse
Nice pickup on the sig
Im the king of typos...i have a wonky brain, and it doesnt always connect my hand with the right keys Sig corrected
Heres what i did on mine, and how i remember doing it, though if some steps dont match up, let me know via PM or email, in my profile:
Required utils/files (assuming you have a standard i9505):
Odin: http://dl.sammobile.com/Odin3-v3.11.1.zip
CF Auto Root: https://download.chainfire.eu/316/CF-Root/CF-Auto-Root/CF-Auto-Root-jflte-jfltexx-gti9505.zip
TWRP: https://dl.twrp.me/jfltexx/twrp-3.0.2-0-jfltexx.img.tar.html
1) Rooting
a) Put phone into download mode - Power + Home + Vol Down, then Vol Up
b) Connect to PC via cable
c) Run Odin
d) Tick next AP
e) Press AP and browse to locate and select the CF Auto file downloaded
f) Press Start
g) It should upload to phone and phone should reboot into recovery and do its thing and then reboot
h) Unplug the phone form the cable
i) You may get, i did, a Google Play update to update SuperSU. I did this and rebooted, you may also get a prompt to update the su binary, do this using the Normal method, and reboot
2) TWRP
a) Put phone into download mode - Power + Home + Vol Down, then Vol Up
b) Connect to PC
c) Run Odin
d) Tick next AP
e) Press AP and browse to locate and select the TWRP file downloaded
f) Click options, and untick Auto Reboot - if you dont manage to catch the device using the recovery boot keys as it reboots, it may boot normally and over-write the recovery, and you'll have flash it again, so i turned this off
f) Press Start
g) When its uploaded, unplug phone,and hold down Power + Home + Vol Up until it reboots and you see the recovery boot text appear in the top left (lines of blue, yellow, red text), let go at this point, a
the device should boot to recovery and install recovery
h) Unplug the phone form the cable
i) Power down the phone (i got a cache mounting issue - discovered when i was flashing Xposed, that you may need to fix...best to do it anyways, and do it now to fix the issue before you try and flash a custom ROM in the future etc)
j) Boot to recovery again - Power + Home + Vol Up until it reboots and you see the recovery boot text appear in the top left, let go at this point, the device should boot to recovery
k) Go into Mount and see if Cache is mounted, if it is, youre fine, if it isnt, try mounting it by ticking Cache. If it wont mount:
i) Click Wipe,
ii) Click Advanced Wipe
iii) Tick Cache
iiii) Click Repair or Change File System
iv) Click Change Filesystem
v) Click Ext4
vi) Swipe to change
It may take some time to fix....
l)Reboot when done
3) Debloating (highly recommended on the stock ROM)
Theres a few pages on which apps and files to remove using a root uninstaller app, or you can Install this and tick the items you want removed: https://play.google.com/store/apps/details?id=com.adamioan.s4lollipopdebloater&hl=en
Please dont ask me what to tick or leave ticked Theres descriptions in the app, or more info on the forums. Personally i tend to decimate ROM's from all non-essential apps, but what works for me may not work for you, you may use things i dont.
When done, reboot
Optional though recommended: Boot into recovery and wipe your dalvik & cache (note: once Dalvik is wiped your next reboot will be long due to app optimising - it will be shorter than normal with less apps though)
Hope this helps
stylemessiah said:
Nice pickup on the sig
Im the king of typos...i have a wonky brain, and it doesnt always connect my hand with the right keys Sig corrected
Heres what i did on mine, and how i remember doing it, though if some steps dont match up, let me know via PM or email, in my profile:
1) Rooting
a) Put phone into download mode - Power + Home + Vol Down, then Vol Up
b) Connect to PC via cable
c) Run Odin
d) Tick next AP
e) Press AP and browse to locate and select the CF Auto file downloaded
f) Press Start
g) It should upload to phone and phone should reboot into recovery and do its thing and then reboot
h) Unplug the phone form the cable
i) You may get, i did, a Google Play update to update SuperSU. I did this and rebooted, you may also get a prompt to update the su binary, do this using the Normal method, and reboot
2) TWRP
a) Put phone into download mode - Power + Home + Vol Down, then Vol Up
b) Connect to PC
c) Run Odin
d) Tick next AP
e) Press AP and browse to locate and select the TWRP file downloaded
f) Click options, and untick Auto Reboot - if you dont manage to catch the device using the recovery boot keys as it reboots, it may boot normally and over-write the recovery, and you'll have flash it again, so i turned this off
f) Press Start
g) When its uploaded, unplug phone,and hold down Power + Home + Vol Up until it reboots and you see the recovery boot text appear in the top left (lines of blue, yellow, red text), let go at this point, a
the device should boot to recovery and install recovery
h) Unplug the phone form the cable
i) Power down the phone (i got a cache mounting issue - discovered when i was flashing Xposed, that you may need to fix...best to do it anyways, and do it now to fix the issue before you try and flash a custom ROM in the future etc)
j) Boot to recovery again - Power + Home + Vol Up until it reboots and you see the recovery boot text appear in the top left, let go at this point, the device should boot to recovery
k) Go into Mount and see if Cache is mounted, if it is, youre fine, if it isnt, try mounting it by ticking Cache. If it wont mount:
i) Click Wipe,
ii) Click Advanced Wipe
iii) Tick Cache
iiii) Click Repair or Change File System
iv) Click Change Filesystem
v) Click Ext4
vi) Swipe to change
It may take some time to fix....
l)Reboot when done
3) Debloating (highly recommended on the stock ROM)
Theres a few pages on which apps and files to remove using a root uninstaller app, or you can Install this and tick the items you want removed: https://play.google.com/store/apps/details?id=com.adamioan.s4lollipopdebloater&hl=en
Please dont ask me what to tick or leave ticked Theres descriptions in the app, or more info on the forums. Personally i tend to decimate ROM's from all non-essential apps, but what works for me may not work for you, you may use things i dont.
When done, reboot
Optional though recommended: Boot into recovery and wipe your dalvik & cache (note: once Dalvik is wiped your next reboot will be long due to app optimising - it will be shorter than normal with less apps though)
Hope this helps
Click to expand...
Click to collapse
Haha your not the only one with a wonky brain bro.....
And WOW wasn't expecting all that... Thanks very much man, your a legend.
I really appreciate your help
Ill give it a crack and see how I go..
Cheers mate
stylemessiah said:
Heres what i did on mine, and how i remember doing it
Click to expand...
Click to collapse
Hi mate,, just thaught I'd let you know I followed your guide and all was sucsessful, thanks again, I had it running for a while and I really like the stock ROM when unbloated.
Since then I've flashed a Resurrection Remix Marshmallow ROM -ver 5.6.7 and its running well except for a few glitches but nothing serious.
I have a question for you though, if you dont mind... I am planning on getting the latest RR ROM and upgrading to that to see how it runs...
But if I were to downgrade to a Lollipop version of RR, would I be ok flashing it from my current state? I have read somewhere that flashing to an earlier version of Android (Marshmallow to Lollipop) is a bit of a different process?
And also if this were true.... Than when I made a TWRP Backup of my rooted stock 5.0.1 Lollipop before I flashed RR 6.0.1 Marshmallow.. If I were to try now to restore from my backup it wouldn't work? because of the different Android versions?
I have done heaps of reading and can't seem to find a great deal on this... only when it comes to stock ROMs
Cheers
kingsdene
kingsdene said:
Hi mate,, just thaught I'd let you know I followed your guide and all was sucsessful, thanks again, I had it running for a while and I really like the stock ROM when unbloated.
Since then I've flashed a Resurrection Remix Marshmallow ROM -ver 5.6.7 and its running well except for a few glitches but nothing serious.
I have a question for you though, if you dont mind... I am planning on getting the latest RR ROM and upgrading to that to see how it runs...
But if I were to downgrade to a Lollipop version of RR, would I be ok flashing it from my current state? I have read somewhere that flashing to an earlier version of Android (Marshmallow to Lollipop) is a bit of a different process?
And also if this were true.... Than when I made a TWRP Backup of my rooted stock 5.0.1 Lollipop before I flashed RR 6.0.1 Marshmallow.. If I were to try now to restore from my backup it wouldn't work? because of the different Android versions?
I have done heaps of reading and can't seem to find a great deal on this... only when it comes to stock ROMs
Cheers
kingsdene
Click to expand...
Click to collapse
Im glad that my wonky memories of rooting/twrp and debloating worked out for you. The stock 5.01 ROM is great without the bloat. Ive since moved onto Optimised CM13, which is going well.
Im afraid i cant help you on downgrading from LP to MM, as ive never done it on this device, but i cant see how that would in any way be an issue as you have a custom recovery installed...afaik thats all thats needed...at least on the S2 it was as easy as flash what the hell you want to on it as long as you had at least a KK recovery installed..
Cant help on backups, as i literally never use them, i never carry over stuff from one ROM to the next, i clean install everything
kingsdene said:
Hi mate,, just thaught I'd let you know I followed your guide and all was sucsessful, thanks again, I had it running for a while and I really like the stock ROM when unbloated.
Since then I've flashed a Resurrection Remix Marshmallow ROM -ver 5.6.7 and its running well except for a few glitches but nothing serious.
I have a question for you though, if you dont mind... I am planning on getting the latest RR ROM and upgrading to that to see how it runs...
But if I were to downgrade to a Lollipop version of RR, would I be ok flashing it from my current state? I have read somewhere that flashing to an earlier version of Android (Marshmallow to Lollipop) is a bit of a different process?
And also if this were true.... Than when I made a TWRP Backup of my rooted stock 5.0.1 Lollipop before I flashed RR 6.0.1 Marshmallow.. If I were to try now to restore from my backup it wouldn't work? because of the different Android versions?
I have done heaps of reading and can't seem to find a great deal on this... only when it comes to stock ROMs
Cheers
kingsdene
Click to expand...
Click to collapse
The downgrading is only a problem on stock to stock ROMs. Any combination of custom to stock should work.
And TWRP has a problem with TouchWiz ROM backups. So your backup might not work either.
I mean, it will work, but you get errors.