Related
I have a transformer prime rooted with cwr v5.8.1.8 and i tried to switch rom from virtuos prime on primalicious . I entered in cwr and deleted all and now i can even boot into my old rom .. i can't use usb mass storage and sd card when I try to boot it gets stuck on boot screen … what can I do now?..
Boot back into CWM and reinstall the ROM.
If that does not work, you will need to do Option 1a in the Recover from a Brick thread.
I can't install the rom again because I deleted everything (my mistake)...
dragos193 said:
I can't install the rom again because I deleted everything (my mistake)...
Click to expand...
Click to collapse
You will probably have to use ADB to push the ROM.zip to your internal sdcard from your PC ... then you will be able to reinstall the rom. If you read thru the "Unbrick your Prime" thread, there are tips to getting this done.
I try to use wsg unbricker but I don't know what options to chose to install a fresh stock rom please help..
nobody knows? please help i'm desperate
i still can't open my prime please anyone know what to do ?
This fixed my ASUS tablet! - Blob Files!
Hello there, for the last few nights I was having the same issue as you. I bricked my tablet, fixed it, and then just got stocked on the recovery with no data on my SDCARD. A guy named "dklue" gave me an idea, i googled some more information about something very important that I was missing!: "Blob files".
The "Primalicious_9.4.2.21._Final.zip" file or the "AOKP.zip" file will not work just like that because they are not in the format to be "Pushed" using the push command (At least thats what i kinda realized lol) anyhow, so i went online and searched for a ROM on Blob format and luckily i found the following!:
[ROM][WW][US][9.4.2.21] Primeval: The STOCK stock rom
So here is what worked for me thanks God! lol (Keep in mind that for some reason this process did not work for me on the new "CWM Touch Recovery 5.8.1.8" I actually had to downgrade my CWM to the 5.5.0.4 Version, you can download it from here:
androidroot . mobi / 2012 / 02/22/introducing-cwm-for-asus-transformer-prime/ --> WITH NO SPACE in between!
Here is how to Install the CWM file on your prime:
1. Get fastboot from that website, and extract it.
2. Download the blob file (tfp_CWM5_androidroot.blob), and put it in the same folder as where you extracted fastboot.
3. Power off your prime.
4. Boot with Volume-down pressed. Wait when you see text appearing. The prime will then allow you to start “fastboot” -> USB ICON.
5. Open up a command-line prompt, and navigate to where you extracted fastboot with “cd”.
6. Enter the following commandline to flash recovery: fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
7. Reboot
-----------------------------------------------------------------------------------------
Anyhow, so after you have that version installed:
1. Download "ROOTED 9.4.2.21 CWM compatible signed US version"
d - h . s t / r 4 4 -> WITH NO SPACE! (This is from the Primeval: The STOCK stock rom) Thread.
2. EXTRACT IT to the same directory where your ADB is! We only need the BLOBFILE from that zip folder!
3. Once you have the files extracted just run the following on your Command line:
adb push blobfile /sdcard/ ---> Its going to look like its not doing
nothing but dont worry its doing it in the background after 401 or some
seconds the command line will returned to you with a message like this:
1275kb, dadadada...
4. VERY IMPORTANT!: enter:
adb shell
dd if=/sdcard/blobfile of=/dev/block/mmcblk0p4
(Same as the previews step it will take forever but it will work dude!)
5. DONE! at least this is what worked for me man!
Im so happy now my Asus is freaking Brand NEw again! i was JUST about to through this garbage away but im so happy "dklue" gave me the BLOB concept idea! heheheh i guess i learned something new now..
I messed up my prime (stuck booting into CWM, could be worse) and I'm in the middle of fixing it, which will end up erasing my whole device, including internal SD. So I'm going to attempt to ADB pull the Nandroids I have on the device before I erase it, but since I cannot use the device, I'm not sure the whole path. Could someone please give me the path from root to the internal SD? Thanks in advance.
Why dont you give this a try....
Hey why dont you try this before you delete EVERYTHING on your Prime?... i discovered how to do it and it looks like it has worked for a few people too... just a thought... Here is how to do it:
"Blob files":
Search for: [ROM][WW][US][9.4.2.21] Primeval: The STOCK stock rom
So here is what worked for me thanks God! lol (Keep in mind that for some reason this process did not work for me on the new "CWM Touch Recovery 5.8.1.8" I actually had to downgrade my CWM to the 5.5.0.4 Version, you can download it from here:
androidroot . mobi / 2012 / 02/22/introducing-cwm-for-asus-transformer-prime/ --> WITH NO SPACE in between!
Here is how to Install the CWM file on your prime:
1. Get fastboot from that website, and extract it.
2. Download the blob file (tfp_CWM5_androidroot.blob), and put it in the same folder as where you extracted fastboot.
3. Power off your prime.
4. Boot with Volume-down pressed. Wait when you see text appearing. The prime will then allow you to start “fastboot” -> USB ICON.
5. Open up a command-line prompt, and navigate to where you extracted fastboot with “cd”.
6. Enter the following commandline to flash recovery: fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
7. Reboot
-----------------------------------------------------------------------------------------
Anyhow, so after you have that version installed:
1. Download "ROOTED 9.4.2.21 CWM compatible signed US version"
d - h . s t / r 4 4 -> WITH NO SPACE! (This is from the Primeval: The STOCK stock rom) Thread.
2. EXTRACT IT to the same directory where your ADB is! We only need the BLOBFILE from that zip folder!
3. Once you have the files extracted just run the following on your Command line:
adb push blobfile /sdcard/ ---> Its going to look like its not doing
nothing but dont worry its doing it in the background after 401 or some
seconds the command line will returned to you with a message like this:
1275kb, dadadada...
4. VERY IMPORTANT!: enter:
adb shell
dd if=/sdcard/blobfile of=/dev/block/mmcblk0p4
(Same as the previews step it will take forever but it will work dude!)
5. DONE! at least this is what worked for me man!
Im so happy now my Asus is freaking Brand NEw again! i was JUST about to through this garbage away but im so happy the BLOB concept idea came to mind! heheheh i guess i learned something new now..
Lol I highly appreciate the support, but my prime won't even boot into fastboot. If I hold down the "vol down" and power it come up with the white text, and then just boots into CWM whatever I do, it has to start from CWM..
Finally got the adb pull going (got some time to kill as I yank 20 gigs through a slow usb).
Now, I know there are already multiple threads discussing this problem, though part 1 of "How to Unbrick" hasn't worked for me. But I'm stuck booting into CWM, so if anyone wants to help take a crack at it, I would oh so appreciate it.
Yesterday, I unlocked and rooted my tf201, and proceeded to mess around with it. DL'd androwook, wiped everything and installed it. I think my mistake was choosing wipe internal SD when installing (it's where the installer was), and as a result, I was not able to get past the boot animation. I screwed around with it some more and eventually, after trying the Unbrick tool by MasterZen, was stuck at the splash screen with no recovery. Somehow, I had managed to screw up the boot and recovery. Oops.
However, I was able to fix it (boots normally, has recovery, etc..) with some knowledge of fastboot. This is what I did, as a complete amateur, so I probably can't answer specific questions and definitely cannot be held responsible for what you do to your tablet. Make sure you confirm files as non-corrupted with MD5s. This is basically a manual alternative to the Unbricker tool by MasterZen.
I used:
fastboot & adb
TWRP recovery twrp.blob
Ubuntu for Android boot image
[Optional] Stock .28 for unlocked (blob from inside the zip), which you will need to rename (system.blob)
Put these blobs in the folder with your fastboot.
1) get tf201 into fastboot (hold volume down + power on), connect to PC
2) command prompt, "cd [directory fastboot is in]"
3) "fastboot devices" & confirm your device is seen, otherwise go to devmgr and uninstall tf201 drivers and install the Universal Naked Drivers.
4) "fastboot -i 0x0b05 flash recovery twrp.blob" - flashes recovery so you have TWRP. You could try CWM if you'd like.
5) "fastboot -i 0x0b05 flash boot prime-sdlinux.blob" - flashes main kernel.
At this point you should be able to shut down, hold down volume down, and boot with the option of getting into recovery. In recovery, you could use ADB to push a specific rom you'd like and install zip from there. Alternatively, if you want to be able to boot into the system, and have downloaded the stock .28 for unlocked devices and placed the blob inside the folder with fastboot, you can type into command prompt:
6) "fastboot -i 0x0b05 flash system system.blob[or whatever you named it]"
And you should be able to boot up normally.
I've rooted and messed around with android phones before, but honestly I don't know enough about it to give 100% confident answers, and as such cannot be held accountable for what you do to your own device. I figured if someone also had this problem and wasn't able to get the Unbricker tool to work, they could benefit from what I learned. So good luck! Leave questions and feedback, and I'll do my best to answer.
Thanks to blade2k11, who in this post, made me realize that the main kernel was screwed, and that's why I couldn't access the recovery, and that I could fix it with the bootimage from the Ubuntu for Android post.
Thank you sooo much. This brought life back to my tablet!
jmonster141 said:
Thank you sooo much. This brought life back to my tablet!
Click to expand...
Click to collapse
I'm really glad to hear it! I almost thought I had posted this for nothing.
Yea man. I was set on me having a $500 paper weight. You're my tablet's savior. Thanks again
Sent from my myTouch 4g using xda app-developers app
thank you
i wanted to thank you so very much i was at my wits end stayed up for hours trying to fix a simple mistake and you saved the day with this if you where standing here i think i would prob kiss ya cause im that happy that i didn't mess up my only real toy i have
:good: I can't thank you enough, I've been working on mine for a few days now, bad rom download messed it up, then one click fix made things worse, was starting to think hardware issues when nothing was saving or taking, you just saved my tab and made my day than you
Happy to hear it. Have fun with custom roms! I'm on cm10 jellybro, I highly recommend it.
Sent from my Transformer Prime TF201 using xda app-developers app
i just went through the fire. did all this to the teee and still no os. was not able to push the rom i wanted even though my device is seen. the .blob file loaded in second,, yet im stuck on the splash screen with no OS installed. what do i need to do know?? i have got a paper wight on my deck and it was not bought to be so
jyarborough said:
i just went through the fire. did all this to the teee and still no os. was not able to push the rom i wanted even though my device is seen. the .blob file loaded in second,, yet im stuck on the splash screen with no OS installed. what do i need to do know?? i have got a paper wight on my deck and it was not bought to be so
Click to expand...
Click to collapse
Did you download the stock .28 rom and take out the system blob? Have you checked the MD5's to make sure they're downloaded without any corruptions?
jyarborough said:
i just went through the fire. did all this to the teee and still no os. was not able to push the rom i wanted even though my device is seen. the .blob file loaded in second,, yet im stuck on the splash screen with no OS installed. what do i need to do know?? i have got a paper wight on my deck and it was not bought to be so
Click to expand...
Click to collapse
Assuming you have access to adb, put the rom file in your adb folder you have been working from, in windows, right click the rom file, go to properieties, copy the name of the file.
In your adb command box you opened from within your adb folder (pressand hold shift while right clicking select command prompt here) type adb push then right click and paste the name of the rom you copied followed by .zip
This should take about 5 minutes to transfer, go get a coffee or something.
Once done, boot into recovery (twrp)
Under install you should see the rom, install, after the reboot you should be good....
i got stuck in a bootloop trying to unbrick, i can boot into recovery using this but when i try to transfer a rom with adb it gives an error that /sdcard is read-only so i cant put my rom on it. i tried using the stock .28 blob but im still in the same bootloop. not sure what else to
Deleted... whew!
Thanks guys for the help. I'm back up and running
Sent from my Transformer Prime TF201 using Tapatalk 2
Thank you soooo much. I have a working tablet again!
Worked!!
geo.z said:
Yesterday, I unlocked and rooted my tf201, and proceeded to mess around with it. DL'd androwook, wiped everything and installed it. I think my mistake was choosing wipe internal SD when installing (it's where the installer was), and as a result, I was not able to get past the boot animation. I screwed around with it some more and eventually, after trying the Unbrick tool by MasterZen, was stuck at the splash screen with no recovery. Somehow, I had managed to screw up the boot and recovery. Oops.
However, I was able to fix it (boots normally, has recovery, etc..) with some knowledge of fastboot. This is what I did, as a complete amateur, so I probably can't answer specific questions and definitely cannot be held responsible for what you do to your tablet. Make sure you confirm files as non-corrupted with MD5s. This is basically a manual alternative to the Unbricker tool by MasterZen.
I used:
fastboot & adb
TWRP recovery twrp.blob
Ubuntu for Android boot image
[Optional] Stock .28 for unlocked (blob from inside the zip), which you will need to rename (system.blob)
Put these blobs in the folder with your fastboot.
1) get tf201 into fastboot (hold volume down + power on), connect to PC
2) command prompt, "cd [directory fastboot is in]"
3) "fastboot devices" & confirm your device is seen, otherwise go to devmgr and uninstall tf201 drivers and install the Universal Naked Drivers.
4) "fastboot -i 0x0b05 flash recovery twrp.blob" - flashes recovery so you have TWRP. You could try CWM if you'd like.
5) "fastboot -i 0x0b05 flash boot prime-sdlinux.blob" - flashes main kernel.
At this point you should be able to shut down, hold down volume down, and boot with the option of getting into recovery. In recovery, you could use ADB to push a specific rom you'd like and install zip from there. Alternatively, if you want to be able to boot into the system, and have downloaded the stock .28 for unlocked devices and placed the blob inside the folder with fastboot, you can type into command prompt:
6) "fastboot -i 0x0b05 flash system system.blob[or whatever you named it]"
And you should be able to boot up normally.
I've rooted and messed around with android phones before, but honestly I don't know enough about it to give 100% confident answers, and as such cannot be held accountable for what you do to your own device. I figured if someone also had this problem and wasn't able to get the Unbricker tool to work, they could benefit from what I learned. So good luck! Leave questions and feedback, and I'll do my best to answer.
Thanks to blade2k11, who in this post, made me realize that the main kernel was screwed, and that's why I couldn't access the recovery, and that I could fix it with the bootimage from the Ubuntu for Android post.
Click to expand...
Click to collapse
:good::good: Thank you soooo much..My prime is alive !! very much appreciated!!!
Dead link
The link for the ubuntu for android kernel is dead...
Can someone post it back please ?
When I attempt to flash the blobs through fastboot it gives me FAILED unknown error. Anyone help me please? The recovery flashes fine but the boot image gives me the failed error. When i try to access recovery it gives me unrecoverable bootloader error
im trying to flash main kernel i get error that says fastboot.exe has stopped working. Any help?
C:\Users\John St\Desktop\android-sdk-windows\platform-tools>fastboot -i 0x0b05 f
lash recovery twrp.blob
sending 'recovery' (7462 KB)...
OKAY [ 2.037s]
writing 'recovery'...
OKAY [ 1.006s]
finished. total time: 3.045s
C:\Users\John St\Desktop\android-sdk-windows\platform-tools>fastboot -i 0x0b05 f
lash boot prime-sdlinux.blob
error: out of memory
Long story short I f'd up trying to install cyanogen. The only thing I can do on my phone currently is enter the bootloader. I've tried going back to stock by using the ruu zip through cmd, yet it always gives me a signature verify fail. When I've ran ruu.exe from my pc it gets to the final step but gives me an error when trying to find my phone.
I'm hoping since I can at least get in to fast boot that there is still hope.
also sorry for clogging the forum with another troubled phone story.
What did you do on the install? Cyan installer, download and install from recovery? A little more info please
Sent from my One using XDA Premium 4 mobile app
nwmn9386 said:
Long story short I f'd up trying to install cyanogen. The only thing I can do on my phone currently is enter the bootloader. I've tried going back to stock by using the ruu zip through cmd, yet it always gives me a signature verify fail. When I've ran ruu.exe from my pc it gets to the final step but gives me an error when trying to find my phone.
I'm hoping since I can at least get in to fast boot that there is still hope.
also sorry for clogging the forum with another troubled phone story.
Click to expand...
Click to collapse
This is the instructions posted by Scotty85
I'm just re-posting it for you
Quote:
http://androidforums.com/t-one-all-t...ml#post5864243
Quote:
here is how you extract rom.zip:
Quote:
the .exe utilities can be finicky,so if you have trouble getting it to run, you can extract "rom.zip" in the following manner:
-start the utility
-check the "i understand" box to move on to the next screen
-hide the utility temporarily out of site
-search your C drive for "rom.zip". you will find it in a temporary location(it will be in a different spot each time you run the utility)
-open the folder location,and transfer rom.zip to a safe location on your PC.
-unhide and cancel the utility,youre done with it.
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
Quote:
here are some directions to flash "rom.zip"
if youre working with a booted,operational phone,you can flsh the file in the following manner:
-open a cmd window
-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )
-place the zip file you want to flash into adb/fastboot directory
-enable usb debug,disable fastboot,plug in phone
-check for connectivity
adb devices (should return serial number)
-boot to fastboot
adb reboot bootloader
-check for connectivity again
fastboot devices
-flash the file
fastboot erase cache
fastboot oem rebootRUU (will put you in ruu mode,black screen silver htc letters)
fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writing, and the green status bar is moving on the phone screen)
*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish
-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)
-reboot back to the OS
fastbooot reboot
you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices
to answer your other question,yes,you will need to re-unlock and re-install recovery after running the RUU. an ruu is designed as an "unroot" solution, or emergency fix,if other attempts have not made the phone operational.
Click to expand...
Click to collapse
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
also to note....you dont have to install linux to get s-off....if you follow my guide you can do it straight from a live disk rather than installing it....so it wont erase or mess up your windows partition at all
Solved!
Thank you, Mjones, I finally got it! I knew it was much easier than I was making it out to be. I was missing the kernel! Yeah, a crucial part in the process, I know
I first ran CWM and flashed the ROM over and ran the .zip through recovery (which I couldn't understand at first as I could never find it in the directory) but the installer would only go 50% and would fail... makes sense why now lol
I later flashed TWRP and backed up again after recovering from the fail. I flashed over the kernel and voila! So simple... Had to slap myself.
Thanks again! Case solved.
REV3NT3CH, that is sweet!! I have been hoping there is a way to gain s-off with Windows. I have 7 at work and 8.1 (which I can't get anything to work on) at home. I actually have to focus on work today haha so I'll look into the method and try it out tomorrow if I can. Thanks for all of the help.
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Sorry, don't know anything about that phone.
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Did you try this first? (Right from Moto's site)
Perform a factory reset using external keys
1. Power off the phone, press and hold volume down button, press power button
2. Screen will come up with "Fastboot", press Vol down key to cycle through choices until you get "Android Recovery", then press Vol up key
3. Wait for the "triangle ! / Android" screen then go on to step 4
4. Press both Vol up and Vol down key simultaneously. A menu will come up
5. Tap on Vol down key until "wipe data/factory reset" is highlighted, and tap Power key. Another Confirmation screen will come. Tap on Vol down key until coming to Yes and tap Power key
6. After userdata is cleared, the "reboot system now" option will be highlighted by Default. Tap Power key
7. Phone will reboot to initial setup screen.
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
not working
hariom.gupta11 said:
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
Click to expand...
Click to collapse
not working on my 4c. write successful but when reboot is completed it goes to previous state.
"the user data partition can no longer be used"
zb602kl_x00tdb
L0RDZ3RO said:
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
Click to expand...
Click to collapse
I have same problem on asus zenfone max pro m1 I bought it online said used and now working
can't boot into recovery.
can't boot into system.
Only EDL Mode and Fastboot Mode, but fastboot is Locked whic I cant unlock because I cannot boot into system to toggle USB Debugging and allow OEM unlocking
Qualcomm is harder to flash than MTK that can use SP FlashTool.
on this I use QFIL but keeps "sahara error". I tried searching and try moving firmware file to bin but no Luck. I'm currently trying different version of QFIL Tool.
If it FAILS my only HOPE is to use MUT-QCfire which will Require a "SmartCardReader" Which is a bit pricey and I don't even know if it will work on my device.