Related
Can I get some quick help please. If the phone boots up with that message then is that standard for a retail unit? Thanks
Mine didn't, but mine came from O2 not direct from Dell.
Mine doesn't and it's direct from Dell.
Ok, this one that I won on ebay but not paid for it yet. It says its from O2 and brand new in box with screen protector, but doesn't sound like retail?
The seller says: "what you seen online photos are promo converse i have not touched my unit
are original stickers and screen protector and when you start up the unit
it show dell confidential"
What do you think & what would you do?
Thanks
Must say have not read of anyone saying that before and i read everything on the net about the streak
hmm i've been reading a lot around this forum and a couple others and never heard of that.
I think its either 1 of 2 things. 1 is that it could be a custom bootscreen that someone made and put it on (very simple to do). or 2 is that is running some beta build of android. Sometimes manufacturers will put confidential or similar terms on prototypes and pre-release devices.
Go to settings-> about phone-> Software information and either post a screen shot of that page or type that info out here.
ok thanks for the info guys. I have not paid for the item just yet but I won the auction today. So basically do not have the item on me. Do you guys think its legit then as it's meant to be locked onto O2? Am guessing the firmware can be updated to the latest one but hoping the phone itself is same as retail? Will probably be paying through paypal so hopefully I have some security if things go wrong.
The device is beta-quality.
Biggest drawback is that it lacks the "fastboot" option (which is mandatory for ROM upgrade).
This means the model can never be upgraded.
skliarie said:
The device is beta-quality.
Biggest drawback is that it lacks the "fastboot" option (which is mandatory for ROM upgrade).
This means the model can never be upgraded.
Click to expand...
Click to collapse
What are you talking about? Where did you get your information? And why are you opening a year old thread?????
The Streak has fastboot. Most of the people on this forum have upgraded or changed their ROM. And this OLD thread was referring to the pre-release Streak of a year ago. The Streak of today is certainly not "beta-quality"!!!
Mods - This thread should be locked as it is outdated.
ive seen that image loc somewhere in framrwork-res/res/
Changing the Dell startup logo... not easily done as fone_fanatic suggested, bootanimation sure, but not the dell logo. My best guess is a beta/testing device. which ..should.. have fastboot I would imagine.
this guy could have some cool stuff on the there, send TheManii a system dump.
I would love 2 things.... how to customize dell logo on startup, not boot animation, logo, probably mroe involved than its worth, I think its encrypted. And fina a list of all the fastboot dialer codes.. they have to be hidden deep in the system, otherwise how would the device recognize them. Its all low level bootloader stuff, though, a bit beyond me.
chrisrotolo said:
ive seen that image loc somewhere in framrwork-res/res/
Changing the Dell startup logo... not easily done as fone_fanatic suggested, bootanimation sure, but not the dell logo. My best guess is a beta/testing device. which ..should.. have fastboot I would imagine.
this guy could have some cool stuff on the there, send TheManii a system dump.
I would love 2 things.... how to customize dell logo on startup, not boot animation, logo, probably mroe involved than its worth, I think its encrypted. And fina a list of all the fastboot dialer codes.. they have to be hidden deep in the system, otherwise how would the device recognize them. Its all low level bootloader stuff, though, a bit beyond me.
Click to expand...
Click to collapse
I have seen that message on a friends streak, and definitely there is fastboot but the device is kindda semi bricked(??), you cant put any custom image on it, neither any other official rom.
The message actually says something like this:
Dell Confidential
The emergency software recovery failed please contact a nearest dell service center to get it repaired, do not pull the battery out of the unit, or try to restore factory defaults.
After that the phone boots up normally( however the phone factory resets on its own a lot, like once or twice a day)
354 rom is installed on the phone
and streakmod recovery while installing(Any custom rom) says that the sd card is not detected.
This happened after he tried something with QDL.
However dell is replacing the unit.
We are even unable to take a nandroid of the phone.
Seems like a bad internal sd card
IMHO to the OP refrain to buy the unit.....
Has anyone had a problem registering transformer device on vip.asus.com?
When I'm trying to do this - website complains that my serial number is invalid (I double checked it and it's correct). Has anyone had something similar?
I have a sneaky suspicion that this might explain why I'm not getting an OTA 3.1 update...
Cheers,
Irek
I think it's much more likely that you just aren't inputting the code correctly. The 0's and O's are hard to tell apart but they are actually different characters. Also the B's and 8's. This won't have anything to do with the fota update either, people get that regardless of if they have registered or not.
I ran into this earlier. Are you trying to put the serial number that is found in settings - about tablet? What you need to use I'd the one on the box or on the sticker inside the warranty pamphlet.
Don't know why they differ and was gonna create a thread to see if I'm the only one.
Sent from my Transformer TF101 using XDA Premium App
fone_fanatic said:
I ran into this earlier. Are you trying to put the serial number that is found in settings - about tablet? What you need to use I'd the one on the box or on the sticker inside the warranty pamphlet.
Don't know why they differ and was gonna create a thread to see if I'm the only one.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
Yes. I was using one from the box. Number had two zeros, so I tried all four combinations replacing zeros with letter 'O' - but no luck. I contacted ASUS support (sent them a photo of the sticker) - will wait for their response.
I had the same issue, then I contacted Asus and they advised me that the first sign should be letter B and the third-letter O.
The rest are definately 8-s and zero's
I got an initial response from ASUS support. I sent them a photo of my box - so they can decode number for themself. Here is a response:
Dear Irek,
Thank you for your email.
The serial number is not being recognized by our systems. I have tried two different databases and still it states-the serial number is incorrect.
Could you advise on where did you purchase the unit?
Click to expand...
Click to collapse
Got mine from amazon.co.uk (so not a dodgy source). Asked them to do some more investigation. Truly bizarre - asus seems to have problems with tracking it's own shipments.
---
EDIT: got a final response from ASUS support - they started internal investigation how this could happen and recommended to return device for a refund (as it might take a while)
pt_monkey said:
I had the same issue, then I contacted Asus and they advised me that the first sign should be letter B and the third-letter O.
The rest are definately 8-s and zero's
Click to expand...
Click to collapse
Thanks PT_Monkey. I thought the third letter was a ZERO instead a O. Your post helped
Also registering your tablet on their websit edoes nothing to help get the update to you faster, I'm not sure why this rumor started. Their OTA just seems to randomly happen and I have a feeling overall there are just issues with it and it has nothing to do with your serial #.
i jsut registered mine. i had an issue with the first "O" the O's are wider than the zeros.
I returned the TF today due to the serial number coming up invalid in Asus database and being unable to receive the 3.1 update.. I have read in other threads that quite a number of people have had the same situation and Asus explains saying that the unit was never entered into the database and an internal investigation is ongoing with no timetable for resolution. . Also it was stated that the system looks for serial number before sending out the update to the devicel It has been reported that they also said to return for exchange or refund. I really really liked this device but could not justify keeping it if I might run into warranty issues somewhere down the line, due to the serial number showing up invalid. Great device though!!!!!!!!!!!!!!!!!!!!!!!!
http://waveshare.asus.com
I xposted on Asus Prime, but it might be relevant to the original model as well. Can anyone get to this site and get it to work? Mine says sending forever.
edit: got it, used my google account to sign in instead and it worked
dude2k5 said:
http://waveshare.asus.com
I xposted on Asus Prime, but it might be relevant to the original model as well. Can anyone get to this site and get it to work? Mine says sending forever.
edit: got it, used my google account to sign in instead and it worked
Click to expand...
Click to collapse
When I enter my serial number it says "Please enter correct Serial Number"
For some reason it shows incorrect serial in about menu. Typed the one written on the box and it showed me another error saying that TF101 and slider running HC are not supported.(updated to ICS)
When I enter my serial it says it will be available on ICS (which I'm running) and not available on honeycomb...
aligatro2010 said:
When I enter my serial number it says "Please enter correct Serial Number"
For some reason it shows incorrect serial in about menu. Typed the one written on the box and it showed me another error saying that TF101 and slider running HC are not supported.(updated to ICS)
Click to expand...
Click to collapse
+1
Mine is TF101.
Same issue.
Anyone found a fix?
Also (more importantly): should the S/N in the menue be the same as the label on the TF101?
If yes: is there a way to change the S/N so the menu shows the correct number?
There are two seral numbers on the device one is the B## number the other is in the software so you need to go to settings/about to find it. If you are on a custom rom that may have changed
mrevankyle said:
There are two seral numbers on the device one is the B## number the other is in the software so you need to go to settings/about to find it. If you are on a custom rom that may have changed
Click to expand...
Click to collapse
Thanks for the quick reply.
Yup, I have the B70xxx S/N on the device and a 16 digit number in the software.
I previously did root/unroot my TF101 but now back on stock. Does rooting/unrooting have something to do with the mismatch? or is this normal to have the 2 different numbers?
Like other posters: when I enter the S/N found in settings I get the message "please enter correct SN". When I enter the B70 SN I get the message "not supported on Honeycomb" (even though I'm on ICS).
The serial number in the menu is the device's specific ID number, this is used when you are in ADB or APX mode, if for example you are programming multiple TF101's simultaneously, to discern which device you are communicating with. As far as I can tell, the S/N on the case is the MFG Serial, not the Device ID, and thus Asus should be tracking it by the serial number, although as mentioned if you flash your device with another firmware, this may cause conflict with Asus' database of S/Ns..I haven't tested this to be sure, but I am thinking that the device ID will remain the same regardless of which ROM you flash, as this seems to be tied to the bootloader, which is what the PC communicates with (for example, my bootloader got wiped while flashing Ubuntu, and after flashing back to stock the PC would not recognize my device until I reflashed the ICS bootloader..so if you have flashed your bootloader this may also cause a conflict with Asus' database, I can't confirm for sure).
I will do some investigating when I get home to see if flashing ROMs and bootloaders will alter the device's ID number, or if I can otherwise discern what exactly will cause conflict like this, i.e. flashing a custom ROM, flashing a modded stock ROM, flashing a new bootloader, etc. That is, provided my device will be recognized to begin with (as stated, I have had to flash the bootloader once, so that may cause a problem for me).
There are some ADB commands that will pull up this device ID number (and maybe serial number too, not too sure on that) and I will see if this number changes at all while flashing custom ROMs..either way, I'm sure there is some sort of algorithm that is responsible for tying these two numbers together (similar to the bootloader in the OG Xbox and the serial number of the device/HDD, all these numbers were used to create the unlock key for the HDD/BIOS, there is more than likely a similar function tying these numbers together for Asus as well). Though it will take some testing to confirm whether these numbers can be altered in the device's memory.
This may help chatch find his stolen TF since he knows his MFG S/N..
I also had my Transformer stolen a few days ago. As soon as I realized it had happened I tried to push some apps to it( plan b, other tracking apps) but I was too late I guess. Maybe it was already wiped. It had the Revolver ICS Rom installed on it and I checked the tracking option in settings.
When I entered the model serial number on the original packing box (Luckily? I still had it) I got that same error about it not working on the TF101.
It really sucks knowing someone is having fun with my sweet baby
Sent from my HTC Raider X710e using xda premium
Androidlost
A much better free alternative (all Android, not only ASUS) is the app androidlost on the market.
I've also just tried both serial numbers, same message as you guys got. Obviously an error by Asus. I'm totally stock USA ICS firmware
Sent from my Transformer TF101 using xda premium
Remember folks the O in B5O, B6O, B7O, etc is a O, as in Ohh, not 0 as in zero. All other 0s in serial number are zero.
Either way this doesn't work with tf101 right now.
Sent from my Transformer TF101 using Tapatalk
I just sent an escalation support email to Asus about this issue. Will keep you informed on what I hear back from them.
Sent from my SGH-T959 using xda premium
eminembdg said:
I just sent an escalation support email to Asus about this issue. Will keep you informed on what I hear back from them.
Click to expand...
Click to collapse
I did too.
But my hopes are low. They did not reply to a previous case I opened online (dock issue). Had to phone Asus Australia to open a case again.
I think everyone who have this problem should log a case with them. Maybe this will put enough pressure on them to take notice.
yud said:
I did too.
But my hopes are low. They did not reply to a previous case I opened online (dock issue). Had to phone Asus Australia to open a case again.
I think everyone who have this problem should log a case with them. Maybe this will put enough pressure on them to take notice.
Click to expand...
Click to collapse
Agree! It literally takes like at most 3 minutes to send escalation email. The more the better
Sent from my SGH-T959 using xda premium
Wow! Total shocker! They still haven't replied back to me. Ugh
Sent from my SGH-T959 using xda premium
Different number here
I work at Best Buy here in the US and bought my Asus Transformer about a month ago. I've tried to use that Device Tracker thing too but keeps telling me the same thing it's been telling y'all. Only thing is, the serial number I have starts with C1O. Does anyone else have something similiar?
CaliTexan5 said:
I work at Best Buy here in the US and bought my Asus Transformer about a month ago. I've tried to use that Device Tracker thing too but keeps telling me the same thing it's been telling y'all. Only thing is, the serial number I have starts with C1O. Does anyone else have something similiar?
Click to expand...
Click to collapse
DOESN'T matter what serial you have nor which one you use, either the one on the sticker or one in the settings menu. They've obviously messed something up on their end. It won't work with our tf101s
Sent from my Transformer TF101 using xda premium
Well here's the reply I got back from Asus :
Dear Mr. Ginley,
I do apologize for your inconvenience and we do aware of the issues. In the meantime have you tried factory reset feature after the latest firmware update? Please backup your personal data and try this method if you have not done so. Please do let me if the problem still persists afterward.
Thank you,
Aaron L ASUS Customer Care Team
Sent from my SGH-T959 using xda premium
Obviously a factory reset wont do anything, I've tried. So I replied with that and we'll see what happens now
Sent from my SGH-T959 using xda premium
eminembdg said:
Obviously a factory reset wont do anything, I've tried. So I replied with that and we'll see what happens now
Click to expand...
Click to collapse
as expected...
why would a factory reset do anything???
it's not our devices that have a problem, it's their Device Tracker system...
I bought my Nexus in July and it was affected by the screen flickering problem (No big deal) but now its having an issue with the digitizer.
every time i touch the right side of the screen it clicks the left side (i.e. if I touch back space it types a Q instead)
anyway on to my issue the SSN on my box no longer is the same as the serial number in the about screen were they the same or have i messed it up somehow when rooting and having fun with MY device!?
I have reset the tablet with the Root toolbox to the default ICS from google and locked the bootloader
Are you putting a zero instead of an "O" after the month digit on the Asus VIP site?
example. It should be C7O not C70. A lot of people on here mistake the O for a zero.
** I just reread about your number in the About settings page is different? Have you tried entering both, as long as its valid it should register
NeoMagus said:
Are you putting a zero instead of an "O" after the month digit on the Asus VIP site?
example. It should be C7O not C70. A lot of people on here mistake the O for a zero.
** I just reread about your number in the About settings page is different? Have you tried entering both, as long as its valid it should register
Click to expand...
Click to collapse
No I called them and gave them the info from the box cause the Serial number on the tablet in the Settings<About<Status does not match the one on the box or on the sticker that was on the nexus it doesn't even start with C6O anymore its a O15 now.
I don't know if it was always like that or did something happen while I was playing around with other roms
I am just worried that sending a tablet RMA with the wrong serial or a serial that doesn't even match the device will cause major problems!
I flashed the original images via fast boot for return and also noticed serial number had changed on device as well.but the store exchanged it anyways but they did notice. I said maybe it was the ota update? They did not care.
Travisdroidx2 said:
I flashed the original images via fast boot for return and also noticed serial number had changed on device as well.but the store exchanged it anyways but they did notice. I said maybe it was the ota update? They did not care.
Click to expand...
Click to collapse
I am starting to second guess the RMA with ASUS as I am seeing a lot of bad rep for their RMA process. Maybe I will just look into fixing it myself. I have the tools and know how if I knew what was causing the problem.:cyclops:
AZKJS said:
I am starting to second guess the RMA with ASUS as I am seeing a lot of bad rep for their RMA process. Maybe I will just look into fixing it myself. I have the tools and know how if I knew what was causing the problem.:cyclops:
Click to expand...
Click to collapse
Call asus and ask about serial changing after update
Sent from my LG-P500 using xda premium
No need to worry, if you pop your back cover off, there is a serial number..
Beamed from my Grouper.
Hello,
I got a NOOK Glowlight 6", but when I turn it on it connects to wifi, but does not want to register. I downloaded the new version of the firmware, but it still gives the same error - "Network Problem. A network-related error occurred. You may have lost connectivity to the local wireless network. Press Continue and we'll try to test your connection". I tried it at several internet access points. Where to look for the problem? How to reset to factory settings?
miteff71 said:
Hello,
I got a NOOK Glowlight 6", but when I turn it on it connects to wifi, but does not want to register. I downloaded the new version of the firmware, but it still gives the same error - "Network Problem. A network-related error occurred. You may have lost connectivity to the local wireless network. Press Continue and we'll try to test your connection". I tried it at several internet access points. Where to look for the problem? How to reset to factory settings?
Click to expand...
Click to collapse
When your device is at the welcome screen and you attach it to your PC, can you still see the update zip on the Nook drive? If so the update has not happened. You need to leave it alone to go to sleep before it will install the update. See my comments in the post directly after this one for information about a factory re-image.
Odd that there are essentially two identical problems within a few days.
nmyshkin said:
When your device is at the welcome screen and you attach it to your PC, can you still see the update zip on the Nook drive? If so the update has not happened. You need to leave it alone to go to sleep before it will install the update. See my comments in the post directly after this one for information about a factory re-image.
Odd that there are essentially two identical problems within a few days.
Click to expand...
Click to collapse
When I copy the device update and let it sleep, I check over time and the backup file is missing. This means that the update was successful. However, it cannot be registered. Additionally, I learned that this device has never been used since it was purchased and has not been registered, although it is an older model. Now I'm trying for the first time and so far without success.
Nook glowlight 6" factory reset
miteff71 said:
When I copy the device update and let it sleep, I check over time and the backup file is missing. This means that the update was successful. However, it cannot be registered. Additionally, I learned that this device has never been used since it was purchased and has not been registered, although it is an older model. Now I'm trying for the first time and so far without success.
Click to expand...
Click to collapse
Today I factory reset the device and copied the new firmware, which is installed, but again does not want to register.
Then I bypassed Oobe and the device can now be used locally, only it is constantly looking for a connection to a news server, but ...
miteff71 said:
Today I factory reset the device and copied the new firmware, which is installed, but again does not want to register.
Then I bypassed Oobe and the device can now be used locally, only it is constantly looking for a connection to a news server, but ...
Click to expand...
Click to collapse
It's difficult to imagine at this late date what might be wrong with a device that has never been used before.
A few things come to mind:
1. You say you did a factory reset. People often confuse an erase/deregister with a factory re-image. They are very different. There's not much point in an erase/deregister with a device that has never been used before. A factory re-image (triggered by eight failed boot attempts or by some software package like Nook Manager), on the other hand, would theoretically correct something that happened recently which corrupted the system and is preventing it from behaving properly.
2. I should have asked this at the beginning but I didn't. Are you by any chance outside the U.S.? If so, is it possible you have a device with non-U.S. firmware? I actually don't know if the 1.2.2 firmware update can be applied successfully to a non-U.S. device. The procedure I would expect to work would be to flash U.S. firmware first, then do the update and then try to register the device. If that is your situation, here is a link to the site where you can get information about flashing U.S. firmware: https://sites.google.com/site/xcdguides/nook/nookregion
3. Skipping OOBE is one approach but unless you plan to remove all the B&N system (including the Reader), you're going to be stuck with a hobbled device with shortened battery life.
4. Have you tried calling B&N support? Sometimes devices are "blacklisted", although it seems like yours would never have had the chance. If the device is blacklisted on their servers, no amount of fiddling on your part is going to fix anything.
nmyshkin said:
It's difficult to imagine at this late date what might be wrong with a device that has never been used before.
A few things come to mind:
1. You say you did a factory reset. People often confuse an erase/deregister with a factory re-image. They are very different. There's not much point in an erase/deregister with a device that has never been used before. A factory re-image (triggered by eight failed boot attempts or by some software package like Nook Manager), on the other hand, would theoretically correct something that happened recently which corrupted the system and is preventing it from behaving properly.
2. I should have asked this at the beginning but I didn't. Are you by any chance outside the U.S.? If so, is it possible you have a device with non-U.S. firmware? I actually don't know if the 1.2.2 firmware update can be applied successfully to a non-U.S. device. The procedure I would expect to work would be to flash U.S. firmware first, then do the update and then try to register the device. If that is your situation, here is a link to the site where you can get information about flashing U.S. firmware: https://sites.google.com/site/xcdguides/nook/nookregion
3. Skipping OOBE is one approach but unless you plan to remove all the B&N system (including the Reader), you're going to be stuck with a hobbled device with shortened battery life.
4. Have you tried calling B&N support? Sometimes devices are "blacklisted", although it seems like yours would never have had the chance. If the device is blacklisted on their servers, no amount of fiddling on your part is going to fix anything.
Click to expand...
Click to collapse
For changing the region for Nook Simple Touch with Glowlight (https://sites.google.com/site/xcdguides/nook/nookregion), but whether the same is applicable for Nook Glowlight (2013)? Or there must be another application?
miteff71 said:
For changing the region for NSTG...
Click to expand...
Click to collapse
No, that stuff is a whole system image for the NST.
It has nothing to do with the Glowlights.
I'm sure that there are localizations for language (which is a bunch of text) and that "region" is something smaller.
How is "region" adversely affecting you, be specific.
Does it say when you try to register, "You live in the Purple Zone, you can't do that!".
If you tell me the exact sympton I can figure out where to defeat it.
Renate NST said:
No, that stuff is a whole system image for the NST.
It has nothing to do with the Glowlights.
I'm sure that there are localizations for language (which is a bunch of text) and that "region" is something smaller.
How is "region" adversely affecting you, be specific.
Does it say when you try to register, "You live in the Purple Zone, you can't do that!".
If you tell me the exact sympton I can figure out where to defeat it.
Click to expand...
Click to collapse
The problem is that by skipping the registration, there is a window in the home news screen that is constantly looking for a connection to the server to view the news, but apparently looking for it on an UK server, and can not connect, so the battery drops more. faster than usual.
As can be seen from the time settings, only European time zones can be selected.
Obviously you need to change the location to register and not draw much from the battery.
miteff71 said:
The problem is that by skipping the registration, there is a window in the home news screen that is constantly looking for a connection to the server to view the news, but apparently looking for it on an UK server, and can not connect, so the battery drops more. faster than usual.
As can be seen from the time settings, only European time zones can be selected.
Obviously you need to change the location to register and not draw much from the battery.
Click to expand...
Click to collapse
OK, so you've not been very precise. What exactly is 6" NGL? A model number would be really helpful so people would know what you are talking about. My assumption (among many) was that you were dealing with an old Nook Touch with Glowlight. If not, then nothing I have said applies.
nmyshkin said:
OK, so you've not been very precise. What exactly is 6" NGL? A model number would be really helpful so people would know what you are talking about. My assumption (among many) was that you were dealing with an old Nook Touch with Glowlight. If not, then nothing I have said applies.
Click to expand...
Click to collapse
I apologize for the cuts. It's about Nook Glowlight 6" white (2013) model BNRV500, not Nook Touch with Glowlight.
miteff71 said:
BNRV500
Click to expand...
Click to collapse
Oh, that's one of the models that I don't have.
It falls on the continental divide of the OMAP 3621 (NTS-like), not the side of the iMX6SL (modern Glows).
You said you downloaded the new firmware.
Which version, do you know the URL?
Renate NST said:
Oh, that's one of the models that I don't have.
It falls on the continental divide of the OMAP 3621 (NTS-like), not the side of the iMX6SL (modern Glows).
You said you downloaded the new firmware.
Which version, do you know the URL?
Click to expand...
Click to collapse
I have downloaded the new firmware v.1.3.2, which is on the B&N website -
https://help.barnesandnoble.com/app/answers/detail/a_id/4212/related/1
https://su.barnesandnoble.com/nook/...13520727ee73c620452b495/nook_1_3_2_update.zip
I have another device from the same model BNRV500, which has US regional settings, it is registered and works perfectly. The only difference is that when setting the time, you can select only US time zones, and the other only European time zones. Can the firmware with the settings be copied / extracted from the device with the US settings and transferred to the other? Probably needs to be rooted?
miteff71 said:
The only difference is that when setting the time, you can select only US time zones
Click to expand...
Click to collapse
Code:
# setprop persist.sys.timezone Asia/Vladivostok
Renate NST said:
Code:
# setprop persist.sys.timezone Asia/Vladivostok
Click to expand...
Click to collapse
Thank you for the answers.
The time zone differences are those seen in the settings, but there is probably a difference in the servers to which the device is trying to connect. I think this needs to change to be successful, but I don't know how.
This code provided by you, where should it be entered and how? I'm sorry, but I'm not a programmer. If it is done with any program, can I try, for example, Android studio? And should the device be rooted before that?
miteff71 said:
Where should it be entered and how?
Click to expand...
Click to collapse
That's the command line. You get there by using ADB. (There's lots of tutorials here on ADB.)
You need to be rooted. That's the #. Unrooted has a $.
I have a similar problem. My glowlight 3 won't register, I enter my credentials, and there is "working please wait" screen and nothing happens. The device is rooted, I installed Simple ink launcher and KoReader, everything works, except that yellow light which is so plesent at night.