Related
YOU MUST HAVE ADB FOR THE MYTOUCH SLIDE SET UP BEFORE DOING THIS!!!!!!!!!! IF YOU DONT KNOW WHAT THAT IS DONT DO THIS!!!!! IF YOUR PHONE BRAKES NOT OUR PROBLEMS!!!!!
Download this package http://outboundlink.us/anxo/dr_ta_1...www.4shared.com/file/rbKZa2UB/Slide_Root.html
1. Unzip that file to the tools folder in your android sdk
2. In cmd cd into the tools folder of your android sdk
• CD\
• Cd androidsdk\tools
3. Boot into recovery (volume down and power, then select recovery)
4. Get the options on the screen in recovery (volume up and power)
5. run the update.zip it will fail
6. now in cmd type adb reboot recovery (don’t press enter)
7. in the recovery hit reboot system now( once it starts rebooting run that command rapidly untill back into recovery)
8. type adb devices(if it says nothing repeat the steps, if it says offline unplug it and then plug it back in, if it says recovery your fine)
9. once you get it to say your device and recovery do these commands
• adb push ota.zip /sdcard/update.zip (press enter)
• adb push slideroot.zip /sdcard (press enter)
10. type this comandin cmd adb push update.zip /sdcard (don’t press enter)
11. on the recovery menu hit apply update.zip and when you do that wait half a second and hit enter in cmd (if that dosent work try the loop way bye typing loop in to cmd wile booting into recovery and the crtl+c to end it when you see offline)(my way works better and mor of the times)
12. now you should be in the new recovery image if not start over
13. co to the partitions menu and hit mount /system
14. then go back and go to install any zip, chose zip from sdcard, and then select slideroot.zip
15. reboot
Thanks to eugene for the initial how-to
Thanks to chiefzreloaded
Thanks kingofyo1 for helping people with me
For the love of GOD I hope this works... I've been wondering why another way hasn't been found yet... trying this in a few minutes.
Are the files in step 1 the same from the original root thread? Should clarify that so people dont download it twice and confuse themselves. And just to be clear, we only need to push the two zips to the sd card...? F*ck it, gonna try it.
Uh, this method isn't going to work on a stock phone. The signature on the update.zip that contains the clockwork recovery will fail. The only reason choosing the update is working for you(jp) is because you've already flashed to the Engineering ROM.
The whole reason eugene's method works is because the phone reads the correct signature the ota.zip and then we push the update.zip with clockwork recovery RIGHT before it starts the update. Following your guide completely skips that part. So, again, won't work on stock.
Sorry, fermonkey. Hope you can get it.
Couldn't even waste time to try it on a stock phone...
Thanks for all the help and documentation on this guys!!
this doesnt work...
the update.zip fails
I was hoping somebody resigned it
yeah well the instructions if you go by them will overwrite the update.zip anyways. but eitherway itdoesnt work.. maybe more clarification is needed?
bhang said:
i was hoping somebody resigned it
Click to expand...
Click to collapse
its not signd wrong its that is has to be pushed through adb
sino8r said:
yeah well the instructions if you go by them will overwrite the update.zip anyways. but eitherway itdoesnt work.. maybe more clarification is needed?
Click to expand...
Click to collapse
updated try now
shinkinrui said:
Uh, this method isn't going to work on a stock phone. The signature on the update.zip that contains the clockwork recovery will fail. The only reason choosing the update is working for you(jp) is because you've already flashed to the Engineering ROM.
The whole reason eugene's method works is because the phone reads the correct signature the ota.zip and then we push the update.zip with clockwork recovery RIGHT before it starts the update. Following your guide completely skips that part. So, again, won't work on stock.
Sorry, fermonkey. Hope you can get it.
Click to expand...
Click to collapse
ya i got that i updated it with better instructions, and it was because the files needed to be pushed through adb the cant just be put on an sd card and flashed
still says no device found
I tried hit up arrow for repeat quick commands in cmd prompt but still nothing. If this works for someone, this will be way easier to root. it seems the device responses to adb because it will reboot into recovery with a cmd during the reboot but it cant find the device offline.
hmmm...! some progress was made! I got it to say offline but when I replugged it in... it says nothing. what next?
I guess I'll rinse and repeat...
fermunky said:
For the love of GOD I hope this works... I've been wondering why another way hasn't been found yet... trying this in a few minutes.
Click to expand...
Click to collapse
any luck with the new method? I got it to say device offline but replugging it produces nothing...
just curious... how do we know this will work? as anyone rooted with this method yet?
First of all, doesn't work on a stock Slide. Second, how is this process any easier? It's almost the same process as the other (working) method except you gave crappier directions.
-------------------------------------
Sent via the XDA Tapatalk App
So this method still relies on your phone being recognized by adb in recovery, right? If so, then no, I am sure I will have no luck what so ever.
Once froyo comes out, will there ever be another way developed to root, or will it always require adb recognition in recovery? Because I fear I'll never get rooted if thats the case.
Dude, seriously, this won't work on stock. There's no clarification needed. Yes, the update.zip is overwritten, but it's overwritten AFTER it reads the signature from the ota.zip. No offense but stop making people waste time on this.
-------------------------------------
Sent via the XDA Tapatalk App
Oh! It's staying in offline mode with this process... now just gotta unplug/replug to see if I get a recovery status in adb!... god I hope this works.!
Hi everyone, I have fixed the latest CM Recovery, files are attached below,
Thanks to defer from #teamdesire @freenode.
Download and flash with fastboot,
Code:
fastboot flash recovery recovery.img
There is also an alternative version which may work for people who get the black screen, please try the alternative version if the first one doesnt work
Worked great for me!
I wanted to test but after the upgrade to 2.1 is not an android I run mode fastboot...........
I tried to install this. All looked to be written OK.
I hold down vol up\down and power on.
The basic recovery menu appears. I select option 2. The screen now just goes black and I have to remove battery to get back into android. Do I actually need a file on the SD card for the CM menu to be displayed?
UK unlocked streak direct from dell - BB=00 - Rom= 4399
Thanks
be_vigilant said:
I tried to install this. All looked to be written OK.
I hold down vol up\down and power on.
The basic recovery menu appears. I select option 2. The screen now just goes black and I have to remove battery to get back into android. Do I actually need a file on the SD card for the CM menu to be displayed?
UK unlocked streak direct from dell - BB=00 - Rom= 4399
Thanks
Click to expand...
Click to collapse
No but you may need the alternative recovery I made, try that one instead.
Thanks for the quick response.
However I still get a black screen using the alt too.
When I flash 1.8.1.7 that loads up OK and I get the CM menu
I just get a black screen with both your fixed and alt versions.
I guess it works for some though. Thanks again mate.
first one works for me with the 2.1 rom
I did get black screen then I pressed volume key and power button..
if I pressed the power button while in the menu I got the black screen again, so repeated the volume then power to get the menu back
so if you get black screen try volume up or down and then power button,
of course the clockwork recovery is a great way of clearing the cache
pressing all the button (no camera button) you get blank screen
re-pressing all the button the screen reappears
but, me too, with a sim free 00 Streak, I can't do anythings, no menu, no update, nothings
be_vigilant said:
I tried .....
UK unlocked streak direct from dell - BB=00 - Rom= 4399
Click to expand...
Click to collapse
the same here
The 2 kernels I have available for recovery are for baseband 21, I would need a dump of stock recovery or boot image from 00 devices to get it working on other devices.
... Obviously its cosmetic, and I dont get my streak till monday, but can that be flipped to be right side up?
AdamG said:
Hi everyone, I have fixed the latest CM Recovery, files are attached below,
Thanks to defer from #teamdesire @freenode.
Download and flash with fastboot,
Code:
fastboot flash recovery recovery.img
There is also an alternative version which may work for people who get the black screen, please try the alternative version if the first one doesnt work
Click to expand...
Click to collapse
I dont understand what do it?When i must use it.
Hmm...
Been working with a trashed recovery partition for a few days.. No biggy, tried pulling off what was on recovery_1 and placing it on etc.. No luck..
But yeah, the first image did work for me (though nandroid failed, my filesystem is pretty trashed.) Do a bit of screwing around replacing files in the system directory and kill my system. I'd already 'fixed' the failed nandroid backup, so I go to restore it, only to see the standard recovery has somehow resurrected itself and clockwork was no longer on.
Magic I tell you.
kwaaq said:
Hmm...
Been working with a trashed recovery partition for a few days.. No biggy, tried pulling off what was on recovery_1 and placing it on etc.. No luck..
But yeah, the first image did work for me (though nandroid failed, my filesystem is pretty trashed.) Do a bit of screwing around replacing files in the system directory and kill my system. I'd already 'fixed' the failed nandroid backup, so I go to restore it, only to see the standard recovery has somehow resurrected itself and clockwork was no longer on.
Magic I tell you.
Click to expand...
Click to collapse
Nandroid only fails because of the path to /data, I should be able to fix this.
how to make a stock recovery image?
Hi I was just wondering how do we go about making a dump of our stock recovery images? Would be nice to be able to backup and restore back to stock if something goes wrong. I have a US streak with BB=31 and Build 6601
AdamG said:
The 2 kernels I have available for recovery are for baseband 21, I would need a dump of stock recovery or boot image from 00 devices to get it working on other devices.
Click to expand...
Click to collapse
help please?
the cmd prompt and device hangs at <waiting for device>
Funk2641 said:
help please?
the cmd prompt and device hangs at <waiting for device>
Click to expand...
Click to collapse
Have you installed the Dell PC suite to get the fastboot driver?
be_vigilant said:
Have you installed the Dell PC suite to get the fastboot driver?
Click to expand...
Click to collapse
Yeah, it's all good. Works great. Only downside is the 30fps limit, but ah well
cemian said:
Hi I was just wondering how do we go about making a dump of our stock recovery images? Would be nice to be able to backup and restore back to stock if something goes wrong. I have a US streak with BB=31 and Build 6601
Click to expand...
Click to collapse
Enable development, so you can run adb, then in adb shell type the following
cat /dev/mtd/mtd1 > /sdcard/recovery.dump
zip the file and upload it here so I can repack it
No mtd1 folder
The command failed saying no such directory...I looked myself and confirmed there is a mtd folder but nothing inside... No mtd1 Folder exists...hmmm
AdamG said:
Enable development, so you can run adb, then in adb shell type the following
cat /dev/mtd/mtd1 > /sdcard/recovery.dump
zip the file and upload it here so I can repack it
Click to expand...
Click to collapse
I currently pull the battery, then turn on volume down and power to go to bootloader and then enter into the recovery. I would like to know if this is the correct way, or if there is another method to enter the recovery. Thanks
Sent from my Amaze running Amazing QuickSense 1.5.1 using XDA app
Other than flashing a ROM with an extended menu ( instead of power off and reboot only reboot has several options reboot, hot reboot, reboot into bootloader and, reboot into recovery) the other option would be to download ROM MANAGER but that would only work if you are using CWM and have flashed it via Rom Manager.... otherwise the way you are doing it is fine
It's a tablet dammit! Not a BIG phone....
adb reboot recovery from command or terminal assuming you have the adb.exe in your system32 directory.
Binary100100 said:
adb reboot recovery from command or terminal assuming you have the adb.exe in your system32 directory.
Click to expand...
Click to collapse
Forgot about adb. Thanks Binary.
Pipsqueak approved this message
eggydrums said:
I currently pull the battery, then turn on volume down and power to go to bootloader and then enter into the recovery. I would like to know if this is the correct way, or if there is another method to enter the recovery. Thanks
Sent from my Amaze running Amazing QuickSense 1.5.1 using XDA app
Click to expand...
Click to collapse
Should not have to pull the battery - just turn it off.
If you want it easier (not connected to computer, etc.), you can install ROM Manager, flash recovery their with it, and then I recommend reflashing xBoarders 5.0.2.0 again.
ROM Manager should still work (mine does), but when you enter Recovery from there, you have the other 5.0.2.0 Recovery (RM 5.0.2.6 will not charge when off).
On a related note--do we need to keep fastboot enabled?
Or use quick boot
Free in market
I've been working on this for 2 days now and I can't seem to find an answer. I'll pay $20 to the dude who finds the resolution.
So, I just got a new Amaze, fresh out of the package. I was able to unlock the bootloader with no problems. However, when I run the flash.bat file the phone reboots into the boot loader, but nothing happens, the MS DOS prompt simply says "sending 'recovery' <4634 KB>". I've tried to use Hasoon's all-in-one-kit, but it is not able to install any recovery either. I'm not a noob, so don't insult my intelligence with stuff like "were you in USB debugging mode"? YES, I've read all the directions, and searched all over.
Things I've tried:
2 diff computers
2 diff USB cables
reinstalled HTC drivers
relocked the and unlocked the bootloader
Tried diff recoveries - CWM 5.0.02.5 and TWRP 2.0.0
Running HTC Amaze
Anyone?
Try this...
Put the recovery.img in your android/tools folder (be sure there are no other recovery.imgs in there)
Run cmd
Type the following...
"fastboot flash recovery recovery.img" be sure that the name of the .img matches the command where it reads recovery.img.
Do it the easy way
ClockworkMOD 5.5.0.4 Amaze 4g/Ruby: http://www.android-dev.us/showthread...4-Off-charging
---------------------
1. Download file to your computer
2. make sure its named PH85IMG.zip
3. Copy to sdcard (externel one)
4. Pull battery and replace
5. Hold volume down and then hit power
6. Wait for it to say do you want toupdate (press volume up)
7. Press power button to reboot
8. Reboot Phone into recovery as normal and enjoy clockworkmod recovery with fixed charging and sdcard
Turboboxer said:
Do it the easy way
ClockworkMOD 5.5.0.4 Amaze 4g/Ruby: http://www.android-dev.us/showthread...4-Off-charging
Click to expand...
Click to collapse
This link is broke.
Double0EK said:
Try this...
Put the recovery.img in your android/tools folder (be sure there are no other recovery.imgs in there)
Run cmd
Type the following...
"fastboot flash recovery recovery.img" be sure that the name of the .img matches the command where it reads recovery.img.
Click to expand...
Click to collapse
Command worked, however hangs at "sending 'recovery' <5066 KB>..."
On the screen of the Amaze there is a green vertical progress bar that is about 1/4 filled, but never moves beyond that.
Do you have root access? If so try downloading Rom Manager from the Market and flashing it with that.
Edit: N/m I went and re-read the instructions again and see you need recovery first.
Turboboxer said:
Do it the easy way
ClockworkMOD 5.5.0.4 Amaze 4g/Ruby: http://www.android-dev.us/showthread...4-Off-charging
---------------------
1. Download file to your computer
2. make sure its named PH85IMG.zip
3. Copy to sdcard (externel one)
4. Pull battery and replace
5. Hold volume down and then hit power
6. Wait for it to say do you want toupdate (press volume up)
7. Press power button to reboot
8. Reboot Phone into recovery as normal and enjoy clockworkmod recovery with fixed charging and sdcard
Click to expand...
Click to collapse
Worked!!! Thanks bro!
There's always an app called rom Manager.....
Sent from my HTC_Amaze_4G using Tapatalk
mznatnat said:
There's always an app called rom Manager.....
Sent from my HTC_Amaze_4G using Tapatalk
Click to expand...
Click to collapse
you need root for that method to work, and even then it has a really old version of cwm that does not have internal sdcard support...
I was trying to create more space. I saw the apps folder and moved it to somewhere else. Then my phone started crashing, so i turned it off. When i turned it back on i got a bootloop. My phone is rooted and i have an alacatel one touch 983. It keeps showing the o2 logo. I think this is because there is no launcher. Help please
If you have adb set up then pull the app folder from where you put it and push it to system/app. I presume you don't have a custom recovery or nandroid backup.
sinkster said:
If you have adb set up then pull the app folder from where you put it and push it to system/app. I presume you don't have a custom recovery or nandroid backup.
Click to expand...
Click to collapse
I think i put it in custect (or a something like that) but not sure, can i just push a folder called app and then add the launcher?
Bump - Please help. CMD says error: device not found, but i have sdk. Im trying to change the driver but it keeps saying its up to date.
If you're not sure where you put the folder then using adb could be pretty tedious anyway... You'd need the whole file, the bootloop probably won't be caused solely by having no launcher. If you've got a custom recovery then flash the Aroma file manager to find/move the folder, or find a CWM/TWRP flashable home launcher. If not, then your best bet is probably to use One touch support to update your rom, i,e, reflash back to stock.
sinkster said:
If you're not sure where you put the folder then using adb could be pretty tedious anyway... You'd need the whole file, the bootloop probably won't be caused solely by having no launcher. If you've got a custom recovery then flash the Aroma file manager to find/move the folder, or find a CWM/TWRP flashable home launcher. If not, then your best bet is probably to use One touch support to update your rom, i,e, reflash back to stock.
Click to expand...
Click to collapse
Well, i have a system.img that i want to flash with fastboot. i also found an o2 rom for my phone. So if i could get adb or recovery mode to work i could restore it. I have a rough idea of where it is, so i could get it, but adb and fastboot don't recognise my device. I tried hard resetting it by holding the volume up button but im still stuck at the o2 screen. I have tried the alcatel driver but that doesn't work. It doesn't recognise it when i try to put it into recovery mode. If you know the combination for the alcatel 983 please say. Maybe it is because hard resetting it disabled usb debugging, but my pc recognises it fine. (cannot open sd card), but it recognises it and it's name. So i do not know why adb doesn't recognise it.
I'm not familiar with Alcatel phones, but it should be volume down while turning on for fastboot. If you can get into fastboot you should be able to flash a custom recovery.
sinkster said:
I'm not familiar with Alcatel phones, but it should be volume down while turning on for fastboot. If you can get into fastboot you should be able to flash a custom recovery.
Click to expand...
Click to collapse
Holding up while turning on makes it to hard reset and holding down does makes it freeze. So how can i make it work with adb on my pc. Should i try a different pc? There are no other buttons, it is touch screen.
Actually holding down while it says waiting for device works, testing some stuff out now thanks. will show my resuslts
When you switch on/press down, the freeze is the phone in fastboot (apparently), so try that, connect to your pc, open cmd window where you'd normally open adb and try 'fastboot erase cache' and see if you get a response. should return a message saying cache erased, or similar. If so, you're in fastboot and you can use it to flash a custom recovery (obviously one for your phone)
This post seems to be a similar issue/resolution. There's no custom recovery yet for the phone.
sinkster said:
When you switch on/press down, the freeze is the phone in fastboot (apparently), so try that, connect to your pc, open cmd window where you'd normally open adb and try 'fastboot erase cache' and see if you get a response. should return a message saying cache erased, or similar. If so, you're in fastboot and you can use it to flash a custom recovery (obviously one for your phone)
Click to expand...
Click to collapse
ok ill try thanks.
Well i done that, but now it is frozen at the o2 screen. I flashed boot, recovery and system img. Lower buttons work but its stuck at o2 screen. What do i do next?
Can you connect with adb yet?
sinkster said:
Can you connect with adb yet?
Click to expand...
Click to collapse
Nope still no adb, still saying device not found. Is there an adb mode that i can get to?
Adb needs the system to respond, out may be borked due to the move of the system/app folder. What commands did you use in fastboot? Fastboot flash system xxx.img?
sinkster said:
Adb needs the system to respond, out may be borked due to the move of the system/app folder. What commands did you use in fastboot? Fastboot flash system xxx.img?
Click to expand...
Click to collapse
Yes i did fastboot flash system/boot/recovery for each their img's. Well i am trying the alcatel one touch update now. Ill see if that fixes it. Ill report back when its done
ok, good luck.
sinkster said:
ok, good luck.
Click to expand...
Click to collapse
Well, that didn't work. Got any other tips? Im still stuck at o2 screen. Thanks
supernovakid said:
Well, that didn't work. Got any other tips? Im still stuck at o2 screen. Thanks
Click to expand...
Click to collapse
It has worked, thanks a lot for your help! You are a great person thanks!
No probs.