Ok first of all , i don't know if frp bypass stuff is allowed on xda anymore , because too much changed here and it's not same as it was before , but anyway ..
Tutorial is based on this video https://www.youtube.com/watch?v=gjU9C6xb_ps
but it only worked partially for me , so if you have trouble with unlocking that way , here is little bit more steps which will help you
Here is link to downloads : https://drive.google.com/drive/u/1/folders/12vVeqaEsuPEj2dPgIugA_Z4I-3AkPPhE
You'll need to install drivers first , then use that program
1) Reboot to bootloader mode
Turn OFF device, push vol down and then power button . after 2-3 sec release power button and you'll be in bootloader mode
2) start that Motorola_FRP
3) wait until 3rd or 4th restart when it asks for ADB Access.
4) First close that program and ONLY AFTER THAT Click OK on screen of phone
5) Go to your ADB folder , Open CMD( Just click on folder name and write cmd there ,then click enter)
Then use this command:
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
"If Above Command not Working Then Try This Command:
adb shell am start -n com.google.android.gsf.login/
If Above Command not Working Then Try This Command:
adb shell am start -n com.google.android.gsf.login.LoginActivity"
Then just reboot your device and you're good to go
I'm quite sure this will work with many other variants too, but i've tested this on my XT1776 , so ...
fastboot erase frp
thats it
Francesco Franz said:
fastboot erase frp
thats it
Click to expand...
Click to collapse
Really?
fastboot erase frp is even command?
I don't know if that's how it works on mediatek chipset , but i'm quite sure that won't work on qualcomm? maybe i'm wrong ...
jkjambo said:
Really?
fastboot erase frp is even command?
I don't know if that's how it works on mediatek chipset , but i'm quite sure that won't work on qualcomm? maybe i'm wrong ...
Click to expand...
Click to collapse
it will work if qualcomm variant has frp partition.
mtk variant already have one.
Francesco Franz said:
it will work if qualcomm variant has frp partition.
mtk variant already have one.
Click to expand...
Click to collapse
I didn't know that .
Don't really have time to test it right now , but i'm interested if qualcomm variant also can be reseted that way , i'm 90% sure it won't work , but still there is chance
jkjambo said:
Really?
fastboot erase frp is even command?
Click to expand...
Click to collapse
Yes. Its a commands. It depend on the type of partitions in your device. There are several threads floating around there in moto e4 dev. section related to this topic.
---------- Post added at 01:36 PM ---------- Previous post was at 01:35 PM ----------
jkjambo said:
I didn't know that .
Don't really have time to test it right now , but i'm interested if qualcomm variant also can be reseted that way , i'm 90% sure it won't work , but still there is chance
Click to expand...
Click to collapse
i owns a mediatek variant of E4 and it worked for me.
Francesco Franz said:
Yes. Its a commands. It depend on the type of partitions in your device. There are several threads floating around there in moto e4 dev. section related to this topic.
---------- Post added at 01:36 PM ---------- Previous post was at 01:35 PM ----------
i owns a mediatek variant of E4 and it worked for me.
Click to expand...
Click to collapse
We are running Qualcomm Owens and "erase" is not a terminal or fastboot command, I tried yesterday after a boo-boo.. ? When I used "fastboot rm -rf frp" cmd, it didn't protest.
bcrichster said:
We are running Qualcomm Owens and "erase" is not a terminal or fastboot command, I tried yesterday after a boo-boo.. When I used "fastboot rm -rf frp" cmd, it didn't protest.
Click to expand...
Click to collapse
fastboot erase partition_name
fastboot flash partition_name file_name.img
Hope you familiar with this.
---------- Post added at 06:58 PM ---------- Previous post was at 06:55 PM ----------
bcrichster said:
We are running Qualcomm Owens and "erase" is not a terminal or fastboot command, I tried yesterday after a boo-boo.. When I used "fastboot rm -rf frp" cmd, it didn't protest.
Click to expand...
Click to collapse
There's nothing like this *rm -rf* in fastboot.
Its a basic shell command to remove files.
If it didn't work than do this.
fastboot erase system
and then try to boot into system. you will get it.
Francesco Franz said:
fastboot erase partition_name
fastboot flash partition_name file_name.img
Hope you familiar with this.
Click to expand...
Click to collapse
You are absolutely correct, not that ya point that out [emoji23] I must've typo'd when I tried. Looks like I did it the hard work way outta frustration. [emoji28]
Running an Xp3r!meπt with my XT1776
Moto E4 Plus XT1776
My device hard brick Qualcomm please need blank flash file for Moto e4 plus xt1776 ????
Frp bypass March 1 2018-no PC needed just WiFi
Just did a bypass on the March 1 2018 security patch.sorry if there's no new information as I do these as a hobby and purposely don't look for answers on the web.
I do a lot of redundant things and useless steps in case I go down that rout. Like setting up Microsoft accounts in Gmail or turning the font size down, is for personal preferance.
If you would like a compleat list of steps in chronological order your sol. I do these once and done. I can only roughly give a Quinton Terintino style retelling of what happened.
(Skip all setup related screens that have a "skip" or "later" button)
basicly; from a freash factory reset! Talkback settings
Help&feedback
YouTube video share arrow
YouTube home page on YouTube app
YouTube settings
Google privacy policy
Google home page in Chrome app
FRP.f0il. C o m -best website ever
Link #1 (we'll come back for link #2)
*Sometimes you have to long press link1 and select gmail
Gmail set up skip but sometimes I've used a method you'd login with a Microsoft account oddly enough I use my Xbox 360 account info and it works (@yahoo.com lol)
in Gmail top right three dot menu -account management settings
youre probably in the system settings by now
Security settings
enable unknown sources
dissable all administration apps
(Useless here but most other times nessisary)
apps- show system- clear data and/or dissable all wizzards and/or things that say setup
(Do not press home button if it appears to light up at any time)
(End of useless crap)
carefully press back button until we reach FRP.f0il again
download link #2 and install the app
(The money shot)
the e4 is the only fone I've ever seen this on.
Ims settings (screen shot added)
provision phone - turn switch on (screen shot added)
change underwear
pull down notification settings
press the gear for system settings
goto backup&restore
FACTORY RESET
ERASE EVERYTHING
spike fone on ground
*not liable for broken device
your FRP has now been bypassed
good day to yous :itallianfingerpinch:
whats password for moto all frp then please
Related
Sorry To make a new thread, but I've been searching for some good instructions on how to flash a radio through fastboot. I know you can flash it through recovery but I'm hearing its safer to use fastboot.
All I need is a link with some instructions.
Thank you.
Code is in this post, beside the links: http://forum.xda-developers.com/showthread.php?t=1571715
mudferret said:
Code is in this post, beside the links: http://forum.xda-developers.com/showthread.php?t=1571715
Click to expand...
Click to collapse
I dunno what to do with that code. There isn't a beginners guide anywhere
Mrcojocaru said:
I dunno what to do with that code. There isn't a beginners guide anywhere
Click to expand...
Click to collapse
Do you know generally how to use Fastboot?
If you don't, you should probably start reading a bit more before using it...
martonikaj said:
Do you know generally how to use Fastboot?
If you don't, you should probably start reading a bit more before using it...
Click to expand...
Click to collapse
I dont know how. I think I used to to root my nexus one but I havent had to use it since. Just recovery.
Mrcojocaru said:
I dont know how. I think I used to to root my nexus one but I havent had to use it since. Just recovery.
Click to expand...
Click to collapse
Here's a good guide for setting up and using adb; mostly applicable to fastboot as well. There are others as well.
Can't recall if fastboot is included in the attached file, but the principles are there, and search the Development forum for "drivers".
http://forum.xda-developers.com/showthread.php?t=1058431
The full Android SDK can be DL'd as well: http://developer.android.com/sdk/index.html
mudferret said:
Here's a good guide for setting up and using adb; mostly applicable to fastboot as well. There are others as well.
Can't recall if fastboot is included in the attached file, but the principles are there, and search the Development forum for "drivers".
http://forum.xda-developers.com/showthread.php?t=1058431
Click to expand...
Click to collapse
thank you I have the adb drivers set up for my phone if thats what you mean. Just dont know more then that
ok I set up adb.. It was different than what I thought you were talking about.
If you have everything set up; boot in to bootloader, connect USB, and then use command in cmd.
Edit: but like someone said: if you don't fully understand, read more about it. Don't do something you're unsure of.
Sent from my Galaxy Nexus using Tapatalk
I understand it but I dont know what to type into cmd
Mrcojocaru said:
I understand it but I dont know what to type into cmd
Click to expand...
Click to collapse
download the radio you want
extract it or put the .img into your adb folder
open cmd (use the shortcut you created from the other post on setting up adb)
type this into the command line:
Code:
fastboot flash radio "name-of-radio".img
---------- Post added at 08:44 PM ---------- Previous post was at 08:43 PM ----------
the easiest way to set it up is download the tools in the dev forum. then use the guide with the pics to make the shortcut.
svtfmook said:
download the radio you want
extract it or put the .img into your adb folder
open cmd (use the shortcut you created from the other post on setting up adb)
type this into the command line:
Code:
fastboot flash radio "name-of-radio".img
---------- Post added at 08:44 PM ---------- Previous post was at 08:43 PM ----------
the easiest way to set it up is download the tools in the dev forum. then use the guide with the pics to make the shortcut.
Click to expand...
Click to collapse
when in command prompt you have to first navigate to your fastboot folder, my fastboot folder is in my android sdk folder so i would type
Code:
cd c:\android-sdk-windows\fastboot
then use
Code:
fastboot flash radio "name-of-radio".img
also your phone needs to be in the bootloader screen for fastboot to work. you can get to the boot screen by holding both volume buttons with the power button when the phone is off
thanks guys
I kept trying to flash a bad img. The OP from that thread posted a working one but not until the 3rd page. Got real frustrated lol.
anyway... im getting 2 solid bars of hspa inside. Used to alternate between 1 and 0.
neotekz said:
when in command prompt you have to first navigate to your fastboot folder, my fastboot folder is in my android sdk folder so i would type
Code:
cd c:\android-sdk-windows\fastboot
then use
Code:
fastboot flash radio "name-of-radio".img
also your phone needs to be in the bootloader screen for fastboot to work. you can get to the boot screen by holding both volume buttons with the power button when the phone is off
Click to expand...
Click to collapse
he would only need to navigate it if he used the old sdk way of setting adb up. if he used the link in the previous posts to create a custom shortcut, he wouldn't need to navigate.
also remember that your phone has to be booted into bootloader first. and after flashing, you need to fastboot reboot.
svtfmook said:
you need to fastboot reboot.
Click to expand...
Click to collapse
uh oh.. didnt do that. can something happen?
EDIT: I reflashed the radio and rebooted from fastboot just in case. Thanks for your help.
Thank you everyone! Used all my thanks for today on you guys lol
Hello Guys
I'am proud to present you the jackmu95 CWM Recovery auto-installer
In the moment the auto-installer is only available for the AT&T (D800) and the International (D802) LG G2. The Verizon variant will follow when I get the aboot.img for this device.
FEATURES
Multi platform support (Windows / OSX / Linux)
Fully automated recovery installation process
Choice between normal and touch recovery
Device check to avoid flashing on unsupported devices
Reboot into recovery option
REQUIREMENTS
Your phone has to be rooted
Installed LG mobile driver (Windows only)
Downloaded and extracted jackmu95 Recovery auto-installer
Enabled USB-Debugging
Accepted RSA Fingerprint message
INSTALLATION
Just run the install_recovery script and let the magic begin
DOWNLOADS
D800 (AT&T)
D802 (International)
CREDITS
ClockworkMod
CyanogenMod
Heatshiver
djrbliss
AndroidUser00110001
HOW-TO pull aboot.img
Because I only own the international version of LG G2 I need you help to support the other variants as well.
All you need to do is to follow the instructions below and sent me the aboot.img as PN.
HOW-TO pull aboot.img
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
chmod 644 /data/local/tmp/aboot.img
exit
exit
adb pull /data/local/tmp/aboot.img
Hey thanks for porting CWM to the G2!
However, im facing errors installing it. My G2 is the international G802 one (even went into settings just to check that) but the installer has been saying it is not compatible with my phone.
Nice!
I have loki enabled recovery images here http://androtransfer.com/?developer=AndroidUser00110001&folder=/recovery/D800/ for the ATT(800) version and Verizon(Vs980) version if you want to use them.
It would be awesome if you could add Telus (d803) to cwm!
https://dl.dropboxusercontent.com/u/68562258/aboot.img
Are you sure you're using the correct property to determine the model #?
I see in your installer the following:
device=`./adb shell getprop ro.product.device`
# Check if device is correct
if [[ "$device" != *d802* ]]; then
And my d802 shows this:
[email protected]:/ $ getprop ro.product.device
g2
[email protected]:/ $ getprop ro.product.model
LG-D802
Sent from my LG-D802 using Tapatalk
fanghan said:
Hey thanks for porting CWM to the G2!
However, im facing errors installing it. My G2 is the international G802 one (even went into settings just to check that) but the installer has been saying it is not compatible with my phone.
Click to expand...
Click to collapse
erraggy said:
Are you sure you're using the correct property to determine the model #?
I see in your installer the following:
device=`./adb shell getprop ro.product.device`
# Check if device is correct
if [[ "$device" != *d802* ]]; then
And my d802 shows this:
[email protected]:/ $ getprop ro.product.device
g2
[email protected]:/ $ getprop ro.product.model
LG-D802
Click to expand...
Click to collapse
Please download the installer again!
I fixed device detection by looking for the device name in the fingerprint instead of the ro.product.device property
d802
i think there is a "bug" when u press wipe cache it freezed or takes too long (more than 10 minutes) to wipe the cache -_- anyway i m gonna try to back my rom so i can test the speed . thanks anyway
---------- Post added at 12:23 AM ---------- Previous post was at 12:13 AM ----------
back seems to me very fast! only 2 min for 3giga back up -_- ! thats awesome ! hope u fix the wipe cache bug now keep up the good work
Also seeing "not compatible with your device".
on 802 int
dukat0s said:
i think there is a "bug" when u press wipe cache it freezed or takes too long (more than 10 minutes) to wipe the cache -_- anyway i m gonna try to back my rom so i can test the speed . thanks anyway
---------- Post added at 12:23 AM ---------- Previous post was at 12:13 AM ----------
back seems to me very fast! only 2 min for 3giga back up -_- ! thats awesome ! hope u fix the wipe cache bug now keep up the good work
Click to expand...
Click to collapse
I just provide the installer for the CWM Recovery and haven't anything to do with the development of the recovery itself
d802
jackmu95 said:
I just provide the installer for the CWM Recovery and haven't anything to do with the development of the recovery itself
Click to expand...
Click to collapse
oO my fault then! thanks , it work like a charm after a reboot ! thanks
MarkyG82 said:
Also seeing "not compatible with your device".
on 802 int
Click to expand...
Click to collapse
Can you please provide me the output of
Code:
adb shell getprop
so I can look into the problem.
shell getprop returns:
error: device offline
and adb devices returns:
List of devices attached
02a03a1bd84c6678 offline
I'm guessing this is the issue.
how can I get it online? running Linux Mint BTW
MarkyG82 said:
shell getprop returns:
error: device offline
and adb devices returns:
List of devices attached
02a03a1bd84c6678 offline
I'm guessing this is the issue.
how can I get it online? running Linux Mint BTW
Click to expand...
Click to collapse
It seems that you haven't accepted the RSA fingerprint message. Do you have a message on your phones screen when you use adb?
nope. all I got is the debug bug, and USB connection selection.
what does the fingerprint message look like? Toast or pop up?
MarkyG82 said:
nope. all I got is the debug bug, and USB connection selection.
what does the fingerprint message look like? Toast or pop up?
Click to expand...
Click to collapse
plug your phone into usb, in shell type adb devices, wake your phone if it is sleeping and you should have a notification to accept the fingerprint message.
So I did what you said and got nothing. For giggles I tried all the connection types and plugged unplugged between each.
never get any pop up or nowt.
MarkyG82 said:
So I did what you said and got nothing. For giggles I tried all the connection types and plugged unplugged between each.
never get any pop up or nowt.
Click to expand...
Click to collapse
But you have USB-Debugging enabled, haven't you?
yep. looked around for other tips and they all give similar advice to what I've tried. Not normally needed for linux but i'm gonna reboot my pc just in case.
@AndroidUser00110001 - If you have the aboot.img for ATT or VZW I can create the CWM recoveries for those models.
Hi,
I just bought a Huawei watch and I'm trying to install the preview. I've enabled ADB and whenever the watch is on, my computer can find it:
[[email protected] sturgeon-nvd83h]$ sudo adb devices
List of devices attached
MQB7N15C09000040 device
Click to expand...
Click to collapse
However, after I reboot to bootloader (adb reboot bootloader) the computer can't find it anymore:
[[email protected] sturgeon-nvd83h]$ sudo adb devices
List of devices attached
Click to expand...
Click to collapse
So I can't unlock the bootloader, and therefore I can't install the preview.
Is there something I'm missing? Thanks!
I've had it happen where when I type "adb devices" while in the watch bootloader and it doesn't show anything. But then I run the 2.0 preview batch file and it still flashes it fine. Did you try just running the batch "flash all" file anyway? If not try it. I've flashed the 2.0 preview probably 5 times in the less than 3 weeks I've had the watch and it's always worked.
Well, it's weird because when I run flash-all I get:
"FAILED (remote: device locked)"
Which implies that it has found the watch and has tried to actually flash the image, but of course, has failed because it's locked.
Yet, when I run fastboot flashing unlock I get:
"< waiting for any device >"
Which seems to mean it's not finding the watch.
OK, that's weird. Manually typing "fastboot oem unlock" didn't work; however, editing "flash-all.sh" and adding the command at the beginning DID work. I have no idea why, but it's now finally flashing the beta. Fingers crossed!
Did you unlock the bootloader? You have to unlock it before flashing. I used this guys tutorial when first learning how to unlock the bootloader and flashing the 2.0 preview and it worked great. https://www.youtube.com/watch?v=qVrBEmi35-E
If you have unlocked the bootloader I'm not quite sure why it wouldn't be seeing the watch if it's seeing it while the watch is in the OS which it clearly is since you're able to use adb.
---------- Post added at 09:53 AM ---------- Previous post was at 09:47 AM ----------
I just now seen your answer post after making my last comment. That is strange but I hope you got it working. That link I posted in my previous comment is the method I followed and I had no issues. Perhaps the reason I was able to do it without having to edit the script is because the guy in that video modified the files to work better. Watch the video and you'll see what I'm talking about.
NOTICE: Several users have reported issues downgrading from v7.2.x, so it might require some additional experimentation to downgrade from that version.
-
Missing your screenshot or twitch streaming functionality? Hate the new launcher layout w/ its tiny one row of icons and its numerous rows of psychologically-aggressive suggestion imposition?
Well, now you can stop cursing at Nvidia, because they provided a way (albiet, a highly technical and mostly-undocumented way), to load any version of their OS that you choose.
I've seen others wanting to downgrade (including myself), so I've collected the relevant steps which I used to successfully revert to an earlier version. This guide assumes a bit of technical working knowledge, so I apologize if you are one of the 'normal' people that Nvidia has bulldozed over...
All the usual "don't blame me for bricked devices" caveats apply.... please be careful, know what each step does! research each step!
Best of luck...
0 - prereqs
make sure your PC & nvidia shield are both plugged into a UPS, b/c a power failure during a flashing operation is not very pleasant.
make sure you have (or do get) the adb & fastboot binaries ("commands") for your computer
make sure that you get all your userdata off the device, because it will be erased by this process
1 - using a web browser
register for an nvidia developer account (which you will have an opportunity to do if you attempt the next step)
download the 6.3 'developer os' rom for your particular model
https: //developer.nvidia.com/shield-developer-os-images (sorry, noob filter won't allow the real/clickable url)
NB: The 6.3 developer rom for the 2017 console is missing the userdata.img, there are currently no reports (on this thread) if a different userimage (pre-6.3 or for the 2015 version) works on the 2017 console (testers welcome!).
NB: if the cost of being identified as a developer offends you (i.e. yielding a name, company, email, etc), then you can probably dig up a link to the roms in the comments or elsewhere on the xda forums.
2 - on the device
enable developer mode by clicking the 'build' entry in settings->info
enable usb debugging in settings->developer-options
plug it into your computer using the usb port furthest from the hdmi port
3 - in a terminal
unzip the downloaded rom & cd into the resulting directory
edit the 'flash-all.sh' script to add the following line just before the final reboot:
fastboot flash userdata userdata.img
#(this will add even more wall-time to the flashing process, but will clobber the already-erased newer 7.0 user partition data with the old)
adb reboot bootloader
fastboot oem unlock && ./flash-all.sh
NB: Now confirm your willingness to lose all your data. On the 2015 'pro' version of the console, this is accomplished by pressing (or holding) the nvidia logo 'button'... AND WILL TAKE NEARLY TWO HOURS. Others use the x/y/a/b buttons on the game controller connected to the usb port nearest to the hdmi port.
[... time passes ...]
NB: the 7.0 to 6.3 was a clean backstep for me, but if you are going between other versions, I can see that this script might stall in the middle if the device does not come back up with adb services available... in which case you will need to enter fastboot manually using a hardware method.
4 - Break TegraOTA
You have now flushed the correct version onto your device, but we can't complete the setup process... if you were to try, the final step would immediately and automatically start downloading & applying the latest (7.0) experience update! Therefore, we must neuter the updater itself.
Still in the terminal:
adb root
adb remount
adb shell
# now these commands are run in the adb shell (technically on the phone through the PC terminal)
# the first path was the right one for me, but I'm putting here all the paths known to me in case you are using a different version
rm -rf /system/priv-app/TegraOTA
rm -rf /system/app/TegraOTA
rm -rf /system/app/TegraOTA.apk
sync
reboot
5 - you should now be able to setup and pain-stakingly reconfigure your nvidia shield to the way it was before you blindly trusted an OEM update without doing extensive research beforehand.
PS: if you fear that netflix or amazon-video will at some point stop working because of this process, you might wish to "fastboot oem lock" the device (knowing that an unlock will erase your user-data, but having the developer rom means you can always get root access via adb).
I hope you find this useful.
Thanks! I will be trying this tonight! I miss 6.3 and PLEX is BROKEN in 7.0!
Any idea if this can be done without needing a controller? My buddy has a shield TV but bought it used without a controller.
rossbeck said:
Thanks! I will be trying this tonight! I miss 6.3 and PLEX is BROKEN in 7.0!
Any idea if this can be done without needing a controller? My buddy has a shield TV but bought it used without a controller.
Click to expand...
Click to collapse
Plex is NOT broken in 7.0 i use it everyday.
Builtfordtough1 said:
Plex is NOT broken in 7.0 i use it everyday.
Click to expand...
Click to collapse
I use it every day too... and since Plex v6.13, files fail to play after 3 seconds unless you run them a 2nd time.
It's a known issue that everyone is having due an acknowledged bug in exoplayer2 with certain containers like mkv. Since 7.0/oreo has plex v6.14 baked in as a system app, it's impossible to downgrade to v6.12 to get rid of the issue until Plex fixes it... and they've known about it for 2 months now. Since quantity has been their focus over quality lately, I'm not holding my breath for a fix.
The solution is to downgrade to 6.3, manually install plex v6.12, and turn off app updates.... so that's my plan.
rossbeck said:
Any idea if this can be done without needing a controller? My buddy has a shield TV but bought it used without a controller.
Click to expand...
Click to collapse
I think it depends on the model. AFAIK, the newer 2017 ones need a controller (or possibly a USB keyboard) to confirm the userdata partition wipe.
Osndok said:
I think it depends on the model. AFAIK, the newer 2017 ones need a controller (or possibly a USB keyboard) to confirm the userdata partition wipe.
Click to expand...
Click to collapse
Ahhh, good call. I'll have him try a usb keyboard.
doesnt work for me... i have a nvidia shield tv 2015. i tried with flash-all.bat
and im stuck after reboot. is there any other way?
crazyscow said:
doesnt work for me... i have a nvidia shield tv 2015. i tried with flash-all.bat
and im stuck after reboot. is there any other way?
Click to expand...
Click to collapse
What command did the script stop at? and how 'stuck' are you (i.e. can you get to fastboot?).
I imagine that if you started with the wrong rom, it would likely fail to boot.
thanks for the fast reply, i just manually installed it without the bat file
I went manually into the fastboot mode by unplugging the power pressing the power button and plugging it back in until fastboot mode comes.
then i typed
fastboot flash staging blob
fastboot flash boot boot.img
wait until the sound on windows comes then - adb devices
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
and then it booted
crazyscow said:
thanks for the fast reply, i just manually installed it without the bat file
I went manually into the fastboot mode by unplugging the power pressing the power button and plugging it back in until fastboot mode comes.
then i typed
fastboot flash staging blob
fastboot flash boot boot.img
wait until the sound on windows comes then - adb devices
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
and then it booted
Click to expand...
Click to collapse
How did you get past the forced update? I was able to flash 6.3, but it forces the update during setup and I don't have ADB access yet because usb debugging isn't turned on. Can't disable the OTA updates without it!
Basically I've successfully flashed 6.3 and am sitting at a working fastboot prompt. Not sure what to do from here.
rossbeck said:
How did you get past the forced update? I was able to flash 6.3, but it forces the update during setup and I don't have ADB access yet because usb debugging isn't turned on. Can't disable the OTA updates without it!
Basically I've successfully flashed 6.3 and am sitting at a working fastboot prompt. Not sure what to do from here.
Click to expand...
Click to collapse
Disabling the OTA update is step four, if ADB does not work, I would guess that you forgot to flash userdata.img in the previous step(s).
Osndok said:
Disabling the OTA update is step four, if ADB does not work, I would guess that you forgot to flash userdata.img in the previous step(s).
Click to expand...
Click to collapse
So you did what to get userdata.img? Created it in TWRP or something? It's not included with the recovery images... and this basically bypasses the OOBE/setup stuff?
Thanks man
rossbeck said:
you did what to get userdata.img? ... It's not included with the recovery images... and this basically bypasses the OOBE/setup stuff?
Click to expand...
Click to collapse
userdata.img is inside the ZIP from the nvidia developer website, as can be seen here:
Code:
$ jar tf nv-recovery-image-shield-atv-pro-6.3.0-dev_rooted.zip | grep user
nv-recovery-image-shield-atv-pro-6.3.0-dev_rooted/userdata.img
rossbeck said:
[the userdata.img] basically bypasses the OOBE/setup stuff?
Click to expand...
Click to collapse
No... not really. The userdata.img from the developer pack both (1) matches the 6.3 version (doesn't have any of the newer, potentially incompatible entries), and (2) has developer-mode & adb enabled by default.
So in addition to it probably just working better, flashing the userdata will let you get adb access, and thus break the OTA, and thus complete the setup w/o the update.
I thought it would boot up, but im still stuck on the android loading screen!
Ill try to reflash the rom again tonight.
update:
I got it to work now, without update having to update to 7.0.2
Code:
adb reboot bootloader
fastboot flash staging blob
fastboot flash boot boot.img
fastboot reboot
//waiting for nvidia logo and the Windows PC to make the connection noise
//otherwise you can check by typing
adb devices
// if it shows something then continue
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img
fastboot reboot
once it booted it up, i went thru the procedure of setting it up with my network and google account, then the window pop-up "downloading version 7.0.2" then i followed the guide in the first post
Code:
adb root
adb remount
adb shell
# now these commands are run in the adb shell (technically on the phone through the PC terminal)
# the first path was the right one for me, but I'm putting here all the paths known to me in case you are using a different version
rm -rf /system/priv-app/TegraOTA
rm -rf /system/app/TegraOTA
rm -rf /system/app/TegraOTA.apk
sync
reboot
after that it booted up into android 7 with not OTA update notification.
thank you!
hello, thanks for the contribution, but when decompressing the image of developer 6.3 of shield tv 2017 I do not know where to get the file userdata.img, could you give me where to get it?
lohengrim93 said:
when decompressing the image of developer 6.3 of shield tv 2017 I do not know where to get the file userdata.img, could you give me where to get it?
Click to expand...
Click to collapse
As I said in #13, I found the userdata.img inside the archive from nvidia (the 2015 "pro" version to be exact), and I don't know why it is missing from (at least) the 6.3 archive for the 2017 device.
If you are feeling adventurous, you can try downloading either of the 2015 zips, and use its userdata.img... maybe the 16gb one?
I would be eager to know if that works for you, since I'm unsure if the userdata.img can be mixed between different versions of the console...
JUST BE VARY CAREFUL to not mix up your directories and start flashing the wrong blobs & boots... that would be a recipe for a brickin', methinks.
crazyscow said:
I got it to work now, without ... having to update to 7.0.2
... i followed the guide in the first post...
after that it booted up into android 7 [without] OTA update notification.
thank you!
Click to expand...
Click to collapse
I'm quite pleased to hear that it worked for you... (my first success report!).
Adb root
When I attempt to run the adb root command it just errors on me at the end, do I need to have the shield booted into setup for it to work?
Insatiablejimmy said:
When I attempt to run the adb root command it just errors on me at the end, do I need to have the shield booted into setup for it to work?
Click to expand...
Click to collapse
You forgot to include (or even describe) the actual error message, so I can only guess as to what is wrong.
However, since "adb root" is the linchpin of the developer rom, I would assume that you did not flash a developer rom (or as indicated above concerning the 2017 model) are missing the "userdata.img", which could also cause this behavior.
Don't want to root your phone but you still want to tweak it? No trouble, you can still use adb shell to change a few settings.
-First, follow this guide to install ADB on your Windows PC: https://www.xda-developers.com/install-adb-windows-macos-linux/
-Then, you have to plug your phone to your PC with a USB cable.
-Finally, launch a command line and use this command:
Code:
adb shell settings put secure sysui_qs_tiles "Wifi,SoundMode,Bluetooth,RotationLock,Flashlight,Dnd,custom(com.android.settings/com.samsung.android.settings.qstile.PowerSavingTile),BlueLightFilter,Location,custom(com.samsung.android.app.aodservice/.settings.AODTileService),custom(com.samsung.android.smartmirroring/.tile.SmartMirroringTile),AirplaneMode,custom(com.sec.android.app.soundalive/.DolbyTile),WorkMode,MobileData,Hotspot"
We also may have a way to enable Call Recorder on our phone with ADB Shell but, I'm still trying to figure out how it could be done.
Nico3d3 said:
Don't want to root your phone but you still want to tweak it? No trouble, you can still use adb shell to change a few settings.
-First, follow this guide to install ADB on your Windows PC: https://www.xda-developers.com/install-adb-windows-macos-linux/
-Then, you have to plug your phone to your PC with a USB cable.
-Finally, launch a command line and use this command:
We also may have a way to enable Call Recorder on our phone with ADB Shell but, I'm still trying to figure out how it could be done.
Click to expand...
Click to collapse
This is great for a530w users cuz those icons are missing, thanks for sharing!
Even though i already found my own way with my systemui mod
---------- Post added at 04:30 AM ---------- Previous post was at 04:27 AM ----------
FOR FREEDOM MOBILE USERS AND OTHER CARRIERS THAT SUPPORT VOLTE
DO THIS AND EVEN VOLTE TOGGLE WILL SHOW
adb shell settings put secure sysui_qs_tiles "Wifi,SoundMode,Bluetooth,RotationLock,Flashlight,Dnd,custom(com.android.settings/com.samsung.android.settings.qstile.PowerSavingTile),BlueLightFilter,Location,custom(com.samsung.android.app.aodservice/.settings.AODTileService),custom(com.samsung.android.smartmirroring/.tile.SmartMirroringTile),AirplaneMode,custom(com.sec.android.app.soundalive/.DolbyTile),WorkMode,MobileData,Hotspot,VoLte"
thank me later
[/COLOR]I have the A530W from Fido, I tried and got this error
/system/bin/sh: syntax error: '(' unexpected
KAPABLE-K said:
[/COLOR]I have the A530W from Fido, I tried and got this error
/system/bin/sh: syntax error: '(' unexpected
Click to expand...
Click to collapse
You probably forgot a quotation mark. Please check cmd has been wrote correctly.
I figured it out, I had to do "adb shell" first then send the command and everything worked.
587.saboor said:
This is great for a530w users cuz those icons are missing, thanks for sharing!
Even though i already found my own way with my systemui mod
---------- Post added at 04:30 AM ---------- Previous post was at 04:27 AM ----------
FOR FREEDOM MOBILE USERS AND OTHER CARRIERS THAT SUPPORT VOLTE
DO THIS AND EVEN VOLTE TOGGLE WILL SHOW
adb shell settings put secure sysui_qs_tiles "Wifi,SoundMode,Bluetooth,RotationLock,Flashlight,Dnd,custom(com.android.settings/com.samsung.android.settings.qstile.PowerSavingTile),BlueLightFilter,Location,custom(com.samsung.android.app.aodservice/.settings.AODTileService),custom(com.samsung.android.smartmirroring/.tile.SmartMirroringTile),AirplaneMode,custom(com.sec.android.app.soundalive/.DolbyTile),WorkMode,MobileData,Hotspot,VoLte"
thank me later
Click to expand...
Click to collapse
Can i use it in a530f
Hovo01 said:
Can i use it in a530f
Click to expand...
Click to collapse
yes
I will not lost my warranty yes?
---------- Post added at 06:01 PM ---------- Previous post was at 06:01 PM ----------
587.saboor said:
yes
Click to expand...
Click to collapse
Thanks do you have other tweaks with adb
Hovo01 said:
I will not lost my warranty yes?
---------- Post added at 06:01 PM ---------- Previous post was at 06:01 PM ----------
Thanks do you have other tweaks with adb
Click to expand...
Click to collapse
you will not lose your warranty
no
[email protected]:~/Downloads/platform-tools-2$ sudo ./adb shell
jackpotlte:/ $ settings put secure sysui_qs_tiles "Wifi,SoundMode,Bluetooth,RotationLock,Flashlight, Dnd,custom(com.android.settings/com.samsung.android.settings.qstile.PowerSavingTil e),BlueLightFilter,Locati>
),custom(com.samsung.android.smartmirroring/.tile.SmartMirroringTile),AirplaneMode,custom(com.sec.android.app.soundalive/.DolbyTile),WorkMode,MobileData,Hotspot" <
jackpotlte:/ $
What can I expect here? I see nothing happen ... mac os as you can see
Robert978 said:
What can I expect here? I see nothing happen ... mac os as you can see
Click to expand...
Click to collapse
There is no output with that cmd. To see if it worked, check if you can now see the new toggles in Quick Panel.
Nico3d3 said:
Don't want to root your phone but you still want to tweak it? No trouble, you can still use adb shell to change a few settings.
-First, follow this guide to install ADB on your Windows PC: https://www.xda-developers.com/install-adb-windows-macos-linux/
-Then, you have to plug your phone to your PC with a USB cable.
-Finally, launch a command line and use this command:
Code:
adb shell settings put secure sysui_qs_tiles "Wifi,SoundMode,Bluetooth,RotationLock,Flashlight,Dnd,custom(com.android.settings/com.samsung.android.settings.qstile.PowerSavingTile),BlueLightFilter,Location,custom(com.samsung.android.app.aodservice/.settings.AODTileService),custom(com.samsung.android.smartmirroring/.tile.SmartMirroringTile),AirplaneMode,custom(com.sec.android.app.soundalive/.DolbyTile),WorkMode,MobileData,Hotspot"
We also may have a way to enable Call Recorder on our phone with ADB Shell but, I'm still trying to figure out how it could be done.
Click to expand...
Click to collapse
looking forward to that native call recorder...
can we enable fm radio app with this if it isn't there?