Hello. I want to install the latest stable Cyanogenmod version 7.2.0 on my Nexus One which was up to now unlocked with stock software.
I followed instructions up to this point:
Installed Android SDK
Installed (downloaded) fastboot
Unlocked phone - bootloader now shows UNLOCKED, and the opened padlock symbol appears when powering up.
Downloaded and transferred recovery-RA-passion-v2.2.1.img
Up to this point all was ok. However when I select RECOVERY (from within BOOTLOADER) and press the POWER button, the phone reboots and I end up with a green android, a white triangle and yellow exclamation mark. The phone basically sticks there and I have to remove the battery. A photo is attached for your reference.
I also downloaded and transferred recovery-clockwork-5.0.2.0-passion.img However the same thing happens.
So basically I am stuck at this point. I can only remove the battery, and reboot the phone using the stock ROM.
What do you recommend?
hw did you transfer recovery.img? was it successfully flashed?
Sent from my Nexus One using Tapatalk
n1newbie said:
hw did you transfer recovery.img? was it successfully flashed?
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
Hi,
i transferred it using cmd prompt with command fastboot flash recovery recovery-RA-passion-v2.2.1.img and it was successful.
The same applies to when i transferred the recovery-clockwork-5.0.2.0-passion.img
What do you recommend?
White triangle and yellow exclamation mark means that you still have stock recovery, so the custom recovery flash did not work. When you see the triangle and exclamation mark you should push and hold both the Volume Up and Power Button (give it a few tries). Not that this will help you, but you don't have to pull the battery anymore
What do you see when you type fastboot devices in the command prompt when your phone is in fastboot mode?
tommert38 said:
White triangle and yellow exclamation mark means that you still have stock recovery, so the custom recovery flash did not work. When you see the triangle and exclamation mark you should push and hold both the Volume Up and Power Button (give it a few tries). Not that this will help you, but you don't have to pull the battery anymore
What do you see when you type fastboot devices in the command prompt when your phone is in fastboot mode?
Click to expand...
Click to collapse
Hi,
I run fastboot by starting a command prompt and changing to directory:
c:\users\xxxxxx\appdata\local\android\android-sdk\platform-tools
when I type fastboot devices i get the following reply:
HT05DP800931 fastboot
when I type fastboot flash recovery recovery-clockwork-5.0.2.0-passion.img i get the following reply:
sending recovery (3058 kb)
OKAY [ 0.499s]
writing 'recovery'....
OKAY [ 1.140s]
finished. total time 1.647s
So I assume the transfer is ok.
Is the path mentioned above correct?
Any idea what could be wrong?
All seems okay to me like that.. Could you try to flash 4EXT recovery? Make sure the recovery.img is in the same folder as fastboot (c:\users\xxxxxx\appdata\local\android\android-sdk\platform-tools). When it's finished, type fastboot reboot-bootloader and then navigate to recovery..
tommert38 said:
All seems okay to me like that.. Could you try to flash 4EXT recovery? Make sure the recovery.img is in the same folder as fastboot (c:\users\xxxxxx\appdata\local\android\android-sdk\platform-tools). When it's finished, type fastboot reboot-bootloader and then navigate to recovery..
Click to expand...
Click to collapse
Hello Tommert38,
Immediately after i sent my last post i tried again RECOVERY and to my surprise it worked! I proceeded with Backup, Wipe Factory and installed zip from SD card (first Cyanogenmod and then Google apps).
Everything seems to work, apart from MARKET. I can browse apps, however when i select any app and try to download it, I get error message "app name" could not be downloaded due to an error.
I googled for similar problems and found a post on xda developers:
http://forum.xda-developers.com/showthread.php?t=1724463
However i cannot find a solution.
Can you help?
can try different rom?
Sent from my Nexus One using Tapatalk
n1newbie said:
can try different rom?
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
Hello,
i tried 7.1 and it works great.
thanks for your help.
spannerj said:
Hello,
i tried 7.1 and it works great.
thanks for your help.
Click to expand...
Click to collapse
good . might be rom/gapps issue
Sent from my Nexus One using Tapatalk
I had similar problems with the white triangle/yellow exclamation mark.
Started with N1, never modified. Trying to run Recovery took me straight to triangle.
Unlocked bootloader, then tried to load ClockworkMod before rooting, as some tutorial told me to. File transferred without error, but still went straight to triangle when trying to run.
Rooted with SuperOneClick.
Went back and loaded CWM again with command line fastboot, again no error but still went to triangle when trying to run.
Downloaded Rom Manager (free) from app store, used it to install CWM. This actually worked for a few times, then it too started going directly to triangle when trying to run. It might have started failing when data was wiped, not sure.
Loaded the Amon Ra recovery tool using fastboot, it has worked reliably so far. Went on to load CGM 7.2 plus the apps, that was uneventful.
Some tutorial claimed you needed to load android-sdk directly under C:, not sure that's really required, but that's what I did.
Dave
That's happening most likely because all the participants of this thread are using stock ROM, and instead of booting to recovery directly from fastboot after flash, they first loaded the ROM and then tried to go to recovery.
Almost 3 years back, when actual developers with knowledge were all around this forum, it was a common knowledge that stock ROM overwrites the recovery on each boot, and to stop it from overwriting one should delete the stock recovery image that is used for that from the ROM. Also, booting to recovery directly after it was flashed and removing the stock recovery image from a ROM was a known way to avoid this kind of problems. I didn't try it, but I believe Google can still help finding these pieces of information, and Wiki definitely still holds them.
Well, I guess nobody reads the Wiki these days.
http://forum.xda-developers.com/wik...ages#For_unlocked_bootloader_-_using_fastboot
What really disturbs me is that the thread went to 2nd page without even a hint for this answer, while it's all that simple to get to - "Wiki -> Recovery", and here you have it.
yellow exclamation in white triangle
tommert38 said:
White triangle and yellow exclamation mark means that you still have stock recovery, so the custom recovery flash did not work. When you see the triangle and exclamation mark you should push and hold both the Volume Up and Power Button (give it a few tries). Not that this will help you, but you don't have to pull the battery anymore
What do you see when you type fastboot devices in the command prompt when your phone is in fastboot mode?
Click to expand...
Click to collapse
i also have the same problem but i did no flash i did hard reset on my galaxy spica(gt-i5700) and now stuck on that symbol my phone gets rebooted every time and get stuck on that symbol so plz help i also tried to flash with odin but my phone goes in download mode but is not detected by odin plzzz help and rply ass fast as possible i am using win 8 32 bit
Related
Okay so i unlocked my bootloader, that went well (as if thats hard)
and then i used Modacos superboot to root, it rooted (except for some reason the super user application opens to just a black screen). After that i continued to flash the recovery so that i can flash Cyanogen. When i try to flash the recovery i keep on getting the error 'cannot load'. i've tried like 4 different recovery roms. Not sure what im doing wrong
Oh and this has been tried on 2 different computers. One win7 and one XP. both gave the same output
_-..zKiLLA..-_ said:
Okay so i unlocked my bootloader, that went well (as if thats hard)
and then i used Modacos superboot to root, it rooted (except for some reason the super user application opens to just a black screen). After that i continued to flash the recovery so that i can flash Cyanogen. When i try to flash the recovery i keep on getting the error 'cannot load'. i've tried like 4 different recovery roms. Not sure what im doing wrong
Oh and this has been tried on 2 different computers. One win7 and one XP. both gave the same output
Click to expand...
Click to collapse
what commands are you using to flash Amon_RA's recovery image? i also assume you're at the white bootloader screen when trying to flash Amon_RA's recovery image. also, to confirm root access, download the N1 Torch app and if it works, you're rooted.
Yes the screen is white. And i am using "fastboot flash recovery recovery-RA-nexus-v1.7.0-cyan.img"
Cannot load what - fastboot or the ROM .img file? Do you have fastboot-windows.exe in the same directory as the rom image?-(not necessary if fastboot command works for you)
Type fastboot devices to double check your link between pc and phone. If not check usb cable & drivers.
Make sure ur unlock is right before flashing Amon. If you've rooted then you should see an unlocked-lock image (the the google Xscreen) while booting, or the N1 torch app method as mentioned above.
_-..zKiLLA..-_ said:
Yes the screen is white. And i am using "fastboot flash recovery recovery-RA-nexus-v1.7.0-cyan.img"
Click to expand...
Click to collapse
Make sure you got to that white screen by pressing the trackball and not the volume rocker.
I renamed the recovery image to "recovery-RA-nexus-v1.7.0.img"
Code:
fastboot flash recovery recovery-RA-nexus-v1.7.0.img
Make sure you check
Code:
fastboot devices
and get your device number and also make sure you put it in the tools folder of the Android SDK
Make these steps
Boot ur phone into bootloader
1 Rename the img to recovery.img
2 Place the file in ur toolfolder where u have ur fastboot
3 Rightclik on toolfolder+Shift choose open cmd here
4 write fastboot devices to be shure u are connected
5 then write fastboot flash recovery recovery.img
hi,I have the problem too.I try many times but still stuck TRIANGLE WITH !.when I do recovery image
the screen come up "sending 'recovery"3948 kb.....ok
writing' recovery'......ok
sending 'recovery"3948 kb.....ok
writing' recovery'......ok
Click to expand...
Click to collapse
Code:
fastboot reboot
Finally got Amon_Ra's recovery to install
I started with a stock N1 with froyo
had a few stumbles along the way and lots of searching...lots and lots lol
using the how-to on the cyanogen page I went to the letter as ive never used ADB
So I installed the Latest Android SDK to get the ADB and Fastboot.
verified connection with "adb devices" command and so on
when I tried to flash amons the first time I got an error saying it couldn't open the file.
I checked to see if i had Super user with the LED flashlight app and I did not so I downloaded Super boot and it worked like a charm
tried again and got the same cannot open error.
I renamed the recovery image back to the original file name and triple checked everything else which didnt help.
at this point it was late and i was exhausted so my memory is fuzzy
but i had a few more issues and finally I installed the clock work app and installed clockwork recovery i then used that to flash amons because that is what i was familiar with from my G1 days.
I do remember I had to go into fast boot and select clear storage. I think thats what caused my N1 to hang on reboot after the ROM was flashed.
But It may have even been what caused my issues with the recovery image.
Hi,
I recently got asked by a friend to flash his google nexus one phone. like a mug i said yes and now i have a issue where it turns on, vibrates 7 times and stays at the splash screen with the x on it. I can boot into the fast boot / recovery mode but nothing works.
this happened after i tried to root the phone, it said waiting for device and didnt do anything so i killed the app (Superoneclick) the phone disappeared from device manager and now wont go past the splash screen.
Does anyone have any idea how i can get it back? .. thanks in advance for any help.
James
I'm guessing, since you used S-O-C, the bootloader is not unlocked. The only way I know how to fix it is if you OEM unlock it. You'll need fastboot and your Android SDK setup correctly.
Once you have the setup done, change directories to the tools folder, wherever you put your sdk. Boot your phone into fastboot by holding the trackball while powering it on.
Code:
cd C:\asdk\tools\
Plug your phone into USB, and check if the computer sees it
Code:
fastboot devices
Unlock the bootloader (THERE IS NO GOING BACK! You can never re-lock a Nexus)
Code:
fastboot oem unlock
Now you can flash a boot.img and system.img (preferably pre-rooted) from fastboot, and it should boot normally. If the phone boots, the phone is perma-rooted, and won't need any other rooting procedure (you just need to flash a rooted rom). Next time, be a little more careful
Hi wdfowty
at running the risk of asking for more help and making you cross could you post some links to these downloads?
I am a total newbie to these phones and want to make sure i have the right apps.
thanks again for the help and the quick response... and if i manage to get this phone back believe me it will be the last one i try to flash !!
cheers
James
Nah, you've got me wrong. I'm all about helping people that are willing and able to be helped.
Follow this guide, it'll walk you through the steps to set up your sdk and unlock the bootloader. The guide is a little dated, so the info might not be 100%, but it's generally everything you'll need to know. If you get stuck, feel free to ask.
Hi again,
when i run the command fastboot devices i get an error AdbWinApi.dll is missing.
it tells me to reinstall the app but i have done that and also run all the updates and i still get the same error?
Interstingly i also get the phone to fastboot and it says in red text on the phone fastboot.usb but i cant see anything in device manager that says Nexus one etc?
any more help appreciated.... worst case you dont fancy a christmas break over in England do you?
cheers
james
jamesabennett said:
Hi again,
when i run the command fastboot devices i get an error AdbWinApi.dll is missing.
it tells me to reinstall the app but i have done that and also run all the updates and i still get the same error?
Interstingly i also get the phone to fastboot and it says in red text on the phone fastboot.usb but i cant see anything in device manager that says Nexus one etc?
any more help appreciated.... worst case you dont fancy a christmas break over in England do you?
cheers
james
Click to expand...
Click to collapse
With the latest version of the SDK tools, they changed the directory for adb and fastboot. Unfortunately I'm not on my Windows machine... but check in the directory where you have the SDK extracted to and look for a platform-tools directory (iirc). From there, you should see fastboot.
So basically where it says this "Type: cd C:\android-sdk-windows\tools" change it to "C:\android-sdk-windows\platform-tools". Keep in mind that directory name may change... again, I'm not on my Windows machine right now.
Hi again,
thanks for the continued help. I have managed to get past that, i have OEM unlocked the phone and managed to copy the flash image to the device using the commands in the link you sent me.
problem i have now is when i go into recovery the phone again just pulls up the splash screen and vibrates 7 times.
i believe what should happen according to the link is to follow the 6 steps below.. even i can do that, but the phone doesnt get that far
//Turn phone off -> Hold Volume Down, hold Power button
//Press Volume Down to highlight Recovery -> press Power to select Recovery
//Backup/Restore -> Nand backup
//Wipe -> Wipe data/factory reset
//Wipe -> Dalvik Cache
//Flash zip from sdcard -> alpha-r##-update-modacocustomrom-nexusone-desire-withadditions-signed.zip (Or whatever other ROM you're using.)
another point is it runs a couple of lines of blue txt relating to the sd card, but it flashes up and dissapears too quickly for me to be able to read it and send across to you.
thanks again and if you can work this out i owe you a beer !!
James
jamesabennett said:
Hi again,
thanks for the continued help. I have managed to get past that, i have OEM unlocked the phone and managed to copy the flash image to the device using the commands in the link you sent me.
problem i have now is when i go into recovery the phone again just pulls up the splash screen and vibrates 7 times.
i believe what should happen according to the link is to follow the 6 steps below.. even i can do that, but the phone doesnt get that far
//Turn phone off -> Hold Volume Down, hold Power button
//Press Volume Down to highlight Recovery -> press Power to select Recovery
//Backup/Restore -> Nand backup
//Wipe -> Wipe data/factory reset
//Wipe -> Dalvik Cache
//Flash zip from sdcard -> alpha-r##-update-modacocustomrom-nexusone-desire-withadditions-signed.zip (Or whatever other ROM you're using.)
another point is it runs a couple of lines of blue txt relating to the sd card, but it flashes up and dissapears too quickly for me to be able to read it and send across to you.
thanks again and if you can work this out i owe you a beer !!
James
Click to expand...
Click to collapse
Have you flashed the recovery image using fastboot, or did you only copy the recover image to the sdcard? Step IV in that guide.
It sounds like you need to reinstall your recovery.
Download the recovery found here: http://forum.xda-developers.com/showthread.php?t=611829
Rename that file to recovery.img and place it somewhere you can remember
Boot the phone into fastboot by holding down the trackball and pressing power button.
Code:
fastboot devices
Code:
fastboot flash recovery C:\path\to\recovery.img
If all went well, there should be no errors. On the phone, use the volume keys to select "Bootloader". It will take you to a white screen with the blue text (ignore it, it's looking for update files like "PASSIMG.zip"). Select recovery, and it'll boot into recovery. If you see menu items, you are good!
I ran the fastboot command and used the flash image ending 2.0.0
this is driving me round the bend !!
What happened when you used the fastboot flash command? Did you see a bar on the top right of the phone?
wdfowty said:
It sounds like you need to reinstall your recovery.
Download the recovery found here: http://forum.xda-developers.com/showthread.php?t=611829
Rename that file to recovery.img and place it somewhere you can remember
Boot the phone into fastboot by holding down the trackball and pressing power button.
Code:
fastboot devices
Code:
fastboot flash recovery C:\path\to\recovery.img
If all went well, there should be no errors. On the phone, use the volume keys to select "Bootloader". It will take you to a white screen with the blue text (ignore it, it's looking for update files like "PASSIMG.zip"). Select recovery, and it'll boot into recovery. If you see menu items, you are good!
Click to expand...
Click to collapse
i do that and it accepts the recovery file and the progress bar goes up on the right hand side and the cmd prompt says its all good. then when i select recovery the phone goes to the black background with the four coloured cross and the unlocked padlock, vibrates 7 times and just hangs on that screen
beleive it or not it booted up a moment ago and the phone worked like it did before with v2.2 on it. so i am happy now it can be recovered... i just dont know what to do to straighten it out!
yes. the bar goes up on the right hand side of the phone. and i have definitely unlocked it as it now says unlocked at the top of the menu.
Have you tried to reimage the phone with the passimg method? Directions are provided in the wiki, under the unlock/restore heading:
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Follow PASSIMG method (filename is case sensitive).
The link to the files is on the word "here" on step 2.
Use FRG33.
Sent from my Nexus One using XDA App
I have a S7 that is an X rev and it only has one camera on it and it has a different ID than the current streak 7s, so I can't apply the update that tmobile put out.
So I rooted the S7 and ran ROM MANAGER and it insists that the clockworkmod is installed correctly, but I can't reboot into recovery from that program (I don't think it works on s7 anyway) nor can I do it with the volume+ and power. (All that does is to boot into android)
The fastboot seems to work fine, so is there a way that I can push one of the .ZIP file ROMs using fastboot? I was thinking the "Dell Streak 2.2.2 update with FULL ROOT" would be a good one to try, but there are many .img files in the zip file and when I try fastboot update, I get the following errors:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I know that the following lines will work, but there isn't a system.img in the .zip file.
$fastboot flash boot boot.img
$fastboot flash recovery recovery.img
$fastboot flash system system.img
Thanks
Maj
You cant use regular fastboot commands its something like "fastboot -l 0413e blah blah search my threads for "how to flash stock img. " at the bottom of first post you will see fastboot help link
Sent from my Dell Streak 7 using XDA Premium App
http://forum.xda-developers.com/showpost.php?p=11929063&postcount=23
Sent from my Dell Streak 7 using XDA Premium App
Hey thatruth I've never used fastboot -iowhatever. All my fastboot cmds are fastboot (cmd) (dir) (file). Op so when holding +volume and power it doesn't put you in the bootloader? Your device may not work with cwr. Being a X device. And op are you using ubuntu/linux?
Sent from a signal
to get into cwr you have to hold vol and power. Then at the android menu select option 2 update.pkg. it will then boot into recovery
you can also reboot into recovery via adb
adb reboot recovery
graffixnyc said:
to get into cwr you have to hold vol and power. Then at the android menu select option 2 update.pkg. it will then boot into recovery
you can also reboot into recovery via adb
adb reboot recovery
Click to expand...
Click to collapse
I have not found a way to get into recovery. Using adb, fastboot, reboot into recovery options, and attempting vol+ and power, just boots straight into android. It says "cold-booting linux" and boots into android. It seems as if there isn't a real partition to do that, so I somehow need to dump an image onto the s7 so that it will have all of these partitions.
I have a Droid Incredible in which I've hacked to death, so I know how to get into the other menus, they just don't appear to be there or accessible for some reason.
Hellzya said:
Hey thatruth I've never used fastboot -iowhatever. All my fastboot cmds are fastboot (cmd) (dir) (file). Op so when holding +volume and power it doesn't put you in the bootloader? Your device may not work with cwr. Being a X device. And op are you using ubuntu/linux?
Sent from a signal
Click to expand...
Click to collapse
Yah, the +volume and power just boots the phone right into android. ROM Manager tells me that my rooted s7 installs cwr just fine. (in fact I've tried every different version it offers) I use w7 x64.
MajikUF said:
Yah, the +volume and power just boots the phone right into android. ROM Manager tells me that my rooted s7 installs cwr just fine. (in fact I've tried every different version it offers) I use w7 x64.
Click to expand...
Click to collapse
did you try flash cwm through fastboot yet?
http://www.4shared.com/file/l2JpliG6/recovery-clockwork-3019-streak.html
use this to download cwm recovery img
jiwengang said:
did you try flash cwm through fastboot yet?
http://www.4shared.com/file/l2JpliG6/recovery-clockwork-3019-streak.html
use this to download cwm recovery img
Click to expand...
Click to collapse
Assuming that's the same cwm that I got in the streaksmart forum, yah. I flashed that using fastboot as the recovery and then issued the reboot into recovery command and it just booted up android.
At this point, I am assuming the build/version I have isn't a standard build and I will have to do something outside the normal channels to get it to work. I might just chuck this and get another. Especially since I heard that there will be a compatible version of honeycomb for devices with less than stellar resolutions like the s7.
I think the key here is to unplug usb from computer and hold down the power and Vol+ button to reboot into recovery mode.
I struggled with this for probably half a day figuring that out.
thx for your help and I finally figured out the fastboot and then recovery.img. So then I rebooted and seleted the software upgrade via update and it been stuck on that selection for awhile. is that normal?
by the way upper left hand it has in white lettering Booting recovery kernel image.
chavezop said:
thx for your help and I finally figured out the fastboot and then recovery.img. So then I rebooted and seleted the software upgrade via update and it been stuck on that selection for awhile. is that normal?
Click to expand...
Click to collapse
It should say Booting recovery kernel image and then take you straight into clock work recovery...
Mines doing the same thing just getting stuck when it says Booting recovery kernel image and the dell logo apears then when i press the power button it turns off if i boot the device up not plugged into my computer and hold the power and volume+ it will flash red the LED and turn off.
Resolved Yet???
I'm having the same issue... CWM says it's working fine but when I try to load ROM it reboots normally back into the menu... Red lights blinking and does nothing when trying to get into recovery mode. Fastboot is only thing that seems to work and that even doesn't work properly...
I'm stuck with a ROM that is constantly crashing. Every 10 min or so, it needs to go. Please anyone that may have a method I could try would be appricitated...
J
Hey guys,
i did stupid things witch my razr i and now i'm completely lost…maybe someone can help?
I've been impatient enough to try to flash the leaked jb rom 3 days ago. That did'nt work
No, whenever i power up the phone it shows the red M logo and nothing happens.
I can power it down by holding vol+down and power for more than 4 seconds.
If i release the keys, it goes back to te red M,
If i keep holding vol+down it boot s into AP fastboot flash mode (secure boot) 20.0f
i can choose recovery and that'll work, but i don't have an update for external storage. rebooting from there leads to red M.
Normal Powerup, Factory and BP Tools are choosable, log says Booting into… but nothing happens after that, i'll stay in fastboot.
Power off works.
I tried to flash various images via »fastboot flash boot/recovery/system«, but nothing worked out.
I flashed the files from Razri_Root_Linux, two files (retail central europe) from here sbf.droid-developers, but nothing helped, every reboot leads to the red M.
I read about RSD-Lite, tried to install it under Win7, got it, but was lost after the Program always complained about an invalid xml.
Since i don't own that machine i went back to my linuxbox where i found sbf_flash, but i don't get it how to put the pieces together (which file/s to use)
Any hints on how to go from here?
[EDIT:] I downloaded 91.2.26001.Retail.en.EU.zip and did all the steps from flashandboot.bat, read
fastboot flash boot
fastboot flash system
fastboot flash recovery
next step ist to select recovery, did this an cwm comes up, sideloaded RAZRiRoot2.zip everything is pisitively quited, no errors are shown.
reboot leads to red M
wiped data/factory reset, reboot
red Logo.
I'm completely lost, please help
[\EDIT]
greetings, D.
I had same problem
Hello.
I had same problem because I did very stupid thing. I flashed homemade JB and because some apps don´t work I tried downgrade my i to ICS back....
My i stucked at the red M then I tried same thing as you and phone still booted into red M.
So I tried in windows cmd and FlashAndRoot.bat from this .zip "91.2.26001.Retail.en.EU - 4.1.2" it did nothing, but I tried to choose in fastboot mode BP Tools, then my i booted and started to flash JB what I can see in command window. Phone was still connected to PC. After next reboot my phone has work normally with JB.
I hope to help you. Let me know.
Lucki
Hi Lucki
thanks for jumping by.
Lucki_X said:
Hello.
So I tried in windows cmd and FlashAndRoot.bat from this .zip "91.2.26001.Retail.en.EU - 4.1.2" it did nothing, but I tried to choose in fastboot mode BP Tools,
Click to expand...
Click to collapse
I tried this, and display on razr i says »Booting into BP Tools mode…«
and nothing more happens, display stays on…
and after some time pc automounts a "cd-rom drive" with some motorola files (Autorun.inf MDMSetup.xml MotorolaDeviceManagerSetup.exe MDMSetup.ini MotorolaDeviceManager_2.2.28)
but it still won't reboot…
i don't know.
Hi.
I had opened command window, "FlashAndRoot.bat" was running (I pressed any key) process was running (it means freezing ) and at this time I chose in fastboot booting into BP tools mode. My phone did restart and after it "FlashAndRoot.bat" process started to flash JB. After flashing my phone is going normally with JB. But some apps don´t work in JB.
Lucki
Lucki_X said:
Hi.
I had opened command window, "FlashAndRoot.bat" was running (I pressed any key) process was running (it means freezing ) and at this time I chose in fastboot booting into BP tools mode. My phone did restart and after it "FlashAndRoot.bat" process started to flash JB. After flashing my phone is going normally with JB. But some apps don´t work in JB.
Lucki
Click to expand...
Click to collapse
Doesn't work. :crying:
since i use linux i opened FlashAndRoot.bat in texteditor and executed the comands from there in terminal
only chance for the script to stop and wait is IMHO(correct-me-if-i'm-wrong) "adb wait-for-device push RAZRiRoot2.zip /sdcard/RAZRiRoot2.zip & adb reboot bootloader"
but that message "Booting into BP Tools mode…" just stays there forever, or does it take longer than 5minutes?
dogo77 said:
but that message "Booting into BP Tools mode…" just stays there forever, or does it take longer than 5minutes?
Click to expand...
Click to collapse
In my case it booted within 10 second and ran.
I am noob, I am writing just my experience. I couldn´t give you another advice, sorry.
I'm not sure how far the real installation went, but i would find Windows computer, get RSD (6.0-6.14) and try to flash ICS first. If failed due to impossibility of downgrading, then try JB. While you are able to boot to Recovery - don't loose hope yet
okaban said:
I'm not sure how far the real installation went, but i would find Windows computer, get RSD (6.0-6.14) and try to flash ICS first. If failed due to impossibility of downgrading, then try JB. While you are able to boot to Recovery - don't loose hope yet
Click to expand...
Click to collapse
Yeah. I'm still stuck at the red logo, or indeed, at a blueish "Bootloader unlocked warnig" message since i was able to install parts of an image from sbf.droid-developers. But flashing always fails while trying to flash system.img_signed.
After reading and trying a lot these last days i think i have to install windows somewhere just to get rsd-lite to run.
sbf_flash for linux didn't work for me and fastboot gives stange warnings about "Invalid sparse file format at header magi"…
so i'll give rsd a try before i give up. As i read in posts by HSDPilot, this is the only tool that works
thanks for your help!
RESOLVED!
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
herrdrchili said:
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
Click to expand...
Click to collapse
so, if i understand you correctly, u've held down the volume down button and power button? becasue that's your fastboot. That's where you need to be to use RSD, and that's what i'd do.
ADB commands aren't used in fastboot mode. You should be able to see the device in fastboot mode with the command fastboot devices. Also, remember that the stock rom will try to restore the stock recovery when it is booted so if you flash recovery in fastboot mode then let the stock rom boot it will reflash the stock recovery which shows you the little droid and the red triangle.
You should still be okay though. Shut the phone off and boot into fastboot manually with power and volume down. Reflash the recovery. I know there are warnings about using mfastboot but I used standard fastboot before I saw those and didn't have an issue. From the fastboot screen after flashing the recovery, use volume down to get to highlight recovery and then press volume up to select, not power. Power will just do a standard reboot.
If you flashed twrp recovery then rebooting system will prompt you to install su. I think clockwork does the same thing. Letting the recovery install su will also prevent the stock recovery from getting restored and from there you should be good.
herrdrchili said:
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
Click to expand...
Click to collapse
ok then - i guess rsd has potential?
xpsychox said:
so, if i understand you correctly, u've held down the volume down button and power button? becasue that's your fastboot. That's where you need to be to use RSD, and that's what i'd do.
Click to expand...
Click to collapse
i can reboot into fastboot, but adb can't see the phone. I'll start trying to setup rsd and and see if it can do any better. any good links you know to get up to speed on that would be appreciated. if you know how to simply reflash the recovery via rsd that would be helpful too - thanks in advance!
herrdrchili said:
i can reboot into fastboot, but adb can't see the phone. I'll start trying to setup rsd and and see if it can do any better. any good links you know to get up to speed on that would be appreciated. if you know how to simply reflash the recovery via rsd that would be helpful too - thanks in advance!
Click to expand...
Click to collapse
the sites that I know of are for the device I have, a non devliper edition... I don't know if it makes a difference, I don't wanna make anything worse.
thanks for the sanity check,,,
btdonovan said:
ADB commands aren't used in fastboot mode. You should be able to see the device in fastboot mode with the command fastboot devices. Also, remember that the stock rom will try to restore the stock recovery when it is booted so if you flash recovery in fastboot mode then let the stock rom boot it will reflash the stock recovery which shows you the little droid and the red triangle.
You should still be okay though. Shut the phone off and boot into fastboot manually with power and volume down. Reflash the recovery. I know there are warnings about using mfastboot but I used standard fastboot before I saw those and didn't have an issue. From the fastboot screen after flashing the recovery, use volume down to get to highlight recovery and then press volume up to select, not power. Power will just do a standard reboot.
If you flashed twrp recovery then rebooting system will prompt you to install su. I think clockwork does the same thing. Letting the recovery install su will also prevent the stock recovery from getting restored and from there you should be good.
Click to expand...
Click to collapse
THANKS! just needed another set of eyes - man i need to not try doing this after a long day again i really appreciate your help. i got it now!
herrdrchili said:
THANKS! just needed another set of eyes - man i need to not try doing this after a long day again i really appreciate your help. i got it now!
Click to expand...
Click to collapse
Glad I could help!