Database Develop

[Q] Accidentally flashed a TW device to WW

Hi, I recently purchased a TF701, upon rooting the device, I flashed the CROMi-X rom. The tablet now struggles to stay connected to wifi and I am unable to flash the 10.26.1.18 update from the ASUS website.
Any assistance would be appreciated.

ChiLL135 said:
Hi, I recently purchased a TF701, upon rooting the device, I flashed the CROMi-X rom. The tablet now struggles to stay connected to wifi and I am unable to flash the 10.26.1.18 update from the ASUS website.
Any assistance would be appreciated.
Click to expand...
Click to collapse
using CWM (you can boot it):
http://droidbasement.com/db-blog/?p=3260
flash (this is the US update system/kernel):
http://droidbasement.com/db-blog/?p=3210
wipe data and reboot. when you boot in, your recovery will be replaced with the stock one (US) and you will be back on the stock US rom (10.26.1.18).
you can try to go back to TW now via the microsd update method.

Thank you so much, also, do you know of a way to downgrade from 10.26.1.18 to 10.26.1.7?

I'm unsure if Asus puts locks in place to prevent rolling back.

[Q] suggestion for update ota and os for vs98012b

hi all, I'm a little lost on what to do. I'm trying to update my phone because I'm not receiving texts out of town (need to reset my phone to get them all every time).
My phone has the following:
android 4.2.2 vs98012b (verizon)
rooted w twrp installed (and I'm guessing some sort of ota block since it hasn't updated)
What I want to do is update my phone so it can get texts out of town so I'm thinking OTA? I've searched and found
VS98024A - OTA manual install + Patched Stock Kernels (http://forum.xda-developers.com/showthread.php?t=2699123), is this the way to go?
Is there a flash I can just use? I don't need the latest OTA or Android OS since I'm fine with what I'm using now (although that would be nice too).
anyways, a point in the right direction would be much appreciated. thanks!

ponso said:
hi all, I'm a little lost on what to do. I'm trying to update my phone because I'm not receiving texts out of town (need to reset my phone to get them all every time).
My phone has the following:
android 4.2.2 vs98012b (verizon)
rooted w twrp installed (and I'm guessing some sort of ota block since it hasn't updated)
What I want to do is update my phone so it can get texts out of town so I'm thinking OTA? I've searched and found
VS98024A - OTA manual install + Patched Stock Kernels (http://forum.xda-developers.com/showthread.php?t=2699123), is this the way to go?
Is there a flash I can just use? I don't need the latest OTA or Android OS since I'm fine with what I'm using now (although that would be nice too).
anyways, a point in the right direction would be much appreciated. thanks!
Click to expand...
Click to collapse
You need to wipe your phone to out of the box stock to use that method, if you're gonna wipe clean, you might as well take the OTA's to the current version of android on our phones.
Another option is this - http://forum.xda-developers.com/showthread.php?t=2715408
You would just need to update your baseband following the instructions in the post then install the rom via TWRP.
Either way you're gonna be wiping your phone clean.

Thank you. I went with the 2nd option and my phone is running great with the update.
Although it took awhile to reconfigure everything back.
mjones73 said:
You need to wipe your phone to out of the box stock to use that method, if you're gonna wipe clean, you might as well take the OTA's to the current version of android on our phones.
Another option is this - http://forum.xda-developers.com/showthread.php?t=2715408
You would just need to update your baseband following the instructions in the post then install the rom via TWRP.
Either way you're gonna be wiping your phone clean.
Click to expand...
Click to collapse

[Q] Rooted 5.0.1, OTA update to T-mo 5.1 offered, failed. How to proceed?

Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!

a phone that is pure stock can take an ota. a phone that has any files changed, or not pure stock can not flash an ota, doesnt matter how many otas you try. you will have to flash the factory img.

So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.

RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
you cant flash it in twrp. you can flash the factory img via fastboot while youre in the bootloader. or you can flash a 5.1 custom rom, that will be easier.

RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
If you want to take the OTA, do the following:
Download the 5.0.1 factory zip.
Extract all of the files.
To unroot, fastboot flash the system.img.
Fastboot flash the stock recovery.img.
If you are unencrypted, fastboot flash the stock boot.img.

RanceJustice said:
Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!
Click to expand...
Click to collapse
Please take a bug report and find the OTA link inside. Instructions here: https://www.reddit.com/r/nexus6/comments/2zlqid/psa_if_you_receive_the_tmobile_51_ota_update/

[ROM] [r02 - 2015-12-13] Flashcast-AutoRoot

What is it?
This is my final gift to the Chromecast community, called Flashcast-AutoRoot. This is a special recovery image for the Chomecast v1 device that will allow it to take official Google OTA's, and then root them during the flashing process. This means you get to keep root, while staying up to date with Google images!
Features:
Auto roots any official Google OTA sent to your device
Supports automatic Recovery Image updates
Spawns a root telnet server
Supports a custom startup script
DHCP and Custom DNS
Q and A:
Q: How do I setup a custom startup script?
A: Just write your script to a file at /data/user_boot_script.sh, and set the executable bit for the file. Once done, it will be loaded on next boot.
Q: How do I setup custom DNS servers?
A: Put the IP addresses of the DNS servers in a file at /data/dns.conf, one per line. On next boot these will be used for DNS requests. Note if you are coming from EurekaROM, it will already have your old settings in place.
Q: How do I setup the EurekaROM Web Panel?
A: By default this ROM has no Web Panel, but this can be added by bootstrapping onto the custom startup script, but I will leave this up to you.
Q: Can Google unroot my device in the future?
A: Technically yes, but they would have a hard time doing so. To get technical, the bootloader partition can't be updated from the stock OS due to the kernel hard-setting it to "ro". While the recovery image can be flashed from the OS, the root process replaces the included recovery image with it's self to prevent any update. The recovery is also unable to update the bootloader partition, so you should always be able to re-flash using a OTG cable. With that said, I have also put in an update method so I can push updates to the recovery image if needed, but at this time I have no plans on doing so unless required, so use this image at your own risk.
Installation:
To install this, all you need to do is SSH/Telnet into an already rooted Chromecast, and run the following commands:
Code:
busybox wget http://pdl.team-eureka.com/recovery/install.sh -O /cache/install.sh
busybox chmod +x /cache/install.sh
/cache/install.sh
Note:
If this is ran on a different ROM than Eureka-ROM there may be an error when ran, but rest assured the flashing process will still work.
GPL/Source:
https://github.com/team-eureka/flashcast-flasher/tree/newmode-alpha

Thanks for all your work for our chromecasts!
Confirm this is working like a charm!

Thank you once again for all the great work you have put in on this device.

@ddggttff3 Is ssh supposed to work after installing? I'm only able to connect to the chromecast via telnet.

josefede_tenor56 said:
@ddggttff3 Is ssh supposed to work after installing? I'm only able to connect to the chromecast via telnet.
Click to expand...
Click to collapse
telnet only (port 23)

For those with windows 10...
Telnet is disabled by default.
Run a command prompt with administrator privs (Shift RClick and run as Administrator) and type in the following to enable it
Code:
dism /online /Enable-Feature /FeatureName:TelnetClient
Installing now and all seems to be going well as it is currently downloading the Google OTA.
Thanks very much @ddggttff3 for this!
Ok Install is done....Had only one error reported about verification and writing to block 8 which was replaced by recovery.
Unit rebooted and is working fine.
Only strangeness was it took a minute and a reboot for the unit to register with The Google Cast (DIAL LIST) but after a reboot it showed up and connected which I believe may be a local unit thing that happens with my unit from time to time not anything to do with this project!
GREAT JOB!

Yup. Worked as expected. Now Im prepared for new update who hope fully also bring multiroom support to standard chromecast as well (keep my fingers crossed)
Skickat från min GT-I9505 via Tapatalk

huge thanks ddggttff3, your the man.

Subscribed to the thread. Thank you again for everything you did for the chromecast

@ddggttff3 , could you please make a tutorial on how to install the web panel?
Sorry I'm new at this.

@ddggttff3, thank you so much for this!
I try this few times on my 2nd CC. First time from Eureka ROM, then from stock rooted.
I receive two errors, one during the first flash (regarding recovery), other during flashing from rooted stock. I guest, they all right, but just to be sure:
Code:
First block failed verification at byte 8 of 10743808. Wrote 11 replacement blocks to recovery.
Code:
/cache/install.sh: line 67: EurekaSettings: not found
expr: syntax error
Also have a two questions:
What's the difference between recovery used in previous Eureka ROM and the one used in this rooted stock?
And once new OTA for stock CC arrives, I should run this command manually again, to receive it, right?

Srandista said:
@ddggttff3, thank you so much for this!
I try this few times on my 2nd CC. First time from Eureka ROM, then from stock rooted.
I receive two errors, one during the first flash (regarding recovery), other during flashing from rooted stock. I guest, they all right, but just to be sure:
Code:
First block failed verification at byte 8 of 10743808. Wrote 11 replacement blocks to recovery.
Code:
/cache/install.sh: line 67: EurekaSettings: not found
expr: syntax error
Also have a two questions:
What's the difference between recovery used in previous Eureka ROM and the one used in this rooted stock?
And once new OTA for stock CC arrives, I should run this command manually again, to receive it, right?
Click to expand...
Click to collapse
I got the first error the same as you but it did not seem to have any affect since the unit completed the rest of the install and is working just fine.
I dod not get the second error you mentioned though.

Should we run this every time we want to update Chromecast, or is it automatically updating itself when new firmware released?

Srandista said:
What's the difference between recovery used in previous Eureka ROM and the one used in this rooted stock?
And once new OTA for stock CC arrives, I should run this command manually again, to receive it, right?
Click to expand...
Click to collapse
The errors you saw are normal, and are nothing to worry about. As for the questions, the recovery on this has some custom scripts (can be seen in the repo) that do the entire process, so once google pushes an update to your device using the stock update binary, this special recovery will automatically root it during installation.
kefallo said:
Should we run this every time we want to update Chromecast, or is it automatically updating itself when new firmware released?
Click to expand...
Click to collapse
Completely automatic, so there is nothing you need to do.

Awesome work, I'm not sure if I want to update my device with this yet since we have the current Eureka rom, but if that was the last this is an excellent way to allow future versions and keep root, thanks for your work!

Hi,
Just found this thread and about to SSH in do the update. Unfortunately I've lost the user/pass.
Help please.
Cheers
Geoff
Edit>> took a guess and was correct. User: root, no need to enter password.
Updating now .....

ghowse said:
Hi,
Just found this thread and about to SSH in do the update. Unfortunately I've lost the user/pass.
Help please.
Cheers
Geoff
Edit>> took a guess and was correct. User: root, no need to enter password.
Updating now .....
Click to expand...
Click to collapse
Try reflashing Eureka rom
Enviado desde mi GT-I9506 mediante Tapatalk

josefede_tenor56 said:
Try reflashing Eureka rom
Click to expand...
Click to collapse
Thanks, I was able to do the update via SSH.
Like an earlier poster, I don't know how to boot the web interface. I'll be doing some research, but hopefully someone will give some hints.
Cheers
Geoff
Edit>> I'm trying to learn about using sed to edit the script file(s). Am I on the right track?

ghowse said:
using sed to edit the script file(s).
Click to expand...
Click to collapse
Sed is available on the CC but looks a bit dangerous. I don't want to brick my device. I'm still looking for another editor. There is no nano, pico, vi etc that I can see.
Still trying .....

I ran this on my eureka rom Chromecast last night and the script seemed successful and then said rebooting, I saw flashcast on my tv but now it just shows white "chromecast..." letters on a black screen. I had it plugged into power on the TV's usb port during the process is there a chance it needed more power during the flash and got corrupt? Any ideas to try to revive it?

News about root for this device?

Anyone know a secure procedure and a custom recovery compatible?

marte66 said:
Anyone know a secure procedure and a custom recovery compatible?
Click to expand...
Click to collapse
We don't have TWRP yet, it's not officially out yet for any G7 models and I don't know when ours may be.
Root your G7 with Magisk
I noticed this method without using TWRP on the G7 XDA forum but haven't tried it, and you must unlock the bootloader first. Apparently it's working for a few G7 users so it should on G7+ too if the correct boot.img is used (for G7+/'lake' not G7/'river') according to your release channel. You still wouldn't have a custom recovery but could install Adaway, Magisk modules, and gain full access to the file system.
EDIT:
If anyone tries this method please report back, and don't forget to unlock the bootloader first and use the Lake/G7 Plus firmware from lolinet. No one has reported it not working but only a handful have used it afaik. I'm on RETLA w/Dec security patch so would rather wait until OTA updated and then I might try it because it would give me everything I need from root except nandroid backups and installing ROMs (of which there aren't any yet). I have my unlock code ready to go and have the needed boot.img from my channel-specific firmware but remain fully stock.
The instructions aren't that detailed but I found you can install Magisk Manager as an apk, open it and when you tap on Install Magisk 18.1 (which isn't installed yet) it also gives the option to "patch boot.img" (which I didn't select but assume it'll let you navigate to where you put the one from firmware & not alter the currently booted partition). When finished you put/copy that altered one on your pc (preferably in your Fastboot/ABD folder) and fastboot flash it, then reboot and you should be rooted in Magisk.
EDIT #2:
Tried it, it works!

I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?

washoq said:
I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?
Click to expand...
Click to collapse
If someone on your channel could capture their PPW29.98-66 OTA before installing, otherwise I think you'd have to wait until it appears on lolinet or Motorola's site, or we get TWRP. I realized I'd be in the same boat because my current firmware was also the only one so far on lolinet, so I decided to go ahead because I'd only get January's security patch (on Dec now) and still be a few months behind anyway.
Having done it I can say that Magisk Manager does let you navigate to the stock boot.img file after offering to patch it, then it goes through the same familiar steps as when installing in TWRP, and at the end tells you it's in your Download folder with the name patched_boot.img. After transferring to my pc I renamed it to boot.img and just manually typed in the fastboot flash boot command.
I also want to repeat that although rooted there's still no custom recovery/TWRP so you can't do nandroid backups, and now when my channel's OTA comes along I'll have to disable Magisk & flash back to my original boot.img before taking it, which I hope works but it should. It's great being rooted though on G7+ with Adaway and Youtube vanced background play, also Root Explorer to change my boot animation or debloat or whatever.

Dahenjo said:
If someone on your channel could capture their PPW29.98-66 OTA before installing, otherwise I think you'd have to wait until it appears on lolinet or Motorola's site, or we get TWRP. I realized I'd be in the same boat because my current firmware was also the only one so far on lolinet, so I decided to go ahead because I'd only get January's security patch (on Dec now) and still be a few months behind anyway.
Click to expand...
Click to collapse
Yeah, I thought so. Thanks anyway.

washoq said:
I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?
Click to expand...
Click to collapse
I see there is a PPW29.98-66 RETAIL channel firmware on lolinet:
https://mirrors.lolinet.com/firmware/moto/lake/official/RETAIL/
I'm not sure what difference the boot.img would have between them if any, and the RETAIL channel is more a 'generic' type which might be a safer choice than others of the same build version. I know the G5+ debloated ROMs by NZedPred ended up with just one version (instead of by various channels as he did originally) after finding he didn't need to bother, though I believe he did make other changes. He'd be a good one to ask though if you want to PM him.
After I get updated (revert to full stock etc) I may try the RETAIL one to re-root to see if we can use it for this purpose regardless of channel. My 'international model' from Amazon is actually just the RETLA channel since it wasn't released in the US, so I'd almost rather be on the more generic channel if it works.
EDIT:
Did some experimenting, reverted to full stock then successfully tried it again with the boot.img from the RETAIL firmware (which for my version is still PPW29.98-28), so I believe RETAIL could be used for other channels too.

This process worked for me. Moto G7 Plus, International Unlocked version.

This worked for me, XT1965-2, AT&T mexican version. Also, managed to run Substratum, just needed to compile, reboot and activate each time I changed theme.

Well I am on the same Page...
Also my Channel Islands reteu2, I can only find reteu...
My g7pluswas shipped already with a newer Version than available. Anyone tried the retail bootloader?
Alternatively, can we somehow flash the whole "retail" version on this phone?

shaDNfro said:
Well I am on the same Page...
Also my Channel Islands reteu2, I can only find reteu...
My g7 was shipped already with a newer Version than available. Anyone tried the retail bootloader?
Alternatively, can we somehow flash the whole "retail" version on this phone?
Click to expand...
Click to collapse
I assume you have G7 Plus (not G7) with the build number you showed.
To answer your question:
I successfully fastboot flashed the full RETAIL channel PPW29.98-66 firmware a few days ago. I was on RETLA PPW29.98-28 with the December security patch and now have the January patch, and my channel is still shown as RETLA. I used the batch file posted in this thread which worked perfectly. Everything for my XT1965-2 RETLA model is working as it should on the newer RETAIL firmware, but I don't know if your RETEU2 has anything different that could cause issues.

Enforced Verity, Unlocked Bootloader, rooted Lake OPENMX Not working with Google Pay
"Couldn't finish setup to pay in stores
This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
Did I screw up by not preserving dm/verity when I patched the boot and if so, is there a way to fix it? Reflash oem rom, reinstall magisk, repatch boot, rereflash new rom with dm/verity preserved?

vvarrior said:
"Couldn't finish setup to pay in stores
This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
Did I screw up by not preserving dm/verity when I patched the boot and if so, is there a way to fix it? Reflash oem rom, reinstall magisk, repatch boot, rereflash new rom with dm/verity preserved?
Click to expand...
Click to collapse
I tried everything but its not working stalble for me either.
You can do delete google pay cache+data and google play services cache+data, reboot and then you can configure a payment method (e.g. add credit card). Afterwards I was able to pay exactly one time... next time it refues my card telling me I am not able to pay with that card any more...
(Bye the way, people say the issue might be connected with wifi as well, so I turned off wifi for that procedure I mentioned above)
Anyway I deleted google pay now using my banks own application, which does not detect root using magisk hide

shaDNfro said:
I tried everything but its not working stalble for me either.
You can do delete google pay cache+data and google play services cache+data, reboot and then you can configure a payment method (e.g. add credit card). Afterwards I was able to pay exactly one time... next time it refues my card telling me I am not able to pay with that card any more...
(Bye the way, people say the issue might be connected with wifi as well, so I turned off wifi for that procedure I mentioned above)
Anyway I deleted google pay now using my banks own application, which does not detect root using magisk hide
Click to expand...
Click to collapse
There's a bunch of Google apps that need verity to be enforced I think. I think we need the stock ROM with the stock boot. Maybe the phone has to be rooted to patch the stock boot.img with verity enforced? I'm not sure but I stepped up to the G7 Plus because it finally has NFC so I can use it to pay and it was an unlocked international version that works good with Google Fi (which also needs verity enforced).
Still looking for a solution and will probably just go back to my old phone until I can get Google Fi and Pay working.