Related
Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
Maybe before you even answer, I'm sure I'll find a link on here to show me how?
One issue I have though, is that when I manually updated to 4.2.1 on my Nexus 7, I still got an OTA update a few days later, that actually ran.
I don't ever plan on flashing roms to any of my devices. Do I need to keep a custom recovery on my Nexus 4 or 7? If not, how to I revert back to the stock recovery?
If you saved the offical stock 4.2.1 images, to revert back to stock recovery, just use the 'fastboot flash recovery recovery.**************.img' command. If you haven't, you might have to flash the whole 4.2.2 rom which you can find on the google dev website. After this, if you only want to root then you don't need to flash a custom recovery, just use the 'boot' command instead of the 'flash' one.
MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
I flashed the OTA sideload file through TWRP and it installed succesfully.
jvbferrer said:
I flashed the OTA sideload file through TWRP and it installed succesfully.
Click to expand...
Click to collapse
How did you do that? Did you sideload wrinkle's file from this thread: http://forum.xda-developers.com/showthread.php?t=2145848?
I should let you know, that while I'm not afraid to install via the custom recovery, it doesn't mean I've done it via commands. I've always used toolkits, or one click methods of rooting and installing custom recoveries.
Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.
wvcadle said:
Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.
Click to expand...
Click to collapse
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?
MacHackz said:
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?
Click to expand...
Click to collapse
Yes, stock rom, rooted and unlocked. I did install Beats today. Could this be the problem? If so, I found a revert zip that I'm assuming is supposed to revert me back to stock audio codecs.
I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.
MacHackz said:
I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.
Click to expand...
Click to collapse
Flashing the revert zip failed. I'm starting to think that flashing anything with TWRP will fail.
How about this. I made a backup of all system data + apps with Titanium earlier today. Could I just reset my phone back to factory defaults, restore my apps + some system data, then re-root (*without a custom recovery*) and wait for the update again? Or will it come again?
Also, I've used Wugfresh's Nexus Toolkit. I don't remember checking the custom recovery button, but ended up with TWRP anyway. What's the easiest way to root without installing a custom recovery?
You could try that, and the update will come straiht away. You can root without flashing a custom recovery, just use the 'boot recovery' instead of 'flash recovery'
MacHackz said:
flash cwm and see if there's any difference
Click to expand...
Click to collapse
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?
wvcadle said:
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?
Click to expand...
Click to collapse
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot
MacHackz said:
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot
Click to expand...
Click to collapse
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.
wvcadle said:
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.
Click to expand...
Click to collapse
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440
MacHackz said:
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440
Click to expand...
Click to collapse
Where in that thread does it show me how to flash the stock recovery back onto my device?
wvcadle said:
Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?
Click to expand...
Click to collapse
The same thing happened to me. I was rooted running stock ROM with TWRP recovery (used wugfresh toolkit). The problem was I forgot I was using a modified kernel (for color correction) by molesarecoming. I flashed the stock kernel back, downloaded and flashed the OTA file from the help desk thread (http://forum.xda-developers.com/showthread.php?t=2145848&highlight=beats), and it worked. Oh, and I flashed the Superuser file immediately after the OTA did it's thing (while still in TWRP) to regain root. I didn't really like how after the initial failed install of the OTA, it took my into TWRP with no error message showing or anything.
I don't think TWRP is your problem -- I think beats is your problem. It may have modified something. Try searching the above-linked thread for answers. Honestly, there's no rush to get 4.2.2, so take your time finding the answer. It's better than wiping the phone just to install a small android update and having to redo everything on your phone again.
Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.
wvcadle said:
Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.
Click to expand...
Click to collapse
I need some help here - I have nexus 7 with 3G and Google (takju) with 4.2.1 installed.
I had it 'rooted" and installed TWRP .
AT the time I followed instructions to chand extension of some file to .bak - to prevent 'unrooting"
I do not remember which file I unfortunately changed.
Now I cannot install the 4.2.2 upgrade - the OTA fails because it boots into TWRP and after that I rrid several selections from TWRP screen (flash, reboot, etc) - but all attempts failed.
I have the upgrade files (bot .tar and .zip) on /sdcard directory but have no idea how to update to 4.2.2.
Tried manual flashing using adb command - all fails.
I do not have beats drivers installed
Can someone tell me how to uninstall TWRP? If the CWM recovery works with this upgrade, I would like to change from TWRP to CWM.
Or any other suggestion wold be appreciated.
I am really struggling with Android operating system the way it configured on Nexus 7 by Google - any simplest is a major pain!
Hope I can get out of this and operate the device instead of continuously meddling with operating system.
Thanks in advance
[email protected]
Hi there guys!
I have rooted and unlocked the bootloader for my Nexus 10, and just wondering how do i go about installing & booting multiple roms? Do i need some special software?
Thanks!
chronosoft said:
Hi there guys!
I have rooted and unlocked the bootloader for my Nexus 10, and just wondering how do i go about installing & booting multiple roms? Do i need some special software?
Thanks!
Click to expand...
Click to collapse
I always find zedomax's videos to be extremely helpful for visuals. He also shows how to load custom roms.
http://forum.xda-developers.com/showthread.php?t=1997227
You'll need to download a recovery program like Clockwork Recovery or TWRP. Both have official websites with the latest release of their recovery programs. Just Google them.
DizoAZ said:
I always find zedomax's videos to be extremely helpful for visuals. He also shows how to load custom roms.
http://forum.xda-developers.com/showthread.php?t=1997227
You'll need to download a recovery program like Clockwork Recovery or TWRP. Both have official websites with the latest release of their recovery programs. Just Google them.
Click to expand...
Click to collapse
Thanks for the reply, I have TWRP installed, so do i just flash the downloaded rom as per normal and use TWRP? Is there an option in TWRP?
Thanks!
chronosoft said:
Thanks for the reply, I have TWRP installed, so do i just flash the downloaded rom as per normal and use TWRP? Is there an option in TWRP?
Thanks!
Click to expand...
Click to collapse
Yeah, so for example. Download CleanROM which is pretty much a stock ROM and all functions of the tablet seem to work that I've tried so far, GPS, WiFi, Camera. Haven't tried HDMI or Audio port yet. Microphone works too.
http://forum.xda-developers.com/showthread.php?t=2113048
Once you download the .zip file for CleanROM to your tablet, it will be in the Downloads directory under the directory /sdcard/0/Dowload.
Then reboot in to fastboot by holding down the volume +/- at the same time along with the power button held. Once you get to the fastboot screen, use the volume rocker until you see Recovery Mode, then hit the power button. This should put you in to TWRP which you said you have loaded as the recovery program. I have Clockwork, it's just a different recovery program, but I've used both before fine. Watch this for TWRP and how to make backups. http://youtu.be/EDZ1WAwXvbE?t=1m30s
Normally, I do a complete clean install each time, but I've also been successful loading from one rom to another and not performing the factory reset. As long as you don't perform the factory reset your apps and settings should remain.
However, I'm a person who likes to do a clean install, so I usually wipe all cache options first, then perform a wipe/data/factory reset and load the rom I want. From there, there should be an option to install from a .zip file, that is where you would go to load the custom rom, then select it and let it do its thing. After installing the ROM, I repeat the steps of wiping cache and factory reset after the ROM install is complete, before I reboot the tablet. Once I do all that, I reboot the tablet and let it load.
People say you should perform a backup of your existing ROM/Settings by using the recovery program to do so, that's really up to you if you want to do it, but it does provide a method to restore your prior rom/settings. I don't, because I just got the tablet and don't have a lot of settings/programs installed at the moment.
If for some reason your tablet just gets stuck at the Nexus X when loading, you may need to perform the wipe data/factory reset from Recovery. If you need to do it from the PC, you can load in to Fastboot (power and volume +/-) let it sit there with your USB cord connected and from your PC go to the directory with fastboot.exe and run "fastboot -w" to wipe. You will lose all your settings and programs just like when doing the wipe through recovery.
Hope this helps. Note, some ROM's suggest loading GApps, I haven't messed with those ROMs yet, but imagine it just requires installing a 2nd .zip file after installing the rom .zip file with recovery.
ah that's how it's done. Thanks for clarifying this DizoA, that's really helpful, appreciate it!
I'm having a big problem with my Nexus 4 here lately. I tried to root it about 2 days ago, and it did not work. So i downloaded TWRP and my computer read it the same as the Nexus 4 root toolkit by WugFresh. I opened TWRP and it asked me to flash or boot (it was on flash), and i think i clicked "Recovery" and it made my Nexus not boot up, it was just at the logo screen. Then i tried to flash TWRP to the bootloader and System and it flashed TWRP, now it won't go into android. It just takes me into the TWRP interface. In the TRWP interface there are 8 options( Install, Wipe, Backup, Restore, Mount, Settings, Advanced, and Reboot). I pressed "Reboot" and i when press System, Recovery, or Bootloader it tells me that the is no OS installed, I've looked up how to install OS back via WugFresh's toolkit, but it's still not working (maybe because I'm on a old computer). So I'm kinda panicking, is there anyone i can call,or take my phone to, or can you guys help PLEASE!?!
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Okay, i'll try that right now..
chromium96 said:
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Click to expand...
Click to collapse
I'm having a problem with the ADB setup, i followed all the directions carfully, and that last step were i had to type in "adb devices" in did not work... is there anyway i can open adb??
Yiddish said:
I'm having a problem with the ADB setup, i followed all the directions carfully, and that last step were i had to type in "adb devices" in did not work... is there anyway i can open adb??
Click to expand...
Click to collapse
Try install these drivers: http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
chromium96 said:
Try install these drivers
Click to expand...
Click to collapse
Nice, that worked. Okay i'm back on track. Also, does it matter what ROM i download?? I don't have to be rooted to push them huh?
Yiddish said:
Nice, that worked. Okay i'm back on track. Also, does it matter what ROM i download?? I don't have to be rooted to push them huh?
Click to expand...
Click to collapse
Nope. Just make sure u put the phone in recovery mode (twrp) before you use the push command.
Sent using xda-developers app
chromium96 said:
Nope. Just make sure u put the phone in recovery mode (twrp) before you use the push command.
Sent using xda-developers app
Click to expand...
Click to collapse
Recovery mode is when the Android is on it's back with a red exclamation over it right??
Yiddish said:
Recovery mode is when the Android is on it's back with a red exclamation over it right??
Click to expand...
Click to collapse
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
chromium96 said:
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
Click to expand...
Click to collapse
Oh, i see. Okay here i go
chromium96 said:
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Click to expand...
Click to collapse
Okay, it got past the Google screen, now it's been on the multicolored X for about 10 minutes+ not doing anything
chromium96 said:
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
Click to expand...
Click to collapse
How long will i be on the X loading screen??
Yiddish said:
How long will i be on the X loading screen??
Click to expand...
Click to collapse
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
BobWalker said:
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
Click to expand...
Click to collapse
Thanks! I think it was just the ROM i chose. I just downloaded Slim Bean, this seems to be working( the startup screen looks cool ) I'm on the "Android is upgrading..." screen and it says "Starting apps." at the moment.
Okay, SlimBean took more than 10 minutes, so i factory reset and tried again, and it's still not booting up. ):
BobWalker said:
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
Click to expand...
Click to collapse
Any ideas why it's still not working??
Yiddish said:
Any ideas why it's still not working??
Click to expand...
Click to collapse
I have not used Slim Bean. It sounds as though you got past the boot animation screen to Slim Bean updating apps (Android upgrading). Normally ROMs that update apps on startup display a count as they update. Does Slim Bean display such an update counter? Does the count progress or does it hang at some point? Note that the system update on startup will take additional time depending on the quality of your phone's network connection. If you are still experiencing issues with Slim Bean, I recommend that you post on the developers forum where you downloaded the ROM.
BobWalker said:
I have not used Slim Bean. It sounds as though you got past the boot animation screen to Slim Bean updating apps (Android upgrading). Normally ROMs that update apps on startup display a count as they update. Does Slim Bean display such an update counter? Does the count progress or does it hang at some point? Note that the system update on startup will take additional time depending on the quality of your phone's network connection. If you are still experiencing issues with Slim Bean, I recommend that you post on the developers forum where you downloaded the ROM.
Click to expand...
Click to collapse
I got passed the boot animation, and it was taking too long to update my apps so i turned my phone off, and back on, after that my phone would not go past the boot animation. Are you guys sure that all i need to do is pus a ROM file?? Because it doesn't seem like it's working. Also, does it matter were i flash TWRP too??
Yiddish said:
I got passed the boot animation, and it was taking too long to update my apps so i turned my phone off, and back on, after that my phone would not go past the boot animation. Are you guys sure that all i need to do is pus a ROM file?? Because it doesn't seem like it's working. Also, does it matter were i flash TWRP too??
Click to expand...
Click to collapse
It is certainly more convenient to replace the stock recovery with TWRP permanently since this gives you more freedom when installing ROMs and performing nandroid backups.
I would try booting into TWRP again, install the Slim Bean ROM one more time, install Gapps, wipe Cache and Dalvik cache, and reboot your phone. If the Nexus gets past the boot animation to "Android upgrading" allow the upgrade to complete. If you are still having problems with Slim Bean, I suggest posting your question in the Slim Bean thread in the developers forum.
BobWalker said:
It is certainly more convenient to replace the stock recovery with TWRP permanently since this gives you more freedom when installing ROMs and performing nandroid backups.
I would try booting into TWRP again, install the Slim Bean ROM one more time, install Gapps, wipe Cache and Dalvik cache, and reboot your phone. If the Nexus gets past the boot animation to "Android upgrading" allow the upgrade to complete. If you are still having problems with Slim Bean, I suggest posting your question in the Slim Bean thread in the developers forum.
Click to expand...
Click to collapse
Where do i get Gapps??
Alright, so I've decided on what I want to use rom and kernel wise, and want someone to double check that they are compatible, and I have the right versions.
I would appreciate if someone would check that I have the right steps and files.
KERNEL:
From:
http://minooch.com/franciscofranco/Nexus4/4.3/zips/
Have:
franco.Kernel-nightly-r182.zip (this is JWR, right?)
ROM:
From:
http://goo.im/devs/paranoidandroid/roms/mako
Have:
pa_mako-3.99-20130823.zip
From:
http://download.paranoidandroid.co/Developers/TLKruzze/gapps/
Have:
pa_gapps-full-4.3-20130822-signed.zip
STEPS:
This is coming from a fresh out of box nexus, so stock 4.3.
1. Typical unlock bootloader, root, flash recovery, etc. I'll probably just use this toolkit for this.
2. Recovery
3. Wipe
4. Flash rom
5. Flash GApps
6. Wipe cache
7. Wipe dalvik cache
8. Boot to make sure it works
9. Recovery
10. Flash kernel zip
11. Reboot
Are those steps and files all correct, or am I missing something?
Thanks!
That's what I'm running now. No issues.
Personally I'd do it with adb for when something goes wrong you know how to fix it. When I unlocked and flashed recovery on my phone, everything wiped, even the stock rom was gone. Luckily I learned adb with my galaxy nexus and was able to restore the factory images with fastboot (minus recovery) and start over.
Also don't use the newest twrp. It was wiping my baseband and I reverted to the last version through fastboot to get it working.
Sent from my Nexus 4
quantim0 said:
That's what I'm running now. No issues.
Personally I'd do it with adb for when something goes wrong you know how to fix it. When I unlocked and flashed recovery on my phone, everything wiped, even the stock rom was gone. Luckily I learned adb with my galaxy nexus and was able to restore the factory images with fastboot (minus recovery) and start over.
Also don't use the newest twrp. It was wiping my baseband and I reverted to the last version through fastboot to get it working.
Sent from my Nexus 4
Click to expand...
Click to collapse
Eh, I still prefer toolkits, even if there is a small risk.
The toolkit will be running CWM, so that shouldn't be a problem.
Thanks!
Zortwil said:
Alright, so I've decided on what I want to use rom and kernel wise, and want someone to double check that they are compatible, and I have the right versions.
I would appreciate if someone would check that I have the right steps and files.
KERNEL:
From:
http://minooch.com/franciscofranco/Nexus4/4.3/zips/
Have:
franco.Kernel-nightly-r182.zip (this is JWR, right?)
ROM:
From:
http://goo.im/devs/paranoidandroid/roms/mako
Have:
pa_mako-3.99-20130823.zip
From:
http://download.paranoidandroid.co/Developers/TLKruzze/gapps/
Have:
pa_gapps-full-4.3-20130822-signed.zip
STEPS:
This is coming from a fresh out of box nexus, so stock 4.3.
1. Typical unlock bootloader, root, flash recovery, etc. I'll probably just use this toolkit for this.
2. Recovery
3. Wipe
4. Flash rom
5. Flash GApps
6. Wipe cache
7. Wipe dalvik cache
8. Boot to make sure it works
9. Recovery
10. Flash kernel zip
11. Reboot
Are those steps and files all correct, or am I missing something?
Thanks!
Click to expand...
Click to collapse
Before installing the ROM you should wipe data,cache,dalvick , system and if you are coming from 4.2.2 based ROM you have do a factory reset before wiping.
Also after flashing the kernel you need to flash Supersu v1.51 zip so that you dont face any root issues.
P.S : Enable the developer option and enable root with app+adb.
Rest you are right and good to go.
Welcome. :good:
As far as wiping goes u can do a few additional steps to make sure there's no issues.
1. Wipe data/factory reset
2. Wipe cache
3. Go into mounts and storage
4. Format /system
5. Format /data
6. Format /cache
7. Go into advanced wipe /dalvik
Rohit02 said:
Before installing the ROM you should wipe data,cache,dalvick , system and if you are coming from 4.2.2 based ROM you have do a factory reset before wiping.
Also after flashing the kernel you need to flash Supersu v1.51 zip so that you dont face any root issues.
P.S : Enable the developer option and enable root with app+adb.
Rest you are right and good to go.
Welcome. :good:
Click to expand...
Click to collapse
Do I have to flash Supersu, or can I just get it from the play store?
Zortwil said:
Do I have to flash Supersu, or can I just get it from the play store?
Click to expand...
Click to collapse
Yeah no problem..
Here is a Flashable zip of Supersu v1.55(latest) : SuperSu Download
You are welcome. :good:
I dont have a C6906 so don't ask me for screenshot, I'm posting this as member requested
C6906_14.5.A.0.242_C6906_Customized US.zip 1.14 GB
https://mega.co.nz/#!ut0ziLAT!b1AuNTolyD4Rm9Aqqqe8gWXme3TTF2Rrp5HqAJAOkTE
this file included SuperSU.zip and dualrecovery already, but if you want to be safe, you can flash them again
links to other files at bottom of this post
C6906_14.5.A.0.242_Customized US_Stripped.ftf 24.2 MB
https://mega.co.nz/#!nldGzISI!IQ0WCWe7KMsQScVy-RbVrIgF9_jmNRqc4BVje7HWi6o
Nut's Recovery flashable zip
flashable zip
http://nut.xperia-files.com/?ql=c5fb...3f320ee594741a
deconfrost said:
C6906_14.5.A.0.242_Customized US_Stripped.ftf 24.2 MB
https://mega.co.nz/#!nldGzISI!IQ0WCWe7KMsQScVy-RbVrIgF9_jmNRqc4BVje7HWi6o
Click to expand...
Click to collapse
Is this flashtool file the same contents as the recovery flashable one, or is this a case where you need to use both to fully perform the update?
Edit: Nevermind, now I saw your file sizes.. obviously the second one is just the kernel(and maybe recovery?) so what's the order to flash these?
deconfrost said:
I dont have a C6906 so don't ask me for screenshot, I'm posting this as member requested
C6906_14.5.A.0.242_C6906_Customized US.zip 1.14 GB
https://mega.co.nz/#!ut0ziLAT!b1AuNTolyD4Rm9Aqqqe8gWXme3TTF2Rrp5HqAJAOkTE
this file included SuperSU.zip and dualrecovery already, but if you want to be safe, you can flash them again
links to other files at bottom of this post
C6906_14.5.A.0.242_Customized US_Stripped.ftf 24.2 MB
https://mega.co.nz/#!nldGzISI!IQ0WCWe7KMsQScVy-RbVrIgF9_jmNRqc4BVje7HWi6o
Nut's Recovery flashable zip
flashable zip
http://nut.xperia-files.com/?ql=c5fb...3f320ee594741a
Click to expand...
Click to collapse
thanks a lot downloading now
araemo said:
Is this flashtool file the same contents as the recovery flashable one, or is this a case where you need to use both to fully perform the update?
Edit: Nevermind, now I saw your file sizes.. obviously the second one is just the kernel(and maybe recovery?) so what's the order to flash these?
Click to expand...
Click to collapse
follow the first post here, its the same just different model number
http://forum.xda-developers.com/xperia-z1/general/c6903customized-hk1276-794814-5-0-t3080949
Just wanted to say that last night I did a Nandroid backup of my 4.4.4 / 157 install, and flashed this guy. Worked flawlessly.
For those who are wondering:
1. Do a nandroid backup of your entire ROM.
2. Wipe Data, both caches, System and if you want, Internal Storage (IS is optional).
3. Flash ROM - that's the big boy file, the 1GB+ one. DO NOT RESTART PHONE.
4. Wipe both caches again.
5. Power Down phone, boot into Flashmode. Use Flashtool to flash the stripped FTF. Straight forward, just do it, nothing special.
6. Boot phone at this point, if #5 is successful. Boot time will take ~10mins or more, this is normal.
7. Install SuperSU from Play Store, just to confirm flash was successful. If no update available, then you're good to go! Rooted and recovery installed at this point. Do another Nandroid backup so you can start messing around with the ROM and XPosed.
After you install Xposed, if you decided to do so that is, if you're installing things like GravityBox and the 20MP Camera fixes, etc. and you get a bootloop - this is a loop that happens during the pink "live wallpaper" loading animation, not the Sony/Xperia/Powered By Android black logos: Clear your cache / dalvik again, and fix permissions. DO NOT FIX SELINUX PERMISSIONS.
Thanks. For the record, dirty flash had no issues. I wiped cache manually, installed your zip, installed stripped ftf, rebooted. First boot took a while (unsurprisingly), and then 'phone' took near 100% cpu for quite a while (I'm guessing some messaging storage conversion/update), but all is fine now, even after further reboots.
araemo said:
Thanks. For the record, dirty flash had no issues. I wiped cache manually, installed your zip, installed stripped ftf, rebooted. First boot took a while (unsurprisingly), and then 'phone' took near 100% cpu for quite a while (I'm guessing some messaging storage conversion/update), but all is fine now, even after further reboots.
Click to expand...
Click to collapse
good to hear
thanks for the detail feddback
Wiltron said:
Just wanted to say that last night I did a Nandroid backup of my 4.4.4 / 157 install, and flashed this guy. Worked flawlessly.
For those who are wondering:
1. Do a nandroid backup of your entire ROM.
2. Wipe Data, both caches, System and if you want, Internal Storage (IS is optional).
3. Flash ROM - that's the big boy file, the 1GB+ one. DO NOT RESTART PHONE.
4. Wipe both caches again.
5. Power Down phone, boot into Flashmode. Use Flashtool to flash the stripped FTF. Straight forward, just do it, nothing special.
6. Boot phone at this point, if #5 is successful. Boot time will take ~10mins or more, this is normal.
7. Install SuperSU from Play Store, just to confirm flash was successful. If no update available, then you're good to go! Rooted and recovery installed at this point. Do another Nandroid backup so you can start messing around with the ROM and XPosed.
After you install Xposed, if you decided to do so that is, if you're installing things like GravityBox and the 20MP Camera fixes, etc. and you get a bootloop - this is a loop that happens during the pink "live wallpaper" loading animation, not the Sony/Xperia/Powered By Android black logos: Clear your cache / dalvik again, and fix permissions. DO NOT FIX SELINUX PERMISSIONS.
Click to expand...
Click to collapse
Hey wiltron,
I have a bell rom *.108 build, it is carrier unlocked, but bootloader is locked.
I have installed the dual recovery, and have used the flashtool before (to recover from a bad flash). I am wondering if flashing this rom was possible, How did you get the 157 firmware ? Was your phone bootloader unlocked ?
thanks
Nz
notzippy said:
Hey wiltron,
I have a bell rom *.108 build, it is carrier unlocked, but bootloader is locked.
I have installed the dual recovery, and have used the flashtool before (to recover from a bad flash). I am wondering if flashing this rom was possible, How did you get the 157 firmware ? Was your phone bootloader unlocked ?
thanks
Nz
Click to expand...
Click to collapse
I'm on Rogers, Locked Bootloader.
I flashed the FTF from the sticky up top, rooted it with the kernel swap method (click here), then used recovery to flash the 502 pre-rooted ROM.
Lets keep things neat and tidy. Further discussions, shares in the FTF Mega Collection thread please
http://forum.xda-developers.com/showthread.php?t=2469191
Thread closed