[XT860] Help is needed (urgent) - Motorola Droid 3

i tried xUltimate to deodexing my XT860 and...... since then ו'm stuck in boot loop

Do you have a bootstrap/safestrap installed?
Sent from my DROID3 using xda premium

Endoroid said:
Do you have a bootstrap/safestrap installed?
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
i have Safestrap Recovery 1.08
when i:
Safestrap => backup and restore => restore => external SD => (appear)
nonsafe-2012-01-31 (the one i got)
run it, and
checking MD5 sums.....
MD5 mismatch!

boazal said:
i have Safestrap Recovery 1.08
when i:
Safestrap => backup and restore => restore => external SD => (appear)
nonsafe-2012-01-31 (the one i got)
run it, and
checking MD5 sums.....
MD5 mismatch!
Click to expand...
Click to collapse
****ty. I don't know if there is a way to fix that. Do you happen to have the tweaked safestrap that allows flashing the nonsafe
Sent from my XT860 using xda premium

If yes to my last question, just flash the stock bell 2.3.6 rom located in the dev forum. If no then you have 2 options. First it follow the steps in this thread http://forum.xda-developers.com/showthread.php?t=1404608
Or
Use motofastboot to flash a system.img, this will restore the /system, reroot, install bootstrap and then flash the already deodexed stock bell rom I previously mentioned to restore your /system, remove bootstrap, install safestrap and flash either that rom, or the rom of your choice into safe system and use safe system from now on.
Sent from my XT860 using xda premium

You can manually find the MD5s on a computer and edit the MD5 file manually to make it work, its dangerous but it works... I've done it before

DeadChex said:
You can manually find the MD5s on a computer and edit the MD5 file manually to make it work, its dangerous but it works... I've done it before
Click to expand...
Click to collapse
I've had that same problem in the past. How do you manually edit the md5 and how do you know what to change it to. Would I just run the md5 command in terminal and then unzip the backup and modify it?
Sent from my XT860 using xda premium

Endoroid said:
I've had that same problem in the past. How do you manually edit the md5 and how do you know what to change it to. Would I just run the md5 command in terminal and then unzip the backup and modify it?
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
The back up should just be a folder, open the folder, and run the MD5 Command in the Terminal on each of the backup archives (eg cache.ext3.tar, system.ext3.tar) and put them into nandroid.md5
The nandroid.md5 file should hopefully be laid out easily and just replace the hashes (random letters and numbers) with the ones you generated with the correct file's hash
And Restore away!

Endoroid said:
Do you happen to have the tweaked safestrap that allows flashing the nonsafe
Click to expand...
Click to collapse
don't know, how to find out?

boazal said:
don't know, how to find out?
Click to expand...
Click to collapse
V1.08d
Sent from my XT860 using xda premium

Endoroid said:
V1.08d
Click to expand...
Click to collapse
it's v1.08,
what can be done?

Either attempt to fix the md5sum as mentioned above, or restore your system through one of the options I mentioned in my previous post
Sent from my XT860 using xda premium

Endoroid said:
Either attempt to fix the md5sum as mentioned above, or restore your system through one of the options I mentioned in my previous post
Click to expand...
Click to collapse
sorry for bothering, i'm not familiar with the process, can you guide newbi? (preferred flash the rom methods)

people's, please i need assistance.....

boazal said:
people's, please i need assistance.....
Click to expand...
Click to collapse
Im at work but later tonight I will give more detailed instructions
Sent from my XT860 using xda premium

Method- Manually Altering MD5 Sums (Windows) (This guide might be off, Windows is not my home OS anymore...)
1. Plug your SD card into your computer.
2. Open up the directory where your back ups are should be /safestrap/backup/BACKUPNAME
3. Download this tool: http://www.pc-tools.net/win32/md5sums/
4. Drag system.ext3.tar and drop it on top of the applications icon
Write down that MD5
5. Drag data.ext3.tar and drop it on top of the applications icon
Write down that MD5
6. Drag cache.ext3.tar and drop it on top of the applications icon
Write down that MD5
7. open up nandroid.md5 with a text editor it should look something like this:
Code:
2ce2ec3c4beac74ba3fba94fb290ea21 cache.ext3.tar
12296836011615c7f2611e19c9390a78 data.ext3.tar
0589700a289739c448b6ff2e317d7951 system.ext3.tar
Replace the hash next to cache.ext3.tar with the one you generated, and repeat this for the other files...
IF nandroid.md5 does not exist, create it and do as mentioned above.
Then... Restore!
Sorry, I know this isn't the easy reflash you wanted but it's the only guide I can write at this time
(This guide was written going off of safestrap 1.08 you may have to change some titles of files)
Thanks and/or donate if I helped
Method- Manually Altering MD5 Sums (Linux-Ubuntu)
1. Plug your SD card into your computer.
2. Open up the directory where your back ups are should be /safestrap/backup/BACKUPNAME
4. Run md5sum on system.ext3.tar
Write down that MD5
5. Run md5sum on data.ext3.tar
Write down that MD5
6. Run md5sum on cache.ext3.tar
Write down that MD5
7. open up nandroid.md5 with a text editor it should look something like this:
Code:
2ce2ec3c4beac74ba3fba94fb290ea21 cache.ext3.tar
12296836011615c7f2611e19c9390a78 data.ext3.tar
0589700a289739c448b6ff2e317d7951 system.ext3.tar
Replace the hash next to cache.ext3.tar with the one you generated, and repeat this for the other files...
IF nandroid.md5 does not exist, create it and do as mentioned above.
Then... Restore!

You're gonna have to do the leg work to get the files and programs I mention because finding and linking while on my fine is a pita.
There is another option, the easiest of all, however it will remove you from the bell update path as we have no way currently of returning to the stock bell firmware. You can grab rsdlite and a fastboot package from the dev forum and flash that, it will fix it up but you are no longer on bell firmware. Up to you if you can live with that.
The other way is to grab motofastboot (google it) and a fastboot package from dev forum. Unzip the fastboot package into a folder and put motofasboot in the same folder. Motofastboot is a command line utility, it has no user interface. Open a cmd prompt (start button, run, cmd) and type cd C:\your\path\to\aforementioned\folder then run
moto-fastboot flash system system.img (I have the 32 bit version so mine is moto-fastboot32) I dont use windows, onlinux I have to precede the command with ./ so for me it would look like
./moto-fastboot32 flash system system.img
Your phone will now boot
Find zergrush easy root utility and follow the directions for it to root your phone, then install a bootstrap(or the tweaked safestrap that allows nonsafe flashing and then go grab the stock bell rom from dev forum and flash that. It is already deodexed.
this will keep you stock bell
Sent from my XT860 using xda premium

DeadChex said:
Method- Manually Altering MD5 Sums (Windows) (This guide might be off, Windows is not my home OS anymore...)
1. Plug your SD card into your computer.
2. Open up the directory where your back ups are should be /safestrap/backup/BACKUPNAME
3. Download this tool: http://www.pc-tools.net/win32/md5sums/
4. Drag system.ext3.tar and drop it on top of the applications icon
Write down that MD5
5. Drag data.ext3.tar and drop it on top of the applications icon
Write down that MD5
6. Drag cache.ext3.tar and drop it on top of the applications icon
Write down that MD5
7. open up nandroid.md5 with a text editor it should look something like this:
Code:
2ce2ec3c4beac74ba3fba94fb290ea21 cache.ext3.tar
12296836011615c7f2611e19c9390a78 data.ext3.tar
0589700a289739c448b6ff2e317d7951 system.ext3.tar
Replace the hash next to cache.ext3.tar with the one you generated, and repeat this for the other files...
IF nandroid.md5 does not exist, create it and do as mentioned above.
Then... Restore!
Sorry, I know this isn't the easy reflash you wanted but it's the only guide I can write at this time
(This guide was written going off of safestrap 1.08 you may have to change some titles of files)
Thanks and/or donate if I helped
Click to expand...
Click to collapse
First i 'ant to thank you
when i open my nandroid.md5 it was empty
i do the exact method, and create the 4 hash (cache, data, system, systemorig) on nandroid.md5 put it back on the phone, try to restore but ...no success. Still receive MD5 mismatch
when I return the SD carde to the pc, the nandroid.md5 empty again!

Endoroid said:
The other way is to grab motofastboot (google it) and a fastboot package from dev forum. Unzip the fastboot package into a folder and put motofasboot in the same folder. Motofastboot is a command line utility, it has no user interface. Open a cmd prompt (start button, run, cmd) and type cd C:\your\path\to\aforementioned\folder then run
moto-fastboot flash system system.img (I have the 32 bit version so mine is moto-fastboot32) I dont use windows, onlinux I have to precede the command with ./ so for me it would look like
./moto-fastboot32 flash system system.img
Your phone will now boot
Click to expand...
Click to collapse
C:\moto-fastboot-win32>moto-fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 25.386s]
writing 'system'... OKAY [ 15.596s]
sending 'system' (175872 KB)... OKAY [ 17.214s]
writing 'system'... OKAY [ 9.043s]
but refuse to boot

boazal said:
First i 'ant to thank you
when i open my nandroid.md5 it was empty
i do the exact method, and create the 4 hash (cache, data, system, systemorig) on nandroid.md5 put it back on the phone, try to restore but ...no success. Still receive MD5 mismatch
when I return the SD carde to the pc, the nandroid.md5 empty again!
Click to expand...
Click to collapse
Linux or Windows? Esure you are safely ejecting (windows) or unmounting/ejecting (Linux) before removing the SDCard, I've noticed file changes sometimes don't stick if you don't safely eject.
I'm not sure if the method I'm giving is a soloution anymore with the reflash (That's not a bad thing!)

Related

Problems in restoring from CWM

Hey guys,
I need help. I just realized that I couldn't restore from CWM backup. I have several backups and I even tried diff version of CWM but all keep saying MD5 checksum match error.
What should I do?
Thanks
Sent from my LG-P990 using XDA App
have you changed the name of them??
They need to be left exactly as the phone makes them
They don't, but you can't have spaces in the name of the folder.
If all else fails, recreate the checksum:
Code:
md5sum *.img > nandriod.md5
Rusty! said:
They don't, but you can't have spaces in the name of the folder.
If all else fails, recreate the checksum:
Code:
md5sum *.img > nandriod.md5
Click to expand...
Click to collapse
not sure i understand this. the code that you mentioned, where should i run it? thanks
Run it via adb shell/terminal in the folder the backup is in
thanks rusty

MD5 Mismatch! How come?

Hi guys. I flashed a new baseband for my Optimus 2x. After that, I wanted to restore my backup and I get a MD5 Mismatch. How come? I didn't rename my backup or changed the recovery. Nothing!
hey, i had this not so long ago, its nothing more than a bad nandroid backup, nothing will fix it, you gotta reflash another backup or start over (i started over cuz other backups were too old)
You may be able to solve it with these steps:
1. Go to the directory of the backup.
2. Delete nandroid.md5
3. Recreate nandroid.md5 of all images with 'md5sum'.
Sent from my Optimus 2X using xda premium
Egan said:
You may be able to solve it with these steps:
1. Go to the directory of the backup.
2. Delete nandroid.md5
3. Recreate nandroid.md5 of all images with 'md5sum'.
Sent from my Optimus 2X using xda premium
Click to expand...
Click to collapse
This will allow you to flash a corrupt image, and is therefore not recommended
I got one just today, really annoying..
@kiljaken any idea why it happens, or how it can be avoided?
Imperticus said:
I got one just today, really annoying..
@kiljaken any idea why it happens, or how it can be avoided?
Click to expand...
Click to collapse
Not really no. All it takes is one changed bit in either file
My guess is you renamed the folder with a space, if so, try without it, if not then recreate the md5 as mentioned the MD5 with md5sum * > nandroid.md5
I always have this issue when I make the back up through Rom Manager. So I always make it now in clockwork recovery mode.
Rusty! said:
My guess is you renamed the folder with a space, if so, try without it, if not then recreate the md5 as mentioned the MD5 with md5sum * nandroid.md5
Click to expand...
Click to collapse
Works!!! Thank you..
1) rename folder (no spaces)
2) inside the folder, type "rm nandroid.md5"
3) then type "md5sum * > nandroid.md5
Sent from my LG-P990 using XDA App
Good spot, I missed out the >

LG Marquee has root!

I have a Marquee and have successfully rooted using http://androidnerds.net/2011/10/08/lg-esteem-oneclickroot-now-ready/. Apparently the LG Esteem is close enough for this to work. After install, you will need to manually update superuser via the market.
Thanks to Hoovhartid over at androidcentral forums for suggesting this.
Can u make backup for ur gb and upload it here?
Sent from my LG-P970 using XDA App
Fatcobrah, if you can give me instructions how to back it up, I will be glad to upload it. I have root access but not CWM recovery.
tcaudill01 said:
Fatcobrah, if you can give me instructions how to back it up, I will be glad to upload it. I have root access but not CWM recovery.
Click to expand...
Click to collapse
install Rom Manager from the market
ROM manager doesn't give an option for my phone for CWM and you can't back up your ROM without it.
Sorry but not risking bricking this thing if I make the wrong choice.
tcaudill01 said:
ROM manager doesn't give an option for my phone for CWM and you can't back up your ROM without it.
Sorry but not risking bricking this thing if I make the wrong choice.
Click to expand...
Click to collapse
Hmm you can use root explorer to copy all files & folder from root folder to sdcard
Sent from my Optimus Black using Tapatalk
lesp4ul said:
Hmm you can use root explorer to copy all files & folder from root folder to sdcard
Sent from my Optimus Black using Tapatalk
Click to expand...
Click to collapse
+1.and you can use adb to pull all files and boot.img ,and we can test it in a safer way
Okay guys, I thought what the hell, I'll try the LGE Black option in ROM manager and see what happens.
IT WORKS!!!!!!!!!!!!!!!!!!
Use the volume keys to move and the search button to select.
I have backed up the ROM from the Marquee and loaded on Mediafire.
The back up wasn't good, so i pulled the link. Sorry!
Hope this helps.
Sorry folks, I don't think the backup is any good. I tried another and it looks the same. It is too small and doesn't have musch data.
Can someone point me to, or step me through, how to pull all the files with adb. I'll be glad to pull and post.
tcaudill01 said:
Sorry folks, I don't think the backup is any good. I tried another and it looks the same. It is too small and doesn't have musch data.
Can someone point me to, or step me through, how to pull all the files with adb. I'll be glad to pull and post.
Click to expand...
Click to collapse
http://www.addictivetips.com/mobile/how-to-perform-and-restore-a-nandroid-backup/
am kinda noob too..so hope this will help!xD
first of all,you need a adb.exe
you can get it from super-one-click,or android sdk,google it
for example,we pull files at d:\system
copy adb files in d:\system
and then,open cmd(win+R,enter cmd)
connect your phone before we start.
type
Code:
d:
adb pull /system .\system
ok then it will pull all the system files into d:\system
does it back up to a directory on the SD card? if it does, you need all the files in the directory. there should be a few .img files along with the nandroid.md5 file. put them all in a zip and upload it.
look in sdcard: \clockworkmod\backup\
the directory the files are in should be named with a date+time stamp
Any chance?
mike-y said:
does it back up to a directory on the SD card? if it does, you need all the files in the directory. there should be a few .img files along with the nandroid.md5 file. put them all in a zip and upload it.
look in sdcard: \clockworkmod\backup\
the directory the files are in should be named with a date+time stamp
Click to expand...
Click to collapse
I've already tried the CWM backup and it is no good, only about 18 meg in size and missing almost everything important.
That is why I was trying to get directions on how to use ADB to pull system files and image from the phone.
tcaudill01 said:
I've already tried the CWM backup and it is no good, only about 18 meg in size and missing almost everything important.
That is why I was trying to get directions on how to use ADB to pull system files and image from the phone.
Click to expand...
Click to collapse
1. Download Android SDK http://developer.android.com/sdk/index.html
2. Install it on C: (not on Program Files for Easy Access)
3. Connect your phone through USB with debugging on
4. Open Command propt from your PC. (windows button + r / type "cmd" without quotes)
5. On command prompt type "cd c:\Android\ASDK\platform-tools" (without quotes then press Enter)
6. Then type "adb pull /system" (without quotes then press Enter)
7. wait till it's finished pulling the files
Now go to C:Android\ASDK\platform-tools. Copy all files now, zip it. Upload, they'll just exclude/disect the adb ones.
this is interesting. I'm going to try to use this method for rooting our P970.
Advices are welcome
Okay, I used ADB and was able to pull the system, boot.img and recovery.img.
Not sure if any of these are correct. The system file is HUGE (434mb zipped) but looks like every thing is there. Both boot and recovery are 5.00mb each.
If this looks right and is what you are after I will upload it to mediafire.
Let me know.
go go up it!, i wanna see if we can get a nice gingerbread with lg drivers from this.
tcaudill01 said:
Okay, I used ADB and was able to pull the system, boot.img and recovery.img.
Not sure if any of these are correct. The system file is HUGE (434mb zipped) but looks like every thing is there. Both boot and recovery are 5.00mb each.
If this looks right and is what you are after I will upload it to mediafire.
Let me know.
Click to expand...
Click to collapse
Yes... that's exactly what we need... just zip it and upload it...
tcaudill01 said:
Okay, I used ADB and was able to pull the system, boot.img and recovery.img.
Not sure if any of these are correct. The system file is HUGE (434mb zipped) but looks like every thing is there. Both boot and recovery are 5.00mb each.
If this looks right and is what you are after I will upload it to mediafire.
Let me know.
Click to expand...
Click to collapse
nicely done
now let our chef master to cook it

LG thrill 4g one click cwr

hello i have tried to use one click and when i do it said that cannot stat recovery.img no such file or directory if you could help let me
thanks to colbur87
Its in the zip, but make sure you launch 1click_cwr in the same folder as recovery.img
Dont copy it out or anything like that. The program looks for recovery.img to be in the same folder as 1click_cwr.
ok thanks but i am still having a few problem when adb push recovery.img /data it said failed to copy recovery,img to /data/recovery.img permission denied
i have tried keeping it in a zip and extracting it all to the same folder only when i extract it is when i can run as admin and my phone is rooted so that not the problem
You can't run an executable in a zip file. It must be extracted first. Even if you just click it from within the zip file, it is still extracted to a temporary location......
All you need to do is:
Extract the entire folder somewhere on your computer (right click extract(depending on your os/installed zip program, the menu may be different. Just extract it!))
Run 1click_cwr as admin (right click on the icon and click run as administrator)
That it your done......
Make sure USB Debugging mode is ON.
i did extract it all to the same folder and right click as
admin and it said in the cmd
adb push recovery.img /data it said failed to copy recovery,img to /data/recovery.img permission denied
any help would be greatly appreciated
anything i can do in my super user to allow access
any chance i could run this program in Linux
by the way my debugging is on
Well, there are two error I see there....first: can't push file to phone because premission denied.
2nd: Can't change premissions on the file because its not found (because of 1st error).
I would suggest googling 'permission denied adb push' I found a lot of people with your same problem...I can only speak to my application which worked for me and a lot of other people.
Have you tried setting permissions for the /data folder? Use root explorer and long press /data folder and check all nine boxes.
Sent from my LG-P925 using XDA App
dcmcc99 said:
Have you tried setting permissions for the /data folder? Use root explorer and long press /data folder and check all nine boxes.
Sent from my LG-P925 using XDA App
Click to expand...
Click to collapse
thanks that did it
after using one click and i do a factory reset would that brick my thrill
hello.... I just recently bought a Thrill from a person off craigslist. It came rooted and I hadnt known. Is there anything I should be worried about? like if he installed anything that could be tracking the phone or anything? Also, how can I tell what method he used to root it. Basically, how do i figure out how to unroot it and erase everything so i can have the expirence of actually doing everything myself so i understand it.
just use super one click root to unroot the device but you have down load the right one click

Automated system/boot.img unpack/repack script

Hello everyone,
I've been playing around with adding root to my stock ROM these past few days, and have found it very slow and tedious trying to remember all the commands to unpack and repack the images.
To make things simpler I've created a script that automates almost the whole process.
I've named it worker as it does all the work for you, and it is just simply a bash script. But it makes things a lot quicker and easier.
I have only been able to test with my S3 Mini, but should work with any ROM that has boot.img and system.img
Simply extract the .img files from the tar.md5 or .zip ROM file, and place them in the original folder.
Once you have those in the original folder just simply run the worker.txt file from the terminal, making sure you are in the worker folder directory.
When the script is run you will be given the options to unpack/repack system.img, mount system.img (This is after you extract it do not try and mount the original file it wont work), unpack/repack boot.img, unpack/repack ramdisk, create ROM (This will create an odin flashable tar.md5 from the repacked files) and finally clean up (This will clear all unpacked and repacked files only leaving the files in the original folder)
To select an option simply type y then enter to execute that command or just hit enter to skip.
When the system.img is mounted it will be mounted in the mount folder.
When repacking the system.img you will be prompted to enter the file size, if you have and S3 Mini I8190N simply type s3mini for the size (This may work for other S3 models but I have no way of testing so let me know). If you have a different device use the file size of the original UNMODIFIED system.img, enter the size in bytes or MB (If entering in MB use this format, xxx being a number. xxxM).
Please give me feedback for improvements or problems,
Thanks for reading.
P.S. Sorry if in wrong place please move if necessary
EDIT: If you can't run the script with the ./ command, chmod +x the file
Antonyb1995 said:
Hello everyone,
I've been playing around with adding root to my stock ROM these past few days, and have found it very slow and tedious trying to remember all the commands to unpack and repack the images.
To make things simpler I've created a script that automates almost the whole process.
I've named it worker as it does all the work for you, and it is just simply a bash script. But it makes things a lot quicker and easier.
I have only been able to test with my S3 Mini, but should work with any ROM that has boot.img and system.img
Simply extract the .img files from the tar.md5 or .zip ROM file, and place them in the original folder.
Once you have those in the original folder just simply run the worker.txt file from the terminal, making sure you are in the worker folder directory.
When the script is run you will be given the options to unpack/repack system.img, mount system.img (This is after you extract it do not try and mount the original file it wont work), unpack/repack boot.img, unpack/repack ramdisk, create ROM (This will create an odin flashable tar.md5 from the repacked files) and finally clean up (This will clear all unpacked and repacked files only leaving the files in the original folder)
To select an option simply type y then enter to execute that command or just hit enter to skip.
When the system.img is mounted it will be mounted in the mount folder.
When repacking the system.img you will be prompted to enter the file size, if you have and S3 Mini I8190N simply type s3mini for the size (This may work for other S3 models but I have no way of testing so let me know). If you have a different device use the file size of the original UNMODIFIED system.img, enter the size in bytes or MB (If entering in MB use this format, xxx being a number. xxxM).
Please give me feedback for improvements or problems,
Thanks for reading.
P.S. Sorry if in wrong place please move if necessary
Click to expand...
Click to collapse
work on gt-i8200n to?
linklusitano said:
work on gt-i8200n to?
Click to expand...
Click to collapse
No reason why not, I'm just not able to test others
Antonyb1995 said:
No reason why not, I'm just not able to test others
Click to expand...
Click to collapse
testing
linklusitano said:
testing
Click to expand...
Click to collapse
Great let me know if it works!
EDIT: Make sure you enter the right size for the system.img file, the pre entered size using s3mini may work fine as they are very similar devices.
Antonyb1995 said:
Great let me know if it works!
EDIT: Make sure you enter the right size for the system.img file, the pre entered size using s3mini may work fine as they are very similar devices.
Click to expand...
Click to collapse
how do i run worker.txt?
linklusitano said:
how do i run worker.txt?
Click to expand...
Click to collapse
Your using Linux right?
Open a terminal and change directory to the worker folder, once there type ./worker.txt and it should run. If it doesn't issue this command chmod +x worker.txt that should fix it.
Antonyb1995 said:
Your using Linux right?
Open a terminal and change directory to the worker folder, once there type ./worker.txt and it should run. If it doesn't issue this command chmod +x worker.txt that should fix it.
Click to expand...
Click to collapse
windows 8.1
linklusitano said:
windows 8.1
Click to expand...
Click to collapse
Ah okay, If you install Cygwin you can run bash scripts in Windows.
LINK: https://www.cygwin.com/

Categories

Resources