I noticed people complain about errors on a brand new flash of a ROM, errors that I never had, or any other use never had. On occasion, flashing data will leave settings/apps intact and actually not do anything at all..so to follow a complete fail proof guide on ensuring a brand new flash...do the following.
1. Wipe data TWICE (2x) one after the other.
2. Flash the ROM. (ONCE)
3. Wipe cache partition. (2x)
4. Wipe dalvik cache. (2x)
5. Fix Permissions. (2x)
REBOOT.
Leave your phone idle IMMEDIATELY after booting for 10 minutes so the phone's background services and first-time use settings can process themselves. Doing this will provide you the most stable flash, and any force closes / crashes more than likely will be the ROM's fault if you followed all steps to the "T.".
This may not be well known to everyone. Whatever. If you don't find it useful, don't comment. If you do, comment. If you need help or have any questions, post them and I will be sure to answer you as quick as possible.
I've always wondered, what's the point of doing wipe twice?
djh said:
I've always wondered, what's the point of doing wipe twice?
Click to expand...
Click to collapse
On occasions (and this is ALSO true with the SGH-t989)
The ROM won't be completely wiped. It will incorporate the old data with your new ROM and cause force closes, or black screens, slower, lower battery life, etc.
By doing this twice, you ensure yourself the platform is ENTIRELY clean and ready for a new version of the ROM.
For example, I once flashed GOV2, over GenericGinger and STILL HAD a green theme. That's how I knew something was wrong. From there on then, I ALWAYS ALWAYS ALWAYS like a religion, wiped twice. There's no reason NOT to do it. It takes very little time, and is added insurance to a fully functional and stable ROM.
Edit : If no one likes the method, by all means do things your own way ; whatever works for you works ; however I do things judging on the fact from experience of using/doing them.
TheLastSidekick said:
On occasions (and this is ALSO true with the SGH-t989)
The ROM won't be completely wiped. It will incorporate the old data with your new ROM and cause force closes, or black screens, slower, lower battery life, etc.
By doing this twice, you ensure yourself the platform is ENTIRELY clean and ready for a new version of the ROM.
For example, I once flashed GOV2, over GenericGinger and STILL HAD a green theme. That's how I knew something was wrong. From there on then, I ALWAYS ALWAYS ALWAYS like a religion, wiped twice. There's no reason NOT to do it. It takes very little time, and is added insurance to a fully functional and stable ROM.
Edit : If no one likes the method, by all means do things your own way ; whatever works for you works ; however I do things judging on the fact from experience of using/doing them.
Click to expand...
Click to collapse
All that fixing permissions will do is make a apk readable and writable, I believe it isn't necessary after 2 wipes.
insanedrunk said:
All that fixing permissions will do is make a apk readable and writable, I believe it isn't necessary after 2 wipes.
Click to expand...
Click to collapse
I may have been dramatic with the fix permissions bit, but it is what I've been doing since I started picking up the GenericGinger project and it hadn't failed me once. I do however recommend doing everything else (mostly the data format) TWICE.
djh said:
I've always wondered, what's the point of doing wipe twice?
Click to expand...
Click to collapse
It's really silly.
It is a problem with some developers cwm updater-scripts. Rather then formating partitions, they just rm -rf the data on the partition. Then they unmount the filesystem without syncing first.
If you don't sync before unmounting, the deletions might not happen.
So, the effect that some users see by wiping twice is that when the filesystem mounts again, the deletions that happened before get "fsync()"ed by the filesystem driver and it appears that formating twice does the right thing.
So developers are causing the problem without understanding the problem.
bhundven said:
It's really silly.
If you don't sync before unmounting, the deletions might not happen.
Click to expand...
Click to collapse
That sure make sense. Thanks for explaining
So you mean the entire time every time I had this problem, it was due to that damn script? This thing happens on like every ROM Lol...
I can take a crack at adding fsync...but should I add it after RM -rf or change it altogether? What do you recommend?
Sent from my SGH-T989 using xda app-developers app
Probably a little too simple, but is this right bhundven?
{
"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"
}
bhundven said:
It is a problem with some developers cwm updater-scripts. Rather then formating partitions, they just rm -rf the data on the partition. Then they unmount the filesystem without syncing first.
Click to expand...
Click to collapse
This thread saved my bacon -- I was contemplating messing about with Odin/Heimdall to try and format partitions manually after 'adb restore' command filled up my internal storage on a Samsung Galaxy S4 Mini with ~3GB of unreachable mess. The CWM factory reset option didn't clear it, but executing 'factory reset' and also 'format /data and /data/media (/sdcard)' from the Mounts and Storage Menu twice did the trick. Not entirely certain if it was a missing sync issue or just a matter of specifically selecting 'format /data and /data/media (/sdcard)', but this thread led me to a much safer solution than bootloader tools!
Is this method guarantee a security delete, which means that impossible to recover data by any recovery software?
Related
TroubleShoot & Unbrick Your HTC 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"
}
Hello Everyone!
So, You got your (supposing) first Android device, and were amazed at all the capabilities the Android OS gave to you, and hence started exploring the world of custom ROM's and some of you (like me) even started basic modding of ROM's to suit personal needs, And hence somehow MANAGED to end up with a struck HTC whitescreen or a Bootloop? Or you are facing some other problems after rooting?
Believe me, Thats quite natural, even i asked for help in my early n00b days! Its fine to ask questions, AS LONG AS THEY ARE NOT ALREADY ANSWERED:angel:
Whatever the problem is, I hope this guide can solve it. Also, it is not easily possible for any normal rooted user to have a Hard Bricked Phone, which of course has no solutions, Other than using it as a paperweight.The methods can be used to revive a phone from a soft brick, or a bootloop. The techniques mentioned below should work on most HTC phones with some minor changes. :highfive:
Case [1] You are struck in a bootloop...
That is not a big deal actually. 90% chances are that a full data wipe will throw it out form the bootloop.
Ok, so a data wipe didnt worked and you are still struck at the bootanimation.... Try replacing the systemui.apk and framework-res.apk of the rom with a rom which was booting properly. (This case is valid mostly if you were theming stuff for you own personal ROM)
Case[2] You are struck on the whitescreen HTC logo. (aka Softbrick)
Confirm if you can go to the recovery via the bootloader menu or not. If no, check the next case.
This usaually happens due to an improperly cooked ROM. And no such ROM is available on XDA as far as i know, so this is for the beginner customizers.
Simply flash another ROM after wipe data/ Factory Reset. This will fix the issue.
Case[3] You cannot even go to the recovery! (aka A bad but still a Soft Brick)
The title is actually misleading... YOU CAN ALWAYS GO TO THE RECOVERY.
Sometimes it happens that the memory at the time of boot is so full, that it cannot process all the commands at once, and hence gets struck when choosing recovery option from the bootloader menu.
Take out the battery, reinsert it...
Press and hold the power button for GREATER than 15 seconds. Continue holding it even after the screen has turned on. (This is a kind of factory reset)
Either wait for the bootanimation or pull the battery again after 30 seconds or so and retry entering the recovery via bootloader menu.
Ok mate, I managed to get to the recovery, NOW WHAT??
Congratulations, First of all
Wipe data/Factory reset your phone.
(optional) Wipe Dalvik Cache ... from the advanced options in recovery.
Wipe data and flash a ROM which is gurranteed to work.
I wish to move from Sense based ROM's to CyanogenMod or ICS or JellyBean or vice versa, Any special procedures?
First, All the mentioned ROM's HAVE SUCCESFULLY BEEN PORTED FOR EXPLORER... expect threads within few days.
The steps mentioned for installing the ROM's , on the respective threads are good enough.
Be on the safe side, go to recovery> Mounts and storage> format /data, /cache, /system partitions.
After formatting them, don't forget to MOUNT THEM.
Flash ROM and if needed, do a factory reset after flashing.
So, your issue is still not solved? Already unlocked the bootloader, and thus voided your warranty? And now thinking of going to the HTC Service center to get your issue fixed?
STOP! Remember that your warranty is now totally void?What face will you show in the service center?
I have got a solution for you... WAIT TILL S-OFF GUIDE. There will be a (hopefully simplified) copy of that here... (after due permission from op)
The solution provided will LOCK your bootloader and it will appear as LOCKED instead of Re-Locked... But a risky process and can harm your phone permanently...
S-OFF is there for pico.. just not for the masses...
If this guide helped you in any way, Dont say or post thanks.... There is a button for it, so USE IT! :fingers-crossed:
RESERVED
[email protected] went on mars...
but soff guide will help claim warranty!
bhargz and cute_price currently soffed (i guess) and soff guide will take time.
Another Reserved... u jelly? :cyclops::laugh:
Nice work man! :good:
Surely those who are in trouble appreciate the touches of humor on your thread
Regards
Txask said:
Nice work man! :good:
Surely those who are in trouble appreciate the touches of humor on your thread
Regards
Click to expand...
Click to collapse
Appretiated! any other suggestions?
acedexplorerABL said:
Appretiated! any other suggestions?
Click to expand...
Click to collapse
Nice Work!
Just Increase the Text size a bit to make it Readable.
Nihar.G said:
Just Increase the Text size a bit to make it Readable.
Click to expand...
Click to collapse
The text is perfectly readable. Making it larger would look stupid.
If it's not large enough for you (despite being the same size as the text in your own and every other post in this thread), hold Ctrl on your keyboard and press + a few times. (Or hold control and scroll up on your mouse wheel)
I am used to the standard format... text is fine for me... what needs extra attention has already been bolded.
Anyways thanks for suggestions.. any other handy fix you guys know?
SifJar said:
The text is perfectly readable. Making it larger would look stupid.
If it's not large enough for you (despite being the same size as the text in your own and every other post in this thread), hold Ctrl on your keyboard and press + a few times. (Or hold control and scroll up on your mouse wheel)
Click to expand...
Click to collapse
It looked smaller than usual that's why suggested -_-
Sent from my HTC EXPLORER using xda app-developers app
Nihar.G said:
It looked smaller than usual that's why suggested -_-
Sent from my HTC EXPLORER using xda app-developers app
Click to expand...
Click to collapse
well its the normal font and size with which we are commenting. If i use a bigger size,it will still look funny
Nice work pal!
It helped me too much, I think my phone was getting a soft-brick :S
Cheers!! ;D
cool stuff
Thanks for this awesome post but my phone i think which is in case 3 didnt get me into recovery by using the solution provided. any suggestions?
aceonline said:
Thanks for this awesome post but my phone i think which is in case 3 didnt get me into recovery by using the solution provided. any suggestions?
Click to expand...
Click to collapse
Can you get to the recovery???
hi where can i download CWM recovery for explorer??
No i cannot get into recovery
Here is a detailed thread regarding my problem
http://forum.xda-developers.com/showthread.php?t=1827822
Lets say about my experience with halt on logo after factory reset. I find that folder "fonts" in my original firmware is located in folder "data" and in folder "system" is only symlink to /data/fonts. If was installed custom recovery, after factory reset from phone setup folder "data" is cleared and fonts can not be restored(may be they are restored from original recovery). If i did factory reset from custom recovery, same folder is cleared too and no atempt to restore fonts. In both cases phone hangs on HTC logo. What is needed to do is to remove symlink to fonts in /system and copy folder /data/fonts to /system/fonts Permissions of folder must be as other folders in "system" and for files inside must be -rw-rw-rw- user root group root. For root access to files you can use "adb shell" when in custom recovery after mounting "data" and "system" from "mounts and storage menu" of custom recovery.
And then you can do factory reset as many times as you wish without problems.
Here is zipped folder "fonts" from my phone but i dont know if it is compatible with every firmware. My firmware is Vodafone Greece(VODAP034).
procedure for locking the boot loader
@acedexplorerABL,
bro, when will you upload the procedure for locking the boot loader..thanks.
My exams are going on till 1st october.... i cant help it... sorry everyone... ill be offline for all the september...
ill update all threads after my exams are over..
acedexplorerABL said:
My exams are going on till 1st october.... i cant help it... sorry everyone... ill be offline for all the september...
ill update all threads after my exams are over..
Click to expand...
Click to collapse
Good luck for your exams
Hello all,
I just tried to make my Nexus 5 read NFC while on the locked screen using this thread.
http://forum.xda-developers.com/nexus-4/development/mod-modified-nfcnci-apk-to-poll-screen-t2391170/page3
Apart from it not working (rooted, read/write, permissions set, etc....) I now get the following error mesage when I try to onter the setting on my Nexus.
"unfortunately, settings has stopped"
Placed back the original 'NfcNci.apk' and 'NfcNci.odex' files with no result.
I did a lot of searching, but cannot find a solution.
I hope anyone can help my out here.
Thanks in advance !!!!!
Don't suppose you made a nandroid before installing the apk. You could just restore it if you did. OtherWise you might have to flash the system.img from the factory image in fastboot
Sent from my Nexus 5 using XDA Free mobile app
Forgot to mension that :silly:
I backed up the original 'NfcNci.apk' and 'NfcNci.odex' before I started. Already placed the back, with no results.
keroner said:
Forgot to mension that :silly:
I backed up the original 'NfcNci.apk' and 'NfcNci.odex' before I started. Already placed the back, with no results.
Click to expand...
Click to collapse
Try clearing data for it if there is any, then try clearing cache?
Lethargy said:
Try clearing data for it if there is any, then try clearing cache?
Click to expand...
Click to collapse
Can you explain how to do this. If it's in the settings menu, it's a problem since I can't get in the settings........
keroner said:
Can you explain how to do this. If it's in the settings menu, it's a problem since I can't get in the settings........
Click to expand...
Click to collapse
And wipe cache + Dalvik in recovery
/data/data
{
"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"
}
If that doesn't work you can just make a nandroid backup, flash factory images, use Titanium Backup to backup the fresh Settings.apk/NfcNci.apk/data then restore your nandroid and restore the TiBu backup of those two
Lethargy said:
And wipe cache + Dalvik in recovery
/data/data
If that doesn't work you can just make a nandroid backup, flash factory images, use Titanium Backup to backup the fresh Settings.apk/NfcNci.apk/data then restore your nandroid and restore the TiBu backup of those two
Click to expand...
Click to collapse
Deleted the content in com.android.nfc. No luck.
Dalvik is new to me.
What I discovered is that the 'NfcNci.apk' looks different after replacing it.
It first looked like a bluetooth logo (the backup on sd still does). But after copying it to 'system/app' it looks like an android robot coming out of a blue box with APK written on it.
When I trie to run the 'NfcNci.apk' it gives me a parse error.
keroner said:
Deleted the content in com.android.nfc. No luck.
Dalvik is new to me.
What I discovered is that the 'NfcNci.apk' looks different after replacing it.
It first looked like a bluetooth logo (the backup on sd still does). But after copying it to 'system/app' it looks like an android robot coming out of a blue box with APK written on it.
When I trie to run the 'NfcNci.apk' it gives me a parse error.
Click to expand...
Click to collapse
Delete both the .apk and .odex, along with data folder then reboot to recovery, clear cache and Dalvik, boot into android and put the backed up files back into /system/app with correct permissions and reboot again. If it doesn't work then try the other method I suggested previously, if that doesn't work I don't know what to tell you lol. Also try clearing data of Settings itself
Thanks for all your help thusfar Lethargy!!!
If you can only tell me how to "clear cache and Dalvik" I will give it a go.
I'm a bit new to android so please forgive me for any simple questions......
keroner said:
Thanks for all your help thusfar Lethargy!!!
If you can only tell me how to "clear cache and Dalvik" I will give it a go.
I'm a bit new to android so please forgive me for any simple questions......
Click to expand...
Click to collapse
Depends on what recovery you're using, TWRP or CWM. In CWM it should be in advanced, in TWRP tick the boxes for it in wipe. Search it up if you're not sure.
On the other hand, "Unfortunately, Lethargy is falling asleep"
Different timezones i guess
I ended up flashing and restoring the apps one by one. So far so good.......
keroner said:
Different timezones i guess
I ended up flashing and restoring the apps one by one. So far so good.......
Click to expand...
Click to collapse
Always make a nandroid backup when doing system modifications lol
Lethargy said:
Always make a nandroid backup when doing system modifications lol
Click to expand...
Click to collapse
That my friend is something I learned the hard way
keroner said:
That my friend is something I learned the hard way
Click to expand...
Click to collapse
Hard way is the best way to learn sometimes
Alright guys, I have yet to figure out what actually happened. All I remember is downloading Liquid Smooth, backing up my Android L Rom. Then wiping data and installing Liquid Smooth, my WiFi didn't work so I went back to Recovery mode, did a wipe and restored my Android L backup.
Now when I unlock the phone after the initial boot. A couple of my applications began crashing. So I ignored it and decided to go to my File Explorer.
When I opened it, the SD Card showed up as empty. No content whatsoever, however on the Storage section in Settings. It says I have quite a bit of things. So I went ahead and installed another File Browser, when I selected Main Storage. It said in big bold letters "Access Denied to Main storage".
At this point I have no clue what had just happened. I went to Recovery, wiped data and restored my backup. Same outcome.
Then I went into mounts and mounted system and still the same thing happened. Could someone explain what just happened and how can I fix this?
I really appreciate the time you've spent to read this, looking for answers. I hope someone replies quickly, I'm quite paranoid at this very moment.
Thanks!
TheArc said:
Alright guys, I have yet to figure out what actually happened. All I remember is downloading Liquid Smooth, backing up my Android L Rom. Then wiping data and installing Liquid Smooth, my WiFi didn't work so I went back to Recovery mode, did a wipe and restored my Android L backup.
Now when I unlock the phone after the initial boot. A couple of my applications began crashing. So I ignored it and decided to go to my File Explorer.
When I opened it, the SD Card showed up as empty. No content whatsoever, however on the Storage section in Settings. It says I have quite a bit of things. So I went ahead and installed another File Browser, when I selected Main Storage. It said in big bold letters "Access Denied to Main storage".
At this point I have no clue what had just happened. I went to Recovery, wiped data and restored my backup. Same outcome.
Then I went into mounts and mounted system and still the same thing happened. Could someone explain what just happened and how can I fix this?
I really appreciate the time you've spent to read this, looking for answers. I hope someone replies quickly, I'm quite paranoid at this very moment.
Thanks!
Click to expand...
Click to collapse
KK and L are different, messes around with userdata. KK uses /storage/emulated/0 and L uses data/media/0. Some people have also lost their internal storage completely. SELinux is also different.
Try opening Terminal Emulator:
su
restorecon -r /data/media/0/*
If that doesn't work then you'll have to backup and flash + wipe userdata.img
Lethargy said:
KK and L are different, messes around with userdata. KK uses /storage/emulated/0 and L uses data/media/0. Some people have also lost their internal storage completely. SELinux is also different.
Try opening Terminal Emulator:
su
restorecon -r /data/media/0/*
If that doesn't work then you'll have to backup and flash + wipe userdata.img
Click to expand...
Click to collapse
{
"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"
}
Got that, rebooted. Same outcome.
So what do you think if I completely wipe my device and install another KitKat Rom, it should be fine?
TheArc said:
Got that, rebooted. Same outcome.
So what do you think if I completely wipe my device and install another KitKat Rom, it should be fine?
Click to expand...
Click to collapse
Try
restorecon -FR /data/media/0
Not sure if wiping in recovery will work, but reflashing userdata.img with a wipe (-w) will work for sure, though.
Lethargy said:
Try
restorecon -FR /data/media/0
Not sure if wiping in recovery will work, but reflashing userdata.img with a wipe (-w) will work for sure, though.
Click to expand...
Click to collapse
Wow thank you brother! That worked like a charm.
You're the best !
TheArc said:
Wow thank you brother! That worked like a charm.
You're the best !
Click to expand...
Click to collapse
Cool.
Lethargy said:
KK and L are different, messes around with userdata. KK uses /storage/emulated/0 and L uses data/media/0
Click to expand...
Click to collapse
/sdcard was always /data/media on fuse storage devices until 4.2 when it moved to /data/media/0. We've been using /data/media/0 since jellybean in Android. /storage/emulated/0 points to the same location and always has since 4.2
Whatever has changed in L, this is not it - although I have no explanation for the problem.
Actually there are multiple locations that point to /data/media/0 since jellybean. I list them all in my nexus 5 storage thread which you can get to via the link in my signature
Sent from my Nexus 5 using Tapatalk
rootSU said:
/sdcard was always /data/media on fuse storage devices until 4.2 when it moved to /data/media/0. We've been using /data/media/0 since jellybean in Android. /storage/emulated/0 points to the same location and always has since 4.2
Whatever has changed in L, this is not it - although I have no explanation for the problem.
Actually there are multiple locations that point to /data/media/0 since jellybean. I list them all in my nexus 5 storage thread which you can get to via the link in my signature
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Someone else said that was it which confused me, I basically searched it and copy + pasted xD
But yeah, I'm not exactly sure what causes internal storage to mess up regarding L. Compare the contents of userdata.img maybe? The issue seems to be weird though, some people can "recover" it with Terminal, some people simply have the contents of internal storage moved into another folder and some people just lost it completely. 9/10 times it's because of a flashable zip and not doing it the proper way with fastboot, but @simms22 had his internal storage moved after a proper flash, but had no issues dirty.
Lethargy said:
Someone else said that was it which confused me, I basically searched it and copy + pasted xD
But yeah, I'm not exactly sure what causes internal storage to mess up regarding L. Compare the contents of userdata.img maybe? The issue seems to be weird though, some people can "recover" it with Terminal, some people simply have the contents of internal storage moved into another folder and some people just lost it completely. 9/10 times it's because of a flashable zip and not doing it the proper way with fastboot, but @simms22 had his internal storage moved after a proper flash, but had no issues dirty.
Click to expand...
Click to collapse
Yeah I remember on the s3, people going from 4.1.2 to 4.2 with flashable zips, and they would end up with /data/media/0/0. Some did it several times and ended up with /data/media/0/0/0/0 etc.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yeah I remember on the s3, people going from 4.1.2 to 4.2 with flashable zips, and they would end up with /data/media/0/0. Some did it several times and ended up with /data/media/0/0/0/0 etc.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Watch it end up being even worse when release version of "L" comes out and suddenly 90% of XDA "lost their internal storage" using flashable zips lol
Elluel said:
Try
restorecon -FR /data/media/0
Not sure if wiping in recovery will work, but reflashing userdata.img with a wipe (-w) will work for sure, though.
Click to expand...
Click to collapse
I am forever indebted to you your majesty.
Alright, so here's what happened.
Finally updated hardware and went from a nexus 6p to a pixel xl.
It's running 8.0.
So I decided it was time to get the phone up to the same customization that I had on my 6p.
One of my first things, after rooting of course, was adding qemu.hw.mainkeys=1 to build.prop in order to get rid of the soft keys. Same exact thing I've done on literally all of my android phones ever.
Rebooted.
I now get this sweet messaging saying "Can't load Android system..." (See Picture) and so on. Suggesting Try again and Factory data reset.
So I'm like whatever, I can just pull build.prop to my computer. So I find some guides on how to do that and boot to the bootloader.
But then adb devices shows:
"List of devices attached"
And then nothing. So adb can't find my phone.
Here's what I tried in trouble shooting.
Disconect Cable
adb kill-server
adb start-server
Plug back in.
Still nothing.
I even tried a different USB port.
So now I'm like "Okay, I'll take the bullet and factory reset."
So I did.
After setup, I get about 30 seconds (without softkeys) of phone time before my the System UI crashes and the phone shuts off.
Upon reboot, I'm faced with the same "Can't load Android system screen..." (See picture again if you want) and we're back to square one.
So...
Can't adb pull on build.prop because adb can't find my phone.
Can't boot into the regular system and edit build.prop from there because the phone isn't rooted (cause the only way to boot into the system is to factory reset).
Can't root the phone because adb can't find my phone.
And lastly, can't flash factory images because adb can't find my phone.
That's all the trouble shooting I've tried. If anyone can help me out here, I would be super grateful, cause right now, I have a really expensive paperweight.
Thanks in advance.
{
"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"
}
hello, try flashing through fastboot following this post:
https://forum.xda-developers.com/showpost.php?p=70041042&postcount=3
here if you want to unlock the bootloader:
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
Yup. That worked. Thank you!
Any idea why adding qemu.hw.mainkeys=1 to build.prop killed my rom?
burt1215 said:
Any idea why adding qemu.hw.mainkeys=1 to build.prop killed my rom?
Click to expand...
Click to collapse
Because the UI has to have nav keys, unless your Pixel has hardware keys, you'll probably have to keep the softkeys.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Because the UI has to have nav keys, unless your Pixel gas hardware keys, you'll probably have to keep the softkeys.
Click to expand...
Click to collapse
I've hidden the softkeys on my Nexus 4, Nexus 5, and Nexus 6P. And on every operating system since ICS.
What's different now? Is it the Pixel XL or Oreo?
burt1215 said:
I've hidden the softkeys on my Nexus 4, Nexus 5, and Nexus 6P. And on every operating system since ICS.
What's different now? Is it the Pixel XL or Oreo?
Click to expand...
Click to collapse
To be honest, I've never heard of it being an issue either, I was just speculating, however unlikely it may be.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
To be honest, I've never heard of it being an issue either, I was just speculating, however unlikely it may be.
Click to expand...
Click to collapse
Ha. No worries.
After fixing my phone, I decided to edit build.prop again, cause it's not stupidity unless you try the same thing multiple times while expecting different results right?
Anyway, same exact thing happened.
This time I fixed it without wiping my phone, but it leads me to believe that build.prop can't be edited... but I'm still not sure why.
burt1215 said:
Ha. No worries.
After fixing my phone, I decided to edit build.prop again, cause it's not stupidity unless you try the same thing multiple times while expecting different results right?
Anyway, same exact thing happened.
This time I fixed it without wiping my phone, but it leads me to believe that build.prop can't be edited... but I'm still not sure why.
Click to expand...
Click to collapse
Are you booting to recovery and wiping cache and dalvik/ART cache(obviously not factory reset or wipe data, just the caches)? It's usually required when modifying system files.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Are you booting to recovery and wiping cache and dalvik/ART cache(obviously not factory reset or wipe data, just the caches)? It's usually required when modifying system files.
Click to expand...
Click to collapse
I edited build.prop and rebooted the system.
Got the same error as the picture in the original post.
Booted into TWRP and pulled build.prop onto my computer.
Edited the file, pushed it back in and rebooted into the system without any errors.
burt1215 said:
I edited build.prop and rebooted the system.
Got the same error as the picture in the original post.
Booted into TWRP and pulled build.prop onto my computer.
Edited the file, pushed it back in and rebooted into the system without any errors.
Click to expand...
Click to collapse
Strange, at least it works.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hi,
I've got a Samsung Galaxy A10 SM-A105F and I tried installing all kinds of different roms on it and they install just fine but then when i go to boot to system I end up in this hell hole of perpetual booting and restarting. I've been at it for 6h now and I'm exhausted. Please help.
Try last known good rom. Possible hardware failure...
blackhawk said:
Try last known good rom. Possible hardware failure...
Click to expand...
Click to collapse
{
"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"
}
These are all the ones I tried. They all install just fine but when I click "reboot system" it reboots but it doesn't boot into the rom but just loops.
Recovering Spaghetti said:
View attachment 5799685
These are all the ones I tried. They all install just fine but when I click "reboot system" it reboots but it doesn't boot into the rom but just loops.
Click to expand...
Click to collapse
I know the Bliss one is GAPPS not a ROM but the rest of 'em are.
I could
blackhawk said:
Try last known good rom. Possible hardware failure...
Click to expand...
Click to collapse
I could provide you some pictures of the installation if that helps.
Flash stock with odin only that way you will know if the phone's ok, it may take a while but probably not as long as half a dozen custom roms.
Recovering Spaghetti said:
View attachment 5799685
These are all the ones I tried. They all install just fine but when I click "reboot system" it reboots but it doesn't boot into the rom but just loops.
Click to expand...
Click to collapse
The problem may not be the firmware; firmware very rarely spontaneously goes corrupt. Most times it's either a rootkit or hardware failure caused. A factory reset confirms the problem wasn't on the user data partition and that you potentially have a real nasty issue. Android 9 or higher should be immune to partition worming rootkits.
Use logcat(?) or other tools to find out why it's crashing. Personally I never had to do this once in 12 years of using Androids, they tend to be a very stable platform. Maybe be a failed sub module ie cam but more than likely it's a failed mobo. Is the battery known to be good?
Here's my lineage os install for instance, now when I press the reboot system button it goes into the loop.
blackhawk said:
The problem may not be the firmware; firmware very rarely spontaneously goes corrupt. Most times it's either a rootkit or hardware failure caused. A factory reset confirms the problem wasn't on the user data partition and that you potentially have a real nasty issue. Android 9 or higher should be immune to partition worming rootkits.
Use logcat(?) or other tools to find out why it's crashing. Personally I never had to do this once in 12 years of using Androids, they tend to be a very stable platform. Maybe be a failed sub module ie cam but more than likely it's a failed mobo. Is the battery known to be good?
Click to expand...
Click to collapse
Yes and this is also like my 3 rom on this phone (installing this one cause my bluetooth headphones couldn't pair for some reason) and they all worked fine before.
Recovering Spaghetti said:
Yes and this is also like my 3 rom on this phone (installing this one cause my bluetooth headphones couldn't pair for some reason) and they all worked fine before.
Click to expand...
Click to collapse
The last one was crdroid which is also one I'm having difficulties with now.
Recovering Spaghetti said:
Yes and this is also like my 3 rom on this phone (installing this one cause my bluetooth headphones couldn't pair for some reason) and they all worked fine before.
Click to expand...
Click to collapse
*I meant 3rd rom
Oh, I managed to actually catch it on camera. That's the issue.
although it's present in screenshots I can't see formatting /data on video.
format /data - type yes - reboot recovery - sideload ROM
aIecxs said:
although it's present in screenshots I can't see formatting /data on video.
format /data - type yes - reboot recovery - sideload ROM
Click to expand...
Click to collapse
I did do that & I also wiped dalvik, product, system, vendor, data, internal storage & cache.
you wiped vendor?
aIecxs said:
you wiped vendor?
Click to expand...
Click to collapse
Yes. Is that wrong?
depends on ROM. I haven't flashed any GSI myself but from what I have read so far is, with Project Treble, /vendor is separated from /system for reason. usually one will keep stock vendor all the time, only system is flashed.
of course, if we're talking about device specific custom ROM, might be the vendor partition is included. nothing wrong with flashing vendor from custom ROM, though..
aIecxs said:
depends on ROM. I haven't flashed any GSI myself but from what I have read so far is, with Project Treble, /vendor is separated from /system for reason. usually one will keep stock vendor all the time, only system is flashed.
of course, if we're talking about device specific custom ROM, might be the vendor partition is included. nothing wrong with flashing vendor from custom ROM, though..
Click to expand...
Click to collapse
Okay, so what do you want me to do now? Perhaps we could get on like google meet or something. Maybe that could make things easier.
refer to post #6
+ read instructions for the ROM