Related
I stopped updating this information a long time ago. I recommend finding a more recent thread...
Very good job, exactly what I have been looking for.
Very good job!
Great instructions.....
WOW!! Wish i had something like this 2 months ago when i got my G1. Nice of you to put this together. Definatly going to help out a lot of people and save them a SH!T load of time and head aches! STICKY!!
Don't you have to downgrade to RC29?
Or is that obsolete now?
Wow this would've definitely come in handy a few weeks ago. But what took me a few hrs to gather by reading posts this one thread explains it all. Glad you took the time to write this. Hopefully a more stable hero comes out too to update this thread with.
Paul22000 said:
Don't you have to downgrade to RC29?
Or is that obsolete now?
Click to expand...
Click to collapse
That's actually explained in step 3.
3.) Download DREAIMG.nbh and put copy to the phone (don't put in a folder) http://bit.ly/wfAOO
That file is the RC29. Good looking out though.
Hi! Good!!
When the phone reboots, you can hold home and power to boot into cyanogen. There is an option to upgrade from ext2 to ext3.
Click to expand...
Click to collapse
What recommends = ext2 or ext3
This partition is not created = linux-swap (32 MB)
Saludos!
OK .. I keep getting the same result.
When I restart the phone and the grey bootload screen comes up, it does a check and replies with "not allow" Anyone know what to do here?
Build number: dream_stg user 1.1 STG-RC8 128394
Hey youneek great guide But could you put a warning for the flashing of haykuro's SPL? The SPL has a chance of bricking your phone if you don't have the latest radio and a PVT board. Even if you have both of those your phone can still be bricked Mind putting that up there for others? Thanks!
youneek said:
mount -o rw /dev/block/mmcblk0p2 /system/sd
cd /system/sd
rm -r *
Click to expand...
Click to collapse
does the /system/sd folder exist in console if you don't do this first:
mount system
and no need to 'cd' .. simply do:
rm -r /system/sd/*
if you are looking to delete everything on the second partition
great guide - if this was out begore I started I would of been running HERO with the quickness.
But still im glad i learned the hard way now i can get myself out of tuff situations
this is a great tutorial.
i also suggest to give people the option on what spl to flash. i prefer the hard. that new special one is dangerous for noobs
elzee said:
OK .. I keep getting the same result.
When I restart the phone and the grey bootload screen comes up, it does a check and replies with "not allow" Anyone know what to do here?
Build number: dream_stg user 1.1 STG-RC8 128394
Click to expand...
Click to collapse
What step are you on elzee?
alritewhadeva said:
Hey youneek great guide But could you put a warning for the flashing of haykuro's SPL? The SPL has a chance of bricking your phone if you don't have the latest radio and a PVT board. Even if you have both of those your phone can still be bricked Mind putting that up there for others? Thanks!
Click to expand...
Click to collapse
Excuse me. I'm just a newbie and going to buy a G1. You said G1 may be bricked during update without a PVT board. How can I check what the board is to avoid? and what's HardSPL?? Thanks a lot.
elzee said:
OK .. I keep getting the same result.
When I restart the phone and the grey bootload screen comes up, it does a check and replies with "not allow" Anyone know what to do here?
Build number: dream_stg user 1.1 STG-RC8 128394
Click to expand...
Click to collapse
Are you formatted to FAT32?
youneek said:
What step are you on elzee?
Click to expand...
Click to collapse
Youneek thanks for your reply,
Always at the step where I have downloaded the dreamimg file to the SDCard > shutdown the phone > then restart it holding the camera and power on buttons.
The grey 'bootloader' screen comes up, does a configuration check then flashes up the "not allow" message and dumps to the multi-coloured screen. At that point I have to pull the battery out to restart.
I'm going to go out today and purchase another SDCard. This one is a Sandisk 1mg card and I've read that certain Sandisk cards will not comply with 'rooting' instructions.
Cheers, elzee
milesukaoma2010 said:
Are you formatted to FAT32?
Click to expand...
Click to collapse
Yes.
I'm going out to buy another SD Card to see whether it makes any difference.
Cheers, elzee
I have most of the important tutorials all up at 1 spot... includes all this and also how to do your splash screen and more... check it out... scan the barcode for the url... (no spamming now )... enjoy! plenty of files for everyone....
Hey guys, if you've read around this forum, you must be familiar with the infamous bricked eMMC problems. This, sadly, is a hardware issue, and once it's bricked, you have no choice but to get the eMMC replaced by a professional. Following the popular saying, "Prevention is Better Than Cure", here are a few tips to prevent the eMMC chips from burning
=> Do not download multiple apps at once from the market. Even two simultaneous apps can screw your phone up.
=> Never Use the "UPDATE ALL" feature from the market. Update each app separately.
=> When you flash a new ROM, restore your apps using titanium backup before adding a Google Account. This will prevent the market from restoring all your apps at once.
=> NEVER EVER PULL THE BATTERY This is very important. Pulling your battery out is the most prominent cause of eMMC bricks. Use alternatives like -
=> Use ADB Commands to reboot into recovery
=> Press the Volume up, Volume Down and Power buttons together to reeboot the phone. In a bootloop, take off the battery cover (without pulling the battery) and press the buttons. The phone will turn off for 2-3 seconds before it turns back on. That's your window. Pull the battery in this time.
=> If you absolutely have to pull the battery, re-insert it at least 30 seconds later.
ADB Commands
ADB Commands
You'll obviously need ADB on your PC, so download and extract the adb & fastboot onto your PC which you'll see in a link in my signature. Ensure that you have HTC drivers on your PC if not also download and install the link in my signature.
Plug phone into PC by USB cable.
Then fire up a CMD on your PC, go to directory where you put adb and issue the command
Code:
[B][COLOR="Blue"]adb devices [/B][/COLOR] [COLOR="YellowGreen"] ---- what is the result?[/COLOR]
If your device appears to be recognised that's good, so next try
Code:
[COLOR="Blue"][B]adb reboot recovery[/B][/COLOR]
[B][COLOR="YellowGreen"]OR[/COLOR] [/B]
[COLOR="Blue"][B]adb reboot bootloader[/B][/COLOR]
I just purchased a new desire s. Is there still a chance that i will get a faulty eMMc chip?
yes, sadly there is.
Run this command in the terminal app or ADB
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
Post the result. If it's M4G2DE, your with us, faulty eMMC
Nice guide. However, where is it confirmed that only M4G2DE chips are faulty? And if they are, surely not all of them have the fault. Didn't someone report the failure with the other chip too? I have the M4 chip, I've updated many apps at a time, pulled battery numerous times (inserted immediately as well), but never had any issues. I guess it could be safe to say there is no way to actually know for sure which chip is faulty and that everyone should follow this guide regardless.
djsubtronic said:
Nice guide. However, where is it confirmed that only M4G2DE chips are faulty? And if they are, surely not all of them have the fault. Didn't someone report the failure with the other chip too? I have the M4 chip, I've updated many apps at a time, pulled battery numerous times (inserted immediately as well), but never had any issues. I guess it could be safe to say there is no way to actually know for sure which chip is faulty and that everyone should follow this guide regardless.
Click to expand...
Click to collapse
good argument...will keep that in mind.
ben_pyett said:
ADB Commands
You'll obviously need ADB on your PC, so download and extract the adb & fastboot onto your PC which you'll see in a link in my signature. Ensure that you have HTC drivers on your PC if not also download and install the link in my signature.
Plug phone into PC by USB cable.
Then fire up a CMD on your PC, go to directory where you put adb and issue the command
Code:
[B][COLOR="Blue"]adb devices [/B][/COLOR] [COLOR="YellowGreen"] ---- what is the result?[/COLOR]
If your device appears to be recognised that's good, so next try
Code:
[COLOR="Blue"][B]adb reboot recovery[/B][/COLOR]
[B][COLOR="YellowGreen"]OR[/COLOR] [/B]
[COLOR="Blue"][B]adb reboot bootloader[/B][/COLOR]
Click to expand...
Click to collapse
can you provide me an instruction on what to type in cmd for me to go to the directory where my ADB is.. for example in local disk D and inside a folder named ADB.. what should i type in cmd? before typing adb devices?
yerfdes said:
can you provide me an instruction on what to type in cmd for me to go to the directory where my ADB is.. for example in local disk D and inside a folder named ADB.. what should i type in cmd? before typing adb devices?
Click to expand...
Click to collapse
You need to "cd" to the directory where your Android SDK is installed, so eg if it is installed at D:\android-sdk then:
Code:
D:\
cd "\android-sdk\"
And then
Code:
cd "platform-tools"
good advice on titanium backup, just after activating my google account on my DS it download all my installed apps. then my phone hangs.
djsubtronic said:
You need to "cd" to the directory where your Android SDK is installed, so eg if it is installed at D:\android-sdk then:
Code:
D:\
cd "\android-sdk\"
And then
Code:
cd "platform-tools"
Click to expand...
Click to collapse
whoa!! im a total noob here.. should i install first android sdk and can you explain to me what is platform tools??
djsubtronic said:
Nice guide. However, where is it confirmed that only M4G2DE chips are faulty? And if they are, surely not all of them have the fault. Didn't someone report the failure with the other chip too? I have the M4 chip, I've updated many apps at a time, pulled battery numerous times (inserted immediately as well), but never had any issues. I guess it could be safe to say there is no way to actually know for sure which chip is faulty and that everyone should follow this guide regardless.
Click to expand...
Click to collapse
Sadly, in my other thread (in which i collected info), only M4G2DE chips came faulty. I never even saw another chip, maybe that's the only one. I've pulled many times battery too, (but NEVER quick-reinserted) and on the first day of XTC Clip S-off, my phone turned off after i tried downloading 2 apps at once. I had nothing, just S-off, i battery pull made the phone work.
shrome99 said:
yes, sadly there is.
Run this command in the terminal app or ADB
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
Post the result. If it's M4G2DE, your with us, faulty eMMC
Click to expand...
Click to collapse
**** Got M4G2DE so this means that i can't pull the battery? right?
yerfdes said:
whoa!! im a total noob here.. should i install first android sdk and can you explain to me what is platform tools??
Click to expand...
Click to collapse
Yes you need to install the Android SDK which includes ADB. You only need to install the basic package and nothing else. Platform-tools is a folder created within the SDK folder where the executables for tools such as ADB are located.
---------- Post added at 04:18 PM ---------- Previous post was at 04:16 PM ----------
shrome99 said:
Sadly, in my other thread (in which i collected info), only M4G2DE chips came faulty. I never even saw another chip, maybe that's the only one. I've pulled many times battery too, (but NEVER quick-reinserted) and on the first day of XTC Clip S-off, my phone turned off after i tried downloading 2 apps at once. I had nothing, just S-off, i battery pull made the phone work.
Click to expand...
Click to collapse
I just pulled and reinserted my battery today again. Probably done it a 100 times now. No issue.
jullejul said:
**** Got M4G2DE so this means that i can't pull the battery? right?
Click to expand...
Click to collapse
As I posted earlier, follow this guide whichever chip you have, just to be safe. As there is no real conclusive evidence as to which models/chips have the fault.
I will check later to see what chip I have cos I have pulled out the battery several times ..in fact it seems to be my saving grace whenever my phone hangs orthe volume down + power button doesn't work
Sent from my HTC Desire S using XDA App
Guys, ALL m4g2de chips are not faulty. Only a few unluck ones are. Sadly, there's no way of finding out if yours is faulty or not. Just follow the guide to be safe
shrome99 said:
Guys, ALL m4g2de chips are not faulty. Only a few unluck ones are. Sadly, there's no way of finding out if yours is faulty or not. Just follow the guide to be safe
Click to expand...
Click to collapse
Okay thanks
Sent from my HTC Desire S using XDA Premium App
lynxnoon said:
I will check later to see what chip I have cos I have pulled out the battery several times ..in fact it seems to be my saving grace whenever my phone hangs orthe volume down + power button doesn't work
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
It does work. You need to hold all three buttons down together. Hold down the volume buttons first then finally press and hold down the power button.
I have a about 3 months desire s, and using command
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
It tells me SEM04G....
Omg. You're probably on a perfect eMMC chip. Have you ever pulled battery?
will read this for sure. thx for the guide mate
OK, I've read a lot of comments about people having trouble installing MoDaCo clockworkmod, or even turning their devices S-off. But my guide is going to go step though step of how to turn your device into a lean, mean killing machine. It took me days to accomplish this when i first got my device, hopefully this will take you under 30 minutes! I'm a junior member, i know, so cut me some slack, PLEASE.
WARNING AND DISCLAIMER: I AM NOT RESPONIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE. FLASH AT YOUR OWN RISK, EVEN IF IT FALLS APART IN YOUR HAND, OR BECOMES GODLY FAST!
1. The first thing we need to do is turn S-OFF for your mytouch 4g slide. It is probably the easiest thing to do, other then installing a rom on your device.
a. You will need to download the usb drivers for your phone, DON'T SKIP THIS STEP, or you'll wonder why your phone isn't discovered by the software. You can find those drivers at this website right here:
http://www.htc.com/managed-assets/support/software/htc-sync/setup_3.0.5579.exe
After you have that software installed, plug in your phone, and give it a couple minutes to install all the correct drivers for your device, then make sure you go to the bottom right of the computer and exit out of that software, it can't be running when your trying to S-OFF your device. Now I dont think you have to have the fastboot drivers installed either, but why not, lets go ahead and download those files and get those installed too.
http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
After you have those installed, its now time to move on.
b. Now thanks to unrevoked and AlphaRev and their team, you will go to their site at http://revolutionary.io/ and you will scroll down and click on Download for Windows (If you can take everything I'm saying and do the linux version, right on!) at that moment a download box will appear, but do not download those files, download the files from this website http://www.megaupload.com/?d=BP2E3ZQ3 .But you will need to enter some information in the box below after you click on windows download, just remember, you don't need those files. Your operating system, device, HBOOT version, and serial number. Your HBOOT version can be found by taking your device, going to apps, settings, power, and uncheck fast boot, then power it off, i always power it off and then pull the battery out, makes me feel safer...and soon as its off, holding the volume down button, camera button, and power button all at the same time. You'll then see a screen with the android bots on the bottom are rolling on skateboards. At the top should be your HBOOT version, and there is only one option on the site, so hopefully your in luck! For your serial number,take the battery out from this screen, don't push any buttons, and on the sticker under the battery, your serial number will be there starting with HT--- or power your device back on, then go to apps, settings, about phone, phone identity, and wala, your device serial number. After you enter all that information into the site, it will generate you a beta key, YOU NEED THAT IN ORDER TO S-OFF AND ROOT YOUR DEVICE!! So write it down somewhere, copy and paste in word, do what you do
c. Now we have everything downloaded, we have our beta key, its time to get to work!
d. The file you downloaded from megaupload, "MT4GS-ADB-WINDOWS" you need to extract that file into a folder on your desktop. Make sure you open the folder mt4gs-adb, and extract the files out of the folder, so you should have 12 items in your folder on the desktop, not just a folder in a folder! I created a folder called "root mt4gs". You want all the files in one location. After there all extracted, open your folder on the desktop. On your phone, go to apps, settings, applications, development, and click on usb debugging and make sure the check mark is blue on the right. Now plug your phone into the computer.
Now in your "root mt4gs" folder, double click on revolutionary. At that moment it should ask you for that beta key i told you to save. Go ahead and enter that now (its case sensitive). Let the software run for a couple minutes....
Now after it says S-Off, your halfway there!! Your HBOOT will now say 1.44.1107. That way you know its done! It will ask you to install clockwork recovery mod, say NOOOO, it has hella problems. It gave me problems when i said yes the first time, i'll show you another way.
e. At this moment, we're going to install clockwork recovery v4.0.0.9, thanks to Paul O'Brien/MoDaCo, the gods lol. First, turn your device off/pull the battery out, thats what i do. Then hold volume down button, camera button, and power button at the same time. It should show you the skateboarding androids, and at the top it should say -Revolutionary- in purple. If it doesn't, don't continue, retry all steps or message me. Then plug your phone into the computer, and using the power button as the selection button, push the power button as your highlighted over FASTBOOT. It should say FASTBOOT USB at the top in red now.
Now believe it or not you already have the file you need in your "root mt4gs" folder. Your now going highlight all the files in your "root mt4gs" folder to the root of your hard drive. Click on My computer, double click on your c: drive, and paste those files right on there, do not copy the folder, or put these files in a folder!! Now your going open a command prompt. {Hold the windows key and tap r}. Then type "cmd" without the parenthesis and it should open up a black box.
Now type cd\
Your command prompt should now just say c:\> thats what you want it to say
Now your going to type adb.exe
You should see a whole bunch of words flash on the command prompt, the last couple words should say "bug tags are printed." That means your right on track.
From here, you are going to type in fastboot devices
it should have the serial number of your device and the word fastboot right next to it!
Now, here comes the tricky part that i got stuck at, but i know you can do it! Now this will work if you put the files exactly where i told you to put them. you now will type fastboot flash recovery c:\clockworkmod.4.0.0.9.img
it should say " sending 'recovery'
okay
writing recovery'
okay
finished. total time: (mine is 10.400s)
Now to make sure it's intalled, on your phone, click power button and you should now see fastboot, recovery, factory reset, simlock, and imagecrc as options, use your volume button to go down to recovery, and click power button.
You should now see clockworkmod recovery 4.0.0.9.
f. Now lets put superuser on your device so you can be free!
click on this file and download it, DO NOT EXTRACT IT
http://downloads.androidsu.com/superuser/su-2.3.6.3-efgh-signed.zip
Now after you have downoaded that file, on your phone, use your trackpad, and scroll down to "mounts and storage"
then scroll down to mount usb storage. now you should be able to put files on your sd card, make sure you put it on the root of your sd card, not in a folder, it doesn't matter, but i prefer it!.
Now unmount on your phone by clicking the option, click go back, and then scroll down to "install zip from sdcard" and click on it, then click "choose zip from sdcard". Find that file we just put on there "su-2.3.6.3-efgh-signed.zip", and click on it, then click yes. Now click on go back, and click reboot system now!
Now if you want to stay stock, your done, your rooted, so now just install root checker, and busybox, and your good to go, if you want to do some roms, keep on reading.
Now you cross your fingers, and grab a soda, because we're 75% done!
g. Now is the easy part, all you do now is download the roms from other developers, copy them to your sdcard, then turn off the phone, hold volume down, camera and power button, go into recovery with using vol up and down buttons as the selector, and the power button to confirm your option. As you enter clockwork mod, you can then go follow the directions of the developer as to wipe certain sections, and how to install there roms/patches. YOUR DONE
If you have any questions, please let me know, also I didn't make ANY of this software, this guide just has every link to get you everything you need at one spot. I also have the original file to make your phone completely stock, so if you need that, let me know and I'll upload that and send the link out.
If you want to donate to me, donate to all the other og's first!
Thanks to
jdmarko
unrevoked
alpharev
paulobrien
MoDaCo
and if I forgot you, let me know. thanks!
Now this is how you give a tutorial!!! If i had some extra cash i would totally donate bro! I was trying to install 4.0.0.9 for two days from the dude that made its site and his directions were not thorough enough. Thanks dude.
Oh dude no worries, a thanks is just as good. I appreciate it, it took me days, so I'm happy I could help brotha!
Sent from my MyTouch 4G Slide using xda premium
Going to try! :-D fingercross tor me!
Thank you very much, very good write up.
Geko90 said:
Going to try! :-D fingercross tor me!
Click to expand...
Click to collapse
Fingers are crossed, the tutorial has proven effective so far, so hope all goes well, tell me how it goes!
poken1151 said:
Thank you very much, very good write up.
Click to expand...
Click to collapse
Thanks! I'm assuming it worked then?!
Superuser wont install for me, Error in /sdcard/su-2.3.6.3-efgh-signed.zip
Status 0
I wiped cashe/ dalvic downloaded several times No good.
correct hboot, s=off
just wont flash SU ???
phil0sophic said:
Superuser wont install for me, Error in /sdcard/su-2.3.6.3-efgh-signed.zip
Status 0
I wiped cashe/ dalvic downloaded several times No good.
correct hboot, s=off
just wont flash SU ???
Click to expand...
Click to collapse
Ok let's figure this out.. on step f, you did unmount your sd card, right? I haven't dealt with this problem before so if I ask a stupid question, I'm just trying to solve this. Also you don't need to wipe anything to install superuser, so that could be the problem also, so reboot ur fone, and let's try step f again! Keep me updated please!
phil0sophic said:
Superuser wont install for me, Error in /sdcard/su-2.3.6.3-efgh-signed.zip
Status 0
I wiped cashe/ dalvic downloaded several times No good.
correct hboot, s=off
just wont flash SU ???
Click to expand...
Click to collapse
It took a lot of us several attempts to flash the superuser zip. The 4.0.0.8 recovery isn't the greatest. Keep trying until it installs and you get root. Then upgrade to the modaco 4.0.0.9 recovery right away. It's not perfect either but it fixes a LOT of the issues known with 4.0.0.8.
And a comment to the OP, this is an incredibly helpful walkthrough! If only people would actually search and find this before posting new threads like "how do i root" and all that crap.
Thank you.
Great job on this and thanks for your work. I wish I would have had this tutorial when I did mine.
Sent via my talk enabled Galaxy Tab using XDA premium.
Techlvr said:
Great job on this and thanks for your work. I wish I would have had this tutorial when I did mine.
Sent via my talk enabled Galaxy Tab using XDA premium.
Click to expand...
Click to collapse
Thanks, I had a lot of trouble doing mine the first time, and I went back to stock, typed this and gave my wife my phone and she went step by step and completed it. So it can't be that hard!
Does this add an app to reboot from as the standard cwm does?
phil0sophic said:
Does this add an app to reboot from as the standard cwm does?
Click to expand...
Click to collapse
An app to reboot from? Not understanding the question throughly... In this cwm, it has the option to reboot system as every other cwm that I've used has. But an app... I do not have an app though...hope I answered your question!
numbaoneforeva said:
An app to reboot from? Not understanding the question throughly... In this cwm, it has the option to reboot system as every other cwm that I've used has. But an app... I do not have an app though...hope I answered your question!
Click to expand...
Click to collapse
OK ill reexplain is there an icon in the apps drawer for CWM to select to reboot etc. because it didnt install one on the MT4Gslide as on my MT4G.
I know something is goofy as SU wouldnt flash, I had to install the new version from the market.
phil0sophic said:
OK ill reexplain is there an icon in the apps drawer for CWM to select to reboot etc. because it didnt install one on the MT4Gslide as on my MT4G.
I know something is goofy as SU wouldnt flash, I had to install the new version from the market.
Click to expand...
Click to collapse
Oh, now i understand. No there isn't. I don't have one at all, as soon as I installed clockworkrecovery, and superuser, I flashed undeads rom on there. And I've been reading that superuser is being buggy when installing it on this phone through cwm...I'll look into that tonight, see if i can find the root cause.
Thanks...This is my wifes phone, she just upgraded from a CLIQ (one of the two people that loved blur)she likes my MT4G and wanted a KBD so here we are....
I want to change the lock ring so need root for the wonderful majic you dev's do....
phil0sophic said:
Thanks...This is my wifes phone, she just upgraded from a CLIQ (one of the two people that loved blur)she likes my MT4G and wanted a KBD so here we are....
I want to change the lock ring so need root for the wonderful majic you dev's do....
Click to expand...
Click to collapse
Well your at the right forum to get you started. And thanks! This is my first post so I'm trying!
Sent from my MyTouch 4G Slide using xda premium
phil0sophic said:
OK ill reexplain is there an icon in the apps drawer for CWM to select to reboot etc. because it didnt install one on the MT4Gslide as on my MT4G.
I know something is goofy as SU wouldnt flash, I had to install the new version from the market.
Click to expand...
Click to collapse
You probably just have to download ROM Manager from the market, I think that's what you're referring to. There isn't a whole lot of support for our device in ROM manager right now, however, and I haven't checked to see if the "reboot into recovery" works. Go into settings > power > and uncheck fastboot. Then, shut down your phone, wait 10 seconds, hold down the volume down button and turn your phone back on. That'll get you into recovery. Did you get superuser to install? Are you rooted?
Mine won't switch from "revolutionary" in purple at the top to "fastboot" at the top.
It says fastboot USB about 6 lines down, but that's it.
When I type "fastboot devices" it errors and says:
'fastboot' is not recognized as an internal or external command, operable program or batch file.
anyone know what's up?
Im not stupid and i no how to read, just with this phone being kinda hard it took awhile to find the correct guide to downgrade and root.
i decided to follow this one, being updated this month
http://wiki.cyanogenmod.com/wiki/TM...l_Update_Guide#Rooting_the_TMobile_myTouch_4G
is this the correct one to use, cause i dont want to use the visionary app. heard that can be bad news
I also checked the emmc chip thru terminal emulator. and were good to go on that.
Ive already downgraded mt4g back to froyo.
but when copy/ paste commands for perm root, s off, h boot, when i paste line for su
it says failed, file is read only
everything still good with phone, i just want root and cwm
any help, would be appreciated and thanked
1) There's nothing wrong with Visionary or gfree. Don't be afraid.
2) cd to the directory of the file you're trying to run and chmod 777 the file. For instance, if the file was root.sh
chmod 777 root.sh
i remembered reading somewhere that using the visionary app can cause problems with lots of aggravation afterward.
and the phones not mine, im rooting it for a friend. ive rooted quite a few devices already but this is my first htc.
origionaly i ran the command at
C:\android sdk\platform-tools
all the command i had no problem with except when trying to push su
so are you saying i should change to
cd c:\android sdk\platform-tools\su>adb push su /sdcard/ ???
orginally i got back
failed to copy 'su' to '/sdcard//su': read-only file system
is it refering to my comp or android as read only file system?
trevor7428 said:
i remembered reading somewhere that using the visionary app can cause problems with lots of aggravation afterward.
and the phones not mine, im rooting it for a friend. ive rooted quite a few devices already but this is my first htc.
origionaly i ran the command at
C:\android sdk\platform-tools
all the command i had no problem with except when trying to push su
so are you saying i should change to
cd c:\android sdk\platform-tools\su>adb push su /sdcard/ ???
orginally i got back
failed to copy 'su' to '/sdcard//su': read-only file system
is it refering to my comp or android as read only file system?
Click to expand...
Click to collapse
I repeat, Visionary is fine.
Android.
I just used visionary today to root my wife's phone. I had to go through the whole downgrade process to get back to 2.2, and everything went very smooth. Now running JB from the codename thread and couldn't be happier with it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Battery life is shaky on that rom, if you want to get the most out of your phone with jellybean, flash the CM10 port by 0.0 or Dark JellyBellyG1. Make sure to clear your batt stats before flashing darkjellybelly because codenamed messes with them.
THEindian said:
Make sure to clear your batt stats before flashing darkjellybelly because codenamed messes with them.
Click to expand...
Click to collapse
Unnecessary if he does a full wipe, which he should do between flashes anyway.
estallings15 said:
Unnecessary if he does a full wipe, which he should do between flashes anyway.
Click to expand...
Click to collapse
Hmm, a full wipe didn't work for me. I got off Codename and went back to insertcoin which i KNOW has awesome battery life and got mediocre battery life, not really different from Codename. Don't even nag me about the full wipe because I did it! lol.
THEindian said:
Hmm, a full wipe didn't work for me. I got off Codename and went back to insertcoin which i KNOW has awesome battery life and got mediocre battery life, not really different from Codename. Don't even nag me about the full wipe because I did it! lol.
Click to expand...
Click to collapse
Flash at 100% and drain it down then recharge. Battery life should normalize after that.
Downgrade and Root Guide..!
this is how i did mine..!
http://minus.com/mu9vZ3P38/
:good:
So I still don't no what I'm doing wrong. I've successfully downgrading.and when using visionary.apk. it says unknown user root. After entering su in terminal emulator. I've tried visionary11 and 14 and a plusversion. All with same results. R/W is checked and hit temp root
I've never had this much trouble rooting any tab or phone
trevor7428 said:
So I still don't no what I'm doing wrong. I've successfully downgrading.and when using visionary.apk. it says unknown user root. After entering su in terminal emulator. I've tried visionary11 and 14 and a plusversion. All with same results. R/W is checked and hit temp root
I've never had this much trouble rooting any tab or phone
Click to expand...
Click to collapse
Enable usb debugging in settings and reboot between every attempt with visionary.
estallings15 said:
Enable usb debugging in settings and reboot between every attempt with visionary.
Click to expand...
Click to collapse
Enable usb debugging in settings and reboot between every attempt with visionary
Click to expand...
Click to collapse
I already have USB debugging enabled, fastboot off. And I restart pull out battory, and even tried uninstalling visionary and reinstaling. There has to be something I'm missing. And just to verify I did downgrade to 2.2.1
trevor7428 said:
I already have USB debugging enabled, fastboot off. And I restart pull out battory, and even tried uninstalling visionary and reinstaling. There has to be something I'm missing. And just to verify I did downgrade to 2.2.1
Click to expand...
Click to collapse
Do a factory reset maybe, just to clean the slate.
factory reset is your best bet dude..! save all your data from your memory card onto your computer or something and format your memory card as well. then do a complete factory reset. it really does solve issues. but ofcourse, it's always a pain recustomizing your phone but yea...!
mokee92 said:
factory reset is your best bet dude..! save all your data from your memory card onto your computer or something and format your memory card as well. then do a complete factory reset. it really does solve issues. but ofcourse, it's always a pain recustomizing your phone but yea...!
Click to expand...
Click to collapse
Hell ya I hate factory reset without root lol. I was hoping I was doing one tiny lil thing wrong. Which was a super easy fix. Lol well if anyone can think of anything else. Let me no. Its my buddies phone. So can't try now. Any other ideas will be thanked too
Pressed the home button while using Snapchat, phone froze, had to hard reset it, phone got stuck in constant Google logo bootloop. Getting a replacement shipped out...but I have a video I recorded yesterday morning that never backed up on Photos, any possible way to save it? Someone mentioned an ADB method..? But with my little research I think you need to factory reset the phone for that, which would make this method a waste as I need to get this video off it.
I never rooted this phone, I didn't unlock the bootloader. I did turn on developer settings. That's all I know regarding that.
Other information regarding the fastboot screen: Boot-slot: a, Console: DISABLED, Secure Boot: PRODUCTION, Device is LOCKED.
I've turned it off and on multiple times, same thing. Rebooted it during loops, or at least tried to, same thing. Went into fastboot mode from loops, pressed start, same thing. Went into fastboot mode from phone off, same thing. I don't know what else to do. There is no way to clear a memory cache apparently. And I am sort of n00bish in this world.
Anyways, what could I possibly do to save this video, or to fix my phone out of this bootloop to take the video off the right way before my replacement comes in? Anyway to do either of that via 'ADB', some lowkey program I don't know about that can rip the entire phone's data onto some type of file I can decrypt, a program like Recuva that will find the file(s) for me and yank them out, etc? I know there has to be somebody out there with the skills or capabilities to do something like this... I hope. Please help out and let me know, thanks.
If you could do something like that with a locked bootloader / unrooted device then all security for Android would be a sham. I'd be very discouraged if someone could hack into a secure device and pull out information such as pictures, phone numbers, messages etc.
If it is locked, you are done. It's encrypted. If it were unlocked you could easily get it off the phone.
Well, I'm not feeling optimistic at all now. So there is 0, nada, nothing I can do to save this video/file or fix my phone? All because the device decided to randomly get stuck in this bootloop, I am absolutely screwed?
Unless you can get it to boot up then I do believe you are out of luck. You can't get into recovery menu?
Sent from my Pixel using XDA-Developers Legacy app
bobby janow said:
Unless you can get it to boot up then I do believe you are out of luck. You can't get into recovery menu?
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
Fastboot > Recovery mode > No command screen > Power button hold + Volume up tap > Android Recovery screen with Reboot system now, Reboot to bootloader, Apply update from ADB, etc?
If that's what you mean, I can get there, I'm there right now.
czbwoi said:
Fastboot > Recovery mode > No command screen > Power button hold + Volume up tap > Android Recovery screen with Reboot system now, Reboot to bootloader, Apply update from ADB, etc?
If that's what you mean, I can get there, I'm there right now.
Click to expand...
Click to collapse
Sorry afk. Yes, that is exactly where you want to be. Try an adb sideload of the latest OTA or even the last full image. I do believe you can sideload that but if not then the OTA. You might be able to recover that way. If something got corrupt then the sideload might fix it. Or is there an option to clear cache? I think there is, you can try that first.
bobby janow said:
Sorry afk. Yes, that is exactly where you want to be. Try an adb sideload of the latest OTA or even the last full image. I do believe you can sideload that but if not then the OTA. You might be able to recover that way. If something got corrupt then the sideload might fix it. Or is there an option to clear cache? I think there is, you can try that first.
Click to expand...
Click to collapse
No option to clear cache, the rest of the options are: Apply update from SD card, Wipe data/factory reset, Mount /system, View recovery logs, Run graphics test, Power off.
I have no idea how to sideload an OTA or image to try to fix this...if you could point it out to me step by step, literally, I'd appreciate it.
czbwoi said:
No option to clear cache, the rest of the options are: Apply update from SD card, Wipe data/factory reset, Mount /system, View recovery logs, Run graphics test, Power off.
I have no idea how to sideload an OTA or image to try to fix this...if you could point it out to me step by step, literally, I'd appreciate it.
Click to expand...
Click to collapse
Don't have directions atm for sideload online but the way it works is you download the OTA from here: https://developers.google.com/android/ota Scroll down to Pixel latest U build 7.1.1. Download it and place it in your fastboot android sdk folder, I put it in the platform-tools so it's easy. Then click apply update from sd card by highlighting it with the vol keys and then power key to select. It will tell you what to do. I forgot exactly but it's something like "adb sideload <ota.zip> whatever the name is and then let it go. It will take about 10 min and after it's all done, highlight the reboot option. Power key and reboot. Hopefully that should fix it. If not, sorry I'm all out of ideas. Well other that adb sideload the full image although someone will have to verify if that would work.
bobby janow said:
Don't have directions atm for sideload online but the way it works is you download the OTA from here: https://developers.google.com/android/ota Scroll down to Pixel latest U build 7.1.1. Download it and place it in your fastboot android sdk folder, I put it in the platform-tools so it's easy. Then click apply update from sd card by highlighting it with the vol keys and then power key to select. It will tell you what to do. I forgot exactly but it's something like "adb sideload <ota.zip> whatever the name is and then let it go. It will take about 10 min and after it's all done, highlight the reboot option. Power key and reboot. Hopefully that should fix it. If not, sorry I'm all out of ideas. Well other that adb sideload the full image although someone will have to verify if that would work.
Click to expand...
Click to collapse
Just sideloaded the latest OTA with the help of a friend, and no luck. Same old stuff. And I think sideloading an image would require the bootloader to be unlocked which would require a factory reset...
Here's another thing that crossed my mind, have any of you ever used EaseUS MobiSaver for Android? It's a tool that allows you to recover deleted files from your phone, similar to Recuva and hard drives. I used it before on my parents' Galaxies, this program is from circa 2014 though so I don't know if it would have much success on a new phone like this...but you never know?
For it to work you need to have your phone on (derp) and have it rooted. Here's the tricky part...if you erase your hard drive and use a tool like Recuva, even though you erased your drive the remnants are still "there" and files are recoverable with a tool like that. Do you think that the same concept would work with phones and EaseUS MobiSaver? Say that I factory reset the phone, set it up as a new device and don't transfer over any backup, I root it, and run said program to scan the deep contents of the phone's hard drive for old data. Do you think this will work in any way possible, like how regular hard drives that got erased work, or is the phone world completely different and incomparable?
EaseUS will not work on a factory reset. You can't recover anything.
bobby janow said:
EaseUS will not work on a factory reset. You can't recover anything.
Click to expand...
Click to collapse
Well then what about programs like these: https://youtu.be/iPCoyRpMrqw?t=58s
http://www.jihosoft.com/recover-data/recover-data-after-factory-reset.html
http://androiddatarecovery.co/recover-data-after-factory-reset-from-android-mobile/
Some people say they have had some success with these...
Let us know. I'll wager you won't get anything back on the Pixel. Good luck.
czbwoi said:
Pressed the home button while using Snapchat, phone froze, had to hard reset it, phone got stuck in constant Google logo bootloop. Getting a replacement shipped out...but I have a video I recorded yesterday morning that never backed up on Photos, any possible way to save it? Someone mentioned an ADB method..? But with my little research I think you need to factory reset the phone for that, which would make this method a waste as I need to get this video off it.
I never rooted this phone, I didn't unlock the bootloader. I did turn on developer settings. That's all I know regarding that.
Other information regarding the fastboot screen: Boot-slot: a, Console: DISABLED, Secure Boot: PRODUCTION, Device is LOCKED.
I've turned it off and on multiple times, same thing. Rebooted it during loops, or at least tried to, same thing. Went into fastboot mode from loops, pressed start, same thing. Went into fastboot mode from phone off, same thing. I don't know what else to do. There is no way to clear a memory cache apparently. And I am sort of n00bish in this world.
Anyways, what could I possibly do to save this video, or to fix my phone out of this bootloop to take the video off the right way before my replacement comes in? Anyway to do either of that via 'ADB', some lowkey program I don't know about that can rip the entire phone's data onto some type of file I can decrypt, a program like Recuva that will find the file(s) for me and yank them out, etc? I know there has to be somebody out there with the skills or capabilities to do something like this... I hope. Please help out and let me know, thanks.
Click to expand...
Click to collapse
You can often get ADB while it's booting. It just depends how far into the boy process is made it. I would power it up and see if you can ADB pull the file.
TCPDump said:
You can often get ADB while it's booting. It just depends how far into the boy process is made it. I would power it up and see if you can ADB pull the file.
Click to expand...
Click to collapse
My friend was able to give it ADB commands on the fastboot/recovery menu, we sideloaded the latest OTA like that to see if it would fix it. What are you describing though, how would I be able to do that? Do you have any instructions or links on what to do? I don't know the file name for instance. The last video before that one was named VID_20170104_011325.mp4, I don't know how to find out the name of the next video file to even try to attempt what you're saying, unless you know of some way...
czbwoi said:
My friend was able to give it ADB commands on the fastboot/recovery menu, we sideloaded the latest OTA like that to see if it would fix it. What are you describing though, how would I be able to do that? Do you have any instructions or links on what to do? I don't know the file name for instance. The last video before that one was named VID_20170104_011325.mp4, I don't know how to find out the name of the next video file to even try to attempt what you're saying, unless you know of some way...
Click to expand...
Click to collapse
Well, IF it had booted enough to mount storage and start the adb daemon then you would use adb shell to locate the file.
Example:
adb shell
cd /sdcard/DCIM/
ls -la
Assuming your filename is in there, it its name is VID_20170104_011325.mp4 then you could exit the shell and do this:
adb pull /sdcard/VID_20170104_011325.mp4
TCPDump said:
Well, IF it had booted enough to mount storage and start the adb daemon then you would use adb shell to locate the file.
Example:
adb shell
cd /sdcard/DCIM/
ls -la
Assuming your filename is in there, it its name is VID_20170104_011325.mp4 then you could exit the shell and do this:
adb pull /sdcard/VID_20170104_011325.mp4
Click to expand...
Click to collapse
Only place I can seem to enter adb commands is when I go to apply update from adb, and when I do so the only thing it responds to is adb devices and sideloading, presumably because that is all it allows me to do in that mode. When I enter adb shell I get error: closed