Related
First of all i spent 3 days Trying and failing to root the phone and this is my first tutorial if theirs anything i missed please don't hesitate to point it out.
I am Not responsible for any damage, Explosions, Nuclear Holocaust etc. this root method may cause.
Files you will need below:
1. Engineering Recovery package: Download
2. SuperOneClick v1.7: from Here Thanks to CLShortFuse
3. A GoldCard: To easily create a Goldcard in a couple of minutes without ADB skills or commands, check this thread
4. Stock firmware: Download
5.the ClockworkMod Recovery 2.5.0.7 : Download
5. a know how of how to use ADB.
- There's a good ADB learning guide here: ADB for noobs
(Thanks steviewevie)
Lets Begin
Step 1: Assuming you already created a gold card place it in your phone and mount it place the Stock Firmware zip and update.zip on root. and unzip Engineering Recovery package and place them in your AndroidSDK in the "Platform-tools" folder.
Step 2: unzip and run SuperOneClick v1.7 and make sure your phone is connected via USB with USB Debugging ON. Now press Shell Root and let it run you should get a success pop up.
Step 3: Run ADB and type the following:
adb devices
you should get your devices serial
adb push flash_image /data/local
adb push mtd0.img /data/local
adb shell
cd /data/local
chmod 04755 *
/data/local/flash_image misc /data/local/mtd0.img
Step 4: Once complete, power off the TMobile myTouch Slide
Step 5: Hold the Volume Down button while powering on until the device is in bootloader mode.
Step 6: After a minute or so, the device will prompt to see if you want to run the update. Press the Volume Up button to accept & apply the update.
NOTE: (IF YOU GET A ERROR MSG THAT THE ZIP VERSION IS OLDER THEN THE THE PHONE VERSION YOUR GOLDCARD WAS MADE WRONG!!)
Step 7: Once the device is finished applying the update, it will ask you to reboot. DON'T reboot the device & press the Volume Down button to tell the device not to.
Step 8: Back at the bootloader menu, use Volume Down to highlight Recovery and press the Power button to boot into the recovery.
Step 9: Once in the recovery, you will see a device with a triangle. Press Volume Up & the Power button.
Step 10: Use the Volume Down button to highlight Apply update.zip & press the Power button to select this.
Final Step: After a moment, the TMobile myTouch Slide will boot into the ClockworkMod Recovery.
After that you can now pull battery and insert your main memory card with your desired ROM and Radio Update if you wish and boot into recovery and Happy
Flashing
Enjoy!!
This is how I achieved root! I guess great minds think alike. I was just about to post too, but you beat me to the punch. See the minute I realized with SuperOneClick I could achieve Shell root I could push mtd0.img and flash and then flash the engineering build but you beat me to it! I was thinking about it all day during class and it worked but kudos to you!
Sent from my T-Mobile myTouch 3G Slide using XDA App
iDaZzLeFatHoeZz said:
This is how I achieved root! I guess great minds think alike. I was just about to post too, but you beat me to the punch. See the minute I realized with SuperOneClick I could achieve Shell root I could push mtd0.img and flash and then flash the engineering build but you beat me to it! I was thinking about it all day during class and it worked but kudos to you!
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
I kinda stmbled onto the root method when I was testing a couple
Sent from my T-Mobile myTouch 3G Slide using XDA App
Yeah me too, I was looking through root methods for other phones and I saw SuperOneClick and then realized with that I can get get shell root and then use ADB to push the files needed, and then flash the engineering build.
Sent from my T-Mobile myTouch 3G Slide using XDA App
But, something of note, this will NOT allow you to gain S-OFF. Once you update to stock OTA you will permanently lose the ability to S-OFF unless you have your device replaced by T-Mobile.
Following your instructions and finally I find myself with RC4 again. Thanks a bunch for helping me out.
Yeah nbetcher is right, stuck on HBOOT 1.0 Thanks for the heads up NB
Sent from my T-Mobile myTouch 3G Slide using XDA App
Does rooting this way effectively get rid of the actual official 2.2.1?
or is the esprimg that of 2.2.1 or the old 2.1?
nobreak1970 said:
Does rooting this way effectively get rid of the actual official 2.2.1?
or is the esprimg that of 2.2.1 or the old 2.1?
Click to expand...
Click to collapse
Gets rid of 2.2.1
Sent from my T-Mobile myTouch 3G Slide using XDA App
Thanks much for this. Back to ArayrayMod Revamped...woot!!!
I love messing with stuff so this was fun.
worked great. thanks!
When I get to step 2 and type in
"#cd /data/local
#chmod 04755 *
#/data/local/flash_image misc /data/local/mtd0.img"
should it be repeating what I type? Cause when I reboot, it checks ESPRIMG then says main version is older, but I know I made my goldcard correctly.
maybe my fault
This method worked great, my only problem is that when using rom manager, reboot into recovery doesnt work. It goes to stock recovery but with a question mark. I placed the update.zip on my sdcard and it wont read it pressing volume up and power. I was able to flash cm7, and google apps, but now cant get back into recovery. Not sure what I did in error. I should mention that, trying to stop my wifes complaining about the stock rom, I updated to froyo. I'm familiar with all the tinkering with these phones, I have a G2 rooted, s-off, with CM7 on it. I just don't know about the slide. Any help would be appreciated. Thx in advance.
It should repeat what you type as a confirmation
Sent from my T-Mobile myTouch 3G Slide using XDA App
This method worked great, my only problem is that when using rom manager, reboot into recovery doesnt work. It goes to stock recovery but with a question mark. I placed the update.zip on my sdcard and it wont read it pressing volume up and power. I was able to flash cm7, and google apps, but now cant get back into recovery. Not sure what I did in error. I should mention that, trying to stop my wifes complaining about the stock rom, I updated to froyo. I'm familiar with all the tinkering with these phones, I have a G2 rooted, s-off, with CM7 on it. I just don't know about the slide. Any help would be appreciated. Thx in advance.
Click to expand...
Click to collapse
U have to keep the update.zip witch is the recovery on sd root and select flash update.zip in stock recovery sense we dont have s-off
Sent from my T-Mobile myTouch 3G Slide using XDA App
Chisle31 said:
U have to keep the update.zip witch is the recovery on sd root and select flash update.zip in stock recovery sense we dont have s-off
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
OK, thats what I figured. Thanks alot!
I don't know what I'm doing wrong, if anything. There's a few things that I might not have right:
1: I'm supposed to cd\ to whatever folder I have the Engineering Recovery package saved to, right?
2: I know when I type adb shell, I should get "#" as a response to my input. So should my prompt look like this:
adb shell
# #cd /data/local
# #chmod 04755 *
# #/data/local/flash_image misc /data/local/mtd0.img
or like this:
adb shell
# cd /data/local
# chmod 04755 *
# /data/local/flash_image misc /data/local/mtd0.img
Ok, just want to make sure I got everything here: basically, once you're rooted with this method, you can go back to factory condition by placing the same esprimg.zip from S-Off troubleshoot section and then re-update with HTC Sync, right?
austinbrown92 said:
I don't know what I'm doing wrong, if anything. There's a few things that I might not have right:
1: I'm supposed to cd\ to whatever folder I have the Engineering Recovery package saved to, right?
2: I know when I type adb shell, I should get "#" as a response to my input. So should my prompt look like this:
adb shell
# #cd /data/local
# #chmod 04755 *
# #/data/local/flash_image misc /data/local/mtd0.img
or like this:
adb shell
# cd /data/local
# chmod 04755 *
# /data/local/flash_image misc /data/local/mtd0.img
Click to expand...
Click to collapse
Did you try both? From my experience with command line stuff, the second looks correct. But, someone can correct me if I'm wrong.
txdeathray said:
Ok, just want to make sure I got everything here: basically, once you're rooted with this method, you can go back to factory condition by placing the same esprimg.zip from S-Off troubleshoot section and then re-update with HTC Sync, right?
Click to expand...
Click to collapse
It seems to me like it would - wouldn't hurt to give it a try.
I did try both. It just repeats it when I hit enter. So I turn my phone off, hold vol down + power, let esprimg load, then it says "Main version is older! Do you want to restart?" I choose no, try to apply update.zip, then it says sig verification failed, so i reboot. Not sure what to do
Im using this method...
DLed the drivers and files needed already..
After a connect phone and turn on USB debuging and run CMD
cd C:\FascinateRoot_v02
adb devices
It will state
"List of devices attached
I500******* device"
If you dont see this you are not connected
adb push rage.bin /data/local/tmp/rage.bin
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
This step is important. After you type the next command there will be a pause and you will have to wait until you are kicked out of adb shell. It is important you do not touch your phone or type anything in the command window. If you do don't worry, nothing bad will happen you will most likely have to pull your battery and try to run the command again. If your phone doesn't lock up you can probably unplug it and plug it back in and start back at "adb shell"
./rage.bin
After several seconds the $ prompt will come back
After another 20 seconds or so you will be kicked back to the C:\FascinateRoot_v02 prompt.
adb devices
If your device is still connected proceed,if not give it a min or to and type adb devices again. if the phone is locked up after a couple mins battery pull and start over.
adb shell
You should now be at a # prompt
This mean you have achieved temporary root on the device.
exit
You should now be at the C:\rootfiles prompt again
Type the following commands:
adb push su /sdcard/su
adb push busybox /sdcard/busybox
adb shell
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > ./su
cat /sdcard/busybox > ./busybox
chmod 4755 su
chmod 4755 busybox
exit
You should be back at the C:\FascinateRoot_v02 prompt
adb install Superuser.apk
It will now install the Superuser.apk this may take some time while it installs when it is over it will say:
Success-after you see Success hit Ctrl-C Then reset your device
The problem i have is that ADB doesnt recognize my device
tryd different "one click" attempts for it also and same thing
"Device not connected or found or seen"
What can i do?
Help pls
Thnx in Advance
Found in this page to be specific
http://forum.androidcentral.com/ver...-roms-hacks/33899-how-root-74.html#post526222
JeezyMT3G said:
Im using this method...
DLed the drivers and files needed already..
After a connect phone and turn on USB debuging and run CMD
cd C:\FascinateRoot_v02
adb devices
It will state
"List of devices attached
I500******* device"
If you dont see this you are not connected
adb push rage.bin /data/local/tmp/rage.bin
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
This step is important. After you type the next command there will be a pause and you will have to wait until you are kicked out of adb shell. It is important you do not touch your phone or type anything in the command window. If you do don't worry, nothing bad will happen you will most likely have to pull your battery and try to run the command again. If your phone doesn't lock up you can probably unplug it and plug it back in and start back at "adb shell"
./rage.bin
After several seconds the $ prompt will come back
After another 20 seconds or so you will be kicked back to the C:\FascinateRoot_v02 prompt.
adb devices
If your device is still connected proceed,if not give it a min or to and type adb devices again. if the phone is locked up after a couple mins battery pull and start over.
adb shell
You should now be at a # prompt
This mean you have achieved temporary root on the device.
exit
You should now be at the C:\rootfiles prompt again
Type the following commands:
adb push su /sdcard/su
adb push busybox /sdcard/busybox
adb shell
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > ./su
cat /sdcard/busybox > ./busybox
chmod 4755 su
chmod 4755 busybox
exit
You should be back at the C:\FascinateRoot_v02 prompt
adb install Superuser.apk
It will now install the Superuser.apk this may take some time while it installs when it is over it will say:
Success-after you see Success hit Ctrl-C Then reset your device
The problem i have is that ADB doesnt recognize my device
tryd different "one click" attempts for it also and same thing
"Device not connected or found or seen"
What can i do?
Help pls
Thnx in Advance
Found in this page to be specific
http://forum.androidcentral.com/ver...-roms-hacks/33899-how-root-74.html#post526222
Click to expand...
Click to collapse
Hm...May sound stupid, but is USB debugging ENABLED? I mean, I see where you posted the directions, which include that, but are you positive it IS enabled? Aside from that, this is a new one to me.
yeah its enabled lol
ive tried it while enabled and disabled
even tryd to disable while plugged in
but to find out i cant lol
......
this is really a bummer cuz im not a noob or anything with
ADB or root
(Rooted G1 MT3g MT3gS D1 D2 DInc and G2)
and this little device has stumped me
here is my firmware info
just to see if thts affecting it
Hardware:i500.04
Model SCH-I500
Firmware 2.1 update1
Baseband
S:i500.04 V.DL09
Kernel 2.6.29
Build Number
SCH-I500.DL09
JeezyMT3G said:
yeah its enabled lol
ive tried it while enabled and disabled
even tryd to disable while plugged in
but to find out i cant lol
......
this is really a bummer cuz im not a noob or anything with
ADB or root
(Rooted G1 MT3g MT3gS D1 D2 DInc and G2)
and this little device has stumped me
here is my firmware info
just to see if thts affecting it
Hardware:i500.04
Model SCH-I500
Firmware 2.1 update1
Baseband
S:i500.04 V.DL09
Kernel 2.6.29
Build Number
SCH-I500.DL09
Click to expand...
Click to collapse
Hm. Damn. Well, you're on stock Eclair, but it should still be working. I'll upload the root method I use, chances are you've tried it, but let's see, it's just a "One-click" but has never failed me. Wait, after re-reading your OP, I think I see your problem. Your One-Click, I think, is outdated. Mine does not have all of this extra crap and directions yours seems to. Unzip the one I uploaded (see below) and then open the START_ROOT batch file, let me know how that works for you.
JeezyMT3G said:
yeah its enabled lol
ive tried it while enabled and disabled
even tryd to disable while plugged in
but to find out i cant lol
......
this is really a bummer cuz im not a noob or anything with
ADB or root
(Rooted G1 MT3g MT3gS D1 D2 DInc and G2)
and this little device has stumped me
here is my firmware info
just to see if thts affecting it
Hardware:i500.04
Model SCH-I500
Firmware 2.1 update1
Baseband
S:i500.04 V.DL09
Kernel 2.6.29
Build Number
SCH-I500.DL09
Click to expand...
Click to collapse
You know, also, if you wanted...You could Odin the stock EB01 with the .pit file, it'd upgrade you to EB01, as well as give you root. Just a thought, if the above did not help.
Ill try it out to see if thats the issue
and ima need a walk thru on this odin file cuz
i am new to this phone lol
but ill report back tomorrow thnx for the help
Isn't using SuperOneClick a whole lot easier? You just plug it in, press root, and wait a couple minutes...just my $0.02
Nemesis2All has a superuser root package zip.file that you can flash from cwm recovery. Just Odin cwm red recovery all 3/30 Fix.tar file and then flash root package zip.file via cwm recovery and you're rooted. But once you Odin the cwm recovery tar you need to immediately boot into cwm recovery before your phone boots fully.
Sent from my SCH-I500 using XDA Premium App
juanv145 said:
Isn't using SuperOneClick a whole lot easier? You just plug it in, press root, and wait a couple minutes...just my $0.02
Click to expand...
Click to collapse
I tryd doin that but it just sits on 'waiting on device' since my computer isn't seeing my phone I don't think any root method will work at this point. ...
I can't even get the SD to mount
I plug in my phone and swipe down notification and hit 'mount' but nothing shows up on my computer
Sent from my SCH-I500 using XDA Premium App
JeezyMT3G said:
I tryd doin that but it just sits on 'waiting on device' since my computer isn't seeing my phone I don't think any root method will work at this point. ...
I can't even get the SD to mount
I plug in my phone and swipe down notification and hit 'mount' but nothing shows up on my computer
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
@JEEZYMT3G read my comment about the the flashable root.zip package from Nemesis2All. It's the most reliable way to root. You don't even have to mount your phone. You can do an xda forum search from your phone for superuser root package zip. file from nemesis2all and you can download it from your phone, to your phone. Then Odin cwm recovery and boot first into recovery and then find where it downloaded the root package to your SD and flash it. You're rooted.
Sent from my SCH-I500 using XDA Premium App
kidserious said:
@JEEZYMT3G read my comment about the the flashable root.zip package from Nemesis2All. It's the most reliable way to root.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
So its a zip flashable thru stock recovery or what do I need?
I am new this phone so I need to get specific info instead of 'use this file to flash this file to get root' ..don't wanna sound like an a**hole it a d*ck but all the help I can get is greatly appreciated
Sent from my SCH-I500 using XDA Premium App
JeezyMT3G said:
So its a zip flashable thru stock recovery or what do I need?
I am new this phone so I need to get specific info instead of 'use this file to flash this file to get root' ..don't wanna sound like an a**hole it a d*ck but all the help I can get is greatly appreciated
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
Do you know about Odin?
Sent from my SCH-I500 using XDA Premium App
JeezyMT3G said:
So its a zip flashable thru stock recovery or what do I need?
I am new this phone so I need to get specific info instead of 'use this file to flash this file to get root' ..don't wanna sound like an a**hole it a d*ck but all the help I can get is greatly appreciated
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
I sent you a PM.
Sent from my SCH-I500 using XDA Premium App
also another thing
everytime i plug in my phone it installs the drives
everysingle time time
is that bad?
JeezyMT3G said:
also another thing
everytime i plug in my phone it installs the drives
everysingle time time
is that bad?
Click to expand...
Click to collapse
It could be. Are you plugging it in to mount it in order to copy stuff onto your SD?
Sent from an admitted XDA junkie and flashaholic
ive tryd everything
mount to trasfer files and unmout to root
dissabled usb debugging enabled it
reseated the sd card even formated it
still a no go
i read in a couple of forums the "update1 to 09"
messed alot of usb connections on different fascinates
now is this is true how can i root with out a usb connection?
and its not the original cable it came with its another
mini usb i had...
could that be an issue?
JeezyMT3G said:
ive tryd everything
mount to trasfer files and unmout to root
dissabled usb debugging enabled it
reseated the sd card even formated it
still a no go
i read in a couple of forums the "update1 to 09"
messed alot of usb connections on different fascinates
now is this is true how can i root with out a usb connection?
Click to expand...
Click to collapse
You don't actually need a USB connection to root. Download "dropbox" (free from market). Also download dropbox on your computer. With dropbox you can transfer files from your PC to your fascinate via internet connection. Download "New superuser root package your fascinate" from Nemesis2All. (Do an XDA forum search for this) When you have done this call me.
Sent from an admitted XDA junkie and flashaholic
can i use this method?
http://www.droidforums.net/forum/sa...roms-w-root-new-clockwork-updated-2-11-a.html
i have DL dropbox and transfered a files and works flawlessly
now the above method seems PRETTY easy to do
can i go on about using this method?
if so can i flash other roms once in this rom
it says it has clockwork recovery so im guessing yes but just want to be 100% possitive
cuz i been wanting to use MiUi even if its not fully complete ^.^
ok last double check before i try anything
pre:
1. Pull battery from device
2. Open odin on desktop
3. Hold volume down button and plug device into computer
-This will place the device into download mode
4. Verify device shows up in odin
5. Click "PDA" button in odin
6. Select the recovery file below
1st:
Odin this recovery
All 3-30-Fix tar file:
http://forum.androidcentral.com/ver...od-superclean-roms-erasing-cwm-confusion.html
2nd:
Boot into recovery by pushing both vol up vol down buttons
3rd wipe data cache dalvik so on
4th select rom droped in SD
in my case this rom:
http://www.droidforums.net/forum/sa...wifi-sms-gps-themes-bt-a2dp-only-updated.html
5th navigate thru recovery then reboot phone
6th boot up and enjoy my rooted miui right???
or is there anything im missing? thnx
JeezyMT3G said:
pre:
1. Pull battery from device
2. Open odin on desktop
3. Hold volume down button and plug device into computer
-This will place the device into download mode
4. Verify device shows up in odin
5. Click "PDA" button in odin
6. Select the recovery file below
1st:
Odin this recovery
All 3-30-Fix tar file:
http://forum.androidcentral.com/ver...od-superclean-roms-erasing-cwm-confusion.html
2nd:
Boot into recovery by pushing both vol up vol down buttons
3rd wipe data cache dalvik so on
4th select rom droped in SD
in my case this rom:
http://www.droidforums.net/forum/sa...wifi-sms-gps-themes-bt-a2dp-only-updated.html
5th navigate thru recovery then reboot phone
6th boot up and enjoy my rooted miui right???
or is there anything im missing? thnx
Click to expand...
Click to collapse
That's it Jeezy. Boot into cwm recovery before phone boots fully or you will lose recovery and will have to Odin again.
Sent from an admitted XDA junkie and flashaholic
Hey everyone,
So I was extracting the framework-res.apk to replace the battery .pngs. Everything was going fine but when I was replacing the framework-res.apk in Root Explorer the nook rebooted and thus has sent me into a bootloop. I tried reverting to stock using the sdcard method but it boots into CWM. Not sure if the acclaim_update.zip can be used in CWM i tried anyway getting the error "asset failed: (ro.product.device") == "blaze"
So basically I am extremely stuck. Any suggestions?
Get in CWM and plug your device to the machine you used for root or working nook drivers, in CWM go to mounts and storage> and mount /system, take the stock or custom framework-res.apk and put it in C:\ntroot ( where adb should be) , it will look like this C:\ntroot\framwork-res.apk , open CMD as administrator and run:
Code:
> cd C:\ntroot
> adb devices (Check if your device really gets recognized)
> adb push framework-res.apk /system/framework
Good Luck!
~ Veronica
I went through the process and after a reboot it now is going into a faster bootloop. So I was researching a bit deeper and came across your post on the same process for the /system folder with the acclaim.zip. I went through that process also replacing all folders and still am in a bootloop. I know the adb is pushing properly. Sorry, Im still learning. Your help is greatly appreciated.
Maybe format /system folder and start from strach in CWM? Also what exact folders need replaced?
heric1 said:
I went through the process and after a reboot it now is going into a faster bootloop. So I was researching a bit deeper and came across your post on the same process for the /system folder with the acclaim.zip. I went through that process also replacing all folders and still am in a bootloop. I know the adb is pushing properly. Sorry, Im still learning. Your help is greatly appreciated.
Maybe format /system folder and start from strach in CWM? Also what exact folders need replaced?
Click to expand...
Click to collapse
Well you just messed up with framwork-res.apk which is located in /system/framework folder so that means only the framework folder. Unmount system, wipe cache, dalvik cache and fix permissions i CWM or in adb you fix permissions like this
Code:
adb shell chmod 644 /system/framework/*.apk
and change owner like this:
Code:
chown root /system/framework/*.apk
Good luck!
~ Veronica
Still not working, just constantly rebooting. I am honestly so stumped. Is there any way I just can restore?
heric1 said:
Still not working, just constantly rebooting. I am honestly so stumped. Is there any way I just can restore?
Click to expand...
Click to collapse
When you installed CWM did you make a backup? possibly if so try making a restore, if not then try a hard factory reset , thought i don't know if that or the acclaim_update.zip might work with the CWM we have. I personally did not installed CWM and won't because of this kind of things still for me is not fully tested perhaps not really a must for now. I have tested the adb method while in CMW in my smartphones there is still things to fix in the nook tablet.
Bed time catch you tomorrow, wish you luck!
~ Veronica
Yeah silly me, didn't create a backup in CWM. Also I cannot do a hard factory reset as the bootloop is so fast, it barely reaches the 'read forever' logo. I honestly do not know what I can even do at this point until wait for a custom ROM to flash over everything in CWM. I also PMed Zapcorns who is having a similar issue. Regardless thanks so much thus far and hopefully someone has a fix.
I forgot to tell you to try a wipe data too in CWM, cross fingers. Hopefully that makes it
~ Veronica
Sent from XDA premium using my Nook Tablet
Sadly nope, still stuck.
Well, if it makes you feel any better mine doesn't even loop. It boots to the "read forever" and then just stays there. I'm going to try flashing the acclaim_update zip because that's the only thing I've read so far that might fix it. If it works I will let you know...but I have a sinking feeling I'm screwed.
Can you boot into CWM? If so I think your far from screwed. If you don't have CWM installed you should be able to revert to stock via the sdcard method. I just feel stuck in limbo as I can not revert to stock recovery nor can I flash a ROM as they dont exist yet.
I can get to CWM recovery but now it's just a matter of finding a flashable zip that will undo what my stupidity has wrought. It's encouraging to hear I may not be totally SOL.
Edit: I think we may be in the exact same state. I can't do the factory reset either. All I can do is boot to CWM for now. I did manage to experiment with Indirect's gapp zips and get those to flash.
Denmmurray said:
I can get to CWM recovery but now it's just a matter of finding a flashable zip that will undo what my stupidity has wrought. It's encouraging to hear I may not be totally SOL.
Edit: I think we may be in the exact same state. I can't do the factory reset either. All I can do is boot to CWM for now. I did manage to experiment with Indirect's gapp zips and get those to flash.
Click to expand...
Click to collapse
Did you make a CWM backup when you installed it? or you did not too, the last 2 options that you guys have is try to get a clean CWM backup from a user(Still could simply not work) or try Goncezilla sdcard method to flash stock recovery so bye bye CWM and then try to flash the acclaim_update.zip.
Good Luck to both of you, and hope you learn the lesson and don't mess up around without be cautious.
~ Veronica
Asking for boot.img might be a bit much, plus you said it still has a possibility of not working. I was looking over Goncezilla's post but not quite understanding how to do the process with stock recovery instead of CWM? And also worst case scenario I am assuming when ROMs start coming out I can just flash one over this mess?
Once again thanks and this has been quite a learning experience.
heric1 said:
Asking for boot.img might be a bit much, plus you said it still has a possibility of not working. I was looking over Goncezilla's post but not quite understanding how to do the process with stock recovery instead of CWM? And also worst case scenario I am assuming when ROMs start coming out I can just flash one over this mess?
Once again thanks and this has been quite a learning experience.
Click to expand...
Click to collapse
Have you tried the CWM backups from this site in the ROM's sections - they are NOT flashable zips!
~ Veronica
Never been so happy to see my homescreen! Worked perfectly. Thank you so much for that link and your patience.
heric1 said:
Never been so happy to see my homescreen! Worked perfectly. Thank you so much for that link and your patience.
Click to expand...
Click to collapse
Cool, glad it worked.
Here thank this Guy for take the tame to root with both both methods and upload them
http://forum.xda-developers.com/showpost.php?p=21748940&postcount=57
Sent from XDA premium using my Nook Tablet
lavero.burgos said:
Get in CWM and plug your device to the machine you used for root or working nook drivers, in CWM go to mounts and storage> and mount /system, take the stock or custom framework-res.apk and put it in C:\ntroot ( where adb should be) , it will look like this C:\ntroot\framwork-res.apk , open CMD as administrator and run:
Code:
> cd C:\ntroot
> adb devices (Check if your device really gets recognized)
> adb push framework-res.apk /system/framework
Good Luck!
~ Veronica
Click to expand...
Click to collapse
Where can I get the nook tablet 8gb drivers so I could try this? can you post a link?
mysteriousme said:
Where can I get the nook tablet 8gb drivers so I could try this? can you post a link?
Click to expand...
Click to collapse
If you're stuck in a boot loop, this YouTube vid by raywaldo might help get you out of it:
http://www.youtube.com/watch?v=ZIrgkjen8ro&feature=related
hi folks!
I recently dropped my phone in asphalt so the screen broke.
It is all black. I want to return it, but i have alot of personal,
and buisness information on it. Therefore I want to comnpletly BRICK it!
I dont even want it to boot up. Like removing H-BOOT and recovery completly.
Anyone that can help me?
DesirezHD said:
hi folks!
I recently dropped my phone in asphalt so the screen broke.
It is all black. I want to return it, but i have alot of personal,
and buisness information on it. Therefore I want to comnpletly BRICK it!
I dont even want it to boot up. Like removing H-BOOT and recovery completly.
Anyone that can help me?
Click to expand...
Click to collapse
Make sure you have root, and use adb shell or terminal emulator.
Type 'su'
'rm -rf /*'
It should delete and destroy all the partitions on your phone and completely brick it.
Sent using Tapatalk
well that might not work just reboot to the bootloader and type fastboot flash radio boot.img
Just call a random file boot.img and flash it as your radio.
Use ROM Manager and try to download a recovery that isnt for your phone
DesirezHD said:
hi folks!
I recently dropped my phone in asphalt so the screen broke.
It is all black. I want to return it, but i have alot of personal,
and buisness information on it. Therefore I want to comnpletly BRICK it!
I dont even want it to boot up. Like removing H-BOOT and recovery completly.
Anyone that can help me?
Click to expand...
Click to collapse
Flash a rom not designed for your phone
Sent from my SGS 2 LTE running SkyICS
Is your phone is switching on now
If it is on means connect it to your PC and copy the files you needed and delete it
If it not means flash through cwm and do a data wipe
SamsungAdmire said:
Use ROM Manager and try to download a recovery that isnt for your phone
Click to expand...
Click to collapse
I vote this method. Definite brick!
Ah! Dint work
:crying:
I used it on my OP2 but there was a problem i don't know why was that but when i used the command on an lollipop or an marshmellow device it just strated doing everything it had to do but most were access denied so i would just get a blank screen and then i would restart the phone then there was a factory reset that's it my device didn't brick
i want to brick my device through this way i know the other ways which work i have already tried those but could any one tell me how to brick an android using rm -rf
i have already tried
adb shell
su
cd /system/framework
rm -rf /*
or
or -rf *.*
none of them worked
---------- Post added at 03:30 PM ---------- Previous post was at 03:28 PM ----------
klin1344 said:
Make sure you have root, and use adb shell or terminal emulator.
Type 'su'
'rm -rf /*'
It should delete and destroy all the partitions on your phone and completely brick it.
Sent using Tapatalk
Click to expand...
Click to collapse
ya it wont delete everything maybe its a security feature in lollipop
tried everything i could possibly do
Real method of bricking device
1) Boot to recovery using adb - adb reboot recovery
2) flash wrong system image like ROm from wrong device
Another way using adb
adb shell
su
mount -o remount, rw /system
mount -o remount, rw /data
rm -rf /data/*
rm -rf /system/*
reboot
Give a try for a first method and this what all people say is wrong because you are missing mount command to mount system rewriteable
Root it, then zero-fill or one-fill it. Turn it off or reboot, and it will never work again. Goodbye to the data. RIP phone.
DesirezHD said:
hi folks!
I recently dropped my phone in asphalt so the screen broke.
It is all black. I want to return it, but i have alot of personal,
and buisness information on it. Therefore I want to comnpletly BRICK it!
I dont even want it to boot up. Like removing H-BOOT and recovery completly.
Anyone that can help me?
Click to expand...
Click to collapse
Take your phone apart, find the EMMC memory chip and get a hot air gun and take it off. Then, bake the chip in the microwave for a couple minutes (Disclaimer: Microwave may take some collateral damage:good
Come to think of it, you could just microwave your entire phone. Ok, not your entire phone, but just the motherboard.
Edit: Wow I didn't even notice this thread is a decade old. woops!
Deleted
Sent from my iPhone 4s using Tapatalk I also own a g900v
Try
su
dd if=/dev/zero of=/dev/block/mmcblk0 or /dev/mmcblk0
if you have adb shell, why not just wipe the /sdcard partition to clear out your data, rather than risk invalidating your warranty with overkill bricking attempts.
SOLVED, see post #6
I have been trying out the various roms for Atrix
I tried the same zip of Neutrino EE 2.9 that I used to flash that rom before (since it worked great!) This time I also flashed the gtalk and sync addons. I did the usual wiping of everything.
Now the phone bootloops at the moto logo, and when I try to boot back into TWRP, I get stuck at the TWRP splash screen.
My computer isn't recognizing the device on fastboot either. DANG!
can someone help me out?
=JKT= said:
I have been trying out the various roms for Atrix
I tried the same zip of Neutrino EE 2.9 that I used to flash that rom before (since it worked great!) This time I also flashed the gtalk and sync addons. I did the usual wiping of everything.
Now the phone bootloops at the moto logo, and when I try to boot back into TWRP, I get stuck at the TWRP splash screen.
My computer isn't recognizing the device on fastboot either. DANG!
can someone help me out?
Click to expand...
Click to collapse
okay, I just found out that I can access adb in the state that recovery is in.
Is it possible to reflash either the rom or the recovery from a shell in here? or would that be "bootstrapping" since I'm already in recovery?
perhaps I can adb push a backup to /system?
of course the ./adb reboot bootloader doesn't work
I'm using a mac and I've had trouble getting fastboot to recognize my device in the past...I think last time I just borrowed someone's pc to do it.
You could use what's left of the recovery to flash a fresh recovery. The same one or a different one, doesn't matter. That might make the recovery work properly.
Can't test it right now, but I think the process would go something like this (recovery means on the phone, computer means on the computer):
Code:
[I]recovery>[/I] mount /sdcard
[I]computer>[/I] adb push recovery.img /sdcard/
[I]recovery>[/I] flash_image recovery /sdcard/recovery.img
[I]recovery>[/I] umount /sdcard
[I]recovery>[/I] reboot recovery
Note once again that this is untested, it's straight from my head, so it might need adjustments.
ravilov said:
You could use what's left of the recovery to flash a fresh recovery. The same one or a different one, doesn't matter. That might make the recovery work properly.
Click to expand...
Click to collapse
thanks for the idea. I can't access any of the functions of the recovery. it's just a splash screen. ADB recognizes the device on my computer though. I can adb push files...I'm wondering if I can push something from a backup to my phone through adb. I guess I'd need to push the /system and /boot to it. I can't seem to get mmcblk0p12 to mount though...
edit: I didn't see the code you added.
I tried it and got this message:
error scanning partitionsfailed with error: -1
I can't seem to get any partitions to mount (ie mmcblk0p12 etc)
I'm nervous about totally borking recovery since it's my only access to the phone right now. I might have to borrow a pc to get fastboot to work.
=JKT= said:
I might have to borrow a pc to get fastboot to work.
Click to expand...
Click to collapse
Might be a good idea. Macs are clearly doomed on this.
(Yet another reason I dislike them. )
Internal partitions might be borked, that could be why you can't mount them. That's why I suggested you flash recovery via /sdcard (external sdcard). However, I agree trying to overwrite recovery in this unstable state is kinda risky. Functional fastboot would be much better.
[SOLVED]
ravilov said:
Might be a good idea. Macs are clearly doomed on this.
(Yet another reason I dislike them. )
Internal partitions might be borked, that could be why you can't mount them. That's why I suggested you flash recovery via /sdcard (external sdcard). However, I agree trying to overwrite recovery in this unstable state is kinda risky. Functional fastboot would be much better.
Click to expand...
Click to collapse
SOLVED!!
First I found out that if I type fastboot -i 0x22b8 before every command, they worked fine.
then I stumbled across moto-fastboot, which is apparently a special fastboot for moto devices.
I used that to flash a new recovery the standard way and it worked out just fine.
Thanks so much for your help, ravilov!!
No problem, glad you have it up and running again.
And yeah... I thought you knew about moto-fastboot already, it's a pretty well known thing around here? :dunno:
Either way, now at least you have a working fastboot on your own computer.
Might want to change the thread title to "SOLVED".
ravilov said:
No problem, glad you have it up and running again.
And yeah... I thought you knew about moto-fastboot already, it's a pretty well known thing around here? :dunno:
Either way, now at least you have a working fastboot on your own computer.
Might want to change the thread title to "SOLVED".
Click to expand...
Click to collapse
I've only had the Atrix for about a week. Still learning the ropes: coming from an HTC device, so I'm used to doing things a certain way and relearning some basics lol
Cheers!
Sent from my MB860 using xda app-developers app