I rooted my inspire the day I got it, but when my screen cracked a couple weeks ago, I flashed the stock unrooted rom so I could go attempt to get my phone/screen replaced. I ended up not getting it replaced ($130 my ass, and it doesnt bother me that much) and just forgot to flash a rom and stuff. I went to do that today and when I go into recovery it gives me the symbol that has the phone and the red triangle with ! inside of it. I then remembered I wasn't rooted, so I used the ace hack kit, like last time, to re root it. the Reverse CID worked but every time I try to downgrade I hit enter then nothing happens, I noticed really fast in the command prompt it flashes that its not known as an internal/external command. Does anybody know a way to get it fixed?
I do not have HTC Sync installed, but I do have its drivers installed. I am running XP
Any and all help is appreciated.
Stop by ATTN1's IRC chatroom and get some real-time help on this:
http://webchat.freenode.net/?channels=#liberatedAria
mrpurplehawk said:
I rooted my inspire the day I got it, but when my screen cracked a couple weeks ago, I flashed the stock unrooted rom so I could go attempt to get my phone/screen replaced. I ended up not getting it replaced ($130 my ass, and it doesnt bother me that much) and just forgot to flash a rom and stuff. I went to do that today and when I go into recovery it gives me the symbol that has the phone and the red triangle with ! inside of it. I then remembered I wasn't rooted, so I used the ace hack kit, like last time, to re root it. the Reverse CID worked but every time I try to downgrade I hit enter then nothing happens, I noticed really fast in the command prompt it flashes that its not known as an internal/external command. Does anybody know a way to get it fixed?
I do not have HTC Sync installed, but I do have its drivers installed. I am running XP
Any and all help is appreciated.
Click to expand...
Click to collapse
It sounds to me like you forgot to download the updated script and replace the one in the hack kit with it.
Related
hey guys,
bought my samsung captivate two days ago and i love it. from reading all the posts about how rooting is awesome i finally took the plunge and rooted my phone with the one click root program. followed the directions to the teeth, everything went fine. even went as far as downloading clockwork and backing up my rom.
few hours later, im totally blown that i rooted my phone. i realized i threw away my warranty.
is there ANY way to unroot the phone and make it totally stock and make it seem like the phone was never altered? i read some answers of "yeah" and some answers of "once your rooted, you can't get back" (i remember reading about an article about how some android phones like the nexus one, once you root theres no going back period). the program i used had a unroot button but im not sure if that would wipe everything away to factory settings and erase all traces of the root.
i know im effing stupid for not thinking it threw. but hey, its good that i came to my senses before i loaded up an os.
to be clear, my phone is just rooted. nothing else. im not running cognitive rom or anything. its running the stock samsung 2.1.
so can anyone PLEASE PLEASE help me solve this problem?
im a total noob when it comes to android.
it took me 20 minutes doing that one click from reading the directions over and over again lol.
i need some step by step directions for stupid people
okay, so i followed the directions to unroot. the programs that were installed when i rooted seemed to have disappear. to be extra sure, i reformatted my sd card and than factory restored the phone (from settings/privacy). quick question though, after i pressed "factory reset" my phone rebooted and than for a quick second i saw the same screen i saw when i rooted (the black screen with the yellow font? looked like a system command prompt i guess). it came on for a sec and than disappeared and it booted regularly. did that happen because i did a factory reset or did that happen because im still rooted?
wtf is wrong with me. i just want my unrooted captivate back (and my warranty lol)
odin to stock with master clear.
There's a thread under android development something with "stock rom" that should restore your phone back to factory.
If you did all of that then you are definitely back to stock now & theres no way of detecting your phone was rooted. You could of gotten away with just using one click to unroot. Thats all I did when I returned mine after a week because my gps never worked at all. I dont think they even did anything to check if it was rooted or anything. Hows your gps on the new one by the way? Mines still bad but at least it sees some satellites now. My old one had a hardware problem where gps wouldn't do anything at all.
Sent from my SAMSUNG-SGH-I897 using XDA App
When you use odin to flash back to stock does that restore the AT&T bloatware as well? Or should I use TiB when I first get the phone to get the bloatware back on?
Thanks,
JOe K.
After trying to exchange my phone for another phone (thinking the GPS is a hardware issue) I had rooted and flashed a custom rom. I reverted back using ODIN master clear and ODIN 2.1 rom (Which puts bloatware and everything on it) and there's no way to detect it. The only time it will truly void your warranty (I believe) if you go into the store with a custom rom or if you go into the store with a bricked phone and they figure out you were modifying your phone.
thanks for the answers guys! why is it that you cant "unroot" a nexus one? i heard they'll always be able to tell if your rooted once you do it.
Hello list,
I have been trying to root my Nexus S with the 2.3.3 update but I've been unsuccessful. I have tried "Allgamer's" GRH78 and a couple of others on youtube but I think the problem is my laptop (windows 7 32-bit) wont recognize the phone. Is there something I'm missing? Has anyone rooted their 2.3.3 phone, and if so can you send a link or PM me so I can figure this out? I eventually want to flash the Cyanogenmod 7 so any help at all would be greatly appreciated.
When I had my HD2 I installed HSPL and flashed all types of ROM's without issue. My Nexus S is acting like my ex......
Thanks,
Rich
Madmax0609 said:
Hello list,
I have been trying to root my Nexus S with the 2.3.3 update but I've been unsuccessful. I have tried "Allgamer's" GRH78 and a couple of others on youtube but I think the problem is my laptop (windows 7 32-bit) wont recognize the phone. Is there something I'm missing? Has anyone rooted their 2.3.3 phone, and if so can you send a link or PM me so I can figure this out? I eventually want to flash the Cyanogenmod 7 so any help at all would be greatly appreciated.
When I had my HD2 I installed HSPL and flashed all types of ROM's without issue. My Nexus S is acting like my ex......
Thanks,
Rich
Click to expand...
Click to collapse
try this http://forum.xda-developers.com/showthread.php?t=875875
Will that work with 2.3.3? And what the hell am I doing wrong that I cant get my laptop to recognize my phone???
Madmax0609 said:
Will that work with 2.3.3? And what the hell am I doing wrong that I cant get my laptop to recognize my phone???
Click to expand...
Click to collapse
Well, you can try to install this driver: http://mazodude.comze.com/files/drivers.rar
That link takes me to a blank page....??? Have you rooted your Nexus and was it at 2.3.3 when you started?
Thanks, and sorry for all the questions.....I'm just trying to get this resolved.
Madmax0609 said:
That link takes me to a blank page....??? Have you rooted your Nexus and was it at 2.3.3 when you started?
Thanks, and sorry for all the questions.....I'm just trying to get this resolved.
Click to expand...
Click to collapse
Did you install the Android SDK? If so, I apologize as I'm not familiar with the shortcut commands for windows but you should try this:
Code:
*File path to your android sdk/tools folder*\fastboot devices
If you get a result like
Code:
################# fastboot
then your phone is being recognized, if not other troubleshooting stepsmight have to be taken.
Havent tried that yet. I will give it a shot.
Thanks!
was having the same issue with fastboot, use these drivers from pda.net
http://www.junefabrics.com/android/download.php
Having the same problem. I've tried PDAnet and am currently updating (again) SDK, but I can't get the fastboot or adb to recognize the device, no matter how hard I try. For what it's worth, my bootloader was unlocked when I upgraded to 2.3.3 (via Clockword Mod), and the unlock status seems to have been preserved. It still says "unlocked," and boots with the open padlock.
Sorry for the double post, but I posted as I was working on it. What worked for me: I had a 2.3.3 stock image booted from Clockwork. I didn't have root permissions with the stock.
The new stock (is it technically a ROM, or is a ROM just Cyanogen, Bionix, etc., like awesome developers create?) preserved the unlocked bootloader (which I've not re-locked, because I never cared about the padlock boot), but not the root. So I was left with a stock 2.3.3 with an unlocked bootloader.
I tried everything to get my phone recognized via USB under the SDK/adb, but couldn't. I adbed and fastbooted devices, uninstalled and reinstalled PDAnet, even deleted and then redownloaded and reinstalled java, SDK, *and* drivers. To no avail.
The first time I rooted, though, I used the one-click method in the MoDaCo forums, by . . . Paul(?). I think that's his name. It's a simple zip file. So I unzipped to my desktop. Which gave me a folder with the GRI40 Nexus S superboot. I disconnected my phone, shut it off, then held the volume up and power keys until it booted into the fastboot bit. Once it was in fastboot (with the green Android and the orange text up top and the blue text options along the side), I reconnected the USB, then just double-clicked the .bat file in the superboot folder.
That gave me root. I verified via rootchecker, and the moment I confirmed root, I went to Clockwork, reflashed Clockwork Mod Recovery, and did a complete back-up. That's where I am now. Not sure where I'm going from here, but I have 2.3.3 GRI40 root with baseband i9020xxb1, and that's how I did it.
willentrekin said:
Sorry for the double post, but I posted as I was working on it. What worked for me: I had a 2.3.3 stock image booted from Clockwork. I didn't have root permissions with the stock.
The new stock (is it technically a ROM, or is a ROM just Cyanogen, Bionix, etc., like awesome developers create?) preserved the unlocked bootloader (which I've not re-locked, because I never cared about the padlock boot), but not the root. So I was left with a stock 2.3.3 with an unlocked bootloader.
I tried everything to get my phone recognized via USB under the SDK/adb, but couldn't. I adbed and fastbooted devices, uninstalled and reinstalled PDAnet, even deleted and then redownloaded and reinstalled java, SDK, *and* drivers. To no avail.
The first time I rooted, though, I used the one-click method in the MoDaCo forums, by . . . Paul(?). I think that's his name. It's a simple zip file. So I unzipped to my desktop. Which gave me a folder with the GRI40 Nexus S superboot. I disconnected my phone, shut it off, then held the volume up and power keys until it booted into the fastboot bit. Once it was in fastboot (with the green Android and the orange text up top and the blue text options along the side), I reconnected the USB, then just double-clicked the .bat file in the superboot folder.
That gave me root. I verified via rootchecker, and the moment I confirmed root, I went to Clockwork, reflashed Clockwork Mod Recovery, and did a complete back-up. That's where I am now. Not sure where I'm going from here, but I have 2.3.3 GRI40 root with baseband i9020xxb1, and that's how I did it.
Click to expand...
Click to collapse
Are you on a PC or a mac?
PC
Loaded up Cyanogen. Seems okay. Tried adding the Honity kernel, but that seems to bugger everything up.
willentrekin said:
PC
Loaded up Cyanogen. Seems okay. Tried adding the Honity kernel, but that seems to bugger everything up.
Click to expand...
Click to collapse
Cyanogen is nice as it adds some features but if you've been living without them you might never notice having them lol. More people need to buy macs <.< I can help anyone get root on a mac >.>
I'm noticing that. It seems like kernels are what introduce problems for me; I've run Bionix and Cyanogen without issue, but as soon as I load up a kernel, I start getting force closes in any app that requires superuser permissions. I've discovered that managing the apps to clear their data/caches can help, but I'd like to find a more stable set up.
willentrekin said:
I'm noticing that. It seems like kernels are what introduce problems for me; I've run Bionix and Cyanogen without issue, but as soon as I load up a kernel, I start getting force closes in any app that requires superuser permissions. I've discovered that managing the apps to clear their data/caches can help, but I'd like to find a more stable set up.
Click to expand...
Click to collapse
When you flash the kernel run fix permissions before you reboot. For me cfs kernels.
I have a friends MT4G here and something went wrong when trying to get it permarooted, I'm not sure what happened before it got to me but I tried to start from scratch and restored the phone back to factory settings, I tried to use Visionary to gain temp root and then went to try permaroot and visionary kept coming back.
I then installed terminal emu. and tried to root and got as far as rebooting to check S-off and the phone keeps crashing, ( reboots then visionary pops up and shuts down, starts again and weather tries to refresh and crashes.) I'm looking for a way to get this phone back to the day it was bought so I can do this for him the right way. I need to know if A. it's even possible, B. what do I need if so, C. other options.
Hboot is there but tries to update and says update failed, Need a hand on this one.
Thanks in advance....
Edit / Update: OK I was told to try something else but now I have the phone working but no chance to get S-off yet, I did a Factory reset and formatted the SD card and poof I was back up and running, I tried to gain temp root then Perma root but it always goes back to S-On no matter what I try. I still have Hboot Recovery here but I'm having a problem getting any further so I'm hoping some one will have a suggestion or even a glimmer of hope they wanna throw my way, the phone owner is a good kid and helps out alot with my son and I really wanna get him back in action here.
Ok, so it sounds like your issue is a bad eMMC chip. This bad chip does not allow root to stick when using the visionary method. The only way to root is using the g-free method. But, when you have a bad eMMC and use the gfree method, you get corrupted partitions and after a while you get a bunch of errors in clockwork mod and end up with a bricked phone...kind of a lose lose situation.
lowandbehold said:
Ok, so it sounds like your issue is a bad eMMC chip. This bad chip does not allow root to stick when using the visionary method. The only way to root is using the g-free method. But, when you have a bad eMMC and use the gfree method, you get corrupted partitions and after a while you get a bunch of errors in clockwork mod and end up with a bricked phone...kind of a lose lose situation.
Click to expand...
Click to collapse
I found a way around the problem and got him back up and running but thanks for the heads up on the gfree, I did find the post on it.
Hey guys,
So today I decided to root my phone. I want to be able to use WiFi tethering without paying their ridiculous monthly fee, so I came here and read all I could about rooting my phone.
I downloaded the "Charge Kit V2" and proceeded with the instructions to install the "EE4stock_DXC.tar.md5" file to my phone. Everything worked as advertised and was completed in less than three minutes. I boot the phone, select the reboot option, and everything appears exactly as I left it.
Thinking I was rooted I downloaded the Android WiFi Tether app, but the thing won't work! So I go back to the FAQ and read that I could check to see if I were rooted by downloading a terminal emulator and typing "SU" into it. I did, and got "Permission Denied". I'm thinking this means I'm not rooted...
Am I rooted? If not, what did I do wrong? If so, why won't my WiFi tether work?
Thanks everyone!
ON edit: Just downloaded a root checker...apparently I'm not rooted. What could have gone wrong? Is the file I installed not rooted?
TomB985 said:
Hey guys,
So today I decided to root my phone. I want to be able to use WiFi tethering without paying their ridiculous monthly fee, so I came here and read all I could about rooting my phone.
I downloaded the "Charge Kit V2" and proceeded with the instructions to install the "EE4stock_DXC.tar.md5" file to my phone. Everything worked as advertised and was completed in less than three minutes. I boot the phone, select the reboot option, and everything appears exactly as I left it.
Thinking I was rooted I downloaded the Android WiFi Tether app, but the thing won't work! So I go back to the FAQ and read that I could check to see if I were rooted by downloading a terminal emulator and typing "SU" into it. I did, and got "Permission Denied". I'm thinking this means I'm not rooted...
Am I rooted? If not, what did I do wrong? If so, why won't my WiFi tether work?
Thanks everyone!
ON edit: Just downloaded a root checker...apparently I'm not rooted. What could have gone wrong? Is the file I installed not rooted?
Click to expand...
Click to collapse
I don't think that package is rooted, or at least it didn't root you when flashed (which happens sometimes).. use odin to flash CWM, boot straight into it and flash the superuser apk, when you boot up update the superuser app in the market and update the binary, after that you'll be rooted no problems
http://db.tt/4b3IK0C <--- superuser
blazing through on my 4G Droid Charge
Thanks for the reply!
Is there a good page with instructions on how to do this? I'm paranoid about bricking my phone and very new at this! Does the CWM load the same way the other.tar.md5 loaded?
What is a CWM?
Tried searching and didn't come up with much.
Thanks!
TomB985 said:
Thanks for the reply!
Is there a good page with instructions on how to do this? I'm paranoid about bricking my phone and very new at this! Does the CWM load the same way the other.tar.md5 loaded?
What is a CWM?
Tried searching and didn't come up with much.
Thanks!
Click to expand...
Click to collapse
this: http://forum.xda-developers.com/showthread.php?t=1160580 is a pretty good info thread on how to flash and what everything is though it's a little dated and most of the roms/CWM files are older, everything else like drivers and Odin versions are fine... CWM is short for ClockWorkMod recovery and along with Odin is what we use to flash roms/kernels/etc. to our phones, and yes in Odin it goes in the same PDA spot as a rom and flashes like normal... however since you don't have a custom kernel to make CWM 'stick' in your system its one time use after you flash it in Odin and you will have to Odin flash it again every time you want to use it, making it perfect if all you want to do is simply root the phone
Please use the Q&A Forum for questions Thanks
Moving to Q&A
THANKS!!!
After tinkering with it a few times, as well as a scare with a failed flash and temporarily bricked phone, I got it to work! I'm now rooted and have successfully run the tethering app with no errors.
Thank you for your time, you made this easy! And I didn't destroy my shiny new phone!
TomB985 said:
After tinkering with it a few times, as well as a scare with a failed flash and temporarily bricked phone, I got it to work! I'm now rooted and have successfully run the tethering app with no errors.
Thank you for your time, you made this easy! And I didn't destroy my shiny new phone!
Click to expand...
Click to collapse
nice glad to hear it, its a piece of cake after you do it once and learn it
blazing through on my 4G Droid Charge
I noticed after taking one of the lineage updates I lost root. I tried to reroot with odin and managed to pork my phone quite good. It took me until about now to get it rooted, unlocked and finally TWRP loaded. Recovery was fighting me the most. Refused to install in odin. I finally got a working rom on it so it would boot. Used casual to root and unlock but TWRP failed in that as well. I finally tried a TWRP app (not the official one, I couldn't get that to work) and I may have my phone back now. Waiting to see if my backup is going to work. Welp, it didn't like the restore and I got the ! triangle saying go back to verizon.
While I was looking through my drives I noticed I have a ton of files but don't know exactly what they are. I've had this phone since I pre-ordered it so at one time the files were valid. What files exactly do I need to totally unpork a phone? I have odin 3.07, the VRALEC bootchain, the VRALF one but odin says it's invalid, and a file called combination_I535VRALG1_I535VZWALG1_743127_REV09_user_low_ship. Using them I can get my phone back to seemingly stock.
Is there a better way? Or at least a way to totally start from scratch and hopefully get lineage back on? I know not to take any of the OTAs since they will relock the bootloader. I don't like that it seemed that it was going to automatically install the update but I'll just keep the phone off until I can sort it. I also have a bunch of other files across 3 computers so if there is a file that's needed but isn't posted somewhere there is a chance I might have it already.
I've been searching for the past day and I've found tons of info but some things don't work and some only kinda work. Any help would be much appreciated.
More info: I am on 4.04 so the bootloader should not be locked. The phone is beat up and the USB connector is wonky. Only a few cables will work and I have to make sure it doesn't move or it will disconnect. It does mention that the secureboot is enabled in download.
I've had it rooted, running a stockish rom and managed to get TWRP on it but when I went to restore my lineage backup, it all went to hell.
So I'm now having issues with the bootloader. ON the download screen it says custom binary download yes (5 counts), Current binary samsung official, system status official and secureboot enable. Pretty sure that means casual didn't work. I have root but not bootloader. Is there another option than casual? I've seen ez unlock 1.2 mentioned but the links are dead.
Why am I remembering flashing something in stock recovery? It's been a long, long time since I've gone back this far. I feel like I'm close since I saw the unlocked screen last night but restoring screwed that all up.
This doesn't make sense. I installed TWRP but it still says the same as above leading me to think my bootloader is not unlocked. I don't get the unlocked boot screen either.
How can I install TWRP with a locked bootloader?
Well it's obious that I can get root, install TWRP but for some reason casual will not unlock the bootloader. I can't seem to find the old thread nor any files to just unlock the bootloader. I know somehow I did it last night as I saw the unlocked screen it's just damned if I can do it now. It must have been another file I had at home but don't have here on the laptop.
It's damn frustrating since this time yesterday I had a working phone running nougat and my dumb ass broke it.
I know this forum is a bit dead, as expected for a 5 year old phone but hopefully someone will see this and have some sage like advice.
Turns out It takes almost a week and a mixture of 3-4 guides here. Some Odin, some Casual, some TWRP flashing and luck. FInally I'm back to where I was before I hit the wrong button.