Related
hello, im a bit of a noob with this stuff
i followed a guide on youtube on how to root my g1 and iv already have jf 1.4 recovery image installed and i want to install recovery-ra-.1.5.2 and iv been typing in commands to reinstall it on terminal emu
mount -a
flash_image recovery /sdcard/recovery-ra-dream-v1.5.2.img
and it keeps coming with file not found, when its on the root of my sd card iv been pulling my hair out on this. and trying diffrent methods and still no luck!!
could anyone tell me the commands to do this ? thanks a lot!
Hope this helps
blackcell1 said:
hello, im a bit of a noob with this stuff
i followed a guide on youtube on how to root my g1 and iv already have jf 1.4 recovery image installed and i want to install recovery-ra-.1.5.2 and iv been typing in commands to reinstall it on terminal emu
mount -a
flash_image recovery /sdcard/recovery-ra-dream-v1.5.2.img
and it keeps coming with file not found, when its on the root of my sd card iv been pulling my hair out on this. and trying diffrent methods and still no luck!!
could anyone tell me the commands to do this ? thanks a lot!
Click to expand...
Click to collapse
download the file again for the g1. rename it to something shorter like "dream" and put it on the root of the sd card
type in these commands in the terminal (DO NOT INCLUDE THE $, #, AND THE WORDS IN THE PARENTHESES!!)
$su (if a pop up comes, pick always allow)
#flash_image recovery /sdcard/dream.img
if that doesn't work then just go back to amon ra's thread about the recovery image and try different methods like adb or fastboot
thanks dude, its worked now... i was doing that method before, just seemed to work today thanks again
sorry guys for my english , im new to this forums, i dont know if this has been posted already but i looked it up in the whole forum and i didnt found nothing about this problem,
my problem is the following :
i have a tmobile g1, and i"ve been trying to root it but i 've been having problem flashing a recovery image.
i have followed every tutorial in this forum and tmobile forum ,but the results are the same , i downgraded my g1 to rc29 with the dream,nbh file ,then i put the recovery.img on the root of my sdcard and the hardspl.zip
everything goes well , i type telnetd ,and i downloaded telnet from the market, so when im typing
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system this part goes well i get the pound prompt the i type
# cd sdcard,,, and i type " ls " to see if the file are on the sdcard. ok everything is in the right place
# flash_image recovery recovery.img " then when im typing this , i get the error
mtd:erase failure at 0x001c0000 (I/O) error
mtd: skipping write block
then i rebooted the phone to see if everything went well , im pressing home+power i get the rainbow screen .. i "ve been having this problem since 2009 , any help with this .................... also i have tried to erase the partition with this command
cat /dev/zero > /dev/mtd/mtd2
but nothing seems to be working .. thanks
i hope someone can help me thanks and sorry if this have been post it
dethsector said:
sorry guys for my english , im new to this forums, i dont know if this has been posted already but i looked it up in the whole forum and i didnt found nothing about this problem,
my problem is the following :
i have a tmobile g1, and i"ve been trying to root it but i 've been having problem flashing a recovery image.
i have followed every tutorial in this forum and tmobile forum ,but the results are the same , i downgraded my g1 to rc29 with the dream,nbh file ,then i put the recovery.img on the root of my sdcard and the hardspl.zip
everything goes well , i type telnetd ,and i downloaded telnet from the market, so when im typing
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system this part goes well i get the pound prompt the i type
# cd sdcard,,, and i type " ls " to see if the file are on the sdcard. ok everything is in the right place
# flash_image recovery recovery.img " then when im typing this , i get the error
mtd:erase failure at 0x001c0000 (I/O) error
mtd: skipping write block
then i rebooted the phone to see if everything went well , im pressing home+power i get the rainbow screen .. i "ve been having this problem since 2009 , any help with this .................... also i have tried to erase the partition with this command
cat /dev/zero > /dev/mtd/mtd2
but nothing seems to be working .. thanks
i hope someone can help me thanks and sorry if this have been post it
Click to expand...
Click to collapse
ok man, first off you have to be on android 1.5 not 1.0 according to every guide and me haha, when on rc29 you have to downlad this file called signed-kila-ota-148830.de6a94ca just google it and download it, put it on sdcard and rename it to update turn phone off and go into recovery pressing home and power together, press alt+L when you see the triangle with the sign and then alt+s to update to 1.5 wait and boot, setup.... then use this apk i uploaded, install it with linda or any file manager from your phone, download amonra recovery v1.6.2 from the forum (http://forum.xda-developers.com/showthread.php?p=4647751#post4647751) and put it on your sdcard then go to the app flashrecovery open it and press backup recovery image or whatever it says at the bottom of the screen then you type this sdcard/recovery-RA-dream-v1.6.2.img and then press flash custom recovery image and you are pretty much done, power off and power on pressing home key and check if is there.... hope i helped
etu_aty said:
ok man, first off you have to be on android 1.5 not 1.0 according to every guide and me haha, when on rc29 you have to downlad this file called signed-kila-ota-148830.de6a94ca just google it and download it, put it on sdcard and rename it to update turn phone off and go into recovery pressing home and power together, press alt+L when you see the triangle with the sign and then alt+s to update to 1.5 wait and boot, setup.... then use this apk i uploaded, install it with linda or any file manager from your phone, download amonra recovery v1.6.2 from the forum (http://forum.xda-developers.com/showthread.php?p=4647751#post4647751) and put it on your sdcard then go to the app flashrecovery open it and press backup recovery image or whatever it says at the bottom of the screen then you type this sdcard/recovery-RA-dream-v1.6.2.img and then press flash custom recovery image and you are pretty much done, power off and power on pressing home key and check if is there.... hope i helped
Click to expand...
Click to collapse
You, apparently, don't know what you're talking about.
1) The first rootable exploit was found when firmware version was 1.0. You do NOT need to update to root.
2) The root exploit present in 1.5 was already present already in 1.0, so the same rooting procedure should work fine in 1.0 as it does in 1.5.
@OP: By the sounds of it, it would appear that your NAND may be SHOT... which means that you're going to have to approach this using a different avenue. Specifically, you're going to need to set up your cache and misc partitions for an SPL update from a running system. You have root, so that should be possible. You may need to modify and/or pull some files from a recovery system in order to accomplish this... if you can get the SPL updated to 1.33.2003, then you will have fastboot capability, which makes the recovery partition redundant -- you will be able to boot an external recovery and bypass the whole problem.
i "ve followed all instruction , but i cant put the device into fastboot because the defaulth bootloader the one with the rainbow does not support fastboot , fastboot is only for engineering spl ,
dethsector said:
i "ve followed all instruction , but i cant put the device into fastboot because the defaulth bootloader the one with the rainbow does not support fastboot , fastboot is only for engineering spl ,
Click to expand...
Click to collapse
then... sorry man i got nothing
i dont know men but there should be a way to fix this , this happenned way back when cupcake was released , i didnt want to wait for tmobile to roll out the update , then i just did it manually , after that the problem with the mdt:erase failure started , i hope wrote haykuro about this , but he didnt answer .
dethsector said:
i dont know men but there should be a way to fix this , this happenned way back when cupcake was released , i didnt want to wait for tmobile to roll out the update , then i just did it manually , after that the problem with the mdt:erase failure started , i hope wrote haykuro about this , but he didnt answer .
Click to expand...
Click to collapse
haykuro doesn't know ANYTHING. He is a kid with no experience, who accidentally stumbled onto something unreliable, and talked a thousand people into bricking their phones.
I've already given you your options on this. You have the choice of following my suggestion and developing something to fix your problem, or you can completely give up. Those are your options.
dethsector said:
sorry guys for my english , im new to this forums, i dont know if this has been posted already but i looked it up in the whole forum and i didnt found nothing about this problem,
my problem is the following :
i have a tmobile g1, and i"ve been trying to root it but i 've been having problem flashing a recovery image.
i have followed every tutorial in this forum and tmobile forum ,but the results are the same , i downgraded my g1 to rc29 with the dream,nbh file ,then i put the recovery.img on the root of my sdcard and the hardspl.zip
everything goes well , i type telnetd ,and i downloaded telnet from the market, so when im typing
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system this part goes well i get the pound prompt the i type
# cd sdcard,,, and i type " ls " to see if the file are on the sdcard. ok everything is in the right place
# flash_image recovery recovery.img " then when im typing this , i get the error
mtd:erase failure at 0x001c0000 (I/O) error
mtd: skipping write block
then i rebooted the phone to see if everything went well , im pressing home+power i get the rainbow screen .. i "ve been having this problem since 2009 , any help with this .................... also i have tried to erase the partition with this command
cat /dev/zero > /dev/mtd/mtd2
but nothing seems to be working .. thanks
i hope someone can help me thanks and sorry if this have been post it
Click to expand...
Click to collapse
Shouldn't this be in the general Q&A section, and not the development section?
allright men, so how im gonna update the spl to 1.33.2003 without gettin into fastboot mode , thats the only way to do that right ? when i downgraded the g1 into 1.0 , i turn it off , then i press home+back and it went into recovery , so i press alt L then alt S , it say something about verifying update , reading update , then it says E:cannot read (5 files) , that means im not rooted it so i cant use any update.zip , then i tried updating to cupcake and it worked so while im in 1.5 i turn the phone off and turn it back on pressing home+back , and it went directly to the rainbow screeen
that means after i update the phone to cupcake , i couldnt even put the phone into recovery mode cuz it went into the rainbow screen thats weird right , cuz it doesnt matter what firmware you onto , the phone it suppose to go into recovery mode no matter what , thats why im finding weird too
dethsector said:
allright men, so how im gonna update the spl to 1.33.2003 without gettin into fastboot mode , thats the only way to do that right ? when i downgraded the g1 into 1.0 , i turn it off , then i press home+back and it went into recovery , so i press alt L then alt S , it say something about verifying update , reading update , then it says E:cannot read (5 files) , that means im not rooted it so i cant use any update.zip , then i tried updating to cupcake and it worked so while im in 1.5 i turn the phone off and turn it back on pressing home+back , and it went directly to the rainbow screeen
that means after i update the phone to cupcake , i couldnt even put the phone into recovery mode cuz it went into the rainbow screen thats weird right , cuz it doesnt matter what firmware you onto , the phone it suppose to go into recovery mode no matter what , thats why im finding weird too
Click to expand...
Click to collapse
Don't hold home and back. Just hold home when you turn it on.
First to say that I'm a total newbie into this.
I'm trying to update my HTC Tattoo to Android v2.3 CyanogenMod ROM. I followed his tutorial but I got stucked on one part.
During the rooting it all goes fine untill I arrive to step 7. I type exit to exit a shell and after that when I want to type adb push su /data/local/bin/ it says adb: not found.
I googled some solutions and searched even here on forum but didnt find acceptable hints how to solve this.
And yes when when I type adb devices it comes up with one device.
Hi,
I was following the article :
[GUIDE] How to downgrade 1.7x/1.8x/2.x to 1.32.405.6
@ http://forum.xda-developers.com/showthread.php?t=905003
.
The cursor blinks after this line:
Code:
[*] vold: 0000 GOT start: 0x00014360 GOT end: 0x000143a0
I have waited for almost an hour, but nothing happens, and I have to break using Ctrl+C.
My questions is, what am I doing wrong/ what needs to be done? Cause I see other posts where the output shows many more lines similar to the one above, and then the # (root) prompt, but I don't get it.
-- Phone: HTC Desire HD [Unlocked]
-- OS: Just received OTA Gingerbread: 2.3.3; s/w version: 2.37.720.3
-- Factory Reset Done
-- PC Connection is in : Charging mode and USB Debugging
Complete output:
Code:
G:\htc desire hd\Mod\Setups\Downgrade>adb push misc_version /data/local/tmp
1104 KB/s (15837 bytes in 0.014s)
G:\htc desire hd\Mod\Setups\Downgrade>adb push GingerBreak /data/local/tmp
1173 KB/s (16830 bytes in 0.014s)
G:\htc desire hd\Mod\Setups\Downgrade>adb shell chmod 777 /data/local/tmp/misc_version
G:\htc desire hd\Mod\Setups\Downgrade>adb shell chmod 777 /data/local/tmp/GingerBreak
G:\htc desire hd\Mod\Setups\Downgrade>adb shell
$ ./data/local/tmp/GingerBreak
./data/local/tmp/GingerBreak
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Plain Gingerbread mode!
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014360
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 0000 GOT start: 0x00014360 GOT end: 0x000143a0
Thanks in advance,
Gautam
Downgrade Failed
I got the same result.. Needed help.. :sad:
Same here. Any help would be appreciated
Ok guys even I am stuck here too and I had posted about this, but no one replied, however I got down to googling tactics and the most statisfying reason that I have come up with (reasoning is based on the countless articles and websites about gingerbread and gingerbreak) is that the gingerbreak crack is for a different version of of gingerbread, a version which was launched before we Indians, got out version of gingerbread and thats why our DHDs are getting stuck at the same place over and over again. It's all because of different s/w version numbers.
I guess we all have to wait for a gingerbreak version that is applicable across all DHD ROMs, only then can we be able to downgrade. There might be other way(s), but I know none. This is my two bit about what all of us, are going through when following the downgrade guide. I may be wrong, I may not be. If you have a different thing to say about it, then by all means let all of us hear it.
Thanks Ruben for the clarification. I think you're right. The following two links suggest that as well.
Check out (Google them as I can't paste links due to the less # of posts that I have):
Google Patches GingerBreak Exploit, But Don’t Worry – We Still Have Root (For Now)
Change Iab98d71c: Detect Android devices vulnerable to CVE-2011-1823
I was trying to downgrade so that I could install Android Revolution HD 5.1.7 on my DHD. Any other way to achieve the same? I wish I knew this; just updated to Ginger a few days ago.
The pleasure was all mine Gautam, just trying to do my part to help other Indian DHD users. anyways check out this page http://forum.xda-developers.com/showthread.php?t=905003&page=149 and I believe jkoljo is already on the job.
Unfortunately there is no other way to downgrade the gingerbread 2.37 hoping for an exploit from, The Android Exploid Crew and jkoljo.
is it cuz we are indians?
Same exact problem. Spent more than 24hrs finding a solution. Really bored of the stock ROM and the gingerbread update does not even have enough visual changes. Zzz really wish someone does something about it
Once again Indians have a disadvantage.
Android Version: 2.3.3
HTC Sense Version : 2.1
Baseband : 12.54.60.25U_26.09.04.11_M2
Kernel : 2.6.35.10-g0956377 ([email protected]#1)
Build Number : 2.36.405.8 CL47853 release-keys
Software : 2.36.405.8
I too was following the instructions. The first time I tried I had my sdhc card in and gingerbreak got a little further than you quoted above but just kept saying 'sendmsg fail'. I googled this and found a post which said that gigngerbreak could run without the sdhc card. So I tried that and got the same problem you reported. I waited a few minutes with nothing happening then decided to pop my card back in...at which point gingerbreak started running again.
If your card is in when gingerbreak starts it might be worth ejecting/inserting when you reach the sticking point.
(In the end it didn't help me, gingerbreak finished OK but then I got an error from misc_version which I have not yet been able to get past)
ericjennings said:
Android Version: 2.3.3
HTC Sense Version : 2.1
Baseband : 12.54.60.25U_26.09.04.11_M2
Kernel : 2.6.35.10-g0956377 ([email protected]#1)
Build Number : 2.36.405.8 CL47853 release-keys
Software : 2.36.405.8
I too was following the instructions. The first time I tried I had my sdhc card in and gingerbreak got a little further than you quoted above but just kept saying 'sendmsg fail'. I googled this and found a post which said that gigngerbreak could run without the sdhc card. So I tried that and got the same problem you reported. I waited a few minutes with nothing happening then decided to pop my card back in...at which point gingerbreak started running again.
If your card is in when gingerbreak starts it might be worth ejecting/inserting when you reach the sticking point.
(In the end it didn't help me, gingerbreak finished OK but then I got an error from misc_version which I have not yet been able to get past)
Click to expand...
Click to collapse
1st you will need the following files
GingerBreak from http://c-skills.blogspot.com/2011/04/yummy-yummy-gingerbreak.html
misc_version from http://www.multiupload.com/A9PNGVBWBE
Default rom http://forum.xda-developers.com/showthread.php?t=905003
and Android SDK http://developer.android.com/sdk/index.html
Also you will need a clean SD card 1 gig or more should be fine (smaller is better)
Unzip GingerBreak and misc_version into a folder say c:\Downgrade (I normally use 7Zip)
You should have:
c:\Downgrade\GingerBreak with 5 Files
c:\Downgrade\misc_version with 4 Files
Make sure you installed Android SDK's Platform tools and updated your path to reflect this
IE: run SDK Manager and install Android SDK Tools and Google USB Driver pack if you don t have HTC Sync driver running.
Format the SD card and copy the rom.zip into the base of the card, not a sub directory. (Do not unzip)
Now: Plug in the phone to the USB and make sure Debugging is on and the phone is set to charge only.
Then open Command prompt ie: run cmd.exe
Go to your Downgrade directory and test if your adb command is in the path. ie: run it and make sure it lists switches and not say file not found
Then run as follow
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
adb shell
./data/local/tmp/GingerBreak
if you fail to get root ie: prompt does not return to # or get a endless sendmsg() failed? Error, reboot the phone and repeat the commands above. The phone I used, took 3 tries to get this right.
at the # run the following
cd /data/local/tmp
./misc_version -s 1.31.405.6
When its done exit cmd and goto your phone, Reboot it while pressing volume down.
It will come up with a menu and follow the update instructions.
You should then be on Android version 2.2 when done.
Please note the rom that is supplied works with unbranded phone only if you have a branded phone you will need to make a goldcard. If you want to know how to make one, google is your friend sorry.
You must have htc sync installed!
**** I TAKE NO RESPONSIBILITY IF THE BELOW PROCESS DOES NOT WORK FOR YOU & IF YOU BRICK YOUR PHONE - DO THIS AT YOUR OWN RISK ****
What you need :
- MicroSD card with SD Adapter
Procedure :
1. You need to setup ADB on your PC and download the Android SDK, guide here:
How To: Set Up ADB/USB Drivers for Android Devices | The Unlockr
2. Create a GoldCard here (remember to open the SD Card as a PHYSICAL DISK) :
How To: Create a Goldcard | The Unlockr
3. Download the Generic Software here :
http://androidfiledepot.com/Storage...ravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U _4.05.00.11_release_121865.exe
4. Insert the Goldcard into the Desire and connect it to your PC. Run the software downloaded in step 3.
5. This will flash your Desire with a generic HTC version of the OS.
6. Enjoy!
If you see error 131, you don't have htc sync!
Nilseby, thanks for the suggestion.
I tried your method, and the process starts; phone switches off and HTC in displayed in White. After a few minutes, it says, that it can't go through with this, and the program just hangs. I powered on the phone and it's back to the way it was. Flashing didn't go through. I created a gold card as well and formatted, still no luck.
2.37.720.3
Why, oh why did I upgrade to 2.37.720.3?
I actually wanted to root my DHD so that I could take screenshots of its screen. Now that it is being reporting that as of now 2.37.720.3 is not downgradable, is there any other way to take screenshots of my phone's screen? Other than, of course, taking pics with another camera.
Thank God!
I am using RCMIX HD Kingdom v 1.2 with Sense 3.0 on my DHD and when I saw I downgrade guide from Gingerbread to get root access, I decided to upgrade to the official 2.3.3 in India. I saw the initial posts in that thread say that the method worked really well.
I had almost made up my mind to try the official update knowing that I can downgrade using the guide, but just before doing that I thought I'd read the more recent posts and guess what I realized the Indian software number 2.37.720.3 cannot be downgraded! Which means no root access and no custom ROMs (at least for now). I immediately changed my mind and didn't upgrade.
Thank God!
Good decision av. Just wait till this issue gets sorted out and then dive in. I was too eager to see what was up with Mr.Ginger and curosity killed the cat.
Sent from my Desire HD using XDA App
We in Australia have the same problem regret upgrading.
Just got my UK 2.37 upgrade a few days ago...why, oh, why did I accept it!? Hopefully not long until the 2.37 gingerbreak is out
guitarist7 said:
Just got my UK 2.37 upgrade a few days ago...why, oh, why did I accept it!? Hopefully not long until the 2.37 gingerbreak is out
Click to expand...
Click to collapse
yeah..
now i cant do anything with it
I can't even get a GoldCard to work on 2.37x , I know its not the cards I'm using as they still work for older releases
DotNetRules said:
I can't even get a GoldCard to work on 2.37x , I know its not the cards I'm using as they still work for older releases
Click to expand...
Click to collapse
What do you mean by getting a GoldCard to work? Is the phone not mounting it or something?
Hello everyone, it's my first post.
I have a strong desire to install Paranoid Android on my phone, one of the first things I did to accomplish this was root my phone.
Note, I don't remember how I rooted my phone, just that I did and executed a root checker to confirm that it was successful.
After rooting I began watching a video tutorial but found myself stuck at the boot screen, unable to proceed.
Here is the above mentioned video: http://www.youtube.com/watch?feature=player_embedded&v=a3pof_WSEEI
Still clueless, I reached out to Reddit for a better guide. It seemed that the video I was watching had assumed I had done certain steps which I had not, so I tried to learn what preliminary steps were necessary.
I was then referred to the following link: forum.xda-developers.com/showthread.php?t=1843585
I began to review all the content and started completing the steps one by one, but I got stuck.
When it came time to bring up my identifier token and submit it I was told that I failed somehow.
It was at this point when I noticed that my boot screen says; *** TAMPERED ***, *** LOCKED ***.
Interestingly enough, the boot screen in the above mentioned video tutorial does not say the same messages as mine, so I thought "herein lies the problem".
I figured that the reason why my identifier token was rejected is because I rooted my phone, so I proceeded to unroot my phone.
I found some instructions, which I cannot find anymore, and downloaded an application to unroot my HTC one X.
Here is the above mentioned file I downloaded: http://downloadandroidrom.com/file/HTCOneX/unroot/OneXUnroot.zip
I tried running the program, as instructed, but failed.
Now I feel stuck, I didn't feel compelled to post here before, but now I do. I really just want to get what I want done ASAP.
I would greatly appreciate any and all help you can offer.
First of all, do a search for the "How to do everything to your HTC One X" thread in this forum. I think its best if you study this guide and go step by step to first unlock your phone, root it and then install whatever ROM you want. This is the best guide that I've ever seen on exactly how to accomplish this and its very very newbie friendly..
SirVivi said:
Hello everyone, it's my first post.
I have a strong desire to install Paranoid Android on my phone, one of the first things I did to accomplish this was root my phone.
Note, I don't remember how I rooted my phone, just that I did and executed a root checker to confirm that it was successful.
After rooting I began watching a video tutorial but found myself stuck at the boot screen, unable to proceed.
Here is the above mentioned video: http://www.youtube.com/watch?feature...&v=a3pof_WSEEI
Still clueless, I reached out to Reddit for a better guide. It seemed that the video I was watching had assumed I had done certain steps which I had not, so I tried to learn what preliminary steps were necessary.
I was then referred to the following link: http://forum.xda-developers.com/show....php?t=1843585
I began to review all the content and started completing the steps one by one, but I got stuck.
When it came time to bring up my identifier token and submit it I was told that I failed somehow.
It was at this point when I noticed that my boot screen says; *** TAMPERED ***, *** LOCKED ***.
Interestingly enough, the boot screen in the above mentioned video tutorial does not say the same messages as mine, so I thought "herein lies the problem".
I figured that the reason why my identifier token was rejected is because I rooted my phone, so I proceeded to unroot my phone.
I found some instructions, which I cannot find anymore, and downloaded an application to unroot my HTC one X.
Here is the above mentioned file I downloaded: http://downloadandroidrom.com/file/H...OneXUnroot.zip
I tried running the program, as instructed, but failed.
Now I feel stuck, I didn't feel compelled to post here before, but now I do. I really just want to get what I want done ASAP.
I would greatly appreciate any and all help you can offer.
Click to expand...
Click to collapse
First, Root! http://forum.xda-developers.com/showthread.php?t=1709296
Second, Unlock Bootloader! http://forum.xda-developers.com/showthread.php?t=1672284
Third, Custom Recovery! TWRP Only, Install Goo Manager from market and install from there is easiest.
Make a nandroid of your current ROM (stock I assume) them you can flash PA.
Hope this helps.
You've made some big mistakes. I see from your other posts your device is the HTC codename EVITA (Snapdragon S4 version of the phone):
SirVivi said:
I was then referred to the following link: http://forum.xda-developers.com/show....php?t=1843585
Click to expand...
Click to collapse
Your link is busted, but I fixed it, to see where it points: http://forum.xda-developers.com/showthread.php?t=1843585
That's the wrong forum. Its from the international (Tegra3) version of the One X, codename ENDEAVORU. Completely different hardware. Flashing things, or following guides meant for the Tegra3 version will fail, and may brick your device.
You need to stick to the subforum for our (Snapdragon S4) version: http://forum.xda-developers.com/forumdisplay.php?f=1538
In particular, our Development subforum: http://forum.xda-developers.com/forumdisplay.php?f=1541
And to see all the resources in an organized list, check out my index thread (sticky at the top of Development): http://forum.xda-developers.com/showthread.php?t=1671237
SirVivi said:
I found some instructions, which I cannot find anymore, and downloaded an application to unroot my HTC one X.
Here is the above mentioned file I downloaded: http://downloadandroidrom.com/file/H...OneXUnroot.zip
I tried running the program, as instructed, but failed.
Click to expand...
Click to collapse
Link is busted, so I can't see what it actually points to. But I'd strongly caution against flashing/running things downloaded from random websites, unless you have good knowledge of what you are looking at, and have some reason to believe its a reputable source. Do yourself a favor and stick to this forum (many of those random websites just steal content from XDA, anyway). Even if the content is legit, other websites are not well organized (EVITA versus ENDEAVORU), and contain a lot of content meant for the international One X, which will damage your phone. Everything in our XDA device subforum (as I've linked above) is meant for our version, and known to be safe.
You're pretty lucky you haven't bricked your device at this point, as you've already applied several things not meant for our phone. My advice would be to follow the recommendations in the post above mine. Root, SuperCID, and unlock the bootloader, using the links he supplied (also found in my index thread I've linked above).
bimmernut318 said:
First, Root! http://forum.xda-developers.com/showthread.php?t=1709296
Click to expand...
Click to collapse
I started the process, it instructed me to "Put su in same directory as ADB. Get to adb command prompt and cd into that directory"
However, it does not explain how to do so.
SirVivi said:
I started the process, it instructed me to "Put su in same directory as ADB. Get to adb command prompt and cd into that directory"
However, it does not explain how to do so.
Click to expand...
Click to collapse
Do some reading here: http://forum.xda-developers.com/showthread.php?t=1754018
---------- Post added at 10:22 AM ---------- Previous post was at 10:20 AM ----------
Also, what carrier version is your phone (AT&T, Telstra, etc)?
And what firmware version (Settings>About>Software information>Software number)?
First, I repaired the links.
Next, my phone is AT&T and my software number is: 1.85.502.3 710RD
Finally, I just discovered that the adb tool is located under C:\Android\android-sdk\platform-tools
I'm currently reading the "Gunnyman's quick and dirty adb/fastboot primer" link you posted.
Note, I had to google to find out where the adb tool was located, the guide did not explicitly say where it would be.
Now that I know the the directory where the adb tool was stored, I think I can proceed with the following instructions: http://forum.xda-developers.com/showthread.php?t=1709296
PS: I need to go to work now, but I will be back at around 8:30 PM CST
SirVivi said:
Next, my phone is AT&T and my software number is: 1.85.502.3 710RD
Click to expand...
Click to collapse
Then you should be good to go with the links that bimmernaut318 gave above. Just wanted to make sure we were sending you in the right direction.
Good luck. Feel free to pop back on here if you have specific questions. It probably seems a pain to have to read and research all this stuff. But its all good stuff to know, and you will be better in the end for learning it.
---------- Post added at 11:19 AM ---------- Previous post was at 11:15 AM ----------
SirVivi said:
I figured that the reason why my identifier token was rejected is because I rooted my phone, so I proceeded to unroot my phone.
Click to expand...
Click to collapse
Just to clarify, root does not affect unlocking the bootloader. In fact, as you may have already determined, its required (to get SuperCID) in order to unlock the BL.
Unlocking the bootloader failed because the AT&T Carrier ID (CID) is blocked on HTCDev.com thanks to AT&T. Achieving SuperCID is the workaround.
Well, when I execute: adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
I get the following message:
C:\Android\android-sdk\platform-tools>adb shell rm /data/data/com.redbend.vdmc/l
ib/libvd*
rm failed for /data/data/com.redbend.vdmc/lib/libvd*, No such file or directory
EDIT:
Actually. I think it was successfull... I restored my phone and tried again, got this.
C:\Android\android-sdk\platform-tools>adb reboot
C:\Android\android-sdk\platform-tools>adb shell rm /data/data/com.redbend.vdmc/l
ib/libvd*
rm failed for /data/data/com.redbend.vdmc/lib/libvd*, No such file or directory
C:\Android\android-sdk\platform-tools>adb shell rm /data/data/com.redbend.vdmc/l
ib/libvd*
rm failed for /data/data/com.redbend.vdmc/lib/libvd*, No such file or directory
C:\Android\android-sdk\platform-tools>adb reboot
C:\Android\android-sdk\platform-tools>adb reboot
C:\Android\android-sdk\platform-tools>
C:\Android\android-sdk\platform-tools>adb shell rm /data/data/com.redbend.vdmc/l
ib/libvd*
rm failed for /data/data/com.redbend.vdmc/lib/libvd*, No such file or directory
C:\Android\android-sdk\platform-tools>adb shell rm /data/data/com.redbend.vdmc/l
ib/libvd*
C:\Android\android-sdk\platform-tools>adb reboot
C:\Android\android-sdk\platform-tools>adb shell ln -s /data/local.prop /data/dat
a/com.redbend.vdmc/lib/libvdmscomo.so
C:\Android\android-sdk\platform-tools>adb shell ls -l /data/local.prop
-rw-rw-rw- root radio 159216 2012-10-20 13:37 local.prop
C:\Android\android-sdk\platform-tools>adb shell "echo 'ro.kernel.qemu=1' > /data
/local.prop"
C:\Android\android-sdk\platform-tools>adb reboot
C:\Android\android-sdk\platform-tools>adb remount
remount succeeded
C:\Android\android-sdk\platform-tools>adb push su /system/xbin/su
2303 KB/s (91980 bytes in 0.039s)
C:\Android\android-sdk\platform-tools>adb shell chown 0.0 /system/xbin/su
C:\Android\android-sdk\platform-tools>adb shell chmod 06755 /system/xbin/su
C:\Android\android-sdk\platform-tools>adb shell rm /data/local.prop
C:\Android\android-sdk\platform-tools>adb reboot
C:\Android\android-sdk\platform-tools>
Strange... I'm running the Spoof-CID.bat and I'm stuck at 'waiting for device'
Similar to this user:
http://i.imgur.com/fmTUP.png
Ok, I think I got past that little hickup. However, now I've been presented with a new problem. Not quite sure how to handle...
Make sure your device has usb debugging mode enabled, and is
Press any key to continue . . .
Restarting ADB
Pulling files
Checking files
Checking if patch can be applied
Everything looks good, rebooting to bootloader.
Once you are in bootloader mode, press any key to dump the ci
Press any key to continue . . .
...
FAILED (status read failed (Too many links))
finished. total time: 0.314s
...
FAILED (command write failed (No such file or directory))
finished. total time: 0.002s
Your CID should read; 11111111
If it doesn't, something when wrong!
Goto HTCDev.com to finish the unlock process with the code ab
After you get your unlock file, drop it into the same folder
Press any key and then follow the instructions on the phone.
Press any key to continue . . .
UPATE: after fiddleing I got the unlock code, however i mistakenly hit a key closing the program... so now I have to start over, lol.
i feel close !
EDIT: Ugh, I don't know what's wrong now. I put the unlock code in the folder as instructed but it's stuck at waiting on device...
EDIT2: OHHH I had to press the power button down whilst hovering over fast boot, THEN I get asked to unlock the bootloader!
Ok guys, I installed goo manager and I think my phone is good to go at this point.
Well.. I think I ****ed my phone.
I tried to pick up where I left off in the video tutorial above.. but when it came time to restart the phone and get to 4:00 in the video I didn't see the screen mentioned.. so now my phone can get to the boot menu but won't system restore.
EDIT: I don't know if anybody's willing to do this... but maybe I could work though this issue with someone's aid over skype?
Since I can still access the boot screen I'm just going to go out and assume that It's still possible to restore my phone, which is still rooted and has the boot loader still unlocked. By the way, I did create a backup at one point using the Android SDK tool I believe. I'm not sure if that helps me.
help.
all the links you posted in your OP are for the endeavoru. you have an evita. don't go back to looking at endeavoru information when you are sooooo close.
just to see where you are at. does bootloader say TAMPERED and UNLOCKED? did goomanager install twrp 2.3.1.0?
DvineLord said:
all the links you posted in your OP are for the endeavoru. you have an evita. don't go back to looking at endeavoru information when you are sooooo close.
just to see where you are at. does bootloader say TAMPERED and UNLOCKED? did goomanager install twrp 2.3.1.0?
Click to expand...
Click to collapse
I'm sorry, DivineLord, like the noob lord that I am I didn't know any better.
My bootloader says TAMPERED and UNLOCKED, I'm not sure if goomanager installed anything other than what it automatically installs upon startup.
EDIT: Would this help me? http://d-h.st/8pr and if so, how would I even use it?
All it takes is five mins of searching on google to realize we have an evita
omario8484 said:
All it takes is five mins of searching on google to realize we have an evita
Click to expand...
Click to collapse
I don't know why so called "how to install" videos don't preface their tutorials by saying precisely what their tutorial requires. :/
downloaded newest twrp http://www.teamw.in/project/twrp2/99
reboot into bootloader
fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img
* after that you will be good to flash roms. remember never factory reset from the bootloader or inside the rom. always factory reset from inside recovery.