• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] ZV4 updated stock ROM

You can flash it via fastboot, you'll find it in the zv4 zip, the command would be fastboot flash boot boot.img, but no it didn't do anything for me because I already had the new boot.img from when I flashed it to create the ROM.
 
Is there any way a user that has successfully completed this -radio included- make a step by step guide, as if I'm 10 to help me through this. I have read through these posts and can't get a chronological idea of how to do this. I would seriously appreciate any help as I'm still new. We all start somewhere, thanks ya'll in advance. XD
 
I'm not happy.
Flashed the new radio and my reception is worse & WiFi is slower.
And if that wasn't enough I can't take video anymore; it pops up can't save videos during phone call even tho I'm not in a call.
 
Tigatron said:
I'm not happy.
Flashed the new radio and my reception is worse & WiFi is slower.
And if that wasn't enough I can't take video anymore; it pops up can't save videos during phone call even tho I'm not in a call.
Click to expand...

Weird, everything just got better for me. Did you update profile and prl? As for the video, that's come up before, isn't that the OK Google thing?

You could always go back to the old radio.
 
bg4m3r said:
Weird, everything just got better for me. Did you update profile and prl? As for the video, that's come up before, isn't that the OK Google thing?

You could always go back to the old radio.
Click to expand...
I did update profile & prl. No difference; also that doesn't explain the WiFi slowing down.
I had the OK Google on before the radio change and could do video thanks for the tip I'll see if that changes anything.
I havnt had a chance to get back on my computer to flash the old radio back yet.

Edit: just found that Ko Google was set to work from any screen (strange didn't know that existed) so I turned that off and sure enough I can record video again. Thanks.

Now I think I'll stay on this radio for another day or so and see if I'm just having a bad signal day or if this new radio just doesn't work well for me.
 
Yay! I helped! :p

I think the any screen thing might be new? I don't use it so I don't know. Just saw it come up a few times.

I haven't had any issues with the new radio, and I'm not sure how that would affect your Wi-Fi either way.

Did you check that it flashed the new kernel too?
 
Just flashed the updated kernel. As per my usual routine when flashing stuff, I wiped the cache and dalvik before booting out of cwm. Is it just me, or does it seem to take forever to wipe the cache through cwm?

Also, to answer someone's previous question, root is still intact as I did not reflash it after flashing boot.img.
 
bg4m3r said:
Just flashed the updated kernel. As per my usual routine when flashing stuff, I wiped the cache and dalvik before booting out of cwm. Is it just me, or does it seem to take forever to wipe the cache through cwm?

Also, to answer someone's previous question, root is still intact as I did not reflash it after flashing boot.img.
Click to expand...

I've noticed it is slow to clear cache as well. Most of the time anyways. Sometimes it goes fast.
 
Just wanted to share some benchmarks. I'll start working to get these improved.
 

Attachments

  • 2014-10-10-20-55-47.jpg
    2014-10-10-20-55-47.jpg
    285.1 KB · Views: 202
  • Screenshot_2014-10-13-22-56-20.jpg
    Screenshot_2014-10-13-22-56-20.jpg
    215.1 KB · Views: 149
getting error when trying to nuke laf partition.. this is the message i receive in fastboot

C:\Users\Anthony\Desktop\ADB Drivers_Updated (1)\ADB Drivers_Updated>adb shell
shell@x5:/ $ su
su
root@x5:/ # dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
/dev/block/platform/msm_sdcc.1/by-name/laf: write error: No space left on device

45057+0 records in
45056+0 records out
23068672 bytes transferred in 2.985 secs (7728198 bytes/sec)
1|root@x5:/ # dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
/dev/block/platform/msm_sdcc.1/by-name/laf: write error: No space left on device

45057+0 records in
45056+0 records out
23068672 bytes transferred in 2.762 secs (8352162 bytes/sec)
1|root@x5:/ #
 
somekid15 said:
getting error when trying to nuke laf partition.. this is the message i receive in fastboot

C:\Users\Anthony\Desktop\ADB Drivers_Updated (1)\ADB Drivers_Updated>adb shell
shell@x5:/ $ su
su
root@x5:/ # dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
/dev/block/platform/msm_sdcc.1/by-name/laf: write error: No space left on device

45057+0 records in
45056+0 records out
23068672 bytes transferred in 2.985 secs (7728198 bytes/sec)
1|root@x5:/ # dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
/dev/block/platform/msm_sdcc.1/by-name/laf: write error: No space left on device

45057+0 records in
45056+0 records out
23068672 bytes transferred in 2.762 secs (8352162 bytes/sec)
1|root@x5:/ #
Click to expand...

Your commands are messed up. Read the instructions again, and carefully. You didn't declare where to save laf.img. Also, are you trying to do that all on one command? They are two separate steps.
 
bg4m3r said:
Your commands are messed up. Read the instructions again, and carefully. You didn't declare where to save laf.img. Also, are you trying to do that all on one command? They are two separate steps.
Click to expand...

The commands are separate, its just how it was copied. And how do I declare where to save the laf.IMG file? The command works but it tells me there isn't enough space on my device.
 
somekid15 said:
The commands are separate, its just how it was copied. And how do I declare where to save the laf.IMG file? The command works but it tells me there isn't enough space on my device.
Click to expand...

Why not use Terminal Emulator instead of doing it through adb shell? Much simpler, and might be the cause of your problem.

Did it actually wipe your laf (try to boot into download mode, you should get fastboot instead)? If so, then it's too late to back it up. If not, then this should be your first line:
Code: 
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img
 
The terminal command indicated, is that done on a terminal emulator on a phone, or is it done on my windows PC using a command prompt (or is there an app)
 
Oh and another thing, would it maybe be better to wait for something like a towelroot to come out for Zv4 ? If that makes any sense that is, like where we don't have to e using DL mode and flash to the next rom or what not or is it maybe impossible
 
bg4m3r said:
Why not use Terminal Emulator instead of doing it through adb shell? Much simpler, and might be the cause of your problem.

Did it actually wipe your laf (try to boot into download mode, you should get fastboot instead)? If so, then it's too late to back it up. If not, then this should be your first line:
Code: 
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img
Click to expand...

I have my iaf backed up already and I have done it through terminal but I still get no space on device error. I'm going to do a factory reset later on and try again.
 
somekid15 said:
I have my iaf backed up already and I have done it through terminal but I still get no space on device error. I'm going to do a factory reset later on and try again.
Click to expand...
I looked at your messages again - it's normal to get "no space left on device" when zero'ing your LAF partition. You should be able to get into fastboot mode now.
 
You must log in or register to reply here.
Back
Top Bottom