Long time lurker, first time poster.
I pulled a pretty stupid move, but hoping for some assitance if possible. So I updated to 893 before going through the forever root. Attempted to root via Pete's Tools. That failed out (of course).
At this point I am thinking about what an idiot I am. Then I think of something even more rediculous to do. I (for some reason) attempted to recover the system back to rev 886 (so I could go through the forever root process) through the RSD lite with the html file for 886. This again, failed out after trying to flash the system img.
Luckily, I had the 893 rev on my external SD card. I made an attempt to reflash that where it again failed out.
I also attempted to recover with the script found here
When attempting to run any of the scripts it would return the line ".... is not recognized as an internal or external command, operable program or batch file"
I am guessing my only hope lies with the ability to go through the fast boot with 893 files? Perhaps there is some setting I am missing to be able to recover through forever root??
Thoughts? Links? Help? Please tell me the Krakken has not conquered me....
Thanks,
Nick
Perhaps figuring out the issue with the forever root to restore the bionic might be best...any suggestions. I haven't found anything from searching...
Try doing this in post 2
http://www.mydroidworld.com/forums/...-your-phone-back-upgrade-path.html#post106072
I am an effing tard. I fixed the issues with the forever root. This thread can be deleted.
Related
I have been trying to unroot my nook color because I am unable to log into my Google account so I can't access the Market (can't establish a reliable connection to Google server). I guess I kind of screwed it up when trying to update from 1.0.0 to 1.1.0. Not sure what's going on there. I've tried to unroot by interrupting the boot 8 times along with all the other methods (ADB Shell is beyond me). When I interrupt the root, on about the 8th time it automatically boots into the clockwork recovery and I can't unroot from there. Any solutions to either of my problems would be greatly appreciated. Currently still on 1.0.0.
Try this: http://forum.xda-developers.com/showthread.php?t=931720
If it doesn't work, let me know. I have a more involved method. The above didn't work for me for some reason but worked for lots of other folks.
I'm having a hard time turning the clockwork_1gb-0.4.tar.gz file into a .img file. I've tried it with winimage and win32diskimager and I can't get the programs to recognize the file.
Did you extract it first? If you have, try getting a linux live cd and using dd, winimage doesnt always work.
I'm kind of a noob to all this stuff and I don't know how to extract this type of file. Is there any way you could post the .img file?
If you just click on the file, it should extract. Or maybe right click on it. Sorry, I'm on a mac so don't know the exact Windows menu structure.
Thanks for the help. I was able to resolve this issue by installing the CWR remover.
Hello all, there had been a lot about the root.bat and errors lately, and it is probably because I never gave a good explanation. So, here it is.
The root.bat was written based off of what djrbliss had written for the esteem. I have expanded it and redone most of it to fix problems and make things easier. It is coded first to run the exploit to get temp root access. After that I have coded it to remove any straggling root files (su, superuser, etc) from when people were rooted before. If those files were not there for whatever reason (never rooted before, etc) it will shoot back errors, but continue the process. I added this for those that were not able to attain root because of the "file already exists" error which would end the process. After removing files it then pushes the newest su and superuser files. After that it copies the stock recovery to your sdcard, then pushes cwm recovery.
Hope this helps shed some light on the errors, and helps to explain a little more about it. Thanks everyone for all of the encouragement and donations for my work, it is all greatly appreciated!
Sent from my VS910 4G using xda premium
That should clear things up. Based on a post I replied to earlier, that helps explain that the errors are normal and that the root process your batch file runs is doing it's job correctly.
Thanks MT!,
-Cybie
All,
I have an HD+ running 2.0.5 and its rooted. When I've turned on wifi, half the time it tries to update to 2.0.6. It always goes through its process then dies at 99% and drops back telling me that something is wrong. The first time I freaked out and thought something really WAS wrong.
Boy was I relieved to see that I still had my stock root.
I was just thinking that maybe I should update to 2.0.6 just to keep it current. I use the Nook side for reading and stuff as it is. Can I just rerun the root process like I did for 2.0.5?
Also what is the best way to make it not fail the update?
I did the white-on-white fix, but changed it back.
Please don't tell me I need to do the 8 boot factory reset.
Thanks,
-Jeff
How did you change back the white on white? I suspect that is what is wrong.
Sent from my Nook HD+ running CM10 on Hybrid SD
Since the fix made a backup of the original file, I just renamed the original back to it's proper name.
I moved the orig to a new temp name. Then I copied the active "fixed" one to a something.bak or something like that.
Then I renamed the original one (with the temp name) back to the original/active name.
Upon renaming it crashed, and rebooted. The w-o-w fix was gone.
BTW, looking back at that description it's a bit messy. If it doesn't make sense I'll just put the commands down (as I recall them)
-Jeff
js5752 said:
Since the fix made a backup of the original file, I just renamed the original back to it's proper name.
I moved the orig to a new temp name. Then I copied the active "fixed" one to a something.bak or something like that.
Then I renamed the original one (with the temp name) back to the original/active name.
Upon renaming it crashed, and rebooted. The w-o-w fix was gone.
BTW, looking back at that description it's a bit messy. If it doesn't make sense I'll just put the commands down (as I recall them)
-Jeff
Click to expand...
Click to collapse
No, I understand what you did. You left the symlink in /system and just manipulated the files in /data. That works to get rid of white on white, but does not put framework-res.apk back in /system. And the update zip needs framework-res.apk there. That is why it was failing.
Did you do a back up of your system before you added white on white like I recommended? If so, restore that and then update. If you did not, you can try putting that original framework-res.apk back in /system/etc via ADB. Doing it with ADB prevents that crashing you experienced the first time.
As a last resort go back to 2.0.0 with my plain stock zip in my HD/HD+ CWM thread. You can flash that and it will not erase your media files. You should backup your system with CWM first. Then wipe /data, then flash the zip. Then sign on, register and it will update you to 2.0.6. Then go to CWM and do an advanced restore of /data. Then flash again the zips you want, like root or gapps. Then you should be ok.
Edit: If you want to keep 2.0.5 and not be bothered by those attempts to update, I just added to both my Tips thread and my CWM thread linked in my signature a method to stop those updates.
Sent from my Nook HD+ running CM10 on Hybrid SD
Thanks for the reply.
I expected the crash from what I had read. I just decided that ADB was more hassle than it was worth for a quick change. That and I like to live dangerously
Ok, the symlink vs the data file makes sense. Now I understand why it wasn't working. Thank you, because I thought all was back where it should be.
As for backups, I did one before rooting, and I've done a couple since just to make sure I've got backups. That plus titanium, I figured I should be able to recover if the worst happens.
Thanks for the tips, and for all the work you've done on rooting these devices. It was the option to root that tipped me over the edge to buy one, and I'm glad I did.
-Jeff
Hey. I'm a noob.
My phone is 24 hours old. I dig it. I did the kitkat OTA. Verizon. Was 12A when i got it, now it's 24A.
I don't like being put in a box, so I rooted the phone. I have a problem though. Here's what i did:
Lot's of reading and research.
I downloaded and installed the ADT bundle for sdk and adb on my Windows 8 desktop.
I downloaded and installed drivers from LG.
I downloaded and unzipped autoprime's IOroot25.
I achieved a good handshake between adb and the phone. (adb devices command).
I set USB connection to Internet/Ethernet, enabled Debugging, airplane mode.
I ran the root.bat.
It stopped right away and asked me to sideload the desired file. I freaked out.
Then i moved the kk-root.zip to my adb/sdk/platform-tools folder and sideloaded it. It rooted the phone in 5 seconds and asked me to reboot, so I did. The phone now says it's rooted.
BUT - the autoprime routine didn't finish. So it never steered me to backing up the EFS.
I think I should do that next.
Can anyone steer me to a tute, or tell me how?
THANKS!
I went back and looked at things. I tried it again, this time running the command prompt from the ioroot folder. It did the same thing.
So I think I did it right the first time.
The Joey Krim app sez I have root, and the phone sez I have root.
Where are the backup EFS files stored? I looked around and can't really find anything on my pc that jumps out at me.
Thx.
Geez.
Got it.
I read so much stuff today that i apparently started missing really obvious things.
If you run ioroot25 on 4.4.2, the script doesn't back up the EFS files. It says that right on the tute.
Sorry to clutter the board with trash. Delete this thread if you can mods.
Thx.
Hi everybody,
hopefully someone here can answer a few questions for me.
I have a Samsung Galaxy 3 mini.
android version 4.4.2
kernel version 3.4.0-1670137
baseband version g730aucubng4
my service provider is AT&T
what I want to do is pretty simple, or so I thought.
I read this article ( https://www.androidpit.com/galaxy-s3-note2-memory-bump) about swapping your phone's internal and external storage so the thing doesn't get so full of apps etc. it runs like crap.
I thought "hey, I haven't rooted my phone yet for fear of loosing stuff, but it's old and slow and if it's that easy, why not"
I rooted it using kingo-root, but decided to use o-nandroid backup to create a backup before I did anything. I fallowed these instructions (http://forum.xda-developers.com/showthread.php?t=1620255/) but during the process of flashing the zip file I got a failure message and managed to wipe my memory loosing everything that wasn't on the external sd card.
anyway, to make a long story short, after 4 days of messing with different apps and trying, unsuccessfully, to do various tasks (mainly dealing with creating backups. using twrp, cwm, titanium backup) I think I've discovered the problem.
contrary to what I had read, my android device's boot-loader was not unlocked, or in fact unlockable.
I finally managed to create a backup using Safestrap. but now to my question.
with my bootloader locked, and working through Safestrap, is it possible to use something like the 11extsd2internalsd file from that first article to swap my two hard drives? or am I stuck, since I can't install new kirnels?
--now, someone is bound to say "hey, you should have searched xyz, there is a thread there about this exact thing". I thought I'd respond to that now and save them the trouble. I have spent the past 5 hours searching, googleing, and reading articles about this. so far, I have learned a lot, but I'm tired and quite frustrated with the whole endeavor.
so I thought I would try asking the experts if it's even possible to do what I originally wanted to do, or if I should just delete all these apps, unroot my phone and go back to deleting my pictures and text messages every other day to save space.
Thanks for having the patiance to read through my tale of woes, hopefully someone will be able to help me out and answer my question.
JM
You can swap internal storage with external SD by editing fstab.<device_name>.
Look, here is this file for my phone (yours will be little different) https://github.com/TeamCanjica/andr...dina/blob/cm-11.0/rootdir/fstab.samsungcodina
Just swap in places this code "voldmanaged=sdcard0"/"voldmanaged=sdcard1"
This file you can edit only after unpacking and repacking boot.img (you need to get ramdisk filesystem, more info and how to http://forum.xda-developers.com/showthread.php?t=2036528).
For flashing boot.img (kernel) after making changes, your device must be rooted (minimum this) or have custom recovery which will let you flash zip package.
As I know, last step is to edit from /system/etc/permissions/platform.xml one line (more info http://trendblog.net/fix-kitkat-sd-card-write-restriction/ )