Related
Before anyone flames me, i am already kicking myself enough for this one, and i dont typically post questions on XDA because i like figuring things out for myself. But this a last ditch effort for me after spending days Googling this problem. So here goes..
I have a Motorola Photon Q (4.1.2, factory locked, rooted) I installed a Density changer on the phone that i have used before in a few rooted phones which worked fine before, however the Q did not like it. The phone will not boot past the logo screen. I can get to system recovery, and installed the necessary drivers, android sdk, etc.. I read in the Density app description, that the app changes build.prop settings. (My fault for not reading the app description better)
I can access the phone by ADB, have a copy of the original build.prop , but when i try to push the build.prop to the phone, i get..
failed to copy 'build.prop' to '/system/build.prop' : Read only file system
I read that the file system permissions can be changed through ADB, but every link i have used to figure out the command line deals with different issues/goes to a different directory in the phone. So i am stuck at figuring out how to change the file permission in system to push the original build.prop through. If anyone can help supply the exact command line needed, or am i wasting my time at this point? I will buy a ....car for the person who can help...(no, not really, but you will have my endless appreciation for helping.)
Thanks, Stat
RSD stock rom?
Sent from my XT897 using XDA Premium 4 mobile app
StatBlack said:
Before anyone flames me, i am already kicking myself enough for this one, and i dont typically post questions on XDA because i like figuring things out for myself. But this a last ditch effort for me after spending days Googling this problem. So here goes..
I have a Motorola Photon Q (4.1.2, factory locked, rooted) I installed a Density changer on the phone that i have used before in a few rooted phones which worked fine before, however the Q did not like it. The phone will not boot past the logo screen. I can get to system recovery, and installed the necessary drivers, android sdk, etc.. I read in the Density app description, that the app changes build.prop settings. (My fault for not reading the app description better)
I can access the phone by ADB, have a copy of the original build.prop , but when i try to push the build.prop to the phone, i get..
failed to copy 'build.prop' to '/system/build.prop' : Read only file system
I read that the file system permissions can be changed through ADB, but every link i have used to figure out the command line deals with different issues/goes to a different directory in the phone. So i am stuck at figuring out how to change the file permission in system to push the original build.prop through. If anyone can help supply the exact command line needed, or am i wasting my time at this point? I will buy a ....car for the person who can help...(no, not really, but you will have my endless appreciation for helping.)
Thanks, Stat
Click to expand...
Click to collapse
Update: So i tried Android Commander for Windows since i am new to ADB commands (only 6 months into Mobile Development classes which hasnt covered ADB yet). The program says i do not have root access which i am guessing since the phone is permanently locked from Motorola, i only get the half assed root access when the phone is up and running? Urgh, my phone is looking more and more like a paper weight at this point. Anyone have any suggestions?
StatBlack said:
Update: So i tried Android Commander for Windows since i am new to ADB commands (only 6 months into Mobile Development classes which hasnt covered ADB yet). The program says i do not have root access which i am guessing since the phone is permanently locked from Motorola, i only get the half assed root access when the phone is up and running? Urgh, my phone is looking more and more like a paper weight at this point. Anyone have any suggestions?
Click to expand...
Click to collapse
If you have adb, is it booting into Android? Or are you adbing to it while it is bootlooping...?
You can try to remount the system RW, but perhaps RSD lite would be the easiest way to get back to stock.
Connect phone.
Run from terminal:
adb root
adb remount
Then push file to /system/
arrrghhh said:
If you have adb, is it booting into Android? Or are you adbing to it while it is bootlooping...?
You can try to remount the system RW, but perhaps RSD lite would be the easiest way to get back to stock.
Click to expand...
Click to collapse
The phone never does boot into android (as far as i know). The Motorola boot screen shows for a few seconds, then the screen turns black and stays that way. I have tried pushing the build.prop through ADB with the screen black, while it is in recovery, and in ADB side load mode. No results. I stupidly had did a hard reset erasing my root access thinking it would fix the build.prop with the reset. Can RSD Lite be used for a stock ROM if the phone is permanently factory locked?
mrvek said:
Connect phone.
Run from terminal:
adb root
adb remount
Then push file to /system/
Click to expand...
Click to collapse
Is this a Mac process? Which is actually the only computer i have now so i have to learn the process all over again on Terminal.
Thanks everyone for the help so far. I appreciate it.
StatBlack said:
The phone never does boot into android (as far as i know). The Motorola boot screen shows for a few seconds, then the screen turns black and stays that way. I have tried pushing the build.prop through ADB with the screen black, while it is in recovery, and in ADB side load mode. No results. I stupidly had did a hard reset erasing my root access thinking it would fix the build.prop with the reset. Can RSD Lite be used for a stock ROM if the phone is permanently factory locked?
Click to expand...
Click to collapse
Yes, you can use RSD on a locked or unlocked device.
StatBlack said:
Is this a Mac process? Which is actually the only computer i have now so i have to learn the process all over again on Terminal.
Thanks everyone for the help so far. I appreciate it.
Click to expand...
Click to collapse
adb works on Mac, Linux or Windows.
In stock rom, ADB will never run as root afaik (I think I tried putting ro.secure to 0 (unlocked bootloader) once and it still didn't work). You have to upload it to for example /data/local folder, su and put it to the right location. If you fail to get root, then the only way is to:
1) Unlock bootloader, install custom recovery, fix from there
2) Flash system.img.ext4 via moto_fastboot.exe (or use RSD to flash entire rom, but it will wipe your data)
Skrilax_CZ said:
In stock rom, ADB will never run as root afaik (I think I tried putting ro.secure to 0 (unlocked bootloader) once and it still didn't work). You have to upload it to for example /data/local folder, su and put it to the right location. If you fail to get root, then the only way is to:
1) Unlock bootloader, install custom recovery, fix from there
2) Flash system.img.ext4 via moto_fastboot.exe (or use RSD to flash entire rom, but it will wipe your data)
Click to expand...
Click to collapse
This has been a "paperweight project" for the last few months (IE, sitting on my desk, gathering dust)
Here is what i have tried...
Installed Motorola Drivers.
Installed RSD Lite 6.1.5.
Tried flashing both ICS and JB system recovery files. No success.
In the Motorola Photon Q FXZ thread..http://forum.xda-developers.com/showthread.php?t=2095536 It says to remove the getvar lines from the FXZ file. I have removed both and still get an error message on flashing "failed flashing process. 1/23 flash partition "gpt_mai.."
I previously tried this on a low battery level, then let it charge all night, but still get a low battery level this morning. Is the battery level affecting it not installing?
I am at a loss as to what to do at this point?
Thanks
StatBlack said:
This has been a "paperweight project" for the last few months (IE, sitting on my desk, gathering dust)
Here is what i have tried...
Installed Motorola Drivers.
Installed RSD Lite 6.1.5.
Tried flashing both ICS and JB system recovery files. No success.
In the Motorola Photon Q FXZ thread..http://forum.xda-developers.com/showthread.php?t=2095536 It says to remove the getvar lines from the FXZ file. I have removed both and still get an error message on flashing "failed flashing process. 1/23 flash partition "gpt_mai.."
I previously tried this on a low battery level, then let it charge all night, but still get a low battery level this morning. Is the battery level affecting it not installing?
I am at a loss as to what to do at this point?
Thanks
Click to expand...
Click to collapse
I found and removed 4 getver lines and it worked for me.
Along time ago.
Sent from my XT897 using XDA Premium 4 mobile app
Hello, guys!
Basically, my rooted device apparently got a virus (not sure), so I did a factory reset. Now I can't get past the setup wizard because it stops unexpectedly. I tried using a custom ROM (I'm on 2.3), and it fails the signature verification.
So, the only approach for me to take seems to be installing CWM or ROM manager or anything else directly into my phone via my PC. Don't know how to do that, though. I can't access or do anything in my phone, so whatever needs to be done needs to be done via my PC, probably.
I'm using an Alcatel One Touch 985.
Thanks in advance!
Note: Installing a fresh copy of the setup wizard would be the easiest fix of all, or even the stock Android ROM. Once I get my phone working in its basic form, everything else becomes much easier to do.
If your phone still boots in either recovery or download mode, then its not bricked
If you have a custom recovery, you can flash your custom rom. If you don't, you can flash a stock ROM
Hope this helps
Basically, my rooted device apparently got a virus (not sure), so I did a factory reset. Now I can't get past the setup wizard because it stops unexpectedly. I tried using a custom ROM (I'm on 2.3), and it fails the signature verification.
Click to expand...
Click to collapse
what that is its most likely the rom you downloaded is for a different phone, are you sure it was your phone specificly? check model no. if not theres a option in CWM to uncheck signature verification and it will sorta force flash what you wanted to flash.
If your phone still boots in either recovery or download mode, then its not bricked
If you have a custom recovery, you can flash your custom rom. If you don't, you can flash a stock ROM
Hope this helps
Click to expand...
Click to collapse
Read the Question before posting stupid Answers, this shows that you didnt even read it...
I can still enter recovery mode, yes.
This all happened while using the ROM the phone came with.
I've tried with what seems to be the only compatible ROM for my phone, and also with other 2.3 ROMs. The problem regarding the ROM issue seems to be that the phone's boot loader isn't unlocked.
I know CWM can fix the signature problem, but how do I get it into the phone in the first place? That's the real issue.
Edit: I've tried unblocking the boot loader with the help of a tutorial online, but I believe I'm missing a step. Ideally this fix should be attempted after I know for sure there's no way to simply install an apk directly into the phone through my PC.
Klowdz said:
I can still enter recovery mode, yes.
This all happened while using the ROM the phone came with.
I've tried with what seems to be the only compatible ROM for my phone, and also with other 2.3 ROMs. The problem regarding the ROM issue seems to be that the phone's boot loader isn't unlocked.
I know CWM can fix the signature problem, but how do I get it into the phone in the first place? That's the real issue.
Edit: I've tried unblocking the boot loader with the help of a tutorial online, but I believe I'm missing a step. Ideally this fix should be attempted after I know for sure there's no way to simply install an apk directly into the phone through my PC.
Click to expand...
Click to collapse
have you tired factory reseting it again? the setup wizard crash is really werid at a stock rom.
I have. Same result.
Perhaps I deleted some file needed for the wizard to function properly.
I don't mind flashing a new ROM into the phone, or do whatever else in order for it to work properly.
Klowdz said:
Hello, guys!
Basically, my rooted device apparently got a virus (not sure), so I did a factory reset. Now I can't get past the setup wizard because it stops unexpectedly. I tried using a custom ROM (I'm on 2.3), and it fails the signature verification.
So, the only approach for me to take seems to be installing CWM or ROM manager or anything else directly into my phone via my PC. Don't know how to do that, though. I can't access or do anything in my phone, so whatever needs to be done needs to be done via my PC, probably.
I'm using an Alcatel One Touch 985.
Thanks in advance!
Note: Installing a fresh copy of the setup wizard would be the easiest fix of all, or even the stock Android ROM. Once I get my phone working in its basic form, everything else becomes much easier to do.
Click to expand...
Click to collapse
Try installing the ROM again, doing the correct wipe. After installing the ROM give the fix permission option.
In what novel way should I do that? I've tried the regular way, as mentioned above, and nothing.
Klowdz said:
In what novel way should I do that? I've tried the regular way, as mentioned above, and nothing.
Click to expand...
Click to collapse
If phone boots, is rooted and setup wizard stops just remove setup wizard app via adb.
Code:
adb shell rm /system/app/<name-of-setup-wizard-app>.apk
Cheers,
AJ
How do I do that? I have the SDK and everything installed, but that's it.
Klowdz said:
How do I do that? I have the SDK and everything installed, but that's it.
Click to expand...
Click to collapse
Following steps are for Windows PC
U need to find a file called adb in the folder of SDK
I use an older version of SDK and it's in folder named 'platform-tools'
Open the folder which contains this file
Then u need to open command prompt window there
( Do that by holding shift while right clicking in the folder then select 'open command window here' option)
Then u can type the following code
in the window.
Abhinav2 said:
adb shell rm /system/app/<name of setup wizard>.apk
Click to expand...
Click to collapse
Sent from my GT-I9000
It says it's a read-only file system.
Maybe It only works if your phone is rooted
If u r rooted U can try adding su command before it
su adb shell rm /system/app/<name of setup wizard>.apk
.
Sent from my GT-I9000
"Su" isn't recognized, but I clearly have it since whenever I try to access adb shell it asks me for permission (not for this task, but for another).
Wouldn't it be simpler to just install the setup wizard again? The problem is where to find that .apk.
OK, been searching for a week, obsessively, to find a fix for this. No luck.
I tried flashing the aosp ROM from official miui v5 through twrp and have been left with this.
1. Bootloader locked, Tamper bit engaged, and running stock recovery with a signature that cannot verify anything. (I mean anything, cannot even reflash the same ROM, factory signed, nothing)
2. What's this? It starts up? It can't be bricked? Oh wait why did it just reboot upon network connection? Right! Persistent has been destroyed/corrupted! Fun stuff.
3. SDD called internal? Sdd gone? Yes, yes it is. Everything has changed which is why I can't DD/ the persistent!!
4. Tried every toolkit (except the mac os one which resets tamper) and been through every internet page ever. Before i embarked upon this mission to unbrick the unbrickable id never heard of a data dump, persistant, or .tar. Now I never want to hear of them again. I have tried everything except the backdoor adb route because the Qualcomm drivers won't install on my 64bit win8.1.
If anyone, anywhere, knows how I can put back to stock, aosp, caulkins, anything, have a heart, help a man!
jpilch said:
OK, been searching for a week, obsessively, to find a fix for this. No luck.
I tried flashing the aosp ROM from official miui v5 through twrp and have been left with this.
1. Bootloader locked, Tamper bit engaged, and running stock recovery with a signature that cannot verify anything. (I mean anything, cannot even reflash the same ROM, factory signed, nothing)
2. What's this? It starts up? It can't be bricked? Oh wait why did it just reboot upon network connection? Right! Persistent has been destroyed/corrupted! Fun stuff.
3. SDD called internal? Sdd gone? Yes, yes it is. Everything has changed which is why I can't DD/ the persistent!!
4. Tried every toolkit (except the mac os one which resets tamper) and been through every internet page ever. Before i embarked upon this mission to unbrick the unbrickable id never heard of a data dump, persistant, or .tar. Now I never want to hear of them again. I have tried everything except the backdoor adb route because the Qualcomm drivers won't install on my 64bit win8.1.
If anyone, anywhere, knows how I can put back to stock, aosp, caulkins, anything, have a heart, help a man!
Click to expand...
Click to collapse
This honestly is very confusing. I had to read what you wrote a couple of times to try and comprehend what the problem is.
Have you tried using fastboot without any toolkit? I ask because you haven't mentioned it anywhere. Persist can be fixed by fastbooting back to pure stock, and Mike's fix on the OnePlus forums, and/or updating to 44S.
Can you tell us what errors you get when you try to reflash the same rom? What recovery are you running? Which rom were you trying to reflash?
I have to agree with @nicholaschum, your post is very vague and confusing in its present form, and I'm a pretty seasoned troubleshooter on XDA.
What's needed? Less emotion, less comic type speech, less sarcasm, more specifics and facts.
Transmitted via Bacon
1328
If I try to sideload, it says either signature failed or whole signature failed.
Anything i push does not get pushed and I have tried multiple drivers from the galaxy ones that come in the reflash.zip from the one plus tech support to the Google ones I am using now.
If I try to fastboot through toolkit it says failed, not unlocked can't flash/erase. If I fastboot through cmd it says error: closed. I do all my checks, and it shows up in fastboot and adb but won't let me send anything.
The phone boots up for about 15 in is before restarting, the only way to get files on are to drop them in explorer within these 15secs, to internal storage, which used to be my sdcard.
I have tried flashing/side loading multiple ROMs from miui, 44s, 33r all signed to caulkins and mahdi. Nothing has worked (and the aosp OTA).
I cannot unlock bootloader, cannot reset tamper, cannot load GUI for more than 15 secs, and cannot root (although kermal already says it is, I suspect su needs to be in place).
I have also tried fastboot -c boot recovery.IMG (and recovery recovery.IMG) but no luck still. Is there a PC version of the Mac toolbox that can reset tamper? At least then I could unlock bootloader and install twrp and flash.
Thanks for the help
Josh
Still sounds like a driver issue imo.
First uninstall ALL previous drivers you have tried from device manager.
Installing one driver after another often causes conflicts.
Then download the official Android SDK and install Google USB driver. Google for instructions if needed but everything is pretty much straight forward.
This driver has the biggest chance of success.
After that you're off to start fixing your phone using fastboot and adb.
OK have done this on both a 32 and 64 bit win 8.1 systems. Exact same result. Error: closed or not unlocked no flash/erase for everything fastboot, and e: can't verify signature/whole-signature e: verification failed. I tried adb explorer through adb sideload and error:closed again. Does this mean the adb protocol for accepting is closed? No idea.
I have a feeling it is something on the phone rather than computer now? Done everything on a 32 bit now and everything is the same and had no drivers previously. And just to be clear when I say stock recovery, I don't mean cwm I mean
android system recovery 3e
KTU84P. 1.2.0 dev-keys
jpilch said:
OK have done this on both a 32 and 64 bit win 8.1 systems. Exact same result. Error: closed or not unlocked no flash/erase for everything fastboot, and e: can't verify signature/whole-signature e: verification failed. I tried adb explorer through adb sideload and error:closed again. Does this mean the adb protocol for accepting is closed? No idea.
I have a feeling it is something on the phone rather than computer now? Done everything on a 32 bit now and everything is the same and had no drivers previously. And just to be clear when I say stock recovery, I don't mean cwm I mean
android system recovery 3e
KTU84P. 1.2.0 dev-keys
Click to expand...
Click to collapse
For the fastboot bit, I've seen this happen a lot. Many people used this to solve their issue: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Hello all.
FIrst, I am not new to this. Just let me get that out in the open. I've done custom ROMs and recoveries on four devices including two HTCs. However I'm new to Asus and this is my first tablet.
So, what is going on is that I have an Asus Memo Pad ME301T. It is rooted, bootloader is unlocked (confirmation appears in upper left corner at boot). However, it will not install the TWRP recovery when I try to push it from my PC. I try to choose the recovery icon on the bootloader, and it shows the fallen android with an error message when it tries to open. I have followed the directions and executed the proper commands from the platform-tools folder in the Android SDK. I thought maybe I could try downloading the BLOB file directly to the device's emulated sdcard and installing it via a terminal command, however I do not know what commands I should use from a terminal emulator. I'm sure it's something simple I'm missing. I am trying to install the TWRP 2.5.0 recovery because it seems to have the highest success rate, and I am currently on the 10.6.1.15.ww stock ROM.
If someone familiar with these tablets could go through the process with me, step by step, one more time (don't just link me to a thread unless it's clear, concise, and exactly what you would do in this situation) or provide the commands so I can try it from the terminal within the tablet, I would appreciate it. When I've had problems in the past it's been something simple most of the time or an extra step I need to do so hopefully one of you can tell me what I'm missing.
Thanks!
asilaydyingdl said:
Hello all.
FIrst, I am not new to this. Just let me get that out in the open. I've done custom ROMs and recoveries on four devices including two HTCs. However I'm new to Asus and this is my first tablet.
So, what is going on is that I have an Asus Memo Pad ME301T. It is rooted, bootloader is unlocked (confirmation appears in upper left corner at boot). However, it will not install the TWRP recovery when I try to push it from my PC. I try to choose the recovery icon on the bootloader, and it shows the fallen android with an error message when it tries to open. I have followed the directions and executed the proper commands from the platform-tools folder in the Android SDK. I thought maybe I could try downloading the BLOB file directly to the device's emulated sdcard and installing it via a terminal command, however I do not know what commands I should use from a terminal emulator. I'm sure it's something simple I'm missing. I am trying to install the TWRP 2.5.0 recovery because it seems to have the highest success rate, and I am currently on the 10.6.1.15.ww stock ROM.
If someone familiar with these tablets could go through the process with me, step by step, one more time (don't just link me to a thread unless it's clear, concise, and exactly what you would do in this situation) or provide the commands so I can try it from the terminal within the tablet, I would appreciate it. When I've had problems in the past it's been something simple most of the time or an extra step I need to do so hopefully one of you can tell me what I'm missing.
Thanks!
Click to expand...
Click to collapse
So you are trying to install twrp from fastboot ?
What command are you using ?
Thx Josh
lj50036 said:
So you are trying to install twrp from fastboot ?
What command are you using ?
Thx Josh
Click to expand...
Click to collapse
Exactly. I open a command line on the folder, renamed the file to twrp.blob, and then I I am using the following:
ADB devices
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
I think the problem is really simple though. I think for some reason, the tablet and the computer are not communicating via fastboot. I.e. the info is not actually getting through the USB cable to the tablet when in fastboot. I have android debugging enabled and all that good stuff. So my assumption is this is a driver issue or an extra step needs done on the tablet to get the communication working. All drivers did install properly according to the PC. Maybe it's even the USB port on the tablet itself and I need to exchange it. But I can transfer files like it's a media device, so I doubt that's it.
Any thoughts?
***UPDATE***I checked settings in SuperuserSU and it turns out I did not have root enabled at boot. Enabled it and it connected to the PC as "fastboot". Commands are still not getting sent to the device. Whenever I try to send the blob, it always says "0 KB" and the device just freezes. Perhaps I need a different command or fastboot on the PC isn't initializing correctly? Or maybe there is a setting on my device that needs tweaked yet?
Thoughts?
I think I know what the problem is. Someone using the TF300T tablet had the exact same problem I'm having. Turned out it was their rooting method. I used KingoROOT despite a few murmurs of it causing issues because I was looking for results quickly not a quality job like I should have been. SuperuserSU has been behaving weirdly, as well as my USB android keyboard and a few other quirks in the OS since I did the root, so it makes sense. I will have to use the KingoROOT app and undo the root, and retry with motochopper. KingoROOT must not have rooted all directories. If that doesn't work, I will probably have to do a full restore to stock settings by re-installing a stock Asus ROM and start fresh.
lj50036 said:
So you are trying to install twrp from fastboot ?
What command are you using ?
Thx Josh
Click to expand...
Click to collapse
Did more work and research. I did actually have the improper drivers installed. I installed them from Asus, so that is fixed. But the problem remained. After further research, it came down to version builds and numbers. I am using a version of Asus' firmware that isn't compatible with the operations I'm trying to perform. I am using version 10.6.1.15. TWRP 2.5.0.0 and newer can NOT be installed on any Asus tablet running anything less than 10.6.1.27. There is something about the bootloader, encryption or a security setting that prevents data from being pushed via a fastboot command. So I now have a Christmas project, which is update to a newer version of Asus firmware.
I found my solution here, in a thread filled with people having the exact same issue:
http://forum.xda-developers.com/showthread.php?t=2179874&page=3
And directions for the fix here:
http://forum.xda-developers.com/showthread.php?t=2187982
Hope my work helps someone else.
Hi all. I'm at my wit's end.
I'm new to Android and am attempting to rid my phone of Verizon bloat apps and want a clean Sense free environment. But my issue is that when I type "adb device" in command prompt, it doesn't show my device.
I have already spent the $25 for Sunshine and s-off'd my M8, and when I type "adb reboot bootloader" it reboots my phone into bootloader. So it's seeing something. In "Device Manager" it comes up as "Android Phone." I think it did that because I tried to do the troubleshooting of manually installing the Google ADB USB driver, but I'm not totally sure.
I have the Android SDK installed.
Ugh... this is headache inducing, and I just want a clean phone
If anyone can give some help, it would be TOTALLY appreciated.
Thanks!
fixed the issue. Instead of using the SDK, I used the website theunlockr and their guide worked perfectly.
Sorry for taking up forum space with my stupidity
pogswarts said:
fixed the issue. Instead of using the SDK, I used the website theunlockr and their guide worked perfectly.
Sorry for taking up forum space with my stupidity
Click to expand...
Click to collapse
You really should be using HTC drivers as well as the HTC version of fastboot. It's better tailored for the use of RUU etc on HTC phones whereas the sdk fastboot will fail.
http://forum.xda-developers.com/showpost.php?p=56890497&postcount=3