Related
The instructions on are for Windows with twrp etc, .exe files... I've rooted Samsung Phones on my Mac, but this tablet seems different from what I'm reading and don't want to screw it up lol. I read a few different things on twrp on Macs and a lot of issues people ran into, unless they did something wrong?? Basically I just want to know how to root and use twrp on Mac with this tablet so I can use other roms I've used on my phones (currently Sho3).
Thanks in advance for any help
115 views and nobody?? lol ... searching online it seems there are multiple ways (unless people wrote instructions differently) for similar on a Mac. I just want to make sure I don't screw this tablet up, I've done my Samsung phones on my Mac.
How were you doing them on a Mac? What was the process, I mean.. I would imagine that you could use Heimdall and load the TWRP image with it, in order to get the custom recovery, then root/install SU after that on the device.
I'm not sure if Heimdall is actually going to work with the gt3, but it's worth a shot.. It's the only cross-platform image writer, for Samsung devices, that I know of. I could be wrong, however.
Edit: here's the link for it: http://forum.xda-developers.com/showthread.php?t=755265
foil said:
How were you doing them on a Mac? What was the process, I mean.. I would imagine that you could use Heimdall and load the TWRP image with it, in order to get the custom recovery, then root/install SU after that on the device.
I'm not sure if Heimdall is actually going to work with the gt3, but it's worth a shot.. It's the only cross-platform image writer, for Samsung devices, that I know of. I could be wrong, however.
Edit: here's the link for it: http://forum.xda-developers.com/showthread.php?t=755265
Click to expand...
Click to collapse
Sorry forgot about this, yeh used Heimdall. I may try later on.
1. Install most recent Heimdall from http://forum.xda-developers.com/showthread.php?t=755265
2. Open Heimdall frontend from applications folder of your Mac.
3. Put device into download mode with power+vol down+home. Will sometimes require multiple attempts. When successful you will see warning about adding custom software to your device.
4. Click utilities tab of Heimdall and detect device.
5. Download pit file to your Mac with the save as dialouge.
6. Click on flash tab of Heimdall.
7. Select pit file you just created
8. Hit add partition select RECOVERY and then select the custom recovery you have already dowloaded from the other threads. Extract to .img before selecting the recovery though. Make sure repartition is NOT selected
9. I unchecked no reboot and resume. (Near bottom right by the start button)
10. Hit start.
11. Verify by restarting with power+vol up
Check my other post at http://forum.xda-developers.com/showthread.php?p=47060381#post47060381 for screenshots describing these steps. And possibly some answers to questions already asked in that thread.
Just did this to mine and it worked fine is OSX 10.9 & Heimdall 1.4.0 and the TWRP_T31x_r3.tar recovery. I should note that this is the SM-T310 8" Tab
zibrah3ed said:
1. Install most recent Heimdall from http://forum.xda-developers.com/showthread.php?t=755265
2. Open Heimdall frontend from applications folder of your mac.
3. Put device into download mode with power+vol down+home.
4. Click utilities tab of heimdall and detect device.
5. Download pit file to your mac with the dave as dialoge.
6. Click on flash tab of heimdall.
7. Select pit file you just created
8. Hit add partition select RECOVERY and then select the custom recovery you have already dowloaded from the other threads. Extract to .img before selecting the recovery though.
9. I unchecked no reboot and resume.
10. Hit start.
11. Verify by restarting with power+vol up
Just did this to mine and it worked fine is OSX 10.9 & Heimdall 1.4.0 and the TWRP_T31x_r3.tar recovery. I should note that this is the SM-T310 8" Tab
Click to expand...
Click to collapse
Thanks a lot for the steps. But I'm getting an error. It says Initialising protocol...
ERROR: Protocol initialisation failed! at the last step where I'm flashing the recovery. Could you please help me? I did exactly as you said.
Thanks.
EDIT: also, I'm on OSX 10.9 as well, and using all the same versions as yours.
---------- Post added at 04:30 PM ---------- Previous post was at 04:20 PM ----------
sw6lee said:
Thanks a lot for the steps. But I'm getting an error. It says Initialising protocol...
ERROR: Protocol initialisation failed! at the last step where I'm flashing the recovery. Could you please help me? I did exactly as you said.
Thanks.
EDIT: also, I'm on OSX 10.9 as well, and using all the same versions as yours.
Click to expand...
Click to collapse
NVM, I got it to work. Searched on google, and someone had the same problem with heimdell and he just rebooted and tried next day or something. So I rebooted and it worked.
Good to hear you got it working. Not a lot of people around to help on this tablet.
Sent from my HTC6500LVW
zibrah3ed said:
Good to hear you got it working. Not a lot of people around to help on this tablet.
Sent from my HTC6500LVW
Click to expand...
Click to collapse
Awesome it worked. Didn't get a chance to do so yet, was honestly a little nervous even though I've used Heimdall on Mac for phones. There's like no support or anything for this tablet, not sure why, it's selling like crazy, BB can barely keep them in stock and it's been out for months. Yet other newer tablets have huge support already and roms etc.
Love it, but kinda wish I got something else now, only thing you can do is root this thing.
surf1 said:
Awesome it worked. Didn't get a chance to do so yet, was honestly a little nervous even though I've used Heimdall on Mac for phones. There's like no support or anything for this tablet, not sure why, it's selling like crazy, BB can barely keep them in stock and it's been out for months. Yet other newer tablets have huge support already and roms etc.
Love it, but kinda wish I got something else now, only thing you can do is root this thing.
Click to expand...
Click to collapse
With Cyanogen not building stable releases for Exynos 4 devices I don't think we will see a ton of action on the AOSP front for this device. With that being said Xposed works on this tablet and provides some of what I'm looking for in custom roms. I use Wanam and Gravity Box modules and I am happy now with stock rooted and using Xposed.
zibrah3ed said:
With Cyanogen not building stable releases for Exynos 4 devices I don't think we will see a ton of action on the AOSP front for this device. With that being said Xposed works on this tablet and provides some of what I'm looking for in custom roms. I use Wanam and Gravity Box modules and I am happy now with stock rooted and using Xposed.
Click to expand...
Click to collapse
yeh I wish we had roms like my i777, I've stuck with Shostock on it, and the phone is so smooth and fast and stable.
zibrah3ed said:
Good to hear you got it working. Not a lot of people around to help on this tablet.
Sent from my HTC6500LVW
Click to expand...
Click to collapse
I just realized I still have Heimdall 1.3.1 still on my Mac, as I'm still on 10.5.8 , I don't think the newer versions of Heimdall work unless on the current OS/X as one says there are issues with 10.6 etc. Wonder if I can still use 1.3.1?
surf1 said:
I just realized I still have Heimdall 1.3.1 still on my Mac, as I'm still on 10.5.8 , I don't think the newer versions of Heimdall work unless on the current OS/X as one says there are issues with 10.6 etc. Wonder if I can still use 1.3.1?
Click to expand...
Click to collapse
Reading the change logs from 1.3.1>1.3.2>1.4.0 compatibility with some devices was enhanced/added. It does not mention ours specifically. I personally wouldn't try it on 1.3.1 but it is your tablet. Why are you stuck on Leopard? PPC?
zibrah3ed said:
Reading the change logs from 1.3.1>1.3.2>1.4.0 compatibility with some devices was enhanced/added. It does not mention ours specifically. I personally wouldn't try it on 1.3.1 but it is your tablet. Why are you stuck on Leopard? PPC?
Click to expand...
Click to collapse
I just never updated it after they cut support for 10.5.8 to keep buying OS after that lol, I've had other MBP and just sold my Retina, too many glitches and odd stuff with the recent OSs, and waiting to see the new model that should have some nice fixes both hardware wise and software. Plus I use Win7 in a virtual system and it's so stable, Virtuals have run into so many issues on the newer OSs from peoples reports and my experience. Only thing is I know people say you can use that to root these easier, I've never gotten any phone to show up to work with in Win in a Virtual System, plug usb in and nothing happens (still goes to OS/X). I only kept this 13" Pro as it's reliable and stable lol, even spilled a big ass jug of water on it once when the dogs when crazy chasing each other and one got caught on my cord and knocked the water over onto the keyboard. I flipped it over and turned it off and stuck it in rice, somehow works fine.... my good luck charm hahaha
Wonder if the new Heimdall (1.4) will work on os/x 10.5.8? I'll msg the dev
zibrah3ed said:
Reading the change logs from 1.3.1>1.3.2>1.4.0 compatibility with some devices was enhanced/added. It does not mention ours specifically. I personally wouldn't try it on 1.3.1 but it is your tablet. Why are you stuck on Leopard? PPC?
Click to expand...
Click to collapse
So I totally forgot about this thread as there was no rom development anyway. Now there are some nice roms for this tablet so want to root and flash. Except can't figure this out, I tried different Heimdalls and they all do the same thing, they say "heimdall crashed" when opened up, but the program is there. When you click on detect devices it says "FRONTEND ERROR Heimdall Crashed".
I messaged the Dev but never heard back. On os/x 10.5.8 and tab is T310 wifi. Some say this Heimdall works for these devices but not on osx version whatever, then vice versa..... ughh confusing lol. No clue what heimdall works with this combo or if there's another way on a Mac. I have Win7 in a virtual machine, but Android never mounts in a VM or at least I've never gotten an Android to do so all these years.
I got this error when I try to download the .pit file:
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!
Click to expand...
Click to collapse
Any ideas?
The device I try to root it's a Tab3 7.0 SM-T211 with Android 4.1.2
This method doesn't work for me either.
I'm on Ubuntu 14.04 and using Heimdall 1.4.0.2
I've tried uploading TWRP 2.6.3, 2.7.0 and 2.7.1
I've tried using ADB too, but to no avail. It seems that the only mode I can get ADB to work is sideload, but when I sideload images it says signature failed. I'm starting to hate this phone.
EDIT: Somehow, after 12 attempts, it worked!!! (with TWRP 2.7.1 flashable recovery)
I came upon this device on Christmas (a gift from my girlfriend to her father) and wanted to root it and also install clockworkmod recovery, so I could mess with it a bit without bricking it. Since I found a lack of tailored guides for it, I decided to write this one, although I really did no actual development whatsoever. Normally I would be posting this on general, but given the spirit of this forum, I guess I'll just leave it here. Also, keep in mind I don't have the device anymore and am writing this from memory. If I missed anything or you have any doubts, please let me know (for example, I can't recall specifically the drivers I installed to make it work properly).
Please, please read the whole guide before trying anything, and if you are a novice user, just leave this be, I don't want you to turn your tablet into a paperweight because of my shoddy instructions written from memory and you probably don't need any of this anyway as there are no custom roms yet.
!!!DISCLAIMER!!!: As stated above, anything you do is at your own risk. I provided the procedures that worked for me on a Qilive 97r tablet, which is an Auchan branded ARCHOS 97b Platinum HD, so my step by step should work for all of you. There are probably easier ways to do this, and I hint at them in the guide, but beware I have not tried them and cannot vouch for them. In fact, I cannot and will not take any responsability if you brick your device following these instructions, correctly or otherwise. You do this at YOUR OWN RISK. You have been warned!
Rooting:
I followed this guide on Windows 7 x64 and it worked perfectly.
So thanks to dhigby for that. I would just like to make a couple of remarks:
When you get to step 7 (Installing Superuser by ChainDD), don't. Install SuperSU by Chainfire instead, Use it to update the superuser binary (I think a prompt shows up) and when asked, let it delete the "other" superuser applications, that is, the chinese one. Clean and easy, you don't need to follow any more steps.
Congratulations, you now have (english language) root!
Clockworkmod Recovery:
There is no specific recovery for this device. Fortunately, thanks to AndroTab.info, there's a generic version for 3188 devices that you'll see should work quite nicely, albeight with some caveats.
What works:
Nandroid backup to/from external SDCard (won't recognize internal)
Installing zip files should also work, although I didn't try it at the time, as the device wasn't mine and I can't since I don't have it anymore, but since it mounts system partitions perfectly well I wouldn't think there would be a problem. Try it at your own risk though.
Other things probably work, give it a try.
What doesn't work:
Internal SDCard access
Probably other things
Installation:
Now that you have a rooted tablet, installing clockworkmod recovery is easy-peasy. Go to developer options and enable USB Debugging, then make sure you have a working adb daemon (look it up) that recognizes your tablet.
NOTE: I'm not sure if I had to install any specific drivers for this to work, I think if so they were installed while rooting by the chinese app. Anyhow, here's the Rockchip drivers, you might want to try to install them if you can't get a connection: http://www.rockchip.nl/downloads/
Download the file RK30GENERIC_CWM.zip from here - that's the recovery.
Now extract flash_image and recovery.img from the downloaded file above to the folder where you have your adb and follow the following commands.
Push the files to /dev partition on the device:
Code:
adb push flash_image /dev/
adb push recovery.img /dev/
Then enter root shell, like so:
Code:
adb shell
su
Now flash recovery.img into recovery partition with flash_image:
Code:
chmod 755 /dev/flash_image
/dev/flash_image recovery /dev/recovery.img
Now power off your device. To enter recovery press volume down then the power button and keep them pressed until CWM boots. Voilá!
NOTE: The instructions above were adapted from here and all credit goes to AndroTab.info ; I posted these particular instructions because they are the ones I used and worked for me; there are other methods listed on that page which might or might not work, TRY THEM AT YOUR OWN RISK.
Backing up your original recovery (for warranty, if anything goes wrong, etc.)
To obtain a backup image of your recovery \ restore it back afterwards, follow this guide here. All credit goes to Originalas.
Don't follow it to the letter though: first and foremost, you need a working linux installation. If you don't have one, I recommend Wubi.
Then:
Follow step 1;
Ignore step 2 (it's outdated);
Follow 3;
Follow 4 - but don't expect the screen to turn on, it won't, just hold the volume down button for 10 seconds or so after plugging it in, don't press the power button!
Ignore 5, 6 and 7
Follow 8, but don't use the last command to flash the CWM recovery onto the device. This is because since it is a generic version, it relies on the original recovery kernel. Flashing the image like stated in step 8 would probably overwrite the kernel and result in no recovery at all (I might be wrong about this).
Do follow the last command to restore your own backup if you ever need to.
I am unsure if recovery dumps obtained in this way are device specific; I don't see a reason why they should be, so I'll provide you with my own backup:
ORIGINAL RECOVERY
Flash through any method of your choice, but keep in mind I haven't tried this on other devices, so, as you know by now DO IT AT YOUR OWN RISK.
Closing remarks:
There you have it. Sorry for not holding your hand through every step, but this is meant for people who know a bit of what they're doing, making it faster than having to look up and figure out all these things and quirks on their own. If you have any doubts don't hesitate to ask, but keep in mind I don't have the device anymore and don't know much more than what I have written here. I do appreciate feedback and corrections, and will gladly change the guide giving you full credit - if it's really urgent just PM me, I might not check this thread often.
Cheers!
thanks, works like a charm...do you have any news about updates\custom roms? I can't find anything even in the archos main site
Jammed_Death said:
thanks, works like a charm...do you have any news about updates\custom roms? I can't find anything even in the archos main site
Click to expand...
Click to collapse
I wouldn't keep my hopes up on custom roms. The software is really bad and what it does with the hardware is terrible. It's like a bunch of chipmunks put the code together by randomly typing into a keyboard.
That said, the likelihood of a new kernel to fix that is next to nil. However, since the ROM is as far as I can tell pretty near stock, you can get a pretty good experience from the device by installing gravity box xposed module. I also recommend trickstermod and changing the governor to performance, as well as some kernel tweaking if you know what you are doing.
Also, very important, limit the amount of processes running in the background to 3 in dev settings or change the used memory limit to something like 1.2 gb. It has 2 gb of RAM, but, as I said, the ROM sucks, the system eats away a full gigabyte, and it doesn't effectively kill background apps, leaving you with a sluggish device if you multitask.
Anyway, those are just some ideas, if you have some more or would like to code for this device, feel free to share Also, as I always say, give it time. You never know who is gonna get they're hands on the device and do something amazing with it.
Newbleeto said:
I wouldn't keep my hopes up on custom roms. The software is really bad and what it does with the hardware is terrible. It's like a bunch of chipmunks put the code together by randomly typing into a keyboard.
That said, the likelihood of a new kernel to fix that is next to nil. However, since the ROM is as far as I can tell pretty near stock, you can get a pretty good experience from the device by installing gravity box xposed module. I also recommend trickstermod and changing the governor to performance, as well as some kernel tweaking if you know what you are doing.
Also, very important, limit the amount of processes running in the background to 3 in dev settings or change the used memory limit to something like 1.2 gb. It has 2 gb of RAM, but, as I said, the ROM sucks, the system eats away a full gigabyte, and it doesn't effectively kill background apps, leaving you with a sluggish device if you multitask.
Anyway, those are just some ideas, if you have some more or would like to code for this device, feel free to share Also, as I always say, give it time. You never know who is gonna get they're hands on the device and do something amazing with it.
Click to expand...
Click to collapse
hi and thanx for the answer
yes i saw that it's almost stock but crappy optimized...in the very first start of the tablet i had 1.8gb occupied by nothing and clean master always notifies me that 90% of the ram is busy...meh
maybe just a kernel will fix like you say but you know, android 4.4 will be a must (rockchip already released sdk for 3188). I am not a coder (totally zero) but i will try your suggestion...just a question about the performance governor, does it drain more battery?
i am trying to backup my rom but cwm is so buggy...first was impossible, now i'm stuck on backing up boot image
there is a twrp available for this tablet?
solved
ehy can someone provide a stock rom for the qilive 97r? I'm using a omni 4.4.4 but i want to rever back
thank you
Dump stock ROM QiLive 97R
Jammed_Death said:
ehy can someone provide a stock rom for the qilive 97r? I'm using a omni 4.4.4 but i want to rever back
thank you
Click to expand...
Click to collapse
Yes, i have one. How could i send to you?
Could we change your Omni stock ROM by mine?
I have tried ROM Archos 97b Platinum but touch screen is not working. The only possibiliti to work is by a USB Mouse.
Many thanks.
Redinpais said:
Yes, i have one. How could i send to you?
Could we change your Omni stock ROM by mine?
I have tried ROM Archos 97b Platinum but touch screen is not working. The only possibiliti to work is by a USB Mouse.
Many thanks.
Click to expand...
Click to collapse
you can upload it on mega or gdrive or something like that
for the omni come here, http://forum.xda-developers.com/showthread.php?t=2310818
author thread with links and guides I think you can even try the fixes with your current rom but better ask oma
about the cwm, there is a way to mount sdcard?
Dump stock ROM QiLive 97R
Jammed_Death said:
you can upload it on mega or gdrive or something like that
Click to expand...
Click to collapse
Here he are...
https://www.wetransfer.com/download...556a9cf8fdbc6ddd7ab35ab820141126224717/09298e
Is only available until Decenber, 3 ,so Download it now.
Jammed_Death said:
for the omni come here, http://forum.xda-developers.com/showthread.php?t=2310818
author thread with links and guides I think you can even try the fixes with your current rom but better ask oma
Click to expand...
Click to collapse
I've been watching but I can not understand. Is confused. There are many files and do not know what to do to "fix".
If you are Portuguese, I would like to talk to you on Skype.
Can be?
Jammed_Death said:
about the cwm, there is a way to mount sdcard?
Click to expand...
Click to collapse
I don´t know how I can answer that. I'm new in android, so I sorry.
Jammed_Death said:
thanks, works like a charm...do you have any news about updates\custom roms? I can't find anything even in the archos main site
Click to expand...
Click to collapse
Try this. Sooooooooo beautiful.:good:
(Because this - "To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!" i can not put link now. So ask me by Skype) SORRY
:victory:
Follow the instrutions ther and enjoy KK 4.4.2 Oma ROM Iron KK v1.2 - 24-05-2013 (My QiLive say now - Nexus 7 :angel:
Regards
Qilive 97r
Hi guys , if any body can help me with my tablet Qilive 97r, when I tryed to install new rom via RK development tool there was an error, and my tablet do not booting any more, just black display, do not know what to do, maybe somebody know where I can download original rom , and original installer, I will be thankful for that's.
Denysorlyk said:
Hi guys , if any body can help me with my tablet Qilive 97r, when I tryed to install new rom via RK development tool there was an error, and my tablet do not booting any more, just black display, do not know what to do, maybe somebody know where I can download original rom , and original installer, I will be thankful for that's.
Click to expand...
Click to collapse
I'm interested
please ROM stock
Hello, i need help , if somebody know where I can download original rom , and original installer, I will be thankful for that's.
I have this device, but right now I am unable to root and twrp it because of warranty but I really want to build a ROM for it and we have the sources so I really want to do it. Any beta testers would be frickin amazing.
So, building asteroids and syncing with latest sources and also trying to fix bluetooth is my main goal here.
First test build is complete! Link: [urlhttp://www.mediafire.com/?0c0xusva0z5e0[/url]
That is the link to a folder containing 2 files, an ext4 file and a fastboot file.
To flash it, make sure your bootloader is unlocked
This will only dual boot the software, because it is just a test and in case it'd mess anything up, it won't affect the watch.
Once you've downloaded the files and put them into your adb and fastboot folder, enable adb debugging (obviously huehuehue).
Once that is all done, don't switch off your watch, leave it in android wear and make sure that adb detects it (adb devices and it should say authorized next to it).
Run adb push -p /location/to/file/asteroid-image-tetra.ext4 /sdcard/linux/rootfs.ext4 (pushes the file to the virtual sdcard)
Once that is done, reboot to bootloader by running adb reboot bootloader.
Then, once you've sure made that fastboot recognizes it (fastboot devices), do fastboot boot /location/to/zImage-dtb-tetra.fastboot
If you want to try and overwrite your current android wear installation, do fastboot flash, however I don't recommend this.
Good luck! Oh, and as a sidenote, since this isn't android wear, the android wear app won't work and I am surprised that bluetooth even works (if it does, report it here!).
RAZERZDAHACKER said:
I have this device, but right now I am unable to root and twrp it because of warranty but I really want to build a ROM for it and we have the sources so I really want to do it. Any beta testers would be frickin amazing.
Please, either send me a pm or write here on this thread and I'll try to release a flashable zip asap
Click to expand...
Click to collapse
Hi
I'm always open for some beta testing. In what direction of development where you thinking? A themed stock, or something radical?
amunarjoh said:
Hi
I'm always open for some beta testing. In what direction of development where you thinking? A themed stock, or something radical?
Click to expand...
Click to collapse
Not themed stock, sure they're great for some people but I am not a huge fan of them so I will obviously not make one. Right now I am compiling resurrection remix for my phone but I might try later on and get a compiled version
RAZERZDAHACKER said:
I have this device, but right now I am unable to root and twrp it because of warranty but I really want to build a ROM for it and we have the sources so I really want to do it. Any beta testers would be frickin amazing.
Please, either send me a pm or write here on this thread and I'll try to release a flashable zip asap
Click to expand...
Click to collapse
I am willing to be a beta tester
Alright, stay tuned. Building rom right now, also getting instructions for how to flash it (I don't think it is a simple twrp flash, not sure, we need some tester to confirm that).
RAZERZDAHACKER said:
Not themed stock, sure they're great for some people but I am not a huge fan of them so I will obviously not make one. Right now I am compiling resurrection remix for my phone but I might try later on and get a compiled version
Click to expand...
Click to collapse
That sounds interesting. Looking forward to further development
Build finished after a couple of hours. Since I am new to this whole android wear thing, I am a bit confused as to which files to flash, but I assume it is the one that is the largest and has the correct file format, right? So here is where the beta tester thingy comes into place. I am still experimenting on flashing the rom (the flashing method can be a bit confusing for new people) so I am planning on coding a toolkit that does all of that for ya, but the main thing is that I use linux and I don't really have a windows machine available to test this and quickly be able to change some things in the code (or either the rom files and then pack em up) so if someone is willing to perhaps skype or something similar where they can test such things that would be amazing, since I don't believe that a lot of people are running linux and want to flash this particular rom for this particular device etc.
Enough ranting! Here comes the rom link! http://www.mediafire.com/?0c0xusva0z5e0
That is the link to a folder containing 2 files, an ext4 file and a fastboot file.
To flash it, make sure your bootloader is unlocked
This will only dual boot the software, because it is just a test and in case it'd mess anything up, it won't affect the watch.
Once you've downloaded the files and put them into your adb and fastboot folder, enable adb debugging (obviously huehuehue).
Once that is all done, don't switch off your watch, leave it in android wear and make sure that adb detects it (adb devices and it should say authorized next to it).
Run adb push -p /location/to/file/rootfs.ext4 /sdcard/linux/rootfs.ext4
Once that is done, reboot to bootloader by running adb reboot bootloader.
Then, once you've sure made that fastboot recognizes it (fastboot devices), do fastboot boot /location/to/file.fastboot.
If you want to try and overwrite your current android wear installation, do fastboot flash, however I don't recommend this.
Good luck! Oh, and as a sidenote, since this isn't android wear, the android wear app won't work and I am surprised that bluetooth even works (if it does, report it here!).
Doesn't boot for me get stuck at the Smartwatch 3 screen then reboots in to wear.
niai_mack said:
Doesn't boot for me get stuck at the Smartwatch 3 screen then reboots in to wear.
Click to expand...
Click to collapse
Thanks for trying, and you followed the instructions here I assume. I'll try to compile a new one today (I got some interesting warnings when compiling)
Aye I followed to the tea, put it in /sdcard/linux/ with the name rootfs.ext4 then booted with the supplied fastboot file.
You do know there's the official release from the dev of Asteroid OS that works without any issues (meaning it boots and functions as expected, minus the bugs), right? In case you didn't, here it is: https://asteroidos.org/install/
I get that you're trying to do something new, and I'm all for it. I'm just posting this here, in case anyone else was curious. It's been out for quite a while now, almost a year by my reckoning.
Bluetooth does not work though, blame Broadcom.
Some extra info. When you fastboot boot the kernel from Asteroid OS, it loads the system that you earlier pushed to your internal memory using adb. You can run the (barebones) OS till your next reboot. Once you reboot, you'll be taken back to Android Wear itself, and you have to reflash the kernel to go back to Asteroid.
niai_mack said:
Aye I followed to the tea, put it in /sdcard/linux/ with the name rootfs.ext4 then booted with the supplied fastboot file.
Click to expand...
Click to collapse
Can you perhaps try "adb push -p /location/to/file/rootfs.ext4 /sdcard/linux/rootfs.ext2" ? Thanks.
I can test as well
d_crossfader said:
I can test as well
Click to expand...
Click to collapse
Sweet, I assume you pretty much know what to do. Can you also test the above mentioned flashing method? So you're replacing the vritual sdcard with ext2 instead of 4.
drakonizer said:
You do know there's the official release from the dev of Asteroid OS that works without any issues (meaning it boots and functions as expected, minus the bugs), right? In case you didn't, here it is: https://asteroidos.org/install/
I get that you're trying to do something new, and I'm all for it. I'm just posting this here, in case anyone else was curious. It's been out for quite a while now, almost a year by my reckoning.
Bluetooth does not work though, blame Broadcom.
Some extra info. When you fastboot boot the kernel from Asteroid OS, it loads the system that you earlier pushed to your internal memory using adb. You can run the (barebones) OS till your next reboot. Once you reboot, you'll be taken back to Android Wear itself, and you have to reflash the kernel to go back to Asteroid.
Click to expand...
Click to collapse
Missed your reply. Correct, and I am aware of that. Just that I want to get into android wear development so I decided to build this from source and perhaps eliminate the bluetooth thing and maybe even have it as a permanent rom instead of android wear, just saying. It'd be pretty cool, though not the most practical thing ever.
RAZERZDAHACKER said:
Missed your reply. Correct, and I am aware of that. Just that I want to get into android wear development so I decided to build this from source and perhaps eliminate the bluetooth thing and maybe even have it as a permanent rom instead of android wear, just saying. It'd be pretty cool, though not the most practical thing ever.
Click to expand...
Click to collapse
Having it permanent is easy. All you'd have to do is fastboot flash the kernel as opposed to fastboot boot.
The Bluetooth thing is almost impossible to fix, it's due to the blobs from bcm. Unless you're proficient at reverse engineering complex code, it's pretty hard.
drakonizer said:
Having it permanent is easy. All you'd have to do is fastboot flash the kernel as opposed to fastboot boot.
The Bluetooth thing is almost impossible to fix, it's due to the blobs from bcm. Unless you're proficient at reverse engineering complex code, it's pretty hard.
Click to expand...
Click to collapse
I can always try :/
RAZERZDAHACKER said:
Sweet, I assume you pretty much know what to do. Can you also test the above mentioned flashing method? So you're replacing the vritual sdcard with ext2 instead of 4.
Click to expand...
Click to collapse
I can do the steps on the first page, not sure about replacing the virtual sd though
d_crossfader said:
I can do the steps on the first page, not sure about replacing the virtual sd though
Click to expand...
Click to collapse
What you're doing on the first page is basically moving the files and flashing them from the virtual sd card so all I ask is if it doesn't work to change the last number in the adb command from a 4 to a 2
RAZERZDAHACKER said:
What you're doing on the first page is basically moving the files and flashing them from the virtual sd card so all I ask is if it doesn't work to change the last number in the adb command from a 4 to a 2
Click to expand...
Click to collapse
cool, will try in a few
Problem: Unable to install TWRP via ODIN. I try to flash the device with the twrp-3.1.1-0-picassowifi.img.tar using ODIN, I get the following errors during the boot recovery step Home+VolUP+Power:
Could not do normal boot.
ODIN Mode
Product name: SM-T525
Current binary: Custom
System status: Custom
Knox Kernel Lock: 0x0
Knox warranty VOID: 0x1
Qualcomm Secureboot: Enabled (CSB)
AP SWREV: S1, T1, R1, A1, P1
Write protection: Enable
UDC Start
I am able to reinstall KitKat back to its original state using ODIN each time which helps alot.
The tablet was in the following state prior to the TWRP installation:
I did a factory reset back to original Kitkat version 4.4.2
Samsung account: No
Google account: Yes
Installation Preparation Steps
Downloaded following files:
LineageOS 14.1,
open_gapps-arm-7.1-nano-20201223
ODIN v3.14.4
Samsung USB Drivers v1.7.31.0
Auto-Root-picassolte-picassoltexx-smt525
twrp-3.1.1-0-picassowifi.img.tar
Installation Steps:
Tested if recovery mode is working prior to installing twrp: Done Successful
Installed USB drivers on your PC
USB Debugging was enabled on device by pressing build number 7 times in settings
Developer options: Activated USB Debugging
Disabled bootloader: not done (not sure how to do it and if it is required)
Rooted device via ODIN: Done successfully (Auto Reboot and F. Reset Time flags checked)
Disabled KNOX via SuperSU
Tested if recovery mode is still working after root: Done Successful
Installed TWRP image via ODIN: Status PASS (Auto Reboot flag unchecked, F. Reset Time flag checked)
Booted into TWRP Recovery using HOME+ Vol UP + Power button
The last step is where the error occurs and TWRP recovery mode did not start.
I tried multiple versions of TWRP, but all attempts failed.
I installed TWRP via play store on the tablet and selected the .img file for my device via the TWRP tool. Although the tool was able to flash the device (stated that the flash was successful within the tool), when I try to enter device recovery mode, I get the same error: Could not do normal boot.
Any idea what could be wrong? Am I missing a step, permission issue?
I would appreciate any hint
thx
Sal
Isn't the T525 the picassolte?
Seems to me you're using the wrong TWRP.
bmwdroid said:
Isn't the T525 the picassolte?
Seems to me you're using the wrong TWRP.
Click to expand...
Click to collapse
There are 2 types of T525, wifi and lte. I have the wifi version.
Sal60 said:
There are 2 types of T525, wifi and lte. I have the wifi version.
Click to expand...
Click to collapse
Well, if you say so.
But I think you're wrong.
wifi=t520 lte=t525
And why did you use Auto-root for lte?
bmwdroid said:
Well, if you say so.
But I think you're wrong.
wifi=t520 lte=t525
And why did you use Auto-root for lte?
Click to expand...
Click to collapse
Thanks for the help. Before I reached out to you, I tried my best to gather all the info to upgrade to LineageOS. Rooting the device was one of the steps. I got the file for t525. I did not think about wifi or LTE. I see now that it makes a big difference.....thx. I'm rather new to the rooting and upgrading a device approach.
Strange, I doubled checked the package. It doesn't say anywhere about LTE - only wifi. But I checked the imei on imei.info and noticed that it is a LTE model. I bought the tab in 2014 and I guess I bought the lte model. This explains alot.
I will try the lte version of twrp.
thx again
I tried the lte version of twrp and I was able to enter into recovery mode. Thanks for the excellent tip.
I guess I need to do more homework on twrp and the whole process. I also got lucky on using the right root file. Because I almost made a huge mistake with rooting, I think I need to take a step back and do more research. I want to make sure that I have a complete image of my tablet just in case I take a wrong turn. I believe twrp is the right tool to do that. Any suggestions on the steps which I need to do?
Initially when I first started to gather all the info and dowloaded the files, I also downloaded lineage-14.1-20201218-UNOFFICIAL-n2awifi.zip. It appears that this file is also for the wifi model. Is there a difference between wifi and lte for lineageos 14.1?
@Sal60 so we finally figured out what you really got .
The saving process is very easy in TWRP just use backup option and save EFS, Boot, System and Data.
Although the last three can easily be restored by flashing stock ROM via Odin.
DON'T flash any ROM which is not specifically designed for your model as danger of bricking will be increased by doing so.
bmwdroid said:
@Sal60 so we finally figured out what you really got .
The saving process is very easy in TWRP just use backup option and save EFS, Boot, System and Data.
Although the last three can easily be restored by flashing stock ROM via Odin.
DON'T flash any ROM which is not specifically designed for your model as danger of bricking will be increased by doing so.
Click to expand...
Click to collapse
Awsome, I backed up everything. I will need to do more research on the right ROM. Using the wifi version I downloaded of the Samsung Galaxy Tab Pro 10.1 is probably not the best way to go.
I see that LineageOS.org does not support my tab as of now and CyanogenMod no longer exist. Do you know of any other projects which might support my tablet?
@Sal60 as I don't own any T52* I've no idea what's going on in ROM development.
bmwdroid said:
@Sal60 as I don't own any T52* I've no idea what's going on in ROM development.
Click to expand...
Click to collapse
Thanks anyway
Sal60 said:
Thanks anyway
Click to expand...
Click to collapse
What about this one here:
[ROM][T525][UNOFFICIAL] LineageOS 16.0 | Android 9.0 Pie 20200229
I'm not responsible for any damage to your device of any sort. By flashing this you take responsibility of anything that happens. Process at your own risk! If you want to check firmware - please make backup. Better to store all partitions, at...
forum.xda-developers.com
Btw. I wouldn't mind, if you find and hit the "like" button
bmwdroid said:
What about this one here:
[ROM][T525][UNOFFICIAL] LineageOS 16.0 | Android 9.0 Pie 20200229
I'm not responsible for any damage to your device of any sort. By flashing this you take responsibility of anything that happens. Process at your own risk! If you want to check firmware - please make backup. Better to store all partitions, at...
forum.xda-developers.com
Btw. I wouldn't mind, if you find and hit the "like" button
Click to expand...
Click to collapse
@bmwdroid: thanks for the link. I will review the url. I completely understand the risk part. I rarely use my very expensive tab anymore because it is so old and more or less useless. Most apps do not work anymore. Samsung stopped updating the tab shortly after it was released.
Sorry about not hitting the like button.
I will update the post with the results after I do some research on the file.
Thanks.
@Sal60 I condemn Samsung for their update strategy as well.
That's why I will never ever again by a new device from them.
All my stuff is older than four years and on custom ROMs either on Nougat or even Q.
I bought them only after searching here for active devolopers.
@Sal60 the brilliant dev @Valera1978 brought out as a Christmas gift :
[ROM][T525][UNOFFICIAL] LineageOS 18.1 | Android 11 | 20210509
I'm not responsible for any damage to your device of any sort. By flashing this you take responsibility of anything that happens. Process at your own risk! If you want to check firmware - please make backup. Better to store all partitions, at...
forum.xda-developers.com
bmwdroid said:
@Sal60 the brilliant dev @Valera1978 brought out as a Christmas gift :
[ROM][T525][UNOFFICIAL] LineageOS 18.1 | Android 11 | 20210509
I'm not responsible for any damage to your device of any sort. By flashing this you take responsibility of anything that happens. Process at your own risk! If you want to check firmware - please make backup. Better to store all partitions, at...
forum.xda-developers.com
Click to expand...
Click to collapse
@bmwdroid I just seen this newly created ROM as well...thx. I checked both URLs. It seems a little complex. My only concern is understanding the technical side of the installations. I guess I have my work cut out for me.
Hi there. I'm trying a buncha roms to see which ones will run a particular app the dev is still polishing up. (It's called SDR++ and is a full-featured SDR receiver app for android)
Anyhow, over the course of flashing/reflashing and running RESTOCK on it - which is a fabulous set of utils for wannabe peeps like me - I have run into a strange error.
My tab is an N7 2013 16gb "flo", and lately I've noticed that a bunch of roms error out from TWRP with error #7, meaning TWRP somehow thinks the tablet isn't a "flo" - but it is. And yes, I triple check the roms I download to make sure they're NOT for a "deb."
How do I fix this or get around it? And be kind please, I really know zero about this stuff, but I *can* read and type.
Thanks for your expertise.
cranky_dan
Which recovery are you using ? There is one which renames the device to "flox". This recovery is required for flashing official LOS 18.1
MikiGry said:
Which recovery are you using ? There is one which renames the device to "flox". This recovery is required for flashing official LOS 18.1
Click to expand...
Click to collapse
Which recovery? TWRP pops up when I boot into recovery.
However, when I'm in fastboot, the device reports that it's "flo".
cranky