I am about to buy a bricked Aria, it won't load past the ATT screen, is there any way to root it without going through Windows? Like with my Evo, I was able to root that either through Windows or through the HBOOT screen.
EDIT: Does anyone know if this method would unbrick the phone?
Dacian said:
I am about to buy a bricked Aria, it won't load past the ATT screen, is there any way to root it without going through Windows? Like with my Evo, I was able to root that either through Windows or through the HBOOT screen.
EDIT: Does anyone know if this method would unbrick the phone?
Click to expand...
Click to collapse
Can you access the boot loader?
Ninja edit -- if you can't access the boot loader, than you probably won't be able to unbrick the phone.
Dacian said:
I am about to buy a bricked Aria, it won't load past the ATT screen, is there any way to root it without going through Windows? Like with my Evo, I was able to root that either through Windows or through the HBOOT screen.
EDIT: Does anyone know if this method would unbrick the phone?
Click to expand...
Click to collapse
If you can get to the att screen then you should be able to access recovery by shutting off the phone and using volume down + power buttons to boot up. If you can do that then you SHOULD be able to fix it.
Sent from my cm6.1 Aria using XDA App
Just wondering... How do you brick a phone that's not rooted? It's not like you can brick it by installing a new ROM to a non-rooted phone.
I haven't bought the phone yet, I'm assuming he probably tried rooting and failed, I can't think of any other reason it wouldn't load past the att logo. And as you said, if it can get to the att logo, you should be able to get to the boot loader, right?
If I can get to the boot loader, I could probably load the stock rom to get it to load into the os to root through revoked.
Dacian said:
If I can get to the boot loader, I could probably load the stock rom to get it to load into the os to root through revoked.
Click to expand...
Click to collapse
Correct. As long as you can get to bootloader you can restore the phone.
Sent from my cm7 Aria using XDA App
Awesome, thanks for the help!
You could essentially have him pay you to fix his phone. But that wouldn't be very nice... =P
do you or anyone have direction to rooting the HTC Aria, This is my first android phone.
you can email me at [email protected]
irving2007 said:
do you or anyone have direction to rooting the HTC Aria, This is my first android phone.
you can email me at [email protected]
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=rjgg__m-KHc
or
http://forum.xda-developers.com/showthread.php?t=788737
or
http://forum.xda-developers.com/showthread.php?t=730002
Related
I used the info on this page: *android.modaco.com/content/htc-desire-desire-modaco-com/310873/possible-hboot-downgrade/* it didn't downgrade the hboot, but that might be something to work on.
CHANGE STEP 3.4. "change it to 1.15.405.1" don't do that, change the "2.20.502.1" in the misc.img from your aria to 1.25.502.2
Oh and you'll need either a Temp root, or a Shell root for adb
I have done this and can confirm that this works
Thanks mate!
I just noticed the Aria got 2.2 finally, albiet through this silly sync method.... It's my wifes phone, I'm sure she's not going to be happy to have to hard reset it.. wth.
Anyway, so why are you guys going back to 2.1? I am surprised not to see more discussion on 2.2 in this forum, but I don't frequent it much since I don't own the Aria myself.
khaytsus said:
I just noticed the Aria got 2.2 finally, albiet through this silly sync method.... It's my wifes phone, I'm sure she's not going to be happy to have to hard reset it.. wth.
Anyway, so why are you guys going back to 2.1? I am surprised not to see more discussion on 2.2 in this forum, but I don't frequent it much since I don't own the Aria myself.
Click to expand...
Click to collapse
I went back to 2.1 because the 2.2.2 version that AT&T released was extremely slow, and my touchscreen would become unresponsive.
andrewishcool95 said:
I used the info on this page: *android.modaco.com/content/htc-desire-desire-modaco-com/310873/possible-hboot-downgrade/* it didn't downgrade the hboot, but that might be something to work on.
CHANGE STEP 3.4. "change it to 1.15.405.1" don't do that, change the "2.20.502.1" in the misc.img from your aria to 1.25.502.2
Oh and you'll need either a Temp root, or a Shell root for adb
Click to expand...
Click to collapse
How do you get a temp root or shell root with the new HBoot still in-place? If temp root is possible, then can't you install clockworkmod and get permaroot?
Gene Poole said:
How do you get a temp root or shell root with the new HBoot still in-place? If temp root is possible, then can't you install clockworkmod and get permaroot?
Click to expand...
Click to collapse
I got a shell root from super one click root (forum.xda-developers.com/showthread.php?t=803682)
after I downgraded to 2.1 I got z4root to get a temp root.
andrewishcool95 said:
I got a shell root from super one click root (forum.xda-developers.com/showthread.php?t=803682)
after I downgraded to 2.1 I got z4root to get a temp root.
Click to expand...
Click to collapse
I'm also very curious about this.
Sounds like the first steps to rooting and downgrading. I'm curious to see if any developers catch this
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
I've been reading up on this and the skinny is that the HBOOT image controls the S-ON and S-OFF flags of the NAND RAM in the device. Even with a temp root shell, you can't write to a partition with its S-ON flag set. This normally includes all the partitions on the phone except the data partition, so trying to root the device requires some sort of interaction with the HBOOT image to turn off the S-ON flag for the recovery and system partitions to properly root a phone.
In short, if and until someone hacks hboot_liberty_7227_1.02.0000_101104, your phone is unrootable.
Gene Poole said:
I've been reading up on this and the skinny is that the HBOOT image controls the S-ON and S-OFF flags of the NAND RAM in the device. Even with a temp root shell, you can't write to a partition with its S-ON flag set. This normally includes all the partitions on the phone except the data partition, so trying to root the device requires some sort of interaction with the HBOOT image to turn off the S-ON flag for the recovery and system partitions to properly root a phone.
In short, if and until someone hacks hboot_liberty_7227_1.02.0000_101104, your phone is unrootable.
Click to expand...
Click to collapse
Help me out, I may be thinking in the wrong direction, but I've been dealing with my nook which is why I thought of this.
Is there not a way to write an hboot to an sd-card or connect via usb at start to make the aria think that the sd-card or the usb connection is the corrected hboot, thus being able to modify?
FroztIkon said:
Help me out, I may be thinking in the wrong direction, but I've been dealing with my nook which is why I thought of this.
Is there not a way to write an hboot to an sd-card or connect via usb at start to make the aria think that the sd-card or the usb connection is the corrected hboot, thus being able to modify?
Click to expand...
Click to collapse
There may be. When I first got my Aria, the rooting procedure involved an HTC signed update that you fooled the hboot into partially loading, then swapped the sdcard with the root package. It involved some complex timing issues where you had to run adb in a loop and plug/unplug the usb cable at appropriate times.
I've been searching the net for that procedure and I can't seem to find the right search terms, or I'm just not looking in the right places or something, but I know that's how I did my Aria before there was an unrevoked plug-n-root.
I have the procedure u are looking for i think...let me know if this is what u were after because i have an archive of saved documents I have copied from forums in the past...GOOD LUCK!
well apparently i haven't posted enough to put the links up in the post
PM me if you want the process...
xerotix said:
PM me if you want the process...
Click to expand...
Click to collapse
May I have a copy of said process? Currently the only way is to buy a very expensive hardware called XClip. I have managed to get the updated 2.2.2 Stock ROM rooted but not deodex or EXT3 FOR ap2sd trying to play with some files from another source to get hboot s off.
econcep said:
May I have a copy of said process? Currently the only way is to buy a very expensive hardware called XClip. I have managed to get the updated 2.2.2 Stock ROM rooted but not deodex or EXT3 FOR ap2sd trying to play with some files from another source to get hboot s off.
Click to expand...
Click to collapse
That process does not work with the new HBOOT. That's why unrevoked doesn't work. Having root access does not unlock NAND.
Currently, the only way known is via hardware tools.
It works. I managed a work around for 2.2.2 update
Hey everyone I am in the second phase of testing my work around with the new HTC Aria update from ATT. I managed to load the update and keep my phone rooted. I am now in the setup mode with no bootloop.
Running into a couple of issues with the new radio but I believe I know how to fix that as well. Keep you all posted and once all bugs worked out I will post my findings and HOPEFULLY MY ROOTED ROM.ZIP with instructions.
IF AT FIRST YOU DON'T SUCCEED.....TRY TRY TRY and TRY I did and I am 99% there.
econcep said:
Hey everyone I am in the second phase of testing my work around with the new HTC Aria update from ATT. I managed to load the update and keep my phone rooted. I am now in the setup mode with no bootloop.
Running into a couple of issues with the new radio but I believe I know how to fix that as well. Keep you all posted and once all bugs worked out I will post my findings and HOPEFULLY MY ROOTED ROM.ZIP with instructions.
IF AT FIRST YOU DON'T SUCCEED.....TRY TRY TRY and TRY I did and I am 99% there.
Click to expand...
Click to collapse
This might be the wrong thread. Did you manage to get around the HBOOT issue with the 2.2 update? If not, then you've just done the same thing I did the day after this release was out:
http://forum.xda-developers.com/showthread.php?t=970272
Gene Poole said:
This might be the wrong thread. Did you manage to get around the HBOOT issue with the 2.2 update? If not, then you've just done the same thing I did the day after this release was out:
http://forum.xda-developers.com/showthread.php?t=970272
Click to expand...
Click to collapse
You are right this might be the wrong thread. But I managed a work around with the new update 2.2.2 and the HBOOT 1.0X. As soon as I can confirm without a doubt that it works and will be able to repeat the process successfully with my husband's ARIA (unfortunately we love hacking things and tend to buy multiple devices) I will be more than happy to share the results.
Again, my apologies if it's the wrong thread.
econcep said:
You are right this might be the wrong thread. But I managed a work around with the new update 2.2.2 and the HBOOT 1.0X. As soon as I can confirm without a doubt that it works and will be able to repeat the process successfully with my husband's ARIA (unfortunately we love hacking things and tend to buy multiple devices) I will be more than happy to share the results.
Again, my apologies if it's the wrong thread.
Click to expand...
Click to collapse
Perhaps I misread (or we're talking past each other). You do have, in fact, HBOOT 1.02.0000 on your Aria, and managed to write to the system partition?
Yes & No. I'm stuck on couple of things. First the will temporary give me root access but then it locks up saying I don't have busybox. I'm rooted but no s-off. I also noticed when I reboot into recovery I go into CWM 2.5.0.1 but other times it boots into CWM 2.5.0.7. When that happens I loose my unknown source in settings>application. Again, if this is the wrong thread, I really am sorry.
I googled alpharev and some others who have worked on rooting. Found some cached pages from Jan when they were testing to root/s-off the Aria. Basing my work on that and couple of other devices that are similar to the Aria.
I am getting a ton of hits on my blog for this link! Please if you use the link, say hi to me or click the thanks button or at least leave feed back!
Also, ads help me out and want to do more writing!!!
Thank you everyone!
Click to expand...
Click to collapse
I decided to downgrade everything on my device and take the latest OTA, including the 2.18 hboot. This version is unlockable through the HTCdev website. From there you can simply flash a custom recovery and install the su binaries.
I have guides written up, on both, on my blog, and encourage you to check them out!
To unlock your bootloader, start HERE. Credit to HTCdev obviously for their attempt to give their customers what they want.
Next, to flash recovery and install su binaries check out THIS. Credit to chainsDD for his awesome work and continued devotion to root.
Note: This will not give you S-off, this does come with some limitations but I have not been hindered too much. The one thing I have not been able to do is flash a custom splash screen, because you have to do it through bootloader and it will not get past security. Other wise you can flash anything you would normally do in recovery.
My goal in doing this was to gain the experience, as many of the newer HTC devices only have this option available to them and I want to see the ins and outs as well as the downsides. I know there are methods of reverting back to froyo and using unrEVOked, which is tempting but I like the knowledge.
I already feel much more comfortable with SDK, fastboot and adb commands. This makes me feel more in tune with the Android OS and more comfortable to begin delving into development. I am a curious person and like to know what is going on with my device.
A discussion here would also be welcomed, for anything relating to using the unlocked bootloader. I will be glad to share my findings and try out some of the other things people are doing in order to use the phone in this state.
First off, any ideas on getting the splash screen changed? I was thinking, maybe a flashable zip? Or pushing through fastboot?
You won't be able to change the splash screen without S-OFF. You can only update the partitions that HTC has unlocked, which are boot, system, and recovery. The others still require signature verification, which means an unsigned zip won't write successfully. I don't know of any way around that, besides the obvious method of downgrading the HBOOT/Baseband and using a full NAND unlock method.
Captain_Throwback said:
You won't be able to change the splash screen without S-OFF. You can only update the partitions that HTC has unlocked, which are boot, system, and recovery. The others still require signature verification, which means an unsigned zip won't write successfully. I don't know of any way around that, besides the obvious method of downgrading the HBOOT/Baseband and using a full NAND unlock method.
Click to expand...
Click to collapse
So where is the splash screen located? I am fairly new to the insides of this stuff, really just dl and flash what sounds good.
Could you make a signed zip that would push the image?
imheroldman said:
So where is the splash screen located? I am fairly new to the insides of this stuff, really just dl and flash what sounds good.
Could you make a signed zip that would push the image?
Click to expand...
Click to collapse
Not exactly sure, but I think it has it's own home (separate from the unlocked partitions, that is). And we cannot make a signed zip that will update a locked partition because we don't have HTC's signature.
Wouldn't you be able to change the splash image 1 from a ruu with the splash screen and then run the ruu to get the splash screen
Sent from my swiper using XDA App
evo4gnoob said:
Wouldn't you be able to change the splash image 1 from a ruu with the splash screen and then run the ruu to get the splash screen
Sent from my swiper using XDA App
Click to expand...
Click to collapse
An RUU still authenticates through the bootloader and needs to have HTC's signature. There aren't any EVO HTC-signed RUUs with a splash screen different than the one we have.
Captain_Throwback said:
An RUU still authenticates through the bootloader and needs to have HTC's signature. There aren't any EVO HTC-signed RUUs with a splash screen different than the one we have.
Click to expand...
Click to collapse
If you go to the 3vo forums I believe there is a workaround for hboot 1.5 so I think it can be applied to us also
Sent from my swiper using XDA App
evo4gnoob said:
If you go to the 3vo forums I believe there is a workaround for hboot 1.5 so I think it can be applied to us also
Sent from my swiper using XDA App
Click to expand...
Click to collapse
Can you find it?
I am getting a ton of hits on my blog for this link! Please if you use the link, say hi to me or click the thanks button or at least leave feed back!
Also, ads help me out and want to do more writing!!!
Thank you everyone!
As the title says, I was wondering because I have some game saves that I don't want to lose. And I was wondered if i could copy them over to a pc.Right now, my tablet is locked :crying: ,No its not rooted. Thanks for any help that you guys may have.
Also, is it possible to root it even thought its locked?
What do you mean by locked?
Sent from my HTC Sensation 4G
Kazireh said:
What do you mean by locked?
Sent from my HTC Sensation 4G
Click to expand...
Click to collapse
When I turn it on, im stuck on the enter your username and pass word screen. and when I try to boot it into recovery mood, I get stuck on the Google logo.
So I was wondering, if i could move some of the save files such as games on to a pc and move them over to the new one that Google was shipped
Bump
Hi,
I'm expecting my Nexus 4 some time this week and I'd like a little help.
I have a htc one x at the moment. A while after I got it, I decided to unlock it and use custom rom etc.
With the nexus 4, I just want to root it without disrupting anything if possible. The one thing I don't want to mess up is getting the Ota updates as I couldn't get that to work again on my one x.
So to summarise, I want to root my Nexus 4 whilst retaining the ability to get Ota updates and full functionality as normal. Can anyone help?
You'll need adb/fastboot + the appropriate drivers.
-unlock BL via fastboot,
-flash recovery via fastboot,
-flash SU zip via recovery,
-leave BL unlocked, no reason to relock it.
That's it. Don't remove, or rename any system apps if you want the OTA to apply. You can even flash OTA's via a custom recovery, this will likely be available here prior to you getting a notification.
Good info here: http://forum.xda-developers.com/showthread.php?t=2010312
So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.
mseebass said:
So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.
Click to expand...
Click to collapse
You know when you are on other phones, you are actually unlocking the bootloader via a exploit or through the manufacturers developer center.
You need a custom recovery in order to obtain root. It is a must need, without it you cannot be rooted.
Only way to change your recovery is to unlock the bootloader. Having a locked bootloader locks it so your recovery can't be changed. So.... You get the idea
Sent from my Nexus 4 using xda premium
mseebass said:
So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.
Click to expand...
Click to collapse
You can do it via adb with an insecure boot image, outlined here below the CWM method: http://forum.xda-developers.com/showthread.php?t=1993331&highlight=insecure
If you do it the CWM, or TWRP way you can flash the stock recovery again. You absolutely have to unlock the bootloader however, no way around that.
CF Root is another option: http://forum.xda-developers.com/showthread.php?t=2025274
i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.
phermey said:
i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.
Click to expand...
Click to collapse
Convenience? With CWM it even patches on first boot so you don't lose root or anything so I like being able to do OTA (well the one update so far) vs. having to connect to my desktop.
threeclaws said:
Convenience? With CWM it even patches on first boot so you don't lose root or anything so I like being able to do OTA (well the one update so far) vs. having to connect to my desktop.
Click to expand...
Click to collapse
no reason to connect to desktop if you have recovery. you can come here on your phone or 'chrome to phone' it over. find the thread. click the download link. then reboot in recovery and flash.
phermey said:
no reason to connect to desktop if you have recovery. you can come here on your phone or 'chrome to phone' it over. find the thread. click the download link. then reboot in recovery and flash.
Click to expand...
Click to collapse
I also could drop it into dropbox but that is all more work than just hitting "install" on my phone, it isn't like updates are released with enough frequency that the amount of work matters but like I said OTA is more convenient for me and CWM made it even more convenient. The OP may have completely different reasons for wanting OTA.
phermey said:
i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.
Click to expand...
Click to collapse
i think you must have missed that part in bold. no reason to be a smart a$$ either when you are the one who didnt know there is no reason to connect to desktop.
remember... the whole reason for this thread in the first place is because the op lost ota on his last phone by rooting it. all i did was try to let him feel at ease.
ORStoner said:
Hi,
I'm expecting my Nexus 4 some time this week and I'd like a little help.
I have a htc one x at the moment. A while after I got it, I decided to unlock it and use custom rom etc.
With the nexus 4, I just want to root it without disrupting anything if possible. The one thing I don't want to mess up is getting the Ota updates as I couldn't get that to work again on my one x.
So to summarise, I want to root my Nexus 4 whilst retaining the ability to get Ota updates and full functionality as normal. Can anyone help?
Click to expand...
Click to collapse
Just use the nexus 4 toolkit, follow it's directions/steps - Can't get any easier or less impact than that. Install Drivers, unlock bootloader and root. Done. OTA still work, install busybox from the play store if needed.
http://forum.xda-developers.com/showthread.php?t=1995688
phermey said:
i think you must have missed that part in bold. no reason to be a smart a$$ either when you are the one who didnt know there is no reason to connect to desktop.
remember... the whole reason for this thread in the first place is because the op lost ota on his last phone by rooting it. all i did was try to let him feel at ease.
Click to expand...
Click to collapse
I wasn't being a smart ass nor was I unaware of other ways to get an OTA update, you said there was no reason for OTA on a nexus device and I responded why someone would want it.
clockcycle said:
Just use the nexus 4 toolkit, follow it's directions/steps - Can't get any easier or less impact than that. Install Drivers, unlock bootloader and root. Done. OTA still work, install busybox from the play store if needed.
http://forum.xda-developers.com/showthread.php?t=1995688
Click to expand...
Click to collapse
Don't use toolkits take the time and learn how to do it yourself so if you get into situations where you messed something up you know how to fix it as you know how adb and fast boot will work.
Toolkits are not worth the short cut
Sent from my Nexus 4 using xda premium
Can I just unlock the bootloader, fastboot boot not flash cwn and install root from there.
Also, how does unlocking bootloader affect warranty?
Sent from my HTC One X using xda premium
ORStoner said:
Can I just unlock the bootloader, fastboot boot not flash cwn and install root from there.
Also, how does unlocking bootloader affect warranty?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This is the best way to do it. Yes you can fastboot boot cwm so it'll be temp and just install supersu zip. Regarding warranty for bootloader, it originally came locked so should you need to return it, warranty will be voided if you unlock it. However, it would really be just fastboot oem lock if you need to relock it. The state won't show relocked if you do it. It'll be plain locked
Sent from my Nexus 7 using Tapatalk 2
Hi my computer has died. MY boot is unlocked. In the past I've rooted galaxy phones without a computer, using a file app. Is it possible to finish my N4 this way? I'd hate to buy a new laptop just to root one phone
Sent by mobile telephone.
U dont need to buy a new one, just use one of ur friends, thats the easiest way.
A lot of the older phones needed to be rooted using an exploit, and thus people made applications that could root it from within the system. Since the Nexus phones are so easy to root without any exploits, all of the toolkits that are created are just using the ADB and Fastboot commands to flash a custom recovery and root the phone.
If you were rooted but didn't have a custom recovery, that would be simple to fix. If you had a custom recovery and needed root, that would be simple to fix. But with neither, I think you're going to need a computer.
You need a computer, OR another device that supports OTG and has a fastboot binary installed.
howard bamber said:
Hi my computer has died. MY boot is unlocked. In the past I've rooted galaxy phones without a computer, using a file app. Is it possible to finish my N4 this way? I'd hate to buy a new laptop just to root one phone
Click to expand...
Click to collapse
Actually, I think there's a kernel somewhere here that you can flash and it will root the device simultaneously. I'll try to look for it and see if it's something you can use. Cheers.
apatal said:
Actually, I think there's a kernel somewhere here that you can flash and it will root the device simultaneously. I'll try to look for it and see if it's something you can use. Cheers.
Click to expand...
Click to collapse
That's not the problem... the problem here would be flashing the kernel.
howard bamber said:
Hi my computer has died. MY boot is unlocked. In the past I've rooted galaxy phones without a computer, using a file app. Is it possible to finish my N4 this way? I'd hate to buy a new laptop just to root one phone
Sent by mobile telephone.
Click to expand...
Click to collapse
I had rooted my N4 without a PC.
I had rooted it with FRAMAROOT app, just 2 click and reboot and N4 was rooted. :good: