Database Info

[Q&A/OT] •ᴥ• GPE •ᴥ• Android Lollipop •ᴥ• MULTICARRIER •ᴥ•

[Q&A/OT] •ᴥ• GPE •ᴥ• Android Lollipop •ᴥ• MULTICARRIER •ᴥ•
Welcome to the home of
{
"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"
}
Digitalhigh GPE - The ORIGINAL GPE for HTC M8
(often imitated, never duplicated!)
Hi! I'm Digitalhigh, and welcome to this Q&A / Off topic thread thread.
My masterpiece rom can be found here​

I've been quiet too because this ROM is perfect for me lol.
I have a challenge for you all though. VVM. And don't tell me to use YouMail because I already know how its "better". I have my reasons for needing Verizon's VVM.
Sent from my HTC One_M8 using XDA Free mobile app

ludeboy said:
And don't tell me to use YouMail because I already know how its "better". I have my reasons for needing Verizon's VVM.
Click to expand...
Click to collapse
Sounds like somebody has been saving their ex's voicemails for too long.... [emoji6]

fronc said:
Sounds like somebody has been saving their ex's voicemails for too long.... [emoji6]
Click to expand...
Click to collapse
Lol
Sent from my HTC One_M8 using XDA Free mobile app

[Q]Is there an advanced wipe I need
jmgg2k said:
Install again the rom. When Aroma ask to reboot say "NO" (additional process being installed). Then reboot from the recovery.
Tell me how it goes
Click to expand...
Click to collapse
First I would like to apologize to Digital High and the moderators for my silly questions.
In the OP there was a link for firmware and a message that you should try with 4.4.4 first then if it does not work go to 5.0.1( I did not know which version was linked as the name of the file does not give it away but assumed it was 5.0.1). I tried it first which worked but no boot animation, WiFi and could not reboot correctly.
Being that I was running Digital High's 4.4.4 GPE from his thread to a T, I installed the firmware that he had linked. I then within TWRP 2.8.1 I clicked wipe and then slide to wipe (Factory reset it says at the top then data/cache/dalvik). I then installed the ROM.
I then ready a post that the newest firmware was under this thread :
http://forum.xda-developers.com/showthread.php?t=2723159
but I ignored per OP guidance.
When the HTC Screen does come up it goes away after a few minutes and is on a lock screen. I did not consider this to be stuck.
I reinstalled and when prompted in Aroma I select "No" the process finished and pushed back to recovery, I hit restart.
Device was at HTC screen (btw the HTC developmental red text is still there gravy right?)for about five minutes, no boot animation, then the android lock screen appears.
I also tried flashing the firmware listed in the link above but get I get 42 custom ID fail. My CID is set to GOOGL001 so I am not sure what the issue is.
Is there an advanced wipe I need to try or a specific firmware I need to flash and then re flash this one? I am up for trying anything to get this working. I have three friends who are looking to do this and donate if it works well but I still can't get my test device figured out.

Hephaestus88 said:
First I would like to apologize to Digital High and the moderators for my silly questions.
In the OP there was a link for firmware and a message that you should try with 4.4.4 first then if it does not work go to 5.0.1( I did not know which version was linked as the name of the file does not give it away but assumed it was 5.0.1). I tried it first which worked but no boot animation, WiFi and could not reboot correctly.
Being that I was running Digital High's 4.4.4 GPE from his thread to a T, I installed the firmware that he had linked. I then within TWRP 2.8.1 I clicked wipe and then slide to wipe (Factory reset it says at the top then data/cache/dalvik). I then installed the ROM.
I then ready a post that the newest firmware was under this thread :
http://forum.xda-developers.com/showthread.php?t=2723159
but I ignored per OP guidance.
When the HTC Screen does come up it goes away after a few minutes and is on a lock screen. I did not consider this to be stuck.
I reinstalled and when prompted in Aroma I select "No" the process finished and pushed back to recovery, I hit restart.
Device was at HTC screen (btw the HTC developmental red text is still there gravy right?)for about five minutes, no boot animation, then the android lock screen appears.
I also tried flashing the firmware listed in the link above but get I get 42 custom ID fail. My CID is set to GOOGL001 so I am not sure what the issue is.
Is there an advanced wipe I need to try or a specific firmware I need to flash and then re flash this one? I am up for trying anything to get this working. I have three friends who are looking to do this and donate if it works well but I still can't get my test device figured out.
Click to expand...
Click to collapse
Are you saying you have a Google Play Edition device? Or did you change the CID to reflect that? You need to install the latest firmware for whatever variant you actually have.

Captain_Throwback said:
Are you saying you have a Google Play Edition device? Or did you change the CID to reflect that? You need to install the latest firmware for whatever variant you actually have.
Click to expand...
Click to collapse
You see that is confusing because you just asked me a question.
I have a Verizon HTC M8 that was running 4.4.4. GPE. I want to got to 5.0.1. Maybe I need some CID clarification but everyone so far has said that for GPE roms you need GOOGL001 vs having the VZW based CID.
Moderators, is there a way to move this the Q and A section like all of my posts without having to repost and also delete them from this thread to free up space or whatnot?

Hephaestus88 said:
Moderators, is there a way to move this the Q and A section like all of my posts without having to repost and also delete them from this thread to free up space or whatnot?
Click to expand...
Click to collapse
Done:good:

TonyStark said:
Done:good:
Click to expand...
Click to collapse
I meant the Q&A thread for the ROM, but I guess those aren't necessarily ROM questions. This works, I guess.
EDIT: Actually, the Q&A thread for the ROM would be better - this will probably get lost here.
---------- Post added at 01:23 PM ---------- Previous post was at 01:21 PM ----------
Hephaestus88 said:
You see that is confusing because you just asked me a question.
I have a Verizon HTC M8 that was running 4.4.4. GPE. I want to got to 5.0.1. Maybe I need some CID clarification but everyone so far has said that for GPE roms you need GOOGL001 vs having the VZW based CID.
Moderators, is there a way to move this the Q and A section like all of my posts without having to repost and also delete them from this thread to free up space or whatnot?
Click to expand...
Click to collapse
You are confused.
The only reason you would change your CID is if you were doing a full GPE conversion by flashing an RUU. That's not what you're doing here. You need to change your CID back, and flash the latest full Verizon 4.4.4 firmware. Not having that flashed is the root of your issue.
P.S. There is a "Q&A" tab on the ROM thread, along the top. All you had to do is reply to my question there, and I would see it.

Captain_Throwback said:
The only reason you would change your CID is if you were doing a full GPE conversion by flashing an RUU. That's not what you're doing here. You need to change your CID back, and flash the latest full Verizon 4.4.4 firmware. Not having that flashed is the root of your issue.
P.S. There is a "Q&A" tab on the ROM thread, along the top. All you had to do is reply to my question there, and I would see it.
Click to expand...
Click to collapse
Sorry, I did not know that. Generally I think people panic when they need help and may not see what is right in front of them.
Is this the current VZW firmware? (Under 4.4.4 Zip)
http://forum.xda-developers.com/showthread.php?t=2723159
Also I believe if I understand you right I need to change my CID to VZW__001, flash VZW firmware, then install GPE ROM? or do you need to change the CID back to GOOGL001 after the firmware update (VZW firmware) to get GPE ROM to go through?

Hephaestus88 said:
Sorry, I did not know that. Generally I think people panic when they need help and may not see what is right in front of them.
Is this the current VZW firmware? (Under 4.4.4 Zip)
http://forum.xda-developers.com/showthread.php?t=2723159
Also I believe if I understand you right I need to change my CID to VZW__001, flash VZW firmware, then install GPE ROM? or do you need to change the CID back to GOOGL001 after the firmware update (VZW firmware) to get GPE ROM to go through?
Click to expand...
Click to collapse
You don't need to change the CID back after flashing the firmware. Your other steps are correct.

Alright.
Would I need to do this from fastboot flash zip or fastboot oem rebootRUU then flash?
I tried the fastboot flash zip with the updated firmware in the fastboot.exe folder and I get (remote: not allowed).
C:\Users\dgreen\AppData\Local\Android\sdk\platform-tools>fastboot flash zip 3.28
Code:
.605.4-firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (30685 KB)...
OKAY [ 2.242s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.261s
I also tried it after running fastboot oem rebootRUU and it said:
Code:
C:\Users\dgreen\AppData\Local\Android\sdk\platform-tools>fastboot oem rebootRUU
< waiting for device >
...
(bootloader) Start Verify: 0
OKAY [ 0.072s]
finished. total time: 0.074s
C:\Users\dgreen\AppData\Local\Android\sdk\platform-tools>fastboot flash zip 3.28
.605.4-firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (30685 KB)...
OKAY [ 2.233s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 2.837s
That is where I got the CID questions from after looking into the 42:custom id check fail and I did not change the MID so I thought it was irrelevant.

Hephaestus88 said:
Alright.
Would I need to do this from fastboot flash zip or fastboot oem rebootRUU then flash?
I tried the fastboot flash zip with the updated firmware in the fastboot.exe folder and I get (remote: not allowed).
C:\Users\dgreen\AppData\Local\Android\sdk\platform-tools>fastboot flash zip 3.28
Code:
.605.4-firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (30685 KB)...
OKAY [ 2.242s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.261s
I also tried it after running fastboot oem rebootRUU and it said:
Code:
C:\Users\dgreen\AppData\Local\Android\sdk\platform-tools>fastboot oem rebootRUU
< waiting for device >
...
(bootloader) Start Verify: 0
OKAY [ 0.072s]
finished. total time: 0.074s
C:\Users\dgreen\AppData\Local\Android\sdk\platform-tools>fastboot flash zip 3.28
.605.4-firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (30685 KB)...
OKAY [ 2.233s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 2.837s
That is where I got the CID questions from after looking into the 42:custom id check fail and I did not change the MID so I thought it was irrelevant.
Click to expand...
Click to collapse
Sorry, I see my post was stated incorrectly.
You don't need to change the CID BACK at the end of the process. As I previously stated, your CID should reflect your actual variant, so that first step is correct and the most important. Just don't change it back at the end. Sorry for the confusion.
And your second process is the correct one.
EDIT: I updated my post to avoid further confusion in case anyone else reads this.

This is where I need help clarifying what I have done. I also read another one of your threads and believe that I may have found the issue but please help clear things up.
I converted to GPE during 4.4 KitKat by following Digital High's writeup. I believe you told another user that you would need to go back to sense layout due to space requirements.
Knowing that information what are my next steps?
CID(VZW__01 or GOOGL001)?
Firmware (Flash the newest Verizon stock one then what, leave, update to 5.0.1)?
ROM(Install stock image then do 5.0.1 GPE?
I am not concerned with any data or backing up.
I am very literal and do not like to leave room for me to misinterpret anything.
Thanks BTW! I really appreciate it.

Hephaestus88 said:
This is where I need help clarifying what I have done. I also read another one of your threads and believe that I may have found the issue but please help clear things up.
I converted to GPE during 4.4 KitKat by following Digital High's writeup. I believe you told another user that you would need to go back to sense layout due to space requirements.
Knowing that information what are my next steps?
CID(VZW__01 or GOOGL001)?
Firmware (Flash the newest Verizon stock one then what, leave, update to 5.0.1)?
ROM(Install stock image then do 5.0.1 GPE?
I am not concerned with any data or backing up.
I am very literal and do not like to leave room for me to misinterpret anything.
Thanks BTW! I really appreciate it.
Click to expand...
Click to collapse
Flashing a GPE ROM is NOT the same as converting to GPE. @digitalhigh doesn't have a write-up for converting to GPE of which I'm aware.
Change to the Verizon CID.
Flash the Verizon 4.4.4 firmware.
Flash GPE ROM.
That's it.

Thread now linked to the Official DevDB Project.

Thank You so much!
I just wanted to follow up and say that it is working now with the boot animation. I would like to mention that there should be instructions about the carrier agnostic lollipop driver option as this is not explained well. I took it as though it is the new 5.0.1 firmware and I checked the box.
I was also receiving a message prior about Dolby Digital stopped working right after boot up on welcome screen. I figure in case anyone else runs into this issue it will an indication of what went awry.
I cannot thank you guys enough. Really was game changer for me today! Let me know how I can help contribute to the XDA-Way.

Hephaestus88 said:
I just wanted to follow up and say that it is working now with the boot animation. I would like to mention that there should be instructions about the carrier agnostic lollipop driver option as this is not explained well. I took it as though it is the new 5.0.1 firmware and I checked the box.
I was also receiving a message prior about Dolby Digital stopped working right after boot up on welcome screen. I figure in case anyone else runs into this issue it will an indication of what went awry.
I cannot thank you guys enough. Really was game changer for me today! Let me know how I can help contribute to the XDA-Way.
Click to expand...
Click to collapse
The Carrier-agnostic firmware IS the 5.0.1 firmware. But the OP specifically states that you must already be updated to your carrier's latest 4.4.4 firmware before flashing the ROM. I'm not sure what the confusion is?

Captain_Throwback said:
The Carrier-agnostic firmware IS the 5.0.1 firmware. But the OP specifically states that you must already be updated to your carrier's latest 4.4.4 firmware before flashing the ROM. I'm not sure what the confusion is?
Click to expand...
Click to collapse
When going through Aroma there is a check box to install this however it is deselected by default. There is not instruction to check this box or not and who should check other than him saying that try it one way first and then another way if it doesn't work.

Hephaestus88 said:
When going through Aroma there is a check box to install this however it is deselected by default. There is not instruction to check this box or not and who should check other than him saying that try it one way first and then another way if it doesn't work.
Click to expand...
Click to collapse
And those are the correct instructions . . . so again, I'm . Some people need it, others don't. If everything is working without it, then don't bother with it. If it's not, then try it.

[TOOL] WinDroid Toolkit | Unlock | Root | Flash | Install | One (M9)

Link To Main Thread
{
"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"
}
About
The WinDroid Toolkit is a Windows program built in Visual Studio using the C# programming language that simplifies the rooting process for many Android devices. The toolkit makes it easy to unlock your bootloader, flash a custom recovery and gain permanent root. It also includes other functions such as flashing kernels, pushing files and installing apps. If you find it helpful, give me a thanks and a donation if you can. If you find a bug or have a feature request, feel free to leave a reply. Thanks!
Download
WinDroid Toolkit
Changelog
Check out this document for current and past changelogs.
Supported Devices
Check out this spreadsheet for a list of currently supported devices.
Device not supported? Make a request here!
Contribute
Check out the source code on GitHub here.
Disclaimers
Please do not post, mirror, or take credit for this toolkit or any related work without explicit permission.
I am in no way responsible for any harm, damage, nuclear fission or bee infestation that may occur to your device through the use of this toolkit.

Reserved
Reserved.

This works with the new bootloader setup for the M9?

Captain_Throwback said:
This works with the new bootloader setup for the M9?
Click to expand...
Click to collapse
The toolkit uses the official HTC Dev bootloader unlock, official TWRP, and latest SuperSU, so I assume it does, unless extra steps are needed.

The program stops on my windows7 x64 laptop
It install the drivers and show online but if i choose Get tooken ID my phoon reboots and after that the program stops.
sorry for my bad english
now i tried to push a file and that works, i got allready my token and unlocked different way.

How
niekie73 said:
The program stops on my windows7 x64 laptop
It install the drivers and show online but if i choose Get tooken ID my phoon reboots and after that the program stops.
sorry for my bad english
now i tried to push a file and that works, i got allready my token and unlocked different way.
Click to expand...
Click to collapse
SO how did you get token and unlock? Get my phone Tuesday so trying to find out how to get this done before it gets here...

kaw900r said:
SO how did you get token and unlock? Get my phone Tuesday so trying to find out how to get this done before it gets here...
Click to expand...
Click to collapse
I used this one
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133

Any chance you can add some sort of extracting files from twrp backup and an deodex function to the tollkit?

DroidShift79 said:
Any chance you can add some sort of extracting files from twrp backup and an deodex function to the tollkit?
Click to expand...
Click to collapse
I can look into it, but any features I add to the toolkit would have to be compatible with all of the devices I support, which is over 90 now. It may not work with every device correctly.

WindyCityRockr said:
I can look into it, but any features I add to the toolkit would have to be compatible with all of the devices I support, which is over 90 now. It may not work with every device correctly.
Click to expand...
Click to collapse
doesn't work. won't flash twrp. and my phone is unlocked.

stargaterules said:
doesn't work. won't flash twrp. and my phone is unlocked.
Click to expand...
Click to collapse
Can confirm, unlocked using htcdev.com and flashed TWRP the old fashioned way (fastboot flash recovery twrp.img) and received this message:
target reported max download size of 536870912 bytes
sending 'recovery' (35928 KB)...
OKAY [ 0.945s]
writing 'recovery'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.968s
So it looks like we might need s-off first? That would suck.

NaitsirkC said:
Can confirm, unlocked using htcdev.com and flashed TWRP the old fashioned way (fastboot flash recovery twrp.img) and received this message:
target reported max download size of 536870912 bytes
sending 'recovery' (35928 KB)...
OKAY [ 0.945s]
writing 'recovery'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.968s
So it looks like we might need s-off first? That would suck.
Click to expand...
Click to collapse
Yup, that's exactly what I get and yes, need s off first. So we gotta wait.

stargaterules said:
Yup, that's exactly what I get and yes, need s off first. So we gotta wait.
Click to expand...
Click to collapse
Actually I misspoke. In bootloader mode it says that, but in download mode, the one with the black background instead of the white background, it works like a charm! That's a relief.

What works like a charm? It's not letting me install recovery because s is on. How did you get past that?

stargaterules said:
What works like a charm? It's not letting me install recovery because s is on. How did you get past that?
Click to expand...
Click to collapse
It's supposed to be in download mode, it works just fine then. Manually choose download mode not bootloader and it works

WindyCityRockr said:
The toolkit uses the official HTC Dev bootloader unlock, official TWRP, and latest SuperSU, so I assume it does, unless extra steps are needed.
Click to expand...
Click to collapse
Recovery must be flashed while in download mode on the M9, not in bootloader. Flashing in bootloader is only possible if the device is S-OFF.

Captain_Throwback said:
Recovery must be flashed while in download mode on the M9, not in bootloader. Flashing in bootloader is only possible if the device is S-OFF.
Click to expand...
Click to collapse
awesome. it works. maybe add the info about device needing to be in download mode so people don't get confused. the program reboots the device into bootloader.

Will the program be updated?

Captain_Throwback said:
Recovery must be flashed while in download mode on the M9, not in bootloader. Flashing in bootloader is only possible if the device is S-OFF.
Click to expand...
Click to collapse
Hi guys, so the steps are the next:
1.- Unlock Bootloader Normally with the program.
2.- using this program Flash recovery but get into download mode manually(the program take to bootloader mode)
3.- ROOT.
Correct?
Thanks!

emptyPD said:
Hi guys, so the steps are the next:
1.- Unlock Bootloader Normally with the program.
2.- using this program Flash recovery but get into download mode manually(the program take to bootloader mode)
3.- ROOT.
Correct?
Thanks!
Click to expand...
Click to collapse
2b Make a stock backup
For 3 you need to make sure you install the latest Beta SuperSU, which I don't think is linked in this app.

Help me knock the dust off this thing....

so last time i used mytf300t. i did the unbrick recovery and saved all the files for recovery. i now try to update the tablet. yrs later from 5.0 with twrp to 6.0 and up. the rom flashed but my recovery wont flash the google app packages. says basically the new scripting isnt supported by my older recovery. being my boot loader is the unbrick one. how can i update this thing and still be able to use the unbrick files in the future if needed?like its been a while since it touched this. i wanna get it going again feel like wasted $ lol

kaos420 said:
so last time i used mytf300t. i did the unbrick recovery and saved all the files for recovery. i now try to update the tablet. yrs later from 5.0 with twrp to 6.0 and up. the rom flashed but my recovery wont flash the google app packages. says basically the new scripting isnt supported by my older recovery. being my boot loader is the unbrick one. how can i update this thing and still be able to use the unbrick files in the future if needed?like its been a while since it touched this. i wanna get it going again feel like wasted $ lol
Click to expand...
Click to collapse
Please check whether you have Kang TWRP [email protected] or not. If not, install it first then try again!

ebonit said:
Please check whether you have Kang TWRP [email protected] or not. If not, install it first then try again!
Click to expand...
Click to collapse
Will this recovery work with the NV bootloader?
Sent from my 0x1 Note 4...... I love tep

kaos420 said:
Will this recovery work with the NV bootloader?
Click to expand...
Click to collapse
The developer advises the devise "MUST BE ON A BOOTLOADER ENDING IN 27.1 or 27.5"
https://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479
Start fastboot by "Vol Down" and "Power On" together and in the left upper corner the bootloader version appears for instance as "WW-epad-10.6.1.27.5-201230902" A03.

{
"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"
}
what I'm working with
Sent from my 0x1 Note 4...... I love tep

Sent from my 0x1 Note 4...... I love tep

**** so I need to update bootloader looks like. Will that mess us my nvflash???
Sent from my 0x1 Note 4...... I love tep

kaos420 said:
**** so I need to update bootloader looks like. Will that mess us my nvflash???
Click to expand...
Click to collapse
The bootloader on your device belongs to the second last Asus update of JB.
"If the current bootloader = 10.6.1.15.3 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device."
Please look here: https://forum.xda-developers.com/showthread.php?t=2195883.
I would like to recommend to you to upgrade your device on the latest ASUS JB Stock Rom. After that you may install Kang TWRP 2.8.7.2 that is required to flash any KatKiss custom rom like MM 6.0 or N 7.1.
https://forum.xda-developers.com/transformer-tf300t/development/rom-t3237867
https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702

Ok updating to latest. How do I keep NV flash? Do I need to do that process over for newer bootloader after?
Sent from my 0x1 Note 4...... I love tep

c:\Android\platform-tools>fastboot -i 0x0b05 flash staging blob
target didn't report max-download-size
sending 'staging' (800931 KB)...
FAILED (command write failed (No error))
finished. total time: 0.004s latest blob . wont flash . fastboot devices works sees serial

A reboot fixed that. Bootloader is latest. I flashed latest twrp 3.0.2 sitting at wipe data via recovery... Been about 5 minutes formatting it... But I wanna remember it takes awhile with this.... Hoping 10 15 minutes.... Kitkass 7.1.1 already on sd card.... Just waiting...
edit
well its up and going new recovery bootloader and rom. thanks for the refresher on this thing. are my old nvflash backups good? or do i need to redo them for the 25.7 one?
Sent from my 0x1 Note 4...... I love tep

No, they are good. You only need them if you totally brick the tab. And then you won't care what you restore it to. You can always work your way back to present.

berndblb said:
No, they are good. You only need them if you totally brick the tab. And then you won't care what you restore it to. You can always work your way back to present.
Click to expand...
Click to collapse
that is awesome to know and very valid. this thing runs better now then it did back then lol .

[v521][RECOVERY][TWRP] TWRP-3.1.1-0_v521-lineage for LG G Pad X 8.0[Unofficial]

{
"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"
}
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through
You can find the source code for TWRP at https://github.com/omnirom/android_bootable_recovery
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Install as image using Flashify or TWRP
Downloads: TWRP-3.1.1-0_v521-recovery.img
Version Information
Status: Stable
TWRP Version: 3.1.1-0
Kernel: 3.10.84-lineage
Created 2017-05-18
Last Updated 2017-05-19

reserved

Thank you!
Sent from my LG-V521 using XDA-Developers Legacy app

king3opobn said:
Thank you!
Sent from my LG-V521 using XDA-Developers Legacy app
Click to expand...
Click to collapse
TWRP-3.1.1-0 is here --> TWRP-3.1.1-0_v521-recovery.img

For some reason im not able to make a nandroid backup of my stock rooted rom. TWRP is failing to mount data. Am I doing something wrong? I've used TWRP countless times on other devices to backup and have never had a problem.

mad212 said:
For some reason im not able to make a nandroid backup of my stock rooted rom. TWRP is failing to mount data. Am I doing something wrong? I've used TWRP countless times on other devices to backup and have never had a problem.
Click to expand...
Click to collapse
i downloaded the 3.1.1-0 version and reinstalled but no issue here. did you edit anything or install on the wrong device? mount points are defined in the /etc/recovery.fstab file in recovery. maybe try re-downloading and installing

mad212 said:
For some reason im not able to make a nandroid backup of my stock rooted rom. TWRP is failing to mount data. Am I doing something wrong? I've used TWRP countless times on other devices to backup and have never had a problem.
Click to expand...
Click to collapse
if you just rooted the device you're going to have to wipe data in twrp before it will be mountable

HighRidas said:
if you just rooted the device you're going to have to wipe data in twrp before it will be mountable
Click to expand...
Click to collapse
That did it. Thanks!

Hi.
Using your recovery, I get this:
"b3" devices; this is a "v521". Installer Error (Status 7)
Flashed to an older version of TWRP for the v521 and that worked. Thoughts?

bmac6996 said:
Hi.
Using your recovery, I get this:
"b3" devices; this is a "v521". Installer Error (Status 7)
Flashed to an older version of TWRP for the v521 and that worked. Thoughts?
Click to expand...
Click to collapse
What zip were you trying to flash? im guessing the first half of your error said "this package is meant for b3 devices..." or something along those lines. Im pretty sure the shabbypenguin 3.0.2.0 is b3 based, so it was generic or compatible with v521, v525 etc. . this is v521 only. I assume whatever zip you were trying to install only had the b3 assert. Most have "b3, v521" asserts in the update-script.
That error usually comes up when the recovery checks the assert in the zip you're installing, against the recovery default.prop and the v521 assert wasn't found in the zip package. So it failed because the recovery read the zip as being for another device.
Could also be your bootloader is outdated.

HighRidas said:
What zip were you trying to flash? im guessing the first half of your error said "this package is meant for b3 devices..." or something along those lines. Im pretty sure the shabbypenguin 3.0.2.0 is b3 based, so it was generic or compatible with v521, v525 etc. . this is v521 only. I assume whatever zip you were trying to install only had the b3 assert. Most have "b3, v521" asserts in the update-script.
That error usually comes up when the recovery checks the assert in the zip you're installing, against the recovery default.prop and the v521 assert wasn't found in the zip package. So it failed because the recovery read the zip as being for another device.
Could also be your bootloader is outdated.
Click to expand...
Click to collapse
This started with my LTE is being slow like snail on LineageOS. Baseband wasn't showing up on status (showing unknown) so I was going to try to flash/upgrade the modem to see if that does anything. Would drop into TWRP and flash but would get that error saying this was made for a "B3" not a "V521".
So I decided to go back to stock and flash with this :
https://forum.xda-developers.com/lg-g-pad-83/development/rom-lg-stock-nougat-t3561088
But even that came up with the same errors So I downgrade to shabbypenguin's TWRP and then I was able to flash those packages. Went back to LG STOCK and tried the modem zips but to my original issue, still getting SLOW LTE speeds. Maybe my radios are kaput? APN looks correct comparatively to other US Tmobile APN settings.
You said it could be the bootloader. Wouldn't going back to stock (link above) or even flashing latest LineageOS or RR update it to the latest bootloader?

HighRidas said:
if you just rooted the device you're going to have to wipe data in twrp before it will be mountable
Click to expand...
Click to collapse
I'm in the same boat like the other guy was, every time time I try to wipe data through twrp it fails.. How am I supposed to wipe it?

@HighRidas twrp 3.2 is released, fyi

Does this support encryption if I encrypt with Lineage? I'm hearing some issues with TWRP in general with encrypted Nougat devices.

Has anyone flashed this successfully? I'm having "remote: unknown command" errors.
to prove that I already successfully unlocked the bootloader:
fastboot getvar unlocked
Code:
unlocked: yes
finished. total time: 0.002s
fastboot flash recovery TWRP-3.1.1-0_v521-recovery.img
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (16170 KB)...
OKAY [ 0.510s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.511s
Any ideas? I'd appreciate any assistance.

mattlach said:
Has anyone flashed this successfully? I'm having "remote: unknown command" errors.
to prove that I already successfully unlocked the bootloader:
fastboot getvar unlocked
Code:
unlocked: yes
finished. total time: 0.002s
fastboot flash recovery TWRP-3.1.1-0_v521-recovery.img
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (16170 KB)...
OKAY [ 0.510s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.511s
Any ideas? I'd appreciate any assistance.
Click to expand...
Click to collapse
Must be done on 20f with dirty cow. https://forum.xda-developers.com/g-pad-x-80/how-to/nougat-7-0-v521-guide-to-update-v521-lg-t3533338

Airtioteclint said:
Must be done on 20f with dirty cow. https://forum.xda-developers.com/g-pad-x-80/how-to/nougat-7-0-v521-guide-to-update-v521-lg-t3533338
Click to expand...
Click to collapse
Ah. Thank you.
Someone really ought to fix the LineageOS guide page for the v521
Now I just have to figure out how to downgrade to 20f without a Windows machine to run LGUP on. I tried in a VM with USB forwarding, but no dice. The USB debugging authorization gets confused when it connects to the host and then the VM...

Encryption does NOT work but I think this is Lineage problem or the device doesn't support it.
When a LineageOS update comes out, and it reboots to recovery, the recovery doesn't install anything. Is this the recovery's fault or LineageOS' fault?
I also have to run this every upgrade (TWRP loop): dd if=/dev/zero of=/dev/block/platform/soc.0/7824900.sdhci/by-name/misc count=1 bs=32

c0080900v said:
I'm in the same boat like the other guy was, every time time I try to wipe data through twrp it fails.. How am I supposed to wipe it?
Click to expand...
Click to collapse
Same here, I go to "Wipe" and swipe and I get various "failed to mount" errors.

cookiemonster79 said:
Same here, I go to "Wipe" and swipe and I get various "failed to mount" errors.
Click to expand...
Click to collapse
You will need to format data on the wipe tab which will remove encryption and delete anything installed but will allow storage to mount.
Sent from my LG-V521 using Tapatalk

Anyone tried to flash Magisk?

I really want to install Magisk, I need to change that green accent color and install some modules

https://forum.xda-developers.com/one-vision/help/magisk-motorola-one-vision-t3938161

Amaterasus said:
https://forum.xda-developers.com/one-vision/help/magisk-motorola-one-vision-t3938161
Click to expand...
Click to collapse
Good morning,
After reading the thread you indicate ...
I think I understand that, it is not possible to root, there is no TWRP, much less Xposed.
Is that so?
Regards
Enviado desde mi unknown mediante Tapatalk

gonzo1963 said:
Good morning,
After reading the thread you indicate ...
I think I understand that, it is not possible to root, there is no TWRP, much less Xposed.
Is that so?
Regards
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
Good morning,
Can anyone answer/help me?
Regards
Enviado desde mi unknown mediante Tapatalk

gonzo1963 said:
Good morning,
Can anyone answer/help me?
Regards
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
Yes mate . At this moment There is not root or twrp for our device yet

AndresOrue said:
Yes mate . At this moment There is not root or twrp for our device yet
Click to expand...
Click to collapse
Good morning,
Thanks for the information. We will continue waiting to be able to have full control of this magnificent smartphone.
Hopefully it will be shortly.
Regards
Enviado desde mi unknown mediante Tapatalk

It has been quite a while and no tutorial to root yet . I dont wanna any new future updates, just root without factory reset... Do you know some option?

gonzo1963 said:
Good morning,
Thanks for the information. We will continue waiting to be able to have full control of this magnificent smartphone.
Hopefully it will be shortly.
Regards
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
Are you guys actually joking? Flash a full firmware from lolinet, then boot and patch the boot image with magisk manager. Once ur done reboot to adb flash and enjoy. Seriously just learn basic steps of how to use a phone.

borksek said:
Are you guys actually joking? Flash a full firmware from lolinet, then boot and patch the boot image with magisk manager. Once ur done reboot to adb flash and enjoy. Seriously just learn basic steps of how to use a phone.
Click to expand...
Click to collapse
sorry to bother you. Can you share your knowledge with the normal people. What did you mean with reboot to adb and flash?

borksek said:
Are you guys actually joking? Flash a full firmware from lolinet, then boot and patch the boot image with magisk manager. Once ur done reboot to adb flash and enjoy. Seriously just learn basic steps of how to use a phone.
Click to expand...
Click to collapse
This metod is not working. oem unlocked.
flashing magisk boot.img-error(no such device)
flashing stock.img everything ok
if you know how to make it working i will be happy 2 hear that

ᕙ(⇀‸↼)ᕗ said:
This metod is not working. oem unlocked.
flashing magisk boot.img-error(no such device)
flashing stock.img everything ok
if you know how to make it working i will be happy 2 hear that
Click to expand...
Click to collapse
I think there is a twrp that is being made in a telegram group. It's super buggy for now but the phone might get twrp

Great, thanks if you give me a link i would try it

Short summary of what I've tried.
Flash magisk patched boot. Both stable and canary.
C:\ADB>fastboot flash boot_a boot.img
target reported max download size of 535822336 bytes
sending 'boot_a' (33792 KB)...
OKAY [ 0.895s]
writing 'boot_a'...
FAILED (status read failed (Too many links))
finished. total time: 0.926s
The phone reboots to fastboot by itself after.
Boot twrp test build.
C:\ADB>fastboot boot twrp-kane.img
downloading 'boot.img'...
OKAY [ 1.590s]
booting...
FAILED (remote failure)
finished. total time: 1.753s
In bootloader log is says: Validation image failed.
I've also tried these things after flashing vbmeta with:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flashing vbmeta with these commands always results in both slots being unbootable for me.
{
"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"
}

Hey, can u share with us this telegram group ?? Im waiting for the root solution.
Regards.