Nabi2-NV7A-US Wi-Fi - Fuhu Nabi 2

Hello,
I have a Nabi2-NV7A-US on Android version 4.4.2.
Kernel version 3.1.10-g812486-dirty
According to product version tapped multiple times:
Version 3.0.13; Bootload Ver 5.3; Device mt799
Recently, without changing anything or using the device for over a year, the Wi-Fi stopped functioning. I would momentarily pick up a SSID now and then but could never connect to it. I believed it was a hardware issue with the wifi chip but, after reading throughout the forums, I think it might be related to the firmware.
I tried to install 3013stock.zip by unzipping the contents and using NabiLab “return to stock” method and installed the stock recovery but this did not fix the Wi-Fi. Maybe I didn’t do it right? Next, I successfully installed TWRP 2.8.7 and rooted the Nabi. After reading literally thousands of posts, I started trying to troubleshoot via ADB shell and the TWRP command prompt to fix the Wi-Fi. I’m not Linux fluent at all but I gave it a go by what I was reading online. IP LINK SHOW tells me wlan0 is in “...state dormant mode dormant...” and I can’t get it to change. iwconfig is not an available command but ifconfig is. I tried installing Reverse Tethering 3.19 so I could access the internet through USB but that required at least one connection to Wi-Fi after each boot which I can’t do. That application installation could have screwed up a few things as well.
The built-in Wi-Fi tests (tapping product version multiple times) failed with “Read config file error. /storage/sdcard1/test_config.txt: open failed : ENOENT (no such file or directory). I wondered why it is looking in sdcard1 so, for grins, I put a copy of wpa_supplicant.conf into the directory and renamed it test_config.txt. This resulted in “Read config file error ./nValue update_config of type java.lang.String cannot be converted to JSONObject. After all the fiddling around, the Wi-Fi no longer finds SSIDs at all and the Bluetooth doesn’t work.
After three 8 hour days of toying with this thing, I am at my wits end. I know this device isn’t supported anymore and isn’t worth much, but I can’t stand to be defeated. Can anyone steer me in the right direction? The most confusing things I have read have to do with the TWPR/recovery versions I have to use when reverting to previous ROMS (ICS, JB, KK). Also, I can’t find the original fuhu_nabi2_back_to_stock_from_scratch.zip stock version 1.9.12 or the fuhu_nabi2_wifi_fix.zip that people have been using to fix their Wi-Fi. I guess I need a step-by-step route to get my Wi-Fi working again either with NabiLab, TWRP, ADB shell, or all three.
Thanks in advance

I guess it's probably best to do a factory reset. I recently had success in resetting mine using this method outlined here https://forum.xda-developers.com/showpost.php?p=63060270&postcount=2 . TWRP was not able to run any of the ROMs I used and resorted to this method as a last resort. I also used 3013stock.zip as the restore file for TWRP. It was able to go through factory reset, and I also have Wi-Fi working. Before doing a restore, I pretty much tried to use all of TWRP's methods of wiping to get it as clean as possible.

I initially factory reset via NabiLab. I then restored via TWRP by using the unzipped 3013stock.zip files in my recovery folder. However, that didn't involve any "wiping". Maybe I'll try it again and use TWRP to wipe/factory reset.
Thanks for trying to help me out.
I wish there were some wpa_supplicant or other linux wifi commands I could use to reset the wifi back to factory. My wlan0 disappeared and a "dummy0" took its place. Although, dummy0 doesn't have the same MAC address I see in my system status reports for the wifi module. I've been trying to teach myself rudimentary linux troubleshooting but with the limited commands available in this Nabi and my limited knowledge of linux, I'm running out of steam.

Yeah I don't think resetting WiFi is necessary. Maybe try to use the original ROM that came with the Nabi or another, but updated to the latest OTA (would have to find the file as the servers are down). I don't think you need to use NabiLab as it might be causing a problem. I would do TWRP -> Advanced Wipe -> Full Wipe. Then, restore with 3013 or maybe with the original ROM updated to the latest OTA. I would also suggest root and then debloat if possible to see if that helps. I chose to flash the .zip file found here https://supersuroot.org/download/ (v2.82), rather than using the root option usually found at the end of TWRP.

Also, the guys here were able to get their WiFi working again by deleting wpa_supplicant.conf . (https://forum.xda-developers.com/showthread.php?t=2202688)

wpa_supplicant deletion
BlueMarble said:
Also, the guys here were able to get their WiFi working again by deleting wpa_supplicant.conf . (https://forum.xda-developers.com/showthread.php?t=2202688)
Click to expand...
Click to collapse
I already tried deleting wpa_supplicant but the one I deleted was in /system/etc/wifi. I just deleted the one in /data/misc/wifi with no improvement. WiFi is on and it shows "Searching for Wi-Fi networks" but never finds any. No change.
The wpa_supplicant.conf file rebuilt itself but now has much less information. One change it made was from cntrl_interface=/data/misc/wifi/sockets (an empty folder) to cntrl_interface=wlan0 which is an interface that does not exist in my system. I have lo, dummy0, sit0, & ip5tn10 of which only dummy0 has a MAC address although it isn't the same as what is shown in the system status for my wifi card. ip5tn10 is a link/tunnel6 with a 16 digit MAC of all zeros.
It seems like I need to get wlan0 interface back with the MAC of the Marvel SD8787 card and get wpa_supplicant.conf configured to use that interface. Looks like the wipe path is next.

I just went into TWRP/wipe/advanced/wiped everything but SD card. Recover 3013 from SD card successful. Installed KK3013bootloader.zip. Rebooted system.
Still finds no wifi. Wi-Fi test (tapping product version multiple times) failed. However, I do have wlan0 now using "ip link show" and it has the proper wifi board MAC address but shows a state and mode of dormant. If I turn Off the wifi with the soft wifi switch, adb shell/"ip link show" shows wlan0 changing from Dormant & Dormant to Down & Default. Turning it back ON goes back to Dormant & Dormant. "netcfg" shows wlan0 as UP.
Question, why do I still have TWRP when I boot into recovery kernel? I thought wiping everything would put me back to the stock recovery. What does installing KK3013bootloader.zip do. I'm confused.
https://bbs.archlinux.org/viewtopic.php?id=117204 seams to address my wifi issue. However, the iwconfig command isn't available to me. "dhcpcd wlan0" gives me the same waiting for carrier and timed out as the poster in that thread
{
"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 still think there must be a magic linux bullet to reconfigure my WiFi. However, with the limited command set available on the Nabi and my limited linux knowledge, it is out of my reach. I wish some XDA gurus could chime in and show me the way.

Oh I meant to say format data. What was the original version of your Nabi (Disney, nickelodeon, original?) , do a restore with that Rom. The partitions may be different for different versions. Do not use Nabi Lab to restore, use TWRP method I linked. If format data was used and the restore was flashed, then your recovery kernel will be different. Instead it will show the broken Android logo and allow you to factory reset. Factory reset. That should return wifi. No need to reinstall bootloader, that was used to unlock your bootloader.
Edit: also have you made any changes to your router during the one year?

Related

Move security app to \system\app directory: Will it be installed after factory reset?

Is it possible to move an app and its files to that directory on rooted phones? Don't apps in that directory automatically stay installed after a factory reset?
I'd like to install PhoneLocator there in case I lose my phone and the person that finds it does a hard reset. Obviously you'd need to also move the file that holds the specific user's login/password info to be able to communicate back after a reset.
If not, is it possible to just unpack the rom I'm using and then stick the files in there?
ScottSNX said:
Is it possible to move an app and its files to that directory on rooted phones? Don't apps in that directory automatically stay installed after a factory reset?
I'd like to install PhoneLocator there in case I lose my phone and the person that finds it does a hard reset. Obviously you'd need to also move the file that holds the specific user's login/password info to be able to communicate back after a reset.
If not, is it possible to just unpack the rom I'm using and then stick the files in there?
Click to expand...
Click to collapse
Yes, if it is installed in /system it won't be deleted on a factory reset. However, the data in those apps gets wiped. Making the data NOT wipe from that app maybe challenging.
-viperboy- said:
Yes, if it is installed in /system it won't be deleted on a factory reset. However, the data in those apps gets wiped. Making the data NOT wipe from that app maybe challenging.
Click to expand...
Click to collapse
It would take a little bit of work but you could add a script w/ the needed data on the system partition to replace it in case of a wipe. Of course an RUU could still wipe it out but the odds of that being used are slim.
xHausx said:
It would take a little bit of work but you could add a script w/ the needed data on the system partition to replace it in case of a wipe. Of course an RUU could still wipe it out but the odds of that being used are slim.
Click to expand...
Click to collapse
everybody is spot on and it is an interesting question/challenge.
the simplest implementation i can think of would be to store your final version of the application's settings on the /system partition .. i'd hide it somewhere since we're doing this all covert stealth like .. and have a simple script on boot copy the application's data settings from the /system partition back to the /data partition on every boot.
the downside would be remembering, whenever you make a change to the application's data settings you would need to copy it back over the /system location, otherwise the /system version would overwrite it on boot.
if you are running a custom kernel, they often allow for scripts in a custom created /etc/init.d/ .. otherwise you can tag up something decent looking that is called from the stock /init.rc
a little more complicated of an implementation would be to write an android app (stored to /system/app) which uses root permission to copy the hidden application's data settings from the /system partition to the /data partition on every boot. the android app could hide itself from the application tray and be trigger via secret dialer code!
the app could also detect changes to the /data directory settings and copy it back over the /system directory ...
hope that helps contribute a bit to the logistics of implementing the idea!
/system/etc/init.post_boot.sh would be the perfect spot to hide the script if you went that route. It already gets called with the stock ROM and the odds of someone finding it there is slim to none. The data itself could be zipped up and placed anywhere. eg. "/system/lib/lib3dstuff.so"
If you use a custom ROM that you think may get switched you could even go so far as to modifying the recovery to reinstalling the files needed for it. That way if they switch to stock from CM or something like that it would still be there, you would just need to make sure that script gets called or that the recovery at least replaces the app's data.
Thanks for the great replies, a lot of great devs that I've actually heard of in here giving advice.
I'm not so worried about changing up the application's data after I set it up. I've got PhoneLocator and SeekDroid for paid apps that can do the basic relocating of my phone in case it's lost. My plan would be to only use Phone Locator for this since it's an app that's not relying on a data connection to send out GPS coordinates and can be triggered by a silent SMS message. I would set it up initially, not touch it afterwards, and then basically use other apps that do similar functions if I needed it.
And I'm not really so worried about someone "discovering" this buried in some system folder on the root. I'm guessing 95% of the people that would "find" my phone would just try and use it as a fun 4 inch wifi device or MP3 player without a cellular connection. And I have faith that if some XDAer found it they would be one of the few people I'd expect to go out of their way to return it.
Some of the solutions seem a bit over my head at this point, is this something I could post in the Dev section to request someone to write the script for? I know people get pissed if things that aren't really dev requests get posted in there.
Or is there a security app that already does something like this?
Back when I was on WinMo 3 years ago using my Mogul there was an app called NueGPS that the developer allowed chefs to cook into their roms, so I'm surprised this hasn't been developed already. Seems the first thing a dishonest person would do that wasn't planning on finding the owner on a lost phone would be to wipe it so they could either sell it or be able to customize it to just use as a wifi device.
I would donate for an app/script like this
That's genius
Sent from my HTC EVO 3d
Root: revolutionary
Recovery: Twrp cwm 4
ROM: Synergy rls318 (I want aosp)
I emailed the developer and he pretty much said this would work. I asked him the same question in the OP.
His reply:
Copy the com.rvo.plpro-1.apk from /data/app, to system/app with an app like Root Explorer. Uninstall the previous installation of ProLocator Pro. Restart your device. Done ! The user info will be stored in that file. Auto enable GPS is default, if it is off, it will be turned on, when a position is asked.
Click to expand...
Click to collapse
Had to "unlock" the app first from within its program to uninstall it from the /data/app directory, but it looks like it works. Before I flash another rom I'll try a standard wipe from the phone settings to see if it holds the settings I have the SMS GPS notifications go out to. He told me those scripts weren't really necessary and that all the user info gets stored in the .apk file. I'm wondering what all these other files do then. This is what came up under a search for plpro in Root Explorer.
{
"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"
}
ScottSNX said:
He told me those scripts weren't really necessary and that all the user info gets stored in the .apk file. I'm wondering what all these other files do then.
Click to expand...
Click to collapse
I'm not in the habit of telling an android developer what his own app does or does not do, but I have developer a few android apps and am semi familar with how the android system works so I'll share my opinion. I'm in agreement more with you than whoever wrote the reply in the email you quoted.
I would be very surprised if his application was somehow internally storing settings inside of its own apk file ...
Those files you found and listed in your screenshot which ,are stored in the application's /data/data directory, are the standard preference type files which most (prob all) android applications use to store their settings. Google provides a very nice and convenient API for storing and managing settings in the app's respective /data/data directory.
It would be worth a try to test out. I would expect the following results from a test:
Move the apk file to /system/app. Wipe /data partition. Reboot and the application should have 100% stock/default settings.
On another approach, a thought just crossed my mind. It could be possible to have the application store your specific settings on a remote server and when the application opens or runs, it could pull down your specific settings from the server. This would of course require internet access (might not have if somebody stole and wiped, at least right away). But thats reverting back to our previous discussion.
Hope that helps as a second opinion from another application developer!

Blackphone PrivatOS screen lock bypass

Hello,
New to this forum as is shows it is my first post, and i have a problem with my Blackphone that i hope you guys could help me with it.
I have a Blackphone first generation with PrivatOS with some files on it and locked screen ( forgot the password / pin actually ),i didnt use the phone for a while since i had some problem downloading and purchasing some apps considering the lack of options compatible with the phone when it was first released and prior to opening the Silent Store.
I've tried several methods i found online such as :
Disable your lock screen using custom recovery and “Pattern Password Disable” (SD card needed)
but no success i get the error ( invalid arg ) when i try to flash the zip file on the SD card.
also i wanted to try this method : http://forum.xda-developers.com/showthread.php?t=2244741
but i am using a Macbook Pro OSX El Capitan 10.11.2
So i ma not sure how to go from here ?
Issue with file manager
Saw i've been trying several method to tackle this problem since i didnt get any reply from the 56 views so far, but i hope someone could explain how to get over this issue i am having trying to apply Method 4 or Method 5 at this post http://forum.xda-developers.com/showthread.php?t=2620456
I was able to download and install all the required applications, from Android SDK and JDK also adb not to forget Android file manager. But i have a problem with the file manager, since i forgot the pin and i am trying to recover some files from the phone it is frustrating to not be able to apply any of these methods because the file manager wont connect the device while it is locked.
Every time i try to type in the command ad devices in Terminal or adb shell i get a return error of device not found, and i guess its because the file manager is not allowing me to do that since the phone is locked.
Any idea how to get over this problem ?
The whole point of that phone is to prevent just what you are trying to do.
Indeed
zelendel said:
The whole point of that phone is to prevent just what you are trying to do.
Click to expand...
Click to collapse
Yes indeed i understand which is the dilemma am in, but that is the point of all phonee pin locks and there are methods to bypass them for most of the phones as i could see all over the internet, this one should not be any different i guess.
I even tried to use the password pattern disable file, but i guess when i flash the file from an SD card i guess some kind of error in the header, am assuming the header in the code of the file should be modified to the OS of this particular phone .
From what i could see the only issue here is the different OS on this phone.
Any suggestions ?
janusjanus said:
Yes indeed i understand which is the dilemma am in, but that is the point of all phonee pin locks and there are methods to bypass them for most of the phones as i could see all over the internet, this one should not be any different i guess.
I even tried to use the password pattern disable file, but i guess when i flash the file from an SD card i guess some kind of error in the header, am assuming the header in the code of the file should be modified to the OS of this particular phone .
From what i could see the only issue here is the different OS on this phone.
Any suggestions ?
Click to expand...
Click to collapse
You would be amazed. This one and the black berry device. Both are meant to be uncrackable by default. I know one secure phone even prevents anything but charging over usb
zelendel said:
You would be amazed. This one and the black berry device. Both are meant to be uncrackable by default. I know one secure phone even prevents anything but charging over usb
Click to expand...
Click to collapse
I am so far, i really assumed that it is possible to so without the factory reset, but i guess that is the only option.
I still have couple of options that i could think of and maybe try,
1- Modify the Pattern Password Disable .zip in order for it to be compatible with Privat OS, easy to say hard to do, since i have no idea how to start tampering with these files and rewrite the coeds in it.
2- Trying to update the firmware on the phone with an SD card which will bypass the pinlock i guess, as i read in one of the posts on the blackphone support website, as a solution for faulty upgrade through the phone.
BTW i didnt try it, but i could see alot of posts for Blackberry to bypass this sort of problem, non for Black phone specifically
I appreciate your sweft reply and attention, hope you could come up with better ideas !?
Another attempt
zelendel said:
You would be amazed. This one and the black berry device. Both are meant to be uncrackable by default. I know one secure phone even prevents anything but charging over usb
Click to expand...
Click to collapse
So, i had to try using the pattern_password_disable.zip in order to see if it is good, and applying the same instruction here i was not able to unlock my Samsung Trend lite 2.
First i downloaded the file into an sdcard, the zip file and tried to flash the .zip from the recovery mood, but the phone did not find anyfiles on the SDcard, so i tried to apply updates from ADB, and when i wrote the comand as instructed on the phone
PHP:
" ad sideload +filename+ "
i got an error
E: footer is wrong
E: signature verification failed
then the phone tried to open it again and i got the same erorr
after that the phone rebooted into the home screen with the pattern lock, i've tried several random guesses but it didnt unlock. ( i know the right one for this phone ).
And since i realized that my mac got connected to the devices while it was in the recovery mood, and i confirmed that by typing adb devices in terminal and the device showed up, i thought of trying the same with the BlackPhone
but i also got the same error
as shown in the picture.
{
"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 wanted to apply the same commands mentioned in the post i've mentioned
PHP:
adb devices
adb shell
cd data/system
rm *.key
but when i type adb shell
i get the error, closed
so any idea on what is going on, i just want to understand my mistake here since these instructions should work on the Samsung !?
Screen shot of Blackphone
http://postimg.org/image/m0tsja4qn/
janusjanus said:
So, i had to try using the pattern_password_disable.zip in order to see if it is good, and applying the same instruction here i was not able to unlock my Samsung Trend lite 2.
First i downloaded the file into an sdcard, the zip file and tried to flash the .zip from the recovery mood, but the phone did not find anyfiles on the SDcard, so i tried to apply updates from ADB, and when i wrote the comand as instructed on the phone
PHP:
" ad sideload +filename+ "
i got an error
E: footer is wrong
E: signature verification failed
then the phone tried to open it again and i got the same erorr
after that the phone rebooted into the home screen with the pattern lock, i've tried several random guesses but it didnt unlock. ( i know the right one for this phone ).
And since i realized that my mac got connected to the devices while it was in the recovery mood, and i confirmed that by typing adb devices in terminal and the device showed up, i thought of trying the same with the BlackPhone
but i also got the same error
as shown in the picture.
I wanted to apply the same commands mentioned in the post i've mentioned
PHP:
adb devices
adb shell
cd data/system
rm *.key
but when i type adb shell
i get the error, closed
so any idea on what is going on, i just want to understand my mistake here since these instructions should work on the Samsung !?
Click to expand...
Click to collapse
Any suggestions
janusjanus said:
http://postimg.org/image/m0tsja4qn/
Click to expand...
Click to collapse
Still awaiting any suggestions ?

[Q] Anyone delt with Samsung 5 Series Chromebook Model xe500c21? Need to Reset.

[Q] Anyone delt with Samsung 5 Series Chromebook Model xe500c21? Need to Reset / Format somehow.
Chromebook is from 2011-2012. I aquired 15 of these units from an auction. All ex units from a local school. I was told all were removed from the Admin System. Yet when I log in i get the login screen with the icon and password box. So its obvious user accounts are still on there and i need to reset the chromebooks somehow. I went to add user i believe it was on the bottom bar and it took me to a google login screen (similar to FRP) asking for username @"school".k12."state".us and password. At the top it says "Enterprise Enrollment Managed by "school".k12."state".us". I have not been able to make it back to the original screen. I tried flipping the dip switch on the side to enable developer mode and it says it was disabled my Admin. Most likely so the kids wouldn't hack it. There is no options for me except a water down Accessibility Menu, Sound, Wifi and Shut Down.
I have tried esc + refresh key on the original login screen and also shift + ctrl + alt + r? i think it was. Neither worked. I have also read that there is a read/write screw that needs to be removed. I am still researching but have yet to find the best working method to bypass and reset these.
I plan on putting Android on a few if possible. On the others I plan on putting Chrome OS back on and Windows 10 on (slimmed down version since SSD on these are only 16GB).
I would appreciate any help anyone can provide.
Thanks,
phonecapone
[Pictures]
Here are some pictures.
{
"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"
}

			
				
Doesn't look like there is a read/write screw on this model. As well I have not successfully been able to enter developer mode. Model seems to be watered down. I had an RMA with Samsung but since 12 out of the 17 have no warranty anymore they want to charge for fixing them. I did hear from a moderator on samsung.com that there is supposedly a specific Chrome OS version that will work on this. Awaiting an answer back.
I have tried everything known to man and nothing works. My last and what should have been my first options are to contact Googles Support dept through samsung and also the school systems IT Dept to get the MAC and domain removed. Deprovisioned basically.
if you've still got these chromebooks around you might want to give this a try. i just got my xe500c21 a few days ago with an enterprise account lock. After long night of tedious trial and error i am officially logged into the developer console with root permissions. Keep in mind that i haven't *entirely* bypassed the enterprise lock, but now that i have root access it will be trivial... lmk if you need details....
the http://mychromehome.blogspot.com/2014/07/download-chromebook-recovery-image.html
this site has a ton of chromebook images you can download directly from google servers. if you check the file names for our device, you'll notice the 4 variables are: 3g, wifi, US, and non-US.
download whichever firmware *does not* match your current configuration, unzip it, and flash it to a usb using win32 Disk Imager.
https://ayera.dl.sourceforge.net/project/win32diskimager/Archive/win32diskimager-1.0.0-install.exe
make sure youve unzipped the .bin file and click the dropdown box to change "img files" to all. select your .bin file and click write. once its done toggle the dev mode switch to on and then reboot to recovery insert the usb. after it finishes you'll notice a new splash screen, then it'll boot up.
at this point if you get online and try to continue you'll still see the enterprise lock, but fear not. toggle the dev mode switch back to off and the reboot. it'll do the wipe and restart, then from the main screen flip the switch one last time to on, then reboot. now youll see an unfamiliar dialog warning you about the dangers of dev mode. proceed and wait for the chromebook to reboot. it took mine about 6 minutes so be patient.
once it reboots you can enter the terminal by pressing ctr + alt + --> (3rd key from left on top row)
login with username chronos
sudo -i
enjoy
microbot118 said:
if you've still got these chromebooks around you might want to give this a try. i just got my xe500c21 a few days ago with an enterprise account lock. After long night of tedious trial and error i am officially logged into the developer console with root permissions. Keep in mind that i haven't *entirely* bypassed the enterprise lock, but now that i have root access it will be trivial... lmk if you need details....
the http://mychromehome.blogspot.com/2014/07/download-chromebook-recovery-image.html
this site has a ton of chromebook images you can download directly from google servers. if you check the file names for our device, you'll notice the 4 variables are: 3g, wifi, US, and non-US.
download whichever firmware *does not* match your current configuration, unzip it, and flash it to a usb using win32 Disk Imager.
https://ayera.dl.sourceforge.net/project/win32diskimager/Archive/win32diskimager-1.0.0-install.exe
make sure youve unzipped the .bin file and click the dropdown box to change "img files" to all. select your .bin file and click write. once its done toggle the dev mode switch to on and then reboot to recovery insert the usb. after it finishes you'll notice a new splash screen, then it'll boot up.
at this point if you get online and try to continue you'll still see the enterprise lock, but fear not. toggle the dev mode switch back to off and the reboot. it'll do the wipe and restart, then from the main screen flip the switch one last time to on, then reboot. now youll see an unfamiliar dialog warning you about the dangers of dev mode. proceed and wait for the chromebook to reboot. it took mine about 6 minutes so be patient.
once it reboots you can enter the terminal by pressing ctr + alt + --> (3rd key from left on top row)
login with username chronos
sudo -i
enjoy
Click to expand...
Click to collapse
Thanks a ton for that information. It has gave me some ideas and i'm sure will help others in a similar situation. Unfortunately I sold all ~20 something of mine and only have 3-4 parts machines left. All need screens and or are still locked. I managed to get all mine unlocked by calling the school district and having their IT guy deprovision all of mine but a couple.
The only chromebook I have left now is a 13 series? i think it is. Its put away else id take a look at it right now. It supposedly has no issues with dev mode which is why i kept it so i can learn everything about chromebooks then sell it off as im not the biggest fan of them personally. Have too many toys too. ha
Thanks for the advice, ill pass it along to a buddy who is doing some dev on chromebooks right now.

Android POS machine H10-1 made by Citaq? Can I reuse it for personal touch tablet?

Hey All
Its been a while since I got to play with anything these days but I recently found one of these POS 10in touchscreen units in the dumpster and it fires up into a menu running android. So I was hoping I could reflash this and use it like a tablet given it's also got a small thermal printer in it, so maybe try and save it from e-waste
I searched online for more details and came across this HERE which is identical to what I have so hoping I can root it and flash it with a clean android?
I would love to repurposed this to use as a touch screen tablet or similar, since it's got a GSM module and can take an SDCard too as I opened it up and took some pictures and I managed to get it in a recovery mode as well - from the PIX its using a rockchip RK3368
{
"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 am not sure if the mini usb port is a OTG port to try and use ADB but I have not been able to do much with it and hoping someone can guide me through to possibly a reflash or ways to unlook root and add in another bootloader/rom
I've downloaded the files from citaq website but so far not been successful to do much with it, has anyone played with these and turned them into something more practical for the home?
Here's hoping for some tips - Apology if this is in the wrong section, move as needed :good:
Cheers
Kosti
@Kostiz
Device actually is running Android 5.1.1. It seems it has only 1GB RAM what is far too little to run a full fledged Android.
As long as you don't replace device's Stock Recovery by TWRP or similar recoveries, after a successful rooting don't install Magisk and/or Xposed Framework, you're on the safe side to play with, IMHO.
As 1st step check whether device is accessable by means of both ADB and Fastboot.
jwoegerbauer said:
@Kostiz
Device actually is running Android 5.1.1. It seems it has only 1GB RAM what is far too little to run a full fledged Android.
As long as you don't replace device's Stock Recovery by TWRP or similar recoveries, after a successful rooting don't install Magisk and/or Xposed Framework, you're on the safe side to play with, IMHO.
As 1st step check whether device is accessable by means of both ADB and Fastboot.
Click to expand...
Click to collapse
Hey, Thanks for chiming in!
So in order to get ADB and or Fastboot its suggested to enable USB debugging in the device system settings, but I am not sure on how to do this, would it be safe to assume this is already USB debug is already enabled?
Could I back up the original stock recovery
I'm a little green on the whole process hence looking thought I'd ask here, I don't think I even have an OTG cable handy
I will see if I can load ADB on a windows box and try and talk to this unit
Cheers
Kosti
@Kostiz
An OTG-cable isn't needed, because the recovery menu
doesn't give you the opportunity to load something from an USB-device
OK, some success!
I went back and connected a mini USB straight to the PC and ADB driver installed detected the android device.
Ran ADB in windows powershell
So whats the best method to backup the entire ROM, and recovery files in the event I stuff this up?
Do I use just ADB for this or someother tools?
I did try one tool here from the vendors website but stuck as not sure what the Chinese characters mean..
Is the fact that this is only 1G i couldn't run Android at all and needs to be stripped down?
Cheers
Kosti
@Kostiz
Android Oreo Go Edition is a lightweight distribution of Android that runs better than normal Android on devices with <= 1 GB of RAM
How to backup device's Stock ROM is eplained here.
Thanks again mate!
Seem I have to do a lot of reading and thankfully everything is here, just got to spend time to read and have a go!
BTW how do I go about using volume rockers and power button to move around the menu in recovery when there is none but only the two buttons as shown the reset and recovery buttons on the main board?
BTW, the current ROM installed boots into a special menu, all other settings are hidden, would there be a way to enable seeing all the items and when getting the the settings (gear icon) that pops up in the corner, only takes me to the standard wifi menu to choose a wifi, so it seems everything else is hidden, if by enabling these I could potentially not need to do anything other than stop the default application from starting up - if that makes any sense
Could I just get back into a adb shell and try
adb shell
su
pm enable applicationname
I have to read up on rooting first I assume before I do much more, this is getting exciting, LOL :good:
Kostiz said:
BTW how do I go about using volume rockers and power button to move around the menu in recovery when there is none but only the two buttons as shown the reset and recovery buttons on the main board?
Click to expand...
Click to collapse
You use Android's HOME button to navigate within the Recovery menu, use POWER button to select option.
Hi, fellas! Please help me with one of these Citaq H10 POS. All we have is bootloop with some custom ROM showing vendor's logo.
Forcing it into recovery gives me some dead android screen with "No command" text.
Please guide me through this challenge, cause I have no other option but to ressurect it somehow.
Good news is that I have another one that is working fine, so we could try cloning it or something. Please help!
Yet I can't attach pics, cause of few posts, but if needed I can PM some.
citaq h10-2
I am also stuck with this machine citaq h10-2 , i did use a wireless kb to move up/down and not the 2 buttons on the motherboard , i can talk with it with ADB but all you can do is put it in sideload to upload new firmware and put it in fastboot but in fastboot you only get a black screen , what I have don is > opened up developer mode but you have no OEM UNLOCK tick box in side so running any bootloader unlock dose not work and i have run them all, if you google this machine for flashing new firmware you only get XDA this forum, unless any body knows another place to get the info from please let us know as i do think this would make a nice tablet with printer, the firmware is 5.1.1 and would love to put 6.0 or above on it but. i did download some firmware and used sideload to install it but it come up with error , i did try and make a backup but cannot do it ?, I think the firmware was from a galaxy s5 , I am not into all this firmware flashing so I am learning as I go along and if I brick it up well it was for free any way as the takeaway was shutting down and he gave it to me so no loss, if any body knows how we can get 6.0 or above on this machine please let us know.
A big thank you to all that can help put android 6.0 or above on this tablet.
Did you guys take a look at the solution here ? It worked for me ! All with a 2k ohm resistor...
Hola, alguien tiene la Rom de este dispositivo?

accidental factory reset with no backup

my phone was accidentally factory reset by a 3 year old holding two buttons, which shouldnt even be an option honestly. i did not have an sd card or a backup for literally the two things i care about most, my notes(samsung notes app) and my photos, and i have no idea why those two were specifically turned off.
i have tried recovering them through my computer with multiple services, minitool, drfone, photorec, fonelab and at least 2 others, all of them said my device had to be rooted, so i tried several things to root my phone as well,(i can only remember kingoroot off the top of my head) but im unable to get the OEM option, ive tried turning off auto updates, changing the date and restarting my phone several times, turning off mobile and wifi data, and im not sure but i think it wont work simply because the option to turn off software updates isnt available(at least, thats the only thing thats different with all the tutorials/videos i watched showing how to do it. i found a post that said its because android updated to make it harder to do and that now software updates happen through google services and to turn that off to do it, but that didnt work either.
my phone is a samsung galaxy a50 and the version(since it reset) is 10.
im begging, please please someone help, anything i can try at all, the last few years of my life are in those photos and notes, i cant lose them, ive been trying to fix this for 6 hours, i dont have much money but i am willing to pay to get back my photos and notes, i really need them. i apologize if this is the incorrect place to post, if it is, please let me know where i can post this to get help.
@Possumpal
A Factory Reset wipes phone's disk space ( what is a non-volatile flash memory ) filled up with user-data and rewrites that partition with the apps provided by OEM/Carrier. As long as the flash memory space ( blocks ) used before wiping and after rewriting doesn't get physically "overwritten" it's basically possible to recover deleted files.
It's not necessary phone is rooted to do so, because you aren't dealing with Android's system-data.
I'm so sorry for not replying sooner, our internet was out for days because someone fixing a leak apparently cut the line. Thank you so much for the reply, that's really exciting to hear! Can you tell me how to retrieve the files then? Or point me to a post or someone who can? Do I need to repost this is the galaxy a50 section? I searched for hours and the only things I found all said I had to root my phone, so I'm not sure how to find it
Possumpal said:
I'm so sorry for not replying sooner, our internet was out for days because someone fixing a leak apparently cut the line. Thank you so much for the reply, that's really exciting to hear! Can you tell me how to retrieve the files then? Or point me to a post or someone who can? Do I need to repost this is the galaxy a50 section? I searched for hours and the only things I found all said I had to root my phone, so I'm not sure how to find it
Click to expand...
Click to collapse
If ADB ( read: USB debugging ) is enabled on phone, then to clone ( read: create a raw image - on byte level - of ) Android's /data and/or /userdata partition to PC
At 1st establish connection running command
Code:
adb devices
Then obtain Android's /data partition's mount-point name by running command
Code:
adb shell mount
and query command's output for line that contains substring
1. if partition name is /data: on /data type ext4
2. if partition name is /userdata: on /userdata type ext4
Left of that substring is shown name of the mount-point, e.g. /dev/block/sda35. Note down that mount point, you need it in next step.
Then, using the mount-point you remembered, run this command
Code:
adb exec-out "dd if=[color=red]/dev/block/sda35[/color] 2>/dev/null" > C:\data.img
what will create the clone on PC's drive C:
Done
is it possible you could link me to the ' how to create a raw image byte level' one? I tried searching the forum for it and google, I'm sure I'm just not doing it right but I cant find it, ive never done this sort of stuff before, I'm sorry I'm being so difficult, I appreciate the help so much, seriously, it means the world to me to be able to retrieve my files
Unfortunately after a factory data reset it may not be possible to regain that data without a backup. You may be able to use custom tools to potentially gain data back that was there but haven't ever seen any success of that
{
"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"
}
My 2 cents: A Factory Reset doesn't mean that user-data are irretrievably lost. The term Wipe Data used in recovery memu is errleading.
Wiping
means overwriting storage space with random data, e.g.
Code:
dd if=/dev/urandom of=/dev/sdX bs=1M
Hence original data in no way can get recovered.
Deleting
means resetting the entry in Android's file system to inform OS that the storage space used is free to write new data onto.
Until that happens the data can be easily recovered by software of which some is free to use.
Formatting
means clearing the entries in Android file system what allows to find/read files on the device, but leaves the files data intact.
You can still recover the data from a formatted storage space.
Personally don't think a Factory Reset wipes user-data in the sense described above, but only deletes them in the sense described above.
But this estimation can be wrong.
the first step isnt working, am i doing something wrong?
i tried it without the space, i tried just adb and just devices, and all of it just says the same thing and i tried doing what it said by putting a \ in front, it still says the same thing
jwoegerbauer said:
My 2 cents: A Factory Reset doesn't mean that user-data are irretrievably lost. The term Wipe Data used in recovery memu is errleading.
Deleting
means resetting the entry in Android's file system to inform OS that the storage space used is free to write new data onto.
Until that happens the data can be easily recovered by software of which some is free to use.
Formatting
means clearing the entries in Android file system what allows to find/read files on the device, but leaves the files data intact.
You can still recover the data from a formatted storage space.
Personally don't think a Factory Reset wipes user-data in the sense described above, but only deletes them in the sense described above.
But this estimation can be wrong.
Click to expand...
Click to collapse
Like I've said even formatting yes you can potentially recover said data, but I've never seen such a tool successfully extract data without it already existing into he device.
---------- Post added at 08:20 AM ---------- Previous post was at 08:16 AM ----------
Possumpal said:
the first step isnt working, am i doing something wrong?
i tried it without the space, i tried just adb and just devices, and all of it just says the same thing and i tried doing what it said by putting a \ in front, it still says the same thing
Click to expand...
Click to collapse
If you have the platform-tools and/or ADB folder use CMD (Command Prompt) to get the job done. Ensure its set to the same directory as the executables
Im.. not sure what that means. I really dont know anything about coding stuff, I can only google how to do everything ive been told, but it doesnt always pull up anything related..

Categories

Resources