Related
Hey Guys at first sorry for my english i'm not good in it. And I'm a Android newbie I just gained a bit exerience with my Touch Diamond but it's broken now..okay but that's not the probleme....
If got a question:
After about 2 days of searching for an android 2.0 or 2.1 ROM I was a little bit confused of the diffrent news everybody was talking about. I'm root on my Hero. That was the first an last thing I made with my device.
1. Everybody is gonna talk about MoDaCo 3.0 but when I was trying to download his ROM my browser never got a request. Is the site down, where that ROM is hosted ?? Could someone give me a working link with this ROM ??
2. Is there a ROM with Android 2.0 or 2.1 outside or even not ??? And if yes are they working well ???
Would be nice if someone can help me =) thanks a lot.
Please answer soon if you know something about that =)
Greetz BassdoxXx
you can get modaco's roms at his website, www.modaco.com.
in the android development section there are some 2.0/1 roms, none of them works flawless, see for yourself if it fits your needs.
Thanks a lot for your fast answer. =)
The problem that i couldn't open the modaco page was my isp -.- i downloaded it at school
BassdoxXx said:
Thanks a lot for your fast answer. =)
The problem that i couldn't open the modaco page was my isp -.- i downloaded it at school
Click to expand...
Click to collapse
What? Does ISP's block that site? Lol, would never happened in Norway
there is a few 2.0+ roms out there for the hero.
most seem to be very usable now.
best sense ui would be lox/behnaam community release on 1.6.
http://htcpedia.com/forum/showthread.php?t=1448
there are two aosp roms worth looking at.
lox aosp ( im using that on a daily basis)
http://htcpedia.com/forum/showthread.php?t=1416
jnwhiteh aosp
http://htcpedia.com/forum/showthread.php?t=1528
Hello all,
I am having very specific request when it comes to choosing a proper rom for install on to my hero.
I am blind. Stock roms are only running Android 1.5. More robust accessibility features are available starting with Android 1.6 and improving even more with Android 2.0.
So for sure I am forced to upgrade my hand set.
There are various roms, some of their authors have even disable google specific features so I know I can't install such a rom.
All the accessibility efforts are being lead by the google developers.
Most likely these accessibility tools won't be usefull to most of you but please can anyone recommend me a rom where market is working and where the following applications can be installed and used?
- eyesfree suite of applications,
- talkback - the google screen reader for android,
- tts service.
All possible help is already appreciated.
sorry for the double posting. I've accidentally posted twice and I am unable to remove the post.
Hope anybody can help me please.
pvdeejay said:
Hello all,
I am having very specific request when it comes to choosing a proper rom for install on to my hero.
I am blind. Stock roms are only running Android 1.5. More robust accessibility features are available starting with Android 1.6 and improving even more with Android 2.0.
So for sure I am forced to upgrade my hand set.
There are various roms, some of their authors have even disable google specific features so I know I can't install such a rom.
All the accessibility efforts are being lead by the google developers.
Most likely these accessibility tools won't be usefull to most of you but please can anyone recommend me a rom where market is working and where the following applications can be installed and used?
- eyesfree suite of applications,
- talkback - the google screen reader for android,
- tts service.
All possible help is already appreciated.
Click to expand...
Click to collapse
i am on mcr3.0, i looked in the market, i can find 8 apps for eyesfree, tts is one of these. i didn't try to install one of these, but usually it works. the search for talkback returned nothing.
not that i want to be rude, but wouldn't you be better off with another phone if you are blind? i can not imagine a touchscreen only phone would be suitable for someone who is not able to see... especially because there are great devices out there that have a full qwerty keyboard, and come with android 2.0 out of the box... imho this would be a better solution.
again, the last thing i want to be is rude, but maybe this was your mistake: you posted in the htc hero section of this forum, the hero is a touch screen only device, including a virtual keyboard on the screen. it has only six buttons and a trackball, and two rocker buttons for the volume. just to make clear we are talking about the same device
if you are still up for the hero you could try the 2.1 rom from here: http://htcpedia.com/forum/showthread.php?p=30418&posted=1#post30418
best you try for yourself, it has some drawbacks, but maybe in areas you don't need (afaik syncing with exchange does not work for example, which wouldn't be a problem for me...). otherwise it might be worth to wait another week or two, we all are waiting unpatiently for the official eclair release from htc
keep asking if you need to know more, but maybe open a new thread, since your problems are very specific, and might drown between all the newbies question about "how to root my phone".
Hello,
Thanks for your reply and a great attitude.
Yes it may sound strange I have really got HTC Hero here. I know I'll be having problems with virtual keyboard but also I am afraid accessibility features of Android phones are not really such mastered one can use it daily. For example reading emails and content from the web browser is not yet possible. I just want to try how things work and I would also like to touch the virtual keyboard. If I can memorize computer keyboard and use it daily, typewriter keyboard, nokia mobile phone keyboard, then perhaps I might be able to make some use of this too.
I am sory but here are some more questions:
I haven't yet verified with some sighted friends but... is it possible my hero is running even older version of android like Android 1.5? I've based the assumption that it's most likelly running 1.5 because majority of the devices I was reading on the net are running it.
You've been triyng to locate eyes-free applications on the market but you were unable to find talkback. Are you sure you are running newer version of Android than 1.5?
Talkback is supposed to be installed with Android 1.6 andd 2.0 by default and you should be able to find it in the accessibility menu of your phone. I am not sure how well this applies to the custom roms.
Talkback requires google's accessibility api which is reported to be available on Android 1.6 upwards.
To tell you the full story first I've asked on the eyes-free google group whether some accessibility experts from there can help me but no one knowledgeable enough has replied to my query, so I'm trying my luck here then.
Oh I am really excited since I've got really well formed informative reply.
Thanks again
Edit:
Also, I've seen somewhere in the forums here this leaked HTC rom does not support the market. Has this been rectified already? You know if market does not work then most likelly I won't be able to install these applications I am tallking about.
Also you are mentioning possibility to wait a few weeks until HTC guys role out the official update for Hero. Wouldn't that break chances I will be able to root my device later?
Edit2:
Ooops, I should read better next time. Market works on this rom. The problem is paid apps can't be installed which is hopefully not a big issue for me since most of the accessibility enabled applications are free.
Which of the downloads from Hero 21 do I need?
63.18.55.06JU_6.35.09.26) or No Wipe Download. I will need a wipe I am sure but since this link says nowipe I am ehmmm. confused.
pvdeejay,
Unfortunately there is not an 'official' update for Android 1.6, 2.0 or 2.1 as of yet. There are rumours of one coming out soon, but nothing cast-iron yet.
You are correct in that the Hero runs 1.5. It does say it under Settings | About Phone (bottom item on list)| Firmware Version (bottom on list again), although without a working screen reader, there is probably little use in knowing how to find that.
If you did want to upgrade, I'm sure plenty of people could help find a ROM that would suit. The only issue with that is that you would need a rooted phone with a custom recovery image installed. Unfortunately, a lot of the procedures would not be easy for you, as the software that you might need to use to go through the procedure is probably not designed that well for accessibility tools. I don't know what kind of software you are using, but some of the instructions for making goldcards are quite complex, and involve editing some numbers in a 'table' which could be quite difficult for you, I would imagine.
I'm sure a friend would be able to help you out with making a goldcard/rooting if you did want to install a custom ROM (you'll probably be waiting a while otherwise ). They could even root their phone while doing yours (just share the goldcard between the devices).
Nonetheless, there is probably a ROM out there with little removed from it. I'll have a look just now, but you would need to have your phone rooted to do anything just now.
When it comes to rooting and installing custom recovery image. Do you thing the following instructions might work for me?
These instructions don't require a gold card:
- How to Root HTC Hero and Install Amon Ra Recovery Image
- How to install a custom rom on a HTC Hero
Hello,
Here are some numbers I've asked my friend to read from system -> about screen. The phone interface is in czech so I am unable to get some names translated to english, but I believe some of the geeks will understand these identifiers and might be able to help me what is best:
Code:
firmware: 1,5
63.118.55.O6U|6.35.04.25
2.6.27-a5504199
Build number: 1.76.405.6 146733 CL# 47214 release-keys
Software version: 1.0.0.A6288
pvdeejay,
to sum it up:
the hero definitly runs on android 1.5. there are no roms for older android versions, and a few homebrewn for newer versions, as we said already.
i searched for talkbalk on my 1.5 rom, so it is obvious that i couldn't find it...
about rooting of newer roms: it is just a matter of time, sooner or later there will be always methods of rooting a rom. what i meant by waiting is: wait until the official update is out, then wait a few more hours until the first rooted and customized rom is out
@pvdeejay,
I would have to agree with kendong2 that waiting for the official ROM is probably the best idea for you at the moment. There are no guarantees that an unofficial ROM would help, and it would be another user interface to try and learn.
@kendon,
I noticed he has the original, easily rooted version of the hero. IIRC, that is what I had on my G2 (and had the security unlocked bootloader out the box). If that's the case, would pvdeejay be able to 'fastboot boot' a full system img file for the purposes of testing it out to see if it meets the requirements.
The reason I ask is that I've only ever fastbooted my AmonRA recovery (I didn't flash it, because I never felt any need to). I'm guessing you could fastboot a full img, but I'm not sure about the practical issues of where it would be stored in memory...
Sorry guys originally I believed I am slowly getting into the matter and am begining to understand how flashing / rooting / upgrading home brew firmwares works on these phones.
After these 2 posts I feel like a total noob again.
Now again some very concrete questions:
What about these 2 guides I've posted links to?
Can I somehow got [Recovery] [13-Dec-2009] RA-hero-v1.5.2 installed so I will be able to do nandroid backup and then possibly flash some new roms?
Can I really brick my phone by trying to install amon ra?
Originally I thought the process works as follows:
1) get the custom recovery image installed (that's the amon ra in this case),
2) do a nandroid backup which will dump everything usefull on to the memory card,
3) backup and reformat the card,
4) download a rom, rename it to update.zip, put it onto the root folder of the cart, reboot the hero in recovery mode, do the wipe of the data partition, and run update,
5) reboot again and believe it's good.
Also some very significant bit is the thing you are all calling the radio. I am afraid I've not identified this bit thus it's missing in this summary.
Which files will I need to download if I decide to try Android 2.1 community edition 1.8? Are these files I've copied links to a few posts earlier both needed?
Can you please check this list, identify the things I am missing, and make suggestions and corrections why this may not work on my device based off of those number I tried to put down here?
Even if I won't be able to do this right now I'd be happy to get corrections as I can learn something new.
Of course I won't be doing all this on my own. I will ask my bro to read all the stuff to me and we'll do it according to your advices.
To give some bits about me and my computer skills, I believe I am a Windows power user, Basically I do also understand unix, I know what's bash how the files are arranged in a file system, can use command-line tools, telnet, ssh. I am working as a network administrator here so some background is there really.
Hi pvdeejay,
Answers to your questions here.
You can actually use fastboot to 'temporarily' load up the AmonRA recovery image into memory and run it from there. I do that on my phone, for the simple reason that I can't be bothered ) ) to flash the recovery. Once you get AmonRA running, the first thing you should do is make a Nandroid backup. It will be saved to your SD card, so then get the nandroid directory of your card and save it to your PC (just in case!)
So, here's how you'd go about this.
(Make sure you have the android sdk installed, and that adb and fastboot commands are working). USB cable should be plugged in throughout.
Before you begin, put the ROM you want (ie. Android 2.1 community edition 1.8) into the root of the microSD card (a .zip file).
Code:
adb devices
Should list your phone's serial number
Now turn off the phone, and turn it on with the back key held down (the one at the very bottom right of the device).
You should enter fastboot mode. Now type
Code:
fastboot devices
and you should see the serial number again.
Now type
Code:
fastboot boot AmonRA.img
where AmonRA.img is a file in your present working directory that is the filename of the latest custom recovery image. This does NOT flash your phone, it merely runs the image (pretty much as close as you get to risk free, other than sitting there with a tinfoil hat on )
See screenshot of the recovery image here:
http://www.sizzledcore.com/wp-content/uploads/2009/12/RA-hero-recovery-image-500x375.jpg
Make the Nandroid backup by choosing 'Nandroid Vx.x Backup' and waiting a while.
If your ROM needs a wipe first (most new ones do), select Wipe data/factory reset. You will lose all your user data on the device (but you've got a nandroid backup just in case)
You're now good to go. So choose "Apply sdcard:choose zip"
Now select the custom ROM zip file you downloaded. It doesn't even need to be called update.zip! Choose it from the list and push trackball.
Wait for the update.zip to go in. Do NOT turn off the device or pull the battery. First boot can take a very long time (upto 30 minutes). Just keep it plugged in via USB and wait...
As for radios, see http://android.modaco.com/content/h...-24-11-hero-roms-radios-in-update-zip-format/ and look at the section titled radios. The latest one is in bold. It is a .zip file as well, that you use these exact same instructions for to install (don't do the wipe or anything like that. Just install the .zip file)
anon2122 said:
@kendon,
I noticed he has the original, easily rooted version of the hero. IIRC, that is what I had on my G2 (and had the security unlocked bootloader out the box). If that's the case, would pvdeejay be able to 'fastboot boot' a full system img file for the purposes of testing it out to see if it meets the requirements.
The reason I ask is that I've only ever fastbooted my AmonRA recovery (I didn't flash it, because I never felt any need to). I'm guessing you could fastboot a full img, but I'm not sure about the practical issues of where it would be stored in memory...
Click to expand...
Click to collapse
this is correct so far, i did the same, except i installed the recovery. i play a lot with my phone, the installed recovery image with the nandroid backup is the best i have ever seen for a phone...
@pvdeejay
you always write so much...
i try to answer everything:
the two guides you posted are good for your situation. i never tried flashrec, but from what i read it is safe to use. i installed my recovery image through fastboot, the guide is here: http://android.modaco.com/content/h...ng-the-patched-recovery-image-on-your-device/
i have no idea how this works out for you, but my honest suggestion would be that you have someone seeing assisting you, you CAN brick your phone, though it is not likely if you follow the instructions precisely. the process is not very time consuming at all, so you don't need to bother anyone for days of their time.
edit: and now i read your post to the end and saw that your brother will be helping you, so you are on the right track
once you have the recovery installed you can make nandroid backups, and i would suggest that you do this first thing after installing the recovery, better make a backup too much than one too less...
the 5 steps you described are correct, except there is no need to rename the zipfile anymore, you can select any .zip from your sdcard.
the radio part is the number that begins with 63.18.55.06, then comes two letters and then more numbers. as by now the version can be identified by the letters, with JU being the up-to-date one. in general you can say the newer the better, but you have to try for yourself. start with the newest one, if you have problems go back.
thanks this seems to be pretty doable plus I will easily be able to restore the current data backed using nandroid backup.
Which android SDK do I need the latest one?
The commands I need to type are supposed to be typed on the PC or on the phone? I assume on the PC but I just would like to ensure.
Hero21 1.8 community edition has a recommended radio listed in the first post. Is it necessary to install that one as well? What should I install first the actual rom or the radio? Do I need installing radio at all? Should i do the same with radio i.e. renaming it to update.zip and using amonra to install it?
Also will I be able to use this method even if I install another rom (running amonra without actually flashing it)?
Edit:
sorry guys did not realize renaming to update.zip is no longer needed.
Edit2:
is there an easy way on how to access sd card from windows? I can't just remove the card from phone and insert it into my laptop because I don't have the proper adapter. Previously my boss was using the hero and perhaps it would be nice to backup the sd card first.
Edit3:
uhmmm, installing android sdk is perhaps not as simple as it sounds.
I have just seen this article.
I am on a limited gprs internet connection, can you please suggest sdk features I won't need to save some download bandwith?
- you need only the adb binary (thats adb.exe for windows) from the sdk, the rest is not needed for this.
- install the radio from the 2.1community-rom-thread, it is the newest. install the radio first. DO NOT PULL THE BATTERY until the phone has rebooted completely. if you pull the battery during radio upgrade your phone will be dead. it takes a few minutes, do not panic!
- you can copy the contents of the sdcard via the usb-cable, plug it into your pc and pull down the notification bar...
Do I need to run SDK Setup.exe when I have downloaded android sdk for windows?
Or can I simply run that binary from the command-line without the installation?
Do I need any USB drivers so my phone can be recognized?
Hi,
i just joined, hope i'm posting in the right forum
i'm about to get my first android phone (aria).
there's a few things that i'd like to do, because i like to tinker with tech toys, and that's the reason for picking up an android phone.
can someone point me to some simple steps that explain what software/applications i will need to achieve the following:
- make a backup image of the ROM it ships with.
- modify / explore the contents and modify that image
- flash the modified image back to the device.
i know that i could use the guides that exist and flash a pre-made image to the device, but i like to do the tinkering myself.
if it matters, i'm running linux on my computers, i can use win7 in a pinch if needed, i've vor an instance running in vmware)
any tips, hints, pointers appreciated.
J.
I have a Nook Simple Touch Glowlight with software verion 1.1.5. All the information that I've been able to Google is for 1.1.2, in fact that is the version that I still see on the B&N website.
I _think_ that I have found a suitable way to root the device with Nooter but I would like to know how to confirm that in fact this is the right project for my software version. I'm sorry that I cannot post a link to the Nooter project, but I have less than 10 posts.
Thanks.
There are at least two methods that work with the Glowworm.
You should not use any method until after you have
- made a noogie disk
- booted from it
- backed up your device
- restored that backup to a test disk (a 2 gig or larger microSD card, for instance) and confirmed that the test results in a disk that has 8 partitions.
Many people have made the backup but not tested it; when they tried to restore, they did bad to fatal things to their devices. A very common failure on restore seems to be only getting one partition restored and blowing out the other partitions.
I don't know if the stuff that eded is working on has come to fruition yet - he was looking at building a tool that could detect whether it was run on an NST or NSTG and root appropriately to the device.
The two routes I know work are:
- glownooter, the nooter project tool, includes Google apps and market support
- tinynoot, pasted together from various tools, gives you minimal root without google apps and with amazon appstore. Will work with either NST or NSTG because it's approach is so minimalist.
Thanks, roustabout! I will be sure to test the backups before I install anything else, then. Good to know!
In any case, what I am most concerned about is getting the right version of the rooting software for my device. I see that Nook devices have different firmware and that certain tools only work with certain firmware versions. I see no mention of my firmware version in any tools' websites, hence my apprehension.
hence the value of a backup
I saw your request on that and I think one of the issues here is that so many folks use Windows exclusively, and the backup process is so easy on linux that trying to tell people how to do it in Windows is like jabbing yourself in the eye with a stick, given that linux is free, vmware player is free, and linux can be installed and used for this job entirely in vmware player. On the other side of the coin, if you know nothing of linux, even using dd correctly will be a challenge since there's a pretty steep learning curve behind setting up a new OS successfully just to be able to get backups off an 80-130 dollar device.
In your case: as of now, there is only one firmware release for the glowlight. This is why the folks with the tools aren't mentioning it, aside from 'this is for a glowlight.'
I didn't mention it, but I also use Linux at home (Kubuntu, like Ubuntu but with a better UI). So many people are now using Ubuntu that I find it surprising that the instructions even bother mentioning the OSes for which the operation is as difficult as you say. I remember when doing things in Linux was hard and Windows was easy, and at that time Linux was hardly ever mentioned!
In your case: as of now, there is only one firmware release for the glowlight. This is why the folks with the tools aren't mentioning it, aside from 'this is for a glowlight.'
Click to expand...
Click to collapse
I did not realize that the 1.1.5 release is glowlight-only. Great, thanks, I'm on to hacking this thing!
ok, so for you the backup process is:
- make the noogie disk
- put it into your device
- power cycle your device
- when it boots to "rooted forever," connect the USB cable to your linux box
- once the linux box mounts the NSTG as storage, pay attention to which device it is mounting it at. Assuming it's sdX:
- backup with dd if=/dev/sdX of=backup.img bs=1M
When that's done, disconnect your NSTG, throw media of some sort, larger than 2G, onto your box and test your restore with
dd if=backup.img of=/dev/sdY bs=1M
Once that's done, do an
fdisk /dev/sdY
and a
p to print the partition table.
You should have 8 partitions (and your backup.img file should be just under 2 gig.)
Hack away; if you ever need to restore, you can just drop the virgin image back on.
I take a snapshot like this of my device every so often since remembering how I got to whatever config I liked is harder than just backing it up.
Thanks for the backup instructions, the idea of testing it on a DVD-ROM looks to save quite a bit of trouble with the actual device..
I rooted with this terrific guide:
http://forum.xda-developers.com/showthread.php?t=1675706
The process was simple. I do have an issue where I need to install a Hebrew font but ES File Manager doesn't seem to see the root folders. I'm having a hard time googling my way out of this one, bu all the other little issues were fairly simple.
One issue that I will mention that was hard to solve was the inability to perform searches in the Market. This page helped me resolve that issue:
blog.the-ebook-reader . com/2011/07/15/rooted-nook-touch-fixing-market-search-and-other-tips-and-tricks-video/
I just figured out that the file manager has to have Root permissions enabled. I've enabled it and added some fonts to /system/fonts but I still cannot get Hebrew text to display on this device. All I get are the typical rectangles instead of characters. Any ideas about how to proceed?
Thanks.
Restore Nook 1.1.2
roustabout said:
Many people have made the backup but not tested it; when they tried to restore, they did bad to fatal things to their devices. A very common failure on restore .
Click to expand...
Click to collapse
1. I made this exact same mistake yesterday and I ended up with a bad backup.
2. My Nook Simple Touch (1.1.2) is now not working because I wiped ALL the partitions before attempted to restore the backup (which I didnt know was bad at the time)
3. Please help me restore the Nook back to factory or any working state. Are there any restorable backup images that can be downloaded online?
p.s. I have tried touchnooter and installed touchformatv2 but all I get now is a Read Forever load screen.
Please Please Help Me Im so sad (I know this is down to carelessness on my part but I really need help)
bubblewrapper said:
1. I made this exact same mistake yesterday and I ended up with a bad backup.
2. My Nook Simple Touch (1.1.2) is now not working because I wiped ALL the partitions before attempted to restore the backup (which I didnt know was bad at the time)
3. Please help me restore the Nook back to factory or any working state. Are there any restorable backup images that can be downloaded online?
p.s. I have tried touchnooter and installed touchformatv2 but all I get now is a Read Forever load screen.
Please Please Help Me Im so sad (I know this is down to carelessness on my part but I really need help)
Click to expand...
Click to collapse
Few people who will be knowledgeable will find your post buried here under this thread. i suggest that you simply start a new thread with a good descriptive title so that the gurus will find it.
Not sure how to get hebrew working. One assumes that in addition to the characters, you need it to right to left? If it's the latter, I know there was a thread discussing doing this with Arabic, and I'm not sure how that turned out. You can also google around for folks looking at this on, I think, mobilereads.
roustabout said:
Not sure how to get hebrew working. One assumes that in addition to the characters, you need it to right to left? If it's the latter, I know there was a thread discussing doing this with Arabic, and I'm not sure how that turned out. You can also google around for folks looking at this on, I think, mobilereads.
Click to expand...
Click to collapse
Actually, I think that I just need the fonts (or at least that would be a great first step). I put fonts with Hebrew glyphs in /system/fonts (using ES File Explorer in Root mode) but even after a restart it does not find the fonts (i.e. Hebrew text still shows as rectangles). I will fight with it some more in the coming days, if I don't succeed I will start a new, concise thread on the topic. There are plenty of Google posts on the subject, but all of the ones that I have seen (not Nook-specific) suggest that dropping the fonts is /system/fonts should be enough. Perhaps it is a permissions issue, I'll see if I can SSH into the device to see permissions.
dotancohen said:
I have a Nook Simple Touch Glowlight with software verion 1.1.5. All the information that I've been able to Google is for 1.1.2, in fact that is the version that I still see on the B&N website.
I _think_ that I have found a suitable way to root the device with Nooter but I would like to know how to confirm that in fact this is the right project for my software version. I'm sorry that I cannot post a link to the Nooter project, but I have less than 10 posts.
Thanks.
Click to expand...
Click to collapse
Sorry that I am so slow to respond, but I think this is the information you need to root a Nook with Glow on version 1.1.5
It uses Glownooter
http://blog.the-ebook-reader.com/20...using-glownooter-includes-googles-app-market/
and this is the backup routine
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
ladykayaker said:
Sorry that I am so slow to respond,
Click to expand...
Click to collapse
Thank you! You don't need to apologize for taking time to respond, you are under no obligation! But I very much do appreciate your assistance and am happy to wait patiently! You will notice that I usually google issues first to try to save us both the time!
I think this is the information you need to root a Nook with Glow on version 1.1.5
It uses Glownooter
http://blog.the-ebook-reader.com/20...using-glownooter-includes-googles-app-market/
and this is the backup routine
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
Click to expand...
Click to collapse
Thank you. It seems that those posts are Windows-centric summerizations of information found here at XDA-developers. The root is pretty much the process that I used, but from the guide right here which has Linux directions as well.
By the way, the-ebook-reader site is often not responding for me. Is it just for me, or does everyone have trouble with that site?
Thanks!
version 1.2.0
UK glowlight ships with 1.2.0. Use tinynooter to root this. You may have issues installing apps atm though but you will get the browser at least.
http://forum.xda-developers.com/showthread.php?t=1961835
Thanks, Loney. In fact, I got this Glowlight in the US, and it reports that it has software verion 1.1.5. But the information will be good for others who might google this thread!
Hello all! you're awesome!
I have this pc/tablet. I try to put a spanish language, and was impossible.
I decided to put a clean install of windows 10, and I crash it...
Now, all is in spanish, but there are some things that not work now: wifi, audio, touchscreen...
I know that it's a drivers problem. But there are not drivers for this product.
I hope that some of you can share with us (and me) an image of the original windows10 that come with the tablet, and maybe I can install.
Now...I lose 350$ in a few hours...
I want them too
i think the original Windows 10 installation image from Voyo with the drivers is here
Code:
https://9896df.lt.yunpan.cn/lk/cxxWj6pRmPTRi#/-0
but i cant make a account there to download it .....
can anyone help to upload it somewhere else?
This is for Voyo v3 mini PC as I can see not for Voyo V3 Vbook
Hi
you can find all folders & files from this China site also hire even Image of restoration
https://yadi.sk/d/9ixK06sZovfdq
stbn7777 said:
Hello all! you're awesome!
I have this pc/tablet. I try to put a spanish language, and was impossible.
I decided to put a clean install of windows 10, and I crash it...
Now, all is in spanish, but there are some things that not work now: wifi, audio, touchscreen...
I know that it's a drivers problem. But there are not drivers for this product.
I hope that some of you can share with us (and me) an image of the original windows10 that come with the tablet, and maybe I can install.
Now...I lose 350$ in a few hours...
Click to expand...
Click to collapse
do you manage to repair Windows dude
hire is all files from Voyo vbook V3 drivers,you can also with google translate use 4pda forum find many answers
I managed to get the drivers from their website after a lot of struggle. I uploaded them to mega just in case others need them:
http s://me ga.nz/#!hVB0Ea6Y (apparently I need a min number of posts to put links)
The decryption key is the following: !9fQTHbIb-H812jw2MwVOAPZoZvDGKuywgiRBkjkOwEE
The wifi driver is giving some security warning when you try to install it. I already had it working yesterday (using other drivers I found) so I decided to not install it when I saw the warning. The rest of them made my camera and touchscreen work properly though so they are good.
jeefo12 said:
I managed to get the drivers from their website after a lot of struggle. I uploaded them to mega just in case others need them:
http s://me ga.nz/#!hVB0Ea6Y (apparently I need a min number of posts to put links)
The wifi driver is giving some security warning when you try to install it. I already had it working yesterday (using other drivers I found) so I decided to not install it when I saw the warning. The rest of them made my camera and touchscreen work properly though so they are good.
Click to expand...
Click to collapse
I ordered ssd disk 128gb ,today arrive in Macedonia tomorrow i will installit on board to see will it work or not as expanded memory.
as i can see till now on my Voyo v3 ,i have oni one sticky button ,windows work geat..
with wifi(driver) i haven`t problems only yet but on 4pda.frorum(rusia) with google translate as a option in Chrom you can get best Voyo Vbook V3 community and best info for Voyo on the net..
jeefo12 said:
I managed to get the drivers from their website after a lot of struggle. I uploaded them to mega just in case others need them:
http s://me ga.nz/#!hVB0Ea6Y (apparently I need a min number of posts to put links)
The wifi driver is giving some security warning when you try to install it. I already had it working yesterday (using other drivers I found) so I decided to not install it when I saw the warning. The rest of them made my camera and touchscreen work properly though so they are good.
Click to expand...
Click to collapse
hey, what's the decryption key for your files man?
aussiepr said:
hey, what's the decryption key for your files man?
Click to expand...
Click to collapse
Sorry, I had no idea mega is encrypting it automatically. This is the key !9fQTHbIb-H812jw2MwVOAPZoZvDGKuywgiRBkjkOwEE (exclamation mark included)
jeefo12 said:
Sorry, I had no idea mega is encrypting it automatically. This is the key !9fQTHbIb-H812jw2MwVOAPZoZvDGKuywgiRBkjkOwEE (exclamation mark included)
Click to expand...
Click to collapse
Thanks, worked fine
Hi, I've recently bought the core m3 version off Gearbest, but ran into a ton of issues out of the box. As with all chinese tablets/laptops/convertibles I buy, the first thing I did was do a Windows reset (to get rid of any potential bloatware/localization issues/ etc/). However, since the reset, I have been unable to charge the device beyond 80%, the pen that came with it is not registering any input, and the touch screen input is waaaaay off (closer to my finger at the top left corner, then deviates further off the further I get from that point).
Now, I'm unsure whether these issues existed prior to the reset, or whether they were caused by it (since I didn't really use the device long enough before the reset). The easiest way would probably be to send it back to claim warranty, but the whole claim procedure through Gearbest is a nightmare at best. I would prefer to try everything possible before actually attempting that ordeal.
I would like to try installing a fresh copy of windows over the "reset" version to see if the potential driver issues are resolved, but am unable to find the proper installer for this device from the myvoyo website. The one available is apparently for the atom x5-Z8300 version of the device, not for the core M version. I did try the drivers from the link above in this thread, but it caused a WDF_VIOLATION bsod.
tl:dr Does anyone have ANY suggestions as to what I can try to fix these issues, or potentially have a link pointing to the correct drivers/windows installer I will need to get the device back to the factory settings? (I speak neither Chinese nor Russian so the company's website and the apparently thorough 4pda forum was of limited use to me - google translate is wonky at best)
Thanks and sorry for the long rant.
WooHoo!! Thanks that fixed my touch and wifi issues!
Do not hesitate to contact them directly via e-mail (the voyo manufacturer). I just did and they seem very helpful (or I am just lucky). I am currently trying to install Android on the machine with their help. If I get all the drivers to work I will post here everything needed + instructions in case anyone wants to do it as well.
---------- Post added at 09:02 AM ---------- Previous post was at 08:57 AM ----------
riyasatazim said:
Hi, I've recently bought the core m3 version off Gearbest, but ran into a ton of issues out of the box. As with all chinese tablets/laptops/convertibles I buy, the first thing I did was do a Windows reset (to get rid of any potential bloatware/localization issues/ etc/). However, since the reset, I have been unable to charge the device beyond 80%, the pen that came with it is not registering any input, and the touch screen input is waaaaay off (closer to my finger at the top left corner, then deviates further off the further I get from that point).
Now, I'm unsure whether these issues existed prior to the reset, or whether they were caused by it (since I didn't really use the device long enough before the reset). The easiest way would probably be to send it back to claim warranty, but the whole claim procedure through Gearbest is a nightmare at best. I would prefer to try everything possible before actually attempting that ordeal.
I would like to try installing a fresh copy of windows over the "reset" version to see if the potential driver issues are resolved, but am unable to find the proper installer for this device from the myvoyo website. The one available is apparently for the atom x5-Z8300 version of the device, not for the core M version. I did try the drivers from the link above in this thread, but it caused a WDF_VIOLATION bsod.
tl:dr Does anyone have ANY suggestions as to what I can try to fix these issues, or potentially have a link pointing to the correct drivers/windows installer I will need to get the device back to the factory settings? (I speak neither Chinese nor Russian so the company's website and the apparently thorough 4pda forum was of limited use to me - google translate is wonky at best)
Thanks and sorry for the long rant.
Click to expand...
Click to collapse
[email protected] . Contact them directly. I just did and they sent me the drivers for the cherrytrail version (though that's not exactly what I asked for). Keep your english simple and concise so they understand you. Theirs is quite bad.
Hi guys
The drivers doesn't work anymore.. someone has them?
i recently bought the voyo v3 ultrabook from gearbest and it constantly just shuts off without warning. this kills windows after a while so have reset it multiple times.
tried to return it to gearbest but the cost was like £60 and then the post office wouldnt touch it because it contained a lithium battery.
basically gave up and accepted £15 compensation from gearbest - would like to try android on this as i have some suspicion that the device could be ok. it can go for hours when windows is not fully booted ie when restoring windows so this could well be on OS thing. trying android would be a good test of this.
big waste of money and time really, note to self is only buy from local stores in the future! doh.
Voyo stays in blackscreen
Hi together,
I need your help. I have the v3 flagship with m3-6y30 and it stays in blackscreen.
I changed the win10 boot options to safe mode and now the screen stays black only. The 'caps lock' led is working. I tried to enter bios or uefi, but it does not work, or at least the screen stays black.
Next I will try to connect micro hdmi to a monitor and I hope that it will work. Another solution would be to write a new originial voyo win10 image to the m2 ssd. Could anyone provide me his ssd image? Maybe someone saved it after resetting win10? I asked voyo for that image, but they did not answer..
It would be great if someone could help me.
Regards
dschingi86 said:
Hi together,
I need your help. I have the v3 flagship with m3-6y30 and it stays in blackscreen.
I changed the win10 boot options to safe mode and now the screen stays black only. The 'caps lock' led is working. I tried to enter bios or uefi, but it does not work, or at least the screen stays black.
Next I will try to connect micro hdmi to a monitor and I hope that it will work. Another solution would be to write a new originial voyo win10 image to the m2 ssd. Could anyone provide me his ssd image? Maybe someone saved it after resetting win10? I asked voyo for that image, but they did not answer..
It would be great if someone could help me.
Regards
Click to expand...
Click to collapse
Could solve it. I can enter Uefi by pressing Esc and I had to use an external monitor.
hi dschingi86
i have a similar problem - I did a clean re-install of windows 10 pro and the screen stopped working. The backlight is definitely working - i can see it come on, but nothing is displayed on the screen. the screen still works for touch though.
It only displays when connected to an external monitor via hdmi.
i've tried reinstalling drivers etc, but nothing works - how do i get the screen to start working again?
How do you enter BIOS?
please help
hensk said:
I ordered ssd disk 128gb ,today arrive in Macedonia tomorrow i will installit on board to see will it work or not as expanded memory.
as i can see till now on my Voyo v3 ,i have oni one sticky button ,windows work geat..
with wifi(driver) i haven`t problems only yet but on 4pda.frorum(rusia) with google translate as a option in Chrom you can get best Voyo Vbook V3 community and best info for Voyo on the net..
Click to expand...
Click to collapse
What type of m.2 ssd drive does the Voyo v3 Pro use sata iii or pcie? What is the maximum size in gigabytes that the Voyo V3 Pro can use? Do you happen to have a image file of Windows 10 for the Voyo v3 Pro? The link to the image file on the Voyo web site no longer works.
Hello!
Normally when I come on the XDA forums, I am asking a question, because I end up making a silly mistake in Android. I never like to put out promotional content for attention, and that is surely what I am not doing here, I am simply putting my work out there to see if the community would like it and if we do like, we can begin setting it up for other devices immediately. Now, I am not a skilled programmer at all, but I know SOME Visual Basic with Windows Forum Applications, so I thought "why not give it a shot." I just wanted to say that.
So I made this simple little application called Lineage OS Installer. Now, reading through some of the comments on the Lineage OS Reddit page, some people were asking if there would be an installer for Lineage OS, and there was a good amount of people who did not want one, which makes sense; people should know what they are getting into, and understanding ADB and Fastboot is indeed important. However, sometimes, there is a person who is not involved with ROMS, who is fine with OEM Android, who does not want to use root and what not, however, they want the latest version of android possible for their device, and that was a main point of CyanogenMod; users could get the latest version of android on their phone and tablet when their manufacturer/carrier stopped supporting it. However, the installation can be intimidating, and for the user that I just described earlier, the user who does not want root and what not, that could mean they won't bother attempting to install a custom ROM. However, this application automates the process; all the user needs to do is click some buttons, and press Enter a few times to install LineageOS.
I understand I don't need "permission" to distribute this program, however, I am just asking if the overall community would support the use of this program.
NOTICE: The applicaton may fail to start properly. I am investigating this issue. In the meantime, ensure you have the latest .NET Framerwork([url]https://www.microsoft.com/en-us/download/details.aspx?id=55170&desc=dotnet47[/URL]). If that doesn't work, try building from the source ([url]https://github.com/PJBeans/LineageOS-Installer/wiki/How-to-build-from-the-source[/URL])
This is a simple graphical and command-line based installer designed to make it easier to install LineageOS; this program is aimed at beginners. It is not the prettiest program ever, but it still works with my Nexus 7 2013 WiFi just fine
Possible support for flashing root may become available in the future.
If you notice a bug (an issue with the application), please submit it here: https://github.com/PJBeans/Lineage-OS-Installer/issues
Features:
[ADB and Fastboot is required, but NOT included.]
- Instructions for enabling Developer Options, USB Debugging, and OEM Unlocking (if required)
- Embedded browsers to download TWRP, GApps, and LineageOS
- Automatically creates a backup with TWRP.
- Flashes TWRP, LineageOS, and GApps with minimal user interaction; no TWRP interaction required! (The most they really do is confirm they want to unlock the bootloader)
If you have a secondary device that supports LineageOS, perhaps you could try out this program and report your results [in a reply to this thread]! In order to make this as stable as possible, it would require lots of testing, and I do not plan on buying each and every Android phone anytime soon. If you want to test this program, use the prebuilt version, as the Source version may contain undocumented bugs blocking one from their goal. Note that:
- It may screw up your device. No automatic restore process is implemented yet, so make sure to have some sort of recovery tool handy.
- When you report back, please include the version of the program you used (as identified in the Downloads section), along with your device.
- CURRENTLY ONLY FOR NEXUS (AND PROBABLY ONEPLUS) DEVICES! HTC, LG, AND OTHERS THAT REQUIRE A BOOTLOADER UNLOCK SITE OR DEVICES WITH A DIFFERENT INSTALLATION PROCESS ( *cough cough* SAMSUNG) ARE NOT SUPPORTED!!
Screenshots:
Coming Soon
Downloads:
Prebuilt
Prebuilt [VB.NET]: (Version 2.0) https://github.com/PJBeans/LineageOS-Installer/releases (Tested on Nexus 7 2013 WiFi)
CURRENTLY FOR TESTING PURPOSES! - "-development" will be removed in the program once the program is known to be stable.
VB.NET is primarily developed by chompy33 (PJBeans), and C# is primarily developed by Evilarceus. Each branch's source can be found below.
Source
Source: (Version 2.0-development) https://github.com/PJBeans/Lineage-OS-Installer (I encourage absolutely anyone to contribute, even if you would like to make just a minor change!)
Updates:
Past:
UPDATE 1.4.0 and 1.4.1(VB.NET)
(I never published 1.3.0, so here's 1.4.0)
- Scripts have been updated; the user no longer needs to interact with TWRP.
- There is one button to install.
- The script automatically backs up data, cache, and dalvik prior to wiping for installation (no backup before unlocking the bootloader, however)
- (1.4.1) Fix issue with application failing to start (Thanks, @dinesh_redhawk for pointing out this bug that I somehow missed!)
- (1.4.1) Update Installer
UPDATE 1.2.0 (VB.NET)
- User must type "yes" before starting the process to ensure they know to read everything and follow all instructions given.
- Support for GApps
- More messages for user instructions.
- Scripts should be working correctly.
UPDATE 1.1 (VB.NET)
- More Material Design
- 3 step installation (Unlock Bootloader, Flash Recovery, install LineageOS)
- Added a beautiful background image (IMO) of New York City on First Form
Current:
UPDATE 2.0 (VB.NET)
- Check out the release notes on GitHub (Prebuilt Download link)
What is your viewpoint on this? Would you actually want an installer to exist for those who are inexperienced with flashing ROMS?
Sorry for such as long post, and I did not put this in DevDB because it is not directly an Android project.
chompy33 said:
Hi,
---
Normally when I come on the XDA forums, I am asking a question, because I end up making a silly mistake in Android. I never like to put out promotional content for attention, and that is surely what I am not doing here, I am simply putting my work out there to see if the community would like it and if we do like, we can begin setting it up for other devices immediately. Now, I am not a skilled programmer at all, but I know SOME Visual Basic with Windows Forum Applications, so I thought "why not give it a shot." I just wanted to say that.
So I made this simple little application called Lineage OS Installer. Now, reading through some of the comments on the Lineage OS Reddit page, some people were asking if there would be an installer for Lineage OS, and there was a good amount of people who did not want one, which makes sense; people should know what they are getting into, and understanding ADB and Fastboot is indeed important. However, sometimes, there is a person who is not involved with ROMS, who is fine with OEM Android, who does not want to use root and what not, however, they want the latest version of android possible for their device, and that was a main point of CyanogenMod; users could get the latest version of android on their phone and tablet when their manufacturer/carrier stopped supporting it. However, the installation can be intimidating, and for the user that I just described earlier, the user who does not want root and what not, that could mean they won't bother attempting to install a custom ROM. However, this application automates the process; all the user needs to do is click some buttons, and press Enter a few times to install Lineage OS.
I understand I don't need "permission" to distribute this program, however, I am just asking if the overall community would support the use of this program.
---
This is a simple graphical and command-line based installer to make it easier to install LineageOS; this program is aimed at beginners. It is not the prettiest program ever, but it still works with my Nexus 7 2013 WiFi just fine
I did not add support for flashing google apps (gapps) yet, just because I do not know if we will use the same open-gapps package that was used in CyanogenMod, or if we would switch to something different.
Features:
[ADB and Fastboot is required, but NOT included.]
- Instructions to enabling Developer Options, USB Debugging, and OEM Unlocking (if required)
- a file called setup.bat, that will set up the directory where all the required files live
- Embedded browsers to download TWRP and LineageOS*
- Included script that runs `adb devices` to ensure device is recognized
- Installation script that sets up the device to install Lineage OS, and pushes LineageOS to the device.
- Gives instructions for steps that must be completed on the device (Wiping, flashing, etc.)
The program's installation script is finished; it does its job to install a ROM to a device; it will unlock the bootloader, flash TWRP, and push the lineageos image. (I substituted LineageOS for CyanogenMod 13 while testing). *The only thing unfinished it the embedded browser to download LineageOS.
I would not recommend using it currently as it is still in early development
Downloads:
Prebuilt: https://drive.google.com/file/d/0B70zQND1cM1WQVFjYi0yZy1BVnc/view?usp=sharing
Source: https://github.com/PJBeans/Lineage-OS-Installer
I understand that the main focus with LineageOS right now is to set up the website, servers, and images, and I do not want to distract those users. But this is what I would like to ask anyone: Would you actually want an installer to exist for those who are inexperienced with flashing ROMS?
Sorry for such as long post, and I did not put this in DevDB because it is not directly an Android project.
Click to expand...
Click to collapse
Ill be honest. This is most dangerous for inexperienced users. If something goes wrong then they have no idea how to fix or find out how to fix it.
If used it would be best suited for someone that does rom testing where they flash multiple times a day, but as you are required to use a pc I really dont see much use for it.
just my thoughts.
zelendel said:
Ill be honest. This is most dangerous for inexperienced users. If something goes wrong then they have no idea how to fix or find out how to fix it.
If used it would be best suited for someone that does rom testing where they flash multiple times a day, but as you are required to use a pc I really dont see much use for it.
just my thoughts.
Click to expand...
Click to collapse
Thank you for your reply! I completely see what you mean; an inexperienced user could possibly freak out, perhaps disconnect the device while something was going on. Perhaps I/anyone else who contributes could add a support section clearly marked for troubleshooting, complete with a guide to reflash stock. If I/someone else did this, would that make it more friendly for beginners in your eyes?
chompy33 said:
Thank you for your reply! I completely see what you mean; an inexperienced user could possibly freak out, perhaps disconnect the device while something was going on. Perhaps I/anyone else who contributes could add a support section clearly marked for troubleshooting, complete with a guide to reflash stock. If I/someone else did this, would that make it more friendly for beginners in your eyes?
Click to expand...
Click to collapse
Yes that make it more friendly for beginners.
I'd be happy to help this project. I could maybe create a UI for this if all goes well.
Also, you should try learning C# if you already know Visual Basic. It's more widely supported and requires less typing. I can still contribute, since I do know both C# and Visual Basic
I wonder if it would be too much to ask to have this program automatically make a NANDROID backup before starting. Incase an inexperienced user disconnected the device or did something to disrupt the install, and caused a soft brick or similar, the NANDROID backup could be restored, and the user could re-attempt, with no harm done.
evilarceus said:
I'd be happy to help this project. I could maybe create a UI for this if all goes well.
Also, you should try learning C# if you already know Visual Basic. It's more widely supported and requires less typing. I can still contribute, since I do know both C# and Visual Basic
Click to expand...
Click to collapse
Thanks! The source is in the original post. The only thing that does not have a UI is the installation (although the current UI is pretty bad) I will try to learn C# as time goes on. If you would like to make part of the program in C#, feel free!
Doofitator said:
I know Visual Basic, and I'd be happy to help with the development of this application, too.
I also wonder if it would be too much to ask to have this program automatically make a NANDROID backup before starting. Incase an inexperienced user disconnected the device or did something to disrupt the install, the NANDROID backup could be restored, and the user could re-attempt, with no harm done.
Click to expand...
Click to collapse
Thanks for your reply! The source is above. Creating a NANDROID back is a great idea, perhaps we could create an automatic restore option too.
I am worried by the usage by inexperienced users. They are more prone to panic and destroy their phone, which could lead to a bad name for lineageOS on many forums where they will complain that lineageOS just killed their phone, while they did'nt understand the simplest part of the process.
BUT
This can be a tool very useful for experienced users who serially update phones of their many inexperienced friends.
I am doing just that (with around 50 differents phones to date) with my many friends of friends, and a tool like yours would simplify my job. For the moment, i keep a directory of directorys containing rooter scripts, recoverys, roms, gapps, utilities (adb, fastboot, odin, heindall,...) and have a multi-gigabyte library of those.
A utility who prepare a directory for a phone model, download rom, twrp/cwm, gapps, and do the phone rooting for every phone is a very desired thing, but it is a hell of a project to achieve.
So good luck with your project, and dont hesitate to ask me for help if you need, i would be proud to help you achieve your goal.
mlsoftlaberge said:
I am worried by the usage by inexperienced users. They are more prone to panic and destroy their phone, which could lead to a bad name for lineageOS on many forums where they will complain that lineageOS just killed their phone, while they did'nt understand the simplest part of the process.
BUT
This can be a tool very useful for experienced users who serially update phones of their many inexperienced friends.
I am doing just that (with around 50 differents phones to date) with my many friends of friends, and a tool like yours would simplify my job. For the moment, i keep a directory of directorys containing rooter scripts, recoverys, roms, gapps, utilities (adb, fastboot, odin, heindall,...) and have a multi-gigabyte library of those.
A utility who prepare a directory for a phone model, download rom, twrp/cwm, gapps, and do the phone rooting for every phone is a very desired thing, but it is a hell of a project to achieve.
So good luck with your project, and dont hesitate to ask me for help if you need, i would be proud to help you achieve your goal.
Click to expand...
Click to collapse
I see what you mean, and I/other contributors will (hopefully) try to make this process very user friendly, so they won't need to panic. I guess developers could use this if they needed to install the ROM on multiple devices, though currently the installation is kind of slow. I appreciate your response!
chompy33 said:
I see what you mean, and I/other contributors will (hopefully) try to make this process very user friendly, so they won't need to panic. I guess developers could use this if they needed to install the ROM on multiple devices, though currently the installation is kind of slow. I appreciate your response!
Click to expand...
Click to collapse
I would suggest that such a tool should be VERY wordy about telling the user what it is doing, and should NEVER suspend its apparent activity.
My experience (and it is commercial experience, with genuine products in the marketplace) is that the user will get nervous, and may do something unfortunate, if they fear that something has gone wrong...and they WILL fear this if there is no obvious activity for a long time...and "long time" might be only a few seconds.
So, to make this tool "safe", it should be continually reassuring the user that it is doing something. There should be a progress bar, that keeps moving. There should also be a text section that keeps updating what is going on. If the operation under way will take awhile, then this text session should (every few seconds) remind the user "I'm still working on this...estimated time to completion is XX seconds" (or some such).
This operation IS dangerous, particularly if the user does something wrong. So keep reassuring the user that everything is fine.
jiml8 said:
I would suggest that such a tool should be VERY wordy about telling the user what it is doing, and should NEVER suspend its apparent activity.
My experience (and it is commercial experience, with genuine products in the marketplace) is that the user will get nervous, and may do something unfortunate, if they fear that something has gone wrong...and they WILL fear this if there is no obvious activity for a long time...and "long time" might be only a few seconds.
So, to make this tool "safe", it should be continually reassuring the user that it is doing something. There should be a progress bar, that keeps moving. There should also be a text section that keeps updating what is going on. If the operation under way will take awhile, then this text session should (every few seconds) remind the user "I'm still working on this...estimated time to completion is XX seconds" (or some such).
This operation IS dangerous, particularly if the user does something wrong. So keep reassuring the user that everything is fine.
Click to expand...
Click to collapse
Good idea! Thanks for the suggestion, we will definitely incorporate this.
Two thumbs up for a LineageOS installer, plz develop it
Definitely having a LineageOS installer is a great idea!
Unquestionably, it will permit people who are not experienced with flashing custom roms(which accounts for a lot of people), nor do they have an interest in learning about that(e.g. my mom) to easily get the latest Android build on their Android phone (which may no longer be supported by the OEM; an e.g. AT&T LG G2).
44alexsmith said:
Definitely having a LineageOS installer is a great idea!
Unquestionably, it will permit people who are not experienced with flashing custom roms(which accounts for a lot of people), nor do they have an interest in learning about that(e.g. my mom) to easily get the latest Android build on their Android phone (which may no longer be supported by the OEM; an e.g. AT&T LG G2).
Click to expand...
Click to collapse
This is exactly what I am trying to achieve. Provided I/contributors make a stable build by the time a stable build of LineageOS comes out (or at least around there, it's an open source project so there is no official date), it could give LineageOS a reputation of being a very easy ROM to install. Thanks for the reply.
Creating an installer for users who don't event know what's going on from the inside is useless IMO.
If the installer fail to flash they get stuck with a bricked device and don't know what to do.
I added a .gitignore to reduce cloning size and keeping things clean: https://github.com/PJBeans/Lineage-OS-Installer/pull/1
If you want, add me as a collaborator on the GitHub project so I don't have to keep on making pull requests.
p4rot said:
Creating an installer for users who don't event know what's going on from the inside is useless IMO.
If the installer fail to flash they get stuck with a bricked device and don't know what to do.
Click to expand...
Click to collapse
Just FYI, I did say earlier that this installer should have an automatic NANDROID backup take place, so phones would be safe if something happened.
Doofitator said:
Just FYI, I did say earlier that this installer should have an automatic NANDROID backup take place, so phones would be safe if something happened.
Click to expand...
Click to collapse
We will attempt to add this (or at least guide the user) later on. Thanks for your response!
evilarceus said:
I added a .gitignore to reduce cloning size and keeping things clean: https://github.com/PJBeans/Lineage-OS-Installer/pull/1
If you want, add me as a collaborator on the GitHub project so I don't have to keep on making pull requests.
Click to expand...
Click to collapse
I set up a live chat on Telegram, the link is on the Repository's Readme. I appreciate your commitment to this project!
I sent an invite at https://github.com/PJBeans/Lineage-OS-Installer/invitations
chompy33 said:
We will attempt to add this (or at least guide the user) later on. Thanks for your response!
Click to expand...
Click to collapse
If possible, I think making this a mandatory step would be better - we don't want people skipping it and then complaining later.