I decided to flash JMZ's kernel and forgot to do a backup first...
Upon reboot none of the features work and wifi won't turn on.
Wiped the entire phone and wifi still refuses to turn on.
I noticed a previous thread says to flash boot.img in order for it to work but I get the following error when using fastboot to do it:
FAILED (remote: not allowed).
Can anyone help?
Okay, so I'm able to flash boot.img now. But flashing it doesn't seem to fix the problem. :crying:
Well, I had to restore the phone completely to stock in order to fix the problem. That's the last time I'm trying that.
Related
hello guys, i really need help with this last few steps of rooting my phone.
from here,http://forum.xda-developers.com/showthread.php?t=1625841
in step 4. flash recovery downloaded aboved by using this command: fastboot flash recovery recovery_for_1.28
i get the error message as per the title
now before i tried to flash the recovery 1.28, i flashed another recovery from o' brian's. would this cause any problems that would lead to the error message above? i assumed that flashing a new recovery would just overwrite the old one.
when i flashed the recovery from o'brian's, it says waiting for device or something similar to that. then i proceeded to go into recovery as instructed. however, my phone simply turns off. when i have to turn it back on manually, nothing changed.
can any kind soul please enlighten me?
niekehecv said:
hello guys, i really need help with this last few steps of rooting my phone.
from here,http://forum.xda-developers.com/showthread.php?t=1625841
in step 4. flash recovery downloaded aboved by using this command: fastboot flash recovery recovery_for_1.28
i get the error message as per the title
now before i tried to flash the recovery 1.28, i flashed another recovery from o' brian's. would this cause any problems that would lead to the error message above? i assumed that flashing a new recovery would just overwrite the old one.
when i flashed the recovery from o'brian's, it says waiting for device or something similar to that. then i proceeded to go into recovery as instructed. however, my phone simply turns off. when i have to turn it back on manually, nothing changed.
can any kind soul please enlighten me?
Click to expand...
Click to collapse
Note what kind of hboot do you have, check your bootloader, if you have Hboot 1.25 then the functional and recommended Recovery for you is by Paul O'Brien, if you are on Hboot 1.28 then the recommended one is bue unlimited.io, if you are lazy to search for them, you have them included in this tool, i really can't understand why people doesn't use this, as it is free and keeps you away from lots of searching, many threads are old, many procedures are old so the guide recommended by me for everything is the guide by stona15, this one
Hope this helps
Alright so here is my predicament.
I have a T-Mobile HTC ONE.
I am S-OFF, have TWRP 2.5.0.0 installed on my device, my bootloader says ***LOCKED*** because I locked it using revone after performing S-OFF.
I tried to install ElementalX 1.1 and after installation, my phone would not boot.
I have tried pushing a different kernel to the device and flashing that in recovery as well but I got the same result - a nonbooting device.
I tried to fastboot flash a kernel, I tried to fastboot flash a different recovery to see if that would allow me to flash the kernel and get my phone booting. No dice. I get "REMOTE FAILED" or not allowed error.
I'm at a loss right now because I didn't back up my boot partition before trying to flash this kernel and I honestly don't know what to do short of doing the HTC Unlock process again and literally losing everything on my phone.. Photos and everything. I don't have a recent PC backup either so that absolutely has to be the last resort.
ANY and ALL help will be greatly appreciated. This is the first time I've ever been in this position and not known what to try next.
Thanks in advance,
Dan
Ok so I was able to use revone to unlock the bootloader again and was able to successfully flash CWM. I tried re-flashing the kernel using CWM and the phone still will not boot.
Does anyone else have any ideas?
dharvey4651 said:
Ok so I was able to use revone to unlock the bootloader again and was able to successfully flash CWM. I tried re-flashing the kernel using CWM and the phone still will not boot.
Does anyone else have any ideas?
Click to expand...
Click to collapse
Did you manage to get back your stuffs (photos and such) yet?
What rom were you running? Just dirty flash it
Sent from my Tricked out HTC One
ryryzz said:
Did you manage to get back your stuffs (photos and such) yet?
Click to expand...
Click to collapse
No I never was able to back up my stuff but I haven't given up yet. I'm refusing to re-flash an RUU until I have exhausted all other options.
Squirrel1620 said:
What rom were you running? Just dirty flash it
Sent from my Tricked out HTC One
Click to expand...
Click to collapse
I was running Trickdroid. I'm still trying to get it back up and running.. Going to try and fastboot flash boot.img from stock 1.29 T-Mobile ROM next and see if that can get it to boot.
EDIT>> Trying a dirty re-flash now.
EDIT2>> Seems a dirty re-flash was just what I needed. Phone is booting now. I appreciate the tip.
Wonder why trying to flash a kernel while running TrickDroid would result in a non-booting device though. Makes no sense.
dharvey4651 said:
No I never was able to back up my stuff but I haven't given up yet. I'm refusing to re-flash an RUU until I have exhausted all other options.
I was running Trickdroid. I'm still trying to get it back up and running.. Going to try and fastboot flash boot.img from stock 1.29 T-Mobile ROM next and see if that can get it to boot.
Click to expand...
Click to collapse
I believe that you can boot into your recovery, right? Did you try adb pull to grab your stuffs?
TrickDorid has its own boot.img, if you try to flash stock T-Mobile boot.img over, then I think it'll cause a mess to you ROM. Try to avoid doing that.
I advice you to try adb pull to get your stuffs and then flash a RUU over
ryryzz said:
I believe that you can boot into your recovery, right? Did you try adb pull to grab your stuffs?
TrickDorid has its own boot.img, if you try to flash stock T-Mobile boot.img over, then I think it'll cause a mess to you ROM. Try to avoid doing that.
I advice you to try adb pull to get your stuffs and then flash a RUU over
Click to expand...
Click to collapse
Well I did a dirty flash and re-flashed TrickDroid. It got my phone booting and it seems there were minimal side effects.
Think I got lucky this time.
Still don't know why a kernel flash would have resulted in a non-booting phone if it said successful.
The strangest thing is that it would actually boot but non-responsive and with a black screen. I was still able to use adb and that's how I was able to re-unlock the bootloader and try fastboot flash the kernel.
Wish I had ENG or modded hboot though so that I had extended fastboot commands and I didn't have to mess with revone but it all worked out for now.
I, like others, seem to have an XT1064 (US) hosed by an OTA update to Lollipop. After getting endless com.process.xxx errors, the phone is unusable. I've tried all of the usual fixes -- clear cache, reset, etc. -- but I'm undaunted: unlocked the bootloader and thought I'd install a custom recovery before either restoring the stock ROM or installing one of the many fantastic ROMs posted here (Titan Prime looks great).
There is a hangup: custom recovery will not flash to sd. Fastboot says OKAY after flash operation, but the phone then boots only to the stock recovery ("Android system recovery <3e> LXB22.46-28") after the "no command" screen. Fine, whatever, I can do a "fastboot boot <recovery.img>" but nearly every recommended image (like TWRP2.7.1.1-titan-motog-2014.img for instance) do not boot -- instead it gives a flickering motorola logo). Thankfully, a custom recovery that would not seem to match version does work this way (the "philz_touch_6.58.7-falcon-unofficial.img"). However neither it nor any other will flash to sd. Any suggestions?
Before going on to another ROM I'd feel better if I had a solid recovery in place. It looks like Titan Prime wants TWRP, but I haven't been able to install it. Is this going to be a problem or will a "soft boot" of PhilZ work?
I'm also concerned about my bootloader version -- I haven't been able to deduce if I've got the right one for Lollipop-based ROMs. Fastboot says "AP Fastboot Flash Mode (S) 48.82(*) (sha-e004609, 2014-12-19 14:35:02)"
Any advice from the gurus here is much appreciated!
Have you tried to boot/flash TWRP 2.8.5.0 or 2.8.6.0 ?
http://forum.xda-developers.com/moto-g-2014/orig-development/recovery-twrp-2-8-2-0-touch-recovery-t2979149
Worked without problems on my device.The older versions are buggy.
Wolfcity said:
Have you tried to boot/flash TWRP 2.8.5.0 or 2.8.6.0 ?
http://forum.xda-developers.com/moto-g-2014/orig-development/recovery-twrp-2-8-2-0-touch-recovery-t2979149
Worked without problems on my device.The older versions are buggy.
Click to expand...
Click to collapse
Thank you Wolfcity! On your suggestion, I now tried TWRP 2.8.6.0 with the same result. "Soft boot" from command line goes to a "flicker" (a slow loop: a second or two of blank screen, then an off-center motorola logo for a few milliseconds, then blank again, repeat). Fastboot flash recovery, boots to "no command".
Hmmm...one wonders what differs about my device that is making it behave so unusually. I sure hope it isn't a true hardware failure, because I voided the warranty when I unlocked the bootloader! :^| Gets me to wondering if the recovery partition is corrupted. I lack the expertise to know the command parameters to reformat it. I take it that the factory recovery is stored elsewhere, accessed by the "hold power + tap vol-up" combo?
*update*
Not looking promising...
Decided to go back to stock before proceeding. Using Shawn5162's batch file, re-imaged stock 4.4.4. When I boot the phone it crashes with the same series of fatal errors as one by one processes fail: iHeart Radio, Google apps, com.process.phone, etc. then then powers off.
I have also tried using PhilZ custom recovery (soft boot, still can't flash it) doing a clean wipe/format first. Same result...after installing stock OS it crashes upon boot.
Is it possible that I have a virus that could survive being wiped? One thing I noticed is that during return to stock the flashing of partition and motoboot both fail. Could something be hiding itself in a partition it has locked me out of?
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.026s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.324s
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.109s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.376s
I'm running out of ideas.
*update*
Does anyone know how to format the partitions from fastboot? I've manually flashed both Kitkat and Lollipop stock firmware. Still, when I boot the phone I get many, many force quit errors until it hangs and shuts down. This was the initial problem that sent me into this mess in the first place!
I noticed among the errors is a message for an app that was installed before any of this happened! And I noticed when using the factory recovery (because I cannot get a proper custom recovery to flash/boot successfully, despite returning OKAY) that the factory reset says format cache failed. I think I've been fooling myself...despite flashing all kinds of things, it isn't actually flashing things!
Maybe I need to manually reformat the partitions to ensure that the phone is totally clean. A custom recovery would do this, but, therein is the problem...I can flash one, and the only one that strangely seems to work is for Falcon not Titan.
Has anything remotely like this happened to anyone else? The phone isn't bricked, but no matter what I try I can't get it to boot and run the OS.
no_frills said:
*update*
Does anyone know how to format the partitions from fastboot? I've manually flashed both Kitkat and Lollipop stock firmware. Still, when I boot the phone I get many, many force quit errors until it hangs and shuts down. This was the initial problem that sent me into this mess in the first place!
I noticed among the errors is a message for an app that was installed before any of this happened! And I noticed when using the factory recovery (because I cannot get a proper custom recovery to flash/boot successfully, despite returning OKAY) that the factory reset says format cache failed. I think I've been fooling myself...despite flashing all kinds of things, it isn't actually flashing things!
Maybe I need to manually reformat the partitions to ensure that the phone is totally clean. A custom recovery would do this, but, therein is the problem...I can flash one, and the only one that strangely seems to work is for Falcon not Titan.
Has anything remotely like this happened to anyone else? The phone isn't bricked, but no matter what I try I can't get it to boot and run the OS.
Click to expand...
Click to collapse
I think you are trying to flash a stock rom of the previous version than the latest one which u have flashed.. I mean u are trying to flash kitkat files after upgrading to lollypop.. so this error
tbiwalkar said:
I think you are trying to flash a stock rom of the previous version than the latest one which u have flashed.. I mean u are trying to flash kitkat files after upgrading to lollypop.. so this error
Click to expand...
Click to collapse
Correct. When I tried to restore using a stock lollipop image, I did not get the errors flashing it.
Unfortunately, none of the core problems are solved.
I did discover that TWRP version 2.8.5.0 will run from "fastboot boot twrp-2.8.5.0-titan.img". But no matter what version I use, "fastboot flash recovery <recovery-name.img> does not work. Fastboot reports success flashing, but booting to recovery only goes to the "no command" screen.
Is there such a thing as "execute permission" on a partition or file (like linux has) and could it be that the partition has become not bootable somehow?
And even after flashing the stock lollipop image I still get repeated force quits and crash. In an attempt to get rid of whatever errors are present on the disk, I went for a full format of data and now TWRP has been hung on format for a couple of hours. I'm afraid to kill it, so I'm going to leave it overnight.
Is it possible that fastboot wipe cache could be fooled, report success, but not actually remove the data? After installing the stock lollipop image, the strangest thing happened. On first start it wouldn't boot, so before restarting I ran fastboot wipe cache then booted it. It came up with an "android is updating" message that quickly vanished then it hung on black screen.
So many questions, I know, but none of the standard advice is working in this case. Thanks to all who've read this thread so far!
Any update on this?
I have a Moto G exhibiting the exact same symptoms (only able to boot the one recovery, can't flash any). Fastboot flash says successful, but nothing is actually flashed.
Mine usually goes to a black screen right after the boot animation, but on rare occasion actually boots all services stop responding and the screen goes black.
If anyone has figured anything out about this let me know!
any fixes?
I am in the same boat. Did you manage to fix it?
Hello,
Tried rooting my phone with no prior experience. Worked, but eventually I got to where the phone wouldn't boot past splash screen (logo came up, then screen went black while backlight is on and didn't respond to stimuli until battery was removed). Possibly resulted from a build.prop file problem. Did get into boot though, so I fixed that problem by installing a cyanogen rom from a zip file using twrp recovery. I didn't want a custom mod though since I'm used to the look and feel of the 4.0.3 ICS I had, and the cyanogen doesn't seem to have google play so I can't even download anything (original purpose of rooting was to get incompatible apps by spoofing via build.prop file). Currently trying to get back to stock. Unfortunately I didn't make a nandroid backup of the system before the problem occurred, hence I have no backup to flash.
What I tried:
1. Use the official HTC 4.0.3 RUU .exe to upload to the phone. Unfortunately HTC Sync doesn't see this phone, even though I have the correct drivers installed.
2. Attempted to use twrp recovery to install the rom.zip extracted from the RUU directly, the same way I successfully installed the cyanogenmod rom. Failed, claiming it's unable to open zip. The .zip file was checked for integrity and returned by an archiver app.
3. Tried to use these commands from the cmd with phone connected to install the .zip from fastboot:
fastboot erase cache
fastboot oem rebootRuu
fastboot flash zip rom.zip (rom.zip being the functional file of the stock rom)
Failed, saying it's not allowed. Tried it with both locked and unlocked bootloader, no difference.
4. Unzipped the file and tried to flash the system.img file directly, but that failed with a "data length is too large" error.
5. My recovery being twrp 2.1.1, tried looking for altenatives. Can't find any links to download the WCX recovery, but I found several for newer twrp versions, including 2.3.1.0 and 2.6.3.0 which I tried downloading flashing. After flashing the phone got stuck at the cyanogenmod loading logo and wouldn't boot further, and the recovery itself didn't work, just showed the HTC splash, turned black, then booted again normally, getting stuck at the cyanogen logo. Same thing for the 2.6.3.0 version, so I reflashed the original 2.1.1, at which point I can get into recovery but the phone is still stuck at the cyanogenmod during normal boot. At this point I installed the original cyanogenmod .zip from recovery and now at least the phone boots up normally. Still need to get stock back somehow.
Out of ideas and exhausted from this. Any help would be appreciated. Perhaps anyone has a working stock 4.0.3 rom for the Vivid, nandroid backup, etc., or any other ideas. Thanks for reading.
Oh crap...
OK... First... Stock rom can be found in development... Most of the roms there are stock... Read the OP... It'll tell you...
Second... You should use TWRP 2.5.3.0 or something like that I forget...
Third... When you tried the ruu... Did you relock your bootloader...
Side note... Could you get your phone to show up with 'fastboot devices'
I use TWRP 2.8.7.1(which was flashed to the phone) and now after flashing this nightly version, the recovery gets stuck on the TWRP screen and flashes every 60 seconds, but never lets me use it.
I've searched through all the forums, but can't find anyone else with this problem. I just want to flash CM12.1 Snapshot, but I can't without the recovery working.
Everytime I flash the same recovery(TWRP2.8.7.1), the bootloader gives me the error "Mismatched partition size". I've tried "Fastboot boot TWRP2.8.7.1.img, but it sits stuck on the loading TWRP screen. I've cleared the cache, but still nothing.
The only recovery that I can get to work is CWM by booting the .img from the bootloader, but that still does nothing because none of the directories will mount, so I cant flash from the recovery.
I'm waiting on motorola to send me the stock files and just reflash stock and start from scratch, but I really want to save my data.
Does anybody have any clue as to what I'm doing wrong before I reset to stock?
Try this one:
http://forum.xda-developers.com/showthread.php?p=61558425
If this recovery doesn't work, you may have to reflash the full stock rom
uluf said:
Try this one:
http://forum.xda-developers.com/showthread.php?p=61558425
If this recovery doesn't work, you may have to reflash the full stock rom
Click to expand...
Click to collapse
Nope.. didn't work. I had the 5.0 files from motorola that I flashed, and I'll update from there.
I really wish motorola would leave those files open to download instead of having to wait... sucks not having a phone, but I survived.
i have the same issue, any idea how to fix it ?