Database Users

[Q] VISIONARY & Clockworkmod Couple Questions

I'm pretty sure I have these items in the correct order to "Permaroot" my MT4G and begin using Clockworkmod to load ROMs (and or/also want to be able to back up my default ROM)
My current attempts:
Downloaded and installed: VISIONary, from android.modaco.com, sorry I can't post actual links (VISIONary+, most recent version) was no longer avalible in the market so I had to install it from the URL)
Downloaded and installed "Clockwordmod" from the Market.
Put the phone into USB-Debugging mod, and disabled fast boot.
VISIONary+ question: I setup TEMPROOT, and "Root on Boot", assuming I would than be able to boot into "Recovery mode" via "Clockworkmod"
The phone reboots, and I'm assuming that would boot into "Root" **Root on boot** (Yes I know the temp. should fail after a reboot, but I thought, I'll stay away from "Permaroot" for now). However, I don't get to any sort of recovery mode, instead I get a screen with a triangle and exclamation in red, and that's it, it just hangs there, I'm thinking that this is just USB-Debugging, and I'm not achieving recovery mode, so this must be the result of not booting into a root mode.
Going back to VISIONary+, I attempt to "Permaroot", the phone's homescreen goes blank and nothing happens. The phone eventually turns itself off but doesn't reboot, subsequently, I must restart it manually, again, I'm not sure if I've achieved anything?
Advice, suggestions? Would be very appreciated.
Questions that might explain what's wrong?
Even in USB-Debugging mode, should I be connected to a PC via USB-Cable during all of this?
Any thoughts on why the PERMAROOT fails, or the "Root on boot" fails to get me to "Recovery mode"?
Last thing, I get a complaint from "Clockworkmod" when loading, that my SD Card must be mounted (which I'm assuming it isn't due to USB-Debugging mode and/or being connected to the PC) So should I get a good charge and disconnect from the PC while attempting all this? Fixed, disconnected USB-Cable, and mounted SD card in settings, this stopped this error
Also, I'm interested in backing up my default ROM ASAP as a safety-net in-case I screw something up. Is this possible via recovery mode in "Clockworkmod"? Links to advice on doing this?
Thanks everyone! Great board!

you should follow this as it worked for me flawlessly
http://forum.xda-developers.com/showthread.php?p=9534017#post9534017

thanks! that post seems to answer a lot of the specifics I might have been missing! Guess I missed it in search! I'll report my results!

I followed it exactly but I still get the Red Exclamation Point. I have rooted my phone s-off and I have superuser and rom manager. I did the Flash Clockwork Recovery but when I reboot into recovery I get Red Exclamation Point then when I click vol up and power the next says " E:Can't open /cashe/recovery/command " What should I do??

[*]The phone reboots, and I'm assuming that would boot into "Root" **Root on boot** (Yes I know the temp. should fail after a reboot, but I thought, I'll stay away from "Permaroot" for now). However, I don't get to any sort of recovery mode, instead I get a screen with a triangle and exclamation in red, and that's it, it just hangs there, I'm thinking that this is just USB-Debugging, and I'm not achieving recovery mode, so this must be the result of not booting into a root mode.
Click to expand...
Click to collapse
You can NOT flash clockwork without S-OFF and the red triangle is recovery. It is stock recovery if you press volup+power you will see the menu

S is off I rooted my phone using the terminal Emulator and that worked fine

When I press upvol and power I see
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cashe partition
E:Can't open /cashe/recovery/command
This is what my screen shows when I try to go into recovery and again my phone is rooted s-off and I use superuser

Try flashing the recovery again... for some reason people have reported it not sticking... just go back and flash it like 2 or 3 times then reboot

I found out the problem it was so easy but I never would of thought of checking but my wife said maybe my Rom Manager is a bad copy (because I get all my apps from a not so honest site) so I deleted my RM and downloaded the freebie on the market and it worked on the first try.....Now I have Glacier Rom running and I feel like a new man

slhpss said:
Try flashing the recovery again... for some reason people have reported it not sticking... just go back and flash it like 2 or 3 times then reboot
Click to expand...
Click to collapse
+1 on that, When I first flashed it, I was still getting the red triangle, after a quick google search I re flashed it an extra 2 times and it worked flawlessly

Bricked and won't boot following attempted Samsung update (16GB Wifi Retail)

A message popped up from Samsung to install an update (I had been pressing cancel for the past week on this update). It says click OK to reboot and apply update (something along those lines) so I do. Now I am stuck with a tablet that won't boot. If I hold the power button it says "Samsung Galaxy 10.1" after about 12 seconds, but then it goes away and back to darkness. Nothing else. Holding power and volume up does nothing.
Someone know what is going on and have any idea how to resolve?

The best way is to restore any backup you have from cwm recovery. Else grab a stock firmware and flash it with ODIN or if zip than CWM recovery. For luck, try clearing cache and data in recovery, first!Perhaps it may work saving you all fuss of flashing a firmware.

I cannot even boot that far too get into recovery. And I just noticed that although I can't boot, the backlight is on (on a solid black screen).... wtf

You can't hold volume down and power button to enter recovery?

Nope. I plugged into my computer and for some reason with the USB connectd it let me enter recovery. Flashed a backup and rebooted, but now I have no wifi... im confused.

it occured once to me when i tried to overclock, it never worked except when installing a new rom... Try to root the device and then install a new rom

OK, was a helluva night messing with ROM and kernel installs... I have yet to go back to completely stock (that's next up tonight, unfortunately), but I installed Starburst ROM and the Wifi still didn't work so I then installed pershoot's kernel and now when I boot the screen is extremely distorted kind of like this: http://t1.gstatic.com/images?q=tbn:ANd9GcTsKa5IoQxnesGdUjykWDDggoQZ38yZ2VXSgPAQ09NOCnETzl9-
As a side note, when I say the wifi is not working, it still shows all networks and allows me to connect just like normal. However when connected no apps can access the network...
Can someone point me to a thread on how to revert EVERYTHING back to stock so I can start fresh? TIA!!

http://forum.xda-developers.com/showthread.php?t=1171089
Should have all the files you need. From where you are now I would flash the stock OTA 3.1 or TW then flash the stock recovery and do a factory reset from that recovery. That should get rid of the garbled screen.

Thanks buddy. On my way to grab the files now

I heard the update was pulled as it sometimes rewrites the bootloader improperly. You might need to send it in, unfortunately.

Any Advice:little droid and the triangle with the exclamation point

Defy sick please render aid!
Had CM7 but wanted to try CM9, easy enough clear, format, flash poof -
Installed cm9 nightly and gaps, everything worked just fine and fluffy. I have done this a few times before, but...
Installed the Motoizer App- still all good
Then I decided to install the Motoizer optimizer pack it said it was going to reboot, and it did. But now it does not make it past the cm9 boot animation screen, the animation just runs and runs… (not very exciting or useful, but it is cool looking)
Pulled battery after waiting a long time, power+down yields the little droid and the triangle with the exclamation point. If I press the middle of the vol up/down (both) then get the recovery utility. Not a lot of options here, I can install a update.zip, factory reset (clears/formate) or wipe cache partition.
Oh and PS, yes I have googled, searched and waived a dead chicken over my sick Defy…so any suggestions?
Thanks,
Just a guy with a sick Defy…

u don't come into bootmenu? only stock recovery?
ur can do a lot of things.
flash the found stock recovery that flash every update, original or not.
or u flash a modified sbf with integrated CM9 or CM10.
all that found in xda
Jelly powered.Defy

Yeah, I saw many posts, they all lead down the sbf road, I was hoping I could fix it with out sbf-ing it, but that is what I ended (I am in a bit of a time crunch right now) up doing, dang, Oh well, no biggie. The phone lives, not sure what happened with motomeiser though, it seemed like a good idea at the time. Well now I have a copy of RSD Lite, which I did not want to ever have to own... If CM9 pans out I will likely stop there and go static since I have too much other stuff to get done.
Thanks anyway.
Enjoy - Darknetone

if u use this -» http://forum.xda-developers.com/showthread.php?t=1787541 recovery that only rewrite the stock recovery, and if ur re-signed ur CM9 zip u can flash it over and nothing from ur data is gone if I'm right.
Jelly powered.Defy

Can you help me please?
I successfully installed framaroot. Then I installed 2ndInit. Green led: I reboot. No blue led. After a couple of reboots, pressing vol- brings me to the little droid and exclamation mark screen. I can't do nothin but remove the battery.
What can I do? I was going to flash twrp and then slimkat. Android is 2.1.
EDIT: In case I follow the RSD suggestion: does this replace the twrp step? Can I install slimkat afterwards?

vipervault - you shouldn't need to flash an sbf if your phone boot up fine, only if it's in a boot loop (red moto logo)
It just sounds like sndinit didn't install properly.
Verify you properly rooted your device: f-droid.org/repository/browse/?fdfilter=super&fdid=com.abcdjdj.rootverifier
If that checks positive, install an updated su binary: f-droid.org/repository/browse/?fdfilter=super&fdid=com.koushikdutta.superuser
Then try installing sndinit again, make sure you have the latest version, 2.3.

danish1984 said:
vipervault - you shouldn't need to flash an sbf if your phone boot up fine, only if it's in a boot loop (red moto logo)
It just sounds like sndinit didn't install properly.
Verify you properly rooted your device: f-droid.org/repository/browse/?fdfilter=super&fdid=com.abcdjdj.rootverifier
If that checks positive, install an updated su binary: f-droid.org/repository/browse/?fdfilter=super&fdid=com.koushikdutta.superuser
Then try installing sndinit again, make sure you have the latest version, 2.3.
Click to expand...
Click to collapse
Thanks @danish1984. 2.3 is the latest version of what? I wrote I have android 2.1; your f-droid link points to com.koushikdutta.superuser 1.0.3.0.

For everybody who doesn't see the blue led: 2ndInit installation did not work. Install it manually as per this thread.

Some notes I've just made a few moments ago.
I was on Quarx CM9 ICS 4.0.4, and so decided to re-live how I installed 2ndInit as I had a few problems.
(and wanted to make log of what I did a day or two ago, only bought 2nd hand Defy a few weeks back, £8.00 UK).
Below I flash original full SBF file, to get back to Eclair v2.1-update1. (Had only previously flashed Fixed SBF's, ie minus CG 31 and 39)
I got my Motorola Defy MB525 (Green Lens), retail UK, Eclair v2.1-update1 stock,
JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_USAJORDANRTGB_P026_A007_HWp3_Service1FF.sbf.gz
from:- https://firmware.center/firmware/Motorola/Defy (MB525)/Stock/
MD5: b42848509d1fb19d746185b79b8e1816 (Did Google search on the MD5 and check matches with droid-developers.org MD5).
(Google HashCheck or HashMyFiles).
With fully Charged defy,
Power down defy, and with Volume+ held, press power key (shows "BootLoader 9.10, Battery OK etc").
Run RSD Lite, v5.6.
Select The .gz file in RSD Lite Filename box, will ask "It may take a while to uncompress, Continue ?",
Select "Uncompress Only" (it will be done, you could have used Winzip or Winrar to extract yourself instead, and chose the extracted sbf).
Connect Defy to USB, it should show "Connected" status in RSD Lite.
Click on the "Connected" line of text to reveal a little more info.
Click "Start", defy will show "SW Update in Progress".
Eventually (after several minutes) RSD will show "Phone[0000]: Phone is being rebooted".
Unfortunately, after some time it looked to RSD as if phone was not rebooting, and suggested Reboot manually.
This I tried multiple times but was in boot loop with MotoBlur animation and eventually black screen and repeating.
I pulled battery, reinsterted battery and attempted manual boot again, no joy, boot looping.
I pulled battery, holding volume down, and power on, and triangle with Exclamation mark (!).
I tapped repeatedly on bottom RHS corner of display and got the "Android System Recovery (2e)"
(some people say to hold down both volume up and down simultaneously, but my works best with bottom RHS corner taps).
Ignore the "E:Can't Open /cache/recovery/command" in yellow on bottom of display.
Select "Wipe Data/Factory Reset", tap OK on bottom left hand side of display (power button does nothing for me within
the system recovery).
After Factory wipe, select "Wipe Cache partition", and tap OK again.
Select "Reboot system now", and OK again.
We were back in business with a properley booting Eclair 2.1-update1 (was a bit tense for a while)
(Perhaps I should have done factory reset, cache wipe before RSD lite flashing).
In new flashed Eclair,
Settings/Sound & Display, select "Screen Timeout"=10 minutes.
Settings/Applications, tick "Unknown Sources".
Settings/Applications/Development, tick "USB Debugging".
File Manager app, I selected Framearoot v1.5.2 (others were tried but caused problems).
Choose "Install SuperUser" (NOT "Install SuperSu").
Hit "Gimli" exploit text, should show "Success", Reboot just for the hell of it.
File Manager, Install, SndInitDefy v1.4, and click "Install 2ndInit Recovery" button. (tried others, only this version worked for me)
SuperUser will pop up twice asking to Allow 2ndInit root premissions, grant the request each time.
Light will turn Green. (And read instructions).
Settings/Applications/Development, UN-TICK "USB Debugging", ie turn it OFF.
Reboot, it will auto jump into Custom recovery when Blue light comes on (dont press anything to get there).
With "Boot" selected, press Power key.
With "Set Default" selected, press Power key.
Move cursor up to "2nd boot" selected,, press Power key.
"Go Back", selected,, press Power key.
"Reboot system", selected,, press Power key.
Let it Reboot without pressing Volume-down when blue light comes on, and then reboot again a second time, for good measure
One last time, roboot, but this time when Blue light comes on press Volumn-down botton, and there you are custom recovery.
You will see "Android Bootmenu (v0.6.1)".
I originally had problems trying to "Install zip from SDCard", as it could not find the sdcard, I eventually figured out
that maybe because I had deleted sdcard stuff from previous android installation and that it did not like it.
So, I copied my stuff from sdcard to hard drive, and within settings/storage, formatted sdcard, after that I had no
problems at all. (just a lot of files to copy back to newly formatted sdcard).
Everything hunky dory.
EDIT:
ALL software mentioned above was present on XDA at time of writing, lots of defy links are broken here.

ticking/clock sound when installing cwm

I tried installing CWM 6.0.4.4. It successfully booted into recovery at first, and I selected "Reboot now." It booted and now it shows a screen which asks for a "PIN/password to decrypt" and on top of that it says, "Device is getting update with new Configuration." The phone is also producing a ticking/clicking sound every ~5 secs or so. What does this mean? It's been this way for 10 minutes now!

I've got this too after I got stuck in a recovery bootloop due to accepting an official OTA with TWRP.
Ran the fix here: http://forum.xda-developers.com/showthread.php?t=2451696
And I got the same message as you mention, with the ticking clock sound.
Did you find a fix mate?

I managed to 'fix' it by simply switching it off (long press power button) and on again. Thank god! I hope it works for you.

Help: Recent Update Broke My Phone

Dear XDA,
It's been a while, I used to have all sorts of fun with rooting and experimenting with new ROMs. Shamefully, I haven't done it in years.
I come now with a problem. My phone seems to have failed the most recent update pushed and started freezing, cycling, all sorts of nasties. Now, however, it automatically boots into Recovery and cannot boot out of it. If I do select a reboot it only accomplishes giving me the one line of "verifying dmverity hash tree" and then after about a minute the phone just shuts off. (update, I watched more closely this time and it verified the above and when it tried to reboot it shut off)
At this rate, there is little I can do. A look at the current software version shows that I am one update behind (I think they pushed a new one today/yesterday). Would applying that update from the SD work? I am on verizon with update
MMB29M.N910VVRS2CQC1
and the newest is
"" D1
Would downloading MMB29M.N910VVRS2CQD1 to my SD card allow me to apply the update? They don't appear to put any of the updates on an online repo anywhere that I can see. I would appreciate your advisement, I need to get back into the phone to move an app over with its current data at the very least.
Regards
Edit1: When I take the battery out for a bit and try to boot into safe mode by holding the volume down button, it still boots into recovery but also then goes to the android "Installing system update" for about a minute before going to the "No Command" screen and eventually the recovery mode.

crazycruiser said:
Dear XDA,
It's been a while, I used to have all sorts of fun with rooting and experimenting with new ROMs. Shamefully, I haven't done it in years.
I come now with a problem. My phone seems to have failed the most recent update pushed and started freezing, cycling, all sorts of nasties. Now, however, it automatically boots into Recovery and cannot boot out of it. If I do select a reboot it only accomplishes giving me the one line of "verifying dmverity hash tree" and then after about a minute the phone just shuts off. (update, I watched more closely this time and it verified the above and when it tried to reboot it shut off)
At this rate, there is little I can do. A look at the current software version shows that I am one update behind (I think they pushed a new one today/yesterday). Would applying that update from the SD work? I am on verizon with update
MMB29M.N910VVRS2CQC1
and the newest is
"" D1
Would downloading MMB29M.N910VVRS2CQD1 to my SD card allow me to apply the update? They don't appear to put any of the updates on an online repo anywhere that I can see. I would appreciate your advisement, I need to get back into the phone to move an app over with its current data at the very least.
Regards
Edit1: When I take the battery out for a bit and try to boot into safe mode by holding the volume down button, it still boots into recovery but also then goes to the android "Installing system update" for about a minute before going to the "No Command" screen and eventually the recovery mode.
Click to expand...
Click to collapse
Download suitable firmware using sammobile
Extract (unzip) the firmware file
Download odin
Open Odin
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button
http://dl.sammobile.com/Odin3-v3.11.1.zip
(Odin link posted in sammoble site)