Database Info

[Q] How can I access again the setup Wizard?

Hello,
When we start for the first time the TF101 (after buying or flashing with a new rom after a wipe data), a setup wizard asks us for some options. In these options there is a choice for enabling 3G/Wifi or only Wifi.
I would like to know how to start again this setup wizard without wiping data!
How can I do?
Regards,
kasi

Why? Not trying to be rude, but anything you can do in setup wizard you can do already outside of that. I always delete setup.apk and setupwizard.apk from all my devices because the life of it is over after we use it initially.

because i would like to have the 3G option back ;-) And it's the only first time to have this choice.
so you tell that files are named setup.apk and setupwizard.apk ? But which one is the real file I need?
Are these files deleted after the first boot?

Those options are inside of Settings > Wireless & Networrks > Mobile Networks.

Nope.
These options were in my Settings but disapeared after Prime v1.6 update.
So to get back this Mobile Network option I have to wipe data and then restart my TF101. The setup wizard will ask me what I want to use and then I will have it.
But for the moment I lost it.
So I would like to start again the setup wizard without wiping my data.

I have the same problem, it seems that we have to go back to prime 1.5 via Nvflash for access to 3G/Wifi model. is there any way? restart to factory is not useful.

piromoplus said:
I have the same problem, it seems that we have to go back to prime 1.5 via Nvflash for access to 3G/Wifi model. is there any way? restart to factory is not useful.
Click to expand...
Click to collapse
Indeed. I've tried, after backing up my app/data, to wipe data/factory reset and same thing.
This option is no more in Settings!
Yes of course we can do a nvflash with Prime 1.5 but.... I think there is another thing to do....

Kasimodo said:
because i would like to have the 3G option back ;-) And it's the only first time to have this choice.
so you tell that files are named setup.apk and setupwizard.apk ? But which one is the real file I need?
Are these files deleted after the first boot?
Click to expand...
Click to collapse
I delete those two files by hand with root explorer..they are NOT deleted after you run them. They are no good anyway after you use the setup wizard the first time. I don't have a clue what could be your problem since just use wifi only. I would start from the very beginning and put in a rooted stock rom. Sometimes trying to save data is not worth the hassle of trying to repair the problem.

Thx for your reply life64x.
I've already tried to restore, to flash again and even to wipe/data.
But even after wiping data/factory reset the setup wizard doesn't ask me anymore to choose between "3G and Wifi" or "Wifi only".
For the apk file (setupwizard), I found it and launched it. Installation seemed to be ok but can't find a shortcut neither in Apps nor in Settings. Not even in Listed Apps for uninstall.
I think there is something missing in the Prime v1.6

Try asking the Prime author is he removed those options?

O? You bought the 3G version?
I didn't know 3G model is available any where but Italy at the moment,
sorry if I misunderstood, but why else would you want to enable 3G on a wifi only device?

andyxover said:
O? You bought the 3G version?
I didn't know 3G model is available any where but Italy at the moment,
sorry if I misunderstood, but why else would you want to enable 3G on a wifi only device?
Click to expand...
Click to collapse
no, rightnow there is not any 3g model available anywhere. but, there was a setting in previous version of prime rom, If we would be able to active 3g/wifi in setup, we can use 3g usb modems(dongle).

I assume you have ADB already, then type this line: "adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity"
:good:

Hmmm... question from 2011.... I found since.... ^^
Thx

Device isn't working properly after wiping...

So I have a problem with my Nexus 5. Yesterday I tried all kinds of different Lollipop roms and at the end of the day I sticked to Cataclysm. I liked it and my phone was all set up but I noticed there were a lot of unnecessary folders on my internal storage and a nested 0 folder (0 inside /0). I didn't like that so I thought about making a nandroid backup, storing it on my computer (together with my music etc.), wiping everything and restoring it by using TWRP and then eventually putting my music back.
So after I stored a backup on my computer, I started my device into recovery mode and chose the option 'advanced wipe'. Usually I would do a lot of research for everything I do but in this case I was a bit lazy to do that, I tried digging into the search results of Google concerning wiping but I gave up after some unsatisfying results. So I checked every box in the list, including data and system and went through with the wiping. So because my storage was completely wiped I didn't have a 'WRTP/BACKUPS' folder anymore. I made a backup from the stuff I had (which was only a few mb's) so I would have that folder again (otherwise I wouldn't be possible to locate my nandroid backup). I wanted to transfer my nandroid from my computer to my phone by connecting it through USB but for some reason the Nexus 5 didn't show up on my PC when it was booted in recovery (this sometimes happens for some reason)
I managed to do it by using 'adb push Cataclysm folder' in cmd. I went into recovery and restored my backup. My phone booted and I thought everything was as it should be. The wallpaper was black but that was logical because my internal storage was wiped, including my custom wallpaper. But then I noticed something strange, my status bar disappeared, sames goes for my navigation bar. I really have no idea what happened because I've restored nandroid backups before and everything went fine.
So then I put a clean version of Cataclysm on my phone and for some reason it asks me to insert a SIM-card into my device while it has one. I skipped that step and then it asked for my home Wi-Fi and I chose mine, then it checked the connection way longer than it would normally do. After I was done with all the steps my homepage entered my screen and guess what, my status bar and also my navigation bar were absent. It was like my cell phone was in immersive mode all the time. Then I tried flashing the KitKat factory image by going into recovery with my phone and opening 'flash-all.bat' on my PC but then it said '< waiting for devices >' while I enabled USB debugging... I opened cmd and typed 'adb decives' and mine showed up, so it was connected (although it now says 'unauthorized' when my phone is normally booted).
Then I flashed clean Cataclysm again and it again said I had to insert my SIM-card and it then again checked the connection with the Wi-Fi for a couple of minutes. When I was done with the installation I tried replacing the wallpaper with one from Lollipop but it didn't work although there was a preview available. There was again no status bar and navigation bar. I then opened chrome and went to this website and now I'm typing this on my Nexus 5 which has a permanent immersive mode now.
So I don't have much in my internal storage anymore, only a TWRP folder with backups, nothing more, not even a 0 folder if I'm not wrong. There's something wrong with my mobile connection and definitely something going on with my navigation bar and status bar. I hope anyone could help me with this because this is really frustrating becausr I tried to fix it for the last couple of hours, unfortunately without any result...
EDIT: I forgot to mention that when I was trying to figure out how to send the nandroid without being able to access my internal storage via my computer, I booted in recovery, went to 'advanced' and then to 'adb sideload' and tried that because I saw it somewhere on the internet. I somehow believe this contributed to the problem I have.
EDIT2: Now, when I try to power off my phone by holding the power button, it reboots the device instead, what's going on... And as I said, I have a black screen as wallpaper for some reason and I can't change this, but if I open my weather widget, the widget window shows up with my chosen wallpaper on the background, what kind of sorcery is this?
EDIT3: I wanted to download a terminal emulator from Google Play to do this but I couldn't get to 100% so I thought there was something wrong with the app on my device. I googled the apk and I wanted to download it from Zippyshare and when I clicked on the button 'download now', the phone showed the message 'no SD card', so I guess that's the culprit of all of this?
TL;DR My phone is acting really weird (no status or navigation bar, phone reboots instead of asking whether I want to have it shut down when I hold the power button, the wallpaper being strange, SIM-card isn't being recognised) after I wiped data and system and actually everything...

Reboot to bootmanager , flash a factory image , wipe , start over . Something must have gotten corrupted in your nandroid backup.
Regarding ADB not working , you also need to authorize the pc you are working from . You will get a prompt on your phone when connecting . If you dont , go to developer setting , wipe ADB credentials , reconnect the phone.
Also , adb push works fine for single files but it sometimes borks when you are pushing big/many files.
Edit : I hope you didn't wipe EFS as well ( though AFAIK TWRP doesn't wipe it on a advanced wipe) . If you did it's time to return it to stock and send it to LG/Google

Niflheimer said:
Reboot to bootmanager , flash a factory image , wipe , start over . Something must have gotten corrupted in your nandroid backup.
Regarding ADB not working , you also need to authorize the pc you are working from . You will get a prompt on your phone when connecting . If you dont , go to developer setting , wipe ADB credentials , reconnect the phone.
Also , adb push works fine for single files but it sometimes borks when you are pushing big/many files.
Edit : I hope you didn't wipe EFS as well ( though AFAIK TWRP doesn't wipe it on a advanced wipe) . If you did it's time to return it to stock and send it to LG/Google
Click to expand...
Click to collapse
Thank you for reading my huge explanation. After hours of searching and trying a lot of things with my device I figured out how to fix it. Do you remember I said that when I tried to flash the factory image with 'flash-all.bat' that it responded with '< waiting for devices >' ? Well, after reinstalling the drivers countless times and trying to find the culprit I realised I was trying to flash it with TWRP being open, and not the bootloader... So after I was aware of that I finally managed to put stock Lollipop on my phone, then I wiped everything and flashed Cataclysm. It felt pretty satisfying to have a working phone again, it's a pity I had to start from scratch but on the other side, I now how a phone without any rubbish.
Regarding adb push, if I would like to ever push a rom or a big file onto my phone in case I would ever have a similar annoyance, what do you recommend me to do it with?
And what is EFS exactly and what happens if I would ever wipe that? Thank in advance!

Regarding ADB push / twrp MTP mode you jst need to remember not to try and upload the entire content of a sdcard backup or > 3-4 gigs. Big files rarely missbehave , but I screwed up my SD permissions when trying to restore my sdcard ( thousands of files and about 14 gb total).
EFS is a secure partition that stores your GSM/network id and profile - IMEI and so on. AFAIK it's pretty hard to erase but it is possible if you play around with format/repartition commands. Just follow the guides and instructions on this forum and it should be fine.
Corrupted or erased EFS = no network connectivity besides WiFi . And since tampering with it is illegal in some countries the only way to fix it is by RMA/warranty.
I'm glad you've fixed it - I'm not surprised it was a simple mistake , I've been there myself ( tried for an hour to flash a factory image unsuccessfully only to realize I had my phone plugged in a USB3 socket ) .
Don't forget to make a nandroid now that you are set up with your fav. ROM - it will come in handy sometime.

Niflheimer said:
Regarding ADB push / twrp MTP mode you jst need to remember not to try and upload the entire content of a sdcard backup or > 3-4 gigs. Big files rarely missbehave , but I screwed up my SD permissions when trying to restore my sdcard ( thousands of files and about 14 gb total).
EFS is a secure partition that stores your GSM/network id and profile - IMEI and so on. AFAIK it's pretty hard to erase but it is possible if you play around with format/repartition commands. Just follow the guides and instructions on this forum and it should be fine.
Corrupted or erased EFS = no network connectivity besides WiFi . And since tampering with it is illegal in some countries the only way to fix it is by RMA/warranty.
I'm glad you've fixed it - I'm not surprised it was a simple mistake , I've been there myself ( tried for an hour to flash a factory image unsuccessfully only to realize I had my phone plugged in a USB3 socket ) .
Don't forget to make a nandroid now that you are set up with your fav. ROM - it will come in handy sometime.
Click to expand...
Click to collapse
I'll definitely make a nandroid, just in case. Thanks for the help and the clarification!

Try wiping your bum more thoroughly

Wifi password lost on shutdown/reset

Hi,
I have been trying to troubleshoot this problem for some time. The basic problem is that every time the device is shutdown/reset the existing wifi data including known hotspots and passwords is lost.
I have tried factory resetting the tablet (Samsung Note 10.1 SM-T520), along with flashing various stock 4.4.2 Roms (i.e. different release dates and different countries). The tablet was purchased in the US and gifted to my mum in New Zealand, it originally had a stock US rom and now has the NZ rom loaded. Unfortunately Samsung's warranty required us to ship the tablet back to the US to investigate the problem (they would not look at it in NZ as it was not from NZ).
Based on some other threads, I thought it was a problem with the wpa_supplicant.conf file. So I rooted the phone using CF root through odin. I have looked at the wpa_supplicant.conf file and noticed that every time the device is shutdown/reset the
Code:
network={
}
section is removed.
When the device is turned on and I enter the network password the wpa_supplicant.conf file will be updated with the network information and as I said when shutdown this information is removed.
The wpa_supplicant has read/write privilages and user is set to system and group is set to wifi (I did not change these), this is the same for the wpa_supplicant.bak.conf which is created on reboot/shutdown (the bak file doesn't keep the network data on reset either)
In the data/misc/wifi/sockets folder (which the wpa_supplicant.conf references) are the following 4 files:
p2p0
wlan
wpa_ctrl_2719-7
wpa_ctrl_2719-8
This has been an ongoing problem for a year now and has driven me to the point of insanity.
Also, the problem was not originally solely related to the wifi data but also other common settings (i.e. app positioning on the home screen, stored settings), however, after some tinkering and flashing various stock roms some of the problems I was having before I have not been able to re-produce. I am waiting until the battery runs out to see if my home screen will return to the default factory state along with other settings which initially was part of the problem.
Any help or advice would be much appreciated I am happy to do any troubleshooting that may shed some light on the problem. The tablet is current rooted with a stock NZ room running 4.4.2.
Thanks

So an update, with some success
I read another thread that suggested the /efs/ss_data file could be causing the problem. Although this file does not exist... however as part of the troubleshooting process to see if this file might be causing the problem the following was suggested
There is most likely a problem with the phone's /efs/ss_data file. I think it's basically a key for decryption of your Wi-Fi passwords and other things in secure storage.
Root is required for this fix.
First we need to confirm it's a problem with secure storage.
Install BuildProp Editor from Play Store
Set ro.secure.storage=false
Reboot, setup Wi-Fi & reboot again
WiFi should now remember passwords if there was an issue with secure storage.
Now let's fix the secure storage issue since we know what's broken.
Set ro.secure.storage=true using BuildProp Editor
Backup EFS using TWRP/CWM recovery
Delete ss_data in /efs using ES File Explorer in root mode
Reboot, setup Wi-Fi and reboot again
Your Wi-Fi passwords should be remembered now on any ROM/kernel, non rooted and without edits to build.props
Click to expand...
Click to collapse
I didn't have the exact entry as per above but changed ro.securestorage.support to false and my wifi password seems to have saved. At least on one reset test.
As a side note, previously my apps weren't updating automatically and my gmail was not responding, now both seem to be working. Everything I have tested so far that had known problems seems to be working.
Now I have ejected the microSD and have not tested it with it in the device, I'm on 3% battery so running it dead before I do more testing.
Can someone shed any more light on how this problem has occurred and what is the permanent fix? (I cannot delete the ss_data file as the advice above suggests as the file does not exist??!!?

About persist partition?

Hi, I had the dreaded grey wifi bug and in my desperation tried all the fixes that are floating around, one of which was formatting the persist partition. It didn't fix it at all. What fixed it was unplugging the battery for an hour but thankfully I manually backed up the persist directory with a root file manager. Anyway my question is: is it ok to copy-paste back the old bt and wifi mac addresses files and set permissions accordingly or do I need to do something else? And is it ok to not restore the widivine and playready directories and their contents? Im asking because I don't want to break anything else as bluetooth and wifi are currently working fine again with their original addresses, dunno if those 2 directories will be needed later. Everything else like imei is unchanged.
Also is reflashing a google stock image through fastboot enough to make sure all partitions and filesystems are refreshed/fixed? My phone did this weird thing of deleting all user app data before the wifi crashed (like they were newly installed) but left the sdcard data like pictures and music intact, so I figure something made one partition/filesystem crap itself and may need to be recreated/fixed.

How to debug data related bootloop?

begonia (Xiaomi Redmi Note 8 Pro), MIUI 11.0.6.0
I had an unfortunate series of events that resulted in a booloop. Basically:
- Magisk suddenly stopped working one day, after 1.5 year of no issues. I did nothing related to it recently, except just using root functionalities in e.g. Tasker
- I flashed newer Magik 23 and also updated TWRP fom 3.3.1 to 3.5.2
- everything worked fine up until one restart, which resulted in TWRP encryption problems. Right before restart I'm pretty sure I installed Viper4android. I could still get into system with a workaround of TWRP's "Decrypt user" hanging into button reboot, but Magisk/root wasn't working anymore
- so I thought reflashing Magisk and dm-verity/forceencrypt would help, but here's where the bootloops started. During the flash attempts I saw some partition mounting errors since the device was decrypted, so maybe that caused some data issues?
I tried now:
- downgrading TWRP to 3.3.1 - decryption works fine in it and I can flash problemlessly from it, however, doesn't help with bootloop. Reflashing Magisk/dm-verity zips from it also didn't help
- flashing recovery ROM (the same MIUI I had - 11.0.6.0) changed nothing
- flashing fastboot ROM in MiFlash with "save user data" option changed nothing, except I guess confirming the issue is with data
- last thing I tried was flashing uninstall.zip for Magisk since that removed its data folders, which I thought may have got corruped, also to no avail
I know it would probably get fixed with data wipe, but I need the data - I have hundreds of apps with lots of configuration for permissions, notiications, etc. and my recent backups from few months ago vanished because SD card got lost. I have a TWRP 3.3.1 backup of the data now, too bad I didn't do it before updating Magisk/TWRP - lesson learned... So the question is - what can I still do to further debug and fix this without losing data?
I read that reading these logs may also help with debugging, but not sure what to look for.
Kernel log (/proc/lastkmsg): https://pastebin.com/T2xBBRvi - some error looking lines at the end, but non-comprehensible. Can I use them somehow futher?
dmesg log: https://ghostbin.com/paste/vyBDk - don't really see anything here, but it's quite long and not sure what to look for
logcat: https://ghostbin.com/paste/PSh7f - lots of "avc" errors
Please help

Bump. Any help would be appreciated

Plug in the USB cable with the phone powered off. Then issue the commands
Code:
adb devices
adb wait-for-device
adb logcat
from your Windows CMD or Linux terminal: it will hang waiting for the device to come on-line, now power up the phone. The logcat should start scrolling off then.

While it's turned off:
Code:
$ adb devices
List of devices attached
mfaajbdu5s79pfhy unauthorized
If you `adb wait-for-device`, the cmd just waits and you can't enter next command.
`adb logcat`, if I skip the above, waits for device itself, but nothing happens, it just restarts to TWRP and the commands still hang. I can use logcat while in recovery though, that's what I did above

Ok, so I just went ahead and tried the following, too:
- made sure the TWRP data backup can get restored, just in case
- wiped data through TWRP, still the same (re)bootloop into TWRP. I tried both factory reset and advanced wipe with Dalvik/Data/ntenal Storage/Cache.
- so I tried reflashing 11.0.6.0 using MiFlash with that erasing data. That at least worked and phone boots after doing this, but unfotunately not what I'm looking it
- I then tried to get TWRP 3.3.1 back. I got into that and the usual rooting steps were invalid - recovery_fromboot ile was not present in system_root/system. Maybe that's not just present in downloadable ROMs? No clue, but doing the rest of required rooting steps - Magisk 23 install -> Close AVB (TWRP action) -> Remove dmverity (TWRP action) resulted this time in infinite type of bootloop, not sure why, waited for over 30 minutes
- so I reset into TWRP and tried flashing the dmverity zip that's from xda. And this is definitely what caused previous (re)bootloop as after flashing that its more or less the same time length before boot stops and restarts into TWRP. Now, weirdly, while installing this there was an error this time, saying that nvdata cannot be mounted
So I guess the problem before was with mounting nvdata? I see it's something related to phone's IMEI. How does it work exactly, is it somehow related to /data partition? Why wouldn't it mount? Why does it work with pure standard flashed ROM? Is it supposed to be empty when you look at it with TWRP's file manager? Could be something else but this is my only clue right now...
EDIT: oh, you can mount it in TWRP and that works fine, it's not empty. Not sure why that install scipt suddenly stated claiming it can't be mounted, by the end of log, though.

Completely no insights?

I'm coming back to the topic after almost 1 year on old backup phone because I got depressed by this incident and couldn't continue working on it. The old one is like 6 years old, it has abysmal battery life, it ran out of space and I can't install certain apps on older Android, I'm also missing a lot of the set up that I had and which was pretty convoluted - with Tasker and lots of other heavily configured apps. Which slows me down each day.
I can bring the new phone into usable state anytime, a matter of less than hour and reflashing the soft completely, however, setting it up initially took me one year of almost daily changes, many of which can't be retraced as my Titanium backup is old for some reason and there were a bunch of root related changes.
So any sort of help as to how I could potentially recover it with the data would be really appreciated.

And bump

Let's try a bump again

And one more hopeful bump. I'm even willing to pay/donate for any useful insight that will lead to progress with this as my old backup phone is becoming unusable and I don't want to start setting up this one from scratch again.

One last bump before trying in a new topic.
TLDR: what's the best way to debug a bootloop? Do the logs above help or is there something else?

Destroy666x said:
I'm coming back to the topic after almost 1 year on old backup phone because I got depressed by this incident and couldn't continue working on it. The old one is like 6 years old, it has abysmal battery life, it ran out of space and I can't install certain apps on older Android, I'm also missing a lot of the set up that I had and which was pretty convoluted - with Tasker and lots of other heavily configured apps. Which slows me down each day.
I can bring the new phone into usable state anytime, a matter of less than hour and reflashing the soft completely, however, setting it up initially took me one year of almost daily changes, many of which can't be retraced as my Titanium backup is old for some reason and there were a bunch of root related changes.
So any sort of help as to how I could potentially recover it with the data would be really appreciated.
Click to expand...
Click to collapse
Titanium backup is now broken, at least the recovery is now broken. You also are not allowed to start duplicate threads.

Titanium backup doesn't really help me anyways. And ok, I guess I'll keep bumping it then...

Can you access fastboot?