WARNING:- DO THIS AT YOUR OWN RISK I'll NOT BE RESPONSIBLE IF ANYTHING HAPPEN TO YOUR PHONE.
Its just for an Indian retail version only. yes, even after updating using the methods given below, you will get future updates
Notes -
Make sure that you are running completely stock version of android before applying the update. Do not try to apply the update with custom recoveries as it may hardbrick your device.Make sure that you have an indian retail version of the Moto E. You can check this by going to Settings->About Phone and scroll down and check if your system version is 21.12.40.condor_retaildsds.retaildsdsall.en.03reteu only.Make sure that you have atleast 50% battery before applying the update.Make a backup of all your apps and data before applying the update. (The update won’t wipe any data on your device, but still, it is safe to do so.)
Method 1*-
Download the update zip from here*http://bit.ly/1FCw68p*(Mediafire Link). This is a soak test update which was captured during the soak testing programme. Soak test isn’t*a*beta update or unstable. It’s just the final build but it rolls out to earlier than the global update.Download Motorola Update Services apk from here*http://bit.ly/1z9Lox0. Install it.Put the zip file which you’ve downloaded in the root of your internal memory as well as external memory. (Root means simply internal or external memory. It means that you have to place the file directly in the internal or external memory and not in any folder inside internal or external memory.)Reboot your phone 2-3 times and leave the device as it is for 15-20 minutes.Now go to Settings->About Phone->System Updates. You will see a screen stating “New system software available”. Click on “Yes I’m in”.Now, a download will begin and you can see that in the status bar. Once the download is complete, swipe down the notification bar and click on Install system update->Install now.Now, your phone will reboot into recovery and install the update update automatically for you. You just have to wait and watch for around 10-15 minutes.When you phone will start booting, just let it boot and don’t panic. Since this is a big software update, so it will take some time to boot up the device.
Method*2 -
I did found that a lot of users are not able to update their device by the above procedure. So I have found one another way of doing the update.Turn on USB debugging on your device. This can be done by doing the following steps – Go into Settings->About Phone and tap on build number 8-10 times. Now press back button and you will see a new option called developers options in the settings. Tap on developers option and enable USB debugging from there.Download motorola device manager from here*http://bit.ly/1MgFKCn.Install the device manager and connect your phone to the PC. The device manager will automatically install all the necessary drivers for you. Now disconnect the phone from the PC.Download minimal adb fastboot from here*http://bit.ly/1ArhfOe.Install it. Now go to My computer->C Drive->Programme Files(x86)->Minimal Adb and fastboot and copy the update zip there. (Do not rename it.)Now go into the recovery mode on your Moto E.This can be done as follows – Power Off your phone. Now press volume down and power buttons simultaneously for 10 seconds. This will take you to the bootloader.Now press volume down which will highlight ‘Recovery’ and then press volume up. Now your device will show up a dead android.Now press volume up first then, while pressing the volume up button, press power button. now release the power button first and then volume up button. Now you will see recovery.Now use volume down button to scroll to ‘Apply update from adb’ and then press power button to select it.Now connect your phone to the PC.Now, open Minimal adb and fastboot from the start menu and type the following command
Code:
adb sideload Blur_Version.21.12.40.condor_retaildsds.retaildsdsall.en.03.zip
This will update your phone.
Congratulations! You’ve got Lollipop on your Moto E! I guess this is the first guide out there.
Do thinks and post your phone screenshots who ever is updating.
Sent from my XT1022 using XDA Free mobile app
link is not working
please fix it
Its working perfectly
Sent from my XT1022 using XDA Free mobile app
Akhil137 said:
Its working perfectly
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
Can u plz check if u can mount script on link2sd app mine not working plz confirm...
will it work on unlocked bootloader
No it will not
Sent from my XT1022 using XDA Free mobile app
Akhil137 said:
No it will not
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
How much time dos it take to update using the ADB? I mean its stuck at Patching system files since 5 minutes.... i have followed all the procedures correctly....
Edit : Guys, It takes Around 15-17 mins. to complete the process in the phone itself... It may get stuck at patching system, etc.... But remember that do not power off the phone or unplug during adb transfer in any case
Regards
Andy
U have to put it in internal only no other thing works in it.
Sent from my XT1022 using XDA Free mobile app
Link
aksudhakar said:
please fix it
Click to expand...
Click to collapse
Use this much only
http://bit.ly/1FCw68p
@Akhil137 Thanks for this
Kindly edit your post to put a space between "http://bit.ly/1FCw68p" and "*(Mediafire" so it will not cause any trouble to members while clicking on the link and it will work perfectly and directly.
---------- Post added at 07:33 PM ---------- Previous post was at 07:29 PM ----------
Can anybody provide screenshot for this ?
Video Tutorial
Here's a Working Moto E Lollipop Update Tutorial: Here's a tutorial i made on How to Install Lollipop on Moto E as there seem to be many problems with people trying different methods: https://www.youtube.com/watch?v=Refs73469IA
Hello, is this an official update or soak test?
I own a Moto G but my friend asked me to keep track of this nonsense for the Moto E
XT1022 = Indian Moto E?
It's pure official stock build, correct? No modifications so that my noob friend can update to the next (possibly 5.1?) whenever it comes out if it does?
He's really doesn't know how to unlock bootloader or anything and doesn't even have a WiFi network so I'm going to download it for him and flash it via stock recovery...
Thanks in advance
Working
thanks for info...just flash it and work flawlessly :good:
failed!
all stock files but recently unrooted and flashed stock recovery. anyone knows the solution?
Chirag_1537 said:
Hello, is this an official update or soak test?
I own a Moto G but my friend asked me to keep track of this nonsense for the Moto E
XT1022 = Indian Moto E?
It's pure official stock build, correct? No modifications so that my noob friend can update to the next (possibly 5.1?) whenever it comes out if it does?
He's really doesn't know how to unlock bootloader or anything and doesn't even have a WiFi network so I'm going to download it for him and flash it via stock recovery...
Thanks in advance
Click to expand...
Click to collapse
This is not official update , Its just the soak test. So May be you should wait for one or two weeks for the official update.
rkmiks said:
This is not official update , Its just the soak test. So May be you should wait for one or two weeks for the official update.
Click to expand...
Click to collapse
Haha, I just spent the last half an hour attempting to explain to my friend how to install the update via adb haha. He's got that mob mentality. The update is there. It's installable. He must have it. Well I failed explaining to him so I'm going to his house tomorrow to upgrade it for him. I couldn't do the Motorola update.apk method. I have no idea how to do that. I have a question. Why doesn't the Moto E stock recovery install anything from SD card?! It works perfectly on my Moto G but here it just says installation from SD card complete.
Also, I'm using the Moto G soak test and it's pratically bug free. I'm sure this'll be fine too
Chirag_1537 said:
Haha, I just spent the last half an hour attempting to explain to my friend how to install the update via adb haha. He's got that mob mentality. The update is there. It's installable. He must have it. Well I failed explaining to him so I'm going to his house tomorrow to upgrade it for him. I couldn't do the Motorola update.apk method. I have no idea how to do that. I have a question. Why doesn't the Moto E stock recovery install anything from SD card?! It works perfectly on my Moto G but here it just says installation from SD card complete.
Click to expand...
Click to collapse
Well I actually updated from the sdcard . I had to copy the Update Zip to both internal and external sdcards and reboot and wait for one or two minutes after reboot and applied the update from the motorola update manager and it worked. Well this update is fine but there are issues about the limited internal storage and link2sd is also not perfectly working. And also if you need to downgrade to kitkat , just don't downgrade to 4.4.2 as it could brick your device as many people have reported.
Also, I'm using the Moto G soak test and it's pratically bug free. I'm sure this'll be fine too
Click to expand...
Click to collapse
I thought final update was already out for Moto G.
rkmiks said:
Well I actually updated from the sdcard . I had to copy the Update Zip to both internal and external sdcards and reboot and wait for one or two minutes after reboot and applied the update from the motorola update manager and it worked. Well this update is fine but there are issues about the limited internal storage and link2sd is also not perfectly working. And also if you need to downgrade to kitkat , just don't downgrade to 4.4.2 as it could brick your device as many people have reported.
Click to expand...
Click to collapse
Maybe I didn't name the file correctly so it wasn't reading it. I'm not sure why it didn't work.
Hahahaha should've told me that in Jan. I bricked my device exactly by downgrading to 4.4.2. It's common sense why you shouldn't do it. I wasn't thinking. I had one of my toughest subject exams the very next day. And I accidentally deleted build.prop and didn't have 5.0.2 factory image. But it's common sense why it will brick lol.
Also I was struggling to explain to my friend the spelling of fastboot and how there's no space in between. I'm sure he won't have problems with link2sd because he's not a SuperUser ?
He has issues with the limited internal but he survives.
Chirag_1537 said:
Maybe I didn't name the file correctly so it wasn't reading it. I'm not sure why it didn't work.
Hahahaha should've told me that in Jan. I bricked my device exactly by downgrading to 4.4.2. It's common sense why you shouldn't do it. I wasn't thinking. I had one of my toughest subject exams the very next day. And I accidentally deleted build.prop and didn't have 5.0.2 factory image. But it's common sense why it will brick lol.
Also I was struggling to explain to my friend the spelling of fastboot and how there's no space in between. I'm sure he won't have problems with link2sd because he's not a SuperUser
He has issues with the limited internal but he survives.
Click to expand...
Click to collapse
Well I hope the flashing goes well and your friend finds lollipop sweet enough. Actually I really feel the smoothness in the UI and If he doesn't mind the thing about link2sd etc he will probably love it.
Actually this build is quite bug free, but to some extent , don't know why but It is comparatively slow than Kitkat... So I reverted back to Cyanogenmod making a nandroid backup on twrp so that I can restore it whenever necessary...... So I think if you have not unlocked bootloader, you should wait for stable moto e lollipop release... I hope they will give it out soon!!
Regards
Andy
Andy1911 said:
Actually this build is quite bug free, but to some extent , don't know why but It is comparatively slow than Kitkat... So I reverted back to Cyanogenmod making a nandroid backup on twrp so that I can restore it whenever necessary...... So I think if you have not unlocked bootloader, you should wait for stable moto e lollipop release... I hope they will give it out soon!!
Regards
Andy
Click to expand...
Click to collapse
I did a factory reset after updating to lollipop and it is much more smooth than what it used to be on kitkat and also battery performance has improved after 2-3 days of flashing lollipop.
Related
Flashing the official gingerbread in u8800 its irreversivel process, at least for now.
If you flash it you have to keep it as no way of going back.
If you root it using the only available method, bye bye!
Everytime you reboot the endless bootlooping starts and the only way to stop it is formatting data.
Which means everytime you reboot = bye bye all data and apps etc.
I think is something that its major importance and no one is mentioning this!!!!
I don't know, maybe I've been preaching to deaf ears or something...but...you can re-install the old ROM back, the CWM recovery won't work with the official GB - that much is true - but you will be able to downgrade to an official 2.2.2 (I used the B162) version with the regular update method (at least I was and everything is working just as normal as it used to).
So, irreversible - I don't think so
with the current CWM recovery - it's a no-go
edit: that being said, what works for me, doesn't necessarily work for everyone, so be careful and blame the guy in the mirror -not me, if it doesn't work for you. =)
I think Huawei says wrong here. I flashed 2.3 yesterday. After that, because of the haptic issue I flashed back to official 2.2. Only problem after the 2.2, recovery console had opened. I did factory reset there and phone started without a problem. Then, I had upgraded to 2.3 again. Still haptic don't vibrate. Other than, no problem here. Maybe, I will go back again to 2.2.
Well you are lucky then because you are the only one.
Perhaps what is saying in the official intructions that will be impossible to dowgread after this upgrade won't apply to you.
I have try it with at least 8/9 versions of official release and nothing works!!!!
what 2.2 version is that and you did it after or before rooting?
Have you tried with internal sd? I copied dload folder to internal and started the upgrade process from Storage-Upgrade Firmware. Where did your phone stuck?
Edit: I didn't root my phone. Waiting proper solution. I had used B138.
no, I'm using external SD.
now I'm downloading another official release to try to downgrade using another one...
this time is U8800 V100R001C17B162CUSTC17D001
Druida69 said:
Well you are lucky then because you are the only one.
Perhaps what is saying in the official intructions that will be impossible to dowgread after this upgrade won't apply to you.
I have try it with at least 8/9 versions of official release and nothing works!!!!
Click to expand...
Click to collapse
Well, like I said, what works for me doesn't necessarily work for you.
Anyway, this is what I did and it worked, maybe it can help others.
0. Copy the original B162 ROM ("dload"-folder which has two files, UPDATE.APP AND UPDATE_CUST.APP) to the root of your SDCARD
1. Update to B162 by holding down +- keys while turning on the phone
2. After the first reboot, it's giving error messages for not being able to mount this and that...just ignore it and...
--> Wipe data / factory reset --> remove battery
3. Update the B162 again --> this time everything should go OK, if so, your phone is back to stock B162 and you're ready to use it or update a custom rom (just install Clockwork recovery like you used to and start from there)
The last point (3) may be unnecessary, but I did so just to make sure everything's ok.
Edit: OK, and I meant b162, not b160...
Druida69 said:
no, I'm using external SD.
now I'm downloading another official release to try to downgrade using another one...
this time is U8800 V100R001C17B162CUSTC17D001
Click to expand...
Click to collapse
For me it also works. I have downgrade without any problem and I use to the b 162 version. Now Ian back to oxygen
Sent from my u8800 using XDA App
yes I made it with this B162.
**** this **** I'm going back to custom rom.
No point of using this official release if future customs will use the libs from this one.
Druida69 said:
yes I made it with this B162.
**** this **** I'm going back to custom rom.
No point of using this official release if future customs will use the libs from this one.
Click to expand...
Click to collapse
And then there's the fact that the official gb is still beta, it's not supposed to work perfectly. But as long as the dev team here stays active, I think that I'm gonna stick with custom roms too.
ho my god.
didn't work.
is always booting into recovery
I am stuck here also (
Nothing worked
I tried clockwork recovery - it doesnt get to. It is just rebooting.
I tried with various dload UPDATE.IMG's (GB Overseas, GB orig chinese,B162,B138) nothing is working - stucked in "Step 1/2 Unpacking" window forever.
Anyone has solution for this ?
Two weeks ago I've flashed the U8800Pro version - real mistake
I've started a topic here:
http://forum.xda-developers.com/showthread.php?t=1327715
katu2006 and on the second page flibblesan gave me a method to start my phone working well.
Post #4, #11 and #13.
Maybe this will help you,too?
sbasil said:
Anyway, this is what I did and it worked, maybe it can help others. (...)
Click to expand...
Click to collapse
You sir are a LEGEND. My phone "lives" again! On CM7 again...
manage to install miui.
several versions now up to the newest one.
I noticed on all of them that it mount the SD card when connected to USB but only shows the system files and not allow writing, copy, cut, etc.
Saying that I dont have permission to change the SD
Druida69 said:
Flashing the official gingerbread in u8800 its irreversivel process, at least for now.
If you flash it you have to keep it as no way of going back.
If you root it using the only available method, bye bye!
Everytime you reboot the endless bootlooping starts and the only way to stop it is formatting data.
Which means everytime you reboot = bye bye all data and apps etc.
I think is something that its major importance and no one is mentioning this!!!!
Click to expand...
Click to collapse
I have just flashed with new U8800V100R001C00B517G001(Beta1.0)(Overseas Normal)(Gingerbread) but after flashing I kept waiting for start my phone. I restasted many times but same, then I format data its worked and when restarted again it goes in same condition any help ?
until flash disk is writable and it is - there will always be way to go back to old versions it just files.. like reinstalling windows on your pc.
Since the new Rom is public I have read all posts about it here. Maybe I had lucky, or simple due it without messing with the files.
Yesterday I made the upgrade to the new rom, directly from the last Oxigen version, without downgrade to 2.2. I simply create the dload folder on SD card, put there de update file, boot with +- Power, and chose upgrade from SD card.
After step 2 I reboot the phone a install step 3 upgrade. Everything as installed fine, no boot loops, nothing...
Also the root method decribed in this forum as work on first time.
24 hours after the upgrade, and some reboots to test, I never se the boot loops, and the phone is working well.
The new ROM, even in beta stage, to me is a great improvement.
Well either you were lucky or me and the majority were unlucky.
But issues only start to happens when rooting.
So that you can see it fried me the 1 USB cable. This cable is only good to charge the battery now....
Also, ****ed the device USB storage MOUNT.
I connect it to the computer and the computer sees it as a CD drive not allowing any changes.
Also when press the button to mount the USB on the device it never gets mounted and gives the messages that the SD can now be removed.
So I have put this issue many times but up to the moment no one even reply to help.
Its actually only 6.0 oops didn't look
If you are getting Error 7 Restore the stock system.img and it will flash
this is being uploaded i will have it up by the end of this day 1/4/2016
Update.zip file found here - Google Drive
when of course i get it fully uploaded
So if you have any questions or comments feel free to email me at [email protected] or text me at 5418870575 I do have school since I'm only 16 but will get to you asap
Me and 6th_Hokage think that the bootloaders completely locked because of the messages that the terminal gives system.img is unavailable because of this reason
Instructions
Step 1: Download the zip to your sdcard.
Step 2: Boot your phone into recovery mode by turning off your phone then holding the power and down volume button at the same time. Holdthese buttons until you see the recovery mode screen
Step 3: Navigate the menu by using the up and down volume buttons. Push the down volume button until you reach Update using sd card" It should be the last selection on the menu,
Step 4: Select this option by pressing the power button Once Step
5: Install the zip by selecting the update.zip.
Step 6: Let the install run(total time took about 15 minutes for me)
Step 7: Reboot the phone.
Your done.
I can't pull the system img I already posted what I was getting trying to pull it - bootloaders completely locked no way of bypassing it so far
Want to watch some tutorials on how to install the stock zv4 or zv5 come on by to my YouTube channel - Dominic Gresham
Ok ill say it... What the hell is this? Where did it come from?
Since Boost has already started OTA, I imagine Dominic is capturing and preparing to upload it for us.
jmacie said:
Since Boost has already started OTA, I imagine Dominic is capturing and preparing to upload it for us.
Click to expand...
Click to collapse
exactly i will also have a youtube video showing up soon enough
Well it should be 6.0.1 because that's what ZV7 is so so so... get some kind of confirmation on it 'cause I'm pretty sure there's no 6.0.0 for our CDMA devices.
kcarden said:
Ok ill say it... What the hell is this? Where did it come from?
Click to expand...
Click to collapse
boost mobile a week ago said that marshmallow 6.0 was coming out for the phone im half way uploaded it should be up vary soon maybe like another 20 minutes but i did run into some issues when capturing the system.img
here i have attached a image of the error that i get and its a weird one
DominicGresham said:
boost mobile a week ago said that marshmallow 6.0 was coming out for the phone im half way uploaded it should be up vary soon maybe like another 20 minutes but i did run into some issues when capturing the system.img
here i have attached a image of the error that i get and its a weird one
Click to expand...
Click to collapse
thanks 6th_Hokage again for the commands
br0adband said:
Well it should be 6.0.1 because that's what ZV7 is so so so... get some kind of confirmation on it 'cause I'm pretty sure there's no 6.0.0 for our CDMA devices.
Click to expand...
Click to collapse
ya it is 6.0 thats the android version
Well that ain't right, geez, guess they'll have to push another update at some point to get that .1 happening. Bleh, I'm selling my Stylo this morning anyway so I guess I'm pretty much done with them till I can find a good deal on a T-Mobile model, the 1GB of RAM just ain't workable for me.
Is this for the sprint lg stylo too thx
i instaled update.zip i put in sd card recovery and install beware they stuck in update system image long time but they instaled fine
Thanks Dominic! and also [email protected] for preparing me to be patient for the update to install. Looking forward for the root solution Dominic, Thanks again!
br0adband said:
Well that ain't right, geez, guess they'll have to push another update at some point to get that .1 happening. Bleh, I'm selling my Stylo this morning anyway so I guess I'm pretty much done with them till I can find a good deal on a T-Mobile model, the 1GB of RAM just ain't workable for me.
Click to expand...
Click to collapse
You must be new to the whole Android thing
add
jmacie said:
Thanks Dominic! and also [email protected] for preparing me to be patient for the update to install. Looking forward for the root solution Dominic, Thanks again!
Click to expand...
Click to collapse
thanks and work great is less lagging and more fast response
the one thing we now have to work on is root for 6.0 and pulling the system.img i can look into the international G3 forums to see how they did it
---------- Post added at 06:10 PM ---------- Previous post was at 06:09 PM ----------
mike9976 said:
Is this for the sprint lg stylo too thx
Click to expand...
Click to collapse
should work an technically you should've gotten it first ._.
Where is the option to adopt sd card??
I did the update through recovery and the only thing i can't seemed to find is how to make sd card adoptable on my lg stylo??
Hey guys two quick questions, first the download seems to not be working, maybe uploading it someplace else would alleviate that. Secondly, doesn't booting into recovery force you to do a factory reset? If anyone that already flashed can clear that up I'd be grateful...
Anyone with root able to uninstall root and install update yet?
Either with simple unroot or factory reset
Blu8 said:
Hey guys two quick questions, first the download seems to not be working, maybe uploading it someplace else would alleviate that. Secondly, doesn't booting into recovery force you to do a factory reset? If anyone that already flashed can clear that up I'd be grateful...
Click to expand...
Click to collapse
Blu8, I just re-dwnld's it went a 8,5 MB/s, that's my max ( downl'd to my PC, then transferred to my SD) and it was fine. So I don't know. Some guys on the facebook stylo page just now were having problems straight dwnloading to their phone, so I don't really know.
Kolma- I used the Un-root and un-brick-xda- http://forum.xda-developers.com/android/development/official-boost-lg-g-stylo-unbrick-guide-t3215198
then I used Dominic's update.zip in his OP on the first page and it all went fine. It took a bit of time to check, extract and install, so be patient, but it went fine for me. Good Luck!
This is Edwin bro lol thanks again
Sent from my LGMS631 using Tapatalk
Hey guys, thought I would make a discussion thread about the new update today for the Sprint S5's. Looks like todays update was just over 200 MB. I don't know if it affects the latest chainfire root yet or not.
But yeah, make your stock S5 search for a update and you should find one waiting.
I've noticed:
The Android Security Patch Level is now December 1, 2016
Software version is now G900PVPU3CPL2
Do we know how long Samsung will continue to update our phone OTA? I appreciate that we still have support. It's not so bad being 1 month behind in security updates since even with security updates we are still vulnerable to 0-day exploits anyway.
Does anyone have a copy or link to this update? I want to see if it helps with signal on nougat based roms.
Thanks in advance
KIES
The~Skater~187 said:
Does anyone have a copy or link to this update? I want to see if it helps with signal on nougat based roms.
Thanks in advance
Click to expand...
Click to collapse
The best way to actually try and get this is through Kies or SmartSwitch apps. Sam Mobile does not have this, and it would be, about another month from now, till they even have it... Been there too many times looking for this so call update.
I know that is does state 01dec2016 security update. I also know, that Knox is added to (at least, all Knox is added data (Kbs, not Mbs) I also believe, they (Samsung, tech side phone updates) have added more apps for Knox. However, we don't have anything that is related to these new updates. heck 2 of them, state they have DATA. Through the stock app manager, you have an option, to erase this, because it is not installed....
not sure if this helps you find what you are looking for. ...
( me 2cents on this),... Why extra apps and data../. Why do we have to download a complete new Stock Rom, when we already were stock anyway ???) (Me dog did a real number on the phone. had to be a good eBay and Amazon shopper... Completely rebuild my S5.
Wondering if the S5 will be having A real update, such as 7.1... ??? !!!) we S5, was not on or in the press release early this month, regard the Samsung, Android updates... 7.0, 7.1 NOUGAT !!!
I certainly believe that they will in time update the S5 to 71 Nougat
This may just be a hunch but I have a feeling that if the Note 8's don't blow peoples faces off that the S5 probably won't be seeing Nougat officially (from Sammy).
Well there's a new update today for me anyways. This one is just over 27 MB's. 2 new updates in one month!
The new software version is called G900PVPS3CQA2
New antutu score updated.
It's very unlikely that S5 will receive an official N OTA from any carrier(or any msm8974, for that matter) as Qualcomm had planned 'no official support' for msm8974 past M. It was already very late in the cycle for M, and may not have made it onto the list for M had the msm8994 sucked less.
Does anybody know if we are still able to root our phone model with this new update?
LEN671 said:
Does anybody know if we are still able to root our phone model with this new update?
Click to expand...
Click to collapse
I don't know for sure myself, as I have not gotten the update bring on aftermarket firmware. But I would imagine if you flash twrp and apply the latest supersu, it should work. I know that's how I did it with the cpk1 update.
Someone please correct me if I am wrong. I don't want anyone bricking their device based on what I've said.
LEN671 said:
Does anybody know if we are still able to root our phone model with this new update?
Click to expand...
Click to collapse
Yes.. I did
I ran into some issues and factory reset, deleted my Internal Storage, and then ODined PK1 Stock onto my Sprint S5. I then got a prompt that G900PVPU3CPL2 update was available. After the phone restarted I was then prompted to update to G900PVPS3CQA2 After that one installed and restarted.. I successfully rooted using CFAutoroot and then put the latest TWRP Recovery on.
Now.. what screwed me up is me trying to put a 7.1.1 Rom on (LOS and even Resurrection Remix). Phone froze and would not allow me to enter any info in or select Wifi. When it did.. I had ZERO signal/data. I then re-odined.. PK1.. without the updates, rooted, and Twrped, then flashed the 7.1.1 (LOS and RR) with no problems. Made back-ups of both (within TWRP) and was able to Restore all three at will. I am currently back on the STOCK/ROOTED w/all updates including the QA2.. as I didn't feel like doing the customization of the 7.1.1. Roms with the game (SuperBowl) getting ready to come on.
Personally I like the Stock- Rooted -Updated- Twrp config as the only thing that bothers me is the heading theme being that Samsung Aqua blue. If I could theme it.. I might stay with it
Cmicasa the Great XvX said:
Yes.. I did
I ran into some issues and factory reset, deleted my Internal Storage, and then ODined PK1 Stock onto my Sprint S5. I then got a prompt that G900PVPU3CPL2 update was available. After the phone restarted I was then prompted to update to G900PVPS3CQA2 After that one installed and restarted.. I successfully rooted using CFAutoroot and then put the latest TWRP Recovery on.
Now.. what screwed me up is me trying to put a 7.1.1 Rom on (LOS and even Resurrection Remix). Phone froze and would not allow me to enter any info in or select Wifi. When it did.. I had ZERO signal/data. I then re-odined.. PK1.. without the updates, rooted, and Twrped, then flashed the 7.1.1 (LOS and RR) with no problems. Made back-ups of both (within TWRP) and was able to Restore all three at will. I am currently back on the STOCK/ROOTED w/all updates including the QA2.. as I didn't feel like doing the customization of the 7.1.1. Roms with the game (SuperBowl) getting ready to come on.
Personally I like the Stock- Rooted -Updated- Twrp config as the only thing that bothers me is the heading theme being that Samsung Aqua blue. If I could theme it.. I might stay with it
Click to expand...
Click to collapse
Thank you for the info!! This is what I wanted to hear!! Someone who had the newest update and then went into detail of what they encountered. Thank you again!! Much appreciated!!
You can always see the latest official stuff for our phones here: https://www.sammobile.com/firmwares/database/SM-G900P/SPR/
The only way we'll ever see Nougat on the S5 is via rom ports, or CM14/CM14.1 Official, which is supporting the S5.
LEN671 said:
Thank you for the info!! This is what I wanted to hear!! Someone who had the newest update and then went into detail of what they encountered. Thank you again!! Much appreciated!!
Click to expand...
Click to collapse
No problem. After using the STOCK/ROOTED MM version with all the updates , I have decided that I really am just gonna stay on it. It is smooth, fast, and has all the things I need. I killed Bloatware so outside of the pull-down bar being aqua blue.. and background being white I'm very content.
Anyone know of an app for rooted phones that will allow me to rectify those things?
Cmicasa the Great XvX said:
No problem. After using the STOCK/ROOTED MM version with all the updates , I have decided that I really am just gonna stay on it. It is smooth, fast, and has all the things I need. I killed Bloatware so outside of the pull-down bar being aqua blue.. and background being white I'm very content.
Anyone know of an app for rooted phones that will allow me to rectify those things?
Click to expand...
Click to collapse
@cmicasa the Great, I keep getting a failed when using Odin, CFAutoroot, KingoRoot, KingRoot, and even when I try to use TWRP. I also read somewhere that I would have to unlock the Bootloader in order for this to work? Do you mind sending me a message in PM about how you did your rooting? If you don't mind sir. Thank you again for your time and assistance.
LEN671 said:
@cmicasa the Great, I keep getting a failed when using Odin, CFAutoroot, KingoRoot, KingRoot, and even when I try to use TWRP. I also read somewhere that I would have to unlock the Bootloader in order for this to work? Do you mind sending me a message in PM about how you did your rooting? If you don't mind sir. Thank you again for your time and assistance.
Click to expand...
Click to collapse
This is everything I did including putting PK1 on my phone, letting it then upgrade to G900PVPU3CPL2 and then update to G900PVPS3CQA2 After that one installed and restarted.. I proceeded to Root and put custom recovery on. Because U will not get the OTA updates once U root
Here are my steps Len:
1) First make sure U have the ODIN 3.10 or above> Links are here SamsungOdin or here Odin Download
2) Then go into Download Mode by pressing the "Volume down +home and then Power buttons" Once device boots hit the volume up button and Android dude should appear
3) open ODIN (I used 3.10) and plug phone to computer.
Load the PK1 tar in the PDA Slot, put your phone in Download Mode (power off, hold Vol Down, Home, and Power), and connect your phone to the PC. (I checked F.Reset and Auto Reboot)
Then after that is successful run CF Auto Root or whatever root injector you have in the PDA slot again. Once that finishes (wait until Odin tells you it was a Success before doing anything), get ROM Toolbox or something of that nature and remove any app with Knox in the title or that has the Knox symbol.
Load your phone into Download Mode one last time and then put whatever recovery you have (I use TWRP, make sure you grab the .tar format instead of the zip) and put that in the Bootloader slot in Odin. Then you're good to go, rooted and custom recovery, sky's the limit.
-I found a perfect site that does exactly what I did using CFAUTOROOT. It explains everything including TWRP
then for Root http://www.stechguide.com/root-samsung-galaxy-s5-android-marshmallow/
then for Recovery http://www.stechguide.com/install-twrp-recovery-samsung-galaxy-s5/
Cmicasa the Great XvX said:
This is everything I did including putting PK1 on my phone, letting it then upgrade to G900PVPU3CPL2 and then update to G900PVPS3CQA2 After that one installed and restarted.. I proceeded to Root and put custom recovery on. Because U will not get the OTA updates once U root
Here are my steps Len:
1) First make sure U have the ODIN 3.10 or above> Links are here SamsungOdin or here Odin Download
2) Then go into Download Mode by pressing the "Volume down +home and then Power buttons" Once device boots hit the volume up button and Android dude should appear
3) open ODIN (I used 3.10) and plug phone to computer.
Load the PK1 tar in the PDA Slot, put your phone in Download Mode (power off, hold Vol Down, Home, and Power), and connect your phone to the PC. (I checked F.Reset and Auto Reboot)
Then after that is successful run CF Auto Root or whatever root injector you have in the PDA slot again. Once that finishes (wait until Odin tells you it was a Success before doing anything), get ROM Toolbox or something of that nature and remove any app with Knox in the title or that has the Knox symbol.
Load your phone into Download Mode one last time and then put whatever recovery you have (I use TWRP, make sure you grab the .tar format instead of the zip) and put that in the Bootloader slot in Odin. Then you're good to go, rooted and custom recovery, sky's the limit.
-I found a perfect site that does exactly what I did using CFAUTOROOT. It explains everything including TWRP
then for Root http://www.stechguide.com/root-samsung-galaxy-s5-android-marshmallow/
then for Recovery http://www.stechguide.com/install-twrp-recovery-samsung-galaxy-s5/
Click to expand...
Click to collapse
Thank you very much for breaking it down dummy style. Haha. It definitely helps. I will try it out when I get to my house and PC.
LEN671 said:
Thank you very much for breaking it down dummy style. Haha. It definitely helps. I will try it out when I get to my house and PC.
Click to expand...
Click to collapse
LOL.. no issues. Definitely go to those bottom links. They even have pictures. Be careful though.. I tried to experiment and see what checking the "Nand and Erase" in odin.. and damn near bricked my phone. Had to get PIT file and rebuild. Working smoother than ever now.. and like I said.. I'm sticking to Stock/Rooted and Xposed
Cmicasa the Great XvX said:
LOL.. no issues. Definitely go to those bottom links. They even have pictures. Be careful though.. I tried to experiment and see what checking the "Nand and Erase" in odin.. and damn near bricked my phone. Had to get PIT file and rebuild. Working smoother than ever now.. and like I said.. I'm sticking to Stock/Rooted and Xposed
Click to expand...
Click to collapse
So just to clear, there is no need to unlock the Bootloader? Also, if my phone has a password, does it need to be disabled? I.e. lock security feature such as creating a pattern in order to unlock the device to use.
LEN671 said:
So just to clear, there is no need to unlock the Bootloader? Also, if my phone has a password, does it need to be disabled? I.e. lock security feature such as creating a pattern in order to unlock the device to use.
Click to expand...
Click to collapse
I'm confused on that. Your phone will be booted into DOWNLOAD mode during the time of ODIN. Your Password will be inconsiquential
Cmicasa the Great XvX said:
I'm confused on that. Your phone will be booted into DOWNLOAD mode during the time of ODIN. Your Password will be inconsiquential
Click to expand...
Click to collapse
Okay, I am just making sure as I am not sure if that was one of reasons why Odin came back saying "FAIL". Thank you again.
Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.
vsriram92 said:
Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.
Click to expand...
Click to collapse
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.
So nice of their support site to be down...
tomlogan1 said:
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.
Click to expand...
Click to collapse
Instructions > https://forum.xda-developers.com/honor-5x/how-to/guide-force-installing-stock-ota-t3502874
What are the bug fixes???
Are there any new features???
I am currently on custom ROM and would like to know the answers to these questions to see if it's worth it to go back to stock rom
Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.
m0ndul said:
Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.
Click to expand...
Click to collapse
So much miss information .. no one bothers to find the truth
Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.
animeme said:
Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.
Click to expand...
Click to collapse
Link below or install the Huawei Firmware Finder form the Google Play Store and set it up to get OTA files in settings.
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=kiw-l24
deleted
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
What he said.
I'm hoping it's nothing more than a VoLTE update that LOS maintainers warn against anyway, if there's actually no one to further explain what it is
received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature
my kiwi-L24 got re-flashed today, it is weird that this B351 update is no longer available from B331's update check
searched on internet, there is news about "honor 5c" getting a B351 nougat update
This came up on one of the 5X's that I have. Updated and forgot to put back stock recovery. Don't be like me and forget to do that. Now it won't work properly and I can't get to start any apps to try and fix it. I can put back TWRP and wipe it, but I don't want to lose my data. I also have that problem now where it keeps telling that the SD card is corrupted. I backed up the data and scrubbed the card in the phone but it keeps coming back with the same thing.
If someone did an actual successful update properly (with stock recovery) then please update and say if everything is working. If not, I'm going to have to find some way to backup the data and then scrub it.
*EDIT*
I believe something like this happened to me before. I was on B151 and went to B331 with TWRP installed by accident. What happened was that the OS was still running EMUI 3.1 but the build was saying B331. After fighting with it (and community support) I managed to get it to B331 fully and EMUI 4.0 - since then and a few custom ROMs I'm back on B151 EMUI 3.1 due to stability. Games and some apps just didn't work on the new one. The second phone was on B331 fully though - then I made the same mistake and it went to B351. This time though, the phone seems screwed. No apps will load. I can get into settings and the file manager, but no Titanium Backup and no Flashify. Going to put back TWRP and try to flash GAPPS and see if it will help me get into Play Store. From there I'll try to reinstall Flashify and flash the ZIP of the update. Will post back once done.
*EDIT*
Well that didn't work. Even after going back and trying to root the device again - then checking the option for it to not detect the dirty flash - still didn't work. Kept complaining that stock apps are already present.
I'm going to try and get some files off the device, but keep having issues. Not sure why. May just have to scrub. Will update again.
*EDIT*
With TWRP on I used "ADB PULL" to get certain files from the root system which I couldn't access otherwise for some reason. Then copied the other things (photos and such) and will now be using the UPDATE.APP to get it working. For this I formatted the SD from within TWRP and created the DLOAD folder (with no caps - so that's dload - but I'm not sure if it matters) and will be copying the UPDATE.APP. Not sure which version yet, because there was some problem with one I had downloaded before. So I need to double-check and re-download.
*EDIT*
So I've successfully flashed the UPDATE.APP from the SD card (same one the phone was claiming is corrupted). Just for reference, here is the file information and hashes.
File Name: Honor 5X_Firmware_KIW-L24_Android 6.0.1_EMUI 4.0_C567D003_United States.zip
Size: 1762266487 bytes
ADLER32: 27cb0c31
CRC32: 1d9379b9
MD2: 6517c34dc9bac0cd8680e3c4fd09d8d9
MD4: 4a803765c0ed54cb5d6853a9f365cd3b
MD5: 04f60b067d546ad71f556e44a7934dc7
SHA1: 8d2718568ac6509a40c95e42857d400395eb88d2
SHA256: 82975923172b3800d3f09f76691f2a694ab98110e3f909084a02bd566448386f
SHA384: da53b58b8e20395595590fd0cec30e56fa6a62e638ec53e46a74ebf58d051fdd7576602019bd3130ca5c00cc432715a0
SHA512: 806e0e8969c293ca8b497a786699ee306352ad6ef434552f2d23decff8a5279c7fd605e046c13f11c2f87947f5a2bdf23d78fdec6263661e68f023fd72bf4381
RIPEMD128: 9d963e5d51c9df9554fa3422da84dd27
RIPEMD160: a1e5b8f08b65dd2bb08e04d62db270ad8f4cf51a
TIGER128: 66fb4e4e4ce11cb30626aea807355f83
TIGER160: 66fb4e4e4ce11cb30626aea807355f8345f1dd79
TIGER192: 66fb4e4e4ce11cb30626aea807355f8345f1dd79dbb39488
GOST: 93774537f6ca49d4406f9d3a0316d014e1e099b34fc1cd9b968dacc870700827
The file name may be different, but as long as you got the right one you should be OK. If you have issues when copied to an SD card - verify that the file on the SD card has the correct hashes. To make it faster use CRC32. For more surety, use MD5. You can get a tool like WinMD5 to check. It's free.
So now that it's done, I'm going to set it up as a new phone and wait to see if the update comes back on. If it does, I'll get it down and upload the B351 recovery. After that I'll need to remember that I have to put back the stock recovery before running any updates. Flashify FTW.
BTW - during the initial setup after connecting to wireless it came back with the update. Pics to follow.
Files will be uploaded here: https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
*EDIT*
So the files are uploading to the folder. The screenshot is attached. Had one issue where after the update I couldn't get back into the phone. Had to wipe/factory reset. I've used FASTBOOT BOOT TWRP.IMG to take the backups of the BOOT and RECOVERY. Hopefully one of the gurus can use that and give the IMG files. I'm going to try root and get FLASHIFY to backup the stock recovery and add to the folder.
khat17 said:
This came up on one of the 5X's that I have...............
Click to expand...
Click to collapse
I don't really like to do double replies, but I guess for ease of finding the info it's better this way. Unless a mod thinks differently and wants to merge all the info.
Google Drive Link With Files
https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
This contains TWRP backups of the recovery and boot images. There's also a file called KIW-L24-B351 which was created with Flashify. I assume you can add the IMG extension to it and flash as needed.
Basically I had this update run on another phone (my wife's) and it messed with the phone due to the recovery being TWRP and not stock. My fault - forgot to do that before handing the phone back to her. I believe it happened to me before but it never messed up the phone this way. Nothing would work except core apps like settings and the stock file manager. The Play Store wouldn't even open.
Anyways - back to factory with UPDATE.APP then run the automatic update from an OTA update on wireless, then FASTBOOT BOOT TWRP.IMG and capture the backups. Then flash SuperSU to get root. Then Flashify. Files are uploaded for your convenience.
Warning that during the initial OTA it took a while. And after it was done I couldn't get into the phone with the password. Had to factory wipe/reset again and setup again. Disable passwords just in case I guess. Hope this helps others - have fun.
No major differences. I haven't really used the stock OS6 but some things look a little different. Nothing major. Will see when she's using it if it lags or has improved memory and such. Not sure if I'll be able to test with apps that wouldn't run previously for me, but will see. Tested with TransDrone and it failed. Once SeedBox information is loaded it still crashes. Only happens on OS6 so I'm sticking with OS5 on mine. Does not happen with custom roms however (from what I recall - would have to check back).
Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.
raulpcamara said:
Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.
Click to expand...
Click to collapse
Follow this video if don't know how to flash back stock recovery through adb. Then take a look at those threads how to downgrade, here, here, here. Hope it helps.
bluesky299 said:
received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature
Click to expand...
Click to collapse
Same here.
It had been too many months of the Honor 5X in the closet so i almost lost track what to do but what i did was revert all the way back to Stock ROM (had to flash an extracted/saved Recovery.IMG) and then do the UPDATE.APP from Dload complete and repeat on up to the current B351.
Of course lost Root but when ready can add that back too.
Yes the Honor 5X runs much smoother now than before plus that Battery Drain issue (Remember That?) where we had to dig deep to change 4 to 0 i think, well Battery Life is also greatly improved on mine.
GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
I tried to update as the previous user did using TWRP and got the corrupted SD card message. I then tried to go back to stock ROM. Went into bootloop.
Been having a hell of a time getting anything to work properly since.
I have a xperia c4 e5303, is a awesome device and 5-6 days ago i wanted to use xposed firmware to enable a fake gyroscope.
AND THE HELL STARTED.
I had the device rooted with custom recovery twrp when i was in lollipop 5.1, i installed the firmware for xposed and the phone was stucked in "android optimization", for hours. I restarded it sometimes but nothing, so i formatted my device and when i rebooted it, i was stucked in "sony" logo screen, some minutes ago i founded that my phone was totally empty.
c: *internal screaming*
I waited the next day, i downloaded the ftf of original marshmallow 6.0 firmware for sony xperia c4 and i installed it on my device, then everything worked perfectly luckely.
Easy peasy lemon squeezy, or not?
Some hours after i founded that i couldn't use the recovery mode!
I searched and searched and i founded that the problem could be the bootloader,so i used a sony official guide to unlock that.
I couldn't finished that guide becouse with any connection, on any computer, android sdk can't install his components(such as google usb driver, that are required for that method), and the program just install everytime the same package in loop. I tried aaaallll the method in the universe for that, i tried also to install once per once the zip files of the downloaded package but it was totally useless.
So i founded another method after some days of searching (with flashtool) and now my bootloader is fully unlocked, if i use flashtool to unlock the bootloader, it says that is unlocked and ask me if i want to relock it so i think now the bootloader unlock is done. FINALLY.
Then, i turned off the phone and started it by pressing the volume down+power botton, and all the device did was reboot himself repitetly until i release hard keys and when i do it the phone start automatically.
I think my device now reboot himself instead of going in recovery mode.
What can i do i am totally frustrated about this and i really don't want to buy a new device becouse i don't have a gyroscope. I love my xperia c4, i just don't know why i can't get the recovery mode back to install twrp, for rooting the device, for retry to get xposed virtual sensor and then finally enjoy my vr experience...
In the end, i have a Xperia C4 5303 with original Marshmallow 6.0 firmware installed, that can't go in recovery mode in any ways.
Pls someone help me..
no one?..
No one here know hot to save my smartphone?
update: now i can use fasboot and adb commands becouse i installed the drivers properly.
but i still can't flash a custom recovery to get the root..
asnachan said:
update: now i can use fasboot and adb commands becouse i installed the drivers properly.
but i still can't flash a custom recovery to get the root..
Click to expand...
Click to collapse
Digging through XDA (next time use the website's search bar, tee hee hee) I found this thread:
https://forum.xda-developers.com/xp.../bootloader-unlocked-custom-recovery-t3285521
Edit: I know it says C5 Ultra whatever but the thread says it also works with your model (C4 E5303 no?)
Before trying anything, I'd seriously recommend reading all eleven pages so you don't miss anything and end killing your phone (or back at square 1).
I'm not an expert on Android or anything (I personally have only owned 1 device — a first gen Moto G), but the method presented in the thread is very odd. Are all Xperia phones this weird?
Read carefully — some steps might be unnecessary (after all, you already unlocked your bootloader [maybe?])
P.S. you lost the recovery because by installing the original firmware it basically got erased (original firmware didn't have TWRP after all!)
P.S.S. you should create a backup once you get TWRP up and running, just in case.
I can't help you more than this because I do not own the device, so I cannot share ~personal wisdom~ with you (beyond recommending the Moto G series).
Good luck!
( And search the forums and threads before posting — that's an XDA rule! )
Sent from my Motorola Moto G using XDA Labs
thx
Bludwurst said:
Digging through XDA (next time use the website's search bar, tee hee hee) I found this thread:
https://forum.xda-developers.com/xp.../bootloader-unlocked-custom-recovery-t3285521
Edit: I know it says C5 Ultra whatever but the thread says it also works with your model (C4 E5303 no?)
Before trying anything, I'd seriously recommend reading all eleven pages so you don't miss anything and end killing your phone (or back at square 1).
I'm not an expert on Android or anything (I personally have only owned 1 device — a first gen Moto G), but the method presented in the thread is very odd. Are all Xperia phones this weird?
Read carefully — some steps might be unnecessary (after all, you already unlocked your bootloader [maybe?])
P.S. you lost the recovery because by installing the original firmware it basically got erased (original firmware didn't have TWRP after all!)
P.S.S. you should create a backup once you get TWRP up and running, just in case.
I can't help you more than this because I do not own the device, so I cannot share ~personal wisdom~ with you (beyond recommending the Moto G series).
Good luck!
( And search the forums and threads before posting — that's an XDA rule! )
Sent from my Motorola Moto G using XDA Labs
Click to expand...
Click to collapse
Thanks a lot for your time, but i am using that thread to root this, and i am stucked at the last point becouse i don't know what he means with:
"THIS IS IMPORTANT
The rom has
Code:
recovery.from.boot.p"
I did all the steps except for that, and i get no errors but when i try to boot in recovery the phone just stay on the logo and then after some minutes reboot himself and starts normally.
i already ask what the last point is in that thread
p.s.: i know i will not have twrp if i reinstall stock fw, but the point is that i don't have also the normal recovery, i can't access to that via adb or via hard keys..
asnachan said:
Thanks a lot for your time, but i am using that thread to root this, and i am stucked at the last point becouse i don't know what he means with:
"THIS IS IMPORTANT
The rom has
Code:
recovery.from.boot.p"
I did all the steps except for that, and i get no errors but when i try to boot in recovery the phone just stay on the logo and then after some minutes reboot himself and starts normally.
i already ask what the last point is in that thread
p.s.: i know i will not have twrp if i reinstall stock fw, but the point is that i don't have also the normal recovery, i can't access to that via adb or via hard keys..
Click to expand...
Click to collapse
Ah. You should've mentioned it (i.e. linked to the guide). Sorry sorry!
Read further down. The "recovery.from.boot.p" is this thing that overwrites TWRP with the stock recovery. Following the «THIS IS IMPORTANT» indication are instructions to get rid of the thing, and so being able to keep TWRP permanently.
You need that last step to succeed.
Sent from my Motorola Moto G using XDA Labs
in the other thread they said to me to roll back to 5.1 i am doing it now
nvm i got hard brick, the phone is dead and i can't enter in download mode....
asnachan said:
nvm i got hard brick, the phone is dead and i can't enter in download mode....
Click to expand...
Click to collapse
I'm very sorry to hear that ?
Sent from my Motorola Moto G using XDA Labs
Is fine, i had to buy another phone that is why is tarted to root the xperia.
just..i'm out from the world of rooting i think. i broke 2 devices 1 by flashing a original rom with sony original flashtool and 1 by installing a root with kigroot, and now on that i can't read the sim.
i wait until the world of rooting will be more stable and with more official custom roms...
RIP