Database Users

Problems with Fastboot

I can't get fastboot to work. I never have really tried it before, so maybe I'm just doing it wrong, but when I turn the phone on using the camera + power method, I get the Androids with skateboards, press back to enter fastboot mode. When I connect the usb cable, it shows "fastboot usb" for one second on the phone, then goes back to "fastboot". I try to connect using the comand prompt all I get is "waiting for device"
Here is what I'm running
Dream PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.26I
ROM: Dudes 1.2
Aero Theme
I do have the USB drivers for both bootloader and ADB with the fastboot.exe file with the SDK/tools folder.
I am running Windows XP professional.
I thought it might be the new SPL from haykuro, so I flashed back to the old Hard SPL with no luck. I have uninstalled the fastbood & ADB drivers, then re-installed them and it still doesn't work.
I searched the forum also & found some people with similar issues, but none of their fixes worked for me.
If somebody could give me a check list of things to check, I would appreciate it.
Thanks in advance.

did you try re-installing the drivers after you plugged in the USB it fastboot? i had a problem similar to this a long time ago, and the drivers were only loading in normal mode when android was booted up for adb and all that good sh*t. i booted into fastboot, plugged in the usb cable, and installed the drivers while at the fastboot screen. hope this helps any

I think I have. I kind of remember uninstalling the drivers, restarting my computer, plugging it in (while in fastboot) and installing the drivers when the "found new hardware" screen popped up. Guess I will try it again and report back.
Thanks.

I fixed it...
Okay, I figured out what I was doing wrong.
I checked the usb driver, found that while installed, it was not enabled. I went ahead and re-installed it from the android sdk just to be sure. Afterwards I found that when I was in fastboot mode, it would say "fastboot usb" instead of just "fastboot".
I still couldn't get use fastboot on my computer and see the device attached.
Turns out I am also an idiot. What I was trying to do is flash a new boot screen. I was reading this post:
aron4588 said:
This is updated with the lastest tool. (Windows)
I included a zip with all files you may need at the bottom of the post.
1. Turn off your phone
2. Turn on the phone into bootloader (camera+power).
Make sure it say fastboot in the middle if not hit back and it should appear-
3. Make sure your device is found in device manger
If you don't see adb device up top in device manger find the yellow mark devices
Right Click, update driver, and point to the location of the USB Driver
(http://dl.google.com/android/android_usb_windows.zip)
4. Open and extract the below zip to your desktop
You should now have a custom and fastboot folder on your desktop
5. Open up a dos window (start>run>CMD)
6. Type cd desktop then cd fastboot
7. If you would not like to flash the sample images skip to step 9
8. copy and paste the command line by line
fastboot flash splash1 mysplash.rgb565
fastboot flash splash2 mysplash.rgb565
fastboot reboot
Part 2 Making your own images
9. Open up the "create" folder
10. Run CreateG1Splash.exe
11. Open up your image in the program and click convert
12. Goto the folder of your images and their you will find mysplash.rgb565
13. Place the mysplash.rgb565 into the fastboot folder
14. copy and paste the command line by line
fastboot flash splash1 mysplash.rgb565
fastboot flash splash2 mysplash.rgb565
fastboot reboot
Files updated 1/4/08
Credit to JF for all app to make this possible
Original G1 Bootloader/Splash Image
Click to expand...
Click to collapse
trying to do it. I was following the post trying to run fastboot from the desktop directory (which the folder was there). However when I tried running it from the SDK/tools folder on the root of my C: drive everything worked great. I have a new boot screen and everything was easy after I figured out to do it all from the /tools folder.
Even though I didn't get a lot of support with this problem I posted, I would still like to thank everybody here at XDA. I try to keep my questions down to a minimum and search the forum, among other places, before I ask the help of everybody here.
Thanks again.

NICE!!! I tried a whole bunch of solutions as well. Finally, I stumbled on yours, and it worked! Hell yeah! I think maybe adding fastboot folder to the path of system variables may have done the trick, too.
Thanks!!!

ccunningham83 said:
I can't get fastboot to work. I never have really tried it before, so maybe I'm just doing it wrong, but when I turn the phone on using the camera + power method, I get the Androids with skateboards, press back to enter fastboot mode. When I connect the usb cable, it shows "fastboot usb" for one second on the phone, then goes back to "fastboot". I try to connect using the comand prompt all I get is "waiting for device"
Here is what I'm running
Dream PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.26I
ROM: Dudes 1.2
Aero Theme
I do have the USB drivers for both bootloader and ADB with the fastboot.exe file with the SDK/tools folder.
I am running Windows XP professional.
I thought it might be the new SPL from haykuro, so I flashed back to the old Hard SPL with no luck. I have uninstalled the fastbood & ADB drivers, then re-installed them and it still doesn't work.
I searched the forum also & found some people with similar issues, but none of their fixes worked for me.
If somebody could give me a check list of things to check, I would appreciate it.
Thanks in advance.
Click to expand...
Click to collapse
best advice i got was load up your phone is fastboot connected to pc...run the same commands in cmd but go through SDK/Tools and run fastboot from there once your in tools...skip putting it to your desktop...that didn't work for me

Hey guys, I have a problem, the driver is installed, but I can't see the device when I go to the cmd. I need help please!
Also, since my recovery is dead, and my cyanogen rom is dead, I have no way to revive my phone... can anybody help me please?

99.9% of the problems with getting fastboot to work are actually problems with windoze and incorrect_drivers/driver_conflicts/windoze_is_retarded.
Best thing to do is use Linux. No special drivers needed.
And this is not to start a linux is better than windoze fight (even if it *is* better )... it is simply a matter of this; android *is* linux, it was developed with linux, that's what all the platform developers use, and simply put, it is absolutely and fully compatible, so when all else fails, that is what you should use as well.
Option a) grab latest fedora livecd and boot off that,
Option b) grab latest fedora installdvd and install it to something and boot it up,
Then:
copy the fastboot executable into any directory (download from developer.htc.com),
connect USB,
put phone in fastboot mode,
./fastboot flash {partition} {image}
And it'll "just work".
Note: http://www.fedoraproject.org/en/get-fedora

omg. countless hours spent on trying to do this. and all i had to do was to use the fastboot in the sdk? thanks youuuuuuuuuuuuuuuuuuuu!
ccunningham83 said:
Okay, I figured out what I was doing wrong.
I checked the usb driver, found that while installed, it was not enabled. I went ahead and re-installed it from the android sdk just to be sure. Afterwards I found that when I was in fastboot mode, it would say "fastboot usb" instead of just "fastboot".
I still couldn't get use fastboot on my computer and see the device attached.
Turns out I am also an idiot. What I was trying to do is flash a new boot screen. I was reading this post:
trying to do it. I was following the post trying to run fastboot from the desktop directory (which the folder was there). However when I tried running it from the SDK/tools folder on the root of my C: drive everything worked great. I have a new boot screen and everything was easy after I figured out to do it all from the /tools folder.
Even though I didn't get a lot of support with this problem I posted, I would still like to thank everybody here at XDA. I try to keep my questions down to a minimum and search the forum, among other places, before I ask the help of everybody here.
Thanks again.
Click to expand...
Click to collapse

Wrong SPL zip file. Now what? [SOLVED]

[SOLVED. READ BELOW FOR DETAILS]
HI all.
I've managed to brick my Hero (T-Mobile G2) by flashing the wrong SPL file.
To make things more difficult I've lost the USB cable.
I can still:
Power+Menu (three vibrations + blinking green)
Power+Back (Fastboot)
Power+Search (Storageclean)
Power+VolumeDown (HBOOT, SD checking ...)
Is there a way to reflash the right SPL with one of these menus?
I've not found any similar case here and in MoDaCo.
Thanks in advance.
[SOLUTION]
This case is particular as there is no system available to use the "adb shell" commands. Nonetheless it's recoverable.
At least in one case
Almost everything comes from MoDaCo.
Despite I would say I'm not a real newbie, this time was a little bit harder than with other embedded devices for some reasons I'll explain later.
What do you need?
1. A miniUSB cable. Now I know that any miniUSB can work.
2. A Windows XP PC. A Linux or Mac OS X should also work. Read below.
3. The right USB software driver (I used this one) otherwise it won't work.
4. A modified recovery image (I used this one) that has flashing capabilities from the SD.
5. A working SPL (Second Program Loader) image (I used this one, thanks to the enlightner.
6. A system ROM image (again, I used this one).
What was the problem?
I used to play also with a Magic and still had an SPL zip of its on my SD.
I already had rooted and modded my Hero with MoDaCo's mod.
By mistake I flashed that SPL zipped image into my Hero and since then nothing was working any more.
The boot process was simply stopping at the "G2 Touch T-Mobile" screen up to the complete battery drain.
The directions found here were ineffective due to the fact that there was no running system to execute the "adb shell" commands.
I am using 99.99% of the time a Linux laptop but decided to get a Windows XP PC in order to simplify the troubleshooting while asking people for help and hints.
Maybe in the future I'll dare to reproduce the problem and solution with Linux. Maybe,
But let's see a stepwise procedure.
How I solved it (impossible to me without MoDaCo's and englightner's help, kudos to them)!
0. Unpack the USB driver and the recovery image ZIP files somewhere into your PC. Put the SPL and the system ROM image zip files into the SD card. Use the root directory of the FAT partition in case you have already partitioned it.
1. Switch off the Hero (by pulling the battery out).
2. Turn it on again without the USB cable in by pressing the back and the power keys. I've noticed some different behaviour if you keep the cable plugged in.
3. A white screen (the Initial Program Loader aka IPL aka Fastboot) will pop up.
4. Plug the USB cable in both the Hero and the PC. The screen will now show in red "FASTBOOT USB".
5. Windows should warn you about some unknown hardware having been plugged (Android 1.0). Ask for a manual installation by browsing to the directory where you unpacked the USD driver. Install it. No reboot is required (unbelievable!).
6. Open a command line session on your PC (Start-->Execute-->CMD on Windows), change the current directory (cd) to where modified recovery image has been unpacked and where both the fastboot.exe and cm-hero-recovery.img files are located.
7. From the command line run this command (without the quotes): "fastboot boot cm-hero-recovery.img". You'll see a green progression bar rising on the right side of the Hero screen and after 1 second you'll see the modified recovery image running.
8. At this point I tried to recover a previously saved nandroid backup. But for some reason this time the recovery was complaining about a chown/chmod not being able to change the permissions on a system file! So it's useless to try it.
9. Instead I asked to flash the SPL zip file. It worked fine and I asked for a reboot.
10. the final step was to pop the recovery tool again (Home+power, keep the home pressed until you'll see the friendly black and green screen) and to slash the system ROM zip file.
I also reset all user data before doing it. I'm not sure whether this reset is required.
11. At the reboot the flashed system ROM was happily waiting for me to customise the settings.
12. As a last check, I rebooted once again the Hero to see whether the solution was permanent. And it was.
Few suggestions for seniors.
Please, please be patient with newbies. This could be the first time they hit the wall and panic and frustration can play an important and irritating role.
Please, please be as precise as possible. What a senior thinks is an implicit piece of information, can lead to hours of frustration for the newbie. For example, the SUB driver installation is not mentioned very often in any thread. It looks trivial. It's not.
Please, please be positive to newbies. By encouraging them they'll become less newbies than they are now.
And a few suggestions for juniors (like me).
Please, please don't panic! If there's a solution, you don't need to panic. If there's none, you don't need to panic as well.
Please, please be precise in describing the problem (I've not been myself). Small unseen details can matter a lot.
Please, please don't blame people for late answers. Very probably they are busy with their own job, life or hobbies.
Please, please remember that if you are in trouble is very probably due to your own mistakes. Not someone else's. You are playing with low level stuff, not just application settings.
If you decide to follow someone's directions, please do it carefully. If you take some decisions on your own, please document them in the thread.

If you can get to fastboot with power and back, then all is not lost. And most importantly it's not a 'brick'. A 'brick' is a device that won't turn on.
You can flash the recovery via fastboot (using this guide) then a new ROM (I suggest my custom ROM) but, er, you're obviously gonna need a USB cable!
P

I was already using your marvelous mod, though.
I only took the SPL file from the wrong directory (I have been playing also with Magic, aka G1).
The cable is a huge problem, now.
At the moment I'm using a mini-USB cable which is good for charging the battery, but has no effect on the communication side.
Can I put some file in the SD card from my PC in order to have it booted into?
I still have a couple of nandroid backups in the SD but have no idea whether this makes any difference.
Anyway, thanks not just for the hints. Your 1.5 (1.5.1 when I'll fix my problem) rocks!

A real miniUSB cable should work fine. Yours must be only wired for charging. Go and buy one.
There's no other way to do it unless power+home gets you into recovery (which it sounds like it should?)
P

The mini-USB comes from my USB 2.5" HD.
It works with cameras and other mini-USB devices for full dvice access.
But it does not work with the Hero.
The original cable looked different from this one because of the asymmetric shape (and possibly an extra pin or two).
The Hero cable looks like it's proprietary design and buying one seems quite difficult. Would any HTC USB cable work?
Now I'm not in the Netherlands anymore and here the HTC stuff looks quite uncommon to have a cable lent.

I never use my HTC cable, I use a standard mini USB cable.
P

OK.
I've bought a brand new mini-USB cable. It works with my Nokia phone, my digital camera dnd also my USB disk.
1. I've donwloaded the file from the guide MoDaCo referred previously.
2. I've unpacked the ZIP file, opened the CMD session, CDed to the directory containing the adb.exe file
3. I've booted the phone to the FASTBOOT (VOLUMEDOWN+POWER)
4. I've connected the phone to the cable.
5. The HERO screen says now "FASTBOOT USB"
6. I've run the command "adb shell reboot bootloader"
7. I get "error: device not found".
What's next?
P.S.
Steps 3 and 4 are not mentioned in the guide, though.

You can't use adb shell from the fastboot screen, you need to boot a recovery image using the "fastboot boot <filename>" command.
Just of curiousity. What is the HBOOT version displayed on your fastboot screen?
Could you type all the text it displays?
I might be able to help you out.

Try following the guide linked above.
You can't do ADB until you've done the 'fastboot boot cm-hero-recovery.img'.
Seriously... how hard can it be to read thru a handful of steps!
P

You are right! It's hard unless you already know how to.
I quote:
- download this file and extract it to your PC or mac
- open a command prompt to the directory containing the extracted files
- type the following commands (prefix each command with ./ if you're on a mac)
So far it's trivial ...
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
That could also be trivial if:
1. I knew about the driver installation (quite later in the thread)
2. I knew in which initial status the phone is to be
Of course, a bit at a time I find everything.
Maybe re-editing the original post to include all the bits in one single place would both boost the success rate of n00bs like me (really) and lower the amount of stupid questions (really) like mine.
Anyway, I need to thank you very much!!!

Hmm, bad news, ust spoken to an extremely knowledgeable friend of mine, and he says your device is knackered.
P

I'm impressed the SPL actually booted on a Hero.
It's is a "real" Hero you have right? aka T-Mobile G2 Touch?
Fastboot can be used when you are in HBOOT, with FASTBOOT USB being displayed.

So, if this doesn't work, you're screwed.
- download this and extract the rom.zip
- copy the .zip to your SD card and name it HEROIMG.zip
- turn on your device with volume down+ power
If it doesn't start flashing, buy a new Hero.
P

packetlss said:
You can't use adb shell from the fastboot screen, you need to boot a recovery image using the "fastboot boot <filename>" command.
Click to expand...
Click to collapse
Good to know. I have no idea about this specific device!
And the help is quite fragmented among a large number of threads.
packetlss said:
Just of curiousity. What is the HBOOT version displayed on your fastboot screen?
Could you type all the text it displays?
Click to expand...
Click to collapse
HERO CVT
HBOOT-1.33.2005 (HERO10000)
MICROP-010e
RADIO-6.35.05.15
Apr 20 2009,15:30:43
packetlss said:
I might be able to help you out.
Click to expand...
Click to collapse
I hope so.

Try doing what modaco suggested and see where that ends up.

modaco said:
So, if this doesn't work, you're screwed.
- download this and extract the rom.zip
- copy the .zip to your SD card and name it HEROIMG.zip
- turn on your device with volume down+ power
If it doesn't start flashing, buy a new Hero.
P
Click to expand...
Click to collapse
I hope to fix mine.
Anyway, is there any comprehensive guide about the booting (not rooting) process with the software stack and the "cheat codes"?
I don't think I'm really a n00b, but the fragmentation of information is quite large for these marveloous Android phones.

The HEROIMG.zip has been flashed, I presume, as a vertical blue bar appeared on top right screen.
After fre minuted the process ended ... with no news.
At the reboot everything is again as before.
Home+Power won't make the CyanogenMode+JF menu pop up.
The simple boot itself won't make my Hero botting in any system.
Only a big "G2 Touch T-Mobile" on the black background.
Now what?

That HEROIMG.zip contained a hboot. When you boot to bootloader is still the same?
You say 'fastboot boot recovery.img' (as per my instructions) didn't work?
P

'fastboot boot recovery.img' works.
It's the subsequent step that doesn't. I cannot mount /sdcard (error: device not found)!
And even recovering a previous nandroid backup won't help.
What I understand there's something in between the fastboot and the actual image (the SPL?) that is missing doe to my original error.

Does the bootloader still show the old version?
P

Need Help: Updating CM, Stuck

[Edit] I got the CM 1.4 recovery to flash and updated CM from sd card... Then hit reboot. It's been sitting on G1 screen for like 10 minutes. Do I need to wait longer or is this a bad sign? What should I do?
Please help!
THank you!
------
Hi guys...
My phone = stats in my sig. (Sorry, its the only way I can keep up with all the details.)
Okay... rephrasing this.
I'm trying to upgrade from the stats below to the current Cyanogenmod. http://wiki.cyanogenmod.com/index.php/Main_Page tells me to do one of three things, none of which tell me how to get rid of Dark Hero theme and I'm not sure about how to get it up to the latest radio/spl etc.
I flashed the recovery (terminal didn't make any feedback messages so I'm not sure if it worked?) and when I did a power-on while holding X, it didn't go into recovery so I"m kinda lost.
I just want to get the latest Cyanogen mod up and running. (Latest stable, not 5.x)
If anyone can give me a hand I'd really really appreciate it.

arsieiuni said:
Hi guys...
My phone = stats in my sig. (Sorry, its the only way I can keep up with all the details.)
Okay... rephrasing this.
I'm trying to upgrade from the stats below to the current Cyanogenmod. http://wiki.cyanogenmod.com/index.php/Main_Page tells me to do one of three things, none of which tell me how to get rid of Dark Hero theme and I'm not sure about how to get it up to the latest radio/spl etc.
I flashed the recovery (terminal didn't make any feedback messages so I'm not sure if it worked?) and when I did a power-on while holding X, it didn't go into recovery so I"m kinda lost.
I just want to get the latest Cyanogen mod up and running. (Latest stable, not 5.x)
If anyone can give me a hand I'd really really appreciate it.
Click to expand...
Click to collapse
A couple of things:
5.0.7 IS the latest stable build. If you want 4.2.15.1, you're going to have to search the forum for it because Cyanogen is no longer working on Donut (1.6) builds.
However, if you want the latest CM, its very simple.
First, download either the latest clockwork recovery or amon_ra recovery. follow the instructions to flash recovery. to check if it installed correctly, you dont power on while holding X, you power on while holding the home button. (alternately, grab the "quick boot" app from the market and you can one-touch boot to recovery or bootloader from your home screen)
Next, download the latest radio and appropriate SPL. In order to install these, follow the instructions here:
http://wiki.cyanogenmod.com/index.php/DangerSPL_and_CM_5_for_Dream#Prerequisites
Note: MAKE SURE YOU FLASH THE RADIO FIRST OR YOU WILL BRICK YOUR PHONE.
Once you follow those steps, you'll have CM 5.0.7 installed.
EDIT: I noticed you grabbed CM recovery 1.4. That recovery is old and outdated, also no longer supported. You need to grab one of the recovery files I mentioned.

Crap...
So trying to follow the instructions at Cyan WIki...
And like I said above, it's now sitting on G1 screen indefinitely...
Have I lost my phone?
Is there any way to fix this?

power off the phone by pulling the battery. boot into recovery by holding home+power. plug your phone into your computer. once there, use ADB from your computer to flash the new recovery, then power the phone off again. power it back on into recovery again (home+power) and then follow the steps in the wiki page i linked you to.

OMG that's wonderful I thought I had ruined it!
But I have no idea how to use ADB. I have never used it before. I found the site but I'm totally lost at that point o_o
If I plug phone into my computer it doesn't recognize to let me access the folder so I can't add files there since I can't Mount it.
How do I add the recovery from ADB?

ok, first things first, make sure you have your drivers installed and adb working (for this, youre going to need the adnroid SDK installed, which can be found here: http://developer.android.com/sdk/download.html?v=android-sdk_r06-windows.zip). to check and see if adb works, open a command prompt on your computer(start>run>cmd), navigate to the sdk tools directory (for example, mine is C:\android\tools\ yours might be different depending on where you install the sdk) and then type "adb devices" without the quotes. if it shows your device connected, proceed to the next step:
Copy the recovery image you're going to install to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your G1 via usb to your computer and type the following commands into the command prompt
adb shell
#mount -a (this can give back an error if you don't have an ext partition, don't worry about it and just proceed)
#flash_image recovery /sdcard/custom-recovery-name-here.img
once that's done, you will have your new recovery going, then proceed with the steps to upgrade the radio and SPL from the wiki page i linked earlier. after you have the radio and SPL done, flash CM and you're all set!

Okay... I tried to use the SDK to install the drivers (it says in INstalled packages: Drivers r3) but It's not showing up under ADB devices when I check it in CMD.
It just says List of Devices: then there's nothing.
I think maybe because my phone won't go past recovery right now, I can't get the drivers working?
Is there a place I can manually download the drivers so I can manually install them?
I went in and followed the instructions here; http://developer.android.com/sdk/win-usb.html to install or upgrade and either way my computer is telling me I have the best driver installed for the HTC android phone. I don't SEE a place exactly like they say that says ADB Interface device.. that doesn't even appear on my list.
I really, really wish I could find my sd card adapter. That would make this considerably easier.

Please could someone help with the last question above?
I'm trapped at this point and can't figure out how to go onward.

For starters, don't flash your radio or SPL. FASTBOOT them.
Setting up adb is very useful. Download the sdk and extract it to where ever you want it and add the "tools" folder to your windows Path. There and HUNDREDS of tutorials on how to do this. Google it. Fastboot is just as easy as using adb, and safer than flashing.

[Q] Really could do with some help from those with experience... Please.

Hi Guys,
I am a noob to xda so please bear with me...
Hoping someone can help me out here.. I will try and explain in as much detail as possible and provide you with as much Info from my phone as I can.
Firstly my phones details
Motorola Atrix 4g (UK version) Second phone as busted the last one. Bought outright as a retail sale.
Orange UK
System Version: 45.31.0.MB860.Retail.en.GB
Android Version: 2.3.4 (After UK released update)
Baseband Version: N_01.100.00R
Webtop Version: WT-1.2.0.133_38
Kernel Version: 2.66.32.9 [email protected]#2
Ok so, decided to root my phone. To do so I used petesMotorolaRootTools_V1.07 found on the website psouza4.com/bionic/
This worked fine and an app installed from the App Market confirmed that the phone was Rooted and had Superuser permissions.
Next I downloaded ClockWorkMod Rom Manager from the Market Inc Premium, SetCPU, Rom Toolbox & Titanium Backup Free. I had a quick look at these apps once downloaded but didnt really do a lot,
However, when Rom Manager opened it promted me to Flash ClockWorkMod Recovery, Which I did and then selected Back up current Rom. I also did this, (bear with me it gets a little vague here as to what I remember seeing)
Now I'm sure it said something like Nandroid Backup, which I selected. It proceeded to say something along the lines of, Backing up or phone will now reboot??
Anyhow, what ever it said, it started to reboot. The Motorola Red Circle logo came up but then at the top it said reboot failed and something ilse that didnt make sense then froze. I pulled the battery and rebooted. Seemed to work fine. Maybe a touch laggy but nothing to bad.
Next did my research into what ROM I'm likely to want to try. Found a few but seemed from what I have read on various forums that they dont work well for uk phones. Then decided perhaps then flashing should be left alone and went back to PetesMotorolaTools and unrooted. before I unrooted however i removed all apps that required root access first. Possibly a mistake?
I noticed that a few preinstalled apps werent working, nothing important or anything I use but there icons were like Blue settings icons all the same.
Did a factory reset through the handset also, in an attempt to return to factory settings.. not much changed really. Also tried to update software though the Motorola website but it said I was all up to date.
I thought maybe that something went wrong so I rooted again. This time the unroot failed. I then dowloaded all the rooted apps that I had before and then unrooted. This worked. Not sure if coincedence or not but it worked and when unrooting it said unfreezing apps about 6 times, before the complete message. Then uninstalled the root apps again.
Most, not all but most of those preinstalled apps were then working ok.
I read a little bit more bout Roms and decided to have another bash. Found and downloaded a few to comp. Then I place an SD card into phone and Flashed it. then tranferred a copy to its root.
Rooted the phone in the same way as before. Downloaded all the apps again opened CWM RM, Flashed CWM Recovery again as was unsure that the time I did it before would work. Then selected back up Current ROM. Without any message this time the phone started to reboot.
It came up with the recovery screen (Android man and !) From what I have read the next step is to tap the bottom right of the screen to bring up the menu.
This did not work nor did anything else happen. After waiting about 25mins with nothing more happening I pulled the batt again.
Decided I'd boot into recovery mode manually and see if the bottom right of screen would work that way. turned off then held On and down Vol. Fastboot showed at top, Scrolled and selected Android recovery. Same Android Man and ! came up, tried tapping the bottom right of screen again.... It didnt work.
Read more on the forums where someone said that pushing up and down on the Vol buttons works. Tried this and hey presto.. a new menu appears. Shown as follows.
Android system recovery <3e>
Android system recovery utility
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
No back up options so rebooted....
Anyway thought I'd try a few times to use CWM RM to flash a rom to device. Each time it took me throught this same process.
Eventually I though what the hec just try and flash it...
So I selected the apply update from sdcard option.
Then selected the ROM I saved to SD Card.
Then the following text appears on screen in yellow.
--Install /sdcard...
finding update package...
Openeing update package...
Verifying update package...
E:signature verification failed
Installation abborted
I tried this a few times to no avail. even tried downloading the roms from CWM RM with no change.
Read some more on the forums and somewhere read to rename the ROM update.zip
Did this and tried again.... No Joy!!!
Selected Fix permissions in an attempt to clean up and thats as far as I have got...
I'm at the end of my tether and dont know what to do...
Please, please, please someone help me get to the bottom of my dilemma..
Thanks for reading and any help in advance.
Just a little more info to help diagnose
CWM RM Details
Rom Manager Premium v4.8.1.3
Current Recovery: ClockworkMod 5.0.2.0
Latest Recover;ClockworkMod 5.0.2.0
Thanks again peoples for taking the time to at least read this..

No where in there did I see "I unlocked my bootloader"
That's fine that you're rooted, but to use CWM Recovery, install ROMs, make Nandroid Backups, etc. you need to unlock your bootloader first! See the international part of the Pudding thread (since your in UK) in the dev section.
Sent from my CM7 Atrix 4G

Ah Hah! You are correct at no point did I unlock my Booty, Thank you I shall give that a go and report back...

Ok so, I have trawled the forum and many others this avo on my research quest to unlock the bootloader as advised above but have been unsucessful so far.
I used the Pudding thread as you said.
when downloading the files advised I noticed that some were downloading as unrecognised files. I still proceeded to follow instructions as written.
Some of them like the RSD Lite I managed to unzip and extract with a programme I have however the next one needed said it was Undefined File type.
Anyway I deleted those files and tried following the other method listed underneath the driver via the link at "Guide for beginners provided by..."
This was unsucessfull as the "fastboot oem unlock" command was not recognised.
Pulled the batt and rebooted into normal mode and I'm back at SQ1
Bit stuck if anyone has any ideas..

Ok, here goes...
1) Make sure you have the drivers installed on your computer. (Available in Pudding Thread)
2) Go to pudding thread, and grab the Unlock Only IHOP sbf file (assuming your not on AT&T).
http://forum.xda-developers.com/showthread.php?t=1136261
"Unlock:
Unlocker only SBFs - These small 1mb SBF files will get your phone ready to fasboot oem unlock. They are the files most people should use.
ATT ONLY - Unlocker for 1.8.3 and 4.5.91 ATT firmwares
Orange/Bell/Telestra/Latin America/International users ONLY - Download IHOP"
3) Download & install RSD Lite. (Available in Pudding Thread)
4) Put phone in RSD Protocol Mode.
a) Power off phone
b) Upon Powering ON, hold Power Button + Volume UP
5) Connect Phone to computer via USB
6) unzip the IHOP sbf file to root of your C:\, open RSD Lite program, and drag sbf file onto File Name Box. Make sure RSD Lite sees your device connected to it, and then flash away.
7) After the sbf has flashed (hopefully without any errors), reboot your phone into fastboot mode (Power Button + Volume Down; when you see fastboot, press volume up to enter fastboot mode).
8) Re-connect phone to computer if you disconnected it.
9) In the folder where your fastboot files are located (if you don't have fastboot files, go download them from sticky in General Section), press Shift + Right Click, select Open Command Window Here.
10) With phone in fastboot mode, connected to PC and command window open in fastboot file location, type:
fastboot oem unlock
*This will give you your device #
Then type:
fastboot oem unlock [insert your # here]
10) Bootloader should unlock, then type fastboot reboot to reboot the phone. Should say Unlocked on boot screen now, if all went well.
11) Install Rom Racer's Recovery or Rom Manager, and you're good to go.
Think that about cover it... if you have any problems, give details of what is happening and at what step. Also, check the Pudding thread for possible solutions, as most problems have already been solved there.

Thank you for your explanation... I will give it a go when I get back from work tomorrow...
I appreciate you taking the time to help..
Sent from my MB860 using XDA App

Dcskeete said:
Thank you for your explanation... I will give it a go when I get back from work tomorrow...
I appreciate you taking the time to help..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
You should definatly also install busybox

Swiftks said:
Ok, here goes...
1) Make sure you have the drivers installed on your computer. (Available in Pudding Thread)
2) Go to pudding thread, and grab the Unlock Only IHOP sbf file (assuming your not on AT&T).
http://forum.xda-developers.com/showthread.php?t=1136261
"Unlock:
Unlocker only SBFs - These small 1mb SBF files will get your phone ready to fasboot oem unlock. They are the files most people should use.
ATT ONLY - Unlocker for 1.8.3 and 4.5.91 ATT firmwares
Orange/Bell/Telestra/Latin America/International users ONLY - Download IHOP"
3) Download & install RSD Lite. (Available in Pudding Thread)
4) Put phone in RSD Protocol Mode.
a) Power off phone
b) Upon Powering ON, hold Power Button + Volume UP
5) Connect Phone to computer via USB
6) unzip the IHOP sbf file to root of your C:\, open RSD Lite program, and drag sbf file onto File Name Box. Make sure RSD Lite sees your device connected to it, and then flash away.
7) After the sbf has flashed (hopefully without any errors), reboot your phone into fastboot mode (Power Button + Volume Down; when you see fastboot, press volume up to enter fastboot mode).
8) Re-connect phone to computer if you disconnected it.
9) In the folder where your fastboot files are located (if you don't have fastboot files, go download them from sticky in General Section), press Shift + Right Click, select Open Command Window Here.
10) With phone in fastboot mode, connected to PC and command window open in fastboot file location, type:
fastboot oem unlock
*This will give you your device #
Then type:
fastboot oem unlock [insert your # here]
10) Bootloader should unlock, then type fastboot reboot to reboot the phone. Should say Unlocked on boot screen now, if all went well.
11) Install Rom Racer's Recovery or Rom Manager, and you're good to go.
Think that about cover it... if you have any problems, give details of what is happening and at what step. Also, check the Pudding thread for possible solutions, as most problems have already been solved there.
Click to expand...
Click to collapse
A BIG THANKS!!!
Thanks so much for the advice and instructions... Unlocked beautifully... Now to find the ideal ROM....
Dont suppose there are any suggestions for International (UK) Atrix users??
Really appriciate the help..
Regards
Danny

I would recommend that you flashed TWRP 2.0 through CWM direct link. It lets you have touch screen in recovery; much easier! Then if you like CM7 you could try this or if you like the MIUI style (like me!) you would want to try this! It hasn't in-game audio yet but it's much cooler in my opinion. But Neutrino CM7 is really great!

Im not sure, maybe someone else can confirm. You should be using moto-fastboot to unlock & not regular fastboot, right?
Sent from my MB860 using xda premium

draken_1337 said:
I would recommend that you flashed TWRP 2.0 through CWM direct link. It lets you have touch screen in recovery; much easier! Then if you like CM7 you could try this or if you like the MIUI style (like me!) you would want to try this! It hasn't in-game audio yet but it's much cooler in my opinion. But Neutrino CM7 is really great!
Click to expand...
Click to collapse
People have had problems with TWRP.............stick with Romracers CWM, it's tried and trusted. If the touch screen in CWM gets you off, so be it, but I'd rather have a recovery that works with all ROM's, and not just some.

[Q] a2107 adb recovery?

I screwed up.
I just experimented with enabling phone mode on that device, after i had it rooted.
so i modified recomipled and signed the framework.apk but i had a typo in my script and the name of the new file is botched up.
My device instantly crashed of course. This is pretty forward to fix once i get access to /system in any way.. also i have a backup of that file on the pc.
Needless to say, without framework it wont boot. I *can* however get into recovery. but there is no adb option in there.
while i am in that menu, the pc recognices the device as "lenovo adb composite" but the adb does not seem to recognize it.
The drivers are set up correctly. the adb worked on the fully running device before the crash. (obviously, since i rooted it that way)
Any suggestions?
and what is the recovery menu point "download cap-firmware" doing exactly?
any help and potential helpfull links very much appreciated, i googled half the night and found next to nothing..

Solved
Solved.
appearantly the decive announces itself slightly differently in this mode.
solution:
The aur version of adb (arch linux) handles this correctly. no drivers needed.
so for all having problems, with this device, my recommendation for now: archlinux or archbang bang live, "packer -S adb" .. "adb shell"

Hi,
you managed to root your A2107A? I've been googling for two weeks and I didn't figure out... Could you please me tell me how you achieve that?
Cheers

da root
FiltroMan said:
Hi,
you managed to root your A2107A? I've been googling for two weeks and I didn't figure out... Could you please me tell me how you achieve that?
Cheers
Click to expand...
Click to collapse
sure thing.
as always first check, that all batteries are charged. (laptop, tablet, ..)
** first you need to enable usb debugging in the menu.
** then plug it in and check on windows that it is recognized properly.
it should show up as "lenovo(or android) composite adb interface" somewhere in device manager.
otherwise tell me, and i'll try to find the proper drivers. (on archlinux it worked without drivers, so if you fail on windows for some reason, that is an option too,)
** after that you need this:
https://dl.dropbox.com/u/31794772/Root_with_Restore_by_Bin4ry_v15.rar
i don't remember where exactly i found this on xda-deverlopers. credits to whoever put that up in the first place, sry.
** choose option 1 in the script.
follow the instructions on the tool. it will ask you at some point to push restore on the tablet, no worries, this is completely intended you wont loose any data if it works right. just leave all fields blank and hit restore.
congrats, you are now rootet. the device might require a reboot and might do that from itself (dont remember)
:good:
ps: doing backup like this first is generally a good idea: http://forum.xda-developers.com/showthread.php?t=1420351

I have the a2107-F will this root process work too?

valravn said:
I screwed up.
I just experimented with enabling phone mode on that device, after i had it rooted.
so i modified recomipled and signed the framework.apk but i had a typo in my script and the name of the new file is botched up.
My device instantly crashed of course. This is pretty forward to fix once i get access to /system in any way.. also i have a backup of that file on the pc.
Needless to say, without framework it wont boot. I *can* however get into recovery. but there is no adb option in there.
while i am in that menu, the pc recognices the device as "lenovo adb composite" but the adb does not seem to recognize it.
The drivers are set up correctly. the adb worked on the fully running device before the crash. (obviously, since i rooted it that way)
Any suggestions?
and what is the recovery menu point "download cap-firmware" doing exactly?
any help and potential helpfull links very much appreciated, i googled half the night and found next to nothing..
Click to expand...
Click to collapse
valravn,
Can you please elaborate a bit on modifying the framework.apk?
The solutions I found require flashing a whole rom which I wouldn't like to do (looks like I got the tablet with the latest FW).
Your help will be much appreciated.
Thanks.

I think i bricked my ideatab. i tried to update the CWM via ROM Manager unfortunately when i restarted the device, it got stuck on the menu showing "Press and select the Country Code". after pressing and selecting one of the choices it will just restart and return to the same menu.
Can you please help me guys? thanks in advance.