Related
I'm having trouble getting back to a regular non locked down firmware. I flashed whispercore without fully understanding that it was actually in fact changing my entire rom.
I didnt even think to try and install CWM first to create a recovery image I need help getting out of this mess. I've used the Whispercore installer to unlock fastboot because whispercore relocks your fastboot after it does its thing.
Seems as though the stock sdk tools hated me for a while there and wouldnt detect my device than I later realised it was just because the sdk downloads itself all fragmented it basically took fastboot and adb and separated the two even though fastboot requires adb to function properly. I wont even begin to speculate as to why that happened, as thats beyond the scope of my question.
I basically have gotten to the point where i have Clock work mod (CWM) installed on my droid and the fastboot oem unlocked but am currently stuck at trying to get Cyanogenmod 7 stable on here.
***UPDATE**
Ok. This situation has been resolved. If you are having trouble with leaving whisper core and you've flashed a bunch of stuff trying desperately trying to fix this issue. Recognize the nexus S is a very easy device to fix. Fastboot is your saviour and the WhisperCore installer will even be kind enough to install all the drivers required to OEM unlock fastboot and do it for you.
Anyways the solution was: Re run the whispercore installer. Let it do its automagic.
Than flash a new Clockwork Mod recovery image this thread provided some clean Clockwork Mod images for flashing with fastboot that link is also for rooting but provides a good example for how to flash a new recovery.
Than Just reboot into recovery and use it to mount your phone via the Clockwork Mod recovery console to your computer, upload your favorite flavor of rom and than unmount the device. Once unmounted go back to the main menu in Clockwork mod and "Flash zip from SD" look for your rom in my case it was update-cm-7.0.3-NS-signed.zip Latest stable at the time. let it do its job.
Basically my issue was a combination of several factors. A bad Clockwork mod and a semi corrupt installation of SDK tools and Whispercore.
Possibly a stock firmware might be required first I just know that trying to straight flash cm7 stable from cwm is not working out.
you can get adb and the 2 dll files and fastboot in the same folder and cd to that directory. fastboot oem unlock should unlock your bootloader. then you should be able to flash a recovery if you want. might also want to check out the 1 click stock thread to see if that works.
I will probably have trouble finding this thread but I will look and if i come up with anything I will certainly post my findings.
This should work. But we shall see I will update the original post if I find a full solution.
Just flash a stock full rom (for i9023 you can use the one in my signature, don't forget get to use the wipe options in cwm recovery before) and the root should be gone. Afterwards, boot into bootloader and use fastboot command "fastboot oem lock" to lock the bootloader again. Than you can do a factory reset (and delete usb storage) to fully restore stock "experience".
__________________
Nexus S running Official 2.3.4 ROM (for i9023) with XTEUV92 Trinity kernel
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1214705&highlight=one+click+stock
I'm getting an error in the zip files no matter what one I use and its "Status 7" whatever that means.
chamunks said:
***UPDATE**
Ok. This situation has been resolved. If you are having trouble with leaving whisper core and you've flashed a bunch of stuff trying desperately trying to fix this issue. Recognize the nexus S is a very easy device to fix. Fastboot is your saviour and the WhisperCore installer will even be kind enough to install all the drivers required to OEM unlock fastboot and do it for you.
Anyways the solution was: Re run the whispercore installer. Let it do its automagic.
Than flash a new Clockwork Mod recovery image this thread provided some clean Clockwork Mod images for flashing with fastboot that link is also for rooting but provides a good example for how to flash a new recovery.
Than Just reboot into recovery and use it to mount your phone via the Clockwork Mod recovery console to your computer, upload your favorite flavor of rom and than unmount the device. Once unmounted go back to the main menu in Clockwork mod and "Flash zip from SD" look for your rom in my case it was update-cm-7.0.3-NS-signed.zip Latest stable at the time. let it do its job.
Basically my issue was a combination of several factors. A bad Clockwork mod and a semi corrupt installation of SDK tools and Whispercore.
Click to expand...
Click to collapse
I am trying to follow what you did and i am completely lost... I have a nexus s g that i am trying to get whispercore off it!
The "Automagic" you talk about. Isnt that just whispercore putting it in fast boot??? If so then then how do you use the recover image?
ACTUALLY I GOT THE ANSWER TO THESE QUESTIONS (ignore this thread)
I've been reading through this guide: http://forum.xda-developers.com/showthread.php?t=1249798
Question 1: When they say wipe everything, do they mean media too? (like music and such) Because when I had a samsung vibrant, they also said that but it never wiped media.
Question 2: Will I have to run a nandroid backup if this is my first time rooting, or will it be unnecessary?
Question 3: After finishing doing everything (unlocking and rooting)
do I just directly flash this http://forum.xda-developers.com/showthread.php?t=1484770 or is there something I need to do beforehand?
Also, in the guide, it says something about green android of ! if you have received an OTA. Which I have received many from Moto before. Will I have to download the original motorola files (HC or ICS, I'm currently on ICS)? If so, where do I put it? I'm confused
okantomi said:
"The green bot of !
there is one problem that exists with all xoom roots/cwm hacks. I had this problem as well as a bunch of other people when trying to flash CWM. If these files are present after an OTA update, then your xoom when entering recovery will show the green android robot with a exclaimation point instead of CWM.
If you have applied an official ota update.zip then you have a file like this on your xoom that will prevent CWM from working:
/system/recovery-from-boot.p /system/etc/install-recovery.sh
From the command window, type
adb remount adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Do not relock! After your Xoom boots back up and goes into the setup screens skip setup and enable usb debugging.
Proceed to Step 4.1, above.
Click to expand...
Click to collapse
Thanks so much! I'm new to this, it's so much different from rooting my Samsung Vibrant phone
cmd hangs
"Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Do not relock! After your Xoom boots back up and goes into the setup screens skip setup and enable usb debugging.
Proceed to Step 4.1, above. "
I did the above steps. All my command prompt does is hang...waiting for the xoom to respond.
rosystreasures said:
"Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Do not relock! After your Xoom boots back up and goes into the setup screens skip setup and enable usb debugging.
Proceed to Step 4.1, above. "
I did the above steps. All my command prompt does is hang...waiting for the xoom to respond.
Click to expand...
Click to collapse
There may be something wrong with my instructions...they've gotten convoluted over time. Try one of the other guides in General..there are a couple of newer ones that might work better. Mine still gives a lot of information but I think I'll retire it 'cause I don't want to cause issues.
I recently rooted and flashed a rom on my xoom. I'm a simple point and click windows user and I didn't have much trouble, so it's not that hard to do.
[HOW TO][UPDATED GUIDE] Unlocking & Rooting your XOOM!
http://forum.xda-developers.com/showthread.php?t=1477024
is the thread I used. Follow the instructions exactly and read the entire thread before you start, it'll save you a few headaches. This'll get you in (I think) ICS with superuser and all that jazz. If you want a rom, like me, then you'll have to head over to the development forum and take your pick. I'm running EOS 2.0, still deciding what to do with my xoom atm.
I wish I'd known of this thread last night. I struggled for several hours to root. It finally did. I also got the rom installed.
rosystreasures said:
I wish I'd known of this thread last night. I struggled for several hours to root. It finally did. I also got the rom installed.
Click to expand...
Click to collapse
I'm glad you got it rooted. That newer guide skips some steps that were needed earlier but are no longer needed. Like I said, I will retire my guide as too confusing now.
Quickboot vs. ROM manager
okantomi said:
I'm glad you got it rooted. That newer guide skips some steps that were needed earlier but are no longer needed. Like I said, I will retire my guide as too confusing now.
Click to expand...
Click to collapse
I started out with the standard 3.2 on my Xoom Wifi
with a nagging system message to update (I am guessing 3.2.2)
So I followed thread 1249798 and now am unlocke & rooted!
I am also using Recovery: Eos Recovery R6
I still get the nagging system message to update.
I would like to load a custom ROM, probably Moray.
My questions are this:
1. Will the Nagging system update message cause a
problem loading a custom ROM?
2. I could use the process as described in thread 1249798
to load the ROM, but I have read that since I am rooted
I could use Quick Boot app. Is this true? What about the
ROM Manager app, could I use this to load Moray? What is
the difference?
3. Since my base is 3.2 I am guessing I cannot load any
EOS ICS Rom's, is this correct? I need to bring my base
to 4.0 right?
4. Both Hammerhead and Moray state that they are both:
"Pre rooted with su and Superuser". Does this mean I did
not have to root my Xoom, I could have just loaded either
of these Roms and become rooted?
5. I have read some comments about:
/system/etc/install-recovery.sh
If I remove this file, will this stop the nagging System Update message?
6. Do I need to back anything up prior to loading a ROM?
Thanks!
Still with that, you can flash TEAM EOS ROM ICS. just boot into recovery and flash the TEAM EOS ROM. Mine was 3.2.1 as well. GOOD LUCK
I'm posting this in a single thread to minimize clutter.
I recently ran Easy Ace Root tool as instructed on my inspire. The bootloader unlocked, CWM flashed, but there was an error during superuser flash.
After a reflash of superuser things looked okay, but superuser began not responding. I re-flashed superuser twice in attempt to fix it using the Easy Ace Root Tool.
EDIT: I have discovered that superuser will only function with "USB debug mode" enabled. I've tried it on and off several times, and each time it malfunctions but function returns without a problem.
The backup I have been restoring seems to work because it was created with the debug mode enabled. Took a while to see it.
Second, CWM started to exhibit the "power off, charge" recovery bug where CWM opens.
Last, I attempted to install/flash 4ext Recovery Touch twice to address the CWM bug. Both times it hung at "flashing recovery" (approx 20 mins. both times). Eventually, it indicated that 4ext was installed. However, booting into recovery shows that I still have CWM. I used two different versions (RC8 & RC 7) in the attempt.
I'm now using the restored and working ROM. Solutions to the superuser debug issue I haven't seen posted
The failure to flash 4ext is troubling.
Questions
1. Could these issues be related? Or, what should I be looking for?
2. The recovery issue seems to be the most important. What might be the cause of 4ext to fail in this manner?
3. Can the Easy Ace Root Tool be rerun on the unlocked bootloader, and would that fix anything?
4. Is there reason to worry about flashing with CWM?
I see a number of possible solutions, the main one is to flash a new ROM, which I have already downloaded a couple, but doesn't adress the recovery problems.
The issue with CWM and 4ext leave me less than confident in using it to flash with, although CWM seems okay. The other item is that some ROMs indicate that S-off in required, but many of the threads are a couple years old.
5. Is it correct that S-off is not required to flash ROMs (I read it somewhere)?
I found an answer: NO, YOU DON'T NEED S-OFF TO FLASH ROMS....
Solving the issues are good lessons
Stock AT&T ROM
Android 2.3.5, Sense 3.0
Bootloader screen indicates-
UNLOCKED
S_ON
I know that's a lot for one thread but I'm just looking for a direction and I'll do the search.
If anyone has suggestions, directions, or ideas fire away.
Thanks
I think the fact that you are still S-ON is causing problems with the recovery flashing, since S-ON basically means that the recovery partition is not-writeable.
Have you tried using fastboot to flash a new recovery? Plug your phone into a computer, get into the bootloader, select "fastboot" (if not already selected), wait for "FASTBOOT USB" to appear, and then run the following on the computer:
Code:
fastboot flash recovery <path to recovery.img>
However that S-ON still worries me. You might have to do things manually:
Code:
androidforums.com/desire-hd-all-things-root/702100-how-manually-achieve-s-off-simunlock-supercid-inspire-4g-dhd.html
(Sorry for the broken URL - I had to disguise it. Blargh, I hate being a n00b.)
Evil_ryan said:
I think the fact that you are still S-OFF is causing problems with the recovery flashing, since S-OFF basically means that the recovery partition is not-writeable.
Have you tried using fastboot to flash a new recovery? Plug your phone into a computer, get into the bootloader, select "fastboot" (if not already selected), wait for "FASTBOOT USB" to appear, and then run the following on the computer:
Code:
fastboot flash recovery <path to recovery.img>
However that S-OFF still worries me. You might have to do things manually:
Code:
androidforums.com/desire-hd-all-things-root/702100-how-manually-achieve-s-off-simunlock-supercid-inspire-4g-dhd.html
(Sorry for the broken URL - I had to disguise it. Blargh, I hate being a n00b.)
Click to expand...
Click to collapse
Thanks, I think you meant to say the fact that I am still S-ON? The S_ON part shouldn't be an issue from all that I've gathered. In fact, that's how I have CWM. The Easy Ace Root Tool does CWM, with an unlocked bootloader S_ON. Nothing I have come across states that S_OFF is required to flash 4ext recovery.
Other noobs might find this other thread useful as there is some info and links to recovery images. http://forum.xda-developers.com/showthread.php?p=22489317#post22489317
No I haven't tried the fastboot yet. That is an option, I've got it and adb setup on my computer already. I have looked at AAHK, but as it says its no longer supported, and I don't think I need of S_OFF. Taking it slow to sort out the problems so I don't do sumthin stooopid.
How are you flashing 4ext? From fastboot?
Right, S-ON, that's what I get for writing this at 12 AM.
Don't bother with AAHK, it's discontinued, and even if you still had a copy it couldn't download the necessary files.
bananagranola said:
How are you flashing 4ext? From fastboot?
Click to expand...
Click to collapse
bananagranola,
I used the 4Ext Recovery Updater for both attempts. As I said in the OP, both attempts hung at "flashing recovery" approx 20 mins, and eventually indicated that 4ext was installed. In Recovery Updater it listed/highlighted the version I thought I had installed, but CWM was still the recovery that booted.
Cremnomaniac said:
bananagranola,
I used the 4Ext Recovery Updater for both attempts. As I said in the OP, both attempts hung at "flashing recovery" approx 20 mins, and eventually indicated that 4ext was installed. In Recovery Updater it listed/highlighted the version I thought I had installed, but CWM was still the recovery that booted.
Click to expand...
Click to collapse
Try doing it from fastboot.
bananagranola said:
Try doing it from fastboot.
Click to expand...
Click to collapse
I thought that would be next.
Can you confirm for me that the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=1848846 are correct for the Inspire 4G?
It's the EVO 3D forum. And I have some other links to using fastboot I'll check before doing it.
Yes, those instructions will work. If you can't boot into fastboot through the GUI, you can also power on the phone while holding the volume down button, and that will get you into the bootloader.
Evil_ryan said:
Yes, those instructions will work. If you can't boot into fastboot through the GUI, you can also power on the phone while holding the volume down button, and that will get you into the bootloader.
Click to expand...
Click to collapse
Okay, great. This is the only recovery .img that I have found 4EXT-recovery-2.2.7_RC5.img - 3.33 MB
If I install the 4ext recovery Updater after flashing it should work okay?
And, Will I be able to update once I have flashed it (assuming it works) and have installed the recovery Updater?
Cremnomaniac said:
If I install the 4ext recovery Updater after flashing it should work okay?
Click to expand...
Click to collapse
Probably. But I don't think it really matters, since if you can flash a recovery using fastboot, you can do everything that 4ext updater otherwise would.
Cremnomaniac said:
And, Will I be able to update once I have flashed it (assuming it works) and have installed the recovery Updater?
Click to expand...
Click to collapse
See above.
If 4ext doesn't work, you can also try CWM and TWRP (TeamWin Recovery Project). I use the latter with my Inspire 4g.
I strongly advise you use the app to download the recovery, unzip, and then flash it from fastboot.
bananagranola said:
I strongly advise you use the app to download the recovery, unzip, and then flash it from fastboot.
Click to expand...
Click to collapse
I'll take "strongly" as more than a suggestion. Thanks, it had not occurred to me to get the recovery.img from the updater.
I had actually found several other images and was trying to figure out what was what. That saved me some time, but I did read a lot about 4ext.
I was considering trying the Recovery Updater one more time. Bad Idea?
Cremnomaniac said:
I'll take "strongly" as more than a suggestion. Thanks, it had not occurred to me to get the recovery.img from the updater.
I had actually found several other images and was trying to figure out what was what. That saved me some time, but I did read a lot about 4ext.
I was considering trying the Recovery Updater one more time. Bad Idea?
Click to expand...
Click to collapse
I have a hunch that if you are S-On, you can only write to the recovery partition from fastboot.
bananagranola said:
I have a hunch that if you are S-On, you can only write to the recovery partition from fastboot.
Click to expand...
Click to collapse
I am S-ON. Does that present an issue with fastboot of the recovery.img?
I'm just going to overwrite the current recovery. Nothing else needs to be done does it?
Cremnomaniac said:
I am S-ON. Does that present an issue with fastboot of the recovery.img?
I'm just going to overwrite the current recovery. Nothing else needs to be done does it?
Click to expand...
Click to collapse
No.
bananagranola said:
No.
Click to expand...
Click to collapse
Solved the 4EXT flashing issue. Looks like 4ext flashed okay with fastboot, and the 4EXT Recovery Control works. Rebooted into recovery a couple times just to be sure. That kills 2 birds the CWM bug and the recovery flash.
Thanks for the help and suggestions all.
Some notes from a noobs experience -
Setting up ADB and Fastboot is very easy.
If your cautious as I am run some basic commands in ADB and Fastboot that won't do damage [devices, reboot, reboot-bootloader, etc.]
If you get "error: cannot load 'recovery.img" make sure you navigate to folder that recovery.img is located. Then run "Fastboot flash recovery [Filename]." Even though I set system variables on my desktop to point to adb and fastboot, it won't find the recovery image if you start from the wrong directory in terminal (i.e., C:\)
If you're in ADB and you use the command "adb reboot-bootloader" it will boot the device straight to "Fastboot USB".
Don't forget that each time you flash a ROM from recovery, you still need to fastboot flash its boot.img separately.
bananagranola said:
Don't forget that each time you flash a ROM from recovery, you still need to fastboot flash its boot.img separately.
Click to expand...
Click to collapse
Thanks for the reminder. I just spent an hour looking at 4EXT "smartflash no available". I hav some links for doing fastboot flash of the boot.img. I think I'm good there.
One question from my OP remains. Superuser only works (i.e., grants root access) when I have USB debug mode selected. When it's off superuser says the app (e.g., Titanium BU) is granted permission but just hangs until I force close it and re-enable USB debug. i can't find anything on this problem.
Is it an issue to run my phone in USB debug mode all the time? Or, any clue to the problem?
Hello everyone!
I need some help rooting my tf300t, because what I've read here and there was somewhat useless, since everyone sais different stuff. For first I'd like to ask for your help in clarifying which one is first. I have read guides in which rooting was first than pushing the recovery, and I have read ones in which fasbooting recovery was the first thing to do, and than flashing su. I have tried both methods, with no luck. When I try to fastboot twrp onto my device, it sais 'waiting for device'. I read that this means fastboot is not properly configured, but I am an administrator on my PC and I have the proper drivers, since adb reboot-bootloader works. So thats for flashing twrp first. Then rooting first. I tried with motochopper, but that does no work on 10.6.1.27.5. So I tried pushing root files manually, but when adb shell /data/local/temp, it sais failure. So if you could help me, of what did I do wrong, I'd greatly appreciate it.
Shad0w32 said:
Hello everyone!
I need some help rooting my tf300t, because what I've read here and there was somewhat useless, since everyone sais different stuff. For first I'd like to ask for your help in clarifying which one is first. I have read guides in which rooting was first than pushing the recovery, and I have read ones in which fasbooting recovery was the first thing to do, and than flashing su. I have tried both methods, with no luck. When I try to fastboot twrp onto my device, it sais 'waiting for device'. I read that this means fastboot is not properly configured, but I am an administrator on my PC and I have the proper drivers, since adb reboot-bootloader works. So thats for flashing twrp first. Then rooting first. I tried with motochopper, but that does no work on 10.6.1.27.5. So I tried pushing root files manually, but when adb shell /data/local/temp, it sais failure. So if you could help me, of what did I do wrong, I'd greatly appreciate it.
Click to expand...
Click to collapse
First make sure that you have unlocked your bootloader (text in the upper right corner of boot screen). What I did first was flash TWRP from ADB. In your case, you would flash the stock ROM, and then flash SU.
cmendonc2 said:
First make sure that you have unlocked your bootloader (text in the upper right corner of boot screen). What I did first was flash TWRP from ADB. In your case, you would flash the stock ROM, and then flash SU.
Click to expand...
Click to collapse
I know I'm unlocked sorry for not mentioning that, though even that was strange, because the unlock device app should have wiped the memory, but it didn't, and still unlocked. But I don't exactly understand what you mean by flashing the stock ROM, then SU. And if you mean that do that with twrp, I can't because fastboot flash recovery twrp.blob just waits for device. Is there another method which I can flash it with? Thanks in advance
Shad0w32 said:
I know I'm unlocked sorry for not mentioning that, though even that was strange, because the unlock device app should have wiped the memory, but it didn't, and still unlocked. But I don't exactly understand what you mean by flashing the stock ROM, then SU. And if you mean that do that with twrp, I can't because fastboot flash recovery twrp.blob just waits for device. Is there another method which I can flash it with? Thanks in advance
Click to expand...
Click to collapse
If it says "waiting for device," your PC is not communicating with the tab. What Windows version do you use? Does "fastboot device" command from fastboot mode on tab return any serial number? It should show a serial number before you can flash TWRP onto the tab. And where did you read that unlocking the device would wipe the memory?
Get fastboot to work first, then you can flash whatever. Otherwise, if you're on stock recovery, try loading the rom zip file onto your sd card and flash it using RCK option. If you have no idea what I'm talking about, read first, so you don't brick your tab just because you have no idea what the heck you're doing.
graphdarnell said:
If it says "waiting for device," your PC is not communicating with the tab. What Windows version do you use? Does "fastboot device" command from fastboot mode on tab return any serial number? It should show a serial number before you can flash TWRP onto the tab. And where did you read that unlocking the device would wipe the memory?
Get fastboot to work first, then you can flash whatever. Otherwise, if you're on stock recovery, try loading the rom zip file onto your sd card and flash it using RCK option. If you have no idea what I'm talking about, read first, so you don't brick your tab just because you have no idea what the heck you're doing.
Click to expand...
Click to collapse
For first, I downgraded my device, so I could root it with motochopper. Then I flashed recovery with the way explained here:http://forum.xda-developers.com/showthread.php?t=1845377
Now twrp seems to be working, i can start it, but it cant mount anything, so i cant flash anything from the device. Both 2.5 and 2.4.4 does this. Goo manager cant find a recovery for this device, so i cant use that either. Fastboot still cant see my tab. Im on windows 7, with proper drivers
Nevermind my stupidity, I installed the wrong recovery, not the one for the 4.2 bootloader. By now I'm a proud owner of a tf300t with cyanogenmod on it Thank you both though, for trying to help
i had a custom recovery (philz) and just updated to 4.4.4 (from 4.4.3 with root) using the OTA update (so dumb).
the phone is fine (4.4.4 at the moment) but when i want to get into the custom recovery, it shows me an android with a red exclamation mark. no recovery access.
i already tried to flash the custom recovery with fastboot but it says unknown partition using this guide:
http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
can anyone help me?
if you have root, use the flashify app to reflash philz recovery. or you can always use fastboot to flash a recovery, without having root as well. the rest you have to do on your own, nobody can help you. did you use toolkits? thats the only reason i can think of why you dont know how to flash a recovery. do yourself a favor, dont use root toolkits, youll never learn a thing and will end up messing up your phone doing something that should be simple.
simms22 said:
if you have root, use the flashify app to reflash philz recovery. or you can always use fastboot to flash a recovery, without having root as well. the rest you have to do on your own, nobody can help you. did you use toolkits? thats the only reason i can think of why you dont know how to flash a recovery. do yourself a favor, dont use root toolkits, youll never learn a thing and will end up messing up your phone doing something that should be simple.
Click to expand...
Click to collapse
hi,
i am trying to flash the recovery with the command prompt
fastboot flash philz.zip
it says unknown partition. i do not know why.
done, nevermind... sintax error LOL
cesar.maranhao said:
done, nevermind... sintax error LOL
Click to expand...
Click to collapse
yea, in fastboot it would have been..
fastboot flash recovery philz.img