Android 4.4
Here's the system dump from the Sony Z Ultra GPE. All credits goes to @sfagundes (speak up if you or someone else are missing)
DO NOT ATTEMPT TO FLASH. THIS IS FOR DEVS ONLY.
- Download (Mega)
- Download (Dev-Host)
Android 4.4.2
Many thanks to @graffixnyc for the pre-rooted 4.4.2 dump! Use at your own risk.
- Download (Dev-Host)
Oooo I think I made a flashable zip of /system ... This night I will play.
Sent from my Xperia Z Ultra using Tapatalk 4
Reb0rn said:
Oooo I think I made a flashable zip of /system ... This night I will play.
Sent from my Xperia Z Ultra using Tapatalk 4
Click to expand...
Click to collapse
Aww man, it's on! :laugh: Just be careful and don't brick it though (not that it'll happen). Keep us posted!
Reb0rn said:
Oooo I think I made a flashable zip of /system ... This night I will play.
Sent from my Xperia Z Ultra using Tapatalk 4
Click to expand...
Click to collapse
Post a link or pm lol
Sent from my Xperia Z Ultra using Tapatalk 4
LordManhattan said:
Here's the system dump from the Sony Z Ultra GPE. All credits goes to @sfagundes and @Bin4ry (speak up if you or someone else are missing)
DO NOT ATTEMPT TO FLASH. THIS IS FOR DEVS ONLY.
- Download (Mega)
- Download (Dev-Host)
To the mods: Please move if this is posted in the wrong section, or remove it entirely if it breaks any rules.
Click to expand...
Click to collapse
Will it not work out of the box since it is the same hardware of the c6802?
PaceyPimps said:
Will it not work out of the box since it is the same hardware of the c6802?
Click to expand...
Click to collapse
No, this is only for devs so they can use it in their own ROMs, or if they want to use this on its own. It is not possible to flash this as it is right now, so you'll have to wait
PaceyPimps said:
Will it not work out of the box since it is the same hardware of the c6802?
Click to expand...
Click to collapse
It's the system folder. So you'd need to create a series of instructions on where everything goes, permissions, root, and recovery reflashed... (i.e. flashable zip)
48 hours and I bet someone will have it working. I'm not able to at the moment. I think most of you know why..
Would it work to flash the system.img thru fastboot? (And boot.img if necessary)
On the Galaxy S4, we flashed the GE rom, but had to use a touchwiz kernel. Not sure how it would work on the Ultra..
lmemma16 said:
Would it work to flash the system.img thru fastboot? (And boot.img if necessary)
On the Galaxy S4, we flashed the GE rom, but had to use a touchwiz kernel. Not sure how it would work on the Ultra..
Click to expand...
Click to collapse
Inside a system.img will usually be 3 different compressed files. (depending on the phone)
Only one of these files will contain all the folders that we are usually familiar with:
app
bin
etc
fonts
lib
media
...
Its best to wait and see what Sony have done with the GPe devices. Probably nothing has changed, and partition info will be the same... but there could be a couple of changes that may brick your device. It's very unlikely, however I'd recommend not flashing the system.img without know exactly whats in there.
hamdogg said:
Inside a system.img will usually be 3 different compressed files. (depending on the phone)
Only one of these files will contain all the folders that we are usually familiar with:
app
bin
etc
fonts
lib
media
...
Its best to wait and see what Sony have done with the GPe devices. Probably nothing has changed, and partition info will be the same... but there could be a couple of changes that may brick your device. It's very unlikely, however I'd recommend not flashing the system.img without know exactly whats in there.
Click to expand...
Click to collapse
If no one tries anything nothing will be gained
Now then. I got the GPe to boot on my Xperia. Too see what works and what not
edit: Well its buggy... and i think it has to do with me using krabappel's 4.4 kernel. Not sure how much i dare goof around with this Playing away...
Reb0rn said:
If no one tries anything nothing will be gained
Now then. I got the GPe to boot on my Xperia. Too see what works and what not
edit: Well its buggy... and i think it has to do with me using krabappel's 4.4 kernel. Not sure how much i dare goof around with this Playing away...
Click to expand...
Click to collapse
LOL...
I don't mean not to try and make a ROM based on this system image, but the files need to be extracted and then a ROM created...
EDIT: Try a normal kernel. (sony) Its not CM based.
hamdogg said:
LOL...
I don't mean not to try and make a ROM based on this system image, but the files need to be extracted and then a ROM created...
EDIT: Try a normal kernel. (sony) Its not CM based.
Click to expand...
Click to collapse
well i got inside the system.img and there is the /system and i pushed it on to my device.
Trying a stock kernel but i highly doubt that will boot it at all
Edit: Stock Sony never gets past bootloader. no boot animation.
Getting a ZU. Will look into it
24hrs someone will get it running smoothe and make a full guide for all how to flash well done devs.
Reb0rn said:
well i got inside the system.img and there is the /system and i pushed it on to my device.
Trying a stock kernel but i highly doubt that will boot it at all
Edit: Stock Sony never gets past bootloader. no boot animation.
Click to expand...
Click to collapse
flash the boot.img from GPE files, dd it on the device from recoverymode
Regards
Bin4ry said:
flash the boot.img from GPE files, dd it on the device from recoverymode
Regards
Click to expand...
Click to collapse
Didn't work thru fastboot.
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 0.937s
Did it thru DD and it worked. Hello Google logo Will play a bit more.
dd if=/path/to/inputfil/boot.img of=/dev/block/blablablabla
fill in the placeholders yourself. Although i did not test yet if the dumped bootimage does work good. I just have no time since i have to finish my thesis now. But if you could do the dirty work would be cool
If something goes wrong just restore the boot with Flashtool in flashmode.
Regards
Bin4ry said:
dd if=/path/to/inputfil/boot.img of=/dev/block/blablablabla
fill in the placeholders yourself. Although i did not test yet if the dumped bootimage does work good. I just have no time since i have to finish my thesis now. But if you could do the dirty work would be cool
If something goes wrong just restore the boot with Flashtool in flashmode.
Regards
Click to expand...
Click to collapse
Incredibly frustrating this is.
I get the bootloader to start. I get the system to boot but it crashes. but its because i cant enter a reovery to delete user data. its always there.
How the hell can i delete data partition from fastboot or flashmode? as the stock gpe bootloader doesnt have a recovery.
EDIT: Ok i figured it out. Had to play with different kernels and thank god twrp has a terminal it doesnt boot im afraid.
I tried with
GPE kernel + gpe System = Bootloader load . Starts boot animation for 1 sec then crash.
revolution kernel + gpe system = bootloader load. Starts Boot animation 1 sec then crash.
Omnirom + gpe system + revolution kernel (dirty flash no wipes) = Bootloader loads. starts bootanimation. Boots. No mobile connection or wifi or anything. and buggy as hell
Now i need to play with the kids so l8ers.
Reb0rn said:
Incredibly frustrating this is.
I get the bootloader to start. I get the system to boot but it crashes. but its because i cant enter a reovery to delete user data. its always there.
How the hell can i delete data partition from fastboot or flashmode? as the stock gpe bootloader doesnt have a recovery.
Click to expand...
Click to collapse
Might just be a shot in the dark, but maybe you could install cwm or twrp by itself? Maybe from a different gpe device? If it is separated I.E. Not like sony's version it stands to reason you may be able to flash a recovery.
Or maybe flash a boot.img that has a recovery and boot it straight to recovery, factory reset, wipe caches, power off, and flash the correct boot.img after that?
Sent from my Xperia Z Ultra using XDA Premium 4 mobile app
pedal2themedal said:
Might just be a shot in the dark, but maybe you could install cwm or twrp by itself? Maybe from a different gpe device? If it is separated I.E. Not like sony's version it stands to reason you may be able to flash a recovery.
Or maybe flash a boot.img that has a recovery and boot it straight to recovery, factory reset, wipe caches, power off, and flash the correct boot.img after that?
Sent from my Xperia Z Ultra using XDA Premium 4 mobile app
Click to expand...
Click to collapse
well ive done that. the problem is that the gpe boot.img doesnt flash normal but must be pushed with a dd command.
Anyways. Just got a tip that it might need the userdata.img. so thats my next step. *sigh* thats the last thing i do now. Getting tired of this ;D
Related
Well, here goes nothing.... With a little effort, I've got this done...
1. A system partition nandroid of the Jelly Bean 10.4.2.15 update created using TWRP 2.2.2
2. A modified TWRP 2.2.2 recovery which works with the new bootloader
This system nandroid image has been created for developer use. So, it's not for everyone to play around with. It does not have the new bootloader or boot image, both of which are required to use this system image. It was created using my modified copy of the TWRP 2.2.2 recovery image.
The TWRP 2.2.2 recovery image below is a modified version of the original TWRP 2.2.2 recovery (credits TeamWin). I have merely replaced the kernel within the recovery image with the new JB kernel, thereby allowing it to work with the new bootloader. This is an un-blob'd recovery image. If you wish to directly flash this image, you need to have nvFlash enabled. Else you need to make a blob pack and flash it.
I've now added a zip with the de-odexed system apps and framework jar. This zip only has the /system/app & /system/framework folders. Just to make it easier if anyone wants to create an update zip.
I've also added blobpacked version of the new JB bootloader, kernel, stock recovery and my modified TWRP recovery. Be careful. If you don't know what your are doing and don't have nvFlash enabled, you could brick your device.
USE AT YOUR OWN RISK!!! THE NEW TF201 JB BOOTLOADER IS ESSENTIAL REQUIREMENT!!! BE CAREFUL OR YOUR COULD BRICK YOUR DEVICE
Let the modding begin!!!
tf201-jro03c-system.ext4.win (The system nandroid image)
twrp-2.2.2-jb.img (The un-blob'd modified TWRP recovery)
tf201-jro03c-deodex.zip (De-odexed system apps and framework jars only)
tf201-jb-bootloader.blob (Blobpack of the new JB bootloader)
tf201-jb-kernel.blob (Blobpack of the new JB kernel)
tf201-jb-stock-recovery.blob (Blobpack of the new JB stock recovery)
tf201-jb-twrp-recovery.blob (Blobpack of the my modified TWRP recovery)
I've use Wook's custom JB TWRP , Can I use this system NANDROID?
Thanks for posting.
Are you going to post the boot image?
Turge said:
Thanks for posting. Can you fix the link to the boot image? It's just pointing to d-h.st.
Click to expand...
Click to collapse
If anyone else needs this its at the link here, Craig was working hard and missed it
http://d-h.st/JMk
Thanks for putting this together Craig, you've done alot for us as of late, loved your CM10 builds
thank you for pulling this together, i look forward to what comes from this
ravenholm said:
I've use Wook's custom JB TWRP , Can I use this system NANDROID?
Click to expand...
Click to collapse
Wookie modified it so it would work for the TF300 JB base so my guess would be no.
Trying to get from HB 1.2 to stock JB with Nvflash bootloader as well...
---------- Post added at 05:52 PM ---------- Previous post was at 05:47 PM ----------
craigacgomez said:
Well, here goes nothing.... With a little effort, I've got this done...
1. A system partition nandroid of the Jelly Bean 10.4.2.15 update created using TWRP 2.2.2
2. A modified TWRP 2.2.2 recovery which works with the new bootloader
...
Click to expand...
Click to collapse
A little pointer here guys would be appreciated? Just where do I start with these files e.g. let's say from Stock ICS .28 to get to this one? e.g. copy files to device internal SDcard or use from PC? I see the one file is named .win? Not sure how to handle that?
Moe5508 said:
Trying to get from HB 1.2 to stock JB with Nvflash bootloader as well...
---------- Post added at 05:52 PM ---------- Previous post was at 05:47 PM ----------
A little pointer here guys would be appreciated? Just where do I start with these files e.g. let's say from Stock ICS .28 to get to this one? e.g. copy files to device internal SDcard or use from PC? I see the one file is named .win? Not sure how to handle that?
Click to expand...
Click to collapse
if you don't know what to do with these files, DO NOT DO ANYTHING WITH THEM.
I cannot stress this enough ATM. Yes, we know what to do with them, but until it is deemed safe, or until a better was of flashing is created, only very experienced users/devs should try this.
biggem001 said:
if you don't know what to do with these files, DO NOT DO ANYTHING WITH THEM.
I cannot stress this enough ATM. Yes, we know what to do with them, but until it is deemed safe, or until a better was of flashing is created, only very experienced users/devs should try this.
Click to expand...
Click to collapse
Em, boss, I hear you but we've probably not understood one another on the kind of clarity I'm looking for? What's the reference point for using this? (e.g. current ROM, operating system of PC etc etc)
For example am running a Linux machine at the moment and can easily run the following command to flash the recovery image using fastboot:
./fastboot-linux -i 0x0b05 flash recovery twrp-2.2.2-jb.img
or something to that effect and then would continue to reboot to recovery, copy the nandroid and restore from there?
Anyway, never mind...I take your advice and keep my fingers clear...
Moe5508 said:
Em, boss, I hear you but we've probably not understood one another on the kind of clarity I'm looking for? What's the reference point for using this? (e.g. current ROM, operating system of PC etc etc)
For example am running a Linux machine at the moment and can easily run the following command to flash the recovery image using fastboot:
./fastboot-linux -i 0x0b05 flash recovery twrp-2.2.2-jb.img
or something to that effect and then would continue to reboot to recovery, copy the nandroid and restore from there?
Anyway, never mind...I take your advice and keep my fingers clear...
Click to expand...
Click to collapse
The reference point is a cleanly wiped system. I'm creating a rom from this but you need the new bootloader and recovery. I had the androidroot bootloader installed, wiped system and factory reset. I flashed my JB stock rom and it did replace the bootloader and recovery with a modified TWRP from Craiggomez. The only issue I'm having is that wifi won't connect. I'll figure it out.
What I'm saying is that if you were to flash this image with the old bootloader and recovery, you'd have serious issues.
Ahhh, waiting a few more weeks/months wont hurt anyone ;p
jermaine151 said:
The reference point is a cleanly wiped system. I'm creating a rom from this but you need the new bootloader and recovery. I had the androidroot bootloader installed, wiped system and factory reset. I flashed my JB stock rom and it did replace the bootloader and recovery with a modified TWRP from Craiggomez. The only issue I'm having is that wifi won't connect. I'll figure it out.
What I'm saying is that if you were to flash this image with the old bootloader and recovery, you'd have serious issues.
Click to expand...
Click to collapse
Is it possible to take the bootloader from the its system dump file that's floating around? Or can twrp also backup downloader?
Sent from my HTC Sensation Z710e using xda premium
jermaine151 said:
The reference point is a cleanly wiped system. I'm creating a rom from this but you need the new bootloader and recovery. I had the androidroot bootloader installed, wiped system and factory reset. I flashed my JB stock rom and it did replace the bootloader and recovery with a modified TWRP from Craiggomez. The only issue I'm having is that wifi won't connect. I'll figure it out.
What I'm saying is that if you were to flash this image with the old bootloader and recovery, you'd have serious issues.
Click to expand...
Click to collapse
Yay, thanks for working on that! I am tempted to flash the jb stock image (from unpack) and do all the above, but still, I'd rather have a more reliable method step by step instruction set.
And yes, there is a new partition scheme. Flashing the image with old partition scheme intact will cause errors that could be fixed by nvflash.
Hawke84 said:
Is it possible to take the bootloader from the its system dump file that's floating around? Or can twrp also backup downloader?
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Yes, the bootloader is out but just give me a little time to fix wifi and you'll have a safe package to flash. I don't post threads here so you'll find it at rootz. I will post a link in this thread. That's assuming that someone else doesn't post a stock JB build for unlocked bootloaders before I do.
I've now added a zip with the de-odexed system apps and framework jar. This zip only has the /system/app & /system/framework folders. Just to make it easier if anyone wants to create an update zip.
Any I'm going to state this again... unless you have the new TF201 JB bootloader, do not attempt to use the recovery or nandroid image...
jermaine151 said:
Yes, the bootloader is out but just give me a little time to fix wifi and you'll have a safe package to flash. I don't post threads here so you'll find it at rootz. I will post a link in this thread. That's assuming that someone else doesn't post a stock JB build for unlocked bootloaders before I do.
Click to expand...
Click to collapse
Thanks, no rush mate
Sent from my HTC Sensation Z710e using xda premium
I think I understood this correctly but if I'm going to be able to flash this with an unlocked bootloader (I flash cm10 nightlies with cwm) Jermaine or whomever will be getting a pretty good chunk of my paycheck.... I use cm10 on a lot of my devices but it's not the best on the prime. I regret unlocking my bl but I know there's a way for official tfp jb.....
Regards,
Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
ManOnTheMoon said:
I think I understood this correctly but if I'm going to be able to flash this with an unlocked bootloader (I flash cm10 nightlies with cwm) Jermaine or whomever will be getting a pretty good chunk of my paycheck.... I use cm10 on a lot of my devices but it's not the best on the prime. I regret unlocking my bl but I know there's a way for official tfp jb.....
Regards,
Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
Click to expand...
Click to collapse
Yes, we will soon have an update zip for unlocked users... I have created an update zip, but haven't tested it yet... and jermaine has one in the works too...
I've also added blobpacked version of the new JB bootloader, kernel, stock recovery and my modified TWRP recovery. Be careful. If you don't know what your are doing and don't have nvFlash enabled, you could brick your device.
craigacgomez said:
Yes, we will soon have an update zip for unlocked users... I have created an update zip, but haven't tested it yet... and jermaine has one in the works too...
Click to expand...
Click to collapse
Let me know if u want me to test I have nvflash and some time this evening. I also half know what I'm doing
Sent from my HTC Sensation Z710e using xda premium
Get it while it's hot!
https://developers.google.com/android/nexus/images
EDIT: Seeing as how the bootloader has changed in this version(MANTAMD03), is it advisable to update officially via factory image or OTA?
When will the ota start coming out because I don't want to flash this as it will wipe all data
Sent from my Xperia Play (r800x)
abdel12345 said:
When will the ota start coming out because I don't want to flash this as it will wipe all data
Click to expand...
Click to collapse
Today.
abdel12345 said:
When will the ota start coming out because I don't want to flash this as it will wipe all data
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
You can also just flash the bootloader. I'm putting together a flashable zip for the system part as we speak.
CazeW said:
You can also just flash the bootloader. I'm putting together a flashable zip for the system part as we speak.
Click to expand...
Click to collapse
Where are you going to post that flashable zip at? Just want to know because I am wanting this asap to see if it helps with random reboots.
So If I flash OTA it will not wipe my data?
absolutnick said:
So If I flash OTA it will not wipe my data?
Click to expand...
Click to collapse
OTA's don't wipe data.
Do I flashed this with stock recovery ?
nightfox11 said:
Do I flashed this with stock recovery ?
Click to expand...
Click to collapse
These aren't the OTA. These are factory images. AFAIK what's posted in OP *will* wipe data.
Someone will eventually post a CWM flashable zip.
A full factory image will wipe everything but if I understand correctly, not touching the userdata.img will leave data intact. If you do that though, there's no point, in my opinion. I might flash a zip to try it out, then do the image down the road. I wipe/reinstall the OS on my computers at least once a year, and my Nexus is no different.
abdel12345 said:
When will the ota start coming out because I don't want to flash this as it will wipe all data
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
You can edit the flash-all script and just delete the 'fastboot erase userdata' line, if I am not mistaken.
Edit: you might need to remove the userdata.img file from within the image-mantaray-jw66v.zip file as well.
tublah said:
You can edit the flash-all script and just delete the 'fastboot erase userdata' line, if I am not mistaken.
Edit: you might need to remove the userdata.img file from within the image-mantaray-jw66v.zip file as well.
Click to expand...
Click to collapse
Anyone gotten it yet? Does it root the same way?
I'm getting less than 2 KB/s download so it will be a while .. geesh.
I've flashed 4.3. Doesn't seem a whole lot different to be honest, maybe a little snappier but it could just be placebo. Can't complain, it was fine before really! :good:
stiggy2012 said:
I've flashed 4.3. Doesn't seem a whole lot different to be honest, maybe a little snappier but it could just be placebo. Can't complain, it was fine before really! :good:
Click to expand...
Click to collapse
I'm just wanting the random reboots and RAM issues to be resolved.
If I just run the flash-all file, what exactly will that do?
edit: I just read the instructions. Will I still have access to TWRP?
I can't wait for a rooted flashable zip. Please let the surface flinger patch be in this.
Sent from my Nexus 10 using Tapatalk 2
If anyone needs a speedy mirror, here's a mega mirror I just uploaded: https://mega.co.nz/#!zcpGQQya!cdHuKjZcArUnURtsFLILdWnrry4_Bu0YB4_RjnzSyz4
Kernel version went from 3.4.5 to 3.4.39 -.-
I figured it out. I just removed the option to erase recovery in the .bat file, and removed the corresponding image in the zip. Yeah so far 4.3 feels smooth. Not much of a difference lol.
Anybody have a link for Flashable Zip yet?
Thanks @[NUT] for finding the way of rooting 4.3 with locked BL. Since nobody makes one for Z Ultra, I will do it.
This is a flashable ROM extracted from stock 14.2.A.0.290 without ANY modification.
The only 2 things added are FULL ROOT and XZDualRecovery.
This method is copied and modified from @[NUT] 's Z1 ROM
Requirements:
Flashtool 0.9.13 by @Androxyde
XZDualRecovery 2.7.71 BETA or newer.
Current rooted FW version: 14.1.B.1.532 OR 14.1.B.2.257 (rooted).
note: 257 is not tested on Z Ultra yet.
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
C6802: How to update to 14.2.A.0.290:
This should work for C6833, too. But you will lose 4G.
WARNING:
As the 'update' part of this ROM package does not work yet:
THIS GUIDE WILL DESTROY ALL USERDATA!
For C6802: Download C6802_14.2.A.0.290.jackie099.flashable.zip (C6833_14.2.A.0.290.jackie099.flashable.zip if u have C6803)and C6802_14.2.A.0.290_Stripped.ftf, save them somewhere you remember;
Put 'C6802_14.2.A.0.290.jackie099.flashable.zip' on (the external) SDcard1;
Put 'C6802_14.2.A.0.290_Stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
To prevent bootloops:
Flash XL39h-C6802_4.2.2-14.1.B.1.532.ftf firmware, please use the newest flashtool, or brick.
root it with Vroot, and install Supersu to replace vroot's permission manager.
Flash XZDualRecovery 2.7.71 (from PC)
In TWRP -> Wipe -> advanced Wipe Tick/Check:
Dalvik-Cache
System
Cache
Data
Internal Storage
Swipe to Right to do the factory reset
After that Click Format Data -> type yes
Flash 'C6802_14.2.A.0.290.jackie099.flashable.zip' or 'C6833_14.2.A.0.290.jackie099.flashable.zip' in TWRP
NOTE: do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6802_14.2.A.0.290_Stripped.ftf';
Now reboot to system.
Check Supersu, and u are rooted!
Hit Thanks or donate me if you think my work is useful for you!
Thank you for this! Much appreciated!
Just to let you know - both of your link (C6802_14.2.A.0.290_Stripped.ftf,) points to the wrong file.
I have been using NUT's 4.3 root guide for other Z-devices, but when trying with my Z Ultra it wouldn't work. I tried going from a rooted generic .532 to generic .290 created according to NUT's guide. I had success on Tablet Z and Z1 but not Z Ultra. I have a C6833.
alphaandomega said:
Thank you for this! Much appreciated!
Just to let you know - both of your link (C6802_14.2.A.0.290_Stripped.ftf,) points to the wrong file.
Click to expand...
Click to collapse
Thank You! It's fixed now.
dape16 said:
I have been using NUT's 4.3 root guide for other Z-devices, but when trying with my Z Ultra it wouldn't work. I tried going from a rooted generic .532 to generic .290 created according to NUT's guide. I had success on Tablet Z and Z1 but not Z Ultra. I have a C6833.
Click to expand...
Click to collapse
If u dont mind losing LTE, u can use this one. Maybe I can make one for 6833 later.
jackie099 said:
If u dont mind losing LTE, u can use this one. Maybe I can make one for 6833 later.
Click to expand...
Click to collapse
Thank you, but I unlocked my bootloader so I am okay now.
If I have time this weekend I can try to make the files for C6833 and share them here.
Good work, but can you remove vRoot from the post and use Kingo or Bin4ary's root tools as vRoot may be harvesting imei no's
jackie099 said:
If u dont mind losing LTE, u can use this one. Maybe I can make one for 6833 later.
Click to expand...
Click to collapse
Hi million thanks for your incredible work. I have a C6806 version.... Dyou know if the C6833 version will work for me if it is finally released?
I cannot be leave there is definitely a solution for our locked bootloader telephones
Many thanks nin advance
Thank you for this! Much appreciated!
jackie099 said:
If u dont mind losing LTE, u can use this one.
Maybe I can make one for 6833 later.
Click to expand...
Click to collapse
+1000!!!!
After looking at XZDualRecovery 2.7.71 I think this will work
DONT TRY THIS AT HOME KIDS
1/ flash either my BE Rom or DoggRom
2/ DON'T reboot yet, go to advanced/ power off (CWM) [or back to the main menu, then go to reboot->power off (TWRP)]
3/ start flash tool / select Flash / Flashmode
4/ select .290 ftf
5/ deselect wipes (done on install or Rom), exclude everything but kernel and then flash
6/ Reboot
7/ run XZDualRecovery 2.7.71 from pc
Will this work @hamdogg, @jackie099 ???
blueether said:
After looking at XZDualRecovery 2.7.71 I think this will work
DONT TRY THIS AT HOME KIDS
1/ flash either my BE Rom or DoggRom
2/ DON'T reboot yet, go to advanced/ power off (CWM) [or back to the main menu, then go to reboot->power off (TWRP)]
3/ start flash tool / select Flash / Flashmode
4/ select .290 ftf
5/ deselect wipes (done on install or Rom), exclude everything but kernel and then flash
6/ Reboot
7/ run XZDualRecovery 2.7.71 from pc
Will this work @hamdogg, @jackie099 ???
Click to expand...
Click to collapse
Well... Deselecting kernel will keep recovery, deselecting wipes should keep data..
hamdogg said:
Well... Deselecting kernel will keep recovery, deselecting wipes should keep data..
Click to expand...
Click to collapse
maybe that should have read:
5/ deselect wipes (done on install of Rom) [Top Box]
5a/ exclude everything but kernel [Middle Box]
5c/ and then flash
at that stage it should boot on a locked bootloader with partial root access, then running XZDualRecovery would give full root and recoveries - It's my belief that our roms wont boot on a locked bootloader as is?
blueether said:
maybe that should have read:
5/ deselect wipes (done on install of Rom) [Top Box]
5a/ exclude everything but kernel [Middle Box]
5c/ and then flash
at that stage it should boot on a locked bootloader with partial root access, then running XZDualRecovery would give full root and recoveries - It's my belief that our roms wont boot on a locked bootloader as is?
Click to expand...
Click to collapse
No locked won't boot unless they flash stock kernel. Sounds about right. But I am on 9th Corona... :silly:
hamdogg said:
No locked won't boot unless they flash stock kernel. Sounds about right. But I am on 9th Corona... :silly:
Click to expand...
Click to collapse
Dont want to try as there is a large thunder storm above and I don't want to be in the middle of flashing something if the power goes out, and I'v had about 6h sleep in the last 3 days
:good: for work :good:
blueether said:
Dont want to try as there is a large thunder storm above and I don't want to be in the middle of flashing something if the power goes out, and I'v had about 6h sleep in the last 3 days
:good: for work :good:
Click to expand...
Click to collapse
Man i know how that feels. On holiday and yet people still go missing... Why can't they take a break!
hamdogg said:
Man i know how that feels. On holiday and yet people still go missing... Why can't they take a break!
Click to expand...
Click to collapse
Very OT, you lost another? - /me always has a PLB now when in the backcountry, work and play.
blueether said:
Very OT, you lost another? - /me always has a PLB now when in the backcountry, work and play.
Click to expand...
Click to collapse
Well yeah.... There's always someone missing.. Hard stastics: a little over 1500 each year, missing people never get found in New Zealand.
Messed up eh!!
Imagine the rest of the world...
What you doing now?
lemmon said:
Hi million thanks for your incredible work. I have a C6806 version.... Dyou know if the C6833 version will work for me if it is finally released?
I cannot be leave there is definitely a solution for our locked bootloader telephones
Many thanks nin advance
Click to expand...
Click to collapse
Sry, I rly dont know. I konw C6833 can flash C6802's ROM, and C6802 can flash C6833's ROM.
hamdogg said:
What you doing now?
Click to expand...
Click to collapse
testing the above... not working, no recoveries
re-locked BL
flashed kernel.sin etc
boots fine
run locked recovery, gets root, copies files etc - reboots but no recovery.
blueether said:
testing the above... not working, no recoveries
re-locked BL
flashed kernel.sin etc
boots fine
run locked recovery, gets root, copies files etc - reboots but no recovery.
Click to expand...
Click to collapse
flash this after flashing the rom to recovery
http://nut.xperia-files.com/downloa...kZHVhbHJlY292ZXJ5Mi43LjcxLUJFVEEuZmxhc2hhYmxl
Download
Mega
Installing
You can't flash this yet (I'm working on that, I promise) but you can boot from it!
NOTE: THIS IS A WIP. Not a lot has been really tested yet and this is posted merely for your enjoyment atm.
I don't suggest flashing anything yet, not that there is anything to flash heh.
Also, I take no responsibility if you break your watch, yada, yada.
To do this, make sure you have Android's tools (for fastboot), an unlocked bootloader, and the watch connected to your computer in Debug mode.
> adb reboot bootloader
<wait for the reboot to happen>
> fastboot boot /path/to/recovery.img
Click to expand...
Click to collapse
Enjoy!
Did u push the tree to github?
1st built for me was a no go
wouldn't twrp make more sense since its touch based?
D-FUSE said:
Did u push the tree to github?
1st built for me was a no go
Click to expand...
Click to collapse
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
ptesmoke said:
wouldn't twrp make more sense since its touch based?
Click to expand...
Click to collapse
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Smith7018 said:
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Click to expand...
Click to collapse
I wasn't trying to shoot you down just suggesting if it would be easier to iron out since its built to be touch based...that's all
ptesmoke said:
I wasn't trying to shoot you down just suggesting if it would be easier to iron out since its built to be touch based...that's all
Click to expand...
Click to collapse
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Smith7018 said:
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Click to expand...
Click to collapse
Interesting.
I was/am working on TWRP, but my first build wouldn't boot.
EDIT: Where did you get that strap? I really like it.
Smith7018 said:
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Click to expand...
Click to collapse
Thanks man. Got it to boot up and backup worked. Guess that's about all u can do for now
Sent from my Nexus 5 using XDA Premium 4 mobile app
dude1981 said:
Thanks man. Got it to boot up and backup worked. Guess that's about all u can do for now
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
jamcar said:
Interesting.
I was/am working on TWRP, but my first build wouldn't boot.
EDIT: Where did you get that strap? I really like it.
Click to expand...
Click to collapse
Same, and I gave up; TWRP's UI won't really work out too well at 280x280, IMO, and CWM swipe is already working heh. I got the watch strap from eBay. It was super cheap and easy to adjust!
Why just booting it via fastboot instead of flashing it?
and have you push your device tree to github??
Smith7018 said:
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Click to expand...
Click to collapse
just zipping your device tree and uploading it would work too.
And how you build a recovery and git look skeery?? lol
Smith7018 said:
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
Same, and I gave up; TWRP's UI won't really work out too well at 280x280, IMO, and CWM swipe is already working heh. I got the watch strap from eBay. It was super cheap and easy to adjust!
Click to expand...
Click to collapse
Good deal. Do u happen have any links to mods or did u create them yourself?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Smith7018 said:
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
Click to expand...
Click to collapse
This is exactly why I've rooted my watch! Well, that and the Gohma ROM.
The issue I'm having is pushing the .zip file to the sdcard. Getting an error saying it's read-only. Can't do it via adb because the second I boot into CWM my laptop forgets it's connected to anything.
PlayfulGod said:
Why just booting it via fastboot instead of flashing it?
and have you push your device tree to github??
Click to expand...
Click to collapse
It's only booting because it doesn't work when flashed to recovery. The file size is around 8 mb whereas the legitimate recovery is 23 mb, which I'm sure is an issue. Is it possible that I'm only creating a ramdisk that gets paired with the watch's kernel and I need to make an image with both of them? Sorry, this whole uBoot stuff confuses me a bit.
PlayfulGod said:
just zipping your device tree and uploading it would work too.
And how you build a recovery and git look skeery?? lol
Click to expand...
Click to collapse
Heh, I'm not actually afraid of git, I guess, I'm afraid of the whole "making a device-specific git repo that can be easily pulled while building CM." I guess I just don't have the time atm to set it up properly, but dw, I'll get to it this weekend! :fingers-crossed:
dude1981 said:
Good deal. Do u happen have any links to mods or did u create them yourself?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, the iOS mod is something I downloaded awhile ago for my N5. I'm afraid I don't have the link anymore. Sorry, man.
Pepski said:
This is exactly why I've rooted my watch! Well, that and the Gohma ROM.
The issue I'm having is pushing the .zip file to the sdcard. Getting an error saying it's read-only. Can't do it via adb because the second I boot into CWM my laptop forgets it's connected to anything.
Click to expand...
Click to collapse
Try pushing the zip to the sd card while it's normally booted and then restart. I think that's what I did, IIRC.
Smith7018 said:
Try pushing the zip to the sd card while it's normally booted and then restart. I think that's what I did, IIRC.
Click to expand...
Click to collapse
Getting:
Code:
C:\fastboot>adb push emoji.zip \sdcard
failed to copy 'emoji.zip' to '\sdcard': Read-only file system
This was just done while the watch is booted normally and plugged in via USB. It almost seems as though the root permission hasn't worked. I'm at a loss.
Pepski said:
Getting:
Code:
C:\fastboot>adb push emoji.zip \sdcard
failed to copy 'emoji.zip' to '\sdcard': Read-only file system
This was just done while the watch is booted normally and plugged in via USB. It almost seems as though the root permission hasn't worked. I'm at a loss.
Click to expand...
Click to collapse
Weird... I don't even think you need root to push to /sdcard/ but I could be wrong. I'd suggest trying /sdcard/emoji.zip so it knows where to resolve. Also, I don't use Windows, but does the backslash work on adb as a file separator?
what happened to development on this?
https://developers.google.com/android/nexus/images?hl=en
Wow nice !!!
Let's Rock!
Can't wait for pure nexus to update to N
Sent from my Nexus 6P using Tapatalk
YES!
Is it possible to flash the factory image using flashfire?
Im currently using this ROM (Stock+Nougat-NRD90M Debloated-Prerooted-Odex-Busybox-Fast & Stable).
Vegeta700 said:
Is it possible to flash the factory image using flashfire?
Im currently using this ROM (Stock+Nougat-NRD90M Debloated-Prerooted-Odex-Busybox-Fast & Stable).
Click to expand...
Click to collapse
I only flash via fastboot and when going between versions I'd personally want to do a fully clean flash. Mind you I reverted to MM after trying N for a couple days, but again, I'd never flash a full factory image via Flashfire.
Vegeta700 said:
Is it possible to flash the factory image using flashfire?
Im currently using this ROM (Stock+Nougat-NRD90M Debloated-Prerooted-Odex-Busybox-Fast & Stable).
Click to expand...
Click to collapse
Unless a lot of users have certified that flashing via dlash fire works, I would recommend a clean flash via fastboot. This way you are flashing the images the most direct way possible. Doing this will also reduce possible entry points for issues.
First person to find an .mbn file in the boot.img or bootloader.img gets SO much cred.
Oh my .. Time to flashing silently
Is there a list of apps that currently don't work (or do work) with 7.0? I'm trying to switch over but there's a couple core apps that I need to know will work fine.
kaslopis said:
Is there a list of apps that currently don't work (or do work) with 7.0? I'm trying to switch over but there's a couple core apps that I need to know will work fine.
Click to expand...
Click to collapse
There's a thread called "Android N: What doesnt work" here in general
david279 said:
There's a thread called "Android N: What doesnt work" here in general
Click to expand...
Click to collapse
Most of the apps on that list that I use did not have the stated issues... None of them did.. I'm not sure if that list is up to date.
You're welcome.
I just finished flashing back to 6.0.1 and getting everything set up.
Of course now it gets released...
E30Nova said:
You're welcome.
I just finished flashing back to 6.0.1 and getting everything set up.
Of course now it gets released...
Click to expand...
Click to collapse
You aren't alone. Went back a day ago myself.
Sent from my Nexus 6P using Tapatalk
From what I've seen, this version isn't all that superb. Being on 6 isn't so bad
I've honestly had zero issues with the factory image for N. I wiped everything and clean flashed the image flat. Once I restored all my apps (around 80), so far it seems very smooth. No issues with lag in either the system or the fingerprint scanner.
I keep getting an error about not being able to find systsem.img in its package.. In thought they fixed this in the flash all script in 5.0 for factory images?
Soured Lie said:
I keep getting an error about not being able to find systsem.img in its package.. In thought they fixed this in the flash all script in 5.0 for factory images?
Click to expand...
Click to collapse
Flash-all is still broken afaik, better flash the individual img`s in fastboot.
Hey y'all,
Sorry to bother here. I looked around but couldn't find anything. I'm running NRD90M on my phone. I install TWRP and I rooted my 6P + unlocked bootloader. However I just downloaded the full image on google NRD90U. I'd like to put back my phone to stock with this new image and be able to just keep it stock and receive OTA. Can someone help me out or giving me a link where there's a tutorial. I already downloaded Fastboot/ADB and installed my drivers.
PS: It's find if it wipes everything. I just want it clean.
Thanks!
StangATX