[Q] flash-all, wondering if everything ran okay - Nexus 5 Q&A, Help & Troubleshooting

Apologies if this sounds like a silly/obvious question to ask, though I'd just like some clarification.
I'm flashing back to Stock 4.4.2, and I'm wondering if everything ran correctly.
In the DOS window it says that it failed to open HHZ11K, and "M8974A, though just under it says that it is that version and 4.4.2 is KOT49H not HHZ11K, even though I downloaded KOT49H.
Within my phone it says the following:
Baseband M8974a-1.0.25.0.23
Build: KOT49H
Version: 4.4.2
-----
Also wondering in the process of installing a new custom ROM should I:
- old rom
- wipe everything (data/system/cache/etc)
- reinstall stock 4.4.2
- install new custom rom
or
- old rom
- wipe everything (data/system/cache/etc)
- install new custom rom

HHZ11K is the bootloader version. Boot to bootloader and have a look
Sent from my Nexus 5 using Tapatalk

To install a custom rom.. Wipe everything and then flash the custom rom zip following with the gapps zip...
-Flowed from an IceCold Hammerhead!

Related

[Q] Do you need ROM Manager to flash ICS 4.0.3?

Hey this is my first time posting - I have a rooted Rogers Samsung Captivate i897 that I upgraded to Gingerbread 2.3.4 in November (with an AT&T based ROM). I am trying to upgrade the firmware to the new ICS 4.0.3 that is now available for this model as I am looking for something new.
So, I did some research and followed the directions that were posted (got ROM Manager, downloaded nightly .zip files & GApps). I then tried to back up my ROM using ROM manager (didn't work but thats OK I have the ROM file on my PC). And did the factory restore/cache wipe and tried to flash the .zip files from my SD and it didn't work.
Here is what it says when I try to flash:
"E: failed to verify whole-file signature"
"E: signature verification failed"
Question 1) What could be causing this error?
Question 2) Should I try to flash a stock ROM first before attempting to flash ICS?
Question 3) do I really need to use ROM Manager?? Is there another method available (flashing from PC from Odin)?
I am hesitant about doing this on the fly because when I updated to Gingerbread in November I had a good scare with my phone - soft bricked it, fixed that, and then got it stuck in a boot loop, then had issues with boot logo conflict between Rogers a AT&T. I was out of a phone for about a day working madly to fix it. I would like to avoid it again at all cost.
Phone Information:
Firmware Version: 2.3.4
Baseband Version: I897UCKH3
Kernel Version: 2.6.35.7-I897UCKH3-CL461307
Build Number: GINGERBREAD.UCKH3
Please help I appreciate it!!

[Q] Troubleshooting while updating to 4.4.4

Hi all,
Since a few days I'm trying to update my Nexus 5 to Android 4.4.4 but everything I've tryed has failed !
Today I'm running stock ROM 4.4.2 + root + TWRP recovery + Xposed
What I've tryed :
_ OTA : device reboot on recovery and does nothing
_ Flash stock using the latest Nexus Rom Toolkit from Wug Refresh : device reboot on bootloader and get stuck on a "downloading..." message while PC get stuck on "downloading bootloader"
_ Flash zip from TWRP : tryed several zip, all of them has failed
I don't know what to do next, so now I'm asking your help...
Also I hope this post is in the right section !
Download vomer's stock rooted 4.4.4 rom from the development section and dirty flash it from custom recovery. This should do the job.
You can find the mentioned rooted stock in my signature, section 6.6
Sent from my Nexus 5 using Tapatalk
Before trying this custom ROM could you explain me the difference with the stock ROM and why I cannot flash the stock one ?
Is it because I have Xposed or something ?
And also after flashing the custom by vomer, can I try to flash again the stock one ?
3RR0R404 said:
Before trying this custom ROM could you explain me the difference with the stock ROM and why I cannot flash the stock one ?
Is it because I have Xposed or something ?
And also after flashing the custom by vomer, can I try to flash again the stock one ?
Click to expand...
Click to collapse
The One which we are telling you to flash is the stock rom. Yes, it's because you have Xposed and other modules installed.. God knows what changes it has made to system.
There's no need to flash the factory images again as vomer's thread contains the stock itself.
- Sent from an IceCold Hammerhead!
3RR0R404 said:
Before trying this custom ROM could you explain me the difference with the stock ROM and why I cannot flash the stock one ?
Is it because I have Xposed or something ?
And also after flashing the custom by vomer, can I try to flash again the stock one ?
Click to expand...
Click to collapse
All of your questions have already been answered, except the Vomer ROM one. While technically a custom ROM, it is only stock ROM with root. So going back to pure stock would be pointless.
Edit: ninja by @vin4yak

[Q] 38r stock kernel

Does anyone have a copy of the stock kernel for 38r. I've run into issues trying to use Franco kernel updater and using the backup copy of the kernel made in that app. Just want a clean version of the newest stock kernel. Thanks in advance.
https://www.androidfilehost.com/?fid=95747613655042881
Thank you
Well, it seems to be 33R (it's what it says while flashing in recovery).
But it as the same version as show in this thread : [ ROM ][ Oct 7 ] Stock Rooted 4.4.4 XNPH38R
Weird.

Successfully dirty flashed from Stock 5.0.1 > Stock 5.1 > Cataclysm Mar 12 + updates

Successfully dirty flashed from Stock 5.0.1 > Stock 5.1 > Cataclysm Mar 12 + updates
Hi,
for anyone that's actually running a Lollipop stock firmware and is willing to switch to this excellent ROM, I inform you that you can install it over a 5.1 Stock firmware without wiping or losing your data.
Until a week ago, my Nexus 5 was on 5.0.1 stock, so I first upgraded it to 5.1 using the LMY47D factory image
https://dl.google.com/dl/android/aosp/hammerhead-lmy47d-factory-6c1ad81e.tgz
I followed the usual fastboot procedure, just modified the flash-all script to remove the -w switch, so that it would not wipe the Nexus data/cache partitions but still upgrade system, bootloader and radio.
Since factory images also reinstall the stock recovery, I reflashed the latest TWRP and used it to flash the Cataclysm Mar-12 Beta, then the latest Cataclysm update (Cataclysm-Beta_Update_Mar_16.zip as of this writing); you can also flash your preferred kernel (I use ElementalX 2.11) and wipe cache (just to be sure) then reboot.
I only experienced a minor issue with the QuickToggles/Notifications pulldown, but easily fixed it following this procedure from the Cataclysm FAQ section:
My home/back button, notification pulldown isn't working after a dirty flash
- Open a terminal emulator on the phone and digit:
- su (enter)
- am start -n com.google.android.setupwizard/.SetupWizardTestActivity (enter)
- follow the instructions and possibly reboot after
Click to expand...
Click to collapse
(don't worry, despite what it says, the setup wizard will not initialize or restore your phone from backup, I guess we must force-launch it to reset some cache file).
That's all: now I have the latest Cataclysm ROM with all my apps and their settings but didn't have to reinstall or restore from backup ... I'm pretty sure we can do this with Cataclysm (and not with other ROMs like CM or Paranoid) because it's basically a stock firmware plus the atl4antis additions.

Phone very "laggy" with stang5litre rom

I just flashed my wife's Galaxy S4 (SCH-I545 ) with stang5litre's Lollipop rom (see: http://forum.xda-developers.com/galaxy-s4-verizon/development/stang5litre-ediition-5-0-t3132555).
I have the NK4 bootloader with Safestrap installed. The previously installed stock OS was 4.4.2. I installed Stang5litre's rom over the exising ROM using SS (in other words, I DID NOT use a new ROM slot).
The method I used was (from the ROM's announcement page):
If coming from any Rom Before OC1 Ex 4.4.2 or Below
1. Boot into SS
2. Flash stang5litre 5.0 Edition v2NON-MDK Rom.zip
3. Flash OC1_firmware.zip
4. Flash SuperSU v2.49 Beta
5. Flash OC1 SS/FF Flashable kernel.zip
6. Reboot system.​
Everything seems to be working okay, but the apps take 10+ seconds to open. Once open they seem to run normally.
Any suggestions?
Also, the instructions included nothing about wiping the phone before flashing, so I did not do it.
Should I have?
Would this ROM/method still work if I did a wipe to factory settings before installing?​Thanks.
You apply al wipes? Data,system,caché, dalvik cache?

Categories

Resources