Database Info

Anyway to gain temproot for now?

Hey,
I was wondering, is there anyway to gain temproot until we have full root? Am I right in thinking that temproot allows programs requiring root access to work e.g. AdFree?
Thanks
Sent from my HTC Sensation Z710e using XDA Premium App

There's an app called gingerbreak which works on the S E Arc (it roots anything on Gingerbread) so I wonder if it will work on the Sensation?
I'm waiting to get mine at the moment...
Hopefully tuesday

Hi !
I've fund this, but can't try, the sensation is not yet available in France
http www zenilshroff.com/ how-to-root-htc-sensation-android-2-3-gingerbread-smartphone/
(sorry, I can't post URL, i'm new on this forum)
-------------
HTC P3600 WM6.1
HTC HD2 WM7+Android 2.2

Roccoswell said:
Hi !
I've fund this, but can't try, the sensation is not yet available in France
http www zenilshroff.com/ how-to-root-htc-sensation-android-2-3-gingerbread-smartphone/
(sorry, I can't post URL, i'm new on this forum)
-------------
HTC P3600 WM6.1
HTC HD2 WM7+Android 2.2
Click to expand...
Click to collapse
Is that saying you need to remove HTC Sync from the device, and then run Gingerbreak?
Sent from my HTC Sensation Z710e using XDA Premium App

credits to this guide: http://www.zenilshroff.com/how-to-root-htc-sensation-android-2-3-gingerbread-smartphone/
1. First download the Gingerbreak.apk file.
2. Save on your computers desktop.
3. Connect the phone to your computer. (do not connect using htc sync)
4. Mount SD card as flash drive as you generally do for USB cable file transfers.
5. Copy the downloaded Gingerbread apk file to SD card root.
6. You should have any File Manager (e.g., Astro File Manager) on your phone. If not, download from Market. These are generally free apps.
7. Disconnect your phone from computer and launch File Manager. You will find in the menu of the phone.
8. Follow the onscreen instructions on File Manager to install APK to your phone from SD card root. You may also use the default application installer software to do this.
9. After installation completes, open the APK.
10. Press ‘root’ button. Simple, isn’t it?
11. The APK exploit will run for some time. Usually it runs for around 10 minutes. Your phone will be rebooted. In case it takes more than ten minutes for auto reboot, please reboot it yourself. Not to panic, this happens a lot of times.
12. Your device is now rooted. Congrats!
13. Make sure that SuperUser app is installed and is running. This is very important for you to enjoy the benefits of rooting.
In order to test if your phone has been successfully rooted, just click a screenshot of your phone. That should show that your phone has been rooted.

Yeah, but does it REALLY work?
Sent from my HTC Sensation using XDA Premium App

Gingerbreak exploit is patched on the SGS II so doubt that will work. Also if phone needs to reboot, no way will root persist due to signed locked bootloader. Go ahead and try but we will need some L33t devs to break this phone.
Sent from my HTC Hero using XDA App

drspikes said:
Gingerbreak exploit is patched on the SGS II so doubt that will work. Also if phone needs to reboot, no way will root persist due to signed locked bootloader. Go ahead and try but we will need some L33t devs to break this phone.
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
Yeah, I'm not really willing to believe it works either mate.
If the guide has some proof (i.e. a bootloader photo) then I will try it. If not, it's all just based on theory, but nothing practical.

Somebody has to be the guinea pig.

Darnell_Chat_TN said:
Somebody has to be the guinea pig.
Click to expand...
Click to collapse
Well, I have tried it, doesn't seem to do a thing so far.
It does say it fails a lot, but still, zero proof that is works, I'm very suspicious that it's all ********

It would be great if we could get this partial root. I personally don't mind not being able to flash custom ROM, but it is very important to me to be able to use some apps that require root permissions like adfree or titanium backup. From what I understand, this 'half-root' should not be very difficult to achieve cause it is not needed to mess with the bootloader for this purpose. The only requirement is to be able to uninstall htc sync for some time.
Here also a link detailing the differences between root levels and clarifying vocabulary. I am posting this cause it has been very useful for me to help understand, so it might also serves others..
http://androidforums.com/evo-3d-all-things-root/329819-no-need-panic-about-locked-bootloader.html

madindehead said:
Well, I have tried it, doesn't seem to do a thing so far.
It does say it fails a lot, but still, zero proof that is works, I'm very suspicious that it's all ********
Click to expand...
Click to collapse
Thank you for trying it. I think you should now do a full factory reset, to totally get that thing off your Sensation. It does not do what it's supposed to do and who knows what it might be doing behind the scenes. Yea, be very suspicious!

Darnell_Chat_TN said:
Thank you for trying it. I think you should now do a full factory reset, to totally get that thing off your Sensation. It does not do what it's supposed to do and who knows what it might be doing behind the scenes. Yea, be very suspicious!
Click to expand...
Click to collapse
Yeah, doing a full reset was in the back of my mind. Think I will go do that now
I'm not optimistic thought. They who owns the website emailed me (I posted a comment doubting it, and it was deleted, so I reposted, and he emailed me), to say the guy who posted it hadn't got back to him, so he was removing it from the site until he had confirmation that it did work. I am still VERY sceptical of it. He said, uninstall HTC Sync from the PC, as that causes problems with root? VERY random thing IMHO.

madindehead said:
Yeah, doing a full reset was in the back of my mind. Think I will go do that now
I'm not optimistic thought. They who owns the website emailed me (I posted a comment doubting it, and it was deleted, so I reposted, and he emailed me), to say the guy who posted it hadn't got back to him, so he was removing it from the site until he had confirmation that it did work. I am still VERY sceptical of it. He said, uninstall HTC Sync from the PC, as that causes problems with root? VERY random thing IMHO.
Click to expand...
Click to collapse
Well, a factory reset and trying to run GingerBreak right after hasn't done a thing. It says to reboot after it doesn't succeed after 10 mins, and that this happens a lot. But EVERY attempt I have been rebooting after 10 mins.
If the guy who "discovered" it can't even post proof, it sounds like a load of ****.

madindehead said:
Well, a factory reset and trying to run GingerBreak right after hasn't done a thing. It says to reboot after it doesn't succeed after 10 mins, and that this happens a lot. But EVERY attempt I have been rebooting after 10 mins.
If the guy who "discovered" it can't even post proof, it sounds like a load of ****.
Click to expand...
Click to collapse
Yea, if they discovered it they can prove their claim with a simple photo.
This speaks to not only the lack of credibility of the person who posted it, but also to the site that allowed it to be posted and remain till the complaints came in. A very untrustworthy source is how I view them because of this.

Gingerbreak won't help you, as there will be a nand lock, and the fact the kernel will be patched...

pulser_g2 said:
Gingerbreak won't help you, as there will be a nand lock, and the fact the kernel will be patched...
Click to expand...
Click to collapse
Yeah, I didn't think it would work to be honest. That really as wishful thinking. The person who posted that seems like a proper idiot

this will work once we get s-off to perminate root and then you can flash the recovery from fastboot or rom manager

xboarder56 said:
this will work once we get s-off to perminate root and then you can flash the recovery from fastboot or rom manager
Click to expand...
Click to collapse
Given your confidence, we'll let you test it first.

Darnell_Chat_TN said:
Given your confidence, we'll let you test it first.
Click to expand...
Click to collapse
Gingerbreak won't help you, as there will be a nand lock, and the fact the kernel will be patched...
Click to expand...
Click to collapse
Even the website states we need s-off so when that is achieved it will work and i will test it once we find a crack for the radio to get s-off/nand lock.

Completely new to Android OS and need some tips

I am brand new to the Android OS and I heard from some friends that rooting is very similar to "jailbreaking" on the iPhone in the sense that you gain a lot of extra features and are able to sideload apps, etc.
I have a few questions before I do my root. Also, I do not want to install Android 2.3 or any other OS on my phone. I want to keep the stock OS, except I want my phone to be rooted (if that works). The guide my friends showed me was this: http://forum.xda-developers.com/showthread.php?t=952352
1. If I root my phone and then install an HTC or AT&T update, does my root go away (HTC Inspire 4G locked to AT&T).
2. Can I remove the AT&T lock so I can use my phone in Europe if I root?
3. I don't want to brick my phone, so is there anyway to back it up beforehand?
Thanks for the help!

1. It won't let you update so your good.
2. Yes you can it unlocks the phone.
3. Yes its called a Nandroid
Sent from my Inspire 4G using XDA Premium App

XAviierG said:
1. It won't let you update so your good.
2. Yes you can it unlocks the phone.
3. Yes its called a Nandroid
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
Also, is the thread I posted the best method for rooting as of right now, or is there a better one?

ComradeNF said:
Also, is the thread I posted the best method for rooting as of right now, or is there a better one?
Click to expand...
Click to collapse
That's how I rooted mines. Very simple
Sent from my Inspire 4G using XDA Premium App

Just remember backups are your friends
Sent from my Inspire 4G using XDA Premium App

ThEiiNoCeNT said:
Just remember backups are your friends
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
+1! I learned this the hard way haha.....I went flash crazy once with mods, and one of them went wrong. I hadn't made a backup in almost a week, so I had a lot of work to do to get everything back the way I like it. Now, I religiously do a backup before doing any mod, everytime . Time consuming, yes, but it'll save you A LOT of time if something goes wrong.

yep very true a back up just saved my butt yesterday

Back up is a must..

I hate when I get bricked without a backup....I have to reinstall the rom and set up everything again..
Sent from my HTC Desire HD using XDA Premium App

words can't explain how many times I've been saved with my backup when messng with different flashes, haha. Very important.
Sent from my Desire HD using XDA Premium App

1- rooting is the hardest /most dangerous part(not that its dangerous, but its more dangerous than flashing a rom/kernel simply cause your flashing a radio). Flashing a rom is simple/safe. After you root don't not flash a rom cause you think its dangerous or you'll brick your phone-you wont.
2- I haven't made a nandroid backup ever. If you soft brick your phone, knowing adb is way more important than a backup. I've bricked my phone probably more than everybody in this thread x50, adb saves me everytime. Even if the computer wont see your phone when it boots, 99.9% of the time it will see it when in recovery, so this is what will really save you. Reboot the phone to recovery, use adb to fix whatever broke from the mod/whatever you just did.
(I'm not saying don't make backups, I'm saying learn adb - it can more likely save your ass than anything. Learn it)

di11igaf said:
1- rooting is the hardest /most dangerous part(not that its dangerous, but its more dangerous than flashing a rom/radio simply cause your flashing a radio). Flashing a rom is simple/safe. After you root don't not flash a rom cause you think its dangerous or you'll brick your phone-you wont.
2- I haven't made a nandroid backup ever. If you soft brick your phone, knowing adb is way more important than a backup. I've bricked my phone probably more than everybody in this thread x50, adb saves me everytime. Even if the computer wont see your phone when it boots, 99.9% of the time it will see it when in recovery, so this is what will really save you. Reboot the phone to recovery, use adb to fix whatever broke from the mod/whatever you just did.
(I'm not saying don't make backups, I'm saying learn adb - it can more likely save your ass than anything. Learn it)
Click to expand...
Click to collapse
Good advice....I need to take the time to do that.....
Sent from my Inspire 4G

[Tool] Nvflash unbricking released!

Hi,
As most of you probably already know by now, I have released a fully functional nvflash for Transformer yesterday
More information is available at http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
UPDATE 15-06-2011:Bumble-Bee (Apache14) is just as much to thank for this as me! Both of us (from AndroidRoot.Mobi) have worked hard on making this happen! Thanks to Roach for providing the nvflash-ready Prime 1.4 ROM!
UPDATE: The Prime 1.4 linked is European (WW) build! Roach will release 1.5 soon probably and there'll be both WW and US available. I'm planning to write a quick guide on how to root when running stock 3.1 already (it's pretty easy!)! E.g. to stay on full stock and *just* have root
Windows nvflash
Linux nvflash
Quick guide to unbricking:
Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
(Windows only) Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip
Run download.sh (linux) or download.bat (windows)
???
Profit

Awesome! Thanks a lot!!

rayman84 said:
Hi,
As most of you probably already know by now, I have released a fully functional nvflash for Transformer yesterday
More information is available at http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
Windows nvflash
Linux nvflash
Quick guide to unbricking:
Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
(Windows only) Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip
Run download.sh (linux) or download.bat (windows)
???
Profit
Click to expand...
Click to collapse
WOW, It's "just like that"? Really that's all what you have to do to unbrick a device? I guess times when flashing roms was dangerous have passed
Great job

Very thanks and keep up the good work!!!

unbrick tool came before root tool. lol
but it's a very useful program for all of us.
thanks for this!
i have a question though, my Samsung Vibrant was HARDWARE LOCKED, which makes button combinations to enter recovery/download modes impossible.
Is there any possibility that my TF has a hardware lock too which will prevent me from accessing the USB when it gets bricked?
i have experience in rooting and/or jailbreaking but i havent rooted my TF yet, coz the only way to root right now is kind of "not layman friendly". and i hate the terms BLOBS. lol
thank you.

So I'm rooted running prime 1.4 could some one explain in laymans terms what difference this makes to me and what if anything I need to do to benefit to my TF
DESIRE HD using leedroid. ASUS TRANSFORMER using prime

atlaswingpasaway said:
unbrick tool came before root tool. lol
but it's a very useful program for all of us.
thanks for this!
i have a question though, my Samsung Vibrant was HARDWARE LOCKED, which makes button combinations to enter recovery/download modes impossible.
Is there any possibility that my TF has a hardware lock too which will prevent me from accessing the USB when it gets bricked?
i have experience in rooting and/or jailbreaking but i havent rooted my TF yet, coz the only way to root right now is kind of "not layman friendly". and i hate the terms BLOBS. lol
thank you.
Click to expand...
Click to collapse
Either you didn't read the post or you might be dyslexic. If you unbrick your device you're pushing a custom ROM which means you automatically get root.

combat goofwing said:
So I'm rooted running prime 1.4 could some one explain in laymans terms what difference this makes to me and what if anything I need to do to benefit to my TF
DESIRE HD using leedroid. ASUS TRANSFORMER using prime
Click to expand...
Click to collapse
You don't need this your already rooted. This is a easy way to root and it can also revive bricks, custom flash different partitions and who knows what other functions can be done with nvflash.
Sent from my HTC Vision using XDA Premium App

Will this wipe your data partition if using this to get a rooted custom rom on?

seshmaru said:
Either you didn't read the post or you might be dyslexic. If you unbrick your device you're pushing a custom ROM which means you automatically get root.
Click to expand...
Click to collapse
it might be both! lol sorry my bad.
im new to tablet/honeycomb rooting so i dont know much about this.
so... im on stock 3.1 right now (i guess the build number wont matter anymore?)
and no root. should i just follow the OP instructions or what?

Canadoc said:
Will this wipe your data partition if using this to get a rooted custom rom on?
Click to expand...
Click to collapse
Using the script included it will wipe all user data. But it may be tweaked later.
Sent from my HTC Vision using XDA Premium App

atlaswingpasaway said:
it might be both! lol sorry my bad.
im new to tablet/honeycomb rooting so i dont know much about this.
so... im on stock 3.1 right now (i guess the build number wont matter anymore?)
and no root. should i just follow the OP instructions or what?
Click to expand...
Click to collapse
Yes if u want a custom rom with root. No more downgrading firmwares anymore like before

Cannot mount SD card in clockwork mod?
EDIT: Nevermind. I tried a different microsd card and it worked fine. False alarm... Move along... nothing to see here
I used the NVFlash utility to flash Prime 1.4 without a hitch but now that I'm trying to deploy the overclock kernel clockwork mod is not playing nice. I get an error E: Can't mount /sdcard when trying to choose a zip file. My understanding is that /sdcard is not the microsd anyway. How do I resolve this? I already tried reformatting the microsd card on my pc but that didn't solve the issue.
Thanks!
-Matt

I thought /Removable/sdcard/ was the sdcard.
Sent from my HTC Vision using XDA Premium App

david279 said:
I thought /Removable/sdcard/ was the sdcard.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
/Removable/MicroSD/ is the MicroSD card slot on the TF104
/SDCard is the 30gigs on the 32gb NAND

Also check the CWM installed. If it's the old one it erases your sd card and internal card on data wipes. You don't want that.
Sent from my HTC Vision using XDA Premium App

david279 said:
I thought /Removable/sdcard/ was the sdcard.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
It's /Removable/MicroSD
But I think the key thing here is that /sdcard is whatever the booting process mounts as /sdcard. This is why CWM has no problem listing the zip files for ROMs, etc. as being from the sdcard. It has accessed it through the actual block device which doesn't change. The whole internal sdcard that we see is some trickery that allows us to have access to all the space on our internal memory, but CWM doesn't know or care about that.
Sent from my Transformer TF101 using XDA Premium App

So...
No rooting, and no CWM..
Just use the tools and profit?

It flashes CWM for future flashing fun.
Sent from my HTC Vision using XDA Premium App

i just dont seem to get it.. . so does this give my stock 3.1 root?

[Solved] Stuck In Custom ROM, Odin and CWM Recovery no go's

Alright, I'm hoping I can get some quick useful feedback on this. I'm currently on AOKP Official Milestone 6, and every time I reboot it reverts me settings I had on August 28th. I've been going thru this all day long, Google searching, scanning forums for our device and the T989.
I've attempted Odin flashes 13 times today to go back to Stock Gb and Stock Ics, the flashes show successful, yet AOKP boots right back up. Recovery does nothing to wipe, currently on Clockworkmod Touch Recovery.
Formatting all caches and partitions, Dalvik wipes all 5x each do nothing, even flashing something after this does nothing. I can't even reset AOKP, it takes me right back to the same condition from August 28th, same theme, apps, etc, all there. I've even formatted both emmc and sdcard, nothing. Whatever I do gets overwritten to the previous condition.
Can someone please help me out with this. I'm not even sure what to classify an issue like this as.
Sent from my SGH-I727 using xda premium

you are not the only one who had this issue, its a failure to write to the nand, for the lack of a better word, i have some links in my ref sticky, 1st link in my sig, under the info section on other users who had this problem, one thing i don't think they tried is using adb to push files
edit: damn i forgot to add those posts to my sticky, i/ll search for them and post them up
EDIT: here is one , couldnt find the other one http://forum.xda-developers.com/showthread.php?t=1751338

Thanks a lot man, what exactly causes something like this to happen? Is it Galaxy specific?
Sent from my SGH-I727 using xda premium

KillaT21 said:
Thanks a lot man, what exactly causes something like this to happen? Is it Galaxy specific?
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
it seems to be a ram hardware failure, but unless i had the problem myself, cant rule out user error, dev's write and wipe the phones constantly, and ive only seen it happen to two users.
read this http://forum.xda-developers.com/showthread.php?t=1704646 and see if it applies to you.
or you can try to push files through adb if phone accepts an adb connection, never tried it so cant help you there

vincom said:
it seems to be a ram hardware failure, but unless i had the problem myself, cant rule out user error, dev's write and wipe the phones constantly, and ive only seen it happen to two users.
read this http://forum.xda-developers.com/showthread.php?t=1704646 and see if it applies to you.
or you can try to push files through adb if phone accepts an adb connection, never tried it so cant help you there
Click to expand...
Click to collapse
I don't think it applies 100% to me. I can write to system, it just gets ignored lol. I read that Mightyoj had the exact issue and adb did nothing for him. I'm within my 30 days, I may need to either find another way to hard brick it or call at&t like he did.
Regardless, thanks for your help Vincom.
Sent from my SGH-I727 using xda premium

Your phone got "lost" / "stolen"
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

vincom said:
or you can try to push files through adb if phone accepts an adb connection, never tried it so cant help you there
Click to expand...
Click to collapse
I remember this issue. The guy who's post you linked to did try adb to no luck. The only thing I can think to try through adb is changing the permissions of emmc? Some one with more knowledge then me might chime in but I'd say
Code:
adb shell
chmod 666 /emmc
That should give read/write to emmc if it will stick. Again you might want to get confirmation on this before attempting it as it is my best guess for your issue. If it's a bad nand you may just be SOL.

Illnevertell said:
Your phone got "lost" / "stolen"
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
There's a thought...hmm
Sent from my SGH-I727 using xda premium

All right, after a few weeks of headache, I thought I'd update this thread as to whats going on.
Sent my phone off to Samsung twice for a fix. Twice due to the support rep not having any clue what the issues were that I was describing to her the first time over, so they sent it back in the same condition as when I sent it to them. Their solution: Applied stock SW.
They didnt even attempt to turn it on to see if the issue was resolved. So fast forward to 3 days after receiving it back and I called Samsung back and carefully worded my problem again and pointed out that I sent it to them before and no solution was found.
So I sent it back off, and 3 days later they called me asking me what exactly was wrong with my phone and I mentioned that it was some issue with the internal memory upon boot that locked everything into a specific setting from August 28th, and that it must be hardware related. She said she would inform the technicians.
So finally, I got my service ticket and the solution they reached was:
Replaced PBA, which is the Print Board Assembly. Looked around on Xda and for the definition and found that a few Samsung devices that were having similar issues as myself and a few others were remedied by replacing it. Currently waiting on them to reship it to me.
So, the "moral" of the story is, if you are within your Manufacturers warranty with Samsung, give Support a call and try as best as you can to explain your problem to them, but dont let them know you're rooted. They are not "supposed" to troubleshoot/fix your issue when rooted. But when they get hands on, they know that the average person that roots would have likely reversed any software issues/damage aside from a brick.
Hopefully this tidbit of information can help future Androidians with Samsung Devices on whats going on and expedite their efforts for a solution. Thanks again to all that were involved
Sent from my SGH-I997 using xda premium

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....