Related
Some PPL on the development forums were asking how to boot $auron's UrukDroid out of bubu's openAOS Boot Menu. Since i can't post there yet, i'll post here.
I looked at bubu's initramfs/init script and it should be fairly easy to boot any partition as well as any rootfs.img.
the menu.lst syntax is:
Code:
{NAME(has to be unique)}|{DEVICE(leave blank for img)}|{IMG}|{INIT}
A special thing is putting 'ARCHOS' into {DEVICE}, because that will boot from ARCHOS' stock SQUASHFS file
so adding this line to menu.txt should let you boot UrukDroid from sdcard
Code:
UrukDoid|/dev/mmcblk2p2||/sbin/init
I have to add, i havn't tried it myself yet, because i haven't put bubu's loader on my A70IT yet.
I would really appreciate you letting me know if it works!
Greetings Oro
Orochimarufan said:
Some PPL on the development forums were asking how to boot $auron's UrukDroid out of bubu's openAOS Boot Menu. Since i can't post there yet, i'll post here.
I looked at bubu's initramfs/init script and it should be fairly easy to boot any partition as well as any rootfs.img.
the menu.lst syntax is:
Code:
{NAME(has to be unique)}|{DEVICE(leave blank for img)}|{IMG}|{INIT}
A special thing is putting 'ARCHOS' into {DEVICE}, because that will boot from ARCHOS' stock SQUASHFS file
so adding this line to menu.txt should let you boot UrukDroid from sdcard
Code:
UrukDoid|/dev/mmcblk2p2||/sbin/init
I have to add, i havn't tried it myself yet, because i haven't put bubu's loader on my A70IT yet.
I would really appreciate you letting me know if it works!
Greetings Oro
Click to expand...
Click to collapse
First:
Thanks for your work
Would this also work, with on internal installed urukdroid?
You would have to get the device name of your root partition
since mine is a sdcard install i can only provide that information.
but if you can boot into uruk right now you can do the following to get the device node:
Open any terminal emulator and type:
Code:
cat /etc/mtab
then search for
Code:
<device> / <fstype> rw,noatime,barrier=1,nodealloc,....
in my case that is:
Code:
/dev/mmcblk2p2 / ext4 ....
take the first one (<device>) and put it into the menu.lst line:
Code:
UrukDroid|<device>||/sbin/init
still i haven't tested any of this. it's just the result of my looking at the bootloader's init script
Greetings oro
Orochimarufan said:
but if you can boot into uruk right now you can do the following to get the device node
Click to expand...
Click to collapse
I cant i installed the openaos boot menu, so urukdroid is gone...
I really want to have uruk again, i hate the stock firmware
I know these steps, but is there no way to compile a *.img from uruk?...
i compiled one but these dont worked...
first of all IMO putting Uruk into an image file would be stupid,
second you'd have to either find a way to run the installer on your computer, or ask $auron what exactly it does and put a working rootfs togehter manually or dump an existing thing
your best bet would be to boot openAOS and dd Uruk's Root Partition into some img file. But since you don't know which yout Uruk Root is and i don't either, only thing left would be to ask $auron where he installs it. and if you know that, you can use my method just as well
greetings
Orochimarufan said:
Only thing left would be to ask $auron where he installs it. and if you know that, you can use my method just as well.
Click to expand...
Click to collapse
Okey, i`ll do
Then i have to install urukdroid and after that install the openaos boot menu?
Nope
if you've got the device node of yout Uruk root you should be able to put it into that menu.lst lint i showed you where <device> is.
Just to mention it, I don't know if $auron provides a working live-initramfs, but if he does you should be able to simply flash that through the sde recovery menu.
by live-initramfs i mean one, that doesn't launch EasyInstall but run UrukDroid directly.
greetings
Orochimarufan said:
Nope
if you've got the device node of yout Uruk root you should be able to put it into that menu.lst lint i showed you where <device> is.
Click to expand...
Click to collapse
Yeah, i understand that.. but how do i install uruk?...
sorry i dont understand
Just to mention it, I don't know if $auron provides a working live-initramfs, but if he does you should be able to simply flash that through the sde recovery menu.
by live-initramfs i mean one, that doesn't launch EasyInstall but run UrukDroid directly.
greetings
Click to expand...
Click to collapse
i aksed sauron per pm
Hmm.. how do i explain.
It's like this:
the device node is like a link to the partition.
If you put Uruk on a Partition, you have to tell the bootloader which partition is the right one, the one with Uruk on it.
The bootloader then searches for an init-file there and executes it
so bubu's menu is the bootloader in this case, so you tell him where he has to search for Uruk by putting the right device node into the menu.lst.
hope you understand it a little better now
greetings
Orochimarufan said:
Hmm.. how do i explain.
It's like this:
the device node is like a link to the partition.
If you put Uruk on a Partition, you have to tell the bootloader which partition is the right one, the one with Uruk on it.
The bootloader then searches for an init-file there and executes it
Click to expand...
Click to collapse
Yes, so first i have to install Urukdroid, because if i dont, bootloader doesnt find anything or not?
so bubu's menu is the bootloader in this case, so you tell him where he has to search for Uruk by putting the right device node into the menu.lst.
hope you understand it a little better now
Click to expand...
Click to collapse
Yep, thanks
I´m still a bit new in booting
Nope, because you installed it already.
You said you had an existing installation on your internal memory, didn`t you?
You just have to find out where it is. And tell that information to the bootloader.
Greetings
TapaTalk on A70IT here -- who's there?
Orochimarufan said:
Nope, because you installed it already.
You said you had an existing installation on your internal memory, didn`t you?
You just have to find out where it is. And tell that information to the bootloader.
Click to expand...
Click to collapse
I had have a Urukdroid installation, before i installed the boot menu i completly wiped my archos for a completly frsh install
Okay then youre right. If there's nothing he obviousli cant execute anything.
So if yuo installed it again, would you be kind enough and report back the device node?
Greetings
TapaTalk on A70IT here -- who's there?
Orochimarufan said:
Okay then youre right. If there's nothing he obviousli cant execute anything.
So if yuo installed it again, would you be kind enough and report back the device node?
Greetings
TapaTalk on A70IT here -- who's there?
Click to expand...
Click to collapse
Yep, but i dont do it today, its getting late (school)
I`ll do it tomorrow, thanks for your help!
Yeah youre right and i've to go to school tomorrow too... an a friend of mine is goong to write her final exams in english... guess i'm going to have more than just this problem tomorrow
Just so you know, we'll visit some relatives this weekend, so i wont be here then.
Greetings
TapaTalk on A70IT here -- who's there?
Orochimarufan said:
Yeah youre right and i've to go to school tomorrow too... an a friend of mine is goong to write her final exams in english... guess i'm going to have more than just this problem tomorrow
Just so you know, we'll visit some relatives this weekend, so i wont be here then.
Greetings
TapaTalk on A70IT here -- who's there?
Click to expand...
Click to collapse
Okey, i'll try it and i'll see
another question: any idea how to get the menu booting instead of normal archos android?
(Sde instead of archos, like sauron did at urukdroid)
What exactly do you mean?
Like switching between custom and stock?
That'd be for hold voldown while the archos bootscreen shows up and selecting SDE or Android.
And the SDE entry will launch whatever you put there through the SDE recovery Menu
Greetings
TapaTalk on A70IT here -- who's there?
No, he mean booting on it not by going in the recovery menu, just on pushing the "ON" button.
eagleofdeath13 said:
No, he mean booting on it not by going in the recovery menu, just on pushing the "ON" button.
Click to expand...
Click to collapse
Yep, this will be helpful, when i have urukdroid on my boot menu, because then my normal use will be uruk, until cyanogen is ready for saily use..
Any hints on that?
I don't really know, but doesn't it remember your last choice?
TapaTalk on A70IT here -- who's there?
Hi,
I finally got very own pair of Google Glass, HAPPY
and I've done a little hack so far...
What works?
Install a launcher on Glass (i used holo launcher)
playback youtube.apk videos
What doesnt work?
Google Play services (cannot install, i guess some mod is required?)
Google Play Store (you can open the store, but when you try to download something, FC comes)
Semi-work?
Bluetooth mouse, but keyboard doesnt work(cannot type any letter or number), but the hotkey on the keyboard works (no idea why, but i ordered the keyboard&mouse bundled bluetooth device to get basic thing working) [Razer Orochi + Apple Bluetooth Keyboard]
If anyone want to ask something or wanna me try something fun on the Glass, please ask!
I would love to see the great potential of this little android devices
Dump.. EVERYTHING.
I need a complete dump of every part of Glass so I can work on creating a decent ROM for phones.
You could try shoveling through the files for Google Play and see if it requires any frameworks and if so, then copy those from a nexus device.
ytwytw said:
Hi,
I finally got very own pair of Google Glass, HAPPY
and I've done a little hack so far...
What works?
Install a launcher on Glass (i used holo launcher)
playback youtube.apk videos
What doesnt work?
Google Play services (cannot install, i guess some mod is required?)
Google Play Store (you can open the store, but when you try to download something, FC comes)
Semi-work?
Bluetooth mouse, but keyboard doesnt work(cannot type any letter or number), but the hotkey on the keyboard works (no idea why, but i ordered the keyboard&mouse bundled bluetooth device to get basic thing working) [Razer Orochi + Apple Bluetooth Keyboard]
If anyone want to ask something or wanna me try something fun on the Glass, please ask!
I would love to see the great potential of this little android devices
Click to expand...
Click to collapse
Like you suspect, it could be your keyboard. They demo'd something similiar to this keyboard at the Hacking Glass talk at I/O
I know and i did order that keyboard and its on the way
Sent from my HTC One using Tapatalk 2
TonyStark23 said:
Dump.. EVERYTHING.
I need a complete dump of every part of Glass so I can work on creating a decent ROM for phones.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2271315
[SYSTEM DUMP][DEV] Google Glass XE5
i guess this is what you need?
or let me know how to dump it
Sent from my HTC One using Tapatalk 2
-a- said:
You could try shoveling through the files for Google Play and see if it requires any frameworks and if so, then copy those from a nexus device.
Click to expand...
Click to collapse
i would love to try but it cant be done without root access and I don't want to root my Glass without factory image from Google
Sent from my HTC One using Tapatalk 2
ytwytw said:
i would love to try but it cant be done without root access and I don't want to root my Glass without factory image from Google
Click to expand...
Click to collapse
TheManii said:
Just to organize everything:
glass_1-img-201305051837.zip
boot.img
recovery.img
system.img
c17357b01ac6.signed-glass_1-665738-from-625737.c17357b0.zip
fpga.img
MLO
u-boot.bin
The first link is the factory image for XRR35 (XE5) from google, the 2nd link is the OTA from XRR02 -> XRR35 (ie XE4 -> XE5)
Click to expand...
Click to collapse
Could you make a list of the partitions on the gGlass to see if we're actually missing any bootloader pieces?
I would assume that fpga.img/MLO/u-boot.bin would make up all the leftover pieces, but we could certianly use a confirmation.
Code:
/dev/block/platform/<omap something>.1(?)/by-name
would be a good place to start, you may need to be rooted but goog's posted enough files to revert that when needed.
I was going to be ballsy and try flashing the image onto a Gnex, I'm actually curious if anyone will attempt to make a Glass ROM for other devices.
TheManii said:
Could you make a list of the partitions on the gGlass to see if we're actually missing any bootloader pieces?
I would assume that fpga.img/MLO/u-boot.bin would make up all the leftover pieces, but we could certianly use a confirmation.
Code:
/dev/block/platform/<omap something>.1(?)/by-name
would be a good place to start, you may need to be rooted but goog's posted enough files to revert that when needed.
Click to expand...
Click to collapse
[email protected]:/dev/block/platform/omap/omap_hsmmc.1 $ ls
by-name
by-num
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
[email protected]:/dev/block/platform/omap/omap_hsmmc.1 $
I guess is this what you need?
TonyStark23 said:
I was going to be ballsy and try flashing the image onto a Gnex, I'm actually curious if anyone will attempt to make a Glass ROM for other devices.
Click to expand...
Click to collapse
https://github.com/zhuowei/Xenologer
i believe just simply install those apk + pie control (to emulate hardware key) is great enough to get GLASS experience on current android devices
ytwytw said:
[email protected]:/dev/block/platform/omap/omap_hsmmc.1 $ ls
by-name
I guess is this what you need?
Click to expand...
Click to collapse
could you do inside the by-name folder?
permission denied
i just back from work, gonna install ubuntu on my pc and unlock bootloader & root it
Sent from my HTC One using Tapatalk 2
This actually has huge potential because I think these Glass apps can be a viable replacement of car mode in our phone. Tasker+Glass app=awesomeness over 9000
spent 3 days on rooting glass
My computer cannot find Glass when its in Fastboot mode, and i tried another machine, fastboot devices works, but after i excute fastboot oem unlock, Glass hangs... damn... and the genetic 4.0.3 root not working either...
Sent from my HTC One using Tapatalk 4 Beta
ytwytw said:
spent 3 days on rooting glass
My computer cannot find Glass when its in Fastboot mode, and i tried another machine, fastboot devices works, but after i excute fastboot oem unlock, Glass hangs... damn... and the genetic 4.0.3 root not working either...
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Try using my tool.
Sent from my Kindle Fire HD 7 using xda app-developers app
-a- said:
Try using my tool.
Sent from my Kindle Fire HD 7 using xda app-developers app
Click to expand...
Click to collapse
Here is the problem, my Windows Machine cannot even see Glass if I do "adb devices", when I reboot the Glass into fastboot mode, connecting to the windows machine, it simply says the USB device has problem, please unplug and plug in again
On my mac machine, I tried to run your bat manually, it doesn't work, which I am not surprised (the exploit only works on XE4, not XE5, and its Android 4.0.3 only, 4.0.4 wont work)
and when I try to unlock bootloader on my Mac, I have the following error
$ fastboot oem unlock
< waiting for device >
...
(bootloader) Warning: Unlocking your device will void your warranty
(bootloader) and erase your personal data from the device.
(bootloader) Run "fastboot oem unlock" again to confirm.
(bootloader) Device still locked.
OKAY [ 0.001s]
finished. total time: 0.001s
$ fastboot oem unlock
...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.149s
$ fastboot oem unlock
...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 230.879s
$
I also tried a ubuntu machine, adb devices can see Glass, but after i reboot into bootloader, fastboot devices wont see Glass anymore
I am MAD, just saying, I have a N4 and HTC One, both works great on Windows, Mac and Ubuntu Machine, no issue at all, so... IDK if google did some trick somewhere IDK
ytwytw said:
Here is the problem, my Windows Machine cannot even see Glass if I do "adb devices", when I reboot the Glass into fastboot mode, connecting to the windows machine, it simply says the USB device has problem, please unplug and plug in again
On my mac machine, I tried to run your bat manually, it doesn't work, which I am not surprised (the exploit only works on XE4, not XE5, and its Android 4.0.3 only, 4.0.4 wont work)
and when I try to unlock bootloader on my Mac, I have the following error
$ fastboot oem unlock
< waiting for device >
...
(bootloader) Warning: Unlocking your device will void your warranty
(bootloader) and erase your personal data from the device.
(bootloader) Run "fastboot oem unlock" again to confirm.
(bootloader) Device still locked.
OKAY [ 0.001s]
finished. total time: 0.001s
$ fastboot oem unlock
...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.149s
$ fastboot oem unlock
...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 230.879s
$
I also tried a ubuntu machine, adb devices can see Glass, but after i reboot into bootloader, fastboot devices wont see Glass anymore
I am MAD, just saying, I have a N4 and HTC One, both works great on Windows, Mac and Ubuntu Machine, no issue at all, so... IDK if google did some trick somewhere IDK
Click to expand...
Click to collapse
Follow the tutorial I linked for the adb drivers in my thread on rooting the glass
Sent from my Amazon Kindle Fire HD using xda app-developers app
-a- said:
Follow the tutorial I linked for the adb drivers in my thread on rooting the glass
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
The problem is... there is no yellow warning sign in device manager, only Glass 1 Camera device listed in device manager :[
tried to force update that driver, but win8 doesnt allow me to do so (driver signature already turn off as I am using other toolbox)
TheManii said:
could you do inside the by-name folder?
Click to expand...
Click to collapse
just flashed insecured boot, and here is your need
[email protected]:/dev/block/platform/omap/omap_hsmmc.1/by-name # ls
boot
bootconfig
bootloader
cache
fpga
recovery
system
userdata
xloader
[email protected]:/dev/block/platform/omap/omap_hsmmc.1/by-name #
Hi all
Im trying to compile OmniRom for Galaxy Note 2 N7100.
Did everything as instructed.
When running "brunch n7100" I have an error:
=============================================
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/n7100/omni_n7100.mk]]: "vendor/samsung/smdk4412-common/common-vendor.mk" does not exist. Stop.
WARNING: Trying to fetch a device that's already there
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/n7100/omni_n7100.mk]]: "vendor/samsung/smdk4412-common/common-vendor.mk" does not exist. Stop.
** Don't have a product spec for: 'omni_n7100'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
=============================================
What should I do to fix it?
Thanks
EDIT: OK, "The Muppets", of cause. Not it builds...
sms2000 said:
EDIT: OK, "The Muppets", of cause. Not it builds...
Click to expand...
Click to collapse
First off, I'd use DonkeyCoyote instead of TheMuppets. Entropy said TheMuppets wouldn't work, but he might have been speaking about only one device. Still I'd use DonkeyCoyote instead.
Still not building?
PonsAsinorem said:
First off, I'd use DonkeyCoyote instead of TheMuppets. Entropy said TheMuppets wouldn't work, but he might have been speaking about only one device. Still I'd use DonkeyCoyote instead.
Still not building?
Click to expand...
Click to collapse
I'm using VM on Win7 8Gb machine so it's slow. Last time it stopped on Email right after successfully building boot.img.
Attempting to rebuild.
I'll try my next with DonkeyCoyote.
sms2000 said:
I'm using VM on Win7 8Gb machine so it's slow. Last time it stopped on Email right after successfully building boot.img.
Attempting to rebuild.
I'll try my next with DonkeyCoyote.
Click to expand...
Click to collapse
It didn't not stop...
Actually it is compiling libchromodium.so (forget how it spell), which is 1.2GB in size.
Just let it run for few hours, it will completed eventually.
PS: I'm using VM on Win8.1 4GB, no complain here.
Sent from Windows 98
Yep, it fails again and again on 'libwebviewchromium.so'. The well known 'Error 1' aka not enough RAM.
I recently built a dedicated computer (8Gb + Haswell 3220) just for ROM compiler but have no time to install it properly. Dealing with VMs is not good.
My VM has 4Gb RAM of total 8Gb installed. I know I need 8+ but have to wait till new RAM received.
For now the thread is on hold.
Thanks for all your help.
EDIT: Just for the small experiment I added a 8Gb 'swap' partition to VM and the following build succeeded using no more than 450Mb of it.
I think we need 6 to 8Gb of RAM for good.
Now the question is would it boot and run for good? But we will see...
Ya I did set the swap partition to 8gb... And it will boot nicely.
If it didn't boot, jus replace/delete the media_profiles.xml
Another note, my Bluetooth and hardware decoding /encoding fail... Pls test it on ur system too.
Sent from Windows 98
dynomist said:
Ya I did set the swap partition to 8gb... And it will boot nicely.
If it didn't boot, jus replace/delete the media_profiles.xml
Another note, my Bluetooth and hardware decoding /encoding fail... Pls test it on ur system too.
Sent from Windows 98
Click to expand...
Click to collapse
I indeed failed to boot. Just the black screen with nothing. I think it was a very bad idea to use TheMuppets with "jallybean".
And what is "media_profiles.xml" for? And where?
U r using jb blob?
i think OmniRom hv all the stuff u need
http://docs.omnirom.org/Samsung_Galaxy_Note_II
___
Btw did ur screen show omnirom animation?
If yes u r lucky, u need to enabled the ro.adb.secure=0 in ur build.prop, then only you can use adb without authorization to troubleshoot.
Type# adb logcat > logcat.txt
___
Google media profile...
Sent from Windows 98
dynomist said:
U r using jb blob?
i think OmniRom hv all the stuff u need
http://docs.omnirom.org/Samsung_Galaxy_Note_II
___
Btw did ur screen show omnirom animation?
If yes u r lucky, u need to enabled the ro.adb.secure=0 in ur build.prop, then only you can use adb without authorization to troubleshoot.
Type# adb logcat > logcat.txt
___
Google media profile...
Sent from Windows 98
Click to expand...
Click to collapse
Yes, if you can download the closed source parts from the phone itself. I cannot. Something wrong with switching 'adbd' to 'root'. It switches sort of but locks at the downloading (never finishes).
Currently I'm recompiling with 'DonkeyCoyote'.
'Nightly' build fails to pass boot animation
I downloaded and installed OmniRom Nightly. Not good.
It cannot pass the boot animation. The OMNI BA just loops across different colors for 15 minutes already.
As I remember the same problem I have with any AOSP or CM ROM. I suspect the problem is the boot loader related.
When I installed my first 4.3 ROM it required the latest BL and I flashed it. Should I downgrade now? Which version of BL works for sure and where can I find it?
Thanks.
EDIT: I verified. My Bootloader - MJ5. Is it OK?
EDIT 2: Downgraded to DMF2 and succeeded installing OmniRom Nightly. Testing...
glad that you able to solve the booting prob...
pls update the roms status after u done with your testing
UPDATE 2022-03-05: Network Access Snafu
During the last week or so, a server-side issue caused 1-Click to fail
either silently or with a "1-Click needs network access!" message
on startup. If you experienced the above, please try again!
Changed:
VirtualBox 6.1.x support (tested with 6.1.16)
works fine on Linux with Firefox and USB2 ports
tends to be flaky on MacOS with Safari; PLEASE use Firefox or Chrome!!
may need to connect via a USB2 hub or try different ports and cables
More accurate state assessment (i.e. rooted/unlocked/etc)
More aggressive planning logic
always look for ROM/GAPPS/SU in internal storage
may end up offering choices that make very little sense
Assorted fixes and improvements
hopefully fewer new bugs were introduced than old ones fixed
Unchanged:
No prerequisites on the device side
no root needed
full stock is OK
stuck in fastboot is fine
heck, it even works with _some_ soft-bricks
Does NOT work on Windows
1-Click is a virtual machine and a script that starts the VM in VirtualBox.
Unfortunately, VirtualBox on Windows fails to pass certain USB devices
including the HDX in bulk mode from Windows to the VM.
Network access required to grab the right aboot + TWRP for your device
Optional TWRP magic to auto-install ROM.zip, GAPPS.zip, and SU.zip from internal storage
PM me for a personal link and please state your regular HOST operating system.
Gotchas:
Requests without HOST OS information will be ignored.
Naturally, the same applies to requests with a Windows HOST OS.
Running 1-Click inside another VM is almost guaranteed NOT to work.
Link requests should be sent at the earliest 2 weeks after join date.
Freshly joined members are encouraged to spend some time
familiarizing themselves with the details of working with this device
by studying the relevant threads in this forum.
If you send a request be sure to monitor your account for replies!
A response should arrive within a week (or so), but the link is only valid for 2 days.
Don't miss your chance!
draxie said:
Title says it all..
(Well, almost: you need a vulnerable bootloader,
i.e. 3.2.3.2 or earlier, that foolishly accepts forged
signatures...)
Download and unpack the attached zip file.
Run the right '1-Click' script for your platform
(that is, '1-Click.bat' for Windows users,
and '1-Click' on OS X and Linux).
Simply clicking on the script works in Windows and OS X.
On these more "one-size fits all" operating systems, the scripts
-modulo network connectivity- will also download and install
VirtualBox, if it's not already installed.
Linux users need either VirtualBox or QEMU installed.
There are simply too many variants to automate this
for all the different distros. Sorry...
On some Linux variants, instead of launching the script
the click action opens the script in editor... YMMV
This may, in fact, be very useful, since on some of the same
Linux variants the script has to be run as root to avoid
automounters taking precedence; in which case, you're
well advised to make sure you read and understand what
the script is doing before you run it as root, because I take no
-that is: ZERO- responsibility for any damage that may result.
I personally tested the scripts on
Linux: Mint 17.2 (both 32-bit and 64-bit versions)
OS X: Mountain Lion, Yosemite, El Capitan
Windows: 7, 8.1, 10
The 1-Click VM runs a minimal Linux system with adb/fastboot
and a pure C "cuber" using OpenSSL's BigNum library.
No need to download adb/fastboot, python, or worry about
drivers on your host system.
Good luck!
Click to expand...
Click to collapse
Very cool! Will be interesting to try this out (have to wait for a someone with an eligible device that is willing to give it a whirl).
Any takers?
Davey126 said:
Very cool! Will be interesting to try this out (have to wait for a someone with an eligible device that is willing to give it a whirl).
Click to expand...
Click to collapse
BTW, this works with already unlocked devices also,
if anyone is willing to do some independent testing.
This is how I tested also... should be completely harmless.
Ran this against my HDX 7
Puttytel reported an 'error reading from serial device', but after it had initiated device shutdown so just a gui annoyance (I'm on windows, so commonplace.) It seemed to work, but I haven't verified yet..
> fastboot -i 0x1949 oem device-info
kindle fire [fastboot]
oem device-info...Device tampered: false
Ok.
I'll do some more testing later.
codeshane said:
Puttytel reported an 'error reading from serial device', but after it had initiated device shutdown so just a gui annoyance (I'm on windows, so commonplace.) It seemed to work, but I haven't verified yet..
> fastboot -i 0x1949 oem device-info
kindle fire [fastboot]
oem device-info...Device tampered: false
Ok.
I'll do some more testing later.
Click to expand...
Click to collapse
Thanks for reporting back!
The puttytel message is normal: the serial port it's talking to
disappears when the VM shuts down.
If/when you test again do check your Kindle after the fastboot prompt
appears but **before** you hit [Enter] in the puttytel window!
You should see "Unlock code correct" in green,
if the unlock worked...
Other than that, since you seem to have fastboot working, you can use
Code:
fastboot -i 0x1949 oem idme ?
to see if your device is unlocked (see here for a list of commands).
draxie said:
Other than that, since you seem to have fastboot working, you can use
Code:
fastboot -i 0x1949 oem idme ?
to see if your device is unlocked (see here for a list of commands).
Click to expand...
Click to collapse
C:\>fastboot -i 0x1949 oem idme ?
...
(bootloader) board_id: 0c0400
(bootloader) serial: xxxxxxxxxxxxxxxx
(bootloader) mac_addr: 00BB3Axxxxxx
(bootloader) bt_mac_addr: 00BB3Axxxxxx
(bootloader) productid: 0
(bootloader) productid2: 0
(bootloader) bootmode: 1
(bootloader) postmode: 0
(bootloader) bootcount: 203
(bootloader) panelcal:
(bootloader) time_offset: 0
(bootloader) signature:
(bootloader) idme done
OKAY [ 0.359s]
finished. total time: 0.361s
I feel rusty, haven't done any android dev in two years.. never tried to unlock a bootloader beyond 'fastboot oem unlock' before, but I really don't want them re-locking this one (they've taken root from me twice before.) I verified I have root still, but some apps are reporting that I don't. lame. more tests when I have some time, thanks for your time and effort!
Update:
Successfully flashed twrp recovery image recovery-twrp-recovery-2-8-1-0-apollo-t2991155
Happily considering ROMs to blow-away Amazon's 'os' with
codeshane said:
C:\>fastboot -i 0x1949 oem idme ?
...
(bootloader) board_id: 0c0400
(bootloader) serial: xxxxxxxxxxxxxxxx
(bootloader) mac_addr: 00BB3Axxxxxx
(bootloader) bt_mac_addr: 00BB3Axxxxxx
(bootloader) productid: 0
(bootloader) productid2: 0
(bootloader) bootmode: 1
(bootloader) postmode: 0
(bootloader) bootcount: 203
(bootloader) panelcal:
(bootloader) time_offset: 0
(bootloader) signature:
(bootloader) idme done
OKAY [ 0.359s]
finished. total time: 0.361s
Click to expand...
Click to collapse
codeshane said:
I feel rusty, haven't done any android dev in two years.. never tried to unlock a bootloader beyond 'fastboot oem unlock' before, but I really don't want them re-locking this one (they've taken root from me twice before.) I verified I have root still, but some apps are reporting that I don't. lame. more tests when I have some time, thanks for your time and effort!
Update:
Successfully flashed twrp recovery image recovery-twrp-recovery-2-8-1-0-apollo-t2991155
Happily considering ROMs to blow-away Amazon's 'os' with
Click to expand...
Click to collapse
Thoughts:
- take a backup of your current rom before flashing; leave it on the device until the new rom is stable (simplifies recovery)
- if you get a response from 'fastboot -i 0x1949 oem idme' your bootloader is unlocked!
- once you overwrite FireOS there is no chance of loosing root due to Amazon actions. OTA capability is baked into FireOS - not the device firmware.
- If you like AOSP go with Nexus v4. Any of the other HDX roms (CM11, CM12, SlimLP) are also fine choices. Each has a few minor quirks but no major 'gotchas'.
Sorry for the delay, wrote back a while ago but I guess it didn't post (cellular, pfft.)
Went for the Nexus v4 rom, which is running great so far. Thanks again for such a brilliantly simple unlock utility!
I have a few questions.
1. How can I tell I have a vulnerable bootloader?
I've been on Safestrap 3.7 and one of the early 4.2.2 Android Roms since the December after the HDX's release. My stock slot Fire OS hasn't been updated either. So am I on a vulnerable bootloader? How do I check?
2. Where do I start with this?
Is there anything I need to remove? Do I need to be on the stock Fire OS slot? Or do I simply run it as you stated.
3. After the unlock where do I go from there?
I'm so out of the loop I don't know what's the ideal stable rom to use .
Thanks, I'd appreciate any help .
zXiC said:
I have a few questions.
1. How can I tell I have a vulnerable bootloader?
I've been on Safestrap 3.7 and one of the early 4.2.2 Android Roms since the December after the HDX's release. My stock slot Fire OS hasn't been updated either. So am I on a vulnerable bootloader? How do I check?
2. Where do I start with this?
Is there anything I need to remove? Do I need to be on the stock Fire OS slot? Or do I simply run it as you stated.
3. After the unlock where do I go from there?
I'm so out of the loop I don't know what's the ideal stable rom to use .
Thanks, I'd appreciate any help .
Click to expand...
Click to collapse
Check your FireOS version in the stock slot. If 3.2.6 or below you can unlock the bootloader. The rollback procedure depends on the current version of FireOS. Report back and we'll go from there.
Just a little add-on to @Davey126's info:
3.2.3.2 and lower can unlock, 3.2.4 - 3.2.6 must downgrade first.
Once on 3.2.8 or higher you can NOT downgrade anymore due to rollback protection by Amazon, attempting would brick the device! So if you're on 3.2.6 or lower do NOT update!
Cl4ncy said:
Just a little add-on to @Davey126's info:
3.2.3.2 and lower can unlock, 3.2.4 - 3.2.6 must downgrade first.
Once on 3.2.8 or higher you can NOT downgrade anymore due to rollback protection by Amazon, attempting would brick the device! So if you're on 3.2.6 or lower do NOT update!
Click to expand...
Click to collapse
Just a quick comment: since there are no known adverse affects of a failed unlock,
you could just try unlocking to see if your bootloader is 3.2.3.2 or earlier..
If the unlock fails, you could move on to figuring out if downgrading is an option.
draxie said:
Just a quick comment: since there are no known adverse affects of a failed unlock,
you could just try unlocking to see if your bootloader is 3.2.3.2 or earlier..
If the unlock fails, you could move on to figuring out if downgrading is an option.
Click to expand...
Click to collapse
True!! But for for the 'typical' Kindle user (I know...sterotypes) working with a Windows host the effort to unlock far exceeds that of simply checking the FireOS version if still installed.
Hi, can any help why it keep telling me my kindle device is not connected? i using windowX86 and sure open the adb on kindle. thank you!
More accuracy please! (-;
fuxkamazon said:
Hi, can any help why it keep telling me my kindle device is not connected? i using windowX86 and sure open the adb on kindle. thank you!
Click to expand...
Click to collapse
Hi there,
I'm convinced that I can help you,
but I would need a more accurate
trouble report...
In the meantime, I'll try to give some background
and possible causes and remedies to what I think
might be your problem.
1-Click relies on VirtualBox's USB filter mechanism
to pass through any USB device with Amazon' s
vendorId (0x1949) to the 1-Click VM.
This may not always work.
The most common reasons are as follows:
No device is connected.
I presume this does *not* apply...
The device is in use.
This could happen easily, e.g. if you were browsing files on your Kindle.
Apart from possible privilege issues (see next bullet),
these kind of issues are usually solved by simply disconnecting
and reconnecting your device while the VM is running.
This is the most common/likely case, which 1-Click also tells you about..
Have you tried this? (Your report is not very clear on this.)
Possible lack of privilege.
I've only encountered this on Linux (as described in the first post),
but, then again, on all the Windows boxes I tested on, my user is
in the Administrators group; so, this may still apply there.
BTW, I'm guessing that you are on some 32-bit version of Windows,
although I must admit that the "windowX86" moniker in your post
doesn' t make this crystal clear.
Global USB filter rules in VirtualBox may override the rule used by 1-Click.
This only applies if VirtualBox had already been installed
and configured with global USB filter rules before 1-Click.
There may be other reasons, but the above should cover
the most obvious/common cases.
ty for you quick reply. i dun know what info i can provide but ill try. im now using this bl unlock on safestrap3.75 stock rom without opening or browsing any documents. yet, it show the samething i did last couple times. Here is,
Welcome to 1-Click
mount: proc mounted on /proc.
mount: sys mounted on /sys.
mount: dev mounted on /dev.
* daemon not run[ 1.269523] random: adb urandom read with 6 bits of entropy available
ning. starting it now on port 5037 *
* daemon started successfully *
Please make sure ADB is enabled on your Kindle
and connect the device to your computer
In case you don't already know, ADB is enabled by turning on the
'Settings/Device[ Options]/Developer Options/Enable ADB' option.
If 'Developer Options' is missing in 'Settings/Device[ Options]',
tapping 'Settings/Device[ Options]/Serial Number' seven times
will enable it..
Hit [Enter] to continue
No device appears to be connected..
You may need to disconnect and reconnect your device
Hit [Enter] to continue[ 27.214445] random: nonblocking pool is initialized
so hope you can find whats going wrong. ty!
draxie said:
Hi there,
I'm convinced that I can help you,
but I would need a more accurate
trouble report...
In the meantime, I'll try to give some background
and possible causes and remedies to what I think
might be your problem.
1-Click relies on VirtualBox's USB filter mechanism
to pass through any USB device with Amazon' s
vendorId (0x1949) to the 1-Click VM.
This may not always work.
The most common reasons are as follows:
No device is connected.
I presume this does *not* apply...
The device is in use.
This could happen easily, e.g. if you were browsing files on your Kindle.
Apart from possible privilege issues (see next bullet),
these kind of issues are usually solved by simply disconnecting
and reconnecting your device while the VM is running.
This is the most common/likely case, which 1-Click also tells you about..
Have you tried this? (Your report is not very clear on this.)
Possible lack of privilege.
I've only encountered this on Linux (as described in the first post),
but, then again, on all the Windows boxes I tested on, my user is
in the Administrators group; so, this may still apply there.
BTW, I'm guessing that you are on some 32-bit version of Windows,
although I must admit that the "windowX86" moniker in your post
doesn' t make this crystal clear.
Global USB filter rules in VirtualBox may override the rule used by 1-Click.
This only applies if VirtualBox had already been installed
and configured with global USB filter rules before 1-Click.
There may be other reasons, but the above should cover
the most obvious/common cases.
Click to expand...
Click to collapse
fuxkamazon said:
ty for you quick reply. i dun know what info i can provide but ill try. im now using this bl unlock on safestrap3.75 stock rom without opening or browsing any documents. yet, it show the samething i did last couple times. Here is,
Welcome to 1-Click
mount: proc mounted on /proc.
mount: sys mounted on /sys.
mount: dev mounted on /dev.
* daemon not run[ 1.269523] random: adb urandom read with 6 bits of entropy available
ning. starting it now on port 5037 *
* daemon started successfully *
Please make sure ADB is enabled on your Kindle
and connect the device to your computer
In case you don't already know, ADB is enabled by turning on the
'Settings/Device[ Options]/Developer Options/Enable ADB' option.
If 'Developer Options' is missing in 'Settings/Device[ Options]',
tapping 'Settings/Device[ Options]/Serial Number' seven times
will enable it..
Hit [Enter] to continue
No device appears to be connected..
You may need to disconnect and reconnect your device
Hit [Enter] to continue[ 27.214445] random: nonblocking pool is initialized
so hope you can find whats going wrong. ty!
Click to expand...
Click to collapse
This looks fine. The question is what you did next..
Have you tried disconnecting and reconnecting your Kindle
as the message above suggests?
(BTW, since this was the only direct question in my previous post,
I sort of expected you to answer that, but now you get another chance. )
just tried this. i had rooted my kindle when root first came out without safestrap as i didnt like all the restrictions of safestrap. i installed twrp much later and then cm 11 for twrp without an unlocked BL. tried this one click and had to disconnect and reconnect the tablet at one point, no biggie. at another it sat there with no instructions till i hit enter, but it did complete and said it was successful. so ty very much. at some point soon ill try a rom that requires an unlocked BL and see that my BL is really unlocked. great program if it really did work. will donate soon
I'm using Thor with stock 13.3.2.4 block OTA update and safetrap 3.75. So can i use this tool to unlock BL right away or i've downgraded 13.1.0.0 then unlock?
nickytun said:
I'm using Thor with stock 13.3.2.4 block OTA update and safetrap 3.75. So can i use this tool to unlock BL right away or i've downgraded 13.1.0.0 then unlock?
Click to expand...
Click to collapse
You can NOT unlock versions above 3.2.3.2, so you must downgrade first.
Good News is you can downgrade to 3.1.0 using the downgrade images provided by @ggow. Check page 2 here (page 1 is about 3.2.5/3.2.6 users who can NOT use these images!). Then flash TWRP, update the bootloader to 3.2.3.2, unlock the bootloader, then use ROM of your choice.
Read the info, ask if you've any questions before you brick your HDX! Note that factory reset in Safestrap means the standard wipe only (wipes data, cache & dalvik only)! Do NOT go into advanced wipe, do NOT wipe System!
Be sure to make backups of your current system (even if you don't need it anymore), remove the secondary slot(s) in Safestrap to get back the storage used by it (if you created any), and after installation of TWRP create a backup of your Fire OS before you flash any custom ROM.
I'm following the beginners guide to release my Moto X Pure from it's shackles and am getting this from the command prompt on step 2.
Can anyone provide some assistance?
https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
C:\Android\sdk\platform-tools>fastboot flash recovery twrpclark.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (0 KB)...
OKAY [ 0.004s]
writing 'recovery'...
(bootloader) Invalid boot image
FAILED (remote failure)
finished. total time: 0.019s
C:\Android\sdk\platform-tools>
You need a newer TWRP image most likely, if you are using the one in that tutorial it is OLD!!!
The Moto X Pure/Style is officially supported device. Go to https://dl.twrp.me/clark/ and download
twrp-3.0.2-0-clark.img
Make sure your bootloader is unlocked and enter the following command:
fastboot flash recovery twrp-3.0.2-0-clark.img
Do NOT reboot, then on your device press VOL DN until it says Recovery and press Power, TWRP should start and allow changes to system and perform a backup to the SD card.
And BTW, pretty much everything else in that tutorial after the bootloader unlock is incorrect/outdated. Look in my signature for the proper way to root if that is your objective.
Thanks again. Petition signed.
Is there an up to date sticky/guide on editing build.prop? I believe I need to add the following line so I can use native hot spot.
net.tethering.noprovisioning=true
I've downloaded ES File Explorer but I don't know if something has changed in Android or in the Explorer, but the guide I'm following isn't helping.
lip008 said:
Is there an up to date sticky/guide on editing build.prop? I believe I need to add the following line so I can use native hot spot.
net.tethering.noprovisioning=true
I've downloaded ES File Explorer but I don't know if something has changed in Android or in the Explorer, but the guide I'm following isn't helping.
Click to expand...
Click to collapse
Got me... I've never had a problem tethering on any Moto device.
acejavelin said:
Got me... I've never had a problem tethering on any Moto device.
Click to expand...
Click to collapse
Neither have a lot of people from what I've read. I didn't have this issue on the Z Play but I sold that device. I want the Pure to be my daily driver, but I need to get this hot spot working. All this work for this!
lip008 said:
Neither have a lot of people from what I've read. I didn't have this issue on the Z Play but I sold that device. I want the Pure to be my daily driver, but I need to get this hot spot working. All this work for this!
Click to expand...
Click to collapse
I think you are chasing the wrong problem... The fix you have is for when carrier's block tethering in provisioning, if it worked fine in Z then that isn't the problem.
I assume you tried the normal cache wipe, network reset, and maybe even factory default?
You need to try to use it and when it fails pull a logcat and see why.
acejavelin said:
I think you are chasing the wrong problem... The fix you have is for when carrier's block tethering in provisioning, if it worked fine in Z then that isn't the problem.
I assume you tried the normal cache wipe, network reset, and maybe even factory default?
You need to try to use it and when it fails pull a logcat and see why.
Click to expand...
Click to collapse
IDK. Lots of unlocked devices still honor the carrier's flag in regards to hotspot. The Nexus devices and my gfriend's Pixel does. A new unlocked Axon 7 or the Moto Z Play do not. I've hard reset the device and now that it's been bootloader unlocked, reset again. I haven't wiped any cache or a network reset. Are those done automatically once a factory reset/bootloader unlock is done?
My device says to contact the carrier in regards to getting the hot spot enabled. I haven't tried it again with the bootloader being unlocked, but I will give it a go this morning and see what happens.
lip008 said:
IDK. Lots of unlocked devices still honor the carrier's flag in regards to hotspot. The Nexus devices and my gfriend's Pixel does. A new unlocked Axon 7 or the Moto Z Play do not. I've hard reset the device and now that it's been bootloader unlocked, reset again. I haven't wiped any cache or a network reset. Are those done automatically once a factory reset/bootloader unlock is done?
My device says to contact the carrier in regards to getting the hot spot enabled. I haven't tried it again with the bootloader being unlocked, but I will give it a go this morning and see what happens.
Click to expand...
Click to collapse
Hmm... That sure sounds like carrier provisioning, weird... I technically don't have tethering on H2O but it works fine and I am stock and bootloader locked.
EDIT: Well, I am a bold faced liar... I tried it now on H2O and got the "Account not set up for tethering" messaging, I know it worked on AT&T before I switched last month but I think my account there had it. Now I am curious too...
Maybe best to search in the Moto X area and if you can't find a thread about it (I looked, but only for a minute), start a new one... the title of this thread won't likely get help for this problem.
---------- Post added at 08:52 AM ---------- Previous post was at 08:49 AM ----------
I found this:
Enable Wireless Tethering Rooted Moto X Pure
1. Modifying system files could render your device useless, so by continuing you’re assuming that risk
2. Using a root file explorer, navigate to /system/
3. (Optional) Make a copy of the build.prop
4. Open the build.prop file with a text editor
5. Add the following line to the bottom of build.prop file: net.tethering.noprovisioning=true
6. Save the file and reboot your device
Click to expand...
Click to collapse
Might root again and try it, I haven't had a need for root in a while... Will see, I am lazy so maybe I won't until I need to.
I generally prefer using Solid Explorer in Root Mode and QuickEdit for editing root files... ES File Explorer was once king, but became overbloated garbage the last couple years.
That's what brings me back to editing the build.prop.
I have a ES file Exporer and checked off the root option so I should be able to access everything on the device.
I have never edited the build.prop and need to find the file path for it.
A sticky or something on editing build.prop would be great.
lip008 said:
That's what brings me back to editing the build.prop.
I have a ES file Exporer and checked off the root option so I should be able to access everything on the device.
I have never edited the build.prop and need to find the file path for it.
A sticky or something on editing build.prop would be great.
Click to expand...
Click to collapse
No likely... It is so rare to have to edit it anymore, so few things require it.
Try a different explorer... ES is junk, use Solid or Root Explorer
acejavelin said:
No likely... It is so rare to have to edit it anymore, so few things require it.
Try a different explorer... ES is junk, use Solid or Root Explorer
Click to expand...
Click to collapse
Thanks you...especially for the quick replies. Maybe I will start up a new thread if I can't find an existing one on this hot spot issue.
lip008 said:
Thanks you...especially for the quick replies. Maybe I will start up a new thread if I can't find an existing one on this hot spot issue.
Click to expand...
Click to collapse
Here is the thread... You can bump it if you need to: https://forum.xda-developers.com/mo...nable-wireless-tethering-moto-x-pure-t3227738
acejavelin said:
Here is the thread... You can bump it if you need to: https://forum.xda-developers.com/mo...nable-wireless-tethering-moto-x-pure-t3227738
Click to expand...
Click to collapse
How do I bump a thread?
lip008 said:
How do I bump a thread?
Click to expand...
Click to collapse
Lol... Just post a reply, it will "bump" it to the top of the thread list for that section.
acejavelin said:
Here is the thread... You can bump it if you need to: https://forum.xda-developers.com/mo...nable-wireless-tethering-moto-x-pure-t3227738
Click to expand...
Click to collapse
I was confused by the "you can bump it if you need to" comment. I took it as being something extra in addition to replying. I wasn't able to figure out the root path, but using the search function on ES Explorer I found the build.prop file, made the change, and presto....I know have hotspot working. Next up is to research the popular ROMS. I'm interested in some of the built in features like ad blocking and of course Nougat. Thanks again.