WARNING
READ AND FOLLOW ALL STEPS CAREFULLY
This guide may have errors and may not work for some in various scenario. If you report them, I may try to explain or correct your steps.
Read properly and DON'T SEND PM, I will simply ignore PM and laugh on you.
Phone must have "UNLOCKED BOOTLOADER" or you may Unlock it with the help of another guide in second post below.
USE INFORMATION AT YOU OWN RISK.
==================================================
STEP BY STEP NEW GUIDE to Easy Root Without PC + Unlock of LG L9 [No Fastboot] DIRECTLY ON PHONE
Introduction
This visual step by step two in one guide can ROOT (unlocked) LG L9 and FLASH RECOVERY without PC.
Useful for new LG L9 phone owners or someone who just unbricked phone by flashing stock kdz. Works on any stock rom.
ROOTING WAS NEVER A FUN LIKE THIS BEFORE. BYE BYE YOU BLOODY @#[email protected]# FASTBOOT METHOD. SO NO DIFFICULT FASTBOOT DRIVER INSTALLATION. THIS AMAZING ROOTING METHOD DOES NOT NEED FASTBOOT METHOD AT ALL
100% WORKING , TESTED ON MY PHONE AND THEN MADE GUIDE.
This is not my own discovery. But for newbies like me, I always have gathered all INFORMATION and FILES together and made this useful step by step guide. Experts can still stay away, than criticize.
Step 1) Preparations:-
In Settings >>> Developer Options >>> Select check mark on for "USB Debugging Mode"
In Settings >>> Security >>> Select check mark on for "Unknown Resources"
Download this MAIN ROOTING zip file and extract/copy all files in the root folder of sdcard on phone. The list of files can be seen in this image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 2) Install LGPwn.apk
From file-manager, find and Install and Run "LGPwn.apk" which you will show first screen to select as "Root Me" as shown in following screen. Then you will see first time SuperSU asking for granting permission, select "Deny" yes "Deny" for first time. (In some cases this SuperUser permission box may not come, dont worry about that.)
Step 3)
Now you will see four instruction screens as follows, just bypass them by clicking "Next" like we always do. Its nothing special but information about its rooting process.
Step 4)
Now you will see EULA License, you need to read and "Accept", now LGPwn will backup root information and will show next screen titled "Backup" but press "Restore" button in that screen as shown below.
Step 5)
Now you will see "Restore Location" screen, select "Internal Storage"
Then "Restore" screen where you click on "LGPwn" entry as shown below.
Step 6)
Then "Selection" Screen will come with dialogue box Cross Model, click "OK" and "Continue" as shown below.
Then another Warning dialogue box appears, click "Restore" and then press "Continue" on main page to go ahead.
Step 7)
Now phone is almost rooted but still some more step to finish it fully.
Step 8) Install Super User.
Now from file manager find , install and run "Super SU" app we copied before. ("eu.chainfire.supersu-1.apk")
Now your phone is rooted fully. Close SuperSU app.
Step 9) Install Recovery with Flashify
Now from file manager find , install and run "Flashify" app we copied before. ("com.cgollner.flashify-1.apk")
"Accept" the Disclaimer, "Grant" Superuser permission, and then click on "Choose a file" on Flash Recovery section box.
Step 10)
Now Flashify will ask you for file-manager name to select Recovery file. Select "Flashify File Explorer" and press "Once".
Now File Explorer will show root area of Phone, here select "SDCARD" and then select file named "recovery-clockwork-touch-6.0.4.5-p760.img" and confirm it by pressing "Yup!"
Note: You can choose any other compatible recovery like PhilzRecovery or TWRP.
When Flashify successfully copies recovery in Recovery partition you should press "REBOOT NOW" to go in recovery mode.
Step 11)
When phone reboots you will see CWM 6.0.4.5 Recovery main screen. YOU ARE DONE!!! Enjoy
This is all CLICK AND GO kind of thing and everything went very smooth on my LG L9 P765 in single attempt like a charm and took less than 2 minutes.
Hope it helps! As usual!
==========================================
CREDITS: Thanks a lot to all the maker of...
1) LGPwn
2) Flashify
3) SuperSU
4) CWM
4) LG for making this phone
5) Youtube video which helped to document it.
6) Anyone who might be responsible. Please remind if I left anyone.
==========================================
HIT THANKS IF YOU LIKE THE INFO-GUIDE
==========================================
Guide to Unlocked Bootloader (ULBL) of LG L9 P760/P765 and other variants.
Guide to Unlocked Bootloader (ULBL) of LG L9 P760/P765 and other variants.
=============================================
Things to remember while proceeding.
IMPORTANT: You must have P760/P765 with P760 V20B EUROPE OPEN rom flashed on it ....or OTHER UNLOCKABLE ROMS. @Gh0sT.RPG tried unlocking on P765 V20B, V20C & V20D all unsuccessful. But He unlocked on P65 V20A Indian in just few mins.
======================================================
How to Unlock Bootloader and do Easy Rooting of L9 P760/765/P768
Step 1) Preparations:-
Download and Install latest LG Driver on Computer (This is for ADB drivers).
Download and extract Android.zip on computer, preferably D drive. The folder "C:\Android" will be automatically created with all necessary files. (You can use D drive also in case of problems saving or running on C drive on Windows 8 or 8.1
In Settings >>> Developer Options >>> Select check mark on for "USB Debugging Mode"
In Settings >>> Security >>> Select check mark on for "Unknown Resources"
Step 2) ADB Mode Connection:-
Now connect phone to pc with USB cable and change USB Mode to "LG Software Mode". Now your windows will install drivers and in Device Manager you will see following ADB PORT entry "USB Modem Phone ADB Port" (or some other words with name ADB).
Step 3)
Now wait for 30 minutes if you want to unlock bootloader (IMPORTANT Read post) and then open "Command Prompt" and give following commands in windows command prompt.
C:\Users\Mahendra\>cd \android
C:\Android>adb devices
Click to expand...
Click to collapse
This should show the list of attached devices in ADB mode like shown below.
Step 4)
Now pass this command in "lower case" only because adb commands are case sensitive.
C:Android\>adb reboot oem-unlock
Click to expand...
Click to collapse
Phone will restart in pre-fastboot mode.
AT THIS POINT, YOU WILL UNLOCK BOOTLOADER:
You will get two options and to select UNLOCK you need to press VOLUME UP key which will unlock the bootloader permanently and when you press VOLUME UP key your phone is UNLOCKED and phone will go in FastBoot mode.
(*Sorry no screenshot available of these two options. Second option is something else I don't remember now, but forget it.)
Once unlocked this Unlock options screen will never show up in future.
Now you will see "Fast Boot mode" screen like shown below. But you don's have to do anything in Fastboot mode so just Remove USB cable. Remove battery and reinsert battery and you may start phone normally.
You are done! Your LG L9 is now with Unlocked Bootloader.
For more information you can visit my old Guide made for same purpose here
http://forum.xda-developers.com/showthread.php?t=2221102
Change Log
Reserved for FAQ
Reserved for misc information
so will the unlock portion work on lgms769 (MetroPCS)
with the ENCRYPTED Bootloader (10-13 date under battery.)??
nu2moding said:
so will the unlock portion work on lgms769 (MetroPCS)
with the ENCRYPTED Bootloader (10-13 date under battery.)??
Click to expand...
Click to collapse
No. Rooting will work only on Unlocked Bootloader. Clearly mentioned in first post.
That Flashify can flash any recovery.img file?
P760
I have LG L9 P760 on V20H firmware. Funny thing is i used LGPwn Tool about a year ago to root my device but did not do extra steps with SuperSU download and stuff just downloaded app installed it and run it, root is running just fine. But I cannot access my Recovery so I guessed that my bootloader is locked. But if it is locked how did LGPwn tool worked for me.
When I run Recovery mode I get green droid with red ( ! ) over it so i thought it must be cuz bootloader is locked. But when I run your unlock method I just get standard reboot. I have all drives installed as well as full android SDK with Google drives installed that should cover Fastboot (right?). I did follow some tutorials here to install fastboot on my PC but I am not sure who to check if everything is installed tho.
Now if I run 3845#*760# in phone dialer and check for bootloader lock it says that it is locked.
What could be issue with this? Drivers on PC or something else on phone?
Thank you for your work.
nhoc_maruko9x said:
That Flashify can flash any recovery.img file?
Click to expand...
Click to collapse
I tried Mobile Uncle Tool, it could not flash any recovery. So did try Flashify latest version and it worked.
Though I did not try TWRP but it flashed all CWM versions I tried. Thats why added four variations. One version without Touch. Technically it should flash any recovery, including Philz too.
darkodelta said:
I have LG L9 P760 on V20H firmware. Funny thing is i used LGPwn Tool about a year ago to root my device but did not do extra steps with SuperSU download and stuff just downloaded app installed it and run it, root is running just fine. But I cannot access my Recovery so I guessed that my bootloader is locked. But if it is locked how did LGPwn tool worked for me.
When I run Recovery mode I get green droid with red ( ! ) over it so i thought it must be cuz bootloader is locked. But when I run your unlock method I just get standard reboot. I have all drives installed as well as full android SDK with Google drives installed that should cover Fastboot (right?). I did follow some tutorials here to install fastboot on my PC but I am not sure who to check if everything is installed tho.
Now if I run 3845#*760# in phone dialer and check for bootloader lock it says that it is locked.
What could be issue with this? Drivers on PC or something else on phone?
Thank you for your work.
Click to expand...
Click to collapse
You tried LGPwn a year ago and obviously it was working for few modesl only. I tried this with latest LGPwn, which I guess is February/March 2014 version. With obvious reason it will not work on Locked bootloader. But you have P760 so you have change to unlock it but first flash old stock rom, as mentioned in 2nd post in this thread and also in my other old thread.
Unlocking Bootloader was possible on only few versions of ICS/JB. Flash ICS V10D then unlock and then try this rooting and installing recovery. Should work. Once you have installed Recovery, you can do anything with this phone
Now fastbook is history, not required at all.
Press thanks button if you like this information.
@cmahendra
I see, I am very glad that fastboot is gone(kinda). Is there anyother way of flashing custom ROM on to L9 other then method you showed here. I used this method long ago when I got my phone in bad shape after trying to install CWM using Arthas installer. And could not get it working. I mean I can try it again, could not find anything about flashing new rom other then what you posted. As well I could not find V10D but I guess V20B EO can work?
Thanks.
darkodelta said:
@cmahendra
I see, I am very glad that fastboot is gone(kinda). Is there anyother way of flashing custom ROM on to L9 other then method you showed here. I used this method long ago when I got my phone in bad shape after trying to install CWM using Arthas installer. And could not get it working. I mean I can try it again, could not find anything about flashing new rom other then what you posted. As well I could not find V10D but I guess V20B EO can work?
Thanks.
Click to expand...
Click to collapse
Thanks
Actually my OFFLINE FIX FLASHING method is easiest of all. Only problem with people is the SEQUENCE ERROR. I can still guide you if you post your problem in that thread. I thing I should make some changes in that thread by changing few words or lines where possibly a confusion arises. If interested post your query which step you find it difficult or error.
So, the steps are:
1. Unlock phone that has a factory stock ROM using your unlock method, then proceed to 2.
1a. Reflash/Unbrick phone with kdz stock ROM if already modified with other ROM, proceed to 1b.
1b. See 1.
2. Root phone with your method. (PC may be used to move files to sdcard?)
I have a factory stock ROM, never been rooted or modified.
Will this work with US T-Mobile LG L9 P769?
Post Flash
cmahendra said:
Thanks
Actually my OFFLINE FIX FLASHING method is easiest of all. Only problem with people is the SEQUENCE ERROR. I can still guide you if you post your problem in that thread. I thing I should make some changes in that thread by changing few words or lines where possibly a confusion arises. If interested post your query which step you find it difficult or error.
Click to expand...
Click to collapse
I have managed to flash V20B Open Europe to my P760. (ROM is from this thread ) Could not find any other KDZ.
Now I have restored my device to factory settings just as you said in other thread and this fixed all system apps that where broken.
Following that I pluged it in and waited for half an hour. Then started cmd and entered all of the commands (adb devices detects my device and Device manager sees my phone as ADB Interface > AndroidNet Sooner Single ADB Interface.) Now I started adb reboot oem-unlock. And it restarted my device but just that it did not go to prefastboot menu or anything similar just regular reboot. I read your old thread on this and cannot find problem.
darkodelta said:
I have managed to flash V20B Open Europe to my P760. (ROM is from this thread ) Could not find any other KDZ.
Now I have restored my device to factory settings just as you said in other thread and this fixed all system apps that where broken.
Following that I pluged it in and waited for half an hour. Then started cmd and entered all of the commands (adb devices detects my device and Device manager sees my phone as ADB Interface > AndroidNet Sooner Single ADB Interface.) Now I started adb reboot oem-unlock. And it restarted my device but just that it did not go to prefastboot menu or anything similar just regular reboot. I read your old thread on this and cannot find problem.
Click to expand...
Click to collapse
I am asumming you have P760/P765 and its good sign that you did everything perfect until "oem-unlock" command.
That's strange to see its booting normally. That means you are not getting fastboot mode also, as shown in screenshot? Your BL seems still Locked but there could be some other issue with bootloader. Try with ICS rom. See if the link of ICS are or not. I forgot exactly which V10 version worked for unlocking bootloader. Read old thread carefully.
Some other devs are claiming they can unlock bootloader with different method. Try that too.
ICS/JB
cmahendra said:
I am asumming you have P760/P765 and its good sign that you did everything perfect until "oem-unlock" command.
That's strange to see its booting normally. That means you are not getting fastboot mode also, as shown in screenshot? Your BL seems still Locked but there could be some other issue with bootloader. Try with ICS rom. See if the link of ICS are or not. I forgot exactly which V10 version worked for unlocking bootloader. Read old thread carefully.
Some other devs are claiming they can unlock bootloader with different method. Try that too.
Click to expand...
Click to collapse
I have flashed ICS (V10A Europe Open) as well as JB (V20B Europe Open) None of them worked from me. Unfortunately adb reboot oem-unlock does not work on my p760 at least on these ROMs. Just standard reboot.
Gonna try to find some other ROMs and try again tomorrow.
Bootloader
I have tested this with V20B again and nothing worked.
Now I have reinstalled Google USB drivers and tried to run some adb commands to so what happens.
After running
adb reboot bootloader phone just restarts no bootloader screen.
When I run fastboot devices nothing shows adb devices sees it tho.
fastboot reboot-bootloader as well does nothing in my case.
Could this be that bootloader is damaged in some way or something similar? Maybe I need to flash new partitions and then repeat process.
darkodelta said:
I have tested this with V20B again and nothing worked.
Now I have reinstalled Google USB drivers and tried to run some adb commands to so what happens.
After running
adb reboot bootloader phone just restarts no bootloader screen.
When I run fastboot devices nothing shows adb devices sees it tho.
fastboot reboot-bootloader as well does nothing in my case.
Could this be that bootloader is damaged in some way or something similar? Maybe I need to flash new partitions and then repeat process.
Click to expand...
Click to collapse
I suspected same thing in previous post. May be your bootloader is corrupted or something else might have happened. By the way I dont think Android partitions are related to bootloader. Its complete different location than android partitions. But I may be wrong in case of this model.
So this works with T-Mobile's LG-P769. However, i did have to have SuperSU installed PRIOR to running pwnLg apk. Also, do not use flashify on the 769 unless your bootloader is unlocked.
elesbb said:
So this works with T-Mobile's LG-P769. However, i did have to have SuperSU installed PRIOR to running pwnLg apk. Also, do not use flashify on the 769 unless your bootloader is unlocked.
Click to expand...
Click to collapse
Not only p769, I clearly mentioned that this method works perfectly on Unlocked Bootloader only with any L9 variant phone.
Sent from my C2305 using XDA Free mobile app
Related
Hey all,
I have a CWM backup of my current rom and have backups of apps and data but am stuck at a bootloop.
As I have read countless articles, it seems my error is because I have a locked bootloader(not actually sure). Though, I only tried to flash
clockcycle's wiped v20d cwm backup file. It failed part way saying it couldn't write to /system.
Since then, I haven't been able to fully enter CWM. just see the red triangle with the droid guy on his back.
I have read Cmahendra's unbricking guide but it doesn't work as I have installed JB and even the tips to unplug, wait 10s and reopen the program to flash again it still won't work. Still stops at 15% saying error connecting to the phone.
There is a similar thread which had this exact problem which said to
use the online method to recover your phone since I had already installed JB. I edited the hosts file to remove the fake offline server and opened up the b2CAppsetup.exe, clicked on customer support,
entered my model LGP769BK and my S/N and it began to start the process and 'analyze' then crashed and said "updating is not possible any longer due to a fatal error while the LG mobile phone software Update"
I've tried to search this out myself and not waste any space but I'm at loss here. If anyone has any help, it would be much appreciated
as I don't have a phone while this is not working.
I've tried all the ways to to hard reset, master reset and still I get the droid guy on his back. I can get to S/w mode like all the other posts say to do but none of those fixes seem to work for me. Am I missing something?
Do I have any options here? I have kind of read that I should just unlock the bootloader but I don't think that applies in my case as I can't turn on my phone fully.
edit: for the online method(LG support tool), it basically cancels when it goes to the 'downloading' phase --> this is what I've seen as most of the answers but doesn't work
Upon further reading,
many seemed to need to replace their u-boot and x-loader
I did so and installed fastboot using Lelus' script here:
http://forum.xda-developers.com/showpost.php?p=41768774&postcount=1
I used option 6 which allowed me to flash the u-boot and x-loader from p760(works with my 769 and others as it says in the options) for JB
I'm not sure if I needed this as I don't have an unlocked bootloader.
I'm not sure of commands in fastboot but I ran
fastboot devices and it showed something
I also ran: fastboot flash recovery recovery.img
and I put one of my cwm backups in the "yours" folder
After I activate fastboot, it brings me to the C:\fastboot\yours folder
I assume this is for me to put my intended files in but I'm unsure if I should use my cwm backup or something else?
After it flashed the recovery img, I sent a fastboot reboot command
but it still went back to the droid lying down with a red triangle.
As some of you may see, I'm not too great with this but I feel like I'm close. Does anybody have an idea of what I should be doing?
should I flash an update.zip?
I don't know many commands but hopefully this gets me going in the right direction.
PLEASE HELP ME!!!!
I guess your cmw restore formatted your system but couldnt load the new system
the recovery you run with a locked bootloader uses a technique called 2nd init which i think is somewhere stored in the system partition. so when the recovery formatted the system, it lost itself too.
I've had a similar problem. the way out would be booting into the SW upgrade mode--switch off the device, remove the battery, remove the usb cable. press the volume up button and connect the phone to the computer. wait for a couple of seconds and then insert the battery.
you should be in the SW upgrade mode
now use the B2C client. if it gives an option to upgrade, use that otherwise, go to the customer support menu and press recovery phone
I have already done earlier. It may have gotten lost in my frenzy of information. I have put the phone into software mode, as you said, and it won't work either; There's no option to click upgrade because it's JB(V20D) and when I click recovery phone and enter my imei, LG mobile support tool(B2capp.exe) analyzes and then has a 'fatal error'
Since I flashed the new u-boot and x-loader my screens are all backwards/mirrored. Maybe the tool flashed an unlocked u-boot and x-loader if that's possible.
Is a recovery possible by fastboot?
I have a clean and full copy of my cwm recovery as well as apps and data backed up, I just need to get this phone in working order
shockah486 said:
I have already done earlier. It may have gotten lost in my frenzy of information. I have put the phone into software mode, as you said, and it won't work either; There's no option to click upgrade because it's JB(V20D) and when I click recovery phone and enter my imei, LG mobile support tool(B2capp.exe) analyzes and then has a 'fatal error'
Since I flashed the new u-boot and x-loader my screens are all backwards/mirrored. Maybe the tool flashed an unlocked u-boot and x-loader if that's possible.
Is a recovery possible by fastboot?
I have a clean and full copy of my cwm recovery as well as apps and data backed up, I just need to get this phone in working order
Click to expand...
Click to collapse
If you fastboot flash the u-boot and x-loader from p769(ICS) it should go thru with the offline flash detailed in cmahendras guide.
http://forum.xda-developers.com/showthread.php?t=2085344
Use the KDZ_FW_UPD.zip from this thread
Or try this
Remove all of the stuff you have downloaded for this. Download the original B2C client from LG's site and use that
Tablechair said:
If you fastboot flash the u-boot and x-loader from p769(ICS) it should go thru with the offline flash detailed in cmahendras guide.
Click to expand...
Click to collapse
Thanks.I'll try this. if I have the ICS bootloader, does that mean I'll have to flash the V10G kdz? or can i do the v20d kdz
dhruvbatra205 said:
http://forum.xda-developers.com/showthread.php?t=2085344
Use the KDZ_FW_UPD.zip from this thread
Or try this
Remove all of the stuff you have downloaded for this. Download the original B2C client from LG's site and use that
Click to expand...
Click to collapse
I have the updated kdz fw upd .zip from the unbrick and root thread as well as downloaded a new, official B2C client but they all still hang at the download part during phone recovery.
Tablechair, that did the trick.
Is this because the tool we use to flash for the offline method doesn't recognize the x and u-boot loaderse of JB?
After I installed the ICS boot loaders, my software upgrade mode wasn't mirrored anymore.
I did as tablechair and flashed the V20D.
Does anyone understand why this problem happened in the firstplace? Maybe I didn't get a full copy of clockcycle's backup cwm
or should I have not flashed his recovery in the first place since I didn't have an unlocked bootloader?
Again thank you for all your help and if anyone can provide answers to my other supplemental questions, that'd be great.
Off to root and probably unlock bootloader to be sure.
edit: I can't find the thanks button. but thank you very much tablechair. much appreciated. Hope this can help someone else
p.s. also big thanks to those who made the fastboot program for p769(Artas182x and sguerrini97). really an invaluable tool as I now know.
shockah486 said:
Tablechair, that did the trick.
Is this because the tool we use to flash for the offline method doesn't recognize the x and u-boot loaderse of JB?
After I installed the ICS boot loaders, my software upgrade mode wasn't mirrored anymore.
I did as tablechair and flashed the V20D.
Does anyone understand why this problem happened in the firstplace? Maybe I didn't get a full copy of clockcycle's backup cwm
or should I have not flashed his recovery in the first place since I didn't have an unlocked bootloader?
Again thank you for all your help and if anyone can provide answers to my other supplemental questions, that'd be great.
Off to root and probably unlock bootloader to be sure.
edit: I can't find the thanks button. but thank you very much tablechair. much appreciated. Hope this can help someone else
p.s. also big thanks to those who made the fastboot program for p769(Artas182x and sguerrini97). really an invaluable tool as I now know.
Click to expand...
Click to collapse
Things don't always go according to plan, maybe his Clockworkmod backup was made from the touch version and he didn't have artas182x second init recovery installed. So when the cwm failed the first time, did you try to restore your cwm backup?
kuma82 said:
Things don't always go according to plan, maybe his Clockworkmod backup was made from the touch version and he didn't have artas182x second init recovery installed. So when the cwm failed the first time, did you try to restore your cwm backup?
Click to expand...
Click to collapse
Not yet. having problems flashing a kdz again. I've tried the 2 different software modes, as well as setting emerg and diag but still getting stuck at 15% again.
Do i have to replace my uboot and xloader with the ICS ones every time I want to use the offline flash method?
edit: yup, after replacing with ICS loaders again i'm able to flash using software upgrade. will update on whether I can restore cwm
kuma82 said:
Things don't always go according to plan, maybe his Clockworkmod backup was made from the touch version and he didn't have artas182x second init recovery installed. So when the cwm failed the first time, did you try to restore your cwm backup?
Click to expand...
Click to collapse
I realized I misread your question. When I flashed before the incident, it failed to write to system and I didn't restore my other folder. I rebooted and it was all missed up. Anyway, now that I've got everything back and now with an unlocked bootloader, i was able to recover my old image. However, data isn't working so I have to find the radio to flash as I recall reading in other threads.
Can someone explain in laymen terms why this is? recap, i was on unlocked bl rooted jb and I flashed my old cwm backup when I was rooted but had a locked bl. My apps and messages were all there but the radio was different. I'd understand if I was going from ICS to JB but I was on JB both times. The only difference being a locked BL. It's got to be something about the Radio from p760 or V20B that didn't work on my earlier backup or something like that because the layout status bar is different with a "data" button and showing H instead of 4g(which are the same afaik).
Since, I restored to my backup from after my bootloader unlock and root so data is working showing 'H' with the different layout
Also, I had problems backing up and restoring until I noticed that it works better when I power off the phone and do the manual commands to enter recovery as opposed to using the app to send me to recovery(where I incurred /system backup errors).
My last question is which cwm recovery should I use? I currently have the one for a locked bootloader installed as per Artas182x's website. On that post he has a link for an unlocked bootloader recovery on the xda forums but that thread was updated to not working. Are there any disadvantages to me using a locked bootloader cwm recovery?
I don't think I have any option but to try it as I want to flash CM10.1 for p769. I also read that if your bootloader is unlocked, you can download the cwm from the googleplay. If this is true, can I just install over or should I uninstall the Artas182x locked bootloader one????
update: have to remove l9 recovery by deleting the appropriate system folders and then flash the appropriate .img through adb commands
Help.
shockah486 said:
I realized I misread your question. When I flashed before the incident, it failed to write to system and I didn't restore my other folder. I rebooted and it was all missed up. Anyway, now that I've got everything back and now with an unlocked bootloader, i was able to recover my old image. However, data isn't working so I have to find the radio to flash as I recall reading in other threads.
Can someone explain in laymen terms why this is? recap, i was on unlocked bl rooted jb and I flashed my old cwm backup when I was rooted but had a locked bl. My apps and messages were all there but the radio was different. I'd understand if I was going from ICS to JB but I was on JB both times. The only difference being a locked BL. It's got to be something about the Radio from p760 or V20B that didn't work on my earlier backup or something like that because the layout status bar is different with a "data" button and showing H instead of 4g(which are the same afaik).
Since, I restored to my backup from after my bootloader unlock and root so data is working showing 'H' with the different layout
Also, I had problems backing up and restoring until I noticed that it works better when I power off the phone and do the manual commands to enter recovery as opposed to using the app to send me to recovery(where I incurred /system backup errors).
My last question is which cwm recovery should I use? I currently have the one for a locked bootloader installed as per Artas182x's website. On that post he has a link for an unlocked bootloader recovery on the xda forums but that thread was updated to not working. Are there any disadvantages to me using a locked bootloader cwm recovery?
I don't think I have any option but to try it as I want to flash CM10.1 for p769. I also read that if your bootloader is unlocked, you can download the cwm from the googleplay. If this is true, can I just install over or should I uninstall the Artas182x locked bootloader one????
update: have to remove l9 recovery by deleting the appropriate system folders and then flash the appropriate .img through adb commands
Click to expand...
Click to collapse
Although I might be late, I have the same problem and the same phone and I really need help. I have a soft bricked phone lg optimus l9 and I had the same problems that you had exactly... Which is weird exept I don't have Clock Work Mod or anything ... If you get this I would really appreciate some help. Thanks
yup me too
I finally got software upgrade to work with my lg p769 that was security error cuz i still haven't unlocked the bootloader, if i knew what a good job lg and T-Mobile did in locking it i would have waited and got a g3 that my buddy rooted in like 5 min and unlocked the boot....
What worked for me is this LG FLASH TOOL 2014 THREAD ON XDA
http://forum.xda-developers.com/showthread.php?t=2797190
flashed both the 20H and 20D successfully i uninstalled everything lg in the control panel first though.
Hope this works for you cuz i was struggling on and off for a month to get this far lol
the 2014 tool ultimately worked for me too, once I fixed a couple things. I had rooted and forgotten to unlock, so it was at Security Error, and it would also disconnect at 15% .. in the 2014 tool, I had to install all the updates even though I'm in windows 7 or it would keep doing it. All good now.
I have been trying all these methods and I am still not able to get in the S/W upgrade mode. The only thing I am getting from the device is being able to put it fastboot mode (The inverted one). I really want to revive this phone
Thanks in advance for any help given
Liger878 said:
I have been trying all these methods and I am still not able to get in the S/W upgrade mode. The only thing I am getting from the device is being able to put it fastboot mode (The inverted one). I really want to revive this phone
Thanks in advance for any help given
Click to expand...
Click to collapse
Hey, it's been ages since I have done any of this but IIRC, if you can get into fastbood mode u can still get into software mode,
- turn phone into fastboot mode
- open the software upgrader thing as you normally do
- maybe switch emerg to diag or something like that
- this part is where it's slightly different than the normal way(same program but u select a different option than the default 1st option on
I think if yoiu look through the tutorials it does mention an alternative method for getting into software mode
in one instance in my past, i had to reflash the ICS boot drivers so the software installer would recognize that
the flashing of the ICS boot drivers is done through fastboot. Should be a post in my history where I asked a question regarding this.
Sorry for the chaos but maybe this will help you get in the right direction since I don't know any of your phone history and what you've done etc
best of luck mate
shockah486 said:
Hey, it's been ages since I have done any of this but IIRC, if you can get into fastbood mode u can still get into software mode,
- turn phone into fastboot mode
- open the software upgrader thing as you normally do
- maybe switch emerg to diag or something like that
- this part is where it's slightly different than the normal way(same program but u select a different option than the default 1st option on
I think if yoiu look through the tutorials it does mention an alternative method for getting into software mode
in one instance in my past, i had to reflash the ICS boot drivers so the software installer would recognize that
the flashing of the ICS boot drivers is done through fastboot. Should be a post in my history where I asked a question regarding this.
Sorry for the chaos but maybe this will help you get in the right direction since I don't know any of your phone history and what you've done etc
best of luck mate
Click to expand...
Click to collapse
Thanks, Never tried switching to DIAG before but I will try it and let you know what is the outcome.
Hopefully you find the thread that states the exact steps bc that is off the top of my head and over a year ago by memory . GL bud
Liger878 said:
Thanks, Never tried switching to DIAG before but I will try it and let you know what is the outcome.
Click to expand...
Click to collapse
Hey, I have been trying it with the fastboot but it keeps timing out and not allowing me to finish. One thing I should let you know is that, ever since I had put the device in fastboot, I am not able to get back the S/W upgrade mode. Dont know if that will help in seeing what my problem is or if you want me to explain everything from the beginning again, I am more than happy to.
Have you followed the steps that I linked to in the first 3 posts of this thread?
Follow the steps to flash the ICS bootloaders in fastboot and then you can do the fastboot trick for getting the software to recognize your device.
Right now your phone has the JB boot loader on it and is thus not recognized by the software.
recap:
step 1: flash the ICS bootloaders in fastboot (look at the linked thread in post 2)
step 2: use the software in emerg or diag mode but sitll follow the same steps as the tutorial. I think my earlier posts should explain precisely.
if you dont flash the ICS bootloaders, it won't be recognized by the KDZ installer
Hi guys, over the past few weeks, I have noticed that many people are having problems rooting their Jetstreams. So because of this, I thought I would put together an all in one guide to help alleviate everyone's problems.
So what this will show you how to do:
Unlock the bootloader
Flash a custom recovery
Grant root access
Prepare the device for S-OFF
Included files:
HTC Drivers
ADB
Fastboot
TWRP 2.4.1.0
SuperSU 1.51
Note: This guide is for windows only
Ok, so lets begin:
Download attached zip
http://www.mediafire.com/download/ao1ykdpx5jn2uni/Root_HTC_Jetstream.zip
Extract the zip to an appropriate place on your computer
Install the HTC drivers
Do so by double clicking the HTCDriver_4.2.0.001.exe from the zip
Run the RUU if needed
I am assuming you are on a completely stock HTC Jetstream with no modifications what so ever. I am also assuming you are on the latest software 1.30.502.1 for AT&T users or 1.26.631.4 for Rodgers users. If you are not, please download and run the latest RUU from the following website:
http://forum.xda-developers.com/showthread.php?t=2094375
Please note that running the RUU will completely WIPE your device of all personal data, so backup accordingly
To run the RUU, make sure the Jetstream is turned on and is fully booted into Android
Make sure "USB Debugging" is enabled under development settings
Make sure "Fastboot" is disabled under power settings
Simply attach the Jetstream to your computer with the appropriate USB cord
Double click on the downloaded RUU .exe file to run the program
If for some reason you cannot boot into Android, you can do the following:
With the device turned off, hold the volume down button and simple press the power button for a second or two
The device will boot into the bootloader, from there use the volume buttons to navigate to fastboot and the power button to select
Once in fastboot, connect the device to the computer with the USB cord and then double click the downloaded RUU .exe
Now lets unlock the bootloader
Please note that unlocking the bootloader will also WIPE your device
Go to http://www.htcdev.com/
Create an account if you do not already have one
Click on "Unlock Bootloader" and then "Get Started"
In the drop down box, select "HTC Jetstream"
Agree to all the legal terms
Follow all the instructions to obtain your unlock token
To easily do this:
Make sure "USB Debugging" is enabled under development settings
Make sure "Fastboot" is disabled under power settings
Connect the device to the computer with the USB cable
Navigate to the extracted folder of the attached zip
Hold the shift key and right click in the folder, then select "Open Command Window Here"
Type the following in the command window
Code:
adb reboot bootloader
Once the device has booted into fastboot, type the following in the command window
Code:
fastboot oem get_identifier_token
Copy the appropriate text according to the website and submit it
You will then be emailed an "Unlock_code.bin" and a link to continue the unlock process
Download the "Unlock_code.bin" and place it in the extracted folder from earlier
Now type the following in the command window
Code:
fastboot flash unlocktoken Unlock_code.bin
On the device you will be prompted to unlock the device, use the volume keys to navigate to "Yes" and use power to select
The device will reboot back into Android
Now lets flash a custom recovery
Connect the device to the computer with the USB cable
In the extracted folder open a command window by holding the shift key, right clicking, and selecting "Open Command Window Here"
Type the following in the command window
Code:
adb reboot bootloader
Once the device has booted into fastboot, type the following into the command window
Code:
fastboot flash recovery htc_jetstream_twrp_recovery_2.4.1.0.img
Once the custom recovery has been successfully flashed, type the following into the command window
Code:
fastboot reboot
The device will then boot back into android
Now lets get root
Connect the device to the computer with the USB cable
Copy the "SuperSU-v1.51.zip' to the root of you SD card
Go to the extracted folder, hold the shift key, right click, and select "Open Command Window Here"
Now type the following into the command window
Code:
adb reboot recovery
While at the recovery main menu, select the wipe option and wipe cache and dalvik cache
Next go back to the main menu and select install
Navigate to the SuperSU zip we placed on the SD card and flash the zip
Once it flashes, go back to the main menu and reboot back into system
The device will boot back into Android and the device will now be rooted!
So what now?
After completing the step above, you device should have an unlocked bootloader, and custom recovery installed, and also have root access. After having all of this you may now go on to install any custom ROMs you may want, however, I would recommend obtaining S-OFF to give yourself full control over your device.
This following link should help to explain what S-OFF is exactly:
http://forum.xda-developers.com/showpost.php?p=42455824&postcount=1
This next link is to the JuopunutBear S-OFF method:
http://forum.xda-developers.com/showthread.php?t=1906353
People I would like to thank:
DoomLoRD - for his initial work with rooting the HTC Jetstream
jmz - for giving us a custom recovery and hosting all the RUUs for us
TeamWin - for TWRP
Chainfire - for his amazing work with Android and SuperSU
Fuses and the rest of Team Unlimited - for giving us an S-OFF method
Disclaimer:
Just to be clear, unlocking and rooting your HTC Jetstream voids your warranty, so anything you do to it is your decision and I am in no way responsible for anything that happens to your device
great work!
@DNarsingh
Windows 8 64 finally can ADB to Jetstream and Sensation XL.
Thanks for driver file HTCDriver_4.2.0.001.exe containing within the zip you attached. The driver within htc_sync_setup_3.3.10.exe couldn't seem to get through.
Did a factory reset on my jetstream, and lost root. When I used CWM for recovery, I tried re-rooting using the guide in this thread. After another factory reset, root was still there, so I handed the jetstream to its new owner. However, the new owner has told me that the pen icon doesn't show up when using the pen. He did another factory reset (which took longer than usual), but still nothing. Anyone know what went wrong?
Notontherugman said:
Did a factory reset on my jetstream, and lost root.
Click to expand...
Click to collapse
I've never heard of a factory reset breaking root. The components that enable root usually exist on the /system partition and it is untouched by a factory reset.
The other root method (that I am unfamiliar) with is an insecure kernel. I don't know how this works, but I am pretty sure that a factory reset should not break it.
finniest said:
I've never heard of a factory reset breaking root. The components that enable root usually exist on the /system partition and it is untouched by a factory reset.
The other root method (that I am unfamiliar) with is an insecure kernel. I don't know how this works, but I am pretty sure that a factory reset should not break it.
Click to expand...
Click to collapse
I'm not a dev, and have just been following how-tos on XDA up to now (from back in the days of HTC HD2); therefore, I can't give details since I am inexperienced.
After the factory reset, Titanium Backup was denied SU, I could not browse the root directories/folders and all the software that needed root to work would not.
My question still stands: the pen icon won't show up. Anyone know what went wrong or what he may be doing wrong? In desperate need for help.
Notontherugman said:
After the factory reset, Titanium Backup was denied SU, I could not browse the root directories/folders and all the software that needed root to work would not.
Click to expand...
Click to collapse
Did you try to install the superuser app that you were formerly using from the market? My guess is that you lost the /data/app/su.apk that manages superuser, but that the binary is still in your /system/xbin/su directory somewhere. You probably removed the seemingly redundant /system/app/su.apk while using Titanium Backup, but are now left without a copy of it.
Notontherugman said:
My question still stands: the pen icon won't show up. Anyone know what went wrong or what he may be doing wrong? In desperate need for help.
Click to expand...
Click to collapse
If you are using Hive ROM then the pen icon will not appear, but the pen will still work with most apps. If you are using a different ROM then I really have no idea why the pen icon is not working. Are you certain that the pen battery still has a charge?
finniest said:
If you are using Hive ROM then the pen icon will not appear, but the pen will still work with most apps. If you are using a different ROM then I really have no idea why the pen icon is not working. Are you certain that the pen battery still has a charge?
Click to expand...
Click to collapse
Not using any ROMs.
I had removed most of the bloatware when I was using it, but the pen icon was there and I could use it just fine (before the factory reset).
Now, after the factory reset and the root method above, he tried his Flyer's pen on the Jetstream as well, so the battery is not a problem.
Notontherugman said:
I had removed most of the bloatware when I was using it, but the pen icon was there and I could use it just fine (before the factory reset).
Click to expand...
Click to collapse
Try using logcat to diagnose the problem. I suspect something will show up during boot or when you press where the pen icon should be.
http://www.xda-developers.com/android/help-your-developers-pull-a-logcat-when-issues-arise
I got the Jetstream back today.
I had managed to make a backup before using Clockwork Mod.
After the above rooting method, CWM is gone, and I can't use the backup files to restore using TWRP.
The link for CWM is gone. This is becoming extremely frustrating.
Notontherugman said:
I got the Jetstream back today.
I had managed to make a backup before using Clockwork Mod.
After the above rooting method, CWM is gone, and I can't use the backup files to restore using TWRP.
The link for CWM is gone. This is becoming extremely frustrating.
Click to expand...
Click to collapse
I have a copy of the CWM recovery.img. When I get home tonight, I will upload it for you.
I would recommend redoing your backup in TWRP afterward. In my experience, this recovery is a bit more up to date..
DNarsingh said:
I have a copy of the CWM recovery.img. When I get home tonight, I will upload it for you.
I would recommend redoing your backup in TWRP afterward. In my experience, this recovery is a bit more up to date..
Click to expand...
Click to collapse
Definitely.
And thank you!
EDIT: found CWM on an old hard disk. Managed to get ADB working. Restoring should fix most of the problems.
Thanks very much for the post
Sent from my SGH- I317M (Note II) running CM 11 using XDA Mobile App
every thing is ok
my device is fully rooted with twrp recovery and unlocked bootloader
but I have a problem.
I have sim card signal Icon but my device can not confirm simcard
what can I do?
Thanks!
Since I have rooted my device I can no longer access downloads from the google play store. I constantly get RPC:S-7:AEC-0 or -7 errors. I have tried all the tricks on various
forums but have had no luck. Do you have any fixes related to the jetstream?
Thanks, Mike
GROTEU said:
Since I have rooted my device I can no longer access downloads from the google play store. I constantly get RPC:S-7:AEC-0 or -7 errors. I have tried all the tricks on various
forums but have had no luck. Do you have any fixes related to the jetstream?
Thanks, Mike
Click to expand...
Click to collapse
It doesn't sound related to rooting. I would suggest a backup (there are many means of accomplishing this) and then a factory restore. If that doesn't work then install a custom ROM.
rooting issues
i have been trying to root my jetstream so i can get some lift out of it but when i get to the fast boot the system just hangs there any suggestions please if you know a complete way to root a htc from rogers i would love the support thanks
Q&A for [ROOT] Root with Locked Bootloader for SGP621 using giefroot
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT] Root with Locked Bootloader for SGP621 using giefroot. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Deleted
I'm at (24).
I requested the link to get an unlock code at developer.sonymobile.com. It's now been over 24 hours and i haven't get an email yet. Tried ist with a differnet email adress too.
How long does it take usally?
WiFi isssue after flashing D6603 rom
Hi,
I liked the idea of flashing D6603 rom on my SGP621 and rooting it..
I like my tablet now even more..
But the WiFi is not working for me now, only LTE/3G..
Also the camera not working, but I don't care because I'm using my mobile phone for taking pictures..
Is there any way to make WiFi working with D6603 rom?
Thanks...
russse said:
I'm at (24).
I requested the link to get an unlock code at developer.sonymobile.com. It's now been over 24 hours and i haven't get an email yet. Tried ist with a differnet email adress too.
How long does it take usally?
Click to expand...
Click to collapse
Normaly it takes not more than a few minutes. You can resend it at any time by requesting it again on sonymobile. If it still does not work you may need to get in touch with developer support on their website.
---------- Post added at 03:38 PM ---------- Previous post was at 03:33 PM ----------
kamal3383 said:
Hi,
I liked the idea of flashing D6603 rom on my SGP621 and rooting it..
I like my tablet now even more..
But the WiFi is not working for me now, only LTE/3G..
Also the camera not working, but I don't care because I'm using my mobile phone for taking pictures..
Is there any way to make WiFi working with D6603 rom?
Thanks...
Click to expand...
Click to collapse
No, you cannot. As there are other drivers used. If you want root and WiFi you need to follow the tutorial to the end and in the process unlock your bootloader and return to the SGP621 stock rom.
Hi lowtraxx
Thanks a lot for your great work!
I have the SGP611 version and have successfully followed rurie's guide to root the unit. Now i'm installing the rooted stock, but I'm stuck at your step 30. In step 28 I booted into fastboot and used Flashtool to execute the Z3TC-stock-twrp.img by pressing the button "Select system to Flash" and selecting the img-file, see pic.
I have tried to reboot by pressing "Reboot into fastboot mode (via Fastboot) to press volume down on purple light. However, the light never goes purple. It is blue, then swishes to red for an instance/glimpse. I have tried to hold down "volume down" and to press it many times but nothing works. Can you explain step 30 to 32 in detail, e.g. by using the buttons on the Flashtool - Fastboot toolbox (see pic)?
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
I hope you did not flash the SGP621_23.0.1.A.0.167_CE.ftf onto your device but the one that is for the SGP611, because from your description it sounds like you are in a bootloop. I haven't used Flashtool to flash a kernel before, I am only using the command line. But my best guess would be that you need to click on Select Kernel to flash, select the Z3TC-stock-twrp.img and click on flash. Once that is done, you should reboot the device and wait until the Xperia logo shows up and the LED goes purple. If you now press volume down you get into recovery where you need to flash the RICDefeat.zip file you downloaded. If that does not work, download flashtool binary for windows, open a cmd prompt as Administrator, boot into fastboot mode and execute 'fastboot flash boot /path/to/the/Z3TC-stock-twrp.img' and then continue as outlined above.
lowtraxx said:
Hi,
I hope you did not flash the SGP621_23.0.1.A.0.167_CE.ftf onto your device but the one that is for the SGP611, because from your description it sounds like you are in a bootloop. I haven't used Flashtool to flash a kernel before, I am only using the command line. But my best guess would be that you need to click on Select Kernel to flash, select the Z3TC-stock-twrp.img and click on flash. Once that is done, you should reboot the device and wait until the Xperia logo shows up and the LED goes purple. If you now press volume down you get into recovery where you need to flash the RICDefeat.zip file you downloaded. If that does not work, download flashtool binary for windows, open a cmd prompt as Administrator, boot into fastboot mode and execute 'fastboot flash boot /path/to/the/Z3TC-stock-twrp.img' and then continue as outlined above.
Click to expand...
Click to collapse
Thanks for your reply. I have used the SGP611 firmware, so no problem.
I have flashed Z3TC-stock-twrp.img unto the unit using the button Select Kernal, but when I reboot the LED never goes purple - only blue and for a quick glimpe (~1-3 ms) red. If I boot the unit in normal mode (without fastboot mode or flash mode) it gets stuck at the Sony logo and cannot be shut down without pressing the small force-shut-down button next to the SD card. (It booted as SPG611 just fine before I flashed Z3TC-stock-twrp.img unto it - using the button Select Kernal.)
EDIT. Tried to download Z3TC-stock-twrp.img again and flash it using CMD in windows. Now I can access Recovery.
I'm progressing, but only slowly.
I'm at step 32 in the guide but every time I try to load/install RICDefeat it fails. Nothing happens when I try to issue 'adb sideload /path/to/RICDefeat.zip', so I have put the file on my external SD card. But when I press "install" - "external_sd" - "RICDefeat.zip" in the twrp Recovery it fails and an error comes: "Error executing updater binary in zip '/external_sd/RICDefeat.zip'".
How can I progress? Why do I have to install RICDefeat?
Without RICDefeat you are not able to mount the system partition writeable, so you have no real root. The error is odd though. Have you tried downloading the RICDefeat.zip again, maybe it was corrupted too (like the TWRP img)
lowtraxx said:
Without RICDefeat you are not able to mount the system partition writeable, so you have no real root. The error is odd though. Have you tried downloading the RICDefeat.zip again, maybe it was corrupted too (like the TWRP img)
Click to expand...
Click to collapse
Yes, I have tried downloading it again by clicking "View Raw". I have copied both to the SDcard, but both fails with same error.
Trying to use ADB Sideload and writing "adb devices" in Windows CMD from the folder C:\Users\USERNAME\AppData\Local\Android\sdk\platfo rm-tools just returns an empty list, and installing from SD fails with "Error executing updater binary in zip '/external_sd/RICDefeat.zip'".
Is it possible to go back some steps and try again - without bricking the device? E.g. to step 26? Is there an other place to down the advanced stock kernel?
centric dk said:
Yes, I have tried downloading it again by clicking "View Raw". I have copied both to the SDcard, but both fails with same error.
Trying to use ADB Sideload and writing "adb devices" in Windows CMD from the folder C:\Users\USERNAME\AppData\Local\Android\sdk\platfo rm-tools just returns an empty list, and installing from SD fails with "Error executing updater binary in zip '/external_sd/RICDefeat.zip'".
Is it possible to go back some steps and try again - without bricking the device? E.g. to step 26? Is there an other place to down the advanced stock kernel?
Click to expand...
Click to collapse
It worked! I now have an rooted Z3 tablet compact with stock rom and locked bootloader. :good:
I solved it by tring to go back to step 26 and try one more time (with the same files,and same method). This time I did get the same errors about LED in twrp, but everything worked just like it was suppose to and explained in this guide. The RICDefeat flash just took 5 seconds.
Thank you for helping me!
Last questions:
Will I be able to receive Other OTA updates, e.g. for Lollipop when Sony is ready?
Can I always go back to step 35 if I want a clean/new installation, or do I have to unlock the bootloader first, going back to step 24?
centric dk said:
It worked! I now have an rooted Z3 tablet compact with stock rom and locked bootloader. :good:
I solved it by tring to go back to step 26 and try one more time (with the same files,and same method). This time I did get the same errors about LED in twrp, but everything worked just like it was suppose to and explained in this guide. The RICDefeat flash just took 5 seconds.
Thank you for helping me!
Last questions:
Will I be able to receive Other OTA updates, e.g. for Lollipop when Sony is ready?
Can I always go back to step 35 if I want a clean/new installation, or do I have to unlock the bootloader first, going back to step 24?
Click to expand...
Click to collapse
Hi,
you will most likely be notified about OTA updates, but you should not take them, because they will not apply properly and most likely remove root again. Just wait for recovery flashable updates or build your own flashable update once the ftfs for the lollipop versions get available. If you want a clean installation without unlocking the bootloader again, just build a flashable zip of a clean ftf and flash that. If you want to send it in for repairs and the like, you can always flash a clean ftf with flashtool, but if you want to root it afterwards you need to unlock the bootloader again.
centric dk said:
It worked! I now have an rooted Z3 tablet compact with stock rom and locked bootloader. :good:
I solved it by tring to go back to step 26 and try one more time (with the same files,and same method). This time I did get the same errors about LED in twrp, but everything worked just like it was suppose to and explained in this guide. The RICDefeat flash just took 5 seconds.
Thank you for helping me!
Last questions:
Will I be able to receive Other OTA updates, e.g. for Lollipop when Sony is ready?
Can I always go back to step 35 if I want a clean/new installation, or do I have to unlock the bootloader first, going back to step 24?
Click to expand...
Click to collapse
I'm currently trying to flash RICDefeat from recovery and am getting the exact same error you reported. Do you know what exactly changed that allowed you to flash it successfully? Did you use the RAW version? Where did you put it, internal memory or SD?
Thanks!
Amplifiction said:
I'm currently trying to flash RICDefeat from recovery and am getting the exact same error you reported. Do you know what exactly changed that allowed you to flash it successfully? Did you use the RAW version? Where did you put it, internal memory or SD?
Thanks!
Click to expand...
Click to collapse
I did not change anything. The second time just went a lot faster as I had tried it before. I put RICdefeat on the SD card.
I also have a Z3 Compact (phone). That it a lot simpler to root and RICdefeat is not needed in that guide. Maybe you can get inspiration there?
centric dk said:
I did not change anything. The second time just went a lot faster as I had tried it before. I put RICdefeat on the SD card.
I also have a Z3 Compact (phone). That it a lot simpler to root and RICdefeat is not needed in that guide. Maybe you can get inspiration there?
Click to expand...
Click to collapse
I actually have been following a guide in the Z3C forums but ended up with partial root. RICD should be able to solve it, but gave me an arror. When I read you've been having similar problems, I thought I'd give it a go. Thanks anyway.
Amplifiction said:
I actually have been following a guide in the Z3C forums but ended up with partial root. RICD should be able to solve it, but gave me an arror. When I read you've been having similar problems, I thought I'd give it a go. Thanks anyway.
Click to expand...
Click to collapse
I followed this guide for Z3C (phone): http://forum.xda-developers.com/showpost.php?p=59627168&postcount=120
centric dk said:
I followed this guide for Z3C (phone): http://forum.xda-developers.com/showpost.php?p=59627168&postcount=120
Click to expand...
Click to collapse
Try this one;
http://forum.xda-developers.com/z3-...to-rooted-lollipop-locked-bootloader-t3083980
All works fine.
Hey,
today I got my Xperia X3CT and I followed this Guide to Root my Tablet: http://forum.xda-developers.com/z3-t...gp621-t3013534
(I rooted my LG G2 so I thought I should be able to Root my Tablet without any problems )
At Point 6 I started my Tablet, but somehow it is Stuck in a Bootloop. I am sure I did everything the way the Guide told me to, but somehow my Tablet is still in a Bootloop. How do I get out of it? I can turn the Device of by pressing the Power Button und the Volume Up Button.
Can someone please help?
EDIT: Got out of the Bootloop by flashing back to SGP621_23.0.1.A.0.167_CE.ftf. That was quite a shocker
I think the Problem was that I was at 23.1.A.0.690. Now that I am at 23.0.1.A.0.167 it should make any problems? Or could there be another Problem? Would be thankful for help
Emildeon said:
I think the Problem was that I was at 23.1.A.0.690.
Click to expand...
Click to collapse
That was the problem , you must follow the manual from kitkat (23.0.1.A.0.167) . I advise to use http://forum.xda-developers.com/z3-...to-rooted-lollipop-locked-bootloader-t3083980 ( No need to open the bootloader ). I made a guide in Spanish
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Whoa! the unlock tool is out!
Is there any chance someone can make a root guide? I really want to buy Zenfone 3 Ultra but I wouldn't do it without root method out there. Any help is appreciated.
Were waiting on a dev to compile TWRP for us then we can get root
Trying to root ZU680KL
Hi!
I have unlocked my ZU680KL with the Asus unlock tool. Bootloader shows 'unlocked'.
Then I unpacked the stock boot.img (from WW_13.6.15.21_20161215, this what I have installed) and using Vim I set:*ro.secure=0, ro.adb.secure=0, and*ro.debuggable=1 in default.prop.
Repacked the new boot.img and flashed it with 'fastboot flash boot new-boot.img'.
'adb shell getprop' indicates that the new setting was applied.
Yet in the stock recovery mode I cannot install SuperSU-v2.79.zip and no adb devices are seen in recovery mode.
What else is needed? Do I have to edit something in the stock recovery or must wait for custom TWRP?
I was following the basic instructions found here:
https://machiry.wordpress.com/2012/10/26/getting-root-access-on-android-the-actual-way/
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
hillg001 said:
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
Click to expand...
Click to collapse
Any news?
https://forum.xda-developers.com/ze...t-zenfone-3-ultra-7-0-ww14-1010-1703-t3612108
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
when the ultra 3 first came out, many suggested waiting for a boot loader unlocker, & not updating any Android versions, because an unlock program might not work on subsequent Android versions. Is that the case? ... or does the unlocker work on the newest Android version too.
Thanks
.
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
I have just downloaded the zip, made the APK and installed it on my Zenfone 3 Ultra.
When I run the app, after clicking all the "are you sure..." acknowledgements, the app does not succeed in unlocking the bootloader. The error message indicates an unknown or perhaps network error, and suggests I "try again later..."
Running WW_14.1010.1804.75_20180612
Anybody else seeing this?
Ideas??
Reading on the ASUS blogs, they indicate it isn't supported anymore (no surprise), but shouldn't it still work??
heroxbd said:
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
Click to expand...
Click to collapse
Note the links above no longer work. Yes, you can get to the page, but the unlocker isn't there any more.
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
Does anybody know which version(s) of the stock ROM this works with? I've tried a couple, and all of them just yield the "unknown error" when running the unlocker.
If you know of a stock ROM version this works with, please post a URL for where I can find it (as it's proven really hard to find specific versions...)
Thanks in advance.
agree it no longer works. getting the unknown error...wait message that everyone else is getting. there are other XDA threads that indicate the same.
Keeping bootloader locked. Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even the SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
-
jrchester said:
Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even and SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
Click to expand...
Click to collapse
How did you do that? Can I get more details?
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hi Madlzz:
Checkout my XDA post here for more details on how I did this:
unlocking bootloader zenfone ultra
Hi all ive had my zenfone 3 ultra (zu680kl) for some years, until a couple of days ago, my friend wanted to see if my phone could be charged with a dash charger, where others wouldnt my battery was already low and overnight it ran out and when i...
forum.xda-developers.com
- John
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
lucy1983 said:
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
Click to expand...
Click to collapse
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
jrchester said:
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
Click to expand...
Click to collapse
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
lucy1983 said:
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
Click to expand...
Click to collapse
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
jrchester said:
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
Click to expand...
Click to collapse
You can install Magisk 24 without any problems. For me it doesn't break safetynet and play store says "certified". Even without enabling zigisk.
I know it's an old phone. The LG G5. But I bought it because my Galaxy died, the G5 was cheap, you can run Lineage OS on it! But wait! No you can't! You'll never make it past loading the custom recovery file. The guide on Lineage's website is worthless, as it's from before 8.0 Oreo. LG patched the that hole closed tighter than a... a.. <insert good simile here>. I have tried every way in the world to get into this phone. I've looked at every thread here. Dirtycow doesn't work. You can't revert back to 7.x Nougat anymore. It can't be done. LG won't let you in.
I have dreamed of escaping google's clutches. It's really important to me. But I can't afford to buy some $250+ dollar phone that may or may not have a working exploit right now.
This time I gambled and lost, so I'm asking for help. Does anyone know of any way I might salvage the situation? I'd be open to buying a phone with Lineage already on it, if it were reasonably priced. I'd also be open to paying someone else to install it on this LG G5, but I have serious doubts you'd be able to. Any help or advice to get Lineage would be greatly appreciated!
bennylava said:
I know it's an old phone. The LG G5. But I bought it because my Galaxy died, the G5 was cheap, you can run Lineage OS on it! But wait! No you can't! You'll never make it past loading the custom recovery file. The guide on Lineage's website is worthless, as it's from before 8.0 Oreo. LG patched the that hole closed tighter than a... a.. <insert good simile here>. I have tried every way in the world to get into this phone. I've looked at every thread here. Dirtycow doesn't work. You can't revert back to 7.x Nougat anymore. It can't be done. LG won't let you in.
I have dreamed of escaping google's clutches. It's really important to me. But I can't afford to buy some $250+ dollar phone that may or may not have a working exploit right now.
This time I gambled and lost, so I'm asking for help. Does anyone know of any way I might salvage the situation? I'd be open to buying a phone with Lineage already on it, if it were reasonably priced. I'd also be open to paying someone else to install it on this LG G5, but I have serious doubts you'd be able to. Any help or advice to get Lineage would be greatly appreciated!
Click to expand...
Click to collapse
Hey, easy man. There's some things you should consider before giving up on a phone. The quick search i did on Google let me know that this device can be bootloader unlocked, and rooted. At this point, I may ask: Is your device linked in someway with Verizon? Did you unlocked its bootloader? did you manage to install TWRP with no issues? Maybe you´re lucky enough to find a way out yourself. I'll try to help you in everything i can.
eduardvi995 said:
Hey, easy man. There's some things you should consider before giving up on a phone. The quick search i did on Google let me know that this device can be bootloader unlocked, and rooted. At this point, I may ask: Is your device linked in someway with Verizon? Did you unlocked its bootloader? did you manage to install TWRP with no issues? Maybe you´re lucky enough to find a way out yourself. I'll try to help you in everything i can.
Click to expand...
Click to collapse
Thanks! I could really use the help. I have unlocked the bootloader. Made it that far. But I haven't been able to root it because all the root exploits seem to have been patched out by the time I got the phone. It's running Android 8.0. It is a U.S Tmobile phone.
Here's where my progress ground to a halt: I can't get that LG program, LGup, to flash 7.0 to the phone. It gives me an error saying "Error - Invalid KDZ file". Well that's odd, I got that KDZ file from LG's official website. They have a section where they keep all the old stock ROMs.
Maybe I'm wrong here, but I think this part is absolutely necessary. You must install 7.0 Nougat in order to roll back the changes LG made when they patched up the recovery mode. Otherwise you can't install a custom recovery file, which is vital. No custom recovery file = no Lineage. Looking forward to your reply !
bennylava said:
Thanks! I could really use the help. I have unlocked the bootloader. Made it that far. But I haven't been able to root it because all the root exploits seem to have been patched out by the time I got the phone. It's running Android 8.0. It is a U.S Tmobile phone.
Here's where my progress ground to a halt: I can't that LG program, LGup, to flash 7.0 to the phone. It give me an error saying "Error - Invalid KDZ file". Well that's odd, I got that KDZ file from LG's official website. They have a section where they keep all the old stock ROMs.
Maybe I'm wrong here, but I think this part is absolutely necessary. You must install 7.0 Nougat in order to roll back the changes LG made when they patched up the recovery mode. Otherwise you can't install a custom recovery file, which is vital. No custom recovery file = no Lineage. Looking forward to your reply !
Click to expand...
Click to collapse
Here is what i found out. Considering your device is LG G5 H830, with android 8.0, it seems you cant install TWRP straight on. However, there is still something you can try. At this point I may ask: can you enter Fastboot Mode? this your only hope to actually root the phone, and then flash TWRP.
Check if you actually can enter fastboot. If you can, then try to send some basic commands like "fastboot devices" "fastboot reboot". I say this because some devices have Fastboot mode disabled on oem, rendering on useless fastboot. Hope this is not your case. Also, post here your exactly fingerprint version (your rom version). It has to be exactly the same one, otherwise it might soft-brick your phone. Maybe you can flash a patched boot image of your actual rom to then flash twrp.
eduardvi995 said:
Here is what i found out. Considering your device is LG G5 H830, with android 8.0, it seems you cant install TWRP straight on. However, there is still something you can try. At this point I may ask: can you enter Fastboot Mode? this your only hope to actually root the phone, and then flash TWRP.
Check if you actually can enter fastboot. If you can, then try to send some basic commands like "fastboot devices" "fastboot reboot". I say this because some devices have Fastboot mode disabled on oem, rendering on useless fastboot. Hope this is not your case. Also, post here your exactly fingerprint version (your rom version). It has to be exactly the same one, otherwise it might soft-brick your phone. Maybe you can flash a patched boot image of your actual rom to then flash twrp.
Click to expand...
Click to collapse
I can indeed send "fastboot devices" and "fastboot reboot", and it does work. The device will be listed in the command window on the computer, and the phone will reboot if you enter the command "Fastboot reboot".
As for the fingerprint version, here's what I was able to accomplish via a terminal in Manjaro Linux. Is this the full fingerprint?
[[email protected] ~]$ adb devices
List of devices attached
LGH8305d6bec71 device
[[email protected] ~]$ adb shell getprop ro.build.fingerprint
lge/h1_tmo_us/h1:8.0.0/OPR1.170623.032/182251913485f:user/release-keys
[[email protected] ~]$
bennylava said:
I can indeed send "fastboot devices" and "fastboot reboot", and it does work. The device will be listed in the command window on the computer, and the phone will reboot if you enter the command "Fastboot reboot".
As for the fingerprint version, here's what I was able to accomplish via a terminal in Manjaro Linux. Is this the full fingerprint?
[[email protected] ~]$ adb devices
List of devices attached
LGH8305d6bec71 device
[[email protected] ~]$ adb shell getprop ro.build.fingerprint
lge/h1_tmo_us/h1:8.0.0/OPR1.170623.032/182251913485f:user/release-keys
[[email protected] ~]$
Click to expand...
Click to collapse
Its seems you were lucky enough. I checked your rom build and compared it with the only rom on your phone that can be rolled back. It totally matchs the anti-rollback v01 firmware 8.0, so you still can roll-back to Nougat if you try the firmware version H83020c, wich you can download over here:
Fastboot-Flashable rom:
Codefire - Listing of H83020c
KDZ Format rom:
http://dl02.gdms.lge.com:5006/dn/downloader.dev?fileKey=FWAAZHZF92MNARE76685PNJ/H83020o_00_0205.kdz
Its seems the first one it's Fastboot-Flashable, so you should know what to do next if the KDZ Rom doesn't work. However, check this website and compare the rom build yourself, just to be clear about it:
Download T-mobile LG G5 H830 Stock kdz firmware H83030C
Download T-mobile LG G5 H830 Stock kdz firmware H83030C -
www.mylgphones.com
The first link has 3 flashable roms there. including KDZ and fastboot format. Make sure to try them all if one doesnt work
If both methods are useless to roll back to Nougat, dont hesitate to tell me. There's still a workaround available.
To be clear, the phone needs to be in "Firmware update" mode in order to use flashboot to flash that Fastboot rom, correct? That's where a "Firmware update" message appears on the screen, and it's encircled by two arrows. It's in the middle of the screen, and it's not small like when you're using fastboot.
I ask because iirc, KDZ files require the use of LGup, that LG official program.
bennylava said:
To be clear, the phone needs to be in "Firmware update" mode in order to use flashboot to flash that Fastboot rom, correct? That's where a "Firmware update" message appears on the screen, and it's encircled by two arrows. It's in the middle of the screen, and it's not small like when you're using fastboot.
I ask because iirc, KDZ files require the use of LGup, that LG official program.
Click to expand...
Click to collapse
It needs to be in firmware update mode only if you are flashing a kdz rom through Lg official flashtool. If you are going to flash through fastboot, you have to make sure your PC recognizes your device sending "fastboot devices". The fastboot flashable room is right in the first link (.zip file, 1,6 GB size file)
The one I'm seeing says it's 1.9 Gigabytes in size. It's #15 on that list, and it's called:
LG-H83020c-Flashable.COMPLETE-ARB01.zip
Correct?
Just wanna be clear on this, the last thing we need is a brick lol
bennylava said:
The one I'm seeing says it's 1.9 Gigabytes in size. It's #15 on that list, and it's called:
LG-H83020c-Flashable.COMPLETE-ARB01.zip
Correct?
Just wanna be clear on this, the last thing we need is a brick lol
Click to expand...
Click to collapse
That should be it. Download it and check it has all partitions (boot, system, recovery, etc...)
You are probably gonna have to flash each partition manually (for example, if you are flashing system, you should write "fastboot flash system system.img" and so on)
Below is a pic of everything that came in that zip file, just to make sure we're on the same page and I've got everything necessary.
I must admit that I'm a little intimidated by flashing each individual component in that zip file. I understand that you can just tell it "Flash this thing!" and it will do it. But how does it know where exactly to flash the new thing? How does it know not to just write it over the previous item you just flashed?
Next question: What all needs to be flashed individually? As you can see, there are a total of 28 entries shown in the pic. But the folders "bootloader" and "META.INF" both contain a lot of stuff. Do you just flash bootloader and META.INF, and it already knows to flash everything the folder contains?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bennylava said:
Below is a pic of everything that came in that zip file, just to make sure we're on the same page and I've got everything necessary.
I must admit that I'm a little intimidated by flashing each individual component in that zip file. I understand that you can just tell it "Flash this thing!" and it will do it. But how does it know where exactly to flash the new thing? How does it know not to just write it over the previous item you just flashed?
Next question: What all needs to be flashed individually? As you can see, there are a total of 28 entries shown in the pic. But the folders "bootloader" and "META.INF" both contain a lot of stuff. Do you just flash bootloader and META.INF, and it already knows to flash everything the folder contains?
Click to expand...
Click to collapse
You don't have to write "fastboot flash" 28 times. You can just write "fastboot flash all". But I'd rather flashing manually.
Ignore the META-INF folder. You can't flash any file inside there. You should only flash every file ending in "xx. Img* such as boot.img or. system.img.
This zip contains that folder because it was meant to be flashed through recovery, but if you try to do that, the recovery will not do it, or it will cancel installation, as there is a line that checks your actual fingerprint to avoid Rolling back.
So the command to flash that whole bootloader file at once is "flashboot flash all bootloader"? And it won't care that it's a folder, and not a .img file?
I see what you mean about flashing the .img files that are below the "bootloader" folder in that pic I posted. To me it makes sense that it would flash those. But as you said, you should only flash every file ending in .img and "bootloader" is actually a folder, even if it is full of those files. So I just want to be clear on how exactly to flash that bootloader file.
Sorry about all the newb questions lol. Once I see your reply here, I'm going to attempt the flash. After that, hopefully I won't need any more help.
bennylava said:
So the command to flash that whole bootloader file at once is "flashboot flash all bootloader"? And it won't care that it's a folder, and not a .img file?
I see what you mean about flashing the .img files that are below the "bootloader" folder in that pic I posted. To me it makes sense that it would flash those. But as you said, you should only flash every file ending in .img and "bootloader" is actually a folder, even if it is full of those files. So I just want to be clear on how exactly to flash that bootloader file.
Sorry about all the newb questions lol. Once I see your reply here, I'm going to attempt the flash. After that, hopefully I won't need any more help.
Click to expand...
Click to collapse
Let's try something a little bit easier first. As you say you unlocked bootloader, maybe you can flash the full rom through recovery. Copy the rom to a sdcard and try that first, maybe you will save yourself a lot of headaches doing this first.
I've bought two H830's and got both to TWRP/LOS ROM no problem. Regardless of your current official build on your phone, you can rollback to version 30c and dirtycow from there to get TWRP. You can get necessary tools/info from here.
0. (If you havn't already...) Enable OEM unlock in settings and unlock bootloader/fastboot
1. Use LGUP tool to clean flash an official 30c version (H83030c_00_0813.kdz) build to your LG H830
2. Dirtycow exploit to get TWRP
3. Use TWRP to install
Let me know how it shakes out
Also an important note, you CANNOT flash directly the recovery via fastboot to get TWRP, only the H850 can do that, NOT the H830. That's something important no one ever brings up. You must use the dirtycow exploit.
EDIT: Oh yeah, and I recommend using UPPERCUT to flash the kdz file since LGUP is such broken trash.
eduardvi995 said:
Let's try something a little bit easier first. As you say you unlocked bootloader, maybe you can flash the full rom through recovery. Copy the rom to a sdcard and try that first, maybe you will save yourself a lot of headaches doing this first.
Click to expand...
Click to collapse
So just put the zip file on my external SD card, and then tell flashboot to...? Or somehow use only the phone itself to flash the rom? Sorry I'm afraid I'm having trouble following along as I've never done this before.
But as per your instructions, the rom (the whole zip file) is now on the external storage SD Card.
Or did you mean to extract the zip file to a folder, and put that on the SD card? My next question would be thus:
What is the exact command to begin flashing, once I have everything in it's proper place? I did a little experiment where I tried to flash one of the files individually. The Linux terminal gave me the following error:
[[email protected] Desktop]$ cd bootloader
[[email protected] bootloader]$ fastboot flash aboot.img
unknown partition 'aboot.img'
fastboot: error: cannot determine image filename for 'aboot.img'
[[email protected] bootloader]$
As you can see, the bootloader folder is on the desktop, with many .img files inside it. Just as the pic in post #11 shows. Inside the bootloader folder is a .img file called "aboot.img". And for some reason fastboot "cannot determine the image filename for aboot.img"
DrowningInFreedom said:
EDIT: Oh yeah, and I recommend using UPPERCUT to flash the kdz file since LGUP is such broken trash.
Click to expand...
Click to collapse
Thank you for the reply! I've got two questions for you:
1. Do you have a link to the version of LG UP that you'd recommend using? It seems that there are many links out there in the wild, and some of them are to old versions. I'm not sure exactly which one I should use.
2. How exactly do you use Uppercut with LG Up? I got Uppercut, but it didn't seem to do anything when I double clicked on it. It just sat there. Is it like some kind of addon or modification to LG up? Or is it supposed to open as it's own program. Thanks!
Use the files provided by codefire , Launch UPPERCUT which will then hook into and launch LGUP automatically (All it does is make LGUP work without errors)
DrowningInFreedom said:
Use the files provided by codefire , Launch UPPERCUT which will then hook into and launch LGUP automatically (All it does is make LGUP work without errors)
Click to expand...
Click to collapse
Here's what happened when I tried to flash the right 80320a file (Nougat):
Any idea why it would say that?