[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.
Related
Has anyone tried to downgrade 4.4.2 to 4.3, there are problems?
LeonelRdz09 said:
Has anyone tried to downgrade 4.4.2 to 4.3, there are problems?
Click to expand...
Click to collapse
I've downgraded twice, no problems here. As long as you do it right, you should be perfectly fine :good::good::silly:
How???
SamsungAdmire said:
I've downgraded twice, no problems here. As long as you do it right, you should be perfectly fine :good::good::silly:
Click to expand...
Click to collapse
Hello, could you please tell me how you downgrade? I'm not a fan or not having WiFi!
awooga1123 said:
Hello, could you please tell me how you downgrade? I'm not a fan or not having WiFi!
Click to expand...
Click to collapse
I follow this guide to flash 4.2.2 and my WIFI works perfectly!
http://forum.xda-developers.com/showthread.php?t=2585242
when i downgraded from the repacked 4.4.2 my wifi stoped working.. there is no way to get it work again except to install the repacked 4.4.2 again
Sent from my XT1032 using XDA Premium 4 mobile app
makcode said:
when i downgraded from the repacked 4.4.2 my wifi stoped working.. there is no way to get it work again except to install the repacked 4.4.2 again
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Could it be that the 4.4.2 radio is not compatible with a rom that is 4.3 or lower?
audit13 said:
Could it be that the 4.4.2 radio is not compatible with a rom that is 4.3 or lower?
Click to expand...
Click to collapse
I doubt it. I've just downgraded from 4.4.2 last night again and everything works perfect. Weird..
SamsungAdmire said:
I doubt it. I've just downgraded from 4.4.2 last night again and everything works perfect. Weird..
Click to expand...
Click to collapse
I suggested that because 4.4.2 needs the latest radio to work properly.
audit13 said:
Could it be that the 4.4.2 radio is not compatible with a rom that is 4.3 or lower?
Click to expand...
Click to collapse
i downgraded also the modem firmware. (./flashall.sh; and manual flash with ./mfastboot....)
i tried the DE UK US retail 4.3 official stock images. but no luck.
i think the repacked firmware had something changed in the partition with some wlan settings.. maybe some drivers i don't know..??
Sent from my XT1032 using XDA Premium 4 mobile app
Ok i solved my problem. Maybe it can help my solution to someone who have the same problem: I don't know why but my /persist/ folder was empty.. i had to diskdump the block of persist from my other moto g and copyed it on my briked one. then i had to edit the two bin files for bluetooth and wifi to set back the real MAC Adress (write down from the retail box)
now it works again without any problems.
Sent from my XT1032 using XDA Premium 4 mobile app
All im getting is "version downgraded for primary-gpt"
SamsungAdmire said:
I've downgraded twice, no problems here. As long as you do it right, you should be perfectly fine :good::good::silly:
Click to expand...
Click to collapse
Could you tell me HOW did you downgrade? Id like to go back to my Retail UK 4.3 ... now Im on XT1032 using US 4.4.2 ... I can flash US 4.3, thats no problem ... but when I try to flash back my original Retail UK 4.3 it says this:
Code:
d:\SORT\MotoG\STOCK_Retail_UK_4.3>flashall.bat
Motorola Mobility flashall script version 1.4
Flashing Options:
- flash persist: 0
- flash userdata: 0
- erase userdata: 0
- erase cache: 0
Waiting for fastboot enumeration...
Fastboot device is ready!!
Flashing GPT and bootloader images...
Executing ".\Windows\fastboot.exe flash partition gpt.bi
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.089s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.547s
.\Windows\fastboot.exe flash partition gpt.bin failed!!
ryanraven said:
All im getting is "version downgraded for primary-gpt"
Click to expand...
Click to collapse
michalurban said:
Could you tell me HOW did you downgrade? Id like to go back to my Retail UK 4.3 ... now Im on XT1032 using US 4.4.2 ... I can flash US 4.3, thats no problem ... but when I try to flash back my original Retail UK 4.3 it says this:
Code:
d:\SORT\MotoG\STOCK_Retail_UK_4.3>flashall.bat
Motorola Mobility flashall script version 1.4
Flashing Options:
- flash persist: 0
- flash userdata: 0
- erase userdata: 0
- erase cache: 0
Waiting for fastboot enumeration...
Fastboot device is ready!!
Flashing GPT and bootloader images...
Executing ".\Windows\fastboot.exe flash partition gpt.bi
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.089s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.547s
.\Windows\fastboot.exe flash partition gpt.bin failed!!
Click to expand...
Click to collapse
i followed this guide:
http://forum.xda-developers.com/showthread.php?t=2542219
the primary gpt downgrade thing is normal. the first time i saw it i freaked out but still went on with it risking it.
After i did the instructions correctly, it booted up into 4.3 normally
By "went on" you mean you entered the commands manually? Because this script I wrote about before sure wont let me continue ...
michalurban said:
By "went on" you mean you entered the commands manually? Because this script I wrote about before sure wont let me continue ...
Click to expand...
Click to collapse
yup, it probably takes some 2 minutes just to put them in. Works perfect for me. :laugh:
SamsungAdmire said:
yup, it probably takes some 2 minutes just to put them in. Works perfect for me. :laugh:
Click to expand...
Click to collapse
Ok, phone seems to be running fine even with those errors (preflash validation failed + some failed signature check). Lets hope its not doing any trouble in the future ... Thanks for your assistance!
BTW what about you and kitkat (lol)? I find it sluggish and charging is slower - so I rooted and disabled the OTA upgrade ...
michalurban said:
Ok, phone seems to be running fine even with those errors (preflash validation failed + some failed signature check). Lets hope its not doing any trouble in the future ... Thanks for your assistance!
BTW what about you and kitkat (lol)? I find it sluggish and charging is slower - so I rooted and disabled the OTA upgrade ...
Click to expand...
Click to collapse
I sort of missed the blueness of 4.3 and browsers on 4.4 were annoying me since Google switched the default browser engine to chromium's engine. Then i saw some screenshots i accidently took from kitkat and missed the nice transparent bars and white icons, and now i'm sticking with kitkat.
hi guys i need help if possible my moto g is stuck on the blue m logo after the boot animation its not a boot loop just stuck on the m. i reflashed the firmware again but no change i havent erased cache and userdata is that the reason?
thanks guys in advance
erased cache and userdata after the downgrade abd it boots normal.
your downgrading lol you MUST delete the userdata and cache or you'll be forever bootloop
SamsungAdmire said:
i followed this guide:
http://forum.xda-developers.com/showthread.php?t=2542219
the primary gpt downgrade thing is normal. the first time i saw it i freaked out but still went on with it risking it.
After i did the instructions correctly, it booted up into 4.3 normally
Click to expand...
Click to collapse
can you post the edited script for the downgrade?
Q&A for [ROM] CM 11.0 (Android 4.4) for RazrHD XT925/XT926
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Is this the ROM for the XT926 from Dhacker? Sorry for a noob type question, but sometimes the ROMS have 926 in the file name which makes it easier for guys like me to know I am getting the right one.
androidhosting.org/Devs/Dhacker29/cm-11-20140207-UNOFFICIAL-vanquish.zip
Poor call quality
Has anyone else had the issue where there is poor audio quality in the earpiece? The audio is all crackly and fuzzy, and makes it very hard to understand. I'm not sure if it's hardware or software related right now, and am trying to find out. Another issue which I've had for the past couple months is that the maximum speakerphone volume is SUPER low, much lower than equivalent speaker volume for a youtube video or something. Might this be related (for example, the earpiece volume, which can now go to a deafeningly high level is actually using the gain meant for the speaker and vice versa (resulting in clipping of the signal going to the earpiece, and poor quality)?
Stuck in a boot loop between Motorola boot animation and CWM Recovery menu
Hi guys, Im looking for some help.
I'm a Razr HD (XT925) owner, unlocked bootloader, rooted and CWM 6.0.4.4.
I was running the latest CM 11 KK4.4.2 nightly. Lately it was a bit unstable (freezing and rebooting...sometimes stuck into the CM animation). Due to that I decided to give Epinter's [ROM] CM 11.0 (Android 4.4) for RazrHD XT925/XT926 a try.
Everything ran smoothly, without any sort of error but after the reboot, it got stuck into a loop between the Motorola boot animation, which keeps on my screen for approximately 30 secs, after that the screen turns black, the same Motorola boot animation pops up again, this time for a bit short time and finally, it brings me to the CWM Recovery menu.
I've tried to restore my CM11 KK4.4.2 image but it quickly shows me a message saying
"Checking MD5 sums...
MD5 Mismatch!"
Another strange facts:
After performing the wipe data/factory reset there are the following messages:
(Please note that Bold/Italic ones seemed sorta strange for me...maybe just because I'm being a noob though!)
"__Wiping data...
Formatting /data...
Formatting /cache...
Formatting /SD-ext...
Formatting /sdcard/.android_secure...
E:unknown volume "/sdcard.android_secure"
Data wipe complete"
E:unknown volume for path [/sd-exit]
MD5 checksum mismatch"
While trying to wipe Delvik cache the following message pops up:
"E:unknown volume for path [/sd-ext]"
So, atm, as you can imagine, my cell phone is sorta useless!
Can anyone help me?!?
Thank you in advance for your time and attention!
Cheers!
Edit 1: I've performed Wipe data/Factory reset, Wipe cache partition and Wipe Delvik cache before applying the Epinter's .zip and ggapps from my SD card. I did the same right before Epinter's .zip and ggapps both got installed without any sort of error message. I've did the same several times after the problem starts as well. In my last attempt of solving it by myself, I've repeated it all again since the the 1st step...all wipes and reinstalling both Epinter's and ggapps!
Edit 2:
I've managed to install from CWM an old .zip I found on my storage and my cell phone came back to life in the very same state it was!
Now, I was reviewing each step in order to try to install Epinter's CM11 KK4.4.4 and I've seen he wrote the following:
Recent versions (July/2014) requires an updated (KitKat) bootloader
After that, a doubt came to my mind...Could it be the cause of this mess I was stuck into? Is my unlocked bootloader JB or KK? How can I know it?!? If it is JB, how can I change it to KK?
If you don't updated to official KK you still on jbbl (Jelly Bean Bootloader)... So install latest snapshot (M11) or latest nightly from here: http://download.cyanogenmod.org/?device=moto_msm8960_jbbl instead epinter's old builds
Thanks and a heads up
DorianX said:
If you don't updated to official KK you still on jbbl (Jelly Bean Bootloader)... So install latest snapshot (M11) or latest nightly from here: (Ive had to delete the link because of my low number of posts) instead epinter's old builds
Click to expand...
Click to collapse
Thanks a lot bro!
Well, in this case I'm pretty sure I'm running a JBBL then!
Believe it or not, after several wipe data/cache it is running...with some freeze outs and restartings more often than Id like but still...its running!
The link for the latest JBBL build is kinda broken (After choosing the latest build, it brings me to a 404 not found error page).
Thanks again and Ill come back in a few days when the link to the latest JBBL is working! As for the compatible GAAPS for the latest JBBL build...the same one Ive used alongside with Epinter's should be ok?!?
Cheers!
Yep CyanogenMod servers are having problems since yesterday... Try later, about gapps use a newer ones maybe from here:
http://forum.xda-developers.com/showthread.php?t=2779598
Or here:
http://forum.xda-developers.com/showthread.php?t=2397942
Thanks again and...
DorianX said:
Yep CyanogenMod servers are having problems since yesterday... Try later, about gapps use a newer ones maybe from here:
(Links not allowed yet for me)
Or here:
(Links not allowed yet for me)
Click to expand...
Click to collapse
Thanks again!
Taking as true the assumption that from now on the vast majority of ROMs to come will be made to be used on KKBL, wouldn't it be worth to upgrade to a KKBL now? Would it be too complicated since I'm not sure what was my default cell phone OS since I'm the 2nd owner and I've bought it from an ebay like site here at Brazil! Any tutorial links?
Cheers again!
What is gcm services and is it safe to force close it? It's eating my battery.
[XT925] Stock ROM with KK BL to install CM11
Hi all!
Im looking a ROM to install in my RAZR HD with the KK Bootloader, needed for flash CM11 moto_msm8960 builds
Does anybody knows which ROM comes with that bootloader? Is posible to upgrade bootloader using a jb rom?
Thanks!
cristian04 said:
Hi all!
Im looking a ROM to install in my RAZR HD with the KK Bootloader, needed for flash CM11 moto_msm8960 builds
Does anybody knows which ROM comes with that bootloader? Is posible to upgrade bootloader using a jb rom?
Thanks!
Click to expand...
Click to collapse
As it has been widely discussed multiple times on multiple threads on all the msm8960 device pages, if your device has not been given the official Moto Kitkat, or if you have not taken the official Moto kitkat update, you will use the moto_msm8960_jbbl builds. If your device has been updated to the official Moto Kitkat, you will use the moto_msm8960 builds.
All bootloaders come from Moto, not CM or another third party ROM developer, so no it is not possible to upgrade or downgrade your bootloader with a custom ROM. You can only do this using the sbfs and the guides here on xda.
Sent from my ATRIX HD using XDA Free mobile app
Camera not initialise
Hey i tried the copy/paste method( placing the files in system/app), But then i'm getting the error "Camera not initialize". Can anybody help me, it will be Thankful...
As of late I'm experiencing problems with the Wifi tethering dropping my service. I've been running CM11 for awhile now with no major issues until recently
The problem I'm having is once I enable wifi tethering, hotspot becomes active and all is well. As soon as I connect a device to that network, my phone drops service. This will happen repeatedly. Every once in awhile the service will hold but it's only a matter of time before it drops again. This problem gradually became worse over time until it happens everytime.
Anyone experiencing this issue? I was hoping it was an issue with my current 20140609-SNAPSHOT but I just updated to cm-11-20141008-SNAPSHOT-M11-moto_msm8960_jbbl and still receiving the same problems.
expired link
Hi
it seems the download link for epinter roms is temporary (hope so) dead
"This Domain Name Has Expired"
But I do no read this thread very often; may be I have did'nt read something about this fact
Kind regards,
Serge
Kbbl problem
Dear developer i own two razr hd's (xt925) both currently running stock kitkat uk build ota.when i install any kkbl rom i get E: Error executing updater binary in zip '/external_SD/roms/cm-11-20141008-SNAPSHOT-M11-moto_msm8960.zip'.
I have tried 6 of your builds and some pa too on both devices I have also tried it on twrp 2.8.1.0,2.8.0.0,2.7.0.0 and Phil adv cwm,cwm 6.0.3? . The problem is probably something wrong with my razr hd but I really need to know what it is . Please could you help PS I have downgraded to jb and the jbbl is working fine but a bit slow sometimes.(EDIT)
Fixed by editing update script. Changed ro.boot.secure_hardware from 1 to 0
Wondering if anyone can help me. I've spent all night trying multiple ways to get this to work but it keeps on failing:
I have already unlocked my bootloader. However whenever I try to install CWM I get the following:
G:\PROGRA~1\Android\android-sdk\platform-tools>fastboot flash recovery cwm.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (10146 KB)...
OKAY [ 0.774s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.913s
----------------------------------------------------------
FASTBOOT SHOWS:
AP Fastboot Flash Mode (S)
10.9b(*) (sha-07671a2, 2014-10-15 04:59:29)
eMMC Info: Size 16GB
Device is UNLOCKED, Status Code: 3
----------------------------------------------------------
Current Recovery Shows:
Android system recovery <3e>
KDA20.117-3
---------------------------------------------------------
After trying all night Im beyond frustrated now. Ive tried doing data wipe as well as cache partition wipe as well with no success, so I hope someone can tell me what im doing wrong. Prior to this I was already on the most recent OTA update from Fido Canada (4.4.2?) however this morning when I woke up it wouldn't turn on, when I finally got it to reboot it was stuck on NON-Animated Batwings logo.
Thanks in advance.
Wizard1Canada said:
Wondering if anyone can help me. I've spent all night trying multiple ways to get this to work but it keeps on failing:
I have already unlocked my bootloader. However whenever I try to install CWM I get the following:
G:\PROGRA~1\Android\android-sdk\platform-tools>fastboot flash recovery cwm.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (10146 KB)...
OKAY [ 0.774s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.913s
----------------------------------------------------------
FASTBOOT SHOWS:
AP Fastboot Flash Mode (S)
10.9b(*) (sha-07671a2, 2014-10-15 04:59:29)
eMMC Info: Size 16GB
Device is UNLOCKED, Status Code: 3
----------------------------------------------------------
Current Recovery Shows:
Android system recovery <3e>
KDA20.117-3
---------------------------------------------------------
After trying all night Im beyond frustrated now. Ive tried doing data wipe as well as cache partition wipe as well with no success, so I hope someone can tell me what im doing wrong. Prior to this I was already on the most recent OTA update from Fido Canada (4.4.2?) however this morning when I woke up it wouldn't turn on, when I finally got it to reboot it was stuck on NON-Animated Batwings logo.
Thanks in advance.
Click to expand...
Click to collapse
Boot into fastboot and type "fastboot getvar all" we need more info to help
Sent from my ATRIX HD using Tapatalk
---------- Post added at 09:41 AM ---------- Previous post was at 09:35 AM ----------
http://www.android.gs/install-twrp-recovery-on-motorola-razr-hd-xt925/
Sent from my ATRIX HD using Tapatalk
I think taking that ota might have made your device incapable of flashing the recovery ur trying.
Sent from my ATRIX HD using Tapatalk
G:\PROGRA~1\Android\android-sdk\platform-tools>fastboot getvar all
< waiting for device >
(bootloader) version-bootloader: 109B(*)
(bootloader) product: vanquish_u
(bootloader) secure: yes
(bootloader) mid: 0056
(bootloader) version: 0.5
(bootloader) serialno: TA24000XCM
(bootloader) qe: qe 0/1
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 31457280
(bootloader) emmc-size: 16GB
(bootloader) reason: Boot menu selected
(bootloader) revision-hardware: 0x8300
(bootloader) cpu: MSM8960 CS
(bootloader) uid: D42FFD0102000100000000000000
(bootloader) cid: 0x0e
all:
finished. total time: 0.083s
U should be able to flash a recovery since your BL is unlocked. What exploit did u use to unlock it? I know myth tools can help with most Motorola's.
Sent from my ATRIX HD using Tapatalk
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.
im having trouble reverting back to stock CM12 from OxygenOS, so im seeking help on XDA forums, Anyways, i keep getting this error. btw i cant insert photos since my post counts is not more than 10.
Code:
target reported max download size of 1073741824 bytes
sending 'modem' <57361 KB>. . .
FAILED <status read failed <Too many links>>
finished. total time: 2.259s
i know i could always put a CM12 flashable zip into my phone and flash it through recovery but the problem is my computer cant detect my internal storage, only fastboot mode. I can go to recovery and fastboot just fine, i can boot into the os but for some reason my OS doesnt have any status bar or nagivation bar. its like the system ui is gone.
Any tutorials on how to revert back to stock from OxygenOS? i looked on youtube but it didnt help since i always get that error.
Thanks.
VercettyEdits said:
im having trouble reverting back to stock CM12 from OxygenOS, so im seeking help on XDA forums, Anyways, i keep getting this error. btw i cant insert photos since my post counts is not more than 10.
Code:
target reported max download size of 1073741824 bytes
sending 'modem' <57361 KB>. . .
FAILED <status read failed <Too many links>>
finished. total time: 2.259s
i know i could always put a CM12 flashable zip into my phone and flash it through recovery but the problem is my computer cant detect my internal storage, only fastboot mode. I can go to recovery and fastboot just fine, i can boot into the os but for some reason my OS doesnt have any status bar or nagivation bar. its like the system ui is gone.
Any tutorials on how to revert back to stock from OxygenOS? i looked on youtube but it didnt help since i always get that error.
Thanks.
Click to expand...
Click to collapse
Go to my guide and follow section 8:
http://forum.xda-developers.com/showthread.php?t=2839471
Don't reboot between any of the commands though or you'll brick. The error you're getting is usually due to outdated adb/fastboot, so you need to update that first.
XDA Moderator
Transmitted via Bacon
Heisenberg said:
Go to my guide and follow section 8:
http://forum.xda-developers.com/showthread.php?t=2839471
Don't reboot between any of the commands though or you'll brick. The error you're getting is usually due to outdated adb/fastboot, so you need to update that first.
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
It Works. Thanks.
do you a guide for reverting to CM11S ?
rednit said:
do you a guide for reverting to CM11S ?
Click to expand...
Click to collapse
Go to my guide (it's linked above) and follow section 8, but instead of downloading the CM12S stock images just get the CM11S images instead. You'll find them all here:
http://forum.xda-developers.com/showthread.php?t=2906746
Thank you very much
I flashed my phone from CM12.1 to Oxygenos-2-1-4 today, but I don't like the oxygenos-2-1-4 mainly it does not have the feature of applying different Themes. My phone is not rooted.
I would like to know how to revert back to CM12.1
If you run into issues, make sure to flash aboot first and do a "fastboot reboot bootloader" to get booted into the stock bootloader (not the oxygenos one)
keep in mind, that the newest 2k1 factory image's cache.img and userdata_64G.img seem to be f2fs formatted, use those files from the JL image, if you want to flash any custom rom afterwards that doesn't fully support f2fs!
Gesendet von meinem A0001 mit Tapatalk
{
"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