...but I am. I unlocked bootloader and rooted a few days ago, now I flash jmz's CM9 on CWM and it took fine. I DL TB and it tells me I'm not rooted. Whhaaa? Furthermore, I go to flash boot.img in fastboot and I get this:
c:\fastboot>fastboot flash boot boot.img
sending 'boot' (3426 KB)...
FAILED (remote: not allowed)
finished. total time: -0.000s
Coming from the Optimus V I've never had to deal with flashing boot.img separately. What am I missing here?
Check the superuser app, maybe you have denied the root access by mistake. Other root apps are working fine?
For now we can not S-Off HTC One V thus this does not allow to flash the kernel (boot.img) using CWM and we need to do it via fastboot. However I have no idea why it does not allow to flash the boot.img
hlavicka82 said:
Check the superuser app, maybe you have denied the root access by mistake. Other root apps are working fine?
For now we can not S-Off HTC One V thus this does not allow to flash the kernel (boot.img) using CWM and we need to do it via fastboot. However I have no idea why it does not allow to flash the boot.img
Click to expand...
Click to collapse
After rooting, SuperSU was installed, then when I flashed from stock to CM9, I noticed it was replaced by Superuser. I didn't deny by mistake... it wouldn't even allow me the chance to, when I tried to open TB it simply stated I wasn't rooted and that Superuser denied it. I went back into recovery and restored, then used TB just fine on stock. For fun, I went into fastboot and tried to flash TWRP recovery and I still couldn't flash anything. Super weird... I had no problems doing it before when unlocking, installing CWM, and rooting.
jetfactor said:
After rooting, SuperSU was installed, then when I flashed from stock to CM9, I noticed it was replaced by Superuser. I didn't deny by mistake... it wouldn't even allow me the chance to, when I tried to open TB it simply stated I wasn't rooted and that Superuser denied it. I went back into recovery and restored, then used TB just fine on stock. For fun, I went into fastboot and tried to flash TWRP recovery and I still couldn't flash anything. Super weird... I had no problems doing it before when unlocking, installing CWM, and rooting.
Click to expand...
Click to collapse
known error for SU check here : http://forum.xda-developers.com/showpost.php?p=27527923&postcount=1
Lloir said:
known error for SU check here : http://forum.xda-developers.com/showpost.php?p=27527923&postcount=1
Click to expand...
Click to collapse
Hey rad, thanks, I'll try that out. Is it really a big deal if I don't flash that separate boot.img in fastboot after flashing that CM9 build through CWM if my phone seems to be acting fine? I'm still kind've confused as to why I can't flash anything in fastboot all of the sudden.
UPDATE: WORKED... thank you so much. I'm stoked right now!
jetfactor said:
Hey rad, thanks, I'll try that out. Is it really a big deal if I don't flash that separate boot.img in fastboot after flashing that CM9 build through CWM if my phone seems to be acting fine? I'm still kind've confused as to why I can't flash anything in fastboot all of the sudden.
UPDATE: WORKED... thank you so much. I'm stoked right now!
Click to expand...
Click to collapse
well you kind of need the modified one for GPS to work
Lloir said:
well you kind of need the modified one for GPS to work
Click to expand...
Click to collapse
Oh, ha, yeah, THAT little thing. Well hmm then, guess I'll have to figure that one out. Have any idea why I'm not able to flash it?
Related
ok you need to have clockworkmod installed...
Code:
fastboot flash recovery recovery.img
(insecure boot.img)
unzip boot.img.zip, boot to bootloader and
Code:
fastboot flash boot boot.img
or flash JRN84D-insecure-boot.zip from recovery
-put the CWM-SuperSU-v0.92-mod.zip on your sd and flash
done. :good:
if you have problems...
flash Koush's Jellybean repack (IMM76I OR IMM30D) http://d-h.st/Gkh
If recovery isn't sticking for you, delete recovery-from-boot.p in /system
I can do this for the other superuser as well...this is chainfire's super su
Thanks. May I clarify if I have to do both to get root or either one?
mcdull said:
Thanks. May I clarify if I have to do both to get root or either one?
Click to expand...
Click to collapse
the boot image is insecure...not necessarily needed
Oic.. thanks alot.
Is there any chance to pack the insecure kernel into cwm package as well?
I have no access to computer that allow me to apply fastboot flash. I am sure a lot of ppl will be in the same situation. Thanks alot.
mcdull said:
Oic.. thanks alot.
Is there any chance to pack the insecure kernel into cwm package as well?
I have no access to computer that allow me to apply fastboot flash. I am sure a lot of ppl will be in the same situation. Thanks alot.
Click to expand...
Click to collapse
sure, give me a minute
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
pablo1215 said:
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
Click to expand...
Click to collapse
bootloader mode -> reflash clockwork recovery using fastboot.
pablo1215 said:
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
Click to expand...
Click to collapse
fastboot a new one in...new one will stick
Code:
fastboot flash recovery recovery.img
Thanks guys appreciate the tip.
not working
Just flashed the two .zips. SuperSU is installed, but it says that the binary needs to be updated. When it tries to update it fails, and no root apps work.
krishmasand said:
Just flashed the two .zips. SuperSU is installed, but it says that the binary needs to be updated. When it tries to update it fails, and no root apps work.
Click to expand...
Click to collapse
reboot, then open supersu and then update
Worked like a charm, I've got clockwork back after a little adb action and now I'm restoring some apps with titanium. Can't wait to see the development on this. Just think I almost sold this phone and bought a Galaxy S3 today, may wait a week or so now.
Thanks guys you are amazing!!!
Flashed both zips in cwm
Super su app is there but needs to update binary
It fails on update
tramane said:
Flashed both zips in cwm
Super su app is there but needs to update binary
It fails on update
Click to expand...
Click to collapse
ok your the second guy...first hasn't responded back. did you reboot and try again?
which "jellybean" version are you on? koush's on rom manager seems to be the best (no wifi issues for one)
ogdobber said:
fastboot a new one in...new one will stick
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Is there a reason why my CWM won't stick? I fastboot a new one in and right after, I can access CWM from the bootloader menu if I don't boot into the OS yet. However, once I do boot into the OS and use ADB to reboot into recovery, it goes back to the Android with the red triangle.
What am I doing wrong? I'm usually pretty good with this stuff.
other superuser
still doesn't work, do you think you can try the other SuperUser app? D:
Enhanced said:
Is there a reason why my CWM won't stick? I fastboot a new one in and right after, I can access CWM from the bootloader menu if I don't boot into the OS yet. However, once I do boot into the OS and use ADB to reboot into recovery, it goes back to the Android with the red triangle.
What am I doing wrong? I'm usually pretty good with this stuff.
Click to expand...
Click to collapse
You'll need to delete that recovery from boot.p file otherwise it'll keep deleting CWM
[please delete]
IINexusII said:
You'll need to delete that recovery from boot.p file otherwise it'll keep deleting CWM
Click to expand...
Click to collapse
I knew common sense told me that I would need to delete the /system/recovery-from-boot.p file, but it wasn't posted here so I didn't bother.
Thanks.
Hi, question: I failed time and again to get CWM working, but finally got it to work using x-parts. However, x-parts is keen to point out that it is not a fully fledged recovery and that "if you wipe the system partition for any reason, it will be gone!".
Does this not mean that if I boot into recovery and install a new ROM (Going for the FXP CM10 one, if it matters), then when I wipe the phone beforehand I'll also wipe my CWM install, thus completely bricking the device? Would appreciate any thoughts, thanks
Artemicion said:
Hi, question: I failed time and again to get CWM working, but finally got it to work using x-parts. However, x-parts is keen to point out that it is not a fully fledged recovery and that "if you wipe the system partition for any reason, it will be gone!".
Does this not mean that if I boot into recovery and install a new ROM (Going for the FXP CM10 one, if it matters), then when I wipe the phone beforehand I'll also wipe my CWM install, thus completely bricking the device? Would appreciate any thoughts, thanks
Click to expand...
Click to collapse
Yes, if you wipe the system partition there will be no more CWM. For CM10, you need to flash a custom kernel for it to work. This custom kernel will usually come with a CWM recovery so it will not be wiped when you flash a new ROM.
僕のLT18iから送られてきた
Thanks. But, to clarify, once I flash new CM10/Jellybean Kernel, my current Gingerbread install will also completely cease to function right? And I'd need to flash back to something earlier to get it to work, if I so desired?
Artemicion said:
Thanks. But, to clarify, once I flash new CM10/Jellybean Kernel, my current Gingerbread install will also completely cease to function right? And I'd need to flash back to something earlier to get it to work, if I so desired?
Click to expand...
Click to collapse
Is your bootloader unlocked?
And yes you will have to flash GB ftf using flashtool
Sent from my LT18i
Yeah, I unlocked the bootloader and rooted it ages ago, but have since neglected actually updating the ROM, decided I can't live in a GB world anymore though.
So, as I understand it, process would be flash a new GB kernel to get CWM > Wipe Everything > Install the relevant ROM and GApps > Done? Does this ROM installation include the update to JB kernel then? Thanks
Artemicion said:
Yeah, I unlocked the bootloader and rooted it ages ago, but have since neglected actually updating the ROM, decided I can't live in a GB world anymore though.
So, as I understand it, process would be flash a new GB kernel to get CWM > Wipe Everything > Install the relevant ROM and GApps > Done? Does this ROM installation include the update to JB kernel then? Thanks
Click to expand...
Click to collapse
If I am not mistaken the kernel boot img should be inside the ROM zip. Check the ROM zip. Just flash the boot img using fastboot, boot into CWM recovery and flash ROM & gapps.
僕のLT18iから送られてきた
Ah, ok, well this brings me full circle. Because I'm trying to follow the boot instructions to do so, but:
fastboot -i 0xfce flash boot boot.img
doesn't work. I've taken the boot.img out of the ROM, and put it in the platform-tools folder. But whenever I try this line, it says it can't boot it, and quotes "no error" (no longer at home so can't quote the exact error, but it's something like that). I assumed the problem was me lacking CWM, hence was trying to install that first. Fastboot devices DOES show the device, and both fastboot and adb commands work in a terminal, but I just can't get it to boot into the ROM recovery for Cyanogenmod. Driving my crazy! Thanks
fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium
Artemicion said:
Ah, ok, well this brings me full circle. Because I'm trying to follow the boot instructions to do so, but:
fastboot -i 0xfce flash boot boot.img
doesn't work. I've taken the boot.img out of the ROM, and put it in the platform-tools folder. But whenever I try this line, it says it can't boot it, and quotes "no error" (no longer at home so can't quote the exact error, but it's something like that). I assumed the problem was me lacking CWM, hence was trying to install that first. Fastboot devices DOES show the device, and both fastboot and adb commands work in a terminal, but I just can't get it to boot into the ROM recovery for Cyanogenmod. Driving my crazy! Thanks
Click to expand...
Click to collapse
You don't need to add -i 0xfce to the command. Just type fastboot flash boot <name of boot image>.img
僕のLT18iから送られてきた
tangosierra_ said:
fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium
Click to expand...
Click to collapse
Thanks, I'll give that a go, not going to be able to try for a few days now, but will. FYI, I took the line of code I was trying directly from the Cyanogenmod wiki for Anzu
tangosierra_ said:
fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium
Click to expand...
Click to collapse
Ok, so finally got home to try this, still throwing this out: "error: cannot load 'boot.img': No error"
I've got the right boot.img in my platform-fools folder, the relevant CM build on my SD Root along with GApps. Drivers are definitely installed correctly as fastboot devices shows the device, as do adb command when it's on - anyone got any suggestions? Would be immensely grateful if this confounded problem could be solved. Thanks
Artemicion said:
Ok, so finally got home to try this, still throwing this out: "error: cannot load 'boot.img': No error"
I've got the right boot.img in my platform-fools folder, the relevant CM build on my SD Root along with GApps. Drivers are definitely installed correctly as fastboot devices shows the device, as do adb command when it's on - anyone got any suggestions? Would be immensely grateful if this confounded problem could be solved. Thanks
Click to expand...
Click to collapse
What is the name of the .img file? It can't have any spaces inside.
僕のLT18iから送られてきた
popthosegaskets said:
What is the name of the .img file? It can't have any spaces inside.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Looks to just be "boot.img" to me, no spaces or anything.
Have you tried flashtool?
Sent from my LT18i using xda premium
tangosierra_ said:
Have you tried flashtool?
Sent from my LT18i using xda premium
Click to expand...
Click to collapse
No, guess I'll try that next. As I remember, that's what I used to flash in order to root it ages ago. Thanks
hello,
i am S-off, unlocked, hboot 1.54.0000 and currently running TWRP 2.6.3.3. I installed 2.6.3.3 on 11-4-13 however, i'm trying to update to 2.6.3.4 and in fastboot i am getting this error...
writing 'recover'... FAILED (remote: not allowed)
this is the command i'm running with the .img file in my sdk folder...
fastboot flash recover openrecovery-twrp-2.6.3.4-m7vzw.img
i have searched the web and the only issue i find with HTC phones is that you will get this error if your bootloader is locked.... however mine is unlocked (confirmed looking at my phone right now in fastboot.
does anyone have any ideas on how i could install 2.6.3.3 last month, but this month i can't install TWRP via fastboot?
should i run the rumrunner s-off tool again to see if that fixes the issue?
i have been running cyanogen 10.2 and NOS 2.0 roms. i have tried switching back and forth and installing TWRP with each of these roms loaded and still no dice.
It looks like you're missing a y in your command if that's how you actually wrote the command.
If all else fails you can download flashify from the play store and use that to update the recovery.
midnight assassin said:
It looks like you're missing a y in your command if that's how you actually wrote the command.
If all else fails you can download flashify from the play store and use that to update the recovery.
Click to expand...
Click to collapse
OMG. you are correct. i don't know how many times i've looked at that to check and even checked in TWRP recovery forum and never noticed it. Thanks for pointing out something that should have been painfully obvious!
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7vzw.img
LOL, no problem. Flashify works too if you ever need it. I like to use fastboot too though.
Hey guys, this is my first post on XDA forum.
So I've recently bought a nexus 7, I used wugfresh's root kit to root my nexus but then it didn't work... so I've tired the auto root by chainfire. Then I was able to get root. So then I went to playstore and downloaded rom manager to install CWM. I went to recovery then I get this message:
E : Cant mount /cache/recovery/log etc.....
I've tried everything I can do such as researching, changing recovery, and watching a youtube tutorial but nothing helped.
Thanks.
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
nhizzat said:
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
Click to expand...
Click to collapse
I tried to format using wugfresh couple times but still not working...
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- https://developers.google.com/android/nexus/images
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
_MetalHead_ said:
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- Link Removed
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
Click to expand...
Click to collapse
I tried to flash TWRP but its still the same error code
z3r0c311 said:
I tried to flash TWRP but its still the same error code
Click to expand...
Click to collapse
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
_MetalHead_ said:
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
Click to expand...
Click to collapse
It would be great if u could tell me the commands, im nubby with this fastboot thing.
z3r0c311 said:
It would be great if u could tell me the commands, im nubby with this fastboot thing.
Click to expand...
Click to collapse
I gave you the commands in my first post in this thread.
Here's a guide to get you started-
http://forum.xda-developers.com/showthread.php?t=2277112
Sorry for another nubby question but how do I get flash_all.bat?
z3r0c311 said:
Sorry for another nubby question but how do I get flash_all.bat?
Click to expand...
Click to collapse
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
_MetalHead_ said:
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
Click to expand...
Click to collapse
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
z3r0c311 said:
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
Click to expand...
Click to collapse
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
_MetalHead_ said:
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
Click to expand...
Click to collapse
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
z3r0c311 said:
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
Click to expand...
Click to collapse
Did the system image flash successfully?
_MetalHead_ said:
Did the system image flash successfully?
Click to expand...
Click to collapse
using flash-all command, yeah
z3r0c311 said:
using flash-all command, yeah
Click to expand...
Click to collapse
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
_MetalHead_ said:
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
Click to expand...
Click to collapse
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
z3r0c311 said:
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
Click to expand...
Click to collapse
No, you can only flash custom ROMs if you have a custom recovery.
I was trying to install superzen but I accidentally wiped the OS. Am I screwed? Is there anything I can do, or is this looking like I bricked the phone?
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Go there and look at section 3.2. MAKE ABSOLUTELY SURE that you grab the correct firmware for your device (WW or CN, 550 or 551). As far as I can tell, unless you made a NANDROID backup in custom recovery prior to wiping system, this would be your only way back to working order.
Are you currently unable to get back to a custom recovery? Can you not just successfully flash superzen now?
Level99 said:
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Go there and look at section 3.2. MAKE ABSOLUTELY SURE that you grab the correct firmware for your device (WW or CN, 550 or 551). As far as I can tell, unless you made a NANDROID backup in custom recovery prior to wiping system, this would be your only way back to working order.
Are you currently unable to get back to a custom recovery? Can you not just successfully flash superzen now?
Click to expand...
Click to collapse
Thanks for the reply, it seems that my computer can't recognize my phone through adb, i can get into recovery, but my phone is just not recognizable. I should mention that it was earlier, and I installed supersu with cwm tethered.
EDIT: I can't use fastboot for twrp.img, it says I don't have permission and now I can't even access recovery because I'm stuck in a bootloop.
UPDATE: Ok so fastboot recognized the phone but I do not have permission to load twrp.img
Have you got this sorted now?
timbernot said:
Have you got this sorted now?
Click to expand...
Click to collapse
no, every time I try to flash twerp with fastboot, I get this error
"writing recovery failed <remote: permission denied>"
EDIT: HOLY HELL GUYS I FIXED IT! It turns out, my usb cord didn't work for some reason, tried another one and it works fine. Doing adb sideload right now.
venom55520 said:
no, every time I try to flash twerp with fastboot, I get this error
"writing recovery failed <remote: permission denied>"
EDIT: HOLY HELL GUYS I FIXED IT! It turns out, my usb cord didn't work for some reason, tried another one and it works fine. Doing adb sideload right now.
Click to expand...
Click to collapse
YaY !:good: