Related
I'm sorry if this is posted anywhere, but I spent a couple hours last night and another couple hours today searching here and in Google with no luck.
-Skip me for TL;DR-
I got a G1 when they first came out, and rooted it as soon as I could. I ran JF1.5 then JF1.6 then after a while upgraded to Cyanogen. It was great and my GF still uses it and loves it. I got a Nexus One about a month after they came out and I've been in love. I haven't went to Cyanogen since, only because the stock rom has been great and I haven't needed any extra features yet.
Now that 720p is available along with a few other things I'd like, I want to upgrade finally.
-TL;DR end-
Basically I'm trying to say I'm not an idiot or very new to loading roms and toying with an Android device.
From past experiences I basically know the process of root/recovery/rom etc.
I loaded froyo onto the phone when it was available via the stock recovery console and an update.zip ... no problems.
Yesterday, I unlocked the bootloader.
Installed Modaco's superboot.
And used fastboot to push recovery-RA-nexus-v1.7.0.1-cyan.img
After that I turned the phone on, and logged in to check it out and make sure I had root. Everything was running great (Froyo saves your app installs in the cloud!!!) and I did, in fact, have root. All seemed well.
-The Problem-
Now, I can't load any more update.zip files. Nothing at all. Stock rom, modded rom, rom updates, anything. When I try to install any update.zip I get the following output:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
At the top of the recovery screen it reads: Android system recovery <3e>
If that makes any difference....
NOTE: I can still use fastboot to push new recovery images, which I've tried.
System information below:
Fastboot/Bootloader Screen:
NEXUSONE PVT SHIP S-ON
HBOOT-0.33.0012
MICROP0b15
TOUCH PANEL-SYNT0103
RADIO-4.06.00.12_7
Dec 17 2009, 13:05:23
ABOUT PHONE
Model number: Nexus One
Android version: 2.2
Baseband version: 32.36.00.28U_4.06.00.12_7
Kernel version: 2.6.32.9-27220-g328f560 [email protected] #1
Build number FRF50
Thanks in advance for any help/info!!
Looks like you still have the stock recovery image... do you have backup & restore options iin recovery mode, if not, you still have the stock recovery, reflash Amon-RAs recovery...
No, I don't have backup or restore in the options, neither in recovery or fastboot.
This doesn't make much sense. Here's what I'm doing. It looks like it should be working fine:
Code:
C:\Users\Chris\Desktop\meh\android-sdk-windows\tools>fastboot devices
HT9CWP806497 fastboot
C:\Users\Chris\Desktop\meh\android-sdk-windows\tools>fastboot.exe flash recovery
recovery-RA-nexus-v1.7.0.1.img
sending 'recovery' (3948 KB)... OKAY [ 0.582s]
writing 'recovery'... OKAY [ 1.439s]
finished. total time: 2.021s
Edit:
I was thinking maybe I need a different radio image, but then I remembered reading that Froyo came with a new radio image (right?). And I couldn't install a new radio image anyway because the update.zip files won't load. I'm pretty stumped here....
Edit again:
The code above was what I just did to flash the new recovery, and I still don't have the options to backup and restore the data.
Another edit!: I also loaded Modaco's superboot again (successfully) and started the process over again with no luck.
You don't have a backup/restore option with AmonRa's 1.7.0? That means you don't actually have the custom recovery. Your fastboot is lying to you.
In the terminal app,type "reboot recovery". What happens?
And,try dropping the ".exe" from fastboot.
what they said. Sounds like you still have the stock recovery image. Try reflashing the recovery again.
I tried both the regular RA recovery and RA Cyanogen recovery using both commands, fastboot and fastboot.exe but I continue to get the same recovery image.
I know there's no way to relock the bootloader, but is there any way to reverse what Modaco's superboot did and try that again?
Go here. Scroll to the bottom of the first post. Looks at the screenshots. Does your recovery look like that?
Nope, it's the stock recovery image with the exclamation point and Andy in the background. 4 options: reply, update.zip, factory reset, and wipe cache
Flawd said:
Nope, it's the stock recovery image with the exclamation point and Andy in the background. 4 options: reply, update.zip, factory reset, and wipe cache
Click to expand...
Click to collapse
Try using amon ra recovery image stock for n1, not the cyanogen version.
This one:
http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-nexus-v1.7.0.1.img
and rename it to recovery.img or something short then try the fastboot flash recovery recovery.img
Flawd said:
Nope, it's the stock recovery image with the exclamation point and Andy in the background. 4 options: reply, update.zip, factory reset, and wipe cache
Click to expand...
Click to collapse
Confirm you have root. Go to the terminal app and type "su". What does it say?
Well root isn't necessary to flash a recovery. He just needs an unlocked bootloader.
Well, OP, you might as well just find a different computer and try it on that.
FaJu said:
Well root isn't necessary to flash a recovery. He just needs an unlocked bootloader.
Well, OP, you might as well just find a different computer and try it on that.
Click to expand...
Click to collapse
OP said he unlocked the bootloader.... so OP verify that when you TURN ON your Nexus One, the logo with the X there is a PADLOCK on the bottom of the screen. If it does, then your bootloader is unlocked and you need to install amon ra recovery.
If no padlock, you're not unlocked.
OP make life easy. Go to Market. Install ROM manager. Either install clockwork recovery, or scroll down. Select the option to flash another recovery. Flash. Done
Recently, I had saved on my HDD before PirateGhost pulled it, his ICS rom, So I followed the diretions to flash the boot.img before flashing thr rom, so it installed and such, and when it went back to the recovery menu it said installed failed, but the actual program that launched o install the stuff said it was ok..Ok lets fast forward I reboot the device and it starts booting up, and shows the boot animation, then it will freeze and of course bootloop, but me being smart I did a backup before I installed anything and it still bootloops, it doesn't even get to the bootanimation... So this is where I start worrying. So I looked and try to revert back to stock just to see if it will work, I can't even lock my bootloader because it says something about error too many links.>.< I need help and any help is most appreciative!
Did you let the PH39IMG.zip install 2 times? Or did you try to update to the newest H-Boot before you re-locked your bootloader? I saw the same error about too many links when I tried to update H-Boot before I locked the bootloader. When you go into the bootloader what version of H-boot does it show?
I have Hboot 1.83.0014, and after i installed the PH39IMG, I installed a new kernel and a new rom too see if it would work and it booted up and everything it was working, so I tried to restart the phone to restore a backup I had and now my recovery won't even boot up, I can still access bootloader and such
Riomaru said:
I have Hboot 1.83.0014, and after i installed the PH39IMG, I installed a new kernel and a new rom too see if it would work and it booted up and everything it was working, so I tried to restart the phone to restore a backup I had and now my recovery won't even boot up, I can still access bootloader and such
Click to expand...
Click to collapse
Read the instructions again. You have the wrong hboot
Sent from my HTC PH39100 using xda premium
Riomaru said:
I have Hboot 1.83.0014, and after i installed the PH39IMG, I installed a new kernel and a new rom too see if it would work and it booted up and everything it was working, so I tried to restart the phone to restore a backup I had and now my recovery won't even boot up, I can still access bootloader and such
Click to expand...
Click to collapse
That's the old H-Boot. That's why the ICS ROM doesn't flash correctly. You need to lock your bootloader and use the PH39IMG.zip to install the new H-Boot. Ignore the error you get on the command line when relocking. You should get into the bootloader and it should say relocked and have a security warning of some kind. Just let it run the PH39IMG.zip and update. It will run once and turn your phone off. Boot back into the bootloader and let it update again. When it's done you will have to flash recovery again, then the boot.img, and then boot to recovery and flash the ROM.
pside15 said:
Just let it run the PH39IMG.zip and update. It will run once and turn your phone off. Boot back into the bootloader and let it update again. When it's done you will have to flash recovery again, then the boot.img, and then boot to recovery and flash the ROM.
Click to expand...
Click to collapse
The step I bolded isn't necessary. If you wait long enough (30-45 seconds?), the phone powers back on and boots into bootloader on it's own and completes the install without any action required on your part.
anthromatt said:
The step I bolded isn't necessary. If you wait long enough (30-45 seconds?), the phone powers back on and boots into bootloader on it's own and completes the install without any action required on your part.
Click to expand...
Click to collapse
Thanks for the info. I wasn't aware of that. I just booted back to the bootloader manually and everything worked well.
pside15 said:
Thanks for the info. I wasn't aware of that. I just booted back to the bootloader manually and everything worked well.
Click to expand...
Click to collapse
Yeah, I discovered that by accident after about 4 failed attempts to successfully flash. The last time I "forgot" to pull the battery after the phone powered off because I had gone into the kitchen to get coffee. When I returned, it had rebooted itself and was finishing the update.
I couldn't flash the recovery while it was locked so I had to unlock it, but currently I am flashing the rom and I will see what happens
I had success by flashing the RUU first then flashing the new recovery, then finally the Rum Float zip file.
Riomaru said:
I couldn't flash the recovery while it was locked so I had to unlock it, but currently I am flashing the rom and I will see what happens
Click to expand...
Click to collapse
Yes, that is true but you didn't complete the H-Boot update. ICS ROMs won't flash properly on the old H-boot. You need to lock the bootloader to use the PH39IMG.zip to update H-Boot then unlock and flash recovery and then ROM.
pside15 said:
That's the old H-Boot. That's why the ICS ROM doesn't flash correctly. You need to lock your bootloader and use the PH39IMG.zip to install the new H-Boot. Ignore the error you get on the command line when relocking. You should get into the bootloader and it should say relocked and have a security warning of some kind. Just let it run the PH39IMG.zip and update. It will run once and turn your phone off. Boot back into the bootloader and let it update again. When it's done you will have to flash recovery again, then the boot.img, and then boot to recovery and flash the ROM.
Click to expand...
Click to collapse
Ok that did it !!!! Thank so much
Riomaru said:
Ok that did it !!!! Thank so much
Click to expand...
Click to collapse
No problem. Glad you got everything worked out.
I have a soft-bricked Raider and looks like I am having the same problem, I have hboot 1.83.0014 and unlocked. a getver all shows the version-main to be 1.65.666.3 so I google that up and found this ICS image...
OTA_HOLIDAY_ICS_35_S_BM_3.38.666.2-1.65.666.3_release_255932wpop8vtj8tts3ou3.zip
http://forum.xda-developers.com/showthread.php?t=1498003
So it appear I need to lock my bootloader and update the hboot.
When I run oem lock this is what I get.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Unknown error))
finished. total time: 0.022s
I let it sit for 15 minutes but no change.
what do I need to do to get my bootloader relocked?
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
hi all,
sorry to sound like a complete idiot in advance !
I have been trying for over a month now to find some way to return my phone to stock so I can get the new ota update but im just having no luck !
I have tried everything to unroot , relock boot loader, and return to stock, I can successfully unroot, successfully relock the boot loader but cannot update OTA everytime I download the ota and allow the phone to start update process the phone boots into bootlaoder and a new line appears in the normal messages **** security warning*** when this happens I loose recovery and the phone hasn't updated. I then have to re-unlock the bootloader to then flash a recovery.
I cant flash RUU as there isn't an RUU available for me, H3G_001 , I have tried the suggested CWM nandroid backup, but this fails half way through something to do with android_secure
I cant seem to get the phone to successfully grant s-off to try the change cid method, I have tried to do this using HTC one kit by hasoon but no luck,
if anyone could please help it would me much appreciated
regards
okz19
Probably you don't have the stock rom or the recovery, because the secure warning come out when you aren't fully stock..
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Justin2003 said:
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Click to expand...
Click to collapse
Is better link to XDA
still stuck!
hi all as you can probably tell form the age of this topic, I have been stuck for a while !!! (11 October ! )
I am still having problems trying to get the new update 2.24.771.3
my phone is carrier locked to three uk
it is unrooted
custom recovery cwm touch
bootloader unlocked / tampered
I understand I need stock recovery and to lock bootloader
I don't have stock rom
my problem is as follows, my phone has been telling me for atleast 4 months now that I have a software update, when I click it it restarts takes me to cwm recovery verifys install then gets stuck on cannot mount data ....
I understand I need to flash stock recovery, I have tried to do this using the "all in one kit" however when I click flash my own recovery, (phone reboots into bootloader) I then proceed to select the stock recovery.img the cmd box then hangs "waiting for device" I am then alerted by my computer that the usb device has malfunctioned. ( I am on windows 8 and have turned of signature verification)
I cannot use the supposed simple method of RUU as there isn't one available for my stupid network!!
I have tried to use a cwm recovery image, this usually starts then spits out android_secure is missing.
yes I do have a hammer ready to hit the phone with, but just before I do this is there ANYONE with any last tips to help me, because ive just about had enough with this stupid phone !
the phone has 24 hours left to live, can you save its life ?
thanks in advance for any help.
1. You cannot install an OTA with a custom recovery.
2. I've encountered a CWM bug having to do with .android_secure. There's a hidden folder in /sdcard that caused it, I don't remember whether this file is ".android_secure" or another. You can probably wipe the sdcard before restoring the backup. If that fails, you can probably manually restore the backup with ADB (this will be hard).
3. If you want to install the custom recovery, boot to the fastboot and use USB to install the recovery. Don't use a toolkit because they're useless when anything goes wrong.
I have an htc One running on the Reliance Network. Versions 4.1.2 / 1.29.651.10
It is Bootloader Unlocked with TWRP 2.6.0.1 and root
I have downloaded the mouthful OTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2-1.29.651.10_release_326731tcfazf1gnytc7g74.zipOTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2
-1.29.651.10_release_326731
When I try to flash it using TWRP it bombs out as there is no MD5 file.
I have two queries:
1. How do I update the TWRP to 2.6.3.0?
2. How do I install the update.
I prefer to use the fastboot method?
I have downloaded the update to my PC since aborting deletes the file. Also, I have the TWRP on my PC.
Please advise and help.
Check PM
sgiitk said:
I have an htc One running on the Reliance Network. Versions 4.1.2 / 1.29.651.10
It is Bootloader Unlocked with TWRP 2.6.0.1 and root
I have downloaded the mouthful OTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2-1.29.651.10_release_326731tcfazf1gnytc7g74.zipOTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2
-1.29.651.10_release_326731
When I try to flash it using TWRP it bombs out as there is no MD5 file.
I have two queries:
1. How do I update the TWRP to 2.6.3.0?
2. How do I install the update.
I prefer to use the fastboot method?
I have downloaded the update to my PC since aborting deletes the file. Also, I have the TWRP on my PC.
Please advise and help.
Click to expand...
Click to collapse
You cannot upgrade when your phone is rooted(i got to know from hetaldp)
I upgraded to JB 4.3, it awesome. Touch is Excellent. i too use relaince. there are no issues.
BUT remember you cannot root again, as over i am facing problems,,,
check : http://forum.xda-developers.com/showthread.php?t=2494594
So Please kindly wait, till the root for hTC ONE for upgraded JB 4.3 one Comes...
Are you using Sprint or T-Moile or Version HTC ONE?
To get upgrade installed, please un-root, relock, and then you can perform the update...
[email protected] said:
You cannot upgrade when your phone is rooted(i got to know from hetaldp)
I upgraded to JB 4.3, it awesome. Touch is Excellent. i too use relaince. there are no issues.
So Please kindly wait, till the root for hTC ONE for upgraded JB 4.3 one Comes...
Are you using Sprint or T-Moile or Version HTC ONE?
To get upgrade installed, please un-root, relock, and then you can perform the update...
Click to expand...
Click to collapse
It is Sprint, and from Hetal. Unrooting and relocking can be a pain, reloading everything. However, for almost two years I did not do any work on the Android side, so have forgotten everything.
I do not mind a locked phone it I can get to 4.3
Can you please pm me with the unrooting, relocking and the 4.3! Root for 4.3 is inevitable - just a matter of time.
Following the GooManager route I managed to get TWRP 2.6.3.0 installed, except the phone did not reboot. I did check it is 2.6.3.0.
Now the problem of the OTA remains. Maybe I will be forced to follow pm.mohanani's route of relocking. I cannot understand if I relock the bootloader then is not the unrooting automatic!
Also, Mr Mohanani GooManager requires root, so do not bother.
Managed to upgrade to 4.3 using Sprint_HTC_One_m7wls_3_04_651_2_RUU from Android Central as suggested by Hetal. I had to do a <fastbook oem lock> first. No problems except it wiped the data totally. Working fine. I have a few points / questions
1. Booting into Recovery is showing the Red Exclamation in a Triangle. Obviously not working, as in rooted!!
2. The Boot into recovery is showing both [RELOCKED] and S-off.
- Is this the cause?
- As per Hetal S-off means that I can root straight away irrespective of the Relocked status
- I guess OTA to KitKat (when it comes) is also a no go.
- What recovery is suggested TWRP 2.6.3, CWM (version?), or some other. This means that 4.4 will again be a full reload.
- Any fixes?
sgiitk said:
Managed to upgrade to 4.3 using Sprint_HTC_One_m7wls_3_04_651_2_RUU from Android Central as suggested by Hetal. I had to do a <fastbook oem lock> first. No problems except it wiped the data totally. Working fine. I have a few points / questions
1. Booting into Recovery is showing the Red Exclamation in a Triangle. Obviously not working, as in rooted!!
2. The Boot into recovery is showing both [RELOCKED] and S-off.
- Is this the cause?
- As per Hetal S-off means that I can root straight away irrespective of the Relocked status
- I guess OTA to KitKat (when it comes) is also a no go.
- What recovery is suggested TWRP 2.6.3, CWM (version?), or some other. This means that 4.4 will again be a full reload.
- Any fixes?
Click to expand...
Click to collapse
There is no need to accept the OTA if you are s-off
bigdaddy619 said:
There is no need to accept the OTA if you are s-off
Click to expand...
Click to collapse
Thanks. So I will again wait for the 4.4 RUU to be available on XDA or somewhere, and then install and forget OTA.
The point is recovery. I presume with S-off custom recovery must to be installed.
Do I install TWRP which takes care of root or do you suggest some other route, ie, root (how?) > recovery.
sgiitk said:
Thanks. So I will again wait for the 4.4 RUU to be available on XDA or somewhere, and then install and forget OTA.
The point is recovery. I presume with S-off custom recovery must to be installed.
Do I install TWRP which takes care of root or do you suggest some other route, ie, root (how?) > recovery.
Click to expand...
Click to collapse
Install TWRP 2.6.3.0
Option 1 flash SuperSU or another superuser file and run stock rooted
Option 2 flash a custom rom
Still stuck. I downloaded GooManager, and it will go into download > nowstarting and hang forever. I was advised to go the adb fastboot way, i.e.
download latestTWRP image filethen
adb reboot bootloader
then when I get
ui fstboot
fastboot flash recovery <twrp-recovery-name.img>
and its done.
I downloaded the .img file. Put everything into c:\recovery. Moved there under the command prompt. Plugged the phone into the computer, got both the drives (htc sync manager, and HTCONE) . So the connection was kosher.
Then gave adb reboot bootloader
The adb daemon started, but it found no device.
Obviously I being a noob in this game was missing something.
Also, I hear that the ROMs are available which to not reformat the storage. Are these the Deodexed versions or something.
Also, once in ten calls or so the screen goes totally blank at the end and is pain to restart the phone.
Checked up with http://forum.xda-developers.com/showthread.php?t=2497712
Seems that I am S-off but no rooted! Now what??
After a day or so and some cool thought I think I may have the problem identified. It is likely to be the lack of a root. I tried the following and the responses there from:
adb reboot bootloader
rebooted into bootloader Showing relocked and S-off. No fastboot option in the lower menu!
Now:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
I get
sending recovery <8600kB>...
Okay [ 1.140s]
writing 'recovery'...
FAILED <remote not allowed>
finished. total time 1.170s
Any ideas, and when may I expect root for 4.3. At the moment the phone appears to be working file, but no recovery!! HELP!!
Do I need to unlock again despite S-off. Also, then what is the bitstream I send it from 4.3 - the same as the old one!!
Yes you need to unlock your bootloader again to be able to flash twrp
I did as per the htc route - Do the unlock, reinstalled the OS, download the bitstream, etc, and then the OS reloaded. Still Goomanager could not get TWRP 2.6.3.0 so used the fastboot route and succeeded in downloading it to the phone. Thanks for encouraging me and putting me on the right track.
Now ho to root. Then I may as well get Titanium up!
You can get SuperSU or Superuser from the playstore or install a custom rom.
A very interesting experience. I could not enter bootloader [Down-vol + power was just restarting the phone], even adb devices was drawing a blank. So I decided to do a factory reset from phone. Lo and behold it dropped me into the TWRP screen. I managed to root, restarted to the main Downloaded su checker which completed the root. Confirmed. Then downloaded Titanium with Pro license (I have it) and did a recovery. Also, TWRP Manager (downloaded) is working and I am able to start into bootloader, etc.
When I try and look for upgrades with TWRP installer it says none. I know 2.6.3.0 has been upgraded to 2.6.3.2 Let sleeping dogs lie.
Also, I have not checked with adb devices but I am sure that too will now work.
Thanks, but what is going on. Is it only God and maybe Google know what happened?
Thanks for helping, and keeping me going.
I had more or less decided to revert to 4.1 and do an S-on <fastboot oem writesecureflag 3> and bootloader lock and look for OTA!
Added on 25th November
adb still not recognising the beast. adb devices gets a blank list. Phone is available under Windows so drivers etc are Ok.
A noob question. I saw
Stock Rooted 3.04.651.2 Odex & De-Odexed
Insecure Boot img. init.d support, data/app support
Stock Rooted 3.04.651.2 Odex
Stock Rooted 3.04.651.2 De-Odexed
on the upgrade thread. Now what do the terms Rootedm Odex and De-Odexed mean to the average user. Stock means the basic htc ROM I presume.
Also, rooted means what stages are covered.
afaik to upgrade you lock the bootloader, do the upgrade, and then in normal situations again unlock the bootloader, root and install a custom recovery (TWRP does the rooting - hopefully).
Do these ROMs take care of some or more of these stages?
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?