Hello all,
I confess, I am truly a newb here, so please try to keep it as simple as possible.
I have tried rooting my new hero, but with no success. First of all, it came without Android Market, which was confusing. I installed it using vending.zip I found somewhere, but that didn't help as well - it didn't download anything AND kept crashing again and again.
I tried flashing it using Flashrec, but that also failed after Flashrec told me it failed to run the command (when trying to backup the recovery image). After that I tried fastboot and hboot, neither worked.
Could anyone help me out?...
see this thread:
http://forum.xda-developers.com/showthread.php?t=563256
no answers yet
And it doesn't seem likely there will be an answer there..
Does it?...
What can I do? Is there a way to downgrade or replace the ROM I have with a European rom?
Further more...
When trying to use a recovery image in fastboot mode, I get the following result:
I type:
Code:
fastboot boot cm-hero-recovery.img
And the response is:
Code:
downloading 'boot.img' ... FAILED (remote: not allow)
You cannot flash that version atm. The thread csasek linked you too is people trying to do what you are doing. Read that thread and post helpful idea's in there
Related
Hi Moto guys
I bought this RAZR. It is a GSM one without operator customizing.
I rooted it normally and tried to update to ICS leak (this one if I remember well).
It didn't work.
Anyway I downgrade back to Gingerbread and tried to flash in recovery the MIUI V4 zip.
It bootlooped.
So I wanted by the same way to downgrade to 2.3.6 again.
It was a fail.
From this, I had the flash failure screen at the beginning and lost the recovery.
Because of a "Battery Low" I made a factory cable and I can access again to the "flash failure" screen.
I found a tuto relating to the same problem than me and tried to apply it.
I downloaded this rom (SPDREM_U_01.6.5.1-167_SPU-15-M2-1-DE_1C.91P_0A.6C_TMDE_CFC_HWp2b_SIGNED.xml.zip) as explained and tried to flash it in RSD lite.
The problem is:
I have no error message, it just stays stuck on "6/11 flash system "system_signed".
I let it several hours, it never passed away this step.
With "Eternityprj_Fla**** script it's the same, it's blocked at "system writing..."
I don't really know if I'm considered to be on ICS or GB. My bootloader version is 0A.75 so I guess ICS one.
Any idea to reanimate this XT910?
Thanks for the help you could bring to me
P.S: I tried these roms since the first fail
-SPDREM_U_01.6.5.1-167_SPU-15-M2-1-DE_1C.91P_0A.6C_TMDE_CFC_HWp2b_SIGNED.zip
-SPDREM_U_01.6.5.1-167_SPU-15-M2-1-FR_SIGNEuropeAustraliaEMEA_USASPDRRTFR_HWp2b_Service1FF_fastboot.xml.zip
-SPDREM_U_01.6.5.1-73_SPU-11-PASS-10_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml.zip
-SPDREM_U_01.6.5.1-167_SPU-15-M2-3_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml.zip
Since I use XP in a VIRTUALBOX machine, I have an icon with activity on device.
During this operation, the activity on the phone is important
C:\Program Files\Android\android-sdk\platform-tools>fastboot.exe flash system sy
stem.img
sending 'system' (793344 KB)...
OKAY [ 28.541s]
Click to expand...
Click to collapse
As it is to this step, no activity...
writing 'system'...
Click to expand...
Click to collapse
I tried with normal fastboot executable from SDK and erpj-fastboot.exe, no difference.
Is it possible I make something wrong with my factory cable?
I don't think so because it makes my phone booting as I plug it and it writes normally boot.img for example with fastboot.
Your help would be appreciated very much guys ^^
Thanks!
Solved!
I can't explain why but I managed to access recovery even if system flash with fastboot never ended.
I flashed ICS rom and it booted well.
So it's solved even if I can't give explanations.
Thanks anyway.
flash fails...repeatedly
This has been covered extensively, but mine is still screwed up, i rooted the phone with clockwork mod. When the official ICS cam eout, i tried to manually download it. I have unrooted the phone and tried to install ics, it failed. So i tried flashing back to factory because clockwork was still popping up on boot. The flash continues to fail. I have tried using moto-fastboot in command prompt, i ha tried rsd lite with the flash(4 different ones). It keeps failing and i end up in the ap fastboot mode. it takes 2 tries to get the phone to boot normally and occasionally the clockwork boot menu pops up on reboot. Any ideas how to just start from scratch. As seen by the problems i have caused myself, i am a complete amateur here.
A little info, the phone is about 8 months old, rooted it once successfully, it is currently unrooted(i tried to reroot but got hung up in ap fastboot), updated drivers twice, moved the flash files all arounf my computer, using windows 7 64 bit. thanks to anyone who may help
Ok ok ok...
if i have an advice, before flashing, read read & read again.
So now.
Give me more info about your phone(xt910 / xt912 / europe / asia / latam /usa ) ??
Can you rsd to system_signed, or flash it manually through fastboot ?
When you installed ics manually which error did you have?
If you can, try to flash system_signed then reflash the OTA package with official recovery & wipe data. But i guess it wont work. For now i can't help you more without more info.
So tell me all you can and write it clear.
Or try this through rsd lite or fla**** http://forum.xda-developers.com/showthread.php?p=28199183
Sent from my XT910 using xda premium
yes, now ics fastboot file is out, you can easily fastboot to get back.
it is usa...i am downloading the ics fastboot now. I have tried the fastboot method with the latest gingerbread build, and also using the command prompt and flash commands....will let you know
thanks
Flash failed right away....how do i know i have the correct drivers? any other ideas?
I had the same issue when attempting to flash. Make sure you switch to a usb 2.0 port.
After that find the moto-fastboot package and then flash all the files manually using moto-fastboot instead of regular fastboot.
You have to do that for every single file. The file names are in the xml in the fastboot file.
im trying to flash cwm custom recovery rom. fastboot flash recovery <downloaded img> yielded a bootloader variable not supported (error). mfastboot flash recovery <downloaded img> yielded sending 'recovery' <7892 kb>..., okay [0.610s], writing 'recovery'..., okay [1.614s], finished. total time: 2.224s. but when i reboot into recovery, i get the stock recovery.
ive searched around online. ive looked for the stock rom file with no success (using android commander) to rename it. i know it must be there, but this is my first time rooting, unlocking the bootloader, and flashing roms. heck i cant even see the cwm rom written.
being a noobie im probably just missing something very basic and could use some detailed instructions to get past this point (my technical vocabulary in this area is very limited). i'm trying to use manual tools, so id like to stick with learning the manual way please.
btw, when i'm in fastboot mode other than rebooting the phone via 3 finger salute is there a terminal command to get back to adb mode? after flashing, i wanted to go back to adb to issue a reboot command from there. i read my flash might be overwritten as i reboot my the stock rom.
thanks in advance for the help.
Tools being used:
adb
fastboot
Android Commander
The phone:
Motorola Droid Razr HD (CDMA) running 4.1.1 build 9.8.10_39
Rooted via Motochopper
Bootloader unlocked via Motopocalypse
Hello all, I recently started the process of rooting my HTC One X+ and it all went smoothly until it came time to flash a recovery.
I used Windroid Universal toolkit to get started, thinking it would make things easier (not that I haven't rooted a phone before).
I unlocked the bootloader just fine, in the bootloader it gives "*unlocked*".
Next, I tried flashing TWRP with the toolkit, it brings me to bootloader, but when going to HBOOT and hitting recovery, it just brings me back to bootloader. Hmm, weird. So I decide to do it manually, download latest TWRP for evitareul (2.8.5.0), reboot into fastboot.
Execute: fastboot flash recovery twrp-2.8.5.0-evitareul.img
and it gives me this:
"sending 'recovery' (8224 KB)...
OKAY [ 1.115s]
writing 'recovery'...
(bootloader) Format partition SOS done
FAILED (remote: err = 0xa)
finished. total time: 1.153s"
I don't know whether it matters, but when going into HBOOT it pops up with some errors saying something along the lines of unable to access SD or something. It goes too fast to really write it down.
So I think maybe deleting cache would help, and to no avail. I look up online for the error code and nobody seems to have an answer for it. I apologize if this has been answered elsewhere on the forums, I looked for quite some time before posting a new thread. I'm not sure what is going wrong.
My end goal was to flash recovery, make a back up, then flash superSU but if I can't flash recovery then I'm not going to do anything else and risk a brick.
Does anyone know what's up with this error and how to fix it?
You're flashing a wrong recovery.
Coolgoly said:
You're flashing a wrong recovery.
Click to expand...
Click to collapse
What recovery should I be flashing then? My device is Evitare_UL, and I am getting img files from
HTML:
https://dl.twrp.me/evitareul/
.
I have tried other versions to no avail.
Evitareul should only have 2.5 TWRP out....
Hey guys, after receiving my new Kindle Fire (ariel running 4.5.3) I followed steps 1-3 outlined here and managed to get TWRP installed and my Kindle rooted. Things started going wrong in step 4 however, when I followed the instructions linking to here, which then linked to here. Steps 6-8 of DeLooper's instructions are where I started to run into problems.
I installed the 4.5.4 update and then the SuperSU update and clicked reboot. I didn't see the "updating message" referred to in the instructions, instead the device just went into a boot loop. During this boot loop, I was still able to get the device into adb mode, and from there back into the TWRP recovery. I tried flashing the same file (with and without SuperSU) several more times with the same results. I also tried wiping the cache as well as doing a factory reset and still nothing.
After going back to the second link above (bibikalka's post), I downloaded the 4.5.4 update file he linked to from Dropbox in "Update 3" (which was different than the 4.5.4 update linked to by DoLooper). I then installed this file using TWRP and rebooted. At this point, my device went back into a boot loop, but now I am unable to access ADB or my recovery.
I still can get the device into fastboot, so I don't believe this is irrecoverable. I tried issuing the following:
Code:
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.8.6.0-ariel.img
however, the command just hangs and nothing happens as far as I can tell.
My guess is that my recovery/bootloader file(s) are to blame for my problems? I'm still fairly inexperienced with all of this, so any wisdom or direction anyone could provide would be GREATLY appreciated. Thanks!
So here's some additional information -
Like I mentioned above, I can get the device into Fastboot mode, but once I get there I can only send one "successful" command. The first command supposedly works but the second will just hang. Occasionally on the second command I'll get the following
ERROR: could not clear input pipe; result e0004051, ignoring...
ERROR: could not clear output pipe; result e0004051, ignoring...
Click to expand...
Click to collapse
So from here I can run
Code:
fastboot -i 0x1949 boot boot.img
and I get
downloading 'boot.img'...
OKAY [ 0.204s]
booting...
Click to expand...
Click to collapse
and that's where it sticks. I've also tried doing the same with the TWRP recovery image I've got and the same thing happens.
Does anyone have any suggestions of anything I can try? I've got nothing at this point, so they don't even need to be good suggestions . Is my Kindle hard bricked?
greenie01 said:
Does anyone have any suggestions of anything I can try? I've got nothing at this point, so they don't even need to be good suggestions . Is my Kindle hard bricked?
Click to expand...
Click to collapse
Sorry you're dealing with this. @bibikalka will have to give you a hand. Just wanted to mention that the difference between the two TWRP_ready update zips is not significant. (Explained here: http://forum.xda-developers.com/showpost.php?p=61771073&postcount=28 ) I linked to mine while b's was briefly unavailable.
Early on a couple people flashed update zip into recovery partition, but I'm not sure how that happened or if it could be the problem. Hang in there. Bibikalka can advise.
greenie01 said:
So here's some additional information -
Like I mentioned above, I can get the device into Fastboot mode, but once I get there I can only send one "successful" command. The first command supposedly works but the second will just hang. Occasionally on the second command I'll get the following
So from here I can run
Code:
fastboot -i 0x1949 boot boot.img
and I get
and that's where it sticks. I've also tried doing the same with the TWRP recovery image I've got and the same thing happens.
Does anyone have any suggestions of anything I can try? I've got nothing at this point, so they don't even need to be good suggestions . Is my Kindle hard bricked?
Click to expand...
Click to collapse
If you cannot boot into TWRP, I think you are done (Pwr & Vol+ during boot up). I wonder if somehow you have 4.5.4 bootloaders in there (instead of 4.5.3), because these would prevent you from booting into TWRP.
Try to get into TWRP, if not, call Amazon.
I'm trying to flash my stock recovery to recover from a bootloop, but for some reason none of the commands I try seem to work. fastboot devices shows my device info, and fastboot reboot reboots the phone. Those would indicate that fastboot is working, but when I try fastboot boot recovery.img terminal shows downloading 'boot.img' . . . and just hangs. Same thing when I try fastboot flash recovery recovery.img, terminal says sending recovery and just hangs. I'm not sure why this is happening. I'm new to tinkering with Android and am pretty out of my depth here, though I am learning. I think this may be happening because the bootloader is still locked (?) and that is preventing any changes to the recovery partition, but that's just a guess. The phone is rooted, but I don't know if the bootloader is unlocked or not. I've tried to find out using fastboot commands, but big surprise, they just hang too.
I have the proper drivers installed, phone is in fastboot mode, USB is plugged into the back of my PC, and i'm using the latest version of fastboot. I'm just not sure what i'm missing here. Has anyone else experienced something similar or can at least guide me in the right direction? Thanks.
Thanks for the reply. Yes this about the @#[email protected] Coolpad. To answer your questions, trying fastboot oem device-info returns "failed (command write failed (no error))". Unfortunately, finding a full stock ROM for this device has proven to be impossible. I've been searching for weeks without luck. Coolpad is a little known brand outside of China it seems. Even going to Yulong's website (Coolpads manufacturer) and relying on google translate to slog through all the Chinese text i've found no mention of this particular phone. Plenty of other Coolpad models, just not this one. And apparently Coolpad Quattro is the same in chinese as it is in english so I know I didn't miss anything because of translation.
Without a stock ROM to use, and with my stock recovery being overwritten it seems like the recovery.img that Flashify created is all I have to work with. As for your last question, i'm not sure what kitchen it is. The download was linked from a Youtube video about porting custom recoveries. It seems to be just a series of BAT files (unpackimg, repacking, and cleanup).