Related
Guys, I'm RETARDED. PLEASE HELP ME.
I was going to update to JesusFreke's RC30v1.3, but when booted up pressing HOME + END, I saw that for some reason, I didn't have the recovery image that uses the test keys while i did have the modded boot image (getprop ro.secure returned 0)
I tried following the guide here since I still had root from the adb shell, but when I tried to do it, I got stuck. When I tried to do the following line,
Code:
cat /data/local/recovery.img > recovery.img
I got this:
Code:
write: No space left on device
No problem, I thought. I'll just wipe the phone and then try it again!
It didn't work.
I then started experimenting with different things, even though I know I shouldn't have... and then I accidentally deleted my recovery.img file. ****.
As you may have surmised from the title of the post, I have root access from within the OS and from ADB and I also have the ADP1 bootloader on my phone. When I try going to the recovery menu, it just takes me to the bootloader (with the skateboarding 'droids). Also, I have installed manup's Bluestar 5 theme. I don't know since when my recovery image had reverted, but I know it was some time after I installed the ADP1 bootloader.
I've tried to do the stuff in the post mentioned above again, but it still gives me the damn
Code:
write: No space left on device
... I think it's mocking me.
The REALLY ironic part was that the first thing that I was going to do when I installed v1.3 was make a NANDroid backup.
Guys, PLEASE help me with this if you can. I know I was a retarded noob, but I'll learn from my mistakes. In the meantime, I can at least USE the phone... just with JF's RC30v1.2 and without Stericson's new theme (which I was gonna apply after backing up from NANDroid after installing RC30v1.3)
Thanks for your time,
~Ankush
The reason you are having write errors is JF has pushed the storage of /system partition to the limit. But flash_image can take any source location. Just put recovery.img in /data and then run
flash_image recovery /data/recovery.img
I saw that for some reason, I didn't have the recovery image that uses the test keys while i did have the modded boot image (getprop ro.secure returned 0)
Click to expand...
Click to collapse
This is a documented bug in v1.2. The new v1.3 recovery has a very distinct background image so there's no more ambiguity.
When I try that, I can boot into the Recovery menu, but when I try to apply the v1.3 update.zip, it fails at the "verifying update package" step and says:
Code:
E:Corrupt file:
data/recovery.img
E:Verification failed.
Installation aborted.
I redownloaded the recovery.img file and tried it again several times, but it didn't work either...
Thanks for the reply though.
~Ankush
P.S: HAPPY NEW YEAR! (at least in EST)
After you have done flash_image, rm recovery.img from /data. Also you might want to check your MD5 of update.zip
Yeah. I ended up downloading the 1.3 update again and then unzipping the recovery.img from that and applying it.
I saw the weird background along with the NANDroid 2.1 option so I applied the update.zip of the redownloaded JFv1.3 update.
I think that the main problem was the md5...
Oh well, it's all dandy now!
Thanks a BUNCH jashsu, have a happy new year!
Please note, this is NOT my own work. It's on the CM Wiki, but since so many people seem to not want to be bothered to read the damn wikis for their intended purpose, I'm going to be a ratbastard enabler and post the steps HERE in a thread, so next time someone goes to post to ask how, IF they use the search function they'll find THIS thread and not threadnaught this forum with questions about how to do it.
This has been tested and works 100%. I have not tried it for CM6, and I don't suggest anyone try it on a 911 patched Rogers Dream until CM6 is stable AND there's a proper kernel image for Dream/Magic 32A/32B. As usual, I hold no responsibility if this bricks your Dream. I have made ROMs for the Raphael, Rhodium, Topaz, and Kaiser, and am an expert on those devices but this is my first actual Android device that I've had for less than a week, and just rooted/flashed it today, so I am NOT an Android expert AT ALL.
Original Guide: Here!
(Note: This guide is for CM5)
Step 1) Download all of the required software. SDK, Fastboot, Exploid from DroidXRoot, SPL 1.33.2005, Amon_Ra Recovery for CM, CM5 Itself, Googleapps, and extra kernel for Rogers Dream.
Step 2) Install extract the SDK archive and rename it to 'sdk' for easier use. In Windows, extract to C:\sdk, linux ~/home/sdk, mac .. wherever you want. Extract the Fastboot.zip to the sdk/tools folder. Move exploid, SPL, and Recovery to sdk/tools for easier use with adb.
Step 3) On your Dream, go to Settings->Applications->Development and enable USB Debugging, and connect your Dream to your computer via USB cable.
Step 4) Enter your sdk/tools directory and type the following:
Code:
* adb push spl-signed.zip /sdcard/1_33_2005_spl.zip
* adb push update-cm5* /sdcard/update-cm5*
* adb push gapps-ds-ERE36B-signed.zip /sdcard/gapps-ds-ERE36B-signed.zip
* adb push bc-5.0.x-ebi1-signed.zip /sdcard/bc-5.0.x-ebi1-signed.zip
* adb push recovery-RA-dream-v1.7.0R-cyan.img /data/local
* adb push exploid /sqlite_stmt_journals
* adb shell chmod 777 /sqlite_stmt_journals/exploid
(*whatever your CM image is.)
Step 5) Running Exploid!
Code:
adb shell /sqlite_stmt_journals/exploid
should produce the following:
Code:
$ adb shell /sqlite_stmt_journals/exploid
[*] Android local root exploid (C) The Android Exploid Crew
[*] Modified by birdman for the DroidX
[+] Using basedir=/sqlite_stmt_journals, path=/sqlite_stmt_journals/exploid
[+] opening NETLINK_KOBJECT_UEVENT socket
[+] sending add message ...
[*] Try to invoke hotplug now, clicking at the wireless
[*] settings, plugin USB key etc.
[*] You succeeded if you find /system/bin/rootshell.
[*] GUI might hang/restart meanwhile so be patient.
Now unplug/replug USB cable to apply exploit. ROOOOOTED!
Step 6) Custom Recovery time!
Type the following:
Code:
adb shell
this will take you to a $ prompt (that's the shell.)
Code:
rootshell
this will ask for a password, which is 'secretlol' without quotes.
Now that you're at a root shell, type
Code:
chmod 666 /dev/mtd/mtd1
exit
Now you're back at the regular shell prompt, type:
Code:
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
If this gives a "mtd: read error at 0x00000000 (Out of memory)" error, it's okay, just type it again and it should work without the error. This is normal, do not panic.
Once this is complete, type
Code:
exit
and power down the phone. (long hold end key)
Step 7) SPL
Hold Home and press the End key to power up the Dream. At the recovery menu select
Code:
Flash Zip from SDCARD
and select the
Code:
1_33_2005_spl.zip
.
Now reboot by holding home+back. It will take you back to the recovery shell, and this is okay. This is actually what we want. Now, type
Code:
adb shell reboot bootloader
and watch the screen to verify that you see:
Code:
HBOOT: 1.33.2005
RADIO: 3.22.26.17
Now, run the following Fastboot commands:
Code:
fastboot erase system -w
fastboot erase boot
fastboot oem powerdown
Step 8) Flashing CM!
Press home+end to power up the phone in recovery mode, and select
Code:
Flash Zip from SDCARD
, Select your CM image, then
Code:
Flash Zip from SDCARD
and select gapps-ds-ERE36B-signed.zip, and finally
Code:
Flash Zip from SDCARD
and select bc-5.0.x-ebi1-signed.zip.
Once that is complete, home+back to reboot, and you're done. That's it. First CM boot may take 5-15 mins.
Reserved for updates
Click to expand...
Click to collapse
Time for the update!
CyanogenMod6rc3
EBI1 Kernel for CM6rc3
Google Apps, Mdpi Tiny for CM6
Use these the same way you would in the above steps for flashing CM5, obviously replacing the zip files from CM5 with the ones from CM6 during the adb push, and the flashing from zip in recovery console. This should work exactly the same as the above version, but the end result is that you'll have FroYo instead of Eclair.
I waited until RC3 for this update because, in my opinion, RC2 was a bit laggy and overall wasn't as stable.
Also note: This process will work for roms OTHER than CyanogenMod so long as they're either based on CM or have an EBI1 Kernel available. Make sure you use the correct EBI1 Kernel by checking what gapps version the Rom uses if it's CM-based but doesn't link to an EBI1 Kernel. For example, if it's gapps-mdpi-FRF91-3 then it's the CM6rc2 EBI1 Kernel you need.
Any questions? Post 'em here.
Thanks for posting this. I know some people got confused.
I highly recommend people also look at the pre existing thread: http://forum.xda-developers.com/showthread.php?p=7306638#post7306638 if they have questions as that is where the q/a is at.
ezterry said:
I highly recommend people also look at the pre existing thread: http://forum.xda-developers.com/showthread.php?p=7306638#post7306638 if they have questions as that is where the q/a is at.
Click to expand...
Click to collapse
The difference is your thread is a vague shortened process that assumes people are going to follow all the links in your post and read through pages of comments to figure out the exact steps of your "simplified process", where my thread gives them a one-stop-shop from stock to a stable rom. You've linked to your thread, so now people who don't mind looking around then posting tons of questions have their place to go.
Tl;dr version: this thread is for the people who can barely be bothered to use the search function and want everything in one place, your thread is for "everyone else".
Sent from my HTC Dream using XDA App
agentfusion said:
The difference is your thread is a vague shortened process that assumes people are going to follow all the links in your post and read through pages of comments to figure out the exact steps of your "simplified process", where my thread gives them a one-stop-shop from stock to a stable rom. You've linked to your thread, so now people who don't mind looking around then posting tons of questions have their place to go.
Tl;dr version: this thread is for the people who can barely be bothered to use the search function and want everything in one place, your thread is for "everyone else".
Sent from my HTC Dream using XDA App
Click to expand...
Click to collapse
Don't worry I'm following this thread so *I* don't inadvertently support people who don't follow links.
It just sucks that people really are that lazy. Seriously. They waste more time typing a question that has been answered 20 times than it would take to search for the proper answer.
So yeah, thanks for posting a topic that has a lot of great information for those of us who aren't lazy, I do personally like yours and think it should be in the informative links sticky. I just wish I had found yours first while I was searching for my answers because it really is informative for those of us not afraid to read and not have things spoonfed to them.
Sent from my HTC Dream [CM5] with xda app.
Thanks for the How-To. It was very easy to follow.
AverageCanadian said:
Thanks for the How-To. It was very easy to follow.
Click to expand...
Click to collapse
No problem! Glad you found it useful. All of those steps now work for CM6, so I will be adding links for CM6rc3 later tonight
Sent from my HTC Dream using XDA App on CM6rc3
update bump.
Tks for the guide. Total newbie here and trying to root my HTC Dream.
Up to now, i fallowed WIKI loll to the letter, tho, when i try to download the EXPLOID, either from your link or the WIKI one, it pup's out as a TROJAN program Exploit.Linux.Lotoor.e !
Is it safe to get it or i shouldn't go there???
I'm stuck to this step now and not sure what to do
Tks for the info..
Wood's said:
Tks for the guide. Total newbie here and trying to root my HTC Dream.
Up to now, i fallowed WIKI loll to the letter, tho, when i try to download the EXPLOID, either from your link or the WIKI one, it pup's out as a TROJAN program Exploit.Linux.Lotoor.e !
Is it safe to get it or i shouldn't go there???
I'm stuck to this step now and not sure what to do
Tks for the info..
Click to expand...
Click to collapse
To the best of my knowledge, it comes up as a trojan because it's a rootkit for Android, which is based on Linux... so virus scanners will consider Exploid as a "virus/trojan" because using a rootkit on a linux machine is basically using a trojan to get root access, which is what you're doing to your phone.. you're using an exploit to get root access.
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.
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.
Here's my One-Click G2 Freedom Tool to get TWRP on your stock 30b tmo G2.
Credits to Bump Team, Snowlin, Bouchigo and blastagator.
Step 1: Root your LP 30b. Go here:
ROOT FOR LP G2
Step 2: Enable USB debugging. Settings, About Phone, Software info, Click Build number 5 times!
Step 3: Allow usb debugging info that pops up.
Step 4: Unzip file and run LAUNCH-FREEDOM-30B-BUMPED.bat. Follow instructions on screen.
G2-TMO-30B-FREEDOM-TOOL.zip
MD5: 6cb05fff3a76cbff4056871d2f8e7221
BTW, no longer have TMO G2. Returned it and probably get a G3 or G4. Need wireless charging. Support will be limited.
Thank you, it worked very well for me on T-MOBILE LG G2
zeinoonm said:
Thank you, it worked very well for me on T-MOBILE LG G2
Click to expand...
Click to collapse
Same here, thank you! Just got the Lollipop OTA this morning.
Question... Do you recommend backing up EFS files? It was unchecked by default and I know it was a big deal with the Optimus G. I am going to just in case but thought I would ask.
Nick N said:
Same here, thank you! Just got the Lollipop OTA this morning.
Question... Do you recommend backing up EFS files? It was unchecked by default and I know it was a big deal with the Optimus G. I am going to just in case but thought I would ask.
Click to expand...
Click to collapse
It wouldn't hurt. I usually don't.
Please Help!
I think I'm in deep trouble! I screwed up and busted a rookie move when I was trying to flash the new Simple Romv2 on my T-Mobile D801. At the time I was running BlissPopv3.2. Well my dumb ass got it bricked and I cant seem to get any detection with your tool or any for that matter. My computer can pick up the device and recognize it but it seem like every time I try to use any tool to reflash a stock rom it says there is no phone connected. I have already updated my LG drivers and still cant seem to get anything to work! Any help will be very appreciated. Thanks in advance.
jesseserna said:
I think I'm in deep trouble! I screwed up and busted a rookie move when I was trying to flash the new Simple Romv2 on my T-Mobile D801. At the time I was running BlissPopv3.2. Well my dumb ass got it bricked and I cant seem to get any detection with your tool or any for that matter. My computer can pick up the device and recognize it but it seem like every time I try to use any tool to reflash a stock rom it says there is no phone connected. I have already updated my LG drivers and still cant seem to get anything to work! Any help will be very appreciated. Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2566032 :good:
LG Flash Tool 2014 KDZ restore
jesseserna said:
I think I'm in deep trouble! I screwed up and busted a rookie move when I was trying to flash the new Simple Romv2 on my T-Mobile D801. At the time I was running BlissPopv3.2. Well my dumb ass got it bricked and I cant seem to get any detection with your tool or any for that matter. My computer can pick up the device and recognize it but it seem like every time I try to use any tool to reflash a stock rom it says there is no phone connected. I have already updated my LG drivers and still cant seem to get anything to work! Any help will be very appreciated. Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2797190
Once I run this, how do I go back into recovery? It's been a while and I forgot
Auggy99 said:
Once I run this, how do I go back into recovery? It's been a while and I forgot
Click to expand...
Click to collapse
Download Quick Boot from play store.
MicroMod777 said:
Download Quick Boot from play store.
Click to expand...
Click to collapse
+1 , This one of my favorite apps . quick and simple :good:
Or Terminal and type su reboot recovery.
How long does the TWRP tool run for?
Hi all, I've got root on my 30b LP stock & I've run the Freedom Bat file, it pushed the 3 files to my phone and the Command Promt shows "Hacking Recovery" and has been at this point for 10-15 minutes now. My phone screen is not asking for prompts...? Is this normal...looking for some advice, thank you!
zeinoonm said:
Thank you, it worked very well for me on T-MOBILE LG G2
Click to expand...
Click to collapse
It took 25 mins
MicroMod777 said:
Here's my One-Click G2 Freedom Tool to get TWRP on your stock 30b tmo G2.
Click to expand...
Click to collapse
Damn, wish I had found this from the start, but +thanks all around. I've spent the last two days screwing around with a refurb phone, thinking I had messed it up. Actually, I had, because I kept getting the boot certification verify error, and download mode didn't show the normal "Firmware" screen or fastboot mode.
FWIW, regarding the "enable USB ethernet" prompt: I searched for info on doing this, and didn't find anything pertinent. Turns out I didn't need to do that, it just worked. But maybe you could add some explanation in this thread, or the .bat file? I've never heard of it, and I've been flashing ROMs since 2008.
Otherwise, perfect. Absolutely perfect. I'm used to working with stock KK on new phones, and LP was really putting up a fight. No more. >
could someone tell devs to consider changing push location from "/sdcard" to "/data/local/tmp" because after an update /sdcard is not accessible and i kept getting an error until i changed the batch file.
Create a text file and save as root.bat and put it in the same folder as bin
@echo off
title [Recovery]
cd bin
echo.
echo *************TMO FREEDOM 30B BUMPED******************
echo.
echo.
echo ************Hack by BUMP TEAM, Snowlin,Bouchigo*****************
echo.
echo.
echo ***********One Click Modded by MicroMod777************
echo.
echo Enable usb debugging and connect your device.
echo Enable usb internet connection ethernet.
echo.
echo.
pause
echo.
adb kill-server
adb wait-for-device
:version
echo.
echo Choose your device version:
echo.
echo 1: [TMO]
echo.
set /P d=
if /i "%d%"=="1" goto :root
goto :version
:root
echo.
echo Sending files to data/local/tmp
adb push recovery.img /data/local/tmp/recovery.img
adb push aboot.img /data/local/tmp/aboot.img
adb push boot.img /data/local/tmp/boot.img
echo.
echo ********PLEASE ALLOW ROOT PERMISSIONS ON PHONE********
echo.
echo.
echo ********************HACKING RECOVERY******************
adb shell "su -c dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
adb shell "su -c dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot"
adb shell "su -c dd if=/data/local/tmp/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot"
echo Done....
:choice
echo.
set /P c=Reboot into recovery now [y/n]?
if /i "%c%"=="y" goto :reboot
if /i "%c%"=="n" goto :exit
goto :choice
:reboot
adb reboot recovery
adb kill-server
exit
:exit
adb kill-server
exit
Click to expand...
Click to collapse
voxluna said:
Damn, wish I had found this from the start, but +thanks all around. I've spent the last two days screwing around with a refurb phone, thinking I had messed it up. Actually, I had, because I kept getting the boot certification verify error, and download mode didn't show the normal "Firmware" screen or fastboot mode.
FWIW, regarding the "enable USB ethernet" prompt: I searched for info on doing this, and didn't find anything pertinent. Turns out I didn't need to do that, it just worked. But maybe you could add some explanation in this thread, or the .bat file? I've never heard of it, and I've been flashing ROMs since 2008.
Otherwise, perfect. Absolutely perfect. I'm used to working with stock KK on new phones, and LP was really putting up a fight. No more. >
Click to expand...
Click to collapse
Can you please tell me how did you fix your phone? got the Tmobile LG G2 and it was running on Android 4.4.2. Then I changed the dpi by editing the build.prop via root explorer up but when the device reboots, it shows system force close and I basically cannot do anything. I realized that my TWRP recovery hadn't installed successfully and also I think download mode is not working. Computer recognizes the device when it is on... Can someone please tell me how to unbrick my device? Is there a way to install TWRP at the current condition of the phone? I think I cannot use lg flashtool because that requires the phone to be in download mode, while mine can't get in download mode...please help! thank you!
Edit: also when I try to hard factory reset the device it shows: ERROR: boot certification error and it gets stuck in black screen.
wizbo27 said:
could someone tell devs to consider changing push location from "/sdcard" to "/data/local/tmp" because after an update /sdcard is not accessible and i kept getting an error until i changed the batch file.
Create a text file and save as root.bat and put it in the same folder as bin
Click to expand...
Click to collapse
Could you tell me what version of TWRP this installs?
Thanks in advance
wizbo27 said:
could someone tell devs to consider changing push location from "/sdcard" to "/data/local/tmp" because after an update /sdcard is not accessible and i kept getting an error until i changed the batch file.
Create a text file and save as root.bat and put it in the same folder as bin
Click to expand...
Click to collapse
Thanks for this. I had the same problem but I used your suggestion to change the .bat file and it worked perfectly for me. Phone now has a working recovery again.
i have d801 tmobile kitkat 20g if i ota update to lp will it be 30b and this root method will work for me?
because i checked every other rooting method and non of them work