I successfully rooted using teletype's guide Shield Android TV rooted from this forum, combined with Tutorial: Root Shield Android TV 500GB (Marshmallow) from the Nvidia Shield Zone website. I think the main reason I had to borrow from the latter was that I could not get a cursor to load on the screen in TWRP using the file in the first guide, despite trying 4 different types of mice. Also, there was something in it about drivers which helped I think.
I was able to use Market Helper fine a few days ago but when I tried last night it told me it could not activate as the device was not rooted.
Did this happen because of an update and is there anyway to avoid this happening in the future while still receiving updates?
Can I re-root without having to reconnect my laptop up again?
Hello experts!
First off I do admit I have cross posted some information here. Perhaps I should have just asked here first. As a lot of research I have been doing lead me here. I am also aware of the XY problem. So I am giving what information I have on my problem and what I have done to resolve it. In a nutshell I need to recover app data from internal storage.
So here is yet another story of a dropped Samsung Galaxy BSOD. The broken screen of death! :-o
So I dropped my phone and the screen broke, fixed it then put on a screen protector that fractured the new screen in my pocket, of all things. Through that it spiraled out and it needed a new LCD as well as screen which failed to repair as LCD remains blank now. I suspect the display controller has somehow fried. Decided to give up and buy a new phone.
My broken phone is a Core Prime G360G. The digitizer doesn't respond. The LCD is blank. The side buttons, volume, power and home, work fine.
The good news. It turns on and technically still works. It has no screen lock. I can plug it in to computer via USB and it mounts over MTP. I can also install apps remotely (so to speak) from another computer from the Play site. I've installed Samsung Switch this way. Switch does work and I managed to back up files from the Windows program which is good but in my case it isn't smart enough as it doesn't back up app data which I need. I also have AirDroid installed and can reach it that way I but didn't enable mirroring before the incident. Trying to use that to download an app (~10MB in my case) just results in the browser stalling.
The bad news. It is not rooted. It has stock standard firmware. USB debugging is not enabled. Last time I tested OTG wasn't supported. At least not for OTG USB sticks.
So in effect it's rooted without being rooted! Yes, i know, I know, Android rule of thumb; before you accidentally drop your phone, even without planning it, and not being a seer, enable USB debugging for no apparent reason! It all makes sense now.
I've spent the last two weeks reading forums all over the place, blogs and watching videos about how to recover data with a broken screen. And in almost all cases they tell you to enable USB debugging. Well that's nice advice and about as useful as advising someone with a broken toilet to sit down, do their business and then flush it! And is met with equally crappy commentary pointing the conundrum out.
My computer has Windows (Vista) and Linux (Mint 64). I read all about ADB and installed this on both Windows and Linux. And tried to talk to it that way with adb and fastboot which failed. I then read of Samsung devices being different, with a download mode, and using this Odin or Heimdall program. So I could "see" the process I tested with my new phone (a J5 Prime as it happens) and learned I needed to use download mode and how to enter it on boot. Recovery mode didn't work as expected. Heimdall was the only program that would work. I managed to view the PIT on my J5. Odin did see my phone but I found the interface harder to work with at first.
I tried on my Core. Blindly got it into download mode. Heimdall could see it. But the transport was buggy as I kept getting USB errors. I ended up removing it then compiling Heimdall v1.4.2 from source. This worked better, even though it was giving empty bulk transfer warnings, but it managed to download the PIT file. So at this point I can blindly get my Core into download mode and am able to communicate with it using Heimdall.
This is where I am at. I would prefer it if a screen mirroring app could be installed that would load up and activate remotely when a client run on my computer is loaded up. I don't care if it is VNC or how it connects. But it would need to load itself up on the phone and work without needing intervention on the phone and without USB debugging. If there is an emergency mirroring app on the Play store or even an APK that can be installed remotely, using AirDroid or any other means, I would be happy to test it. I'd write one myself if knew how to write an app! LOL.
If USB debugging could be enabled by any remote means then I am welcome to hear how. It opens a window to possibility. But a window that is hard to open if it's locked.
So I would prefer to keep this at the app level if possible. Since apps can help. But if need be as long as it doesn't destroy data I am willing to install a custom recovery image. It looks like I will need to do this as I have exhausted all other possibilities. At least, when I read of the latest broken screen mirroring app, there is always a catch of it needing debugging or activating on the phone.
Although there is support for other Core Prime variants, support for my specific G360G model seems to be lacking. The information I read looks vague at best. I read about CWM and TWRP. But on the TWRP site, although there is Core Prime images, nothing is listed for exactly a G360G. There is no point to me flashing TWRP recover image only to find it doesn't work and I have bricked recovery mode. I'd look like a right twerp!
So guys, after all the info I have given you, what's the next step? Thanks.
Okay so just an update here. I have some good news and bad news on my part. I've been hacking around with customising recovery and modifying compatible recovery images in order to get debugging activated.
The good news is I got USB debugging enabled. The bad news is my computer is unauthorised.
I'm stuck at this point. I updated the adb_keys file with what was on my computer and it won't budge. I finally get somewhere and now I've once again hit a wall. This is just so annoying. :-x
The final countdown. After months of cracking and hacking I've broken in! I modded my hack to create the needed folder just to be sure and updated my RSA key. Applied the firmware patch and let it reboot. Even while booting I knew something was different. The digitizer started responding to my touch and making water noises. Which was strange as I never noticed it doing that before.
I issued an adb command and it was accepted. I could then browse around the system. I already had screen mirroring software installed and all it needed was USB debugging working and suddenly it worked. This was a blessing as I found that trying to do other things like going into a root shell or do an adb backup caused a requester to come up on screen. Had I not been able to satisfy that on a virtual screen I would have run into the same trap of circles I had just climbed out of. Having a rooted phone with no root access.
I was then able to install a backup app and extract the data out. Hooray! I had actually installed it from Google Play site remotely but found there was no space for it and it had failed. But the account said it was installed. With a view to a mobile I could then remove another app and install it from Play on the phone itself. Given how well this worked once I learned what was needed to be done I suppose I should make up a guide. An automated script to create an ADB patch wouldn't go far astray.
Hello Everyone,
I am having lots of issues with rooting my ZC550KL. Used both the Asus Utility Unlocking tool (The APK does not install even though the unknown sources option has been enabled) and the Fastboot hangs while looking for a connected device. I have had used the Google USB Driver on Windows and the Phone is recognised, also tried this on Linux and still no luck..
Can someone help me with any other fresh Ideas on how I can get this sorted? I have had used the latest Update from Asus and updated to marshmallow. Also not sure if I can downgrade back to 5.0.2 which was the original Firmware this phone was shipped with.
Really appreciate any feedback.
After a few hours of digging, I've ended up flashing the stock Lollipop Image and now I am finally rooted..
Hey guys,
there are some SM-T230NW available via ebay. They come from BMW 7 series cars with their feature called "Touch Command".
I bought one of those off ebay and thought I might be able to remove the BMW-branded OS, set a neutral boot screen and use it as a normal tablet.
My problem is, I cannot flash a new recovery via odin (security check fail), and I do not know how to root such a device.
Can anyone help me with that?
Edit: I forgot one thing: It has knox enabled.
Woud you still have you BMW touch tablet?
Hey! This is my first time here, sorry if I'm doing smth wrong, I just really need help. My fossil gen 6 is kinda useless at this point after updating to Wear OS 3 and I would like to flash it back to Wear OS 2, since I don't get any notifications & I can't even sync my notes at this point without connecting to wifi (not even through mobile data, which is pretty annoying -> my phone & watch doesn't connect to each other through bluetooth)
thanks, for any guides in advance!
night
You will have to perform a factory reset and repair the watch and phone again. Only option at the moment.
edwin270 said:
You will have to perform a factory reset and repair the watch and phone again. Only option at the moment.
Click to expand...
Click to collapse
Did that 3 times already, nothing changed. Thanks for your answer though!
Did you get anywhere with this? I also want to go back to wear os 2. I hate the fossil app
I'd like to know too. I just came back to Android with the S23 Ultra and wanted to pair my Razer x Fossil watch to it. But I decided to update since I was doing a factory reset/disconnect anyways. Big big BIG mistake.
There has to be a way to flash wear OS 2.3 back to the watch and re partition it as stock. I'm able to see my watch as a USB perhp on my machine without BT or wifi connection.
Anyone have the old firmware for these watches? Short of buying another Razer watch for $600
I do have all the required files to go back to wearOS 2, but wont suggest it might brick your device. Have a partition backup first.
For OTA add the hash in the placeholder.
Main URL: https://redirector.gvt1.com/packages/data/ota-api/package/<hash_with_extension_here>
v2.30: 230d380c72f87f94cbd4e43b944afd70700d6ffd.zip (Apply updates from playstore regarding wearOS to get it upto 2.38)
Minor Update: 4e201fee66e76ed4694e77eaa589f7767f93beea needs to applied after flashing the above package.
V3: a569fe07dfdcb4edea85f9535d592b9af4621cd1.zip
Malvik said:
I do have all the required files to go back to wearOS 2, but wont suggest it might brick your device. Have a partition backup first.
For OTA add the hash in the placeholder.
Main URL: https://redirector.gvt1.com/packages/data/ota-api/package/<hash_with_extension_here>
v2.30: 230d380c72f87f94cbd4e43b944afd70700d6ffd.zip (Apply updates from playstore regarding wearOS to get it upto 2.38)
Minor Update: 4e201fee66e76ed4694e77eaa589f7767f93beea needs to applied after flashing the above package.
V3: a569fe07dfdcb4edea85f9535d592b9af4621cd1.zip
Click to expand...
Click to collapse
Hey ! Thanks for the file. I'll take the risk to brick my watch.
Do you know how I can flash the archive ?
MiamKebab said:
Hey ! Thanks for the file. I'll take the risk to brick my watch.
Do you know how I can flash the archive ?
Click to expand...
Click to collapse
I'm also looking to be able to flash my watch between WearOS 2 and 3. Have you figured anything out by chance? All the things I normally do aren't working, with and without TWRP.
Malvik said:
I do have all the required files to go back to wearOS 2, but wont suggest it might brick your device. Have a partition backup first.
For OTA add the hash in the placeholder.
Main URL: https://redirector.gvt1.com/packages/data/ota-api/package/<hash_with_extension_here>
v2.30: 230d380c72f87f94cbd4e43b944afd70700d6ffd.zip (Apply updates from playstore regarding wearOS to get it upto 2.38)
Minor Update: 4e201fee66e76ed4694e77eaa589f7767f93beea needs to applied after flashing the above package.
V3: a569fe07dfdcb4edea85f9535d592b9af4621cd1.zip
Click to expand...
Click to collapse
Or would you be able to provide some guidance on how to proceed?
Arkbird1000 said:
I'm also looking to be able to flash my watch between WearOS 2 and 3. Have you figured anything out by chance? All the things I normally do aren't working, with and without TWRP.
Click to expand...
Click to collapse
From what I found, the original cable with 4 spins (2 on each side) should be used to connect your watch to a PC and use the USB debugging.
So I bought one but nothing happened. I'm just able to use Bluetooth or WiFi debugging and these can't be used to unlock the bootloader as WiFi and Bluetooth are disabled on bootloader mode. So fastboot can't detect the watch.
So I'm stuck and that sucks, my duck.
Another way is to remove the watch's back and tweak the USB connectors but I'll not do that...
MiamKebab said:
From what I found, the original cable with 4 spins (2 on each side) should be used to connect your watch to a PC and use the USB debugging.
So I bought one but nothing happened. I'm just able to use Bluetooth or WiFi debugging and these can't be used to unlock the bootloader as WiFi and Bluetooth are disabled on bootloader mode. So fastboot can't detect the watch.
So I'm stuck and that sucks, my duck.
Another way is to remove the watch's back and tweak the USB connectors but I'll not do that...
Click to expand...
Click to collapse
I see. I have been able to make it farther, but I also was running into problems getting the USB connection to work. Most of what I did was under Linux instead of Windows but I found that after enabling USB debugging I often had to remove the watch from the cradle, put it back on, then run 'adb devices' from the connected computer to get the daemon going. That usually got the adb popup on the watch to show, then I can select the 'always allow' option.
All that said, at the moment I'm not currently able to boot my watch unless I have the bootloader unlocked. I have restored the stock recovery after using TWRP and unsuccessfully flashing anything via that adb shell or from the bootloader with fastboot. Even worse, some things are not working properly, such as automatic brightness and some of the wireless capabilities. I might need to see if I can work something out with Fossil if I'm unable to resolve these issues.
You guys seems way ahead on me in the downgrade process...
I made Wear OS 3 update but the Fossil app used to pair the watch won't work with Oneplus 8 Pro (Android 13), gotta go back but i have no idea how...
Yet i flashed a lot of custom roms and stuff in the past, but now.. kinda lost
Im looking forward to see news here
Good luck guys, i'll keep updated if i somehow manage to flash the OTA posted ahead
Edit : well i was on Apkmirror to try an older apk of the app, and found out their app targets android 12 but not android 13..........
Arkbird1000 said:
I see. I have been able to make it farther, but I also was running into problems getting the USB connection to work. Most of what I did was under Linux instead of Windows but I found that after enabling USB debugging I often had to remove the watch from the cradle, put it back on, then run 'adb devices' from the connected computer to get the daemon going. That usually got the adb popup on the watch to show, then I can select the 'always allow' option.
All that said, at the moment I'm not currently able to boot my watch unless I have the bootloader unlocked. I have restored the stock recovery after using TWRP and unsuccessfully flashing anything via that adb shell or from the bootloader with fastboot. Even worse, some things are not working properly, such as automatic brightness and some of the wireless capabilities. I might need to see if I can work something out with Fossil if I'm unable to resolve these issues.
Click to expand...
Click to collapse
I do have the TWRP but need to find it, took some tweaks from Ticwatch 3 pro. I didnt pushed it on the repo tho. I didnt what made me do it, but I wiped my system partitions and had to rebuilt from the OTA only. But after getting the watch working again, I had few functionalities broke, including the OTA updates. If you can social enginner your way thru fossil to get files such as stock rom and other files for qualcomm software like rawprogrammer and firehose files it can be great help.