This thread has been deleted.
This thread has been deleted.
This thread has been deleted.
***** really really really reserved*****
Working w/ Root on a Mac (OSX Yosemite)
CONFIRMED: This works using AT&T (SM-R750A), OSX (Yosemite), VirtualBox and Windows XP. See this link for the driver setup I used on my Mac.
http://www.onebadkid.com/?p=6930
I also find that after factory reset, I still have root! Great job!
---
Also, I haven't been able to get the scripts to work in the virtual machine so I've just been "pushing" the files manually. I did open up the scripts to get the destinations for the various files, so thank you OP. Also, you have to have the Tizen Wearables SDK installed and then use SDB commands in the terminal.
Remember, when using SDB on a Mac, it's: ./sdb [command] (you have to use the "dot-slash")
./sdb devices (to show whether or not your device is connected)
./sdb root on
./sdb shell (puts you into the device's shell so you can navigate the device in a Darwin/Linux terminal)
./sdb push [/full path of the file you want to upload to the device] [/full path of the desination]
I usually open up three Darwin/Linux Terminals on my Mac. One to use to navigate my watch in shell, the other to run the ./sdb command (just like in Windows, you have to run SDB on the mac from within it's home location: "/Users/[you]/tizen-wearable-sdk/tools"), and a third to drop files into so I can quickly see their full file path/location.
"PWD" = print working directory so you can use that in the Darwin/Linux Terminal so you don't get lost.
I'm using Windows 8.1 (don't know if it matters) but after updating to this driver my PC no longer recognized my Gear S. Had to roll back to previous driver.
Ohhhhh!!!
ohh SO installing these and getting it ready for the rest
Edit: got rootfs.img odin'd in so now i wait lmao
Wondering
Good write up so far. I had already gotten root from the previous thread with horrible direcions. LoL After I got my replacement gear s (ALWAYS CHECK YOUR SIM COVER), I rooted it using the bad direction method again (luckily I already know how to do these things), but your directions are very clear cut and noob friendly. You're doing a huge favor to new comers who come looking to root their gear. Hopefully they don't brick them before they find this.
cipherswitch said:
Got any request for certain alarms, notification sounds or ringtones? Shoot me a PM and I will get through them as fast as I can and repost here.
No themes as of yet, but I will definitely be working on custom clock faces apart from everything else
Click to expand...
Click to collapse
Reset my gear to factory to try out your method.
Odin'd over the root img and all went well after a few reboots (dont' turn off destination, installing new configuration, final reboot).
Watch reboots, open a command prompt and type "sdb root on" (Switched to'root' account mode)
sdb shell whoami
root
sdb shell setup-folder.sh
-1: /bin/setup-folder.sh: Permission Denied
I went and checked your .bat file and it uses the same command. The device says I have root but it's read only file system. I have been trying every trick I know the past half hour; any thoughts?
Megaflop666 said:
Reset my gear to factory to try out your method.
Odin'd over the root img and all went well after a few reboots (dont' turn off destination, installing new configuration, final reboot).
Watch reboots, open a command prompt and type "sdb root on" (Switched to'root' account mode)
sdb shell whoami
root
sdb shell setup-folder.sh
-1: /bin/setup-folder.sh: Permission Denied
I went and checked your .bat file and it uses the same command. The device says I have root but it's read only file system. I have been trying every trick I know the past half hour; any thoughts?
Click to expand...
Click to collapse
Do this
sdb root on
sdb shell
chmod +x /bin/setup-folder.sh
./bin/setup-folder.sh
Megaflop666 said:
Reset my gear to factory to try out your method.
Odin'd over the root img and all went well after a few reboots (dont' turn off destination, installing new configuration, final reboot).
Watch reboots, open a command prompt and type "sdb root on" (Switched to'root' account mode)
sdb shell whoami
root
sdb shell setup-folder.sh
-1: /bin/setup-folder.sh: Permission Denied
I went and checked your .bat file and it uses the same command. The device says I have root but it's read only file system. I have been trying every trick I know the past half hour; any thoughts?
Click to expand...
Click to collapse
Color me embarrassed. It seems in the final uploads, I nabbed the rootfs file that wasn't done yet. Uploading the new file now,sorry for the delay.
I reset, flashed the wrong one to confirm the issue then flashed the correct rootfs and confirmed it working. That was the issue, Im waiting for the new one to upload to mediafire now.
and yeah, I couldnt type this morning, totally freaking out.
cipherswitch said:
Color me embarrassed. It seems in the final uploads, I nabbed the rootfs file that wasn't done yet. Uploading the new file now,sorry for the delay.
I reset, flashed the wrong one to confirm the issue then flashed the correct rootfs and confirmed it working. That was the issue, Im waiting for the new one to upload to mediafire now.
and yeah, I couldnt type this morning, totally freaking out.
Click to expand...
Click to collapse
Its all good, I decided to tear into some things and bricked the damn thing, so I am sitting here waiting (forever) for the original firmware to download so I can factory restore it. I was not even able to get into recovery, just download mode. LoL
Oh well, if flashing the original firmware doesn't fix it, i'll take it up to Tmo at 10am and get a new one.
new rootfs uploaded as of 12/17/14 8:42 am est, I also updated the link in the writeup.
::::::Just a quick dirty write-up of how to load sounds with your newly rooted Samsung Gear S::::::
Since most folks are rooting their Gear S for the ability of adding Ringtones (which can be done via a pay app) and adding Notifications, Wallpapers, Watch Faces, you get it......
Once you have followed the awesome rooting guide contained here and you want to load some stuff:
Path for Ringtones:
/opt/share/settings/Ringtones/
Path for Notifications:
/opt/share/settings/Alerts/
Path for Wallpapers:
/opt/share/settings/Wallpapers/
Path for Alarm Sounds:
/opt/share/settings/Alarms/
I have placed both mp3 and off files and they both work fine. Sometimes when setting your applicable Alert/Notification/Ringtone and the file is a mp3, the sound will not play, no worries, it will when the Alert/Notification/Ringtone is invoked.
To load files (Choose appropriate folder listed above)
sdb root on
sdb shell ls /opt/share/settings/Alerts/ (Shows directory listing for /opt/share/settings/Alerts/ on the Gear 2)
sdb push NAMEOFFILE /opt/share/settings/NOTIFICATION_TYPE_FOLDER (ie /Alerts or /Ringtones)
Megaflop666 said:
Its all good, I decided to tear into some things and bricked the damn thing, so I am sitting here waiting (forever) for the original firmware to download so I can factory restore it. I was not even able to get into recovery, just download mode. LoL
Oh well, if flashing the original firmware doesn't fix it, i'll take it up to Tmo at 10am and get a new one.
Click to expand...
Click to collapse
It is SO hard to brick this device so you will be fine! If you get into the firmware failed to install screen you're still good to go. Like I said, I got to bootloops and thought it was dead but stock fixed everything.
No worries you're fine!
You'll be fine!
You will be fine. I've been able to restore from this screen using stock.
Um actually..... its easier. Connect your gear, drop your content into the right folders (eg; ringtones, alerts and such) and run the update script. done and done.
ipstack said:
::::::Just a quick dirty write-up of how to load sounds with your newly rooted Samsung Gear S::::::
Since most folks are rooting their Gear S for the ability of adding Ringtones (which can be done via a pay app) and adding Notifications, Wallpapers, Watch Faces, you get it......
Once you have followed the awesome rooting guide contained here and you want to load some stuff:
Path for Ringtones:
/opt/share/settings/Ringtones/
Path for Notifications:
/opt/share/settings/Alerts/
Path for Wallpapers:
/opt/share/settings/Wallpapers/
Path for Alarm Sounds:
/opt/share/settings/Alarms/
I have placed both mp3 and off files and they both work fine. Sometimes when setting your applicable Alert/Notification/Ringtone and the file is a mp3, the sound will not play, no worries, it will when the Alert/Notification/Ringtone is invoked.
To load files (Choose appropriate folder listed above)
sdb root on
sdb shell ls /opt/share/settings/Alerts/ (Shows directory listing for /opt/share/settings/Alerts/ on the Gear 2)
sdb push NAMEOFFILE /opt/share/settings/NOTIFICATION_TYPE_FOLDER (ie /Alerts or /Ringtones)
Click to expand...
Click to collapse
sbrownla said:
It is SO hard to brick this device so you will be fine! If you get into the firmware failed to install screen you're still good to go. Like I said, I got to bootloops and thought it was dead but stock fixed everything.
No worries you're fine!
Click to expand...
Click to collapse
I wasn't worried to begin with. It's dead, stock firmware flash didn't even fix it. New one will be here tomorrow afternoon. It'll be my third one since I first bought it done my kids drowned the first one. Lmao
Megaflop666 said:
I wasn't worried to begin with. It's dead, stock firmware flash didn't even fix it. New one will be here tomorrow afternoon. It'll be my third one since I first bought it done my kids drowned the first one. Lmao
Click to expand...
Click to collapse
Hm ... what was it doing when you tried to flash?!
I was working on changing some permissions, rebooted it and it never came back, don't even have recovery. From what tmo said, this has happened to other people on this watch
Related
Alright, so this is going to take a bit of explaining, please bear with me.
I got this phone a couple of weeks ago, subsequently rooted it, and shortly thereafter decided upon Viper for my ROM. After playing around for a bit, I took a look at Beastmode kernel yesterday. I backed up my phone, installed the new kernel, and everything went to hell shortly thereafter. Upon rebooting, my phone no longer detected a mounted SD card. Along with this, it also doesn't have working audio. I tried rolling back to my restoration point, but I cannot find it now. While digging through directories in recovery, I've found two things out.
1: There is now a storage/emulation/legacy folder with (almost) every folder that was in mnt/sdcard.
2: My restore point is gone, and I don't have the original kernel on my phone
I figured this wouldn't be THAT big of a problem, connect my phone to my PC, go into ADB and try to push the stock s-off kernel. Next set of problems.
1: /mnt/sdcard is showing as a non-directory, insists it doesn't exist.
2: storage/emulation/ shows as read only, and all lower subdirectories are coming up as not existing (I believe it to be an issue with folder naming, legacy is actually 0 on my file explorer on the phone, I think?).
Where I stand now::
At this moment, I have the HTC Droid DNA Toolkit running, the stock s-off Kernel, and a phone that doesn't cooperate with anything.
Also; I tried downloading the .zip directly on my phone, but because it doesn't think there's an SD card, it's refusing to let me download it. It lets me download apps from the market, though.
Any ideas?
PS! Forgot the biggest SNAFU in all of this. On my phone are about 200 pictures from my vacation which I hadn't put onto my computer yet because I am an imbecile. This is keeping me from wiping the phone down to brass tacks and starting all over. If someone can find a way for me to pull said pictures from my device, I can wipe it and see if that helps.
Killerkendolls said:
Alright, so this is going to take a bit of explaining, please bear with me.
I got this phone a couple of weeks ago, subsequently rooted it, and shortly thereafter decided upon Viper for my ROM. After playing around for a bit, I took a look at Beastmode kernel yesterday. I backed up my phone, installed the new kernel, and everything went to hell shortly thereafter. Upon rebooting, my phone no longer detected a mounted SD card. Along with this, it also doesn't have working audio. I tried rolling back to my restoration point, but I cannot find it now. While digging through directories in recovery, I've found two things out.
1: There is now a storage/emulation/legacy folder with (almost) every folder that was in mnt/sdcard.
2: My restore point is gone, and I don't have the original kernel on my phone
I figured this wouldn't be THAT big of a problem, connect my phone to my PC, go into ADB and try to push the stock s-off kernel. Next set of problems.
1: /mnt/sdcard is showing as a non-directory, insists it doesn't exist.
2: storage/emulation/ shows as read only, and all lower subdirectories are coming up as not existing (I believe it to be an issue with folder naming, legacy is actually 0 on my file explorer on the phone, I think?).
Where I stand now::
At this moment, I have the HTC Droid DNA Toolkit running, the stock s-off Kernel, and a phone that doesn't cooperate with anything.
Also; I tried downloading the .zip directly on my phone, but because it doesn't think there's an SD card, it's refusing to let me download it. It lets me download apps from the market, though.
Any ideas?
PS! Forgot the biggest SNAFU in all of this. On my phone are about 200 pictures from my vacation which I hadn't put onto my computer yet because I am an imbecile. This is keeping me from wiping the phone down to brass tacks and starting all over. If someone can find a way for me to pull said pictures from my device, I can wipe it and see if that helps.
Click to expand...
Click to collapse
Have you tried using an OTG cable to mount a flash drive? That's what I do when I backup/flash anything, I keep all my roms, kernels, backups, basically anything flashable on a flash drive, and use an OTG cable in CWM.
For the pictures:
Step 1; adb reboot recovery
Step 2; adb devices (to make sure it's detected)
Step 2.1: If your phone isn't detected, open sideload in recovery, adb devices again, then close sideload
Step 3: adb pull /sdcard/ C:\<username>\Desktop\sdcardbackup\
To fix everything else you'll probably need to wipe everything and flash a new rom.
EDIT: For future "snafus" the sdcard is on /sdcard/ not /mnt/sdcard/ because it's on internal memory, not mounted memory.
walther1337 said:
For the pictures:
Step 1; adb reboot recovery
Step 2; adb devices (to make sure it's detected)
Step 2.1: If your phone isn't detected, open sideload in recovery, adb devices again, then close sideload
Step 3: adb pull /sdcard/ C:\<username>\Desktop\sdcardbackup\
To fix everything else you'll probably need to wipe everything and flash a new rom.
EDIT: For future "snafus" the sdcard is on /sdcard/ not /mnt/sdcard/ because it's on internal memory, not mounted memory.
Click to expand...
Click to collapse
Well, I feel silly for that confusion. I've pulled everything from the sdcard, which honestly mattered more to me than fixing the phone. I'll putter around with getting the ROM and kernel operating correctly in the next couple of hours.
UPDATE!
Once I had the adb pull command corrected for me, pushing the new ZIP on there was an instant success in recovery. SD card exists correctly once again, installed Viper ROM over, full functionality once more.
Killerkendolls said:
Well, I feel silly for that confusion. I've pulled everything from the sdcard, which honestly mattered more to me than fixing the phone. I'll putter around with getting the ROM and kernel operating correctly in the next couple of hours.
UPDATE!
Once I had the adb pull command corrected for me, pushing the new ZIP on there was an instant success in recovery. SD card exists correctly once again, installed Viper ROM over, full functionality once more.
Click to expand...
Click to collapse
you can always do this too as long as the device is recognized by adb
Code:
adb shell
this will get you into the actual device where you can navigate around by using the " cd /dir_name " command and to go back up a dir use " cd .. " (a space and 2 "."s are needed) or just " cd " to get back to the starting point... if you know how to navigate through a unix terminal then you will know what to do here...
some other useful commands
Code:
ls, ls -a, ls -l, cd, cp, mv
ls = list (lists files/folders) "-a" means all, "-l" just makes it look neat and laid out better.
cd = change directory aka "dir"
cp = copy /path/to/file.ext /path/to/where/you/want/to/save/it/file.ext
mv = move (same as ^ ) except it just moves it and doesn't copy
oh and to exit adb shell just type "exit"
Honestly, just grab a working kernel. And use fastboot. Especially since you're s-off
fastboot flash boot boot.img should get you back in working order.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
I just bought this tablet today, and I wish to root it to run the Android OS 4.3 or higher. It won't let me play Magic 2014 and I can't successfully download the Google Play Store. Does anyone know anything about this who can help me? Would the rooting process be similar to other Double Powers?
Also just picked up a few of these for the kids. Noticed that it does not have google play or log in services. will have to push the apk and libs to the tablet after root has been granted
sketchle said:
I just bought this tablet today, and I wish to root it to run the Android OS 4.3 or higher. It won't let me play Magic 2014 and I can't successfully download the Google Play Store. Does anyone know anything about this who can help me? Would the rooting process be similar to other Double Powers?
Click to expand...
Click to collapse
I just got the same tablet for the kids, super cheap. I used kingo-android Root (just google "kingo android root cnet") it's super easy!:good:
Ah, damn it, I can help, but I can't post hyperlinks. I'll see what I can do. If this is hard to read, I hope some non-rookie will quote me and fix the links in the quote.
I picked one of these up on Black Friday for less than 50 bucks. Good times. It was a bear getting the Play Store not to crash every session. For quite a while I struggled with the Play Store seeming to run OK for a minute, then "Unfortunately Play Store has stopped" and back to the home screen. Clearing the cache and making sure the Download service was started didn't help. But now things are looking up.
I'm still running Android 4.2.2, which is what the tablet came with. I'm afraid I can't help you with finding a 4.3 rom.
Anyway, mgordon's suggestion of Kingo Root works as well as any. You can also use its bundled adb.exe to push the Play Store onto your tablet. To install a working Play Store, after rooting, follow these steps:
Get this Play Store APK: triple-w dot androidfilehost dot com /?fid=23203820527945029 (found [here](triple-w dot androidpolice dot com /2013/11/01/download-latest-google-play-store-4-4-22/#download))
Go to your Start Menu --> All Programs --> Accessories, and right-click on Command Prompt and choose "Run as Administrator."
In the command prompt window, navigate to adb supplied by Kingo Root. (cd "\Program Files (x86)\Kingo Android ROOT\tools") then continue with the following additional commands.
adb push \users\yourusername\Downloads\com.android.vending-4.4.22.apk /system/app/com.android.vending-4.4.22.apk
adb shell chmod 755 /system/app/com.android.vending-4.4.22.apk
adb reboot
Good luck!
I tried using the Kingo ROOT app, but mine just wont root. Ive rum it close to a dozen times now. Any suggestions? Thanks!
And calraith, thanks for the walk through on getting google play to work. It works great!
tbs123456q said:
I tried using the Kingo ROOT app, but mine just wont root. Ive rum it close to a dozen times now. Any suggestions? Thanks!
And calraith, thanks for the walk through on getting google play to work. It works great!
Click to expand...
Click to collapse
I attempted three or four various methods of rooting before successfully rooting with Kingo. It could've been that Kingo wouldn't have been successful for me without the filesystem modifications made by other tools -- I'm not sure, and don't really feel like restoring to find out.
Maybe try rooting with sf.net/projects/rootandroid ; and after reboot if your apps fail to gain root privileges, use Kingo to remove and restore root. See if that helps.
calraith said:
I attempted three or four various methods of rooting before successfully rooting with Kingo. It could've been that Kingo wouldn't have been successful for me without the filesystem modifications made by other tools -- I'm not sure, and don't really feel like restoring to find out.
Maybe try rooting with sf.net/projects/rootandroid ; and after reboot if your apps fail to gain root privileges, use Kingo to remove and restore root. See if that helps.
Click to expand...
Click to collapse
I will give that a try. Thanks!
Here's another useful hack. You know /sdcard points to the rather scant internal sdcard. Once you install a few apps there's little room left for music, movies, etc. You can put some of your media on an external sdcard mounted at /mnt/extsd, but some apps expect their media content to be accessible within /sdcard -- camera apps and FireTaps, for example.
It'd be nice if you could have /sdcard/DCIM and /sdcard/FireTaps as symlinks from true directories on /mnt/extsd. Unfortunately since sdcards use a fat32 filesystem, symlinks aren't supported. You can, however, use mount bindings to accomplish the same sort of thing. Mount is a kernel thing rather than a filesystem thing.
After you get your tablet rooted, you can install and use "Universal init.d" from the Play Store to execute user-made startup scripts. I wrote the following script to bind all the directories from my external sd to my internal. I saved it as /system/etc/init.d/99extbind (using ES File Explorer with root permission) and did chmod 700 (from a JS Terminal console and su for root). Any directory I want to move from the internal sd to the external, now i just move it via cut & paste then reboot. After reboot, the contents of the directory are accessible from both directory trees, but physically only use space on the external card.
Code:
#!/system/bin/sh
bind_to_sdcard() {
d=$*
d2=/mnt/sdcard/${d##*/}
[ ! -d "$d2" ] && mkdir "$d2"
mount -o bind "$d" "$d2"
}
# purging empty directories
for d in /mnt/sdcard/.*; do [ -d "$d" ] && rmdir "$d" 2>/dev/null; done
for d in /mnt/sdcard/*; do [ -d "$d" ] && rmdir "$d" 2>/dev/null; done
# binding directories from external sd on internal sd
for d in /mnt/extsd/.*; do [ -d "$d" ] && bind_to_sdcard $d; done
for d in /mnt/extsd/*; do [ -d "$d" ] && bind_to_sdcard $d; done
exit 0
Edit: If you attach your tablet to a PC via USB and enable USB storage, the tablet will not be able to make the internal sdcard available to the PC. I'm guessing this is because when the tablet attempts to umount /mnt/sdcard the device is busy with other child mounts and can't be umounted. The internal sdcard is still accessible to ES File Explorer and similar while not plugged into a PC, though. I recommend copious backups just in case calamity strikes, in any case.
Edit 2: After ejecting from the PC, SwiftKey complained about not being able to read the sdcard, and predictions and swiping were unavailable. A reboot fixed it.
So far for me, the benefits outweigh the problems. I've now got over a gig of FireTaps songs, 250 megs of books, and 500+ megs of application data available in /sdcard where before i was limited to about 1.3 gigs.
Sent from my D7020 using Tapatalk 2
calraith said:
Ah, damn it, I can help, but I can't post hyperlinks. I'll see what I can do. If this is hard to read, I hope some non-rookie will quote me and fix the links in the quote.
I picked one of these up on Black Friday for less than 50 bucks. Good times. It was a bear getting the Play Store not to crash every session. For quite a while I struggled with the Play Store seeming to run OK for a minute, then "Unfortunately Play Store has stopped" and back to the home screen. Clearing the cache and making sure the Download service was started didn't help. But now things are looking up.
I'm still running Android 4.2.2, which is what the tablet came with. I'm afraid I can't help you with finding a 4.3 rom.
Anyway, mgordon's suggestion of Kingo Root works as well as any. You can also use its bundled adb.exe to push the Play Store onto your tablet. To install a working Play Store, after rooting, follow these steps:
Get this Play Store APK: triple-w dot androidfilehost dot com /?fid=23203820527945029 (found [here](triple-w dot androidpolice dot com /2013/11/01/download-latest-google-play-store-4-4-22/#download))
Go to your Start Menu --> All Programs --> Accessories, and right-click on Command Prompt and choose "Run as Administrator."
In the command prompt window, navigate to adb supplied by Kingo Root. (cd "\Program Files (x86)\Kingo Android ROOT\tools") then continue with the following additional commands.
adb push \users\yourusername\Downloads\com.android.vending-4.4.22.apk /system/app/com.android.vending-4.4.22.apk
adb shell chmod 755 /system/app/com.android.vending-4.4.22.apk
adb reboot
Good luck!
Click to expand...
Click to collapse
Thank you, thank you!! I have been trying for I don't know how long to get the Play Store to work. I tried it and now it works great!!!
More help with Google Play please...
Hello everyone I have the DOPO D7020 and am trying to install Google Play per the instructions given. I installed Kingo Root and have successfully rooted the device. I downloaded the play store APK to my desktop. I am running the command prompt as administrator but this is where I get stuck. When I follow the directions and enter the commands or even copy and paste the commands to the command prompt it says "....is not recognized as an internal or external command, operable function or batch file." Any help is greatly appreciated, thanks in advance!
impp83 said:
Hello everyone I have the DOPO D7020 and am trying to install Google Play per the instructions given. I installed Kingo Root and have successfully rooted the device. I downloaded the play store APK to my desktop. I am running the command prompt as administrator but this is where I get stuck. When I follow the directions and enter the commands or even copy and paste the commands to the command prompt it says "....is not recognized as an internal or external command, operable function or batch file." Any help is greatly appreciated, thanks in advance!
Click to expand...
Click to collapse
You need to hold down shift and right click on the adb folder, you can't just run the adb commands from any old command prompt, not without setting environment variables, Windows gets cranky about that stuff.
EDIT: Shift, right click, and select "Open Command Window here"
---------- Post added 25th December 2013 at 12:15 AM ---------- Previous post was 24th December 2013 at 11:37 PM ----------
So I scored a couple of these from amazon, planned on giving one to my mother for Christmas, but before that, I had to have one for myself to see what it was about. I actually used Vroot as my root solution. I was able to use the method above to get google play working, so big win there, now if I could only get TiBu to write to the external SD
Kamiex said:
So I scored a couple of these from amazon, planned on giving one to my mother for Christmas, but before that, I had to have one for myself to see what it was about. I actually used Vroot as my root solution. I was able to use the method above to get google play working, so big win there, now if I could only get TiBu to write to the external SD
Click to expand...
Click to collapse
Super Backup (com.idea.backup.smscontacts) will let you specify the backup path. Or you could use my mount -o bind trick in comment #8.
Sent from my SCH-I405 using Tapatalk 2
calraith said:
Super Backup (com.idea.backup.smscontacts) will let you specify the backup path. Or you could use my mount -o bind trick in comment #8.
Sent from my SCH-I405 using Tapatalk 2
Click to expand...
Click to collapse
I actually figured it out late last night. I had the SD card formatted in Fat32, things like ES File Manager and Root Explorer could read and write to it just fine, I formatted the card with exFat and TiBu had no problem writing to it.
USB Drivers
calraith said:
Ah, damn it, I can help, but I can't post hyperlinks. I'll see what I can do. If this is hard to read, I hope some non-rookie will quote me and fix the links in the quote.
I picked one of these up on Black Friday for less than 50 bucks. Good times. It was a bear getting the Play Store not to crash every session. For quite a while I struggled with the Play Store seeming to run OK for a minute, then "Unfortunately Play Store has stopped" and back to the home screen. Clearing the cache and making sure the Download service was started didn't help. But now things are looking up.
I'm still running Android 4.2.2, which is what the tablet came with. I'm afraid I can't help you with finding a 4.3 rom.
Anyway, mgordon's suggestion of Kingo Root works as well as any. You can also use its bundled adb.exe to push the Play Store onto your tablet. To install a working Play Store, after rooting, follow these steps:
Get this Play Store APK: triple-w dot androidfilehost dot com /?fid=23203820527945029 (found [here](triple-w dot androidpolice dot com /2013/11/01/download-latest-google-play-store-4-4-22/#download))
Go to your Start Menu --> All Programs --> Accessories, and right-click on Command Prompt and choose "Run as Administrator."
In the command prompt window, navigate to adb supplied by Kingo Root. (cd "\Program Files (x86)\Kingo Android ROOT\tools") then continue with the following additional commands.
adb push \users\yourusername\Downloads\com.android.vending-4.4.22.apk /system/app/com.android.vending-4.4.22.apk
adb shell chmod 755 /system/app/com.android.vending-4.4.22.apk
adb reboot
Good luck!
Click to expand...
Click to collapse
Where did you get the USB Drivers? In my device manager, I get "Other Devices -> Android" with a yellow triangle and exclamation point.
EDIT: Nevermind, just finished rooting! Had it connected as MTP, switched to USB large storage.
after rooting its easir to install lucky patcher > toolbox >then install modded play store. inintely easier and faster
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
duuude im baked said:
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
Click to expand...
Click to collapse
Thought I would share some info I found when I ran into the wifi problem on my daughter's nabi. I did some searches on the internet and the typical answer I found for solving the wifi issue was "reset the device" or "unroot and return to stock rom - flash all updates and reroot". Being a glutton for punishment, and the fact I didn't want to reset the device, I searched and searched and was able to fix my daughter's wifi without doing a reset or unroot/reroot. Before I get into it I wanted to mention that wifi failures can happen for a number of reasons so while this worked for myself, it may not work for you.
Some prerequisites:
Most importantly; you need a rooted device. If you do not have root access you will not be able to write files or access the commands to fix the issue I am about to outline.
Some knowledge of linux would be helpful, but not necessarily required.
Lets get started:
Warning! It goes without saying but I will say it anyways - you can mess up your nabi by rooting it. Some of the commands below could mess up your nabi bad. If this scares you then you probably should not proceed any further. I am not responsible for any damage you do to your nabi.
Commands are listed between ' and ' - do not use the ' when inputing the commands.
Note: The first two/three steps are not necessary but they do give you insight as to how I was able to determine my problem. If following this doesn't fix the problem for you the logcat output may give you some important info that you can google that may help you fix your particular problem.
Note: Steps 5 and on can be skipped if you have a text editor (vi or nano) on your device. If you have a text editor loaded simply edit the conf file directly.
1. You will need to run the command 'adb logcat' in a command-line window and in your appropriate directory. Adb is available as part of the android sdk but can also be found stand alone since most people do not need the sdk.
2. Try to turn on the wifi. You should see the output of your adb logcat window scroll some data. If the wifi is not attempting to turn on at all sometimes you can move between the settings options then go back to the wifi settings and move the slider. If you cannot get your wifi to turn on you can scroll the window up and attmept to find the data from when the device started up. In the output you should see lines that talk about wlan0 and probably something that says "failed" somewhere. In my case I could see where the wlan0 enabled but then a few lines down it said something about "Line: 25 failed" and "failed to parse file".
3. The file is actually a configuration file used by the wifi kernal module/driver. In my case this file had become corrupted.
4. Set adb in root mode (won't work if the device does not have root access) by running 'adb root' at the command-line. You may need to click on an "allow root permission" window on the actual device after running this command.
5. Run 'adb pull /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb shell' from command line.
b. 'su'
c. 'cat /data/misc/wifi/wpa_supplicant.conf' - copy the output from the command and paste into a text editor (see note in step 6 on why NOT to use notepad).
d. Save the file as wpa_supplicant.conf, preferrably in the same diretory as adb.
e. 'exit' twice should exit you from the adb shell and return you to your command-line. If all else failes a "ctrl-c" should drop you out of adb.
6. Use a text editor to open wpa_supplicant.conf. The file should be located int he same directory as adb. If you are using Windows I would strongly suggest you NOT use notepad. Notepad will typically change all the EOLs (End Of Line) from \n to \r\n which will really mess things up worse.
7. In the file you should see "network={" entries. There maybe one entry, there maybe many entries. You can remove all lines between "network={" and "}" including the latter themselves. If you see your 'home' network listed you can leave it as the only entry and make sure its priority is set to 1 but it maybe better to remove it as well just in case it contains part of the corrupted data.
8. Save the file.
9. Do 'adb push wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb push wpa_supplicant.conf /sdcard/wpa_supplicant.conf' from command-line.
b. Run 'adb shell'
c. 'su'
d. 'dd if=/sdcard/wpa_supplicant.conf of=/data/misc/wifi/wpa_supplicant.conf'
e. Do 'exit' twice to exit the adb shell. If all else fails then a "ctrl-c" should drop you ot of adb.
10. If the wpa_supplicant file was corrupted then the wifi should now be able to enable and you should now be able to connect to a network.
I hope this is helpful to at least a few people.
Hi all,
EDIT
Thanks to techdudester on the second page, getting rid of the malware is now even easier!
Just flash the image he found here with the following procedure and you're good to go!
Instruction:
1. Flash the new ROM.
a. Get the ROM here . (Use this ROM only if you have a Venstar V140D tablet!)
b. Follow the linked tutorial to install the flash software and flash the new ROM on your device with: Phoenix Suit.
Voila, ready!
Enjoy your malware free tablet!
Tips and tricks. (or something...)
Get adb working (needed for all the other tricks down below):
1. Download the Google development tools (sdk) here and install them on your computer. I assume you have windows 7 installed during the rest of this tutorial.
2. Connect your device to your computer and make sure it is installed correctly.
a. Connect your device while its powered on via USB to your pc.
b. Go to Start, right click "My Computer" and select "Properties". Click "Device Manager".
c. Right click the Android device with the exclamation mark and select "Update Driver Software...".
d. Select "Browse my computer for driver software".
e. Select "Let me pick from a list of device drivers on my computer".
f. Keep "Show All Devices" selected and click Next.
g. Click "Have Disk..." and click "Browse..."
h. You can find the drivers in the "SDKInstallLocation"\sdk\extras\google\usb_driver directory and click OK. Replace SDKInstallLocation with the location that you selected during installation of the SDK.
i. Select the "Android ADB Interface" driver from the list and click Next.
j. Confirm installation by clicking on "Yes". Sometimes you also have to click on "Install" if a screen pops up to ask you again if you really want to install the driver...
k. Click "Close".
To use it:
Open a command prompt (in search type "cmd" followed by ENTER) and go to the following directory ""SDKInstallLocation"\sdk\platform-tools".
If you want a backup of your tablets system directory (highly recommended!) use:
"adb pull /system C:\system"
where C:\system is the target location on your local computer where you want the backup of the system directory.
Remove the update package (this doesn't work for updating the tablet, so, useless.)
adb remount
adb shell
cd system/app
rm Update.apk
exit
Remove the unwanted apps (dragonfire.apk etc)
adb remount
adb shell
cd system/preinstall
rm *
exit
If you would like to have your tablet in the correct time zone after factory reset, you will have to adjust the build.prop file.
First you need to get it to your pc so you can edit it:
in the command prompt window and at the same location as in the tutorial above type "adb pull /system/build.prop C:\temp\build.prop".
Just in case, make a copy of the build.prop in Windows Explorer so you always have the original file if something goes wrong.
Now you can edit the build.prop, but DON'T EDIT IT WITH THE WINDOWS NOTEPAD! Use Notepad++ or similar to edit the build.prop.
After you made the changes (and be careful here, you could end up with a tablet that does not want to boot up, solution further down below) you have to upload the file back to your tablet.
in the command prompt type:
adb remount
adb push C:\temp\build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
Don't forget the last line! If you do not chmod the file (set the correct permissions) your tablet will not boot up.
Changes in the build.prop:
Time zone:
Default time zone is "persist.sys.timezone=Europe/London"
you can change this to your locale time zone like "persist.sys.timezone=Europe/Amsterdam" (for the netherlands )
Search the internet for valid time zones.
Change the default language:
The default language is determined by these two values in the build.prop:
persist.sys.language=en
persist.sys.country=US
For dutch change them to:
persist.sys.language=nl
persist.sys.country=NL
and again, search the internet for valid language values.
Higher brightness after factory reset:
Add the following line to the build.prop file (at the top of the file)
ro.ph.def_brightness=225
You pushed the build.prop without changing the permissions:
No problem. Just connect your booting tablet to the PC, install the driver if its not installed correctly like explained in the tutorial, and then change the rights via adb. It's no problem that it's not fully booted!
in a command prompt in the adb directory:
adb remount
adb shell chmod 644 /system/build.prop
adb reboot
If you pushed a wrong non functioning build.prop, just use this method to push the original build.prop (you know, the copy you made ) back to the device (followed by setting the correct permissions of course).
Remove the (in my opinion) irritating boot sound:
adb remount
adb shell
cd system/media
rm boot.wav
exit
rom download
can you provide another way to download the rom file ,i cant seem to get the registration process to work
stevethesignguy865 said:
can you provide another way to download the rom file ,i cant seem to get the registration process to work
Click to expand...
Click to collapse
I have dropped it here. Hope this helps
I bought the same tablet for my daughter. She's (and so am I) suffering from a lot of annoying popups and ads.
Thanks for sharing your instructions here, very hard to find them!
Since I'm a complete newbie: one important question. When you flash the ROM, all of the apps (games) will be removed I guess?
Second question: can you put the stock rom on a different location? Both of the links (including Filedropper) don't contain any files...
Thanks!
1ce/ said:
I bought the same tablet for my daughter. She's (and so am I) suffering from a lot of annoying popups and ads.
Thanks for sharing your instructions here, very hard to find them!
Since I'm a complete newbie: one important question. When you flash the ROM, all of the apps (games) will be removed I guess?
Second question: can you put the stock rom on a different location? Both of the links (including Filedropper) don't contain any files...
Thanks!
Click to expand...
Click to collapse
Yes, all applications will be removed. As soon as you configure the tablet again with the same gmail account, it will probably start installing the applications and games automatically, but in game progress will be lost for most (not online) games.
I am re-uploading the file. Will update this post with the link as soon as it finishes
edit: upload finished, get it while its there LINK
BlueFlame said:
edit: upload finished, get it while its there LINK
Click to expand...
Click to collapse
Great! Thanks for the swift response. The file is about 307 MB. Is this correct? I'll start working on it, probably this weekend. I'll keep you posted.
1ce/ said:
Great! Thanks for the swift response. The file is about 307 MB. Is this correct? I'll start working on it, probably this weekend. I'll keep you posted.
Click to expand...
Click to collapse
Yes, thats correct. Once unpacked it will be around 520 MB.
Good luck!
Hi BlueFlame,
Thanks for the post. Is it possible to get the image uploaded again? Would be much appreciated.
Maylar said:
Hi BlueFlame,
Thanks for the post. Is it possible to get the image uploaded again? Would be much appreciated.
Click to expand...
Click to collapse
On request. You can find it here. (Adjusted link. Stored on Google Drive)
Thanking you. Very much appreciated.
Thank's for a fantastic procedure... Worked very well.
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
1ce/ said:
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
Click to expand...
Click to collapse
Is that the firmware that I provided?
If not, try to download it again.
If so, I think that your tablet has a newer firmware than this one. You could contact the seller of your tablet for the current (latest) firmware for this tablet.
If you get a newer firmware, please share
Image file invalid
Hi Blueflame,
I've tried to re-flash, but at some point i'm getting the message at livesuit V1.11 that the image file is invalid.
It's the 3rd time i have downloaded the file, what could be cause of this error?
Greetz Mike
mcwheelz said:
Hi Blueflame,
I've tried to re-flash, but at some point i'm getting the message at livesuit V1.11 that the image file is invalid.
It's the 3rd time i have downloaded the file, what could be cause of this error?
Greetz Mike
Click to expand...
Click to collapse
Not sure. Will upload it again this weekend just to be sure that it's not my uploaded image. (I will let you know once I've done that)
You can, on the other hand, contact the supplier (where you bought the tablet) and ask them for the latest version of the ROM. I would also be interested in that
BlueFlame said:
Not sure. Will upload it again this weekend just to be sure that it's not my uploaded image. (I will let you know once I've done that)
You can, on the other hand, contact the supplier (where you bought the tablet) and ask them for the latest version of the ROM. I would also be interested in that
Click to expand...
Click to collapse
Uploaded again! same link (just made it a new version in Google Drive).
Open Firmware failed - possible solution
1ce/ said:
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
Click to expand...
Click to collapse
Try to put the image file in a directory without special characters (i.e. c:\temp). Worked for me.
wundabua
Te real FIX is In!
Ok, i have one of these allwinner, Venstar, "whatever", A33 D140v tablets. It had all the usual problems and more, because the first thing I tried, was to use the built in recovery to "restore to factory". This made things even worse, because after the recovery, I couldn't reach the Google authentication servers.
I am pro tech with 25 years in the trenches and I have to admit this thing really threw me for a loop, because I spent an entire day researching the solution, installing Android SDK, drivers, Phoenix Suit, Live Suit, etc. These were all very complicated "solutions" that took me exactly nowhere. I finally found the answer in a rather stupid Youtube video.
The REAL answer is actually very quick and easy compared to all these other recommended methods.
In the first place, model V140d image is only used for these infected tablets. The actual model is V11 and once you use the quick restore method I discovered, you will have a malware free V11 model. The whole secret to this method, is the fact that these units were designed to be quickly, automatically and completely restored in less that 5 minutes through the use of their built in micro SD slot.
Imagine that!
If you check your tablet that came new in the box as something other than V140d, the method I used will most probably not work for you.
Anyway, the quick method I discovered, can be seen on my own tech support site. To find it, Google: Just Call Techdude
Then click on the support link at the top of the page on my site and all will be revealed.
techdudester said:
Ok, i have one of these allwinner, Venstar, "whatever", A33 D140v tablets. It had all the usual problems and more, because the first thing I tried, was to use the built in recovery to "restore to factory". This made things even worse, because after the recovery, I couldn't reach the Google authentication servers.
I am pro tech with 25 years in the trenches and I have to admit this thing really threw me for a loop, because I spent an entire day researching the solution, installing Android SDK, drivers, Phoenix Suit, Live Suit, etc. These were all very complicated "solutions" that took me exactly nowhere. I finally found the answer in a rather stupid Youtube video.
Click to expand...
Click to collapse
Hi techdudester,
The combination "pro tech with 25 years in the trenches" and "very complicated "solutions"" sounds a bit strange.
But either way, a THANK YOU is in order!
The ROM you found works on my tablet (flashed yesterday) and so far so good. No popups and no unwanted application downloads!
I will adjust my initial post to incorporate this image.
First time posting and I wanted to say thank you to all the excellent talent here on XDA! None of this would have been done without the work of so many people.
I have a Moto G Play (2021) (XT2093-4) that I recently purchased (Best Buy - $159 US/Carrier Unlocked) and I wanted to document my adventure in to rooting, making '/system' RW, and fixing the missing LED notification light (hint: I used the charging light) (hint^2: It's not required to make '/system' RW in order to fix the LED notification light - I just wanted more control over my phone).
First, "OEM unlocking" was greyed out for me, but became available after several days of having the phone online with a SIM card.
I followed the instructions here to unlock the bootloader and root with Magisk (Non-TWRP). Along with these instructions.
Once bootloader is unlocked, you will need the 'boot.img' file from your stock firmware. I used the "Rescue and Smart Assistant" utility to grab a copy of the stock firmware (GUAMNA_RETAIL_QZAS30.Q4_39_35_9_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml) and extracted the "boot.img" file for the next steps.
Continue installing Magisk (Filenames may be different! Don't just copy and paste.):
Code:
adb install Magisk-v23.0.apk
adb push boot.img /sdcard/Download
(Follow the instruction on your phone to patch 'boot.img' in Magisk)
adb pull /sdcard/Download/magisk_patched-23000_aKKMt.img
adb reboot bootloader
fastboot flash boot_a magisk_patched-23000_aKKMt.img
fastboot flash boot_b magisk_patched-23000_aKKMt.img
You should now have a working, rooted Moto G Play. You can just stop here and have fun with your phone, but I noticed that even with root, the system partition was not RW.
I followed these instructions to make '/system' writable (Note: you will need the 'sysrw_repair.zip' that's included in the bundle and a Linux system):
Code:
adb push systemrw_1.32_flashable.zip /data/local/tmp/
adb shell
su
cd /data/local/tmp/
unzip systemrw_1.32_flashable.zip
cd systemrw_1.32/
chmod +x systemrw.sh
./systemrw.sh in=`ls -l /dev/block/by-name/super | awk '{print $NF}'` out=/data/local/tmp/systemrw_1.32/img/super_original.bin size=50
The phone doesn't have enough space to complete 'lpmake' on the device and will end with an "Error 73" code. Running the "sysrw_repair_v1.32" tool on a Linux machine was a workaround because it pulls the '*.img" files to your local machine then combines them in to a single '.bin' file. But, before I did that, and because it's really annoying, I made some room to stop the phone from complaining about a lack of space:
(Still on the phone's adb)
Code:
rm ./img/super_original.bin
Now, on the Linux machine, I unzipped 'sysrw_repair_v1.32_proper.zip' then commented out line 39 (where it calls the "flash()" function) of the script (sysrw_repair.sh) because I wanted to flash the "super" partition myself.
(On another Linux terminal)
Code:
cd /path/to/unzipped/sysrw_repair/dir/
chmod +x sysrw_repair.sh
./sysrw_repair.sh
This results in a new folder (img) with a rather large bin file (super_original.bin).
(Back on the phone adb)
Code:
exit # Exit root
exit # Exit adb
adb reboot bootloader
Now it's time to flash the fixed bin file to the "super" partition:
Code:
cd /path/to/unzipped/sysrw_repair/dir/
fastboot flash super ./img/super_original.bin
fastboot reboot
You should be able to login and have a writable '/system':
Code:
adb shell
su
mount -o rw,remount /
No errors should appear.
Last, I like having an LED indicator that tells me that I have an SMS/MMS notification waiting. Motorola thought it would be wise to eliminate that feature altogether instead of having the option to enable it. So, I forced it back on using a startup script that dumps the notifications and greps for some key words. And, if it finds something, it "breaths" the charging LED. The script loops until the notification is gone, then keeps checking for new notifications every 30 seconds. (Note: the "/data/adb/service.d/" directory is used by Magisk like an INIT service):
(Still root on the phones adb)
Code:
cd /data/adb/service.d/
cat <<EOF > ledfix.sh
#!/bin/sh
while true; do
if dumpsys notification | egrep NotificationRecord | egrep sms > /dev/null
then
if [[ $(cat /sys/class/leds/charging/breath) == 0 ]]
then
echo 1 > /sys/class/leds/charging/breath
sleep 2
continue
else
sleep 2
continue
fi
elif egrep 'Charging' /sys/class/power_supply/battery/status > /dev/null
then
if [[ $(cat /sys/class/leds/charging/breath) -ne 0 && $(cat /sys/class/leds/charging/brightness) -ne 0 ]]
then
echo 0 > /sys/class/leds/charging/breath
echo 255 > /sys/class/leds/charging/brightness
elif [[ $(cat /sys/class/leds/charging/breath) == 0 && $(cat /sys/class/leds/charging/brightness) == 0 ]]
then
echo 255 > /sys/class/leds/charging/brightness
else
continue
fi
else
echo 0 > /sys/class/leds/charging/breath
echo 0 > /sys/class/leds/charging/brightness
fi
sleep 30
done
EOF
chown 0.0 ledfix.sh
chmod 0755 ledfix.sh
reboot
Now, the charging light will fade off and on about every 2 seconds if there's an SMS/MMS notification waiting. And will check for notifications every 30 seconds. I'm sure someone can come up with a better way of doing this, but this was a nice quick-and-dirty way to get what I wanted.
Hope this helps!
I created an account to say thank you for this, I have already done a good portion, having unlocked the bootloader, the problem is the Rescue Smart Assistant, it won't let me log in, it keeps telling me it can't connect, and the GUI is different because of an update, there is no download button inside the program, only a greyed out rescue button. How did you manage to make the backup Boot.img? Maybe you are using a different OS, and/or version of the program (Not the app, that is already auto-installed), I'm using Windows 10, are you on Linux? I might just need to try from Linux, maybe in a VM.
I was trying to do this before I found this post, and have already installed ADB, the SDK, fastboot, and Motorola Drivers, I just need a way to get the Boot.img, and to patch it, also figure out how to flash it. The last android I rooted with a custom rom was the HTC EVO 4G with Oreo/Jellybean, so I'm a little rusty, but am able to understand technical jargon.
If anyone could help, that would be awesome. I've reinstalled different versions of Rescue Smart Assistant as well, they always upgrade on boot, same problem. I've added exceptions to my firewall and everything.
UPDATE: Was about to post this when I had updated from android 10 to 11 and decided to try logging in again a little closer to my router, to see if the connection was timing out, I think that was the cause, as I can now sign in, and the GUI seems correct from the first appearance. I don't see why I should have any trouble following the rest of the guide, but feel I should share my trials and frustrations anyways, for anyone else experiencing the same,
Thanks again.
PROFSLM said:
I created an account to say thank you for this, I have already done a good portion, having unlocked the bootloader, the problem is the Rescue Smart Assistant, it won't let me log in, it keeps telling me it can't connect, and the GUI is different because of an update, there is no download button inside the program, only a greyed out rescue button. How did you manage to make the backup Boot.img? Maybe you are using a different OS, and/or version of the program (Not the app, that is already auto-installed), I'm using Windows 10, are you on Linux? I might just need to try from Linux, maybe in a VM.
I was trying to do this before I found this post, and have already installed ADB, the SDK, fastboot, and Motorola Drivers, I just need a way to get the Boot.img, and to patch it, also figure out how to flash it. The last android I rooted with a custom rom was the HTC EVO 4G with Oreo/Jellybean, so I'm a little rusty, but am able to understand technical jargon.
If anyone could help, that would be awesome. I've reinstalled different versions of Rescue Smart Assistant as well, they always upgrade on boot, same problem. I've added exceptions to my firewall and everything.
UPDATE: Was about to post this when I had updated from android 10 to 11 and decided to try logging in again a little closer to my router, to see if the connection was timing out, I think that was the cause, as I can now sign in, and the GUI seems correct from the first appearance. I don't see why I should have any trouble following the rest of the guide, but feel I should share my trials and frustrations anyways, for anyone else experiencing the same,
Thanks again.
Click to expand...
Click to collapse
You can also get the firmware from
Lolinet Mirrors
https://t.me/MotoUpdatesTracker
Search for Firmware by codename, software channel, Software Version, and build #
So I wasn't going crazy when I could swear a LED notification light in the upper right side above the screen blinked once whenever I rebooted the phone?
Why would Motorola include such a thing and not utilize it for more than merely a boot up indicator? Like I dont even get to see it come on while charging, it literally only blinks once during boot and that's it.
mario0318 said:
So I wasn't going crazy when I could swear a LED notification light in the upper right side above the screen blinked once whenever I rebooted the phone?
Why would Motorola include such a thing and not utilize it for more than merely a boot up indicator? Like I dont even get to see it come on while charging, it literally only blinks once during boot and that's it.
Click to expand...
Click to collapse
I know!
I don't know what triggers that light to come on. I even waited until the battery was at 6% and the light still never came on.
So, I updated the script above to make the light go full brightness if the battery is charging. The order matters, so if a notification comes in while charging, it'll "breath" the LED. Also, if the battery is full, then the light will turn off. Kind of telling you that it's time to unplug.
I followed these steps and my touch screen stopped working. I had previously installed twrp already on it while trying to learn how to root it, and when i boot into fastboot it goed through twrp, i also used the boot.img file from lolinet, not sure which of these caused the issue. Interestingly though, the touch screen does work whilst in twrp. any suggestions on how to fix or what would be causing it? Phone does work with usb mouse over OTG
jorduino said:
I followed these steps and my touch screen stopped working. I had previously installed twrp already on it while trying to learn how to root it, and when i boot into fastboot it goed through twrp, i also used the boot.img file from lolinet, not sure which of these caused the issue. Interestingly though, the touch screen does work whilst in twrp. any suggestions on how to fix or what would be causing it? Phone does work with usb mouse over OTG
Click to expand...
Click to collapse
Are you absolutely sure you used the correct boot.img from an image version exactly matching your phone variant version?
mario0318 said:
Are you absolutely sure you used the correct boot.img from an image version exactly matching your phone variant version?
Click to expand...
Click to collapse
Im not completely sure how to get the right file, but I think the first time it was the wrong one, but then when i got what i thought was the right one, it just didn't work at all and I had to recovery flash it. I had just updated so maybe the correct image wasn't available yet. Im going to try again though
Oh! Hello @latentspork. Thanks for your interest in my SystemRW project. I just came across this thread randomly...
I'm happy you got my script to work on your Motorola device by using the included sysrw_repair script
Please feel free to send me your log files from script folder. Thanks. It's useful for further development of the script
latentspork said:
The phone doesn't have enough space to complete 'lpmake' on the device and will end with an "Error 73" code. Running the "sysrw_repair_v1.32" tool on a Linux machine was a workaround because it pulls the '*.img" files to your local machine then combines them in to a single '.bin' file. But, before I did that, and because it's really annoying, I made some room to stop the phone from complaining about a lack of space:
Click to expand...
Click to collapse
That's not 100% accurate. Lpmake error 73 means CAN'T_CREATE and has nothing to do with error 70 (insufficient space).
To this day I still don't know exactly what causes error 73 on some devices (mostly Motorola and others) but it looks like some kind of kernel panic. If anyone knows how to avoid this error 73 in Android please let me know! Thanks!
Yes that's true the included sysrw_repair script (Linux only) pulls the image files from the phone to your computer and attempts to run the same lpmake command with the same arguments that just failed with error 73 on the phone itself and now all of a sudden it just works in Linux. Go figure.
latentspork said:
(Still on the phone's adb)
Code:
rm ./img/super_original.bin
Click to expand...
Click to collapse
Why would you delete the super_original.bin ? That's your stock read-only super image which by default is automatically dumped by script for backup purposes in case you ever get a bootloop.
And if you launch the script by specifying a custom input value (in=x) like in your example above then you won't even have a super_original.bin file to begin with because script will skip the whole dumping of original super image process.
latentspork said:
This results in a new folder (img) with a rather large bin file (super_original.bin).
Click to expand...
Click to collapse
I think you mean super_fixed.bin
latentspork said:
Now it's time to flash the fixed bin file to the "super" partition:
Code:
cd /path/to/unzipped/sysrw_repair/dir/
fastboot flash super ./img/super_original.bin
fastboot reboot
Click to expand...
Click to collapse
Here in your instructions you are manually flashing the wrong file. Shouldn't you be flashing super_fixed.bin to your super partition?
Usually I only flash the super_original.bin to get back out of a bootloop...
latentspork said:
Now, on the Linux machine, I unzipped 'sysrw_repair_v1.32_proper.zip' then commented out line 39 (where it calls the "flash()" function) of the script (sysrw_repair.sh) because I wanted to flash the "super" partition myself.
Click to expand...
Click to collapse
See that's why I included that automatic flash() function in the repair script. Then you don't have to worry about manually flashing the wrong file to your super partition
Enjoy a fully read/write-able device!
Great news! New SystemRW version coming soon!
@lebigmac
I really appreciate the reply and the tool! It did work really well on my model (XT2093-4).
That's not 100% accurate. Lpmake error 73 means CAN'T_CREATE and has nothing to do with error 70 (insufficient space).
To this day I still don't know exactly what causes error 73 on some devices (mostly Motorola and others) but it looks like some kind of kernel panic. If anyone knows how to avoid this error 73 in Android please let me know! Thanks!
Click to expand...
Click to collapse
I only assumed that "Error 73" was caused by insufficient space, because the phone really did run out of space. I noticed that the phone was out of space because I got a home screen notification warning, asking me to free up space. I confirmed it with a "df -h" at the shell. Apparently, the OS takes up almost 15GB. When you add the ".img" files, there's only about 5GB left. There wasn't enough room to complete the ".bin" file. Maybe I could have used an SD card or something.
You're probably correct in that "Error 70" is the correct error for that, but on my phone, I never saw that error. I did notice that the tool was still trying to write data as the phone ran out of space, then it would throw the "Error 73". Maybe it didn't register the lack of space, or just an oddity with my model? No idea.
Why would you delete the super_original.bin ?
Click to expand...
Click to collapse
This is the file that was created when I initially ran the "./systemrw.sh" command on the phone. The result of running the command on the phone were several ".img" files and a very large "super_original.bin", but it was incomplete because the command threw an "Error 73". I was following your instructions, and I noticed that the output name of the file was "original" instead of "fixed". I probably could of outputted it to a new name to reduce confusion, but I didn't really care too much about the name as long as I had a working file.
I think you mean super_fixed.bin
...
Shouldn't you be flashing super_fixed.bin...
Click to expand...
Click to collapse
Normally, yes. But the Linux script also outputted the filename "super_original.bin". Again, as long as it worked, I was okay with it. The commands I used above were the exact commands that I ran at the time. I copied them from the terminal consoles I was using. So I don't know why it wasn't outputting the correct filename (again, I was following your instructions and was a little confused that the names came out differently - I just figured I was doing something wrong like not use the proper output command or something).
Then you don't have to worry about manually flashing the wrong file to your super partition...
Click to expand...
Click to collapse
I was really just being cautious because my previous phone broke and I didn't have a fallback.
But, at no point were there two bin files (original and fixed), so there wasn't much confusion. Where I originally had just ".img" files before running the script, I now had a single ".bin" file. I knew that was the file I needed.
But again, thank you for all the hard work on this tool! I was reading that it's worked on lots of different model phones, and it's always good to see the open source community doing things that help all kinds of people.
For moto notification for this phone at least use https://play.google.com/store/apps/details?id=br.com.itsmeton.motoledreborn or moto led reborn from the play store it just works
Hi, sorry. This can be removed. I put it in place because I was having issues with the xda app. For whatever reason, every time I tried to share this particular post, it would share a link for the post which I used originally, rather than the current post. I knew that if I commented I could get back here easily on my PC.
So what is the place holder for