Database Info

Somewhat worried...

Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?

redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
go to the root of your external sd card and delete all the zip file(s), you probably left it there when you downgrade. Also delete file from internal sdcard in /cache/recover if any. Once you unlocked you shouldn't receive anymore OTA.

redheadplantguy said:
I finally got the nerve to unlock. I had to downgrade doing it.
Click to expand...
Click to collapse
Strange, many people said the unlock tool works fine on JB.
redheadplantguy said:
Now, I heard after unlocking, an ota will brick tablet.
Click to expand...
Click to collapse
Where?
I don't say it cannot brick your tablet, but I am not aware of any reports that it does.

redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!

MartyHulskemper said:
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!
Click to expand...
Click to collapse
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.

redheadplantguy said:
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.
Click to expand...
Click to collapse
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.

buhohitr said:
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.
Click to expand...
Click to collapse
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.

redheadplantguy said:
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.
Click to expand...
Click to collapse
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.

buhohitr said:
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.
Click to expand...
Click to collapse
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.

redheadplantguy said:
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.
Click to expand...
Click to collapse
That does sound like it actually flashed something (at least partly). I would run that unlock tool another time just to be sure I wouldn't get into trouble down the road (Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on. Flashing over stock, well... minor nuisance, but it would be majorly inconvenient to have to flash root and stuff all the time.)

MartyHulskemper said:
Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on.
Click to expand...
Click to collapse
No, it just doesn't work. The updater-script inside the OTA package compares the checksums of the system apps to be patched, and aborts as soon as one doesn't match the previous stock ROM.
The only potential danger I see is the communication with the bootloader which kernel to boot - the OTA downloader (DMClient) somehow has to instruct the bootloader to load the recovery kernel to install the dlpkgfile from /cache, and if that process is still not understood by custom recovery creators (there were some problems apparently, I don't know if they are solved), you might end up with a device that only boots into the recovery and not into Android.

Thanks. I will.
Sent from my SGH-T679 using Xparent ICS Blue Tapatalk 2

F2 to HE update?

I bought my S3 used and it was already unlocked but from what I can tell still had the stock ROM (base version says it is I535VRLF2 but DEVICE STATUS says it is modified). When it powers up, I do not get a CWM or TWMP screen -- it goes directly to the normal startup so I am not sure what the previous owner loaded/did. I do not see any folders in the root folder (using ES FIle Explorer) for CWM and nothing in DATA/BACKUP (EDIT: just saw build number is VRALG7)...
Today I got a notice about an OTA upgrade (to HE) and got help on how to freeze it (as I did not want to lose root and all the customization I did to some files) but now I am wondering what changes were made from F2 to HE. I did find a post that talks about the HE upgrade.
Was F2 the previous OTA for the S3, or did my phone miss other OTAs? And if so, I am missing out on some important changes where I should let the OTA happen and then go and unlock the phone again? I read a number of threads about 'the new radio' which I assume is software to improve the phone or WIFI. Am I missing out?
Thanks
Frank
Michigan

I don't think you are missing out on anything to be honest. I did update mine and reroot without any issues, but can't really tell a difference. I would still do it so I can have the latest update on my phone since this one doesn't lock anything that we can't get back into.
Sent from my SCH-I535 using xda premium

There has been only three official releases, F2,G7,and HE. Since you are at G7 I would go ahead and OTA HE. Latest ROMS are based off of it plus you will have all the latest firmware and modem.

sfobrien said:
There has been only three official releases, F2,G7,and HE. Since you are at G7 I would go ahead and OTA HE. Latest ROMS are based off of it plus you will have all the latest firmware and modem.
Click to expand...
Click to collapse
Thanks for the reply. Will that break either my root or unlock (actually, I am not sure what state this phone is at since I did not do it -- I do find SuperSU in APPS, and have granted SuperUser to programs like Titanium Pro but there is nothing for CWM or other ROM managers...)?
Frank

If you did an OTA to get to G7 your root is probably gone. You said you have Titanium installed, try to use it. If not rooted it won't work and will advise you so. If this is the case do the OTA to HE and then you will be up to date stock ROM wise.

sfobrien said:
If you did an OTA to get to G7 your root is probably gone. You said you have Titanium installed, try to use it. If not rooted it won't work and will advise you so. If this is the case do the OTA to HE and then you will be up to date stock ROM wise.
Click to expand...
Click to collapse
No, sorry, I must not have explained it correctly. Titanium Pro, ES File Explorer, etc works fine, and I can edit/delete/freeze, etc no problem. So it is still rooted (or unlocked, I can figure out which is which). I would update to HE but only if it did not mess up what I have....
Thanks
Frank

FMinMI said:
No, sorry, I must not have explained it correctly. Titanium Pro, ES File Explorer, etc works fine, and I can edit/delete/freeze, etc no problem. So it is still rooted (or unlocked, I can figure out which is which). I would update to HE but only if it did not mess up what I have....
Thanks
Frank
Click to expand...
Click to collapse
Ok I understand now. Root and unlocked are two different things. You can flash an HE ROM and not lose your root. Unlock in your case I think you are referring to the bootloader. It will have to be unlocked prior to flashing custom ROMS. Get an app called EZ Unlock from the Playstore and it will unlock bootloader for you if it's not unlocked already.
I recommend CleanROM 3.1 if you decide to flash. Hope this has helped you some.

I'm trying to revert back to custom because i lost my IMEI but the process I was following required me to flash "VRALF bootchain" 2x and then flash "HE package" but i dont know where to get the HE package and i tried flashing root66 and VRALHD but they both failed can someone help me?

andimanium said:
I'm trying to revert back to custom because i lost my IMEI but the process I was following required me to flash "VRALF bootchain" 2x and then flash "HE package" but i dont know where to get the HE package and i tried flashing root66 and VRALHD but they both failed can someone help me?
Click to expand...
Click to collapse
The only way to get stock HE currently is OTA.

sfobrien said:
Ok I understand now. Root and unlocked are two different things. You can flash an HE ROM and not lose your root. Unlock in your case I think you are referring to the bootloader. It will have to be unlocked prior to flashing custom ROMS. Get an app called EZ Unlock from the Playstore and it will unlock bootloader for you if it's not unlocked already.
I recommend CleanROM 3.1 if you decide to flash. Hope this has helped you some.
Click to expand...
Click to collapse
I am not interested in loading any custom ROMs (although I am hoping we get the official JB soon). The only thing that is of interest to me is to be able to run certain programs that require superuser access (e.g. Titanium Pro) and to be able to edit and delete files in the root directory. So I assume all I need is root, and I don't want any OTA updates to take that away (or overwrite files that I have modified or edited that deal with the OS). Maybe that is why I cannot find any reference to CWM -- the previous owner only rooted it but did not unlock it....
Frank

FMinMI said:
I am not interested in loading any custom ROMs (although I am hoping we get the official JB soon). The only thing that is of interest to me is to be able to run certain programs that require superuser access (e.g. Titanium Pro) and to be able to edit and delete files in the root directory. So I assume all I need is root, and I don't want any OTA updates to take that away (or overwrite files that I have modified or edited that deal with the OS). Maybe that is why I cannot find any reference to CWM -- the previous owner only rooted it but did not unlock it....
Frank
Click to expand...
Click to collapse
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
http://www.scottsroms.com/downloads.php?do=file&id=247

Or you can download GooManager and flash TWRP for a more user friendly touch recovery. :laugh:
And flash the same rom from Scott.

prdog1 said:
Or you can download GooManager and flash TWRP for a more user friendly touch recovery. :laugh:
And flash the same rom from Scott.
Click to expand...
Click to collapse
Thanks forgot about GooManager.

sfobrien said:
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
http://www.scottsroms.com/downloads.php?do=file&id=247
Click to expand...
Click to collapse
OK. I have 6.0.0.8 right now. I am surprised it was there, as with my Nexus and my TP on a cold boot it would show CWM at startup. And there would be folders in the root directory (/CWM). But yes, I have CMW.
And OK on now being able to download and install a rooted HE. But most are saying it either does nothing or makes the phone run a little hotter, so unless I see a pressing need, I will just stay with what I have.
Thanks again.
Frank

prdog1 said:
Or you can download GooManager and flash TWRP for a more user friendly touch recovery. :laugh:
And flash the same rom from Scott.
Click to expand...
Click to collapse
I had tried TWRP with my HP TP and although it has a nice interface, one time, on loading a new nightly, it TOTALLY messed up my TP. I thought it was bricked. I ended up having to do a complete restore back to WebOS using WebDoctor and a lot of what I thought was code-level input via the PC trying to bring it back to life. Since then, I have only used CWM.
Thanks for the input though!
Frank

FMinMI said:
I had tried TWRP with my HP TP and although it has a nice interface, one time, on loading a new nightly, it TOTALLY messed up my TP. I thought it was bricked. I ended up having to do a complete restore back to WebOS using WebDoctor and a lot of what I thought was code-level input via the PC trying to bring it back to life. Since then, I have only used CWM.
Thanks for the input though!
Frank
Click to expand...
Click to collapse
It is personal choice. I have not had any problems with it and have been running since device was released for pre-order. I run whatever recovery seems to be most stable for the device. CWM for Tbolt. Amon Ra for Rezound. And now TWRP for S3. Have seen more bricks and failed flashes contributed to CWM so I stick with TWRP.

help
sfobrien said:
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
Can anyone tell me why every time I try to flash a ROM after I have taken all the OTA updates I am on VRLGHE; when my phone re-boots I get the verizon screen saying I have unapproved software and take to a verizon store.
Click to expand...
Click to collapse

FMinMI said:
OK. I have 6.0.0.8 right now. I am surprised it was there, as with my Nexus and my TP on a cold boot it would show CWM at startup. And there would be folders in the root directory (/CWM). But yes, I have CMW.
And OK on now being able to download and install a rooted HE. But most are saying it either does nothing or makes the phone run a little hotter, so unless I see a pressing need, I will just stay with what I have.
Thanks again.
Frank
Click to expand...
Click to collapse
The OTA installed with a custom recovery installed? Interesting. Usually OTA's fail if anything but stock recovery is installed. I only lost root but restored root with OTA Rootkeeper with stock recovery. Good to know that custom recovery can be installed and still get OTAs!

masonjb said:
sfobrien said:
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
Can anyone tell me why every time I try to flash a ROM after I have taken all the OTA updates I am on VRLGHE; when my phone re-boots I get the verizon screen saying I have unapproved software and take to a verizon store.
Click to expand...
Click to collapse
Boot loader is locked.
Click to expand...
Click to collapse

prdog1 said:
masonjb said:
Boot loader is locked.
Click to expand...
Click to collapse
OK, I used EZ Unlock 1.2 and it said "unlocked" is there a way to know for sure before flashing if it is unlocked?
Thanks!
Click to expand...
Click to collapse

[FIRMWARE] Flash KitKat the EASY Way!!!! or Go back to JellyBean

KitKat the EASY Way!!!!
Or, go back to 4.2.2 JellyBean
If you are going to return your phone back to warranty, I would suggest this method in this thread as it does a COMPLETE wipe of your device and puts it back to 'Factory'. It removes Root Flags so it does not show having been rooted, and removes ALL data.
Disclaimer: This is not MY method, but a method I used. The information and files have been figured out over time by many individuals and it's been combined in this thread.
This thread is to help Noobs AND Veterans to flash their ATT D800 LG G2 to KitKat. This will be very spelled out, and I’ve even included a video (see below), so NO Mistakes. Yes, that means you!
PLEASE refer to the Video Below before asking questions, as too many questions get a little overwhelming.
Warning! Please Read!​
This WILL erase everything on your phone and put it back to FACTORY STATE, so be sure you’ve backed up!
Ok, first thing you need to do is download the version you want. I’ve got KitKat 4.4.2 version D80020c, and I’ve got JellyBean 4.2.2 version D80010o. These are VERY LARGE files, so be patient, although I am able to get as much as 6MB/s download speeds from this server.
BIG THANKS TO bigfau for the KitKat TOT and DLL files!!!​
Download Installer - KitKat 4.4.2 D80020c - This Flashes Stock KitKat, WITHOUT Root, and WITHOUT Recovery. - Use TowelRoot and AutoRec to get Root and Custom Recovery. - Single File LARGE archive. KK MIRROR DOWNLOAD
D80020c Split Archive Download - This is the same archive as above, but split into smaller pieces for easy download.
Download Installer - JellyBean 4.2.2 D80010o - Single File LARGE archive. JB MIRROR DOWNLOAD
D80010o Split Archive Download - This is the same archive as above, but split into smaller pieces for easy download..
Download Installer - JellyBean 4.2.2 D80010d - This is for those who want to install Custom Recovery and not update to KK... - Single File LARGE archive.
Now, for the fun stuff (You may want to print this out for reference and check them off as you go)
Pre-requisites:
1. Be sure your phone is currently running a Compatible based ROM. If not, please flash a Custom Compatible Based ROM onto your phone. (ie: If you have a D800, be sure you have a D800 ROM on it. If you have a D802, be sure you have a D802 based ROM on it.)
2. Be sure you have turned on USB Debugging before starting.
Step #1: Program Installation:
1. Save the installer to your desktop
2. Run the Installer by double clicking
3. Wait a while for everything to extract (It might look like nothing is happening. This can take a few minutes, be patient, it’s HUGE)
4. (On Win7 or Win8, Accept User Account Control)
5. Accept my License
6. Don't Change Anything and click ‘Install’
7. Wait some more… and more… Large files are extracting…
8. When it pops up, click ‘Next’ to install the LG drivers. Even if you’ve already installed them, install again! This is to verify you’ve got the right ones installed.
9. Click ‘OK’ to finish the Driver install
10. Click ‘Next to install the LG Flash Tool
11. Don't Change Anything and click ‘Install’
12. Uncheck ‘Run LGFlashTool 1.8.1.1023 and click ‘Finish’ (If you forget to uncheck this, just close the program when it opens)
13. Click ‘Next’ to start the LGFlashTool Patch. (This makes it so you don’t need to change the date back on your PC)
14. Click ‘Next’ again
15. Click the bullet to ‘Agree to my License’ and then click ‘Next’
16. Don't Change Anything and click ‘Next’
17. Click ‘Start’
18. Click ‘Next’
19. Click ‘Exit’ to finish Patch Installer
20. Congratulations, Program Installations are all DONE!
Step #2: Place Phone into Download Mode:
1. With phone NOT plugged into a USB Cable, Hold the Power button to turn off phone
2. Plug your USB cable into your computer
3. Hold the Volume UP Button on your Phone
4. While Still Holding the Volume UP button, plug in the USB cable to your Phone
5. Continue to hold the Volume UP button until your phone enters Download Mode
6. If this does not work, pull the USB cable and start from #1 of this section
Step #3: Change Com Port to 41
1. With your phone STILL in Download Mode and STILL Plugged into Computer
2. Go into Device Manager
---a. Press and hold your Windows Key (Between CTRL and ALT)
---b. Tap the ‘Pause/Break’ Key (Usually Top Right of Keyboard, might be different on yours)
---c. Click on ‘Device Manager’
3. In the Device List, scroll down to ‘Ports (COM & LPT) and double click to expand
4. Find the ‘LGE AndroidNet USB Serial Port (COM4)’ (Your COM Port Number might be different, that’s OK)
5. Double click to open the port
6. On the Tabs at the top of that screen, click on ‘Port Settings’
7. Click on ‘Advanced…’
8. Click on the Com Port number to drop down the list
9. Scroll down to ‘COM41’ and select it
10. Click ‘OK’ Button to save that
11. Click ‘OK’ Button to close the Com Port Properties
12. Close the Device Manager
13. Close the System Window
14. Go back to the Desktop
15. That’s it, You’ve Changed the Com Port to 41
Step #4: Run LGFlashTool:
1. Double Click the ‘LGFlashTool’ icon on the Desktop (Win7 or Win8 accept ‘User Account Control’)
2. In the ‘Model Config’ window, check the box ‘Select Manual Mode’
3. Next to the DLL space, click the Three Dots ‘…’
4. Select the DLL file named ‘LGD800_.....v160.dll’
---a. For 4.4.2 KitKat, select ‘LGD800_20130811_LGFLASHv160.dll’
---b. For 4.2.2 JellyBean, select ‘LGD800_20130904_LGFLASHv160.dll’
5. Click the ‘Open’ Button
6. Next to the S/W space, click the ‘Remove ALL’ Button
7. Next to the S/W space, click the ‘Add’ Button
8. Select the tot file for the version you are flashing
---a. For 4.4.2 KitKat, select ‘LGD800AT-01-V20c-310-410-FEB-02-2014+0.tot’
---b. For 4.2.2 JellyBean, select ‘LGD800AT-01-V10o-310-410-OCT-19-2013+0.tot’
9. Click the ‘Open’ Button
10. Click ‘OK’ Button to save choices
11. In the LG FlashTool program, click the ‘Yellow Arrow’ pointing to the Right.
12. Wait for the program to verify your DLL and TOT selections (This takes a while)
13. If successful, you will see ‘READY!!’ on ‘Port 1 (COM41)’
14. If you DON’T see ‘READY!!’, you may need to start over
15. If you see ‘READY!!’ unplug your phone from the USB cable and Plug it right back in. DO NOT PRESS ANY BUTTONS ON YOUR PHONE. It should STILL be in Download Mode.
16. The LG FlashTool progam will now start flashing your phone!!
17. At around 80%, the program will restart your phone.
18. It takes a while for the phone to restart, but it will boot to Android. Wait for the flash program to finish and it will turn your phone back OFF. And give you a ‘SUCCESS”
19. Close FlashTool
IF for some reason, the LG FlashTool does not finish 100%, and you get a ‘Fail’, as long as your phone has now rebooted into Android, you don’t need to worry about this. Just close the program, and enjoy your Freshly Restored LG G2!
For anyone having issue with the device check not passing due to mismatched device (caused by flashing a Custom ROM with Different device model ID to your D800: ie, D801 to a D800 or vice versa.), try using the attached dll file instead of the device specific one. It has been reported to work for many... You will need to extract the zip file to get the dll.

good stuff bud!

Thanks SuperSport. I have added a link to your thread in my guide.
Can we get an installer for 80100d . It will be easier for newbies

Just so you know, in step #4 you have 4.4.2 twice But great job man! You might want to use the 10d 4.2 as that is the one that recoveries work best with. Just a thought.

epapsiou said:
Thanks SuperSport. I have added a link to your thread in my guide.
Can we get an installer for 80100d . It will be easier for newbies
Click to expand...
Click to collapse
What variant is the 801? Sprint, Verizon? Sorry, on my phone at the moement.
EDIT: Doh! Now I know what you meant... Sorry...
BAM1789 said:
Just so you know, in step #4 you have 4.4.2 twice But great job man! You might want to use the 10d 4.2 as that is the one that recoveries work best with. Just a thought.
Click to expand...
Click to collapse
Thank you for that. FIXED.
EDIT: Why is 10d easier? Is it due to the script in ioroot22? I keep flashing 10o, then use ioroot22, then use FreeGee to install TWRP. Easy Peasy. BUT, I might have modified ioroot22 script for that, I don't remember ATM.

You my friend are a very nice person lol. Taking the time to put this together.
Sent from my LG-D800 using Tapatalk

SuperSport said:
EDIT: Why is 10d easier? Is it due to the script in ioroot22? I keep flashing 10o, then use ioroot22, then use FreeGee to install TWRP. Easy Peasy. BUT, I might have modified ioroot22 script for that, I don't remember ATM.
Click to expand...
Click to collapse
I haven't had my G2 very long so I haven't been able to test myself, but just looking around the forum seems the 10o firmware causes boot issues with some custom ROMs. I could be wrong though. Maybe the problem doesn't exist anymore and I'm reading old info.

SuperSport said:
What variant is the 801? Sprint, Verizon? Sorry, on my phone at the moement.
EDIT: Doh! Now I know what you meant... Sorry...
Thank you for that. FIXED.
EDIT: Why is 10d easier? Is it due to the script in ioroot22? I keep flashing 10o, then use ioroot22, then use FreeGee to install TWRP. Easy Peasy. BUT, I might have modified ioroot22 script for that, I don't remember ATM.
Click to expand...
Click to collapse
Ioroot and then freegee TWRP route works on 80100o. Unfortunately, flashing ROMs (stock based and flex based especially) causes issues. I do not think anyone figured out the reason but going to 80100d solves the issue.

epapsiou said:
Ioroot and then freegee TWRP route works on 80100o. Unfortunately, flashing ROMs (stock based and flex based especially) causes issues. I do not think anyone figured out the reason but going to 80100d solves the issue.
Click to expand...
Click to collapse
So I understand... If you flash Stock 10o, then Root and Flash Custom Recovery, you have issues flashing other ROMs? But if you Flash back to Stock 10d, you do not have issues flashing Custom ROMs?
Also, FYI: ioroot23 was just released... I don't know if that will make a difference. It has 10o support built in.

SuperSport bro u made my life so much easier. Thank u for your hard work bro.
Sent from my LG-D800 using Tapatalk

SuperSport said:
So I understand... If you flash Stock 10o, then Root and Flash Custom Recovery, you have issues flashing other ROMs? But if you Flash back to Stock 10d, you do not have issues flashing Custom ROMs?
Also, FYI: ioroot23 was just released... I don't know if that will make a difference. It has 10o support built in.
Click to expand...
Click to collapse
Yes that is correct.
I am not sure if rooting was an issue. It was the recovery that seemed to be the issue. Not sure though and I guess since 10d worked not many people bothered to investigate further.

epapsiou said:
Yes that is correct.
I am not sure if rooting was an issue. It was the recovery that seemed to be the issue. Not sure though and I guess since 10d worked not many people bothered to investigate further.
Click to expand...
Click to collapse
I'm having the same issue flashing any stock based rom on 800o. It throws me in a bootloop. How would I get the 800d fw?
Sent from my LG-D800 using Tapatalk

SuperSport said:
So I understand... If you flash Stock 10o, then Root and Flash Custom Recovery, you have issues flashing other ROMs? But if you Flash back to Stock 10d, you do not have issues flashing Custom ROMs?
Also, FYI: ioroot23 was just released... I don't know if that will make a difference. It has 10o support built in.
Click to expand...
Click to collapse
i can confirm this is true. i lg flash tool'ed back to 10o, while i could get root i couldnt get twrp or philz recovery to work. when i went back to 10d with lg flash tool, i could get root and recovery to work. i even loki'd a couple recoveries and the recoveries wouldnt only give me a black screen when i tried to enter them on 10o. and i used ioroot23 to do all of this with.

Is this tool safe to use if the phone shows rooted after you go into download mode? Although I swore I unrooted the phone.
Took a chance and did this anyway and all is good. Upgraded successfully! Thank you so much for providing this tool! It was such a pain searching for a serial for lgflashtool. Will be donating asap for the help. Thank you thank you thank you. Directions were perfect as well and very easy to follow.

Downloads not working for me... 68% complete is furthest I've gotten. Tried seven or 8 times.
Sent from my LG-D800 using xda app-developers app

Success! after using this I called AT&T and they pushed me another small update then after that the kitkta update. I know there's no recovery available yet right?

Sorry Everyone, I've been out of town and only on my phone, but mostly busy with family stuff.
freebee269 said:
i can confirm this is true. i lg flash tool'ed back to 10o, while i could get root i couldnt get twrp or philz recovery to work. when i went back to 10d with lg flash tool, i could get root and recovery to work. i even loki'd a couple recoveries and the recoveries wouldnt only give me a black screen when i tried to enter them on 10o. and i used ioroot23 to do all of this with.
Click to expand...
Click to collapse
Thank you for the clear info. I will build a 10d version. Hopefully tomorrow.
strose09 said:
Is this tool safe to use if the phone shows rooted after you go into download mode? Although I swore I unrooted the phone.
Took a chance and did this anyway and all is good. Upgraded successfully! Thank you so much for providing this tool! It was such a pain searching for a serial for lgflashtool. Will be donating asap for the help. Thank you thank you thank you. Directions were perfect as well and very easy to follow.
Click to expand...
Click to collapse
I'm sorry, I have been away from home. Just read this. Yes, you are fine if your phone is rooted. This Flash will remove Root. As mentioned in the First post, there is currently no way to root KitKat, (Unless I've missed something since last night). So root, then go to KitKat.
mjgspr95 said:
Downloads not working for me... 68% complete is furthest I've gotten. Tried seven or 8 times.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
Some people have issues with Internet Explorer on Mega Website. You might install Chrome or Firefox and try it that way, or use a Download Manager of your choice.
humblehyper said:
Success! after using this I called AT&T and they pushed me another small update then after that the kitkta update. I know there's no recovery available yet right?
Click to expand...
Click to collapse
That is Correct, no Custom Recovery. Not unless something has appeared since last night when I last went through the forums.

Usefull guide thanks
but i think there is not a difference between those Flash DLL i had 20130904 and just freshy flashed KitKat
also if anyone cares about a LG Flash tools "PASS" then while it stops on 80-94% and boot into OS itself, do a Factory Reset of phone and it will check a Factory Flag (it sets to 5) and gives message a PASS

Doesn't sound like an easy way!!!:what:
Sent from my Nexus S using Tapatalk

pcoruganti said:
Doesn't sound like an easy way!!!:what:
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Oh but indeed it is.
Sent from my LG-D800 using Tapatalk

[Q] Root for the One Plus One?

This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.

adambombz said:
This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.
Click to expand...
Click to collapse
It's not rooted out-of-the-box. Google doesn't allow this. But apparently, root will be very easy; just plug it into your computer and enter in a few command lines and you're set (so I've heard). Undoubtedly someone will make a one-click script that makes it even easier.

EDIT: Sorry for that one, was posting too fast without thinking first... Actually rooting includes unlocking bootloader and flashing the required binaries via recovery like said below my post.
Sent from my Desire X using XDA Premium 4 mobile app

dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Click to expand...
Click to collapse
Really? Sweet!

Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Naturally if you want to root the phone, it's only a quick USB cable plug into your computer and a few command line entries away.
Click to expand...
Click to collapse
Good read, BTW.
OnePlus One Review | Android Central

CafeKampuchia said:
Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Good read, BTW.
OnePlus One Review | Android Central
Click to expand...
Click to collapse
That's where I heard it. In any case, it'll be simple; that much was promised from the beginning.
What about SuperSU though? I'm honestly not sure how that gets installed to the right place; the only times I've rooted were with programs that did it for me.

I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk

dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Sent from my Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh really? Absolutely ridiculous.
tiny4579 said:
I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Correct - no retail device shipping with Google CTS/GMS can have root enabled, much less the ability to right OUT OF THE BOX. It has to be done manually by the user, at their discretion.

From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.

Chromium said:
From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.
Click to expand...
Click to collapse
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?

dmo580 said:
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?
Click to expand...
Click to collapse
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.

cyanogenmod has been planning to separate root for years. i think they are coming up with a simple method of root. maybe just an app install?

You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Cm I think opted to make root removal so they could get cts approval and install Google Apps.
Sent from my HTC One using Tapatalk

it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.

The Jack of Clubs said:
it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.
Click to expand...
Click to collapse
I wonder if they're using this recovery.
https://github.com/CyanogenMod/android_bootable_recovery-cm
Simple recovery is the working title.
You are correct that custom recoveries aren't always needed for root; however, in Android 4.3 and later, the two primary root applications need to install a superuser daemon which makes rooting outside of recovery more difficult.

tiny4579 said:
You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Click to expand...
Click to collapse
You all guys keep saying that rooting is trivial, but nobody told how to root. I believe you that it's trivial but - anyway -please tell me how to do this step by step.

I'm actually having trouble getting my 64GB production unit to boot into TWRP or have it flash and stick. fastboot says everything is fine, then rebooting into recovery produces the stock simple recovery.
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
I'm sort of at a loss - I've done this to many Nexus devices before, and the idea is the same. My bootloader is unlocked, that went without any issues.
Booting a debug boot.img from https://cyngn.com/products/oneplusone via fastboot just ends up shutting down and showing the battery charging icon.
Volume Up + Power while booting ends up with a black screen - in fact, the only way I can get into recovery is from a booted OS.
Edit: After many tries, trying different cables and unchecking the Settings -> Development -> update recovery with system updates, the TWRP flash succeeded, and the subsequent SuperSU sideload went just fine. Now I'm rooted.
Another tip regarding using Power+VolDn or Power+VolUp - things happen so slowly that if you keep holding Power, it'll actually trip a reboot before it has a chance to load. Just hold the Power button for a few seconds when booting, then let go and keep the VolUp or VolDn pressed.

Chromium said:
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.
Click to expand...
Click to collapse
I just did this and it seems to have worked. TiBu just completed..
Used "Fastboot boot TWRP-2.7.1.0.zip" at ADB/Fastboot interface. It booted to TWRP. As I closed, it stated that it looks like "Your device isn't rooted, Do you want to install SuperSU?" To which I said Yes. It rebooted and I was able to open SuperSU, already on the phone, and get root. Then, opened TiBU and performed a full backup.

Archon810 said:
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
Click to expand...
Click to collapse
The first time I did this it hung for a while. it eventually boots into the recovery. I think it took about 2 minutes for it to finally boot into it.
Maybe that helps?

Root One+ fastboot devices hnags "waiting for device"
I amd trying to unlock bootlaoder, and install TWRP on my ONE+. I have tried both android SDK, and TOOLKIT FOR ONEPLUS FROM XDA, and I cannot get fastboot devices to recognize my One+.
What I have do so far:
My PC: windows 7 - 64bit
Installed SDK kit form developer.android.com, and installed the latest composite usb driver from Google.
Installed OnePLus toolkit and tried using that, no dice.
when I execute "fastboot devices" from my fastboot folder, my prompt hangs "waiting for device" FOREVER!!!
"ADB DEVICES" WORKS PERFECTLY, AND ECHOES MY SERIAL NUMBER BACK TO ME."

How I gained root and CWM recovery on my MT7-L09 with out bootloader unlock.

Let me start off by saying I'm new to the Huawei Ascend Mate 7 but I'm no newcomer to Android. I've been a member of XDA for some years now. Since before IceCream sandwich. I've done my far share to help out this community as it has helped me. I'm originally a themer, but lately been working on a few ROMs. Mostly tweaked based on stock, deodexed, zip aligned, debloated, and build prop mods.
My worth I bring to the table is I'm just BALLSY and experienced enough to try anything and flash just about anything. (With in reason of course). I seem to have acquired a unique talent to be able to unbrick every device that's been laid before me over the passed year or so as well as a few of my own. And have aided in the unbricking of several peoples device that have reached out to me on here.
So with this uncanny ability to be able to unbrick devices I took it upon myself to take a few stabs at gaining root and flashing CWM to my MT7-L09 without unlocking the boot loader. Due to reading post after post of people not getting replies from their emails to Huawei asking for an unlock code.
So now to the point......
I can in NO way take credit for this development nor do I take any responsibility for your actions or decisions to follow this guide unsuccessfully.
1. First I downloaded the 141 update with Supersu built in thats posted here in this forum and the Mate7.zip posted here as well.
Moved the 141 update with SU titled Update.zip to my sdcard/dload.
2. Went to settings/updater clocked MENU at the bottom, then selected LOCAL UPDATE.
3. After it completed (which took about 5 mins) I rebooted installed SuoerSu from the play store and SuperSu Pro. And opened to update binary.
4. Then used a Root Browser to locate the Mate7.zip that I downloaded earlier in the same forum. I then extracted its contents.
5. Download FLASHIFY from the play store. Grant SuperSU permission. And use FLASHIFY to flash the CWMRECOVERY.zip that was also in the Mate7.zip file that you extracted earlier.
6. And this is the most important thing. I don't know how many times I've seen people start modding and flashing then brick and ask for help only to realize "no I didn't make a backup". ALWAYS MAKE A BACKUP IMMEDIATELY AFTER INSTALLING A CUSTOM RECOVERY. If you don't then you have no one to blame but yourself when you can restore.
So as stated above I had no hand in developing any of this. Its just a method I used to gain root, update, and gain CWM recovery WITHOUT boot loader unlock.
And here's the copied text from URYLDOR's forum where I found all the essential pieces I used to gain all this. I did not unlock my boot loader though. This method nor any other would work for me so I took a shot in the dark at my method just to get root, CWM, and update as well.
ALL THANKS SHOULD BE GIVEN TO HIM FOR HIS DEVELOPMENT and if my method works for you then youre welcome to thank me for it and it alone but thank @Uryldor too.
...............................................................
Here is the translated guide to unlock bootloader on European model from the link I posted earlier.
I’m not responsible of any damage made to your device.
Download, unzip and run the Huawei product ID generator then select Huawei Y300-0000 in the product model field. Paste your IMEI in the product IMEI field and it should give you a product ID. We will use it later.
Go to http://en.club.vmall.com/emotiondownload.php?mod=unlock&action=apply tick the box at the end of the Unlocking Agreement and click next.
Here is what to choose/write in the form:
Product type: Smartphone
Product model: Huawei Y300-0000
Product SN: The SN of your Mate 7
Product IMEI/MEID: The IMEI of your Mate 7
Product ID: The number Product ID Generator gave you.
Enter the captcha and click submit.
Now it should give you your unlock code.
Download mate7.zip from https://mega.co.nz/#!aB8mRATA!nY7VJPUEESxBv5iRZ95vORbcjUQwLoyEyHagPi6RMGI and unzip it.
Install the driver if needed by running Driver\all\DriverSetup.exe
Copy SuperSU-PRO-V2.09.zip to your sd card.
Reboot your Mate in fastboot by holding Volume Down+Power for 10 seconds and plug it.
Unzip Recovery_b119.zip, go to tools, hold Shift and right click then choose “Open command windows here.
Type:
Now your bootloader is unlocked. Don’t close the command windows, now we will install the ClockWorkMod recovery.
In the window type:
You can flash recovery_stock.img with the same command if you want to revert back to the stock recovery.
Now go into recovery by holding Volume Up+Power for 10 seconds.
Then go to:
Install zip>choose zip from /storage/sdcard1> SuperSU-PRO-V2.09.zip and select yes.
Reboot.
Your Mate 7 is now unlocked and rooted!

Thanks you save my life and my mate 7... work fine here

Did you not have to flash using the force update method? I installed 141 via the local update method (came from 137) and SuperSU fails to update the binary.

ritdaw said:
Did you not have to flash using the force update method? I installed 141 via the local update method (came from 137) and SuperSU fails to update the binary.
Click to expand...
Click to collapse
Yeah but I downloaded the 141 update that has root built in. I then used "FLASHIFY" From the play store to flash the cwm.IMG. I then booted to CWM then flashed the SuperSU.zip that's mentioned in the above thread. Then made a back up in CWM. Rebooted and didn't have to update binary after all that.
Warning. Do not flash CM-11 if you used my method to root and install CWM. I did and now I'm soft bricked. I think it has something to do with the boot loader not being unlocked. I'm stuck at the "Rescue Mode" screen with the error
Error!
Func NO : 12 ( Func_load_iom3)
Error NO : 1
It took cm-11 OK. Just didn't ever boot fully so when I went to reflash the 141 update to restore it or my backup it acted like it took that fine but upon first boot back to stock I ended up stuck in "Rescue Mode" and getting the above code. ADB not recognizing it since its in "Rescue Mode" which is basically fast boot. Some fast boot commands work like Fastboot update ....... And fastboot reboot. But not " fastboot flash " does not. And that's where I think the boot loader being locked is preventing me from fast booting anything to it.
Any suggestions are appreciated.

Mmmmm... bad news men... I hope you can bring to life your Huawei mate again... I use you method and works fine... but I don't think flash any Rom... maybe you can try unlock your boot loader or use Huawei hi suite?

i was able to flash the 141 with supersu - but i wasn't able to update it, nor to flash anything with flashify because there are no root-rights - at least the phone still works
i successfully applied steps 1 and 2
3 downwards not usable (update supersu not working, even after reboot)
UPDATE: with the force update it worked

There is no cwmrecovery in the mate7 folder. Are you referring to the other recovery that isn't the stock one?

charlieb620 said:
There is no cwmrecovery in the mate7 folder. Are you referring to the other recovery that isn't the stock one?
Click to expand...
Click to collapse
Yeah it says its a modified version of stock. Its cwm. Even has the logo

Question??? I installed this Rom and everything works fine... but if I delete a system app (Google maps for example)... the app is gone but when the phone reboot the apps appears again??? I use a root browser to delete the app... which should be the problem??? I am the only whit this trouble??

Will this method also work when you;ve updated to lollipop? I cannot get the unlock code from huawei for my mate 7, and do want to root!

djzero86 said:
Question??? I installed this Rom and everything works fine... but if I delete a system app (Google maps for example)... the app is gone but when the phone reboot the apps appears again??? I use a root browser to delete the app... which should be the problem??? I am the only whit this trouble??
Click to expand...
Click to collapse
Its because you have to also go into data/app and delete it there, and data/data and delete it there too. Then wipe dalvik and cache. Reboot. Done.

mattwheat said:
Its because you have to also go into data/app and delete it there, and data/data and delete it there too. Then wipe dalvik and cache. Reboot. Done.
Click to expand...
Click to collapse
I will try....

On my ham 7 don't work... I tried doing that you say and can't delete the apps

mattwheat said:
Its because you have to also go into data/app and delete it there, and data/data and delete it there too. Then wipe dalvik and cache. Reboot. Done.
Click to expand...
Click to collapse
Well matt somes guys never learn like me.LOL I went and bought another Lg g flex. I still have My Mate 7 and mate 2 galaxy mega, note 3 , note 2 Did you see where Huawei may get the next Nexus line..

dekraan said:
Will this method also work when you;ve updated to lollipop? I cannot get the unlock code from huawei for my mate 7, and do want to root!
Click to expand...
Click to collapse
Yes, worked for me on 5.1
EDIT: !!DONT FLASH!! on 5.1, phone boots, i can get into recovery, but can't install anything
does anyone have stock recovery for B308 5.1??

Will unlock bootloader on this devices break up some features, as on Xperia devices (like DRM keys and so)?
Thank you!

your warranty, but as far as i can tell it doesn't break any features

KennyLG123 said:
Well matt somes guys never learn like me.LOL I went and bought another Lg g flex. I still have My Mate 7 and mate 2 galaxy mega, note 3 , note 2 Did you see where Huawei may get the next Nexus line..
Click to expand...
Click to collapse
Sorry just seeing this message. Yeah it was just released for pre sale yesterday. Huawei does in fact make the Nexus 6p and LG makes the 5x. I'm seriously considering getting the 6p....

Are you sure it works?
It works without unlock bootloader?
The 141, that the Russian guys, only the SuperSU app, but without the superuser binary, which will start during the boot process, it is not worth anything.
So much power could be any other rom.
The stock bootloader available in the boot process, and does not allow only the stock recovery.
Are you sure it works?