Okay, so I have a Samsung Galaxy S 5, specifically the SM-G900H.
I rooted it some months ago and yesterday wanted to use the Screen Mirroring, so I found that you could get that function back by adding a line to the build.prop file.
Did that using this build.prop editor in F-droid.
It worked, but it also gave me a 2048 resolution and tablet layout (odd, I just added the key "wlan.wfd.hdcp" with the value "disable"), since I saw it stated that it had made a backup I chose to use the "restore" option and then boot. I'm not sure if it restored the wrong file or what but now after the first splash screen I get a black screen.
I went into Recovery Mode (Home+Power+VolumeUp) and tried to do adb from there but I only see the phone as "Host" and adb gives me an "error: closed" message whenever I try to do anything else than adb devices. If I try this without going into recovery mode I see the device as "offline".
So giving up hope to do this smartly by fixing the build.prop I tried a data wipe from recovery mode, the error persists but now I get stuck hearing the second splash screen's sound over and over again.
If I start ODIN mode I can see the device and flash (?) the auto-root found here without problem.
So, what do you recommend I do at this point? is there any way to edit the build.prop file with either ODIN or recovery mode's adb sideload?.
Or should I just flash a new ROM? I downloaded Cyanogenmod but I'd rather keep using stock for now. Where can I find the latest stock rom?.
Sorry if this has been solved elsewhere, I've looked and tried a bunch of them... there's a lot of noise out there.
update (making progress)
In case anybody wants to chime in (or this helps anyone else in the future)
I think I made some progress but the phone is not functional yet.
I flashed the TWRP found here:
http://forum.xda-developers.com/galaxy-s5/development/rom-kian-rom-bog6-t3187812
and went into recovery mode with that.
I did a backup, although I'm not certain what it backed up and where because neither the free space it needed nor the used space I had match up very much with that... a bit worried.
Then I mounted the /system and saw that there was no build.prop but only the build.prop.bak so I renamed that to build.prop and now I can see the second splash screen and don't hear it (I think this is because I might have had the volume down before) and it gets stuck there.
But hey, now I can edit the build.prop and maybe backup my files (mostly the chat logs and pictures) into the SD card. Will see what happens... I'll try to remember to come back and update.
build.prop.bak is the original it backed up when you edited it, it saves a new copy
Just rename to build.prop and reboot
*Detection* said:
build.prop.bak is the original it backed up when you edited it, it saves a new copy
Just rename to build.prop and reboot
Click to expand...
Click to collapse
hmmm Detection I did that at some point and it didn't seem to work, but it could have been that I didn't wait long enough.
After several more changes it worked (although my phone is still in tablet mode and I lost all my personal data).
Related
Was playing around at work today, getting ready to install the edited build.prop. I had renamed the old one to build.prop.bak, and somehow managed to restart the phone without putting a new one in.
The phone stays at the M screen, and I can get into the standard recovery (i thought I had the custom one installed...guess not). Is there anyway I can push a new build.prop file through standard recovery??
The only thing I have tried to do is reapply the 2.2 update.zip I was running, which didn't work due to signature verification failure.
Don't know. You may have to hard reset, or apply the sbf.
terriermike said:
Was playing around at work today, getting ready to install the edited build.prop. I had renamed the old one to build.prop.bak, and somehow managed to restart the phone without putting a new one in.
The phone stays at the M screen, and I can get into the standard recovery (i thought I had the custom one installed...guess not). Is there anyway I can push a new build.prop file through standard recovery??
The only thing I have tried to do is reapply the 2.2 update.zip I was running, which didn't work due to signature verification failure.
Click to expand...
Click to collapse
Is adb accesible with the standard recovery??
Meaning if you type in:
Code:
adb devices
Do your device show up?
If so, you can use adb to push the build.prop to /system
If not, sbf
I will try that. I've never used adb before, just terminal from the phone. I went on the google adb site and could't find a download link though...can you post it? I just see a bunch of tutorials on how to use it.
terriermike said:
I will try that. I've never used adb before, just terminal from the phone. I went on the google adb site and could't find a download link though...can you post it? I just see a bunch of tutorials on how to use it.
Click to expand...
Click to collapse
http://code.google.com/p/xdroidx/wiki/HowToSetUpADB
I've been going through quite an ordeal with my Tab over the past few days.
It started with my Tab boot looping for no apparent reason, then I couldn't get fastboot to work, but now I solved my fastboot problems. I followed some instructions (here: http://forum.xda-developers.com/showpost.php?p=14600617&postcount=111) on how to use fastboot to get it working again, and i flashed that system image linked to in that post. And it worked, I had my Tab up and running again, but I noticed that my storage space total is now at 13GB; I remember it having 32GB total storage before this whole ordeal. I'm guessing I flashed the wrong system image to my device, so does anyone have the correct system image for the I/O Tab 10.1?
I tried this one: http://forum.xda-developers.com/showthread.php?t=1075993 and my device gets stuck in the boot screen (not even looping, it just stays on the "Samsung Galaxy Tab 10.1" screen)
Any help would really be appreciated.
use this to recover:
http://forum.xda-developers.com/showpost.php?p=14684694&postcount=77
read the whole thing (quoted and unquoted).
you can get images here:
http://droidbasement.com/galaxy/sys-backup/hc_31
if you have media (/data/media (internal sdcard)), back it up prior (you will lose it).
that droidbasement link returned a 404 not found error.
fixed.
refresh.
let me upload raw fastbootable images also, for the first part.
check back in one hr.
done uploading.
Ok, I've got it all sorted out. Thanks for the quick response, Pershoot.
Here's a breakdown of how I got it working again...
First, I installed PDAnet as a shortcut to get the fastboot drivers, as soon as I installed it, fastboot started working.
Then I downloaded the files linked here: http://forum.xda-developers.com/show...&postcount=111
Then I followed the first half of Pershoot's instructions (http://forum.xda-developers.com/showpost.php?p=14684694&postcount=77) using the files provided by novicejeep. I did all the fastboot stuff, booted into recovery, factory reset, reboot, but instead of getting a boot loop, my device booted up just fine. I had previously flashed these same files to get it working but those times my storage showed as 13GB for some reason, but now it's showing as 27GB. I'm guessing the factory reset corrected that issue (or maybe it was erasing before flashing each thing?).
The only downside now is that I'm back on 3.0.1, so what's the safest way to get up to 3.1 for a root user? I suppose I'll take my chances with System Update in the Settings.
Thanks Pershoot, novicejeep, kdietze3 and everyone else here on the forums
if you are on 3.0, then just use the restore method to 3.1.
you would have been on 3.1, if you would have used all 3.1 images, as outlined in my instructions from the sys-backup/hc_31 folder.
I ran system update and now I'm on 3.1 again
Even though I had fastboot working, I couldn't get ADB to work so I couldn't push the backup file to the device so I could restore it. Without that, I just kept bootlooping.
When I used the 3.0 files, I didn't even get that far in your instructions. At the part where you expect it to boot loop, it just booted up with no problems. Whereas when I flashed the hc31 files you posted, I bootlooped at that step.
dracoaffectus said:
I ran system update and now I'm on 3.1 again
Even though I had fastboot working, I couldn't get ADB to work so I couldn't push the backup file to the device so I could restore it. Without that, I just kept bootlooping.
When I used the 3.0 files, I didn't even get that far in your instructions. At the part where you expect it to boot loop, it just booted up with no problems. Whereas when I flashed the hc31 files you posted, I bootlooped at that step.
Click to expand...
Click to collapse
yea as outlined. then prceed on with the instructions, and when done, you will be sorted.
The new kernel did not like my tab. It crashed pretty hard when I plugged it in to charge. Now when I try to boot, it loops at the "glowing SAMSUNG" screen. I tried to restore with ODIN and it's still looping. Going to try this method.
I take no responsibility for any harm that comes to your phone as a result of applying this mod.
Official Clockwork Mod Recovery 5.0.2.6
Note that ROM manager support isn't currently complete. ROM downloads etc should all be working fine, but it needs to be updated to properly flash the recovery. At the moment it uses a method called fakeflash which will load the latest recovery from within whatever recovery you have installed. All other aspects are working fine though.
Download:
5.0.2.6: http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.6-u8800.img
Installation Instructions (upgrading - root explorer method):
Using any file explorer which is able to remount as writeable (such as root explorer), browse to the /cust_backup directory and remount it as writeable
Navigate to the image directory and backup up the current recovery by renaming it to something like recovery.bak, or _recovery.img
Rename the downloaded recovery to recovery.img and copy to the image directory.
Installation Instructions (new install):
Unplug any usb connection and turn the phone completely off
Whilst holding both the volume + and volume - keys hold the power button to turn the device on. Let go when you see a pink/purple screen.
Attach the usb cable to your computer and wait until a few usb mass storage devices are detected and mounted. Look for one that has just one directory called 'image' in it. Navigate into this directory and you'll see recovery.img etc.
(optional) Rename recovery.img to recovery_backup.img
copy the new recovery.img to image, unmount the mass storage device (safely remove in windows) and then pull the battery out to turn the phone off.
Hold volume + and power to boot to recovery.
Install any custom rom
Install rom manager and update to latest recovery
Source:
https://github.com/stockwell/android_device_huawei_u8800
That's cool! Is it still possible to boot it with stock kernel, or you did modifications to recovery_kernel?
You can't flash the boot images with cwm i thibk. Download and add this recovery img in /cust_backup/image folder its done.
And thanks stockwell. Haptic now work in recovery mode. Blue text version is much better than yellow
- U8800
blue text i like it.
thanks stockwell
stockwell said:
[*] Instead of using /cust_backup it now uses /boot. This doesn't affect rom installations but it WILL affect backups as it won't restore the cust image. If you want to go back to one of these backups from the new recovery you can go to the backup location, rename cust.img to boot.img, and also edit nandroid.md5 so that it says boot.img instead of cust.img. The backup will then restore but just be aware that it will also revert to the recovery you had when the backup was made.
Click to expand...
Click to collapse
Stockwell, this is for old backups and for the ones made already with the new recovery? We still have to make these alterations everytime we want to restore?
Thanks a lot . Good job.
Sent from my u8800 using XDA App
Druida69 said:
Stockwell, this is for old backups and for the ones made already with the new recovery? We still have to make these alterations everytime we want to restore?
Click to expand...
Click to collapse
Sorry I meant to reword that since its a little unclear. This is only for backups made with an old version of recovery. All new backups will name it boot instead of cust.
stockwell said:
Sorry I meant to reword that since its a little unclear. This is only for backups made with an old version of recovery. All new backups will name it boot instead of cust.
Click to expand...
Click to collapse
You probably need to change your anyKernel script as well to use /boot instead of /cust for the boot.img, if I did not misunderstood.
Ok thank you stockwell, was just to have 200% sure
NForce25 said:
That's cool! Is it still possible to boot it with stock kernel, or you did modifications to recovery_kernel?
Click to expand...
Click to collapse
The recovery kernel is the kernel I use for Miui, but with the framebuffer set to 16-bit colour.
There's nothing specifically added to the kernel to make it work with the recovery other than that, but if you do manage to get it to boot on your pro then the display will be weird since its trying to output 16-bit colour to a 32-bit colour framebuffer.
It requires only a small modification to get the recovery working in 32-bit colour though, so if you do get it to boot then I can help you get it fixed up.
franciscofranco said:
You probably need to change your anyKernel script as well to use /boot instead of /cust for the boot.img, if I did not misunderstood.
Click to expand...
Click to collapse
Ah thanks yeah I will need to change it. I'll try and get it done now, the new version of AnyKernel should be compatible both with the new and old versions of recovery.
Edit: Modified version of AnyKernel is on my github. I haven't tried it out but it should work fine on new and old recoveries.
This recovery is already rock’in rolling in my machine.
Why when we use most of the option we have endless line of “NO” and then the option to execute in the middle of them.
Example:
No
No
NO
No
Wipe davilk
No
No
No
By the way, tried to flash new Ffranco kernel several times and in recovery it’s done successfully but when I enter the systems and go to settings it still showing the previous kernel...
Druida69 said:
This recovery is already rock’in rolling in my machine.
Why when we use most of the option we have endless line of “NO” and then the option to execute in the middle of them.
Example:
No
No
NO
No
Wipe davilk
No
No
No
By the way, tried to flash new Ffranco kernel several times and in recovery it’s done successfully but when I enter the systems and go to settings it still showing the previous kernel...
Click to expand...
Click to collapse
its there to avoid mistakes i think
and to lead user to actually read whats written there
will not comment that....
Stockwell, been making tests and apparently is not just the last Francisco's kernel that isn't working with this new recovery. All previous ones don’t work either.
I have reverted to previous recovery until this is fixed or until I know if I'm doing something wrong
stockwell said:
The recovery kernel is the kernel I use for Miui, but with the framebuffer set to 16-bit colour.
There's nothing specifically added to the kernel to make it work with the recovery other than that, but if you do manage to get it to boot on your pro then the display will be weird since its trying to output 16-bit colour to a 32-bit colour framebuffer.
It requires only a small modification to get the recovery working in 32-bit colour though, so if you do get it to boot then I can help you get it fixed up.
Ah thanks yeah I will need to change it. I'll try and get it done now, the new version of AnyKernel should be compatible both with the new and old versions of recovery.
Edit: Modified version of AnyKernel is on my github. I haven't tried it out but it should work fine on new and old recoveries.
Click to expand...
Click to collapse
Thanks stockwell, will try later.
I was able to brick my phone after i've restored from backup.
So please be aware with this version of CWM.
Brgds,
S.
mesnati said:
I was able to brick my phone after i've restored from backup.
So please be aware with this version of CWM.
Brgds,
S.
Click to expand...
Click to collapse
What ?
stockwell said:
I take no responsibility for any harm that comes to your phone as a result of applying this mod.
So after months of expecting Jacob to get us ROM manager support I got fed up and decided to do it myself.
Basically the main hurdles preventing this previously were that we were reliant on using the init from the Huawei recovery, and also the offmode charge code was a direct modification to the recovery source. I spent quite a bit of time yesterday and today and have overcome these problems, and the result should hopefully be rom manager support in the near future.
What's different?
Instead of using /cust_backup it now uses /boot. This doesn't affect rom installations but it WILL affect backups made from an older recovery as it won't restore the cust image (its looking for boot now). If you want to go back to one of these backups from the new recovery you can go to the backup location, rename cust.img to boot.img, and also edit nandroid.md5 so that it says boot.img instead of cust.img. The backup will then restore but just be aware that it will also revert to the recovery you had when the backup was made.
Haptic feedback is enabled on touch keys, and the keypad backlight is turned on
When in offmode charging you need to pull the USB cable out and let it turn off before booting, you can't just press the power button to turn it on.
Backups are compressed
It's blue.
Download:
5.0.2.3: http://code.google.com/p/u8800-miui/downloads/detail?name=CWM Recovery 5.0.2.3-new_install.zip
Installation Instructions:
Unplug any usb connection and turn the phone completely off
Whilst holding both the volume + and volume - keys hold the power button to turn the device on. Let go when you see a pink/purple screen.
Attach the usb cable to your computer and wait until a few usb mass storage devices are detected and mounted. Look for one that has just one directory called 'image' in it. Navigate into this directory and you'll see recovery.img etc.
(optional) Rename recovery.img to recovery_backup.img
copy the new recovery.img to image, unmount the mass storage device (safely remove in windows) and then pull the battery out to turn the phone off.
Hold volume + and power to boot to recovery.
Source:
https://github.com/stockwell/android_device_huawei_u8800
(Note that the device config isn't properly setup for anything other than the recovery, so don't expect to be able to use it for a fully working CM7 build)
Click to expand...
Click to collapse
Why mount /cust on /boot?
It has no functional purpose and just ****s it up.
"So after months of expecting Jacob to get us ROM manager support I got fed up and decided to do it myself. "
The lack of a ROM Manager release is due to me trying to avoid using the huawei init where I can, because it's full of stupid hacks.
Maybe after months of users complaining at me to do something I don't have to do, I might just get fed up and decide not to do it anymore.
I've said it before and I'll say it again, this is why I hate xda.
Current recovery works perfectly for what I use it, any reason to change? Does this enable anything special? Reading the "what's different" I don't see any reason why but i could be missing something.
Edit, Have no idea who this guy Jacob is but from a few posts I've seen from him, all he does is whine. Dude buy a stuffed animal or something.
POST 1 today
"If you want to go back to one of these backups from the new recovery you can go to the backup location, rename cust.img to boot.img, and also edit nandroid.md5 so that it says boot.img instead of cust.img. The backup will then restore but just be aware that it will also revert to the recovery you had when the backup was made."
For me is not pratical to change to 5.0.2.3. I have 12 Backups various. When I make a Restore I return to 4.0.1.5 and the renamed Recovery_backup.img on internal data storage are deleted. I continue whit 4.0.1.5.
Thanks.
........................................
EDIT: I made this and work (GENO method), no pink screen :
To install (you need root):
1. Backup /cust_backup/image/recovery.img
2. Download, extract and place the recovery.img into /cust_backup/image/
3. Done.
To go to recovery:
1. Power off
2. Hold Vol+ and Power buttons to power on (hold both buttons UNTIL you see the recovery)
HCDR.Jacob said:
Why mount /cust on /boot?
It has no functional purpose and just ****s it up.
"So after months of expecting Jacob to get us ROM manager support I got fed up and decided to do it myself. "
The lack of a ROM Manager release is due to me trying to avoid using the huawei init where I can, because it's full of stupid hacks.
Maybe after months of users complaining at me to do something I don't have to do, I might just get fed up and decide not to do it anymore.
I've said it before and I'll say it again, this is why I hate xda.
Click to expand...
Click to collapse
I changed it to /boot because first off I hate calling it /cust (it should be /cust_backup anyway), and second off because (unless I'm missing something, which I may well be) nandroid won't back it up without modification unless it's called boot. It doesn't **** anything up except for anykernel(which I fixed) because all of our rom install scripts explicitly mount mmcblk0p1 to /cust rather than just trying to mount cust and letting the fstab do the rest.
As for the rest of it, have a look at my github and my post. I'm not using the Huawei init and I'm not doing any modifications to the recovery source to achieve offmode charging. This port is fully functional and should be completely compatible with rom manager.
You're not obligated to do anything, I'm merely stating that ages ago you took money from people on this forum to buy a phone, and announced that you would be porting CM7 and getting official CWM recovery, so I expected rom manager support to come. Months later we have nothing, so I did it myself.
swayjd said:
Current recovery works perfectly for what I use it, any reason to change? Does this enable anything special? Reading the "what's different" I don't see any reason why but i could be missing something.
Edit, Have no idea who this guy Jacob is but from a few posts I've seen from him, all he does is whine. Dude buy a stuffed animal or something.
Click to expand...
Click to collapse
There's no reason to change to this really, it's more of a 'pre-release' to make sure it works without any problems. If/when koush merges it into rom manager though this will be the version that's incorporated so I needed to make sure it didn't have any huge problems I missed.
Druida69 said:
will not comment that....
Stockwell, been making tests and apparently is not just the last Francisco's kernel that isn't working with this new recovery. All previous ones don’t work either.
I have reverted to previous recovery until this is fixed or until I know if I'm doing something wrong
Click to expand...
Click to collapse
His new version should work now, AnyKernel (the method used to flash the kernel to the phone) needed a small modification to make it compatible with new and old version of recovery.
I was using my N73G at home this evening and it spontaneously rebooted to the Google splash screen... and stayed there for well over 5 minutes. I tried long pressing power to reboot again, and it went back to the same screen.
TWRP is installed, and I am able to get into that. I tried wiping cache and dalvik, and it booted straight back to the splash screen again, solid for 3 minutes before I went back into TWRP. In the file manager my files all appear to be safe and sound. I am currently running a nandroid backup before I futz with it any further. TWRP has not given me any errors over the course of the backup.
I should note that I have had some trouble connecting to TWRP over ADB although I can use ADB when booted into the OS. So if I need to go fishing for files over USB, I hope I won't come up empty. If necessary I could try flashing CWM recovery instead, as I may be able to get my files more easily that way.
Anyway, ideas are welcome. I was running a bake of the Modaco custom ROM, and the zip for that ROM is still on the device, so I was thinking I might try reflashing that. But first I should try and get my nandroid off the slab.
As fortune would have it, I have already ordered an RMA device swap due to issues with the speaker blowing out. So if I fail to resuscitate it, help is already on the way. But I would like my tab to work again by the time I go back to work Monday
Update: Figured out the ADB recovery driver problem. Nandroid backup was successful. I'm now pulling the backup image to my desktop. Will try a ROM reflash next.
UPDATE UPDATE: The weirdest thing. I noticed while it was plugged into my machine, still stuck on the Google boot logo, that I was able to see the tab in ADB devices. So I typed in adb logcat and found some message about /system/xbin/busybox missing.
I browsed with ADB shell and found there is a busybox in /system/bin. So I did ADB remount, and then copied busybox from bin to xbin. Entered a reboot command, and bam! Five seconds on the Google splash, and then right to the booting X.
Why in the world would this have happened... maybe the busybox installer app got an upgrade and botched an attempt to upgrade busybox?
cmstlist said:
UPDATE UPDATE: The weirdest thing. I noticed while it was plugged into my machine, still stuck on the Google boot logo, that I was able to see the tab in ADB devices.
Click to expand...
Click to collapse
The adb daemon - adbd - is started by init as a service so long as you have previously enabled adb debugging. So, it happens before the whole android reboot sequence kicks off (checking that all .apks without odex files have up-to-date .dex entries in dalvik cache, permission checks, etc.) You can access it on devices that are "stuck" in the late stage of booting.
TWRP - for better or worse - does not claim the same USB vid/pid ID that is used by the N7's ADB facility, even though the exact same driver can be used for either adb mode ... so long as you manually went into the driver install package and add the "universal" vid/pid values used by TWRP to the driver's .inf file. I think this is done simply to minimize the effort keeping up with new device identifiers by the TWRP team. It does create the impression that separate drivers are needed - but only because neither of the two drivers (Google vs. Universal) have the "other's" vid/pid pair listed as matching devices in their .inf files.
Anyhow, you got it all sorted out - congrats.
Thanks! I had been worried maybe the whole file system was corrupted, so in comparison this was a relief.
Sent from my Galaxy Nexus using Tapatalk 2
Hi guys!
I have made a serious mistake, and I feel so stupid! I was wondering if any of you awesome people at XDA would be able to save me.
I have an LG G2 vs980 Lollipop 5.0.2
So, all I wanted to do was change my startup screen to get rid of that boring LG logo and replace it with something neater. I went over to Google and found a guide on how to do this, and followed the steps 1 by 1. Everything actually worked out perfectly, but it wasn't until after I was locked out of my phone that I realized that I had used a startup image that was not compatible with my LG G2! (Total face palm!). Now, whenever I power my phone, it flashes that "neat" image that I replaced the stock one with - before the screen goes completely blank and I cannot do anything at all. That's not good!
So my question is this - Is there a way I can access my system folder without having access to my phone? I know EXACTLY what file I need to remove/edit to solve this problem! In fact, that is what is frustrating me the most. It's not some random error message out of the blue that I know nothing about. I know exactly what the problem is, I just don't know if I have access to the solution. I just really hope I don't have to wipe everything back to stock all because of a lousy startup image.
Is there a way to access the system folder on my phone so I can remove the bad file and replace it with the stock image so I can get my phone working again? If anybody can help me figure out the best method to solve this issue, I would be forever grateful! Thank you guys so much in advance!
Much appreciative,
Terri (Psyintz)
If you are rooted I assume you have also TWRP or CWM installed. TWRP has an integrated file explorer so you can delete these files. And you can try to push new files through ADB. Just google
android adb push while in recovery
Good luck!
Jan Philipp said:
If you are rooted I assume you have also TWRP or CWM installed. TWRP has an integrated file explorer so you can delete these files. And you can try to push new files through ADB. Just google
android adb push while in recovery
Good luck!
Click to expand...
Click to collapse
But I don't remember installing TWRP or CWM during the process. The guide I used to change my startup image just had me use some sort of "one-click rooting" application, before detailing which files I needed to backup and exchange in order to change my startup image. So I'm not very confident in the fact that I have either of those things installed, which makes me afraid to try and click on my factory reset button.
After finding a guide on installing TWRP via this ADP thing, I seem to get stuck early on in the process. When it asks me to open a command prompt and type "adb reboot bootloader" it returns the message "error: device (null) not found." I am not sure why it is not finding my device. Is it because my phone does not boot, so it is not able to connect to it?
I am beginning to lose faith in there being an option to solve this problem without just performing a factory reset, and losing all of my data. If I were to take this route, can I just use my phone's built-in option? By holding the correct keys, and then choosing to wipe all my data and return to stock?