Related
I've got the HTC Hero from Orange and noticed that the ROM version is higher than the one posted in this forum (Build 1.76.61.3). If somebody could explain how to pull the ROM from the phone I'd be happy to post it.
can u adb into it? if so you just need to type the following in command prompt if your using windows:
adb pull /system
Sweet god you can be a hero if you can use adb and type the following command:
adb pull /proc/config.gz .
and attach the file here!
You can load the 1.3.1 recovery (i think) and nandroid backup the system!
*************THIS IS A GUESS ON HOW TO DO IT!*****************
I bet someone will help you get this dumped!
but you can probably dump the following like so:
adb pull /system ./system (make the folder in your adb directory)
adb pull /data ./data (make the folder in your adb directory)
adb pull /etc ./etc (make the folder in your adb directory)
cat /dev/mtd/mtd1 > /sdcard/recovery.img
cat /dev/mtd/mtd2 > /sdcard/boot.img
adb pull /sdcard/recovery.img . < there is a . after it and it needs to be there! >
adb pull /sdcard/boot.img . < there is a . after it and it needs to be there! >
This would be my guess on how to do it, but i could be wrong.
I'm downloading the SDK now, will post back if I managed to get anything from the phone.
PS: If I post all those things will any of my personal settings/data be included?
I've tried all those commands, the only one that worked is the adb pull /system ./system , it didn't work for etc and data, reckoned there weren't any files to copy. the cat... ones just didn't do anything. I'm guessing this is because I'm not rooted on the phone. Any suggestions?
herman3101 said:
I've tried all those commands, the only one that worked is the adb pull /system ./system , it didn't work for etc and data, reckoned there weren't any files to copy. the cat... ones just didn't do anything. I'm guessing this is because I'm not rooted on the phone. Any suggestions?
Click to expand...
Click to collapse
System is enough Now please upload it to megaupload/rapidshare
Does system include any user modified files or is it read only during use?
herman3101 said:
Does system include any user modified files or is it read only during use?
Click to expand...
Click to collapse
system is readonly
Excellent, it's still uploading and I will update my other post with the link once it's done. I've also uploaded the config.gz as somebody requested it.
Thank you very much I thing JAC can make a great rom out of this!
upload finished, link on other thread
this thread is done
for more info and the rom look here
http://forum.xda-developers.com/showthread.php?t=540680
My phone is on 4.1.2 still, and I had edited the build.prop to not update to 4.2 (after hearing all the problems). Now that 4.2.2. is out i decided to update, I tried restoring the build.prop file that i had as a backup of 4.1.2. I guess I must've changed some text without realizing.
Now my phone is stuck, it gives me the Google Logo with the unlocked sign, and then it disappears...and where there should be a boot animation...black. Nothing. Stays like that.
Any way I can push the build.prop via the computer using abd or something?
Not sure if adb will push to system, since i had an issue pulling from system.
Are you rooted?
You could try booting to recovery to enable adb, then remount system as r/w
adb shell
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
cd /system/ NOT SURE IF THIS IS REQUIRED, I'D TRY IT FIRST WITHOUT THIS LINE TO SEE
chmod 644 build.prop
chown root.root build.prop
exit
I've never had to do that, but i belive my linux syntax is correct, i pulled it from http://www.linux.org/article/view/file-permissions-chown. This is only of course if the build.prop failed bc on the incorrect permissions and ownership(maybe you had it on your sdcard). If this doesn't work, it looks like you'll be fastboot flashing a system image. [Sometimes the time and date of your build.prop may affect the ability to ota even if you get it to boot, to which you would need to reflash the system image anyway]. But i'd like to know if you try this and it works.
So what I ended up doing was installing clockwork recovery and then installing an odexed Rom version of the stock image of 4.1.2. Everything works, nothing got wiped.
Sent from my GT-N7100 using xda app-developers app
bodh said:
Not sure if adb will push to system, since i had an issue pulling from system.
Are you rooted?
You could try booting to recovery to enable adb, then remount system as r/w
adb shell
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
cd /system/ NOT SURE IF THIS IS REQUIRED, I'D TRY IT FIRST WITHOUT THIS LINE TO SEE
chmod 644 build.prop
chown root.root build.prop
exit
I've never had to do that, but i belive my linux syntax is correct, i pulled it from http://www.linux.org/article/view/file-permissions-chown. This is only of course if the build.prop failed bc on the incorrect permissions and ownership(maybe you had it on your sdcard). If this doesn't work, it looks like you'll be fastboot flashing a system image. [Sometimes the time and date of your build.prop may affect the ability to ota even if you get it to boot, to which you would need to reflash the system image anyway]. But i'd like to know if you try this and it works.
Click to expand...
Click to collapse
Yes, you need to 'cd /system' before typing the commands to change permissions and ownership, as you have them.
Sent from my Nexus
ksc6000 said:
So what I ended up doing was installing clockwork recovery and then installing an odexed Rom version of the stock image of 4.1.2. Everything works, nothing got wiped.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
How did you install clockwork recovery when it was not booting at all ??! Could you please guide me ? I actually have an LG Optimus G stuck in boot loop ..... (T_T)
Claureid said:
How did you install clockwork recovery when it was not booting at all ??! Could you please guide me ? I actually have an LG Optimus G stuck in boot loop ..... (T_T)
Click to expand...
Click to collapse
Then you should go to your own forums, as 99% of the info here wont do you any good
Claureid said:
How did you install clockwork recovery when it was not booting at all ??! Could you pbootlease guide me ? I actually have an LG Optimus G stuck in boot loop ..... (T_T)
Click to expand...
Click to collapse
I don't think you can do that with your phone what I did. But here is the gu ide that I used to temporarily boot into clockwork recovery to use it:
http://forum.xda-developers.com/showpost.php?p=23229578&postcount=3
ksc6000 said:
I don't think you can do that with your phone what I did. But here is the gu ide that I used to temporarily boot into clockwork recovery to use it:
http://forum.xda-developers.com/showpost.php?p=23229578&postcount=3
Click to expand...
Click to collapse
Thanked you buddy !!
OK I used the kit at port for smt210r and I tryed to add build.props and it gets stuck at boot any ideas
dsilx said:
OK I used the kit at port for smt210r and I tryed to add build.props and it gets stuck at boot any ideas
Click to expand...
Click to collapse
d,
did you reset permissions on build.prop to 644 ?
if not boot to recovery, connect to pc
in terminal, assuming you are using linux, enter;
adb start-server
adb remount
adb shell
and wait for service to start and bring up prompt
then at prompt
# chmod 644 /system/build.prop
exit and reboot
m
no windows 7/8
moonbutt74 said:
d,
did you reset permissions on build.prop to 644 ?
if not boot to recovery, connect to pc
in terminal, assuming you are using linux, enter;
adb start-server
adb remount
adb shell
and wait for service to start and bring up prompt
then at prompt
# chmod 644 /system/build.prop
exit and reboot
m
Click to expand...
Click to collapse
hi no im using windows its different sadly and how can i see if i reset the build.prop to 644 plse for give me i am new to this and il try to do adb
all i know is when i started editing the rom it wouldnt let me edit it so i had to go on my computer and edit it with notpad ++
okay
dsilx said:
hi no im using windows its different sadly and how can i see if i reset the build.prop to 644 plse for give me i am new to this and il try to do adb
all i know is when i started editing the rom it wouldnt let me edit it so i had to go on my computer and edit it with notpad ++
Click to expand...
Click to collapse
notepad++ is good,
unless you set something wrong inside build.prop then it is the wrong permissions on the file
download aromafm http://forum.xda-developers.com/attachment.php?attachmentid=2231581&stc=1&d=1378202418
install just like any zip in recovery just make sure you mount system from recovery. navigate to /system long press on
build.prop and select change permissions. and you should be good unless like i said you got something wrong in
build.prop itself.
m
Just flash the latest update. All my updates include a build.prop.
gr8nole said:
Just flash the latest update. All my updates include a build.prop.
Click to expand...
Click to collapse
Yes, but learning how to get around things has value..
m
link pls and thanks
gr8nole said:
Just flash the latest update. All my updates include a build.prop.
Click to expand...
Click to collapse
Can I pls have the link and @moonbutt74 thanks for all our help I'm just a little confused on what to do with the aroma cause I don't see build.prop
But thank u for all the help
dsilx said:
Can I pls have the link and @moonbutt74 thanks for all our help I'm just a little confused on what to do with the aroma cause I don't see build.prop
But thank u for all the help
Click to expand...
Click to collapse
before your run aromafm, select mounts option in recovery and mount /system , then run aromafm.
there is an option in aromafm to automount all partitions, very helpful.
it takes a little till you get the hang of using it. very good tool.
m
I wanted to download an app on my samsung galaxy tab 3 smt211 which is not compatible .So i decided to change build.prop,but that doesnt yield any result.So then i copied complete build.prop of nexus 5 and replaced my tab's original one.Now my device isnt booting.I have a backup of original build.prop,Please suggest now what should i do???
will flashing stock rom help me out????
ashu220087 said:
I wanted to download an app on my samsung galaxy tab 3 smt211 which is not compatible .So i decided to change build.prop,but that doesnt yield any result.So then i copied complete build.prop of nexus 5 and replaced my tab's original one.Now my device isnt booting.I have a backup of original build.prop,Please suggest now what should i do???
will flashing stock rom help me out????
Click to expand...
Click to collapse
Boot into your custom recovery, and use the File Manager option or use Aroma File manager to perform the following:
Mount /system
Copy your build.prop backup to the /system folder.
Then, reboot.
Your custom recovery may or may not have a built in File Manager (depends which recovery you are using). If not, you can download and use Aroma File Manager. Flash it like a rom and a file manager will open.
thanks
i have already flashed stock rom and solved the issue
i used your cwm recovery only(techbeast)
But after flashing stock rom i m aving various problems.
Tab switches off on its own.
Apps stop working
System ui also stop working.
Why is it happening ??
But after flashing stock rom i m having various problems.
Tab switches off on its own.
Apps stop working
System ui also stop working.
Why is it happening ?
gr8nole said:
Boot into your custom recovery, and use the File Manager option or use Aroma File manager to perform the following:
Mount /system
Copy your build.prop backup to the /system folder.
Then, reboot.
Your custom recovery may or may not have a built in File Manager (depends which recovery you are using). If not, you can download and use Aroma File Manager. Flash it like a rom and a file manager will open.
Click to expand...
Click to collapse
ashu220087 said:
I wanted to download an app on my samsung galaxy tab 3 smt211 which is not compatible .So i decided to change build.prop,but that doesnt yield any result.So then i copied complete build.prop of nexus 5 and replaced my tab's original one.Now my device isnt booting.I have a backup of original build.prop,Please suggest now what should i do???
will flashing stock rom help me out????
Click to expand...
Click to collapse
in recovery, connect to pc
adb shell
chmod 644 /system/build.prop
reboot
if you still loop, push the original, again, recovery, connect
adb push <your build.prop> /system/
adb shell
chmod 644 /system/build.prop
if you get permission warning, remount rw and do it again, either
adb remount
adb root
or
adb shell
mount -o rw.remount /system
m
Unmodified factory images extracted from the Robin - Updated for Android 6.0.1 build 00WW_1_450 (released on 07 Oct 2016)
This is flashable zip, and it requires TWRP. Note that while the zip includes the boot.img, it doesn't include the recovery - so you can continue using TWRP if you've flashed it. If you wish to return to 100% stock, flash the included recovery.img file as well.
Download:
https://www.androidfilehost.com/f/Robin-Factory-Images
Note: If your Robin is currently unencrypted and you want it to remain that way, don't forget to flash the modified boot.img immediately after flashing the ROM, or else your device will become encrypted again.
Note:The official fastboot images can be found here: https://community.nextbit.com/t5/Tools/Nextbit-Robin-Factory-Images/m-p/10649
Disclaimer: The files and instructions provided herein are meant for users who understand and accept the risks of flashing firmware files. I will not be held responsible for any loss or damages that could occur as a result of following these instructions, downloading or flashing these files.
Good job @[deXter]! We'll get the official ones posted soon.
Thanks for posting that!
D
Nextbit_Khang said:
Good job @[deXter]! We'll get the official ones posted soon.
Click to expand...
Click to collapse
Any news Khang? Not to push, but I remember you saying your original plan was to get these out by the end of the month.
Hey @Nickamina - Foxconn is working with us, but it's been slow going. We don't have an ETA just yet, but are hoping soon we'll have the factory images available since people have been having trouble with the OTA (if they have TWRP installed).
the update zip is corrupt, i believe it so. thts why ppl keep getting error in update.
Nextbit_Khang said:
Hey @Nickamina - Foxconn is working with us, but it's been slow going. We don't have an ETA just yet, but are hoping soon we'll have the factory images available since people have been having trouble with the OTA (if they have TWRP installed).
Click to expand...
Click to collapse
i second that. did the update today. went to stock recovery. little robot and everything. got about 1/4 of the way and went to stock recovery menu. wiped data and cache thinking that it had finished the update. now i have a robin that won't boot. i did not wipe system, but the phone will not boot. any thoughts on how to get it back up and running? adb twrp and then flash stock image from this thread? any help would be appreciated.
@lordlittlebrooks yes, enter twrp and push the system image and mentioned above
D
Hi all,
I've uploaded the factory images for the new build 00WW1_19F (released on 29th March).
Please see the updated OP for full instructions.
So being a flashable zip in TWRP, would it be possible to just sideload? Or push and move to /cache/ since my data is encrypted? If so, just flash and wipe cache and I'll be golden then? Thanks!
Both sideloading and flashing from /cache should be possible, in theory. I'm currently running unencrypted so I can't confirm, so I would be interested to see what your results are.
[deXter] said:
Both sideloading and flashing from /cache should be possible, in theory. I'm currently running unencrypted so I can't confirm, so I would be interested to see what your results are.
Click to expand...
Click to collapse
Alright, well I'll do this when I get home then, seems like a more reliable way than unrooting and going back to stock to update!
The only thing that gets me is not being able to wipe dalvik through recovery though. Is it possible to wipe beforehand on terminal emulator, and then continue on through recovery by any chance?
PhlexPlexico said:
Is it possible to wipe beforehand on terminal emulator, and then continue on through recovery by any chance?
Click to expand...
Click to collapse
su
cd /data
rm -rf dalvik-cache
mkdir dalvik-cache
chmod 0771 dalvik-cache
Don't forget to reboot immediately, or else apps may start to crash and weird things will happen.
[deXter] said:
su
cd /data
rm -rf dalvik-cache
mkdir dalvik-cache
chmod 0771 dalvik-cache
Don't forget to reboot immediately, or else apps may start to crash and weird things will happen.
Click to expand...
Click to collapse
Would it be possible just to:
cd /data/dalvik-cache
rm -f *
Reboot
Could I do that since I won't have to mess with chmod as well? I mean, it's obviously no big deal but would this work too?
PhlexPlexico said:
Would it be possible just to:
cd /data/dalvik-cache
rm -f *
Reboot
Could I do that since I won't have to mess with chmod as well? I mean, it's obviously no big deal but would this work too?
Click to expand...
Click to collapse
No, because the dalvik-cache contains sub-folders.
You could rm -rf the sub-folders if you wanted to though, but that's just extra commands.
PhlexPlexico said:
Would it be possible just to:
cd /data/dalvik-cache
rm -f *
Reboot
Could I do that since I won't have to mess with chmod as well? I mean, it's obviously no big deal but would this work too?
Click to expand...
Click to collapse
I just tested this out in the terminal - you could cd to the dalvik-cache folder and run "rm -rf *". This will get rid of all the files and subfolders in the dalvik-cache folder, and you don't have to mess with the permissions.
[deXter] said:
I just tested this out in the terminal - you could cd to the dalvik-cache folder and run "rm -rf *". This will get rid of all the files and subfolders in the dalvik-cache folder, and you don't have to mess with the permissions.
Click to expand...
Click to collapse
Oh perfect! Thanks!
[deXter] said:
I just tested this out in the terminal - you could cd to the dalvik-cache folder and run "rm -rf *". This will get rid of all the files and subfolders in the dalvik-cache folder, and you don't have to mess with the permissions.
Click to expand...
Click to collapse
Sorry about the double post, but here's an update so far. Gonna try sideloading next but when I tried to move it to cache adb spat out an error stating: failed to copy 'update.zip' to '/cache//update.zip': No space left on device
So yeah, will try sideloading in a little bit here!
Alright! Went through sideload and so far success! Here's the steps that I did:
1) Get Terminal Emulator
1.a) su
1.b) cd /data/dalvik-cache/
1.c) rm -rf *
1.d) reboot recovery
2) Navigate to sideload feature (Advanced -> ADB Sideload)
3) On PC (got superSU back because I like my root)
Code:
G:\Users\XXXX\Downloads>adb sideload update.zip
Total xfer: 1.00x
G:\Users\XXXX\Downloads>adb sideload BETA-SuperSU-v2.68-20160228150503.zip
Total xfer: 1.56x
G:\Users\XXXX\Downloads>
Afterwards, wiped cache from recovery, and rebooted! Now just optimizing apps! May install xposed here after all is said and done, but seems to be golden! Thanks Dexter! You may have to teach me how to create some of these update zips!
Sorry, dumb question that everyone hates. I'm currently rooted, unencrypted with TWRP installed: is it possible to just dirty flash over the top of my current ROM and not lose my system data without losing everything and then flash the no-encryption zip?
Thanks a lot.
mnp said:
Sorry, dumb question that everyone hates. I'm currently rooted, unencrypted with TWRP installed: is it possible to just dirty flash over the top of my current ROM and not lose my system data without losing everything and then flash the no-encryption zip?
Thanks a lot.
Click to expand...
Click to collapse
Yep you can dirty flash. Just make sure you flash the no-encryption mod, followed by supersu immediately after (in that order).