[ROM][Factory Image] 4.3 - Rooted - BusyBox

Search This thread

hlaalu

Senior Member
Nov 24, 2007
421
58
Has anyone found an extended power menu that works with this?

Sent from my Nexus 10 using Tapatalk 2
 

Urbanrootz

Senior Member
Sep 17, 2010
560
174
Deep Sleep Issue!!!!!!!

Loving JB 4.3...very snappy, no lag whatsoever, and the Bluetooth improvements, no more skipping when streaming via BT. I do have 1 ROM issue, and I think this might be a Jelly Bean issue, but correct me if I'm wrong - I notice when the N10 goes to sleep, its deep sleeping to where I have to soft-boot the device to get it back on! Has anyone else experienced this, and is this a fix for it? I'm dreading a factory reset, but might be the next option!

Cheers-

Rootz
 

Urbanrootz

Senior Member
Sep 17, 2010
560
174
What number of this img? I'm looking for jwr66Y

This Image version is JWR66V!

---------- Post added at 04:47 PM ---------- Previous post was at 04:45 PM ----------

Loving JB 4.3...very snappy, no lag whatsoever, and the Bluetooth improvements, no more skipping when streaming via BT. I do have 1 ROM issue, and I think this might be a Jelly Bean issue, but correct me if I'm wrong - I notice when the N10 goes to sleep, its deep sleeping to where I have to soft-boot the device to get it back on! Has anyone else experienced this, and is this a fix for it? I'm dreading a factory reset, but might be the next option!

Cheers-

Rootz

Update: So I had to perform factory reset, which surprisingly fix the Issue with deep sleeping.


Cheers...
 

SilentSummer

Senior Member
Jun 12, 2010
843
111
Installed this update on the wife's N10 and it still tells me there is a system update. Anyone else seeing this?
Confirmed in System Settings that its on 4.3.
 

Urbanrootz

Senior Member
Sep 17, 2010
560
174
Installed this update on the wife's N10 and it still tells me there is a system update. Anyone else seeing this?
Confirmed in System Settings that its on 4.3.


Yes you will, because they was another update after this one! This is version JWR66V, the latest version is JWR66Y which adds some security patches, nothing major.
 

chilimac02

Senior Member
Mar 30, 2007
85
1
Texas
www.otecology.com
:good: I'm sure they is.....might have to do search for it....I personally haven't seen anything yet....but I'm sure they is options out there.....

I am more qualified to jack with my Galaxy Skyrocket, so bear with me... I've tried installing your ROM, then letting it update to the newest ROM. It keeps saying "error 7"... What the heck does that mean?

Can I use this rom and let it update itself to the newest release (I know its minor)?

If not, can you point me to a thread that takes me back to stock? bootloader and all?
 

Urbanrootz

Senior Member
Sep 17, 2010
560
174
I am more qualified to jack with my Galaxy Skyrocket, so bear with me... I've tried installing your ROM, then letting it update to the newest ROM. It keeps saying "error 7"... What the heck does that mean?

Can I use this rom and let it update itself to the newest release (I know its minor)?

If not, can you point me to a thread that takes me back to stock? bootloader and all?

:eek: Cheers mate, but this not my ROM, I didn't post it,but i did install it on my Nexus10. From my knowledge, error 7 means a mismatch with update while doing a system check, this tends to happen with rooted devices. I would suggest just flashing stock images from Google, then re-root your device.

Here's a few links hope they help!

http://www.droid-life.com/2013/07/25/android-4-3-update/
 

zoomy942

Senior Member
Jun 5, 2007
1,590
116
Mine always fails with a build prop error in clock work recovery. This is frustrating. And there any flash able Y builds? I'll just dirty flash in top of this version. Ugh!

Sent from my Galaxy Nexus using Tapatalk
 

Urbanrootz

Senior Member
Sep 17, 2010
560
174
Mine always fails with a build prop error in clock work recovery. This is frustrating. And there any flash able Y builds? I'll just dirty flash in top of this version. Ugh!

Sent from my Galaxy Nexus using Tapatalk


Clock work mod? Have you tried :good: TWR(Team Win Recovery) Instead, It's much more stable than CWM....in my opinion.....less problems.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 65
    This is the factory image from Google made into a flashable zip with CWM or TWRP.
    Clear cache/dalvik cache but no need to clear your user data.
    Warning: CWM users have reported that the "Disable Recovery Flash" option is breaking root. Be advised to choose "No." I do not have CWM so I cannot confirm but there is no reason to disable the recovery flash because no recovery is included in the zips.

    If flashing from CM10.1 or some other custom roms, you may need to clear the Clock app's data.

    Downloads:

    Android 4.3 odexed, rooted, BusyBox, and insecure boot:
    Mirror 1: http://tinyw.in/lnoM
    MD5: a54ae08a9c2cbedb58577a01cc05c65d

    Deodexed version:
    Mirror 1: http://tinyw.in/EI3t
    MD5: 5172bd4b25c13076b7d8310dde4ac43b

    New bootloader(should not be necessary):
    Mirror 1: http://tinyw.in/rspG
    Mirror 2: http://d-h.st/VYv
    MD5: 9324a66fbe97f7aabfcfa9a0059f3f1a
    Flash bootloader with: "fastboot flash bootloader bootloader-manta-mantamd03.img"

    Changelog:

    07/24/13: Initial version
    07/26/13: Updated zips with SuperSU 1.43 that fixes a CPU usage bug
    8
    Hi,

    Another question: "insecure boot" is the same as "unlocked bootloader"?

    Thanks :)

    Insecure boot and unlocked bootloader do not refer to the same thing.

    Insecure boot refers to the fact that a elevated permission root shell and root access is available by default for example for an insecure boot image when you start adb shell you will automatically see a root shell prompt of (You will also have acess to the ADB re-mount command which re-mounts the system r/w):

    Code:
    #

    Where as on a secure boot image when you start adb shell you will automatically see a regular shell (And you will not have acess to the ADB re-mount command):

    Code:
    $

    On a secure boot image you gain root access by rooting the device (Installing the su binary and some form of a Superuser app) and then you can obtain a root shell by either typing the following in either terminal or adb shell:

    Code:
    $ su

    Which results in the familiar elevated privilege root shell:

    Code:
    #

    An unlocked bootloader refers to the fact that you can modify any partition on the device without having to flash an officially signed firmware image. Let me know if you still have questions hopefully this clears things up for you :).
    6
    i stil cant restore titanium backups

    In TiBu change the location of your backup directory->
    menu/go to preferences/backup settings/backup folder location
    its going to say /storage/emulated/0/TitaniumBackup
    hit back arrow at bottom until it reads just /storage/emulated
    select legacy/TitaniumBackup
    4
    Deodexed version up.


    I am now on Jaybobs Paranoid Android and want to flash. Should I wipe completely(or system and caches) then fastboot new bootloader prior to the new rom itself?

    You should be able to install without any wipe. Some people like to clear the cache and dalvik cache but even that shouldn't be necessary.

    If you get an app or two that force closes after boot then you will just need to clear that app's data in Settings->Apps
    3
    I had the same. After some times it begins top lag. Wiped full a lot of times. For me it runs not so smooth as SaberMod. The lag came from termal throttling or from surfacelinger leak. Dont know.

    @dalingrin

    Missunderstand i something? 3.4.5{0?) is higher as 3.4.39. I thought it is .50 not .05 at the end of the kernel. When the 2nd is right, i was wrong.:eek:

    The kernel version is not a decimal number. The latest stable kernel is 3.10 which is newer/greater than kernel 3.9.

    Hi,
    thnx 4 ur effort, 4.3 seems better and snappier than 4.2.2 but I have an issue that every 2-3 hrs of use it becomes laggy and unresponsive till I shut down and restart it becomes perfect again this happened twice the 1st day after I flashed this ROM via twrp -and root is ok- ( dirty flash on buttered-manta AOKP )....is it a common bug or I should factory reset, what do u suggest?

    It could potentially be the SuperSU bug with 4.3 that causes 100% CPU usage.
    The bug should be fixed now with the new SuperSU from here: http://download.chainfire.eu/342/SuperSU/UPDATE-SuperSU-v1.43.zip

    I am uploading new zips for the OP now.