Ok, so this happened...
I was editting my build.prop so I could get apps that were unusable with my phone. So i downloaded the build.prop for the device that could run it, but instead of just changing the Moto G one, I replaced it on accident!
Every time I try to reboot it, the screen pops up for a little bit, but then fades to a pink screen then to black. I can't access the main part of my phone at all! I can still get into recovery mode, however. The main issue is the build.prop file, right?
I have a backup build.prop on my computer, but when I try to use adb to put in in, it doesn't recognize it. The phone also can't hold onto and battery charge anymore, either.
I need help to put my backup build.prop in. Please and thank you!
EDIT: I found out I can still sideload things, but I don't know if it will fix it.
1. Download TWRP 2.8.4.0 from HERE. and place it in the folder where you have ADB/Fastboot.
2. Try booting into the bootloader, then in your Fastboot Window, type fastboot flash recovery [recovery.img] where recovery.img is the name of the TWRP file.
3. You should now have flashed TWRP on your phone. Next, in the Bootloader, navigate down to RECOVERY using VOL DOWN then select it using VOL UP
4. In TWRP, go to Mount. Then, type in adb push file /sdcard/ where file is the name of the build.prop file
4. In TWRP, go to advanced, then select File Manager. Navigate to the folder that contains Build.prop and delete the file.
5. In the file manager, navigate to the /sdcard/ directory and copy the build.prop file to wherever it should be.
Let me know how that works out for you
Related
Hi,
Is there any method to keep using stock Rom with root and do not wipe the data?
Thanks
Root nexus s rom 2.3.6
Ehi!
I'm also looking for that!!
I just got the nexus S whit the 2.3.6 rom and I want to root it, but I haven't find any answer online
someone can help us??
thanks!
http://forum.xda-developers.com/showthread.php?t=1007782 read this topic page1 and page 49 very important...
please click thanks button
- -
easiest way
just install from recovery this file
if i didn't upload wrong file...
does not work for me, signature verification failed...
here is the link for your question:
http://forum.xda-developers.com/showthread.php?t=935819
the link does not work for 2.3.6 as google fixed the issue on fasboot boot...
---------- Post added at 04:09 PM ---------- Previous post was at 04:01 PM ----------
Damned what a crap...
Has been two days looking around to find a solution, and seems not possible for the 2.3.6...
What a shame google to pretend having open source system and having no way to unlock your device without loosing your data as
- The data is wiped as you unlock the device.
- To fu**ing backup the data you need to have a fu**ing unlocked device.
WTF, I just got it in my ass..
If someone at last know a way....
New Part 2 - Does NOT wipe everything - Keeps a locked bootloader
1. Make sure Part 1 is completed.
2. Make sure you have downloaded the Clockwork Recovery file and the Superuser file.
3. Move the Clockwork Recovery file to your tools folder within the Android SDK folder, and rename it to recovery.img (for simplicity).
4. Connect your Nexus S via USB to your computer and mount it as USB storage. Copy across the Superuser file to the top level of your sdcard. (So the first window you see, not in any other folders. The sdcard is just where all the files are stored, don't worry about it too much for now).
5. We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don't worry about this!). Follow along with any other instructions. You should be set now.
6. With the latest SDK version, some tools have been relocated to another directory, so we need to make a copy and move them back. Navigate to the directory where you unzipped the Android SDK file in part 1. Inside it, go to the platform-tools folder, and copy both AdbWinApi.dll and AdbWinUsbApi.dll. Go back to the main Android SDK directory and find the tools folder. Paste these two files in there, and we are all ready to use 'fastboot boot' (the boot image command) now.
7. Open a command prompt window (Start > Run > cmd.exe).
8. Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) 'cd c:\*YOUR SDK*\tools'.
9. Make sure your Nexus S is still in the Bootloader Interface (refer to step 9, part 1 of it isn't).
10. We now need to use the 'fastboot boot' command to load Clockwork Recovery onto our Nexus S. In the command prompt, type in the following (but without the quotes, as always) 'fastboot boot recovery.img'
11. Once you are in Clockwork Recovery (it may take a couple of tries, don't panic, just redownload Clockwork Recovery, and complete steps 3 and 10, part 2) it should look something like this:
12. Using the Volume buttons and Power button, select install zip from sdcard.
13. Select choose zip from sdcard.
14. Select the su-version#-signed.zip file you downloaded earlier and apply it.
15. Select yes (there are lots of nos).
16. Confirm it says something like this: install from sdcard complete
17. Select Go Back.
18. Select Reboot.
19. Done! You should still have all your data present on your phone, and have root access!
all credits goes to Jonathon Grigg
plipness said:
New Part 2 - Does NOT wipe everything - Keeps a locked bootloader
1. Make sure Part 1 is completed.
2. Make sure you have downloaded the Clockwork Recovery file and the Superuser file.
3. Move the Clockwork Recovery file to your tools folder within the Android SDK folder, and rename it to recovery.img (for simplicity).
4. Connect your Nexus S via USB to your computer and mount it as USB storage. Copy across the Superuser file to the top level of your sdcard. (So the first window you see, not in any other folders. The sdcard is just where all the files are stored, don't worry about it too much for now).
5. We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don't worry about this!). Follow along with any other instructions. You should be set now.
6. With the latest SDK version, some tools have been relocated to another directory, so we need to make a copy and move them back. Navigate to the directory where you unzipped the Android SDK file in part 1. Inside it, go to the platform-tools folder, and copy both AdbWinApi.dll and AdbWinUsbApi.dll. Go back to the main Android SDK directory and find the tools folder. Paste these two files in there, and we are all ready to use 'fastboot boot' (the boot image command) now.
7. Open a command prompt window (Start > Run > cmd.exe).
8. Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) 'cd c:\*YOUR SDK*\tools'.
9. Make sure your Nexus S is still in the Bootloader Interface (refer to step 9, part 1 of it isn't).
10. We now need to use the 'fastboot boot' command to load Clockwork Recovery onto our Nexus S. In the command prompt, type in the following (but without the quotes, as always) 'fastboot boot recovery.img'
11. Once you are in Clockwork Recovery (it may take a couple of tries, don't panic, just redownload Clockwork Recovery, and complete steps 3 and 10, part 2) it should look something like this:
12. Using the Volume buttons and Power button, select install zip from sdcard.
13. Select choose zip from sdcard.
14. Select the su-version#-signed.zip file you downloaded earlier and apply it.
15. Select yes (there are lots of nos).
16. Confirm it says something like this: install from sdcard complete
17. Select Go Back.
18. Select Reboot.
19. Done! You should still have all your data present on your phone, and have root access!
all credits goes to Jonathon Grigg
Click to expand...
Click to collapse
As said before, does not work anymore for 2.3.6 as google has fixed this exploit...
The OTA Update:
Your phone will download the OTA update as a zip file in the Download folder.
------------------------------------
The Problem:
------- quote by jackdowsan -------
I downloaded the file, placed it in my zip, went to cwm recovery and tried intall zip from sd card, it failed saying something about signature verification....
What are my options? I am on stock with root and custom recovery..
------------------------------------
The Solution:
I was in the same situation and I've resolved it by extracting the original OTA recovery.img from the OTA Update zip and flashed it through fastboot. Then I've updated the system software successfully and flashed back the ClockworkMod recovery.
If somebody needs a step by step guide, please see below:
WARNING! You may loose your root access after this procedure. Do not worry. You can root it again the same way you did before, or much easily by using the application Voodoo OTA RootKeeper (free, no ads, on the market). Just install it before you start and then again after the process to restore your root access.
1. Send the system software update archive located in your phone's download folder to your PC. Open it and inside you'll find another archive - firmware.zip. Open it and extract the original OTA recovery.img. Put it in the same folder with the fastboot.exe file.
2. On your HTC One X, enable USB debugging by going to Menu>>Settings>>Applications>>Development>>USB debugging and check-mark the box.
3. Turn OFF your smartphone using the Power button.
4. Press and hold Volume DOWN button and then immediately press Power button. Select Fastboot mode from the menu that appears on the screen.
5. Connect your phone to your PC using the USB cable that came with it.
6. Open a Command Prompt Window on your Desktop, go to the folder with your fastboot.exe and then type in the following commands. It will flash recovery on your phone.
fastboot flash recovery recovery.img
7. When the flashing is done, simply enter the following command into Command Prompt Window to reboot your phone.
fastboot reboot
8. You have successfully installed the original OTA Recovery on your HTC One X. Start the phone update again and it'll successfully update to 1.29.401.11. Your job is done!
9. Once everything is completed you can put ClockworkMod Recovery again by following the steps above but instead of using the OTA recovery.img file use the ClockworkMod recovery.img.
Cheers,
P.S. Sorry if this thread is not in the right place. Please move it if it's necessary. I'm still new here
Thanks a ton, would try this today
Just tried it, something did not go right, firtly, I had a little different update file then yours, I had
OTA_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7-1.28.401.9_release_259295wbmgoi0p47wgsfl6
which is like 34.5mb or something....
I extracted it and got recovery.img from firmware.zip and followed your guide, but after fastboot reboot, when I entered my phone, I still see it on 1.28.401.9
what could be wrong? I saw the fastboot recovery command executed just fine...what else can it be?
Thanks!
This solution should work on any OTA phone with custom recovery and root access.
So you flashed the OTA recovery.img, restarted the phone and in the normal mode you started the System Software update, right? My phone installed the update with no problems and it was showing the new version. The thing I lost was the root access but I explained how to gain it back.
If an experienced developer is reading this thread they may be able to advise us why the solution did not work with your phone.
i have a slight problem. i grabbed the ubuntu touch alpha and went in to recovery, loaded it (according to thread instructions) but ended up with a bootloop.
in the end i thought "lets just put another rom back on for now" and then realised i had deleted the other rom from the sdcard! so i'm stuck with it not booting in to ubuntu, and not able to get another rom on as it doesn't boot in.
can i connect to the internal sdcard area myself by plugging the usb in to the pc or something?
i have twrp loaded as recovery
thanks
ah, TWRP adb sideload to the rescue!
problem
my problem is stuck in boot screen after i did super wipe full what should i do? i have cwm 5.5.0.4. i try flash from sd put it says no files found
partti86 said:
my problem is stuck in boot screen after i did super wipe full what should i do? i have cwm 5.5.0.4. i try flash from sd put it says no files found
Click to expand...
Click to collapse
The issue, Superwipe wipes the internal /sdcard/ and also this is where it flashes from.
You need to boot to recovery and then use ADB to push files to the sdcard.
If you have never used ADB, it can be a bit daunting.
First, you need adb from the Android SDK. It is a big file for the few you need. I have a copy of the relevant ADB files here: https://db.tt/b9dQ6xzp
Unzip this to c:\adb folder on windows. If you are using Linux, it should already have adb in the /usr/bin/ folder.
Next, you need the Universal Naked Drivers: http://forum.xda-developers.com/attachment.php?attachmentid=1934814&d=1367674531
Unzip these to c:\universal_naked_drivers
Boot to CWM and then plug in your USB cable. It should show a new device found. It may find 2, an MTP and then there should be another either Unknown device or an Android ADB device. Right click and update the driver. Be sure to search for driver, then tell it you want to pick from a list. Hit the Have Disk button and then hit the browse button and browse to c:\universal_naked_drivers and hit OK. It should show you a driver to select and hit OK. If you are using Win 8, there is an additional step that is required to used non-signed drivers.
Once the driver is updated, download the zip file you want to flash on your PC. I assume it is a ROM.zip file for this example. Place this file in the c:\adb folder and call it ROM.zip (can be named something else, but this is what we will use for this example).
Now, open a command prompt and execute the following:
Code:
> [B]c:[/B]
c:\> [B]cd c:\adb[/B]
c:\adb> [B]adb devices[/B]
It will probably say some messages about the daemon is not running, restarting adb.
Then it should show a list. There should be some numbers followed by "recovery"
If no devices are shown, check that your ADB device is showing in the Device Manager.
Once you see it in the adb devices list, continue:
Code:
c:\adb> [B]adb push ROM.zip /sdcard/[/B]
successfully pushed xxx bytes
c:\adb>
At this point you should now see the ROM.zip file on the internal storage in CWM to allow you to install it.
Choose to install the file then reboot (not to recovery). You have to let it flash the file (progress bar will show). Once the screen goes black and the progress bar disappears, it should now boot to your ROM..
If your ROM requires a custom kernel and/or GAPPS to be flashed, use the same procedure to push your kernel.zip and GAPPS.zip to the /sdcard/ directory.
mk2media said:
ah, TWRP adb sideload to the rescue!
Click to expand...
Click to collapse
Can you explain what you did please? what is adb sideload?
Hello all.
I know there are many threads of this kind but nothing worked for me. So Please help!
I unlocked my bootloader, installed TWRP and flashed SuperSU binaries. Everything was working fine.
Then I wanted to flash cm12 nightly. So i downloaded the zip file and also the Gaaps.zip file. I transfered them to the phone and booted to recovery.
1. Then instead of wiping cache i wiped the whole system i.e factory data reset. So then i tried reboot it says NO OS INSTALLED! do you want to continue? After that "Your phone is not rooted. Install SuperSU? As i don't have the SuperSU files so it just reboots to the bootscreen and stays there. I can go to the recovery and fastboot mode.
2. then i booted to recovery and went to adb sideload. I have the ADB files on my desktop and pasted the ROM.zip file to the folder.
3. Then i tried the command adb sideload ROM.zip with my phone connected. But then a lot of coding appears in the cmd window and phone stays at adb sideload.
4. When i connect my phone to my pc in recovery It comes up as "One" in the disk drives. I open it and it has a folder named TWRP and inside thata file. Nothing else. The good thing is I have a nandroid backup of my device when it had SuperSU binaries.
*the "One disappears when I go to ADB sideload in my phone*
So can I transfer the backup to my phone in a separate folder named "Backups" and install it via restore in TWRP? Or do have to do something else?
Please help! Please! :crying:
You're already getting help for this here:
http://forum.xda-developers.com/showthread.php?t=3044924
Transmitted via Bacon
For people who converted over to GPE and are having a hard time installing most roms, I have a fairly easy fix for you. The problem is with the partition table. I specifically did this with 1032 falcon assuming you already have recovery installed.
1. You need mfastbootv2.zip from here: http://www.mediafire.com/download/14p0x9cb34s2kqj/mfastboot-v2.zip
2. You will also need gptfix.zip from here: http://forum.xda-developers.com/moto-g/general/fix-android-lollipop-ota-gpe-stuck-t2970842
3. Extract mfastbootv2.zip to a folder.
4. Extract gptfix.zip to the mfastbootv2 folder you just created.
5. Put your phone in bootloader mode by holding the power and down buttons for 5 seconds until you see the menu then hook your phone to your computer via usb.
6. Now open the folder you extracted gptfix.zip and mfastbootv2 to, hold shift on the keyboard, right click on a blank area in the folder and choose open command window here.
7. Now type "mfastboot flash partition gpt.bin" without quotes. Shouldn't take long. A second or two.
8. Once completed reboot to recovery and format data and system (may get some errors) then reboot recovery so twrp can create a folder to put your rom in.
9. With my phone hooked to the computer via usb, i mounted usb in twrp then copied my rom to the twrp folder using windows explorer and flashed a rom that would never flash before!
Hope this helps. I know this info was already talked about but i found it was split up and unclear.