Related
running rod's miui rom and was trying to remove excess crap via titanium pro. when trying to remove facebook it would reboot and give an error message about signature failure. so i thought i'd see if it would successfully remove a different app. rod included a fancy widget app that i had no desire for. when trying to remove that, it did a number on my n1. i cannot get into the recovery mode or anything.
this is a video of what the phone now does. no matter if i pull the battery or what.
http://www.youtube.com/watch?v=6a4DP3IjZiQ
That's an interesting one.
When you turn it on - this is the first thing you see? No "X" at all?
Did you try ADB to see if it sees the device?
Looks just like radio flash, but with radio flash there are no recovery messages, if I remember correctly.
no, i get the un-animated X, and then it goes straight to this. regardless if i hold down the trackball or not.
what do i need to do to try to adb to it? i don't fool with adb ever, just when i first rooted/unlocked it.
Put a diff update.zip for another rom on your sdcard. Lemme know if it works
Sent from my Bionixed SGH-T959 using XDA App
brnbock said:
Put a diff update.zip for another rom on your sdcard. Lemme know if it works
Sent from my Bionixed SGH-T959 using XDA App
Click to expand...
Click to collapse
i took enoms rom, renamed it update.zip and placed it on the sdcard. still nothing, same thing.
if i press the powerbutton whilst on the android out of the box thing it says.
"ClockworkMod Recovery v2.5.1.0
Finding Update Package........
Opening Update Package.......
Verifying Update Package......
Installing Update....."
this is shown in the video, but blurry and hard to read.
well, if im doing things right..... adb remount said it successfully did so.
(edit) ok, i can definitely connect via adb, i just ran the reboot bootloader command and the phone rebooted..... albeit back to that stupid looping screen.
any other ideas folks...... i'm up against a wall here.
i am able to get this in terminal
[email protected]:~/Android/tools$ ./adb devices
List of devices attached
HT02KP901120 recovery
[email protected]:~/Android/tools$
You need a rom that can be flashed as an update.zip, most are not flashed that easy. Can you get into fastboot?
Sent from my Bionixed SGH-T959 using XDA App
brnbock said:
You need a rom that can be flashed as an update.zip, most are not flashed that easy. Can you get into fastboot?
Sent from my Bionixed SGH-T959 using XDA App
Click to expand...
Click to collapse
i don't think so
Try booting into fastboot, if you can your good if not then I will do some digging.
Sent from my Bionixed SGH-T959 using XDA App
brnbock said:
Try booting into fastboot, if you can your good if not then I will do some digging.
Sent from my Bionixed SGH-T959 using XDA App
Click to expand...
Click to collapse
well, i cant get to the recovery screen to initiate fastboot. if i use adb reboot-recovery it just reboots the phone and goes back to the looping crap i'm stuck at.
if i try any fastboot commands, i get nothing. i just can't get it to do anything other than respond to adb commands.
a fella from nexus one forums suggests that perhaps my bootloader is messed up and needs to be restored? that sound possible?
That was this fella, and I'm actually more convinced that the recovery is stuck trying to do an update... xD
Sent from my Nexus One using XDA App
danger-rat said:
That was this fella, and I'm actually more convinced that the recovery is stuck trying to do an update... xD
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
haha. the omnipresent danger-rat is indeed the fella.
I was hoping Jack or Rusty would be here to check my logic...
Here's what we believe so far:
1 - phone appears to be in recovery, and trying to install an update.
2 - phone is in recovery, so adb is (kinda) working.
3 - there's no update.zip on the SD card.
4 - trying to overwrite the recovery via adb gives a "device or resource busy" response...
My guess is that if the install process can be killed, then you should be able to re-gain control?
...I've no idea how to kill processes via adb... :-(
Sent from my Nexus One using XDA App
Woooooo HOOOOOOOO!!!!!!!!!!!!!!!!!!
i'm not entirely sure what i did......... but i think i have it. i transfered amon's 1.7.0 img to the sdcard and aptly renamed it recovery.img. after just now trying to restart to see if i could get fastboot to do anything it must have found the recovery.img and reflash amon. i'm looking at amons recovery now as i type.
i just rebooted and now i'm back into rods miui...... phone is working fine.
danger-rat said:
I was hoping Jack or Rusty would be here to check my logic...
Here's what we believe so far:
1 - phone appears to be in recovery, and trying to install an update.
2 - phone is in recovery, so adb is (kinda) working.
3 - there's no update.zip on the SD card.
4 - trying to overwrite the recovery via adb gives a "device or resource busy" response...
My guess is that if the install process can be killed, then you should be able to re-gain control?
...I've no idea how to kill processes via adb... :-(
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
just wanted to say thanks so much for all your effort and help man.
now a new quick question... which is what started this whole fiasco.
how can i remove unwanted apps from rods miui rom?
noremacyug said:
now a new quick question... which is what started this whole fiasco.
how can i remove unwanted apps from rods miui rom?
Click to expand...
Click to collapse
adb shell
su
rm -rf /system/app/nameofapp.apk
once the apps are deleted:
(on the phone)
go to settings--> manage applications
and delete any leftover files pertaining to the programs you just deleted
Reboot
Then reboot and make a backup
*EDIT*
You may need to reboot after removing the programs for those file to show up in Manage Applicaions
Okey, before FRG83D I rooted my phone with SuperOneClick. Then I decided to go back to the original ROM, and update to FRG83D. As you know, this revoked my root access. So now I unlocked the bootloader and ran Superboot. However I don`t get rooted. My suspicions are that because my old Superuser apk is left, something goes wrong. Plz help me figure this out!
Well all need a root for 2.2.1
Sent from my Nexus One using XDA App
Shivammcool said:
Well all need a root for 2.2.1
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Are you telling me there is NO way to root 2.2.1 ? :O
No, I think the other guy is just thinking of a root-without-unlock method.
You are already unlocked. So it's just a matter of changing the system correctly to root it. Easiest way is to probably flash an already rooted stock build over it. (I assume you want to remain stock)
Or at least you need to find the correct way to root 2.2.1, which is hard because there are probably a lot of people out there looking for a root without unlocking, so that will pollute your search results.
Edit: Of course, I could be way off base and not know what I'm talking about.
Yup, flash a rooted stock rom, like Geo's.
I still don't know why people love to make things harder on themselves than it needs to be lol.
Okey, this is kinda crazy, because Adblock is working and has all permission, but nothing else!
Sent from my Nexus One using XDA App
MrSvedberg said:
Okey, this is kinda crazy, because Adblock is working and has all permission, but nothing else!
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Not familiar with Adblock, but if it is similar to AdFree it just works by replacing your /system/etc/hosts file with one that directs every advertising address to the loopback address, thus preventing the apps from loading. If that file was in place before you lost root, it will continue to block ads for you.
Okey, but if I just want to flash CM, what do I do? Can't get to recovery :/
Sent from my Nexus One using XDA App
You're unlocked, right? Super easy :-D
Download a recovery *.img (or extract it from a recovery .zip).
Reboot your N1 to fastboot mode (press and hold VOL-DOWN while powering on - press Power to select Fastboot USB when the option is presented).
Connect your USB cable.
Run fastboot flash recovery recovery.img (replacing "recovery.img" with the appropriate file name). When complete, you have an aftermarket recovery again.
Boot to recovery and install whatever ROM you want
codesplice said:
You're unlocked, right? Super easy :-D
Download a recovery *.img (or extract it from a recovery .zip).
Reboot your N1 to fastboot mode (press and hold VOL-DOWN while powering on - press Power to select Fastboot USB when the option is presented).
Connect your USB cable.
Run fastboot flash recovery recovery.img (replacing "recovery.img" with the appropriate file name). When complete, you have an aftermarket recovery again.
Boot to recovery and install whatever ROM you want
Click to expand...
Click to collapse
Thx a lot m8, but could you dumb that down just a little bit? Still a bit n00b in the area x)
Sent from my Nexus One using XDA App
Those steps are broken down a bit more specifically (including prerequisites) in this thread, which I found from the NexusOne Wiki, which is a great place to look for such common information.
Done it, and I'm 110 % sure I did it right! Still does not work!
Sent from my Nexus One using XDA App
What part are you having trouble with?
Can't boot into recovery...
Sent from my Nexus One using XDA App
MrSvedberg said:
Can't boot into recovery...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I'm afraid you'll have to be more descriptive than that.
HOW are you trying to boot to recovery? There are several methods:
1) Issue the adb reboot recovery command
2) Boot to the bootloader (press and hold Volume-Down while powering on), use the volume keys to scroll down to Recovery, and the power button to launch it.
3) Use an application like Quick Boot to reboot directly to recovery from the OS, though that may require a working root.
Have you tried these methods? If so, what happened? What did you see on the screen?
Number 2. Just seeing an Android and a triangle.
Sent from my Nexus One using XDA App
MrSvedberg said:
Number 2. Just seeing an Android and a triangle.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Then that is the stock recovery. Flashing a third-party recovery was not successful. Did you receive any error messages from the fastboot flash recovery recovery.img command?
Your bootloader IS unlocked, right? You have a padlock icon on the bottom of the screen immediately after poweron?
The flash was successful, no error messages. And yes, the padlock is there.
Sent from my Nexus One using XDA App
MrSvedberg said:
The flash was successful, no error messages. And yes, the padlock is there.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
What recovery image are you trying to use?
Does anyone want to mess with my d3 to gfix the bootloop its in. Tryed the way it says to in the other thread no go. Please help
Sent from my DROID2 using Tapatalk
I've fixed three bootloops on my phone so far... not saying it'll be possible, but what did you do and what have you tried, specifically?
Jewremys mods framework.jar.apk installed that. That's it. In system/framework. Tried the adb method to get out of bootloop. Thanks for trying to help.
Sent from my DROID2 using Tapatalk
sparkyman216 said:
Jewremys mods framework.jar.apk installed that. That's it. In system/framework. Tried the adb method to get out of bootloop. Thanks for trying to help.
Sent from my DROID2 using Tapatalk
Click to expand...
Click to collapse
Have you tried PM'ing the author?
No
Sent from my DROID2 using Tapatalk
sparkyman216 said:
No
Sent from my DROID2 using Tapatalk
Click to expand...
Click to collapse
will your phone show up in adb at all? i did the same thing you did and mine showed up in adb when it was bootlooping. if it does you will need to re-root then adb push the backed up(original)framework res
It's not framework.jar.apk. it's framework-res.apk. OP, if you pushed it to framework.jar, you're probably screwed. Go learn before you flash something next time.
Sent from my DROID3 using Tapatalk
Jewremy said:
It's not framework.jar.apk. it's framework-res.apk. OP, if you pushed it to framework.jar, you're probably screwed. Go learn before you flash something next time.
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
would this be the reason quite a few people have soft bricked?
OK I made mistake in my typing I didn't mean to type jar. Thank you some of u for trying to help
And sorry to others for wasting your time.
Sent from my DROID2 using Tapatalk
sparkyman216 said:
OK I made mistake in my typing I didn't mean to type jar. Thank you some of u for trying to help
And sorry to others for wasting your time.
Sent from my DROID2 using Tapatalk
Click to expand...
Click to collapse
You're not wasting any of our time. We've all been there. I've had a long day at work. I'd help if I could, but no sbf just yet...
If you enabled USB debugging, you can connect ADB from the BP Tools menu mentioned here:
http://forum.xda-developers.com/showthread.php?t=1236465
Keep in mind that even with ADB connected, the phone will continue to boot loop (and make annoying sounds) over and over and over while you're in ADB. So just because it keeps booting, don't think that ADB won't work.
If you didn't enable USB debugging though and can't get out of a bootloop, then I would recommend a factory reset from the recovery menu. Same process as mentioned in that other thread, but select Recovery instead. When the triangle appears, press vol+ and vol- at the same time, then choose to format/wipe data (vol+/- to select, power to confirm). Then reboot again.
At this point, if you get through activation where you've entered your google account, but FC after that (happened to me), try sending yourself a text message with a market link to a third-party launcher, like ADW Launcher or Go Launcher. Use the link to launch the market, to install the launcher, to run the launcher, to get to settings, and ENABLE USB DEBUGGING.
Hope some of that helps.
if he pushed something to /system, clearing /data wont get him out of the bootloop
I went to restore my backup via clockwork mod and now my phone is stuck on the Motorola Logo. Any suggestions? Need help. Can't get into recovery through Bp Tools.
check out this RSD thread
http://forum.xda-developers.com/showthread.php?t=1255198
you can flash the fastboot by going into recovery.
MrJudylicious said:
check out this RSD thread
http://forum.xda-developers.com/showthread.php?t=1255198
you can flash the fastboot by going into recovery.
Click to expand...
Click to collapse
Can't get rsd lite to install on my computer. Don't know what I'm doing wrong. Follow the instructions to the letter and nothing.
I was able to use Psouza unbrick script and it got my phone up and running. Thank you very much for your reply though.
Sent from my DROID3 using XDA App
Joe.cotto said:
I was able to use Psouza unbrick script and it got my phone up and running. Thank you very much for your reply though.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
This?
http://forum.xda-developers.com/showpost.php?p=17427668&postcount=84
Nah. It's on Rootzwiki under "Unbrick DROID 3". I have the link at home.
Sent from my DROID3 using XDA App
Joe.cotto said:
I went to restore my backup via clockwork mod and now my phone is stuck on the Motorola Logo. Any suggestions? Need help. Can't get into recovery through Bp Tools.
Click to expand...
Click to collapse
use x + power button and go to android recovery
1. press x first then power button
2. when the m logo shows let go the power button but keep pressing the x
3. when triangle shows, press volume up and down at the same time
then the screen will show android system recovery
do a wipe cache first then wipe data/factory reset
then reboot your phone..
if this doesn't work, sbf is the only choice left as far as i know of
Joe.cotto said:
Can't get rsd lite to install on my computer. Don't know what I'm doing wrong. Follow the instructions to the letter and nothing.
Click to expand...
Click to collapse
Even if RSD lite 5.5 is usually working even on win vista and seven X64, XP is still the better choice to flash phones.
Use it, even virtualized.
I was able to get it running again using the Psouza script. Thank you guys. I keep all that in mind if it happens again.
Sent from my DROID3 using XDA App
So I'm on the latest JB firmware and I am rooted. However, my phone will randomly freeze and I want to perform a factory reset to fix the problem. Can I restore root using Voodoo, or is there any other way perhaps?
Sent from my Motorola ATRIX™ HD
install safestrap before reset.. so you`ll have root 4ever i think
Root is usually kept after factory reset. Because the related hack is done inside the system directory？
Sent from my MB886 using Tapatalk 2
You cannot, I've done that already and list root after my phone got bricked. Use safestrap
Sent from my Atrix HD using Tapatalk app
BreakShadow said:
You cannot, I've done that already and list root after my phone got bricked. Use safestrap
Sent from my Atrix HD using Tapatalk app
Click to expand...
Click to collapse
Really? That's funny. Then how did I reset my stock JB rooted AHD twice yesterday and still manage to have root afterwards?
Sent from my MB886 using xda app-developers app
RCon227 said:
Really? That's funny. Then how did I reset my stock JB rooted AHD twice yesterday and still manage to have root afterwards?
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
My bad, I misread, I was thinking about RSD. Lost my root flashing the SBF after my phone got bricked by CF3D
Sent from my Atrix HD using Tapatalk app
just safestrap and give slot1 all the free space on the inernal memory.. its like 1gb system 3gb data
that should give you plenty of space for apps and just use an sd card for storage..
that way you can reset, reflash, do pretty much anything you want to the system on slot1 and not mess up anything.
So to clarify...I can just factory reset and still retain root?
Sent from my Motorola ATRIX™ HD
MagicXB said:
So to clarify...I can just factory reset and still retain root?
Sent from my Motorola ATRIX™ HD
Click to expand...
Click to collapse
I reset mine and still had root after. I don't see why it would yield a different result for anyone else.
Sent from my MB886 using xda app-developers app
Doing a factory reset shouldn't affect root at all. Most likely, all you have to do is download super user from market and update!
Sent from my MB886 using xda app-developers app
Thanks guys, I did a factory reset and still have root.
Atrix HD soft bricked by audio beats driver
What do I do when I soft brick my atrix HD and only have a titanium backup?
I have the AT&T stock ICS phone but is soft brick and it can't pass the boot logo. Any ideas?
Pharawer said:
What do I do when I soft brick my atrix HD and only have a titanium backup?
I have the AT&T stock ICS phone but is soft brick and it can't pass the boot logo. Any ideas?
Click to expand...
Click to collapse
If you have only encountered a soft brick, it is possible that you could recover by using RSD Lite.
Sent from my Motorola ATRIX™ HD
If anyone is worried, just install safestrap, and make sure you download the flashable zip from the superuser site. If you lose root, you won't, but if, just flash the superuser zip.
I had to do this after trying the MIUI version of superuser.
Sent from my phone.
MagicXB said:
If you have only encountered a soft brick, it is possible that you could recover by using RSD Lite.
Sent from my Motorola ATRIX™ HD
Click to expand...
Click to collapse
Ok so it is repairable, i have read a little about RSDlite and what i get is this (correct me if am wrong):
1. Get RSD Lite 6.14 (recommended version) for Windows only.
2. Get the stock firmware file, make sure you pick the latest ICS firmware file here (7.7.1Q-144_MB886_MR1-22_SIGNED_CFC.xml.zip) for AT&T.
3. After successfully downloaded, extract the zip file. And edit the 7.7.1Q-144_MB886_MR1-22_SIGNED_CFC.xml file using notepad, and then remove 2 lines with getvar.step operation=”getvar” var=”max-download-size”
4. Open RSD Lite, open the XML file that you have edited before.
5. Turn off your phone, and then enter the Boot Mode Selection Menu by press and hold the following keys together (Volume Up+Volume Down+Power). Using vol down, scroll to AP Fastboot menu, and then vol up to select it.
6. Connect Atrix HD to PC via USB, your phone will be recognized by RSD Lite as MB886.
7. Now it’s time to hit the Start button, and please wait for about 10-25 minutes.
8. Once the flash process done, your device will reboot. Your Motorola Atrix HD (MB886) should restore to stock and unroot now.
My phone is from AT&T and has firmware 77.10.16 ICS does this guide is the correct one for me? Or should I try using HD utility? im very noob here so please post noob-friendly answers.
Pharawer said:
Ok so it is repairable, i have read a little about RSDlite and what i get is this (correct me if am wrong):
1. Get RSD Lite 6.14 (recommended version) for Windows only.
2. Get the stock firmware file, make sure you pick the latest ICS firmware file here (7.7.1Q-144_MB886_MR1-22_SIGNED_CFC.xml.zip) for AT&T.
3. After successfully downloaded, extract the zip file. And edit the 7.7.1Q-144_MB886_MR1-22_SIGNED_CFC.xml file using notepad, and then remove 2 lines with getvar.step operation=”getvar” var=”max-download-size”
4. Open RSD Lite, open the XML file that you have edited before.
5. Turn off your phone, and then enter the Boot Mode Selection Menu by press and hold the following keys together (Volume Up+Volume Down+Power). Using vol down, scroll to AP Fastboot menu, and then vol up to select it.
6. Connect Atrix HD to PC via USB, your phone will be recognized by RSD Lite as MB886.
7. Now it’s time to hit the Start button, and please wait for about 10-25 minutes.
8. Once the flash process done, your device will reboot. Your Motorola Atrix HD (MB886) should restore to stock and unroot now.
My phone is from AT&T and has firmware 77.10.16 ICS does this guide is the correct one for me? Or should I try using HD utility? im very noob here so please post noob-friendly answers.
Click to expand...
Click to collapse
This guide is correct, just flash the right ROM(FXZ), that's all.
Sent from my Atrix HD using Tapatalk app
It fail
BreakShadow said:
This guide is correct, just flash the right ROM(FXZ), that's all.
Sent from my Atrix HD using Tapatalk app
Click to expand...
Click to collapse
The flash failed at first but i tried again and it worked. Thanks you just saved my phone!