Related
I'm not too ready to go nuke all of my apps and data without being able to back them up properly. Hopefully the other group will have a method that doesn't involve completely flashing a new image so I can use Titanium Backup before flashing any custom ROMs.
TheBiles said:
I'm not too ready to go nuke all of my apps and data without being able to back them up properly. Hopefully the other group will have a method that doesn't involve completely flashing a new image so I can use Titanium Backup before flashing any custom ROMs.
Click to expand...
Click to collapse
on every other phone, when gaining root access it requires a hard reset. better to root in the beginning.
p-slim said:
on every other phone, when gaining root access it requires a hard reset. better to root in the beginning.
Click to expand...
Click to collapse
Really? I'm pretty sure I didn't have to factory-reset to root my Hero. I've also had my EVO for over a week, so everything is already installed and organized.
TheBiles said:
I'm not too ready to go nuke all of my apps and data without being able to back them up properly. Hopefully the other group will have a method that doesn't involve completely flashing a new image so I can use Titanium Backup before flashing any custom ROMs.
Click to expand...
Click to collapse
If i understand this, rooting does not require any flashing, so you can root , install titanium back up, and then when a custom rom is ready you can flash it.
I will check the grack one out, but I am 80% sure I am going with the one from awesome guys here.
The other group of devs are using a exploit in sprint\htc software. They are going to release the info on the exploit to sprint\htc in 1 week after release. So say goodbye to your other root. I am pretty sure toast root is from a rom thats for engineering purposes. So the root should stay working. Don't quote me on this but I am pretty sure this is correct info.
shep211 said:
The other group of devs are using a exploit in sprint\htc software. They are going to release the info on the exploit to sprint\htc in 1 week after release. So say goodbye to your other root. I am pretty sure toast root is from a rom thats for engineering purposes. So the root should stay working. Don't quote me on this but I am pretty sure this is correct info.
Click to expand...
Click to collapse
I'm lost here, who are "The other group", the guys from grack.com??
mikevillarroel said:
I'm lost here, who are "The other group", the guys from grack.com??
Click to expand...
Click to collapse
yes the other group of devs is grack.com
shep211 said:
yes the other group of devs is grack.com
Click to expand...
Click to collapse
They have made this web http://unrevoked.com/ and it's suppose to go live tomorrow, if so......what do we do, root as toast did or root as they will?
mikevillarroel said:
They have made this web http://unrevoked.com/ and it's suppose to go live tomorrow, if so......what do we do, root as toast did or root as they will?
Click to expand...
Click to collapse
they still dont have "sticky root" or the ability to flash custom roms and such. ur gonna need to use my method for that until we figure out nand protection and how to exploit it. i think they are only releasing their root method as a "proof of concept" or t show how easy it was to gain root perms on the stock build. it will most likely not be the replacement for my method. i talk with them a bit and its just in hopes that both methods together could possible bring a nand exploit to life.
At this point I am waiting as I don't see any reason to root. I can't use titanium backup and frankly don't care about themes or additional roms. OOTB is fast as hell.
Once full system access is achieved, or a fully functional Froyo ROM is available, then I will root.
Just my observation, but I alway ERR on the side of caution.
mikevillarroel said:
If i understand this, rooting does not require any flashing, so you can root , install titanium back up, and then when a custom rom is ready you can flash it.
Click to expand...
Click to collapse
The first thing you do is flash an image to your phone that overwrites your current ROM.
shep211 said:
The other group of devs are using a exploit in sprint\htc software. They are going to release the info on the exploit to sprint\htc in 1 week after release. So say goodbye to your other root. I am pretty sure toast root is from a rom thats for engineering purposes. So the root should stay working. Don't quote me on this but I am pretty sure this is correct info.
Click to expand...
Click to collapse
I was hoping that I'd get the ability to access recovery and flash new ROMs with theirs, so then I could just flash a custom ROM with normal root anyways. According to toast, this doesn't seem to be the case...
toastcfh said:
they still dont have "sticky root" or the ability to flash custom roms and such. ur gonna need to use my method for that until we figure out nand protection and how to exploit it. i think they are only releasing their root method as a "proof of concept" or t show how easy it was to gain root perms on the stock build. it will most likely not be the replacement for my method. i talk with them a bit and its just in hopes that both methods together could possible bring a nand exploit to life.
Click to expand...
Click to collapse
Really? I thought sticky-root was one of the items on their checklist to accomplish before release.
Does anyone happen to know if I can backup apps with a non-root required app then restore them and use Titanium Backup's Market Doctor to fix their Market entries? The lack of backing up Market links is the only reason I don't use other backup apps.
Bielinsk said:
At this point I am waiting as I don't see any reason to root. I can't use titanium backup and frankly don't care about themes or additional roms. OOTB is fast as hell.
Once full system access is achieved, or a fully functional Froyo ROM is available, then I will root.
Just my observation, but I alway ERR on the side of caution.
Click to expand...
Click to collapse
just dont flash or except any updates from sprint. those could possibly ruin ur chances of root ever.
toastcfh said:
they still dont have "sticky root" or the ability to flash custom roms and such. ur gonna need to use my method for that until we figure out nand protection and how to exploit it. i think they are only releasing their root method as a "proof of concept" or t show how easy it was to gain root perms on the stock build. it will most likely not be the replacement for my method. i talk with them a bit and its just in hopes that both methods together could possible bring a nand exploit to life.
Click to expand...
Click to collapse
toastcfh said:
just dont flash or except any updates from sprint. those could possibly ruin ur chances of root ever.
Click to expand...
Click to collapse
how can we avoid this updates from sprint?
Sorry if my questions sound stupid but i'm just learning here man! .
mikevillarroel said:
how can we avoid this updates from sprint?
Sorry if my questions sound stupid but i'm just learning here man! .
Click to expand...
Click to collapse
Most custom roms will remove the OTA update feature. Only stock roms will have this feature. If you are on a stock rom and update is available you can decline it also.
toastcfh said:
just dont flash or except any updates from sprint. those could possibly ruin ur chances of root ever.
Click to expand...
Click to collapse
Very wise advice. I have HTC updates turned off. Not sure if there is any place to disable Sprint updates.
Also on ANY piece of electronics you have to give your consent for any update to be applied, so even with the stock ROM you can decline updates.
-------------------------------------
Sent via the XDA Tapatalk App
TheBiles said:
... even with the stock ROM you can decline updates.
Click to expand...
Click to collapse
Where would one go to decline this? Is there a setting I can just set now, and forget, (how?) or will I need to decline every time?
JustinChase said:
Where would one go to decline this? Is there a setting I can just set now, and forget, (how?) or will I need to decline every time?
Click to expand...
Click to collapse
Unless you are rooted you will continue to get that notification, its quite annoying.
I don't really know too much about root, but I'm wondering how things will work when root is widespread. Will we always have to rely on devs for every future android upgrade or something?
do some research!
rocketpaul said:
do some research!
Click to expand...
Click to collapse
I'd assume no, except for perhaps the first one, but I haven't seen it explicitly stated anywhere.
The short version is that there's userland root access. That pretty much means that the what's on the device can be modified, like apps removed etc but afaik there's no bootloader access yet which would be necessary for flashing custom images.
Root will make cracking the bootloader easier though so it's a major step on the way.
Octanum said:
I don't really know too much about root, but I'm wondering how things will work when root is widespread. Will we always have to rely on devs for every future android upgrade or something?
Click to expand...
Click to collapse
If its anything like the HTC Dream I had before my Sony X10, the root is a process that keeps your phone rooted. Unless you revert back to the original software, you should never lose it. As for the OS, there usually will be people developing custom ROM's for quite a while on this phone but essentially on that part, yes it does depend on the devs.
For those who do NOT like to delve into the Dev area often and may have not seen this
http://forum.xda-developers.com/showthread.php?t=886903
go ahead and be daring...I myself like to wait until atleast a Beta.
Good stuff, thanks. I've been longing to root this phone, but I refuse to do it without a factory .zip which I can flash to restore defaults. Too many people have various issues after rooting, just don't want to take that chance. Can't wait to see what CM puts out though.
what issues? You make a nandroid to go back to
Sent from my Nexus S using Tapatalk
allen099 said:
Good stuff, thanks. I've been longing to root this phone, but I refuse to do it without a factory .zip which I can flash to restore defaults. Too many people have various issues after rooting, just don't want to take that chance. Can't wait to see what CM puts out though.
Click to expand...
Click to collapse
I'm completely with you on this,need that safety net before any modding of any kind.
xspyda said:
I'm completely with you on this,need that safety net before any modding of any kind.
Click to expand...
Click to collapse
Make a nandroid backup.
So to clarify, if I do the following ...
1) factory reset
2) unlock bootloader
3) root phone
4) make nandroid backup
I can then restore the nandroid backup at any time and phone will be completely stock, recovery, bootloader and all exactly as it is now with no sign of modding whatsoever?
I haven't had a lot of time to read into this so not sure as yet what's involved in the above steps but in a nutshell am I on the right lines? Theres a lot of confusing (and conflicting) info out there!
Thanks.
mprziv said:
Make a nandroid backup.
Click to expand...
Click to collapse
While I understand what you're saying, it seems like some people are having issues even after injecting root. I can live without Titanium or drocap2 for a few days longer while Google drops the official restore...although I do want tethering asap.
allen099 said:
While I understand what you're saying, it seems like some people are having issues even after injecting root. I can live without Titanium or drocap2 for a few days longer while Google drops the official restore...although I do want tethering asap.
Click to expand...
Click to collapse
?? You can already tether on stock. Also, I haven't heard of anyone having problems just from rooting the phone, in fact, all you're really doing is unlocking the bootloader and installing an apps to give you su permissions. Like the others said, you can always nandroid back to stock and relock the bootloader if you want to.
The major things wrong with the CM7 alpha on the NS are the Camera and Wifi and other things you would consider major
Cam and wifi work on alpha2.
irishrally said:
Cam and wifi work on alpha2.
Click to expand...
Click to collapse
Once it hits beta ill grab it up but until then im way happy with what i got now
guys come on. This is a dev phone. This is what Nexus is about. Why not flash? Cyanogen is the most consistant and top quality Roms. I love the stock just as much as the next guy, but I didn't buy this phone to be boring. Just flashed CM7 and all is good. updates should make it even better!! Let the fun begin!!
yungfresh said:
guys come on. This is a dev phone. This is what Nexus is about. Why not flash? Cyanogen is the most consistant and top quality Roms. I love the stock just as much as the next guy, but I didn't buy this phone to be boring. Just flashed CM7 and all is good. updates should make it even better!! Let the fun begin!!
Click to expand...
Click to collapse
I'm all for that sure but not until I have a simple and sure fire way of returning absolutely everything to stock, out of the box condition.
Im personally waiting for Amon_RA to release his NS recovery
and ya, the whole not having a sure fire way to go back to stock is a downer.
Google needs to release the stock ROM in its entirety
I'm sure they'll do that soon... or at least I hope they will. Only then will the fun begin for me!
Just wondering, why do you guys need a surefire way to return to stock? Just reflash stock rom and relock bootloader.
ikon8 said:
just reflash stock rom and relock bootloader.
Click to expand...
Click to collapse
Is it really that simple though? My understanding is that the only available 'stock' rom is not in fact stock, rather its an adapted rom as Google have yet to release the actual one?
I want to be able to return to normal in case I want to return the phone.
ikon8 said:
Just wondering, why do you guys need a surefire way to return to stock? Just reflash stock rom and relock bootloader.
Click to expand...
Click to collapse
you cant reflash the stock recovery over CWM either....so when they release the stock ROM officially all you would have to do is re lock the bootloader and flash the rom and it will overwrite EVERYTHING
i was a hardcore CM user on my N1 , flashed nightlies every day but i just dont see anything in CM for the NS that would make me jump right into an alpha
slowz3r said:
when they release the stock ROM officially all you would have to do is re lock the bootloader and flash the rom and it will overwrite EVERYTHING
Click to expand...
Click to collapse
That sounds like just what I'm waiting for. Wonder when it will come. Until that time I guess we just have to be patient.
xspyda said:
That sounds like just what I'm waiting for. Wonder when it will come. Until that time I guess we just have to be patient.
Click to expand...
Click to collapse
Im sure it is on the servers, just a matter of time before someone manages to find it...they always do
Hey guys, I've been thinking about rooting my MT4G, but I can't risk getting this phone bricked. I was wondering what the risks are using this method http://forum.xda-developers.com/showthread.php?t=858021
I've heard that it can only be truly bricked if you mess with the HBoot or radio stuff. Is this true and what are your thoughts on the matter?
Thanks,
Barrett
The method that's depicted in that link is the "safer" one generally. While there is always a risk involved with this type of thing, you can be safe by following those directions EXACTLY. if you do that, it should be just fine.
There SHOULD be no risks to rooting. But check if you have a good or bad chip first... Because the myTouch 4G is just dumb like that. HTC really messed up with this phone with it's plethora of hardware problems.
I personally think that if you "can't risk" a brick, you probably shouldn't root it. And yes there should be no risks, but with these crazy chips floating around and people not being able to follow directions, there are always risks.
lowandbehold said:
I personally think that if you "can't risk" a brick, you probably shouldn't root it. And yes there should be no risks, but with these crazy chips floating around and people not being able to follow directions, there are always risks.
Click to expand...
Click to collapse
+1
There are always risk when you are tampering with the firmware of anything. Phones, Computers, Routers what ever. If you cannot "RISK" it you might just want to use VISIONary.apk r14 and just leave "temp root on boot" checked.
Read up as much as you can and then read some more, watch some youtube howto videos and if after all that you are still doubtful that you can do it then stick with stock. Its really not as overwhelming as it seems to root a phone though, but it is pretty basic and after youve done it once you will wonder why you didnt do it sooner.
I also agree with these guys. If you cant take the risk, then dont do it. There are people that want to root and those who dont. Then there are people who should root and those who should not. Rooting is only needed if you want to flash custom kernels,roms, radios etc. If your an average user then dont worry about rooting. It will do you no good.
If you do decide to root, then just read and take your time. The instructions are all laid out and have been used many times. When in doubt ask.
Good luck
Thanks guys, I really appreciate all of the responses! I'm fairly certain I'll root, but I am still reading. I'd like to know some worst case scenarios and what I can do to prevent them. What if I mistype something while perm rooting? Also, what are the risks of loading custom roms? Is there always a way to restore it even if your stuck on bootloop? One more thing, how do I know if I have a bad chip and what happens if I do?
Thanks again,
Barrett
Barrett S said:
Thanks guys, I really appreciate all of the responses! I'm fairly certain I'll root, but I am still reading. I'd like to know some worst case scenarios and what I can do to prevent them. What if I mistype something while perm rooting? Also, what are the risks of loading custom roms? Is there always a way to restore it even if your stuck on bootloop? One more thing, how do I know if I have a bad chip and what happens if I do?
Thanks again,
Barrett
Click to expand...
Click to collapse
Best thing i can say to do as kind of a brick prevention tool is to make sure you flash eng bootloader cause it opens up more options that would be unavailable if you have a problem. If you mistype something it may not be as big a problem as WHERE it is mistyped. I dont think you can check for the bad chip until your phone is rooted. but it is something that can be checked through adb. The post with instructions in how to check the chip is the one that says something about post your emmc serial.
There really isnt any risk in loading a custom rom, other than getting a corrupt file download that wont flash. Make sure you make a backup through rom manager as soon as you get rooted. It will save you bigtime from having to reset everything up after a problem (ie bootloop or phone overclocked to the point of freezing.)
I think there's a high risk of becoming a flash-O-holic!
well, i tried that method several times and i keep getting s-on. good luck with you
Ace42 said:
I think there's a high risk of becoming a flash-O-holic!
Click to expand...
Click to collapse
I second that, I flash new roms too frequently.
Sent from my demonSPEED Glacier using XDA Premium App
I was hesitant at first, but a couple months later, I went ahead and jumped in. Not too much to be afraid of if you follow instructions. Wouldn't ever go back to a stock ROM and I wondered what I was so afraid of after it was all over.
I try out new ROMs like I'm trying on shirts, its that simple once you get over the initial hump of being a bit hesitant to root a device. There's a supportive community here that will answer any questions you have and chances are- someone has already gone through whatever it is you have an issue with and has a fix. Search is your friend, that's how I got by. Just jump in. All the resources are here and other places on the web.
If you're still hesitant... just don't do it. It's not worth your time and anxiety if you're going to be continually fearful of doing something wrong. This is the kind of thing for tinkerers.... if you're not a tinkerer, just enjoy your phone as it is.
You can check your eMMC chip before rooting by using terminal app. The command is: cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
eqjunkie829 said:
Best thing i can say to do as kind of a brick prevention tool is to make sure you flash eng bootloader cause it opens up more options that would be unavailable if you have a problem. If you mistype something it may not be as big a problem as WHERE it is mistyped. I dont think you can check for the bad chip until your phone is rooted. but it is something that can be checked through adb. The post with instructions in how to check the chip is the one that says something about post your emmc serial.
There really isnt any risk in loading a custom rom, other than getting a corrupt file download that wont flash. Make sure you make a backup through rom manager as soon as you get rooted. It will save you bigtime from having to reset everything up after a problem (ie bootloop or phone overclocked to the point of freezing.)
Click to expand...
Click to collapse
I have heard of the eng bootloader, but can you explain it to me?
Pravox said:
You can check your eMMC chip before rooting by using terminal app. The command is: cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
Click to expand...
Click to collapse
It says "no t found"
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
That is the correct command. Make sure you include the space after "cat". I just tried on an unrooted phone and received SEM04G in reply.
Pravox said:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
That is the correct command. Make sure you include the space after "cat". I just tried on an unrooted phone and received SEM04G in reply.
Click to expand...
Click to collapse
M4G2DE
From what I've read, this is the bad one. Now what?
Barrett S said:
M4G2DE
From what I've read, this is the bad one. Now what?
Click to expand...
Click to collapse
Yup, thats the one they say is the bad one. I've got it too.
Sent from my demonSPEED Glacier using XDA Premium App
eqjunkie829 said:
Yup, thats the one they say is the bad one. I've got it too.
Sent from my demonSPEED Glacier using XDA Premium App
Click to expand...
Click to collapse
Okay, do I go ahead and root and claim a warranty if the chip gives out?
[deleted]
Don't worry about this. I've sent it in for repairs and I'll probably be purchasing a second development Nook for the future.
I've been trying to find time to give this a try. Maybe tomorrow?
flippinpentagrams said:
I've been trying to find time to give this a try. Maybe tomorrow?
Click to expand...
Click to collapse
Thank you so much! B&N did not make developing on this device easy. The nougat update (which I hope will show up at some point) should give us the full software (hopefully). Lots of hope.
I'd love to do this for you.
I do have a working understanding of rooting various devices, rooting, installing custom ROMs, basic adb/fastboot functions, etc. However, I am far from an expert or developer and the linked forum post is fairly confusing to me. It seems to suggest that the tool won't work at all with 6.0 devices. Google didn't help.
If you could explain exactly what you need done, I'd be more than happy to pull the bin for you.
Yeah, same here. I'd love to help, but I'm not quite sure what to do.
I don't want to brick my device either. You didn't brick it using MTK did you?
dragonmere said:
I'd love to do this for you.
I do have a working understanding of rooting various devices, rooting, installing custom ROMs, basic adb/fastboot functions, etc. However, I am far from an expert or developer and the linked forum post is fairly confusing to me. It seems to suggest that the tool won't work at all with 6.0 devices. Google didn't help.
If you could explain exactly what you need done, I'd be more than happy to pull the bin for you.
Click to expand...
Click to collapse
[deleted]
Are they going to fix it though, after you made a big mess of it (and probably voided the warranty)?
smileygon10 said:
Are they going to fix it though, after you made a big mess of it (and probably voided the warranty)?
Click to expand...
Click to collapse
All it needs is a flash of the stock image. It really depends on what they decide to do. In most cases companies will just flash it and resell or send it back. Fairly minimal. It's a worthless brick to me right now.
It doesn't take a large mess to brick a device. One file mishap and the device can simply decide not to boot.
Regardless, if they won't fix under warranty many will still allow repairs for a service charge.