Related
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?
Nexus 6 Rooted and Unlocked and now new OTA – confused
Dear Friends,
I am currently having Nexus 6 with Build Number MRA58N which is rooted unlocked. Last time I had to format Nexus 6 just to update to this build. The nexus toolkit was somehow not working for me.
Now I see again that there is an OTA called android 6.0.1
image hosting
Now I tried using Wugfresh Toolkit first to take android backup but it fails and shows as shown in screenshot that currently there is no modified boot.img available for MRA58N.
free photo upload
I really don’t want to flash factory image bcz it will overwrite everything and erase all.
Kindly help.
Reformatting and again restoring is too much of pain.
Google is your friend, you should Google something like that before creating a post, but anyway you can't take an Ota on a rooted device, if you want the Ota, flash system.img of the current rom, and then take the Ota
I did try and read many posts but still could not conclude anything for sure. Yes I agree OTA cannot be taken on rooted device and thats why my question. you suggested flashing system.img of current rom. Now thats where confusion starts as many posts mention that one needs to be 100percent stock. Many people recommended complete wipe and yet many posed lot of questions because of marshmallow special kernel rom issues which is beyond my technical understanding.
Hence I summarized to pose my query to get considered opinion and guidance. Your response is helpful but am not able to fully comprehend.
Hence request for more guidance.
Really appreciate if some experts would kindly reply to my query and guide me. It will be very helpful as I really want to update but really scared of messing up. Kindly respond.
http://www.droidviews.com/how-to-install-ota-updates-on-rooted-nexus-6/
also watch a few youtube vid's - it is a road well traveled.
i.e.
- Flash the system image for build that you are currently running.
- sideload the update
be patient and don't even think of interrupting the process.
Read the stickies and learn something, toolkits and no skills spell disaster.
Did all what was suggested word by word and now my device is stuck with ADB sideload step. Pls see the two screenshots which i took as photo from another phone. (So apologise pic quality).
Kindly guide what went wrong.
The current build was rooted using wugfresh toolkit.
Now i am stuck at this ADB step. Kindly help Pls.
upload an image
image hosting site over 5mb
Did all what was suggested word by word and now my device is stuck with ADB sideload step. Pls see the two screenshots which i took as photo from another phone. (So apologise pic quality).
Kindly guide what went wrong.
The current build was rooted using wugfresh toolkit. Did all what was suggested word by word and now my device is stuck with ADB sideload step. Pls see the two screenshots which i took as photo from another phone. (So apologise pic quality).
Kindly guide what went wrong.
The current build was rooted using wugfresh toolkit.
Now i am stuck at this ADB step. Kindly help Pls.
upload an image
image hosting site over 5mb
Now i am stuck at this ADB step. Kindly help Pls.
Something got messed up in the process. You can try to individually flash your corresponding boot.img from your version via fastboot. You can download and extract that boot.img from Google's stock images.
This is just me speaking my mind but why people go through the trouble to root just to keep the stock ROM is beyond me.
Given your situation you are better off wiping/formatting and reflashing a new ROM stock (hopefully not) or custom.
Offering this as a comment, not an answer. I agree with mikeprius - in your position I would bite the bullet, download the latest MMB29K image, and run flash-all to wipe and set your device to the newest version - or perhaps even wait for the one which may arrive within a few days. If you leave the device on stock, unrooted, you'll be able to apply OTAs without any problem at all.
For curiosity, why do you even need root? As you've discovered, it opens up cans of worms that can be more trouble than they're worth unless there's an *overwhelming* necessity for root.
looks like failed with verification of /boot
reflash these for build you are currently on - I've done this without losing data:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
fastboot reboot-bootloader
it''ll probably pop up with the dead android -- don't reboot. Press
power button+vol up
you may have have to do a bunch of times -- eventually it go to the menu to allow you sideload the update.
Why are people so fixated on installing an old ROM and then sideloading the update when the obvious answer is to simply install the components of the latest ROM? I get the desire to retain the existing data, but to my eyes it looks as if the phone is now in an unstable and unreliable state and a complete refresh is the best solution.
it's a choice and there is experience gained in the exercise - and the existing data thing is big deal to many.
This Thread is dead, I have decided to move this thread to here for some reasons, one of the reasons is that my tool should work on ALL devices (except Samsungs).
The TWRP version in this is v3.2.3-22 fajita. The Magisk Version in this is v18.0 (You can update it), this method should work on ALL versions of Oxygen OS that the OnePlus 6T runs on, maybe even works on custom ROMs.
Do NOT delete the folder "Files" (or anything in it) as it contains TWRP, necessary ADB and Fastboot files as well as the Magisk Installer.
IMPORTANT: I am not held responsible for any damage you do to your device. You are required to follow all instructions carefully. If you say that I messed up your device I won't care. If you ask for help, I might help. Enjoy the tool
This is only for Windows PCs
Instructions:
0-Open settings, then scroll down till you see "About Phone" tap it then tap "Android version"
then tap "Build number" a bunch of times till it says "You are now a Developer!" Now exit out of "About Phone" and tap "System" now tap on Developer options and look for "OEM unlocking" enable it then scroll down till you find "USB debugging" enable it too. Now plug your phone into your PC via the cable that OnePlus sent with the phone originally and press "Always Allow" then tap OK then install the ADB Drivers on your PC.
1. Download and install WinRAR: 64bit - 32bit
2. Extract the folder to your C drive directly.
3. Open the Folder "TWRP" then run "Bootloader Unlocker.exe" as Administrator (It formats your phone; deletes all data)
4. Once it is done setup your phone again and repeat step 0 but skip the OEM Unlocking part.
5. Now run "TWRP Flasher.exe" as Administrator (Follow all Instructions in the prompts; if you do not I am not held responsible if you brick your phone).
6. Now you have rooted your phone with Magisk and installed TWRP.
7. The final boss is for last... Press the Thanks button if my tool/s helped even by a little bit.
HELP
Just in case something goes wrong I linked two threads, stock fastboot ROMs and a MSMDownload Tool (If you can't get to Fastboot Mode)
CREDITS: @_Masked_ (Everything) and @mauronofrio (TWRP image and Installer)
STATE: Working.
Downloads:
Tool :
V2 - V2.1
Threads
Stock ROMs
MSMDownload Tool (OOS 9.0.6)
THREAD IS DEAD
Announcement: THREAD IS DEAD
@_Masked_ The zip file you linked to under "Tool" is password protected (I ran a Brute Force on it, already got to 4 chars long PW. Not going to spend anymore time on this, I just wanted to see what was in the Bat files).
Why is TWRP rehosted and not linking to official (or unofficial) sources?
Why are the stock roms linked under downloads? I can't see anything about them in the instructions.
Why is the MSMdownloadtool listed under downloads? It doesn't seem to have any relevancy to this.
Updated Thread
V2
_Masked_ said:
Added in first post.
Click to expand...
Click to collapse
Why is it password protected?
Why is this thread/bundle at all needed? There are plenty of established guides doing a much better job of explaining and instructing one how to do the things you've tried to do in this thread, that doesn't rebundle and rehost files (which from a new account is a tad suspicious).
I created the thread before I went to sleep, today I noticed I forgot to do a bunch of things, a lot of the instructions are in the.cmd file. And I would never steal threads or stuff like that. I used to have a account from 2016 but I forgot the username and lost access to the email (it was hacked). So I created a new account.
Sent from my ONEPLUS A6013 using Tapatalk
@_Masked_ The Bat files are well written. I however agree with @sssarg's last point. You are reinventing the wheel, if it was an Exe that might be different but your commands are the same as what is already in all the Guides/Threads.
card13 said:
@_Masked_ The Bat files are well written. I however agree with @sssarg's last point. You are reinventing the wheel, if it was an Exe that might be different but your commands are the same as what is already in all the Guides/Threads.
Click to expand...
Click to collapse
I actually wrote it from scratch, I might convert it to a .exe in the future.
Sent from my ONEPLUS A6013 using Tapatalk
v2 is coming out soon.
Thank you for this tool. It is a step in the right direction (more user friendly flashing). I understand that you can flash the device with a custom recovery and root it with just a few single clicks which is very helpful for noobs.
I did not make any modifications to my 6t yet, but will definitely do with your tool in the near future.
lieblingsbesuch said:
Thank you for this tool. It is a step in the right direction (more user friendly flashing). I understand that you can flash the device with a custom recovery and root it with just a few single clicks which is very helpful for noobs.
I did not make any modifications to my 6t yet, but will definitely do with your tool in the near future.
Click to expand...
Click to collapse
Glad to help, if you had the first version of my tool you can get the newer one which has less code and is much easier to use in my opinion.
Did you number your versions? Would be useful if there were more than one.
Also, point 4. is a little bit misunderstandable, because it is just a repetition of point 1-3. You could say "repeat steps 1-3".
The section "Downloads" is not being explained. Nobody knows why u linked the msm tool and the stock roms.
lieblingsbesuch said:
Did you number your versions? Would be useful if there were more than one.
Also, point 4. is a little bit misunderstandable, because it is just a repetition of point 1-3. You could say "repeat steps 1-3".
The section "Downloads" is not being explained. Nobody knows why u linked the msm tool and the stock roms.
Click to expand...
Click to collapse
I will add them when I get back home. I am uploading V2 to a site that is trusted more than the anonymous file site.
Sent from my ONEPLUS A6013 using Tapatalk
The twrp flasher doesn't start because you used an unregistered compiler.
Can this be used on T-Mobile?
bigjailerman said:
Can this be used on T-Mobile?
Click to expand...
Click to collapse
Yes, if your bootloader is Unlocked, check out my thread for all devices except Samsungs.
Why is it dead now?
lieblingsbesuch said:
Why is it dead now?
Click to expand...
Click to collapse
"This Thread is dead, I have decided to move this thread to Miscellaneous Android Development for some reasons, one of the reasons is that my tool should work on ALL devices (except Samsungs)."
omerbagi10 said:
"This Thread is dead, I have decided to move this thread to Miscellaneous Android Development for some reasons, one of the reasons is that my tool should work on ALL devices (except Samsungs)."
Click to expand...
Click to collapse
It is no longer in Miscellaneous Android Development it is here since I didn't find Miscellaneous Android Development suitable for it
So this is my first thread and had a heck of a time trying to successfully root the 6t using Magisk and TWRP. Why might you ask? Because the unofficial TWRP for the Oneplus 6T has a bug with the Media Transfer Protocal (MTP) so once TWRP is installed, you can't use it to install flashable zips. The device shows the 6T internal storage as empty and therefor you cant flash a zip if TWRP cant find a zip to flash. So anyways heres what I did to get this working.
*****NOTE***** I am not a dev, i simply stumbled across a solution (work-around), to the TWRP MTP issue, and therefor if anything goes wrong with your device, it is on you. DO NOT BLAME ME if you brick your device. If you so choose to follow this guide, ANY/ALL risk and the subsequent consequences, are YOURS AND YOURS ALONE.
***CREDITS*** TO: @topjohnwu for MAGISK & @mauronofrio for his unofficial android Q TWRP
STEP1: Grab this TWRP https://androidfilehost.com/?fid=1395089523397961761
STEP2: Grap magisk beta v19.2 https://github.com/topjohnwu/Magisk/releases/download/v19.2/Magisk-v19.2.zip
STEP3: Run the following command: fastboot flash boot twrp.img
***NOTICE ABOVE COMMAND*** (uses "flash boot" instead of "boot")
STEP4: Manually reboot into back into recovery
***NOTE*** once in recovery I used "swipe to allow modifications" , dont know if it matters
STEP5: Go to adb sideload tab from within TWRP Recovery
STEP6: Once adb sideload finishes loading, run the following command: adb sideload magisk.zip
STEP7: Let sideload finish, reboot device, open magisk app and follow its instructions to finish install.
kluongo said:
So this is my first thread and had a heck of a time trying to successfully root the 6t using Magisk and TWRP. Why might you ask? Because the unofficial TWRP for the Oneplus 6T has a bug with the Media Transfer Protocal (MTP) so once TWRP is installed, you can't use it to install flashable zips. The device shows the 6T internal storage as empty and therefor you cant flash a zip if TWRP cant find a zip to flash. So anyways heres what I did to get this working.
*****NOTE***** I am not a dev, i simply stumbled across a solution (work-around), to the TWRP MTP issue, and therefor if anything goes wrong with your device, it is on you. DO NOT BLAME ME if you brick your device. If you so choose to follow this guide, ANY/ALL risk and the subsequent consequences, are YOURS AND YOURS ALONE.
***CREDITS*** TO: @topjohnwu for MAGISK & @mauronofrio for his unofficial android Q TWRP
STEP1: Grab this TWRP https://androidfilehost.com/?fid=1395089523397961761
STEP2: Grap magisk beta v19.2 https://github.com/topjohnwu/Magisk/releases/download/v19.2/Magisk-v19.2.zip
STEP3: Run the following command: fastboot flash boot twrp.img
***NOTICE ABOVE COMMAND*** (uses "flash boot" instead of "boot")
STEP4: Manually reboot into back into recovery
***NOTE*** once in recovery I used "swipe to allow modifications" , dont know if it matters
STEP5: Go to adb sideload tab from within TWRP Recovery
STEP6: Once adb sideload finishes loading, run the following command: adb sideload magisk.zip
STEP7: Let sideload finish, reboot device, open magisk app and follow its instructions to finish install.
Click to expand...
Click to collapse
The twrp we have works fine dude
Lol
And you are referring to using TWRP on Android Q beta correct??? Because when I tried using the latest stable TWRP for 6T but with Android Q... It would not flash
JUST FYI
The mtp issue is a known bug with the Q developer preview.
Rite from download page.
"Known Issues
Camera, portrait mode does not work
Ambient Display is not working
System stability issues
Encryption will change in the next preview build
Some apps may not function as expected when running on this Developer preview release
Issue With MTP cannot copy rollback from PC to Phone."
Not with twrp.
The only issue with twrp at the moment is reading v3 synthetic keys to decrypt if you have pin/password set and running may security patch.
kluongo said:
And you are referring to using TWRP on Android Q beta correct??? Because when I tried using the latest stable TWRP for 6T but with Android Q... It would not flash
Click to expand...
Click to collapse
Thank you twinn for clarifying that... So I stand corrected on twinns point... But not on fullofhells needless comment
kluongo said:
Thank you twinn for clarifying that... So I stand corrected on twinns point... But not on fullofhells needless comment
Click to expand...
Click to collapse
Use Blu spark, secondly the resolution for mtp, is enable dev options and turn on USB file transfer. Then USB works. Use a prepatched twrp and pre rooted twrp Blu spark kernel. Flash in fastboot, twrp works fine. Fully. Not apparently not needless if u still have issues posting erroneous comments that serve no purpose. U should read. It serves so many purposes. U would see the fix for mtp on Q and how in the main twrp thread a week or more ago I discussed how twrp works fine if u do as I listed there.. I read everything, I assumed every other user does the same.
fullofhell said:
Use Blu spark, secondly the resolution for mtp, is enable dev options and turn on USB file transfer. Then USB works. Use a prepatched twrp and pre rooted twrp Blu spark kernel. Flash in fastboot, twrp works fine. Fully. Not apparently not needless if u still have issues posting erroneous comments that serve no purpose. U should read. It serves so many purposes. U would see the fix for mtp on Q and how in the main twrp thread a week or more ago I discussed how twrp works fine if u do as I listed there.. I read everything, I assumed every other user does the same.
Click to expand...
Click to collapse
:highfive:
WOW.
Where to start here?
The TWRP you linked (https://androidfilehost.com/?fid=1395089523397961761) is for OPO 6, not 6T, but it does say fajita, and not enchilada
TWRP works fine for us, if you use the latest.
P and Q are different beasts, as of now, and there are posts on how to flash TWRP on Q.
This thread seems redundant an unnecessary.
But....that's just my $.02
So first, i just searched all 9 pages of the 6t Guides thread section... not one single thread explaining, or detailing, any guide or tutorial, for individuals to play around with Q... On that point, not redundant.... Secondly the fajita image i posted is not for the 6... its from mauronofrio for the 6t, under the thread he started for twrp images for the 6t... so.. if it is in fact for the 6... maybe he should be notified?..... and if this thread is redudnant, why cant i find any guide detailing steps to mess around with Q?
kluongo said:
So first, i just searched all 9 pages of the 6t Guides thread section... not one single thread explaining, or detailing, any guide or tutorial, for individuals to play around with Q... On that point, not redundant.... Secondly the fajita image i posted is not for the 6... its from mauronofrio for the 6t, under the thread he started for twrp images for the 6t... so.. if it is in fact for the 6... maybe he should be notified?..... and if this thread is redudnant, why cant i find any guide detailing steps to mess around with Q?
Click to expand...
Click to collapse
Here's a thread about Q on the 6T: https://forum.xda-developers.com/oneplus-6t/how-to/oneplus-6t-androidq-beta-release-links-t3928174 (specifically post #62)
The TWRP link page you linked specifically says "Download test-twrp-3.3.0-Q-fajita.img for the OnePlus OnePlus 6" but I commented that it was correctly for the 6T. I would get ahold of Mauronofrio to inform him of the error.
It's only redundant because after reading the thread I posted above^, it seems we have some waiting to do until we even get a stable Q build.
Thanks!
Yes, I did in fact see that thread and briefly read it over. On the contrary, it did not help me in the manner i needed. Alot of people don't have the time to dig through threads to find an answer to a problem, especially from a thread which was never intended to address said problem in the first place (according to its title, as well as the entire first page of posts). I have been following these forums, quietly, since the galaxy s4 was released and hence, when I look for a guide or missing piece of information I require, i know to read and look around a bit before starting a thread. As such, I have not needed to create a thread EVER... and then there was this problem with no clear cut guide, thread, solution... nada.... so alas, I decided to provide one for a change... I am now reminded why i choose to stay mostly quiet... because xda has become a honeypot full of negative trollers, and "full-of-themself" donald trumps, when it should contain more people offering constructive critisicm, positive environment, and turning the less knowledgeable into the more informed android enthusiast.
Just my $.01
kluongo said:
Yes, I did in fact see that thread and briefly read it over. On the contrary, it did not help me in the manner i needed. Alot of people don't have the time to dig through threads to find an answer to a problem, especially from a thread which was never intended to address said problem in the first place (according to its title, as well as the entire first page of posts). I have been following these forums, quietly, since the galaxy s4 was released and hence, when I look for a guide or missing piece of information I require, i know to read and look around a bit before starting a thread. As such, I have not needed to create a thread EVER... and then there was this problem with no clear cut guide, thread, solution... nada.... so alas, I decided to provide one for a change... I am now reminded why i choose to stay mostly quiet... because xda has become a honeypot full of negative trollers, and "full-of-themself" donald trumps, when it should contain more people offering constructive critisicm, positive environment, and turning the less knowledgeable into the more informed android enthusiast.
Just my $.01
Click to expand...
Click to collapse
No need to stay quiet, just learn to use the search function, and participate on the already created threads instead of creating new ones. (Just a suggestion...)
And the ad hominem attempts are unnecessary.
Love,
'full-of-myself'
No..
Love,
@fullofhellself
?
Damn wth did I do..lol... We are a system of checks and balances for all users. Full of myself... Yeah okay.. better be nice or mom's not gunna pay your internet bill.. and I hate trumpian politics. I just loathe redundant unusable posts. As do my constituents here..
kluongo said:
Yes, I did in fact see that thread and briefly read it over. On the contrary, it did not help me in the manner i needed. Alot of people don't have the time to dig through threads to find an answer to a problem, especially from a thread which was never intended to address said problem in the first place (according to its title, as well as the entire first page of posts). I have been following these forums, quietly, since the galaxy s4 was released and hence, when I look for a guide or missing piece of information I require, i know to read and look around a bit before starting a thread. As such, I have not needed to create a thread EVER... and then there was this problem with no clear cut guide, thread, solution... nada.... so alas, I decided to provide one for a change... I am now reminded why i choose to stay mostly quiet... because xda has become a honeypot full of negative trollers, and "full-of-themself" donald trumps, when it should contain more people offering constructive critisicm, positive environment, and turning the less knowledgeable into the more informed android enthusiast.
Just my $.01
Click to expand...
Click to collapse
Chill out, no need to bring politics into a phone modding forum, seems kinda silly doesn't it? But yes, you should have just gone to the existing 6T Android Q thread and just used the search function. Wouldn't have been that hard. I never even installed Android Q and I even remember reading through numerous posts of people wanting to return to stock. I don't blame you for posting or anything, I'm just letting you know that there definitely was a clear-cut easy way to find a way to go to stock from the Q beta.
LMAO xda is getting out of control... I agree with the OP as the other thread is not about this particular issue... Which was getting twrp and magisk going on the Q beta (NOT returning to stock - like where did that even come from if your following along lol)
I could easily see him getting flamed for hijacking the thread if he posted this tutorial in the other person's thread. You can't win for loosing any more.
This is also why I stay mostly silent on here smh!
juggz143 said:
LMAO xda is getting out of control... I agree with the OP as the other thread is not about this particular issue... Which was getting twrp and magisk going on the Q beta (NOT returning to stock - like where did that even come from if your following along lol)
I could easily see him getting flamed for hijacking the thread if he posted this tutorial in the other person's thread. You can't win for loosing any more.
This is also why I stay mostly silent on here smh!
Click to expand...
Click to collapse
omfg. Read post 1. Reread. Read again. Now read your sentences. Try not to feel dumb. Search function = no one wastes time. That's all.
fullofhell said:
omfg. Read post 1. Reread. Read again. Now read your sentences. Try not to feel dumb. Search function = no one wastes time. That's all.
Click to expand...
Click to collapse
[emoji848]Maybe it's you who should re-read. The first post doesn't mention anything about returning to stock. He's trying to install magisk on a BETA, which is the polar opposite of returning to stock [emoji2375][emoji2363]...
If anything having a dedicated thread for a "specific reason" is much easier to find, and less time consuming, than searching for a possible answer in the comments of another thread on a somewhat related post. He's making the search more efficient since you mention "wasting time", you're the one wasting time *****ing on a usefull post lol.
You're assuming installing TWRP is for the purpose of returning to stock but there's a ton of other reasons someone could want to install TWRP and then magisk... Also there's other ways to return to stock besides TWRP soooo [emoji2375] i guess that's a waste of time too...
What are we doing SMH [emoji23][emoji24][emoji88]
Sent from my SM-G975U1 using Tapatalk
juggz14301 said:
[emoji848]Maybe it's you who should re-read. The first post doesn't mention anything about returning to stock. He's trying to install magisk on a BETA, which is the polar opposite of returning to stock [emoji2375][emoji2363]...
If anything having a dedicated thread for a "specific reason" is much easier to find, and less time consuming, than searching for a possible answer in the comments of another thread on a somewhat related post. He's making the search more efficient since you mention "wasting time", you're the one wasting time *****ing on a usefull post lol.
You're assuming installing TWRP is for the purpose of returning to stock but there's a ton of other reasons someone could want to install TWRP and then magisk... Also there's other ways to return to stock besides TWRP soooo [emoji2375] i guess that's a waste of time too...
What are we doing SMH [emoji23][emoji24][emoji88]
Click to expand...
Click to collapse
Who is talking about returning to stock? He's talking about installing TWRP and magisk on Q beta.
Here's an interesting one...
I found the android 14 beta just too buggy, so (per procedure) withdrew from the beta program, downloaded the latest stable 13 os via system setup, installed it and restarted when prompted. Similar to a factory reset, when the phone rebooted, the setup program ran.
But early in the process when offered to copy data from a phone (which I obviously had just blown away) I choose "don't copy", but nothing happens. Choose it again and I get an error message "settings keeps stopping" offering app info (no help there), close app, or send feedback (no way to do that at that point). Dead in the water, can't proceed..
I tried the copy data option from wife's 6a but that didn't work. Doesn't recognize the cable is connected - using the official google cable that came with the phone.
Notes:
I've got a case open with google (level 2) but so far nothing.
Adb doesn't recognize the phone so I can't sideload the rom.
Bought at Best Buy last October. I may take it back there to see if the Geek Squad can do something but I'm not optimistic.
I can get into bootloader, recovery, etc. (via buttons, not ABD). But I don't see where that helps.
Any suggestions?
weinbers said:
Here's an interesting one...
I found the android 14 beta just too buggy, so (per procedure) withdrew from the beta program, downloaded the latest stable 13 os via system setup, installed it and restarted when prompted. Similar to a factory reset, when the phone rebooted, the setup program ran.
But early in the process when offered to copy data from a phone (which I obviously had just blown away) I choose "don't copy", but nothing happens. Choose it again and I get an error message "settings keeps stopping" offering app info (no help there), close app, or send feedback (no way to do that at that point). Dead in the water, can't proceed..
I tried the copy data option from wife's 6a but that didn't work. Doesn't recognize the cable is connected - using the official google cable that came with the phone.
Notes:
I've got a case open with google (level 2) but so far nothing.
Adb doesn't recognize the phone so I can't sideload the rom.
Bought at Best Buy last October. I may take it back there to see if the Geek Squad can do something but I'm not optimistic.
I can get into bootloader, recovery, etc. (via buttons, not ABD). But I don't see where that helps.
Any suggestions?
Click to expand...
Click to collapse
I'm not sure what you mean about system setup unless you mean system update but try using the firmware from here.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
You went from one version of firmware to another so ADB might have to be enabled again in developer options once you get it booted up again.
I like to put fastboot "--slot all" in front of the bootloader and radio in the flash-all.bat so they install to both slots.
Tulsadiver said:
I'm not sure what you mean about system setup unless you mean system update but try using the firmware from here.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
You went from one version of firmware to another so ADB might have to be enabled again in developer options once you get it booted up again.
I like to put fastboot "--slot all" in front of the bootloader and radio in the flash-all.bat so they install to both slots.
Click to expand...
Click to collapse
System setup as in a brand new phone.
Can't use abd or alternative software - no way to load it as abd doesn't recognize the phone. Fastboot doesn't work, can't sideload, etc.
weinbers said:
System setup as in a brand new phone.
Can't use abd or alternative software - no way to load it as abd doesn't recognize the phone. Fastboot doesn't work, can't sideload, etc.
Click to expand...
Click to collapse
Okay, I thought you said you could get into bootloader.....
Tulsadiver said:
Okay, I thought you said you could get into bootloader.....
Click to expand...
Click to collapse
I can, but since adb doesn't recognize the device, sideloading doesn't work.
weinbers said:
I can, but since adb doesn't recognize the device, sideloading doesn't work.
Click to expand...
Click to collapse
The files I linked are fastbooted files, not adb.
Tulsadiver said:
The files I linked are fastbooted files, not adb.
Click to expand...
Click to collapse
Ah, I see. So I get this right, what is the full syntax for the fastboot command I should use, please. - a lot of switches needed. I've downloaded the rom and I'm ready to flash... Using windows.
Slot a is the active slot now.
Do I need to do the radio separately?
BTW, I have a locked bootloader...
Thanks for the help!
weinbers said:
Ah, I see. So I get this right, what is the full syntax for the fastboot command I should use, please. - a lot of switches needed. I've downloaded the rom and I'm ready to flash... Using windows.
Slot a is the active slot now.
Do I need to do the radio separately?
BTW, I have a locked bootloader...
Thanks for the help!
Click to expand...
Click to collapse
Sorry, this won't help you then. It requires that the bootloader be unlocked.
Tulsadiver said:
Sorry, this won't help you then. It requires that the bootloader be unlocked.
Click to expand...
Click to collapse
thanks anyway!
Have you tried going into Recovery Mode and factory resetting/wipe data there?
You wouldn't need an unlocked bootloader...
Also, you can try to sideload OTA images (using adb) and that also can be done in a locked bootloader...
you can find it below...
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
getting the computer to "recognize" the device for adb commands usually is just a matter of installing and applying the proper usb drivers (also found below)
https://dl.google.com/android/repository/usb_driver_r13-windows.zip
*if you are running Linux or MacOS, there's different resources for that...
If you need help, getting your computer to recognize your device, you can be walked through it relatively easily -- at least I can assist if using Windows...
simplepinoi177 said:
Have you tried going into Recovery Mode and factory resetting/wipe data there?
You wouldn't need an unlocked bootloader...
Also, you can try to sideload OTA images (using adb) and that also can be done in a locked bootloader...
you can find it below...
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
getting the computer to "recognize" the device for adb commands usually is just a matter of installing and applying the proper usb drivers (also found below)
https://dl.google.com/android/repository/usb_driver_r13-windows.zip
*if you are running Linux or MacOS, there's different resources for that...
If you need help, getting your computer to recognize your device, you can be walked through it relatively easily -- at least I can assist if using Windows...
Click to expand...
Click to collapse
Reset from recovery doesn't get past the error.
Can't use adb as device isn't recognized
USB drivers are up to date
But thanks anyway
weinbers said:
Reset from recovery doesn't get past the error.
Can't use adb as device isn't recognized
USB drivers are up to date
But thanks anyway
Click to expand...
Click to collapse
You haven't mentioned otherwise, so I'm just going to have to assume you are running a Windows machine...
Usually, the issue isn't that the USB drivers are up to date, but whether the Device Manager is correctly identifying the device (P7) and/or using the proper Google driver (rather than the repository Microsoft insists on using).
If you open Device Manager (when your device is connected to the computer and are in Recovery Mode [since having it connected in the initial Setup without USB Debugging probably is not going to allow it to show up in Device Manager]), is there any device that is "unknown" or has a yellow triangle, or even a mobile device but it is identified as anything other than "Android ADB Recovery Interface" (possibly under LeMobile Android Device)? If it is like that, then that identifies why your P7 is not being detected by adb; or if you do see it, then you know it's something other than a device driver issue....
@weinbers How did you roll back from A14? Have you tried another computer?
bobby janow said:
@weinbers How did you roll back from A14? Have you tried another computer?
Click to expand...
Click to collapse
Yeah...I had the same wonder...I'm curious on how he did it with a locked bootloader...
As I recall, there are certain points or beta versions where that's the only time you can opt out of the "beta program"; I just figure it was that situation. A bit of research shows that it flashes/installs OTA from non-beta to rollback.
I'm pretty sure it's a driver issue (adb device not being recognized), so maybe another computer might have some luck...
bobby janow said:
@weinbers How did you roll back from A14? Have you tried another computer?
Click to expand...
Click to collapse
yes
weinbers said:
yes
Click to expand...
Click to collapse
How did you rollback? OTA from Beta? Did you at least flip the OEM toggle? Fastboot devices shows what? When you say in the OP "downloaded the latest stable 13 os via system setup" what exactly do you mean?
simplepinoi177 said:
Have you tried going into Recovery Mode and factory resetting/wipe data there?
You wouldn't need an unlocked bootloader...
Also, you can try to sideload OTA images (using adb) and that also can be done in a locked bootloader...
you can find it below...
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
getting the computer to "recognize" the device for adb commands usually is just a matter of installing and applying the proper usb drivers (also found below)
https://dl.google.com/android/repository/usb_driver_r13-windows.zip
*if you are running Linux or MacOS, there's different resources for that...
If you need help, getting your computer to recognize your device, you can be walked through it relatively easily -- at least I can assist if using Windows...
Click to expand...
Click to collapse
Checked/tried all that (drivers installed and fine) - nada
bobby janow said:
How did you rollback? OTA from Beta? Did you at least flip the OEM toggle? Fastboot devices shows what? When you say in the OP "downloaded the latest stable 13 os via system setup" what exactly do you mean?
Click to expand...
Click to collapse
Yes, OTA from exiting the beta program, basically just like a factory reset from a stable operating system. Fastboot devices shows my device but can't do anything.
weinbers said:
... using the official google cable that came with the phone.
Click to expand...
Click to collapse
Try using an A to C cable using a USB 2.0 port and see if your computer recognizes the device so you can sideload an OTA.
weinbers said:
Yes, OTA from exiting the beta program, basically just like a factory reset from a stable operating system. Fastboot devices shows my device but can't do anything.
Click to expand...
Click to collapse
What do you mean can't do anything? Have you looked at all these fastboot commands? https://technastic.com/fastboot-commands-list/ ? I'm assuming you never toggled the OEM switch, correct? If that was not available to you why did you install an unstable beta as per all the reports currently knowing you might not be able to recover? Nonetheless, there are a ton of fastboot commands you can use to recover your system so forget adb for now since your adb debugging is not available to allow adb commands. So what does the fastboot unlock command report back?