So I know I WAS rooted at one point, up until about a week ago. Then all of a sudden a few days ago I went to flash the latest CM6 nightly, and opened up TitaniumBackup to make sure I had everything backed up. It said that it didn't have root access. I rooted back on 1.5 or 1.6, using Fresh's 1-click method. Will that still work even though I'm running a Froyo ROM now? Sorry if this has been asked and answered before, but I couldn't find anything searching. I can still boot to recovery, and flash ROMs, but the apps that require root access (TitaniumBackup, drocap2, Superuser, wifi tether) say they can't gain root access. I did flash a file suggested by impaler to try to fix issues with adding SU permissions, and it seems that this issue started about that time.
I can't install the Android SDK (no internet access besides my phone, and that doesn't want to play nice with the servers for some reason), so I should specify that this should be non-ADB if possible.
SirRipo said:
So I know I WAS rooted at one point, up until about a week ago. Then all of a sudden a few days ago I went to flash the latest CM6 nightly, and opened up TitaniumBackup to make sure I had everything backed up. It said that it didn't have root access. I rooted back on 1.5 or 1.6, using Fresh's 1-click method. Will that still work even though I'm running a Froyo ROM now? Sorry if this has been asked and answered before, but I couldn't find anything searching.
Click to expand...
Click to collapse
Universal AndRoot. Check it out. http://bit.ly/aa4jxJ
Unfortunately, that didn't work. Titanium still says it can't acquire root. I tried both options, and both times it said failed.
I had that happen once and when I checked Superuser TB was "denied". I "allowed" it in Super User and it worked.
Sent from my HERO200 using XDA App
if you do a nandroid restore it seems to do the same for me i just do the restore then reflash the build without wiping data and its been working fine
thoughtlesskyle said:
if you do a nandroid restore it seems to do the same for me i just do the restore then reflash the build without wiping data and its been working fine
Click to expand...
Click to collapse
Will give this a shot later tonight once my phone charges. I hate how it takes so long to charge via USB.
I took this screenshot on the xda app one day way back when I had the same problem you did. I asked for help and this guy got it for me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SirRipo said:
Will give this a shot later tonight once my phone charges. I hate how it takes so long to charge via USB.
Click to expand...
Click to collapse
This worked. Thanks for the tip.
Sprint said no Froyo for Hero, I said eff that.
Related
I've been stuck in a boot loop on one of my G-Tabs for about 4 days now. Been trying every fix I can find to no avail so far. I have the Viewsonic to G-Tablet boot loop. I keep noticing people reffering to using NVFlash with the Img9 fix to add in ClockWord mod. Many said to do that flash then to wipe the data, which is where the problem lies. I get this error everytime I try:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas?
Repartition 2048 and 0.
Hello KJ and thanks for replying, I have seen you offer help to alot of people so thanks for dropping by here too.
I have tried that as well and it hasn't done anything. I don't know if it is the order in which I am doing things or what on this tab. My other one works like a dream but it was done before the 4539 (I think that's right) update came out.
I have done the NV Flash and added CWM via Ext SD and then partitioned and that was a no go. I also tried doing Roebeet's example of doing NVFlash and changing te Img9 file as well with a repart and that didn't work either.
I also tried this "fix" and even it didn't work.
http://forum.xda-developers.com/showthread.php?t=974422
I'm not giving up because from all I am reading, these things seem immpossible to fully brick. I also feel pretty safe to say that it is my fault and that maybe I don't have the correct order for doing the entire process but I have tried until I turned blue in the face before giving up and going to bed.
Well... what your tablet is having trouble mounting is the partitions that you should be creating with the repartitioning. /dev/blk/mmcblk3 is the internal memory. Are you familiar with ADB?
No not at all. I googled during this and saw Android Debug Manager. Something with that I should try? I definitely don't claim to be the smartest guy on the block but at the same time I pick up this stuff well and am not really scared to try something if you have an idea.
Congrats, man. I think you're the first to truly brick his gtab.
tunez23 said:
No not at all. I googled during this and saw Android Debug Manager. Something with that I should try? I definitely don't claim to be the smartest guy on the block but at the same time I pick up this stuff well and am not really scared to try something if you have an idea.
Click to expand...
Click to collapse
Unfortunately, I'm not a good enough teacher (I lack the proper patience) to get someone going with ADB from scratch. Especially since my development environment is somewhat unusual so I often have no frame of reference to assist in setting up the tools. So, if you're up to it, you need to do one of two things. Either get ADB installed and running on your computer or get a rooted ROM and a terminal emulator on the device that we need to work on.
Your situation is somewhat different from the others in that you can actually get CWM installed and get into recovery. I still think that perhaps some combination of partitioning, data wipe and fix permissions should be working for you. What I would do in your case is:
1) Data wipe one more time (perhaps use: http://forum.xda-developers.com/showthread.php?t=1030915)
2) Reboot into CWM recovery and repartition
3) nvflash the stock ROM again (without CWM)
4) Factory reset from the ROM settings
If that fails then research setting up ADB for your computer and we'll discuss some diagnostics you can run from that.
Thanks KJ, I will try those when I get home this evening.
So I downloaded RCMix's sense 3.5 rom and it was running pretty smooth until about 4 days later I downloaded the six axis controller demo app to see if I could hook up a PS3 controller to my Sensation 4G. When it asked for root access it force closed. At first I was like "whatever its probably the app". Then I uninstalled it and reinstalled it again and the same thing happened. Then I used titanium backup to start backing up my apps and it said that I didn't have root access, then it told me to restart the app and so I did. When I restarted it, it asked for root access, I clicked accept and it force closed. Then I started getting really worried; after a while it said that titanium backup was granted su. I successfully backed up all my apps before titanium backup crashed and told me I had no root. I switched to Android Revolution HD and wanted to see if I had solved the problem, turns out I completely have no root. I looked up the superuser app on the market and people are losing root due to the update. I'm worried as to how to get root back and switching to another rom just for the simple fact that my phone might brick itself if something goes wrong. Does anyone have an idea as to what I can do about it?
frostyroot said:
So I downloaded RCMix's sense 3.5 rom and it was running pretty smooth until about 4 days later I downloaded the six axis controller demo app to see if I could hook up a PS3 controller to my Sensation 4G. When it asked for root access it force closed. At first I was like "whatever its probably the app". Then I uninstalled it and reinstalled it again and the same thing happened. Then I used titanium backup to start backing up my apps and it said that I didn't have root access, then it told me to restart the app and so I did. When I restarted it, it asked for root access, I clicked accept and it force closed. Then I started getting really worried; after a while it said that titanium backup was granted su. I successfully backed up all my apps before titanium backup crashed and told me I had no root. I switched to Android Revolution HD and wanted to see if I had solved the problem, turns out I completely have no root. I looked up the superuser app on the market and people are losing root due to the update. I'm worried as to how to get root back and switching to another rom just for the simple fact that my phone might brick itself if something goes wrong. Does anyone have an idea as to what I can do about it?
Click to expand...
Click to collapse
Hi,
It sounds like a common Super User problem.
Try updating super user to 3.0.6,then go into preferences and update SU binaries to 3.0.1.
This seems to have cleared up the problem for most people.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It still doesn't work!
Try going into settings -> Applications-> manage applications
Find superuser in the list and then choose uninstall updates (you also need to go into the app and disable automatic updating.
It worked for me so hopefully you will have some luck too!
They have just update the binary, that will help with those FC. Download the newest superuser, update the binary (settings>bottom), then delete data (Home>Settings>Programs>superuser>delete data)
Then it should work
frostyroot said:
It still doesn't work!
Click to expand...
Click to collapse
Hi,
You have to keep trying.
It will eventually work.
Got root access back!
Sent from my HTC Sensation XE with Beats Audio using XDA App
I guess you'll find out shortly cause i'm about to do it
Factory reset should not touch /system which is where the binary and apk reside.
Sent from my MB865
Well, here are some preliminary findings
After rooting I was not able to use my phone for USB Mass storage, not exactly sure why, just an observation. Before root, it worked fine.
After FR, I am now able to use my phone for USB MS again. However, upon the first time trying to mount it as MS device I got a pop up window telling me of one or more problems on the disk (sdcard) and it said that happens when a file or files were not done writing to the card before it was unmounted. Not sure how that could have happened, but it did. It gave me two options, scan and fix Atrix 2 or scan w/o fixing Atrix 2. Choosing option 1 would run checkdisc and attempt to fix any problems found, that's what I did and it fixed the problem.
After rooting I was unable to check for system updates, let me clarify....I could physically tell the phone to check for them but I would get an error that said "Check for system update is not available at this time, please try again later."
After FR, I get a different message that states "Your device is up to date, no update necessary at this time."
After rooting I was able to use MyBackup Root to backup all my apps and stuff.
After FR, this is what I get when trying to open the app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am going to install SU to see if that changes anything re: root access, will post back with update.
i launched Titanium Backup the other day after rebooting and it said i didnt have root. rebooted again and launched the app, root came back....its really weird... had this happen on the Atrix 1 as well. even on custom roms that are pre-rooted.
A lot of times it is because the superuser app is not running or failed to launch. Opening superuser and going back to whatever app complained usually works for me.
IMO, I haven't even rooted this device (yet) but that's my experience on my last phone.
koriflame said:
A lot of times it is because the superuser app is not running or failed to launch. Opening superuser and going back to whatever app complained usually works for me.
IMO, I haven't even rooted this device (yet) but that's my experience on my last phone.
Click to expand...
Click to collapse
out of all the devices i have and have had, the atrix and the atrix 2 are the only ones i have seen this on.
It's worth a try, next time it occurs. Again, I haven't done anything with this device specifically, so it could be something else.
I've decided not to try it, nothing really to gain at this point since rooting this phone doesn't accomplish much yet.
I rooted my phone, I think... I did get these errors:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Goes on for about 30 lines...
Is that normal and safe?
What's next? What do I do from here? I really have no idea what to do or what I can do. Please share any information on the world of a rooted android device
Looks normal to me. It pushed busybox and superuser to system, which means you're rooted and can now run root apps. Just reboot and you're done.
plainjane said:
Looks normal to me. It pushed busybox and superuser to system, which means you're rooted and can now run root apps. Just reboot and you're done.
Click to expand...
Click to collapse
It came with superuser, but what does it do? I did not find busybox. Where can I find it and how does it work? It auto rebooted. Where can I get rooted apps and what else can I do?
dalawh said:
Where can I get rooted apps and what else can I do?
Click to expand...
Click to collapse
You can get rooted apps from the market or just download and flash them. Titanium Backup, Superuser, ROM Manager are examples.
ROM manager will also let you flash clockworkmod recovery, the basic tool for installing new roms/kernels/radios.
Your world is just beginning, really.
thebobp said:
You can get rooted apps from the market or just download and flash them. Titanium Backup, Superuser, ROM Manager are examples.
ROM manager will also let you flash clockworkmod recovery, the basic tool for installing new roms/kernels/radios.
Your world is just beginning, really.
Click to expand...
Click to collapse
There seems to be so much to learn, yet I know so little where to start. Is there a specitic thread you would recommend?
dalawh said:
There seems to be so much to learn, yet I know so little where to start. Is there a specitic thread you would recommend?
Click to expand...
Click to collapse
Firstly, there's a different sub-forum for each phone, so find yours' and hopefully they have a good FAQ. Once you've installed cwm, here is a tutorial for installing ROMs on Galaxy Nexus; it should mostly carry over. There's likely more tutorials around google/youtube for your own specific phone.
For titanium backup, always remember to backup user apps ONLY. Never, ever backup system apps or system data, because with custom roms you'll be changing the system. For a "full" (we call it "nandroid") backup use cwm.
thebobp said:
Firstly, there's a different sub-forum for each phone, so find yours' and hopefully they have a good FAQ. Once you've installed cwm, here is a tutorial for installing ROMs on Galaxy Nexus; it should mostly carry over. There's likely more tutorials around google/youtube for your own specific phone.
For titanium backup, always remember to backup user apps ONLY. Never, ever backup system apps or system data, because with custom roms you'll be changing the system. For a "full" (we call it "nandroid") backup use cwm.
Click to expand...
Click to collapse
I have a Samsung Exhibit. I only see threads on Exhibit II.
Btw, where is the backup user apps ONLY? TB is really confusing.
ii got a new tf300t n it has a .17 build n it wont update to .29 or .26
i keep checking n its unsuccessfullll
how to foce or manually update?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
any one?
Do what it says in this manual - basically, you download the appropriate firmware (.29 for US) from ASUS.com, unzip the file once, put that on an SD card, insert the card in your tablet and you should see a notification that the system has found the update file.
i heard people say you will not be able to root if you update manually
who the hell Zips a Zip file?
update detected after extracting to micro sd
and also successfull!!!
nooktablet said:
i heard people say you will not be able to root if you update manually
Click to expand...
Click to collapse
Not true anymore. miloj took care of that in this thread: http://forum.xda-developers.com/showthread.php?t=1704209
should this be failing?
nooktablet said:
i heard people say you will not be able to root if you update manually
Click to expand...
Click to collapse
I was on .17 and got root using Sparkyroot. Backed up root with OTA rootkeeper and then manually upgraded to .29. Lost root. Tried to regain root with OTA rootkeeper and was unsuccessful. Still trying to regain root and will be monitoring here and a few other threads for a solution.
As for Miloj's thread...it may work, but it is waaaaay beyond my tech knowledge. I was sweating the one click Sparkyroot root method. I did try reading it a few times and all I got out of it was "I really shouldn't try this without adult supervision".
For now I have a working tablet on .29. I guess I can wait a few more weeks (or months) for a one click Sparkyroot type program for root on .29 (or later update)
kindrudekid said:
who the hell Zips a Zip file?
Click to expand...
Click to collapse
ASUS, apparently
As for your last post, when I was rooting my tab (when I was still on stock ROM), the update also failed until I downloaded BusyBox Installer from Play Store and installed the latest version of BusyBox. But then again, your checking for busybox line says OK, mine had 'native', so dunno if it'll work (or if you have already done that) but if you haven't, it can't hurt to try, right?
yes thats what happened to me too!!!!!
lost root even after using the OTA Root keeper
But i Downloaded this its the same method by Miloj http://forum.xda-developers.com/showthread.php?t=1706588
but with a batch based GUI
its simple attach see to it drivers are present
select 1 and wait and press yes when asked to compare GUID UID is same with a few line above the yes/no prompt
den installed JRummy's busy box and got the above screenshot
my OCD with such stuff is etching to get a green OKay
w3by said:
ASUS, apparently
As for your last post, when I was rooting my tab (when I was still on stock ROM), the update also failed until I downloaded BusyBox Installer from Play Store and installed the latest version of BusyBox. But then again, your checking for busybox line says OK, mine had 'native', so dunno if it'll work (or if you have already done that) but if you haven't, it can't hurt to try, right?
Click to expand...
Click to collapse
i got the busybox fixed using Jrummy's Busybox installer
You could find all that you want about TF300T here:
[INDEX][14 JUN 12] INDEX of ROMS/RECOVERY/ROOT/GUIDES/HBOOT/RADIOS/TWEAKS etc...
It's not really difficult to found, it's stickied