Database Info

So did I just brick my phone?

Phone was rooted using TWRP. I locked the bootloader and now I can't boot up into anything but the page with the TAMPERED RELOCKED screen, also has bootloader, reboot, reboot bootloader, power down. Am I screwed? I just wanted to revert my rooted phone back to the original OS and it's been a freaking NIGHTMARE ):

XHaGGeNx said:
Phone was rooted using TWRP. I locked the bootloader and now I can't boot up into anything but the page with the TAMPERED RELOCKED screen, also has bootloader, reboot, reboot bootloader, power down. Am I screwed? I just wanted to revert my rooted phone back to the original OS and it's been a freaking NIGHTMARE ):
Click to expand...
Click to collapse
So you've relocked the bootloader, and then nothing else?
Run the RUU from the bootloader screen. Make sure the RUU is for YOUR phone

That's the thing, I can't get into it! I can't get into that screen where I could access stuff to INSTALL, MOUNT, etc.. it keeps taking me to the white screen with bootloader,reboot, etc.

XHaGGeNx said:
That's the thing, I can't get into it! I can't get into that screen where I could access stuff to INSTALL, MOUNT, etc.. it keeps taking me to the white screen with bootloader,reboot, etc.
Click to expand...
Click to collapse
Seeing as though you have relocked the bootloader you can either a. unlock the phone again so you can install a custom rom or b. run a ruu to get it back to stock.

Yeah because the problem is i have no OS to boot into. It just goes into recovery mode. Can you point me in the direction on how I can unlock the bootloader again?

XHaGGeNx said:
Yeah because the problem is i have no OS to boot into. It just goes into recovery mode. Can you point me in the direction on how I can unlock the bootloader again?
Click to expand...
Click to collapse
No no no. You said you wanted to go back to stock correct?
Download your stock RUU, and run from that white menu that says RE-LOCKED at the top. That's your bootloader

Ok, when you mean run from that white menu that says RELOCKED, how can I run it from that menu if I cant get into anything from this menu? Do you mean just run the RUU program from my computer and have my phone connected to the PC? I used to be able to go into that TWRP screen when i was in bootloader but now I can't.

XHaGGeNx said:
Ok, that's what I am doing already. I am downloading the RUU for my phone. Hope to gawd this will save my phone. I am just worried because it's literally stuck at this bootloader menu screen. I can't do anything else.
Click to expand...
Click to collapse
Believe me, the fact your screen is on is a sign you are not bricked. Run the RUU (Make sure it's one that is easily rootable, like the 1.85 for ATT), and go through the process of bootloader and unlock and rooting. Hope this helped

I am glad to hear that. It's almost done downloading, about 4 minutes left. I really want to thank you for helping me out here. I am such a screw up with this stuff. Sigh. anyways, I'll let you know what happens here shortly. Thank you so much once again. Really..

Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash

It's working! It's updating and everything. Phew! No offense taken, I hear ya and agree. Just being a noob at all this can put me into a lot of trouble. I have learned a lot of stuff though lol. Anyways, thank you everyone for helping me! I should be good from here

Glad to hear its working

Cheers man, good to hear everything is fixed.
If you need anything else, contact me. There are a bunch of ways to.
As for rooting again? Just read up and you'll be set.

mgutierrez87 said:
Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash
Click to expand...
Click to collapse
Hate to bump heads with ya dude but this isn't the way to be, I frown upon threads like this as well but I encourage others to root no matter who they are. Granted they do need to take the time to research what they are doing and how to get themselves out of a hole like this but someone has to help them learn
This is a community working towards a common goal, you never know maybe this dude will make his way towards development somewhere in the future. Or more likely since others helped him in his time in need he will turn around and try to do the same for someone else
Just my two cents
Sent from my HTC One XL using Tapatalk 2

mgutierrez87 said:
Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash
Click to expand...
Click to collapse
A simple "Be more careful next time because of ..." would have been just fine.

superchilpil said:
Hate to bump heads with ya dude but this isn't the way to be, I frown upon threads like this as well but I encourage others to root no matter who they are. Granted they do need to take the time to research what they are doing and how to get themselves out of a hole like this but someone has to help them learn
This is a community working towards a common goal, you never know maybe this dude will make his way towards development somewhere in the future. Or more likely since others helped him in his time in need he will turn around and try to do the same for someone else
Just my two cents
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
My apologies. We had been PMing for over an hour before this thread trying to get his phone back. I came off a little rude on that last post but he knows how hard I was trying to help him and that he can always come here for answers. Most forum guys would tell him to "search it"

please
how did you fix your phone i almost have same problem

He didn't delete ROM, recovery or anything. He relocked his bootloader. It just won't let you reboot unless you relock with a stock recovery flashed.
Sent from my One X using Tapatalk 2

http://forum.xda-developers.com/showthread.php?t=1982968
Could u guys stop by my thread and help me out?
I kinda have the same problem, and RUU tells me phone is off, error 170.
Thanks

Bricked HTC One X

Hey guys.....
I tried flashing IceColdJelly on my HTC One X ATT and i was rushing and i just remembered a notice before i rebooted the phone that it says there was no OS something something to this rom and i clicked OK and it attempted to reboot. Now its not turning on at all. Cannot get into download mode or ANYTHING. Don't tell me to try pressing any more buttons because i've been doing that for the past 3 hours. I know my way around phones and this is my biggest problem i've ever faced. I put in the phone to the computer and it recognizes it but has 3 beeps after basically cannot do anything to the phone. I have TWRP recovery on it btw. Basically, its a paperweight. Cannot turn on a single freaking thing. Please help. I cannot thank you guys enough if you can help in any way....
Thanks.

Andrew10567 said:
Hey guys.....
I tried flashing IceColdJelly on my HTC One X ATT and i was rushing and i just remembered a notice before i rebooted the phone that it says there was no OS something something to this rom and i clicked OK and it attempted to reboot. Now its not turning on at all. Cannot get into download mode or ANYTHING. Don't tell me to try pressing any more buttons because i've been doing that for the past 3 hours. I know my way around phones and this is my biggest problem i've ever faced. I put in the phone to the computer and it recognizes it but has 3 beeps after basically cannot do anything to the phone. I have TWRP recovery on it btw. Basically, its a paperweight. Cannot turn on a single freaking thing. Please help. I cannot thank you guys enough if you can help in any way....
Thanks.
Click to expand...
Click to collapse
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck

tactical kitten said:
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck
Click to expand...
Click to collapse
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....

Andrew10567 said:
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Don't panic.right now there is no solution.There will be one soon.
GOOD LUCK

Wrong section ...... And not to be a **** the but hahaha people really need to Stop and read
Sent from my Nexus 7 using Tapatalk 2

Andrew10567 said:
Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Taking the time to research before flashing a ROM that is not even meant for your phone would have saved a lot of heartache:
http://forum.xda-developers.com/showthread.php?t=1974101

I thought the ICJ Bricking Crew was no more. I guess those clowns are trying to make a comeback.

tactical kitten said:
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck
Click to expand...
Click to collapse
I have downgraded using JET from 1.14 to 2.20. Process includes bricking your phone to get into special recovery mode that give RW access to hboot, but you do need TWRP at some point I think (not sure though) to get in bricked, before you start downgrade, so you might not be able to downgrade.
However, I don't think you are SOL. Look into manual steps of downgrading here: http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107
OP gives you there way to verify that device is connected and part of the steps is listing partitions. If you can get partitions listed on your PC, then I think you can just dd system image and it should come back to life... also have you tried 2.20 RUU? I had a corrupted system partition (bad sector causing reboot when I would try to access system - including booting phone or into twrp recovery). I ended up using RUU (which also failed from the same bug, but It actually reformatted my system partition giving me access to twrp and then I was able to restore).

http://www.youtube.com/watch?v=wwleOote5M0&feature=youtube_gdata_player
Sent from my HTC One XL using Tapatalk 2

Andrew10567 said:
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Lol. wow kid.
Sent from my HTC One XL

rpomponio said:
http://www.youtube.com/watch?v=wwleOote5M0&feature=youtube_gdata_player
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
It hurts to laugh so hard.

igagnidz said:
However, I don't think you are SOL. Look into manual steps of downgrading here: http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107
Click to expand...
Click to collapse
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.

iElvis said:
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.
Click to expand...
Click to collapse
If there is no ROM loaded onto the phone, as in doing a full /system wipe, the asserts will not work.
The assert that's being flashed looks at the build.prop that's already loaded onto the phone.
Sent from my One X using xda premium

Myrder said:
If there is no ROM loaded onto the phone, as in doing a full /system wipe, the asserts will not work.
The assert that's being flashed looks at the build.prop that's already loaded onto the phone.
Click to expand...
Click to collapse
And of course, it's good practice to wipe /system when changing roms. I didn't think of that. That's obviously why people are still getting in trouble.

iElvis said:
And of course, it's good practice to wipe /system when changing roms. I didn't think of that. That's obviously why people are still getting in trouble.
Click to expand...
Click to collapse
I don't ever wipe /system when flashing ROMs. It gets wiped when you flash anyway. I always wipe user data (factor reset), Dalvik and cache. But that's it.

iElvis said:
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.
Click to expand...
Click to collapse
Yep, if you format /system, the build.prop is gone, and the assert looks to the build.prop.. why it flashes, I don't know.
The way its set up seems like it would only flash if "ro.device=endeavoru" or whatever the line is, is present. I guess there is no fail safe to stop the process if the build.prop isn't present

Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.

Andrew10567 said:
Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.
Click to expand...
Click to collapse
They do and you're not the first to ask. I think they just swap up the motherboard.

Andrew10567 said:
Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.
Click to expand...
Click to collapse
They can fix any software corruption they have the tools too they know their phones front to back and can rewrite anything to them...just tell them what happened and they'll tell you the cost( maybe they'll feel bad and give a nice price) honesty can get you in good places sometimes

Thanks. Will send everyone who replied a thank button. Regardless of what type of comment...... I'll need to check the cost. Hopefully its below 100....

[Q] Hard Bricked? Don't see how....

Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan

ryan9316 said:
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
Click to expand...
Click to collapse
You could take your phone back and tell them it won't boot etc.
If you can't get it to boot neither can they, so no-one will know it's been unlocked/rooted.
Some people will say this is fraudulent, but hey, if you can live with yourself who cares what anyone else thinks?

Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app

exad said:
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I saw this and will give it a try, thank you for the advice!

ryan9316 said:
I saw this and will give it a try, thank you for the advice!
Click to expand...
Click to collapse
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.

mkalbarc said:
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
Click to expand...
Click to collapse
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.

ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
If the emmc controller isn't responding, it's worth even less than that.
Sent from my One X using xda app-developers app

ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...

mkalbarc said:
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
Click to expand...
Click to collapse
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.

pside15 said:
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
Click to expand...
Click to collapse
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. the rom that I had flashed was the latest cleanrom. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.

mkalbarc said:
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
Click to expand...
Click to collapse
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.

pside15 said:
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
Click to expand...
Click to collapse
Funny thing about the One... I was thinking about getting it but after this issue I will never look at another phone that doesn't have a removable sd card...

I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app

3 words: Dropbox Camera Upload.

exad said:
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Very well said... I always get a little nervous when screwing with a new $500+ device.
Sent from my HTC One X using xda app-developers app

iElvis said:
3 words: Dropbox Camera Upload.
Click to expand...
Click to collapse
Thank you for the advice! I will remember that with my next phone.

I just use g+ to instantly upload my photos. Unlimited space is hard to argue with
Sent from my One X using xda app-developers app

phone not able to boot
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off

anuj.sherawat said:
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
Click to expand...
Click to collapse
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app

31ken31 said:
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
thanks first of all I was on CMW, formatted the drive as computer prompted, lost the data but was able to flash the ROM and fastboot the boot image to phone.
Now only one problem the phone restarts and then goes to boot loop everytime I have to fastboot the boot image file.
DO I need to change the recovery and is there any way to by pass the fastboot process? Sorry for noob question

Bought used N5- No mobile network whatsoever!

So i bought me a new used nexus 5 on craigslist from some old chinese guy. He said it wasn't connecting to a network no matter what or whose sim cards he used and how many times he rooted it. the phone is on stock unrooted 4.4.2. I got it on the cheap and was hoping ot fix it up and use it. Any idea what might be wrong with it?

butthurtlocker said:
So i bought me a new used nexus 5 on craigslist from some old chinese guy. He said it wasn't connecting to a network no matter what or whose sim cards he used and how many times he rooted it. the phone is on stock unrooted 4.4.2. I got it on the cheap and was hoping ot fix it up and use it. Any idea what might be wrong with it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2601997

Sounds like the old Chinese guy knew what he was doing.

You don't mention that YOU returned it to stock, you just said it was stock and unrooted. If it is exactly the way he gave it to you I would fastboot flash the stock 4.4.2 images from google and see what that does for you. You could simply have a corrupted file somewhere.

thionylx said:
You don't mention that YOU returned it to stock, you just said it was stock and unrooted. If it is exactly the way he gave it to you I would fastboot flash the stock 4.4.2 images from google and see what that does for you. You could simply have a corrupted file somewhere.
Click to expand...
Click to collapse
Yes when he sold it to me it was stock. I haven't returned it to stock, ive rooted it and tried diff rom/basebad combos and still nothing. Theres also a weird persistent notification that i cant swipe away that says Nework (ROGERS) Unvailable....even when i reset and try a Telus sim! Is there an easier way to flash stock besides fastboot? I am pretty new to this gig and am not too comfortable with fastboot

butthurtlocker said:
Yes when he sold it to me it was stock. I haven't returned it to stock, ive rooted it and tried diff rom/basebad combos and still nothing. Theres also a weird persistent notification that i cant swipe away that says Nework (ROGERS) Unvailable....even when i reset and try a Telus sim! Is there an easier way to flash stock besides fastboot? I am pretty new to this gig and am not too comfortable with fastboot
Click to expand...
Click to collapse
This being a Nexus you have little or no risk of doing damage by playing around. My original Droid X was always threatening to self destruct if you messed up the tiniest little step. Spending a couple hours learning about and installing Fastboot and ADB will be the best investment you can make. Once you learn to use them the fear of messing something up is gone. You can flash roms at will without worry as you can always return to stock and start over.

Flash a Google stock image
Sent from my Nexus 5 using Tapatalk
---------- Post added at 08:15 PM ---------- Previous post was at 08:14 PM ----------
All nexus 5 regardless of carrier should be unlocked
Sent from my Nexus 5 using Tapatalk

butthurtlocker said:
Yes when he sold it to me it was stock. I haven't returned it to stock, ive rooted it and tried diff rom/basebad combos and still nothing. Theres also a weird persistent notification that i cant swipe away that says Nework (ROGERS) Unvailable....even when i reset and try a Telus sim! Is there an easier way to flash stock besides fastboot? I am pretty new to this gig and am not too comfortable with fastboot
Click to expand...
Click to collapse
Just follow method one of this. It's easy http://forum.xda-developers.com/showthread.php?p=47156064
PS, why did you buy a device thinking you could fix it of you don't know fastboot commands

thionylx said:
This being a Nexus you have little or no risk of doing damage by playing around. My original Droid X was always threatening to self destruct if you messed up the tiniest little step. Spending a couple hours learning about and installing Fastboot and ADB will be the best investment you can make. Once you learn to use them the fear of messing something up is gone. You can flash roms at will without worry as you can always return to stock and start over.
Click to expand...
Click to collapse
Thanks man thats a good point!

jd1639 said:
Just follow method one of this. It's easy http://forum.xda-developers.com/showthread.php?p=47156064
PS, why did you buy a device thinking you could fix it of you don't know fastboot commands
Click to expand...
Click to collapse
Oh thats perfect bro thanks, nice and straightforward. Will see how this goes after school. I just htought it was maybe a radio issue or rom issue so i thought i could flash around and fix it. Also it was only 70 bucks and in mint condition aside from this problem so I didn't think it was a bad deal

Sounds like the ESN/IMEI is bad.
Hard to fix ATM.
Sent from my Nexus 5 using Tapatalk

Dragn4rce said:
Sounds like the ESN/IMEI is bad.
Hard to fix ATM.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oh really?how does that happen!? The imei isn't blacklisted or anything and shows up as a registered imei. I tried flashing stock image and still no dice! Looks like I'm doomed. Any other suggestions?

That usually happens when the following steps occur.
The original owner unlocked bootloader.
They put twrp on it and did a full backup including ESN
The device developed a fault so they RMA'd it.
They restored the backup from the faulty device into the new one.
The ESN is device specific and by restoring it onto a different device you end up with not being able to connect to a network.
You can check by going into the about phone menu in the settings. If it displays your imei then I don't think this is your problem.
Have you tried popping the back cover off and checking the antennae contacts
Sent from my Nexus 4 using xda app-developers app

The good news is the parts are worth more than the $70 you paid for it. Find someone with a busted screen and sell it.

jd1639 said:
The good news is the parts are worth more than the $70 you paid for it. Find someone with a busted screen and sell it.
Click to expand...
Click to collapse
That's a good idea.

Thanks for the advice. Ended up selling it this morning as is to an eager repair junkie. Btw my imei was showing up and the antennas were all in place so still a mystery what was up with it!
Sent from my LG-G2 using xda app-developers app

[Q] Bootloader error / Soft brick

So as Im sure everyone already knows I done messed up. I literally had the tablet(asus tf700) for less than a day. Im not very linux savvy but i know enough about electronics that i can usually get by, well not this time. I had rooted and unlocked my device, downloaded cm 11 that was to be installed via twrp recovery. Everything went gravy and then i had a loop problem with cyanogenmod, im guessing i didnt have the correct bootloader to use cm 11 in the first place. So i tried to just go back to stock only to find out that my backups had been corrupted and the names of the files were there but nothing on them. So I looked around for a bit and tried to figure out how to just flash a new rom in there, low and behold my pc laptop stopped working leaving me with only a mac to use right now. The pc will turn on and work for a bit but there is a fan out so it overheats very quickly. So i tried to use the nexus toolkit to possibly go back to stock via the nexus 10 or nexus 7 options they have. Needless to say this was very stupid and now instead of being in a bootloop with cyanogenmod I am stuck looking at the asus letters when it starts up, it doesnt even bootloop it just stays there and to top it off i now have a bootloader error 0x00000000 and i cant do anything other than the sync looking thing hich i am assuming is fast boot. I can plug it in and the computer shows the device as fastboot but just dont know what to try anymore. I have read the buster post and i know this is kind of a repost but i just dont understand the linux portion of his response. Im guessing my tablet still has a fighting chance but im just devastated at this point to have lost its use within a day of having it. Ive really learned a lot by this happening so i dont beieve i will make these mistakes again but can someone please help me get this beauty back to her prime " pun intended ".

Try writing in smaller paragraphs - that is really hard to read
From what I can tell you appear to have flashed something form a nexus into your bootloader partition?
If so I think you can say goodbye to the device unless you previously did the flatline nvflash backups to make it unbrickable?
ah wait! you said you have fastboot? Can you fastboot devices from a cmd prompt and get a device id back?

NobleXperiment said:
So as Im sure everyone already knows I done messed up. I literally had the tablet(asus tf700) for less than a day. Im not very linux savvy but i know enough about electronics that i can usually get by, well not this time. I had rooted and unlocked my device, downloaded cm 11 that was to be installed via twrp recovery. Everything went gravy and then i had a loop problem with cyanogenmod, im guessing i didnt have the correct bootloader to use cm 11 in the first place. So i tried to just go back to stock only to find out that my backups had been corrupted and the names of the files were there but nothing on them. So I looked around for a bit and tried to figure out how to just flash a new rom in there, low and behold my pc laptop stopped working leaving me with only a mac to use right now. The pc will turn on and work for a bit but there is a fan out so it overheats very quickly. So i tried to use the nexus toolkit to possibly go back to stock via the nexus 10 or nexus 7 options they have. Needless to say this was very stupid and now instead of being in a bootloop with cyanogenmod I am stuck looking at the asus letters when it starts up, it doesnt even bootloop it just stays there and to top it off i now have a bootloader error 0x00000000 and i cant do anything other than the sync looking thing hich i am assuming is fast boot. I can plug it in and the computer shows the device as fastboot but just dont know what to try anymore. I have read the buster post and i know this is kind of a repost but i just dont understand the linux portion of his response. Im guessing my tablet still has a fighting chance but im just devastated at this point to have lost its use within a day of having it. Ive really learned a lot by this happening so i dont beieve i will make these mistakes again but can someone please help me get this beauty back to her prime " pun intended ".
Click to expand...
Click to collapse
Wow, you beat me on the unlock your new device within one day of usage...
You can see the post above to see if you still can use your fastboot. If your fastboot is still working, you can download the full latest firmware from Asus website and install it with fastboot command...good luck....:fingers-crossed:

Yeah sorry bout the length, i know a lot of times everyone asks for more details so i figured id get that out of the way, honestly didnt even know if i would get a response so much appreciated, i will be home shortly to try the download, def a huge failblog learning experience at best. when you do that what exactly is the point of making two blops. ?

To be honest with all the amazing kits that have come out of this forum Im quite baffled there is not one to reestablish things like the nexus toolkit. With my computer overheating i basically only have time to install a kit and run it before it stops working, so hopefully i have enough time to cmd prompt, but thats really the stuff i dont get. Is it possible to go into a little depth as far as the command prompts?the busters solution would be an easy guide to work from i would imagine.

NobleXperiment said:
To be honest with all the amazing kits that have come out of this forum Im quite baffled there is not one to reestablish things like the nexus toolkit. With my computer overheating i basically only have time to install a kit and run it before it stops working, so hopefully i have enough time to cmd prompt, but thats really the stuff i dont get. Is it possible to go into a little depth as far as the command prompts?the busters solution would be an easy guide to work from i would imagine.
Click to expand...
Click to collapse
Yes the are a number of tool kits in the dev forum But unlocking and setting up recovery and the bootloader on the asus transformer is different to the nexus devices so you can't have such a simple route I'm afraid.

sbdags said:
Yes the are a number of tool kits in the dev forum But unlocking and setting up recovery and the bootloader on the asus transformer is different to the nexus devices so you can't have such a simple route I'm afraid.
Click to expand...
Click to collapse
Would I be able to us nvflash to install custom bootloader and then progress towards installing new rom? or does tht not really have anything to do with my situation? the asus website isnt working for me either so I cant download the proper firmware.

NobleXperiment said:
Would I be able to us nvflash to install custom bootloader and then progress towards installing new rom? or does tht not really have anything to do with my situation? the asus website isnt working for me either so I cant download the proper firmware.
Click to expand...
Click to collapse
Your tablet is very close to becoming a paper weight - not the ideal situation to generate your nvflash blobs.
First step should be to get a working fastbooot connection. Either fix the PC or get fastboot set up on your Mac. http://forum.xda-developers.com/showthread.php?t=1917237
A half-dead tablet and non-working PC is just a little more challenge than you need right now.
Without fastboot you cannot fix this. So get that set up and we can help more.
Sent from my K00C using Tapatalk

berndblb said:
Your tablet is very close to becoming a paper weight - not the ideal situation to generate your nvflash blobs.
First step should be to get a working fastbooot connection. Either fix the PC or get fastboot set up on your Mac. http://forum.xda-developers.com/showthread.php?t=1917237
A half-dead tablet and non-working PC is just a little more challenge than you need right now.
Without fastboot you cannot fix this. So get that set up and we can help more.
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
I got fast boot setup on the Mac and it did show that it connected but I can't download the asus firmware on my Mac for some reason?

NobleXperiment said:
I got fast boot setup on the Mac and it did show that it connected but I can't download the asus firmware on my Mac for some reason?
Click to expand...
Click to collapse
You tried all the links? I use Global and it works.
Which SKU are you? I think I have the US .10 firmware lying around somewhere - can upload it to Dropbox.
Sent from my K00C using Tapatalk

Thank you for the firmware offer but I went thru and fixed my pc and then got everything working with busters mothod:victory: I had to try it about 3 times and use my eSATA usb for some reason but i actually ended up going from stock 4.1.1 to 4.2.1 so all in all great success. honestly baffled that i pulled this off.

NobleXperiment said:
Thank you for the firmware offer but I went thru and fixed my pc and then got everything working with busters mothod:victory: I had to try it about 3 times and use my eSATA usb for some reason but i actually ended up going from stock 4.1.1 to 4.2.1 so all in all great success. honestly baffled that i pulled this off.
Click to expand...
Click to collapse
:Good:
Now generating your NVflash blobs will be a breeze
Sent from my K00C using Tapatalk

berndblb said:
:Good:
Now generating your NVflash blobs will be a breeze
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Should i go the route of NVflash now? I only mentioned it because I saw you could download blob files but does it really make you device unbrickable? Is this something i should go for or just be happy i fixed the tablet?

NobleXperiment said:
Should i go the route of NVflash now? I only mentioned it because I saw you could download blob files but does it really make you device unbrickable? Is this something i should go for or just be happy i fixed the tablet?
Click to expand...
Click to collapse
It makes it unbrickable. You can recover from any brick with the nvflash blob files.

NobleXperiment said:
Should i go the route of NVflash now? I only mentioned it because I saw you could download blob files but does it really make you device unbrickable? Is this something i should go for or just be happy i fixed the tablet?
Click to expand...
Click to collapse
Entirely up to you. You were a half-step away from hard bricking your tablet. If this is a typical pattern for you (try first - ask/read later) it may be a very good idea to get those blobs squared away
You have to flash a modded bootloader and modded recovery just for generating the blobs (and flash back afterwards), so it may be a good idea to get this done before you get everything set up.
Sent from my K00C using Tapatalk

With all of this being a first to me I certainly underestimated how easy it is to brick a device, but I did manage to fix it which seems much harder to do so i would have to think i can get the nvflash done. Appreciate the support here and everything people do within the forums, if somebody could direct me to an approved guide that would be quite nice, im assuming its very similar to what i just went through?

NobleXperiment said:
With all of this being a first to me I certainly underestimated how easy it is to brick a device, but I did manage to fix it which seems much harder to do so i would have to think i can get the nvflash done. Appreciate the support here and everything people do within the forums, if somebody could direct me to an approved guide that would be quite nice, im assuming its very similar to what i just went through?
Click to expand...
Click to collapse
Follow these instructions to the letter.
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
I anything is unclear, ask in this thread:
http://forum.xda-developers.com/showthread.php?t=1901479
Sent from my K00C using Tapatalk

So yeah while i thought the upgrade to 4.2.1 was a lucky mistake but now i cant use kingo to root my phone, any suggestions without having to go back to an earlier firmware?

or would getting the nvflash unroot the device again anyway?