Hey guys!
I finally decided to update my z1 compact to 5.1.1
Currently I'm on 4.4.4 (.0.157 firmware); it's rooted thanks to a guide found on this forum that let me to not unlock my bootloader (but sincerely I don't remember which one was since it's passed about one 1 year :cyclops: )
I have to say that I've NOT backuped my DRM keys yet (bc I'm very very lazy :angel: )
Now, what should I do in order to experience new Lollipop thrill on my device but still keeping root and bootloader locked on it? Can I update directly with new official firmware using Flashtool (and then root it) or os there some pre-rooted firmware that can be suitable with my case?
Sorry guys, I wrote in wrong section. I reported the thread to moderator already. I'm waiting for the shifting. I'm really sorry
Have a look at this thread --> PRF Creator
Basically, download the Lollipop firmware, and create a pre-rooted, flashable zip file that you can flash from your existing recovery.
If you look in the forums, some users will probably have uploaded a pre-rooted lollipop zip for you to try if you don't feel comfortable trying to do it yourself.
Hope that helps
MickieH said:
Have a look at this thread --> PRF Creator
Basically, download the Lollipop firmware, and create a pre-rooted, flashable zip file that you can flash from your existing recovery.
If you look in the forums, some users will probably have uploaded a pre-rooted lollipop zip for you to try if you don't feel comfortable trying to do it yourself.
Hope that helps
Click to expand...
Click to collapse
Could this be a solution for the c6916 American z1s as well?
Helgaiden said:
Could this be a solution for the c6916 American z1s as well?
Click to expand...
Click to collapse
Hiya,
It should work with any firmware really.
I've used it for my Z1, and my Z3, and used UK, CE1, and CE5 firmwares with no problems at all.
If you need any help, let me know.
MickieH said:
Hiya,
It should work with any firmware really.
I've used it for my Z1, and my Z3, and used UK, CE1, and CE5 firmwares with no problems at all.
If you need any help, let me know.
Click to expand...
Click to collapse
Even with a locked bootloader?
Helgaiden said:
Even with a locked bootloader?
Click to expand...
Click to collapse
Yes. They're only stock roms. They still have stock kernels.
You only need to unlock the bootloader if you want to run a custom kernel, like Cyanogenmod, or any other custom rom that doesn't use a stock Kernel.
All of my phones still have locked bootloaders.
All PRF does (very cleverly) is inject root and recovery into a stock ROM. The only reason the output file is a zip file is because we can't create ftf files ourselves. Those are signed by Sony. All you do is install the zip from an already existing recovery, so your phone must be rooted, with recovery already.
MickieH said:
Yes. They're only stock roms. They still have stock kernels.
You only need to unlock the bootloader if you want to run a custom kernel, like Cyanogenmod, or any other custom rom that doesn't use a stock Kernel.
All of my phones still have locked bootloaders.
All PRF does (very cleverly) is inject root and recovery into a stock ROM. The only reason the output file is a zip file is because we can't create ftf files ourselves. Those are signed by Sony. All you do is install the zip from an already existing recovery, so your phone must be rooted, with recovery already.
Click to expand...
Click to collapse
I don't think recovery exists for the z1s c6916, but I do have root. What options are there for that?
Helgaiden said:
I don't think recovery exists for the z1s c6916, but I do have root. What options are there for that?
Click to expand...
Click to collapse
XZ Dual Recovery should work on the C6916 according to NUT.
I don't see why it wouldn't, it's still a Z1
It's in the compatibility list here,
http://forum.xda-developers.com/showthread.php?t=2647487
Have you ever tried it?
MickieH said:
XZ Dual Recovery should work on the C6916 according to NUT.
I don't see why it wouldn't, it's still a Z1
It's in the compatibility list here,
http://forum.xda-developers.com/showthread.php?t=2647487
Have you ever tried it?
Click to expand...
Click to collapse
I have not. Thus far the bootloader has not been unlockable so I haven't really tried doing much, or anyone else for that matter.
Helgaiden said:
I have not. Thus far the bootloader has not been unlockable so I haven't really tried doing much, or anyone else for that matter.
Click to expand...
Click to collapse
You don't need an unlocked bootloader for nuts xz dual recovery.
The only thing you need is root, because you need permission to write to your phones system partition.
motorazrv3 said:
You don't need an unlocked bootloader for nuts xz dual recovery.
The only thing you need is root, because you need permission to write to your phones system partition.
Click to expand...
Click to collapse
So then I wonder if anyone has used this method to flash a newer 5.1.1 factory image from a regular z1 onto the US tmo Z1s...
Helgaiden said:
So then I wonder if anyone has used this method to flash a newer 5.1.1 factory image from a regular z1 onto the US tmo Z1s...
Click to expand...
Click to collapse
I don't know but I think not. Because the phones hardware isn't the same on all z1 types, you get the risk that something is not working or you are bricking your phone. That's the reason we have the different phone models like 6902, 6903,....
That's right. You can flash NUT's recovery on locked bootloader devices, that is what it was designed for, and the reason it's called 'lockeddualrecovery' :good:
If you flash a different model numbers firmware, then the modem is likely to be wrong for your carrier. If you look at some of the rom threads you'll see a lot of the Z1 C6903 roms contain patches for the C6902 also, which I'm assuming is the C6902's correct modem.
I don't know if you could flash another models on yours, but exclude the modem, thus retaining your own.
If you want to remain on stock, then I would highly recommend downloading your own model firmware from XperiFirm, SuperSU, and lockeddualrecovery for the Z1, then run it through PRF Creator. That way you'll end up with the correct firmware (and thus modem) which would be pre-rooted, with locked dual recovery.
Which firmware do you want to have? The latest for the US TM that I can see is
1277-0679 USA T-mobile US 14.5.B.0.247
---------- Post added at 03:57 PM ---------- Previous post was at 03:34 PM ----------
I wonder if we could create a pre-rooted zip from the unbranded UK 14.6.A.1.236 by not including the modem whilst creating the zip.
If you flash a zip containing that firmware, but not the UK modem, it would leave the most up to date modem that you already have, so connectivity should not be lost.
When running PRF Creator, there is a tick box to include the modem or not.
I'm just thinking out loud here, as it seems to be a similar issue to the C6902 patches on C6903 firmares.
I'm no developer, so I could be wrong.
MickieH said:
That's right. You can flash NUT's recovery on locked bootloader devices, that is what it was designed for, and the reason it's called 'lockeddualrecovery' :good:
If you flash a different model numbers firmware, then the modem is likely to be wrong for your carrier. If you look at some of the rom threads you'll see a lot of the Z1 C6903 roms contain patches for the C6902 also, which I'm assuming is the C6902's correct modem.
I don't know if you could flash another models on yours, but exclude the modem, thus retaining your own.
If you want to remain on stock, then I would highly recommend downloading your own model firmware from XperiFirm, SuperSU, and lockeddualrecovery for the Z1, then run it through PRF Creator. That way you'll end up with the correct firmware (and thus modem) which would be pre-rooted, with locked dual recovery.
Which firmware do you want to have? The latest for the US TM that I can see is
1277-0679 USA T-mobile US 14.5.B.0.247
---------- Post added at 03:57 PM ---------- Previous post was at 03:34 PM ----------
I wonder if we could create a pre-rooted zip from the unbranded UK 14.6.A.1.236 by not including the modem whilst creating the zip.
If you flash a zip containing that firmware, but not the UK modem, it would leave the most up to date modem that you already have, so connectivity should not be lost.
When running PRF Creator, there is a tick box to include the modem or not.
I'm just thinking out loud here, as it seems to be a similar issue to the C6902 patches on C6903 firmares.
I'm no developer, so I could be wrong.
Click to expand...
Click to collapse
I like where you're going with this. Hopefully a dev chimes in.
I just want to be off the broken memory leak firmware the z1s c6916 got stuck with. It gets absolutely crippling at times.
Helgaiden said:
I like where you're going with this. Hopefully a dev chimes in.
I just want to be off the broken memory leak firmware the z1s c6916 got stuck with. It gets absolutely crippling at times.
Click to expand...
Click to collapse
Same here buddy, same here.
Sent from my C6916 using XDA Free mobile app
Right, well, first things first.
To install recovery, download this --> Z1 Locked Dual Recovery 2.8.21 by NUT
This is the installer which you can run from your PC.
Make sure you have unknown sources ticked in your security settings, and USB debugging turned on in Developer options for it to work.
I use that one as I haven't tried the new combined installer/flashable recovery yet, and I know this one works fine on my Z1.
You could always download and use the newer combined one from NUT's download page if you wish, it's here --> Combined installer and flashable package
It's up to you on that.
Extract the zip file, then connect your phone to your PC while it's turned on, and double click the 'install.bat' and follow the on screen prompts. You will find that it will test reboot into recovery once it's finished anyway, if I remember correctly.
Once you have installed it, I would boot into recovery. You can press volume up or down when you turn your phone on, and it vibrates, or look for the NDR Utils app in your app drawer which is great for getting into recovery.
I like to use TWRP myself.
I'd create a backup once you're in recovery then at least you won't have to worry too much if anything does go wrong later.
Make sure you have a copy of the backup on an external SD card I would recommend.
That solves that problem.
Now, the newest firmware I have on my Z1 I have used PRF Creator, and created a zip file of it without including the modem files.
If you open the zip and look inside you will see the amss modem files, which are usually in the root directory, are missing.
This pre-rooted zip is C6903_Customized UK_1276-0875_14.6.A.1.236_R6D but without the modem files.
The zip can be downloaded here --> 14.6.A.1.236 For C6916 TM - UK Unbranded firmware with NO MODEM FILES
Be warned anyone downloading this that IT DOES NOT CONTAIN ANY MODEM FILES.
If you flash this in recovery, it will leave your current modem as is.
Now I can't guarantee that this will work, but you will have a working recovery anyway, so if it does go pear shaped, you can always restore that, and you'll be good.
PRF Zips will not wipe your userdata either, so anything on your internal memory will not be wiped.
While I find this good for minor OS version jumps, like 5.02 to 5.1.1, I do not recommend it for jumping different versions, i.e Lollipop back to KitKat for example. For something like that, I would personally prefer a full wipe.
Anyway, get the recovery installed and working, and once you're happy that you know how to use it, go ahead and flash the zip and see how you go.
If you do try it, and it works, great, just check your connectivity, mobile data, 2G, 3G, LTE, to make sure it's working ok.
If it doesn't work, I'm really sorry to have wasted your time, but you should be fine with a backup ready to fix any problems. Hopefully someone more knowledgeable will be along with a fix.
Anyway, good luck :good:
MickieH said:
Right, well, first things first.
To install recovery, download this --> Z1 Locked Dual Recovery 2.8.21 by NUT
This is the installer which you can run from your PC.
Make sure you have unknown sources ticked in your security settings, and USB debugging turned on in Developer options for it to work.
I use that one as I haven't tried the new combined installer/flashable recovery yet, and I know this one works fine on my Z1.
You could always download and use the newer combined one from NUT's download page if you wish, it's here --> Combined installer and flashable package
It's up to you on that.
Extract the zip file, then connect your phone to your PC while it's turned on, and double click the 'install.bat' and follow the on screen prompts. You will find that it will test reboot into recovery once it's finished anyway, if I remember correctly.
Once you have installed it, I would boot into recovery. You can press volume up or down when you turn your phone on, and it vibrates, or look for the NDR Utils app in your app drawer which is great for getting into recovery.
I like to use TWRP myself.
I'd create a backup once you're in recovery then at least you won't have to worry too much if anything does go wrong later.
Make sure you have a copy of the backup on an external SD card I would recommend.
That solves that problem.
Now, the newest firmware I have on my Z1 I have used PRF Creator, and created a zip file of it without including the modem files.
If you open the zip and look inside you will see the amss modem files, which are usually in the root directory, are missing.
This pre-rooted zip is C6903_Customized UK_1276-0875_14.6.A.1.236_R6D but without the modem files.
The zip can be downloaded here --> 14.6.A.1.236 For C6916 TM - UK Unbranded firmware with NO MODEM FILES
Be warned anyone downloading this that IT DOES NOT CONTAIN ANY MODEM FILES.
If you flash this in recovery, it will leave your current modem as is.
Now I can't guarantee that this will work, but you will have a working recovery anyway, so if it does go pear shaped, you can always restore that, and you'll be good.
PRF Zips will not wipe your userdata either, so anything on your internal memory will not be wiped.
While I find this good for minor OS version jumps, like 5.02 to 5.1.1, I do not recommend it for jumping different versions, i.e Lollipop back to KitKat for example. For something like that, I would personally prefer a full wipe.
Anyway, get the recovery installed and working, and once you're happy that you know how to use it, go ahead and flash the zip and see how you go.
If you do try it, and it works, great, just check your connectivity, mobile data, 2G, 3G, LTE, to make sure it's working ok.
If it doesn't work, I'm really sorry to have wasted your time, but you should be fine with a backup ready to fix any problems. Hopefully someone more knowledgeable will be along with a fix.
Anyway, good luck :good:
Click to expand...
Click to collapse
i tried to do a clean install and wiped the data, dalvik cache, internal memory (zip file was on external SD), and cache then flashed the zip. After complete, I pressed "reboot." Screen went black and now the LED blinks orange. If I hold the power button, I feel the phone vibrate but nothing happens. Damnit.
edit: got fastboot and flashmode working again and I'm flashing stock 4.4.4. Maybe I'll try this method again to make sure I didn't mess something up along the way.
edit 2: after restoring stock 4.4.4 , re-rooting, re-doing the nuts recovery, then reflashing the the above zip...same problem. No hope for us on the c6916. I'll go back to 4.4.4 that ran better than 5.0.2 and just deal with the SD card issues in KK. Maybe i'll root it to fix that though..
So I just found out that Android auto still require lollipop or better. DAMNIT. Just when I'm happy by moving back to 4.4.4 i find out that to use a feature of the vehicle I'm getting soon, I need to go back to the broken ass 5.0.2 lollipop firmware us Z1s owners are stuck with.
There has to be a solution to get us to 5.1. There just has to be. Any ideas?
What would happen if we tried creating a 5.1.1 pre-rooted zip for the tmobile z1s without the kernel and without the modem. I assume 5.1.1 would just not boot with the outdated kernel for 5.0.2, but it might still be worth trying, right?
Related
Hi folks, I have an Xperia Z and its still stuck at 4.1.2
It's a prototype model, I've used the phone now for months and its been working great despite the lack of updates but I'm hoping it can have the latest software like the rest of the phones out there.
The bottom of the phone has C6606 written on it but the image on the screen shows C6616. Any suggestions would be appreciated.
tinodevoe said:
Hi folks, I have an Xperia Z and its still stuck at 4.1.2
It's a prototype model, I've used the phone now for months and its been working great despite the lack of updates but I'm hoping it can have the latest software like the rest of the phones out there.
The bottom of the phone has C6606 written on it but the image on the screen shows C6616. Any suggestions would be appreciated.
Click to expand...
Click to collapse
can you take a screenshot of the 6616 screen? and can you go to the firmware by customization thread and follow the instructions? what is your cust.# ?
Thanks for the reply. l've PM'd you a link to the screen shot since I can't post any links on the forum yet. I'll check out the customization thread.
tinodevoe said:
Thanks for the reply. l've PM'd you a link to the screen shot since I can't post any links on the forum yet. I'll check out the customization thread.
Click to expand...
Click to collapse
I think you can flash c6606 Software without problems... Maybe even of C6603 via Flashtool.
tinodevoe said:
Thanks for the reply. l've PM'd you a link to the screen shot since I can't post any links on the forum yet. I'll check out the customization thread.
Click to expand...
Click to collapse
OK, that is really very strange. You could try to contact DoomLord or Apollo89, they have knowledge of such things.
Are you rooted? Can you do a CWM Backup? I suggest having a full backup before flashing another rom. So in case you need it, you can flash it back.
I am not sure if you have the same kernel as the rest of us. If you can not do a CWM backup, and are not rooted, you need to find a way to extract the file "boot.img" from the phone. This is the kernel, which you can easily flash back. But for this operation, a bootloader unlock will most probably be necessary.
If you can get no help from Doom or Apollo and can not extract boot.img, you might need to flash hoping for luck, or stay on the firmware you have.
Disclaimer: I might be much too paranoid, after all your phone seems to have the same hardware as the normal one, and a flash of a 10.4.B.0.569 ROM should be no problem. I just don't want to be the one that did not warn you and be responsable for a broken phone...
===============================================================
EDIT: Just had a look at the thread, C6616 is bell Canada, if you had found that, you could have reported back and told us that you solved the problem.
===============================================================
thanks for the advice. I still haven't tried anything with the phone. I've unlocked and flashed the firmware on my old Galaxy Nexus which for some reason also never updated (bought directly from Bell) but this one trying to read through all the information I'm having some trouble deciding on which method to use and where to really start.
If someone has a simple tutorial on flashing these phones please do share, otherwise I might just leave it as is and by the latest Nexus when this phone's done.
tinodevoe said:
thanks for the advice. I still haven't tried anything with the phone. I've unlocked and flashed the firmware on my old Galaxy Nexus which for some reason also never updated (bought directly from Bell) but this one trying to read through all the information I'm having some trouble deciding on which method to use and where to really start.
If someone has a simple tutorial on flashing these phones please do share, otherwise I might just leave it as is and by the latest Nexus when this phone's done.
Click to expand...
Click to collapse
Here is the link where its all explained http://forum.xda-developers.com/showthread.php?t=2275632
Also there is this video http://www.youtube.com/watch?v=j8EQmufr0lw
You need to download latest flashtool and latest firmware FTF for your model and follow instructions, really not hard, hardest part is to w8 untill all that downloads from internet
N1k0la89 said:
Here is the link where its all explained http://forum.xda-developers.com/showthread.php?t=2275632
Also there is this video http://www.youtube.com/watch?v=j8EQmufr0lw
You need to download latest flashtool and latest firmware FTF for your model and follow instructions, really not hard, hardest part is to w8 untill all that downloads from internet
Click to expand...
Click to collapse
sorry to sound dumb, but I can't figure out which firmware to select for my phone. Can someone please recommend a link for the correct file to flash this with? Also does it matter which generic firmware I use? I don't want to get the Bell firmware and end up with all the bloatware they have on there. I'd prefer as close to a clean firmware as possible so I can start getting the latest updates onto this phone.
tinodevoe said:
sorry to sound dumb, but I can't figure out which firmware to select for my phone. Can someone please recommend a link for the correct file to flash this with? Also does it matter which generic firmware I use? I don't want to get the Bell firmware and end up with all the bloatware they have on there. I'd prefer as close to a clean firmware as possible so I can start getting the latest updates onto this phone.
Click to expand...
Click to collapse
I think all Generic firmwares have the same "bloatware" app in common and all carrier branded firmwares have their carrier specific apps, so just choose a generic firmware and then remove all unuseful bloatware apps (if you go root).
akisg said:
I think all Generic firmwares have the same "bloatware" app in common and all carrier branded firmwares have their carrier specific apps, so just choose a generic firmware and then remove all unuseful bloatware apps (if you go root).
Click to expand...
Click to collapse
I finally just tried one method, following the guide here; http://forum.xda-developers.com/showthread.php?t=2240614
I installed flashtool and installed the stock Bell software, http://forum.xda-developers.com/showthread.php?t=2390178
It looked like everything went fine and when checking system updates it showed 4.3 was finally available!
but then after it downloaded the file I tried to install and it just gave me an error message :crying:
So what would be the next step for me?
tinodevoe said:
I finally just tried one method, following the guide here; http://forum.xda-developers.com/showthread.php?t=2240614
I installed flashtool and installed the stock Bell software, http://forum.xda-developers.com/showthread.php?t=2390178
It looked like everything went fine and when checking system updates it showed 4.3 was finally available!
but then after it downloaded the file I tried to install and it just gave me an error message :crying:
So what would be the next step for me?
Click to expand...
Click to collapse
Any info about that error??
Why not flash to 4.3 directly with flashtool or to 4.2 and then upgrade to 4.3?
Also try a fresh install by wiping data (if you have already a backup of them of course) it maybe helps..
akisg said:
Any info about that error??
Why not flash to 4.3 directly with flashtool or to 4.2 and then upgrade to 4.3?
Also try a fresh install by wiping data (if you have already a backup of them of course) it maybe helps..
Click to expand...
Click to collapse
I've tried a couple times now to update that system update, its 10.4.B.0.569, once it starts to install it goes to the robot install logo at the startup for a second then starts the phone right away without doing the full install. The message on screen is simply "could not install".
i'll try a factory reset then directly to 4.3. I'm assuming I can use the same method as before or do I need to look into rooting the phone now?
tinodevoe said:
I've tried a couple times now to update that system update, its 10.4.B.0.569, once it starts to install it goes to the robot install logo at the startup for a second then starts the phone right away without doing the full install. The message on screen is simply "could not install".
i'll try a factory reset then directly to 4.3. I'm assuming I can use the same method as before or do I need to look into rooting the phone now?
Click to expand...
Click to collapse
As soon you are installing a stock rom, you don't have to worry about root.
But if you wanna root, your only choice is to flash a 4.2 rom, root it with a method of your choice and then upgrade to a prerooted 4.3.
Can someone please point me in the right direction to a FW that works with my phone? the only one that I seem to be able to use with flashtool is this one here which is 4.1.2. http://forum.xda-developers.com/showthread.php?t=2390178
however it won't let me update the system!
I'm guessing that I need a C6616 firmware to make this work, but I also tried this one, http://forum.xda-developers.com/showthread.php?t=2612159 and I get an error in flashtools, in red writing 'ERROR - error flashing. Aborted'.
I've been searching on here and all the other firmwares are 6603 which I tried a couple and again errors in flashtools.
trying again with that 4.1.2 its flashing it but its not the firmware I need!
ok, finally got one of them to work! I'm not sure what it was but I downloaded a bunch of firmwares until one of them finally updated me to 4.3.
thanks for all the help!
Hi all,
I have a c6903 Z1 currently on Kitkat 4.4.2 (after an OTA update I really wish I'd never done) and I want to root it so I can install the SD card permission fix - can't put up with not being able to write to external SD, it's infuriating. If I can fix that, I can probably put up with KitKat.
If I'm still not happy with that then I want to go back to 4.3
Having read a lot, and I mean pages, and pages, about it, and having to downgrade, I've picked up that I would have to use NUT's .534 ftf to avoid losing the IMEI, and then I was going to root with vRoot.
Does anyone know, does that install Superuser or will I need the Superuser zip too?
At that point I want to then install recovery, so I'm looking at NUT's Z1 Locked Dual Recovery.
I rekon that should all be fine.
To get it back on KitKat I should then put the 757 zip on my SD card and flash in recovery, reboot and flash the stripped ftf with Flashtool, along with the recovery again.
If I still don't like it, I could then just repeat the above, but with the .136 zip and stripped ftf.
Am I thinking right here?
The only thing that's a bit worrying is that, for example, the .136 update thread says to come from .290.
Is this so, do I have to install that first, or can I go straight from the newly rooted .534 directly?
Sorry if this has been answered before, but my eyes are killing me staring at this screen now.
The only other thing I'm thinking is to just not root, and simply flash a Jelly Bean full ftf.
I'd rather have root and recovery though.
Thanks,
Mick.
wow, you didn't read much
DO NOT USE VROOT, IT SEND YOUR IMEI TO AN IP ADDRESS IN CHINA.
To get root on 757, just follow the step sin my signature
No need to use any root methods or unlock the bootloader
3 steps, 5 minutes work max.... a bit longer if you have slow download speeds
gregbradley said:
wow, you didn't read much
DO NOT USE VROOT, IT SEND YOUR IMEI TO AN IP ADDRESS IN CHINA.
To get root on 757, just follow the step sin my signature
No need to use any root methods or unlock the bootloader
3 steps, 5 minutes work max.... a bit longer if you have slow download speeds
Click to expand...
Click to collapse
Just wasn't looking in the right places, so it seems.There is an awful lot of info on here though, and one link leads to another, however very informative reading.
Thank you so much for your help, don't mean to be a pain, and I do appreciate it.
All you guys do an amazing job.
Will it make any difference if I use the Z1 locked recovery instead of the XZ one, or should I just use the XZ anyway? Does it matter?
MickieH said:
Just wasn't looking in the right places, so it seems.There is an awful lot of info on here though, and one link leads to another, however very informative reading.
Thank you so much for your help, don't mean to be a pain, and I do appreciate it.
All you guys do an amazing job.
Will it make any difference if I use the Z1 locked recovery instead of the XZ one, or should I just use the XZ anyway? Does it matter?
Click to expand...
Click to collapse
download the file for the Z1 from [NUT]s page since that one is for this phone.
the XZ is for the xperia Z and that is a different phone. It is always advisable to download and flash things that are deigned/made for the phone you have, not another phone....
u don't need to install the 290 version first, get nut's 534 stock, then install dualrecovery and go straight with the 136 one.
Check nut's instructions or use this youtube video which is foolprove.
youtube.com/watch?v=1aq9YTlfCgc
help
I have an unrooted sony Xperia z1 (C6902), and I want to have the timeshift video and 4k video recording features on my phone, please help me out,
I don't want to loose my warranty,
Tried to install z2 super camera apps from various threads but didn't worked,
gregbradley said:
download the file for the Z1 from [NUT]s page since that one is for this phone.
the XZ is for the xperia Z and that is a different phone. It is always advisable to download and flash things that are deigned/made for the phone you have, not another phone....
Click to expand...
Click to collapse
Thanks again, and sorry, it does complicate things as I have the Xperia Z and a Z1.
I'll go with the Z1 recovery then.
Your help is greatly appreciated, it really is.
Sometimes you just can't see the fire for the smoke, you know.
Thanks again,
Mick.
MickieH said:
Thanks again, and sorry, it does complicate things as I have the Xperia Z and a Z1.
I'll go with the Z1 recovery then.
Your help is greatly appreciated, it really is.
Sometimes you just can't see the fire for the smoke, you know.
Thanks again,
Mick.
Click to expand...
Click to collapse
I am not sure if we got our wires crossed before.
the XZDR installer will install dual recovery on your phone from PC
the Z1 flashable file will upgrade to the latest version from recovery itself, but will only work on a Z1.
gregbradley said:
I am not sure if we got our wires crossed before.
the XZDR installer will install dual recovery on your phone from PC
the Z1 flashable file will upgrade to the latest version from recovery itself, but will only work on a Z1.
Click to expand...
Click to collapse
Oh, right, well, I've downloaded this installer -> Z1-lockeddualrecovery2.7.123-BETA from NUT's site.
I'll flash NUT's .534 ftf with flashtool first, then I'll run the installer from my lappy, and that should root and install the recovery.
I have also downloaded the Z1-lockeddualrecovery2.7.123-BETA.flashable - I assume that's what I need to flash after flashing another ROM if it doesn't include it's own recovery.
I have noticed some ROMS have earlier version recoveries, like .80, built in. Can I still flash the .123 on to of those with no issues? I have read there had been some issues with flashing over older recoveries.
Has anyone figured out why the IMEI was being lost? Was it due to the baseband
I've already got the drivers installed, in fact I successfully flashed back to .136 just to try it (last flashing I did was on my Arc S, so been a while) last night as I just couldn't be bothered with KitKat anymore.
Thanks again,
Mick.
MickieH said:
I have noticed some ROMS have earlier version recoveries, like .80, built in. Can I still flash the .123 on to of those with no issues? I have read there had been some issues with flashing over older recoveries.
Click to expand...
Click to collapse
If the installation was successfully then it doesn't matter. The older one working well. In the case you want flash the newets one then you have to wipe your phone with a stock FTF.
MickieH said:
Has anyone figured out why the IMEI was being lost? Was it due to the baseband
Click to expand...
Click to collapse
kind of, but don't worry, you will have your IMEI back after upgrade again.
I can open a topic for this question, but i'll just ask it here to prevent extra spam etc hehe.
If i get to a 757 rooted firmware using these methods, and i want to go to a non rooted firmware like 769 if it comes out. Will that be just a matter of reflasing the tft that belongs to that firmware using flashtool, or do i have to make more steps?
Thanks for answering!
saintgein said:
I can open a topic for this question, but i'll just ask it here to prevent extra spam etc hehe.
If i get to a 757 rooted firmware using these methods, and i want to go to a non rooted firmware like 769 if it comes out. Will that be just a matter of reflasing the tft that belongs to that firmware using flashtool, or do i have to make more steps?
Thanks for answering!
Click to expand...
Click to collapse
When 769 will be out then NUT will have Pre-Rooted FTF like the 757, so you will have just to repeat the same steps. If you will want go to 769 Stock then 1 step will be required, flash it via Flashtool.
I want to remind you also that we do not predict future so we don't know what Google will do to they future Firmwares so the steps can be less or more, nobody know it.
Just one more thing, sorry to be a pain.
I'm happy with the process, flash NUT's. 534 ftf, then run the recovery installer to get root and recovery.
I don't want to install a custom rom right now.
I either want to end up on 4.3 with root and recovery, or 4.4.2, root, recovery, and the SD card fix.
If I use the zip and stripped ftf files from NUT's download page, I'll still retain root access, is that right?
Then just reflash the recovery zip before rebooting, and job done?
I've had no issues with the stock .136 firmware I've currently downgraded to other than the NFC icon not appearing when active. Something I've gathered can be fixed by editing the build.prop, but doesn't bother me anyway.
MickieH said:
If I use the zip and stripped ftf files from NUT's download page, I'll still retain root access, is that right?
Click to expand...
Click to collapse
Yes, that's why is called Pre-rooted.
MickieH said:
Then just reflash the recovery zip before rebooting, and job done?
Click to expand...
Click to collapse
No, the Recovery will still there from the first installation, it will not be wiped. After installing zip and strippied files, you will be able to boot into recovery.
eclyptos said:
Yes, that's why is called Pre-rooted.
No, the Recovery will still there from the first installation, it will not be wiped. After installing zip and strippied files, you will be able to boot into recovery.
Click to expand...
Click to collapse
Ok, thank you for your help, I understand now, just needed to be clear before I went ahead.
Better to ask than mess it up.
To get root on 757, just follow the step sin my signature
Where to find steps??
I really am getting confused with a lot of different info, please help with simple instructions.
maid said:
Where to find steps??
I really am getting confused with a lot of different info, please help with simple instructions.
Click to expand...
Click to collapse
Yes, I had the same problem, there's lots of info on here. There's hundreds of pages to read and it can get confusing.
I'll assume your phone hasn't been messed with. i.e. The bootloader is locked, and it's not rooted, and that you're using a Windows PC.
If you have changed your phone, let us know.
Make sure you have USB debugging turned on in your Developer Options, and Unknown sources in the Security settings.
To enable Developer Options in your settings, go to Settings, About phone, and keep taping Build number until it says 'You are now a Developer'
You'll need to download the latest version of Flashtool from here --> http://www.flashtool.net/download.php
You'll need to install the drivers for your phone too. The driver installer is in the flashtool/drivers folder.
Ok, so this is what I've gathered so far :
This is the link to the steps, thanks to gregbradley --> http://forum.xda-developers.com/showpost.php?p=52407809&postcount=2
If you follow those, you'll end up with a rooted phone with whatever stock based rom you fancy.
Now the following are my thoughts, and what I've learned so far, but I'm not an expert.
My advice would be read more, and make sure you feel comfortable with what you are going to do, before you do it.
If you are unsure about anything, ask.
You'll need to use Flashtool to flash your phone.
The second post here,from DoomLord, shows how to connect your phone in flash mode --> http://forum.xda-developers.com/showthread.php?t=2440565 - Basically turn the phone off, then press volume down and connect to the PC via USB when Flashtool tells you to.
I downloaded the .534 ftf from NUT's download page which is here --> http://nut.xperia-files.com/
I downloaded this file --> http://nut.xperia-files.com/?dlid=QzY5MDNfMTQuMS5HLjEuNTM0X1tOVVRdLmZ0Zi50b3JyZW50
You have to download that with your torrent program.
If you don't know how to do that, I've uploaded the ftf to my cloud storage.
You can direct download the .534 ftf here --> https://mega.co.nz/#!mgwkAagR!6_iTB3LwVkGz6yvSaKQsEVPtyaIPq3BJGFCk1EDw9XQ
Place the .534 ftf in the c:/flashtool/firmwares folder
Make sure your phone is fully charged, and back up anything you want keeping, as flashing will wipe your phone.
Now run Flashtool, click the Flash icon (top left) and select the .534 ftf.Flashing the .534 ftf that NUT provided will prevent loss of IMEI.
Don't mess with any settings, and click Flash, and follow the instructions on screen.
That will return your phone to stock 14.1.G.1.534
Download the Z1 Locked Dual Recovery Installer from NUT's page --> http://nut.xperia-files.com/?dlid=WjEtbG9ja2VkZHVhbHJlY292ZXJ5Mi43LjEyMy1CRVRBLmZsYXNoYWJsZS56aXA=
Connect your phone to your PC and run the install.
That will root your phone, and install recovery.
From there you can then install whatever stock based ROM you want.
If you want your phone on KitKat 4.4.2, rooted, with recovery, then download the .757 files from NUT's download page.
You'd need the flashable zip --> http://nut.xperia-files.com/?dlid=QzY5MDNfMTQuMy5BLjAuNzU3LmZsYXNoYWJsZS56aXAudG9ycmVudA==
Download is via torrent.
Flash that zip from recovery.
The stripped part --> http://nut.xperia-files.com/?dlid=QzY5MDNfMTQuMy5BLjAuNzU3X1N0cmlwcGVkLmZ0Zg==
Flash that from Flashtool
That should be it.
Unless your bootloader is unlocked, do not try to flash anything other than stock based roms as it won't work, and will brick your phone.
Hope that helps :good:
MickieH said:
Yes, I had the same problem, there's lots of info on here. There's hundreds of pages to read and it can get confusing.
I'll assume your phone hasn't been messed with. i.e. The bootloader is locked, and it's not rooted, and that you're using a Windows PC.
If you have changed your phone, let us know.
Make sure you have USB debugging turned on in your Developer Options, and Unknown sources in the Security settings.
To enable Developer Options in your settings, go to Settings, About phone, and keep taping Build number until it says 'You are now a Developer'
You'll need to download the latest version of Flashtool from here --> http://www.flashtool.net/download.php
You'll need to install the drivers for your phone too. The driver installer is in the flashtool/drivers folder.
Ok, so this is what I've gathered so far :
This is the link to the steps, thanks to gregbradley --> http://forum.xda-developers.com/showpost.php?p=52407809&postcount=2
If you follow those, you'll end up with a rooted phone with whatever stock based rom you fancy.
Now the following are my thoughts, and what I've learned so far, but I'm not an expert.
My advice would be read more, and make sure you feel comfortable with what you are going to do, before you do it.
If you are unsure about anything, ask.
You'll need to use Flashtool to flash your phone.
The second post here,from DoomLord, shows how to connect your phone in flash mode --> http://forum.xda-developers.com/showthread.php?t=2440565 - Basically turn the phone off, then press volume down and connect to the PC via USB when Flashtool tells you to.
I downloaded the .534 ftf from NUT's download page which is here --> http://nut.xperia-files.com/
I downloaded this file --> http://nut.xperia-files.com/?dlid=QzY5MDNfMTQuMS5HLjEuNTM0X1tOVVRdLmZ0Zi50b3JyZW50
You have to download that with your torrent program.
If you don't know how to do that, I've uploaded the ftf to my cloud storage.
You can direct download the .534 ftf here --> https://mega.co.nz/#!mgwkAagR!6_iTB3LwVkGz6yvSaKQsEVPtyaIPq3BJGFCk1EDw9XQ
Place the .534 ftf in the c:/flashtool/firmwares folder
Make sure your phone is fully charged, and back up anything you want keeping, as flashing will wipe your phone.
Now run Flashtool, click the Flash icon (top left) and select the .534 ftf.Flashing the .534 ftf that NUT provided will prevent loss of IMEI.
Don't mess with any settings, and click Flash, and follow the instructions on screen.
That will return your phone to stock 14.1.G.1.534
Download the Z1 Locked Dual Recovery Installer from NUT's page --> http://nut.xperia-files.com/?dlid=WjEtbG9ja2VkZHVhbHJlY292ZXJ5Mi43LjEyMy1CRVRBLmZsYXNoYWJsZS56aXA=
Connect your phone to your PC and run the install.
That will root your phone, and install recovery.
From there you can then install whatever stock based ROM you want.
If you want your phone on KitKat 4.4.2, rooted, with recovery, then download the .757 files from NUT's download page.
You'd need the flashable zip --> http://nut.xperia-files.com/?dlid=QzY5MDNfMTQuMy5BLjAuNzU3LmZsYXNoYWJsZS56aXAudG9ycmVudA==
Download is via torrent.
Flash that zip from recovery.
The stripped part --> http://nut.xperia-files.com/?dlid=QzY5MDNfMTQuMy5BLjAuNzU3X1N0cmlwcGVkLmZ0Zg==
Flash that from Flashtool
That should be it.
Unless your bootloader is unlocked, do not try to flash anything other than stock based roms as it won't work, and will brick your phone.
Hope that helps :good:
Click to expand...
Click to collapse
Bootloader is unlocked I have flashed firmware before but not rooted.
My main reason for wanting to root was to get rid of apps I dont want like the google ones.
Do you already have a recovery installed?
If not, installing the Z1 locked dual recovery will also root your phone. Just make sure USB debugging is turned on, plug your phone in normally, and click install.
As per my post above, I've just flashed NUT's .534 ftf, booted up, then ran the recovery installer, and it's working well.
I can boot into recovery, and have already done a nandroid backup. Best to do that before anything else.
All I have to do now is choose a rom and flash it.
In all honesty, if your bootloader is unlocked, I'd probably flash a custom kernel which has recovery and root already. I don't know much about flashing with unlocked bootloaders as I don't intend to unlock mine just yet.
Did you backup your TA partition before unlocking?
MickieH said:
Do you already have a recovery installed? No
If not, installing the Z1 locked dual recovery will also root your phone. Just make sure USB debugging is turned on, plug your phone in normally, and click install.
As per my post above, I've just flashed NUT's .534 ftf, booted up, then ran the recovery installer, and it's working well.
I can boot into recovery, and have already done a nandroid backup. Best to do that before anything else.
All I have to do now is choose a rom and flash it.
In all honesty, if your bootloader is unlocked, I'd probably flash a custom kernel which has recovery and root already. I don't know much about flashing with unlocked bootloaders as I don't intend to unlock mine just yet.
Did you backup your TA partition before unlocking?
Click to expand...
Click to collapse
No
If I flash a custom kernel do I just use flashtool?
Q&A for Bootstack (KK and L) for L90
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Bootstack (KK and L) for L90. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
what can we do with bootstack ?
leandro_sousa said:
what can we do with bootstack ?
Click to expand...
Click to collapse
Bootstack is a bunch of files deep inside the phone. They are responsible for turning device ON and OFF, having SIM card support or download mode for flashing .kdz systems.
If you want to use stock KitKat or any customROM (KK or L) you need KitKat bootstack.
If you want to use stock Lollipop you need Lollipop bootstack.
Hi,
At the moment I'm running stock lollipop on a d405N. The Phone is also rooted, and i've unlocked bootloader and flashed TWRP 2.8.6.0.
After flashing your KK bootstack, can I immediately flash a custom Lollipop rom and Gapps, and if so will my waveband work?????
grey heron said:
Hi,
At the moment I'm running stock lollipop on a d405N. The Phone is also rooted, and i've unlocked bootloader and flashed TWRP 2.8.6.0.
After flashing your KK bootstack, can I immediately flash a custom Lollipop rom and Gapps, and if so will my waveband work?????
Click to expand...
Click to collapse
Yes. That's exactly for what bootstacks are made for.
If you will have any problems after using those files, let me know.
Also I would appreciate information if it worked so I could mark it as stable.
Xemidra said:
Yes. That's exactly for what bootstacks are made for.
If you will have any problems after using those files, let me know.
Also I would appreciate information if it worked so I could mark it as stable.
Click to expand...
Click to collapse
Thanks for your quick reply,
I see i made an error, it should be baseband not waveband
A few more questions though, before flashing your bootstack should I do a clean wipe?
Also, captivate king says: quote: Flash this after flashing my ROM, and you should be good to go, does the order in which I flash matter or not????
Thanks in advance,
grey heron said:
Thanks for your quick reply,
I see i made an error, it should be baseband not waveband
A few more questions though, before flashing your bootstack should I do a clean wipe?
Also, captivate king says: quote: Flash this after flashing my ROM, and you should be good to go, does the order in which I flash matter or not????
Thanks in advance,
Click to expand...
Click to collapse
I figured out that you meant baseband
It's not necessary to do a wipe. Changing bootstack does not affect /system, /data and /cache partitions, but if you'll have problems with your customROM you should of course start with a wipe.
There is no order in which you should flash your bootstack and ROM. I firstly flashed bootstack (while being on stock Lollipop) and restarted my phone to see if it worked. I had no SIM support so I knew that my flash was successful. Then I flashed CM.
One more important thing is that you cannot restart you phone if flashing bootstack fail. Also it's recommended to flash bootstack before you boot your customROM for the first time to eliminate any possible bugs caused by wrong baseband file.
If you have any more questions feel free to ask them.
Xemidra said:
I figured out that you meant baseband
It's not necessary to a wipe. Changing bootstack does not affect /system, /data and /cache partitions, but if you'll have problems with your customROM you should of course start with a wipe.
There is no order in which you should flash your bootstack and ROM. I firstly flashed bootstack (while being on stock Lollipop) and restarted my phone to see if it worked. I had no SIM support so I knew that my flash was successful. Then I flashed CM.
One more important thing is that you cannot restart you phone if flashing bootstack fail. Also it's recommended to flash bootstack before you boot your customROM for the first time to eliminate any possible bugs caused by wrong baseband file.
If you have any more questions feel free to ask them.
Click to expand...
Click to collapse
Hi again,
both bootstacks for D405N worked for me, no more problems with baseband and wifi, :good:so thanks again.
I was just wondering, why all the files in the bootstack? Wouldn't just changing the modem be sufficient? I know i'm showing my ignorance, but just when I think I've figured things out, I get back to square one
grey heron said:
Hi again,
both bootstacks for D405N worked for me, no more problems with baseband and wifi, :good:so thanks again.
I was just wondering, why all the files in the bootstack? Wouldn't just changing the modem be sufficient? I know i'm showing my ignorance, but just when I think I've figured things out, I get back to square one
Click to expand...
Click to collapse
It's for compatibility reasons. To make sure that everything is working fine I changed all files. It's less secure but more effective.
Hi Xemidra and everyone else.
I have used this for about 12-14 times now, going from stock LP to custom ROM and back, and as far as I Know it's working without any problems.
It's a great timesaver, but wouldn't it be better that ROMs have LP as a base instead of KK, so that using bootstacks or other or reflashing KK wouldn't be needed?
Is it something that a ROM chef could do?? Or is this a CM thing???
Another thought, the modem file used. I've read somewhere that its not just the variant, but that different regions, countries etc. can have different (optimal) modem files, ie what would work great for me in Holland, might be unacceptable for someone in say Brazil??? Anybody know more about this??? I've tried searching for this article again, but couldn't find it. I use google, anybody know a better search engine for these type of querries?
grey heron said:
It's a great timesaver, but wouldn't it be better that ROMs have LP as a base instead of KK, so that using bootstacks or other or reflashing KK wouldn't be needed?
Click to expand...
Click to collapse
Yes, it would be. You need to contact you ROM developer about this. I can't do anything about that.
Which bootstacks did you use ?
Another thought, the modem file used. I've read somewhere that its not just the variant, but that different regions, countries etc. can have different (optimal) modem files, ie what would work great for me in Holland, might be unacceptable for someone in say Brazil???
Click to expand...
Click to collapse
Maybe. I haven't head anything about that. No one complaint about quality of calls etc. I believe that different bootstacks for different variants are enough. Countrys from which I use the .kdz file to create bootstack are random.
i have D410_v20A stock rom rooted
what file can i use to first unlock my bootloader can i use D410_v20b_patched_aboot
no one helped me on this
my question is can i use any D410 hacked aboot to unlock my bootloader or what
please help i want to start try some new roms
http://forum.xda-developers.com/lg-l90/general/guide-guide-to-unlocking-bootloader-l90-t2852917
---------- Post added at 11:45 AM ---------- Previous post was at 11:28 AM ----------
i have D410_v20A stock rom rooted
what file can i use to first unlock my bootloader can i use D410_v20b_patched_aboot
no one helped me on this
my question is can i use any D410 hacked aboot to unlock my bootloader or what
please help i want to start try some new roms
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
i have D410_v20A stock rom rooted
what file can i use to first unlock my bootloader can i use D410_v20b_patched_aboot
no one helped me on this
my question is can i use any D410 hacked aboot to unlock my bootloader or what
please help i want to start try some new roms
Hi,
Am on a d405N myself, but I would stick to the same version aboot as your firmware: D410 v20a fw >>>> D410_v20a_patched_aboot. Stick with what works.
I wouldn't use just any aboot version. It might work, but why take the chance?
If you can't find the D410_v20a_patched_aboot, consider upgrading your fw to v20b first. Firmware is a bit easier to find.
It would be even better to flash a d410 v10 kdz, aand use a d410 v10 aboot. This way you wouldn't have to worry about using bootstacks.
Hope this helps, and stop spamming.
Odd Report
I'm here to thank you so much for putting all this information togetther, although it's possitive... my report should be a little odd, I want to report that BOOTSTACK_v1.4_D405N-10F helped me get my D400HN's (yes, D400HN) sim card running with Temasek's CM12... just in case someone is looking for an answer like this...
Thanks a lot!
dnuuk said:
I'm here to thank you so much for putting all this information togetther, although it's possitive... my report should be a little odd, I want to report that BOOTSTACK_v1.4_D405N-10F helped me get my D400HN's (yes, D400HN) sim card running with Temasek's CM12... just in case someone is looking for an answer like this...
Thanks a lot!
Click to expand...
Click to collapse
Your phone will from now present itself as D405n.
Because you seem like a nice guy I made a bootstack especially for you and you variant (D400hn).
It's not tested and it may be faulty. If you want to go ahead and download it. From what I read your variant has an unlocked bootloader so I included the stock one.
Xemidra said:
Your phone will from now present itself as D405n.
Because you seem like a nice guy I made a bootstack especially for you and you variant (D400hn).
It's not tested and it may be faulty. If you want to go ahead and download it. From what I read your variant has an unlocked bootloader so I included the stock one.
Click to expand...
Click to collapse
Awww! How nice and kind of you!!
I'll download it right away and give it a try tonight as soon as I get home... just a quick question... should I just flash it over the custom ROM I'm already using? or should I do a clean flash? If it's of any use, Im running CM12 Temasek Build.
Anyway, thanks a zillion for being so kind and dedicated, as well as for the patient for noob users like me :silly:
Hope you're well
dnuuk said:
Awww! How nice and kind of you!!
I'll download it right away and give it a try tonight as soon as I get home... just a quick question... should I just flash it over the custom ROM I'm already using? or should I do a clean flash? If it's of any use, Im running CM12 Temasek Build.
Anyway, thanks a zillion for being so kind and dedicated, as well as for the patient for noob users like me :silly:
Hope you're well
Click to expand...
Click to collapse
It shouldn't have any impact on your ROM but if you'll have any trouble then do the wipe.
Let me know if it worked for you.
Xemidra said:
It shouldn't have any impact on your ROM but if you'll have any trouble then do the wipe.
Let me know if it worked for you.
Click to expand...
Click to collapse
Well bad news... couldn't wait to get home and flashed it already dear @Xemidra, as soon as boot starts i get a nasty error that says Error: Boot certification verify, secure booting error. Cause: boot certification verify (and about 6 times de number "520")... And it turns off automatically three seconds after showing that screen, if I try Vol Down + Power, release and push the same combination again (as trying to get in Recovery Mode, TWRP in my case) the numbers changed to a 4 digit number (something like 5340 or so), tried three more times to enter recovery mode and I get the factory reset confirmation but as soon as I accept on YES the phone turns off completely and won't turn back or respond (unless I take the battery off and put it back on)
Any ideas on how to come back to life? KDZ? I had a lot of issues with KDZ before, couldn't get the LG software to recognize my phone at all
Any suggestion would be greatly appreciated, thanks
dnuuk said:
Well bad news... couldn't wait to get home and flashed it already dear @Xemidra, as soon as boot starts i get a nasty error that says Error: Boot certification verify, secure booting error. Cause: boot certification verify (and about 6 times de number "520")... And it turns off automatically three seconds after showing that screen, if I try Vol Down + Power, release and push the same combination again (as trying to get in Recovery Mode, TWRP in my case) the numbers changed to a 4 digit number (something like 5340 or so), tried three more times to enter recovery mode and I get the factory reset confirmation but as soon as I accept on YES the phone turns off completely and won't turn back or respond (unless I take the battery off and put it back on)
Any ideas on how to come back to life? KDZ? I had a lot of issues with KDZ before, couldn't get the LG software to recognize my phone at all
Any suggestion would be greatly appreciated, thanks
Click to expand...
Click to collapse
I can get to Download mode, but it only says ROOTED (In red) and an user number i.e. USER B47, but LG Flash Tool won't recognize the phone (the drivers are fine, the computer does recognize the phone, not LG Flash tool 2014
Any aditional ideas or should I just forget I had a phone?
dnuuk said:
I can get to Download mode, but it only says ROOTED (In red) and an user number i.e. USER B47, but LG Flash Tool won't recognize the phone (the drivers are fine, the computer does recognize the phone, not LG Flash tool 2014
Any aditional ideas or should I just forget I had a phone?
Click to expand...
Click to collapse
Try to use LG Mobile Support Tool ? It always worked for me. Make sure you really have all the drivers installed.
It will flash the original .kdz meant for your phone.
Sorry for all the trouble I guess that the bootloader was locked ? or it needed to be unlocked using oem-unlocked feature.
Hi all,
I havnt flashed a device since the first android ROMS for the HTC HD2, so that gives you an idea of how rusty I am, so please bare with me. I've been reading and searching for hours and my eyes feel like they are bleeding so I'm typing this plea for help whle I atill have some vision.
I ve got a c6903 z1 running the latest 5.1.1 update. stock kernel etc, locked bootloader.
I was on 5.02 rooted and now want to root 5.1.1
After lots of reading I realise that I need to downgrade to 4.4.4 kitkat, then root then install dual recovery, then installl a pre rooted 5.1.1... FIRSTLY - Does this sound right? are these the right steps to root 5.1.1?
Secondly, It took me a while finding Generic .108 ftf files but now I've found a few (through the ftf 'mega thread') and dont know which one I need... the options are:
C6903_14.4.A.0.108_1276-7939_R3C Generic MY.ftf 1060174KB
C6903_14.4.A.0.108_Customized KR.ftf 948416KB
C6903_14.4.A.0.108_Customized UK.ftf 1034553KB
C6903_14.4.A.0.108_Generic-MEA_1277-2880_R5C.ftf 1010011KB
C6903_14.4.A.0.108_Generic FR 1276-5833_R5C.ftf 1019704KB
C6903_14.4.A.0.108_Generic IT 1276-0557.ftf 1050780KB
C6903_14.4.A.0.108_Generic RU 1276-7743.ftf 973615KB
C6903_14.4.A.0.108_Generic_SG_1276-7937_R3C.ftf 1048335KB
Will any of these work considering I'm not staying on 4.4.4?
I assumed I could safely use the 'UK' file from the above list but then got paranoid I might brick my z1 by flashing a Ukranian ROM lol.
I've now got 'the fear' and am afraid I might **** this whole process up and brick my device.
which reminds me, one last thing... Ive downloaded the official SONY Flashtool (ver. 0.9.19.8).. is this the right tool for the job? I seem to remember reading that the official flashtool only works on unlocked bootloaders, but I've read so much im confused as hell at this point.
Sorry for the long post,
Any help would be greatly appreciated.
Correct. There is no direct root for 5.1.1 currently. You could also downgrade to 5.0.2 instead, it doesn't really make a difference between that and 4.4.
It doesn't really matter what your interim ROM is as long as you do a clean flash when updating to 5.1.1 again.
Flashtool is the correct tool to be using. It has a utility called XperiFirm built it. You can use that to get any FTF that's publically available so that you don't have to depend on FTF threads.
The only way to have rooted 5.1.1 is with a pre-rooted zip, so you'll have to use PRFCreator to create that zip if there isn't one already posted for the specific variant you want to use.
thesweeney80 said:
Hi all,
I havnt flashed a device since the first android ROMS for the HTC HD2, so that gives you an idea of how rusty I am, so please bare with me. I've been reading and searching for hours and my eyes feel like they are bleeding so I'm typing this plea for help whle I atill have some vision.
I ve got a c6903 z1 running the latest 5.1.1 update. stock kernel etc, locked bootloader.
I was on 5.02 rooted and now want to root 5.1.1
After lots of reading I realise that I need to downgrade to 4.4.4 kitkat, then root then install dual recovery, then installl a pre rooted 5.1.1... FIRSTLY - Does this sound right? are these the right steps to root 5.1.1?
Secondly, It took me a while finding Generic .108 ftf files but now I've found a few (through the ftf 'mega thread') and dont know which one I need... the options are:
C6903_14.4.A.0.108_1276-7939_R3C Generic MY.ftf 1060174KB
C6903_14.4.A.0.108_Customized KR.ftf 948416KB
C6903_14.4.A.0.108_Customized UK.ftf 1034553KB
C6903_14.4.A.0.108_Generic-MEA_1277-2880_R5C.ftf 1010011KB
C6903_14.4.A.0.108_Generic FR 1276-5833_R5C.ftf 1019704KB
C6903_14.4.A.0.108_Generic IT 1276-0557.ftf 1050780KB
C6903_14.4.A.0.108_Generic RU 1276-7743.ftf 973615KB
C6903_14.4.A.0.108_Generic_SG_1276-7937_R3C.ftf 1048335KB
Will any of these work considering I'm not staying on 4.4.4?
I assumed I could safely use the 'UK' file from the above list but then got paranoid I might brick my z1 by flashing a Ukranian ROM lol.
I've now got 'the fear' and am afraid I might **** this whole process up and brick my device.
which reminds me, one last thing... Ive downloaded the official SONY Flashtool (ver. 0.9.19.8).. is this the right tool for the job? I seem to remember reading that the official flashtool only works on unlocked bootloaders, but I've read so much im confused as hell at this point.
Sorry for the long post,
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Hey there! Welcome to the Z1 community
All you have to do is make sure you flash the ftf specific to your device. As long as it says C6903 in the ftf, you're good to go. all these locations are just country specific customizations with some apps and stuff. I'd say you can just flash the SG ftf for a mostly bloat free system.
In addition, you can't use the SONY flashtool (EMMA) unless you have an unlocked bootloader. I'd recommend you use flashtool (just google it) which lets you flash on both lock and unlocked bootloaders. Once you flash KK, use one of the rooting programs (Turn on USB debugging, and connect it to your computer, run the application and go through the steps. Let me know if you need help on what method of root to use.)
Once rooted, you should have a recovery, which should let you flash a prerooted zip easily.
If you have an unlocked bootloader, just flash any custom kernel through fastboot, boot into its recovery By pressing vol up or down at boot logo) and flash the zip.
Final tip is, make sure you have the prerooted zip on your sd card before you flash a custom kernel, as not all can mount to the PC from the reovery and flashing an incompatible kernel (such as a 4.4.4 kernel on a 5.0 rom) won't let you boot into the ROM.
Feel free to ask if you have any doubts, come across any issues, or need any help at all.
SOURCE: I flashed a customized TW ftf on a Singapore bought C6902 which I'm using in India with no issues at all.
xasbo said:
Correct. There is no direct root for 5.1.1 currently. You could also downgrade to 5.0.2 instead, it doesn't really make a difference between that and 4.4.
It doesn't really matter what your interim ROM is as long as you do a clean flash when updating to 5.1.1 again.
Flashtool is the correct tool to be using. It has a utility called XperiFirm built it. You can use that to get any FTF that's publically available so that you don't have to depend on FTF threads.
The only way to have rooted 5.1.1 is with a pre-rooted zip, so you'll have to use PRFCreator to create that zip if there isn't one already posted for the specific variant you want to use.
Click to expand...
Click to collapse
Thanks for the quick reply mate. Sounds good, I might just go to 5.02 then as rooting that was fairly painless.
Ive already found a pre-rooted zip for stock 5.1.1 so I think I'm good to go on that one. Almost ready to dive in... thanks for clearing that up.
AnrgKrshn said:
Hey there! Welcome to the Z1 community
All you have to do is make sure you flash the ftf specific to your device. As long as it says C6903 in the ftf, you're good to go. all these locations are just country specific customizations with some apps and stuff. I'd say you can just flash the SG ftf for a mostly bloat free system.
In addition, you can't use the SONY flashtool (EMMA) unless you have an unlocked bootloader. I'd recommend you use flashtool (just google it) which lets you flash on both lock and unlocked bootloaders. Once you flash KK, use one of the rooting programs (Turn on USB debugging, and connect it to your computer, run the application and go through the steps. Let me know if you need help on what method of root to use.)
Once rooted, you should have a recovery, which should let you flash a prerooted zip easily.
If you have an unlocked bootloader, just flash any custom kernel through fastboot, boot into its recovery By pressing vol up or down at boot logo) and flash the zip.
Final tip is, make sure you have the prerooted zip on your sd card before you flash a custom kernel, as not all can mount to the PC from the reovery and flashing an incompatible kernel (such as a 4.4.4 kernel on a 5.0 rom) won't let you boot into the ROM.
Feel free to ask if you have any doubts, come across any issues, or need any help at all.
SOURCE: I flashed a customized TW ftf on a Singapore bought C6902 which I'm using in India with no issues at all.
Click to expand...
Click to collapse
Thanks for the in depth reply mate much appreciated. And thanks for the welcome, cheers
Ive got a locked bootloader so I'll check out that unnoficial flashtool, thanks.
Now here is where my confusion and lack of knowledge becomes another problem... You say that after rooting kitkat (using something like 'easy root tool'?) I "should have a recovery, which should let you flash a prerooted zip easily.".......
I was under the impression that after rooting kitkat I would have to install
'XZ Dual Recovery' to let me flash the pre-root zip.
Do I not have to install XZ dual recovery?
Thanks again for all your help... just trying to clear up the details before I start the whole process.
Cheers mate.
thesweeney80 said:
Thanks for the in depth reply mate much appreciated. And thanks for the welcome, cheers
Ive got a locked bootloader so I'll check out that unnoficial flashtool, thanks.
Now here is where my confusion and lack of knowledge becomes another problem... You say that after rooting kitkat (using something like 'easy root tool'?) I "should have a recovery, which should let you flash a prerooted zip easily.".......
I was under the impression that after rooting kitkat I would have to install
'XZ Dual Recovery' to let me flash the pre-root zip.
Do I not have to install XZ dual recovery?
Thanks again for all your help... just trying to clear up the details before I start the whole process.
Cheers mate.
Click to expand...
Click to collapse
Some root kits will install a custom recovery for you, but it's so easy to just install XZDR, that's what I always do. XZDR will actually give you multiple recoveries to choose from (but TWRP is generally considered the best), but it also has some nice addition features like RIC killer (which allows you to have full root vs partial root).
I should also clarify my previous statement - XperiFirm is great for getting *new* firmware.. but you will either need to back up copies of old firmware for future use, or seek them out in threads if you need them later.
xasbo said:
Some root kits will install a custom recovery for you, but it's so easy to just install XZDR, that's what I always do. XZDR will actually give you multiple recoveries to choose from (but TWRP is generally considered the best), but it also has some nice addition features like RIC killer (which allows you to have full root vs partial root).
I should also clarify my previous statement - XperiFirm is great for getting *new* firmware.. but you will either need to back up copies of old firmware for future use, or seek them out in threads if you need them later.
Click to expand...
Click to collapse
ahhh, now that makes sense (re: some root solutions including a recovery), thank you for clearing that up.
One final thing (before I dive in and at least get KK installed+rooted)...
If I have to start reading one more subject I think my head will explode lol so If you could just clear up one thing about RIC Killer....
I want full root, not partial - do I have to mess with RIC Killer or can I leave it alone?
On the guide I am trying to follow; someone said they ended up 'half rooted' - would that be because of RIC killer or user error when creating the pre-rooted zip?
just dont want to go through all this and end up only being half rooted haha, cheers.
edit: ok so after checking flashtool it seems I already have the right one (NOT SONY)... I have version 0.9.19.7 But there are two warnings (pasted below) on the flashtool thread.
Does the first warning simply mean 'Use the latest version'??
I have no clue about the second warning...do i just uncheck the uption regarding simlock.ta IF it is in the list of options when I flash kitkat? I have no clue if my ftf file includes simlock.ta.
Both warnings mention bricks and hard bricks so I'm taking them pretty seriously haha.
Any advice on these warnings would be great, thanks for your patience.
"WARNING : Since Xperia Z, sony added a new set of files I called bootbundle. Those files can be bundled from 0.9.13 and can be flashed from 0.9.13 only. To all those flashing devices from Z edition to all after Z, it is highly advised to use 0.9.13 and to be sure FTF you flash contain the bootbundle set. I've been reported of hard bricks because of missing such set of files from bundles.
I WANT TO GET YOUR ATTENTION ABOUT THE LATEST BRANCH 0.9.19. Without FSC, the tool will by default include simlock.ta if this file is present in the FTF. The result will be a bricked phone
As a workaround, until I release a patch, please please tick the exlude simlock.ta if you see it in the list.
0.9.19.6 fixes the simlock.ta issue. This file is by default excluded. Then it will not be flashed until you explicitely untick the exlcude simlock box. Do it at your own risk."
thesweeney80 said:
ahhh, now that makes sense (re: some root solutions including a recovery), thank you for clearing that up.
One final thing (before I dive in and at least get KK installed+rooted)...
If I have to start reading one more subject I think my head will explode lol so If you could just clear up one thing about RIC Killer....
I want full root, not partial - do I have to mess with RIC Killer or can I leave it alone?
On the guide I am trying to follow; someone said they ended up 'half rooted' - would that be because of RIC killer or user error when creating the pre-rooted zip?
just dont want to go through all this and end up only being half rooted haha, cheers.
Click to expand...
Click to collapse
Even if you don't have a RIC killer installed, most root stuff will work fine. On the Z1, the RIC will prevent you from doing specific things, most importantly mounting /system as writable, which is necessary for certain type of advanced modifications.
However, if you install XZDR, you'll get the custom recovery + the RIC killer. I would just do that.
edit: ok so after checking flashtool it seems I already have the right one (NOT SONY)... I have version 0.9.19.7 But there are two warnings (pasted below) on the flashtool thread.
Does the first warning simply mean 'Use the latest version'??
I have no clue about the second warning...do i just uncheck the uption regarding simlock.ta IF it is in the list of options when I flash kitkat? I have no clue if my ftf file includes simlock.ta.
Both warnings mention bricks and hard bricks so I'm taking them pretty seriously haha.
Any advice on these warnings would be great, thanks for your patience.
"WARNING : Since Xperia Z, sony added a new set of files I called bootbundle. Those files can be bundled from 0.9.13 and can be flashed from 0.9.13 only. To all those flashing devices from Z edition to all after Z, it is highly advised to use 0.9.13 and to be sure FTF you flash contain the bootbundle set. I've been reported of hard bricks because of missing such set of files from bundles.
I WANT TO GET YOUR ATTENTION ABOUT THE LATEST BRANCH 0.9.19. Without FSC, the tool will by default include simlock.ta if this file is present in the FTF. The result will be a bricked phone
As a workaround, until I release a patch, please please tick the exlude simlock.ta if you see it in the list.
0.9.19.6 fixes the simlock.ta issue. This file is by default excluded. Then it will not be flashed until you explicitely untick the exlcude simlock box. Do it at your own risk."
Click to expand...
Click to collapse
Correct, the warning is to just make sure you use a version later than 0.9.13; you're fine to use 0.9.19.7. It will tell you that .8 is out, but the change is not important to you. You don't need to do anything special regarding simlock.ta.
If you have an external SD card, copy everything you want to flash onto the phone before starting (5.1.1 prerooted, SuperSU, XZDR), so it's already there when you need it.
xasbo said:
Even if you don't have a RIC killer installed, most root stuff will work fine. On the Z1, the RIC will prevent you from doing specific things, most importantly mounting /system as writable, which is necessary for certain type of advanced modifications.
However, if you install XZDR, you'll get the custom recovery + the RIC killer. I would just do that.
Correct, the warning is to just make sure you use a version later than 0.9.13; you're fine to use 0.9.19.7. It will tell you that .8 is out, but the change is not important to you. You don't need to do anything special regarding simlock.ta.
If you have an external SD card, copy everything you want to flash onto the phone before starting (5.1.1 prerooted, SuperSU, XZDR), so it's already there when you need it.
Click to expand...
Click to collapse
THANKS.
So As long as I install XZDR I will have RIC killer and that will ensure a full root? thats great, cheers..
Thanks for clearing up the flashtool warnings too, very much appreciated.
As for your final tip about the SD card... do you mean copy everything to the SD card? or the phone? I'm ASSuming you mean the SD card as the phone memory will get wiped during flasshing if I clear everything? no?
Sorry mate I'm having a total brain-fart after everything Ive read, my comprehension skills are at an all time low lol. Tired.
Thanks again for all ya help mate, I'm just about ready to get this crap done... and then once Ive finished I know I'll be thinking 'wtf was all the panicking about? lol.
THANKS.
thesweeney80 said:
THANKS.
So As long as I install XZDR I will have RIC killer and that will ensure a full root? thats great, cheers..
Thanks for clearing up the flashtool warnings too, very much appreciated.
As for your final tip about the SD card... do you mean copy everything to the SD card? or the phone? I'm ASSuming you mean the SD card as the phone memory will get wiped during flasshing if I clear everything? no?
Sorry mate I'm having a total brain-fart after everything Ive read, my comprehension skills are at an all time low lol. Tired.
Thanks again for all ya help mate, I'm just about ready to get this crap done... and then once Ive finished I know I'll be thinking 'wtf was all the panicking about? lol.
THANKS.
Click to expand...
Click to collapse
Make sure you flash SuperSU and XZDR at the same time. If you do not, it will not work correctly (still only partial root). If you make your own pre-root ZIP, you can roll them into it and do it in one fell swoop.
Yeah. External SD card = not the phone. If you do a clean flash (which you should), you will be wiping the phone storage.
xasbo said:
Make sure you flash SuperSU and XZDR at the same time. If you do not, it will not work correctly (still only partial root). If you make your own pre-root ZIP, you can roll them into it and do it in one fell swoop.
Yeah. External SD card = not the phone. If you do a clean flash (which you should), you will be wiping the phone storage.
Click to expand...
Click to collapse
You're the man, man...THANKS. :highfive:
I'll check the pre-root zip I found and if it doesnt have Supersu included I'll make my own and include XZDR too - I like the idea of having things 'slipstreamed' into one flash - thanks for the tip.
Thanks a lot for all your help in calming all my little worries about this process,,, very much appreciated.
I'll do the whole lot tomorrow and report back... thanks again.
Suggestion - since you are re-learning and your goal at the moment is to have a rooted 5.1.1, I suggest you download and install Flashtool for windows. Go to http://www.flashtool.net/index.php. Now in Flashtool, your need to install the appropriate drivers for your device/s. Instructions searching (I'm doing my lunch while typing reply - lol). Then use XperiFirm which is integrated in Flashtool. It has its own icon, just click it so you can download a 5.0.2 FTF for yor region. Install that 5.0.2 FTF on your phone using Flashtool (Flash it Baby! Flash it!) Then you can root 5.0.2 with ease using Kingroot. Replace Kingroot with SuperSU. Then install NUT's Dual recovery. Then you can download any of the pre-rooted 5.1.1 FTFs XDA peeps are putting up under the General section and boom. You are now on 5.1.1. with root.
Deathschythe33 said:
Suggestion - since you are re-learning and your goal at the moment is to have a rooted 5.1.1, I suggest you download and install Flashtool for windows. Go to http://www.flashtool.net/index.php. Now in Flashtool, your need to install the appropriate drivers for your device/s. Instructions searching (I'm doing my lunch while typing reply - lol). Then use XperiFirm which is integrated in Flashtool. It has its own icon, just click it so you can download a 5.0.2 FTF for yor region. Install that 5.0.2 FTF on your phone using Flashtool (Flash it Baby! Flash it!) Then you can root 5.0.2 with ease using Kingroot. Replace Kingroot with SuperSU. Then install NUT's Dual recovery. Then you can download any of the pre-rooted 5.1.1 FTFs XDA peeps are putting up under the General section and boom. You are now on 5.1.1. with root.
Click to expand...
Click to collapse
cheers mate, I appreciate all the help I can get lol.
I decided to go with 5.0.2 instead of kitkat, but when I click on the .270 firmware links in xperifirm I get an error which says:
"Incomplete Firmware.
The following files are missing on the server:
fsp.zip.
Proceed with caution"
I clicked on the latest 5.1.1 firmwares and none of them give this error... so does the error simply mean that .270 is not the latest version? I couldnt find the answer in google. Are thes firmwares without fsp.zip safe to flash?
Thanks again.
edit: hmmm looks like i'll have to flash 4.4 instead.
When I try to download a .270 (5.0.2) firmware in xperifirm; it stops downloading after a few seconds and says a reuired file is missing
If I try to download one of the .368 firmwares it downloads ok
edit 2: F*ck my life... Not enough space on C: for unpacked ftf file (Small c partition on SSD) ... so unless there is a way for flashtool to flash from d:\...\firmware im screwed. I'll try compressing (NTFS) the c drive and hope thats enough
thesweeney80 said:
edit 2: F*ck my life... Not enough space on C: for unpacked ftf file (Small c partition on SSD) ... so unless there is a way for flashtool to flash from d:\...\firmware im screwed. I'll try compressing (NTFS) the c drive and hope thats enough
Click to expand...
Click to collapse
There is a solution, but it's slightly complicated. Proceed at your own risk, maybe do a little research to make sure you understand what I'm tell you to do.
1) Browse to C:\Users\<username>\. if you aren't already, show hidden files and folders.
2) Grab the .flashTool directory and move it onto a drive with sufficient free space (e.g., D:\.flashTool).
3) Go to Start and type cmd into the search field. When cmd.exe shows up, right-click and select Run As Administrator.
4) Change to the user directory ("cd C:\Users\<username>").
5) Make a junction point named .flashTool pointed to where ever you moved the folder (e.g., "mklink /j .flashTool D:\.flashTool").
This will make flashtool think that its settings/data folder is in the right place, when really it's just a fake folder linked somewhere else.
xasbo said:
There is a solution, but it's slightly complicated. Proceed at your own risk, maybe do a little research to make sure you understand what I'm tell you to do.
1) Browse to C:\Users\<username>\. if you aren't already, show hidden files and folders.
2) Grab the .flashTool directory and move it onto a drive with sufficient free space (e.g., D:\.flashTool).
3) Go to Start and type cmd into the search field. When cmd.exe shows up, right-click and select Run As Administrator.
4) Change to the user directory ("cd C:\Users\<username>").
5) Make a junction point named .flashTool pointed to where ever you moved the folder (e.g., "mklink /j .flashTool D:\.flashTool").
This will make flashtool think that its settings/data folder is in the right place, when really it's just a fake folder linked somewhere else.
Click to expand...
Click to collapse
Thanks again mate. Ive done that once before and forgotten all about it.
This time I just compressed c:\ with NTFS compression and it gained just enough space (F*ck you Winsxs).
But the above info will surely come in handy in future, so once again: Thanks! Tou've been a big help.
Just about to install XZDR and a pre-rooted 5.1.1 :fingers-crossed: Cheers mate :good:
thesweeney80 said:
Thanks again mate. Ive done that once before and forgotten all about it.
This time I just compressed c:\ with NTFS compression and it gained just enough space (F*ck you Winsxs).
But the above info will surely come in handy in future, so once again: Thanks! Tou've been a big help.
Just about to install XZDR and a pre-rooted 5.1.1 :fingers-crossed: Cheers mate :good:
Click to expand...
Click to collapse
What a way you went through.
As you already were on 5.0.2 and rooted you just had to install xzdr to your phone.
After that you could flash one of the Pre-Rooted zip files you need.
Sent from my C6903 using XDA Free mobile app
motorazrv3 said:
What a way you went through.
As you already were on 5.0.2 and rooted you just had to install xzdr to your phone.
After that you could flash one of the Pre-Rooted zip files you need.
Sent from my C6903 using XDA Free mobile app
Click to expand...
Click to collapse
well I know that now dont I? :silly: haha
yeah I was on a kingrooted 5.02, and should have just installed XZDR etc but I upgraded to 5.1.1 ASSunming I could root it with kingroot again, big mistake.
If I had read about kingroot not working on 5.1.1 I could have saved 24hrs worth of headaches.
Oh well... all done now. Rooted on 5.1.1, busybox installed and all
Now begins the long process of re-installing and customizing all over again *yipee*
No doubt I will go through all this again in a few weeks when I decide to unlock the BL and install a customROM And kernel
THIS is why I spent a few years with a 'dumb' phone after my HD2... ohhh the joys of flashing.
BIG Thanks to evryone who helped me out on this especially Xasbo, Gamer4Life and Deathschythe33. CHEERS
:good: glad you got it sorted.
Please Xasbo help, I Have loop all the time
xasbo said:
:good: glad you got it sorted.
Click to expand...
Click to collapse
Please, kan you help, I flashed downgrading my C6903 from .386 to C6903_14.4.A.0.108_Stripped, and got loops. Then I Tried again with several firmwares.108 and .386 and got the same result Loop :crying::crying:
I flashed with C6903_14.4.A.108 Generic SG and everything went fine, I got this massage:"NFC Firmware updating" "Don´t turn off you device", and got loop. Oh my god???? What Iam doing wrong?
Any suggestion. Thank you
asswembler said:
Please, kan you help, I flashed downgrading my C6903 from .386 to C6903_14.4.A.0.108_Stripped, and got loops. Then I Tried again with several firmwares.108 and .386 and got the same result Loop :crying::crying:
I flashed with C6903_14.4.A.108 Generic SG and everything went fine, I got this massage:"NFC Firmware updating" "Don´t turn off you device", and got loop. Oh my god???? What Iam doing wrong?
Any suggestion. Thank you
Click to expand...
Click to collapse
Hmm. I've never seen that NFC message before. Did it look like that firmware update completed before the phone restarted?
Are you still able to flash anything to the phone? What are you trying to accomplish?
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Zeuszoos said:
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Click to expand...
Click to collapse
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
dottyparent said:
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
Click to expand...
Click to collapse
First, thank you for responding!
I used that page on my last Note 4 (it died, hardware failure), after I tried MM but hated the Ext SD handling and so I went back down to the T2 KK ROM on that page and it worked fine (I installed the entire ROM). But my replacement Note 4 that just arrived already had MM as I said and updated to a Build # I haven't seen.
But if you look at the Build #, T-Mobile seems to have (via the Updates) turned the phone into a "N910T3" instead of a "N910T". Weird! Especially since I'm with MetroPCS. Hahaha! They're owned by T-Mobile though, use the same Towers, etc..
Anyway, I'd like to try and stick with MM this time around.
But you did hit one of my grey areas.
Let me see if I understand you correctly... If I were to Flash just the KK BL, my phone would/would not continue to Boot into Marshmallow as it is now, if I Flashed nothing but that?
Or am I correct in saying that your method would mean taking the phone back, so that it would be running KitKat and then going back up to Marshmallow using a different ROM that TWRP will be able to go onto?
The reason I'm fuzzy, is because I've never Flashed just a BootLoader, so I'm not sure what would happen if I Flash just the KK BootLoader onto an MM ROM and Reboot???
Thank you again for your time!
Zeuszoos said:
First, thank you for responding!
I used that page on my last Note 4 (it died, hardware failure), after I tried MM but hated the Ext SD handling and so I went back down to the T2 KK ROM on that page and it worked fine (I installed the entire ROM). But my replacement Note 4 that just arrived already had MM as I said and updated to a Build # I haven't seen.
But if you look at the Build #, T-Mobile seems to have (via the Updates) turned the phone into a "N910T3" instead of a "N910T". Weird! Especially since I'm with MetroPCS. Hahaha! They're owned by T-Mobile though, use the same Towers, etc..
Anyway, I'd like to try and stick with MM this time around.
But you did hit one of my grey areas.
Let me see if I understand you correctly... If I were to Flash just the KK BL, my phone would/would not continue to Boot into Marshmallow as it is now, if I Flashed nothing but that?
Or am I correct in saying that your method would mean taking the phone back, so that it would be running KitKat and then going back up to Marshmallow using a different ROM that TWRP will be able to go onto?
The reason I'm fuzzy, is because I've never Flashed just a BootLoader, so I'm not sure what would happen if I Flash just the KK BootLoader onto an MM ROM and Reboot???
Thank you again for your time!
Click to expand...
Click to collapse
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
dottyparent said:
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
Click to expand...
Click to collapse
Is this a method you've tried B4?
I'll check out that thread and see if they've got an MM Modem too.
Isn't that the "EFS" part of a ROM? If so, there are EFS Backup apps. But they may require Root though.
TTYL
Zeuszoos said:
Is this a method you've tried B4?
I'll check out that thread and see if they've got an MM Modem too.
Isn't that the "EFS" part of a ROM? If so, there are EFS Backup apps. But they may require Root though.
TTYL
Click to expand...
Click to collapse
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
dottyparent said:
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
Click to expand...
Click to collapse
dottyparent said:
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
Click to expand...
Click to collapse
There is an MM ROM that is Rooted and has TWRP built in, but I don't know if it would Flash over this with Odin or not
I am also considering trying the entire KK T2 ROM again to go down to KK and then Flashing that MM ROM.
It has both Odexed & DeOdexed. If I remember right, DeOdexed is the better choice, right?
Thanks for all your time and help!
Dave
Hi,
You know what's sad, is that if I could somehow Roog it without TWRP, then I could use the way awesome "Flashify" app to try to get TWRP on this phone! <lol>
Dave
dottyparent said:
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
Click to expand...
Click to collapse
dottyparent said:
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
Click to expand...
Click to collapse
Could you please tell me where the files are that you used, so that I can have the exact same ones to work with? I looked at the link you provided, but I couldn't find just the BootLoader in it. I saw where someone requested just the BootLoader and Modem (you?) and "Trex888" said he would upload them right away and provide a link, but I did not see one ever posted. Just the link for the entire ROM.
Btw, in Odin, if you're Flashing only the BootLoader, do you use the "BL" button instead of the "AP" (formerly "PDA") button? What about just the Modem (thru Recovery?)?
I just tried Flashing the entire T2 KK ROM that I had used to go back from MM to KK on my first Note 4, but this one wouldn't take that either. It immediately said "FAIL".
I'm sorry if I'm a pain. It's just that I'm disabled and constantly laying on my side, so a laptop is out for regular use and so this phone is my main and only communication with the outside world. What I'm saying is that it's not a hobby phone and I have to get it right, because (see below). So I don't want to Flash something that may not do it, so I want to exactly match what you did.
You see, I can only sit up to Flash from Odin on my Windows computer with my phone cabled to it for just so long because of my condition.
Not your problem, I know. But I'm explaining it to you so that you can understand that I'm not just trying to be lazy. But instead, I need to make sure I do exactly what worked for you, with exactly those files, because if something goes wrong, it could take me days of short time computer access due to my situation (too much overwhelming pain) to figure it out and get it (hopefully) fixed. So you can see the importance, no doubt.
This phone right now (see Build #) says it's a T3, but whatever works.
Right now, it's without Recovery so I can't Root it, so I can't get Write access to my Ext SD, etc.. I need to Root!
Also, this T3 MM ROM is having issues with the Display. Sometimes it'll get all chopped up and I have to Reboot.
So anyway, I need to get this done and I would very much appreciate your further help!
Thank You!!!
Dave
Zeuszoos said:
Could you please tell me where the files are that you used, so that I can have the exact same ones to work with? I looked at the link you provided, but I couldn't find just the BootLoader in it. I saw where someone requested just the BootLoader and Modem (you?) and "Trex888" said he would upload them right away and provide a link, but I did not see one ever posted. Just the link for the entire ROM.
Btw, in Odin, if you're Flashing only the BootLoader, do you use the "BL" button instead of the "AP" (formerly "PDA") button? What about just the Modem (thru Recovery?)?
I just tried Flashing the entire T2 KK ROM that I had used to go back from MM to KK on my first Note 4, but this one wouldn't take that either. It immediately said "FAIL".
I'm sorry if I'm a pain. It's just that I'm disabled and constantly laying on my side, so a laptop is out for regular use and so this phone is my main and only communication with the outside world. What I'm saying is that it's not a hobby phone and I have to get it right, because (see below). So I don't want to Flash something that may not do it, so I want to exactly match what you did.
You see, I can only sit up to Flash from Odin on my Windows computer with my phone cabled to it for just so long because of my condition.
Not your problem, I know. But I'm explaining it to you so that you can understand that I'm not just trying to be lazy. But instead, I need to make sure I do exactly what worked for you, with exactly those files, because if something goes wrong, it could take me days of short time computer access due to my situation (too much overwhelming pain) to figure it out and get it (hopefully) fixed. So you can see the importance, no doubt.
This phone right now (see Build #) says it's a T3, but whatever works.
Right now, it's without Recovery so I can't Root it, so I can't get Write access to my Ext SD, etc.. I need to Root!
Also, this T3 MM ROM is having issues with the Display. Sometimes it'll get all chopped up and I have to Reboot.
So anyway, I need to get this done and I would very much appreciate your further help!
Thank You!!!
Dave
Click to expand...
Click to collapse
Okay. Here is what I did exactly.
Download my Files here: https://1drv.ms/f/s!AJEa3D0cBAhIbQ
Stock 910T files here https://androidfilehost.com/?w=files&flid=20602
i guess if you need any other stock files sammobile works.
This will reset your phone!
1) Odin flash the AOG1 file. this turns the phone into a t2 phone.
2) Odin the ANK4 rom. this returns the phone to a 910t.
3) Boot into the ANK4 rom and download the MM update. This should land you on the first MM update, EPE3
4) Flash TWRP, thourgh AP, which should work. Might as well flash superSU or magisk.
At this point i would wipe everything and install a custom rom, but you could update to a newer boot loader and modem using the BL and CP buttons, respectively.
hope this helps
dottyparent said:
Okay. Here is what I did exactly.
Download my Files here: https://1drv.ms/f/s!AJEa3D0cBAhIbQ
Stock 910T files here https://androidfilehost.com/?w=files&flid=20602
i guess if you need any other stock files sammobile works.
This will reset your phone!
1) Odin flash the AOG1 file. this turns the phone into a t2 phone.
2) Odin the ANK4 rom. this returns the phone to a 910t.
3) Boot into the ANK4 rom and download the MM update. This should land you on the first MM update, EPE3
4) Flash TWRP, thourgh AP, which should work. Might as well flash superSU or magisk.
At this point i would wipe everything and install a custom rom, but you could update to a newer boot loader and modem using the BL and CP buttons, respectively.
hope this helps
Click to expand...
Click to collapse
Thank you for responding!
The OG1 is the T2 ROM that I had just tried and reported that unlike my previous Note 4, it would not Flash on this one to turn it into a KK T2. I also tried the other 2 ROMS to no avail.
I think it's because this one says it's a T3.
Thanks,
Dave
Zeuszoos said:
Thank you for responding!
The OG1 is the T2 ROM that I had just tried and reported that unlike my previous Note 4, it would not Flash on this one to turn it into a KK T2. I also tried the other 2 ROMS to no avail.
I think it's because this one says it's a T3.
Thanks,
Dave
Click to expand...
Click to collapse
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
No, I'm sorry, but you have to give me the answer.
All seriousness aside, I depreciate all your effort.
I can only think of one thing left to try... Go to Sammy's site and get the Lollipop 5.1.1 ROM and see what happens. It can't hurt to try, right?
I'll let ya know what happens and thank you again!
Happy Thanksgiving!
Dave
dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
Guess what? I decided to take a picture of my phone's screen after it Failed to let me Flash anything at all in Odin. I tried TWRP again and this time read what my phone responds with and it says the following:
Custom Binary (Recovery) Blocked By FRP LOCK
Does that mean anything to you?
TTYL
Zeuszoos said:
Guess what? I decided to take a picture of my phone's screen after it Failed to let me Flash anything at all in Odin. I tried TWRP again and this time read what my phone responds with and it says the following:
Custom Binary (Recovery) Blocked By FRP LOCK
Does that mean anything to you?
TTYL
Click to expand...
Click to collapse
Well I searched around XDA and it seems to be a problem exclusive to the T3. Try going to settings -> security and see if there is a option to disable resetting protection. Or see if there is a way to disable OEM locking. However it's probably not there. The only successful thread I found was this
https://forum.xda-developers.com/note-4/help/note-4-t-mobile-sm-n910t3-custom-binary-t3346840
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
If all else doesn't work, perhaps you could repartition your phone. You need a pit file and a few ROMs
Zeuszoos said:
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Click to expand...
Click to collapse
That's weird. I updated my N910T to EQI2 with Odin, rooted using CF-Auto-Root for N910T and then flashed TWRP 3.1.1 and I had no problems at all
dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
ShaDisNX255 said:
That's weird. I updated my N910T to EQI2 with Odin, rooted using CF-Auto-Root for N910T and then flashed TWRP 3.1.1 and I had no problems at all
Click to expand...
Click to collapse
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Zeuszoos said:
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Click to expand...
Click to collapse
That's because I have a n910t not a t3
Zeuszoos said:
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Click to expand...
Click to collapse
I upgraded from LL. The device was running 5.0.1 and now has 6.0.1
dottyparent said:
Well I searched around XDA and it seems to be a problem exclusive to the T3. Try going to settings -> security and see if there is a option to disable resetting protection. Or see if there is a way to disable OEM locking. However it's probably not there. The only successful thread I found was this
https://forum.xda-developers.com/note-4/help/note-4-t-mobile-sm-n910t3-custom-binary-t3346840
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
If all else doesn't work, perhaps you could repartition your phone. You need a pit file and a few ROMs
Click to expand...
Click to collapse
Thank you for looking! I found out what it is.
It's "Factory Reset Protection" (FRP)
What it does, is keep someone else from Factory Resseting your phone if they steal it. When they reset it, during setup, they have to type in the last Google Email and Password that the phone used, before they can set up theirs.
After reading that, I remembered having to put my Google Info in at two separate points and seeing it telling me to "Verify", but I was just blowing right through setup, not reading all of the small print. I mean hey, I had no idea that even existed and was just annoyed that I had to type the same thing twice!
It will only be found on phones that already have Lollipop and up on them out of the box and probably not all of them yet. And you don't have to worry about downloadable ROMS, so those who have phones that started with KitKat, or even early versions of Marshmallow 6.0 or 6.0.1 would not have seen this happen to them. Even those who updated to the same version of Mm that my phone has won't, if they started with KK or an older MM and then updated to it.
Again, this is something that your phone would have "Out of the Box" and the phone (not all) would have at least L on it.
Just FYI, it's not just Samsung, either.
Just FYI, I have confirmed this info. It is a fact.
Once I have an easy to do, working fix, hopefully without having to perform a Factory Reset, I will "Create A Thread" and as normal for me, write clear and easy, step by step (not leaving any out) instructions on how to "Unlock FRP" and then come back here and post a link to the thread. Hopefully this week.
This phone will not beat me!!!
TTYL
Dave