Database Users

Did I brick my phone? Rebooted with no build.prop

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

Stock bootloader

Anyone know where/how to get the t mobile bootloader from?
I've trier to extract the Rom.zip from ruu but it doesn't work this maybe cos I'm crap. Instructions welcome
even the most talented devs were noobs once... so there's hope for the rest of us!

Any one? Help would be great here guys
ive tried copying rom.zip from the ruu to the memory card but clockwork keeps aborting saying (bad) wether i have signature verify on or off, ive also tried renaming it to update.zip but get the same. i also cant open the zip folder on my laptop tho i can extract the iso files from it, ive also tried putting these in another zip folder but still no joy. any ideas?
dangling in the wind here guys :~(
Sent from my HTC Wildfire using XDA App

Ok, so iv done tonnes of searching of the whole xda site and Google (which just kept leading me back here ) missing out all my trial n errors n sticking to the nearest solution iv found in my quest to re-brand my phone and have it back running the stock t mobile 2.1 (note: I'm running a rooted generic 2.1 Not ota or ruu froyo)
1) started ruu
2) opened %temp% on windows and copied rom.zip to machine and then to SDcard
3) renamed Rom.zip to PC49DIAZ (because that's was the name bootloader would search for everytime b4 I could go into recovery)
4) went into fastboot
-fastboot then found the file and came up with 'checking sd pc49diaz' and blue bar in top right corner appeared and filled up. Blue bar then went and 'checking sd pc49diaz' was left on screen.
-it then flashed some text really quick (I only saw the word 'data')
And that was it. I rebooted and NOTHING
What am I doing wrong? Surely some one can help? Devs??
even the most talented devs were noobs once... so there's hope for the rest of us!

[Q] Help with adb pushing to KF sdcard

Ok folks, I believe I have read 30 or 40 threads on this site and 20 or so on other sites regarding pushing to sdcard and I think it's ok I now ask for help here.
I have rooted my Kindle Fire successfully
I installed android market successfully
When I saw the people saying turn off wifi to avoid getting the 6.2.1 update I did so.
Now I want to install cm7 on my kindle so I don't have to worry about updates anymore. Ok, now onto the problem.
Downloaded whistlestops update-wipeall.zip and put it into C:\Program Files <x86>\android\android-sdk\platform-tools
Made sure device was fully powered and plugged into Windows 7 computer
went to command prompt and changed directories to C:\Program Files <x86>\android\android-sdk\platform-tools
Ran cmd prompt
adb push update-wipeall.zip /sdcard/
and problem is I get failed to copy 'update-wipeall.zip' to '/sdcard//update-wipeall.zip': Permission
denied
I have checked to make sure I am rooted and still nothing. at this point after reading and banging my head against wall I could really use some help from community.
p.s. apologies for repost not sure how planets aligned for previous to end up in Lenovo forum

I was having the same issue. I ended up installing TWRP (which took me all night to do) and flashing CM7 with that.

I have twrp installed but need to get the cm7 file to the kindle to flash. Heck I even went into twrp and did a full backup just to make sure I could restore if I needed.
So how did you get cm7 onto sdcard to flash or am I just hopelessly lost?

To push update.zip you must unmount kindle from your computer (right click on kindle disk in "my computer" and unmount/unplug)
and again, open command prompt
adb kill-server
adb devices
...bla bla bla

Thanks Kisman that did the trick.
Now I have a new set of problems but original was solved.
I went into TWRP did mount usb storage
Copied image over to kindle remounted
Went to install. There is my wonderful file, clicked the file, flash, even did the wipe as suggested in inital instructions (Thanks Whistlestop) rebooted and well nothing, I got the yellow triangle, it goes away to be replaced by nothing.
Rebooted again into twrp and restored backup (thank you twrp team)
back to square one, calling it a night now, maybe fresh eyes in morning will turn up something.

Moose66 I used this tutorial to install CM7 - and I suggest you to do the same thing
http://www.kindlefirewire.com/2011/12/06/how-to-install-cyanogenmod-7-on-kindle-fire-tutorial-video/
I copied update.zip file from this topic:
http://forum.xda-developers.com/showthread.php?t=1390773
From this topic I copied: log, last_log, stockrecovery.img and updaterecovery.img:
http://forum.xda-developers.com/showthread.php?t=1368012
Be sure you copied log and last_log without .txt extention. My firefox added extention .txt automatically
sorry for my English, good luck

I followed the whistlestop (thanks again) instructions using the first choice for unmodded roms, update-wipeall.zip to the letter. It says everything was successful but on reboot I get the yellow triangle like I should and then a backlit screen and nothing else. I waited 5 minutes and tried rebooting 3 or 4 times before I used twrp to restore the previous version.
I am not sure what I am doing wrong at this point.
p.s. appreciate all the community help I have received thus far

Write here step by step what you did exactly

[SOLVED] [Q] [Help] stuck in boot loop after using a build.prop editor

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).

Question Nothing Phone (1) Brick Recovery lost and "No such file or directory"

So guys,
I got my nothing phone 1 three days ago and I absolutely love it. Then yesterday I tried to root it. I thought it would be easy since I´ve rooted three phones already (older ones like oneplus 2)
I unlocked the Bootloader and it worked fine. Then I researched how to root with magisk and found out that you dont get the boot.img anymore just like that and have to "payload-dump" i tried this for around two hours with every method i could find but it just wouldnt work.
Then I found an already patched boot file and flashed directly out of joy. Then the bootloop hits the Phone.
I forgot to check the versions and the boot.img was version 1.5.3 and my phone was already running newest 1.5.4
fastboot is still totally fine and I can use every command
I cant access the recovery. When I do fastboot reboot recovery it just gets back into bootloop
I thought okay it shouldnt be that hard to flash the stock image but I was so wrong.
Everytime I try to flash something it says "fastboot: error: cannot load '.\images\boot.img': No such file or directory"
and I really dont know how to correct that.
Read something about fastbootd but when I do "fastboot reboot fastboot" it gets back into a bootloop"
I would really appreciate help, since I need this phone for work in some time and of course would reward i anyone can help me.
ps yeah I know it was stupid to do this on my future work phone but I really thought I knew what I was doing
the complete output I get from the phone 1 tool by sh4tteredd is in the screenshots since I dont know how to extract it as a text
but I think the main problem is that it always says "No such file or directory"
also!: it also says "No such file or directory" when I try to manually flash command by command or a "Flash_all.bat"

Try to Flash the stock 1.5.4 stock boot image.... from fastboot... and let me know what happened.. this link might be help you https://forum.xda-developers.com/t/nothing-phone-1-rom-ota-nothing-os-repo-of-nothing-os.4464039/

Make sure use Android Platforms 33.0.3 since the latest verson is riddled with bugs.

soltion:
honestly idk, but i tried flashing an very old stock rom (from when roms were still split and i think I even used the wrong one) but that seemed to brake the system so hard that i eventually was able to just flash the newest stock rom and even root it with a patched file I found online (this time the right verion of course haha)