A favor please??
Hey guys. I am going to try and make a recovery that works 100% fully for everyone. I see a few people have issues and others don't. I try and fix it. Need some help. I don't have this phone so I need a few files before I can get started. If anyone could get me 3 things
If anyone knows how to do a dump_image the stock recovery.img for me.
Post the file /proc/partitions
Post the file /proc/mounts
For the 2 and 3. You can also do an adb commands. "adb shell" then "cat /proc/partitions" and "cat /proc/mounts"
Thank You Guys! and if everything goes well. I can port over CWM Touch.
Here's items 2 and 3. I just got my DNA so I haven't unlocked yet, and I don't know of a way to dump the recovery without unlock, but I'll post it as soon as I can.
Related
See by the post count, certainly a noob but I think I've done my homework here. I know this is posted in various places with long threads attached but here it is ...
Atrix 4G ATT
I was on 1.8.3 rooted, did the OTA update to 4.5.91. I think I want root back.
Is this thread the safest way to accomplish this?
http://forum.xda-developers.com/showthread.php?t=1138204 (OP)
I'm not concerned with losing any data on the phone as far as media or anything.
abuse away for being new, idiot with android at the moment.
Best and safe way is preinstall method by eval.... Why?
you dont need to unlock your unit it work with lock / unlocked units
So the method referenced in my first post?
1. Flash with RSD (2.3.4 SBF)
Then ...
Hi guys.. here is a useful little /preinstall for you (attached)
Put phone in fastboot mode, then:
Code:
fastboot flash preinstall preinstall.img
fastboot reboot
(older versions maybe need "fastboot -i 0x22b8")
after fastboot & reboot, type in adb ("adb shell") or terminal emulator, exactly:
Code:
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
The last step is optional (and next-to-last *should* be unnecessary), as you can install Superuser however you like. In fact, if you've installed it, simply typing "/preinstall/su" is another way to root, and you could then mount /system read-write and copy it into /system/bin.
Many thanks to Brandon & The2d for brainstorming this out in a crazy "there's no way it could be possible" rooting session. There were a lot of harder ways... who knew we'd be so lucky! And thanks to Edgan for the great "dosu" =)
You can find fastboot here: http://forum.xda-developers.com/show....php?t=1138092
Click to expand...
Click to collapse
thanks!
I used this briefmobile method
http://briefmobile.com/motorola-atrix-4g-root
same as you - OTA to 2.3 from stock locked AT&T. Above method worked first time no data loss. YMMV of course.
I specifically did NOT want to use anything related to sbf due to all the warnings about bricking etc. etc.
I'm holding off on BL unlock as right now 2.3 is a great build even with AT&T restrictions/crapware, hoping that the official unlock will drop before stable CM/AOSP builds appear, but you never know lol
I saw this one too but wasn't sure, no issues at all on this one?
EDIT: That was easier than anticipated..... What's next for a noob such as myself? Tech background: UNIX Engineer (AIX/Solaris/Linux) 15+ years *NIX experience. I don't know crap for java, I alright with c, perl, python, korn ....
Hi there everyone, i am in need of assistance.
I have follwed the guide on here for downgrading my phone usin the ADB commands and all is good up until the actual downgrading stage. After a few attempts i had managed a temp root (i think) using command line.
" adb shell " brought back the # so i know i did that right, but when it comes to pushing the rom file to my sd card it comes back adb not found in which case i cannot reboot the bootloader if that doesnt work.
Is there something i am doing wrong or is the file im uusing just not compatible, "PC10IMG.zip"
If there is another way to downgrade after temp root with maybe a different rom file i would be very grateful if someone could help me.
Any questions you have to help me, just let me know
Thanks
Sent from my HTC Vision using XDA App
Im still very new at this but i'll thrown in my two cents here.
After you've gotten temporary root status '#' and you've set your version to 1.00.000.0 following the guide, your next step is it push the stock ROM used to downgrade into your sd card.
At this point make SURE you are not in the adb shell, (aka you dont see the #)
so make sure you exit first.
Another thing is to make sure the ROM you want to push, the "...._PC10IMG.zip" file is in the correct directory, same directory as your CMD.
Lastly the push process takes time so dont be impatient, unlike the other files you pushed before which were more or less instant, this one will take at least a minute and the CMD may look idle so really just have to wait.
when the results show, you can then proceed with reboot bootloader command.
hope it helps.
i got stuck after this point, i keep getting a cid error, which is a totally differnt issue from your above question.
Hey guys,
I've been slackin' on the updates of my rom lately and thought it was finally time to do a proper update. I got my HTC one in the US around release and rooted it back then. However, now I was trying to install Android Revolution on it and the installation went fine (well, at least so I thought) up until the time I was going to boot it. It constantly keeps on re-booting me into the TWRP menu, even though the rom seems to be installed.
I was looking around and found out about ADP push http://forum.xda-developers.com/showthread.php?t=2325853
However, I get stuck on the step where I'm supposed to get up my Serial number in the terminal. It seems as if the command runs through but comes up with nothing, just a blank space. At first I simply ignored this and moved on to the next step. However, my computer doesn't seem to acknowledge the command ./adb push NameOfRom.zip /data/media/
Where do I go from here?
Thank you
Mr. Harrow
Mr_Harrow said:
Hey guys,
I've been slackin' on the updates of my rom lately and thought it was finally time to do a proper update. I got my HTC one in the US around release and rooted it back then. However, now I was trying to install Android Revolution on it and the installation went fine (well, at least so I thought) up until the time I was going to boot it. It constantly keeps on re-booting me into the TWRP menu, even though the rom seems to be installed.
I was looking around and found out about ADP push http://forum.xda-developers.com/showthread.php?t=2325853
However, I get stuck on the step where I'm supposed to get up my Serial number in the terminal. It seems as if the command runs through but comes up with nothing, just a blank space. At first I simply ignored this and moved on to the next step. However, my computer doesn't seem to acknowledge the command ./adb push NameOfRom.zip /data/media/
Where do I go from here?
Thank you
Mr. Harrow
Click to expand...
Click to collapse
I found this http://forums.androidcentral.com/htc-one/332846-hi-i-have-htc-one-m7-its-stuck-twrp.html
Shouldn't have to go through the hassle of going through that process though? Seeing as there's a zip of the android revolution on the phone which is installable, but nevertheless doesn't boot. Please help a fella out?
Try to wipe all but SD card, flash rim like normal, then pull the recovery logs (found in advance settings) and post it here if it won't boot
Also know that many HTC phones when unlocked through htcdev, need you to flash the kernel through fastboot after flashing the ROM, if you're unsure if you need to do this boot to bootloader and note all it says on this screen and then check your device forum for specifics on this
Sent from my Nexus 4 using XDA Premium 4 mobile app
Also make sure you got the correct rom from the correct forum. There are multiple One forums now and it's not the first time it's happened..
PS. ./adb is only for Linux - is that what you are running?
And I know the stuff is on /data/media but try this:
adb push nameofrom.zip /sdcard/
I know about logcat, but fit seems to be a shell command, and it does not seem to be working when I am in recovery mode. I also know the recovery.log. But I still like to see what is happening in real time with my own two eyes. Is there some way of activating logcat while you are in recovery? It seems like I can shell into my device. I get this error
Code:
/sbin/sh: exec: line 1: logcat: not found
when I try to issue
Code:
./adb logcat
command. I created an image with Android Kitchen which seems to be installed waaaay too fast. i.e. I get a successful confirmation from TWRP, but when I try to reboot the device I get an error stating that there is no OS installed.
sansari123 said:
I know about logcat, but fit seems to be a shell command, and it does not seem to be working when I am in recovery mode. I also know the recovery.log. But I still like to see what is happening in real time with my own two eyes. Is there some way of activating logcat while you are in recovery? It seems like I can shell into my device. I get this error
Code:
/sbin/sh: exec: line 1: logcat: not found
when I try to issue
Code:
./adb logcat
command. I created an image with Android Kitchen which seems to be installed waaaay too fast. i.e. I get a successful confirmation from TWRP, but when I try to reboot the device I get an error stating that there is no OS installed.
Click to expand...
Click to collapse
I may be way off, but you tried Galaxy Tool by idone. Here is the link http://forum.xda-developers.com/not.../app-one-click-hotspot-enabler-menus-t2816159 it has the ability to access logcats and sys dumps, might be worth a try ?
jimzweb1 said:
I may be way off, but you tried Galaxy Tool by idone. Here is the link http://forum.xda-developers.com/not.../app-one-click-hotspot-enabler-menus-t2816159 it has the ability to access logcats and sys dumps, might be worth a try ?
Click to expand...
Click to collapse
Hey thanks. I'll have a look at it. I got some stuff with ./adb logcat. I had to reinitialize the tool a few times but TWRP is worth it's weight in gold. I have not had the opportunity to try some of the other recoveries out there. But that is because TWRP does all the things I need to do.
sansari123 said:
Hey thanks. I'll have a look at it. I got some stuff with ./adb logcat. I had to reinitialize the tool a few times but TWRP is worth it's weight in gold. I have not had the opportunity to try some of the other recoveries out there. But that is because TWRP does all the things I need to do.
Click to expand...
Click to collapse
No problem, I have used both TWRP and CWM. In the past I was not possible to switch, and use the backups from one to the other. Now that's changed and they are basically compatible making the choice between them just a personal preference. Let me know if the Galaxy Tool Hidden menu app helped ?
Hi all,
I have been through douzens of threads and forums looking for a solution to this.
I followed some instructions to modify the build.prop file on my Huawei G535-L11 to disable Huawei theme manager in order to get Xsposed working fully (changed ro.config.hwtheme: 0). I did a backup of my original build.prop before hand, and my phone was rooted and unlocked but running the stock rom.
Unfortunately, it rebooted but won't go past the first 'EE' splash screen (just turns off again).
I can inconsistently get in to both fastboot and Android recovery, so I have been trying to use adb to push the original build.prop to /system/ on the phone.
However, this fails as /system/ is apparently RO. I have now discovered that I can't get SU permissions despite my phone being rooted.
If I try:
adb shell
$ su
nothing happens and it goes back to a $ prompt.
If I try:
adb root
I get the message (paraphrased):
adb cannot run as root in production builds.
So I can't push or do any adb method of restoring the build.prop file?! I don't understand why it is acting as if it is not rooted. I had Link2sd, Gravity Box, No Frills Cpu Controller all set up and working before, so I'm fairly sure I did truly have root.
I have also tried flashing a TWRP recovery, which apparently is successful, but when I go in to recovery it is still the Android Recovery.
Does anyone have any ideas what I could do to get my phone working again please?! This is my last gasp before the phone gets filed under 'B' in the cylindrical cabinet in the corner of the room!
Any assistance greatly appreciated!
Some systems are very finicky with modded build.props, or you didn't set the file's permissions correctly. I'm afraid without being able to boot or a working custom recovery, then adb won't work, much less root enabled adb functions. adb works in some stock recoveries, but only for sideloading files directly signed by the manufacturer. In regards to TWRP, is the bootloader unlocked? If not, that would explain why it didn't work. Other than that, I don't believe you'll have any other options besides reloading the stock firmware.
Hi,
Thanks for the reply. Yes, the bootloader was / is unlocked.
Unfortunately, there isn't any stock firmware available anywhere. Unless someone out there has a backed up rom image from the EE Kestrel?
This is supposed to be a working TWRP for your device http://forum.xda-developers.com/showpost.php?p=58522448&postcount=117 - if you get it loaded, there might be a chance to push the working build.prop back to the phone. I would read that thread too and see if there isn't more useful info there or another member with your phone that could make a backup for you. Good luck.
Thanks.
Unfortunately, I'm pretty sure that is the TWRP I've tried. I'll double check when I'm on my PC.
I might try requesting a rom image on that thread, but the community for this phone seems to be pretty dead :/
I've just gone and ordered a new phone anyway, but it seems like a waste of a good phone just for the sake of one line of bad code!
Thanks for your help. I'll post again if I have any success.