Related
I hope some has an answer to this.
1) I was on 2.3.3, rooted, and had made a complete Nanroid backup (boot.img, data.img, cache.img, nandroid.md5, recovery.img, system.img)
This was for:
Baseband: M200KRKB3
Build: GRI54
2) I manually updated to 2.3.4 and somehow lost root and CWM.
3) Due to a hardware issue (the headphone jack seems to have a loose
connection) I have to get back to 2.3.3 with the same Baseband so I can
go get the phone serviced. Since 2.3.4 was not provisioned here yet they
will reject servicing the phone under warranty.
My question: How can I do this?
I have tried to fastboot flash the files but that did not work.
I appreciate any suggestions. Thanks.
Did you upgrade from 2.3.3 to 2.3.4 successfully?
looks like I got same version than yours, but I can't upgrade successfully, I got error when I try to upgrade by Full ROM
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
if you did it, could you please let me know how I can upgrade my phone?
Thanks
adam22030 said:
I hope some has an answer to this.
1) I was on 2.3.3, rooted, and had made a complete Nanroid backup (boot.img, data.img, cache.img, nandroid.md5, recovery.img, system.img)
This was for:
Baseband: M200KRKB3
Build: GRI54
2) I manually updated to 2.3.4 and somehow lost root and CWM.
3) Due to a hardware issue (the headphone jack seems to have a loose
connection) I have to get back to 2.3.3 with the same Baseband so I can
go get the phone serviced. Since 2.3.4 was not provisioned here yet they
will reject servicing the phone under warranty.
My question: How can I do this?
I have tried to fastboot flash the files but that did not work.
I appreciate any suggestions. Thanks.
Click to expand...
Click to collapse
did you reflash the CWM recovery with fastboot?
what is the error?
with CWM recovery you should be able to nandroid restore ur backup!
After doing: fastboot flash recovery recovery.img
I get this:
sending 'recovery' (8192 KB)...
OKAY [ 2.313s]
writing 'recovery'...
FAILED (remote: Write Fail)
finished. total time: 2.328s
On the bootloader screen it says: Exceed blocks 0x000000020 > 0x00000001e
I might have too many 0's in there but I think you get the point.
Suggestions? Am I missing something?
adam22030 said:
After doing: fastboot flash recovery recovery.img
I get this:
sending 'recovery' (8192 KB)...
OKAY [ 2.313s]
writing 'recovery'...
FAILED (remote: Write Fail)
finished. total time: 2.328s
On the bootloader screen it says: Exceed blocks 0x000000020 > 0x00000001e
I might have too many 0's in there but I think you get the point.
Suggestions? Am I missing something?
Click to expand...
Click to collapse
hmm.. which nexus s type is that? I9023 oder I9020?
there are different CWM versions, do u use the correct one?
is ur fon still unlocked?
It is I9020 (but Korean version) and I actually forget which CWM I had used.
Phone is unlocked.
check out which u have.. there is a I9020T and I9020A i think.. (should be written beneath the battery)
then maybe download the CWM img file again, from one of the both guides in the stickies corresponding to those two models.
maybe u have a wrong version..
i didn't have problems flashing CWM after going to 2.3.4. (tho i have a I9023).
Ok I will try that...and let you know...
OK - almost there.
I got the restore done - BUT the baseband is still at xxKD1
I have the M200KRKB3 radio.img - how can I apply that?
that should be
Code:
fastboot flash radio M200KRKB3 radio.img
don't know if that's how ur radio image is named, just insert the name of ur file
Nope...that didnt work..
error: cannot load 'M200KRKB3'
adam22030 said:
Nope...that didnt work..
error: cannot load 'M200KRKB3'
Click to expand...
Click to collapse
what is the file named, M200KRKB3 radio.img? or M200KRKB3_radio.img with underscore?
if it doesn't have an underscore, maybe it can't find the file.. dunno :/
Yea - I figured that out
All done! And thank you so much for your advice and help! Really appreciate it.
no problem, glad to help
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?
Anyone having trouble flashing to the 4.2.2 Camera update? I am using HouseOfMoto and getting an error when it tries to write the system update.
The phone tells me in the Flashboot screen "Invalid PIV image: system"
The HoM tool tells me "sending 'system' (262144 KB)... OKAY [ 22.653s] writing 'system'... INFOPreflash validation failed FAILED (remote failure)"
> I have tried all flashing methods available in HoM (RSD Flash and OMAP)
> I have tried both Full and Keep Data in HoM
> I have d/l the 4.2.2 update from multiple sources.
> I have successfully done RMM (I have root) and MWMN (I have '0' which means write protection is off).
> I have successfully used HoM before to get to the 15.15 4.2.2 update
> I just went back to the 15.15 using HoM and system writes fine
> I feel I understand the correct steps and understand the goal of each step
Thanks in advance for any help!
---
SOLVED: Was using wrong FXZ file.
Khanusma said:
Anyone having trouble flashing to the 4.2.2 Camera update? I am using HouseOfMoto and getting an error when it tries to write the system update.
The phone tells me in the Flashboot screen "Invalid PIV image: system"
The HoM tool tells me "sending 'system' (262144 KB)... OKAY [ 22.653s] writing 'system'... INFOPreflash validation failed FAILED (remote failure)"
> I have tried all flashing methods available in HoM (RSD Flash and OMAP)
> I have tried both Full and Keep Data in HoM
> I have d/l the 4.2.2 update from multiple sources.
> I have successfully done RMM (I have root) and MWMN (I have '0' which means write protection is off).
> I have successfully used HoM before to get to the 15.15 4.2.2 update
> I just went back to the 15.15 using HoM and system writes fine
> I feel I understand the correct steps and understand the goal of each step
Thanks in advance for any help!
Click to expand...
Click to collapse
I'm confused are you trying to update or run fxz. HoM doesn't use update it uses fxz file.
bigv5150 said:
I'm confused are you trying to update or run fxz. HoM doesn't use update it uses fxz file.
Click to expand...
Click to collapse
Use the fxz. I successfully used the 15.15 fxz.
Did i d/l an update file and not an fxz file? The file I have runs in HoM but gives the error.
Sent from my XT1080 using Tapatalk
Hi,
I'm preparing to do the root update on my phone prior to taking the Kitkat update. I've read through the [4.4 ROOT] SlapMyMoto 1.0 (Requires you to be on 4.2.2) thread once. I'm still a little fuzzy, so I'm trying to read through some of the previous threads, but reading this led me to a question. I've seen multiple references to fxz and using that to restore to a previous version. Is this a utility of some sort like ADB? If so, where can I get it?
thx.
Slarti77 said:
Hi,
I'm preparing to do the root update on my phone prior to taking the Kitkat update. I've read through the [4.4 ROOT] SlapMyMoto 1.0 (Requires you to be on 4.2.2) thread once. I'm still a little fuzzy, so I'm trying to read through some of the previous threads, but reading this led me to a question. I've seen multiple references to fxz and using that to restore to a previous version. Is this a utility of some sort like ADB? If so, where can I get it?
thx.
Click to expand...
Click to collapse
Its called HouseOfMoto. There is a thread on xda for it specifically.
Khanusma said:
Its called HouseOfMoto. There is a thread on xda for it specifically.
Click to expand...
Click to collapse
Thanks Khanusma,
I'll read that thread next. I know that the root from 4.2.2 to 4.4 mentions a few tools you have to use to prep before you do SlapmyMoto. I just didn't realize that fxz was part of HouseOfMoto.
Slarti77 said:
Thanks Khanusma,
I'll read that thread next. I know that the root from 4.2.2 to 4.4 mentions a few tools you have to use to prep before you do SlapmyMoto. I just didn't realize that fxz was part of HouseOfMoto.
Click to expand...
Click to collapse
To get to 4.4 you have to turn write protect off and then get on the 4.2.2 Camera update (which will take away root if you have it) and then you can SlapMyMoto (which will place a back door on your 4.2.2 which can be exploited after you get on 4.4). I was trying to do that but I cant get the 4.2.2 Camera Update FXZ to work.
Slarti77 said:
Thanks Khanusma,
I'll read that thread next. I know that the root from 4.2.2 to 4.4 mentions a few tools you have to use to prep before you do SlapmyMoto. I just didn't realize that fxz was part of HouseOfMoto.
Click to expand...
Click to collapse
Can you let me know the 4.2.2 update file you are flashing? I may be using the wrong one .
The firmware just jumped to LRX21V. Installing this now and hoping for more goodness.
Don't Flash LRX21V
UGH. Bad idea. The flashing threw all sorts of errors about "status read failed (Too many links)" and I'm reverting to the previous firmware. Between this and the issues on the other Nexuses with flashing I'm really disappointed with Google. Even this reflash isn't looking good.
IskiE
I updated just now. Seems fine. Was hoping it would fix my HDCP problems, but no luck.
i have two players. my second one came in last night (monday).
out of the box it updated. no issues at all with that. the other one did not get the update yet.
I was able to reflash back to "M". I had to leave it running overnight as the reformat of the system partition that it was doing was taking a long time. It didn't offer the "V" update. It may be just the factory images that have issues - OTAS updates may be good.
I flashed from M to V (factory image) with no issues whatsoever.
Code:
C:\Android\devices\fugu\fugu-lrx21v>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (12167 KB)...
OKAY [ 1.477s]
writing 'bootloader'...
OKAY [ 4.194s]
finished. total time: 5.675s
rebooting into bootloader...
OKAY [ 0.600s]
finished. total time: 0.601s
< waiting for device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
--------------------------------------------
Bootloader Version...: FUGU-02.05
Baseband Version.....: N/A
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.591s]
checking version-bootloader...
OKAY [ 0.591s]
sending 'boot' (5406 KB)...
OKAY [ 1.347s]
writing 'boot'...
OKAY [ 1.331s]
sending 'recovery' (6058 KB)...
OKAY [ 1.329s]
writing 'recovery'...
OKAY [ 1.317s]
erasing 'system'...
OKAY [ 1.458s]
sending sparse 'system' (521954 KB)...
OKAY [ 15.101s]
writing 'system'...
OKAY [ 9.090s]
sending sparse 'system' (431032 KB)...
OKAY [ 12.105s]
writing 'system'...
OKAY [ 7.374s]
rebooting...
finished. total time: 54.637s
Press any key to exit...
I did remove the wipe switch (-w) from the flash-all.bat. But it was wiped when I unlocked.
Does this latest update resolve any known issues?
Luxferro said:
I flashed from M to V (factory image) with no issues whatsoever..
Click to expand...
Click to collapse
I managed to get the update over to my Player this evening. I had flashed the bootloader in the zip and that was causing issues. Even so, I couldn't simply flash the zip - I had to walk the 3 images over one by one. The system.img took a little convincing a few tries.
Long story short I have the "V" version installed now.
IskiE
Benjamin06 said:
Does this latest update resolve any known issues?
Click to expand...
Click to collapse
BUMP
I'd also like to know what's new in the new build
THE_KINGDOM said:
BUMP
I'd also like to know what's new in the new build
Click to expand...
Click to collapse
http://aosp.changelog.to/aosp-LRX21T-LRX21V.html
Courtesy of Android Police. http://www.androidpolice.com/2014/1...uild-from-5-0-0_r2-lrx21m-to-5-0-0_r5-lrx21q/
I personally had no issues with the upgrade. Looks/feels the same to me, must be back-end stuff.
I still haven't received the OTA update for the latest build...??
Mine hasn't updated to V yet
Can the unlocked boot loader be causing the OTA not to be pushed ?
Sent from my Nexus 6 using XDA Premium HD app
ktownhero said:
I personally had no issues with the upgrade. Looks/feels the same to me, must be back-end stuff.
Click to expand...
Click to collapse
Had you unlocked your bootloader before upgrading? I'm wondering how I can get the upgrade to be seen, but it's not happening...perhaps I'm just not in the update batch yet.
Just got the OTA tonight
I'm on 21V now
Fixed the wireless drop outs
Sent from my Nexus 6 using XDA Premium HD app
My update downloaded and tried to install then said install failed, now it won't let me re-download it. I'm unlocked and rooted, I wonder if that is the problem?
Stud22 said:
My update downloaded and tried to install then said install failed, now it won't let me re-download it. I'm unlocked and rooted, I wonder if that is the problem?
Click to expand...
Click to collapse
Unlocked no. Rooted, yes.
Stud22 said:
My update downloaded and tried to install then said install failed, now it won't let me re-download it. I'm unlocked and rooted, I wonder if that is the problem?
Click to expand...
Click to collapse
You should be able to use the installed Super SU to un-root your player. Start the app and hit the menu to do so... I haven't attempted this on the NP yet, but it works on many other devices.
Alternatively, you could flash only the system.img from the factory images using fastboot then re-root after the update. For most people, simply un-rooting, installing the over-the-air update then re-rooting would be the better option.
Good luck.
Anyone know how to unroot it, I tried the multi-tool thing but I couldn't get it to work
Sent from my LG-D800 using Tapatalk
You'll need to download the factory imagine and flash it using adb commands.
Download the factory image from https://developers.google.com/android/nexus/images
At the top of the page are the instructions to flash.
This is the reason I haven't rooted. Waiting for a custom recovery so that we can do proper backups and restores without wiping the unit.
[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.