Related
Hi, I'm hoping someone can help me. I'm running OSX Snow Leopard, using terminal and attempting to gain root access to my new Nexus One. I was able to quickly and easily unlock the boot loader, however, I have made multiple attempts to gain root access for model ERE27 using superboot, but while everything seems to appear normal, I can not flash the recovery-RA-nexus-v1.7.0.1-cyan.img. When I reboot the phone I attempt to run terminal app from market and find I am still denied permission. I've checked every site I could to correct this, but seem to be missing something every time. When attempting to root, I cd to applications/android-sdk-mac_86/tools/superboot. I press enter then chmod +x-install-superboot-mac.sh Then I press enter and key ./fastboot-mac. After processing in terminal and seeing a status bar briefly on the nexus upper right screen of the Nexus, terminal says Okay. I reboot and no root access. PLEASE HELP. Been at this for an embarrassingly long time now...
Have you installed a rooted rom? or just trying to see if you have root access on the stock rom?
Jeremy.Bentham said:
Hi, I'm hoping someone can help me. I'm running OSX Snow Leopard, using terminal and attempting to gain root access to my new Nexus One. I was able to quickly and easily unlock the boot loader, however, I have made multiple attempts to gain root access for model ERE27 using superboot, but while everything seems to appear normal, I can not flash the recovery-RA-nexus-v1.7.0.1-cyan.img. When I reboot the phone I attempt to run terminal app from market and find I am still denied permission. I've checked every site I could to correct this, but seem to be missing something every time. When attempting to root, I cd to applications/android-sdk-mac_86/tools/superboot. I press enter then chmod +x-install-superboot-mac.sh Then I press enter and key ./fastboot-mac. After processing in terminal and seeing a status bar briefly on the nexus upper right screen of the Nexus, terminal says Okay. I reboot and no root access. PLEASE HELP. Been at this for an embarrassingly long time now...
Click to expand...
Click to collapse
Try using the nexus-addon-0.1-signed.zip
http://forum.xda-developers.com/showthread.php?t=636795
So I'm a bit of genius and decided I'd try to fully fix my 99% functional phone and have now made it so it won't boot into home screen... I believe I corrupted blur-services.apk and/or blurcontacts.apk, so I get greeted with a series of crash screens.
What I did? I copied over some Bell XT860 system files (including blur-services.apk) from a system dump in Root Explorer, which caused a crash in the middle of copying. After rebooting the phone, it won't properly go into home screen. I tried a system recovery with no luck, oops.
So I'm hoping/assuming that copying over blur-services.apk properly through ADB might solve the issue, but I can't get into ADB on my phone. I've tried using bp-tools & psouza's tool for temp ADB rooting, with no luck -- it won't pickup the connection, even though my phone's storage is available on my computer and clearly connects. Granted, I might be missing a step somewhere...
If someone could guide me into getting into ADB, I can push the blur-services files properly and hopefully regain control over my phone again...
I must say... if I can get this phone operational again, I will stop messing with it!
Two issues...
1) I could use a non-corrupted copy of each of these files [along with their respective odex files]...
2) I can't get into ADB on my phone. I've tried using bp-tools & psouza's tool for temp ADB rooting, with no luck -- it won't pickup the connection, even though my phone's storage is available on my computer and clearly connects.
I must say... if I can get this phone operational again, I will stop messing with it!
Update:
Luckily for me, I was still able to access my gmail and launched Android Market from there. This allowed me to download Go Launcher, GO Contacts, etc. and at least restore functioning to my phone. Most importantly, this enabled me to check off USB debugging (which I lost when I foolishly reset my phone).
So now I've got a semi-functional phone that gives me error messages at least every 30 seconds about one of the .com applications closing.
However, there is hope that I can get her fully functional since I can now obtain ADB access!
---------- Post added at 02:08 AM ---------- Previous post was at 01:44 AM ----------
Sweet, after being able to check USB debugging, I was able to save my self again using psouza4's tools and guidance.... I really have no idea where noobs like me would be without his help!
Main Lessons:
1) Don't play with your phone too much without a proper SBF
2) If you're like me and can't resist, DO NOT FACTORY RESET YOUR PHONE. This only makes the problem worse.
Hey everyone,
first off, I have my Kindle for a few weeks now and it's my first Androit device. I started reading into rooting and adb commands only a few days ago, so please excuse me if I'm not writing accurately with some terms. Additionally, I could not find a similar problem via searching.
Here's my problem (I'll try to be as detailed as possible):
I rooted my KFSOWI running 11.3.1.0 yesterday using Moronigs rooting method. It went well and I had full root access (typing su in an adb shell resulted in an # and all that).
Today I wanted to edit the framework-res.apk to exchange some images. Stupid as I tend to be I wanted to rename the original file and then paste my modified one. The device started giving out various crashes, telling me that lots of apps stopped working. Only then I realised that the file is needed to run the system. Unfortunately the Kindle had shut down at some point and when I boot it now it only gives me a black screen (although the backlight is still on).
Here's what I tried so far:
1. I wanted to adb push the modified file to the system/framework folder, but it tells me that the folder is read-only.
2. So I wanted to change permissions but it seems I don't have root access anymore (I don't even get the # output in the adb-shell after typing su).
3. I tried installing the package via adb but it says "Error: COuld not access package manager. Is the system running?"
I guess it doesn't boot up the package manager and root access. You guys have any idea what I can do right now? Seems like a lost cause to me. And if so, can I try sending it back via warranty?
Any help is very much appreciated. And thanks for all the great work on these forums.
Does nobody have an idea? Would be very sad if I couldn't use it anymore. Although I'm the only one to blame. Does someone have experience on sending it back to amazon for warranty? As far as I know rooted devices lose their warranty.. :-/
Karelian_ said:
Hey everyone,
first off, I have my Kindle for a few weeks now and it's my first Androit device. I started reading into rooting and adb commands only a few days ago, so please excuse me if I'm not writing accurately with some terms. Additionally, I could not find a similar problem via searching.
Here's my problem (I'll try to be as detailed as possible):
I rooted my KFSOWI running 11.3.1.0 yesterday using Moronigs rooting method. It went well and I had full root access (typing su in an adb shell resulted in an # and all that).
Today I wanted to edit the framework-res.apk to exchange some images. Stupid as I tend to be I wanted to rename the original file and then paste my modified one. The device started giving out various crashes, telling me that lots of apps stopped working. Only then I realised that the file is needed to run the system. Unfortunately the Kindle had shut down at some point and when I boot it now it only gives me a black screen (although the backlight is still on).
Here's what I tried so far:
1. I wanted to adb push the modified file to the system/framework folder, but it tells me that the folder is read-only.
2. So I wanted to change permissions but it seems I don't have root access anymore (I don't even get the # output in the adb-shell after typing su).
3. I tried installing the package via adb but it says "Error: COuld not access package manager. Is the system running?"
I guess it doesn't boot up the package manager and root access. You guys have any idea what I can do right now? Seems like a lost cause to me. And if so, can I try sending it back via warranty?
Any help is very much appreciated. And thanks for all the great work on these forums.
Click to expand...
Click to collapse
At this point, I would send it back to Amazon. all they will check for is physical damage and send it back to China. I hear some people bricking their tablet several times and getting a replacement. Thing is that Amazon's warranty questions are only water damage and did you drop it questions. So you don't even have to BS them to get a replacement.
If you have a fast boot cable you might restore it. Now it's not the cable that came with Kindle, it's a special programming cable that will put it into fast boot mode.
Sent from my Amazon Kindle Fire2 using xda app-developers app
braider said:
If you have a fast boot cable you might restore it. Now it's not the cable that came with Kindle, it's a special programming cable that will put it into fast boot mode.
Sent from my Amazon Kindle Fire2 using xda app-developers app
Click to expand...
Click to collapse
There are no exploits for this boot loader yet. Don't think a fastboot cord will do much at the time.
Sent from Nexus 7 flo running SinLess ROM 4.2.2 using xda app-developers app
Did noone come up with a solution, because i did the same thing, with the framework-res.apk
i can make a fastboot cable if itll do any good without an unlocked bootloader. could i possibly push the most recent update.bin from amazon and restore the device to stock???
---------- Post added at 04:06 AM ---------- Previous post was at 03:10 AM ----------
i wouldnt take bricked for an answer and i found a fix
what i did was make sure the kindle was connected to adb and typed the following
adb reboot
adb wait-for-device shell su
the shell managed to snag the SU file and displayed # before the device looped thru all of the boot apps over and over, but then CMD froze.
so i tried this
adb reboot
adb wait-for-device shell su mount -o remount,rw -t ext4 /dev/block/platform/omap/omap.hsmmc.1/by-name/system /system
and in one line got root access and remounted the system as RW
my problem was that framework-res APK was replaced with ZIP so all i had to do was rename it
# cp /system/framework/framework-res.zip /system/framework/framework-res.apk
and success!!
# exit
$ exit
adb reboot
and she booted right up!!!!
First response so please be kind. My KFSOWI is stuck in the bootloop too. I have a factory cable and can get into fastboot but don't have any factory images to restore. Anyone have any ideas?
Do you get any adb access? I don't think casebook will be any help until someone unlocks the bootloader
Sent from my KFSOWI using XDA Premium 4 mobile app
Verified Downgraded from ZVA to ZV6 with full root access
LS991 Sprint Only.
QUICK GUIDE & TESTING
(Please read the entire guide before trying anything.)
I nor anyone at XDA is responsible for anything that may happen to your device.
Simply, by taking incentive to change the stock setup provided by the manufacturer for your device; you assume all responsibility for anything that happens.
download LGUP
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
(Thanks to shakeyabooti)
download LS991ZV6_00.zip and extract to get .tot file with winrar/7zip or any other unzipping program
http://downloads.codefi.re/autoprime/LG/LG_G4/LS991/LS991ZV6/LS991ZV6_00.zip (or google/xda search for mirrors) (Thanks to autoprime)
download LGROOT
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
(Thanks to Unjustified Dev)
download LG Drivers
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772 (or google)
(Thanks to Unjustified Dev)
download rootedsystem.ls991.zip and extract to get .img file with winrar/7zip or any other unzipping program
http://forum.xda-developers.com/sprint-g4/general/zv6-root-success-t3205963/page3
(scroll down to parin11's post. #29 and thank you to both parin11 and mswlogo)
-install drivers
-enable oem unlock in developer settings
-plug device in as charge only, switch to mtp to verify drivers are working correctly, then disconnect
--if on mtp then switch to charge only to verify drivers are working correctly, then disconnect
-enable usb debugging
-reconnect and drivers auto install
-disconnect after 2 minutes.
--while you wait;
-for LGUP extract and install _dll version then the second msi.
-for LGROOT extract to a folder to keep things organized
-remove the back cover of your device and leave it off for access to battery pulls.
-power off device
-hold volume up key and plug in your device and keep holding the volume down key until it passes the screen that says download mode.
-open LGUP
-make sure UPGRADE is checked/has a little circle/bullet point
-click in the empty space directly to the right of where it says BIN with the checkmark
-3 dots will appear to the right of the program in the same row that says BIN; which is your browse option
-navigate to LS991ZV6_00.tot and select
-reconfirm your UPGRADE option is checked
-press start and allow the device to fully complete the process.
-your device will boot to the loading screen right before showing the android desktop and "freeze"
-In most if not all new flash scenarios; your device will not boot up until a factory restore and clear cache is done.
-To do this you must simply remove the battery and usb cable from your device AFTER it has hung on the logo for about 3 minutes / 180 seconds.
(Most new devices average a first time boot of up to 150 seconds maximum to be considered fully "loaded")
-With the battery and cable removed; hold the power and volume DOWN button together at the same time.
-insert the battery while holding these buttons together and just wait while holding them and you will see it says booting into recovery.
-once your in the recovery you use the power key to select and the volume keys to navigate.
-navigate to factory restore/reset hit the power button, navigate to "yes" out of all the "no's" and hit the power button again
-it will say its complete and either ask you to go back reboot or return to menu. RETURN TO THE MENU, do not boot up yet.
-Once returned to the main menu you will see it says clear cache. Select and press yes and now you can select reboot; or return to menu then reboot.
Your device will be on ZV6 stock and fully booted after this.
Now this is where it gets kind of odd because my device never actually loaded the rootedsystemls991.img file nor did I run a root script
when attempting to flash it with the steps listed in the other root guides BUT i followed this guide from step one to step 9 (and outlined continuing through the guide)
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
this allowed all the necessary rooting files to be in the places necessary to execute the root but I did one extra step
I did an adb.exe push rootedsystem.ls991.img /data/local/tmp command as well while the device was on the home screen.
This was so I could basically emulate the command listed by |Unjustified Dev| as it also states to do in the ZV5 guide.
So this is what I did,
-After my device booted up and loaded to the home screen on stock zv6, I opened the LGROOT folder
-held shift and clicked "open command prompt here"
-when cmd opened I ran the following command
adb.exe devices
This allowed me to see that my device was connected to the PC with its generated serial number.
-then i ran the following command
adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp
-After this I applied the command to push the .img file to the same location. This was the "emulated command" I spoke of.
adb.exe push rootedsystem.LS991.ZV6.img /data/local/tmp
-I then added the .img file directly to the Internal Storage / Stock Phone MTP storage
-Afterwards I simply powered off my device, removed the usb cable, held the volume up button, then plugged it back in still holding the volume button until
the text download mode was gone again; and no this is not a timing thing im just saying that again incase anyone forgot how to get into download mode. lol.
-I then ran the ports.bat file included in LGROOT to find the COM port drivers.
-Followed up with this command
Send_Command.exe \\.\COM8 (<--Replace number here with the COM port listed for the "DIAG" portion of the device.)
-Now, still in download mode I executed this command about three times with no avail.
dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
(Which by the way I had the file in both the MTP side of root and in the data/local/tmp)
or you could change it to /data/local/tmp/ like
dd if=/data/local/tmp/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
This would possibly solve the issue I was having. So you would have root now.
THIS PART REQUIRES TESTING.
BUT continue reading you'll be shocked.
sidenote:
They state that all you have to do is put the .img file into the root of your Internal Storage / Stock Phone MTP storage
and run the command in download mode but this failed when I tried to execute it.
dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
The command above was the command they listed to be able to restore the device from stock to stock with root access. Please note I tried this command while the phone was turned on in debugging with enable oem unlock on, while in download mode and while in recovery mode all with debugging and enable oem unlock checked with either no response / device detected, or attempts causing the command prompt to show the # symbol after a few seconds of executing the line above which shouldn't happen,
since the size of the file is 4GB... The ENTIRE SYSTEM PARITION. -_-. There is a considerable amount of hangtime here is what I'm saying.
If the dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0 command worked for you then great, boot up and enjoy root! BUT.
For those who didnt have luck doing so with the command that failed me above, for some odd reason after pushing both the SuperSU bundle and the entire .img file to /data/local/tmp/ with the files in the internal storage /data/media/0/ as well
trying to only execute the command for the .img (/media/0/ not /local/tmp/) | (not the "fixed" command") and NOT for the SuperSU
eg.
-This was for the image which was the only one I used. (USED)
dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
This was for root only which I did not touch. (NOT USED)
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
-This caused the device to simply show the # sign almost immediately as I spoke of above.
-I typed in LEAVE and the device booted back up.
-The odd thing I'm speaking about is when I turned the device back on it showed that SuperSU was installed and was requesting to be "updated".
-I chose normal and it asked for a reboot. Rebooted started back up and it asked for root access when I clicked on it.
-Granted and successful.
-Went to the playstore.
-It said update next to SuperSU which was even odder.
-Clicked it and updated it and it got the latest version, asked for one more reboot, started back up, then I opened the app. Everything was normal.
-Downloaded root checker basic, titanium backup, and greenify immediately.
All passed with flying colors.
-There is an error that pops up in titanium backup regarding adding underscores or slashes into modified file directories for backup purposes assumed but
opening greenify ended up picking up this issue and requesting to fix it.
Why not right?
-Heh. It worked.
I have never experienced this type of latency within programming so this is extremely odd and without executing the SuperSU script command or,
a sucessful flash of the .img it just seems too odd, but; there you have it! All of the mods / developers working on this device I would like to hear
your insight on this.
So you have two options. Follow what I did or test the command with /data/local/tmp/ and try your luck flashing stock with root again or just run the root script on stock instead of trying to flash from stock to stock rooted.
Thank you and enjoy your root!
P.S. I didn't end up experiencing this issue since it works perfectly but in the event that SuperSU does not install after trying to flash the .img and getting
the 2 second delay with the # sign appearing immediately and rebooting after 3 attempts I would have personally tested the original adb SuperSU script command recommended for the ZV5 users
which was listed above and is
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
And for the love of your device. Don't try to update your device from an older version using this method. Ayeeeyiyiy
I will re-test what I stated and make a completely organized guide and video for everyone.
I just wanted to let you all know now to assist the entire community in understanding this device's root process a little more.
Will this work with brand new phone?
This method looks exactly like what I would need if I were to sign up with Sprint and get a brand new G4 from them. I just want to make sure that this method would work on the brand new phone to get root access and possibly flash new ROMs to the device. I have gotten burned before by getting devices that I think would work only to find out I had gotten an unsupported variant. Any knowledge would be greatly appreciated. Thank you.
wow, thanks!
Thanks for all your hard work. This phone has been one of my best and the only thing missing has been root, etc. Chewing over your instructions and thoughts. My confidence level is not quite there to pull the trigger, but i'm getting close. Hoping this is a promising method for those of us on Sprint ZVA. I will continue to do research and watch this thread. Thanks so much for your time, tips and expertise.
brpaaron said:
This method looks exactly like what I would need if I were to sign up with Sprint and get a brand new G4 from them. I just want to make sure that this method would work on the brand new phone to get root access and possibly flash new ROMs to the device. I have gotten burned before by getting devices that I think would work only to find out I had gotten an unsupported variant. Any knowledge would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
As long as its not been updated to zvb. Antirollback implemented on zvb
Still running zv6
I am still running zv6 and never updated. Do I need to update to downgrade to root or can I just skip to after the downgrade?
i am running zv9 i can not stock zv6
I have ZVC can i downgrade to ZV6?
LG G4 LS991.
LG G3 D850 ROM Fulmics 6.6
Recovery TWRP v2.8.7.0 bumped
LS991 ZVD
Hi there does anyone know whether or not it will work on the ls991 zvd update??? Sprint variant
Ls 991 ZVD
Will this method work on ls991 zvd i havent found anything on it
Expo6810 said:
Will this method work on ls991 zvd i havent found anything on it
Click to expand...
Click to collapse
No. Zva or lower. You will brick it.
---------- Post added at 02:28 AM ---------- Previous post was at 02:28 AM ----------
No zva or lower
TheMadScientist420 said:
No. Zva or lower. You will brick it.
---------- Post added at 02:28 AM ---------- Previous post was at 02:28 AM ----------
No zva or lower
Click to expand...
Click to collapse
Is there anything i can do for my zvd
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
as far as i know. nothing
new root methods and tweaks come out everyday.
all the good devs as far as i know have stopped developing g4 and moved on due to the locked bootloader d other issues
---------- Post added at 09:24 AM ---------- Previous post was at 09:17 AM ----------
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
a root method has been exposed on the g5
intime it may come for the g4 also but not adapted rite now
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
Right now i have ZVC software version can i downgrade zv6????
hawzsth said:
Right now i have ZVC software version can i downgrade zv6????
Click to expand...
Click to collapse
no u will brick
TheMadScientist420 said:
no u will brick
Click to expand...
Click to collapse
its already brick any solution...... now its show 9008 no power on ...
hawzsth said:
its already brick any solution...... now its show 9008 no power on ...
Click to expand...
Click to collapse
octoplus box with jtags the only fix
thats a hardbrick
---------- Post added at 08:30 AM ---------- Previous post was at 08:29 AM ----------
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
as of rite now no
If I downgrade my zva will it allow me to sim unlock it
Somebody know if can downgrade ZVI to another version
Pls any update on locked bootloader?
Thank you!
Just learned here enough. Thank you!
I just head through UsU thread after reading this; Respectively thanks for the post again! ??
Hi all,
Found my old Kindle Fire2 lying around so thought i'd have a go at building whatever I can for it. Seems like there was already source code in the repo's for CM 12.1 but nobody had built it. Well I've built it and it seems to work fine!
Only had to fix a script which had broken since CM 11 for wifi and all seems good.
NOTE RE MAC ADDRESS
FYI your MAC address will now get randomly generated at first boot. If keeping your existing MAC address is important, don't flash this.
I can't take any responsiblity for this, I've purely built it and fixed a couple of issues. Please thank whoever contributed to the source in the repo's.
I've only installed from a complete wipe. Don't try it unless you're prepared to wipe your device.
Enjoy...
ROM
cm-12.1-20170728-UNOFFICIAL-otter2.zip
Open Gapps pico for 5.1
http://opengapps.org/?download=true&arch=arm&api=5.1&variant=pico
Going to have a go at building CM13 next. Tried 14.1 but got hung up on selinux issues so going to take a step back to CM13.
Original link fixed
I need to fix the wifi script at boot. Currently if you install the rom you'll need to open a terminal and run:
/system/bin/fix-mac.sh
Wifi should start shortly after...
works perfect.
also perfect timing. i picked the otter2 yesterday from my dads house, who didnt use it anymore, because he switched to an galaxy tab long time ago.
I am currently having trouble with the Wi-Fi
It just hangs at Turning on Wi-Fi!
I have tried to clear cache and dalvik cache after installing gapps and lineage
I also performed a full wipe before flashing the rom
EDIT: Sorry didn't read further down
I am having an interesting problem with this ROM. It appears stable until I install any app, either from APK or play store. afterward everything force closes and will not work again until data is wiped or permissions repaired. when the permissions are repaired, any installed apps from APK or play store vanish like they were never installed. copying anything to /system/app works fine, but that is not a long term solution.
Raised a couple of threads about the wifi issue for a bit of help but nobody had replied. I'll have another look when I have time. Can't say i had any issues after installing app's though.
Think I might have fixed the selinux policy as i misread the neverallow rule and didn't realise it actually excludes sdcards from remount, so I can explicitly allow it.
Hopefully new fixed build to come soon.
Hi, I know a few people have asked about the Wi-Fi issue, but im not aware of how to open a terminal once everything is installed. the only terminal I can find is in the recovery mode but it wont find the file you mentioned
I just flashed and executed /system/bin/fix-mac.sh after installing "super su", but still WIFI does not start. Any additional hints? Thank you very much for the efforts.
Found a working solution:
1. Activate terminal in settings
2. Install latest SuperSU
3. Open terminal and execute "su 0 setenforce 0"
4. Execute "/system/bin/fix-mac.sh" afterwards
--> WIFI should start and "stay alive"
guys do you have the latest twrp for kf2? all links are dead on other threads.
Apologies if this is obvious - but how did you install the latest SuperSU without Wi-Fi? Is it a case of downloading the apk and transferring via adb?
Is the build working otherwise? The old CM one is beyond repair - works for a couple days and then gets itself into boot loop.
Thanks!
androidbenutzer said:
Found a working solution:
1. Activate terminal in settings
2. Install latest SuperSU
3. Open terminal and execute "su 0 setenforce 0"
4. Execute "/system/bin/fix-mac.sh" afterwards
--> WIFI should start and "stay alive"
Click to expand...
Click to collapse
---------- Post added at 09:30 AM ---------- Previous post was at 09:21 AM ----------
[/COLOR]
androidbenutzer said:
Found a working solution:
1. Activate terminal in settings
2. Install latest SuperSU
3. Open terminal and execute "su 0 setenforce 0"
4. Execute "/system/bin/fix-mac.sh" afterwards
--> WIFI should start and "stay alive"
Click to expand...
Click to collapse
not work:crying:
rapmen said:
---------- Post added at 09:30 AM ---------- Previous post was at 09:21 AM ----------
[/COLOR]
not work:crying:
Click to expand...
Click to collapse
Same here... all steps ok, but Wi-Fi still won't turn on. Heart-breaking! Build working fine otherwise...
nebula_rider said:
Same here... all steps ok, but Wi-Fi still won't turn on. Heart-breaking! Build working fine otherwise...
Click to expand...
Click to collapse
I bricked my Otter2 today, so I had to restart all over:
1. Flash the Android-Image in TWRP
2. Flash the GAPPS-Pico-Image in TWRP
3. Flash the SuperSU-Image in TWRP
4. Allow the Terminal in the Android developer settings
5. Open the terminal and execute "su 0 setenforce 0"
6. Allow "root" in the appearing popup.
7. Execute "/system/bin/fix-mac.sh"
8. Activate WIFI
9. Done
This works!
androidbenutzer said:
I bricked my Otter2 today, so I had to restart all over:
1. Flash the Android-Image in TWRP
2. Flash the GAPPS-Pico-Image in TWRP
3. Flash the SuperSU-Image in TWRP
4. Allow the Terminal in the Android developer settings
5. Open the terminal and execute "su 0 setenforce 0"
6. Allow "root" in the appearing popup.
7. Execute "/system/bin/fix-mac.sh"
8. Activate WIFI
9. Done
This works!
Click to expand...
Click to collapse
Ok so I gave this another go - thanks for the encouragement androidbenutzer! - and can confirm that it does, indeed, work!
My problem was with step number 7. This is going to sound so so lame, but I was just typing "system/bin/fix-mac/sh" on Terminal (without the quotes). It looked like Android was trying to run fix-mac.sh, but failing to mount something. For the fellow rookies out there, you first need to navigate to /system/bin. I'm sure there's a very simple way to do this, but since I know no better, this is how I did it:
cd\
cd system
cd bin
THEN type "fix-mac.sh" (without the quotes).
Wi-Fi switched on and remained on.
Thanks dom_b and androidbenutzer! So glad to have the wee otter2 up and running again!
nebula_rider said:
Ok so I gave this another go - thanks for the encouragement androidbenutzer! - and can confirm that it does, indeed, work!
My problem was with step number 7. This is going to sound so so lame, but I was just typing "system/bin/fix-mac/sh" on Terminal (without the quotes). It looked like Android was trying to run fix-mac.sh, but failing to mount something. For the fellow rookies out there, you first need to navigate to /system/bin. I'm sure there's a very simple way to do this, but since I know no better, this is how I did it:
cd\
cd system
cd bin
THEN type "fix-mac.sh" (without the quotes).
Wi-Fi switched on and remained on.
Thanks dom_b and androidbenutzer! So glad to have the wee otter2 up and running again!
Click to expand...
Click to collapse
I tried all the steps, and still no luck.
pakidermo5000 said:
I tried all the steps, and still no luck.
Click to expand...
Click to collapse
Actually you wouldn't get too far even if you could turn the wi-fi on. The build is plagued with the "Trebuchet has stopped" error, which apparently is common in CM. I tried every fix recommended online, without success.
I didn't read the entire thread but here's a super easy way to fix the wifi issue. Connect a USB cable from the Otter2 to your computer. Make sure you have adb installed. Open a command prompt and type:
adb.exe /devices
Now look at the security message on the tablet. Click yes
adb.exe shell
At the shell prompt, type the following:
[email protected]:/ # /system/bin/fix-mac.sh
---------- Post added at 02:42 PM ---------- Previous post was at 02:05 PM ----------
SuperSu is here:
http://rootmygalaxy.net/download-latest-supersu-v2-82/