Related
Hey guys I have to send back my thunderbolt to VZ, I just got the Charge instead cuz the TB sucked!!
I rooted my TB and all, I was ready to Unroot using the ADB way... I uploaded the 3 files and then it says ADB: no such file for the recovery part.
So Then I wiped my cache and my Partition thinking I was good to go with the upload from Zip through recovery. That didnt work
Now Im trying to get the phone into Download mode so I can connect using Odin. Then Flash a Stock Rom using Odin onto phone....
Also when in Terminal App on phone and get SU permissions and then try ADB: Reboot Download or recovery , I get ------ No Such Tool?
questions are How do I Unroot this Damn phone to send back to VZ???
And how do I flash stock Rom without Odin?
The TB in no way sucks. It will slaughter that POS Charge.
Luke
Odin? isn't that a samsung thing?.. HTC uses RUU's
Thunderbolt doesn't have a download mode.. and when in the terminal on the phone you don't need the adb: part.. just "reboot recovery" and when using adb on the computer don't use a colon ":" either just adb
Anyways.. here is a link to unroot.. it should help
Also.. I went from the Charge to the thunderbolt... much happier... Charge battery life was just about as bad.. if any better its because its a slightly bigger battery
yurdle said:
Odin? isn't that a samsung thing?.. HTC uses RUU's
Thunderbolt doesn't have a download mode.. and when in the terminal on the phone you don't need the adb: part.. just "reboot recovery" and when using adb on the computer don't use a colon ":" either just adb
Anyways.. here is a link to unroot.. it should help
Also.. I went from the Charge to the thunderbolt... much happier... Charge battery life was just about as bad.. if any better its because its a slightly bigger battery
Click to expand...
Click to collapse
been searching dude, Im stuck it doesnt load and for some odd reason not letting me flash a rom. Any suggestions?
http://www.androidpolice.com/2011/0...t-the-htc-thunderbolt-and-return-it-to-stock/
thats what I been following, when I go to the reboot recovery it says no such file
Sorry you are having trouble. Please read this thread:
[HOWTO] Restore to stock for root users and non-root users UPDATED 5/17/2011
http://forum.xda-developers.com/showthread.php?t=1009423
It is an update from the method you have been trying. I assume you are still rooted? Follow the first part of the tutorial, it is for rooted phones needing to return to stock. I have used this method a couple of times without issue.
I would suggest starting from the beginning and re- download all of the files. Check mdsum5, painstakingly follow each and every step and you should be returned to stock in about 20 minutes once you have downloaded all of the files.
Odin is not a tool we use with the Thunderbolt. We use ADB shell and Hboot and CWR as means of flashing Roms, radios and other files to our phones. I assume you are at least a bit familiar with these as at some point you rooted your phone.
Another piece of advice, its free and you don't even have to thank me; when you get your new awesome Charge and you start having issues with it and you just can't seem to figure out which key words to rub together in Google to find the magical solution. You may want to avoid going to the Charge forums asking for help stating that the Charge sucks but you people should help me out anyway. You might find that people are more inclined to help you out. I'm just saying.....
tswltd said:
Sorry you are having trouble. Please read this thread:
[HOWTO] Restore to stock for root users and non-root users UPDATED 5/17/2011
http://forum.xda-developers.com/showthread.php?t=1009423
It is an update from the method you have been trying. I assume you are still rooted? Follow the first part of the tutorial, it is for rooted phones needing to return to stock. I have used this method a couple of times without issue.
I would suggest starting from the beginning and re- download all of the files. Check mdsum5, painstakingly follow each and every step and you should be returned to stock in about 20 minutes once you have downloaded all of the files.
Odin is not a tool we use with the Thunderbolt. We use ADB shell and Hboot and CWR as means of flashing Roms, radios and other files to our phones. I assume you are at least a bit familiar with these as at some point you rooted your phone.
Another piece of advice, its free and you don't even have to thank me; when you get your new awesome Charge and you start having issues with it and you just can't seem to figure out which key words to rub together in Google to find the magical solution. You may want to avoid going to the Charge forums asking for help stating that the Charge sucks but you people should help me out anyway. You might find that people are more inclined to help you out. I'm just saying.....
Click to expand...
Click to collapse
Very well put...
Sent from my ADR6400L using XDA Premium App
Hello, all!
I ran through lots of threads, but I cannot find a remedy for my problematic rooting.
Firstly, maybe I have to warn you that I'm noob in rooting devices, I promise I'll catch up!
I very much would like to root my Dell Streak, I chose SuperOneClick 2.3.1 to do so.
I got SuperOneClick, turned my phone in USB debugging mode, allowed unknown apps, unmounted SD card.
Connected all cables...press Root and SuperOneClick gets non-responding after:
(see attached picture)
In this situation if I run adb devices I see mine listed.
Have you had similar situation? Have you got any ideas how to finish rooting my phone?
Ok. Forget SuperOneclick Go to this link and read, absorb, read again, read once or twice more then, absorb. Finally read over many more times and once you think you've taken it all in, read it again. Honestly. Rooting is great if you get it right but it's what nightmares are made off if you brick your phone.
http://forum.xda-developers.com/wiki/Dell_Streak_5/Flashing_Guide#Rooting_your_phone
Basically, you need to install Streakmod (a custom recovery) using "Fastboot". This will enable you to install "Superuser. zip". This will "Root" your phone. Best of luck.
You're nicer to him than I would have been. All I will add to what you said is that the search engine is his best friend and he might want to learn how to use it.
Yeah, but if the OP comes back with the same question i'll send em back to the same link. As you know, there is probably an answer to every "Android" related question within this forum. People just need to look. I'm just being nice cos back in February i was a noob asking the same question. What i quickly learned was, if you bother to look, you find and you learn loads of other valuable stuff along the way.
I had simialar issue and solved it
my dell streak was not able to fastboot dellstreakMOD because after reboot the system auto overwrite mod file. So I need Root first to trick/disable auto overwrite function.
Then I run into SupperOneClick 2.3.1 issue. I solved problem by using much older version supper One Click 1.55.
Good Luck!
One-click root solutions aren't recommended for the Streak because as you found out, they don't always work. However, the method on the wiki has a success rate of 100%. So what I don't understand is, why in the heck would anyone use a method that has a high rate of failure over a method that doesn't.
hey...s.o.c is no more recommended...
just flash the su.zip using streakmod and voila.. nothing else
Sent from my Dell Streak using xda premium
alpharetta said:
my dell streak was not able to fastboot dellstreakMOD because after reboot the system auto overwrite mod file. So I need Root first to trick/disable auto overwrite function.
Then I run into SupperOneClick 2.3.1 issue. I solved problem by using much older version supper One Click 1.55.
Good Luck!
Click to expand...
Click to collapse
The reason, why we are using the SupperOneClick is already mentioned: You are proposing us to do the fastboot method to get the custom recovery running. But to do so on the streak we first need to avoid the automatic restore of the stock-recovery tool. And to do so, we need a rooted device...
You see our point? It's like a cat biting in it's own tail, or a man sucking his own... You got me though?
It's not a proposal. If you bothered to look at the bottom of the flashing guide page on the wiki, you would have seen the following note:
Not recommended: Gingerbreak, SuperOneClick, Universal Androot, Z4Root
Click to expand...
Click to collapse
That note is on the flashing guide for a reason: these methods quite frequently do not work on the Streak. Besides, this really isn't as difficult as you're making it sound. The one thing that needs emphasis is that you'll install StreakMod Recovery twice. The first time is to root. The second time comes after using a file manager to delete install-recovery.sh, the file that causes the recovery to get overwritten.
If that series of steps in the flashing guide is too much for you to handle, I would not recommend rooting. The Streak is arguably the easiest device to root, requiring no special tools like goldcards to do the job. If you want a real challenge, try rooting an HTC Inspire. Without special tools an Inspire cannot be rooted.
Hi there quick question as I just got my hands on a Dell streak I see you post the guide for rooting and say its 100% safe is this 100% correct cause I don't fancy bricking it also will it work on build froyo 2.2.2?
By the way I'm not not a noob as I rooted my dhd the hard way round when it first came out the same way the inspire was rooted also built 2 custom roms and work on 3 others
Only asking cause the set up of the Dell is very different to an htc and a year on htcs are getting easier to root with a one click tool
And please don't say to read read and read again as that's what I will be doing anyway I ain't going to fly before I can walk lol
sent from my dhd
This rooting method works with any stock ROM. One-click methods fail for various reasons, and on a failure are likely to require the restore tool we have for the purpose, QDL Tool, in order to recover from the failed root.
With a Streak you need nothing more than some knowledge of how to use Fastboot to get the recovery on the Streak. This is more educational than using a one-click tool in my opinion. From there, the trick is immedately booting into the recovery after flashing it so you can flash superuser.zip. Once you've got superuser.zip on the device, you're rooted even if the recovery is overwritten. For best results however, you need to make sure to delete the file I mentioned in my prior post and install the recovery a second time. The one part that seems to trip most people up is flashing the recovery twice. They don't anticipate the recovery they just installed being removed when they try to get into it.
Now, is it 100% safe? Unless you do something you're not supposed to such as pulling the cable while in the middle of flashing a recovery or trying to erase the Streak using fastboot -w/fastboot -erase it's very safe. Safer in my opinion than the AAHK for the Inspire because with the AAHK you have numerous opportunities to brick the Inspire (S-OFF, Radio Install, Recovery Install) instead of just one (Recovery Install).
I don't have to tell you to read and read again. My sig takes care of that. But after 3,000+ posts I don't think you have to read my noob FAQ. Especially as you are not a noob.
Strephon Alkhalikoi said:
This rooting method works with any stock ROM. One-click methods fail for various reasons, and on a failure are likely to require the restore tool we have for the purpose, QDL Tool, in order to recover from the failed root.
With a Streak you need nothing more than some knowledge of how to use Fastboot to get the recovery on the Streak. This is more educational than using a one-click tool in my opinion. From there, the trick is immedately booting into the recovery after flashing it so you can flash superuser.zip. Once you've got superuser.zip on the device, you're rooted even if the recovery is overwritten. For best results however, you need to make sure to delete the file I mentioned in my prior post and install the recovery a second time. The one part that seems to trip most people up is flashing the recovery twice. They don't anticipate the recovery they just installed being removed when they try to get into it.
Now, is it 100% safe? Unless you do something you're not supposed to such as pulling the cable while in the middle of flashing a recovery or trying to erase the Streak using fastboot -w/fastboot -erase it's very safe. Safer in my opinion than the AAHK for the Inspire because with the AAHK you have numerous opportunities to brick the Inspire (S-OFF, Radio Install, Recovery Install) instead of just one (Recovery Install).
I don't have to tell you to read and read again. My sig takes care of that. But after 3,000+ posts I don't think you have to read my noob FAQ. Especially as you are not a noob.
Click to expand...
Click to collapse
Thank you very much for the info seems pretty much straight forward will crack on with it in a few days once I'm familiar with as much as I can need to learn the streak more before I start playing lol
As for the inspire its pretty much the same as a dhd and tbh flashing a radio is as simple as flashing a Rom from recovery I also tested flashing the radio from a different htc phone and regardless that it flashed but got stuck on splash screen I could still not brick the phone, now its really difficult to brick inspire or dhd, but it is known that eng s-off can cause issues on the inspire but not on the dhd
Just some info back for yourself mate as a thank you for yours also will hit the thanks button next time I'm pc
sent from my dhd
Thanks for the info. I rooted my roommate's Inspire using the AAHK on the day she got it. It ended up being a little more time consuming than using REVOlutionary to S-OFF my Aria the second time I rooted it*. I proceeded to put Android Revolution on the Inspire and she's a happy camper.
*The first time I rooted the Aria, which was the day I got it a year ago, I used UnrEVOked to root it. At the time there was no S-OFF possible.
Perspective for users of devices with locked bootloaders:
All dell devices are the equivilent of S-OFF/unprotected bootloader devices.
S-OFF, root, and custom are all seperate (but closely intertwined) concepts.
There are equivilents of superuser.zip for the nexus devices, as they ship either S-OFF or have
'fastboot oem lock/unlock' available to allow the user to S-ON or S-OFF at will.
Superuser.zip is equally valid on an already s-off'ed device that has a custom rec installed.
If your device can be officially S-OFFed and you install a custom recovery and use superuser.zip (or the device's equivilent form) you never have to touch a one click tool.
If your device is S-ON and there is no official way to S-OFF you must S-OFF it first, usually that requires making changes on it while it's on, which usually requires root. The only way to root a live device is though exploits in android, this is what one click tools do.
After having S-OFF'ed you can install a custom rec, and then it doesnt matter if you're rooted or not as you can install custom recs.
As long as you remain S-OFF'ed you never have to worry about rooting as custom recs/flashing zips completely bypasses android's security model.
This is the only reason that Android 3.0+ can be rooted, the ONLY ways to root 3.0+ is by rooting outside android. There are no known exploits in 3.0+ (and hence ICS devices are completely unrootable for the time being if S-ON) Every single 3.0+ device is rooted by either by superuser.zip or superboots (which are normal kernels that automatically install superuser.zip without needing a custom recovery)
The problem with superboots are that they are device AND rom specific, during the 2xx era for the s5 there were superboots available. But they had to be remade for every single version as flashing the wrong one will brick your device.
Most of the exploits used by one click tools are patched by 360, and I believe ALL exploits are patched in 4xx. Normally there are known vulnerabilities in 2.3.3, but Dell has added their own fixes to these seeing as it's one of the few devices running 2.3.3 that hasnt been updated to 2.3.4 or higher
Superuser.zip is version independant, and to a degree device independant. As long as it can mount your /system partition it can root it.
The S-ON/S-OFF terminiology is specific to HTC devices, but the concept is common to all android devices;
Dell = always S-OFF
HTC = dependant on device/carrier
Moto = mostly S-ON, some atrix's can be unlocked, xooms always unlocked
Samsung = usually S-OFF
'fastboot oem unlock' = sets S-OFF if allowed
'fastboot oem lock' = sets S-ON if allowed
Ok here it goes I have had nothing but HTC android devices on sprint. Sometime this week I will be getting the note. I am no noob with HTC devices I can do a pretty big amount of stuff but with Samsung its a different story. Especially this whole thing of using odin to do stuff is new to me. One of my question is this do you have to use odin or can you use cwm for everything? The other question is this why do samsung devices need a root kernel where as other devices need the hboot unlocked or a root in the system? Also I have init.d scripts and init_post_boot.sh files that I have edit to my liking with editing can I make them run on the note? Most of them are settings that i like and feel make my phone run the best.
Sent from my PG86100 using xda premium
Your scripts will work and Samsung just has a different way they pack their software then HTC and the other company's.
ODIN is what we mainly use to get started or revert back to stock once you are rooted with a customer recovery like CWM you can use Clockwork and flash roms and kernels but to revert 100% to stock you will be looking at ODIN which is super easy to use. Basically you put your phone in download mode and it finds your phone you select what you want to flash follow instructions on that file you are flashing and it'll reboot when done.
My personal experience I've bricked a few phones but everyone I was able to bring back with ODIN =) & you will love the feel of Samsung Phones over HTC I went from a Captivate to a Inspire wasn't happy then went to a Infuse now I'm on my Note =)
& about the Root kernel it's easier to root the phone that way from what I've noticed the devs doing.
sent from AT&T Samsung Galaxy Note Dual Core 1.83 GHz
maxjivi05 said:
Your scripts will work and Samsung just has a different way they pack their software then HTC and the other company's.
ODIN is what we mainly use to get started or revert back to stock once you are rooted with a customer recovery like CMW you can use Clockwork and flash roms and kernels but to revert 100% to stock you will be looking at ODIN which is super easy to use. Basically you put your phone in download mode and it finds your phone you select what you want to flash follow instructions on that file you are flashing and it'll reboot when done.
My personal experience I've bricked a few phones but everyone I was able to bring back with ODIN =) & you will love the feel of Samsung Phones over HTC I went from a Captivate to a Inspire wasn't happy then went to a Infuse now I'm on my Note =)
& about the Root kernel it's easier to root the phone that way from what I've noticed the devs doing.
sent from AT&T Samsung Galaxy Note Dual Core 1.83 GHz
Click to expand...
Click to collapse
Thank you I appreciate it
Sent from my PG86100 using xda premium
I just got the razr coming from Samsung's galaxy S (t-mobile vibrant) which I had rooted, OC'd, and running ICS on. I'm not new to rooting/flashing kernels/roms, etc. but I am new to the razr.
I am just wondering if there are any safety features built into this system in case something happens or it gets bricked or something? On the vibrant I could ALWAYS get into download mode and use a computer program called ODIN to flash my phone back to stock. It was nearly impossible to brick it... is there anything like this with the Razr yet?
From what I understand so far, I will root it, install safestrap (i.e. CWM) and then I can flash any of the Razr roms I want... Correct? Thanks guys!
in_dmand said:
I just got the razr coming from Samsung's galaxy S (t-mobile vibrant) which I had rooted, OC'd, and running ICS on. I'm not new to rooting/flashing kernels/roms, etc. but I am new to the razr.
I am just wondering if there are any safety features built into this system in case something happens or it gets bricked or something? On the vibrant I could ALWAYS get into download mode and use a computer program called ODIN to flash my phone back to stock. It was nearly impossible to brick it... is there anything like this with the Razr yet?
From what I understand so far, I will root it, install safestrap (i.e. CWM) and then I can flash any of the Razr roms I want... Correct? Thanks guys!
Click to expand...
Click to collapse
you need to be more informed before flashing any of the razr rom's
not every custom rom will provide both, CDMA and GSM... so you need to differ witch one's will work with your device.
way to install is right. rooting, safestrapping, flashing... but keep an eye on the rom preferences
downlode mode... yeah, i think so... bricked my razr with flash failre, boot was unavailable... but could enter fastboot mode (POWER + VOLDOWN) to flash some new rom via rsd lite or fla**** by eternityproject
ok thanks... well, I have the Razr with Verizon in the US. But when I was talking to the verizon rep, he said that it uses both CDMA and GSM... (because I had asked him why they had switched over to SIM cards). He said that they are using the GSM network for data only because it works much faster/smoother for data. But it was my understanding that they are still using CDMA for voice. Am I wrong?
Do you have any threads you could post to explain the process to a newb? =) I have read a lot of the stickies... thanks for the response!
I have a Galaxy Note i717 from AT&T that I rooted. Worked great.
Yesterday I upgraded to ICS via Kies. Worked great.
Then I proceeded to root it again using odin.
Unfortunately even after all the things done it now will not boot up at all.
All I get is the S a m s u n g logo. I can put it into boot mode and the computer see's it but nothing more.
If anyone can point me to any rom/bootloader/ etc. I would be most grateful.
Or just let me know what to do and where to get roms. I did search and there are many for the i700.
I guess I need a bootloader and rom right?
Sorry folks. Point me somewhere else will have to get another phone.
T h a n k s ...
Others would tell you to look in the dev section for the stock rom (its usually called something like "in case of brick) I've had issues issues getting it to work but Im certain it was user error as to why it didn't work for me. But another option that I think could work would be to get your phone into download mode and run the ics upgrade thru kies again. You'll lose everything in your phone but I think it'll get your phone up and running again. But before you do any other that...did you make a nandroid back of? Or have you downloaded any roms to your phone because if you did you can just enter cwm and reflash any rom you may have or just flash your backup, backups are so important when doing these sort of things, saves a lot of head aches.
Edit: after reading your post again it says your phone messed up after rooting, try and re run the root file thru Odin, I kinda sorta remember reading something similar to this were people had issue trying to root. I'll try and find the thread.
Sent from my SAMSUNG-SGH-I717 using xda premium
this happened due to rooting with the Gingerbread method...so using Nash reply run/reinstall your Official ICS...and to root....
see My Links in red in my signature...go the GNote Super page....you should see what is being used to root the Official ICS...I used it and lots others, there prob more methods out there, but I found this is the easiest and more proven method....
Cant miss the info on GNote page regarding Rooting.
so to recap...since your believe you have bricked your phone...
use the method Nash replied to you with...put into download mode....run the official ics, you will need the model, serial number of your phone...
let us know how it works out for you...
mpanwar said:
I have a Galaxy Note i717 from AT&T that I rooted. Worked great.
Yesterday I upgraded to ICS via Kies. Worked great.
Then I proceeded to root it again using odin.
Unfortunately even after all the things done it now will not boot up at all.
All I get is the S a m s u n g logo. I can put it into boot mode and the computer see's it but nothing more.
If anyone can point me to any rom/bootloader/ etc. I would be most grateful.
Or just let me know what to do and where to get roms. I did search and there are many for the i700.
I guess I need a bootloader and rom right?
Sorry folks. Point me somewhere else will have to get another phone.
T h a n k s ...
Click to expand...
Click to collapse
And once you're rooted and all fixed up, enter cwm and create a backup. These are great because no matter what you do to your phone as long as you can enter cwm you'll always be able to fix your phone via backup.
Sent from my SAMSUNG-SGH-I717 using xda premium
I wanted to mention, I'm not sure how you updated thru kies originally (legit update or emergency update) the method you'll be using this time (if you choose to fix thru kies) is the more or less emergency method. I wanted to mention this because when your in download mode and connect your phone to your PC and run kies, kies will try to connect to your device but will time out over time...it took me 2 days of Q and A before I realized kies won't connect with phone in download mode, but that's OK. Once phone is connected click tools/firmware upgrade and initialization, and as bigjoe said youll than need to input model and serial numbers (all caps) than click OK. You'll have a few prompts afterwards but yo basically on your way to a running phone.
Sent from my SAMSUNG-SGH-I717 using xda premium
Brick = nothing at all happening on phone.
Samsung logo = bad flash (corrupt file used)
Brick can sometimes be revived with a JTAG device.
Samsung logo means re download file, re read instructions and relevent thread, and redo your work.
Don't be too anxious -you will fix it.
I suggest using Kies upgrade > emerency firmware method. Download mode is the key.
If you are with Rogers, the following is useful.
http://forum.xda-developers.com/showthread.php?t=1657262
I went through the exact same problem with someone else's Note that I was upgrading, subsequently flashing.
The above process bring the phone back to 100% stock gingerbread.
Thanks All and Resolved.
eugenekim618 said:
If you are with Rogers, the following is useful.
http://forum.xda-developers.com/showthread.php?t=1657262
I went through the exact same problem with someone else's Note that I was upgrading, subsequently flashing.
The above process bring the phone back to 100% stock gingerbread.
Click to expand...
Click to collapse
Thanks all for the replies.
I was able to go to DEV Section and get the full AT&T ICS Rom. Used ODIN to get it back to factory ICS.
Then (with great care ) re-rooted it using ICS root stuff. I have it all in case anyone else needs this route. Else follow instructions above.
Thanks all. I think for now ICS is where this will stay. In fact Gingerbread was good enough except for not being able to use Chrome.
mpanwar said:
Thanks all for the replies.
I was able to go to DEV Section and get the full AT&T ICS Rom. Used ODIN to get it back to factory ICS.
Then (with great care ) re-rooted it using ICS root stuff. I have it all in case anyone else needs this route. Else follow instructions above.
Thanks all. I think for now ICS is where this will stay. In fact Gingerbread was good enough except for not being able to use Chrome.
Click to expand...
Click to collapse
great, can you put solved in the title...thx