I have jamal2367's [AOSP] official 4.4.2 - S4 Google Edition ROM installed (final R1.2) a SGH-1337M.
The other day it started getting stuck on boot; the blue, red, yellow, green circles just continually go in and out without anything else happening. I have booted into CWM Recovery (v6.0.4.4) and done a wipe cache partition and wipe dalvik cache but it did not help.
Can anyone provide advice/steps on how to copy the data (mostly pics and WhatsApp history) off this phone? SMS history would also be nice but not necessary.
toggly said:
I have jamal2367's [AOSP] official 4.4.2 - S4 Google Edition ROM installed (final R1.2) a SGH-1337M.
The other day it started getting stuck on boot; the blue, red, yellow, green circles just continually go in and out without anything else happening. I have booted into CWM Recovery (v6.0.4.4) and done a wipe cache partition and wipe dalvik cache but it did not help.
Can anyone provide advice/steps on how to copy the data (mostly pics and WhatsApp history) off this phone? SMS history would also be nice but not necessary.
Click to expand...
Click to collapse
I would make a backup in your recovery and then flash the rom you had installed. See if that helps.
Edit: You didn't try to update. I changed my comment saying you had tried.
1. Download Aroma File Manager
2. Put a external sd into your phone.
3. Boot into the custom recovery and flash the Aroma file.
4. It will boot into a file browser and you can copy all the files from internal to your external.
ps it's possible that your custom recovery already has a filemanager build in. Then all these steps are obsolete.
I boot into AROMA Filemanager but I can't see anything on the internal SD card (see attachment).
Any ideas? Does that folder icon mean the "sdcard" folder is encrypted?
toggly said:
I boot into AROMA Filemanager but I can't see anything on the internal SD card (see attachment).
Any ideas? Does that folder icon mean the "sdcard" folder is encrypted?
Click to expand...
Click to collapse
Is it encrypted? Then probably it won't work. In that case just reflash the rom you are on without wiping.
toggly said:
Does that folder icon mean the "sdcard" folder is encrypted?
Click to expand...
Click to collapse
Lennyz1988 said:
Is it encrypted? Then probably it won't work. In that case just reflash the rom you are on without wiping.
Click to expand...
Click to collapse
I don't know, that's why I am asking what that icon means?
You say CWM is working, so you can just adb pull everything you need. Applications usually save data in a directory under /data/data or /sdcard/Android/data.
You should find the directories you want with adb shell, then you can adb pull them, then if you reflash your rom you can adb push them back into the same locations. Also, depending where they are saved, your pictures will most likely not be deleted when you reflash your rom. Better safe than sorry though.
If you don't have adb you'll have to download the binary, or you can install the entire Android SDK. Which operating system do you use?
toggly said:
I don't know, that's why I am asking what that icon means?
Click to expand...
Click to collapse
The icons means that it's symlinked. If it's not encrypted then you should find the data. It can be in an other place then where you are looking. Try looking in /data/media or some other maps in /data
Or just flash the rom you are currently on without wiping.
soldier9599 said:
You say CWM is working, so you can just adb pull everything you need. Applications usually save data in a directory under /data/data or /sdcard/Android/data.
You should find the directories you want with adb shell, then you can adb pull them, then if you reflash your rom you can adb push them back into the same locations. Also, depending where they are saved, your pictures will most likely not be deleted when you reflash your rom. Better safe than sorry though.
If you don't have adb you'll have to download the binary, or you can install the entire Android SDK. Which operating system do you use?
Click to expand...
Click to collapse
Adb won't work unless he already has authorized adb when his device was booted.
toggly said:
I boot into AROMA Filemanager but I can't see anything on the internal SD card (see attachment).
Any ideas? Does that folder icon mean the "sdcard" folder is encrypted?
Click to expand...
Click to collapse
You need to mount partitions to see the contents.. Go to Aroma File Manager Settings and check the option "Moumt automatically partition on boot".. then restart your recovery and flash again the Aroma File Manager
Lennyz1988 said:
Adb won't work unless he already has authorized adb when his device was booted.
Click to expand...
Click to collapse
I've had devices where the first thing I did with them was unlock bootloader, fastboot flash recovery, and then go into recovery and adb sideload, all without booting the system.
peppe130 said:
You need to mount partitions to see the contents.. Go to Aroma File Manager Settings and check the option "Moumt automatically partition on boot".. then restart your recovery and flash again the Aroma File Manager
Click to expand...
Click to collapse
That did the trick, thanks!!
Nothing
soldier9599 said:
I've had devices where the first thing I did with them was unlock bootloader, fastboot flash recovery, and then go into recovery and adb sideload, all without booting the system.
Click to expand...
Click to collapse
Yes and I believe that. But from version 4.2.2 android forces rsa encryption. So you need to boot into your rom and enable it. Unless the custom rom/kernel has disabled it, but I haven't seen any that have.
Related
Hi,
like I said I cannot get Google apps on my nook color. I've tried everything. I originally had cm7.0.3 but that wouldn't work so I tried 7.1.0 rc and it still won't work. I tried booting in recovery mode numerous times, I've tried using ROM manger to install from SD but again doesn't work. Someone please help!
chad11 said:
Hi,
like I said I cannot get Google apps on my nook color. I've tried everything. I originally had cm7.0.3 but that wouldn't work so I tried 7.1.0 rc and it still won't work. I tried booting in recovery mode numerous times, I've tried using ROM manger to install from SD but again doesn't work. Someone please help!
Click to expand...
Click to collapse
settings > accounts and sync > add account > log in
that should help. That's how i fixed it when i had the same problem.
thanks but in the first post I forgot to mention I also can't add my Google account. I get as far as it is checking the server connection bu then it say it can't connect
chad11 said:
thanks but in the first post I forgot to mention I also can't add my Google account. I get as far as it is checking the server connection bu then it say it can't connect
Click to expand...
Click to collapse
can you connect to the internet at all?
re-do everything. Do "adb pull /data/app/ app/" and "adb pull /data/data/ data/" and go into the app folder. Delete anything that has to do with Google (market, googleservices, etc.) Download cm7 and gapps from the links at the end of this post Put em on your sd card. Boot into recovery. Mounts & Storage, wipe data, system, and cache. Now flash cm7 first, then gapps. Now flash anything else you use (dal's OC kernel, etc) and reboot. Re-setup your Nookie. Now push puth the app/ and data/ folders to your sd card. Download File Expert and Root Explorer. Using file expert, navigate to the sd card. Select the app/ folder you pushed, and press and hold. Now hit install all apk packages. Keep installing. If you get an error, Setting>Applications>Allow Non-Market installs. Now use root explorer to merge the data/ folder on your sd with the /data/data/ folder on the emmc. Done. Hope that wasn't to complicated.
ikingblack said:
re-do everything. Do 1) "adb pull /data/app/ app/" and "adb pull /data/data/ data/" and go into the app folder. Delete anything that has to do with Google (market, googleservices, etc.) 2) Download cm7 and gapps from the links at the end of this post Put em on your sd card. Boot into recovery. Mounts & Storage, wipe data, system, and cache. Now flash cm7 first, then gapps. Now flash anything else you use (dal's OC kernel, etc) and reboot. Re-setup your Nookie. Now push puth the app/ and data/ folders to your sd card. Download File Expert and Root Explorer. Using file expert, navigate to the sd card. Select the app/ folder you pushed, and press and hold. Now hit install all apk packages. Keep installing. If you get an error, Setting>Applications>Allow Non-Market installs. Now use root explorer to merge the data/ folder on your sd with the /data/data/ folder on the emmc. Done. Hope that wasn't to complicated.
Click to expand...
Click to collapse
You are aware that when you do #3 you will take care of #1. wiping the /data wipes everything in it.
And if you want go about it that way you could even just do a
Code:
c:\<target folder> adb install [package name]
and it will install the app for you. so you can pull it, wipe it then reinstall everything.
adb pull backs it up. and whoops, here are links:
CM7: http://download.cyanogenmod.com/get/cm_encore_full-123.zip
Gapps: http://goo-inside.me/gapps/gapps-gb-20110613-signed.zip
ikingblack said:
adb pull backs it up. and whoops, here are links:
Click to expand...
Click to collapse
Then why are you having the [OP] reflash the gapps if they are just going to manually install them?
the problem the [OP] is having is the device [Nook Color] will not connect to google's servers. It has nothing to do with the g/apps not showing up on the device.
No, we are backing up all the apps, because one time I had this problem and a fresh slate caused it. And as for the adb install commands, It would take forever, because you would have to type in the APK's name. For my method, all you have todo is hit Install. Just keep stabbing the right lower corner of the screen.
ikingblack said:
No, we are backing up all the apps, because one time I had this problem and a fresh slate caused it. And as for the adb install commands, It would take forever, because you would have to type in the APK's name. For my method, all you have todo is hit Install. Just keep stabbing the right lower corner of the screen.
Click to expand...
Click to collapse
So because you reinstalled the applications it's magically reconnected to Google's servers?
Nope. There was something corrupt in my /data/ folder. Wiping and re-installing all apps was what I had to do.
OK your first post was a little complicated for me. this is the first time I've rooted somethiing. could you please put in simpler terms. by the way I don't have any apps on my device or any other data i care about so I don't need to back anything up if that would make it easier
also yes (neidlinger) I did have a internet connection, and I also can't install a new build through recovery
Alright, if you don't have anything to back up, do this:
Download CM7, gapps, and other stuff you want (overclock kernel) and put it on the sd card.
Now boot into recovery, CWM.
Go into Mounts + Storage. Wipe system, data, and cache. Go into advanced (on the first menu) and wipe dalvik cache.
Hit "install zip from sd card" and then "choose zip from sd card".
Now select CM7. Wait for it to flash
Choose zip again, but choose gapps, then flash an OC kernel if you wanted. Note the NC doesn't have back and menu buttons, so download a Hard Key editor to make Volume+ to menu and volume- back.
Now reboot device. Now set it up. After typing in your google account, it will *attempt* to connect to Google Servers. It will fail. It will then show a button to connect to wifi. Hit it and connect to the wifi. Then continue set up steps. Enjoy CM7 with a smaller guide. Much smaller.
ikingblack said:
Alright, if you don't have anything to back up, do this:
Download CM7, gapps, and other stuff you want (overclock kernel) and put it on the sd card.
Now boot into recovery, CWM.
Go into Mounts + Storage. Wipe system, data, and cache. Go into advanced (on the first menu) and wipe dalvik cache.
Hit "install zip from sd card" and then "choose zip from sd card".
Now select CM7. Wait for it to flash
Choose zip again, but choose gapps, then flash an OC kernel if you wanted. Note the NC doesn't have back and menu buttons, so download a Hard Key editor to make Volume+ to menu and volume- back.
Now reboot device. Now set it up. After typing in your google account, it will *attempt* to connect to Google Servers. It will fail. It will then show a button to connect to wifi. Hit it and connect to the wifi. Then continue set up steps. Enjoy CM7 with a smaller guide. Much smaller.
Click to expand...
Click to collapse
Please Take TIME to read the entire post before firing off solutions that will not help the [OP]
chad11 said:
also yes (neidlinger) I did have a internet connection, and I also can't install a new build through recovery
Click to expand...
Click to collapse
To the OP. Do me a favor. And i under stand this is your first time messing with a rooted device.
I need you to either get your SDK up and running, and do the patch for it to pick up your Nook Color. Once you do that you need to go into the adb command prompt and type
Code:
adb kill-server
adb start-server
that will kill and start the the bridge to connect your phone to the computer
then type
Code:
adb devices
it should show your serial number
once that is done type
Code:
ls /data/app
That will show you all of your applications that are store in the /data folder on your device.
should see a bunch of com.android.[package_name]
They'll look like this
Code:
com.google.android.apps.books-2.apk
com.google.android.apps.docs-2.apk
com.google.android.apps.googlevoice-2.apk
com.google.android.apps.maps-2.apk
com.google.android.apps.plus-1.apk
com.google.android.apps.reader-1.apk
com.google.android.gm-1.apk
com.google.android.music-2.apk
com.google.android.street-1.apk
com.google.android.voicesearch-1.apk
com.google.android.youtube-1.apk
If you see those then you know your Google Apps were installed when you flashed the package from the get go.
you can also do a
Code:
ls /system/app
and look for MarketUpdater.apk GoogleServicesFramework.apk. If you see those then you know are good to go.
The only reason i'm not suggesting it's a bad flash is i had the SAME problem when i went from Rooted Stock to CM7. Once i logged into my device all of the G/Apps showed up. It was almost like they do appear until you are logged in.
what is SDK and adb
chad11 said:
what is SDK and adb
Click to expand...
Click to collapse
SDK is Software Development Kit. It enables one to create ROMs, Themes, Applications and what not. (http://developer.android.com/sdk/index.html)
the ADB is the Android Debug Bridge it is what enables your phone to talk to your computer. via the CMD prompt. (http://developer.android.com/guide/developing/tools/adb.html)
The very basics of it you will need the ADB drivers. Which i have a link to in my signature. However some extra steps must be taken to make the computer pick up the Nook Color.
I mtried to get them both but when I tried to install SDK It said I had to install a java SE thing but i don't know which windows to install: 84, 64, or ititium. I don't know if I spelled it right but they wouldn't work
@neidlinger in your post it said "ls /data/app". Well, actually it should be "adb shell ls /data/app"
Heads up.
hey, I just figured something out. when I boot into clockworkmod recovery it deosn't show up. then when I take the sd card out and power it back on it shows up. what does this mean
Trying to restore a NAND in CWM but it says "couldn't find directory, no files found" when I click "restore"
So i did a backup, and it shows up when I then hit "restore" in sdcard/clockworkmod/backup (listed at top of recovery screen) but when I boot and look on my sdcard, it shows the old backups I made in the folder listed, not the one I just made. I can't find the one I just made, even though if I reboot into recovery, it still shows it (the latest) and only it.
Any idea where the newest one is, and why I cant restore the older ones?
Are you running CWM 6.0.1.9?
Also, take a look at http://forum.xda-developers.com/showthread.php?t=1991657.
I am running v6.0.1.9 and the link you posted seems to say that this should be an issue resolved with this version. Though it did tell where to find the new backup.
It lists some adb commands to move the old backups to the new directory, can I just do that in rootexplorer with copy/paste?
TheAtheistReverend said:
I am running v6.0.1.9 and the link you posted seems to say that this should be an issue resolved with this version. Though it did tell where to find the new backup.
It lists some adb commands to move the old backups to the new directory, can I just do that in rootexplorer with copy/paste?
Click to expand...
Click to collapse
I don't see why you couldn't move the files with rootexplorer. Give it a try!
They moved fine
They are seen by recovery, and now I just switched to TeamWin recovery. We'll see if that sees them too.
Are we confident that wiping doesn't clear this location? I'm a little worried that a factory reset or something might wipe the data folder
TheAtheistReverend said:
They moved fine
They are seen by recovery, and now I just switched to TeamWin recovery. We'll see if that sees them too.
Are we confident that wiping doesn't clear this location? I'm a little worried that a factory reset or something might wipe the data folder
Click to expand...
Click to collapse
Please read the following
http://forum.xda-developers.com/showthread.php?p=34794673
If you are worried about losing the backups, copy them to your pc or onto OTG storage. I use cwm and my backups are now in /data/media/clockwork. If you activate multi-user, I think they go to /data/media/0/clockwork, but I can't test. Not sure about the TW recovery.
scott_doyland said:
Please read the following
http://forum.xda-developers.com/showthread.php?p=34794673
Click to expand...
Click to collapse
Confusing But the info is there. I don't like how complicated it ahs gotten to wipe, restore, recover, and flash. It used to be so simple...:silly:
Hi!
So, I flashed the official cwm touch 6.0.3.3 from http://www.clockworkmod.com/rommanager, for Nexus 4.
When I perform a backup, it successfully completes.
However, when I boot back into system, the /sdcard/clockworkmod directory is empty.
When I try an adb pull, it's still empty.
But, when I reboot into cwm touch recovery, it clearly shows an available backup, in the same directory (/sdcard/clockworkmod/backup)
And, an adb pull, while in recovery works perfectly.
Any reason why it's not showing up, when I've booted up into Android?
Thanks!
arvindch said:
Hi!
So, I flashed the official cwm touch 6.0.3.3 from http://www.clockworkmod.com/rommanager, for Nexus 4.
When I perform a backup, it successfully completes.
However, when I boot back into system, the /sdcard/clockworkmod directory is empty.
When I try an adb pull, it's still empty.
But, when I reboot into cwm touch recovery, it clearly shows an available backup, in the same directory (/sdcard/clockworkmod/backup)
And, an adb pull, while in recovery works perfectly.
Any reason why it's not showing up, when I've booted up into Android?
Thanks!
Click to expand...
Click to collapse
/data/media/clockworkmod/backup
And there it is!
abaaaabbbb63 said:
/data/media/clockworkmod/backup
And there it is!
Click to expand...
Click to collapse
Thanks!
Why is the directory listing different on System boot?
arvindch said:
Thanks!
Why is the directory listing different on System boot?
Click to expand...
Click to collapse
To protect the backup from accidental deletion.
abaaaabbbb63 said:
To protect the backup from accidental deletion.
Click to expand...
Click to collapse
OK... But, it makes accessing the backup, to copy it to my PC, confusing...
How does this directory listing change work? symlink?
Also, what does the make .img file option, in backup&restore do?
When I tap on it, it just resets the page...
arvindch said:
OK... But, it makes accessing the backup, to copy it to my PC, confusing...
How does this directory listing change work? symlink?
Also, what does the make .img file option, in backup&restore do?
When I tap on it, it just resets the page...
Click to expand...
Click to collapse
Yes, vanilla JB uses a lot of symlinks.
I have no ideea about the make img.
abaaaabbbb63 said:
Yes, vanilla JB uses a lot of symlinks.
I have no ideea about the make img.
Click to expand...
Click to collapse
Oh..
Yeah, it's a weird option.
my nexus 4 was rooted with 4.3 but then i decide to upgrade to 4.4
this is the video i am trying to follow, basically just wipe & install which i did most the time.
youtube title "NEXUS 4: HOW TO MANUALLY UPDATE TO ANDROID 4.4 KITKAT"
it has two files one is mako and one is gapp.
after i did all the wiping in cwm and try to install the mako file, it shows "no file context" or sth similar, and installation is abort (i think there is problem when i transfer the file), but then i continue to install the gapp file (what the hell was i thinking?)
so now i am stuck in the google start up loop, i can only access cwm recovery mode and don't have a valid rom to install in my sdcard.
i tried to adb push another rom to the sdcard with no success (my storage was already very low, any way to remove files in the storage at this point?)
the "mount & storage" also doesn't seem to let me mount the sdcard (but system shows up "unmount").
so now i don't know what to do.
if anything has any idea or suggestion please let us know.
i am quite desperate now with a dead phone and will try anything.
thanks for reading such a long thread.
Dude that vid is old and it installs pa or some other port just flash factory images from google
Sent from my F1 using xda app-developers app
try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.
Frickelpit said:
try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.
Click to expand...
Click to collapse
any step by step guide to do this?
i am still new to this thing even i install a few roms before.
i will google it now, but any additional info is much appreciate.
thanks
Frickelpit said:
try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.
Click to expand...
Click to collapse
frustrated..
i can't seem to get my windows to recogize the device (when i type adb devices, it shows an empty list)
already try trouble shooting this for a long time with no result.
any idea?
telly0050 said:
frustrated..
i can't seem to get my windows to recogize the device (when i type adb devices, it shows an empty list)
already try trouble shooting this for a long time with no result.
any idea?
Click to expand...
Click to collapse
after tons of troubleshooting finally got it back to work.
it ends up the reason is i didn't update to the latest cwm at the very beginning.
and sideloading 4.4 didn't work because of that too, i have to install an old 4.2 to have it working.
Hi, I cant get to install any roms on my phone after updating via OTA (Lineage 17.1)
I can access to twrp but when I try installing any rom half bar is completed and after that, it crashes and boot loop.
I have tried to install different roms but same result. Can anyone help please?
Already tried:
Factory reset
wipe: data/cache/ system
Restore firmware via fastboot flash.
Change SD card
Installed 3 different stock roms via fastboot and they boot but after few seconds reboot on setup (Gboard and maps apps crash warning)
View attachment 5130605
No solution anyone?
dawe0120 said:
No solution anyone?
Click to expand...
Click to collapse
Post your recovery.log and I will tell you what's wrong with your phone.
TWRP main screen > advanced > create log
Please rename it from recovery.log => recovery.txt or .zip it to upload the file here.
WoKoschekk said:
Post your recovery.log and I will tell you what's wrong with your phone.
TWRP main screen > advanced > create log
Please rename it from recovery.log => recovery.txt or .zip it to upload the file here.
Click to expand...
Click to collapse
Thanks for the response here it is.View attachment 5131037
dawe0120 said:
Thanks for the response here it is.View attachment 5131037
Click to expand...
Click to collapse
This log doesn't show anything about your error. Reproduce the error and than grep the log.
Ok done, here is what I did:
Wiped side b (to make sure there's no other rom installed), then tried to install pixel experience rom and the twrp crash at mid bar happened again. (Same process as shown in screenshot)
After that rebooted to twrp and created the log.
View attachment 5131307
dawe0120 said:
Ok done, here is what I did:
Wiped side b (to make sure there's no other rom installed), then tried to install pixel experience rom and the twrp crash at mid bar happened again. (Same process as shown in screenshot)
After that rebooted to twrp and created the log.
View attachment 5131307
Click to expand...
Click to collapse
Ok, due to the crash TWRP does not record the error. But you can try this :
Before you are going to flash the ROM connect your device with your PC. Open ADB cmd line and first of all check the connection with
Code:
adb devices
After that run
Code:
adb logcat >> recovery.txt
When TWRP crashes you'll find the recovery.txt inside of your ADB folder on your PC.
WoKoschekk said:
Ok, due to the crash TWRP does not record the error. But you can try this :
Before you are going to flash the ROM connect your device with your PC. Open ADB cmd line and first of all check the connection with
Code:
adb devices
After that run
Code:
adb logcat >> recovery.txt
When TWRP crashes you'll find the recovery.txt inside of your ADB folder on your PC.
Click to expand...
Click to collapse
I did what you told me, but the only thing in the recovery.txt is:
/sbin/sh: logcat: not found
First command: displays my S/N - recovery
So comm is not the problem.
dawe0120 said:
I did what you told me, but the only thing in the recovery.txt is:
/sbin/sh: logcat: not found
First command: displays my S/N - recovery
So comm is not the problem.
Click to expand...
Click to collapse
The connection is ok but logcat isn't included in TWRP.
Ok, next try:
When TWRP crashes check connection again with adb devices. Got a connection? Then go ahead with
Code:
adb pull /tmp/recovery.log recovery.txt
and upload it here.
WoKoschekk said:
The connection is ok but logcat isn't included in TWRP.
Ok, next try:
When TWRP crashes check connection again with adb devices. Got a connection? Then go ahead with
Code:
adb pull /tmp/recovery.log recovery.txt
and upload it here.
Click to expand...
Click to collapse
Ok, here is what I did:
Wiped side B again(to clean the previous failed installation)
Installed P.E. rom (same crash issue happened)
Then reboot to twrp. Put de communication command (everything ok S/n and recovery displayed)
And finally wrote the adb pull command successfully
HEre's the file: View attachment 5131657
dawe0120 said:
Ok, here is what I did:
Wiped side B again(to clean the previous failed installation)
Installed P.E. rom (same crash issue happened)
Then reboot to twrp. Put de communication command (everything ok S/n and recovery displayed)
And finally wrote the adb pull command successfully
HEre's the file: View attachment 5131657
Click to expand...
Click to collapse
A reboot clears the log so I still got no information. Either you grep the log when TWRP crashes or the log buffer will be cleared with next reboot.
How did you wipe slot b?
WoKoschekk said:
A reboot clears the log so I still got no information. Either you grep the log when TWRP crashes or the log buffer will be cleared with next reboot.
How did you wipe slot b?
Click to expand...
Click to collapse
Ok, this time what I did is to run the pull command just before the crash (at mid bar) I tried to run it at the freezing but obviously the communication with the device was suspended.
I hope this made any difference.
View attachment 5131691
What I mean by saying wiping slot b is selecting it via twrp and then wipe data, cache, system etc.
dawe0120 said:
Ok, this time what I did is to run the pull command just before the crash (at mid bar) I tried to run it at the freezing but obviously the communication with the device was suspended.
I hope this made any difference.
View attachment 5131691
What I mean by saying wiping slot b is selecting it via twrp and then wipe data, cache, system etc.
Click to expand...
Click to collapse
The log ends at 40% of your installation process but no error is shown.
All I would recommend is to flash the stock ROM and download a new Pixel ROM (from official source!). Since it's not possible to take any logs showing your error I don't have a better solution for that.
This process is a Google implementation and not a simple flash script like older ROMs use it. So it's really hard to find an error, even if you know the complete Java source (and I don't ).
Wiping slot _b: There's no need to wipe data for that. Your data partition has got no slots, it's only /data.
Let me explain you in short what's the meaning of all those options:
cache = /data/cache
dalvik-cache = /data/dalvik-cache
internal = /data/media
data = all of /data, except 'media' (internal storage) directory
So, you can see that those options for choosing what to wipe are all stored under /data. The easiest way to wipe them all together would be to format data completely. One step and you're done! If you like to...
WoKoschekk said:
The log ends at 40% of your installation process but no error is shown.
All I would recommend is to flash the stock ROM and download a new Pixel ROM (from official source!). Since it's not possible to take any logs showing your error I don't have a better solution for that.
This process is a Google implementation and not a simple flash script like older ROMs use it. So it's really hard to find an error, even if you know the complete Java source (and I don't ).
Wiping slot _b: There's no need to wipe data for that. Your data partition has got no slots, it's only /data.
Let me explain you in short what's the meaning of all those options:
cache = /data/cache
dalvik-cache = /data/dalvik-cache
internal = /data/media
data = all of /data, except 'media' (internal storage) directory
So, you can see that those options for choosing what to wipe are all stored under /data. The easiest way to wipe them all together would be to format data completely. One step and you're done! If you like to...
Click to expand...
Click to collapse
I have tried to flash 3 different stock roms via fastboot. They boot but then the system crashes at setup and reboots. I get warnings that maps and gboard stoped unexpectedly.
Honestly I dont know what else to try, the only thing I did is to update via OTA (didnt know I shouldtn have) =(
https://forum.xda-developers.com/g6-plus/development/rom-pixel-experience-t4069215 this is the rom Im trying to install and it's an official release.
If I format data instead of wiping will I lose twrp recovery?
View attachment 5131731
Does this info help?
dawe0120 said:
I have tried to flash 3 different stock roms via fastboot. They boot but then the system crashes at setup and reboots. I get warnings that maps and gboard stoped unexpectedly.
Honestly I dont know what else to try, the only thing I did is to update via OTA (didnt know I shouldtn have) =(
https://forum.xda-developers.com/g6-plus/development/rom-pixel-experience-t4069215 this is the rom Im trying to install and it's an official release.
If I format data instead of wiping will I lose twrp recovery?
Click to expand...
Click to collapse
Your Pixel ROM is fine, it's the official release.
Format /data or wiping /data completely is nearly the same. Both methods will erase all stored data. But format will build up a new partition. It's like formatting a USB-Stick in Windows for example.
But none of them would delete your recovery. TWRP is a part of /boot (boot.img) which is only another partition besides /data.
As long as you're not able to boot up your device with the stock ROM you won't be able to boot the Pixel ROM, too. Pixel is only a overlay for stock.
Which three stock ROMs did u try to flash? Build no and source/links would be helpful.
This is the current build for your device: (software channel RETLA is guess??)
XT1926-6_EVERT_RETLA_DS_9.0_PPWS29.116-11-23
Download it and flash it with the attached flashfile.bat (for uploading purposes I had to zip it)
The commands are taken from the flashfile.xml inside the firmaware .zip
WoKoschekk said:
Your Pixel ROM is fine, it's the official release.
Format /data or wiping /data completely is nearly the same. Both methods will erase all stored data. But format will build up a new partition. It's like formatting a USB-Stick in Windows for example.
But none of them would delete your recovery. TWRP is a part of /boot (boot.img) which is only another partition besides /data.
As long as you're not able to boot up your device with the stock ROM you won't be able to boot the Pixel ROM, too. Pixel is only a overlay for stock.
Which three stock ROMs did u try to flash? Build no and source/links would be helpful.
This is the current build for your device: (software channel RETLA is guess??)
XT1926-6_EVERT_RETLA_DS_9.0_PPWS29.116-11-23
Download it and flash it with the attached flashfile.bat (for uploading purposes I had to zip it)
The commands are taken from the flashfile.xml inside the firmaware .zip
Click to expand...
Click to collapse
I flashed it via fastboot the flash didn't show any errors.
The phone starts and says "verity mode disabled", then this happened:
View attachment 5131805
(Video on rar file)
dawe0120 said:
I flashed it via fastboot the flash didn't show any errors.
The phone starts and says "verity mode disabled", then this happened:
View attachment 5131805
(Video on rar file)
Click to expand...
Click to collapse
Oh... that doesn't look good at all!
It seems to be a kind of hardware failure and not only a software bug. Was the OTA update that led to your problem successful?
Boot into TWRP and see if you could find some logs in /sys/fs/pstore and /data/vendor/dontpanic.
WoKoschekk said:
Oh... that doesn't look good at all!
It seems to be a kind of hardware failure and not only a software bug. Was the OTA update that led to your problem successful?
Boot into TWRP and see if you could find some logs in /sys/fs/pstore and /data/vendor/dontpanic.
Click to expand...
Click to collapse
Yes de OTA update was successful, the phone worked flawlessly the whole day(Wednesday) without problems, then I went to sleep that day and when I woke up my phone was bricked. (No I didn't drop my phone or anything like that) These are the files I found on the pstore folder (nothing on the dontpanic folder)
View attachment 5132711
View attachment 5132713
After some research I found posts about the same issue as me :
https://forums.republicwireless.com/t/screen-flickering-with-moto-g-6/21309
So If it's a hardware problem wow just wow. I only have had this phone for nearly 2 months and It's already dying? (Never dropped it or anything like that)
I'll never buy anything from motorola again for the rest of my life.
dawe0120 said:
Yes de OTA update was successful, the phone worked flawlessly the whole day(Wednesday) without problems, then I went to sleep that day and when I woke up my phone was bricked. (No I didn't drop my phone or anything like that) These are the files I found on the pstore folder (nothing on the dontpanic folder)
View attachment 5132711
View attachment 5132713
After some research I found posts about the same issue as me :
https://forums.republicwireless.com/t/screen-flickering-with-moto-g-6/21309
So If it's a hardware problem wow just wow. I only have had this phone for nearly 2 months and It's already dying? (Never dropped it or anything like that)
I'll never buy anything from motorola again for the rest of my life.
Click to expand...
Click to collapse
I guess it could be hardware issue because a full factory image like I linked above covers almost all of your device. You get the kernel and all drivers.
I'll study your logs later that day.