Related
Its been done on the Incredible and Evo, now the Slide. This SHOULD BE IT. Here is their post with exact method. Adjust for the N1 and test on an unrooted phone. ASAP. This should be it!!!!!
QUOTED FORM EUGENE373 @ MT3GS FORUM:
Originally Posted by brokensanity
How-TO Root the Slide
First!! - Go to Settings > Application > Development and turn on USB Debugging. This should save you headaches.
NOW… Power Off the Slide
Download This Package > Slide Root.zip
kingofyo1's Video How-to > http://www.youtube.com/watch?v=sVjoKvy-YZg
Step 1.
Place the Contents of "Slide Root.zip" into your Android SDK Tools folder.
Step 2.
Open Command Prompt or Terminal and CD to the SDK/Tools Directory.
Step 3.
Power on the Slide into the bootloader by Holding Down ( Volume Down + Power Button )
Step 4.
Now run your loop file from the prompt (either type "loop" in windows or "./loop.sh" in a *nix like)
Step 5.
Once your loop is running in your prompt, select Recovery from the bootloader menu.
Step 6.
When recovery loads, you should Have an Offline Device. You can use ctrl+c to stop your script & see.
If this doesn't happen, Power Off and try again..
Step 7.
Un-plug your USB cable from the back of your phone & Plug it back in for it to Detect ADB Correctly!!! This is an important step. At this point you can adb devices to see if you can see your device and that it is in recovery mode.
Step 8.
Select Update.zip from the menu. (This will fail, but we already know that! Select it anyway).
Step 9.
adb push ota.zip /sdcard/update.zip (*nixlike users add a ./ in front of all terminal commands please.)
Step 11.
adb push slideroot.zip
Step 12.
This is Very important!! Have this Command ready in your prompt before applying update.zip again!!
adb push update.zip /sdcard
step 13.
Hit run update.zip, as soon as you see a Little Bar appear under the text push Enter to execute the command in your prompt (adb push update.zip /sdcard )
Step 14.
In successful, you should see Clockwork Recovery. If unsuccessful, repeat steps 12 & 13.
Step 15.
Now, go to the Partitions menu and Mount System
step 16.
Go back one level & select install any zip from sdcard. Select slideroot.zip & apply update from zip (This will finish the Root process).
Step 17.
Reboot your phone & wait for it to load completely. To confirm that your slide is connected as a device use the command adb devices. If this works, you will see it as a device. Your prompt will say something like:
$ ./adb devices
List of devices attached
HT05YUP12710 device
Step 18.
adb install Superuser.apk (If this looks like it works, but says it cannot locate directories, make sure you can find your device using adb devices… If things still don't work, my best advice is to start over)
Step 19.
After Superuser is installed try to use adb to shell to your device.
adb shell
you will get a $
Then type su
Superuser should pop-up asking if you give permission, do so.
Your $ should turn into a #. If so, you have root.
Congrats.
Special Thanks to:
Paul O'Brien:
Koushik K. Dutta:
&
The Guys using the Incredible OTA Spoofing Method
Why don't you test it out and let us know the results? ;-)
why do we care about the bootloader since both HTC and Google are ok with us unlocking it?
Im waitn for someone to try this out... hahaahah
b9nez said:
why do we care about the bootloader since both HTC and Google are ok with us unlocking it?
Click to expand...
Click to collapse
If people don't unlock the bootloader they get to keep their warranty
PhantomRampage said:
If people don't unlock the bootloader they get to keep their warranty
Click to expand...
Click to collapse
Most of the time, they'll replace our equipment. It's been done before, i'm witness to that.
I don't argue this would be a good idea but it's not THAT necessary. :\
Edit: only real upside i can see is getting rid of that annoying unlock icon but since i'm already unlocked there's no point.
This would be pretty good for people like me, who has an unrooted Nexus One
whorehay said:
This would be pretty good for people like me, who has an unrooted Nexus One
Click to expand...
Click to collapse
The key is that we need a DEV with an unlocked phone in hand. I can switch my purple-tinted screen out and get it over to a good one, but that could take a few weeks, anyone else have the tools ready?
I read that whole thread and there was no mention of bootloader at all. If someone can confirm it isn't touched I might be willing to give this a go with my new ATT N1.
If I somehow manage kill it, is there a way to recover a stock image without root?
Santoro said:
I read that whole thread and there was no mention of bootloader at all. If someone can confirm it isn't touched I might be willing to give this a go with my new ATT N1.
If I somehow manage kill it, is there a way to recover a stock image without root?
Click to expand...
Click to collapse
If it is messing with just the image then im 99% sure yeah you can.
I have a mytouch slide also and this method works. Were having problems getting a recovery to stick on the phone though. I have no idea if this works on n1. Id try but my bootloaders already unlocked.
Santoro said:
I read that whole thread and there was no mention of bootloader at all. If someone can confirm it isn't touched I might be willing to give this a go with my new ATT N1.
If I somehow manage kill it, is there a way to recover a stock image without root?
Click to expand...
Click to collapse
I can say that it wont hurt the phone. I tried a process similar to this before I had the details with one of the better known devs from XDA this weekend for a few hours. Even though we couldn't get the timing right, at the end of the day, I still had my original Rom, and it haven't even been hit with a recovery.
i have exchanged my N1 with an unlocked bootloader without any issues. and many other people have as well. if its a hardware issue they will ALWAYS honor warranty. if your phone is bricked by something you flashed they won't honor that
FishFan319 said:
I can say that it wont hurt the phone. I tried a process similar to this before I had the details with one of the better known devs from XDA this weekend for a few hours. Even though we couldn't get the timing right, at the end of the day, I still had my original Rom, and it haven't even been hit with a recovery.
Click to expand...
Click to collapse
So I know just enough to be dangerous. I need to understand a little more before I try this on my N1.
This slide_root.zip, are it's contents phone-specific? You said we should modify the process for the N1, are you saying that the contents of the file need modification? Or just the navigation around the recovery?
I am pretty leery until I understand what the slide_root file does and if it is compatible with my phone. Anyone know?
If I do it and it fails, does anyone have a link to how I would reinstall a stock image via USB?
edit: grammar
I developed a screen problem and had to pay to get it repaired because the bootloader was unlocked. Nothing to do with ROM or anything, a section accross the top of the screen went unresponsive to touch. So I know for a fact that they DON'T always honor warranty after unlock. I guess I must've gotten the a*hole operator/technician then for my call...
Jr33 said:
i have exchanged my N1 with an unlocked bootloader without any issues. and many other people have as well. if its a hardware issue they will ALWAYS honor warranty. if your phone is bricked by something you flashed they won't honor that
Click to expand...
Click to collapse
That really is a matter of interpretation by the tech you get at HTC. Based on the poster just above this, the warranty is not ALWAYS honored. Right?
Santoro said:
That really is a matter of interpretation by the tech you get at HTC. Based on the poster just above this, the warranty is not ALWAYS honored. Right?
Click to expand...
Click to collapse
right. I could not get mine repaired for the dusts under screen problem with unlocked bootloader.
I think most of them slipped through since they could swap in US
kaiser_tytnii said:
right. I could not get mine repaired for the dusts under screen problem with unlocked bootloader.
I think most of them slipped through since they could swap in US
Click to expand...
Click to collapse
I stupidly got mine etched. Had I thought about the fact that it would preclude me from getting cross-shipped warranty work, I'd have reconsidered.
I WISH I COULD TYPE IN ALL CAPS IN TITLES TOO...
Anyway....
I'm assuming the OP didnt intend for yet another thread to devolve into the warrantly debate.
bobtentpeg said:
I WISH I COULD TYPE IN ALL CAPS IN TITLES TOO...
Anyway....
I'm assuming the OP didnt intend for yet another thread to devolve into the warrantly debate.
Click to expand...
Click to collapse
yep, i agree. let's stop the warranty debate here.
i probably will find someone who has a unrooted phone to try it out
Cut to the chase, I can no longer get into recovery. I am trying to use adb in command prompt, but am running into a roadblock where $ comes up, and no commands will work. I quite literally have no idea what to do. I just want to go back to normal. I know it's my fault for trying new things, but if the phone still boots up, there must be a way out of this hell. Please can anyone have mercy on me and help? What information must I provide? VM670 is the phone. I think it's on stock ROM cause the UI is all virgin mobile looking.
Edit: I tried to restore some BCDS backup or something in Rom manager. Now my screen is just black, but I can hear it boot up. Is my phone toast?
mcnic05 said:
Cut to the chase, I can no longer get into recovery. I am trying to use adb in command prompt, but am running into a roadblock where $ comes up, and no commands will work. I quite literally have no idea what to do. I just want to go back to normal. I know it's my fault for trying new things, but if the phone still boots up, there must be a way out of this hell. Please can anyone have mercy on me and help? What information must I provide? VM670 is the phone. I think it's on stock ROM cause the UI is all virgin mobile looking.
Edit: I tried to restore some BCDS backup or something in Rom manager. Now my screen is just black, but I can hear it boot up. Is my phone toast?
Click to expand...
Click to collapse
I am not sure if I remember correctly, but when $ pops up, don't you have to type "su" (without the quotations) to allow superuser actions or something? What I mean is, before you type any other command, you must first type "su", press enter (when you do the $ should turn into a # or something), then proceed with the rest of the commands.
when I type su, it waits a second, then tells me permission denied I believe.
Can you post the set of instructions that you are following?
I was just able to get into recovery for some reason! It was the one I remember with orange text this time. (older version?) I wiped everything.... but had no ROM to flash. -_- trying something now.
After 2 days of trying to fix my phone, I give in, make an account and ask for help here. No more than 5 minutes later my phone is back to just how I want it for no reason at all. I am so utterly baffled right now. Thanks sweetnsour for being there . love this place
Simply get root (GingerBreak or Super One Click) , then install recovery with Rom Manager.
Sent from my LG-P500 using Tapatalk
mcnic05 said:
when I type su, it waits a second, then tells me permission denied I believe.
Click to expand...
Click to collapse
Are you root your phone? Use, depending your stockROM, z4root (2.2 and some 2.2.1), Gingerbread (2.2.1, 2.2.2) or SuperOneClick + Gingerbread exploit + some ADB commands (2.3.3)
When you rooted, you can flash customrecovery using commands or, in case of CWM, Clockworkmod apk.
mcnic05 said:
when I type su, it waits a second, then tells me permission denied I believe.
Click to expand...
Click to collapse
Because when you typed su , your phone will appear the super user permission , it only give you 9 seconds to allow the su...... But you just see the black screen
Need 10 posts to comment in developers forum. So I'll just thank everyone for their help! And say how much faster bobzhomes build is than others I've used. Love it.
OMG! I'm not going into details on what I did, I'd just like to request the Stock ROM that came with it so I could restore my phone. It has android 4.1.2 and I just want to install it using the "Apply Update From sdcard." And if you must know, I edited the Build.prop file (The internet told me to.) And it messed up and wouldn't start up and got stuck in "Bootloop" so I tried factory reset and it didn't and I really need my phone because if I don't fix it I'll have to try to send it in to Huawei or T-Mobile or who ever. Plllllllz help.
Solution may be here soon.
No one has the stock rom on hand yet. We are working on building a custom recovery for the phone, so please be patient.
Hopefully we can have a working recovery by this weekend, then you will have a way to still access your phone.
What files did you mess up on your phone? If i know the files, I can get someone to upload the files and then you can push the files to your phone using adb. If you haven't yet, I would recommend unlocking your bootloader via the instructions here:
http://forum.xda-developers.com/showthread.php?t=2546455
By unlocking the bootloader, you will be eligible to test the custom recovery as soon as it is available. Also, list the foiles you messed up, so that we can possibly upload them for you.
It will be a while until someone can form a stock rom update.zip for you.
Also, you can view the progress that we are making on the custom recovery.
amamartin999 said:
OMG! I'm not going into details on what I did, I'd just like to request the Stock ROM that came with it so I could restore my phone. It has android 4.1.2 and I just want to install it using the "Apply Update From sdcard." And if you must know, I edited the Build.prop file (The internet told me to.) And it messed up and wouldn't start up and got stuck in "Bootloop" so I tried factory reset and it didn't and I really need my phone because if I don't fix it I'll have to try to send it in to Huawei or T-Mobile or who ever. Plllllllz help.
Click to expand...
Click to collapse
You don't want to go into details but you still want someone to help you? Hahahahaha!!!
Good luck with that plan!
CtrlAltDelIrl said:
You don't want to go into details but you still want someone to help you? Hahahahaha!!!!
Click to expand...
Click to collapse
Show some compassion - I'm sure most of the people here have messed up, and hit their heads against the wall for it.
Deeeno said:
Show some compassion - I'm sure most of the people here have messed up, and hit their heads against the wall for it.
Click to expand...
Click to collapse
Yes and in those cases they're usually eager to share all the details required, unlike the OP.
When the proper details are supplied it's easy to help, nobody likes to mindread here.
CtrlAltDelIrl said:
When the proper details are supplied it's easy to help, nobody likes to mindread here.
Click to expand...
Click to collapse
Probably doesn't know exactly what they did to mess up.. so doesn't know how to explain it.
Merely asked for the stock application to try and fix it themselves is what I gathered.
But Whatever
Explanation.
Was using Android tweaker 2 and accidentally hit the "On Screen Navigation Keys" and then when I went to turn it off it wouldn't switch. It stayed on. Updated the T weaker app, hoping for a fix but the option disappeared and I was stuck with them. Searching the internet I found a option that allowed to disable the soft keys in the Build.prop. But when I save it and restarted the phone was stuck at the T-Mobile screen.
Also I never figured out how to do ABD it tried for a long time but it didn't work. Since I got it in October, I need to know who to send it to be repaired, since I have a warranty (But I don't really want to send it away so that's why I asked.) So, there's and explanation. I'd tell you what I edited if I could find the website.
ADB
Okay, I got ADB working. But if I unlock Bootloader, does that that void my warranty?
And basically I need a default Build.Prop. Thats the only file I edited.
Return the phone since you are under warranty, you won't be without a phone
If you are under warranty with tmobile, you should be able to get a replacement if you are on their JUMP insurance, even if it was accidental.
I would recommend first going to your tmobile store and asking them to send you a replacement(and to waive the restock fee). They will send you one by mail in a few days, then all you have to do is send the old phone back to them in the prepaid shipping package(instructions are included).
I would recommend doing this instead of unlocking your bootloader and waiting for a recovery and custom rom to come out. My belief is that unlocking your bootloader does NOT directly void your warranty, unless the company can prove that the unlocking directly bricked your phone(which it doesn't). A thread with the legality of unlocking your bootloader is found here: http://forum.xda-developers.com/showthread.php?t=2250113
Again, I recommend just bringing in your phone and saying your phone just refuses to boot anymore since an update or something of that like. You won't have to wait long. Also, the phone is $63 on ebay, if you are uneasy about going to tmobile to return it.
build.prop for Android 4.1.1
default Prism 2 build.prop file for Android 4.1.1 attached below. Don't know if this will work with 4.1.2, so make a backup of your build.prop before replacing it!
Prism 2 said:
default Prism 2 build.prop file for Android 4.1.1 attached below. Don't know if this will work with 4.1.2, so make a backup of your build.prop before replacing it!
Click to expand...
Click to collapse
Dont do this, you will brake it even more, every version has specific build prop.
Okay, but no.
Not on insurance....
They didn't offer it at Walmart, that I know of. The real reason I got it was that I was sick of my unlocked Pantech Link (An AT&T on T-Mobile...)
And plus, I'm just broke right now -_-
Are you sure you have Android 4.1.2? I have the latest stock T-mobile rom (just tried updating today) and I'm "up to date" with 4.1.1
How do you have 4.1.2?
That's strange. Can any other users confirm that their Prism Ii has 4.1.2?
Well...
Well.. I may be mistaken. But I can't check =/
Almost certain you have 4.1.1
Doubt they would push an OTA just to upgrade from 4.1.1 to 4.1.2, but if someone can verify they have 4.1.2 i am open for correction.
I think pushing the new build.prop to your phone is worth the shot, and it would not effect your bootloader since it is locked, and you are already softbricked.
To push the build.prop to your phone, you have to rename the old one in adb, and then use the adb push command to push the file into the appropriate folder ( /system )in this case.
If you need help organizing the files or using the actual commands, let me know. Also, you want to place the build.prop file in the same folder you installed adb.
Also, to run adb, you have to open cmd and change your directory(the command is cd) to the folder you installed adb to, in order to use the adb command.
The adb command only runs when you are in that folder in the command prompt, because adb is not a systemwide command
streetdev22 said:
Doubt they would push an OTA just to upgrade from 4.1.1 to 4.1.2, but if someone can verify they have 4.1.2 i am open for correction.
I think pushing the new build.prop to your phone is worth the shot, and it would not effect your bootloader since it is locked, and you are already softbricked.
To push the build.prop to your phone, you have to rename the old one in adb, and then use the adb push command to push the file into the appropriate folder ( /system )in this case.
If you need help organizing the files or using the actual commands, let me know. Also, you want to place the build.prop file in the same folder you installed adb.
Also, to run adb, you have to open cmd and change your directory(the command is cd) to the folder you installed asb to, in order to use the adb command.
The adb command only runs when you are in that folder in the command prompt, because adb is not a systemwide command
Click to expand...
Click to collapse
Pushed the Build.Prop, but still does the same thing. Lost the old one though, because I forgot to rename it.
Try Factory Reset once more
You are stuck in a bootloop? Try factory resetting once more.
If that does not work, you may be our first live install recovery image tester, and you'd just have to wait until a custom ROM was released.
Reseted... Still stuck.
Omg. They must make these phones just to make us upset when they break.
Wait until I get the unlock code from Huawei, also some other things to try
It should be any minute now, and I will see if there are other fixes. For now, unlock your bootloader according to the guide.
We will need access to recovery anyway, through recovery, we will try wiping cache/dalvik cache if available, and that may be the fix you need.
Also: I think you may need to change the permissions on the build.prop you pushed!
You would have to change the permissions to 644 according to this thread: http://forum.xda-developers.com/showthread.php?t=2152850&page=2
To do this, we would still need to use adb.
Commands in adb:
adb shell
remount rw
chmod 644 /system/build.prop
Also, are you sure that the file actually pushed successfully?
Hey guys,
I've been slackin' on the updates of my rom lately and thought it was finally time to do a proper update. I got my HTC one in the US around release and rooted it back then. However, now I was trying to install Android Revolution on it and the installation went fine (well, at least so I thought) up until the time I was going to boot it. It constantly keeps on re-booting me into the TWRP menu, even though the rom seems to be installed.
I was looking around and found out about ADP push http://forum.xda-developers.com/showthread.php?t=2325853
However, I get stuck on the step where I'm supposed to get up my Serial number in the terminal. It seems as if the command runs through but comes up with nothing, just a blank space. At first I simply ignored this and moved on to the next step. However, my computer doesn't seem to acknowledge the command ./adb push NameOfRom.zip /data/media/
Where do I go from here?
Thank you
Mr. Harrow
Mr_Harrow said:
Hey guys,
I've been slackin' on the updates of my rom lately and thought it was finally time to do a proper update. I got my HTC one in the US around release and rooted it back then. However, now I was trying to install Android Revolution on it and the installation went fine (well, at least so I thought) up until the time I was going to boot it. It constantly keeps on re-booting me into the TWRP menu, even though the rom seems to be installed.
I was looking around and found out about ADP push http://forum.xda-developers.com/showthread.php?t=2325853
However, I get stuck on the step where I'm supposed to get up my Serial number in the terminal. It seems as if the command runs through but comes up with nothing, just a blank space. At first I simply ignored this and moved on to the next step. However, my computer doesn't seem to acknowledge the command ./adb push NameOfRom.zip /data/media/
Where do I go from here?
Thank you
Mr. Harrow
Click to expand...
Click to collapse
I found this http://forums.androidcentral.com/htc-one/332846-hi-i-have-htc-one-m7-its-stuck-twrp.html
Shouldn't have to go through the hassle of going through that process though? Seeing as there's a zip of the android revolution on the phone which is installable, but nevertheless doesn't boot. Please help a fella out?
Try to wipe all but SD card, flash rim like normal, then pull the recovery logs (found in advance settings) and post it here if it won't boot
Also know that many HTC phones when unlocked through htcdev, need you to flash the kernel through fastboot after flashing the ROM, if you're unsure if you need to do this boot to bootloader and note all it says on this screen and then check your device forum for specifics on this
Sent from my Nexus 4 using XDA Premium 4 mobile app
Also make sure you got the correct rom from the correct forum. There are multiple One forums now and it's not the first time it's happened..
PS. ./adb is only for Linux - is that what you are running?
And I know the stuff is on /data/media but try this:
adb push nameofrom.zip /sdcard/
Hi all,
I have been through douzens of threads and forums looking for a solution to this.
I followed some instructions to modify the build.prop file on my Huawei G535-L11 to disable Huawei theme manager in order to get Xsposed working fully (changed ro.config.hwtheme: 0). I did a backup of my original build.prop before hand, and my phone was rooted and unlocked but running the stock rom.
Unfortunately, it rebooted but won't go past the first 'EE' splash screen (just turns off again).
I can inconsistently get in to both fastboot and Android recovery, so I have been trying to use adb to push the original build.prop to /system/ on the phone.
However, this fails as /system/ is apparently RO. I have now discovered that I can't get SU permissions despite my phone being rooted.
If I try:
adb shell
$ su
nothing happens and it goes back to a $ prompt.
If I try:
adb root
I get the message (paraphrased):
adb cannot run as root in production builds.
So I can't push or do any adb method of restoring the build.prop file?! I don't understand why it is acting as if it is not rooted. I had Link2sd, Gravity Box, No Frills Cpu Controller all set up and working before, so I'm fairly sure I did truly have root.
I have also tried flashing a TWRP recovery, which apparently is successful, but when I go in to recovery it is still the Android Recovery.
Does anyone have any ideas what I could do to get my phone working again please?! This is my last gasp before the phone gets filed under 'B' in the cylindrical cabinet in the corner of the room!
Any assistance greatly appreciated!
Some systems are very finicky with modded build.props, or you didn't set the file's permissions correctly. I'm afraid without being able to boot or a working custom recovery, then adb won't work, much less root enabled adb functions. adb works in some stock recoveries, but only for sideloading files directly signed by the manufacturer. In regards to TWRP, is the bootloader unlocked? If not, that would explain why it didn't work. Other than that, I don't believe you'll have any other options besides reloading the stock firmware.
Hi,
Thanks for the reply. Yes, the bootloader was / is unlocked.
Unfortunately, there isn't any stock firmware available anywhere. Unless someone out there has a backed up rom image from the EE Kestrel?
This is supposed to be a working TWRP for your device http://forum.xda-developers.com/showpost.php?p=58522448&postcount=117 - if you get it loaded, there might be a chance to push the working build.prop back to the phone. I would read that thread too and see if there isn't more useful info there or another member with your phone that could make a backup for you. Good luck.
Thanks.
Unfortunately, I'm pretty sure that is the TWRP I've tried. I'll double check when I'm on my PC.
I might try requesting a rom image on that thread, but the community for this phone seems to be pretty dead :/
I've just gone and ordered a new phone anyway, but it seems like a waste of a good phone just for the sake of one line of bad code!
Thanks for your help. I'll post again if I have any success.