So recently I applied the stock rooted 4.0.4 rom to my CDMA Nexus. After this, it would have this strange problem where occasionally the screen would just not respond to any touch. I would battery pull many times over before it would start working again. Tonight I finally got fed up and tried to apply the factory image (4.0.2) to it through Wug's root toolkit v1.3. When it completed the phone went into a serious bootloop, not getting past the google logo. What happened? Did I just make a very expensive paperweight?
Restore everything to an earlier time including the bootloader, recovery, radios, and rom through adb. You can also use a toolkit like the one found below to restore your phone to stock then redo everything:
http://forum.xda-developers.com/showthread.php?t=1392310
Yeah, I've tried that a few times and it's still stuck on the Google image and won't move forward. Just restarts and restarts.
Another evidence that 1 click methods leads to ppl doing stuff without any understanding
Thanks for your help, sir. I know I'm not the most knowledgeable but you don't have to rub it in. I'm already down a phone.
Sent from my HTC_Flyer_P512_NA using xda premium
thurstroubadours said:
Thanks for your help, sir. I know I'm not the most knowledgeable but you don't have to rub it in. I'm already down a phone.
Click to expand...
Click to collapse
There really are tons of threads here telling you exactly what to do in a case like yours - you just have to use the search and take the time to read through them.
And no, it's not bricked as long as you can get into the recovery.
thurstroubadours said:
Thanks for your help, sir. I know I'm not the most knowledgeable but you don't have to rub it in. I'm already down a phone.
Sent from my HTC_Flyer_P512_NA using xda premium
Click to expand...
Click to collapse
While I understand your anger, he does also make a valid point. 2 reasons why. If you didn't use a one click method maybe your phone would be working fine. 2nd by doing it the hard way hopefully you learned something and when you have a problem you know how or at least understand what is involved with fixing it.
Hope you get it fixed.
Sent from my Nexus S 4G using xda premium
exactly, my intention was not to make you feel bad.
I was hoping this example would make ppl learn the proper way.
As if you did, you wouldnt be in this predicament.
You would also know that you haven't bricked your device, not freak out over it and just fix it.
Cold hard facts are generally blunt and I understand your frustration, I also appreciate that you didnt start a flame war.
Hope you've sorted it out and and learned something in the process.
Good luck.
Ok. I did manage to fix it by learning how to manually flash the stock image. Perhaps I did need the hard line!
Sent from my HTC_Flyer_P512_NA using xda premium
Related
The title says it all. The only prerequisite is that you already have the drivers for your phone installed. Which i assume most people looking at this thread do as they were needed to get root in the first place.
Always back up your stuff and any apps before using.
Features:
Restores back to stock 2.3.4
Relocks Bootloader
Removes root
Fixed:
1. Now it will not run when gsm users try to use it.
2. Runs alot smoother thanks to Indirect.
Download this zip.
Extract it
Click on run.bat
and follow the onscreen instructions
now your phone should be back to 100% stock
Thanks to pete for the img files
Thanks to Indirect for the fixing problems with gsm users using this.
so this will unroot, relock, and put stock recovery back on?
Yes it returns it to the same way it was when it came out of the box. So be sure to back up any data on your internal memory you want to keep.
sweet, thanks to you and pete
hellcatt said:
sweet, thanks to you and pete
Click to expand...
Click to collapse
No problem. I just decided to automate his process. And include all the files you need. Also if anyone needs the drivers just use pdanet as described in the one click root thread
yea i know there are the purests out there that dont believe (so to say) in the one clicks but those of us who are only partial idiots and cant figure out sdk, odin, and whatever else there is the one clicks really help. i know what i want my phone to do i just want the "for dummies" way to do it
It's like a dream come through, I now know this ns4g section of XDA is the best section.
Thanks to Mike & Pete for their Energy and Persistence.!!!
Sent from my Nexus S 4G using XDA Premium App
hellcatt said:
yea i know there are the purests out there that dont believe (so to say) in the one clicks but those of us who are only partial idiots and cant figure out sdk, odin, and whatever else there is the one clicks really help. i know what i want my phone to do i just want the "for dummies" way to do it
Click to expand...
Click to collapse
No problem. Thats how i am too. Thats why i make everything i use flashable or simple and easy.
Thank you SO SO SO SO SO much! I had installed the netarchy-nexus kernel on mine, which killed my battery way to fast, and I couldn't remove it...not even with my nandroid backup.
Jyro275 said:
Thank you SO SO SO SO SO much! I had installed the netarchy-nexus kernel on mine, which killed my battery way to fast, and I couldn't remove it...not even with my nandroid backup.
Click to expand...
Click to collapse
Glad to hear i helped
hellcatt said:
yea i know there are the purests out there that dont believe (so to say) in the one clicks but those of us who are only partial idiots and cant figure out sdk, odin, and whatever else there is the one clicks really help. i know what i want my phone to do i just want the "for dummies" way to do it
Click to expand...
Click to collapse
You and me both. I just learned earlier this week that fastboot and adb were drivers that come with sdk. It is confusing without a literal step by step guide. I would like to learn all the processes and make a guide for total beginners. Unless anyone else knows of one already in existence for the NS4G?
I must admit, though, that the more threads I read the more confident I get about following through with it. All of you devs and themers and advanced users, I tip my hat to your knowledge and helpfulness with threads like these.
Sent from my Nexus S 4G using XDA Premium App
HareyCarey said:
You and me both. I just learned earlier this week that fastboot and adb were drivers that come with sdk. It is confusing without a literal step by step guide. I would like to learn all the processes and make a guide for total beginners. Unless anyone else knows of one already in existence for the NS4G?
I must admit, though, that the more threads I read the more confident I get about following through with it. All of you devs and themers and advanced users, I tip my hat to your knowledge and helpfulness with threads like these.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Things get easier with time. Also having the great people on this forum around helps too
Big thanks to you! I was having screen issues and this made my life easier so i can take my phone to sprint tomorrow!
difrent7 said:
Big thanks to you! I was having screen issues and this made my life easier so i can take my phone to sprint tomorrow!
Click to expand...
Click to collapse
What screen issues are you having?
thanks for this. I wanted to return to stock for the update and did it the long way,because i don't think this was posted yet. I think anyone that is rooting their phone should at least learn how to use sdk and the commands. Im glad I had to force my self to do it that way, but this will really help for the next time with one click root and now unroot its great. I had to root again because it was delayed and cant stand stock
No problem and yes the long way is beneficial from a learning standpoint. But i prefer quick and easy and anyone who wants to learn the long way just open the run.bat file in notepad and teach yourself
michaelpeerman said:
No problem and yes the long way is beneficial from a learning standpoint. But i prefer quick and easy and anyone who wants to learn the long way just open the run.bat file in notepad and teach yourself
Click to expand...
Click to collapse
Does it have detailed step by step instructions or more of an overview?
Sent from my Nexus S 4G using XDA Premium App
HareyCarey said:
Does it have detailed step by step instructions or more of an overview?
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
open it and look, its the commands you would have to type in
This is way awesome, thanks
Some think this is a lazy way, but some of us have to find work arounds for stuff like this. Right now I'm stuck using Wxp/ home, tried everything I could think of and still couldn't get sdk installed . This helps enormously. I don't mind learning the hard way, but I also like to do things efficiently and save time.
Thanks
Sent from my Nexus S 4G using XDA App
Joey_ufc said when he runs. Bat, says he is missing files, any help
Sent from my Nexus S 4G using XDA App
really struggling here. first day coming from the evo. i rooted, backed up with clockwork and flashed this caulkin rom. i am in an endless boot loop somhow. problem is i cant seem to be able to get into clockwork now and fix things. at first when i held volume and power it went into ODIN downloading mode which i am completely unfamiliar with
please help, how can i get into clockwork to reinstall my backed up rom? how do i get out of this loop? thanks.
I have the same problem I think. Its the "Android" letters or the 4G sprint thing?
Go to dev fourm and then click first sticky
There will be a YouTube link click it
Follow instructions
Sent from my SPH-D710 using xda premium
gtuansdiamm said:
Go to dev fourm and then click first sticky
There will be a YouTube link click it
Follow instructions
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
can't i just somehow get in clockwork without going into ODIN and putting my phone back into stock?
knives of ice said:
can't i just somehow get in clockwork without going into ODIN and putting my phone back into stock?
Click to expand...
Click to collapse
My friend asking for help here is not a problem but coming from the Evo like I did you know that there are ways out of just about anything. Like the poster above said is 100% correct. Instead of sitting here waiting for answers use Google, use the stickies remember what you did prior on your Evo. Now for my part of helping you out, its vol up + power will take you to recovery. Or here's a thought plug it in your pc and use adb.. How about the command adb reboot recovery..
Now to me if you read up on the phone research threads before you went in on it then these trouble shooting tips would be second nature. Sorry if I sound like a **** but too many of us are in here messing with phones and have no clue what to do if we screw up and especially when there are a million HELP ME THREADS....
Good luck and hope it works out for you...
knives of ice said:
can't i just somehow get in clockwork without going into ODIN and putting my phone back into stock?
Click to expand...
Click to collapse
I don't really thinly so
Sent from my SPH-D710 using xda premium
knives of ice said:
can't i just somehow get in clockwork without going into ODIN and putting my phone back into stock?
Click to expand...
Click to collapse
Just thought I would check..are you holding volume up and power long enough? It will show the SGS2 screen twice before going to recovery
Sent from my SPH-D710 using xda premium
JohnCorleone said:
Just thought I would check..are you holding volume up and power long enough? It will show the SGS2 screen twice before going to recovery
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
This was my problem you need to hold them at the same time for waaaaay longer than needed on the evo.
Once i got in clockwork it was smooth sailing but there was no way for me to know these subtle differences
knives of ice said:
This was my problem you need to hold them at the same time for waaaaay longer than needed on the evo.
Once i got in clockwork it was smooth sailing but there was no way for me to know these subtle differences
Click to expand...
Click to collapse
Glad you got everything worked out. I came from the Epic and seeing the splash screen twice was new to me as well.
Sent from my SPH-D710 using xda premium
Oh wow i thought you soft bricked your phone
Sent from my SPH-D710 using xda premium
knives of ice said:
This was my problem you need to hold them at the same time for waaaaay longer than needed on the evo.
Once i got in clockwork it was smooth sailing but there was no way for me to know these subtle differences
Click to expand...
Click to collapse
That was kinda my point. If you did a little research or better yet QbKing has a million videos you would of know this. Once again my bad but too many of us are just panicking and posting questions that are clearly answer in these threads or are really simple to figure out... Glad you figured it out though...
i think i bricked my epic 4g touch. i had ics fb21 on it and i tried to restore a gingerbread rom back onto it via cwm and something went terribly wrong. i tried all the steps in qbking77s youtube video about unbricking/unrooting. my phone successfully went through the steps but when it reboots it just boot loops. when i try to boot into recovery it continues to bootloop. download mode is still available? any suggestions? thanks in advanced
Have you tried putting it into download mode and then using one of the one click restores via odin? If its bootlooping, your not at a total loss
Sent from my SPH-D710 using xda premium
r2hudson said:
i think i bricked my epic 4g touch. i had ics fb21 on it and i tried to restore a gingerbread rom back onto it via cwm and something went terribly wrong. i tried all the steps in qbking77s youtube video about unbricking/unrooting. my phone successfully went through the steps but when it reboots it just boot loops. when i try to boot into recovery it continues to bootloop. download mode is still available? any suggestions? thanks in advanced
Click to expand...
Click to collapse
Did you have cwm touch on it ?
Sent from my SPH-D710 using Tapatalk
rshudson---use this lick
use this link and it will restore your epic completely with roon access and than find the recovery zip/tar and you will be fixed ...the link has directions and videos
http://forum.xda-developers.com/showthread.php?t=1433101
GOOD LUCK BRO !!!!!!!!!!!
andhow said:
Have you tried putting it into download mode and then using one of the one click restores via odin? If its bootlooping, your not at a total loss
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
i tried these but they seem to get stuck right before it completes. it freezes right before the end, no reboot, no nothing
Epix4G said:
Did you have cwm touch on it ?
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
actually i did, installed it straight from rom manager. has this been a common problem?
r2hudson said:
actually i did, installed it straight from rom manager. has this been a common problem?
Click to expand...
Click to collapse
so in odin it stops at data. something ...u got A BRICK should have read what all the devs were saying and the other 10 threads that did the same as you ..... read read read ... when going from ics to gb always odin back to stock first then restore ... look in general you will find many threads about this already
http://forum.xda-developers.com/showthread.php?t=1504808
http://forum.xda-developers.com/showthread.php?t=1509795
http://forum.xda-developers.com/showthread.php?t=1509886&page=3
rocketman228 said:
use this link and it will restore your epic completely with roon access and than find the recovery zip/tar and you will be fixed ...the link has directions and videos
http://forum.xda-developers.com/showthread.php?t=1433101
GOOD LUCK BRO !!!!!!!!!!!
Click to expand...
Click to collapse
i have tried this, it just gets stuck at the data.img step, been stuck for over an hour. thanks all for your help
Epix4G said:
so in odin it stops at data. something ...u got A BRICK should have read what all the devs were saying and the other 10 threads that did the same as you ..... read read read ... when going from ics to gb always odin back to stock first then restore ... look in general you will find many threads about this already
Click to expand...
Click to collapse
wow, thought so, i guess there hasnt been a way to undo this? it only gets stuck when i use the one click odin. when i use the regular odin it completes but just bootloops. could i take this to a sprint repair center?
read links
u have a bad data partition and are bricked .... read before doing anything like this ....many people before you did this and there is no way back besides jtag ....
you can take to sprint and they may replace but who knows they may turn you away
r2hudson said:
actually i did, installed it straight from rom manager. has this been a common problem?
Click to expand...
Click to collapse
Oh man...ROM Manager and Touch recovery?... not sure if that's fixable
Sent from my Nexus S 4G using xda premium
I believe a few people have said it already. But don't use from manager to flash recoveries. Especially the touch one. You will brick your phone and can't fix it. Only a JTAG service would fix it or a replacement by sprint. Either way good luck and read up on stuff before you try it out.
Sent from my SPH-D710 using xda premium
How many bricks does this make now? I had one. Lol
Sent from my Nexus S 4G using xda premium
musclehead84 said:
How many bricks does this make now? I had one. Lol
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I swear more than 30 but who knows how many didn't post and such
Sent from my SPH-D710 using Tapatalk
OH Shix, Dang Dawg, I didn't know there was a such thing as a soft/full brick! I am lucky, I was using mobile odin and flashed the md5 check instead of the tar for fb21 modem and my phone was acting very similar but I just flashed the ONE CLICK EL29 and I was back to stock. hope if you havent tried that, you do and it works for you. I didn't like the touch cwm. but now I am deleting it from sdcard so i dont mistakenly soft/full brick my device. Keep us updated!
UPDATE
UPDATE
after using odin to unroot/unbrick my epic4gt and having still it fail to turn on passed the boot screen, i took my busted phone back to sprint on monday. told them what the problem was, "my phone wont go passed the first screen when i turn it on". they said "ok, we'll just erase everything off, should be as good as new".
i stood around waiting for about 45 minutes, i was so bored i even shamefully sent out a tweet from an iphone..smh. sales associate then came back to me saying," ive never seen anything like this, nothing will work on it, you must have rooted this phone?" my response was "i have done nothing to that phone".
with a kinda upset smirk on his face he says, "it had to be rooted buuuuut since we have no proof we will order you a phone for free, come pick it up friday."
life has been so tough w/out my epic for a whole week, happy that i get my new one on friday
You know...
I'm starting to wonder how I feel about ppl that brick their phones, through fault of their Own, then take them into sprint claiming the "update broke it!", "i never rooted that! i have No Idea what you're talking about!", and I wonder if this is going to make it harder for people with Legitimate issues to get replacements, and affect the way Sprint looks at rooting our phones in general. This Affects Their Bottom Line.
Sent from my calculator watch.
kingdazy said:
You know...
I'm starting to wonder how I feel about ppl that brick their phones, through fault of their Own, then take them into sprint claiming the "update broke it!", "i never rooted that! i have No Idea what you're talking about!", and I wonder if this is going to make it harder for people with Legitimate issues to get replacements, and affect the way Sprint looks at rooting our phones in general. This Affects Their Bottom Line.
Sent from my calculator watch.
Click to expand...
Click to collapse
I wonder this same thing....I get that people want their phone working g but on the other hand its not Sprints fault you bricked it. And then just flat out lying? Its a grey area for sure .
Sent from my SPH-D710 using XDA App
dodgerbluehero said:
I wonder this same thing....I get that people want their phone working g but on the other hand its not Sprints fault you bricked it. And then just flat out lying? Its a grey area for sure .
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Uh Oh here comes the moral police.... Not saying you are wrong but really if people can get something replaced for free, do you really think the majority would not try it... We live in a grey world.... It is what it is
Men Lie, Women Lie, Numbers Never Lies - "Jay-Z" Just felt like saying that....lol
---------- Post added at 06:49 PM ---------- Previous post was at 06:47 PM ----------
r2hudson said:
UPDATE
after using odin to unroot/unbrick my epic4gt and having still it fail to turn on passed the boot screen, i took my busted phone back to sprint on monday. told them what the problem was, "my phone wont go passed the first screen when i turn it on". they said "ok, we'll just erase everything off, should be as good as new".
i stood around waiting for about 45 minutes, i was so bored i even shamefully sent out a tweet from an iphone..smh. sales associate then came back to me saying," ive never seen anything like this, nothing will work on it, you must have rooted this phone?" my response was "i have done nothing to that phone".
with a kinda upset smirk on his face he says, "it had to be rooted buuuuut since we have no proof we will order you a phone for free, come pick it up friday."
life has been so tough w/out my epic for a whole week, happy that i get my new one on friday
Click to expand...
Click to collapse
Congrats... next time dont start a new thread about something that already had a million other threads and a Official How I Bricked my phone thread.... I KNOW YOU SAW IT.....lol
Yeah say what you want but I pay 8 dollars a month to sprint for insurance so weather its my fault or not they should replace my device which they did and I could give a **** less how it effects everything because I pay for insurance.
Sent from my SPH-D710 using XDA App
So i am finally pulling the trigger and getting the nexus. I am not new to XDA flashing ROMs or even development in general but i have learned the hard way it is better to be safe than sorry. Anyway I live in San Francisco and will be buying the GSM version from the google play store so i will just fire off my questions.
1. so this would be where i go to unlock root and flash a custom recovery http://forum.xda-developers.com/showthread.php?t=1392310 and on the list my phone would be option 7 correct ???????
2. are there any steps that i should be careful on or just take extra care???
3. Any useful tips in general i will be testing other ROMs and Kernels but will probably end up using AOKP and Franco kernel since i know him from a previous phone.
Thank you in advance and anything you think of that i didn't
dislplin01 said:
1. so this would be where i go to unlock root and flash a custom recovery http://forum.xda-developers.com/showthread.php?t=1392310 and on the list my phone would be option 7 correct ???????
Click to expand...
Click to collapse
No, use this: http://forum.xda-developers.com/showthread.php?t=1529058
2. are there any steps that i should be careful on or just take extra care???
Click to expand...
Click to collapse
Be careful with all commands.
3. Any useful tips in general i will be testing other ROMs and Kernels but will probably end up using AOKP and Franco kernel since i know him from a previous phone.
Click to expand...
Click to collapse
Do nandroid backups before flashing new ROMs so you can always go back to your previous setup.
Let me all another question is there a radio our Ril I should flash to get better data speeds any thread you suggest
Sent from my Sensation using Tapatalk 2
Use this tool kit. Easy unlocking, rooting, relocking and unrooting all in one program. http://www.wugfresh.com/dev/gnex-root-toolkit/
Sent from my Galaxy Nexus using XDA
chancy319 said:
Use this tool kit. Easy unlocking, rooting, relocking and unrooting all in one program. http://www.wugfresh.com/dev/gnex-root-toolkit/
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
No. Please don't use this. Use the link marton gave
Sent from my Galaxy Nexus
Zepius said:
No. Please don't use this. Use the link marton gave
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I was actually wondering about that program I don't like things that are to ready lol what is wrong with it
Sent from my Sensation using Tapatalk 2
dislplin01 said:
I was actually wondering about that program I don't like things that are to ready lol what is wrong with it
Sent from my Sensation using Tapatalk 2
Click to expand...
Click to collapse
Technically nothing is wrong with it, but if you have problems with the way marton posted , its easier to find out what went wrong where
Sent from my Galaxy Nexus
Zepius said:
No. Please don't use this. Use the link marton gave
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
+1 billion.
At least when you do it manually you will know what went wrong and at what step and if you need to ask for help it will be a lot easier for you to get it of you have that information.
And as a bonus you get to learn!
Learning is fun! :thumbup:
There's nothing wrong with the program. It works flawlessly but I know most people on here like to do it the manual way.
Sent from my Galaxy Nexus using XDA
The script is a horrible way to do things. It's slower than using advice and fastboot directly, unless you are a beginner in which case it still sucks because it's much better to actually take the time to learn how stuff works.... makes it easier to fix things later on.
Sent from my GNex
One Toolkit argument:
If you "break" your phone in a week/month/year/whatever...
And come back requesting help...
We're MORE than glad to help.
However, you'll find the process of diagnosis and repair to go much more smoothly when you have ADB/Fastboot set up.
Which is really 99% of the work in unlocking/rooting manually.
If you have a bricked device you're
a ) in a panic
b ) not going to be able to tell if the actual ADB/Fastboot set up isn't working...
Or if your device is broken to the point where it won't be recognized even on a working set up.
KNOWING you have ADB/Fastboot set up correctly is, again, %99 percent of fixing your phone.
If you come in and say "adb devices" doesn't show anything it could be TWO possible reasons, rather than one.
Oh...
And learning ftw.
And the fact that adb pushing items to our MTP phones is sometimes easier than using drag-n-drop.
And...you might at one point need this ability to unbrick =].
Thanks for the help guys any baseband you would recommend I'm in San Francisco just want the best coverage
Sent from my Sensation using Tapatalk 2
Jubakuba said:
One Toolkit argument:
If you "break" your phone in a week/month/year/whatever...
And come back requesting help...
We're MORE than glad to help.
However, you'll find the process of diagnosis and repair to go much more smoothly when you have ADB/Fastboot set up.
Which is really 99% of the work in unlocking/rooting manually.
If you have a bricked device you're
a ) in a panic
b ) not going to be able to tell if the actual ADB/Fastboot set up isn't working...
Or if your device is broken to the point where it won't be recognized even on a working set up.
KNOWING you have ADB/Fastboot set up correctly is, again, %99 percent of fixing your phone.
If you come in and say "adb devices" doesn't show anything it could be TWO possible reasons, rather than one.
Oh...
And learning ftw.
And the fact that adb pushing items to our MTP phones is sometimes easier than using drag-n-drop.
And...you might at one point need this ability to unbrick =].
Click to expand...
Click to collapse
Yea I'm familiar with adb and fast boot I just like to be safe and know what guide is the most up to date and reasent for the version of phone I am getting
Sent from my Sensation using Tapatalk 2
Hi all. I am pretty sure I bricked my wife's S3 when I tried to root it using the following http://forum.xda-developers.com/showthread.php?t=1746682 - has nothing to do with the tool kit, more like user error. I have rooted multiple past phones and my current note 2. I got to the odin part and it did it's thing but nevere rebooted to go to the next step. I cannot get into recovery, the computer doesn't recognize the phone now and the screen doesn't do anything. Any ideas? I am pretty sure I bricked it and will need to get a new phone for her.
Appreciate any help or confirmation of a new paper weight.
Sent from my Samsung Galaxy Note 2 via Tapatalk!
Does the device do anything at all when you try to power it on? What exact steps did you take when you attempted to root the device? If the phone does ABSOLUTELY NOTHING, not even vibrate, then your looking at a hard brick. If it does vibrate and/or you can at least get to the splash screen, then it's a soft brick and stuck in a boot loop.
Sent from my SGH-T999 using xda premium
---------- Post added at 11:20 PM ---------- Previous post was at 11:18 PM ----------
And was re-partition checked or unchecked when you tried to root with Odin?
Sent from my SGH-T999 using xda premium
LfnsR said:
Hi all. I am pretty sure I bricked my wife's S3 when I tried to root it using the following http://forum.xda-developers.com/showthread.php?t=1746682 - has nothing to do with the tool kit, more like user error. I have rooted multiple past phones and my current note 2. I got to the odin part and it did it's thing but nevere rebooted to go to the next step. I cannot get into recovery, the computer doesn't recognize the phone now and the screen doesn't do anything. Any ideas? I am pretty sure I bricked it and will need to get a new phone for her.
Appreciate any help or confirmation of a new paper weight.
Sent from my Samsung Galaxy Note 2 via Tapatalk!
Click to expand...
Click to collapse
It does sound like it is bricked. In the future, never unplug the phone while Odin is flashing it. (Im assuming this is what you did?) Always wait until it says PASS, RESET, or FAIL. Sometimes it can hang for 20 or more minutes, but it should always eventually show one of those 3 results.
Just to be sure though. Pull the battery, then put it back in. Try to boot into Download Mode. Try to boot into Recovery. If you can get one of these you are probably not bricked. If you cannot get to either one, and you cannot boot normally, then I am afraid you are bricked.
This does not mean you need to buy a new phone however. What it needs is something called a JTAG fix. You can probably find several shops online that will do this for you, but the one that always gets mentioned around here is http://mobiletechvideos.com
Sorry to hear about your misfortune, but I hope this helps you. If you do get it fixed, next time I suggest rooting with the root66 method. It is much safer imo, at least I see a lot fewer problems with it.
Good Luck!
Thanks for the info. I did get the reset and waites for just over 15 minutes. Nothing was happening and I thought it was bricked so I did unplug it. When I used the same tool to root my N2 it took less than 5 minutes for the entire process.
I will check out the link. Appreciate your help! Thank you.
Sent from my Samsung Galaxy Note 2 via Tapatalk!
Thanks for getting back. He screen doesn't come on at all, but it does vibrate once after a battery pull and then nothing. I followed the steps and got to "reset" in odin where it was waiting for the phone to reboot and after 15+ minutes I thought "crap" bricked it. Unplugged, which I would screw it up which it did. I am going to look into the company DocHoliday77 mentioned below. Worth a shot as cheaper than buying another phone.
Sent from my Samsung Galaxy Note 2 via Tapatalk!
There is this thread don't know if anyone has tried it with tmobile but should be doable in theory. http://forum.xda-developers.com/showthread.php?t=2369125
Sent from my SGH-T999 using xda premium
mt3g said:
There is this thread don't know if anyone has tried it with tmobile but should be doable in theory. http://forum.xda-developers.com/showthread.php?t=2369125
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thanks for the link. I wonder if its just the aboot.mbn on that image or if there's something else. (Ill read through the threads later to see if its mentioned). Either way if we can make a version using our aboot it should work for us too. I don't think using Sprints will work for us, but I could be wrong.
Definitely interesting though!
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Thanks for the link. I wonder if its just the aboot.mbn on that image or if there's something else. (Ill read through the threads later to see if its mentioned). Either way if we can make a version using our aboot it should work for us too. I don't think using Sprints will work for us, but I could be wrong.
Definitely interesting though!
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Agreed I just skimmed it the other week and just remembered it a couple days ago and now finally brought its attention over here. Still haven't looked at it yet fully.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Thanks for the link. I wonder if its just the aboot.mbn on that image or if there's something else. (Ill read through the threads later to see if its mentioned). Either way if we can make a version using our aboot it should work for us too. I don't think using Sprints will work for us, but I could be wrong.
Definitely interesting though!
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
mt3g said:
Agreed I just skimmed it the other week and just remembered it a couple days ago and now finally brought its attention over here. Still haven't looked at it yet fully.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Inside the 20MB.xz file (open with 7z), is an 80MB img file. Need to dd it somewhere to make any more progress.