So, I am not 100% certain where I went wrong in all of this, but I know that I did enough to warrant the hassle. If anyone can step in and help educate me for next go-around, I would appreciate it.
I had 4.1.8.3 with Gingerblur 3.1 installed, Gingerbreak via adb, GladEnabler sideloading, webtop modded, debian installed in webtop, Blue Mist theme with Launcher Pro Plus, and the Blue Mist themed Launcher Pro stuffs. I was starting to get some constant restarts of Launcher Pro, wasn't really sure what to do with that, but didn't mess around with it really. I had this setup for a little while, was starting to think about doing it all over, so I got a little risky. I started messing with freezing things in Titanium Backup without knowing truely what to do, thinking thaw was an easy undo. Things were starting to slow up on me and I wanted to experiment with breathing new life into the phone. I ended up borking my Blur accounts irreversibly and my contacts would not sync anymore. I only had the phone numbers that I had manually entered. I had them backed up on the PC and Lookout website, but it seemed like a good time to start over fresh. I already had a nandroid backup from a week earlier, so I did a full app+data backup in Titanium and copied over both SD cards to my PC. Last night I flashed 4.1.5.7 firmware and 4.1.8.3 service firmware and started all over.
I first ran into problems getting adb to recognize my device, so I installed the Android SDK software for Win7 and it updated my adb drivers. Great, it worked. Gingerbreak via adb (remembering to unmount my internal SD card this time) and we have root. Then I ran Glad Enabler, worked great. Then I installed Titanium from the market, restored user apps with data selectively. Everything is looking pretty good, figured I would try out the Atrix mods app in the dev forum. At that point I read closer that the early USB enumeration and 2nd-init scripts needed the NFHimself modded Gingerbreak to utilize the other mods, so I ran that version of gingerbreak (yeah, with root access already) to get files in the right location, everything seemed to go smoothly. At 4:30 am, I called it quits for the night.
In the morning, I figured I would just theme it so I tried out Motobread. Beautiful, btw. I was trying to figure why Titanium wasn't recognizing my Pro license key, and it said to check in settings/applications to see where it was installed. Hmmm, Settings isn't even in the app drawer anymore. So I ran Settings from the home menu and it did nothing. So, I un-rooted with NFHimself's app, re-flashed the 4.1.8.3 service firmware and got the Settings menu back. I then ran NFHimself's Gingerbreak, early USB enumeration and 2nd init, and everything is looking fine.
So now I'm getting ready to CWM install GladiAtrix, installed Flash 10.3 from the market, checked that it worked, and off we go! Everything seemed to go smoothly, the hulu fix works! Checked the webtop stuff when the kids went up for their naps, the menu didn't pop up with HDMI connection, and when I opened it from the app drawer, it told me no loaded web pages for webtop or something to that effect, so I ran the fix patch in CWM and I'm all set. Lxterminal and all.
New nandroid backup now, I guess.
Lessons learned:
-before messing with Blur services, get ready for a long night
-be a little less willing to say 'what the hell' before running something for the first time
Hopefully everyone sees that: a) all of these development tools work if installed correctly, and b) they don't necessarily work if installed incorrectly. I hope someone can learn from my mistakes.
Related
I've been using Alien 4 as my daily driver for a month or so now. Occasionally, I'll run a nandroid, and install something else to "try things out", but I always come back to Alien. Most recently, my SU access on my phone seems to have disabled itself. One day, I'm clicking alond nicely, using titanium for app backup, working with a bunch of other apps that require root, and suddenly, nothing with root works. I was prompted to update Superuser.apk from the market a few weeks ago (memory is a little fuzzy on exact timeline), but I'm thinking that has something to do with it. I have disabled / enabled debugging, attempted to reroot via the howto over at briefmobile, and have pretty much exhausted my googlefu. Has anyone run into this? Does anyone have any thoughts on how to get SU either downgraded, or reinstalled? Keep in mind that because I've lost root, using tools like root explorer or ADB are pretty limited. I wanted to post this over to the Alien Rom thread, but because I'm mostly a lurker, I'm apparently verboten from posting in Dev threads. Thanks for the help in advance.
-BigdogBTS
bigdogbts said:
I've been using Alien 4 as my daily driver for a month or so now. Occasionally, I'll run a nandroid, and install something else to "try things out", but I always come back to Alien. Most recently, my SU access on my phone seems to have disabled itself. One day, I'm clicking alond nicely, using titanium for app backup, working with a bunch of other apps that require root, and suddenly, nothing with root works. I was prompted to update Superuser.apk from the market a few weeks ago (memory is a little fuzzy on exact timeline), but I'm thinking that has something to do with it. I have disabled / enabled debugging, attempted to reroot via the howto over at briefmobile, and have pretty much exhausted my googlefu. Has anyone run into this? Does anyone have any thoughts on how to get SU either downgraded, or reinstalled? Keep in mind that because I've lost root, using tools like root explorer or ADB are pretty limited. I wanted to post this over to the Alien Rom thread, but because I'm mostly a lurker, I'm apparently verboten from posting in Dev threads. Thanks for the help in advance.
-BigdogBTS
Click to expand...
Click to collapse
have you tried using the preinstall method to re-root that eval- posted here: http://forum.xda-developers.com/showpost.php?p=15023022&postcount=2
Apparently I just needed to look one link further:
http://forum.xda-developers.com/showthread.php?t=1255548
Pete's Motorola Root Tools method re-rooted my Atrix. On a side note though, it reinstalled the older version of superuser, which is behaving appropriately. My issues must have been related to the new version.....
So i rooted my wife's tablet when 1.4.0 was on it. everything was working great....until 1.4.1 was pushed. The android market app, android email app and android clock app no longer open. Ive been searching for a solution and i think i may have found one without having to revert back to 1.4.0 and start all over again. If i understand this correctly, all i need to do is this:
Sideload the ADB root hijack.apk file
Follow the Indirect's ADB Root Hijack APP, Allows Root PATCH and Reentry of Root Script video
And i think thats it. Am i missing a step? Also, for what its worth, When i try running the new NThidden app and try to run the unknown sources script, i get a force close everytime. Does this mean that something isnt right with my root? Sorry if im not making some sense...pretty new to this rooting stuff. Thanks in advance.
Honestly, as someone who half knows what I am talking about, I think your best bet is to back everything up, factory reset, and then use the latest and greatest auto root program. This will have the addecd benifit of you never have to worry about it auto updating again!
Everything I have read says 1.4.1 was put in place by people who hate you and want you to be poor. =p
The_Joe said:
Everything I have read says 1.4.1 was put in place by people who hate you and want you to be poor. =p
Click to expand...
Click to collapse
It's not that they want you to be poor; they just want the money that you have to be theirs. They wouldn't begrudge you new money -- as long as you spend it on their services.
This is just me but I would factory reset and follow indirects method with alberts youtube vids..I know people have 1.4.1 going but Im sticking with 1.4.0 until I really need to update. Then watch alberts vids on how to block Over The Air updates and then you wont have to worry bout her tablet getting a forced update.
I'm having the same problem as GMcD.
AFAIK, I used the latest root script that should have blocked the OTA updates. Before I restore to factory and try rooting again, can anyone suggest how I can make sure that the OTAs are disabled again?
Is there any way to verify that the OTA updates have been disabled?
Thanks in advance!
PS much thanks to Indirect and Albert! Great work guys!
go to your settings then device info--> about your NOOK--> Software version should be 9.9.9 if not then it's not blocking OTA's
Frustrated...
Okay, I must be missing something and have hit the point of total frustration I have, I think, a fair amount of experience with rooting (DroidX, GalaxyS, GX2, Axtrix2 and NookColor with NF and HL+ running before they were allowed) so can only guess it's something silly or simple I am overlooking...
I bought my (3) kids NTs for Christmas since I own a fully rooted NC and saw the potential of the device for the price AFTER it was rooted. After they opened and registered them, I jumped online, D/L'd Indirect's scripts (YOU ROCK DUDE!) and had them rooted and on their way in an hour. 5 days later, the stupid 1.4.1 update hits (I was one of those who thought the root alone blocked the OTA) and jacked up all 3 devices.
I have tried EVERY post, hint and tip I can find here to get 1.4.0 back on these devices without success. Things I done:
- Factory reset MULTIPLE times (turning on wifi ONLY long enough to get past the registration screen)
- Downloaded the acclaim_update.zip file multiple times from multiple sites (latest one yesterday afternoon from Indirect's post). I have left it zipped, not changed the name and put it on the root partition of the card.
- Tried 3 different SD cards (all 2GB and have been used for rooting all my other devices without any issues), formatted from the PC and formatted from the NT
No matter what I seem to do, I can't get back to base 1.4.0. FR reverts back to stock 1.4.1 after reset and when I try to boot to the SD cards, the screen flashes a second like it's going to then just errors out saying try again or contact support. I "think" I have followed every post or trick to the letter, but can't get anywhere...
Anyone else seeing this problem or do I just have three jacked up tablets? Am I missing something?
I had just gotten mine rooted (using Indirect method), when I got hit with the update. Luckily I had a titanium backup. Here's what I did:
Restored 1.40 with sd card (did not even move my data, just copied the card to computer just in case it got wiped)
Rooted using updated Indirect method (smoother and easier than 1st time and set version to 9.9.9.
Then restored apps & data from backup (still on sd card)
Only trouble I had was with the drivers (I had to load a program to delete the drivers-don't recall the name but it's in Indirect's troubleshooting drivers thread)
Whole process was a pain but still only took a couple of hours.
Mike
I forgot one step in between the restoring and the rooting:
When I restored to 1.40 my n button wouldn't work so I had to erase and deregister the device (in settings under device info)
Then when I was able to connect I had to register again (no big deal)
Good luck,
Mike
FML
grimknight said:
Okay, I must be missing something and have hit the point of total frustration I have, I think, a fair amount of experience with rooting (DroidX, GalaxyS, GX2, Axtrix2 and NookColor with NF and HL+ running before they were allowed) so can only guess it's something silly or simple I am overlooking...
I bought my (3) kids NTs for Christmas since I own a fully rooted NC and saw the potential of the device for the price AFTER it was rooted. After they opened and registered them, I jumped online, D/L'd Indirect's scripts (YOU ROCK DUDE!) and had them rooted and on their way in an hour. 5 days later, the stupid 1.4.1 update hits (I was one of those who thought the root alone blocked the OTA) and jacked up all 3 devices.
I have tried EVERY post, hint and tip I can find here to get 1.4.0 back on these devices without success. Things I done:
- Factory reset MULTIPLE times (turning on wifi ONLY long enough to get past the registration screen)
- Downloaded the acclaim_update.zip file multiple times from multiple sites (latest one yesterday afternoon from Indirect's post). I have left it zipped, not changed the name and put it on the root partition of the card.
- Tried 3 different SD cards (all 2GB and have been used for rooting all my other devices without any issues), formatted from the PC and formatted from the NT
No matter what I seem to do, I can't get back to base 1.4.0. FR reverts back to stock 1.4.1 after reset and when I try to boot to the SD cards, the screen flashes a second like it's going to then just errors out saying try again or contact support. I "think" I have followed every post or trick to the letter, but can't get anywhere...
Anyone else seeing this problem or do I just have three jacked up tablets? Am I missing something?
Click to expand...
Click to collapse
I am having the same issue. I have tried to dl, re-dl everything possible to get mine to go to a 1.4.0. i just received mine as a gift and tbh i dislike how you have to purchase every little thing on it. SOOOOOOO what can I do to get it to a 1.4.0. I can follow instuctions and just need to warm up on this new technology hehe.. Oh another thing, as im going by albert wertz video, i cant help but to notice that his NT starts at 9.9.9? If I can get mine to go to a 9.9.9 and then restarting from there, I can do that as well. PLZ HELP
my question is, TiBu needs root. Now mine becomes 1.4.1 and TiBu is not working. How can I back up my stuff before reverting it back to 1.4.0?
Unfortunately, you can't. I bit the bullet today and did the 1.4.0 restore, re-root and OTA block. I've had to re-download all my apps and lost any saved game data but it is worth it to me.
I had restored my son's NT and realized how much nicer it is to have a rooted device that didn't require adb commands for installing apps. The entire process took me about 45 minutes with about a third of the time waiting for large app downloads (Madden 12).
Ok so here is the deal. I successfully did the zergrush script (did not know about the 1 click root apk). Either way that was successful, I had installed the market, a lot of google apps and gave it back to the person. Then they decided to install the amazon app store and chose app installer instead of package installer. That messed up apk installations for everything it seemed. During the zerg rush script, it gave me the option to make the "n" button a dedicated home key button, and so I had done that. After I did a factory restore, it remained the homekey button, and now I cannot find the browser or anything, I don't know how to bring up the browser what so ever. I can seemingly access everything else in the 1.4.0 install that it gives me. Unfortunately adb is not working, I can't seem to get the <!>Nook Tablet in the device manager anymore, no matter how many times I try to force and remove the default USB Mass Storage it installs.
Basically i seemed to have screwed myself. Using various search results in both the android development thread and this thread didn't seem to yield results for anyone else dealing with this issue. If anyone can lend me a hand or point me in the right direction, or even show me a thread that someone is dealing with this issue also, that would be fantastic. Thanks community!
Also, I used the script that doesn't allow OTA updates, so it seems the sdcard load acclaim_update.zip doesn't work either.
Well... I have successfully been able to force the 1.4.1 update back onto the device, which has given me "n" menu access. Now I will reattempt to revert back to 1.4.0 and root again.
My error was that I was putting the 1.4.1 update onto the sdcard instead of onto the nook partition.
Hey guys....here's my situation.
I bought a Blu Touch Book 7.0 plus off of Amazon. Got it two nights ago. It's a true phablet. 512 RAM / 512 ROM - I was a little concerned but figured as long as I could root it, I was good to go.
Anyways - no I am not looking for a root. I was able to root it relatively easily after an initial failed attempt which required a factory reset - if anyone is interested, it required PDANET+ & UnlockRoot, SuperOneClick and other methods failed. I threw in a class 10 SD, and modded Android so all apps would be downloaded/installed to my SD card (I did this using the SDK & command prompt in USB debugging mode). I had researched apps previously and began to furiously download and tweak. I threw in a T-Mobile SIM, and everything was going well, I was very happy. It actually seems to be a well made device, though it's a little bulky and the phone function works much better with a bluetooth headset.
Then, I deleted Phone.apk. Despite all apps being downloaded/installed to my SD card, space was still at a premium and I had downloaded a third party dialer. I figured worst case, I could do a factory reset and/or could simply re-download the file (I was actually about to download a good backup program tonight after work, I've been busy the past two days and my anxiety to set up other stuff got the better of me). There was no immediate issue, but shortly later I got the dreaded 'com.android.apk has stopped' (or what not) message popping up constantly. I reset the device, it booted up but it was not reading my sim, and was missing icons. That's when I did something stupid-er. I found a Phone.apk file on the net, downloaded to my device, and copied it to the relevant directory.
Since then, when I boot up, first it shows that Android is upgrading, then it shows the 'unfortunately, the process com.android.apk has stopped.' I click 'Okay,' and it keeps popping up. I wasn't able to delete the wrong Phone.apk as there was not enough time for a longpress between error messages. I was able to initiate a factory reset - I was rather relieved - I had learned a bit the past day or two via trial and error, and I would be able to re-do everything perfectly this time.
But the factory reset did not revert to the right 'Phone.apk' file. So the problem still exists....
If anyone can help me, I would be oh so grateful....thanks...
A factory reset clears all user data & apps. If you deleted the phone app from system, you will have to reflash a stock zip, which I'm assuming you don't have, or find the stock apk and put it back in the right place as a system app.
If you have Titanium Backup you can use that to do it, provided you can find the stock phone apk.
Well, a problem is, I doubt that I will be able to find any ROMs or Phone.apk's for my device. At least not for a little while. There are some ROMs out there I believe for the original Blu Touch Book - but the original has a diff processor and is running Froyo rather than ICS.
Now, if I somehow can find a workable Phone.apk or a workable ROM, how do I go about flashing/copying? I can hook up to a PC (though I'm not aware of any USB storage mode that I can turn on), but the phone itself is just about unusable unless I can manage to delete the wrong Phone.apk file, as long as the file is simply missing it will boot up without the relevant features. And - let me repeat that I did a factory reset to try and fix this - it didn't fix my problem but it erased my apps and my root access....I can probably restore root but it won't stop the warning notification from popping up non-stop.
I was able to boot into safe mode previously - but it didn't help. If there is an applicable recovery mode, I can't figure that out. To my knowledge, there is no USB Mass Storage option that I can turn on.
I purchased from Amazon, so luckily I can return the item, and worst case they review it's condition and charge a restocking fee. Of course, I was looking forward to receiving this device for more than a week and have been obsessed with it since it's arrived...and I am also temporarily back to using Sprint (in Phoenix) on a 3.5" Windows Phone (I am an ex Windows Mobile fan boy, Windows Phone disappoints) after experiencing 6 MB/s 3G speeds on T-Mobile for a day or so (on a 7 inch screen and on a prepaid plan far cheaper than what I pay Sprint). I was about to port my number. Basically I am depressed. An irony here - I'm pretty sure Amazon sold me a used device that was advertised as new. On initial boot, the Android set up program did not launch. Upon my first factory reset, the set up program launched, and the dialer skin was different than what it was out of the box. The 'refuse product if this seal is broken' sticker on the packaging was partially broken, too, although it appeared to be partially in tact. But now if I try to play that angle, I come off like a scam artist...
Anyways thank you very much for your reply...all attempts to help are appreciated quite a bit...
Taking things one step at a time, let me simplify my request:
How can I delete (or replace) a system file from my device (in this case, the incorrect Phone.apk) remotely via a USB connection? I have the sdk installed on my computer, I can connect the device to my computer, but I can't really use the device until the file is deleted. Is it possible to push via ADB? Something to that effect? Will the 'push <local> <remote>' command work even if I do not have root access? What syntax is used to specify the path? Is it possible to simply delete a file without replacing it?
Does the Phone.apk file have to be specific to my device or could it be specific simply to my mobile carrier/frequency bands and/or ICS? I realized the Phone.apk file I copied to the device earlier was for the Huawei m835, a CDMA phone running Froyo...
Or, am I simply SOL?
Thanks....
One of the things about Android devices, as a former Windows Mobile user also, is that factory resets work differently as you've found out the hard way. In WM you could delete any system file you wanted and a hard reset would restore it. On Android if a required /system file is deleted you are SOL unless you have a way of restoring a backed up version. Its highly recommended IMO to have a working recovery like CWM, TWRP and a backup before you go messing around with /system files. But with a generic android device its probably not possible to find a recovery to install. You cannot write to the /system directory without root access, adb will give you an error. You may be able to use a phone.apk from another device with the same version of android.
I did find a Phone.apk from a device with the same manufacturer, on the same frequencies, with the same screen res, running the same version of Android. I have the full System/App folder if needed.
And I may have restored root access using UnlockRoot (I have read iffy things about the program but again it's all that worked for me initially). (EDIT - I do now have root access, I was able to verify the Superuser app on the device)
However when I load the SDK and type in 'adb root,' after the 'daemon started successfully,' I quickly get an 'error: closed.' And then when I try to push the Phone.apk file to the relevant folder, I get 'failed to copy / permission denied' (EDIT as I was warned of)
Is there anything I can load onto my SD card to help? I can run probably install an APK off of my storage card. Although I am very limited in what I can do - between error messages I can only get in one quick touch of the screen (and it usually takes a few tries per touch)...I can't do anything that requires a long-click...and I had also deleted the stock keyboard and the stock browser...limits me further...
Now, if I can delete my current Phone.apk and upload the stock keyboard, I am certain I can figure this out. There has to be some way to do this....
EDIT// I packed it up to return to Amazon. If there was a solution out there, oh well...
Like I said you may have been able to use Titanium to install it as a system app and that may have taken care of things once you set it as the default app and/or removed the faulty one.
^^ Right, but the challenge was installing Titanium Backup, and then using it while the error notification popped up on the screen every split second. Unless I am missing something, only way to download it would have required me to buy a Bluetooth keyboard and struggle to pair it so I could type (I had a USB keyboard that didn't work), maybe reassociate my device with my Google account (struggling to type letter by letter between each 'OK' click), have the apk sent to my device over unsecured wifi, put the .apk on SD (or just delete the wrong apk and reboot), and then hope that I could use Titanium backup to do the trick without the ability to press anything on the screen for longer than a half second or so...
Actually, I guess that could have worked, provided the Bluetooth keyboard worked. Of course, there's the chance that the Phone.apk I found for the similar device, might not have worked. Anyways, late now. I have a new one on the way, and I was shipped a slightly used one to begin with anyways, might be for the better. I kinda feel bad that the phone is now 'defective' as a result of my impatience/etc but then again I didn't do anything that the instruction manual warned against, not to mention the instruction manual says a factory reset restores factory data, which I think infers that it restores essential system components. And as much as I was an idiot, I don't do anything which should have caused a nearly non-recoverable error. That's on Google's end. Google doesn't even really discourage rooting and if you allow Android on a device with 512MB rom...
Learning experience. One of the first things I do when I get my new one, I download a backup program and find out if there is a recovery mode. In any event, I won't make the same mistakes twice. Thanks to those who replied or considered replying. Anybody has tips for the future, that aren't obvious or easily found, feel free...
If u r rooted this is very easy.
Open sdk and type su if u get "#" then u r rooted.
If so let us know
---------- Post added at 10:05 AM ---------- Previous post was at 09:34 AM ----------
as a rethought I see u deleted system app so u were rooted
---------- Post added at 10:21 AM ---------- Previous post was at 10:05 AM ----------
Firstly adb pull the file "/proc/mounts" open it using notepad and see how system is mounted.
then remount system as rw using
"mount -o remount,rw -t yaffs2 /
<path to your system> /
system"
Now u can delete stuff or add new stuff without perm error
---------- Post added at 10:24 AM ---------- Previous post was at 10:21 AM ----------
Or just download this . Maybe it'll work http://www.totalcmd.net/plugring/android_adb.html
caponer said:
Or just download this . Maybe it'll work http://www.totalcmd.net/plugring/android_adb.html
Click to expand...
Click to collapse
Eh, I already sent the phone back to Amazon. This, however, looks like a useful something to have access to in the future. Thank you for the link...
No way. Come on,why did u send it to amazon when u had me right here we could have fixed this so easily.
thref23 said:
Hey guys....here's my situation.
I bought a Blu Touch Book 7.0 plus off of Amazon. Got it two nights ago. It's a true phablet. 512 RAM / 512 ROM - I was a little concerned but figured as long as I could root it, I was good to go.
Anyways - no I am not looking for a root. I was able to root it relatively easily after an initial failed attempt which required a factory reset - if anyone is interested, it required PDANET+ & UnlockRoot, SuperOneClick and other methods failed. I threw in a class 10 SD, and modded Android so all apps would be downloaded/installed to my SD card (I did this using the SDK & command prompt in USB debugging mode). I had researched apps previously and began to furiously download and tweak. I threw in a T-Mobile SIM, and everything was going well, I was very happy. It actually seems to be a well made device, though it's a little bulky and the phone function works much better with a bluetooth headset.
Then, I deleted Phone.apk. Despite all apps being downloaded/installed to my SD card, space was still at a premium and I had downloaded a third party dialer. I figured worst case, I could do a factory reset and/or could simply re-download the file (I was actually about to download a good backup program tonight after work, I've been busy the past two days and my anxiety to set up other stuff got the better of me). There was no immediate issue, but shortly later I got the dreaded 'com.android.apk has stopped' (or what not) message popping up constantly. I reset the device, it booted up but it was not reading my sim, and was missing icons. That's when I did something stupid-er. I found a Phone.apk file on the net, downloaded to my device, and copied it to the relevant directory.
Since then, when I boot up, first it shows that Android is upgrading, then it shows the 'unfortunately, the process com.android.apk has stopped.' I click 'Okay,' and it keeps popping up. I wasn't able to delete the wrong Phone.apk as there was not enough time for a longpress between error messages. I was able to initiate a factory reset - I was rather relieved - I had learned a bit the past day or two via trial and error, and I would be able to re-do everything perfectly this time.
But the factory reset did not revert to the right 'Phone.apk' file. So the problem still exists....
If anyone can help me, I would be oh so grateful....thanks...
Click to expand...
Click to collapse
Could you share how you did a factory reset please?
wizardofkoz said:
Could you share how you did a factory reset please?
Click to expand...
Click to collapse
Settings/Backup & reset/Factory data reset
Rooting Help
"I was able to root it relatively easily after an initial failed attempt which required a factory reset - if anyone is interested, it required PDANET+ & UnlockRoot, SuperOneClick and other methods failed."
Can you tell me how did u root it exactly because i am trying all new ways and nothing is working they just cant pick up this phablet.
androidhelp1234 said:
"I was able to root it relatively easily after an initial failed attempt which required a factory reset - if anyone is interested, it required PDANET+ & UnlockRoot, SuperOneClick and other methods failed."
Can you tell me how did u root it exactly because i am trying all new ways and nothing is working they just cant pick up this phablet.
Click to expand...
Click to collapse
I installed PDAnet+ on my phone & PC (as a means of installing a driver for the TB Plus). Then, I ran a program called 'UnlockRoot,' followed instructions, and I had root. UnlockRoot v3.1 is what is installed on my computer.
I moved on awhile ago to the Galaxy Tab 3 7.0 (Galaxy Tab 4 7.0 would be my best recommendation for a budget phablet). The Touch Book plus only held up so well (though I still have it and it still works albeit with no speaker and a screen that needs to be color-filtered due to a mysterious type of screen damage).
DOH!
thref23 said:
I installed PDAnet+ on my phone & PC (as a means of installing a driver for the TB Plus). Then, I ran a program called 'UnlockRoot,' followed instructions, and I had root. UnlockRoot v3.1 is what is installed on my computer.
I moved on awhile ago to the Galaxy Tab 3 7.0 (Galaxy Tab 4 7.0 would be my best recommendation for a budget phablet). The Touch Book plus only held up so well (though I still have it and it still works albeit with no speaker and a screen that needs to be color-filtered due to a mysterious type of screen damage).
Click to expand...
Click to collapse
After so many weeks of hunting around and asking help on forums *which no one was able to help* i stumbled across this which i hope other will find and find useful to them to!
mobiledriverfree.blogspot.com/2015/09/blu-touchbook-g7-pc-suite-and-usb.html
This not only aloud FULL root access within 3 mins, but also gave full super user, was able to retreive lost files, rebuild the software, and reboot the phone. (not to meantion remove ALL the bloatware freeing up half the phones storage)
Enjoy!!!
LeeMarden said:
After so many weeks of hunting around and asking help on forums *which no one was able to help* i stumbled across this which i hope other will find and find useful to them to!
mobiledriverfree.blogspot.com/2015/09/blu-touchbook-g7-pc-suite-and-usb.html
This not only aloud FULL root access within 3 mins, but also gave full super user, was able to retreive lost files, rebuild the software, and reboot the phone. (not to meantion remove ALL the bloatware freeing up half the phones storage)
Enjoy!!!
Click to expand...
Click to collapse
You do realise that this thread is 3+ Years old , right ?
I couldn't leave well enough alone. I am in Europe, using a Verizon Motorola Droid, which was working (although at each boot would say 'unknown SIM - press ok, then it worked). I rooted the phone, installed Titanium, backed everything up and then started playing. I froze a load of bloatware - everything fine. I then downloaded Greenify and hibernated apps I didn't use. It was great. I should have stopped. I didn't. I downloaded Xposed framework, and then the Gravitybox module. Whoops. My phone took on a life of its own. First, my 'phone' (dialler) and 'people' (contacts) icons said 'app isn't installed' when they were clicked. I restored my Titanium backup. No change. I unfroze all the Titantium apps. No changed. I then rebooted, and the phone and contacts icons completely disappeared, as well as my wallpapers and ringtone, to something that my phone couldn't identify. I uninstalled Gravitybox and rebooted. Now the phone no longer connects to the cell phone signal either. I'm sunk, and really need some idea of what to do. Please.......Is there any way of just getting this phone back to some kind of workable order?
Try re-flashing the gapps for your android version. I think Android 4.2.2. And always remember: Make backups. Systembackups with Safestrap for example.
Einheit-101 said:
Try re-flashing the gapps for your android version. I think Android 4.2.2. And always remember: Make backups. Systembackups with Safestrap for example.
Click to expand...
Click to collapse
Thanks. I'm on 4.1.2. I have been trying to find instructions and/or a link regarding just reflashing the whole phone to the stock version, but can't find any. Would you know of one? I am a total noob (as evidenced by my thread) - so I am wondering - if I downloaded one of the other systems, like Liquid Smooth or whatever, does that also flash the phone where all the system files are new, or does it build upon the kernel which I appear to have screwed up??
Google should find a flashable Gapps.zip file. If nothing works, look into the firmwares super thread for stock roms or install cyanogenmod.
My mystery is somewhat solved - the upshot being don't leave a rooted phone around a young fella who is just starting to play with computers, as my son has been 'uninstalling' various files on my phone - the effect of which, of course, didn't come into effect until I rebooted, having downloaded Gravity Box. I have been able to find and restore 'People' and 'Phone' through my Titanium back-up. However, my phone is still not seeing my sim - another file that has been uninstalled, I imagine. I would hope that perhaps someone knows the name of the file that allows the phone to see the sim, rather than me having to uninstall all the files. My son says he only uninstalled about 5 files, but does not remember the names. Not a developer in the making!
I also have the problem with the recovery menu, where I cannot boot into it. Would an uninstalled file cause this? I downloaded Clockworkmod recovery, only to be then told that it does not support the Motorola Razr 'Spyder'. Are there any other options? And is the XT912 considered the 'Razr Spyder or is it one of the Droid options?? Thanks for any help you can give.