Hey guys, having a big problem here. Pretty much what the title says. I got my new (used) XT862 this morning, it had been reset to a fresh rom and wasn't rooted. I was so excited to finally get it that I started modding straight away.
First of all, I forgot to jot down the exact version number of the rom. I know already this was really stupid, but I can't do anything about it now... It was 2.3.4... I'm guessing it might have been the original 890? Is there any way to find this out from the recovery menu?
I'll try to describe what I did as completely as possible, I don't know if something might have gone wrong during the process or what.
First I installed Safestrap 3.05 from this link, not realizing that I had to have root (duh). It seemed to install fine, then when I ran it I got the standard "stopped responding" error with the "force close" button.
I then rooted it using Motofail, first I forgot to switch to root on my PC and it stopped at "daemon started successfully" so I hit CTRL+C until it dumped me back to the command line. Then I changed users on my desktop with su, ran it again and it worked perfectly, the superuser app on the phone showed up and it was operating normally.
(Here's what happened the first time I ran Motofail from my non-root user acct, I had to hit CTRL+C twice, once after "daemon started successfully, once after "waiting for phone to reboot" at which I rebooted the phone manually. Was still booting fine at this point.)
Code:
[*]
[*] Motofail: Universal Motorola Gingerbread Root Exploit (Linux version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
^Cerror: protocol fault (no status)
[*] Device found.
[*] Deploying payload...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: insufficient permissions for device
error: insufficient permissions for device
[*] Owning phone...
error: insufficient permissions for device
[*] Rebooting device...
error: insufficient permissions for device
[*] Waiting for phone to reboot.
^C
After rooting it was still booting fine so I think the problem was not there. Once everything was finished and I was back at the home screen I re-ran Safestrap which appeared to be running normally. I was planning to install Minimoto but I ran "create recovery image" first which I figured couldn't hurt. Well, Safestrap worked for a minute, then crashed (the "not responding - force close" error screen came up) and trying to run it again just crashed it immediately.
I did nothing else, just rebooted the phone not realizing the crash had apparently messed up my bootloader? Now I just get a boot loop, it plays the little Droid animation over and over again.
When I boot into the menu with M+power I don't get a Safestrap menu, and running "recovery" from there just gives me a screen with an /!\ icon and the Android character. I get the same screen if I try to boot with X+power.
I've tried to download the fast unbrick rom from here but neither of the links work... The old Dropbox link is long gone and the new Mediafire mirror says its allotment of 10 free downloads per week has been exceeded... infuriating!
Can anyone give me some advice or steer me in the right direction? I was so excited to get my new phone, I'll be heartbroken if I've managed to brick it for good! I don't want to do anymore damage without advice... please help?
********** // **********
EDIT: I found a mirror for fast/easy unbrick and that worked, so I'm now back to the stock 890 rom with functional bootloader and am much relieved. Two questions though:
1 - Can anyone shed some light on what went wrong during the safestrap process that bricked the phone? Was the fact that I tried to install it before I rooted it the cause?
2 - There is still a /safestrap directory on my internal storage (containing only the files "active_slot" and "translate"), should I delete this? Are there other bits of Safestrap left behind that I should get rid of too?
I will eventually try again as I'd really like to run Minimoto on this thing but I want to understand what I did wrong first.
Any info appreciated, thanks!
xjas said:
EDIT: I found a mirror for fast/easy unbrick and that worked, so I'm now back to the stock 890 rom with functional bootloader and am much relieved. Two questions though:
1 - Can anyone shed some light on what went wrong during the safestrap process that bricked the phone? Was the fact that I tried to install it before I rooted it the cause?
2 - There is still a /safestrap directory on my internal storage (containing only the files "active_slot" and "translate"), should I delete this? Are there other bits of Safestrap left behind that I should get rid of too?[/b]
I will eventually try again as I'd really like to run Minimoto on this thing but I want to understand what I did wrong first.
Any info appreciated, thanks!
Click to expand...
Click to collapse
1. I'm not sure why, but I can tell you that I have rooted using Motofail and installed Safetrap 3.05 multiple times without issue. Also, you should realize that Safestrap creates its /system, /data, and /cache directories for each ROM slot on "internal storage", so you need to make sure that you keep enough space there to fit the ROM slots. It's pretty much a given that you should use an external SD card and have the camera app, etc., store data on external SD rather than internal storage. I'd also avoid running apps on "internal storage".
2. It won't hurt to delete those files.
So, you should be able to:
- clear out enough storage on "internal storage". Make sure that you have at least 1 GB more than the data partition you want to create available, though I would want more
- enable USB debugging and root using Motofail
- *then* install Safestrap and install recovery
- do a full reboot to make sure that both the Safestrap menu pops up and the phone restarts fully without looping, etc. (In other words, make sure that stock boots and runs fine.)
- then create a ROM slot, activate it, flash Minimoto and have fun.
Well, went back through the whole process and it went great the second time. Now have Minimoto 1.7 running on a 3 GB partition (probably way overkill??) I'm really enjoying the minimalism in this release, no more sifting through pages of uninstallable crap in the menu to get the stuff I actually use. The extra speed & free memory makes a nice bump up from the HTC Dream (with 1.5 Cupcake!) this phone replaces.
Thanks for the advice, still no idea what went wrong the first time but I'm happy it's working how I want now.
Related
Hey guys and gals,
My Galaxy S had an incident which resulted in a broken, non-responsive touchscreen. The phone itself is working and appears to have lost no data. I'd like to backup the phone in whole. Got it attached via USB and Dev mode, ADB, Droid Explorer and Android Screencast are working. Z4Root installed. Thought of two ways of backing-up the phone:
1. Use Android Screencast to backup through some GUI app. Problem: AS can't control the phone, give it control (by modifying /data/local) since the ADB shell has no root permissions and the app that gives those (Superuser, with Z4Root) is a GUI app. Double-rooting?...
2. Use the ADB shell to boot the phone in recovery mode and backup to the SD card using that. Problem: Need a suitable recovery image that I can control using just the volume and "home" buttons. Some reassurance that it won't screw my data up would also be welcome.
Would appreciate any help!
Edit: Downloaded recovery-clockwork-2.5.1.2-galaxys.zip (from a 2010 blog post by Koushik Dutta. Can't post a link due to technical reasons). Can I rename it update.zip and flash it from the default recovery? If so, than I would be able to do a Nandroid backup, wouldn't I?
Edit: Current build is xxJP7 with recovery version 3e, which means installing a new recovery image is going to be problematic. Also, no CF-Root version intended for this build. Unverified reports that other versions work for this build as well, but not in a hurry to risk it.
Edit: Managed to install the SpeedMod kernel using Odin 3 1.52 (and ADB and Android Screencast), following a guide written by Rodney Chua ("Tourist in Paradise" blog). Managed to backup in whole using the new recovery. Haven't been successful in testing the backup through the SDK emulator. Also wasn't able to repair the Android Screencast problem despite having root control through the new recovery.
Any way of testing a recovery image for integrity?
Edit: The strangest thing happened on the way to the forum: I Started Android Screencast and had GUI control over my phone, while my shell suddenly had root permissions. I used that chance to install the latest ClockworkMod recovery, and after getting the okay I tried to backup from within the program. After a couple of seconds my phone suddenly showed the old 3e recovery (which shouldn't really be there) with an error message. A reboot from ADB was normal, and a reboot to recovery brought me back to the SpeedMod recovery I've recently installed. No trace of a new Nandroid backup, and I've no Android Screencast control anymore.
I did find out, though, that the shell root permissions are due to Droid Explorer presumably running the adb root command on startup.
Edit: Somehow lost the IMEI and all related data. A Reboot sorted this somehow, though. Some icon and widget placement was lost, presumably do to the device clearing the dalvik cache after I've tried fixing the Android Screencast issue. Have the nandroid backup (and nothing significant has changed since doing that), so I don't care much. Android Screencast positively related to having ADB running with root permissions, though it occasionally stops working and requires an ADB and/or Android Screencast restart.
Edit: To sum things up, managed to do what I wanted to do - Got a complete nandroid backup.
Heard from adb based backup but would be interested too. Any similar to odin but in "pull" mode?
So I'm a bit of genius and decided I'd try to fully fix my 99% functional phone and have now made it so it won't boot into home screen... I believe I corrupted blur-services.apk and/or blurcontacts.apk, so I get greeted with a series of crash screens.
What I did? I copied over some Bell XT860 system files (including blur-services.apk) from a system dump in Root Explorer, which caused a crash in the middle of copying. After rebooting the phone, it won't properly go into home screen. I tried a system recovery with no luck, oops.
So I'm hoping/assuming that copying over blur-services.apk properly through ADB might solve the issue, but I can't get into ADB on my phone. I've tried using bp-tools & psouza's tool for temp ADB rooting, with no luck -- it won't pickup the connection, even though my phone's storage is available on my computer and clearly connects. Granted, I might be missing a step somewhere...
If someone could guide me into getting into ADB, I can push the blur-services files properly and hopefully regain control over my phone again...
I must say... if I can get this phone operational again, I will stop messing with it!
Two issues...
1) I could use a non-corrupted copy of each of these files [along with their respective odex files]...
2) I can't get into ADB on my phone. I've tried using bp-tools & psouza's tool for temp ADB rooting, with no luck -- it won't pickup the connection, even though my phone's storage is available on my computer and clearly connects.
I must say... if I can get this phone operational again, I will stop messing with it!
Update:
Luckily for me, I was still able to access my gmail and launched Android Market from there. This allowed me to download Go Launcher, GO Contacts, etc. and at least restore functioning to my phone. Most importantly, this enabled me to check off USB debugging (which I lost when I foolishly reset my phone).
So now I've got a semi-functional phone that gives me error messages at least every 30 seconds about one of the .com applications closing.
However, there is hope that I can get her fully functional since I can now obtain ADB access!
---------- Post added at 02:08 AM ---------- Previous post was at 01:44 AM ----------
Sweet, after being able to check USB debugging, I was able to save my self again using psouza4's tools and guidance.... I really have no idea where noobs like me would be without his help!
Main Lessons:
1) Don't play with your phone too much without a proper SBF
2) If you're like me and can't resist, DO NOT FACTORY RESET YOUR PHONE. This only makes the problem worse.
This tool is based on the original D4 Utility with additions and rewrites by me. Doing any of this is at your own risk.
08/14 Tool Version now 2.0 !!! THE JUMP TOOL IS DEAD!!! No reason for this now that we have ICS Fastboot files.
08/31 Tool Version now 2.1 Here's what's new
10/25 Tool Version 2.2 corrected minor script error and updated to safestrap 3.05
1. Set of instruction included within the tool. Once you open the tool select menu 1 to display them. This is a .txt file so you must have some reader (I use notepad++).
2. Safestrap 3.05 (Thanks Hashcode)
3. Latest Superuser (3.1.3) and binary (3.1.1)
4. Restore to 6.16.217 ICS or upgrade a GB phone to 6.16.217 ICS with option to save or erase data
5. Unroot script - This will remove superuser, the su binary and busybox. However if you boot into recovery it will still indicate root or at least past root (qe display in recovery). Even a fastboot with data wipe will not reset this.
Where to download: http://d-h.st/users/jsnweitzel
Add the ICS fastboot file to the lite tool to run menu 11 or 12. Get it here: http://sbf.droid-developers.org/cdma_maserati/list.php Then unzip it and add the files to the "files" folder of the tool.
If you have trouble connecting your phone be sure you have the latest drivers installed from moto:
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/78460/p/30,6720,8302
Use this tool at your own risk.
Can't wait to try this to go from .213 to .215! Will let you know my results. Right now, there are too many bugs in .213 for me to use it on a daily basis, hope .215 is better!
Edit: nevermind, d-h.st is back up again!
Edit 2: update went very smoothly, thanks!
Edit 3: fixed my issues with a data wipe - almost got bricked, but your tool saved me again! Now I'm back in action with .215 and having the best phone experience ever. If I could hit 'thanks' multiple times, I would!
Works just fine! Thank you very much!
..
Works great!!! Thanks
I just pushed this to my phone and now it is running soo much better (mostly due to the new build of the ICS leak) I was missing a home button and the lock screen, but so far not seeing too many bugs and I have root again. Brilliant! Cheers!
Just giving post a bump, updated tool.
FYI, there is no link to the .217 OTA zip in the OP.
Dave Lister said:
FYI, there is no link to the .217 OTA zip in the OP.
Click to expand...
Click to collapse
Thanks for the heads up. Fixed the link.
So let's see I'm reading this correctly.
I installed the 217 leak file today (got tired of waiting for the ota soak test) and lost root.
To get it back I just need the lite version linked above, is that correct?
bdbraaten said:
So let's see I'm reading this correctly.
I installed the 217 leak file today (got tired of waiting for the ota soak test) and lost root.
To get it back I just need the lite version linked above, is that correct?
Click to expand...
Click to collapse
Yes only menu 9 will not work, everything else should be good.
jsnweitzel said:
Yes only menu 9 will not work, everything else should be good.
Click to expand...
Click to collapse
Any thoughts on what's going on, I tried it and ran option 8 to root but my root apps aren't working. Here's what the screen says:
---------------------------------------------------
[*]
[*] Motorola ICS Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
[*] Device found.
[*] Rebooting device...
[*] Waiting for device to reboot...
[*] Rebooting device again...
[*] Waiting for device to reboot...
[*] Attemping persistence...
remount succeeded
1397 KB/s (0 bytes in 22364.000s)
2321 KB/s (0 bytes in 2005736.000s)
2196 KB/s (0 bytes in 843503.000s)
[*] Cleaning up...
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
---------------------------------------------------
So it looks like it worked I don't see superuser in my app drawer and when I try an app that can use root like estrongs file explorer it says "feature not available"
Any ideas? I've tried it multiple times and with two different computers (one on vista the other xp pro) and same result.
Thanks.
It look like the install of busybox and superuser were skipped (failed is probably more accurate) for some reason. Did you have the phone set to "MTP" or "PTP" mode. You don't want to run it in mass storage.
jsnweitzel said:
It look like the install of busybox and superuser were skipped (failed is probably more accurate) for some reason. Did you have the phone set to "MTP" or "PTP" mode. You don't want to run it in mass storage.
Click to expand...
Click to collapse
I don't remember which one it was set as. Does it make a difference on mtp or ptp mode for which one works better?
I have only seen an issue with the mass storage mode. Check in the tool files folder and be sure that a copy of Superuser.apk is there. If it still doesn't work I can't see why. As a last resort you could try installing it from the market.
jsnweitzel said:
I have only seen an issue with the mass storage mode. Check in the tool files folder and be sure that a copy of Superuser.apk is there. If it still doesn't work I can't see why. As a last resort you could try installing it from the market.
Click to expand...
Click to collapse
Thanks for the help, the superuser is there in the files folder.
I'm debating if I should try it from the market or just try fastbooting the phone and see what happens.
I only want to root to get rid of the bloat, not sure if I'll install custom roms or not yet on this one.
You can "disable" some apps without root. Looking under settings and apps. Select one and hit disable. For some you will have to uninstall updates first.
jsnweitzel said:
You can "disable" some apps without root. Looking under settings and apps. Select one and hit disable. For some you will have to uninstall updates first.
Click to expand...
Click to collapse
I'll look into that.
I'm going to try downloading the full tool and try that, I was just using the lite version. It shouldn't make a difference but I figure it doesn't hurt to try it. If that fails I'll try to decide what my next step will be.
I tried to install superuser from the market but it wouldn't let me.
just get the one on the market and update the binary and it should work fine.. tib wiil fix the perms when you run it the first time. tried it b4 and it works fine
myfishbear said:
just get the one on the market and update the binary and it should work fine.. tib wiil fix the perms when you run it the first time. tried it b4 and it works fine
Click to expand...
Click to collapse
Are you talking about the superuser app from the market? I tried to get it and it wouldn't let me install it, claims it's already installed but it doesn't show up in my app drawer.
---------- Post added at 11:04 AM ---------- Previous post was at 10:57 AM ----------
I GOT IT!!!!!!!!
I had an idea based on the comment about getting from the market so I tried the idea and it worked.
I copied the superuser apk file over to my sd card, I installed it from there and said to go ahead and replace the file that was there. I opened it directly after the install and updated the binarys (said it was current but did it anyway) now my root apps ask for and get super user permission.
So it looks like I'm up and running.
Thanks,
Brent.
Hi, I have SGS I9000 for over 2 years now, and today, I unlocked it and it just started to reboot, by itself. As far as the start goes is moment when it needs to switch between "starting aplicatios" and home screen. Then he goes again into starting android mode (it doesn't turn off completly, just android reeboting). It worked fine before seconds before.
I have MIUI android V4 and I've tried everything, wiping, restoring, but main problem is that I have some unsynced contacts and sms that I need but I can't access them. Can you help me please? (only way I can access internal storage is boot/mount/mount USB, because of the restarting thing)
something must be segfaulting everytime it comes to load the UI, what does adb logcat say?
Could you please tell me how to check adb logcat? I don't know much about phones but I'm willing to learn
unzip the adb package below, open a command prompt in that directory and type adb.exe logcat
you need Android Debug Bridge drivers installed, windows should do the job for you, unless you're on crappy vista
if it gets stuck on - waiting for device - you don't have those drivers
Tank you SuicideFlasher on your replies but I managed everything by my self :victory: I flashed my phone with Odin and got semaphore kernel, but it got stuck in a boor loop again. I then copied restore folder from my computer to internal storage (that i previously saved there), reinstalled CWM with Odin and restored the system that worked (I backup ed all data) and now I completely formated my phone to start over. Congrats if any of this makes any sence but it worked for me :good:
it's good to see beginners trying to fix stuff by themselves :good: you have good probabilites of becoming a dev one day imo
anyway, by using logcat you would just have watched the phone freak out in that bootloop while seeing in detail whatever the log could tell you, but i think that log would have frightened the hell out of you if your knowledge is really that minimal atm
Hello guys,
I hope someone can help me with this problem...
So the thing is - yesterday I finally got OneUI 3 and Android 11 update (yay?). But ofcourse as soon as the phone rebooted and optimised all the apps and came back to main screen it rebooted after a minute or so...everytime. As soon as I enter my pin and unlock the phone it reboots after a short period.
The same problem happened when I de-bloated the phone a while ago via ADB - but I then enabled back all the apps except facebook and some "safe to debloat apps" which were not even system apps and it has since worked for almost a year. But here we go again....
I even "re enabled/installed" all the apps I could list in ADB ( so basically all the apps on the phone) and then went to wipe cache - but still no go.
I am also wondering if there is a posibility to somehow mount storage just to copy some files to my computer (which are important, and my latest backup is around a month old) and then I'll gladly do a a factory reset - no problem.
Any help would be appreciated, thanks!
If you're able to use ADB to enable/install apps, then you should be able to use "adb pull path/to/files" to copy the files to your computer. You could reboot into recovery mode and see if your computer pulls up the storage that way too. Also, if you have TWRP, you can use the file system to copy files to an external SD card. So you have a few options to get your files.
You can also create a back-up of specific apps (and their data) using "adb backup -f MyBackUpName.ab com.corp.AppName".
TacoDeMuerte said:
If you're able to use ADB to enable/install apps, then you should be able to use "adb pull path/to/files" to copy the files to your computer. You could reboot into recovery mode and see if your computer pulls up the storage that way too. Also, if you have TWRP, you can use the file system to copy files to an external SD card. So you have a few options to get your files.
You can also create a back-up of specific apps (and their data) using "adb backup -f MyBackUpName.ab com.corp.AppName".
Click to expand...
Click to collapse
Hello, thanks for the reply and helping out.
But all the commands and stuff is kinda useless because the phone reboots sooner than in 30 seconds after getting to the main screen. When I boot to recovery the storage doesn't get mounted.......
And I would've had TWRP but the phone is still under warranty so that's a shame, because on my backup phone I have it (and so did on all the previous ones) and it would be great. But IIRC if I install TWRP now, the phone needs to be wiped.
FFS samsung, what is this....because I now read a couple threads and posts on social media people having exactly same problem, and some didn't do anything with ADB prior to update. shame...