Related
I thought I'd do this tutorial because some people still seem to be having trouble searching the forum for answers, even though the forum is still only small, so I thought I'd put everything in one place, these are all the processes I've followed and they've worked for me, here you will find links to all the useful posts and places to find out what you need too..... Also I'll try to make it a little more Noob friendly too
But as always if you turn your phone into a paperweight, don't come blaming me for it, I've personally done everything (apart from flashing a stock rom and that is because I've never needed to) in the tutorial and its worked for me and worked for the majority of people in here and that is because we know how to follow instructions properly
If you are unsure about doing anything in this tutorial... DON'T DO IT... Ask a question here... But dont ask rom specific questions here though!!!
Now this will be for doing everything on a Windows PC. If anyone else wants to add what to do on Linux, Mac etc please let me know and I'll add them...
Now you've obviously come here because you're considering rooting and maybe even putting a custom rom on your phone. If thats not the case there is no point reading on...
Once you have your shiny new Sensation XL the first thing you will need to do is check the build number because we have noticed that a couple of the latest builds have not been rootable. You can do this by going to 'settings/about phone/software information/more'
Check the second post for details of the builds we know of at the minute that you will not be able to root. The only way around this at the minute is to flash an older RUU (Stock Rom) which we know can be rooted. Details of how to do this can be found at the bottom of this post!!!
Once you've either got a rootable build or you have downgraded and before you actually try to root your phone you will need to Unlock the bootloader!! Unfortunately unlocking the bootloader is the only way to be able to put custom roms on your phone.
You can get permanant root but you won't be able to put a custom rom on your phone, so if you only want root you don't need to unlock bootloader. You will need to use v4 from this post... http://forum.xda-developers.com/showthread.php?t=1341127 ... Cheers Shingers
But for recovery (CWM) and the ability to put custom roms on your phone (lets face it you do... thats why you're here ) you WILL NEED TO UNLOCK BOOTLOADER
To do this you will need to go to the HTCDEV website at www.HTCDEV.com then you will need to register an account to be able to unlock your bootloader. Now the Sensation XL isn't listed in the devices that it says can be unlocked so what you need to do is when its time to select your device scroll to the bottom and select 'All Other Supported Devices'. Then you will get the warning boxes pop up asking you if you're sure you want to do it then saying you could void your warranty as well. Once you've clicked ok on those you'll be through to the instructions on how to unlock your bootloader.
Remember how to get your phone into fastboot from the instructions because you will need to do it again, or if anything goes wrong.
But if you follow the instructions properly nothing should go wrong... Its been tried and tested by lots of people...
And just incase you don't remember how to do it... Take battery out and pop it back in, then press volume down and power button together until you see the white bootloader screen and then press the power button to get into fastboot.
Please please please follow the instructions to the letter, because if you don't it WILL NOT work. Its a very comprehensive walkthrough on how to do it so you shouldn't have any problems unlocking your bootloader as long as you follow the instructions... If you're struggling here maybe you shouldn't read any further and leave your phone like stock
Then once you have that done you will need to get root and for that you will need to follow shingers5 tutorial below...
Get the file for rooting here DooMLoRD_v2_ROOT-zergRush-busybox-su.zip
1. enable usb debugging from settings - applications - development
2. plug phone to pc via usb cable - charge only
3. open extracted zip folder and click runme. thats all. (if experience any daemon hanging problems pls install htc sync and plug in phone so drivers are installed. once done delete htc sync and repeat root procedure) PC will open a cmd screen with prompts that you need to follow. The app does rest... So its nice and easy
4. After root is complete pls visit market and update SU app. once done root will be fully functional and eliminate any future FCs
5. Also as an extra tip you can install SU UPDATE fixer from market to update your binaries to 3.0
ALL DONE
If you're struggling with the above instructions, remember that you will need to un-install HTCsync because it interferes with fastboot and rooting...
Then once you're rooted you will need to put CWM (Clockwork Mod) recovery on in order for you to be able to back up your phone and flash custom roms. The custom recovery by Paul O'Brien is the best one to use and is available to download here... http://android.modaco.com/topic/348973-clockworkmod-recovery-5027-unofficial-modaco-edition/
You will need your phone in fastboot again and you will need to find the fastboot folder on your PC (Windows). When you're in the fastboot folder press the left shift button and right click on the mouse and select open command prompt here. Make sure your phone is connected to the PC and is in fastboot. Also make sure that the recovery.img file that you downloaded from MoDaCo is in the fastboot folder too. Get back to the command promt window and type the following
fastboot flash recovery r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img (Tip: once you get to the r1 bit just hit tab and it will auto complete the rest of the line)
If you can't get the Paul O'Brien recovery installed (apparantly not everyone can) try the Older recovery from here http://forum.xda-developers.com/showthread.php?t=1348693
Now you've got root and CWM
A lot of people who have come this far will want to put a custom rom on... unfortunately its not completely straight forward. But again there is a way round round it and you should only need to do it once, when you're coming from a stock rom.
Now there is two ways of doing it, but one of the ways doesn't always work so I would suggest that you do it the guaranteed way, it is a little longer but it is guaranteed to work! And this method is thanks to shingers5 in this thread http://forum.xda-developers.com/showthread.php?t=1366238 but I will go through it again here....
1. You cant just flash a custom rom on this phone, firstly you will need the 'Chinese rom' which is here http://hotfile.com/dl/148413075/8990501/runnymede_ax918_111511_101713.zip.html and make sure it is on the SDcard part of your phones memory. Make sure it on the root of the SDcard because it will be easier to find later. Then you will need this rom RCMix3d Runny XL rom from here http://dl.dropbox.com/u/56143145/RCMix3D_Runny_XL_v1.2.zip (thanks to benjamin.j.goodwin) and make sure that is on the SDcard too with the other rom
2. Then you will need to download this file from here http://forum.xda-developers.com/showpost.php?p=19494357&postcount=18 it is the 'Chinese boot.img' and will need flashing from fastboot again. So put the phone in fastboot and extract the 'boot.img' from the 'boot.rar' file and put it in the fastboot folder on the PC. Open the command prompt again and type this... fastboot flash boot boot.img ... This should only need doing once if you're coming from a stock rom.
3. Once you've done that you will need to get into recovery. From fastboot select bootloader and then look for recovery, it should be under fastboot if its worked correctly. Select that and the phone should then reboot and go into 'CWM' (recovery). Once there you will need to use the volume keys and power button just like when you were in bootloader. Go down and select 'Factory Reset/Data Wipe' and select that, the select yes on following screen. This will take a few mins (don't worry if it looks like its not doing anything). After that go down to 'Wipe Cache' and select that. and then go down to 'Advanced' select that and on the following screen select 'Wipe Dalvik Cache'.
People who have used CWM before will know all that, but I'm putting it in anyway
4. Once thats all done you will need to select 'Install Zip File from SDcard' and then you will get another screen where you go to 'choose zip from SDcard' and the you will see all the contents of your SDcard, scroll down till you can select the Chinese rom you put on earlier (remember what it was called) and then select yes to install it. Sit back and wait another few minutes. Once its done select the 'reboot now'. The phone will then reboot again and start to load the new rom up. This will take a while so don't worry. Now once the phone has started you should get the start up wizard and you will just need to skip through it (don't worry about it being all in chinese... its in english). Not everyone needs to install the Chinese rom, some people can just go straight to the RCMix3d rom and install that, but it doesn't work for everyone, so I'm putting this in because it always works when you do it this way. Installing the Chinese rom should only need doing once if you're coming from a stock rom.
5. Boot into recovery again and goto 'Factory Reset/Data wipe', then 'Wipe Cache', then 'Advanced' and 'Wipe Dalvik Cache' and then go back to main screen and select 'Install Zip From SDcard' and then select 'RCMix3d zip' file and install that. Once thats done select Reboot Now and wait while phone boots up again... and VOILA you now have a custom rom Installed.
6. You could either leave that rom on (its a very good rom) or choose to install one of the other custom roms, read through the first few posts of each rom and decide from there whether you want to install that particular rom, or do what I did and install everyone and see which you like best
ANDTopix ... http://forum.xda-developers.com/showthread.php?t=1429241
BinDroid ... http://forum.xda-developers.com/showthread.php?t=1420841
CoreDroid ... http://forum.xda-developers.com/showthread.php?t=1444664
Runnymede XE ... http://forum.xda-developers.com/showthread.php?t=1502570
Or you want a tweaked rom with stock look (also from BinDroid) ... http://forum.xda-developers.com/showthread.php?t=1430794
There is also an ICS based rom available now
WRE 1.5 (Worst Rom Ever) ... http://forum.xda-developers.com/showthread.php?t=1491039
Now if you're having problems with any part of this and/or you softbrick your phone, my suggestion is that you stop what you're doing and either see if you can get your phone on and working properly (if so all is well with the world) or turn the phone off and pull the battery out, pop it back in and see if you can get into fastboot, if you can your phone should (I'm saying should, because I don't know what you've done to your phone to be considering this ) be recoverable. You will need to make sure phone is in fastboot and then get command prompt up in fastboot folder and type this...
fastboot oem lock
That will relock the bootloader so that you can flash a stock HTC stock image (or RUU) back to your phone. Your bootloader WILL need to be relocked for you to be able to flash stock image back to phone. You can find stock HTC roms (RUU's) here http://forum.xda-developers.com/showthread.php?t=1317895
When you're in fastboot and your phone is connected to the PC and you've downloaded the correct RUU for your region (they are region specific) double click on the RUU.exe and that should start the procedure of flashing the stock image back to your phone. I've never needed to do this, so I'm not 100% on the whole process.
Please remember that if you flash a RUU back to your phone, you will lose root etc, it will be like when you first got the phone...
Also remember that these instructions are tried and tested by many of the members in here and if something isn't working please check that you've followed the instructions to the letter, because it could be quite likely that you've done something wrong or missed something out...
Now I've tried to be as thorough and as noobish as I can possibly be, but if you think you can add anything just let me know and I will add it.
Special thanks to shingers5 who did all the work to start off with, all I've done really is bring them all together and Football for getting all the stock roms in one place
Software versions 1.24.709.2 and 1.14.709.2 seem unsupported by current methods of rooting.
The only way aound this at the minute is if you can find an older stock rom for your region you will have to flash that in order to be able to root your phone. You will need to relock your bootloader to be able to flash another RUU (see first post). And remember as we can't get S-OFF at the minute it will have to be a rom for your phones region...
Everything in one place , Thanks !
snear said:
Everything in one place , Thanks !
Click to expand...
Click to collapse
It is still confusing about boot.img and chines rom etc. Is it to be done just once?
Some ROMs say flash the Boot.img file as well. Is it different from what you have mentioned or just the same thing.
I would love to try different ROM but I am not comfortable about how to achieve it.
You will only need to flash the Chinese boot.img once and that is when you're coming from a stock rom. Once you've flashed it and the Chinese rom, then flashed RCMix3d you will be able to just flash any rom without the need for flashing the boot.img again.
I know it seems a little long winded but its the only guaranteed way of getting custom rom on your phone. Some people are lucky enough to be able to flash the boot.img and then flash any rom, but that doesn't always work, thats why I've put the method that is tried and tested as working
[vertigo] said:
You will only need to flash the Chinese boot.img once and that is when you're coming from a stock rom. Once you've flashed it and the Chinese rom, then flashed RCMix3d you will be able to just flash any rom without the need for flashing the boot.img again.
I know it seems a little long winded but its the only guaranteed way of getting custom rom on your phone. Some people are lucky enough to be able to flash the boot.img and then flash any rom, but that doesn't always work, thats why I've put the method that is tried and tested as working
Click to expand...
Click to collapse
Thank you Vertigo for make it clear. I will give it a go now.
And there are enough people around to help the new Guys & Girls with there SXL
Cheers for the tutorial
I've got an s-off sensation xl so was wandering if I can avoid the HTC unlock bit?
Johnston411 said:
Cheers for the tutorial
I've got an s-off sensation xl so was wandering if I can avoid the HTC unlock bit?
Click to expand...
Click to collapse
To be honest I'm not 100% sure. But to be on the safe side it might be worth unlocking it anyway. Unless you're feeling brave and want to try it with out first, Then you could maybe let us know if it does work
I'm guessing if there was a clockworkmod.zip I could flash from the stock recovery I wouldn't need to.
I think I'll be cautious and unlock it
+1 From me ...
I only have 2 questions for now.
If I choose "Sensation", instead of "all other supported devices," Is it wrong?
And I can not open a Command Prompt, when I press the left shift button and click your right mouse button in the fastboot folder.
There is no such option ...
luba6ky said:
+1 From me ...
I only have 2 questions for now.
If I choose "Sensation", instead of "all other supported devices," Is it wrong?
And I can not open a Command Prompt, when I press the left shift button and click your right mouse button in the fastboot folder.
There is no such option ...
Click to expand...
Click to collapse
Yeah I would say so, from what people have said if you pick sensation it doesn't work, it does however work if you pick 'all other supported devices'.
If you can't get command prompt open from that menu, do you know how to navigate to the fast boot folder if you open a command prompt from the start menu?
[vertigo] said:
Yeah I would say so, from what people have said if you pick sensation it doesn't work, it does however work if you pick 'all other supported devices'.
If you can't get command prompt open from that menu, do you know how to navigate to the fast boot folder if you open a command prompt from the start menu?
Click to expand...
Click to collapse
Yes, I know how to navigate to the fastboot folder.
Thanks again!
All this information is in another 3 posts about ROOT, CWM, and Bootloader unlock and i read them before i rooted month ago. Thank you for your work, but personaly i think your thread is little bit to large It would burn my brain if i would follow this doing rooting Maybe for someone is good to have it all in one place.
P.s. I flashed Bindroid ROM after boot.img flashing. Then i flashed Dutchdanny provided flashable stock ROM, now use RCMix, and no problem. Actualy i flashed boot.img twice, but i think its only necessary first time and does not matter which ROM u flash first.
Yeah I know its a big post and that all the information in the first post is a available in other posts, but not everyone is like you and searches the forum for answers. On the whole most people do the same but there are some people who 'can't be bothered' to search for answers and start threads asking questions that have already been answered. I know because I've been answering them.
So I thought that it would be a good idea to put everything in one place so the answers would be easier to find.
Its like I said in the first post that some are lucky enough to flash another rom and it work straight away, but not everyone can (like me), so I posted the guaranteed way to get it to work (just like in shingers5 post) because if I didn't that would create more questions. Also I said that you should only need to flash boot.img once and not you can't flash it more than once.
Its basically an attempt to keep the forum clean and not full of unnecessary posts... that can only be a good thing surely
How do i find fastboot folder in my pc ... Or do i hve to create myself??????
Sent from my HTC Sensation XL with Beats Audio X315b using xda premium
MOEHEET said:
How do i find fastboot folder in my pc ... Or do i hve to create myself??????
Sent from my HTC Sensation XL with Beats Audio X315b using xda premium
Click to expand...
Click to collapse
Have you installed the Android SDK like it told you to on the HTCDev website. If so just search for fastboot.exe on your computer. Its all clearly explained when you go through the process of unlocking your bootloader at HTCDev.
Download Android SDK here http://developer.android.com/sdk/index.html
Edit: Attached pics to make it a little easier
Ok got it..thnx 4 ur help...
Much appriciated ..
Ta
Sent from my HTC Sensation XL with Beats Audio X315b using xda premium
hi all ,
i have try to unlock my bootloader since january and have the same problem all the time .
the process keep lock at
"H:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)..."
i have tried to reinstall sdk , htc pilot , ect ect but it s the same problem
please help me
my phone it root with DooMLoRD_v2_ROOT
voileuxcool said:
hi all ,
i have try to unlock my bootloader since january and have the same problem all the time .
the process keep lock at
"H:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)..."
i have tried to reinstall sdk , htc pilot , ect ect but it s the same problem
please help me
my phone it root with DooMLoRD_v2_ROOT
Click to expand...
Click to collapse
Your phone is not permanantly rooted if your bootloader is still locked. Try un-installing HTCsync because that can interfere with fastboot. Also have you put the unlock_code.bin file in the fastboot folder?
After only four day of having this phone i managed to brick it. I would really like to know if its fixable or if i have a really nice paper weight. Im stuck on a boot loop, I was half way through flashing a rom when it suddenly shut off. Now it will not boot up. I can load into the bootlader but when i try to go into recovery it just sends me to fastboot. When i restart the phone i can see the old recovery (TWRP)for just an instant but then the screen goes completely black. If i plug in to my pc, nothing happens my computer detects it but it says y device is damaged nd it cant identify it. PLEASE HELP Am i out of luck?
Ive looked around but i couldnt seem to find anyone with the same problem as me (Sprint Variant)
Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help
There's a Sprint One forum as well, so hopefully you found a ROM on there!
http://forum.xda-developers.com/forumdisplay.php?f=2215
jaythenut said:
Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help
Click to expand...
Click to collapse
I really hope so because on a college budget i cant afford another phone D:
Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.
wnp_79 said:
Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.
Click to expand...
Click to collapse
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
i suggest you contact with HTC customservices to repair this problem.
Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock
Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.
DynamicRam said:
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock
Click to expand...
Click to collapse
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
dont give up
Sent from my HTC One
Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
Edit: Just got done typing the stuff below and saw you can't connect to your device in fastboot? What do you mean by re-installed driver?
Don’t worry, as long as you can still get into hboot your phone is not completely bricked!
The fastboot commands I referred to need to be carried out on your laptop/pc when you phone is connected in fastboot.
Can I assume that as you have already unlocked bootloader and flashed a custom recovery you are already familiar with this and have your computer set up for fastboot commands?
(Apologies if you already know some of this, best not to skip parts out though!)
I’d start with downloading a fresh version of your chosen recovery, and place it in your fastboot directory ready. I’d also do the same with your ROM.
Like you have already done, boot into fastboot. Connect your phone to your pc, and the red text should change to ‘Fastboot USB’.
Then open up command prompt and get to your fastboot directory. (On Windows 7 you just find that folder in Explorer, hold shift and right-click, then choose ‘Open command window here’.)
To check your pc is talking to your phone, type ‘fastboot devices’. You should get a device serial number back if all is well.
Then type ‘fastboot erase cache’ and hit enter.
Then type ‘fastboot erase recovery’ and hit enter.
Then type ‘fastboot flash recovery [name of recovery].img’ and hit enter.
Then type ‘fastboot reboot recovery’ and hit enter.
Hope fully you should successfully boot into recovery now. Once in recovery, mount USB storage and copy over your fresh ROM. Choose to do a full wipe including cache and dalvik, then reflash your ROM.
Reboot.
Let me know how this goes.
cronus101 said:
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.
Click to expand...
Click to collapse
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:
Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app
Muquita said:
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:
Click to expand...
Click to collapse
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html
Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck
wnp_79 said:
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html
Click to expand...
Click to collapse
(Win8 but the procces is identical.) All my drivers are up to date. Still no love.
On the dev forum is a thread that includes all the latest drivers (including an app to remove older drivers.)
Find that thread, download the drivers and bmp and driver removal tool. Remove drivers with tool, install the new drivers, reboot, connect phone and see if 'adb devices' finds anything.
Also make sure you're using the latest adb.
Sent from my HTC One using xda app-developers app
thneed said:
Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app
Click to expand...
Click to collapse
This actually sounds really similar to my situation.. Would you care to be a little more specific on the procedure? noob here.
Tabtoub said:
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck
Click to expand...
Click to collapse
My pc will not recognize my phone. The drivers are up to date but when i plug it in it says something malfunctioned ?
I read through many threads and have followed the official Sony bootloader unlocking instructions. I have requested and received the unlock code from Sony via email. I have downloaded the inf file and placed it in the correct folder in Android SDK (which I also updated). But I am cannot access fastboot mode, I hold down Vol + and plug in the USB cable but the device shows a red led and goes into charging mode. Also the PC never prompts me to install fastboot driver it simply loads the SP as Sony mass storage device (in device manager).
I have read that some people seem to think that the SIM lock affects the ability to access fastboot but this SP is SIM unlocked. Sony's official guide to unlocking the bootloader says I need to access fastboot mode to enter the unlock code but how can I unlock the bootloader if I can't get into fastboot mode?
hmmm... don't know really... i once entered fastboot mode by mistake, while trying to root stock rom. wasn't reading instructions and put device in a fsatboot mode instead of debugging... was on stock rom so don't know if custom rom would let me do that. should check myself... if anything i know it is possible to get me that blue light shining.
To enter fastboot mode in Xperia SP just power down the phone and hold down the volume up key while pluging your phone into your pc
If you need flashmode do the same thing but with the volume DOWN button held down.
I´ve got the same problem. I can´t enter in flashmode neither in fastboot mode. I´m on windows 8 32bits and I installed the .245 Deodexed ROM with a problem on root and without CWM. I don´t know what to do now, please help me.
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
gandalf_grey91 said:
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
Click to expand...
Click to collapse
Sorry for that i dont think that it is your computers fault because you enter fastboot (and flashmode) using your mobile phone NOT your PC
So i would roughly assume that this is a Rom bug or something in the flashing proccess went wrong.
jackaros said:
Sorry for that i dont think that it is your computers fault because you enter fastboot (and flashmode) using your mobile phone NOT your PC
So i would roughly assume that this is a Rom bug or something in the flashing proccess went wrong.
Click to expand...
Click to collapse
Thanks for trying to help, but I understand that flashmode and fastboot are accessed using the phone. Actually the phone needs a piece of software like flashtool to keep it in flashmode otherwise it drops into charging mode. I didn't mention my computer so I don't know where you got that from.
As I explained, I am unable to access fastboot with stock ROM (1.257) and a custom ROM (based on 2.245) so it can't be a ROM bug or the flashing process having gone wrong.
if it's not too much of a trouble for you, go and flash .245 stock, than .257 stock kernel only. like you are trying to root it for the first time, complete rooting procedure, and than proceed on to installing CWM, but instead of connecting device in debugging mode to install CWM, try and see if you can put it in a fastboot. this was exactly the moment when i accidentally put mine SP in fastboot. of course, i'm not saying to go ahead and install anything if you score, but only to confirm if you can put your device into a fastboot mode since installing anything without CWM will likely soft brick your device.
Same problem here, i can't do anything using flashtool after flashed 2.245. I did with SUS, maybe is some flashtool issue.
Ze Tolas said:
Same problem here, i can't do anything using flashtool after flashed 2.245. I did with SUS, maybe is some flashtool issue.
Click to expand...
Click to collapse
It may be a flashtool problem you are right because 2 incidents with different Roms that both use flashtool to flash those roms.....
its pretty much self explenatory.
skojevac said:
if it's not too much of a trouble for you, go and flash .245 stock, than .257 stock kernel only. like you are trying to root it for the first time, complete rooting procedure, and than proceed on to installing CWM, but instead of connecting device in debugging mode to install CWM, try and see if you can put it in a fastboot. this was exactly the moment when i accidentally put mine SP in fastboot. of course, i'm not saying to go ahead and install anything if you score, but only to confirm if you can put your device into a fastboot mode since installing anything without CWM will likely soft brick your device.
Click to expand...
Click to collapse
Interesting. Ok, I've read up on the process. So I use the various stock .ftf files and flashtool with the phone in flash mode? Bear in mind that kernel didn't allow fastboot when I used it with the stock .257 ROM the device came with. If I do it, I will nandroid backup first, of course, but I think I remember reading in one thread that someone managed to soft brick their XSP doing this very thing.
Bear in mind that kernel didn't allow fastboot when I used it with the stock .257 ROM the device came with. [/QUOTE said:
that's why you need to complete rooting procedure. root stock 1.257 kernel, than back to stock 2.245 with root preserved, and before you would install CWM try to put device in a fastboot mode, this assuming you still have a UB.
Click to expand...
Click to collapse
have you tried to boot into android, open a root terminal and type
exec reboot bootloader
that should bring you straight into fastboot
SuicideFlasher said:
have you tried to boot into android, open a root terminal and type
exec reboot bootloader
that should bring you straight into fastboot
Click to expand...
Click to collapse
All that happens is that the terminal session ends and closes (not FC) the terminal app. Using the same command via adb just does a standard reboot.
i just placed my in a fastboot mode, no problems whatsoever. do you have drivers for the device installed? you will find these in flashtool installation folder.
skojevac said:
i just placed my in a fastboot mode, no problems whatsoever. do you have drivers for the device installed? you will find these in flashtool installation folder.
Click to expand...
Click to collapse
Yes. The fastboot_with_android_usb_file.rar package specified on DooMLoRD's bootloader unlocking/relocking appears to have been removed and there are no new links in that thread. So, I found and installed the drivers included with the flashtool. But it seems to be the device that is the problem. It is acting like a carrier locked model. I am rapidly starting to believe that this one has a locked bootloader.
gandalf_grey91 said:
Yes. The fastboot_with_android_usb_file.rar package specified on DooMLoRD's bootloader unlocking/relocking appears to have been removed and there are no new links in that thread. So, I found and installed the drivers included with the flashtool. But it seems to be the device that is the problem. It is acting like a carrier locked model. I am rapidly starting to believe that this one has a locked bootloader.
Click to expand...
Click to collapse
I said before, it's new firmware (maybe RU) with a Windows Flashtool issue. Today i did flash kernel to my SP using Linux client.
Same issues
gandalf_grey91 said:
All that happens is that the terminal session ends and closes (not FC) the terminal app. Using the same command via adb just does a standard reboot.
Click to expand...
Click to collapse
Hi, I have some similar issues. I've also been flashing some stuff and whenever I try to go to fastboot it just boots into CWM. Very annoying to say the least. The dark blue light goes on when i hold down volume up and for a short moment I see the fastboot driver installing on my computer. But before it completes it's already in CWM.
Not sure what to do from here on wards, maybe some advice on which kernel to flash? I am pretty sure the latest kernel I flashed is the .254 root kernel from doomlord.
Ps. I really would like to flash CM when it becomes available as nightly :angel:
Thanks in advance!
Fast boot mode for xperia ion hspa???
gandalf_grey91 said:
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
Click to expand...
Click to collapse
I had already installed cm10.1 jb for my xperia ion.
Now i tried to install cm11 kitkat for my xperia ion.
Every thing is gone good.
But now got stuck up with a problem.
fast boot mode is active only for 5 seconds while connecting my xperia ion to System with flash tool.
help me to do the need ful.
Guide me to download compatible drivers and flash tool for fast booting process.
If you have UNLOCKABLE bootloader, then you dont have a FASTBOOT mode on your phone. Its just pure luck. some phones dont have it... kind of a sony crap... I also happen to be one of those LUCKY ppl. no unlock, so stuck with Stock kernel forever.
When you connect your phone to Flashtools in FLASHMODE...
See for a string BOOTLOADER: NOT_ROOTABLE.... it means you belong in the lucky group...
If it says rootable, then you're doing something wrong.
Pardon me if i read something incorrect. i skimmed through all the posts before posting.
Hi
Yesterday my phone dead? Reloop after sony logo, i cant go to recovery. (before i had Ressurection 5.0.2 rom)
Later i flashed boot.img for lollipop and phone booted with charger, but mt wifi don't worked and i tired to install another rom with cwm.
Later idk how my recovery changed to Cyanogenmod Recovery and i cant do anything
Now i flashed unrooted stock .tft and i still have loops.
When i try to flash boot.img i have problem with writing :
sending 'boot' (10182 KB)...
OKAY [ 0.337s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.339s
Click to expand...
Click to collapse
I have warranty but idk do I have to give my phone to service.
What i have to do?
m1ko8 said:
Hi
Yesterday my phone dead? Reloop after sony logo, i cant go to recovery. (before i had Ressurection 5.0.2 rom)
Later i flashed boot.img for lollipop and phone booted with charger, but mt wifi don't worked and i tired to install another rom with cwm.
Later idk how my recovery changed to Cyanogenmod Recovery and i cant do anything
Now i flashed unrooted stock .tft and i still have loops.
When i try to flash boot.img i have problem with writing :
I have warranty but idk do I have to give my phone to service.
What i have to do?
Click to expand...
Click to collapse
Well, sad to say, but you don't have the warranty anymore, as you have unlocked your bootloader, within erasing all your DRM keys (ironic, I know).
But if you have a TA-Partition backup, then you could just push in, (just be sure before pushing TA to flash stock .ftf with its kernel) and your DRM keys are back. Then you could proceed futher for warranty service.
Firstly, if you don't want go to warranty, try to flash Pabx Lollipo (it's stock lollipop). After that you could check if it has been fixed and flashing commands are properly working
LaurynasVP said:
Well, sad to say, but you don't have the warranty anymore, as you have unlocked your bootloader, within erasing all your DRM keys (ironic, I know).
But if you have a TA-Partition backup, then you could just push in, (just be sure before pushing TA to flash stock .ftf with its kernel) and your DRM keys are back. Then you could proceed futher for warranty service.
Firstly, if you don't want go to warranty, try to flash Pabx Lollipo (it's stock lollipop). After that you could check if it has been fixed and flashing commands are properly working
Click to expand...
Click to collapse
DRM keys ? What is that?
I locked bootloader before and deleted all files accidentally
How to flash this file?<--- nvm
Can i flash userdata.img in flashtool? Idk why fastboot dont work in cmd .-.
Edit2: After flash Unrooted ftf PC Companion accepted my phone and now my phone is repairing, i will write later does it works.
Edit3: PC companion repair dont work too.
m1ko8 said:
DRM keys ? What is that?
I locked bootloader before and deleted all files accidentally
How to flash this file?<--- nvm
Can i flash userdata.img in flashtool? Idk why fastboot dont work in cmd .-.
Edit2: After flash Unrooted ftf PC Companion accepted my phone and now my phone is repairing, i will write later does it works.
Edit3: PC companion repair dont work too.
Click to expand...
Click to collapse
DRM keys are stored in your TA-Partition, they're required for many functions to work: Clear audio, Camera functions, Official ROM and it's updates (If i'm right with this one) and other.
I recommend you to download android SDK, then go to it --> Platform tools --> SHIFT + RMB (right mouse button) --> Open Command Prompt Here.
After that, shut down your phone. Wait atleast 30 seconds. then by holding Vol +, plug it into PC. Blue LED should show up.
Then in CMD type this:
fastboot devices
Click to expand...
Click to collapse
It should be returned some numbers and letters. If it doesn't show anything, then your windows maybe doesn't support fastboot or you don't have drivers to that (fastboot + adb drivers).
Make sure in this folders are fastboot.exe and adb.exe (the most importantly to us is fastboot.exe) and some other files as well.
If ir returns information correctly, then you can download any rom and extract it (I sugges you to use Pabx).
Extract everything from .ZIP/.RAR, you should see system.img, boot.img, userdata.img. Place them into platform-tools directory (where fastboot.exe and other files are).
Then simply write these commands in CMD:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
If everything will go OK, then you can reboot your device:
fastboot reboot
Click to expand...
Click to collapse
Then your phone should start normally, after that you can manually install CWM and other things either.
If it didn't work, just quote me regarding the problem, I'll try to help you
LaurynasVP said:
DRM keys are stored in your TA-Partition, they're required for many functions to work: Clear audio, Camera functions, Official ROM and it's updates (If i'm right with this one) and other.
I recommend you to download android SDK, then go to it --> Platform tools --> SHIFT + RMB (right mouse button) --> Open Command Prompt Here.
After that, shut down your phone. Wait atleast 30 seconds. then by holding Vol +, plug it into PC. Blue LED should show up.
Then in CMD type this:
It should be returned some numbers and letters. If it doesn't show anything, then your windows maybe doesn't support fastboot or you don't have drivers to that (fastboot + adb drivers).
Make sure in this folders are fastboot.exe and adb.exe (the most importantly to us is fastboot.exe) and some other files as well.
If ir returns information correctly, then you can download any rom and extract it (I sugges you to use Pabx).
Extract everything from .ZIP/.RAR, you should see system.img, boot.img, userdata.img. Place them into platform-tools directory (where fastboot.exe and other files are).
Then simply write these commands in CMD:
If everything will go OK, then you can reboot your device:
Then your phone should start normally, after that you can manually install CWM and other things either.
If it didn't work, just quote me regarding the problem, I'll try to help you
Click to expand...
Click to collapse
Thanks, i know how to use fastboot but xperia dont charge. I will do everything what u said for a while and i leave edit.
btw. Thanks
Edit: Idk it's important but before it in android 5.0.2 Ressurection ROM sometimes it turn off without charger plugged , i think it was ROM fail
Edit1: Do you think it's better solution than SUS repair?
Edit2:After flash tired to turn on phone but red led blinked 3 times , then i connect phone to charger and red led blinks every 1-2 second. What i have to do?
@m1ko8
Don't be panic
download latest z fw .292 ftf then download flashtool and install it and goto C>flashtool>drivers install that file,then put downloaded ftf to firmware folder ,after run flastool and click thunder icon select flashmode select fw and wait prepairing then connect device when notify popup massage.then progress bar fill when it end disconnect cable and power on ur device
Isuru cs said:
@m1ko8
Don't be panic
download latest z fw .292 ftf then download flashtool and install it and goto C>flashtool>drivers install that file,then put downloaded ftf to firmware folder ,after run flastool and click thunder icon select flashmode select fw and wait prepairing then connect device when notify popup massage.then progress bar fill when it end disconnect cable and power on ur device
Click to expand...
Click to collapse
When I try to install this drivers with checked fastboot and flashtool drivers "Installation failed" for both drivers.
After install FTF my phone still stuck on sony logo and restart , its important what firmware i install? (region?) I have from Play in Poland then i must install Firmware Play PL ? I installed Firmware UK and RU and EU . still i have bootloop.
I tired too repair with pc companion. hmm.. bad luck, today probably i will give my phone to service
m1ko8 said:
When I try to install this drivers with checked fastboot and flashtool drivers "Installation failed" for both drivers.
After install FTF my phone still stuck on sony logo and restart , its important what firmware i install? (region?) I have from Play in Poland then i must install Firmware Play PL ? I installed Firmware UK and RU and EU . still i have bootloop.
I tired too repair with pc companion. hmm.. bad luck, today probably i will give my phone to service
Click to expand...
Click to collapse
I'm sorry to tell you, but you phone doesn't have warranty anymore and specilized Sony staff won't take it for fixing, as you have unlocked your bootloader, so you need take it to local repair service (Sony might fix it, but with some price of course).
Either way, you can try install drivers on other computer, if you have one, then try on it.
LaurynasVP said:
I'm sorry to tell you, but you phone doesn't have warranty anymore and specilized Sony staff won't take it for fixing, as you have unlocked your bootloader, so you need take it to local repair service (Sony might fix it, but with some price of course).
Either way, you can try install drivers on other computer, if you have one, then try on it.
Click to expand...
Click to collapse
I locked bootloader before. Repair with PC companion. Bootloader is locked and when i unlocked it (have unlock code) after reconnect fastboot it was locked again. idk how I think they can't see it cause its power and software problem and service give me new phone . They can see i had unlocked bootloader ?
I think something inside phone overheated and i dont thinnk so does Polish service see it
m1ko8 said:
I locked bootloader before. They can see it?
I think something inside phone overheated and i dont thinnk so does Polish service see it
Click to expand...
Click to collapse
Yeah, if your phone is psychical damage (overheated) and doesn't turn on, then they may change it for you to another one, but If they will bring the life back to it, they would be able to see if DRM keys are in their place, and even if you've re-locked your BL, it doesn't change the situation at all, because in the service menu they could check if DRM keys are not erased, if so - they will not fix it under the warranty
LaurynasVP said:
Yeah, if your phone is psychical damage (overheated) and doesn't turn on, then they may change it for you to another one, but If they will bring the life back to it, they would be able to see if DRM keys are in their place, and even if you've re-locked your BL, it doesn't change the situation at all, because in the service menu they could check if DRM keys are not erased, if so - they will not fix it under the warranty
Click to expand...
Click to collapse
2 days ago my phone stay in my bed at night witch charger and he was very hot. Later i dont turn it on again.
Yesterday i connected my phone to charger and he dont charging. I can go to flashmode and fastboot .Installing system throught fastboot , pc companion repair dont worked. I think they are too lazy to check it.
I have no choice , money is no problem anyway i must repair it
Edit: Now wait ~2 weeks >.<
LaurynasVP said:
Yeah, if your phone is psychical damage (overheated) and doesn't turn on, then they may change it for you to another one, but If they will bring the life back to it, they would be able to see if DRM keys are in their place, and even if you've re-locked your BL, it doesn't change the situation at all, because in the service menu they could check if DRM keys are not erased, if so - they will not fix it under the warranty
Click to expand...
Click to collapse
Some news
Service gave me new Xperia Z (under warranty ofc)
m1ko8 said:
Some news
Service gave me new Xperia Z (under warranty ofc)
Click to expand...
Click to collapse
Cool! I'm happy for you!
And try to not harm your phone anymore, make care of it
LaurynasVP said:
Cool! I'm happy for you!
And try to not harm your phone anymore, make care of it
Click to expand...
Click to collapse
They informed me about motherboard repair. But they gave me new phone
Now i have Android 5.1 and unlocked bootloader But i will take care of my phone .
But.. what ROM You recommend for nice look and smooth work ( You like lollipop? )
They gave you a new z with lollipop preinstalled? Or did you flash a custom rom?
shoey63 said:
They gave you a new z with lollipop preinstalled? Or did you flash a custom rom?
Click to expand...
Click to collapse
Dont be funny OFC I flashed .
m1ko8 said:
They informed me about motherboard repair. But they gave me new phone
Now i have Android 5.1 and unlocked bootloader But i will take care of my phone .
But.. what ROM You recommend for nice look and smooth work ( You like lollipop? )
Click to expand...
Click to collapse
@m1k8 I suggest you to use Validus ROM. Just now I'm waiting for 5.1 update @shoey63 - of course he has phone with an unlocked bootloader, even he said so, that means he just pre-installed it by himself
LaurynasVP said:
@m1k8 I suggest you to use Validus ROM. Just now I'm waiting for 5.1 update @shoey63 - of course he has phone with an unlocked bootloader, even he said so, that means he just pre-installed it by himself
Click to expand...
Click to collapse
What version ? Validus-LP-v7.0-2015-03-09 or Validus-LP-v7.0-2015-03-11? ( New version not always is better)
m1ko8 said:
What version ? Validus-LP-v7.0-2015-03-09 or Validus-LP-v7.0-2015-03-11? ( New version not always is better)
Click to expand...
Click to collapse
09-03 for now. I'm not sure which version was perfect working, as the newest 03-11 isn't working properly as it should to.
Now I'm waiting for the update to 5.1.. I do know that from 03-08 there will be lots of bugs : screen always on, even if you turn of it just will turn to grey color, that's all, ambient auto display doesn't work either and some other problems.
So, I suggest you to try only from 03-03 to 03-08
LaurynasVP said:
09-03 for now. I'm not sure which version was perfect working, as the newest 03-11 isn't working properly as it should to.
Now I'm waiting for the update to 5.1.. I do know that from 03-08 there will be lots of bugs : screen always on, even if you turn of it just will turn to grey color, that's all, ambient auto display doesn't work either and some other problems.
So, I suggest you to try only from 03-03 to 03-08
Click to expand...
Click to collapse
Understand
So , I decided to install ressurection ROM , and work perfect ( Validus rom is dark , i dont like dark themes and have some bugs , Ressurection is for me much better. )
Note : This guide is for H-81120-I & H-81120-O the latest update any firmware version below it will cause hard-brick so be careful before attempting anything, i wont be held responsible.
As a user with less knowledge about Commands and all, i was searching for answers by reading threads here and there and found my answers though some time tricky and sometimes easy.
Also in reading those threads i found many fellow members stumble upon resulting Soft bricks and in some cases a Hard brick or can say making their beloved G4 a paper weight.
So i thought i must put some really easy steps in order to clearly guide people like me who are too noob to understand the sophisticated developers steps.
Another reason for this Thread is also i saw many people asking about how to etc after updating to 20-O update for our H811 MM.
Few things to Prepare before Start
1- Properly Install Drivers for your H811 Variant of G4, cant find them Install LG Bridge.
2- Read the Whole thread before starting anything.
3- Confirm that all requirements are full filled and your variant is capable of everything mention in the OP.
4- Enable Developer Option then inside it enable OEM unlock and Usb debugging.
5- Always use Command prompt as Administrator.
6- Make a folder name G4 and paste all the file required for the unlocking in it for easy access and remembrance.
7- For Safer side after unlocking the bootloader boot into TWRP from fast boot and do not install TWRP.
8- Flash your SuperSU after that boot into android and see if all works.
9- Again Via Fastboot boot into TWRP make a backup of everything working fine. Boot into android.
0- Again same Via Fastboot boot into TWRP and now install your TWRP image via TWRP install function. So if by any means this is the culprit you can still revive your phone via your backup.
Attachments to Download
1- Adb Package can be found Here.
2- Download the latest TWRP.img 3.0+ from Here . This file needs to be on your computer and external sdcard.
3- Download the latest SuperSu zip (2.67+) from Here [Thanks to Chainfire] and stick on external sdcard as well.
Since downloading is complete now simply unzip the adb folder (containing fastboot by default) and paste both the TWRP image file and SUPERSU zip inside it.
Now Hold Shift and Open Command prompt here.
1- Input command to see if your device is visible in ADB.
Code:
adb devices
if you see your device and the status is off line then there will be a prompt on your G4 screen waiting for approval, accept it and input same command now all will be fine.
2- Now input below commands one by one. ( All credits to Autoprime )
Code:
adb reboot bootloader ( This will reboot your device to Fastboot mode )
fastboot oem unlock ( This will wipe all your data )
fastboot getvar unlocked ( This will check your bootloader status: Should be successful )
fastboot boot twrp-3.0.2-0-h811.img ( Phone boots TWRP ) Please put the full file name with .img extension or it wont work.
3- Now the Phone should be in TWRP install SuperSU from there which you have already pasted inside your external SD card.
4- Reboot to system and see if SuperSU is installed. In some cases First flash of SuperSU does not work if your case is same the again boot to Fastboot and from there boot into recovery, since your bootloader is unlocked no need to repeat the unlock OEM command.
5- Now for safer side follow the steps 7, 9, 0 mention in Preparation heading above.
Hopefully all will be in your favor.
Useful Links if you still fail
Kdz 20-O after download must be unzipped
H81120o_00_0613.kdz
LGUP Software:
( All credits to MicroMod777 )
Disclaimer: Nothing in this thread is my work, if i have missed any credit please do let me know i will add. I know several guides are available for same purpose so if any body finds it offending any rights can ask the moderators to remove this thread. The purpose only is to guide simple people like me to save their devices from getting bricked.
As by reading the thread many people are falling for permanent TWRP installation as its mention in the OP anyways for people not getting permanent Recovery follow below:
Boot to TWRP from fastboot Bootloader
When recovery comes up click Install >>>> then in the right below corner you ll see a tab for IMAGE >>> press it browse the recovery IMG which you stored in your SD card >>> swipe to flash >>> From asking where to install >>> select recovery >>> DONE.
SignatureBoy said:
Attachments to Download
1- Adb Package can be found Here.
2- Download the from Here . This file needs to be on your computer and external sdcard.
3- Download the latest SuperSu zip (2.67+) from Here [Thanks to Chainfire] and stick on external sdcard as well.
Click to expand...
Click to collapse
Indeed needs to be in both but needs to be in the same Folder as Fastboot file, if not wont work.
beside will be cool if you add a NOTE about if they are in 20o they must stick with 20o base roms, if not they'll get Hard-Brick.
DrakenFX said:
Indeed needs to be in both but needs to be in the same Folder as Fastboot file, if not wont work.
beside will be cool if you add a NOTE about if they are in 20o they must stick with 20o base roms, if not they'll get Hard-Brick.
Click to expand...
Click to collapse
the ADB package i uploaded contains the Fastboot inside it
The thread clearly states it for 20-O
SignatureBoy said:
the ADB package i uploaded contains the Fastboot inside it
Click to expand...
Click to collapse
ok i meant the TWRP file needs to be in the same folder where Fastboot file is
DrakenFX said:
ok i meant the TWRP file needs to be in the same folder where Fastboot file is
Click to expand...
Click to collapse
That is also mention if you read the first post,
Since downloading is complete now simply make a folder and put all files downloaded inside it unzip the adb folder and paste both the TWRP image file and SUPERSU zip inside it.
Click to expand...
Click to collapse
SignatureBoy said:
DrakenFX said:
beside will be cool if you add a NOTE about if they are in 20o they must stick with 20o base roms, if not they'll get Hard-Brick.
Click to expand...
Click to collapse
The thread clearly states it for 20-O
Click to expand...
Click to collapse
Guys,
If I read it right:
LG G4 must be on 20o (stock) to follow this instruction.
If it’s on 20i or below, it must be updated to 20o (OTA or whatever) first!
It might be obvious for you, but not for me.
Again, but better be safe, then sorry.
ApokrifX said:
Guys,
If I read it right:
LG G4 must be on 20o (stock) to follow this instruction.
If it’s on 20i or below, it must be updated to 20o (OTA or whatever) first!
It might be obvious for you, but not for me.
Again, but better be safe, then sorry.
Click to expand...
Click to collapse
yes it is for 20-O only
SignatureBoy said:
yes it is for 20-O only
Click to expand...
Click to collapse
Thanks for clarification. I’d change 1st post a bit:
Few things to Prepare before Start
0. LG G4 with 20o (stock) firmware.
When I do adb reboot bootloader it just boots me back into Android... shouldn't it take me to the Fastboot screen?
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
DanGarion said:
When I do adb reboot bootloader it just boots me back into Android... shouldn't it take me to the Fastboot screen?
Click to expand...
Click to collapse
Nevermind, I forgot about OEM Unlock...
thanks for the write up
This is not specific to 20o. It's the same steps we've been using all along. Nothing new to see here.
Sent from my LG-H811 using XDA-Developers mobile app
problem with fastboot
Thanks you for helping:fingers-crossed:
problem with fastboot
Hi,
I am a newbie in xda. I am trying to root and install TWRP into my lg g4. I am using software version H81120o. I checked enable OEM unlock and USB debugging. I have downloaded lg driver though lg bridge and all the files from the post. However, I got two problem while installing the twrp-3.0.2-0-h811.img.
1st problem (stuck here and need to reboot also not showing h811 on "the list of devices attached" after typing command "adb reboot bootloader"):
C:\Windows\system32>adb devices
List of devices attached
LGH811xxxxxxxx device
C:\Windows\system32>adb reboot bootloader
C:\Windows\system32>fastboot oem unlock
...
FAILED (remote: Already unlocked)
finished. total time: 0.012s
C:\Windows\system32>fastboot getvar unlocked
unlocked: yes
finished. total time: 0.004s
C:\Windows\system32>fastboot boot twrp-3.0.2-0-h811.img
cannot load 'twrp-3.0.2-0-h811.img': No error
2. 2nd problem(stuck here and need to reboot):
C:\Windows\system32>fastboot boot twrp-3.0.2-0-h811.img
< waiting for device >
I checked online this problem might do with driver not up to date. Under device manager, my lg g4 is recognized under android device with android bootloader interface.
What should I do now?
Thanks you for helping:fingers-crossed:
This Root-Method worked like a charm... The only issue I'm running into is for the TWRP recovery to actually stick. When i manually reboot into recovery I get the little android guy with his chest open and the red triangle with the "!" in the middle.....am I doing something wrong by any chance??
I did everything but can't seem to get TWRP installed
Thanks a lot for this write up. I have been trying for about 2 weeks to root my g4 and it worked finally, So many thanks to you
The Remedy said:
This Root-Method worked like a charm... The only issue I'm running into is for the TWRP recovery to actually stick. When i manually reboot into recovery I get the little android guy with his chest open and the red triangle with the "!" in the middle.....am I doing something wrong by any chance??
Click to expand...
Click to collapse
same problem here but I just now got it working...sort of . I still can not make anything come up except the factory data reset when I use the phone volume and power button.
I thought it might be just that I wasn't coordinated enough so I downloaded this small app to do a recovery reboot.
After I installed the app and used it, I got the little android guy with his chest opened with the red triangle. I took out my battery, put it back in and booted my phone with the power button.
I then connected my phone to computer via usb and went back into adb and opened TWRP and installed the twrp-3.0.2-0-h811.img again but this time I looked around a little more first, and noticed a setting to either install in boot or recovery partition. I selected recovery partition (neither were selected) and installed it. Now I can boot to TWRP recovery with the app I installed but still nothing but factory data reset with the volume and power buttons. I can live with this for a while until I can maybe find a solution.
I had the same issue but when u get into twrp make sure the IMG is in your SD card and to permanently have twrp installed go to home and press install.. Choose from image and install hope this helps
Sent from my LGLS992 using Tapatalk
fuzzy_ said:
same problem here but I just now got it working...sort of ................
Now I can boot to TWRP recovery with the app I installed but still nothing but factory data reset with the volume and power buttons. I can live with this for a while until I can maybe find a solution.
Click to expand...
Click to collapse
In regard to booting into TWRP recovery with just the power and vol buttons, I just read this on another thread:
It boots into what appears to look like a default LG G4 factory reset page. For me, i clicked reset, and then yes, and surprisingly it brought me to where i wanted to go. TWRP Recovery.
I tried this and it worked for me as well.
I had been there before and tried it and it did a factory reset after I had spent an hour or two tweaking my phone, I was not a happy person. This time I did feel almost positive I had TWRP installed correctly and did not have nearly as much time spent getting things set up like I want them on my phone...It was still scary pressing that reset button and yes button.
If you don't have TWRP (or maybe some other recovery) installed it will factory reset your phone. I just thought I would share this and what happened with me. Do it at your own risk.