Related
So, I think my question is useful to a lot of us, even myself, so I hope someone could help me out. It goes a little something like this:
I have a Nook Tablet, wrapped under my xmas tree. Going straight to the point: what is the best way to get it rooted, under the light of this new software update? On the 25th December, should I turn it on, register it, quickly disable wifi, and start to root it, along with the titanium backup solution? Shoud this work? Or do you have another (and better) solution?
Thanks in advance to all who can help us!
Just got mine today and root couldn't have been easier using this thread -> [Update 12/10/11] Full root for Nook Tablet. [11/20/11] [Permanent root!]
I never saw anything come up on the tablet about an update. Side loaded apps work fine also, just installed all 3 angry birds.
Thanks! A bunch, really! You made my day!
Just got mine today as well. Prepare to root after reading the thread here.
SteelH said:
Just got mine today and root couldn't have been easier using this thread -> [Update 12/10/11] Full root for Nook Tablet. [11/20/11] [Permanent root!]
I never saw anything come up on the tablet about an update. Side loaded apps work fine also, just installed all 3 angry birds.
Click to expand...
Click to collapse
Hi, would like to know if you have the Wi-Fi ON all the way during the process? Thanks!
keidgeibef said:
So, I think my question is useful to a lot of us, even myself, so I hope someone could help me out. It goes a little something like this:
I have a Nook Tablet, wrapped under my xmas tree. Going straight to the point: what is the best way to get it rooted, under the light of this new software update? On the 25th December, should I turn it on, register it, quickly disable wifi, and start to root it, along with the titanium backup solution? Shoud this work? Or do you have another (and better) solution?
Thanks in advance to all who can help us!
Click to expand...
Click to collapse
Just to be safe, first thing I would do after turning on and registering is go straight to root thread and download tgps app. then disable wifi. then after rooted, enable wifi and download titanium backup, then freeze devicemanager.apk. this will block verification of software version.There are other methods of blocking OTA.
Also, there is still a question on if they are even pushing OTA, some of us never got one and have left our devices on for the past couple of days...
albertwertz said:
Just to be safe, first thing I would do after turning on and registering is go straight to root thread and download tgps app. then disable wifi. then after rooted, enable wifi and download titanium backup, then freeze devicemanager.apk. this will block verification of software version.There are other methods of blocking OTA.
Also, there is still a question on if they are even pushing OTA, some of us never got one and have left our devices on for the past couple of days...
Click to expand...
Click to collapse
Do I need to download tgps app directly on the nook, can't I push it through my sd card?
Yes, comptonsoft.com/test and select the top left link.
So it looks like we can still root if ee have one sitting under the tree waiting for us huh? I had been debating between this and the acer a100 and chose this for the battery life and ease of root/use factors. Hmm. Thanks for the info
Sent from my LG-P925 using Tapatalk
you can root anyway, just might have to sideload stock rom of 1.4.0 through sdcard restore
---------- Post added at 10:36 AM ---------- Previous post was at 10:36 AM ----------
keidgeibef said:
Do I need to download tgps app directly on the nook, can't I push it through my sd card?
Click to expand...
Click to collapse
yes, can be done through sdcard as well
Thanks, albertwertz
I just wish someone could post a really simple guide (n00b alert) on how people who don't have their NT yet could root it and bypass this software update as soon as possible...
From what I heard as with any nook device in the past....."a software update shouldn't start to update immeadtely as soon as it's turned on"
So hopefully like mentioned above register turn off wifi, root then TGPS etc. This way you avoid leaving yourself open to get hit with the update.
In theory if this is all true; we should be ok even after the weekend.
I will do mine tonight but I need to do my wife's after she opens it; I'm not letting B&N spoil the surprise
radtechy said:
From what I heard as with any nook device in the past....."a software update shouldn't start to update immeadtely as soon as it's turned on"
So hopefully like mentioned above register turn off wifi, root then TGPS etc. This way you avoid leaving yourself open to get hit with the update.
In theory if this is all true; we should be ok even after the weekend.
I will do mine tonight but I need to do my wife's after she opens it; I'm not letting B&N spoil the surprise
Click to expand...
Click to collapse
Thanks I'm filled with relief... Happy xmas, everyone!!!
Just got confirmation that Indirect's root removes OTA automatically. So once you root with a PC, ***and install GAPPs***, it will forever be rooted unless you force sideload the update.
albertwertz said:
Just got confirmation that Indirect's root removes OTA automatically. So once you root with a PC, ***and install GAPPs***, it will forever be rooted unless you force sideload the update.
Click to expand...
Click to collapse
You just made my day.....
Root and don't worry thanks a bunch albert.
Are you are the guy who made the you tube tutorial?
albertwertz said:
Just got confirmation that Indirect's root removes OTA automatically. So once you root with a PC, ***and install GAPPs***, it will forever be rooted unless you force sideload the update.
Click to expand...
Click to collapse
Looks like I WON'T be sending my Nook back after all! Thanks so much!
radtechy said:
From what I heard as with any nook device in the past....."a software update shouldn't start to update immeadtely as soon as it's turned on"
So hopefully like mentioned above register turn off wifi, root then TGPS etc. This way you avoid leaving yourself open to get hit with the update.
Click to expand...
Click to collapse
Assuming your modem is not also your wifi router, just unplug the modem before you register the device and if you like, you can still use wifi to load files from a local file server. No need to worry about how quickly you disable wifi if there is no line to the outside world.
albertwertz said:
Just got confirmation that Indirect's root removes OTA automatically. So once you root with a PC, ***and install GAPPs***, it will forever be rooted unless you force sideload the update.
Click to expand...
Click to collapse
How did you confirm?
Not saying your lying, but I don't know how you would be able to confirm it blocks OTA updates.
radtechy said:
You just made my day.....
Root and don't worry thanks a bunch albert.
Are you are the guy who made the you tube tutorial?
Click to expand...
Click to collapse
yes, the link in my signature should direct you there. I make a bunch of other stuff too
---------- Post added at 12:12 PM ---------- Previous post was at 12:12 PM ----------
xdahgary said:
How did you confirm?
Not saying your lying, but I don't know how you would be able to confirm it blocks OTA updates.
Click to expand...
Click to collapse
we talk through gtalk and irc. He said that the GAPPS part removes OTA and he just added those comments to his root thread.
albertwertz said:
yes, the link in my signature should direct you there. I make a bunch of other stuff too
---------- Post added at 12:12 PM ---------- Previous post was at 12:12 PM ----------
we talk through gtalk and irc. He said that the GAPPS part removes OTA and he just added those comments to his root thread.
Click to expand...
Click to collapse
Is there a default location to get these GAPPS from beforehand? As well as any other needed software for root/applications etc.
Ok folks,
If you're lucky enough to get a TP that's rootable with RazorClaw, you're gonna wanna keep it. Problem is that Asus keeps trying to ram a firmware update down our throats that kills root. We can't have that.
Problem with the OTA is that it keeps spamming you to update, and also in theory at least, you can only postpone it 3 times before it forces you too. Hitting back works somewhat, but you're still gonna get spammed.
The TP also immediately looks for the update as soon as it attaches to wireless.
SwiftKS provided me with the idea of freezing it with TiBu. While it could work in theory, I couldn't get it work as TiBu will only freeze the app with Pro version. I have the pro version, but it wouldn't recognize my key without connecting to market. Which, as you guessed, also lets the TP go out and grab the OTA.
Thanks to some the folks over in the "For any chance of root on TP..." thread in General, I found something else that works.
As always on here, I'm not responsible for anything going wrong or you bricking your device. You assume all risk. If you have your apps backed up, I suggest moving them to your PC to copy back later.
1. Root with RazorClaw if you haven't already.
2. Download Voodoo OTA Root keeper from Market
3. Run Voodoo OTA Rootkeeper and have it protect root
4. Once it says it's protected, download and install the OTA
5. After the OTA is applied, go back into Voodoo OTA Rootkeeper and have it restore superuser.
6. Enjoy!
Thanks to SwiftKS for planting the idea, and the guys in the mentioned thread above for their idea.
Have a great holiday folks!
Hmm, also, you could probably use File Explorer and go in to system/app and rename Update Launcher.apk
Possibly. Didn't try that as I thought it might still try to do its thing even with a different name.
Hehe, Android isn't THAT smart. But, if they're paranoid they could always remove the file from the system/app folder and drop it onto an SD card for safe keeping.
****.
After a few hours, it pulled it down. Must be another process at work.
Mods, feel free to close/delete the thread. Or if anyone else has any ideas, they're welcome to post.
I tried.
could probably just move the. Apk to somewhere else completely or rename it to ****update.apk.bak (don't have one ATM.) Should have one tomorrow so I'll look more into it.
di11igaf said:
could probably just move the. Apk to somewhere else completely or rename it to ****update.apk.bak (don't have one ATM.) Should have one tomorrow so I'll look more into it.
Click to expand...
Click to collapse
That's what I've been thinking. Seemed to work for everything I didn't want to run in the past. My experience is limited to DInc and GB but there's no reason why it shouldn't work here. Assuming it's the only apk thats responsible for the upgrade process. Alternatively, you could block asus servers from the host file perhaps?
The update makes things so much better though ::-(
Sent from my Transformer Prime TF201 using xda premium
You could always get the update(assuming someone can grab it somehow), see what is does/replaces, then just push the updated system/framework files to the old firmware then have the best of both worlds.
Remember with root you can manually push anything in /system you want just can't flash kernels and the like yet u til we have a recovery working or a way to rite a new kernel.
When I get the tp hopefully it won't be updated. We should be able to grab the update via adb and pre root it (maybe) if that is possible ill post my results
sent from my Atrix via XDA premium
What does it improve?
I can try renaming the apk and awe what happens. I'm not sure what it'll do though as it still says the process isn't running.
I'd prefer to keep root so unless someone has tried rooting then updating, I'm hesitant to try it.
I did find done files that look like they were downloaded last night in the /d directory. Didn't muck with them though without a recovery.
Sent from my Galaxy Nexus using XDA App
when it downloads the update does it reboot into recovery?
if there is a way to get between that with adb we could pull the update and check it out, possibly add root to it and see if the update will continue.
Can you please add in your post what is Prime firmware version!
Thanks
marko! said:
when it downloads the update does it reboot into recovery?
if there is a way to get between that with adb we could pull the update and check it out, possibly add root to it and see if the update will continue.
Click to expand...
Click to collapse
I held off on updating for 3 days but then ******* friend didn't know what to do and hit to update it. I thought about what you said. It does boot into recovery. I was trying to find where the OTA was being stored those 3 days that it was downloaded to my prime, but I couldn't find it. Of course I only checked the system folder and forgot to check the data folder. I'll look to see if it's there now but I have a feeling it's been deleted since the update has been done already.
---------- Post added at 03:10 PM ---------- Previous post was at 03:07 PM ----------
ka911 said:
Can you please add in your post what is Prime firmware version!
Thanks
Click to expand...
Click to collapse
The prime version that is rootable is 8.8.3.23 build
Gamestop retails come out with 8.8.3.27 build (not rootable)
The OTA build makes it 8.8.3.29 (not rootable)
Superguy had a best buy model that had the 8.8.3.23 build.
unknown_owner said:
I held off on updating for 3 days but then ******* friend didn't know what to do and hit to update it. I thought about what you said. It does boot into recovery. I was trying to find where the OTA was being stored those 3 days that it was downloaded to my prime, but I couldn't find it. Of course I only checked the system folder and forgot to check the data folder. I'll look to see if it's there now but I have a feeling it's been deleted since the update has been done already.
---------- Post added at 03:10 PM ---------- Previous post was at 03:07 PM ----------
The prime version that is rootable is 8.8.3.23 build
Gamestop retails come out with 8.8.3.27 build (not rootable)
The OTA build makes it 8.8.3.29 (not rootable)
Superguy had a best buy model that had the 8.8.3.23 build.
Click to expand...
Click to collapse
Most likely it gets downloaded to the cache!
if anyone who is rooted can get into adb after DL the update just try
Code:
adb root
adb pull /cache
has anyone tried any of the other root methods or just the one included with razorclaw?
Find where the download comes from, and block it using the hosts file. Look in the resources/data for the update app for the ip.
marko! said:
has anyone tried any of the other root methods or just the one included with razorclaw?
Click to expand...
Click to collapse
I tried a lot of the methods out there but no luck of course on any of them even the tried the other root method from the original TF.
TONS of people should be getting the TF from Best Buy tomorrow or Wednesday. So hopefully we can get some people to try some things! I'm gonna be searching all over the place for that update!
dsmitty166 said:
TONS of people should be getting the TF from Best Buy tomorrow or Wednesday. So hopefully we can get some people to try some things! I'm gonna be searching all over the place for that update!
Click to expand...
Click to collapse
A zip of the OTA can be found here
unknown_owner said:
A zip of the OTA can be found here
Click to expand...
Click to collapse
Now, to see if we can add root to the update...
I have a rooted Tablet (1.4.0, OTA blocked). I watched Netflix fine last night at the around 10pm.
Today I try opening Netflix and every title I attempt to watch gives me the same error, 1005. It seems to be the error that netflix gives when it's a device that was not previously allowed.
Argh. Should I try installing Netflix from the Amazon App store? Are they the same thing? Would anything like that work?
I've already restarted my Nook and attempted to re-connect to Wifi. My account still works, as I've been able to watch Netflix on my computer.
Anyone else having issues?
Thanks!
Working fine for me and Im on 1.4.0 (ota blocked) also.
I'm pretty sure the netflix app on the amazon store is not the same as the one on the NT.. The NT is netflix certified so it plays at higher resolution than other tablets with the app and the netflix on the NT probably has some changes to support the NT DRM.
Sent from Nook Tablet
So it turns out that apparentally I'm on 1.4.1 now. I tried to go through amazon app store and install their Netflix app... and it said something along the lines of "you don't have permission to install apps." **** you B&N.
I rooted after Indirect released his total root package. I just verified again, since I still have the folder on my desktop, and it contains FOTAKill.apk in the system/app/ directory.
I just followed directions, and I had full root and working Google services after I followed the steps. This is upsetting
I may have messed something up but.. it's hard to mess up double clicking a .bat file haha.
I'll just have to format and revert back to 1.4.0
Wufei74 said:
So it turns out that apparentally I'm on 1.4.1 now. I tried to go through amazon app store and install their Netflix app... and it said something along the lines of "you don't have permission to install apps." **** you B&N.
I rooted after Indirect released his total root package. I just verified again, since I still have the folder on my desktop, and it contains FOTAKill.apk in the system/app/ directory.
I just followed directions, and I had full root and working Google services after I followed the steps. This is upsetting
I may have messed something up but.. it's hard to mess up double clicking a .bat file haha.
I'll just have to format and revert back to 1.4.0
Click to expand...
Click to collapse
Yes people is reporting that some OTA kill methods stopped working, not sure if the replacing device manager method works well but i think B&N will find a way to override it and push the new update again, hopefully someone come up with something definitive. Recommendation always make a backup with titanium backup i've seen many posts that it works good.
Veronica
lavero.burgos said:
Yes people is reporting that some OTA kill methods stopped working
Click to expand...
Click to collapse
Where are people reporting this?
This is the first post I've seen that claims that idirect's method of blocking OTA's doesn't work. If that's really the case, I would expect to see tons of reports coming in that NT's with OTA's blocked via idirect's method are updating.
Is anyone else actually having this issue?
Or is it an isolated incident?
---------- Post added at 05:02 PM ---------- Previous post was at 04:16 PM ----------
Wufei74 said:
I rooted after Indirect released his total root package. I just verified again, since I still have the folder on my desktop, and it contains FOTAKill.apk in the system/app/ directory.
Click to expand...
Click to collapse
Also, Wufei74, did you use indirect's method for modifying data for devicemanager? Because that seems to be only sure way to block OTAs. Having the fotakill.apk in the system directory doesn't do the trick. You need to actually modify the devicemanager, as explained here, by indirect:
http://forum.xda-developers.com/showthread.php?t=1405418
Do us a favor and let us know if you actually did this before your NT updated, yes? Because if you did do it and your NT still updated, then we could all be getting updates soon. On the other hand if you did NOT do it and simply relied on the fotakill.apk, then the reason your NT updated is clear. Either way, the more information you provide, the easier it will be for us to determine what we're dealing with here.
I have checked the other threads where people have posted this same error message, but found only a vauge reference to a "flashtool" and some comments about baseband versions. So, hopefully, if i make a greater description in detail here someone might have a few other tips or ideas.
I love the Motorola Defy. I have owned several and found it to be an excellent device. I have tested the ruggedized feature as thoroughly as one may ever imagine and only successfully killed one device (it fell into a hot tub and sat there kind of boiling for a while, ha!)
I currently have two Defy devices. One primary (we'll call this my A phone) and the secondary that i use for dev, testing new ROMs, tweaking, and as a backup (the backup phone's earpiece speaker died so that's why i still keep it around but only as a backup) which we'll call my B phone. Until recently, i was running CyanogenMod 7.1 on these phones.
A few days ago, my primary phone was having network problems. I was visiting rural Iowa, where a buddy of mine (who also has T-Mobile) used to live and he even prepared me by saying "get ready for some iWireless fun!"... indeed, once on the ground out there i constantly failed to have T-Mobile signal, and their roaming agreements with others seem to be a patchwork mess. I could go into...
System Settings > Wireless & Networks: More... > Mobile Networks > Network Operators
...and the "Available Networks" would occasionally show T-Mobile, it would always show AT&T, and sometimes another minor carrier (like iWireless, etc)
I successfully would "force" the A phone to select T-Mobile and it would be happy for a while, then after lots of rural driving it would seem to get lost again. When i flew home back to a proper city, all was well with the A phone again and it remained happy. Suddenly, however, just the other day it lost GSM signal. When i went back to the "Available Networks" screen i started getting the "Error while searching for networks" message. I've had this happen on other drvices before and it would often right itself after a few reboots and i never knew why.
Since i was planning on upgrading my ROM anyway, i took out my B phone (which i use for testing, etc) and fired it up. It was still running CM 7.1 and when i swapped my SIM card over, everything was fine. Just for fun, i made a nandroid backup from this phone (the working B phone) and pushed it onto the A phone. Still the same problem with the A phone... "Error while searching for networks"
I downloaded the latest nightly of CM10 (and i'm ever so distressed to see that CyanogenMod still does not have permission management replaced. How much money someone at Google paid them to take that out we'll never know) and installed it fresh on the B phone. I did a fresh install of CM10 on the B phone and really liked it. After some tweaking, installing basic apps, etc. i was pretty satisfied. I made a nandroid image of the B phone's new CM10 environment and pushed it to the A phone. Still the same problem... "Error while searching for networks"
Now i'm really stumped. These are both running with identical settings, etc...
Model MB525
Android 4.1.1
Baseband EPU93_U_00.60.03
Kernel 2.6.32.9-ga649a2e
CyanogenMod 10-20120924-NIGHTLY-mb525
... and as of just a day or so ago, the A phone had no problems with its radio. It wasn't dropped or otherwise subjected to anything funny. People have made reference in other threads to tweaking the baseband somehow (although this wouldn't seem to be an issue, since both devices show the same identical details when i check the About Phone status) but just in case, i updated my Baseband Switcher and tried to force the A phone to some other setting, then back to the USA setting. Still no joy.
Here's something weird, though... currently the IMEI shows as all zeros on the A phone (the phone with this problem). Is that normal, when the phone is not on a network? What could cause that? Is this perhaps just a fluke hardware problem that i've identified after trying everything else?
I also seem to see conflicting information (or unclear wording) in other threads about the kernel. Is it or is it not part of what gets backed up with a nandroid backup? I would try updating or fussing with the kernel, but as you can see from my text above... even the kernel version appears to be identical between both phones.
So, there you have it. Now i have two phones...
A phone - used to be my primary, until the radio nuttiness and permanent "Error while searching for networks" condition
B phone - used to be my secondary due to faulty earpiece speaker, now my primary so i just either make speakerphone calls or text for now
... and no matter what O/S i run on them (i've tried switching back with nandroid to CM 7.1, CM9, etc etc) they all manifest these same behaviors. Anything else i can try or do you think my A phone's radio is just shot somehow? (Frustrating because it was litterally fine merely days ago. Ah well, everything works until it doesn't.)
"Error while searching for networks" detailed discussion
If anyone out there has some really deep knowledge about what the Android system does when it interacts with the radio and searches for networks, etc... i'd love to know. It's always so disheartening when a non-specific error message appears and you have limited means of discerning exactly what is happening under the hood to cause it.
picked up another phone... same problem
on a whim i picked up another Motorola Defy because i utterly love these devices and they are starting to go away... the restore with clockworkmod was perfectly simple and straightforward... but the new phone has the same problem: "Error while searching for networks" and there is no way of connecting to any GSM tower.
this is incredibly frustrating, and i cannot for the life of me figure out what the difference between these phones can be. why would one phone be connecting just fine and the others totally and utterly failing to? they are all US T-Mobile Defys.
i'm going to borrow a buddy's SIM card and see if it will register on any network, maybe my SIM is just doing something loopy.
IMEI all zeros
on all of the phones that are experiencing the GSM problem, Android reports the IMEI to be all zeros under "About Phone"
this is also the case with the latest brand new phone that i just purchased. now, i'm fairly certain that this wasn't the case until i put the CyanogenMod 10 ROM on it. how the hell can a ROM foul up a radio so badly? (and how can it happen on just some phones but not others of identical model?)
a-ha, i may have discovered something non-symmetrical between these phones after all...
there are slight differences one phone's kernel version data. they are very slight, only pertaining to details after the version number. (which, for all i know is just a checksum or some other value specific to when the kernel was compiled)
Phone #1 (currently can connect to GSM networks)
Kernel version
2.6.32.9-ga649a2e
[email protected] #1
Thu Jan 20 07:50:55 CST 2011
Phone #2 (used to connect to GSM networks but no longer does)
Kernel version
2.6.32.9-ga649a2e
[email protected] #1
Thu Jan 20 07:50:55 CST 2011
Phone #3 (brand new and has never connected to any network under CM10)
Kernel version
2.6.32.9-ga28fcc4
[email protected] #1
Wed Apr 6 15:55:29 CST 2011
... so, that seems to raise more questions than it answers for me. two of them appear to be completely identical, yet they behave differently with the SIM card (Phone #1 sees networks, Phone #2 does not).
the last one, Phone #3, has slightly differing kernel version data but i don't know why. that phone also cannot see networks.
Deviant Ollam said:
that phone also cannot see networks.
Click to expand...
Click to collapse
read this http://forum.xda-developers.com/showthread.php?t=1857054 , If you have 0000 as your IMEI, you may have to correct it for it to be allowed to connect by some networks
i'm reading other forums and seeing repeated references to the files...
libril.so
librilswitch.so
... which appear to live in /system/lib
one user on a forum asserts that "These types of bugs are due to mismatched RIL and Radio" but does not offer any information on how one might go about checking this or addressing the problem.
i'm going to try copying those two above-mentioned files from the "working" phone and pushing them to one of my non-working phones. let's see how this goes.
(and, of course, anyone with real knowledge in this area is free to jump in at any time... but for now this is a sort of fun intellectual exercise, just seeing my own process play out in this thread that i alone am posting in. ah well, maybe it will help some future person someday.)
xsenman said:
read this http://forum.xda-developers.com/showthread.php?t=1857054 , If you have 0000 as your IMEI, you may have to correct it for it to be allowed to connect by some networks
Click to expand...
Click to collapse
thanks! great irony, to see an expert pop up right as i comment about being monologing to no one in this thread, hah. i'll read that other thread right after i try my file copy experiment.
i've copied over libril.so and librilswitch.so to the non-working phone's /system/lib directory, but i see that the permissions were altered in the process. i've fixed that (set them to RW- R-- R--) but now i wonder if a chown command is in my future, too.
xsenman said:
read this http://forum.xda-developers.com/showthread.php?t=1857054
Click to expand...
Click to collapse
upon reading that, i started to follow instructions for repairing a lost IMEI.
one of your instructions in this post is to "Download EFS Folders for modification and restoration My Android Collection" however when one visits that link there does not appear to be any entry (even when you expand all the sub-sections) called "EFS Folders" or anything that makes mention of "modification" or "restoration"
help?
Deviant Ollam said:
there does not appear to be any entry (even when you expand all the sub-sections) called "EFS Folders" or anything that makes mention of "modification" or "restoration"help?
Click to expand...
Click to collapse
sorry its in My Android Solutions and mostly for Samsung , none for motorola, you may need to search google . But mostly flashing the initial STOCK firmware the unit came with would correct it
maybe i'm misunderstanding what you mean when you say the "efs folder is found in your root of your Internal Phone memory"... because none of these three phones appear to have any folder called "efs" anywhere i can find it, least of all in the root location (at least when viewed with Root Explorer)
in the root path i see folders like...
acct
cache
config
data
dev
etc
mnt
pds
... and so on and so on, but no efs folder in there. is it a hidden folder? is there a way one must manually turn on the viewing of hidden folders in Root Explorer?
xsenman said:
flashing the initial STOCK firmware the unit came with would correct it
Click to expand...
Click to collapse
heh, that sort of reminds me of using a recovery CD that would ship with PCs back in the day... where does one acquire the stock firmware that comes with a device? is there a hidden recovery partition that does not get disturbed somewhere on the phone?
i tried to choose "stock recovery" instead of "custom recovery" in my bootloader, but that just resulted in the boot error image (similar to this but with a little android figure as opposed to a phone)
EDIT: seems like RSDLite with the stock SBF file might do me right. i have both of those (but i recall RSDLite being an absolute bastard when it comes to ever seeing a phone properly) so i'll try that.
Deviant Ollam said:
... and so on and so on, but no efs folder in there. is it a hidden folder? is there a way one must manually turn on the viewing of hidden folders in Root Explorer?
Click to expand...
Click to collapse
yep, it should be hidden and cannot be edited , and all the information, I am able to provide is based on Samsung, so I am afraid it can be different for your units.
---------- Post added at 11:37 AM ---------- Previous post was at 11:35 AM ----------
Deviant Ollam said:
i have the original backups from my very first Motorola Defy, if that will work. or is there a stock Defy image somewhere kicking around online?
Click to expand...
Click to collapse
try your original backup. that should do it
---------- Post added at 11:44 AM ---------- Previous post was at 11:37 AM ----------
use your WIKI http://forum.xda-developers.com/wiki/Motorola_Defy
xsenman said:
yep, it should be hidden and cannot be edited , and all the information, I am able to provide is based on Samsung, so I am afraid it can be different for your units.
Click to expand...
Click to collapse
any suggestions on where i might look, heh?
xsenman said:
try your original backup. that should do it
Click to expand...
Click to collapse
sadly, i misspoke... don't have the original backup for this device. i have only backups after installing CyanogenMod in various stages
trying now to download the stock rom from the wiki. i cannot say how much of a strong and passionate hatred i have for all these goddamn terrible upload sites. is there a reason that the community can't just settle on ONE that is reliable and useful? the stock Froyo rom for my Defy is linked in a thread with a multiupload link and that forwards to a lnx.lu link which is a steaming pile and doesn't even load in Chrome or Firefox. It loads in IExplore but doesn't download.
is there not just one standard site where people would upload??
got RSDLite to recognize phone
so... for those who later find this thread and keep on reading (i'm continuing to post in the spirit of this) i will report that now RSDLite is updating my phone back to the Froyo 2.2 stock image that i have.
getting RSDLite to see the phone involved getting it into the bootloader (not, as i now realize, the "boot menu")
power on Motorola Defy with VolUp pressed... bootloader (some folk even say that hold VolUp while inserting battery)
power on Motorola Defy with VolDown pressed... boot menu (and then recovery)
... so that was the trick on that one, i do recall knowing that in the past. learning is fun. re-learning is less fun.
wonder of wonders... using RSDLite to push the stock 2.2 rom to the phone worked, and upon boot (wherein the whole MotoBlur nonsense started) i was able to see that the phone thinks it has an IMEI number now! so now i'm going to see about doing a step-by-step upgrade to CM10 and i'll see if the IMEI stays put. =)
Deviant Ollam said:
wonder of wonders... using RSDLite to push the stock 2.2 rom to the phone worked, and upon boot (wherein the whole MotoBlur nonsense started) i was able to see that the phone thinks it has an IMEI number now! so now i'm going to see about doing a step-by-step upgrade to CM10 and i'll see if the IMEI stays put. =)
Click to expand...
Click to collapse
make a nandroid backup using CWM first so that you don't need to do it all over again
xsenman said:
make a nandroid backup using CWM first so that you don't need to do it all over again
Click to expand...
Click to collapse
hah, yeah... that's the first thing i'm doing.
Disclaimer: Flash this ROM at your own risk. I am not responsible for what you do on your device. I left this stock to provide a base for anybody that wants to use it. Mod this rom how you want. Just please remember to give credit where credit is due.
This is a pure stock rooted rom. It has items like busybox, init.d support and so forth. No apps were added or removed.
Kernel source is available from htcdev.com Using stock zImage with no changes at all.
Downloads
mine too just in case
Awesome! Thanks jmz!
a
Is that stock with htc sense or just pure android ? And do you know how can i make my device write to external Sd card and not only internal storage ?
pafchu said:
Is that stock with htc sense or just pure android ? And do you know how can i make my device write to external Sd card and not only internal storage ?
Click to expand...
Click to collapse
- unlock bootloader
- flash TWRP
- flash root or rooted rom
- flash new kernel
- instal SD Fix from google play (free)
that`s all... working
It's stock with sense.
ok that worked thanks!!! can i also kindly ask if someone can provide a stock kernel as i want to use ART instead of Dalvik but after flashing the kernel provided here i am unable to make my device switch to ART.. thanks in advance
pafchu said:
ok that worked thanks!!! can i also kindly ask if someone can provide a stock kernel as i want to use ART instead of Dalvik but after flashing the kernel provided here i am unable to make my device switch to ART.. thanks in advance
Click to expand...
Click to collapse
What exactly is the issue?
jmz said:
What exactly is the issue?
Click to expand...
Click to collapse
the issue is that after flashing different kernel i am unable to switch from Dalvik to ART...i need a stock kernel so i can flash it and use ART.
Hope that helps!
I am also having few problems with these stock ROMs.
Icons on the lock screen are misplaced (little to the left).
Can't completely remove notification sounds (make them silent).
The AT&T and HTC images at the bootscreen are smaller (there is a big black frame).
I will post pictures when I get back home from work.
sorry guys if i bothered you with my stupid questions but i found the problem that was preventing me from switching Dalvik to ART. it was xposed framework that caused the issue and after i uninstalled the framework i was able to switch to ART thanks for your help anyway
I will add few pictures of my screen.
http://i59.tinypic.com/n1fnn8.jpg
http://i60.tinypic.com/90c7pl.jpg
http://i62.tinypic.com/v3eyxi.jpg
http://i58.tinypic.com/2jdfl9h.jpg
http://i57.tinypic.com/1zx2kb4.jpg
Can't really figure out how to fix that.
I tried both ROMs and I am currently with jmz's kernel.
keep having random reboot,, need a stock kernal:crying:
Nixing said:
I will add few pictures of my screen.
Can't really figure out how to fix that.
I tried both ROMs and I am currently with jmz's kernel.
Click to expand...
Click to collapse
In case you didn't fix that:
The AT&T Desire 610 has a 480*854 screen. If you are running an AT&T rom on an international Desire 610 you may have this problem.
deconectat said:
In case you didn't fix that:
The AT&T Desire 610 has a 480*854 screen. If you are running an AT&T rom on an international Desire 610 you may have this problem.
Click to expand...
Click to collapse
Thank you very much for your answer.
I didn't knew that.
wheres the rom? On the DL page, there is nothing but a list of devices, none of which seem to be htc, much less 610.
Ok, figured that out... My trouble is, I cant seem to get root working! I installed rooted rom, even the kernal that goes with it, but still can not remove apps from att. Thats kinda my whole goal, but not having much luck getting it going. Any ideas what Im doing wrong??
---------- Post added at 07:10 AM ---------- Previous post was at 06:35 AM ----------
OK, Ive missed something.. I can even remove files from the rom, and they are stll there... I guess I've messed something up, or missed something completely. No matter what I do, I can not remove a system app, even if I remove it from the rom and flash it back to the phone...
klloyd said:
Ok, figured that out... My trouble is, I cant seem to get root working! I installed rooted rom, even the kernal that goes with it, but still can not remove apps from att. Thats kinda my whole goal, but not having much luck getting it going. Any ideas what Im doing wrong??
---------- Post added at 07:10 AM ---------- Previous post was at 06:35 AM ----------
OK, Ive missed something.. I can even remove files from the rom, and they are stll there... I guess I've messed something up, or missed something completely. No matter what I do, I can not remove a system app, even if I remove it from the rom and flash it back to the phone...
Click to expand...
Click to collapse
If you're using the at&t 610, flash the Rom and kernel. Go to the play store after signing into your Google account.
Download the kitkat sd card fix and titanium backup.
Make sure you have the latest busybox and root binaries before hand.
Use the sd card fix app, restart your phone. Once it turns back on, wait a solid minute as it runs the start up. Now go into titanium back up and start deleting apps.
That should do it.
If not, follow up with deleting the app and it's associated .apk in your system/apps folder.
klloyd said:
Ok, figured that out... My trouble is, I cant seem to get root working! I installed rooted rom, even the kernal that goes with it, but still can not remove apps from att. Thats kinda my whole goal, but not having much luck getting it going. Any ideas what Im doing wrong??
---------- Post added at 07:10 AM ---------- Previous post was at 06:35 AM ----------
OK, Ive missed something.. I can even remove files from the rom, and they are stll there... I guess I've messed something up, or missed something completely. No matter what I do, I can not remove a system app, even if I remove it from the rom and flash it back to the phone...
Click to expand...
Click to collapse
My guess is you're S-on, the phone won't allow you to write or modify the system files. Honestly you're not truly rooted unless you're s-off. Where did you find the download? I don't see our phone in the list either
https://www.androidfilehost.com/?w=devices&uid=9390288116658470939
All files are mirrored here now