Build.prop, stuck in boot screen - Verizon Motorola Droid Turbo Q&A, Help & Troublesh

Hello guys, i need a little help.
I was looking for some tutorial to unlock dev cameras on my xt1225. I found one tutorial and he said to edit Build.prop, i'm noob at this, so I downloaded a file manager and entered in /system/, copied build.prop for backup, and edited the original build.prop. I restarted my phone and now i'm stuck in the boot screen.
I don't know for what reason but ADB (properly configured) does not show any device connected to the PC so I can't use the commands adb pull and adb push.
I have tried copy the backup of build.prop and overwrite the modified one, but no sucess (I did it in TWRP file manager)
I'm using XT1225 5.0.2 Stock ROM.
Edit: So, i tried to change his permissions (or think that i tried, in twrp filme manager with chmod command,), now the phone runs the boot animation and turn black, before he did not do it, before he just stuck in the white screen with motorola logo. (Tried chmod 644, 755, 777)
Sorry for bad english.

Neblue said:
Hello guys, i need a little help.
I was looking for some tutorial to unlock dev cameras on my xt1225. I found one tutorial and he said to edit Build.prop, i'm noob at this, so I downloaded a file manager and entered in /system/, copied build.prop for backup, and edited the original build.prop. I restarted my phone and now i'm stuck in the boot screen.
I don't know for what reason but ADB (properly configured) does not show any device connected to the PC so I can't use the commands adb pull and adb push.
I have tried copy the backup of build.prop and overwrite the modified one, but no sucess (I did it in TWRP file manager)
I'm using XT1225 5.0.2 Stock ROM.
Edit: So, i tried to change his permissions (or think that i tried, in twrp filme manager with chmod command,), now the phone runs the boot animation and turn black, before he did not do it, before he just stuck in the white screen with motorola logo. (Tried chmod 644, 755, 777)
Sorry for bad english.
Click to expand...
Click to collapse
I don't know about the chmod command, but the TWRP "Fix Permissions" does not work with our current (old) version of TWRP. It just messes up the phone.
1) since you have TWRP, did you make a back-up? If so, restore that. Problem solved.
(If no back-up, why not? That's one of the reasons we use TWRP, so we can restore a good backup when we screw something up.)
2) If you have TWRP, that means your bootloader is unlocked. GOOD.
Boot back into recovery, reflash your ROM. Problem solved.
Reboot, make sure everything is OK, then make a TWRP back-up!
EDIT: OOPS. I see you are using stock 5.0.2, not custom ROM. OK, I hope you made a backup. See #1.
There may be other solutions but all the ones I find seem to involve pushing new files to your phone and you say you can't do that...
______
Also in our version of TWRP, if you wipe cache do NOT attempt it from the "install" prompt (There's an option there to wipe cache. Ignore it.) Only wipe Cache from the "Wipe" section/Advanced Wipe/checkmark Cache and Dalvik Cache. (Even though we use ART, habits die hard.)

OK, I restored a backup following your thread, but before, searching for a solution, I formated the cache/data partition from f2fs to ext4 (so dumb), there's a way to undo it? There's no f2fs wipe option in twrp, I think I'll need to wait to a new version of twrp? Or flashing with rsd lite will do it?
Everything is working fine.
Thanks for your answer.
Sent from my XT1225 using XDA Free mobile app

Neblue said:
OK, I restored a backup following your thread,
Everything is working fine.
Thanks for your answer.
Click to expand...
Click to collapse
Glad your phone is back up and running! Aren't you glad you made a back-up?
Not sure about the F2Fs stuff. I haven't messed with it.
Yes, I agree we need a newer version of TWRP. I would gladly donate money toward to the developer!

Related

How to Install 4.2 images, keep root and all data

**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..
jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.
mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options
You have .bat file in the package.
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions
I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?
I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app
mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app
can I install image-nakasi-jop40c.zip directly without upgrading bootloader?
Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.
Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!

Help - Rooted, failed installing Busybox, now stuck while booting

Hello guys, I really need your help here.
I will try to explain the situation as detailed as possible, if you still need any info, just ask.
I own a HTC One, carrier locked (Base) and not the sprint version, whatever that is.
Yesterday I unlocked the bootloader and rooted the device, following a tutorial by a german tech site. It all went well, everything worked and I was happy. I did a complete backup of the Internal Storage, as accessible by PC. I did also install TWRP and used it to flash SuperSU. I did not do any backup using TWRP.
After downloading a few root apps, a few demanded missing Busybox, so I went to research a bit. I found some installers, downloaded the first one, and clicked install. It said something along the lines of "Install failed, try another location", so I did that. It failed again. I uninstalled the installer and tried another, same result. After a bit of research, I found out I had to unlock read/write permissions for the system partition.
I then found this Thread, telling to flash a .zip file which contains
- Everything necessary to install the latest SuperSU and supporting files (su binary included)
- Install latest busybox in recovery
- A ported wp_mod.ko module for this kernel
- A script to start wp_mod.ko
- A modified boot.img - insecured (allows for remounting of /system to rw when in Android), enabled USB debugging by default, and added busybox run-parts (alows scripts to run during boot).
Without noticing that the title said "Sprint HTC One" and without knowing the difference, I went on and flashed this .zip using TWRP.
The first time, it turned off/rebooted before it was finished (before TWRP showed the reboot option). Turning it on again, it was stuck on the "HTC - quietly brilliant" screen. I held the power button until it turned off, booted into recovery (TWRP) again and tried flashing the .zip again, this time seemingly successful. I clicked reboot, and it again got stuck on the "HTC - quietly brilliant" screen, now I don't know what to do.
After trying rebooting a few times, I did a factory reset, now before rebooting again, TWRP gave me the warning "No OS - Are you sure to reboot?" or something similar, which I find very strange.
Is my backup of Internal Storage of any use? (BTW: I can not access it right now, sadly)
Does anyone know what I could do?
Thanks in advance for all answers.
Oneiiros said:
Hello guys, I really need your help here.
After trying rebooting a few times, I did a factory reset, now before rebooting again, TWRP gave me the warning "No OS - Are you sure to reboot?" or something similar, which I find very strange.
Is my backup of Internal Storage of any use? (BTW: I can not access it right now, sadly)
Does anyone know what I could do?
Thanks in advance for all answers.
Click to expand...
Click to collapse
Long description, but you didnt say what you want to accomplish.
Anyway, probably easiest to flash a custom ROM using one of the following methods:
1- OTG Cable
2- adb push <name of rom>.zip /sdcard/
3- adb sideload <name of rom>.zip

[Q] Brick Help vs980 LG G2

Currently irate because I already typed all this then hit enter to be told I can only register once from this ip.
Any way...
Rooted vs98027a Android 4.4.2 via Stump Root
Used AutoRec which installed TWRP 2.7.00
Backed up Stock Rom
Mount button is missing
Rebooted into Stock to transfer backup to PC and place "cm-12-20150603-NIGHTLY-vs980.zip" as well as Lp gapps.
Rebooted back into TWRP
Wiped, then Installed the CM Nightly, wiped cache and rebooted.
Stuck in LG Boot loop.
Use buttons to boot back into TWRP, open Restore and It's just a blank navigation window.
TWRP just became ****ing worthless
Tried to wipe and possibly install same CM again. Still boot looping.
Tried getting to download mode, but it reboots before installing driver.
I have not a clue as to what to do next.
I can't get it to mount.
ADB Sideload Fails.
Terminal Command lets me select a blank navigation window.
And my original file structure is in like sdcard/0/0/0/0/0/0/0/0/ etc.
Please help, or at least redeem CM and TWRP's value somehow, because this is bs.
I sort of fixed it.
Restore showed up blank, because within the many /0/0/0/0/0/0/0/0 a new TWRP folder would be made or course containing nothing.
I also learned the adb is this magnificent goddess that can do things even when your phone can't.
Throughout further reading I glimpsed upon something about "loki" files that aren't compatible with specific versions of twrp or something. So If you've also been through this and still feel brave enough to flash a custom, then make sure you get the newest version of twrp...
As for the Restore issue, assuming you have a backup saved on pc, wipe everything then adb push the whole file (TWRP/BACKUPS/BLAHBLAH/BLAUGHESDIHF) to /sdcard/.... then it should show up in restore, if it doesn't then use file manager to place it in the right TWRP directory... You can also use the file manager to move the restore folder to the "correct" twrp folder if you don't have it backed up.

Looking for factory images, LG Urbane sorta kinda bricked

Hi,
Seeing if anyone has stock images (system & boot) for the Urbane. I have hours of searching in online and came up empty. I flashed a system file that didn't belong and am now stuck on the splash screen. Does anyone have or has anyone seen the stock images??
Thanks in advance.
You sound like you know more about this stuff than me, but can you use the OTA update and recovery in the development forum? Would a factory reset overwrite system changes?
I was able to find a TWRP backup that was submitted on the forum for a LGWR development that worked perfectly. I will say I put my self through a lot of trouble as the rom I flashed messed with partitions and write permissions. I ended up doing a wipe in TWRP followed by individually wiping each partition. Then I was able to load the backup through adb and restore.
Thanks!
rwade434 said:
Hi,
Seeing if anyone has stock images (system & boot) for the Urbane. I have hours of searching in online and came up empty. I flashed a system file that didn't belong and am now stuck on the splash screen. Does anyone have or has anyone seen the stock images??
Thanks in advance.
Click to expand...
Click to collapse
Hi @rwade434,
Were you able to find a way to recover? I have got myself (stupid me!) into trouble by flashing the wrong ROM (damn!) and now I am stuck into fastboot menu!
Any idea how and where to get the original LJZ13E or LDZ22D image back to our Urbane?
Thanks a lot.
Ok, I have got myself out of misery by following the nice thread at http://forum.xda-developers.com/watch-urbane/general/twrp-2-8-6-0-test-build-t3122005. There was the TWRP recovery and the 5.1.1. image backup. Thanks for the tips.
It certainly wasn't easy for me to find, it doesn't seem the the Urbane is really owned by anyone out there.
Were you able to find any ROMS for the Urbane?
This works to get the watch back to the last firmware version, but it seems that the system remains modified and unable to take the newest 1.3 firmware (Status 7 error). If anyone has the true, factory images (non-TWRP), I sure would appreciate them being posted (as I am sure others would too). Worst case scenario, a TWRP backup of the latest 1.3 image would work, too. Thanks!
meatlocker said:
This works to get the watch back to the last firmware version, but it seems that the system remains modified and unable to take the newest 1.3 firmware (Status 7 error). If anyone has the true, factory images (non-TWRP), I sure would appreciate them being posted (as I am sure others would too). Worst case scenario, a TWRP backup of the latest 1.3 image would work, too. Thanks!
Click to expand...
Click to collapse
Follow the step (copy from www reddit com/r/AndroidWear/comments/3hsmkq/ota_downloads/), it can fix the problem.
-----------------------------------------
The first thing that I did was relocked my bootloader, then unlocked it again, which wipes everything (again). Next, I used the adb shell command, and typed "su" to gain Super User. Then, I mounted the file system to r/w, using the following command: mount -o remount,rw /system Next, I cd'd to system/bin. In system/bin, I used the mv command to rename the app_process32_original file to app_process32. That looks like: mv app_process32_original app_process32. Then, I renamed the install-recovery_original.sh file to install-recovery.sh (using the same mv command as above).
-----------------------------------------
And then reboot into recovery mode and sideload the new ota.
Hahaha, that's a first for me. You quoted my own comment from Reddit. I hope my solution helps someone else. Have a 'thanks' for offering to help someone, Alex.
@rwade
rwade434 said:
I was able to find a TWRP backup that was submitted on the forum for a LGWR development that worked perfectly. I will say I put my self through a lot of trouble as the rom I flashed messed with partitions and write permissions. I ended up doing a wipe in TWRP followed by individually wiping each partition. Then I was able to load the backup through adb and restore.
Thanks!
Click to expand...
Click to collapse
Could you tell me what folder did you use to store the backup.zip? I've been trying to bring my Urbane back to life. It's driving me crazy.
mseck said:
Could you tell me what folder did you use to store the backup.zip? I've been trying to bring my Urbane back to life. It's driving me crazy.
Click to expand...
Click to collapse
https://mega.nz/#!0N0SiCrK!NEHqeolukz7jkuazn3V3eHSzVMC2hcEDbk4P3-cU7mY
Copy the folder of the zip into TWRP/BACKUP/505KPZK0107693/ and restore backup
potaturrias said:
https://mega.nz/#!0N0SiCrK!NEHqeolukz7jkuazn3V3eHSzVMC2hcEDbk4P3-cU7mY
Copy the folder of the zip into TWRP/BACKUP/505KPZK0107693/ and restore backup
Click to expand...
Click to collapse
Do i live the file as RAR or change it to ZIP? or unzip and move the folder itself?
@rwade434
Thank you for the TRWP back up, I had a couple issue creating directories so i created them manual. and Copy/paste each file.
I've been without my watch for 4 Days. Thank you much!
Factory reset, like new

Behaves as if it has TWO /system partitions

I recently got my Nexus 6 back with a new (to me) motherboard installed. After allowing multiple OTA updates to the current (March 2017) firmware, getting my apps installed and setup, etc., I went to make some changes to the /system partition.
Knowing that /system is mounted read-only normally, I downloaded the current copies of adb and fastboot, as well as TWRP. I booted my phone into fastboot, ran fastboot boot twrp.img, mounted /system, and used adb to make a change. I then booted normally, but didn't see the effect of the change, so I checked with adb, and the change wasn't there. OK, that could be a few things, so I went back into TWRP, and -- this is where it gets weird -- saw the change.
Yes, if I boot up on TWRP and mount /system, I see whatever changes I have made to the /system partition visible when running TWRP, but when I boot the stock bootloader, I don't see any of them. It is behaving as if there are two /system partitions: one visible when booting with TWRP and the other visible when booting with stock.
I've never seen this before. Any thoughts?
NoelJB said:
...
Knowing that /system is mounted read-only normally, I downloaded the current copies of adb and fastboot, as well as TWRP. .
I've never seen this before. Any thoughts?
Click to expand...
Click to collapse
Is TWRP the latest version 3.1.0.0?
Did you use a recent rootexplorer?
For instance prev, version ES file explorer does not work with recent Android.
When booting TWRP-recovery normally the system partition needs to be mounted manually.
Why do you use adb to make changes to system, instead of the file manager of TWRP?
> Is TWRP the latest version 3.1.0.0?
Yes.
> Did you use a recent rootexplorer? For instance prev, version ES file explorer does not work with recent Android.
Not rooted, hence using TWRP to edit the /system partition.
> When booting TWRP-recovery normally the system partition needs to be mounted manually.
Yes, hence my comment about mounting /system.
> Why do you use adb to make changes to system, instead of the file manager of TWRP?
What would it matter? The contents of /system shown by the TWRP file manager are identical to those shown by adb shell. My problem is that the contents don't match what I see when booting with the stock bootloader. As I said, it is as if TWRP were showing one /system partition, and the stock bootloader were showing another.
NoelJB said:
... adb instead of the file manager of TWRP.....
What would it matter?.
Click to expand...
Click to collapse
.... using a shell and an 2nd device is rather different. I prefer the filemanager; it's more direct.
Sorry no more thoughts....
Lemme guess...
You're on the bone stock kernel...
If that's the case... There's a thing that keeps stuff from working... I wish I could be more help but... It's been almost 2 years since I've seen this...
I THINK you can flash any other kernel and it will solve your problem... Or maybe one of the root solutions would do it too...
Sent from my Nexus 6 using Tapatalk
did you solve it?

Categories

Resources