Related
Hi All,
1. Will unlock the bootloader wipe out the phone? If so how to root 2.3.6 without losing data?
I want to backup my data in the N1, then do flash the CM7 mod onto that.
It's in retail 2.3.6, I want to backup my data first.
sms, did with sms backup and restore.
call logs and bookmarks, how I backup them?
apps, want to backup with titanium backup, but hasn't root the phone yet.
I found the root guide for 2.3.6 here
https://bexton.net/2011/10/12/bexboot-root-nexus-one-passion-grk39f/
But it wants me to unlock the bootloader first, unlock the bootloader will wipe the phone so I will lost my data right?
apps can be redownloaded, so how I backup my call logs and bookmarks without root (yet)?
--
another question is I see the note for the latest N1 CM7 build is
'The latest radio is needed to run CyanogenMod 7'.
I can see my phone already has baseband of 5.08.00.04, do I need to do anything related to the radio while I flashing CM7?
Regards,
Sorry, there is NO way to back up your data if you are on 2.3.6 with a locked bootloader and without root.
I'm on stock 2.3.6.
Tried using the bexboot method, but it goes through all the steps and does nothing.
The bat file at the end doesn't reboot my phone or root.
I have also tried downgrading my device, but every time i go into fastboot, it says I have the wrong img file, or the file can't be found. I have properly renamed the file and put it on my sd card. no luck.
please help
patelkartik27 said:
I'm on stock 2.3.6.
Tried using the bexboot method, but it goes through all the steps and does nothing.
The bat file at the end doesn't reboot my phone or root.
I have also tried downgrading my device, but every time i go into fastboot, it says I have the wrong img file, or the file can't be found. I have properly renamed the file and put it on my sd card. no luck.
please help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=18527514&postcount=1853
patelkartik27 said:
I'm on stock 2.3.6.
Tried using the bexboot method, but it goes through all the steps and does nothing.
The bat file at the end doesn't reboot my phone or root.
I have also tried downgrading my device, but every time i go into fastboot, it says I have the wrong img file, or the file can't be found. I have properly renamed the file and put it on my sd card. no luck.
please help
Click to expand...
Click to collapse
Sry for the late response, but i've been on a business trip. The issue with my first version of bexboot was, that it was compiled from a heavily "prestressed" system with lots of modifications. Thus i rebuilt the boot image from a complete clean source.
So if somebody is still looking for an "idiot-proof" way to root a Nexus One on stock GRK39F, check out the updated version release of Bexboot v2.0 what have been confirmed working from people who had issues with v1:
https://bexton.net/2011/11/07/bexboot-for-passion-version-2-root-for-nexus-one-with-android-grk39f/
Greets!
Bexton said:
Sry for the late response, but i've been on a business trip. The issue with my first version of bexboot was, that it was compiled from a heavily "prestressed" system with lots of modifications. Thus i rebuilt the boot image from a complete clean source.
So if somebody is still looking for an "idiot-proof" way to root a Nexus One on stock GRK39F, check out the updated version release of Bexboot v2.0 what have been confirmed working from people who had issues with v1:
https://bexton.net/2011/11/07/bexboot-for-passion-version-2-root-for-nexus-one-with-android-grk39f/
Greets!
Click to expand...
Click to collapse
What is the advantage of doing this, if all you have to do is flash a custom recovery and flash this from recovery??
efrant said:
What is the advantage of doing this, if all you have to do is flash a custom recovery and flash this from recovery??
Click to expand...
Click to collapse
Hey Efrant,
well, actually there is no big difference. But if i should find some, maybe:
A) ALL-IN-ONE
* It comes packed with all you need.
* There is no need to have the SDK installed before using it.
* You don't need to flash a custom recovery before using it.
B) STOCK
* As you don't need a custom recovery to flash it, you also don't need to overwrite any of the original stock ROM files. So actually your system stays completely untouched.
C) UP-TO-DATE
* It installs the latest versions of Superuser APK / su binary, rather than the linked ones.
The bottom line: Actually it was built for "beginners", to provide a simple to use method to root a stock ROM. You can download a zip archive, connect an untouched, never used/modified stock phone to a computer, type two/three commands in a terminal window, the phone reboots, you have root and the system is still pure stock. That's what it's all about..
Cheers!
Bexton said:
Hey Efrant,
well, actually there is no big difference. But if i should find some, maybe:
A) ALL-IN-ONE
* It comes packed with all you need.
* There is no need to have the SDK installed before using it.
* You don't need to flash a custom recovery before using it.
B) STOCK
* As you don't need a custom recovery to flash it, you also don't need to overwrite any of the original stock ROM files. So actually your system stays completely untouched.
C) UP-TO-DATE
* It installs the latest versions of Superuser APK / su binary, rather than the linked ones.
The bottom line: Actually it was built for "beginners", to provide a simple to use method to root a stock ROM. You can download a zip archive, connect an untouched, never used/modified stock phone to a computer, type two/three commands in a terminal window, the phone reboots, you have root and the system is still pure stock. That's what it's all about..
Cheers!
Click to expand...
Click to collapse
Thanks for the explanation. Good work.
But just to address some of your points:
A) ALL-IN-ONE:
if you don't install the SDK, you still need to install the fastboot and ADB drivers anyway - there is no difference between using this method or any other method, i.e., either the SDK or the drivers themselves have to be installed for your device to be recognized by the computer.
B) STOCK:
flashing a custom recovery on a stock ROM does not really overwrite anything, because once you boot your device, the stock recovery is automatically flashed back by the ROM.
no ROM files are touched by flashing a custom recovery.
C) UP-TO-DATE
I linked to the wrong thread in my post.. oops I meant to link here: http://androidsu.com/superuser/
efrant said:
Thanks for the explanation. Good work.
But just to address some of your points:
A) ALL-IN-ONE:
if you don't install the SDK, you still need to install the fastboot and ADB drivers anyway - there is no difference between using this method or any other method, i.e., either the SDK or the drivers themselves have to be installed for your device to be recognized by the computer.
B) STOCK:
flashing a custom recovery on a stock ROM does not really overwrite anything, because once you boot your device, the stock recovery is automatically flashed back by the ROM.
no ROM files are touched by flashing a custom recovery.
C) UP-TO-DATE
I linked to the wrong thread in my post.. oops I meant to link here: http://androidsu.com/superuser/
Click to expand...
Click to collapse
Well, as said: actually there's no big difference. And yeah, indeed you're right about the recoveries. But to address one of your (/my) points:
The SDK is an application package that needs to be installed.
Fastboot, as well as the ADB are standalone executables; there is nothing to be installed. These executables are just a tiny part of the whole SDK Package. There's no need to download and install all the SDK Package, if you'd need just the adb, the fastboot and the drivers. Thus you'd save at least some time (and bandwith).
Also, when i'll include the install script tomorrow (as it has been with v1), it will reduce the number of commands you have to type in the terminal to two.
So the bottom line: eventhough you're right about (almost all of) your contras, if you'd need to start with an untouched phone and computer it's definitely faster - and i think, also just simpler - to do it "my way".
But.. anyway.. it's the same way.
---------- Post added at 10:46 PM ---------- Previous post was at 10:34 PM ----------
PS: And therefore - to re-answer your initial question:
efrant said:
What is the advantage of doing this, if all you have to do is flash a custom recovery and flash this from recovery??
Click to expand...
Click to collapse
Depending on your working environment, it simply can save some time.
Anyone can help me?
I tried to install Froyo by Laszlo, I followed the instructions, I tried to flash the 2.22.27.08 radio, but I received this message:
Install from sdcard . . .
Finding update package . . .
Verifying update package . . .
Installing update . . .
*************
Can't Install Radio
You are using CustomMTD
CustomMTD must be removed
before you can install a radio
Install from sdcard complete.
I don't understand... Install is complete or what? How to check?
Please help me, this is my first G1 device and i want a fast and stable ROM (Froyo by Laszlo).
Be careful you read up before you start flashing radios, a brick is easy if your careless. To check your current radio and spl just hold the camera button while powering on. This screen will tell you what's installed.
Sent from my HTC Vision using xda premium
He needs to *remove cmtd* (by flashing fr_remove_xxx.zip) before flashing a new radio or spl by recovery, or he needs to flash the new radio by flastboot (which I suggest, because it's much more secure). Everything about cmtd you can read on Firerat's Github repository.
Removing cMTD
Yes, you may like to remove cMTD The primary reason for removing cMTD is to flash a radio or hboot via recovery. I'm not going to go into detail here, but if you can then consider using fastboot instead of recovery for this. Sometimes you have no option, recovery will have to do..
there are few ways to remove cMTD
With early versions you just flashed an original recovery.img
In later versions, I supplied an extra remove.zip which can still be used.
since version 1.5.9-Alpha4, you just set systemMB to 0
adb shell
sed -i s/systemMB=.*\ /systemMB=0 /sdcard/mtdpartmap.txt
then flash AutoPatch-v1.5.9-Beta1-CustomMTD_S.zip, format routine, reboot to recovery If you are restoring a rom, then flash AutoPatch-v1.5.9-Beta1-CustomMTD_S.zip (twice) to make sure the boot.img is patched
Click to expand...
Click to collapse
I understand this, that's the correct method? :
#1: plug the phone to my PC and install the drivers (need drivers?)
#2: run adb via "run" on the start menu
#3: write the resize command ("sed"? not "set"?)
#4: unplug the phone and launch to recovery, then run the AutoPatch-v1.5.9-Beta1-CustomMTD_S.zip (where can i find?)
#5: reboot to recovery, full wipe, install radio
#6: then reboot to recovery, full wipe, install hboot
#7: then reboot to recovery, full wipe, install ROM?
To remove cmtd you can also download FR-remove-v1.5.6-CustomMTD_S.zip, copy it onto your SD-card, reboot into recovery and flash the zip. That's all, now you have removed your custom partition layout, *but* your ROM installed will no longer boot up *and* you should clean up everything by either flashing Ohsaka's Superwipe or doing a
Code:
fastboot erase system -w
Now you have a clean phone with standard partition layout and you can start from there to install what you need. As always I suggest: Read before flashing! Especially if you want to go to the 27.08 /0013d combo you should read and understand Terry's thread before starting to flash.
Uhm, how to enter fastboot?
edit: i'm on fastboot mode but i don't have built on my PC.
Nah, i flashed the 1.33.0013d hboot via recovery and installed the Froyobylaszlo ROM. The radio needed fastboot, but i have a little problem... I installed the SDK, installed the drivers, but if i tryin to flash radio via fastboot, this searching for the dev for ever (waiting for the device)
The ROM is awesome, fast, have much of RAM, etc. - however not perfectly. I have 256MB Swap and 512MB ext4, but a few app/game, like Galcon and Opera Mini (my recomended apps) frozen at the beginning black screen and all browser (stock, Dolphins) force closing... user error? That's the missing radio's effect?
I thank all helps.
Sent from my HTC Dream using XDA
AndDiSa said:
He needs to *remove cmtd* (by flashing fr_remove_xxx.zip) before flashing a new radio or spl by recovery, or he needs to flash the new radio by flastboot (which I suggest, because it's much more secure). Everything about cmtd you can read on Firerat's Github repository.
Click to expand...
Click to collapse
Flastboot???? lolololol Anywho, maybe you haven't changed the PATH directory on your pc?
TheShortybro said:
Flastboot???? lolololol Anywho, maybe you haven't changed the PATH directory on your pc?
Click to expand...
Click to collapse
Probably you should read the whole thread before posting your comments ...
Sent from my Gingerbread on Dream using XDA
Just a guess, maybe he forgot and don't be so rude!
TheShortybro said:
Flastboot???? lolololol Anywho, maybe you haven't changed the PATH directory on your pc?
Click to expand...
Click to collapse
:banghead:
I need help for my problem, not ****ful comments...
@AndDiSa, you don't know the root of my problems with Froyobylaszlo?
Sent from my HTC Dream using XDA
At what status are you at the moment?
Can you please boot into hboot-mode (back-button + power on) and can you send the spl/radio versions currently installed on your phone?
Force-closing apps normally are not related to the radio/spl version. I would wipe dalvik-caches and probably run "fix_permissions" on a root shell, this should help ...
Hboot - 1.33.0013d
CPLD - 4
Radio - 1.22.12.29
-----
Baseband: 62.33.20.08U_1.22.12.29
Kernel: 2.6.34.8-froyobylaszlo [email protected]#1
Mod ver: FroyoByLaszlo-5.2
Build: FRG83
Android: 2.2.1
AndDiSa said:
Force-closing apps normally are not related to the radio/spl version. I would wipe dalvik-caches and probably run "fix_permissions" on a root shell, this should help ...
Click to expand...
Click to collapse
Please, give me a link
Sent from my HTC Dream using XDA
Requirements:
Flashtool
A recovery (can be both CWM and TWRP)
NOTE: As some people have problems flashing the update, please update your existing recovery to the latest recovery with XZDualRecovery
Current FW version: 10.1.A.1.350 or 10.1.A.1.434: maybe others too, try and let me know!
From the users in the thread I noticed people CWM running into trouble because their cache partition is gone. See the 'Known Issues' in the OP of the XZDualRecovery link above for more info and links to a fix. Fix that first before you attempt this update using CWM!
Special features:
Superuser integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.3 RELEASE (CWM 6.0.3.2 & TWRP 2.5.0.0) pre-installed;
Tailored FTF to minimize the chance of accidental system wiping!
No need to clear caches!
@shem2409 created a nice youtube video guide to assist you in your work, be sure to check his post for it! Thanks m8!
TIP: This ROM is compatible with the shutdown/reboot MOD by @niaboc79
TIP: This ROM and the integrated recovery are compatible with the reboot wrapper by @DooMLoRD, get it here!
C6603: How to update to 10.1.1.A.1.253:
For C6603: Download C6603.flashable.253.zip (Bittorrent: 728MB) and Xperia_Z_10.1.1.A.1.253_C6603-stripped.ftf (14MB), save it somewhere you remember;
Put 'C6603.flashable.253.zip' on (the external) SDcard1;
Put 'Xperia_Z_10.1.1.A.1.253_C6603-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';
Flash everything in 'Xperia_Z_10.1.1.A.1.253_C6603-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel. DooMKernel v7 has support for this ROM version.
Flash 'C6603.flashable.253.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
C6602: How to update to 10.1.1.A.1.253:
For C6602: Download C6602.flashable.253.zip (Bittorrent: 703MB) and Xperia_Z_10.1.1.A.1.253_C6602-stripped.ftf (14MB), save it somewhere you remember;
Put 'C6602.flashable.253.zip' on (the external) SDcard1;
Put 'Xperia_Z_10.1.1.A.1.253_C6602-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';
Flash everything in 'Xperia_Z_10.1.1.A.1.253_C6602-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel. DooMKernel v7 has support for this ROM version.
Flash 'C6602.flashable.253.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
The first boot will be considerably slower and after a long wait at the boot animation you will see Android optimizing the apps on your phone, It will update your NFC with a firmware and after that, all is done!
IMPORTANT NOTE:
For some devices the first or second reboot after the successful upgrade may be initiated by the ROM/Kernel to upgrade some low-level firmware. This will be done from the screen which normally shows you the kernel logo. This upgrade flash will also happen when on a custom kernel by @DooMLoRD. DO NOT INTERRUPT THAT WHATEVER YOU DO OR HOWEVER LONG IT TAKES! Just let it do it's thing and wait, your phone will continue boot as soon as it's done.
I have done this myself, using my own method and I have not found any problem yet. :fingers-crossed:
Enjoy! :victory:
Known XZDualRecovery Issues:
All known issues in TWRP and CWM on locked boot loaders apply, see their respective threads for more information.
Be especially careful with the cache partition when using CWM. Hopefully version 2.0 solved the cache issues but in case of problems with /cache use the FTF in my files to restore the cache partition if yours ever stops mounting due to the CWM issues, read this and this for more info on that. This FTF was created for .434 but as the cache did not change between .350, .434 and .253 you can still use it to fix the cache partition.
CWM Usage warning: Root can be lost (almost worst case), a bootloop can be experienced (worst case) or a reboot upon remounting /system to be able to write to it (most cases, relatively harmless) when using CWM and before a reboot out of recovery the 'ROM may flash recovery, fix it?' question is answered with 'yes'. This can be recovered from by opening a terminal app and typing the following commands:
Code:
su
/system/bin/stop ric
mount -o remount,rw /system
chmod 755 /system/etc/install-recovery.sh
Alternatively you can boot in to TWRP and go to the Advanced menu -> File manager and look for /system/etc/install-recovery.sh to set permissions 755 on it.
If even that is too much to handle for you, see the patch at the bottom of the OP to flash the fix.
TWRP Usage warning: It seems TWRP 2.5.0.0 has issues with the internal storage, which seem related to the changes made to support encrypted storage volumes... This means the internal storage sometimes shows up almost empty (just folders) and no files. Try to use CWM when that happens.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore a .434 /system ONLY using any means you are familiar with so you can try again.
Root it using any means you are familiar with.
Install XZDualRecovery and then try to update again using TWRP. This time you can skip the FTF as it has already done it's job.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /tmp/XZDualRecovery, pack them up and send them to me.
Thank you
Flashable ROM Mutator:
Download AROMA ROM Mutator 0.13
This (former patch package) uses AROMA to create a user friendly menu to choose between updates to be installed.
If you want to switch from SuperUser (default in this ROM) to SuperSU you can use this to make the change.
If you have the reboot problem when trying to remount /system writable, you can reinstall the superuser app of your preference, it's installation includes the patch.
If you are missing /system/bin/chargemon.stock and you want to be able to charge your phone while it's turned off.
Flash using one of the recoveries!
Version 0.13 and upwards is using AROMA 2.70B1 or better, the below warning can be ignored for now. Let me know how it performs!
AROMA Warning: AROMA currently works best in TWRP but even there it has some issues on the Z/ZL. It sometimes does not start up correctly or it has a 'sticky button' issue. It makes it a little less easy to use but this will be fixed in time. It is a combination problem caused by the new hardware and incompatibility with it and the fact the recoveries both have been updated considerably to work on the latest phones, causing issues with some functionality of AROMA.
If it hangs when trying to start, reboot your phone and try again.
If it has the sticky buttons, press the button again to activate.
You can avoid the sticky buttons by pressing them for about half a second (that means not too short and not too long). It will work, it's just showing a bug associated with the latest recoveries.
The Samsung S4, HTC One and One X and the Nexus 4 & 7 show the same issues. For them AROMA sometimes crashes, this is an issue i have not yet observed on the Z/ZL.
XDA:DevDB Information
Update to 10.1.1.A.1.253, a ROM for the Sony Xperia Z
Contributors
[NUT]
ROM OS Version: 4.1.x Jelly Bean
Based On: STOCK
Version Information
Status: No Longer Updated
Created -0001-11-30
Last Updated 2013-06-25
Reserved
Reserved
Reserved
I take it you have to be coming from .434 to .253? I also see you have unlocked your bootloader and using a custom kernel
danw_oz said:
I take it you have to be coming from .434 to .253?
Click to expand...
Click to collapse
Yes, i have
Hi NUT, may I know how to check my XZ is fully rooted or not ?
Thanks a lot ~
KennyCHF said:
Hi NUT, may I know how to check my XZ is fully rooted or not ?
Thanks a lot ~
Click to expand...
Click to collapse
Try with root explorer, remount /system as rw (for reading and writing), if it suddenly reboots, your rooting failed.
The root methods by bin4ry and DooMLoRD have more issues. This release was unchanged, root gets installed after the rom itself by the flashable zip. As a result, i could not find a fault yet
Can you show me how root the room (.Zip) because i created my rom (C6602 in my country) but when i installation Suppersu.zip, i go to Root explorer set R/o and my phone reboot....Thanks alot if U help me
can i flash docomo status bar after finish?
my phone's bootloader is locked. So after following this method will i be having the latest kernel, fota & baseband? will there be any problem if i flash them from the .253 FTF?
I've got a stock ROM, locked and unrooted and branded.
Can I use the FTF file with flashtool only for upgrade and unbrand the phone?
This method include the latest kernel, fota, baseband etc..? or just system files?
im downloading the zip file now,
but where can i get the stripped ftf file? is it inside the zip or what?
thanks :3
Aresmar said:
This method include the latest kernel, fota, baseband etc..? or just system files?
Click to expand...
Click to collapse
Yes, of course
alfiabraham said:
my phone's bootloader is locked. So after following this method will i be having the latest kernel, fota & baseband? will there be any problem if i flash them from the .253 FTF?
Click to expand...
Click to collapse
Yes, no problem whatsoever.
Mastrox said:
I've got a stock ROM, locked and unrooted and branded.
Can I use the FTF file with flashtool only for upgrade and unbrand the phone?
Click to expand...
Click to collapse
NO, your phone needs a recovery and that can only be if you are rooted...
spazzy1912 said:
im downloading the zip file now,
but where can i get the stripped ftf file? is it inside the zip or what?
thanks :3
Click to expand...
Click to collapse
Inside the zip yes
changkho1908 said:
can i flash docomo status bar after finish?
Click to expand...
Click to collapse
You can do to it whatever you want after installation, it's a full Rom
nhoc_huhu said:
Can you show me how root the room (.Zip) because i created my rom (C6602 in my country) but when i installation Suppersu.zip, i go to Root explorer set R/o and my phone reboot....Thanks alot if U help me
Click to expand...
Click to collapse
I'll give you an example soon.
Sent from my C6603 using xda app-developers app
Sorry I want to be sure.
I am locked Bootloader/rooted/recovery etc.
I will do as your guide says. But If I want to get the latest kernel etc; I have to flash kernel baseband etc from a stock 253 ftf?
Am I right? Or your files already have these?
A bit confused here
EDIT:
I looked at your "Xperia_Z_10.1.1.A.1.253_C6603-stripped.ftf" it containes the kernel baseband and stuff. So first you flash the new kernel etc... than the new system via recovery if I understand correctly. And system includes all the necessary root busybox and recoveries.
I still can't believe how this works on locked bootloader hehe.
Aresmar said:
Sorry I want to be sure.
I am locked Bootloader/rooted/recovery etc.
I will do as your guide says. But If I want to get the latest kernel etc; I have to flash kernel baseband etc from a stock 253 ftf?
Am I right? Or your files already have these?
A bit confused here
EDIT:
I looked at your "Xperia_Z_10.1.1.A.1.253_C6603-stripped.ftf" it containes the kernel baseband and stuff. So first you flash the new kernel etc... than the new system via recovery if I understand correctly. And system includes all the necessary root busybox and recoveries.
I still can't believe how this works on locked bootloader hehe.
Click to expand...
Click to collapse
An FTF file is basically the same thing as the packages downloaded by SUS, the only difference is you use a different tool to install them and that a FTF is a container where the separate files are stored into one easy to handle bunble.
The locked bootloader accepts them because it also uses the exact same way to flash them but with a greater freedom of choice. The separate sin files are signed by Sony and that is still unchanged so the bootloader will accept them because of that.
And you understand the procedure well. Now go and do it
Sent from my C6603 using xda app-developers app
[NUT] said:
Try with root explorer, remount /system as rw (for reading and writing), if it suddenly reboots, your rooting failed.
The root methods by bin4ry and DooMLoRD have more issues. This release was unchanged, root gets installed after the rom itself by the flashable zip. As a result, i could not find a fault yet
Click to expand...
Click to collapse
I have followed your instruction to do, then I get the new firmware with root.
However my XZ will reboot when I mount the /system with R/W.
It does not happen before the upgrade. Any method to solve it ? thanks.
After flashing ftf, I lost my recovery.
I cant enter recovery now, so I couldnt flashed flashable.253.zip.
What should I do?
Everything is still working but I am on my old rom. "KA07 Revolution"
[NUT] said:
I've been cooking up a FW 10.1.1.A.1.253 Generic release, this thread will carry it into the world... i know @wawyed did one too, he beat me too it
I hope I can offer something he can not: ease of installation and without losing any data!
Requirements:
Flashtool
A recovery (can be both CWM and TWRP)
Current FW version: 10.1.A.1.350 or 10.1.A.1.434: maybe others too, try and let me know!
Special features:
Superuser integrated in system, FULL root, no reboots when remounting /system rw!
XZDualRecovery 2.1 BETA (CWM 6.0.3.2 & TWRP 2.5.0.0) pre-installed;
Tailored FTF to minimize the chance of accidental system wiping!
No need to clear caches!
How to update to 10.1.1.A.1.253:
Download NUTs_Xperia_Z_10.1.1.A.1.253.zip (743MB), save and unpack it somewhere you remember;
Put 'flashable.253.zip' on (the external) SDcard1;
Put 'Xperia_Z_10.1.1.A.1.253_C6603-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';
Flash 'Xperia_Z_10.1.1.A.1.253_C6603-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to!
Flash 'flashable.253.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
The first boot will be considerably slower and after a long wait at the boot animation you will see Android optimizing the apps on your phone, It will update your NFC with a firmware and after that, all is done!
I have done this myself, using my own method and I have not found any problem yet. :fingers-crossed:
Enjoy! :victory:
Click to expand...
Click to collapse
when we flash with flashtool...(locked bootloader) we have to exclude something?
I'm preparing to flash a custom rom to my girlfriend's I9000, but if anything goes wrong I want to be able to just reflash a nandroid backup and not need to change any settings or reconfiguring anything. I need some advice about how to make a nandroid backup in the least invasive way possible, i.e., preventing tinkering to the current (stock) rom. The problem--I think I need to use a custom recovery to make a nandroid backup. How do I do that with the least tinkering to the current ROM? Premise, I'm using Linux and I do not have access to a windows machine. I have the android sdk installed (fastboot, adb) and I'm comfortable using the commandline. I don't know much about android, but I _do_ like to know what I'm doing She currently is using stock, unrooted I9000XWJW5_I9000XENJV6_XEN.
I considered (and tried some of) the following options.
1. Boot a CWM recovery image with fastboot, without flashing CWM to the device. Unfortunately, I don't seem to be able to boot to fastboot with the I9000.
2. Boot to existing recovery and flash CWM recovery image in the form of an update.zip file. Unfortunately, recovery complains about some signature problem with the update.zip and refuses to install it. I think it is 3e recovery--too new?
3. Use adb shell to upload an exploit, then remount /system rw, install su, reboot, install superuser.apk, install CWM manager, flash CWM recovery. Just like all the oneclickroot scripts. Unfortunately, _none_ of the exploits I found gave me root?! I tried zergRush ("Hellions with BLUE flames !"), psneuter, GingerBreak (let it run for over 15 minutes, no result) and motofail. Is there any exploit known to work on this stock rom?
4. Flash a new kernel with heimdall that includes a recovery (e.g., cf-root 4.4 or semaphore kernel). I'm not looking forward to doing this because cf-root and semaphore are not just kernels but all kinds of other stuff as well that I don't necessarily want to be there when I make a nandroid backup. In other words, these options, to me, seem quite invasive, and I wouldn't know very well what I was doing anymore.
5. Unpack the correct fs-image from a stock rom, add su and superuser.apk, repack it, flash with heimdall. Install CWM via CWM manager. I did not find information about how to do this or whether it even works.
The best would be that it actually _is_ possible to boot to fastboot on I9000. Let me know if it is, but I couldn't find any information about this. Also, I really hope that someone can advise a different exploit for option 3. Some pointers for option 5 would help as well. If nothing else works I'll flash cf-root or semaphore. A prerooted stock kernel image with only su and superuser.apk would be preferable, but that I haven't found that either. Anyway, I hope someone can lend me a suggestion or give me a pointer!
find ur own cf root, its da easiest way to attain 2e recovery, 3e recovery activate signature check,no need for adb, juz find ur own cf root.
or juz switch rom to stock jvu latest.
so many way to attain solution available if u can reach download mode, so why messing with adb? u wanna lose ur internal sd partition?
Sent from my GT-I9000 using xda premium
compacity said:
find ur own cf root, its da easiest way to attain 2e recovery, 3e recovery activate signature check,no need for adb, juz find ur own cf root.
Click to expand...
Click to collapse
Okay, that rules out flashing CWM from stock recovery
or juz switch rom to stock jvu latest.
so many way to attain solution available if u can reach download mode, so why messing with adb? u wanna lose ur internal sd partition?
Click to expand...
Click to collapse
As I said, I want the least invasive method, and I want to understand what I'm doing. Installing a kernel image with an initrd that I know little about, that I do not understand very well. Logging in via adb, running an exploit and doing some basic Linux commandline stuff, that I _do_ understand. So to me, adb is less messy than flashing some modified kernel (although I might end up doing that). Regarding the sd partition--is there any real risk losing one by using adb? Anyway, I'll use dd to back up the sd partition.
PJBrs said:
Okay, that rules out flashing CWM from stock recovery
As I said, I want the least invasive method, and I want to understand what I'm doing. Installing a kernel image with an initrd that I know little about, that I do not understand very well. Logging in via adb, running an exploit and doing some basic Linux commandline stuff, that I _do_ understand. So to me, adb is less messy than flashing some modified kernel (although I might end up doing that). Regarding the sd partition--is there any real risk losing one by using adb? Anyway, I'll use dd to back up the sd partition.
Click to expand...
Click to collapse
there s always risk when u altering somethin, juz be sure to know what ur doing.
Sent from my GT-I9000 using xda premium
I ended up flashing the semaphore kernel and making a nandroid backup from the included cwm. First though, I did find various more exploits, but none of them worked. Apparently JW5 stock rom is quite invulnerable. I also found out that it should be possible to modify the factoryfs.rfs directly, but you need the rfs kernel model, which is not part of the mainline kernels. There are Samsung patches for rfs floating around, but they don't compile on recent kernels. In fact, the easiest way to modify a stock factoryfs.rfs image would be to loop-mount it on another rooted Samsung device. So, that was too much a hassle.
Anyway, girlfirend now is using CM10 and is an awful lot faster than stock JW5 Should have done that ages ago!
PJBrs said:
I ended up flashing the semaphore kernel and making a nandroid backup from the included cwm. First though, I did find various more exploits, but none of them worked. Apparently JW5 stock rom is quite invulnerable. I also found out that it should be possible to modify the factoryfs.rfs directly, but you need the rfs kernel model, which is not part of the mainline kernels. There are Samsung patches for rfs floating around, but they don't compile on recent kernels. In fact, the easiest way to modify a stock factoryfs.rfs image would be to loop-mount it on another rooted Samsung device. So, that was too much a hassle.
Anyway, girlfirend now is using CM10 and is an awful lot faster than stock JW5 Should have done that ages ago!
Click to expand...
Click to collapse
so....when will ur girlfriend gonna treat u for ur success?
Sent from my GT-I9000 using xda premium
compacity said:
so....when will ur girlfriend gonna treat u for ur success?
Click to expand...
Click to collapse
That's rude, not appreciated.
PJBrs said:
That's rude, not appreciated.
Click to expand...
Click to collapse
juz joking thou
Sent from my GT-I9000 using xda app-developers app
Hi! I have an lg OB running ics 4.0.4(V30B). The phone it's rooted and I have CWM installed from Rom Manager. I can acces Recovery from Rom Manager and with the phone off ( VOLUME PLUS + G KEY). The problem is that I can't flash any Rom bellow ics (not even with Smart Flash Tools) without getting bootloops. I can flash Roms based on ics and above( IZS,CM10.1,NAMELESS ROM NIGHTLIES 4.4.4).
Could someone help me?
Nobody?
JoKeR[RO-VL] said:
Nobody?
Click to expand...
Click to collapse
I was hoping you fixed the issue. I don't know what to do.
It's a matter of unlocking the boot loader. Once you do that, you can jump back and forth between ICS-based ROMs and everything else.
Gingerbread ROMs include the boot loader (marvel and Huexxx).
androcraze said:
I was hoping you fixed the issue. I don't know what to do.
It's a matter of unlocking the boot loader. Once you do that, you can jump back and forth between ICS-based ROMs and everything else.
Gingerbread ROMs include the boot loader (marvel and Huexxx).
Click to expand...
Click to collapse
Man I can flash ICS-based ROMs .JB and KK, I can't flash GB stock or GB-based ROMs, not even with SFT.
I think the bootloader it's unlocked because I can acces CWM from switch off phone(key combo)....I am confused because i read many tutorials but they are contradictory
That happends also with me 2 times.
Just flash CWM recovery again.
ptxpaulo said:
That happends also with me 2 times.
Just flash CWM recovery again.
Click to expand...
Click to collapse
Already tried....when i try to flash a GB ROM stock or custom GB-based Rom I get stuck in a bootloop.Same story with Smart Flash Tools...SFT says "succes", I hear the "ta daaa" sound ,phone reboots but stuck in a bootloop.
JoKeR[RO-VL] said:
Already tried....when i try to flash a GB ROM stock or custom GB-based Rom I get stuck in a bootloop.Same story with Smart Flash Tools...SFT says "succes", I hear the "ta daaa" sound ,phone reboots but stuck in a bootloop.
Click to expand...
Click to collapse
Try toii install a ROM right after rebooting from flash.
What I did is: Install a JB ROM, After, I reinstall CWM with ADB, reboot and then I could install any rom.
ptxpaulo said:
Try toii install a ROM right after rebooting from flash.
What I did is: Install a JB ROM, After, I reinstall CWM with ADB, reboot and then I could install any rom.
Click to expand...
Click to collapse
Sorry but how to install CWM with ADB? I've installed CWM(6.0.1.4) only from Rom Manager....
JoKeR[RO-VL] said:
Sorry but how to install CWM with ADB? I've installed CWM(6.0.1.4) only from Rom Manager....
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1613183
ptxpaulo said:
http://forum.xda-developers.com/showthread.php?t=1613183
Click to expand...
Click to collapse
Doesn't work and its stuck on lg logo now
Try to flash first original Froyo 2.2.2 , and then you can upgrade to GB ! Worked for me !
seby24gl said:
Try to flash first original Froyo 2.2.2 , and then you can upgrade to GB ! Worked for me !
Click to expand...
Click to collapse
Did you unlocked the bootloader first? can you put a link with your froyo and SFT?
I am from Romania so I need an Europe Open
No, I don't tried to unlock bootloader, but like you , I got the bootloops every time I downgrade from ICS, Nameless or cyanogen roms . I use original Froyo - flashed with SFT , then upgrade to GB with Cwm recovery patch- flashed with SFT, then boot to recovery and install Nameless. I will give you the links, once I uploaded to my dropbox.
Here, I hope will help you : https://www.dropbox.com/s/psniks1yvqwymy9/firmware v10a-europe-p970.rar
seby24gl said:
No, I don't tried to unlock bootloader, but like you , I got the bootloops every time I downgrade from ICS, Nameless or cyanogen roms . I use original Froyo - flashed with SFT , then upgrade to GB with Cwm recovery patch- flashed with SFT, then boot to recovery and install Nameless. I will give you the links, once I uploaded to my dropbox.
Here, I hope will help you : https://www.dropbox.com/s/psniks1yvqwymy9/firmware v10a-europe-p970.rar
Click to expand...
Click to collapse
Thanks bro! Hope it works.
seby24gl said:
No, I don't tried to unlock bootloader, but like you , I got the bootloops every time I downgrade from ICS, Nameless or cyanogen roms . I use original Froyo - flashed with SFT , then upgrade to GB with Cwm recovery patch- flashed with SFT, then boot to recovery and install Nameless. I will give you the links, once I uploaded to my dropbox.
Here, I hope will help you : https://www.dropbox.com/s/psniks1yvqwymy9/firmware v10a-europe-p970.rar
Click to expand...
Click to collapse
JoKeR[RO-VL] said:
Thanks bro! Hope it works.
Click to expand...
Click to collapse
It's not working. Don't know what to try
UP! When I use the bootloader unlocker app the flashing process take about 2-3 seconds and the app closing by itself without any message like "succes". I even tried to flash a u-boot img uploaded by huexxx and at the second reboot the phone stucks on lg logo without flashing leds
JoKeR[RO-VL] said:
UP! When I use the bootloader unlocker app the flashing process take about 2-3 seconds and the app closing by itself without any message like "succes". I even tried to flash a u-boot img uploaded by huexxx and at the second reboot the phone stucks on lg logo without flashing leds
Click to expand...
Click to collapse
Did you already try the alternative way without the app? Which means load the files to your sdcard and afterwards type the dd if=xxxx of=xxxx? This could show if it works or fails. And did you ever flash the LU5900 port? So the early ICS ROM released by Redy, Gabwerkz and me. Try the manual unlock first.
Sent from my XT1052 using XDA Free mobile app
N00BY0815 said:
Did you already try the alternative way without the app? Which means load the files to your sdcard and afterwards type the dd if=xxxx of=xxxx? This could show if it works or fails. And did you ever flash the LU5900 port? So the early ICS ROM released by Redy, Gabwerkz and me. Try the manual unlock first.
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
NO I did not flash the LU5900 port.Where do I need to type dd if ? I use windows 7 on my laptop.
JoKeR[RO-VL] said:
NO I did not flash the LU5900 port.Where do I need to type dd if ? I use windows 7 on my laptop.
Click to expand...
Click to collapse
As written in the thread, type it into terminal emulator (an app). Read the thread carefully please.
Sent from my XT1052 using XDA Free mobile app
N00BY0815 said:
As written in the thread, type it into terminal emulator (an app). Read the thread carefully please.
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
OK I have the terminal emulator on my phone.
I've read the thread and it says "Move this two files, bootloader and recovery to the root of memory sdcard;
Enter in the command line
su
dd if=/sdcard/u-boot.img of=/dev/block/mmcblk0p2
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
And reboot or reboot recovery."
I have downloaded all on my laptop(bootloader recovery and su) but I am confuse....what's with that "su"?
Do I have to put it on the root of the sdcard too?
Sorry for my noob question