Related
Hello, can someone help me convert my Moto G 2014 XT1064 (US) to the Google Play Edition?
I bought the Moto G on sale at Amazon a few days ago, then remembered why I had put off purchasing it previously, all of the Motorola bloatware!! No Motorola, I don't need an additional backup service, and I don't want your services constantly running and pinging home, and I'd like to get updates in a reasonable amount of time. My device said it was up to date but was still on KitKat, which was very disappointing.
So far I've unlocked my bootloader (via the official Motorola method) and I did successfully upgrade to Lollipop but it was the Motorola version.
These are the packages that I have downloaded:
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip (the motorola 5.0 update?)
Blur_Version.22.11.6.titan_retuaws.retuaws.en.US.zip (small update for motorola android 5)
GPE_XT1032_KOT49H.M004_CFC.xml.zip (stuck at Google screen with unlock icon, waited 30 minutes)
One issue is that it seems like both of the main sites that host the stock images have been down for a few days:
- http://sbf.droid-developers.org/phone.php?device=36 (DOWN as of 12/12)
- http://motofirmware.com/files/category/38-titan/ (DOWN as of 12/12)
I also used the MotoToolAioV3.1 with the GPE_XT1032_KOT49H ROM which resulted in a bootloop, I'm guessing this is for the 1st gen Moto G?
Right now I'm back on Motorola KitKat version 21.11.17.titan_retuaws.retuaws.en.US.
Is there a way to make my Moto G XT1064 stock GPE or should I look for a custom ROM that or should I try CyanogenMod 11?
One thing to note is that I was running on less that 50% battery when trying to flash GPE_XT1032_KOT49H with MotoToolAIO, could this have been an issue or is this only to prevent the battery from dying?
Thanks for the help guys!
P.S. It was not worth it saving $70 to get the on-sale version at Amazon rather than the Google Play Edition. I've not even been able to find out for sure if you can get the 2014 version with GPE, which makes this even more frustrating.
Also, which versions are compatible with each other or are none of them compatible unless stated? Will the 1st gen ROMs work on the 2nd gen phone?
there is no GPE edition for Moto G 2ND GEN.......... and 1st gen ROMS wont work in our phones.. flashing dem results results in a BOOTLOOP
ak88900 said:
there is no GPE edition for Moto G 2ND GEN.......... and 1st gen ROMS wont work in our phones.. flashing dem results results in a BOOTLOOP
Click to expand...
Click to collapse
Thanks, it's really disappointing that I can't have stock Android on a Moto G 2014 and have it somewhat easy to update. When is that going to change Google, come on, it's been the same ROM -> Bootloop -> flash -> brick -> hours of ADB and mfastboot for 5 or 6 years. Having 20 Motorola services phoning home and alerting me to signin to Motorola constantly is inexcusable, and makes this otherwise great phone a LEMON.
Is there a tool or method to strip out all of the Motorola junkware?
eeeee
derekm_ said:
Thanks, it's really disappointing that I can't have stock Android on a Moto G 2014 and have it somewhat easy to update. When is that going to change Google, come on, it's been the same ROM -> Bootloop -> flash -> brick -> hours of ADB and mfastboot for 5 or 6 years. Having 20 Motorola services phoning home and alerting me to signin to Motorola constantly is inexcusable, and makes this otherwise great phone a LEMON.
Is there a tool or method to strip out all of the Motorola junkware?
Edit: I don't understand, we have root, we have an unlocked bootloader, why can't this phone be 100% converted to a GPE phone? What's the technical limitation that's preventing this?
Click to expand...
Click to collapse
yeah all u gotta do is Root->install Titanium Backup->uninstall all unwanted bloatware
GPE---- well the gpe edition dosnt exist--
ak88900 said:
yeah all u gotta do is Root->install Titanium Backup->uninstall all unwanted bloatware
GPE---- well the gpe edition dosnt exist--
Click to expand...
Click to collapse
Oh, sweet, thank you so much!
It probably seems like a "duh" but this tip should be a sticky!
I never once have read somewhere that the Moto G 2014 doesn't have a Google Play Edition. Eventually I suspected that it didn't but only after an hour of flashing and bootloops.
So this is not the 2014 version? https://play.google.com/store/devices/details/Moto_G_Google_Play_edition_8GB?id=moto_g_8gb&hl=en Is the model number of the GPE phone I just linked to XT1032?
.
derekm_ said:
Oh, sweet, thank you so much!
It probably seems like a "duh" but this tip should be a sticky!
I never once have read somewhere that the Moto G 2014 doesn't have a Google Play Edition. Eventually I suspected that it didn't but only after an hour of flashing and bootloops.
So this is not the 2014 version? https://play.google.com/store/devices/details/Moto_G_Google_Play_edition_8GB?id=moto_g_8gb&hl=en What's the model number of the GPE phone I just linked to?
Click to expand...
Click to collapse
A varient of XT1032
Man you must be dumb if you think you can flash the moto g 2013 gpe rom to the 2nd generation moto g. It's like me trying to flash a GS5 or Note 4 ROM on my GS4. It will never work and results in a softbrick or worse. Also quit being so dramatic. This motorola rom is as close to stock android as you are gonna get from an OEM. If you want to get rid of the unintrusive motorola services just root and remove the unwanted apps with titanium backup.
ImperiousRex89 said:
Man you must be dumb if you think you can flash the moto g 2013 gpe rom to the 2nd generation moto g. It's like me trying to flash a GS5 or Note 4 ROM on my GS4. It will never work and results in a softbrick or worse. Also quit being so dramatic. This motorola rom is as close to stock android as you are gonna get from an OEM. If you want to get rid of the unintrusive motorola services just root and remove the unwanted apps with titanium backup.
Click to expand...
Click to collapse
It's certainly not obvious at first glance that there is not a GPE version of the 2014 version of the Moto G.
What's the technical reason that I can't flash the rom on a different device? Hardware driver support? Config files?
Is it really that difficult for Android to support having multiple drivers available for different hardware? Windows does it just fine. Linux does it.
I can't seem to root the XT1064, most people seem to end up in bootloops when trying to and so did I, so no Titanium Backup at the moment.
This is as close to stock as many manufacturers offer?? That's very disappointing.
derekm_ said:
It's certainly not obvious at first glance that there is not a GPE version of the 2014 version of the Moto G.
What's the technical reason that I can't flash the rom on a different device? Hardware driver support? Config files?
Is it really that difficult for Android to support having multiple drivers available for different hardware? Windows does it just fine. Linux does it.
I can't seem to root the XT1064, most people seem to end up in bootloops when trying to and so did I, so no Titanium Backup at the moment.
This is as close to stock as many manufacturers offer?? That's very disappointing.
Click to expand...
Click to collapse
dude try the root kernel(thanks to @savoca) and BETA-SUPERSU-v2.38.zip(http://forum.xda-developers.com/moto-g-2014/general/twrp-twrp-backup-t2964330) worked for me/
it takes about 10 minutes to boot...........
ak88900 said:
dude try the root kernel(thanks to @savoca) and BETA-SUPERSU-v2.38.zip(http://forum.xda-developers.com/moto-g-2014/general/twrp-twrp-backup-t2964330) worked for me/
it takes about 10 minutes to boot...........
Click to expand...
Click to collapse
Thanks, I'll try that today.
I tried the xt1064_lollipop_boot.img version yesterday with the 2.16, 2.35, 2.38, 2.39 but I might not have waited long enough on some of them (did wait 15+ minutes with 2.16 with no luck).
What screen was it on while booting? Was it ever a completely black screen (with backlight on) for an extended period of time?
What ROM / OS version were you on when you rooted it?
derekm_ said:
Thanks, I'll try that today.
I tried the xt1064_lollipop_boot.img version yesterday with the 2.16, 2.35, 2.38, 2.39 but I might not have waited long enough on some of them (did wait 15+ minutes with 2.16 with no luck).
What screen was it on while booting? Was it ever a completely black screen (with backlight on) for an extended period of time?
What ROM / OS version were you on when you rooted it?
Click to expand...
Click to collapse
i got the bootlogo for over 15mins.. and finally booted up...
i am using XT1068 Dual sim stock lollipop 22.11.16(XT1064 firmware):silly:
ak88900 said:
i got the bootlogo for over 15mins.. and finally booted up...
i am using XT1068 Dual sim stock lollipop 22.11.16(XT1064 firmware):silly:
Click to expand...
Click to collapse
Are you using the stock Lollipop recovery or TWRP?
How do you get into recovery from Lollipop? I've tried all different combinations of power/volume buttons but cannot get past the Broken Android screen.
By "flash SuperSU" does everyone mean using "adb sideload superSU.zip" from recovery?
derekm_ said:
Are you using the stock Lollipop recovery or TWRP?
How do you get into recovery from Lollipop? I've tried all different combinations of power/volume buttons but cannot get past the Broken Android screen.
By "flash SuperSU" does everyone mean using "adb sideload superSU.zip" from recovery?
Click to expand...
Click to collapse
The rom seems to replace the flashed Recovery with the stock..... I flash the recovery every time I want..... :-/
Place the SuperSU.zip(v2.38 beta worked for me). In your INTERNAL memory and boot into recovery(TWRP) flash it..
ak88900 said:
The rom seems to replace the flashed Recovery with the stock one...... I flash the recovery every time I want..... :-/
Place the SuperSU.zip(v2.38 beta worked for me). In your INTERNAL memory and boot into recovery(TWRP) flash it..
Click to expand...
Click to collapse
I pushed SuperSU 2.38 to /data/local/tmp/ because that's the only place that I could write to as far as I know.
I booted into recovery and installed SuperSU then rebooted (I didn't clear any cache manually).
The phone is on the Warning Bootloader Ulocked screen and rebooting. I'll let it sit for about 20 minutes and see if anything good happens. Thanks for the assistance.
Edit: is mine on the wrong screen? You said yours stayed on the "bootlogo", is that the Motorola splash screen or the "Warning Bootloader Unlocked" screen?
Edit: IT WORKED! Thank you!!
Edit: Looks like it's bootlooping after reboot.
derekm_ said:
I pushed SuperSU 2.38 to /data/local/tmp/ because that's the only place that I could write to as far as I know.
I booted into recovery and installed SuperSU then rebooted (I didn't clear any cache manually).
The phone is on the Warning Bootloader Ulocked screen and rebooting. I'll let it sit for about 20 minutes and see if anything good happens. Thanks for the assistance.
Edit: is mine on the wrong screen? You said yours stayed on the "bootlogo", is that the Motorola splash screen or the "Warning Bootloader Unlocked" screen?
Edit: IT WORKED! Thank you!!
Edit: Looks like it's bootlooping after reboot.
Click to expand...
Click to collapse
Yeah it bootloops at every reboot..... But eventually it'll boot up..... Hope someone comesup with a more stable rooting method
im pretty happy with kk, but i do want to be on 5.0, so i just wanted to make a few thing clear first.
1. if anything goes wrong with flashing a captured ota, how to restore my kk as it is now? will simply restoring a twrp backup do the trick on any stock rom?
2. where can i find the stock rom? the motorola site links arent working for me.
3. the quicksettings panel. is there a way/mod/app/ that will let me pull down quicksettings with one swipe like on cm and with gravitybox?
4.i really like to be able to customize the quicksettings, is that possible?
5. are there any bugs that seriously affect most users?
i am planning to root immediately so root only mods are fine.
im on a rooted unlocked bootloader xt1063,
thanks for your time,!
1. Just flash the stock ROM via fastboot.
2. I guess are some links on the Development section.
3. in 5.0, unfortunately not.
4. I guess no :/
5. Only a bootloop that happens with the newest versions of SuperSU (the only versions that works with 5.0), no major bugs..
Sent from my XT1063 using XDA Free mobile app
thanks for your fast response
is there a fix for said bootloop yet? can you show me a link?
Kobro said:
thanks for your fast response
is there a fix for said bootloop yet? can you show me a link?
Click to expand...
Click to collapse
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
pastorbob62 said:
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
Click to expand...
Click to collapse
lol im no noob to flashing roms and updates, i am new to lollipop
thanks so much for your info, it is very helpful.
Kobro said:
lol im no noob to flashing roms and updates, i am new to lollipop
thanks so much for your info, it is very helpful.
Click to expand...
Click to collapse
I wasn't implying you were a noob, just sharing my experience with you since you asked the question. Every device has its own quirks and idiosyncrasies. And I have seen posts from people with apparent considerable experience that displays much impatience.
Kobro said:
3. the quicksettings panel. is there a way/mod/app/ that will let me pull down quicksettings with one swipe like on cm and with gravitybox?
4.i really like to be able to customize the quicksettings, is that possible?
Click to expand...
Click to collapse
Try pulling down with two fingers instead of one- I've heard that this is the shortcut for the quick settings. (I don't have a device w/ 5 to try.) I think Google has also made the tiles in the quick settings dynamic and "smart" based on what you use most often. I tend to prefer having a static view and knowing exactly which ones are present (and in the same place!), but I won't know until I actually use it more.
I have the US GSM variant (XT1064) which came preloaded with 21.11.23. The OTA I've found only applies to 21.11.17 (the original release), and I've not had any luck downgrading. Good luck in your Lollipop quest!
Flash custom rom and enjoy lollipop
pastorbob62 said:
I wasn't implying you were a noob, just sharing my experience with you since you asked the question. Every device has its own quirks and idiosyncrasies. And I have seen posts from people with apparent considerable experience that displays much impatience.
Click to expand...
Click to collapse
your right for stating everything clearly, my bad
anomalyconcept said:
Try pulling down with two fingers instead of one- I've heard that this is the shortcut for the quick settings. (I don't have a device w/ 5 to try.) I think Google has also made the tiles in the quick settings dynamic and "smart" based on what you use most often. I tend to prefer having a static view and knowing exactly which ones are present (and in the same place!), but I won't know until I actually use it more.
I have the US GSM variant (XT1064) which came preloaded with 21.11.23. The OTA I've found only applies to 21.11.17 (the original release), and I've not had any luck downgrading. Good luck in your Lollipop quest!
Click to expand...
Click to collapse
yes that works, and has been since 4.3, on my custom rom devices it just is not so comfortable on a 5" device i was thinking more of something like pull down from right.
these responses motorola about the model xt1068
Catherine: Hi, my name is Catherine. How may I help you?
ENRICO: good morning
are to hold model xt1068, I wanted to know when will the update to Android 5
Catherine: Hi, at the moment we do not have a release date for Lollipop in Europe. It is currently going through testing before release but we are working hard to get it out as soon as possible. You can find the latest information at http://www.motorola.com/updates
ENRICO: thanks
Catherine: No problem, is there anything else that I can help you with?
ENRICO: no thanks
Catherine: Ok, have a nice day!
ENRICO:
pastorbob62 said:
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
Click to expand...
Click to collapse
just wanted to let you know, i have successfully flashed lollipop, rooted with twrp, run into the bootloop, found a solution in the general forum, (wipe cache and dalvik) and voila rooted 5.0
thanks for all your input.
Kobro said:
just wanted to let you know, i have successfully flashed lollipop, rooted with twrp, run into the bootloop, found a solution in the general forum, (wipe cache and dalvik) and voila rooted 5.0
thanks for all your input.
Click to expand...
Click to collapse
Don't need it now, but good to know should I have to reflash in the future. Thanks for the info. :good:
Dear All,
Two days before , I brought the HTC One (32 GB Golden) which on digging the Phone identity came to know the Model no 831C, later after goggling it came to know that I belongs to Sprint Carrier.
On inserting the code of Hardware components, I found few test/s were not passed and worked normally, other issues are TV app is not recognizing the server, Double Tap Screen wake/sleep works depending on its mood, vDM Client error pops up often.
Request all the experts here to please help me out with the Solution as to how can I make it work flawlessly.
Regards
Karan Adhikari
karan_adhikari said:
Dear All,
Two days before , I brought the HTC One (32 GB Golden) which on digging the Phone identity came to know the Model no 831C, later after goggling it came to know that I belongs to Sprint Carrier.
On inserting the code of Hardware components, I found few test/s were not passed and worked normally, other issues are TV app is not recognizing the server, Double Tap Screen wake/sleep works depending on its mood, vDM Client error pops up often.
Request all the experts here to please help me out with the Solution as to how can I make it work flawlessly.
Regards
Karan Adhikari
Click to expand...
Click to collapse
1) Which tests didn't pass ?
2) Which ROM are you using ?
3) TV app is discontinued by HTC (HTC suggests "Peel Smart Remote")
4) Double Tap Screen Wake works only when you lift up phone and proximity is not blocked (5 seconds cooldown between trying again).
Double tap status bar sleep is buggy on lollipop (this can be different if you have custom kernel)
5) disable vDM client app to prevent popups (you should also disable other sprint apps like HtcSprintService and Self Service SZ)
First of all, thank you for addressing my query & sorry for delay in revert.
Sir, I do know it’s the Sprint phone, as far your concern on below questions, let me try to answer them as below:
1) Which tests didn't pass?
When I run the all functions test by this code (*#*#3424#*#*) in one of the test the error word in green / red appears on screen
2) Which ROM are you using?
I believe it’s the Custom ROM, which would have be provided by Sprint. Software no is 1.54.651.8
3) TV app is discontinued by HTC (HTC suggests "Peel Smart Remote")
No comments, will try to search the PSR on play store.
4) Double Tap Screen Wake works only when you lift up phone and proximity is not blocked (5 seconds cooldown between trying again).
Will strictly follow next time when I do it.
Double tap status bar sleep is buggy on lollipop (this can be different if you have custom kernel)
Its on Android KK 4.4.2
5) disable vDM client app to prevent popups (you should also disable other sprint apps like HtcSprintService and Self Service SZ)
I didn’t find the option to disable vDM app nor did I found other apps of sprint. May I request you to suggest any alternates for it ?
Now, sir my other query is Is it advisable to flash a latest LP rom (i.e Goggle play edition or the rom developed by Bad boys team here) , also it seems that I am S-ON, because when I enter the bootload screen Power + Vol Down key where three android icon at bottom appears , I read LOCKED at the very top of the screen.
Pl. suggest whether it shall be advisable to do it if so request you to suggest the best ROM which shall run flawless in India.
Thanking you in anticipation.
Regards
Karan
Can somebody help me out with this please.. ??
The snapshots of my device are attached hereby, my only query is, and considering the attached images of device can I flash a Custom ROM on to it? Will that be advisable to do so? Are there the chances to Brick the device.
If the answer according to all the Experts here lies in assertive, which ROM is best, since this is a Sprint Device, I have found on the forum that Badboyz rom shall go flawless with any Sprint device, so may I go ahead with it. I am in India presently so wish that all the apps i.e Remote TV, Radio should run properly.
Regards
Karan Adhikari
karan_adhikari said:
The snapshots of my device are attached hereby, my only query is, and considering the attached images of device can I flash a Custom ROM on to it? Will that be advisable to do so? Are there the chances to Brick the device.
Click to expand...
Click to collapse
You need to delete the second and third pictures, there is way to much personal information in there.
The "Locked" at the top of the screen in the bootloader means that the bootloader is locked. If you look directly underneath it you'll see that it says "S-Off". To flash custom recoveries or roms or anything, you need the bootloader unlocked. You can do this using HTCDev, or since you're soff, you can unlock it via adb.
Once you're bootloader is unlocked, you should be set for everything. Flash a custom recovery like Captain Throwback's custom TWRP, get root if you don't have it already, update your firmware, etc. The bad boys xda page has most of this stuff in it.
Note: Your phone is supercid, so you're not limited to just sprint roms.
---------- Post added at 10:31 AM ---------- Previous post was at 10:04 AM ----------
Also, just wondering what exactly were the tests that failed when you did *#*#3424#*#* ?
Thanks a lot sir, I am grateful to you, I have followed you instruction of deleting the images.
Now, last night I did the Factory Hard reset (P+V-DN keys), it went fine, except the data was erased which I never wanted to be backed up though I was haunting of loosing the Sim Lock, but all went fine.
I have my registration on HTCDEV too, and the process of obtaining the TOKENID should go without any hassles.
Now in pursuant to your advise below, will it still be mandatory to unlock the bootloader ? or I may follow the process of wipe/data and then immediately flash the BB's Rom ?
Further, I stand corrected that all the function tests are passed normally, it was my mistake of not placing the Handset on the plain surface while performing one of the test.
Finally, why the model no in phone identity says 831C, and not M8 - May I request your views on this please?
Thanking you once again for addressing, all you guys are rocking, I am here on this forum since 2008, and needless to say "A Proud Member"
All my Best wishes to MEMBERS.
With Regards
K.B. Adhikari
ssantos132 said:
You need to delete the second and third pictures, there is way to much personal information in there.
The "Locked" at the top of the screen in the bootloader means that the bootloader is locked. If you look directly underneath it you'll see that it says "S-Off". To flash custom recoveries or roms or anything, you need the bootloader unlocked. You can do this using HTCDev, or since you're soff, you can unlock it via adb.
Once you're bootloader is unlocked, you should be set for everything. Flash a custom recovery like Captain Throwback's custom TWRP, get root if you don't have it already, update your firmware, etc. The bad boys xda page has most of this stuff in it.
Note: Your phone is supercid, so you're not limited to just sprint roms.
---------- Post added at 10:31 AM ---------- Previous post was at 10:04 AM ----------
Also, just wondering what exactly were the tests that failed when you did *#*#3424#*#* ?
Click to expand...
Click to collapse
karan_adhikari said:
I have my registration on HTCDEV too, and the process of obtaining the TOKENID should go without any hassles.
Now in pursuant to your advise below, will it still be mandatory to unlock the bootloader ? or I may follow the process of wipe/data and then immediately flash the BB's Rom ?
Click to expand...
Click to collapse
Yes, you still need to unlock the bootloader. After that you need to flash a custom recovery.
After doing these two you will be able to flash a custom rom, just make sure you follow all the instructions on the BB rom page
ssantos132 said:
Yes, you still need to unlock the bootloader. After that you need to flash a custom recovery.
After doing these two you will be able to flash a custom rom, just make sure you follow all the instructions on the BB rom page
Click to expand...
Click to collapse
Thanks once again. I am planing to adopt the process of unlocking the bootloader , via HTCDEV and then for flashing the custom Rom, shall seek your guidance hope you won't mind if I bother you for it.
Best Wishes
Karan
Hi ssantos132,
I found there is a SuperSU app preinstalled on my Handset, which prompts me to Grant access when I try to install some other apps from PS- goggle, is my device rooted, because I have found in this link (http://blog.laptopmag.com/root-htc-one-m8), wherein lastly the SuperSU app gets installed automatically.
Pl. guide.
Thanks
Yeah, it looks like you already have root. Try downloading a root checker app from the play store if you want to make sure.
ssantos132 said:
Yeah, it looks like you already have root. Try downloading a root checker app from the play store if you want to make sure.
Click to expand...
Click to collapse
Well thanks for replying. I did that earlier, it says Congratulation your device is rooted. So now when we have concluded that my device is Rooted, the only thing left to be done is, flashing a Custom recovery thru TRWP or CWM right ? Incase if its already been rooted and say if I re-do it, any risk for Device?
Pl. guide.
With Regards
Karan
karan_adhikari said:
Well thanks for replying. I did that earlier, it says Congratulation your device is rooted. So now when we have concluded that my device is Rooted, the only thing left to be done is, flashing a Custom recovery thru TRWP or CWM right ? Incase if its already been rooted and say if I re-do it, any risk for Device?
Click to expand...
Click to collapse
Yeah, once the bootloader is unlocked you can flash a custom recovery then a rom. You can't flash a custom recovery through TWRP or CWM though. Download a custom recovery then use fastboot flash recovery recovery recovery.img
Believe me, That is one rare cellphone you have got.
I am having the same and as I tried few roms, without backing up the radio and replaced it with some random one. Now my phone is just a toy to play with.
I ll suggest you to stick with the rom you are having right now, Take a nandroid backup of the rom, radio and everything else. and keep it safe for future. You will never be able to find them online for this particular phone.
If you would like to help me solve my phone's issue, Please upload the radio. My phone is just laying around in my desk as I have no way to get it to work.
karan_adhikari said:
Dear All,
Two days before , I brought the HTC One (32 GB Golden) which on digging the Phone identity came to know the Model no 831C, later after goggling it came to know that I belongs to Sprint Carrier.
On inserting the code of Hardware components, I found few test/s were not passed and worked normally, other issues are TV app is not recognizing the server, Double Tap Screen wake/sleep works depending on its mood, vDM Client error pops up often.
Request all the experts here to please help me out with the Solution as to how can I make it work flawlessly.
Regards
Karan Adhikari
Click to expand...
Click to collapse
I know about these devices that are being sold in India. I bought a used phone on OLX having same model number with the exact similar problems. I assume these devices are development only devices which don't run a final version of software. I have noticed that most of the issues in the phone are software related. Using my development expertise, I was able to fix most of the problems and upgrade the firmware to Lollipop, however I have messed up the radio and was unable to restore the radio firmware to anything that actually works (This phones come with a radio version that can't be obtained from any online source). If you can provide the radio image from your device, I will prepare a flashable zip to upgrade the firmware to Lollipop which would include the modem you provide, along with instructions on how to unlock the device and flash it to get going. Probably this would iron out the issues that you are facing with your device.
To grab the radio image from your device, use the following command from "adb shell" or Terminal Emulator
Code:
$ su
# dd if=/dev/block/mmcblk0p20 of=/sdcard/radio.img
You will find a file in the sdcard (Internal) named radio.img. Please upload it and provide me with a link.
I would advice you not to make any changes to the device until I provide you with clear instructions on how to do so. Trust me, I really had a hard time with this phone.
Well thanks indeed for the time you took for replying, Sir are you from India Since the name sounds such ?
Secondly, I am desperately looking to upgrade the Software to Latest 5.02 Lollipop from present Kitkat, my basic requirement is that any ROM to which I flash should at least contain the Stock FM Radio, wherein it should be able to tune in the Indian Radio Station.
Confusing issues which keep me scratching my head is that I have pre installed SuperSU app in it. Also I re checked it via installing the app Root Checker which indicated that my device is Rooted. However as and when I tried my device to restart it in Recovery mode it starts normally after a while , the SuperSU app is not getting started.
Can you help me through please. Favor me with (1) Do I need to unlock the Bootloader ? (2) Do I need to flash the custom recovery thru TRWP or CWM ? (3) suggest best Rom which will working with FM Radio (4) A Layman's User Guide to carry out all the process.
Thank You once again.
Regards
Karan Adhikari
dhiru1602 said:
I know about these devices that are being sold in India. I bought a used phone on OLX having same model number with the exact similar problems. I assume these devices are development only devices which don't run a final version of software. I have noticed that most of the issues in the phone are software related. Using my development expertise, I was able to fix most of the problems and upgrade the firmware to Lollipop, however I have messed up the radio and was unable to restore the radio firmware to anything that actually works (This phones come with a radio version that can't be obtained from any online source). If you can provide the radio image from your device, I will prepare a flashable zip to upgrade the firmware to Lollipop which would include the modem you provide, along with instructions on how to unlock the device and flash it to get going. Probably this would iron out the issues that you are facing with your device.
To grab the radio image from your device, use the following command from "adb shell" or Terminal Emulator
Code:
$ su
# dd if=/dev/block/mmcblk0p20 of=/sdcard/radio.img
You will find a file in the sdcard (Internal) named radio.img. Please upload it and provide me with a link.
I would advice you not to make any changes to the device until I provide you with clear instructions on how to do so. Trust me, I really had a hard time with this phone.
Click to expand...
Click to collapse
I will try to help you out definitely, once i am out of my confusion, of taking the Nandriod back up, I will try to upload the img file so your problem is hopefully solved
Thanks
gjmptw said:
Believe me, That is one rare cellphone you have got.
I am having the same and as I tried few roms, without backing up the radio and replaced it with some random one. Now my phone is just a toy to play with.
I ll suggest you to stick with the rom you are having right now, Take a nandroid backup of the rom, radio and everything else. and keep it safe for future. You will never be able to find them online for this particular phone.
If you would like to help me solve my phone's issue, Please upload the radio. My phone is just laying around in my desk as I have no way to get it to work.
Click to expand...
Click to collapse
(1) Do I need to unlock the Bootloader ?
YEs, you must unlock it. It won't affect the phone's basic functunalities
(2) Do I need to flash the custom recovery thru TRWP or CWM ?
Yes. I recommend twrp.
(3) suggest best Rom which will working with FM Radio
None for the phone we are using A Layman's User Guide to carry out all the process.
Please don't upgrade the rom as it might mess with the boot("radio") . Upload your radio and wait for Dhiru's post.
thanks, where shall I get the Radio file please ?
gjmptw said:
(1) Do I need to unlock the Bootloader ?
YEs, you must unlock it. It won't affect the phone's basic functunalities
(2) Do I need to flash the custom recovery thru TRWP or CWM ?
Yes. I recommend twrp.
(3) suggest best Rom which will working with FM Radio
None for the phone we are using A Layman's User Guide to carry out all the process.
Please don't upgrade the rom as it might mess with the boot("radio") . Upload your radio and wait for Dhiru's post.
Click to expand...
Click to collapse
Mr. Dhiru,
Pl intervene and guide me on how do I take the back up and upload the Radio file. So far what I understood is that TWRP toolkit from sites like Rootjunky and follow the youtube video uploaded for it and instal the TWRP and back the radio file and then upload them here for your needful
Pl. guide whether is understanding is correct or not ?
Thanks
karan_adhikari said:
Well thanks indeed for the time you took for replying, Sir are you from India Since the name sounds such ?
Secondly, I am desperately looking to upgrade the Software to Latest 5.02 Lollipop from present Kitkat, my basic requirement is that any ROM to which I flash should at least contain the Stock FM Radio, wherein it should be able to tune in the Indian Radio Station.
Confusing issues which keep me scratching my head is that I have pre installed SuperSU app in it. Also I re checked it via installing the app Root Checker which indicated that my device is Rooted. However as and when I tried my device to restart it in Recovery mode it starts normally after a while , the SuperSU app is not getting started.
Can you help me through please. Favor me with (1) Do I need to unlock the Bootloader ? (2) Do I need to flash the custom recovery thru TRWP or CWM ? (3) suggest best Rom which will working with FM Radio (4) A Layman's User Guide to carry out all the process.
Thank You once again.
Regards
Karan Adhikari
Click to expand...
Click to collapse
Required advice pl. help somebody
Pl. advise as on which TWRP img file should I take into consideration for flashing, since my boot loader is old one the firmware no 4096, Software no is 1.54.651.8, and its sprint 831C (HTC ONE m8). I yesterday tried with the the latest 2.80 twrp img file but got stuck on "Entering Recovery" Screen, some how could manage to come back by Power+Vol up and when the screen got black then Vol Down which took me to boot-loader and then came back by reseting phone. Now the phone is working normal.
I am desperately looking to install CWM or TWRP , so that can take an nandroid backup of the system file, and later post it for the experts here to update the firmware and fix other issues......
snaps of device are attached here
Request all experts to kindly guide me here on it.
Thanking you in anticipation
Karan Adhikari
karan_adhikari said:
Mr. Dhiru,
Pl intervene and guide me on how do I take the back up and upload the Radio file. So far what I understood is that TWRP toolkit from sites like Rootjunky and follow the youtube video uploaded for it and instal the TWRP and back the radio file and then upload them here for your needful
Pl. guide whether is understanding is correct or not ?
Thanks
Click to expand...
Click to collapse
I got my Nexus 6P for Christmas, and I decided to root my Motorola Nexus 6 from last year. I've been waiting to do this for a few months, and was excited to finally enable several of the options I couldn't otherwise enable (such as double tap to wake and auto rotate on the lock screen and Google Now launcher). About an hour ago I got around to rooting and done so with little issues. It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. I rooted following the steps in a YouTube video by DroidModderX and the device is running perfectly fine. The device hasn't died yet, and I'll be interested to see when it will die. The battery life seems to fluctuate between 4,001% and 4,204% (Those two figures being the highest and lowest figures respectively). Rebooting does not fix this error.
I know it's not a massive problem, but I'd like to know what's causing this issue and how to resolve it. I haven't flashed any custom OS's on my phone, I'm still running stock Android 6.0.1 Marshmallow with the latest December security patches. The device is carrier unlocked also. How can I fix this?
Thanks,
Eamonn.
sonic2kk said:
It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. being the highest and lowest figures respectively). Rebooting does not fix this error.
Click to expand...
Click to collapse
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.
sansnil said:
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.
Click to expand...
Click to collapse
Ah, thank goodness. I'll re-root tomorrow and post back if I have any problems. Thanks!
Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.
Why did you need root for the Google now launcher?
mikeprius said:
Why did you need root for the Google now launcher?
Click to expand...
Click to collapse
What do you mean? I can run the Google Now launcher perfectly fine. Root works fine as well. The problem isn't with the Google Now launcher but with the warning on boot. I didn't need to root, I chose to. Am I misunderstanding?
Your original post made it seem like you need root for double tap to wake and Google now launcher.
sonic2kk said:
Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24269982087021512 gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: https://www.androidfilehost.com/?fid=24340319927534323 (flash this also after you flash the bootstack).
HueyT said:
(removed url) gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: (removed url) (flash this also after you flash the bootstack).
Click to expand...
Click to collapse
Worked perfect. That got rid of the corrupt message. One last question: (This is the last one, I swear! ) Are you saying that Android Pay won't work at all after rooting or that it wouldn't have worked if that screen had have appeared on boot? I hope to use the service if and when it comes to the UK.
mikeprius said:
Your original post made it seem like you need root for double tap to wake and Google now launcher.
Click to expand...
Click to collapse
Ah, sorry for the confusion my friend ?
I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...
orangekid said:
I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...
Click to expand...
Click to collapse
Haha if it wasn't a display error I might have (Though it would have only been like 3 days on the Nexus 6 )
Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6
Dalek Caan said:
Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6
Click to expand...
Click to collapse
Sorry, I don't remember where I got the updated files now. I do remember sticking to looking on XDA and not just searching randomly online, maybe you could try searching the forums?
is it possible to root with chainfire root files. I did a clean install of the January security update, then flashed the latest boot.img from chainfire then flashed SuperSU 2.66.zip through TWRP, but im still getting this. I received this same issue with the last patch. Im at the point where it isnt worth rooting. Any help would be appreciated.
Hi folks,
I'm using a Fire 7 5th Gen rooted and with the excellent Nexus Rom (02/12/2017 version). Following the upgrade I've had an issue whereby as soon as the screen goes to sleep the device appears to power off. It takes several presses of the power button to turn on again and booting into fastboot doesn't seem to work. The battery monitor shows approx 52% power (which seems about correct to me, based on how I've used it since last charge) so I didn't think it would be a battery issue. Does anyone have any idea what might be going on here and what I might do to fix it? Any help would be massively appreciated.
Thanks,
Jonathan
jonathanmoneill said:
Hi folks,
I'm using a Fire 7 5th Gen rooted and with the excellent Nexus Rom (02/12/2017 version). Following the upgrade I've had an issue whereby as soon as the screen goes to sleep the device appears to power off. It takes several presses of the power button to turn on again and booting into fastboot doesn't seem to work. The battery monitor shows approx 52% power (which seems about correct to me, based on how I've used it since last charge) so I didn't think it would be a battery issue. Does anyone have any idea what might be going on here and what I might do to fix it? Any help would be massively appreciated.
Thanks,
Jonathan
Click to expand...
Click to collapse
Symptoms are similar to a recently reported issue in the Lineage 12.1 thread if you applied the latest Nexus update. If that's the case simply roll back to the prior build.
Hi Davey,
Thanks for the update, I saw that thread after my OP and did wonder. I'm going to either roll back to an earlier version of the Nexus ROM or try a stable version of the Lineage ROM. As I can't get the device to stay on long enough to use FlashFire, I'm assuming an ADB sideload will be my best bet. Slightly off topic but is there one of those ROMs you'd recommend over the other?
jonathanmoneill said:
Hi Davey,
Thanks for the update, I saw that thread after my OP and did wonder. I'm going to either roll back to an earlier version of the Nexus ROM or try a stable version of the Lineage ROM. As I can't get the device to stay on long enough to use FlashFire, I'm assuming an ADB sideload will be my best bet. Slightly off topic but is there one of those ROMs you'd recommend over the other?
Click to expand...
Click to collapse
If the device shuts down while the Amazon logo is being displayed then it may be hardware related. ADB sideload of FireOS (be sure to get the build right) is your best option, preferably starting from stock recovery.
At present only two Custom ROMs are under active maintenance: Fire Nexus and LineageOS 12.1. Both are stable and feature complete. While I generally prefer pure AOSP (favoring Nexus) Lineage works well with this device and requires less customization to get the UX I prefer. Note: This device is not my daily driver so keeping things simple takes priority. Nexus is akin to a blank sheet of paper just waiting for some love while Lineage already has a few lines drawn in.
Davey126 said:
If the device shuts down while the Amazon logo is being displayed then it may be hardware related. ADB sideload of FireOS (be sure to get the build right) is your best option, preferably starting from stock recovery.
At present only two Custom ROMs are under active maintenance: Fire Nexus and LineageOS 12.1. Both are stable and feature complete. While I generally prefer pure AOSP (favoring Nexus) Lineage works well with this device and requires less customization to get the UX I prefer. Note: This device is not my daily driver so keeping things simple takes priority. Nexus is akin to a blank sheet of paper just waiting for some love while Lineage already has a few lines drawn in.
Click to expand...
Click to collapse
Thanks for the ROM advice. I love the Nexus ROm but I've been tempted by lineage for a while so I might take this opportunity to give it a go
In relation to sorting my current issues, the device doesn't shut down while the grey logo is being displayed, the OS loads and I usually get about 30-90 seconds of functioning before it dies again. Sorry if this seems like a NOOB question but is there any reason not to ADB sideload my chosen Lineage or Nexus ROM directly? Or if I'm going to reinstall fireOS just choose the factory reset option from fastboot (on those rare occasions I can get fastboot to work).
jonathanmoneill said:
Sorry if this seems like a NOOB question but is there any reason not to ADB sideload my chosen Lineage or Nexus ROM directly? Or if I'm going to reinstall fireOS just choose the factory reset option from fastboot (on those rare occasions I can get fastboot to work).
Click to expand...
Click to collapse
Amazon's crippled bootloader disables most commands and (obviously) ADB isn't an option from native fastboot. I doubt sideload will permit installation of a custom ROM from stock recovery. However, if you have done it before (and it works) great!
Davey126 said:
Amazon's crippled bootloader disables most commands and (obviously) ADB isn't an option from native fastboot. I doubt sideload will permit installation of a custom ROM from stock recovery. However, if you have done it before (and it works) great!
Click to expand...
Click to collapse
I hadn't tried this before and just as you predicted it didn't work. I was wondering how can I find out which version of the stock fireOS I need? Or will a factory reset from recovery still permit me to root again from scratch....
jonathanmoneill said:
I hadn't tried this before and just as you predicted it didn't work. I was wondering how can I find out which version of the stock fireOS I need? Or will a factory reset from recovery still permit me to root again from scratch....
Click to expand...
Click to collapse
You can try a factory reset. Failing that and w/o knowledge of the FireOS build that was previously installed go with 5.3.1 which is the last rootable version and will avoid a potential (recoverable) brick scenario if you inadvertently attempt to downgrade the bootloader.
Davey126 said:
You can try a factory reset. Failing that and w/o knowledge of the FireOS build that was previously installed go with 5.3.1 which is the last rootable version and will avoid a potential (recoverable) brick scenario if you inadvertently attempt to downgrade the bootloader.
Click to expand...
Click to collapse
Factory reset from the recovery screen seems to have solved my issues, tablet is purring like a kitten. Also saved myself the .bin for 5.3.1 in case of emergency. Thanks again for the advice on this
jonathanmoneill said:
Factory reset from the recovery screen seems to have solved my issues, tablet is purring like a kitten. Also saved myself the .bin for 5.3.1 in case of emergency. Thanks again for the advice on this
Click to expand...
Click to collapse
I was the one having the update issues, but it was on the Lineage ROM! Looks like whatever ggow did, it's affecting both Nexus and Lineage. I think I'll just roll back to the previous build then restore apps.