Related
Hi,
I have the Galaxy S4 i9505 and having issues with trying to root the device. So after reading tons of posts over the last few days with regards to rooting I think I have finally worked out what I need to do and have all relevent files required (Odin, CWM etc).
So I went to put the phone into recovery mode by using the vol+ menu and power button but instead of getting the flashing custom roms warning message and press vol+ to continue it loads to a manual recovery with several options and an icon of dead android icon with a red exclamation mark.
The phone is brand new, not done any rooting on it before, the only thing I did was use KIES to update the phone.
Currently running Kernal 3.4.0-526204, Build I9505XXUAME2.
I'm not a complete noob when it comes to rooting android, have messed with a crappy MOMO9 tablet rooting and flashing different custom roms however this is a little different as this phone costs 10 times as much lol, I've also come over from iphone 4 which used to jailbreak etc.
I have done alot of searching and found guides for other devices, just not sure it will work on my version and brick the phone. Can anyone maybe point me in the right direction or know of a guide to help me resolve this problem.
Many Thanks
Goggers said:
Hi,
I have the Galaxy S4 i9505 and having issues with trying to root the device. So after reading tons of posts over the last few days with regards to rooting I think I have finally worked out what I need to do and have all relevent files required (Odin, CWM etc).
So I went to put the phone into recovery mode by using the vol+ menu and power button but instead of getting the flashing custom roms warning message and press vol+ to continue it loads to a manual recovery with several options and an icon of dead android icon with a red exclamation mark.
The phone is brand new, not done any rooting on it before, the only thing I did was use KIES to update the phone.
Currently running Kernal 3.4.0-526204, Build I9505XXUAME2.
I'm not a complete noob when it comes to rooting android, have messed with a crappy MOMO9 tablet rooting and flashing different custom roms however this is a little different as this phone costs 10 times as much lol, I've also come over from iphone 4 which used to jailbreak etc.
I have done alot of searching and found guides for other devices, just not sure it will work on my version and brick the phone. Can anyone maybe point me in the right direction or know of a guide to help me resolve this problem.
Many Thanks
Click to expand...
Click to collapse
For preparing your phone for Odin for flashing, you should be putting your phone in download mode (volume down, power and home button). This will display the custom ROM warning message, and you press the up volume key to put it in download mode. I'll assume this is what you're trying to do? Then the usual kill all Kies related processes, plug your phone in, wait till odin identifies it, then proceed to flash your file.
P. S. What guide are you following to root your device?
Sent from my GT-I9505 using xda app-developers app
I'm not sure
Hi,
I used a guide from galaxys4root.com I think, as luck would have it my pc crashed just after writing the orig post and my history/recover webpage didnt work, happy days. Its ok I like a challenge, think it helps with learning, wouldnt learn anything if it went right all the time.
I have made a little progress, I tried both vol + and vol -, both put me into manual recovery with dead android logo (i meant to put vol - in my previous post not vol +) Just incase I had a bad upgrade from XXUAMDD to XXUAME2 I reflashed the update using KIES and tried again. This time I was able to go into download mode and managed to get CWM v6.0.3.2 flashed and was able to boot to that using vol + no problem.
Now I have an issue with SuperSU failing to update the binary, I used CWM to load a file called "CWM-SuperSU-v0.99.zip" which I suspect is not correct for my current version so its back to searching for me. Trying to get my head round all the different versions of S4 etc and what works on which device.
CWM-Recovery?
Goggers said:
Hi,
I used a guide from galaxys4root.com I think, as luck would have it my pc crashed just after writing the orig post and my history/recover webpage didnt work, happy days. Its ok I like a challenge, think it helps with learning, wouldnt learn anything if it went right all the time.
I have made a little progress, I tried both vol + and vol -, both put me into manual recovery with dead android logo (i meant to put vol - in my previous post not vol +) Just incase I had a bad upgrade from XXUAMDD to XXUAME2 I reflashed the update using KIES and tried again. This time I was able to go into download mode and managed to get CWM v6.0.3.2 flashed and was able to boot to that using vol + no problem.
Now I have an issue with SuperSU failing to update the binary, I used CWM to load a file called "CWM-SuperSU-v0.99.zip" which I suspect is not correct for my current version so its back to searching for me. Trying to get my head round all the different versions of S4 etc and what works on which device.
Click to expand...
Click to collapse
Hey-
First you should flash a stock rom namely XXUAME2.
Than try this here: http://forum.xda-developers.com/showthread.php?t=2238442
That recovery is stable and reliable. The CWM-Recovery is currently not fully bug-free.
I think SU is included in TWRP, so you don't have to worry about that.
After you've done that, you can flash any custom rom for the GT-I9505.
My recommendation is OMEGA 3.1 and the ADAM-KERNEL 1.3.1+
All that stuff you can find here.on xda.
Good luck -
Your SU 0.99 is too old and doesn't fit at all.
Getting there
Hi,
Thanks for tips and pointing me in the right direction. I have since downloaded a couple of ROM's, both pre-rooted to get a better understanding of things, at present i'm running [ROM][ME2][31May] FoxHound GearEngine 0.1 Stable | Themed | Smooth | Clean | Hybrid. Its way faster than stock rom and quite impressive.
I'm still trying to understand why so much memory is taken up by the OS, i understand it has something to do with TouchWhiz or something. I now need to look into running apps from the sd card if this possible, I know its not with standard rom and un-rooted device.
I actually got both S4 and HTC One as I have two contracts with t-mobile ready for upgrade, I have since sent the HTC One back to have it replaced with another S4 as the wife also prefers the S4 over the HTC One, not to say its not a good phone as its amazing, the main selling point for me was the ability to upgrade memory with SD Card.
Hopefully I can get back into this again and maybe start creating roms again, i used to create them for the older HTC windows phones, mainly TYTNII and touch.
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.
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.
Hi All,
I realise you guys must be sick of these kind of posts but just thought that one of you would be able to point me in the right direction before I do something else wrong!
I was rooted on d802, Cloudy 3.3 with TWP 2.8.6.1 installed. I was trying to get magisk to work but after flashing the various zips etc I left my phone for a few minutes and a toddler came along and swiped the install superSU prompt on TWRP that comes up before rebooting :/:/:/.
So now I am stuck in this "[720] Fastboot mode started". When I plug it into my computer I get a few other things popping up and on device manager it comes up as "Android Bootloader Interface", Device type Kedacom USB Device.
Before messing around with all these things I made a full backup with TWRP so if I can just get back to that I am hoping I will just be able to restore it? At the moment I am unable to get to recovery mode, it just keeps rebooting quickly showing the LG logo and proceeding to fastboot mode. I have tried the holding down power and vol d button but it happens so fast and doesnt seem to do anything.
Where should I go from here? There seem to be a lot of different methods and various things, the more I search the more ways I find!! What is best in my particular situation?
Also could somebody definitively tell me if Magisk will work with cloudy 3.3? I can find no mention anywhere on the internet of someone saying they have done it/got it to work.
amishra123 said:
Where should I go from here?
Click to expand...
Click to collapse
Hi!
This way > http://forum.xda-developers.com/lg-g2/help/fixing-fastboot-mode-started-t2930963
And if it doesn't work I would make this > http://forum.xda-developers.com/lg-g2/help/noob-friendly-recovery-download-mode-t3112805
And you can find a list with all fixes right here > http://forum.xda-developers.com/showpost.php?p=63327417&postcount=4
Good luck!
Thank you very much for your prompt reply !!
I kept trying with the power and volume down and managed to somehow get back into recovery, and then I recovered using the backup!! All back to normal now !
I've since updated to the latest twrp and that all went smoothly aswell.
Any word on whether magisk V9 will work with cloudy g2 3.3 ? I'm tempted to give it another go...
Use the unsu zip , uninstall xposed using the zip , then flash magisk , phh superuser and finally the cbump. I'm really tempted to try again but not sure if it was doing that , that messed it up last time or if it was twrp trying to install super su (Im quite sure it is probably the latter though). Any thoughts ?
EDIT: incase this helps anyone else, I think what I did was to keep the power and vol down held for a long time , if I remember correctly it seemed to cycle a few times through logo and then the fastboot screen until it finally switched off. Prior to this as soon as I thought it was off it would just start again. This time though it went through into the factory reset screen and then recovery.
amishra123 said:
All back to normal now !
Click to expand...
Click to collapse
Nice to here that. :good:
amishra123 said:
Any word on whether magisk V9 will work with cloudy g2 3.3 ?
Click to expand...
Click to collapse
That's a question for the CloudyRom-thread. I bet you're not the first with this question.
A couple weeks back I deleted the OS off of my phone while messing with TWRP recovery trying to install a custom ROM. I looked around the forums and i got my phone to the point where It booted into a stripped down version of android with stock recovery on it, although everything was mirriored and backwards. But when i tried to install the stock rom for my LeEco S3 with stock recovery it got stuck i a boot loop and I couldn't turn off the phone or boot into recovery or anything. So i let it keep booting until it ran out of battery and died. So then i decided i would put the stripped down version back on and start again.
So I went back to my sp flash tool and reinstalled all the partions except the boot and recovery partitions (according to the steps on the forum) but my phone still wont boot into anything, it is completely black and wont boot into recovery or fastboot, and im running out of ideas on how to fix this phone :crying:
After pretty much giving up all hope of fixing my phone, i figured i would try the format option in the flash tool and then reinstall all of the pattitions. I selected format all flash, not doing proper research first, and now i cant even reinstall partions, I get a STATUS_BROM_CMD_SEND_DA_FAIL error anytime i try to flash the partitions.
can you at least get the phone to fastboot mode?
microMXL said:
can you at least get the phone to fastboot mode?
Click to expand...
Click to collapse
No I cannot, The screen is completely black and nothing comes on at all if I hold down the power button.
well damn, looks like a soft brick, it can be repaired but not gonna lie, it is a pain in the butt...
https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937
the guys have made an awesome guide on that thread.
microMXL said:
well damn, looks like a soft brick, it can be repaired but not gonna lie, it is a pain in the butt...
https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937
the guys have made an awesome guide on that thread.
Click to expand...
Click to collapse
I have already looked through that thread, and i have done everything up to the flashing process, and then I get a STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003) Error. I looked it up but the only option I haven't tried to solve the issue is to remove the battery, which i cannot do currently because to remove the battery you need a heat gun to remove the screen to get to the rest of the phone. I think I've given up all hope on fixing this phone and may just begin saving for a new one.
Sgt.Collywobbles said:
A couple weeks back I deleted the OS off of my phone while messing with TWRP recovery trying to install a custom ROM. I looked around the forums and i got my phone to the point where It booted into a stripped down version of android with stock recovery on it, although everything was mirriored and backwards. But when i tried to install the stock rom for my LeEco S3 with stock recovery it got stuck i a boot loop and I couldn't turn off the phone or boot into recovery or anything. So i let it keep booting until it ran out of battery and died. So then i decided i would put the stripped down version back on and start again.
So I went back to my sp flash tool and reinstalled all the partions except the boot and recovery partitions (according to the steps on the forum) but my phone still wont boot into anything, it is completely black and wont boot into recovery or fastboot, and im running out of ideas on how to fix this phone :crying:
After pretty much giving up all hope of fixing my phone, i figured i would try the format option in the flash tool and then reinstall all of the pattitions. I selected format all flash, not doing proper research first, and now i cant even reinstall partions, I get a STATUS_BROM_CMD_SEND_DA_FAIL error anytime i try to flash the partitions.
Click to expand...
Click to collapse
Help, pls I got the exact same problem... Pls any solution to it... I have been at it for a month now no solution, help
same problem. after twrp flash x626 not boot