I've been reading up about what to do after I tried to "factory reset" my phone and then was stuck at the htc start up soon, which kept looping.
I've been trying to load recovery.img during fastboot (back+power) and then to apply update.zip during recovery (home+power).
However, the problem is that during fastboot, the device isn't recognized (when I go to adb devices on command prompt, no device is listed). I know that my drivers are good bc the device is found when I start up in the recovery mode. I tried to skip the part where I load recovery.img (since when I try to do that, it tells me that it can't be loaded), and to go straight to apply update.zip, but then the phone tells me that update.zip is either bad or can't be mounted.
I have a Rogers Magic (32A). I am a complete newbie, so any help would be greatly appreciated. I should also say that before I tried to do the factor reset, the phone was on the hero rom loaded by a previous user.
try this:
boot in recovery:
fastboot boot recovery.img
then, push update.zip on your sd card ( need a good rom in the tools folder on your computer)
adb shell mount /sdcard
adb push update.zip /sdcard
and apply update.zip with the recovery menu.
thanks for your reply, but it didn't work:
first, it said "cannot load recovery.img"
and then when I tried to mount, it said "mount: mounting dev/block/mmcblk0p1 on /sdcard failed: Device or resource busy"
replace recovery to correct path to your recovery image. (your phone mut be in fastboot mode power with back button pressed)
ex:
fastboot boot c:\sdk\tools\recovery-RAv1.2.1G.img
then your phone must boot on recovery and you could push update.zip
thanks so much. I figued it out - just a simple problem of the update.zip file being corrupt.
pato17 said:
thanks so much. I figued it out - just a simple problem of the update.zip file being corrupt.
Click to expand...
Click to collapse
i am having the same issues.
any help?
beastmods said:
i am having the same issues.
any help?
Click to expand...
Click to collapse
What exactly have you tried to do?
Sent from my HTC Magic using XDA App
Hi. My magic is having the same issues. Although I believe it is my own doing. I was going to create a gold card and I flashed the sappimg.zip, I can boot the phone into fastboot but it us not seen, when I run the fast boot command it just says waiting on device..
I can boot the phone up normally but it does not want to connect to the market our link my gmail account to it..
All to jailbreak... Any ideas?
Edit....
I must have had a poor internet connection last night. I have got the market working.
Sent from my GT-I9000 using Tapatalk
I am having the same problem.
I have a 32b on vodafone uk.
all the device adb drivers have installed fine. I have tried this on both my laptop and desktop (win 7) and when the phone is turned on - it shows fine under adb devices.
When i boot to fastboot, the phone doesnt show, and therefore i cannot load a custom rom.
Trying to root the phone I have so far used the goldcard method to downgrade to get back to 1.5, if i try to flash the recovery img from the phone (using flash rec) then when i boot to recovery (home+power) it hangs on the vodafone screen - this is why i wont to flash from fastboot.
any ideas?
Thanks
phone rooted?
FlashRec is out of date, I'm pretty sure. Is your phone rooted already, or are you at stock?
Hi Guys,
I've been trying to unlock, root and flash my Xoom but have become stuck - and I Just need some clear guidance on what to do next before I completely mess it up.
I have a UK 3g Xoom, and I was following this guide here
I managed to unlock the Xoom fine, it was reset back to how it was. made sure i checked debugging in the settings...These were the last steps I did (in bold):-
1.) Reboot into fastboot mode
adb reboot bootloader
(You should see “Starting Fastboot protocol Support.” at the top of your Xoom)
2.) Time to get your hands dirty
a.) fastboot flash boot boot.img
b.) fastboot reboot
The xoom will reboot and display the Dual Core M logo then do:
c.)
adb remount
adb push bcm4329.ko /system/lib/modules
adb reboot
Once Again The xoom will reboot and display the Dual Core M logo then do:
d.)
the device did reset - but when the M logo appears I tried adb remount command, but it's telling me device not found. I have installed all the usb drivers etc...not sure what's going on.
The device can be reset, but doesn't get any where, i can get Starting fastboot protocol support up on there screen, and a couple of time i was able to get in to recovery (android logo with !)
Edit*
and im sure the recovery is the standard one - i only get options for:- rebot system now, apply update from usb drive, wipe data/factory reset, wipe cache partion.
Can I sort this out?
Thanks in advance
Ok, I've managed to flash back a stock image...device is locked again.
HSKalay said:
Ok, I've managed to flash back a stock image...device is locked again.
Click to expand...
Click to collapse
There are guides here on the xda Xoom forum that you can use very successfully--try this:
http://forum.xda-developers.com/showthread.php?t=1249798
It's much easier to flash solarnz's Universal Xoom Root zip linked in the thread above than using the method you linked to. You will need a micro sdcard and solarnz's cwm recovery R4c v 3.2.0.0.
UPDATE 3: I've got it back to as stock as I can get it. I think I'm going to just return it and get a new one. Thank you all for your help.
UPDATE 2: As of right now, I'd like to completely remove FFF from the device, but I can only use fastboot to do it. I have absolutely no adb access. Is there a way?
UPDATE: Here is a video showing what is happening to my KF: http://www.youtube.com/watch?v=MH6oUg1NmC0
I hate to start another thread about boot loops/bricking, but I'm not sure what's going on with my fire.
I had CM7 installed successfully since the day after Christmas. This morning I woke up and my Fire was being really sluggish, so I rebooted it (I did not select reboot into recovery).
After it powered on, I was stuck at the CM7 boot screen (with the skateboarding android). I let it sit, but no luck. I went into TWRP to try and restore the backup I made of the stock rom. It looked successful, but when I rebooted I was stuck at the Kindle Fire boot screen.
Next, I tried wiping the device and re-installing CM7, but I received an error (something along the lines of E:Error unable to find /tmp/sideload/blahblah).
So I again restored my backup of the stock rom. Now when I power on my Fire I see the yellow triangle, then the kindle fire logo, yellow triangle, kindle fire logo, and it just keeps repeating. The problem is I am unable to connect to adb because the PC only seems to recognize the adb device for a few seconds after the yellow triangle, which does not give me enough time to fix the problem.
Any ideas?
looks like you'r out of battery ! the kf is rebooting !
would take the wall charger and charge for an hour
it's not possible to charge with the computer - it lasts forever
then it should respond in a stable state
b63 said:
looks like you'r out of battery ! the kf is rebooting !
would take the wall charger and charge for an hour
it's not possible to charge with the computer - it lasts forever
then it should respond in a stable state
Click to expand...
Click to collapse
Recovery shows my battery level to be at 53%. I've got it on the charger now, but I have a feeling there is something else going on.
Also, I am unable to mount my Fire's SD to my computer in recovery. It looks like it is working, but my computer never acknowledges it.
maybe because your last installation failed
nevertheless i would try to charge and then go in twrp and retry the installation
if that's not sucessful i would try to switch the kf to fastboot and copy a new rom. stock or prerooted stock or cm7 - whatever you like
in twrp there is a point "mount" - sdcard - then you should get it from computer
b63 said:
maybe because your last installation failed
nevertheless i would try to charge and then go in twrp and retry the installation
if that's not sucessful i would try to switch the kf to fastboot and copy a new rom. stock or prerooted stock or cm7 - whatever you like
in twrp there is a point "mount" - sdcard - then you should get it from computer
Click to expand...
Click to collapse
Thanks for the reply. Is adb required to get into fastboot? The problem is that I am unable to get into adb because my computer only sees the Fire for about 1 second. When I go into device manager, I don't see it at all.
EDIT: Yeah, I see the mount in TWRP, but it does not do anything when I select it.
Hi Im a beginner but Id like to try to help :
In case you become desperate ignore twrp's battery display and try wall charger.
Anorher idea id have is to shut down throughr twrp and start up then instead of rebooting.
ADB is needed to get into fastboot, but it's quick. If you use KFU, you can probably hit the option during the couple seconds you have available. I would say your best bet, however, is booting into twrp, doing a full wipe of system, cache, davlik cache, and maybe data, and then trying the rom install again.
skourg3 said:
ADB is needed to get into fastboot, but it's quick. If you use KFU, you can probably hit the option during the couple seconds you have available. I would say your best bet, however, is booting into twrp, doing a full wipe of system, cache, davlik cache, and maybe data, and then trying the rom install again.
Click to expand...
Click to collapse
So this time it looks like the installation worked in TWRP, but after reboot now I'm stuck at the CM7 boot screen. This is at least some progress, so when I get home I'll see what I can do.
Sent via my internet connected mobile cellular telephone.
Well, the battery is definitely not the issue. I've been trying to get fastboot, but the problem is the fact that I can not get adb. Has anyone else had issues with getting adb? I've already tried to install the drivers, and that doesn't work.
EDIT: I've tried issuing "adb devices" from the command prompt repeatedly as soon as I hear the ding until it disconnects a second later, but still I have had no luck.
Also, I found this thread in which someone else appears to have had a similar issue to mine.
[Q] New kind of unfixable Super Brick?
at the moment adb is useless - you should try to get the device in fastboot mode - correctly recognised from your computer - then work with fastboot commands - if you don't get that then your next opinion is buying or making a factory cable - but we should try to avoid that ...
b63 said:
at the moment adb is useless - you should try to get the device in fastboot mode - correctly recognised from your computer - then work with fastboot commands - if you don't get that then your next opinion is buying or making a factory cable - but we should try to avoid that ...
Click to expand...
Click to collapse
I can not seem to get fastboot to work either. Does fastboot rely on adb? Or do you just run the .exe file? I tried to run it, and nothing happened.
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
b63 said:
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
Click to expand...
Click to collapse
Just wanted to let you know I updated the OP with a video showing what is happening to my KF.
Haven't tried that particular rom yet, but I have wiped data and cache and attempted to re-install CM7.
great idea with the video !!!
b63 said:
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
Click to expand...
Click to collapse
OK, so I restored my original rooted kindle rom, but I still can't get into fastboot because of the problem I showed in the video. It is doing exactly the same thing, just instead of the CM7 boot screen, it is the Kindle Fire boot screen.
Is is possible to get into fastboot without the computer? Can anyone think of a reason why I would not be able to mount my device in TWRP?
I just want to understand something about fastboot... can you upload and flash roms with it? Or can you only get TWRP / FFF with it? I ask because I already have them, and I still can't do anything (mount from inside TWRP doesn't work). Thanks!
Sent via my internet connected mobile cellular telephone.
with fastboot you can install the newest fff and if you need twrp
but with the newest fff you can issue ""fastboot oem format"
see here:
http://forum.xda-developers.com/showthread.php?t=1369405
that should solve every issue ...
b63 said:
with fastboot you can install the newest fff and if you need twrp
but with the newest fff you can issue ""fastboot oem format"
see here:
http://forum.xda-developers.com/showthread.php?t=1369405
that should solve every issue ...
Click to expand...
Click to collapse
Cool. I just ordered one of SkOrPn's cables, so once I get it I'll be sure to give an update. Thanks for all the help so far!
The cable isn't need when you have the FFF bootloader, in fact, when your computer does see the device for the short amount of time shown in the video, fastboot is active. It's a feature of FFF. Fastboot is a command line tool like adb but is used for different things. It comes in Android sdk which if you have that, you should update the tools packages in the Android manager and it will update adb and fastboot. It looks like something is not working correctly in twrp and the OS is failing to load. I'm not sure you need to oem format tho.....
At some point you had to have used fastboot to install twrp and/or FFF.... Unless you used adb dd? :what:
Anyway, I can help more but it's late where I am, need to sleep. Was going to write more but... Need sleep lol. I'll post some questions and check back tomorrow.
Have you used adb before? Do you know if platform-tools is in your environment variables PATH? In other words, can you open up cmd and type adb or do you need to "cd" to platform-tools then use adb? If you know where adb is located? If so, is a file called fastboot in there? (Maby called fastboot.exe)
foxdog66 said:
The cable isn't need when you have the FFF bootloader, in fact, when your computer does see the device for the short amount of time shown in the video, fastboot is active. It's a feature of FFF. Fastboot is a command line tool like adb but is used for different things. It comes in Android sdk which if you have that, you should update the tools packages in the Android manager and it will update adb and fastboot. It looks like something is not working correctly in twrp and the OS is failing to load. I'm not sure you need to oem format tho.....
At some point you had to have used fastboot to install twrp and/or FFF.... Unless you used adb dd? :what:
Anyway, I can help more but it's late where I am, need to sleep. Was going to write more but... Need sleep lol. I'll post some questions and check back tomorrow.
Have you used adb before? Do you know if platform-tools is in your environment variables PATH? In other words, can you open up cmd and type adb or do you need to "cd" to platform-tools then use adb? If you know where adb is located? If so, is a file called fastboot in there? (Maby called fastboot.exe)
Click to expand...
Click to collapse
Yep, I've used adb successfully, and it is set up as an environmental variable. I actually installed FFF and TWRP with the KFU. Problem is I think something else is botched; perhaps it is TWRP itself, since I am unable to mount from TWRP. I'll try again when I get home.
Sent via my internet connected mobile cellular telephone.
I rooted my Nexus 7 months ago, but today I decide I wanted to try a new ROM and was wiping by data and system partitions for a fresh install of CM10, and I accidentally chose format all data. So my device is wiped except for TWRP.
Im in TWRP and when I run "adb devices" from my pc I get the following...015d2994a62bf403 sideload
but when I tried to use adb sideload, but i get the error "failed to write data 'protocol fault <no status>'
I'm screwed here...
You are not screwed, you still have a working bootloader (which I presume to be unlocked).
If the recovery keeps coming up in sideload mode after re-starting it, try soft-booting a recovery instead of booting it off the (previously flashed) recovery stored on the device
(with fastboot/bootloader showing on the N7)
Code:
fastboot boot recovery-image-file.img
This will certainly let you use a newer recovery as well if you want.
If that works and your drivers are correctly set up, you can push a file
(with soft-booted recovery running)
Code:
adb push My-Favorite-ROM.zip /sdcard/My-Favorite-ROM.zip
and then if that completes successfully, flash that ROM.
good luck
Hello Everyone,
I have been using CM7 for a long time on my ZTE Blade Gen II.
But recently I tried installing CM 10 Kang development.
After installing it, I am not able to boot into recovery.
When I open Clockwork Mod, it says my phone sis not rooted.
I tried rooting my phone again using Z4root, but am not able to.
My phone's ram is only 256 thus it is not able to load jellybean properly.
I also tried booting through cmd by using adb bootloader, it says more than one device and emulator and fails to rebooot or root my phone.
Can anybody help me get my phone back to CM 7 and get it rooted again.
Thanks,
Himanshu
hisun2006in said:
Hello Everyone,
I have been using CM7 for a long time on my ZTE Blade Gen II.
But recently I tried installing CM 10 Kang development.
After installing it, I am not able to boot into recovery.
When I open Clockwork Mod, it says my phone sis not rooted.
I tried rooting my phone again using Z4root, but am not able to.
My phone's ram is only 256 thus it is not able to load jellybean properly.
I also tried booting through cmd by using adb bootloader, it says more than one device and emulator and fails to rebooot or root my phone.
Can anybody help me get my phone back to CM 7 and get it rooted again.
Thanks,
Himanshu
Click to expand...
Click to collapse
Get phone in fastboot mode.
Plug it in to PC.
Get boot.img and recovery.img (if there is one) from CM7 Rom.
Open ADB.
Type in commands:
adb devices
adb reboot bootloader
fastboot flash boot.img
fastboot flash recovery.img (if there is one)
Then you get in recovery and can install the CM7 rom.
kevinrus123 said:
Get phone in fastboot mode.
Plug it in to PC.
Get boot.img and recovery.img (if there is one) from CM7 Rom.
Open ADB.
Type in commands:
adb devices
adb reboot bootloader
fastboot flash boot.img
fastboot flash recovery.img (if there is one)
Then you get in recovery and can install the CM7 rom.
Click to expand...
Click to collapse
Hello,
Thanks for the guidance. When I try to reboot into fastboot by using following command:
adb -s CM10.1-Blade reboot bootloader
My phone reboots and it just gets stuck on Dell screen. It does not get into the fastboot.
Thanks,
Himanshu
Please help me
hello friends, can someone please help me, I am still stuck on this.