Hi,
I was following these instructions: https://wiki.lineageos.org/devices/gta4xlwifi/install#pre-install-instructions
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
Now, click the button that the onscreen instructions correlate to “Continue” and/or “Unlock Bootloader”.
However, on my screen I see the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Volume up: ContinueVolume up long: Device unlock mode.Now which of these correlate to "“Continue” and/or “Unlock Bootloader”"?
Mario545 said:
Hi,
I was following these instructions: https://wiki.lineageos.org/devices/gta4xlwifi/install#pre-install-instructions
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
Now, click the button that the onscreen instructions correlate to “Continue” and/or “Unlock Bootloader”.
However, on my screen I see the following:
Volume up: ContinueVolume up long: Device unlock mode.Now which of these correlate to "“Continue” and/or “Unlock Bootloader”"?
Click to expand...
Click to collapse
What's ambiguous about it? Short press to download mode, long press to unlock the bootloader.
Short press is "Continue". Long press is "Device unlock mode"
I have to press the button that correlates to “Continue” and/or “Unlock Bootloader”. But both of them do. The one says "Continue" as in "Continue". The otherone says "Device unlock mode" as in "Unlock Bootloader”. Both are a match!
"Device unlock mode" seems to be the correct one. I would reformulate the instructions:
Now, click the button that the onscreen instructions correlate to “Device unlock” and/or “Unlock Bootloader”. You will then be forwarded to a new page where you have to confirm unlocking the bootloader. Click the button that corresponds to "yes" or "continue".
Click to expand...
Click to collapse
If anyone knows how to change the wiki, you can do it based on my suggestion.
P.S. And also
The device will demand you format userdata, please follow the onscreen instructions to do so.
is not correct. My device just formated userdata without any prompt. Maybe change it to "... the device will may demand ..."
Here is another beauty. It says:
Select Samsung USB Composite Device or MSM8x60 or Gadget Serial or Device Name from the drop down menu.
Click Replace Driver, then selecting Install Driver from the drop down list built into the button.
But replace it with what? There are multiple options you can select from the scroll box.
By default, it looks like this:
WinUSB (v7.0.0.1) -> WinUSB (v6.1.7600.16385)
And it says "Downgrade driver". Is that what they want? I can also scroll to the next one, then it would look like:
WinUSB (v7.0.0.1) -> USB Serial (CDC)
?
As many LineageOS documentation, this once again is incomplete, not well maintained, not tested well.
...so it seems it just needs to be any libusb compatible driver. WinUSB (v7.0.0.1) was sufficient and I didn't replace or install anything. If I would not have years of experiences with custom ROMs and operating systems in general, at this point, I would have been totally lost.
Normally, if I see something like this in a wiki, I would click "edit" and expand the documentation sharing my years of experience with others. But there is no edit button, and I have never figured out how to edit something in this wiki, so then this knowledge is just lost. The next user will stumble across the same issues.
Mario545 said:
...so it seems it just needs to be any libusb compatible driver. WinUSB (v7.0.0.1) was sufficient and I didn't replace or install anything. If I would not have years of experiences with custom ROMs and operating systems in general, at this point, I would have been totally lost.
Normally, if I see something like this in a wiki, I would click "edit" and expand the documentation sharing my years of experience with others. But there is no edit button, and I have never figured out how to edit something in this wiki, so then this knowledge is just lost. The next user will stumble across the same issues.
Click to expand...
Click to collapse
It seems just about everyone else has been able to follow the instruction without your help.
Yeah, because this mess regarding ambiguous install instructions and lack of good documentation has been around for a while now in the custom ROM community, scaring away anyone but the most experienced technical users. So it's no wonder that whose who remain can follow this insufficient instructions easily. It's a small community nowadays. The founder of CyanogenMod once had a dream to make their software accessible to everyone. But nowadays you have to constantly keep reading very detailed technical documentations, read through endless forum threads, teach yourself lots of things only a developer should need to care about, just to be able to keep using and installing custom ROMs. Sad.
Mario545 said:
Yeah, because this mess regarding ambiguous install instructions and lack of good documentation has been around for a while now in the custom ROM community, scaring away anyone but the most experienced technical users. So it's no wonder that whose who remain can follow this insufficient instructions easily. It's a small community nowadays. The founder of CyanogenMod once had a dream to make their software accessible to everyone. But nowadays you have to constantly keep reading very detailed technical documentations, read through endless forum threads, teach yourself lots of things only a developer should need to care about, just to be able to keep using and installing custom ROMs. Sad.
Click to expand...
Click to collapse
Maybe that's the point. If you don't know enough to interpret the instructions, you shouldn't be fooling with rooting and custom ROMs. If you can't understand short press to "Continue" to download mode or long press to Unlock the bootloader, do you really understand the consequences of rooting and custom ROMs?
Mario545 said:
Now which of these correlate to "Continue” and/or “Unlock Bootloader”"?
Click to expand...
Click to collapse
I understand your problem. It's really not clear which one to take. I've installed quite a bit of ROM. I always get very nervous when the explanation is not quite the same from the explanation and the tablet/smartphone.
Related
The purpose of this program is to make my life easier when developing on the Android Platform. At he same time it may also make your life easier. I would like to keep this project totally open source and I include all of the source files withing the .zip that it comes in. What does this program do? It will allow you to flash custom ROMs straight from your computer, fast and hassle-free.
In this new version, I have done a ton of error/big fixes, rewrote quite a lot, and finally added wiping functionality. Enjoy!
Infiniflash REQUIRES that your device has ClockworkMod Recovery or any recovery that supports /cache/recovery/extendedcommand.
By the way, if you can think of a better name/icon for this program, please, please, please tell me.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For full documentation and to download please visit: http://infinimod.com/ideas/
tried to use it
was not successful
1.pluged my DHD to pc (charge only)
2.run infiniflash.exe
3.have selected the rom
4.success comes and says the rom is going to be flashed from recovery
5.DHD goes to recovery
6.after 3 secs back restarted and nothing happened
what did I wrong?
mohammadsp said:
tried to use it
was not successful
1.pluged my DHD to pc (charge only)
2.run infiniflash.exe
3.have selected the rom
4.success comes and says the rom is going to be flashed from recovery
5.DHD goes to recovery
6.after 3 secs back restarted and nothing happened
what did I wrong?
Click to expand...
Click to collapse
I have a DHD as well and had the same issue. You must install the driver for it to work on your device.
1) Visit this link to download and install HTC Sync (which contains the driver): http://goo.gl/P3ZP1
2) After installation plug your device in.
3) To verify you have the driver, open the Infiniflash folder, hold the shift key and right click on the tools folder. Click open command prompt.
4) Now type in the command: adb devices
5) If your device showed up, it worked! Otherwise, try restarting or syncing your phone in HTC Sync, it should start working eventually.
6) Now that you have the driver, Infiniflash will *hopefully* work from now on.
Best of luck
Cheers.
Infinimint said:
I have a DHD as well and had the same issue. You must install the driver for it to work on your device.
1) Visit this link to download and install HTC Sync (which contains the driver): http://goo.gl/P3ZP1
2) After installation plug your device in.
3) To verify you have the driver, open the Infiniflash folder, hold the shift key and right click on the tools folder. Click open command prompt.
4) Now type in the command: adb devices
5) If your device showed up, it worked! Otherwise, try restarting or syncing your phone in HTC Sync, it should start working eventually.
6) Now that you have the driver, Infiniflash will *hopefully* work from now on.
Best of luck
Cheers.
Click to expand...
Click to collapse
yes true
the problem is that the pc doesn't recognize the phone
will give it a try
thanks
mohammadsp said:
yes true
the problem is that the pc doesn't recognize the phone
will give it a try
thanks
Click to expand...
Click to collapse
No problem, don't forget to tell us if it worked
This looks awesome, and I would use it but is there a different button for wiping to ext 4 and 3? All the roms I seem to switch between use different formats.
Thanks
Joey93 said:
This looks awesome, and I would use it but is there a different button for wiping to ext 4 and 3? All the roms I seem to switch between use different formats.
Thanks
Click to expand...
Click to collapse
By wiping to ext3 & ext4 do you mean formatting the /system partition to one of those formats? If so I might be able to implement it or make an add-on . By the way, which device requires you to do that? I've never heard of that before... are you sure it's a requirement?
Oops Double Post.
Has anyone successfully used this program?
even tho i cannot use this app as i am on linux i will salute your development as this app is a great idea. thank you for your contribution. wish i knew more about programming and could help port this over to linux but alas...
Grondinm said:
even tho i cannot use this app as i am on linux i will salute your development as this app is a great idea. thank you for your contribution. wish i knew more about programming and could help port this over to linux but alas...
Click to expand...
Click to collapse
Thank you very much! I think I'll port it over soon, but the only bad part about that is that I have no idea how to make GUI's in Linux so it would be command line only .
It's funny that you mention that though because I'm a Linux user myself and never really thought about it.
and after I rebooted again, then add 1 to the error as shown below :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have tried reset and run 2 lines are not save me!
help me
help me
vdsno1 said:
help me
Click to expand...
Click to collapse
Hey, I'm not positive what your post is asking for, but I think its for the stock rom, is that correct? If so, pm me and I'll send you my stock backup. It may have some extra "stuff" you don't want, but it's all I've got.
thanks yu
S_transform said:
Hey, I'm not positive what your post is asking for, but I think its for the stock rom, is that correct? If so, pm me and I'll send you my stock backup. It may have some extra "stuff" you don't want, but it's all I've got.
Click to expand...
Click to collapse
thank you for your enthusiasm and now I can not get into TWRP hashcode of you can help me how to restore it or not!
vdsno1 said:
thank you for your enthusiasm and now I can not get into TWRP hashcode of you can help me how to restore it or not!
Click to expand...
Click to collapse
Do you have adb still? if you do it may be fixable, but if not it may be impossible. I had to get a replacement from Amazon after a build.prop bricked me and I lost adb. Do you know why it stopped booting correctly?
thanks
S_transform said:
Do you have adb still? if you do it may be fixable, but if not it may be impossible. I had to get a replacement from Amazon after a build.prop bricked me and I lost adb. Do you know why it stopped booting correctly?
Click to expand...
Click to collapse
I am not sure whether the current adb because when I connect my laptop hdx, I see it still looking for the driver jumps until hdx was standing at my screen was taken at # 1 is my laptop can not find that driver again so I was not sure adb
vdsno1 said:
I am not sure whether the current adb because when I connect my laptop hdx, I see it still looking for the driver jumps until hdx was standing at my screen was taken at # 1 is my laptop can not find that driver again so I was not sure adb
Click to expand...
Click to collapse
In order to get it working you may have to manually assign it to the device. Try going to devices, right click on the kindle device and go to properties. Switch to properties and go to the one that doesn't have an assigned driver, if there is one. Hit properties, then change settings on the window that pops up. Go to driver, update driver, browse my computer, and then pick from a list. If you have the adb drivers installed, go to kindle fire, or amazon, or something like that, and then click adb interface. If it lets you do that then you should be able to get adb working. Hopefully this is useful.
S_transform said:
In order to get it working you may have to manually assign it to the device. Try going to devices, right click on the kindle device and go to properties. Switch to properties and go to the one that doesn't have an assigned driver, if there is one. Hit properties, then change settings on the window that pops up. Go to driver, update driver, browse my computer, and then pick from a list. If you have the adb drivers installed, go to kindle fire, or amazon, or something like that, and then click adb interface. If it lets you do that then you should be able to get adb working. Hopefully this is useful.
Click to expand...
Click to collapse
I did as you said is absolutely not found 1 hdx devices and adb does not work I still do not know how to do it again!! can anyone help me not
help me help me
vdsno1 said:
help me help me
Click to expand...
Click to collapse
First of all, you need to stop posting this EVERYWHERE. There are many warning about messing with the HDX posted & you chose to ignore them.
Secondly, if you want help, be concise. All I see is "bridge doesn't work". Your picture does not show up, if that is what it is, so I have no idea what you are referencing. I have no idea what your setup is, or whether you have read any of the posts talking about loss of ADB. You need to slow down & take a breath.
Do you have the entire Android SDK installed? Have you tried getting ADB connection from the Android SDK home/main directory? Once I lost ADB access, the only way I could conenct after restoring was from my installed SDK directory, which for me is C:/Android. For you it depends on where you installed it, but you need to try from there or the platform tools folder.
thanks
GSLEON3 said:
First of all, you need to stop posting this EVERYWHERE. There are many warning about messing with the HDX posted & you chose to ignore them.
Secondly, if you want help, be concise. All I see is "bridge doesn't work". Your picture does not show up, if that is what it is, so I have no idea what you are referencing. I have no idea what your setup is, or whether you have read any of the posts talking about loss of ADB. You need to slow down & take a breath.
Do you have the entire Android SDK installed? Have you tried getting ADB connection from the Android SDK home/main directory? Once I lost ADB access, the only way I could conenct after restoring was from my installed SDK directory, which for me is C:/Android. For you it depends on where you installed it, but you need to try from there or the platform tools folder.
Click to expand...
Click to collapse
yes thank you for sharing .... I will not post any more awkward!
- Can you tell me in detail how do you save your machine is compatible or not?
vdsno1 said:
yes thank you for sharing .... I will not post any more awkward!
- Can you tell me in detail how do you save your machine is compatible or not?
Click to expand...
Click to collapse
FIrstly, do you have the Android SDK installed? You need to do that to have the latest version of the platform tools & you need to follow those instructions so that you can call those tools from any folder, by adding them to your environmental path. There are already a hundred tutorials on installing the SDK, so I am not going to list every step. Start here: http://developer.android.com/sdk/installing/index.html
Then, once you are done, follow up with the info here: http://forum.xda-developers.com/showthread.php?t=1842969
That will get you to a point of readiness & understanding to begin trying to recover. LMK when you are done.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi Friend
in contact with the developers VRoot
I request them on Sony 's Android 4.3 also
work with the Boot Loader Lock
This feature was added in the new version of the program
Today I got the opportunity to put this learning
How Root
* First joined the program, or download the source site
*Before installation , make sure your device drivers are installed
*Now install the program normally
*The options on your phone ( Unknown sources & USB debugging ) enabled
*Now connect your phone to the PC and the program Vroot open
(When you connect the phone to connect to internet)
*The program will let you update messages
After a few seconds it takes to install a Application on your phone
Now Root Messaging application will appear on the right
Select it
*Then your phone will reboot
But the program is still work in progress
May take several minutes
After a few seconds, the phone again will reboot
*The appearance of this message, your phone is successfully root
*The application icon should appear on your device menu
*Now your phone can act Czech Root was successful
*to remove the Vroot and install SuperSU
First, go to this link to download the recovery Philz
http://forum.xda-developers.com/showthread.php?t=2649923
* Click on Options install.bat
Then select the first option
question, select the option Allow
*This message displays a successful installation of your recovery
Now turn off your phone
Turning on the phone will see four lights advancing when the blue light show press
Volume up -> Philz
install zip from sdcar and then select the option to install CWM SuperSU
Then reboot the phone
Congratulations work done
Now we have root and recovery
Training Tips
Vroot sent IMEI to some chinese server
I think it is the first Training Root Boot Loader Lock Android 4.3 for Sony
Amir
Moderator Edit: Links removed
I hope some1 can try it fast..and if it works move thread to android devlopment section
Like I said in the news thread this program sents your IMEI and perhaps even your serialnumber.... why would you even use it if it is sents private data to some random server in China...
" Vroot sent IMEI to some chinese server"
Okaaay I honestly don't trust this method with sending IMEI to some chinese server...
mrjraider said:
Like I said in the news thread this program sents your IMEI and perhaps even your serialnumber.... why would you even use it if it is sents private data to some random server in China...
Click to expand...
Click to collapse
Not only China, but also to be sent to all countries
Our distinguished scientist , or a genius that we have very important
SKA67 said:
Not only China, but also to be sent to all countries
Our distinguished scientist , or a genius that we have very important
Click to expand...
Click to collapse
Okay now you've lost me there....
So why even sharing this program when it steals your Imei and Serialnumber from your phone and sents it to multiple places....
Fetching IMEI is a serious concern! However, if a genius can decipher what's the exploit used here...! it seems the program is doing things through ADB??
Training Tips
Vroot sent IMEI to some chinese server
SKA67 said:
Training Tips
Vroot sent IMEI to some chinese server
It is mentioned in the text
Please watch your tone
Someone forced you to make use of this software is no
I use this program for about one year and I never had a problem
Click to expand...
Click to collapse
No but there were two threads with this program and both are closed due to security issues.. And yet again this damn program appears on XDA.... It seems that searching is a bit hard.
Friends
I 've asked the developers vroot about code IMEI
They noted that only promotions and much of the software used
That currently do not use
Sorry but this is closed. As this tool collects IMEI we wouldn't allow discussion and using it here in XDA for the security purpose of our members. The tool may just collect the IMEI for rooting purpose but the matter still not unveiled completely what actually it is. So till then we won't allow Vroot here. Thanks for understanding
I was having an issue where the Nook wouldn't apply a software update. I figured if I reformatted that would fix it. Well it did. During the initial setup it found and applied the software update OTA. But, after I connect to Wifi, type in my credentials, and click next, I get stuck on this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Nook can't get past this. I know it's up to date because it just downloaded an update. I know it was working because earlier today I was reading a book. But now I've hit a wall. I found another topic regarding registering a glowlight 6", but his problem seems to be slightly different. The users in that topic talked about bypassing the registration, but I can't find advice on that for my particular model. The methods I have tried aren't working, so they must be for other model Nooks. And besides, I'd like to have this device working as intended. I don't intend to root it if I don't have to. I've jailbroken my kindles and rooted many android phones over the years, so it's not a big deal if it must be done. But even then, I don't know how I can root it without getting into settings to turn on debugging.
I'll also mention that the device is for the USA region (or ought to be since that's what all the time zone choices are), and so am I.
EDIT: What I failed to mention was that I got the Nook from Savers yesterday (a thrift store) for $5. Well today I talked to Barnes and Noble and the device is blacklisted. Whoever used to own it reported it stolen once upon a time. This deal was too good to be true
Semi-related: The NOOK/ntx_6sl/ntx_6sl:4.4.2/KOT49H/52.0.78_user:user/release-keys release is out.
http://su.barnesandnoble.com/nook/piper/5.2/piper/0.78/update.zip
I'm not sure what great things are in there, but my "glow45patch.zip" is still compatible. (See signature, MergeSmali)
Renate NST said:
Semi-related: The NOOK/ntx_6sl/ntx_6sl:4.4.2/KOT49H/52.0.78_user:user/release-keys release is out.
http://su.barnesandnoble.com/nook/piper/5.2/piper/0.78/update.zip
I'm not sure what great things are in there, but my "glow45patch.zip" is still compatible. (See signature, MergeSmali)
Click to expand...
Click to collapse
Thanks Renate. I'm doing some reading about the Mergesmali utility you made. I think I am competent enough to use it, but I don't see much info about what use it serves me in particular. Can I use the glow45 patch with mergesmali.exe to bypass the initial setup?
TidusWulf said:
Can I use the glow45 patch with mergesmali.exe to bypass the initial setup?
Click to expand...
Click to collapse
No, the point of it is to patch the specific aspects mentioned, sleep images, white background.
The utility of it is that the same patches were written for 4.5 and continue to work for 5.2 (and beyond).
Moreover, you can't modify any system files until your Glow is rooted.
For skipping registration, is this useful? https://forum.xda-developers.com/nook-touch/general/how-to-access-nook-glowlight-3-t4096829
I'm actually no good at exploit rooting because I usually just hook up a UART console instead.
Oh wow, I got to the easter egg. Thanks for that link. I haven't got this far before. So I've got USB debugging turned on. What next? I just want to use this device as an ereader, nothing else. I'm not sure how to bypass registration still yet, and I've read that there's an extra step I have to take to disable telemetry otherwise my battery life will be really bad.
Also, by platform version is 52.0.78 and my nook apk is 5.2.4.27
EDIT: This looks promising, except that it's for the Glow3 and I have the Glow2 https://forum.xda-developers.com/nook-touch/general/how-to-root-set-nook-glowlight-3-t3802331
I was hoping I could avoid rooting, but it looks like I'll have to in order to overcome that boot animation glitch. And also because it seems the only bypass is to install a separate launcher I guess.
There's been a lot of convergence.
Except for a few hardware things (and 6" vs. 7.8") the Glow2, Glow3 & Glow4 are the same.
Just don't install an update.zip for the wrong model!
Renate NST said:
There's been a lot of convergence.
Except for a few hardware things (and 6" vs. 7.8") the Glow2, Glow3 & Glow4 are the same.
Just don't install an update.zip for the wrong model!
Click to expand...
Click to collapse
Thank you for all the great advice. Perhaps then I should first find a way to make a clean backup before I make any big changes like a custom recovery, or disabling apps and jars.
I've made a lot of progress, but now I'm stuck. I used adb push to temporarily run TWRP and made a backup. Then I used adb to install relauncherX. Pressing HOME doesn't prompt me to pick a launcher. I used https://forum.xda-developers.com/showpost.php?p=64191791 to run a script to Root the device. I also disabled the boot animation using this code:
adb shell
su
mount -o remount, rw /system
mv /system/bin/bootanimation /system/bin/bootanimation.bak
reboot
Click to expand...
Click to collapse
I assume root has persisted thru the reboot because in cmd I was as to run ADB SHELL followed by SU and now I have [email protected]_6sl:/ # in my command prompt.
Problem is, Even though I'm rooted and have a custom launcher, I still can't get past the sign in screen. I think if I knew what process it was, I could kill it with adb, but ps isn't giving me any clues, and dumpsys activity is like information overload, and beyond my skillset to decipher. While in adb shell, su, I used kill 3162 (the pid of com.nook.partner) and that didn't help either. It DID however remove the top bar from the screen, where it shows wifi and battery.
EDIT: So, thanks to me actually READING a little more, I followed some info here https://forum.xda-developers.com/nook-touch/general/how-to-access-nook-glowlight-3-t4096829 and managed to disable the activies necessary to bypass registration. I have the RelaunchX launcher now. I'm 90% of the way there! Now I just need an app that can launch ebooks, because the Nook app wants me to sign in, instead of read.
TidusWulf said:
Now I just need an app that can launch ebooks...
Click to expand...
Click to collapse
So, get a reader app.
One that was mentioned recently was AlReader (that's Al as in Albert).
I don't know, I don't use it.
OK, I just received this device:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
which is sold under various names from vendors @AliExpress.
I'm trying to match this unit with one of the threads here and it seems like no one is dealing with it, but I may have missed some relevant posts, can you please help me with that? Or maybe you know about other forums where they discuss the unit...
The device has several issues (bottom line: do not buy it, the hardware is okish but the software is horrible) and I'd really like to explore ways to customize it but I'm not even able to connect to it via adb, let alone become root or install a custom firmware...
Seem like no one heard of it. Bad luck.
I'm trying to gain root access and fix some of the bull***, but I'm running short of options.
What I know so far:
Invoking "su" from the command line (or via adb) returns a "not allowed" message;
I have no firmware to patch with magisk;
the amazing temp root does not work, the device is patched.
What else could I try?
I may try the MTK Droid Tools, but I think they use the same exploit used by the amazing temp root so I guess this is not a solution. Moreover they need Windows and I can't connect to the unit with adb in windows, only with Linux (heavens know why, the Universal ADB Drivers says it's all "ok" but adb does not see the device).
Did you get anywhere with it? I just got 825x_pro for my R56 Mini.
Nowhere. There seem to be some info in the 4pda.ru forum (in russian) but I did not dig deep into into.
What's your factory setting password? 1812 takes me to factory settings and 8877 takes me to another menu which I can use to go to engineer mode
How and where to use these codes
Fake device tester says that it is android 9 instead of 10
amit1976 said:
Fake device tester says that it is android 9 instead of 10
Click to expand...
Click to collapse
What tester? Have you got a link so I could check mine please?
Have you found where to put these codes?
brodzik said:
What tester? Have you got a link so I could check mine please?
Have you found where to put these codes?
Click to expand...
Click to collapse
There are many apps on playstore , i used fake device test by appsolutely unique
amit1976 said:
There are many apps on playstore , i used fake device test by appsolutely unique
Click to expand...
Click to collapse
I just installed it and the app doesn't open, I mean the screen blinks like it's just about to start and then it goes back to home screen, any ideas?
Does anyone happen to know if there is custom rom that will work on this device please?
brodzik said:
What's your factory setting password? 1812 takes me to factory settings and 8877 takes me to another menu which I can use to go to engineer mode
Click to expand...
Click to collapse
Where to use the codes?
I got alps 825x_PRO. 10.1" It can't remember settings, video out is not working, lights are not working. Need reload firmware. So far I got 8888, 8877, 8878, for settings. But it won't remember. If anyone can help me where to get firmware. Seller Ossuret Factory Store is bad. Sending videos of different models and useless solutions. Refused to give me the firmware.
tefracky said:
Where to use the codes?
Click to expand...
Click to collapse
Hi,
You have to go to:
- The settings
- "Car infotaiment" and click in the high right corner on the "cogwheel" and you get a little window where you have to type the numbers (example: 5678; 8888, ....etc ) And you get the hidden menu !
brodzik said:
I just installed it and the app doesn't open, I mean the screen blinks like it's just about to start and then it goes back to home screen, any ideas?
Click to expand...
Click to collapse
Yup this was my experience of "Fake Device Software" Could it mean it is fake? I downloaded another and found the device advertising it's self as Android 10 but with an API level of 28 which relates to Android 9 or wear devices so ???