At long last, I rooted my Motorola A855 today. I used the "SuperOneClick" method. Afterward, I still didn't have Nandroid available at the Recovery Mode Boot Screen, which I found odd, as I thought SuperOneClick would flash SPRecovery automatically.
Reading this page[1], I assumed that I wouldn't need Nandroid, and could just use ROM Manager to meet all my needs.
I installed ROM Manager v3.0.1.4. It seems to be happy with SuperUser permissions, and can "successfully flash ClockworkMod Recovery 2.5.0.1", according to the app, at least. The "Backup ROM" menu option doesn't seem to have any trouble either.
However, "Reboot into Recovery" provides me no new options at the Recovery Mode screen, and "Flash Alternate Recovery: SPRecovery 0.99.3b" gives the cryptic error message "An error occurred while flashing your recovery."
This thread[2] is a discussion others have had with the same issue last year, and they eventually found that it was a server-side issue that cleared up in a few days. Perhaps the issue has reappeared?
So, a few questions:
Does using SuperOneClick to root your A855 permanently damage it?
If not, how do I get nandroid / SPRecovery flashed onto my phone? Should I undo the root job performed by SuperOneClick?
Does ROM Manager now work on this phone (or will it soon)?
Thanks for your help.
Links:
---
Unfortunately, I can't post the links to this forum, as I'm a new member. You'll have to trust me that they exist. (They're both on droidforums dot net.)
I had hit this problem with my Motorola Droid, and finally successfully flashed the ClockworkMod recovery ROM.
After trying to flash the recovery ROM the first time, my phone would only boot to a point of showing a large exclamation point with a phone in front of it.
To troubleshoot, I started with the Droid "Official" FAQ on the CyanogenMod forums. But, like the OP mentions, when I tried to flash the Alternate Recovery, it gave me the "An error occurred while flashing your recovery." error.
So, I then determined to manually flash the SPRecovery ROM. I found a file which purported to contain the ROM at ted.servepics.com (in TeddysRageRooterPkg.zip), and though I didn't trust the file entirely, even after a virus scan, I flashed it manually.
To flash manually, I opened a terminal and ran:
Code:
/data/data/com.koushikdutta.rommanager/files/flash_image recovery /sdcard/recovery-0.99.3b.img
When I rebooted into the recovery mode, it successfully booted, and then I was able to flash the normal ClockworkMod Recovery ROM.
Related
Hi guys. I don't really know what happened here. I've flashed a few different versions of Cyanogen's builds onto my MT3G without any problems. Today I flashed the official 1.6 dev build of Donut before doing Cyanogen's 4.2.3.1 flash. Well, the 1.6 seemed to go smoothly, but after the reboot, the recovery would no longer load. It's now giving me a picture of the phone with an exclamation point when I try to load the recovery.
How can I fix this? Anyone? Please?
taken from cyanogens website site instructions.
If you boot the 1.6 image it will install the HTC stock recovery. Booting back to recovery will show the /!\[] symbol. THIS IS NOT LOSING ROOT. You can still flash update.zip files from this recovery. Also, you can still flash a nicer (CM-1.4) recovery with fastboot, or flash_image inside the CM install once you get it installed.
thats what sounds like happen to me
How do I do anything though? I don't have the ability to do anything, it just sits there on that screen.
<edit> Also, I can't re-flash the recovery. I've tried, but it gives me the error:
Flash FAILED: The command could not be run
After figuring out how to install ADB and trying to fix it via that, it appears that I have somehow lost root. It's giving me Permission Denied or remote device not allow when I try to flash or use fastboot.
Got it fixed. Took me forever, but I made a goldcard and flashed with the stock ROM. Now I'm good to go again after installing CM recovery 1.4.
Hello All,
Sorry if this has already been solved before, and thanks in advance for help. (I tried to post this in the ARHD41.0 thread, but as a newbie I cannot post there.)
I have an HTC One (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remained S-On. Made a backup through CWM recovery, transferred that to my PC, then figured I might as well celebrate the holidays by flashing my first ROM.
I downloaded the Android Revolution HD 41.0 ROM (forum.xda-developers.com/showthread.php?t=2183023), transferred to the SD, and then installed the zip through the CWM ROM manager (it seemed at least from what I read in the posts that followed that the ROM worked just fine with CWM). After going through the option selection process (I believe that this was the Aroma installer), I opted to wipe data since I was starting from a different ROM altogether (of course, silly me, this also wiped the backup on the SD). Seemed to install just fine, booted into what appears to be some part of the recovery where it asked if I wanted to root, I selected yes, and the phone rebooted.
Or, at least, tried to. It has been stuck at the beginning of the boot, where there is a white background with the HTC logo and "quietly brilliant" underneath, and it remains stuck there. If I press power and volume down for an abnormally long time, I can get into the bootloader and the recovery from there, but rebooting from there just leaves me at the boot screen again. As I said, there is no backup on the SD for me to restore. When in bootloader, I connected to the PC and fastboot turns to fastboot USB, but adb isn't showing anything when I enter abd devices.
I'm sure I probably did something very silly and am missing something very simple, but given that this is my first time, I have no idea what it is and how to go about fixing it.
Thanks again for all your help!
lyciansarpedon said:
Hello All,
Sorry if this has already been solved before, and thanks in advance for help. (I tried to post this in the ARHD41.0 thread, but as a newbie I cannot post there.)
I have an HTC One (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remained S-On. Made a backup through CWM recovery, transferred that to my PC, then figured I might as well celebrate the holidays by flashing my first ROM.
I downloaded the Android Revolution HD 41.0 ROM (forum.xda-developers.com/showthread.php?t=2183023), transferred to the SD, and then installed the zip through the CWM ROM manager (it seemed at least from what I read in the posts that followed that the ROM worked just fine with CWM). After going through the option selection process (I believe that this was the Aroma installer), I opted to wipe data since I was starting from a different ROM altogether (of course, silly me, this also wiped the backup on the SD). Seemed to install just fine, booted into what appears to be some part of the recovery where it asked if I wanted to root, I selected yes, and the phone rebooted.
Or, at least, tried to. It has been stuck at the beginning of the boot, where there is a white background with the HTC logo and "quietly brilliant" underneath, and it remains stuck there. If I press power and volume down for an abnormally long time, I can get into the bootloader and the recovery from there, but rebooting from there just leaves me at the boot screen again. As I said, there is no backup on the SD for me to restore. When in bootloader, I connected to the PC and fastboot turns to fastboot USB, but adb isn't showing anything when I enter abd devices.
I'm sure I probably did something very silly and am missing something very simple, but given that this is my first time, I have no idea what it is and how to go about fixing it.
Thanks again for all your help!
Click to expand...
Click to collapse
Hey,
Not to worry just run this command from fastboot (Power button +vol down while booting-> fastboot) plug your phone in and run
fastboot erase cache
Click to expand...
Click to collapse
and if its not fixed, just flash again. Make a back up next time! BTW if you need adb just get it from HERE (hint clickn 'here') if you need more help PM me, im always available
You need TRWP 2.6.3.3 or latest version (2.6.3.4) recovery!
Some members successfully flashed by CWM but also some of them face problems, so its better to you to follow FAQ to get good results : )
http://forum.xda-developers.com/showpost.php?p=48035061&postcount=62237
Ba7rani said:
You need TRWP 2.6.3.3 or latest version (2.6.3.4) recovery!
Some members successfully flashed by CWM but also some of them face problems, so its better to you to follow FAQ to get good results : )
http://forum.xda-developers.com/showpost.php?p=48035061&postcount=62237
Click to expand...
Click to collapse
I actually just saw the posts about the CWM issue a little while ago - that's what I get for not reading all the posts! I flashed with TWRP, the ROM installed, and the phone booted.
Now, this is where things get interesting. My backup that I had made with CWM before I initially tried to flash the ROM was still in \data\media\clockworkmod (where it had initially backed up to), and I wanted to check if I was still able to restore from it. TWRP doesn't recognize it as a backup folder/file (not sure if it would be compatible; this is also my first time restoring), and I flashed back to CWM recovery (phone still boots fine after that)...which doesn't recognize it either. I tried moving it to \sdcard\clockworkmod (where the md5 checksum file was originally generated), \sdcard (just in case, since the recovery option says "restore from \sdcard"), as well as \mnt\shell\emulated\clockworkmod (that's where the CWM ROM manager says that it would have backed up to), but the recovery says "No files found" for any of those as well. Any thoughts on where the backup ought to be located?
lyciansarpedon said:
I actually just saw the posts about the CWM issue a little while ago - that's what I get for not reading all the posts! I flashed with TWRP, the ROM installed, and the phone booted.
Now, this is where things get interesting. My backup that I had made with CWM before I initially tried to flash the ROM was still in \data\media\clockworkmod (where it had initially backed up to), and I wanted to check if I was still able to restore from it. TWRP doesn't recognize it as a backup folder/file (not sure if it would be compatible; this is also my first time restoring), and I flashed back to CWM recovery (phone still boots fine after that)...which doesn't recognize it either. I tried moving it to \sdcard\clockworkmod (where the md5 checksum file was originally generated), \sdcard (just in case, since the recovery option says "restore from \sdcard"), as well as \mnt\shell\emulated\clockworkmod (that's where the CWM ROM manager says that it would have backed up to), but the recovery says "No files found" for any of those as well. Any thoughts on where the backup ought to be located?
Click to expand...
Click to collapse
If you have Titanium backup pro you can restore from nandroid file
Menu > restore from Nandroid ..
* Its not recommended to restore system apps or data by Titanium
Found my mistake:
lyciansarpedon said:
\mnt\shell\emulated\clockworkmod\backup (that's where the CWM ROM manager says that it would have backed up to)
Click to expand...
Click to collapse
Missed that I needed to create that directory, oy. Recovery found it just fine, and restored it just as I left it.
Thanks all!
Hello,
Tried rooting my phone with no prior experience. Worked, but eventually I got to where the phone wouldn't boot past splash screen (logo came up, then screen went black while backlight is on and didn't respond to stimuli until battery was removed). Possibly resulted from a build.prop file problem. Did get into boot though, so I fixed that problem by installing a cyanogen rom from a zip file using twrp recovery. I didn't want a custom mod though since I'm used to the look and feel of the 4.0.3 ICS I had, and the cyanogen doesn't seem to have google play so I can't even download anything (original purpose of rooting was to get incompatible apps by spoofing via build.prop file). Currently trying to get back to stock. Unfortunately I didn't make a nandroid backup of the system before the problem occurred, hence I have no backup to flash.
What I tried:
1. Use the official HTC 4.0.3 RUU .exe to upload to the phone. Unfortunately HTC Sync doesn't see this phone, even though I have the correct drivers installed.
2. Attempted to use twrp recovery to install the rom.zip extracted from the RUU directly, the same way I successfully installed the cyanogenmod rom. Failed, claiming it's unable to open zip. The .zip file was checked for integrity and returned by an archiver app.
3. Tried to use these commands from the cmd with phone connected to install the .zip from fastboot:
fastboot erase cache
fastboot oem rebootRuu
fastboot flash zip rom.zip (rom.zip being the functional file of the stock rom)
Failed, saying it's not allowed. Tried it with both locked and unlocked bootloader, no difference.
4. Unzipped the file and tried to flash the system.img file directly, but that failed with a "data length is too large" error.
5. My recovery being twrp 2.1.1, tried looking for altenatives. Can't find any links to download the WCX recovery, but I found several for newer twrp versions, including 2.3.1.0 and 2.6.3.0 which I tried downloading flashing. After flashing the phone got stuck at the cyanogenmod loading logo and wouldn't boot further, and the recovery itself didn't work, just showed the HTC splash, turned black, then booted again normally, getting stuck at the cyanogen logo. Same thing for the 2.6.3.0 version, so I reflashed the original 2.1.1, at which point I can get into recovery but the phone is still stuck at the cyanogenmod during normal boot. At this point I installed the original cyanogenmod .zip from recovery and now at least the phone boots up normally. Still need to get stock back somehow.
Out of ideas and exhausted from this. Any help would be appreciated. Perhaps anyone has a working stock 4.0.3 rom for the Vivid, nandroid backup, etc., or any other ideas. Thanks for reading.
Oh crap...
OK... First... Stock rom can be found in development... Most of the roms there are stock... Read the OP... It'll tell you...
Second... You should use TWRP 2.5.3.0 or something like that I forget...
Third... When you tried the ruu... Did you relock your bootloader...
Side note... Could you get your phone to show up with 'fastboot devices'
Here are all of the procedures I followed to see if you can help me any. Believe me, I've tried searching everywhere.
1. I downloaded the latest version of the Windroid toolkit, found here (http://forum.xda-developers.com/showthread.php?t=2499926). I saw it worked with HTC Vivid on 4.0.3, which was an old shattered phone I had lying around. That tool is pretty old, so I had no idea what the TWRP version it flashed for me, nor the version of the SuperSU it tried installing. (it downloaded it onto the device but can't install it.)
2. I unlocked the bootloader via the tool, then proceeded to flash the TWRP version it had to the device, it currently works fine (loading into recovery). But I opted not to create a backup for the stock ROM, so that's gone forever. And at this point I can't install the SuperSU because of an error in TWRP "Error executing updater binary in zip" (which I googled extensively to no avail, none of the fixes worked). And for some reason, my computer recognizes when the device is connected, but I can't adb push or fastboot flash recovery "file".img to the phone. I am exasperated and stuck.
Takeaway notes: No stock ROM, Unknown TWRP and Supersu versions. I can't install the SuperSu zip because of "Error executing updater binary in zip". I am not sure how to--if i can--push any other ROMs to my device, because it seems like I can't communicate at all with my device through my PC. Although the fastboot does say "FASTBOOT USB"
This is the stage I'm at. I tried flashing a new image of TWRP, the most recent version that works on my phone, via fastboot. So I have a folder with the adb crap and fastboot crap and the image. I type "fastboot flash recovery twrp.img" and it just goes to the next line without doing anything.
I know this information was all over the place, but I'm not really sure what information you guys need to help point me in the right direction.
Thanks.
I have had my Droid turbo since launch and as such followed the path the getting root on it for some time. I used Mofo to get root back on android 4.4.4, used it again to upgrade to 5.1 while keeping root, used sunshine to unlock the bootloader when that came out, and finally installed TWRP recovery on it. I had not done much to it since, but had Intended to install cyanogenmod for a while.
Well I thought I would finally get to it this weekend. I made a nandroid back-up with TWRP, copied it to my computer, backed up some files I didn't want to lose, and went ahead and installed the latest version of cyanogenmod 13 for quark (Moto MAXX and Droid Turbo) and the necessary gapps. It all went very well. I booted into cyanogenmod just fine, and signed in to google.
I was in the process of setting things up, like preferences/wallpapers/wigets etc, while google downloaded my apps. Not long after I started doing this, nova launcher would repeatedly crash, as well as cyanogenmod's built in launcher. I got fed up with it and rebooted. But the phone shut down and started acting odd. It would show what looked like the bootloader, but the open android guy was not there, and I had no options at the top. Sometimes it would just say AP Fastboot Flash Mode (Secure) with no other text.
I got it to go to the bootloader after holding down the power and volume down button, and got it to boot to TWRP. But TWRP said there is no OS installed, and it refused to install anything, wipe anything, and TWRP itself crashed after a bit when I left it there to try and use ADB to push my nandroid back up to it.
Now TWRP will not load from the bootloader, and I cannot flash anything. I wanted to just re-flash the stock firmware. So I downloaded fresh copies of it from the root thread here on XDA, but no matter what, i get the error "(bootloader) Failed to erase partition" It does this for anything. I tried flashing TWRP and the fresh system image. I tried following the steps on the root thread that flash things that you need to prepare the phone for the system image, but all attempts to flash fail with the same message.
I also tried using mofo to flash a clean system image. But it just stops and quits at 7%. I have had this problem before, and got around it by using mofo 0.0.2. But I no longer have that version.
I am at a loss here. I need my phone back ASAP. Any help would be much appreciated.